![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||||||||
Solution Type Problem Resolution Sure Solution 2089322.1 : Fabric Interconnect (Xsigo) After XgOS Install or Upgrade 'ethmgmt' Network Interface Will Not Come up, Cannot Configure Networking
In this Document
Created from <SR 3-11513443891> Applies to:Oracle Fabric Interconnect F1-15 - Version All Versions to All Versions [Release All Releases]Oracle Fabric Interconnect F1-4 - Version All Versions to All Versions [Release All Releases] Private Cloud Appliance X5-2 Hardware - Version All Versions to All Versions [Release All Releases] Oracle Virtual Compute Appliance X4-2 Hardware - Version All Versions to All Versions [Release All Releases] Information in this document applies to any platform. SymptomsAfter XgOS install or upgrade or installing a new Gen2 Front Panel, the 'ethmgmt' network interface is not found. Without the 'ethmgmt' network interface present, networking cannot be configured to connect the Fabric Interconnect to a network. When looking at the Fabric Interconnect over serial console the errors show that eth1 is being renamed to eth4. The errors are also found in /var/log/kern.log. Here is the errors where the network devices are being renamed: (snip below is also found also in /var/log/kern.log) xvio01:~# grep eth /var/log/dmesg
[ 25.558411] Driver 'sd' needs updating - please use bus_type methods [ 25.767591] e1000e 0000:00:19.0: eth0: (PCI Express:2.5GB/s:Width x1) ec:9e:cd:13:42:58 [ 25.775713] e1000e 0000:00:19.0: eth0: Intel(R) PRO/1000 Network Connection [ 25.782808] e1000e 0000:00:19.0: eth0: MAC: 10, PHY: 10, PBA No: ffffff-0ff [ 25.850887] e1000e 0000:01:00.0: eth1: (PCI Express:2.5GB/s:Width x1) 00:13:97:00:a5:9a [ 25.859007] e1000e 0000:01:00.0: eth1: Intel(R) PRO/1000 Network Connection [ 25.866069] e1000e 0000:01:00.0: eth1: MAC: 4, PHY: 8, PBA No: ffffff-0ff [ 25.930569] e1000e 0000:02:00.0: eth2: (PCI Express:2.5GB/s:Width x1) 00:13:97:00:a5:9b [ 25.938687] e1000e 0000:02:00.0: eth2: Intel(R) PRO/1000 Network Connection [ 25.945751] e1000e 0000:02:00.0: eth2: MAC: 4, PHY: 8, PBA No: ffffff-0ff [ 38.703819] udev: renamed network interface eth1 to eth4 <<-- !!! [ 38.705424] udev: renamed network interface eth2 to eth3 <<-- !!! [ 44.441422] ADDRCONF(NETDEV_UP): ethiop: link is not ready [ 44.482647] ADDRCONF(NETDEV_UP): ethfabric: link is not ready The issue here is eth1 gets renamed to eth4. When XgOS expects to rename eth1 to ethmgmt, this is naturally going to fail. Manually editing /etc/init.d/xgifrename.sh and changing all instances of eth4 back to eth1 works until the Fabric Interconnect is rebooted. Also the manual changes made using 'ifconfig' to force to use eth4 revert to original whenever the Fabric Interconnect is rebooted. For example to force ethmgmt to use eth4 and configure IP reverts when the Fabric Interconnect is rebooted - using ifconfig to manually plumb an IP address to eth4 is a workaround, but will be lost every time the Fabric Interconnect is rebooted. xvio01:~# ifconfig eth4 <ip address>/24 up Reinstalling the XgOS from scratch also doesn't resolve the problem. Changes XgOS install or upgrade/downgrade or brand new Gen2 Front Panel installation. CauseThe 'forcebaseos' option forces a new fresh install of the Linux kernel in addition to the XgOS downgrade/upgrade. It is possible if this option is needed, that there was a bad XgOS install at the factory, and the 'forcebaseos' option forces a new install of the Linux kernel. SolutionReinstall the XgOS using 'forcebaseos' option. After the XgOS .xpf file is placed on the Fabric Interconnect as user root under /var/fsroot/admin, as admin user run this command: system upgrade <version.xpf> forcebaseos
Attachments This solution has no attachment |
||||||||||||||||||
|