Okay, this is on an F630 running a pretty old DOT (NetApp Release 4.3.4D5: Tue May 26 14:05:43 PDT 1998), so I don't expect any answers, but I thought I'd ask anyway.
We just had this box stop passing traffic on it 1000fdx interface. I logged in on console and tried to cycle the 1000fdx interface and got a pretty strange message:
whirlpool> ifconfig -a e2: flags=42<BROADCAST,RUNNING> mtu 1500 ether 00:c0:95:f8:2f:6d (Twisted pair) f3: flags=43<UP,BROADCAST,RUNNING> mtu 4352 inet 192.168.254.250 netmask ffffff00 broadcast 192.168.254.255 ether 00:00:f8:bd:c6:04 (Dual Attach Fiber) e10: flags=60043<UP,BROADCAST,RUNNING,TCPCKSUM,IPHDRCKSUM> mtu 1500 inet 192.168.250.250 netmask ffffff00 broadcast 192.168.250.255 ether 00:60:cf:20:48:61 (1000fx) lo: flags=9<UP,LOOPBACK> mtu 1536 inet 127.0.0.1 netmask ff000000 broadcast 127.0.0.1 whirlpool> ifconfig e10 down Couldn't do snap trace, one already active
We ended up rebooting the box and it came back up okay.
There was no snapshot running. The filer wasn't doing anything out of the ordinary or under heavy load. Nothing in the logs either. It looked fine, except it just stopped passing traffic. The interface was not pingable. I did not try cycling the port on the the switch it's plugged into (a Lucent Cajun P550).
The box had been up for over 183 days w/o a single problem.
Any idea what that message means?
Anyone seen a NetApp just stop passing traffic like this on an 1000fdx interface?
Thanks.
j. -- Jay Soffian jay@cimedia.com UNIX Systems Administrator 404.572.1941 Cox Interactive Media
Hi Jay,
You probably had a trace running on the GbE interface when you ifconfig'd it down. Snap trace is a facility used in alttrace which attempts to preserve trace information in a special buffer for future reference.
Either way, I suspect the message was merely informative and not indicative of a problem disabling the NIC.
--Lee
On Mon, 3 May 1999, Jay Soffian wrote:
Okay, this is on an F630 running a pretty old DOT (NetApp Release 4.3.4D5: Tue May 26 14:05:43 PDT 1998), so I don't expect any answers, but I thought I'd ask anyway.
We just had this box stop passing traffic on it 1000fdx interface. I logged in on console and tried to cycle the 1000fdx interface and got a pretty strange message:
whirlpool> ifconfig -a e2: flags=42<BROADCAST,RUNNING> mtu 1500 ether 00:c0:95:f8:2f:6d (Twisted pair) f3: flags=43<UP,BROADCAST,RUNNING> mtu 4352 inet 192.168.254.250 netmask ffffff00 broadcast 192.168.254.255 ether 00:00:f8:bd:c6:04 (Dual Attach Fiber) e10: flags=60043<UP,BROADCAST,RUNNING,TCPCKSUM,IPHDRCKSUM> mtu 1500 inet 192.168.250.250 netmask ffffff00 broadcast 192.168.250.255 ether 00:60:cf:20:48:61 (1000fx) lo: flags=9<UP,LOOPBACK> mtu 1536 inet 127.0.0.1 netmask ff000000 broadcast 127.0.0.1 whirlpool> ifconfig e10 down Couldn't do snap trace, one already active
We ended up rebooting the box and it came back up okay.
There was no snapshot running. The filer wasn't doing anything out of the ordinary or under heavy load. Nothing in the logs either. It looked fine, except it just stopped passing traffic. The interface was not pingable. I did not try cycling the port on the the switch it's plugged into (a Lucent Cajun P550).
The box had been up for over 183 days w/o a single problem.
Any idea what that message means?
Anyone seen a NetApp just stop passing traffic like this on an 1000fdx interface?
Thanks.
j.
Jay Soffian jay@cimedia.com UNIX Systems Administrator 404.572.1941 Cox Interactive Media
-------------------------------- Lee Razo (lrazo@netapp.com) Network Appliance, Inc. Santa Clara, Ca. http://www.netapp.com/ "I agree with Lee" -David Koresh --------------------------------
-
Jay Soffian -
Lee Razo