AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20090218173318.6d025018@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:exch1.onstor.net
NSV:
SSH:
R:<jonathan.goldick@onstor.com>,<damon.wong@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/andys@onstor.net@exch1.onstor.net/INBOX	0	2779531E7C760D4491C96305019FEEB51851A3BF86@exch1.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Wed, 18 Feb 2009 17:33:31 -0800
From: Andrew Sharp <andy.sharp@onstor.com>
To: Jonathan Goldick <jonathan.goldick@onstor.com>
Cc: Damon Wong <damon.wong@onstor.com>
Subject: Re: Odd system ping behavior and can't connect to NTLM server
Message-ID: <20090218173331.56150f40@ripper.onstor.net>
In-Reply-To: <2779531E7C760D4491C96305019FEEB51851A3BF86@exch1.onstor.net>
References: <2779531E7C760D4491C96305019FEEB51851A3BF86@exch1.onstor.net>
Organization: Onstor
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Wed, 18 Feb 2009 17:17:19 -0800 Jonathan Goldick
<jonathan.goldick@onstor.com> wrote:

> No, perhaps Andy has seen this one.
>=20
>=20
> ________________________________
> From: Damon Wong
> To: Jonathan Goldick
> Sent: Wed Feb 18 17:10:54 2009
> Subject: FW: Odd system ping behavior and can't connect to NTLM server
> Any idea on what is causing the odd behavior?
>=20
> ________________________________
> From: Damon Wong
> Sent: Wednesday, February 18, 2009 2:38 PM
> To: John Rogers; Sandrine Boulanger; Raj Kumar
> Subject: Odd system ping behavior and can't connect to NTLM server
>=20
> I am trying to do =E2=80=9Csystem ping=E2=80=9D to Matrix under vsvr and =
1 out of 3
> is failed. However, it looks like it accesses different interfaces
> each time.
>=20
> g5r204 G5R204-T1 diag> system ping MATRIX.LAB
> src ip bind is 192.167.2.1
> PING 10.3.0.5 (10.3.0.5) from 192.167.2.1 : 56(84) bytes of data.
> 64 bytes from 10.3.0.5: icmp_seq=3D1 ttl=3D128 time=3D0.275 ms
> 64 bytes from 10.3.0.5: icmp_seq=3D2 ttl=3D128 time=3D0.160 ms
> 64 bytes from 10.3.0.5: icmp_seq=3D3 ttl=3D128 time=3D0.140 ms
> 64 bytes from 10.3.0.5: icmp_seq=3D4 ttl=3D128 time=3D0.129 ms
>=20
> --- 10.3.0.5 ping statistics ---
> 4 packets transmitted, 4 received, 0% packet loss, time 3000ms
> rtt min/avg/max/mdev =3D 0.129/0.176/0.275/0.058 ms
> g5r204 G5R204-T1 diag> system ping MATRIX.LAB
> src ip bind is 192.167.2.1
> PING 10.2.0.5 (10.2.0.5) from 192.167.2.1 : 56(84) bytes of data.
> 64 bytes from 10.2.0.5: icmp_seq=3D1 ttl=3D128 time=3D0.275 ms
> 64 bytes from 10.2.0.5: icmp_seq=3D2 ttl=3D128 time=3D0.198 ms
> 64 bytes from 10.2.0.5: icmp_seq=3D3 ttl=3D128 time=3D0.184 ms
>=20
> --- 10.2.0.5 ping statistics ---
> 3 packets transmitted, 3 received, 0% packet loss, time 2000ms
> rtt min/avg/max/mdev =3D 0.184/0.219/0.275/0.040 ms
> g5r204 G5R204-T1 diag> system ping MATRIX.LAB
> src ip bind is 192.167.2.1
> PING 10.3.50.187 (10.3.50.187) from 192.167.2.1 : 56(84) bytes of
> data.
>=20
> --- 10.3.50.187 ping statistics ---
> 10 packets transmitted, 0 received, 100% packet loss, time 8999ms

The different target IP addresses are a result of getting different
answers from your DNS setup for MATRIX.LAB each time.

My guess is you don't have a route to 10.2.x.x either.

> g5r204 G5R204-T1 diag> arp show
> ARP Table
> ---------------------------------------------------------
> dest              mac                 age               interface
> ---------------------------------------------------------
> 10.3.50.187       0:0:0:0:0:0         9326              test
> 10.3.0.5          0:0:0:0:0:0         9326              test
> 10.3.0.249        0:1:30:45:57:0      11550             test
> 10.3.0.247        0:1:30:b7:5d:40     11520             test
> 10.3.0.253        0:1:30:17:72:a0     11519             test
> 10.3.34.16        0:15:17:25:46:c4    11102             test
> 10.3.50.187       0:0:0:0:0:0         10458             test
> 10.3.0.5          0:3:47:ae:9d:86     11652             test
> 10.3.51.6         0:c:29:a4:bf:26     10534             test
> 10.3.0.7          0:7:e9:1a:f8:4b     11652             test
> 10.3.0.1          0:19:b9:a1:6a:2c    10545             test

