If you need to reorganize the network card of a XenServer for any reason, follow the procedures below. Note XenServer 6.1 has an easier way to reorder the NICs and instructions are here - http://support.citrix.com/article/CTX135809
1. The first step is to add the static mapping the card in the name of that device configuration file:
/etc/sysconfig/network-scripts/interface-rename-data/static-rules.conf
for example, to assign the NIC with the MAC address "00: 25: B5: 16: 01: DF" on behalf of the eth2 device, add this line to the static file rules.conf:
eth2: mac = "00: 25 : B5: 16: 01: DF "
2. After adding the static mapping rule, run interface-rename.py:
/etc/sysconfig/network-scripts/interface-rename.py
3. Check that the mapping is correct by looking /var/log/interface-rename.log.
if successful, the log will show something like:
INFO [2013-02-28 10:33:02] NIC side eth2 -> (00: 25: B5: 16: 01: DF, 0000: 07: 00.0) is moved on the PCI bus eth2 -> (00: 25: B5: 16: 01: DF, 0000: 07: 00.0)
INFO [2013-02-28 10:33:02] with renowned success-side link eth2 eth2 to
instead, if you see a mistake he is unable to rename like this message:
error [2013-02-28 10:31:27] Can not rename link to side-eth2 eth1 . (Exit 2)
Then try to change the device name (eth) in this file as:
/etc/sysconfig/network-scripts/interface-rename-data/dynamic-rules.json
Look for the MAC address of the network card you want to edit and rename the "ethX". If you have another network adapter that is already using the same device name, you must change too. Legitimately, dynamic-rules.json updated when interface-rename.py runs, but I still get problems with the script when he tries to do the update. Thus, I find that the update rules.json dynamic file using manually to get past the error.
If you need to rearrange some NICs, it is preferable to add the static mapping one at a time. Make the first network adapter, run interface-rename.py, make sure that the mapping is updated correctly in dynamic-rules.json, then proceed to add the next NIC.
4. Once everything is done, make a snitch-scan :.
xe pif-scan host uuid =
and restart the server to ensure that the work of rearrangement
0 Komentar