X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C89A64.DADB5908@onstor-exch02.onstor.net>; Wed, 9 Apr 2008 10:12:13 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: Defect  TED00022924 Cougar- system ping does not work on vsvr IP from vsvr context or outside Re-opened
Date: Wed, 9 Apr 2008 10:12:13 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E09596163@onstor-exch02.onstor.net>
In-Reply-To: <20080409101103.1f70c748@ripper.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Defect  TED00022924 Cougar- system ping does not work on vsvr IP from vsvr context or outside Re-opened
Thread-Index: AciaZLE3n3rOFmm/R5KOE0u0wqE+oQAAB0sg
References: <WEBMAILz4rlDQcpCqJf000011f2@mail.onstor.com> <20080409101103.1f70c748@ripper.onstor.net>
From: "John Keiffer" <john.keiffer@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>


Not that I know of... I don't use vlan tagging...

-----Original Message-----
From: Andy Sharp=20
Sent: Wednesday, April 09, 2008 10:11 AM
To: John Keiffer
Subject: Re: Defect TED00022924 Cougar- system ping does not work on
vsvr IP from vsvr context or outside Re-opened

On 9 Apr 2008 09:57:29 -0700 <john.keiffer@onstor.com> wrote:

> Note_Entry: I'm re-opening this defect. I do not think this is
> resolved. I have a Cougar cluster g6r10 to which I added g5r10. The
> mgmt vsvr on g5r10 is enabled, has an interface, and a route. It can
> ping 10.3.0.1, but it can't ping the target vsvr of a different filer
> that I want to do a DMIP to. This vsvr on the remote cluster CAN be
> pinged by the mgmt vsvr of g6r10.
>=20
> 04/09/08 09:44:21 g5r10 VS_MGMT_67415 diag> system ping 10.3.5.1 -n 5
> vsvr id =3D 5
> src ip bind is 192.167.5.1
> PING 10.3.5.1 (10.3.5.1) from 192.167.5.1 : 56(84) bytes of data.
>=20
> --- 10.3.5.1 ping statistics ---
> 5 packets transmitted, 0 received, 100% packet loss, time 3999ms
>=20
> 04/09/08 09:53:00 g5r10 VS_MGMT_67415 diag> interface show interface
> Interface  Table
>
------------------------------------------------------------------------
--
> Interface     Admin.     Operation  Mac Address
> LPORT          Vlan
>
------------------------------------------------------------------------
--
> int_mgmt      UP         UP         0:7:34:7:57:90
> fp1.0           0 04/09/08 09:53:11 g5r10 VS_MGMT_67415 diag>
> interface show ip IP Table
> ----------------------------------------------------------------
> dest              mask              interface            vlan
> ----------------------------------------------------------------
> 10.3.10.81        255.255.0.0       int_mgmt          disabled (0)
                                                        ^^^^^^^^
Does this have anything to do with why you can't ping? ~:^)

> 04/09/08 09:53:14 g5r10 VS_MGMT_67415 diag> arp show ARP Table
> ---------------------------------------------------------
> dest              mac                 age               interface
> ---------------------------------------------------------
> 10.3.34.16        0:15:17:25:46:c4    5860              int_mgmt
> 10.3.5.1          0:0:0:0:0:0         3977              int_mgmt
> 10.3.12.26        0:7:e9:17:1d:e2     5808              int_mgmt
> 10.3.34.22        0:d:60:83:ee:f6     5747              int_mgmt
> 10.3.34.27        0:d:60:83:f0:3e     5740              int_mgmt
> 10.3.5.1          0:7:34:1:b8:10      5274              int_mgmt
> 10.3.10.101       0:7:34:7:40:10      5210              int_mgmt
> 10.3.15.15        0:3:47:b1:e3:c8     5202              int_mgmt
> 10.3.10.81        0:7:34:7:57:90      0                 int_mgmt
> 10.3.0.1          0:1:30:b8:4b:80     5183              int_mgmt
> 04/09/08 09:53:18 g5r10 VS_MGMT_67415 diag>
>=20
> 04/09/08 09:44:28 g6r10 VS_MGMT_1856 diag> system ping 10.3.5.1 -n 5
> vsvr id =3D 1
> src ip bind is 192.167.1.1
> PING 10.3.5.1 (10.3.5.1) from 192.167.1.1 : 56(84) bytes of data.
> 64 bytes from 10.3.5.1: icmp_seq=3D1 ttl=3D255 time=3D17.9 ms
> 64 bytes from 10.3.5.1: icmp_seq=3D2 ttl=3D255 time=3D8.09 ms
> 64 bytes from 10.3.5.1: icmp_seq=3D3 ttl=3D255 time=3D1.38 ms
> 64 bytes from 10.3.5.1: icmp_seq=3D4 ttl=3D255 time=3D7.95 ms
> 64 bytes from 10.3.5.1: icmp_seq=3D5 ttl=3D255 time=3D8.00 ms
>=20
> --- 10.3.5.1 ping statistics ---
> 5 packets transmitted, 5 received, 0% packet loss, time 3999ms
> rtt min/avg/max/mdev =3D 1.380/8.682/17.978/5.311 ms
> 04/09/08 09:53:02 g6r10 VS_MGMT_1856 diag>
> Files_list_entry: Change 28501 by andys@ripper on 2008/03/24 16:26:27
>=20
>         Fix TED00022924 - system ping -c N does not work
>        =20
>         This was marked for cougar but it looked to me like it
>         wouldn't work too well on bobcat either.  The count option
>         wasn't being handled right.
>        =20
>         Took the opportunity to clean up all the code for system ping.
>        =20
>         reviewed by maximk
>=20
> Affected files ...
>=20
> ... //depot/dev/nfx-tree/code/ssc-nfxsh/cmd_system.c#44 edit
> ... //depot/dev/nfx-tree/code/ssc-nfxsh/linux.h#12 edit
> ... //depot/dev/nfx-tree/code/ssc-nfxsh/openbsd.h#12 edit
>=20
>=20
> Project:=20
>=20
>=20
