LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking
User Name
Password
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.

Notices


Reply
  Search this Thread
Old 11-15-2015, 04:37 AM   #1
nasirjavaid
LQ Newbie
 
Registered: Nov 2015
Posts: 15

Rep: Reputation: Disabled
All network interfaces stop working after sometime


Respected members and experts,

This is my first post in this forum. We have a streaming server running wowza streaming engine. This server has 2 ethernet ports, one of which has live ip while other has local ip and connected to 2 capture terminals via that local ip.
Now since couple of weeks we are facing the issue that server becomes unreachable from live ip and we have to manually delete 70-persistent-rules file and reboot to enable the interfaces back.

I have researched and found NetworkManager should be disabled and only Network should be left enabled in system services. But as server is in other country and there is no one locally available so I fear if server gets unreachable then no one will be able to troubleshoot it locally. So please advise the safest steps to carry out for diagnosing and solving the issue behind it.

Could it be only network manager issue or it could be ethernet hardware failing.

Server is CentOS 6.4

here is the messages file and we can see interface names also have been changed strangely by udev...

Nov 11 07:51:16 localhost kernel: igb: Intel(R) Gigabit Ethernet Network Driver - version 4.0.1-k
Nov 11 07:51:16 localhost kernel: igb: Copyright (c) 2007-2012 Intel Corporation.
Nov 11 07:51:16 localhost kernel: igb 0000:05:00.0: Refused to change power state, currently in D3
Nov 11 07:51:16 localhost kernel: igb 0000:05:00.0: PCI INT A -> GSI 32 (level, low) -> IRQ 32
Nov 11 07:51:16 localhost kernel: igb: The NVM size is not valid, defaulting to 32K
Nov 11 07:51:16 localhost kernel: igb 0000:05:00.0: PHY reset is blocked due to SOL/IDER session.
Nov 11 07:51:16 localhost kernel: igb 0000:05:00.0: The NVM Checksum Is Not Valid
Nov 11 07:51:16 localhost kernel: igb 0000:05:00.0: PCI INT A disabled
Nov 11 07:51:16 localhost kernel: igb: probe of 0000:05:00.0 failed with error -5
Nov 11 07:51:16 localhost kernel: igb 0000:05:00.1: Refused to change power state, currently in D3
Nov 11 07:51:16 localhost kernel: igb 0000:05:00.1: PCI INT B -> GSI 42 (level, low) -> IRQ 42
Nov 11 07:51:16 localhost kernel: igb: The NVM size is not valid, defaulting to 32K
Nov 11 07:51:16 localhost kernel: igb 0000:05:00.1: PHY reset is blocked due to SOL/IDER session.
Nov 11 07:51:16 localhost kernel: igb 0000:05:00.1: The NVM Checksum Is Not Valid
Nov 11 07:51:16 localhost kernel: igb 0000:05:00.1: PCI INT B disabled
Nov 11 07:51:16 localhost kernel: igb: probe of 0000:05:00.1 failed with error -5
Nov 11 07:51:16 localhost kernel: e1000e: Intel(R) PRO/1000 Network Driver - 2.1.4-k
Nov 11 07:51:16 localhost kernel: e1000e: Copyright(c) 1999 - 2012 Intel Corporation.
Nov 11 07:51:16 localhost kernel: e1000e 0000:07:00.0: Disabling ASPM L1
Nov 11 07:51:16 localhost kernel: e1000e 0000:07:00.0: PCI INT A -> GSI 24 (level, low) -> IRQ 24
Nov 11 07:51:16 localhost kernel: e1000e 0000:07:00.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
Nov 11 07:51:16 localhost kernel: e1000e 0000:07:00.0: eth0: (PCI Express:2.5GT/s:Width x4) 00:26:55:d7:fb:fe
Nov 11 07:51:16 localhost kernel: e1000e 0000:07:00.0: eth0: Intel(R) PRO/1000 Network Connection
Nov 11 07:51:16 localhost kernel: e1000e 0000:07:00.0: eth0: MAC: 0, PHY: 4, PBA No: D51930-007
Nov 11 07:51:16 localhost kernel: e1000e 0000:07:00.1: Disabling ASPM L1
Nov 11 07:51:16 localhost kernel: e1000e 0000:07:00.1: PCI INT B -> GSI 34 (level, low) -> IRQ 34
Nov 11 07:51:16 localhost kernel: e1000e 0000:07:00.1: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
Nov 11 07:51:16 localhost kernel: e1000e 0000:07:00.1: eth1: (PCI Express:2.5GT/s:Width x4) 00:26:55:d7:fb:ff
Nov 11 07:51:16 localhost kernel: e1000e 0000:07:00.1: eth1: Intel(R) PRO/1000 Network Connection
Nov 11 07:51:16 localhost kernel: e1000e 0000:07:00.1: eth1: MAC: 0, PHY: 4, PBA No: D51930-007
Nov 11 07:51:16 localhost kernel: udev: renamed network interface eth0 to rename2
Nov 11 07:51:16 localhost kernel: udev: renamed network interface eth1 to eth4


