Interface mappings on SDX picked wrongly
Article ID: CTX208375
Updated On:
Description
Interface mappings on SDX 22040 changed when the device came up. Customer was using four 10 gig interfaces which are part of LA channel. When the device booted up he noticed that if a cable is connected to let’s say 10/17 interface on the device then on SVM he can see that 10/19 is shown up.
Resolution
We have suggested a factory reset of the appliance to fix this issue.
Customer did the factory reset and after that we could see that the interface mappings were picked properly.
Kern.log:
Feb 25 00:41:14 netscaler-sdx kernel: [ 64.652006] eth4 renamed to eth26 by udevd [17803]
Feb 25 00:41:14 netscaler-sdx kernel: [ 64.951906] eth5 renamed to eth27 by udevd [17988]
Feb 25 00:41:14 netscaler-sdx kernel: [ 64.952696] eth6 renamed to eth6_rename by udevd [17990]
Feb 25 00:41:14 netscaler-sdx kernel: [ 64.961866] eth9 renamed to eth29 by udevd [17994]
Feb 25 00:41:14 netscaler-sdx kernel: [ 64.991648] eth0 renamed to eth0_rename by udevd [17998]
Feb 25 00:41:14 netscaler-sdx kernel: [ 65.011838] eth8 renamed to eth28 by udevd [18003]
Feb 25 00:41:14 netscaler-sdx kernel: [ 65.069326] eth6_rename renamed to eth8 by udevd [17990]
Feb 25 00:41:14 netscaler-sdx kernel: [ 65.432173] eth7 renamed to eth9 by udevd [18057]
Feb 25 00:41:14 netscaler-sdx kernel: [ 65.541690] eth3 renamed to eth5 by udevd [18067]
Feb 25 00:41:14 netscaler-sdx kernel: [ 65.561799] eth1 renamed to eth4 by udevd [18076]
Feb 25 00:41:14 netscaler-sdx kernel: [ 65.589332] eth0_rename renamed to eth1 by udevd [17998]
Feb 25 00:41:14 netscaler-sdx kernel: [ 66.072114] eth2 renamed to eth0 by udevd [18106]
We keep track of this change in mappings in the Interface-rename.log as well. In that log I can see that this issue was flagged on 23rd as well when the configuration was done for this appliance but it might be a case that interfaces were not checked and validated at that time.
We have another file by the name biosdevname-d.out where we again keep track of the actual interface at bios level and what kernel has picked. If we see that file even there we can see that interfaces are wrongly mapped:
BIOS device: eth0
Kernel name: eth0
BIOS device: eth1
Kernel name: eth1
BIOS device: eth2
Kernel name: eth4
BIOS device: eth3
Kernel name: eth5
BIOS device: eth4
Kernel name: eth26
BIOS device: eth5
Kernel name: eth27
BIOS device: eth6
Kernel name: eth8
BIOS device: eth7
Kernel name: eth9
BIOS device: eth8
Kernel name: eth28
BIOS device: eth9
Kernel name: eth29
BIOS device: eth10
Kernel name: eth10
BIOS device: eth11
Kernel name: eth11
BIOS device: eth12
Kernel name: eth12
BIOS device: eth13
Kernel name: eth13
BIOS device: eth14
Kernel name: eth14
BIOS device: eth15
Kernel name: eth15
BIOS device: eth16
Kernel name: eth16
BIOS device: eth17
Kernel name: eth17
BIOS device: eth18
Kernel name: eth18
BIOS device: eth19
Kernel name: eth19
BIOS device: eth20
Kernel name: eth20
BIOS device: eth21
Kernel name: eth21
BIOS device: eth22
Kernel name: eth22
BIOS device: eth23
Kernel name: eth23
BIOS device: eth24
Kernel name: eth24
BIOS device: eth25
Kernel name: eth25
Customer did the factory reset and after that we could see that the interface mappings were picked properly.
Problem Cause
In the XenServer support bundle logs in the kern.log we will be able to see any interface map changes and in this case we can see this reported:Kern.log:
Feb 25 00:41:14 netscaler-sdx kernel: [ 64.652006] eth4 renamed to eth26 by udevd [17803]
Feb 25 00:41:14 netscaler-sdx kernel: [ 64.951906] eth5 renamed to eth27 by udevd [17988]
Feb 25 00:41:14 netscaler-sdx kernel: [ 64.952696] eth6 renamed to eth6_rename by udevd [17990]
Feb 25 00:41:14 netscaler-sdx kernel: [ 64.961866] eth9 renamed to eth29 by udevd [17994]
Feb 25 00:41:14 netscaler-sdx kernel: [ 64.991648] eth0 renamed to eth0_rename by udevd [17998]
Feb 25 00:41:14 netscaler-sdx kernel: [ 65.011838] eth8 renamed to eth28 by udevd [18003]
Feb 25 00:41:14 netscaler-sdx kernel: [ 65.069326] eth6_rename renamed to eth8 by udevd [17990]
Feb 25 00:41:14 netscaler-sdx kernel: [ 65.432173] eth7 renamed to eth9 by udevd [18057]
Feb 25 00:41:14 netscaler-sdx kernel: [ 65.541690] eth3 renamed to eth5 by udevd [18067]
Feb 25 00:41:14 netscaler-sdx kernel: [ 65.561799] eth1 renamed to eth4 by udevd [18076]
Feb 25 00:41:14 netscaler-sdx kernel: [ 65.589332] eth0_rename renamed to eth1 by udevd [17998]
Feb 25 00:41:14 netscaler-sdx kernel: [ 66.072114] eth2 renamed to eth0 by udevd [18106]
We keep track of this change in mappings in the Interface-rename.log as well. In that log I can see that this issue was flagged on 23rd as well when the configuration was done for this appliance but it might be a case that interfaces were not checked and validated at that time.
We have another file by the name biosdevname-d.out where we again keep track of the actual interface at bios level and what kernel has picked. If we see that file even there we can see that interfaces are wrongly mapped:
BIOS device: eth0
Kernel name: eth0
BIOS device: eth1
Kernel name: eth1
BIOS device: eth2
Kernel name: eth4
BIOS device: eth3
Kernel name: eth5
BIOS device: eth4
Kernel name: eth26
BIOS device: eth5
Kernel name: eth27
BIOS device: eth6
Kernel name: eth8
BIOS device: eth7
Kernel name: eth9
BIOS device: eth8
Kernel name: eth28
BIOS device: eth9
Kernel name: eth29
BIOS device: eth10
Kernel name: eth10
BIOS device: eth11
Kernel name: eth11
BIOS device: eth12
Kernel name: eth12
BIOS device: eth13
Kernel name: eth13
BIOS device: eth14
Kernel name: eth14
BIOS device: eth15
Kernel name: eth15
BIOS device: eth16
Kernel name: eth16
BIOS device: eth17
Kernel name: eth17
BIOS device: eth18
Kernel name: eth18
BIOS device: eth19
Kernel name: eth19
BIOS device: eth20
Kernel name: eth20
BIOS device: eth21
Kernel name: eth21
BIOS device: eth22
Kernel name: eth22
BIOS device: eth23
Kernel name: eth23
BIOS device: eth24
Kernel name: eth24
BIOS device: eth25
Kernel name: eth25
Was this article helpful?
Yes
No
Powered by
