Dell PowerConnect Brocade 815 Brocade Adapters Troubleshooting Guide - Page 57

Ethernet link ports or LOM not coming up on reboot in Linux, Loss of adapter hardware address in Linux

Get Dell PowerConnect Brocade 815 PDF manuals and user guides View all Dell PowerConnect Brocade 815 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 57 highlights

Network interface problems (CNA or NIC) 2 Ethernet link ports or LOM not coming up on reboot in Linux The host system's LAN on motherboard (LOM) is not coming up or ports are not visible after rebooting Linux host. 1. Possible Cause: A ifcfg-ethX script is not configured to bring up each LOM and CNA during the system boot process. Action: Make sure that a script is configured for each adapter and LOM once drivers are installed. Scripts are located in the following directories: • SLES - /etc/sysconfig/network • RHEL - /etc/sysconfig/network-scripts 2. Possible Cause: NetworkManager is enabled. There are known issues with NetworkManager managing multiple NICs in some Linux distributions. Action: Disable NetworkManager. To check if NetworkManager is running, enter either of the following commands: • chkconfig --list | grep NetworkManager • nm-tool To disable NetworkManager for RHEL 5 systems, enter the following commands. chkconfig NetworkManager off chkconfig NetworkManagerDispatcher off To disable NetworkManager for SLES systems, perform the following steps. a. Open YaST. b. Select the Network Devices Network Card. c. On the first screen set the Network Setup Method option to Traditional Method with ifup. Loss of adapter hardware address in Linux The ifconfig command displays, HW Addr as 00:00:00:00:00:00. Possible Cause: The adapter failed to initialize. Action: Disable the Ethernet I/O controller by entering the BCU vnic --disable command, then enable the I/O controller by entering the BCU vnic --enable command. Loss of adapter IP address in Linux The IP address set in Linux with the ifconfig command disappears when the adapter goes down or host system reboots. 1. Possible Cause: The IP address was set with the ifconfig command and the adapter is enabled in DHCP (Dynamic Hardware Configuration Protocol) mode. Action: Configure IP address using system GUI-based networking tools. Brocade Adapters Troubleshooting Guide 33 53-1002145-01

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
Brocade Adapters Troubleshooting Guide
33
53-1002145-01
Network interface problems (CNA or NIC)
2
Ethernet link ports or LOM not coming up on reboot in Linux
The host system’s LAN on motherboard (LOM) is not coming up or ports are not visible after
rebooting Linux host.
1.
Possible Cause:
A ifcfg-ethX script is not configured to bring up each LOM and CNA during the
system boot process.
Action:
Make sure that a script is configured for each adapter and LOM once drivers are
installed. Scripts are located in the following directories:
•
SLES - /etc/sysconfig/network
•
RHEL - /etc/sysconfig/network-scripts
2.
Possible Cause:
NetworkManager is enabled. There are known issues with NetworkManager
managing multiple NICs in some Linux distributions.
Action:
Disable NetworkManager.
To check if NetworkManager is running, enter either of the following commands:
•
chkconfig --list | grep NetworkManager
•
nm-tool
To disable NetworkManager for RHEL 5 systems, enter the following commands.
chkconfig NetworkManager off
chkconfig NetworkManagerDispatcher off
To disable NetworkManager for SLES systems, perform the following steps.
a.
Open YaST.
b.
Select the
Network Devices Network Card
.
c.
On the first screen set the
Network Setup Method
option to
Traditional Method with ifup
.
Loss of adapter hardware address in Linux
The
ifconfig
command displays, HW Addr as 00:00:00:00:00:00.
Possible Cause:
The adapter failed to initialize.
Action:
Disable the Ethernet I/O controller by entering the BCU
vnic --disable
command, then
enable the I/O controller by entering the BCU
vnic --enable
command.
Loss of adapter IP address in Linux
The IP address set in Linux with the
ifconfig
command disappears when the adapter goes down or
host system reboots.
1.
Possible Cause:
The IP address was set with the
ifconfig
command and the adapter is enabled
in DHCP (Dynamic Hardware Configuration Protocol) mode.
Action:
Configure IP address using system GUI-based networking tools.