No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

The N8300 can’t identify the heartbreak IP of the node which is needed to add

Publication Date:  2012-11-26 Views:  44 Downloads:  0
Issue Description
There are 4 nodes in a set of N8300 storage, after ISM removing an engine node of the N8300, we can’t find the engine node’s heartbreak IP via the ISM or command line, but from the external monitor, we find the removed N8300 engine node’s status is normal, and its heartbreak IP can ping through the other 3 engine nodes’ heartbreak IP.

Alarm Information
None
Handling Process
1. Connect to the tool via the serial port or KVM, restart the heartbreak network interface “priveth0”:
linux:/etc/sysconfig/network # rcnetwork restart priveth0
Shutting down network interfaces:
    priveth0  device: Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet (rev 20)
    priveth0  configuration: eth-id-84:2b:2b:67:1d:7f
    priveth0                                                          done
Setting up network interfaces:
Interface 'priveth0' of device 'priveth0' renamed to priveth0
Don't use PERSISTENT_NAME any longer. See /usr/share/doc/packages/sysconfig/README.Persistent_Interface_Names
    priveth0  device: Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet (rev 20)
    priveth0  configuration: eth-id-84:2b:2b:67:1d:7f
    priveth0  (DHCP) . . . . . no IP address yet... backgrounding.
    priveth0                                                          waiting
linux:/etc/sysconfig/network #
2. View the file of the “priveth0”, and confirm the DHCP is open:
linux:/etc/sysconfig/network # ls
config                          ifcfg-eth-id-84:2b:2b:67:1d:81  ifcfg-eth-id-90:e2:ba:00:fe:1c  ifcfg.template       scripts
dhcp                            ifcfg-eth-id-84:2b:2b:67:1d:83  ifcfg-eth-id-90:e2:ba:00:fe:1d  ifroute-lo
if-down.d                       ifcfg-eth-id-84:2b:2b:67:1d:85  ifcfg-eth-id-90:e2:ba:00:fe:62  ifservices.template
if-up.d                         ifcfg-eth-id-90:e2:ba:00:fd:c0  ifcfg-eth-id-90:e2:ba:00:fe:63  providers
ifcfg-eth-id-84:2b:2b:67:1d:7f  ifcfg-eth-id-90:e2:ba:00:fd:c1  ifcfg-lo                        routes
linux:/etc/sysconfig/network #
linux:/etc/sysconfig/network # cat ifcfg-eth-id-84\:2b\:2b\:67\:1d\:7f
BOOTPROTO='dhcp'
STARTMODE='onboot'
PERSISTENT_NAME='priveth0'
POST_UP_SCRIPT='/opt/VRTSnasgw/scripts/privdev_up.sh'
linux:/etc/sysconfig/network #
3. In the N8300 master node, check if the DHCP has been open, if so, restart the DHCP:
N8300zx_01:~ #
N8300zx_01:~ # rcdhcpd
Usage: /usr/sbin/rcdhcpd {start|stop|status|try-restart|restart|force-reload|reload|probe|check-syntax} [-v]
N8300zx_01:~ #
N8300zx_01:~ # rcdhcpd status
Checking for DHCP server:                                             running
N8300zx_01:~ #
N8300zx_01:~ #
N8300zx_01:~ #
N8300zx_01:~ #
N8300zx_01:~ # rcdhcpd stop
Shutting down DHCP server                                             done
N8300zx_01:~ # rcdhcpd status
Checking for DHCP server:                                             unused
N8300zx_01:~ #
N8300zx_01:~ #
N8300zx_01:~ # rcdhcpd start
Starting DHCP server [chroot]                                         done
N8300zx_01:~ #
N8300zx_01:~ #
N8300zx_01:~ #
N8300zx_01:~ #

Root Cause
1 As the heartbreak IP can be ping through, and it can SSH the old operation, so the network physical link hasn’t any problem;
2. We conclude it may be caused by the master engine node can’t identify the removed node’s heartbreak IP.

Suggestions
For the unidentified heartbreak IP, if the network physical link hasn’t any problem, restart the DHCP service in the master node, and restart the network service in the distributed node, generally, the problem can be settled.

END