Nov 11 07:51:17 localhost NetworkManager[2120]: <info> monitoring kernel firmware directory '/lib/firmware'.
Nov 11 07:51:17 localhost NetworkManager[2120]: <info> Bonding/Bridging/VLAN support disabled
Nov 11 07:51:17 localhost NetworkManager[2120]: ifcfg-rh: Acquired D-Bus service com.redhat.ifcfgrh1
Nov 11 07:51:17 localhost NetworkManager[2120]: <info> Loaded plugin ifcfg-rh: (c) 2007 - 2008 Red Hat, Inc. To report bugs please use the NetworkManager mailing list.
Nov 11 07:51:17 localhost NetworkManager[2120]: ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-eth3 ...
Nov 11 07:51:17 localhost NetworkManager[2120]: ifcfg-rh: read connection 'System eth1'
Nov 11 07:51:17 localhost NetworkManager[2120]: ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-lo ...
Nov 11 07:51:17 localhost NetworkManager[2120]: ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-eth2 ...
Nov 11 07:51:17 localhost NetworkManager[2120]: ifcfg-rh: read connection 'System eth0'
Nov 11 07:51:17 localhost NetworkManager[2120]: <info> WiFi enabled by radio killswitch; enabled by state file
Nov 11 07:51:17 localhost NetworkManager[2120]: <info> WWAN enabled by radio killswitch; enabled by state file
Nov 11 07:51:17 localhost NetworkManager[2120]: <info> WiMAX enabled by radio killswitch; enabled by state file
Nov 11 07:51:17 localhost NetworkManager[2120]: <info> Networking is enabled by state file

Nov 11 07:51:17 localhost NetworkManager[2120]: <info> (eth1): carrier is OFF
Nov 11 07:51:17 localhost NetworkManager[2120]: <info> (eth1): new Ethernet device (driver: 'e1000e' ifindex: 2)
Nov 11 07:51:17 localhost NetworkManager[2120]: <info> (eth1): exported as /org/freedesktop/NetworkManager/Devices/0
Nov 11 07:51:17 localhost NetworkManager[2120]: <info> (eth1): now managed
Nov 11 07:51:17 localhost NetworkManager[2120]: <info> (eth1): device state change: 1 -> 2 (reason 2)
Nov 11 07:51:17 localhost NetworkManager[2120]: <info> (eth1): bringing up device.
Nov 11 07:51:17 localhost kernel: ADDRCONF(NETDEV_UP): eth1: link is not ready
Nov 11 07:51:17 localhost kernel: 8021q: adding VLAN 0 to HW filter on device eth1
Nov 11 07:51:17 localhost NetworkManager[2120]: <info> (eth1): preparing device.
Nov 11 07:51:17 localhost NetworkManager[2120]: <info> (eth1): deactivating device (reason: 2).
Nov 11 07:51:17 localhost NetworkManager[2120]: <info> (eth4): carrier is OFF
Nov 11 07:51:17 localhost NetworkManager[2120]: <info> (eth4): new Ethernet device (driver: 'e1000e' ifindex: 3)
Nov 11 07:51:17 localhost NetworkManager[2120]: <info> (eth4): exported as /org/freedesktop/NetworkManager/Devices/1
Nov 11 07:51:17 localhost NetworkManager[2120]: <info> (eth4): now managed
Nov 11 07:51:17 localhost NetworkManager[2120]: <info> (eth4): device state change: 1 -> 2 (reason 2)
Nov 11 07:51:17 localhost NetworkManager[2120]: <info> (eth4): bringing up device.
Nov 11 07:51:17 localhost acpid: starting up
Nov 11 07:51:17 localhost acpid: 1 rule loaded
Nov 11 07:51:17 localhost acpid: waiting for events: event logging is off
Nov 11 07:51:17 localhost kernel: ADDRCONF(NETDEV_UP): eth4: link is not ready
Nov 11 07:51:17 localhost kernel: 8021q: adding VLAN 0 to HW filter on device eth4
Nov 11 07:51:17 localhost NetworkManager[2120]: <info> (eth4): preparing device.
Nov 11 07:51:17 localhost NetworkManager[2120]: <info> (eth4): deactivating device (reason: 2).
Nov 11 07:51:17 localhost NetworkManager[2120]: <info> modem-manager is now available
Nov 11 07:51:17 localhost NetworkManager[2120]: <info> Trying to start the supplicant...
Nov 11 07:51:18 localhost NetworkManager[2120]: <info> wpa_supplicant started

