Workaround

1. Reboot the affected blades.
2. Verify that the pcitool -v output is similar to the following:

   # pcitool -v | grep 207
   Device ID: 2070
   Device ID: 2070
   Device ID: 2070
   Device ID: 2078
   Device ID: 2078

3. Verify that the modinfo output is similar to the following:

   # modinfo | grep sxge
   168 ffffffffee5735f8 149b8 258 1 sxge (SOL 10/40G Ethernet 1.43)

4. Verify that the ifconfig -a output is similar to the following:

   # ifconfig -a
   lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
      inet 127.0.0.1 netmask ff000000
   igb0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
      inet 10.134.167.112 netmask ffffff00 broadcast 10.134.167.255
      ether 0:21:28:a7:9a:ac
   sxge0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3
      inet 192.168.100.112 netmask ffffff00 broadcast 192.168.100.255
      ether 0:21:28:c6:ff:e6
   sxge1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 5
      inet 192.168.110.112 netmask ffffff00 broadcast 192.168.110.255
      ether 0:21:28:c7:a:e
   sxge2: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 4
      inet 192.168.200.112 netmask ffffff00 broadcast 192.168.200.255
      ether 0:21:28:c7:0:18
   sxge3: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 6
      inet 192.168.210.112 netmask ffffff00 broadcast 192.168.210.255
      ether 0:21:28:c7:a:40

   After you complete this procedure, the NEM can be configured and used. If the issue persists, please contact your Oracle Service representative.