Not sure what you're trying to show me with the arp cache info...
except that 10.3.50.187 is in the list twice, both times with a null
mac address.   10.3.0.5 also has a null mac address.  Very naughty of
somebody.  What are these IP addresses assigned to?  Vmware instances?

> It also happened when I tried to ping the domains on vmware setup.
> Since they only have one interface, 1 out of 2 is failed.
>=20
> How can we fix it?

Fix your DNS setup and your null MAC addresses.  I'll take an aspirin,
and you can call me in the morning.  Or perhaps the DNS is correct, as
in it's a round-robin setup and supposed to return a different address
each time, in which case you have to fix your routing or other problems.

> And when I tried to setup a domain on vsvr, it always complains:
>=20
>             g5r204 G5R204-T1 diag> vsvr enable
>             Retrieving windows domain information failed. Verify your
> domain configuration and network connectivity to the domain
> controller(s).
>=20
>             Error log:
>             Unable to find a suitable server
>=20
>             % Command failure.
>=20
>             Feb 18 14:32:30 g5r204 : 0:0:eventd:NOTICE: Process-EVENT
> IP i/f: IP 192.167.2.1, Port bp0, State Up Feb 18 14:32:30 g5r204 :
> 0:0:auth_agent:INFO: authAgent_getDomainSid[2252] : domain name:
> netbios=3D<2K3NTPC.LAB>  ads=3D<> Feb 18 14:32:30 g5r204 :
> 0:0:auth_agent:INFO: authAgent_getDomainSid[2364] :
> loginPrinc.domain=3D2K3NTPC.LAB
> loginPrinc.name=3DAdministrator Feb 18 14:32:30 g5r204 :
> 0:0:auth_agent:INFO: authen_getDomainSid[2605] : execing
> '/onstor/bin/net rpc info -U <uname> -a <passwd>
> -Z /tmp /AUTH_TMPmNax7x
> -s /onstor/conf/smbd.conf.G5R204-T1_2K3NTPC.LAB' Feb 18 14:32:34
> g5r204 : 0:0:auth_agent:ERROR: authen_getDomainSid[2621] : SID not
> found in log file. Feb 18 14:32:34 g5r204 : 0:0:auth_agent:ERROR:
> authAgent_getDomainSid[2386] : Failed to get domain SID. rc=3D2 Feb 18
> 14:32:34 g5r204 : 0:0:auth_agent:INFO: authAgent_getDomainSid[2252] :
> domain name: netbios=3D<2K3NTPC.LAB>  ads=3D<> Feb 18 14:32:34 g5r204 :
> 0:0:auth_agent:INFO: authAgent_getDomainSid[2364] :
> loginPrinc.domain=3D2K3NTPC.LAB
> loginPrinc.name=3DAdministrator Feb 18 14:32:35 g5r204 :
> 0:0:auth_agent:INFO: authen_getDomainSid[2605] : execing
> '/onstor/bin/net rpc info -U <uname> -a <passwd>
> -Z /tmp /AUTH_TMPI0AiIq
> -s /onstor/conf/smbd.conf.G5R204-T1_2K3NTPC.LAB' Feb 18 14:32:39
> g5r204 : 0:0:auth_agent:ERROR: authen_getDomainSid[2621] : SID not
> found in log file. Feb 18 14:32:39 g5r204 : 0:0:auth_agent:ERROR:
> authAgent_getDomainSid[2386] : Failed to get domain SID. rc=3D2 Feb 18
> 14:32:39 g5r204 : 0:0:auth_agent:ERROR: Failed to retrieve domain SID
> for domain 2K3NTPC.LAB (virtual server G5R204-T1) Feb 18 14:32:39
> g5r204 : 0:0:vsd:ERROR: vsd_enableVsProc : Error enabling auth.
> services for VS 2, status 8 Feb 18 14:32:39 g5r204 :
> 0:0:eventd:NOTICE: Process-EVENT IP i/f: IP 192.167.2.1, Port bp0,
> State Remove Feb 18 14:32:40 g5r204 : 1:2:efs:INFO: 184: FS:
> g5r204-t1-vol1 0x77000000183 - unmount - req - Unmounting volume Feb
> 18 14:32:41 g5r204 : 0:0:sdm:NOTICE: (sdm_procCloseReq)  handle:
> 0x01200002 Feb 18 14:32:41 g5r204 : 0:0:sdm:NOTICE:
> (sdm_doCloseDevice) FP Device:
> ONStor_0a50a1_0a4f7100480d333d4511000000, Handle: 0x01200002 Feb 18
> 14:32:41 g5r204 : 0:0:eventd:NOTICE: Process-EVENT Volume: name
> 'g5r204-t1-vol1', Id 0x0000077000000183, Event 'Offline',   State
> 'Down' Feb 18 14:32:41 g5r204 : 0:0:nfxsh:NOTICE: cmd[56]: vsvr
> enable : status[11]
>=20
> Thanks,
> Damon
>=20
>=20
