Asset ID:	1-72-1345728.1
Update Date:	2011-08-08
Keywords:

---

Solution Type  Problem Resolution Sure

Solution  1345728.1 :   VTL - net0 interface netmask changing during boot (255.255.255.0)  

In this Document
  Symptoms
  Changes
  Cause
  Solution
     Workaround
     Permanent Fix

---

Applies to:

Sun StorageTek VTL Plus Storage Appliance - Version: 1.0 - Build 1323 to 2.0 - Build 1656 - Release: 1.0 to 2.0
Information in this document applies to any platform.

Symptoms

Failover configured

VTL processes will not start due to no heartbeat

Cannot access ng0 or e1000g interface

Cannot ping ng0 or e1000g interface

net0 netmask is set to 255.255.255.0 instead of 255.255.254.0

Changes

Server was rebooted on a system with failover configured

Cause

Code issue

Solution

Workaround

The fix will be in P24 or P25, until then manually reset netmask and/or set the netmask at bootup (Sxx or rc2.d script) for customer that runs into this bug.


To verify that you have run into this issue run at the command line:
# ifconfig -a

Output similar to the following will be displayed (x4200 is ng0 and x4600 is e1000g)
====================
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1 inet 127.0.0.1 netmask ff000000

e1000g0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2 inet 10.x.x.x netmask ffffff00 broadcast 10.x.x.x
ether 0:14:4f:8c:e5:60

e1000g0:1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2 inet 10.x.x.x netmask fffffc00 broadcast 10.x.x.x

e1000g1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3 inet 10.x.x.x netmask fffffc00 broadcast 10.x.x.x
ether 0:14:4f:8c:e5:61

e1000g1:1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3 inet 10.x.x.x netmask fffffc00 broadcast 10.x.x.x
===================

To recover immediately from the netmask situation, ssh into node 1 and issue the following commands:
# ifconfig e1000g0 netmask 255.255.254.0
# ifconfig e1000g0 down
# ifconfig e1000g0 up

If this does not bring the connection back up, find a PC with VTL Console installed to connect to the internal 3com Ethernet switch; make the ip of the PC to be 10.0.0.77; netmask 255.255.255.0.  This should allow access to the machine over 10.0.0.101.

Once the VTL GUI is up, right click on the node, select Systems Management>Network Management.  In the pop up window select inet0 and to config NIC.  Use edit to change the netmask from 255.255.255.0 to 255.255.254.0.

When asked "which do you want to be the primary", select nge0 for an x4200M2 server node or e1000g0 for a x4600M2.

Permanent Fix

Apply VTL+ 2.0 Build 1656 Patch 24

Note: Fix was not back ported to earlier versions, must upgrade to Build 1656.

Attachments

This solution has no attachment