The following issues are related to NICs.

1. AMD fails to start, returns error code "1" and the "ethx - not found!" error in the rtm.log file.

CASE:

The sniffing interface has a different MAC address than what is configured in the ifcfg-ethx network script.

SOLUTION:

Note: The following commands apply to RHEL 6.

Sometimes, one of the sniffing interfaces gets a different MAC address in the network script file (/etc/sysconfig/network-scripts/ifcfg-ethx) than what can be found in the system. For example, the below output shows the contents of the ifcfg-eth3 file when running the cat /etc/sysconfig/network-scripts/ifcfg-eth3 command.

# Intel Corporation 82571EB Gigabit Ethernet Controller
DEVICE=eth3
HWADDR=00:1A:13:D6:49:B0
ONBOOT=yes
USERCTL=yes


Running the lspci -vv command, as seen below, shows that the interface has actually a slightly different MAC address.

07:00.0 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (rev 06)
Subsystem: Intel Corporation PRO/1000 PT Dual Port Server Adapter
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Interrupt: pin A routed to IRQ 130
Region 0: Memory at beee0000 (32-bit, non-prefetchable) [disabled] [size=128K]
Region 1: Memory at beec0000 (32-bit, non-prefetchable) [disabled] [size=128K]
Region 2: I/O ports at 7000 [disabled] [size=32]
[virtual] Expansion ROM at b4000000 [disabled] [size=128K]
Capabilities: [c8] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=1 PME-
Capabilities: [d0] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable-
Address: 00000000fee00000 Data: 40ac
Capabilities: [e0] Express Endpoint IRQ 0
Device: Supported: MaxPayload 256 bytes, PhantFunc 0, ExtTag-
Device: Latency L0s <512ns, L1 <64us
Device: AtnBtn- AtnInd- PwrInd-
Device: Errors: Correctable- Non-Fatal+ Fatal+ Unsupported-
Device: RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
Device: MaxPayload 128 bytes, MaxReadReq 4096 bytes
Link: Supported Speed 2.5Gb/s, Width x4, ASPM L0s, Port 6
Link: Latency L0s <4us, L1 <64us
Link: ASPM Disabled RCB 64 bytes CommClk- ExtSynch-
Link: Speed 2.5Gb/s, Width x4
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Device Serial Number 80-49-d6-ff-ff-13-1a-00


1. From the above, you can see that ifcfg-eth3 has B0 instead of 80 in the MAC address.

Note: Keep in mind that the output of lspci -vv shows the MAC address (Device Serial Number) characters in the opposite order. In order to properly convert the MAC address from the lspci -vv output to the one that is system readable, start building the MAC address by copying the pair of characters beginning with the end of the string. Hence, the MAC address 80-49-d6-ff-ff-13-1a-00 from lspci -vv would become 00-1a-13-ff-ff-d6-49-80. Then, remove all "ff" characters from the string and change the remaining ones to uppercase. As a result, we get the following MAC address: 00:1A:13:D6:49:80. Alternatively, in some cases, you may be able to obtain the MAC address in the correct order from the output of the kudzu -p command. In most cases, the ouput of kudzu -p does not show any MAC address at all and hence the use of lspci -vv in this example.

2. Edit the ifcfg-ethx network script for the sniffing interface in question and correct the MAC address as it was obtained from "lspci -vv". In our example, for eth3 above, the script should now show the following content:

# Intel Corporation 82571EB Gigabit Ethernet Controller
DEVICE=eth3
HWADDR=00:1A:13:D6:49:80
ONBOOT=yes
USERCTL=yes


3. Restart the AMD by running the command: ndstop;ndstart.

This should resolve the issue and the AMD should start without errors.

What to do next

If you experience further issues after the above changes, search the knowledge base for possible solutions or contact Support for assistance.