Nov 11 17:05:03 eze-119 NetworkManager[2281]: ifcfg-rh: read connection 'System eth1'
Nov 11 17:05:03 eze-119 NetworkManager[2281]: ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-lo ...
Nov 11 17:05:03 eze-119 NetworkManager[2281]: ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-eth2 ...
Nov 11 17:05:03 eze-119 NetworkManager[2281]: ifcfg-rh: read connection 'System eth0'
Nov 11 17:05:03 eze-119 NetworkManager[2281]: <info> WiFi enabled by radio killswitch; enabled by state file
Nov 11 17:05:03 eze-119 NetworkManager[2281]: <info> WWAN enabled by radio killswitch; enabled by state file
Nov 11 17:05:03 eze-119 NetworkManager[2281]: <info> WiMAX enabled by radio killswitch; enabled by state file
Nov 11 17:05:03 eze-119 NetworkManager[2281]: <info> Networking is enabled by state file
Nov 11 17:05:03 eze-119 kernel: 802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
Nov 11 17:05:03 eze-119 kernel: All bugs added by David S. Miller <davem@redhat.com>
Nov 11 17:05:03 eze-119 kernel: 8021q: adding VLAN 0 to HW filter on device eth2
Nov 11 17:05:03 eze-119 kernel: 8021q: adding VLAN 0 to HW filter on device eth3
Nov 11 17:05:03 eze-119 NetworkManager[2281]: <info> (eth1): carrier is OFF
Nov 11 17:05:03 eze-119 NetworkManager[2281]: <info> (eth1): new Ethernet device (driver: 'e1000e' ifindex: 2)
Nov 11 17:05:03 eze-119 NetworkManager[2281]: <info> (eth1): exported as /org/freedesktop/NetworkManager/Devices/0
Nov 11 17:05:03 eze-119 NetworkManager[2281]: <info> (eth1): now managed
Nov 11 17:05:03 eze-119 NetworkManager[2281]: <info> (eth1): device state change: 1 -> 2 (reason 2)
Nov 11 17:05:03 eze-119 NetworkManager[2281]: <info> (eth1): bringing up device.
Nov 11 17:05:03 eze-119 NetworkManager[2281]: <info> (eth1): preparing device.
Nov 11 17:05:03 eze-119 NetworkManager[2281]: <info> (eth1): deactivating device (reason: 2).
Nov 11 17:05:03 eze-119 kernel: ADDRCONF(NETDEV_UP): eth1: link is not ready
Nov 11 17:05:03 eze-119 kernel: 8021q: adding VLAN 0 to HW filter on device eth1
Nov 11 17:05:03 eze-119 NetworkManager[2281]: <info> (eth4): carrier is OFF
Nov 11 17:05:03 eze-119 NetworkManager[2281]: <info> (eth4): new Ethernet device (driver: 'e1000e' ifindex: 3)
Nov 11 17:05:03 eze-119 NetworkManager[2281]: <info> (eth4): exported as /org/freedesktop/NetworkManager/Devices/1
Nov 11 17:05:03 eze-119 NetworkManager[2281]: <info> (eth4): now managed
Nov 11 17:05:03 eze-119 NetworkManager[2281]: <info> (eth4): device state change: 1 -> 2 (reason 2)
Nov 11 17:05:03 eze-119 NetworkManager[2281]: <info> (eth4): bringing up device.
Nov 11 17:05:04 eze-119 NetworkManager[2281]: <info> (eth4): preparing device.
Nov 11 17:05:04 eze-119 NetworkManager[2281]: <info> (eth4): deactivating device (reason: 2).
Nov 11 17:05:04 eze-119 kernel: ADDRCONF(NETDEV_UP): eth4: link is not ready
Nov 11 17:05:04 eze-119 kernel: 8021q: adding VLAN 0 to HW filter on device eth4
Nov 11 17:05:04 eze-119 NetworkManager[2281]: <info> (eth2): carrier is ON
Nov 11 17:05:04 eze-119 NetworkManager[2281]: <info> (eth2): new Ethernet device (driver: 'igb' ifindex: 4)
Nov 11 17:05:04 eze-119 NetworkManager[2281]: <info> (eth2): exported as /org/freedesktop/NetworkManager/Devices/2
Nov 11 17:05:04 eze-119 NetworkManager[2281]: <info> (eth2): now managed
Nov 11 17:05:04 eze-119 NetworkManager[2281]: <info> (eth2): device state change: 1 -> 2 (reason 41)
Nov 11 17:05:04 eze-119 NetworkManager[2281]: <info> (eth2): preparing device.
Nov 11 17:05:04 eze-119 NetworkManager[2281]: <info> Activation (eth2) starting connection 'System eth0'
Nov 11 17:05:04 eze-119 NetworkManager[2281]: (nm-device.c:3281):nm_device_activate: runtime check failed: (priv->state == NM_DEVICE_STATE_DISCONNECTED)
Nov 11 17:05:04 eze-119 NetworkManager[2281]: <info> (eth2): device state change: 2 -> 7 (reason 0)
Nov 11 17:05:04 eze-119 NetworkManager[2281]: <info> Activation (eth2) Stage 3 of 5 (IP Configure Start) scheduled.
Nov 11 17:05:04 eze-119 NetworkManager[2281]: <info> (eth3): carrier is ON
Nov 11 17:05:04 eze-119 NetworkManager[2281]: <info> (eth3): new Ethernet device (driver: 'igb' ifindex: 5)
Nov 11 17:05:04 eze-119 NetworkManager[2281]: <info> (eth3): exported as /org/freedesktop/NetworkManager/Devices/3
Nov 11 17:05:04 eze-119 NetworkManager[2281]: <info> (eth3): now managed
Nov 11 17:05:04 eze-119 NetworkManager[2281]: <info> (eth3): device state change: 1 -> 2 (reason 41)
Nov 11 17:05:04 eze-119 NetworkManager[2281]: <info> (eth3): preparing device.
Nov 11 17:05:04 eze-119 NetworkManager[2281]: <info> Activation (eth3) starting connection 'System eth1'
Nov 11 17:05:04 eze-119 NetworkManager[2281]: (nm-device.c:3281):nm_device_activate: runtime check failed: (priv->state == NM_DEVICE_STATE_DISCONNECTED)
Nov 11 17:05:04 eze-119 NetworkManager[2281]: <info> (eth3): device state change: 2 -> 7 (reason 0)
Nov 11 17:05:04 eze-119 NetworkManager[2281]: <info> Activation (eth3) Stage 3 of 5 (IP Configure Start) scheduled.
Nov 11 17:05:04 eze-119 NetworkManager[2281]: <info> modem-manager is now available
Nov 11 17:05:04 eze-119 NetworkManager[2281]: <info> Trying to start the supplicant...
Nov 11 17:05:04 eze-119 NetworkManager[2281]: <info> Activation (eth2) Stage 3 of 5 (IP Configure Start) started...
Nov 11 17:05:04 eze-119 NetworkManager[2281]: <info> Activation (eth2) Stage 4 of 5 (IP4 Configure Get) scheduled...
Nov 11 17:05:04 eze-119 NetworkManager[2281]: <info> Activation (eth2) Stage 3 of 5 (IP Configure Start) complete.
Nov 11 17:05:04 eze-119 NetworkManager[2281]: <info> Activation (eth3) Stage 3 of 5 (IP Configure Start) started...
Nov 11 17:05:04 eze-119 NetworkManager[2281]: <info> Activation (eth3) Stage 4 of 5 (IP4 Configure Get) scheduled...
Nov 11 17:05:04 eze-119 NetworkManager[2281]: <info> Activation (eth3) Stage 3 of 5 (IP Configure Start) complete.
Nov 11 17:05:04 eze-119 NetworkManager[2281]: <info> Activation (eth2) Stage 4 of 5 (IP4 Configure Get) started...
Nov 11 17:05:04 eze-119 NetworkManager[2281]: <info> Activation (eth2) Stage 5 of 5 (IP Configure Commit) scheduled...
Nov 11 17:05:04 eze-119 NetworkManager[2281]: <info> Activation (eth2) Stage 4 of 5 (IP4 Configure Get) complete.
Nov 11 17:05:04 eze-119 NetworkManager[2281]: <info> Activation (eth3) Stage 4 of 5 (IP4 Configure Get) started...
Nov 11 17:05:04 eze-119 NetworkManager[2281]: <info> Activation (eth3) Stage 5 of 5 (IP Configure Commit) scheduled...
Nov 11 17:05:04 eze-119 NetworkManager[2281]: <info> Activation (eth3) Stage 4 of 5 (IP4 Configure Get) complete.
Nov 11 17:05:04 eze-119 NetworkManager[2281]: <info> Activation (eth2) Stage 5 of 5 (IP Configure Commit) started...
Nov 11 17:05:04 eze-119 NetworkManager[2281]: <info> (eth2): device state change: 7 -> 8 (reason 0)
Nov 11 17:05:04 eze-119 NetworkManager[2281]: <info> Policy set 'System eth0' (eth2) as default for IPv4 routing and DNS.
Nov 11 17:05:04 eze-119 NetworkManager[2281]: <info> Activation (eth2) successful, device activated.
Nov 11 17:05:04 eze-119 NetworkManager[2281]: <info> Activation (eth2) Stage 5 of 5 (IP Configure Commit) complete.
Nov 11 17:05:04 eze-119 NetworkManager[2281]: <info> Activation (eth3) Stage 5 of 5 (IP Configure Commit) started...
Nov 11 17:05:04 eze-119 NetworkManager[2281]: <info> Policy set 'System eth0' (eth2) as default for IPv4 routing and DNS.
Nov 11 17:05:04 eze-119 NetworkManager[2281]: <info> (eth3): device state change: 7 -> 8 (reason 0)
Nov 11 17:05:04 eze-119 NetworkManager[2281]: <info> Activation (eth3) successful, device activated.
Nov 11 17:05:04 eze-119 NetworkManager[2281]: <info> Activation (eth3) Stage 5 of 5 (IP Configure Commit) complete.
Nov 11 17:05:04 eze-119 NetworkManager[2281]: <info> wpa_supplicant started
 
Old 11-15-2015, 04:52 AM   #2
berndbausch
LQ Addict
 
Registered: Nov 2013
Location: Tokyo
Distribution: Mostly Ubuntu and Centos
Posts: 6,316

Rep: Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002
You shouldn't use network manager on a server in Centos 6. Centos 7 is different.
Quote:
But as server is in other country and there is no one locally available so I fear if server gets unreachable then no one will be able to troubleshoot it locally.
Wow. You run a server in a different country with nobody present locally, and you don't have console access? Are you sure this is the case? A server usually has a way to access the console via the network, e.g. iLO on HP Proliants.

I have had my share of problems with NetworkManager getting into my network configuration. It should be sufficient to set up your network config files and be 100 certain they are OK, disable (but don't stop) NetworkManager and reboot.
The line NM_CONTROLLED=no in the ifcfg-ethX file should normally suffice, but I have had problems with that - it seems to me that NetworkManager detects the change immediately and proceeds to mess everything up before letting that interface go..
 
Old 11-15-2015, 02:47 PM   #3
nasirjavaid
LQ Newbie
 
Registered: Nov 2015
Posts: 15

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by berndbausch View Post
You shouldn't use network manager on a server in Centos 6. Centos 7 is different.

Wow. You run a server in a different country with nobody present locally, and you don't have console access? Are you sure this is the case? A server usually has a way to access the console via the network, e.g. iLO on HP Proliants.

I have had my share of problems with NetworkManager getting into my network configuration. It should be sufficient to set up your network config files and be 100 certain they are OK, disable (but don't stop) NetworkManager and reboot.
The line NM_CONTROLLED=no in the ifcfg-ethX file should normally suffice, but I have had problems with that - it seems to me that NetworkManager detects the change immediately and proceeds to mess everything up before letting that interface go..

Thank you so much for your reply. Yes sorry to say this is the case that there is no expert to handle locally .... some newbie installed server in gui and left it in that way... even lv_root has 55GB only and lv_home has 250 ... you can imagine how server was setup. When I got ssh access, it was running that way and I couldn't have done much.

You are right about NM and I, too, want to disable it but afraid if this revokes remote access then there will be no one to troubleshoot it locally.

Server is ProLiant DL160 G6 Can you please elaborate little more about console interface via network as server itself becomes inaccessible so how can console be available? I completed RHCSA training and going for RHCE so I am still learning. Any help regarding this will be appreciated.

Should I only disable NM and problem will be solved? what about strange renaming of ethx interface... ?
 
Old 11-15-2015, 06:06 PM   #4
berndbausch
LQ Addict
 
Registered: Nov 2013
Location: Tokyo
Distribution: Mostly Ubuntu and Centos
Posts: 6,316

Rep: Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002
I feel with you

Find DL160 G6 manuals to learn about this product. You will have some hunting to do; probably due to the separation of HP in two companies, the links you find via Google and friends are broken.

In a nutshell, Proliants have a management device named iLO, which provides access to hardware configuration, BIOS (named RBSU in the Proliant world), CDROM and other media, and also the graphical or serial console. All this independently of any OS. In fact, you can install the OS on a new server via the iLO.
The iLO is accessed through a special IP address, either through a separate dedicated port or the same port as your normal ethernet, and either via ssh or a web browser.

There are a number of points that will make it hard for you to use the console on the iLO. But there is hope (see next paragraph).
What is its IP address?
The graphical console requires a license, which your server may not have
The serial interface doesn't require a license, but must be configured in grub and the kernel (kernel parameter "console=/dev/ttyS0" or ".....S1").

HP provides a utility named hponcfg, which allows you to view iLO configuration and change it via an XML file. I would learn about it and check out and configure you system's iLO before doing anything risky. I bought an ML330 G6 a few months ago and reset the iLO password this way.

Proliants being ubiquitous, there is no shortage of information on the iLO. Note that G6 Proliants use iLO version 2.

As to your last question, it's NW Manager that renames your NW interface due to it's screwed-up mentality, so as soon as you eliminate it, and the MAC address in your udev rule matches your interface's, you should be fine. However, any error in the config file or udev rule might make the system inaccessible, thus my recommendation to check out the iLO.

Last edited by berndbausch; 11-15-2015 at 06:09 PM.
 
1 members found this post helpful.
Old 11-15-2015, 09:36 PM   #5
nasirjavaid
LQ Newbie
 
Registered: Nov 2015
Posts: 15

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by berndbausch View Post
I feel with you

Find DL160 G6 manuals to learn about this product. You will have some hunting to do; probably due to the separation of HP in two companies, the links you find via Google and friends are broken.

In a nutshell, Proliants have a management device named iLO, which provides access to hardware configuration, BIOS (named RBSU in the Proliant world), CDROM and other media, and also the graphical or serial console. All this independently of any OS. In fact, you can install the OS on a new server via the iLO.
The iLO is accessed through a special IP address, either through a separate dedicated port or the same port as your normal ethernet, and either via ssh or a web browser.

There are a number of points that will make it hard for you to use the console on the iLO. But there is hope (see next paragraph).
What is its IP address?
The graphical console requires a license, which your server may not have
The serial interface doesn't require a license, but must be configured in grub and the kernel (kernel parameter "console=/dev/ttyS0" or ".....S1").

HP provides a utility named hponcfg, which allows you to view iLO configuration and change it via an XML file. I would learn about it and check out and configure you system's iLO before doing anything risky. I bought an ML330 G6 a few months ago and reset the iLO password this way.

Proliants being ubiquitous, there is no shortage of information on the iLO. Note that G6 Proliants use iLO version 2.

As to your last question, it's NW Manager that renames your NW interface due to it's screwed-up mentality, so as soon as you eliminate it, and the MAC address in your udev rule matches your interface's, you should be fine. However, any error in the config file or udev rule might make the system inaccessible, thus my recommendation to check out the iLO.
Hahaha, thanks for understanding my pain .... We have a manager type thing there which is little bit techy so will try to discuss with him if he can set up iLO... So my fears are right about if I disable network manager system could be inaccessible but manager guy can enable network manager again......... lets experiment

Thanks for being so helpful

Cheers!
 
Old 11-16-2015, 05:08 AM   #6
nasirjavaid
LQ Newbie
 
Registered: Nov 2015
Posts: 15

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by nasirjavaid View Post
Hahaha, thanks for understanding my pain .... We have a manager type thing there which is little bit techy so will try to discuss with him if he can set up iLO... So my fears are right about if I disable network manager system could be inaccessible but manager guy can enable network manager again......... lets experiment

Thanks for being so helpful

Cheers!
Its me again dear... Today our little-tech guy went there and done some stuff upon my instructions on skype........we decided to disable network manager because network interface card was resetting again and again and server was unreachable even after 5-10 minutes of reboot.

we have disabled network manager from "setup" menu and renamed eth2 -> eth0 and eth3 -> eth1 in ifcfg-eth0 and ifcfg-eth1 and deleted the 70-persistent rules files and rebooted... now ifconfig shows network interfaces eth0 and eth1 are up along with lo....

But we still can't ping any network... also if we run setup->network configuration then it shows 4 devices eth0, eth1, eth2, eth3

eth0 and eth2 are same .... and eth1 and eth3 are same......... Can you please help what could be wrong?

If I can have your skype ID then will be much thankful.. My skype ID is nasirjavaidnasir
 
Old 11-16-2015, 07:44 AM   #7
berndbausch
LQ Addict
 
Registered: Nov 2013
Location: Tokyo
Distribution: Mostly Ubuntu and Centos
Posts: 6,316

Rep: Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002
What do you mean by "eth0 and eth2 are same"? Same MAC address?

Post the ifcfg files here, and the output of ip a and ip r.
 
Old 11-16-2015, 12:20 PM   #8
nasirjavaid
LQ Newbie
 
Registered: Nov 2015
Posts: 15

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by berndbausch View Post
What do you mean by "eth0 and eth2 are same"? Same MAC address?

Post the ifcfg files here, and the output of ip a and ip r.
Strange thing is network interfaces become up but can't ping until we revert back to NM


eth0 and eth2 are same- means 70-persistent.rules is created with 4 entries and eth0 & eth2 share same settings like this

[root@eze-119 ~]# cat /etc/udev/rules.d/70-persistent-net.rules
# This file was automatically generated by the /lib/udev/write_net_rules
# program, run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single
# line, and change only the value of the NAME= key.

# PCI device 0x8086:0x105e (e1000e)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:26:55:d7:fb:fe", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

# PCI device 0x8086:0x10c9 (igb) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="d8:d3:85:e5:ed:d3", ATTR{type}=="1", KERNEL=="eth*", NAME="eth3"

# PCI device 0x8086:0x105e (e1000e)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:26:55:d7:fb:ff", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"

# PCI device 0x8086:0x10c9 (igb) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="d8:d3:85:e5:ed:d2", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2"

I see igb and e1000e... does it means there are 2 drivers in action?

Here are the output of ip a, ip r and ifcfg-eth2 and ifcfg-eth3

[root@eze-119 ~]# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN qlen 1000
link/ether 00:26:55:d7:fb:fe brd ff:ff:ff:ff:ff:ff
3: eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN qlen 1000
link/ether 00:26:55:d7:fb:ff brd ff:ff:ff:ff:ff:ff
4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
link/ether d8:d3:85:e5:ed:d2 brd ff:ff:ff:ff:ff:ff
inet 119.82.251.230/24 brd 119.82.251.255 scope global eth2
inet6 fe80::dad3:85ff:fee5:edd2/64 scope link
valid_lft forever preferred_lft forever
5: eth3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
link/ether d8:d3:85:e5:ed:d3 brd ff:ff:ff:ff:ff:ff
inet 23.1.1.191/24 brd 23.1.1.255 scope global eth3
inet6 fe80::dad3:85ff:fee5:edd3/64 scope link
valid_lft forever preferred_lft forever



[root@eze-119 ~]# ip r
119.82.251.0/24 dev eth2 proto kernel scope link src 119.82.251.230
23.1.1.0/24 dev eth3 proto kernel scope link src 23.1.1.191
169.254.0.0/16 dev eth2 scope link metric 1004
169.254.0.0/16 dev eth3 scope link metric 1005
default via 119.82.251.229 dev eth2 proto static



[root@eze-119 ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth2
DEVICE=eth2
NM_CONTROLLED=yes
ONBOOT=yes
TYPE=Ethernet
BOOTPROTO=none
NAME="System eth0"
IPADDR=119.82.251.230
NETMASK=255.255.255.252
GATEWAY=119.82.251.229
PREFIX=24
IPV6INIT=no
USERCTL=no
DEFROUTE=yes
IPV4_FAILURE_FATAL=yes
UUID=5fb06bd0-0bb0-7ffb-45f1-d6edd65f3e03
DNS1=119.82.248.67
HWADDR=D83:85:E5:ED2
LAST_CONNECT=1432011451



[root@eze-119 ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth3
DEVICE=eth3
NM_CONTROLLED=yes
ONBOOT=yes
TYPE=Ethernet
BOOTPROTO=none
NAME="System eth1"
IPADDR=23.1.1.191
NETMASK=255.255.255.0
PREFIX=24
HWADDR=d8:d3:85:e5:ed:d3
IPV6INIT=no
USERCTL=no
GATEWAY=23.1.1.3


This is current working configs with NM. NetworkManager is really annoying...

Thanks.

Last edited by nasirjavaid; 11-16-2015 at 12:26 PM.
 
Old 11-17-2015, 02:51 AM   #9
berndbausch
LQ Addict
 
Registered: Nov 2013
Location: Tokyo
Distribution: Mostly Ubuntu and Centos
Posts: 6,316

Rep: Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002
Nasir, interestng problem. I searched around a little for the remark "custom name provided by external tool", because I believe the key to your worries is there. One of the possible "external commands" is biosdevname; have a look if you find it, then see if removing it helps.

There must be ways to find what external command is doing this to you, just haven't found out yet. It's probably buried somewhere in the system log or in the udev information. Or perhaps it's possible to redo the udev actions while the system is online, and monitor what happens. I will be looking into this.
This is great learning for me, so I have no problem spending time on it, when I have the time.

Edit: Concise info about biosdevname: http://blog.nold.ca/2013/05/consiste...ming-with.html. Also check if the troubleshooting recommendations in https://docs.fedoraproject.org/en-US...ce_Naming.html help in your case.

Last edited by berndbausch; 11-17-2015 at 03:48 AM.
 
Old 11-17-2015, 06:32 AM   #10
nasirjavaid
LQ Newbie
 
Registered: Nov 2015
Posts: 15

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by berndbausch View Post
Nasir, interestng problem. I searched around a little for the remark "custom name provided by external tool", because I believe the key to your worries is there. One of the possible "external commands" is biosdevname; have a look if you find it, then see if removing it helps.

There must be ways to find what external command is doing this to you, just haven't found out yet. It's probably buried somewhere in the system log or in the udev information. Or perhaps it's possible to redo the udev actions while the system is online, and monitor what happens. I will be looking into this.
This is great learning for me, so I have no problem spending time on it, when I have the time.

Edit: Concise info about biosdevname: http://blog.nold.ca/2013/05/consiste...ming-with.html. Also check if the troubleshooting recommendations in https://docs.fedoraproject.org/en-US...ce_Naming.html help in your case.
Haha, it may be interesting but its nightmare for me ....... Thanks for the specific links. I am studying them... But for me problem is not the naming of the interfaces but why they get resetting again and again...

Yesterday I scanned the system with clamav and found some infected files... could they cause such behaviour or this is something else? this is what I am after. Luckily server is running fine since yesterday when we performed this exercise but I wan't to be on safe side by diagnosing the issue..


Here is the output of clamscan

LibClamAV Warning: cli_scanxz: decompress file size exceeds limits - only scanning 27262976 bytes
/home/WowzaStreamingEngine-4.1.0/manager/temp/applications/test/vod/FlashHTTPPlayer/vod.swf: Swf.Exploit.CVE_2015_5548 FOUND
/home/WowzaStreamingEngine-4.1.0/manager/temp/applications/test/live/FlashHTTPPlayer/live.swf: Swf.Exploit.CVE_2015_5548 FOUND
/home/WowzaStreamingEngine-4.1.0/manager/lib/WMSManager.war: Swf.Exploit.CVE_2015_5548 FOUND
/home/WowzaStreamingEngine-4.1.0/examples/LiveVideoStreaming/FlashHTTPPlayer/Live.swf: Swf.Exploit.CVE_2015_5548 FOUND
/home/WowzaStreamingEngine-4.1.0/examples/VideoOnDemandStreaming/FlashHTTPPlayer/VOD.swf: Swf.Exploit.CVE_2015_5548 FOUND


Thanks.
 
Old 11-17-2015, 01:53 PM   #11
nasirjavaid
LQ Newbie
 
Registered: Nov 2015
Posts: 15

Original Poster
Rep: Reputation: Disabled
Here is some more info after reading your provided links

[root@eze-119 ~]# ls /sys/class/net/ -lah
total 0
drwxr-xr-x 2 root root 0 Nov 16 19:24 .
drwxr-xr-x 43 root root 0 Nov 17 10:32 ..
lrwxrwxrwx 1 root root 0 Nov 16 19:24 eth0 -> ../../devices/pci0000:00/0000:00:03.0/0000:07:00.0/net/eth0
lrwxrwxrwx 1 root root 0 Nov 16 19:24 eth1 -> ../../devices/pci0000:00/0000:00:03.0/0000:07:00.1/net/eth1
lrwxrwxrwx 1 root root 0 Nov 16 19:24 eth2 -> ../../devices/pci0000:00/0000:00:09.0/0000:05:00.0/net/eth2
lrwxrwxrwx 1 root root 0 Nov 16 19:24 eth3 -> ../../devices/pci0000:00/0000:00:09.0/0000:05:00.1/net/eth3
lrwxrwxrwx 1 root root 0 Nov 16 19:24 lo -> ../../devices/virtual/net/lo


[root@eze-119 ~]# lspci | grep -i giga
05:00.0 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01)
05:00.1 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01)
07:00.0 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (rev 06)
07:00.1 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (rev 06)


[root@eze-119 ~]# ethtool -i eth0
driver: e1000e
version: 2.1.4-k
firmware-version: 5.11-2
bus-info: 0000:07:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: no


[root@eze-119 ~]# ethtool -i eth2
driver: igb
version: 4.0.1-k
firmware-version: 1.72, 0x0000dc12
bus-info: 0000:05:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: no


[root@eze-119 ~]# ethtool -i eth1
driver: e1000e
version: 2.1.4-k
firmware-version: 5.11-2
bus-info: 0000:07:00.1
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: no


[root@eze-119 ~]# ethtool -i eth3
driver: igb
version: 4.0.1-k
firmware-version: 1.72, 0x0000dc12
bus-info: 0000:05:00.1
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: no


It seems two drivers are being used for single interface.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Ubuntu /etc/network/interfaces - my 3 network cards - not working correctly WildDrake! Linux - Networking 2 06-13-2013 01:53 PM
Network card stop working irregularly and after resetting its start working. a.anand385 Linux - Networking 2 06-21-2012 08:22 AM
Network manager stop working completly (( not working after reinstalling)) alieblice Linux - Networking 0 10-20-2011 06:52 AM
only one out of two network interfaces working ernesto_cgf Linux - Networking 2 05-21-2008 03:46 PM
How to stop my network adaptor working nikkkko Linux - Hardware 17 10-31-2006 11:22 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Networking

All times are GMT -5. The time now is 02:00 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration