[prev in list] [next in list] [prev in thread] [next in thread]
List: veritas-ha
Subject: Re: [Veritas-ha] SFRAC 4.1 HP-Ux 11.23 "V-14-2-15241 LLT
From: Shashi Kanth Boddula <shashi-kanth.boddula () hp ! com>
Date: 2007-08-21 4:09:52
Message-ID: 46CA62C0.8010502 () hp ! com
[Download RAW message or body]
Ok, Thank you for the clarification.
Abhijit Toley wrote:
> Hi Shashi,
>
> No. It is not necessary to plumb IP on top of LLT interfaces. However, LLT will \
> work even if you do so.
> Regards,
> Abhijit.
>
>
> > -----Original Message-----
> > From: Shashi Kanth Boddula [mailto:shashi-kanth.boddula@hp.com]
> > Sent: Tuesday, August 21, 2007 8:40 AM
> > To: Abhijit Toley; Bryan Wood
> > Cc: veritas-ha@mailman.eng.auburn.edu
> > Subject: Re: [Veritas-ha] SFRAC 4.1 HP-Ux 11.23 "V-14-2-15241
> > LLT notconfigured"
> >
> > The problem is solved, i have found another cluster with same cluster
> > ID, so i reconfigured my cluster with different ID, now
> > everything looks
> > fine.
> >
> > I have one basic questions here.
> >
> > From the VERITAS documentation for SFRAC 4.1, i have found
> > the bellow
> > point.
> >
> > "LLT serves as a high performance replacement for the IP
> > stack and runs
> > directly on top of
> > the Data Link Protocol Interface (DLPI) layer. The use of LLT rather
> > than IP removes
> > latency and overhead associated with the IP stack."
> >
> > From the above word, is it necessary to configure the NIC which i am
> > going to use for private communication (in my case, it it LAN1) with
> > TCP/IP parameters ?
> >
> > -- Shashi
> >
> >
> > Abhijit Toley wrote:
> >
> > > Hi Shashi,
> > >
> > > Let me clarify the meaning of the following output and see
> > >
> > if iy helps.
> >
> > >
> > >
> > > > 0 cayman OPEN
> > > > lan1 UP 00:17:08:7C:4B:BF
> > > > lan0 DOWN
> > > > 1 charger OPEN
> > > > lan1 UP 00:17:08:7C:58:FB
> > > > lan0 DOWN
> > > > * 2 invicta OPEN
> > > > lan1 UP 00:30:6E:49:D6:61
> > > > lan0 UP 00:30:6E:1C:D2:B5
> > > >
> > > >
> > > The * indicates the node on which this command was fired.
> > >
> > This node is always OPEN with itself and the MAC addresses
> > are the MAC addresses of the lan1 and lan2 respectively of this node.
> >
> > > For the other nodes, e.g.
> > >
> > > "lan1 UP 00:17:08:7C:4B:BF"
> > >
> > > means that "on lan1 of the local node (i.e. on which the
> > >
> > command was fired), packets are coming from the node cayman
> > (this particular line is for node cayman) from the mac
> > address 00:17:08:7C:4B:BF"
> >
> > > Hope this helps in the furthur analysis.
> > >
> > > Thanks and Regards,
> > > Abhijit.
> > >
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: veritas-ha-bounces@mailman.eng.auburn.edu
> > > > [mailto:veritas-ha-bounces@mailman.eng.auburn.edu] On Behalf
> > > > Of Shashi Kanth Boddula
> > > > Sent: Monday, August 20, 2007 11:15 AM
> > > > To: Bryan Wood
> > > > Cc: veritas-ha@mailman.eng.auburn.edu
> > > > Subject: Re: [Veritas-ha] SFRAC 4.1 HP-Ux 11.23 "V-14-2-15241
> > > > LLT notconfigured"
> > > >
> > > > Bryan, Thank you very much for your reply. I think you have
> > > > cached the
> > > > actual problem.
> > > >
> > > > In the last node where LTT is running fine, on that node,
> > > > "lltstat -nvv"
> > > > gives the bellow output.
> > > >
> > > >
> > > > 0 cayman OPEN
> > > > lan1 UP 00:17:08:7C:4B:BF
> > > > lan0 DOWN
> > > > 1 charger OPEN
> > > > lan1 UP 00:17:08:7C:58:FB
> > > > lan0 DOWN
> > > > * 2 invicta OPEN
> > > > lan1 UP 00:30:6E:49:D6:61
> > > > lan0 UP 00:30:6E:1C:D2:B5
> > > >
> > > >
> > > > In this command output, whatever the MAC address it shows for
> > > > first two
> > > > nodes are wrong. My first two nodes LAN1 doesn't have that
> > > > MAC address
> > > > what this command shows on the third node.
> > > >
> > > > How it is possible that this command shows some other MAC
> > > > address for my
> > > > first two nodes.
> > > >
> > > > On the first two nodes where LLT fails, if i try to start LLT
> > > > manually,
> > > > from the output, whatever MAC address it shows , that MAC address
> > > > doesn't belongs to none of my 3 nodes.
> > > >
> > > > cayman:/ #/sbin/init.d/llt start
> > > > LLT lltconfig ERROR V-14-2-15238 node 0 already exists in
> > > >
> > cluster 200
> >
> > > > and has the address - 00:17:08:7C:4B:BF
> > > > LLT lltconfig ERROR V-14-2-15241 LLT not configured, use -o
> > > > to override
> > > > this warning
> > > >
> > > > In the above output, it is showing "00:17:08:7C:4B:BF".
> > > >
> > > > But, i am not finding this MAC on all my nodes.
> > > >
> > > > cayman:/ #lanscan
> > > > Hardware Station Crd Hdw Net-Interface NM MAC
> > > > HP-DLPI DLPI
> > > > Path Address In# State NamePPA ID Type
> > > > Support Mjr#
> > > > 0/0/0/0 0x00306E1C905C 0 UP lan0 snap0 1 ETHER
> > > > Yes 119
> > > > 0/6/0/0 0x00306E278F4A 1 UP lan1 snap1 2 ETHER
> > > > Yes 119
> > > >
> > > >
> > > > charger:/ #lanscan
> > > > Hardware Station Crd Hdw Net-Interface NM MAC
> > > > HP-DLPI DLPI
> > > > Path Address In# State NamePPA ID Type
> > > > Support Mjr#
> > > > 0/0/0/0 0x00306E2C80B9 0 UP lan0 snap0 1 ETHER
> > > > Yes 119
> > > > 0/6/0/0 0x00306E0F7A74 1 UP lan1 snap1 2 ETHER
> > > > Yes 119
> > > >
> > > >
> > > >
> > > > invicta:/ #lanscan
> > > > Hardware Station Crd Hdw Net-Interface NM MAC
> > > > HP-DLPI DLPI
> > > > Path Address In# State NamePPA ID Type
> > > > Support Mjr#
> > > > 0/0/0/0 0x00306E1CD2B5 0 UP lan0 snap0 1 ETHER
> > > > Yes 119
> > > > 0/2/0/0 0x00306E49D661 1 UP lan1 snap1 2 ETHER
> > > > Yes 119
> > > >
> > > > Bryan, please tell me what could be the problem ?
> > > >
> > > >
> > > > Bryan Wood wrote:
> > > >
> > > >
> > > > > > > cayman:/ #/sbin/init.d/llt start
> > > > > > > LLT lltconfig ERROR V-14-2-15238 node 0 already
> > > > > exists in cluster 200
> > > > > > > and has the address - 00:17:08:7C:4B:BF
> > > > >
> > > > > Which NIC has that MAC address?
> > > > >
> > > > > Collect "lltstat -nvv" from one of the other cluster
> > > > > nodes to see if that MAC is from this cluster. Might
> > > > > also check the arp cache with "arp -a". It is
> > > > > possible that your new node is in some vlan with
> > > > > another cluster already using nodeID 0.
> > > > >
> > > > > Use snoop (or tcpdump with similar options):
> > > > >
> > > > > # snoop -Prt d -d qfe0 -x0,36 ethertype 0xcafe
> > > > > 1 0.00000 ? -> (broadcast) ETHER
> > > > > Type=CAFE (Unknown), size = 70 bytes
> > > > >
> > > > > 0: ffff ffff ffff 0800 20be 6355 cafe 0101
> > > > > ........ .cU....
> > > > > 16: 150a 0000 0002 ffff 8c00 0000 0038 0000
> > > > > .............8..
> > > > > 32: 0000 8000 ....
> > > > >
> > > > > 2 0.20005 ? -> (broadcast) ETHER
> > > > > Type=CAFE (Unknown), size = 70 bytes
> > > > >
> > > > > 0: ffff ffff ffff 0800 20be 6c8d cafe 0101
> > > > > ........ .l..þ..
> > > > > 16: 150a 0000 0001 ffff 8c00 0000 0038 0000
> > > > > .............8..
> > > > > 32: 0000 8000 ....
> > > > >
> > > > > Byte Description Value in 2nd packet
> > > > > ===== =============== ===================
> > > > > 00-05 destination MAC ffff ffff ffff
> > > > > 06-11 source MAC 0800 20be 6c8d
> > > > > 12-13 ethertype cafe
> > > > > 16 hex cluster ID 15
> > > > > 21 hex node ID 01
> > > > >
> > > > > So:
> > > > >
> > > > > [s1]# snoop -Prt d -d hme0 -x16,6 -c 10000 ethertype
> > > > > 0xcafe | grep 0: | sort -u
> > > > > Using device /dev/hme (non promiscuous)
> > > > > 10000 packets captured
> > > > > 0: 570a 0000 0002
> > > > > W.....
> > > > > 0: 570a 0000 0003
> > > > > W.....
> > > > > 0: 570a 0000 0004
> > > > > W.....
> > > > > 0: 580a 0000 0004
> > > > > X.....
> > > > > 0: 580a 0000 0005
> > > > > X.....
> > > > > 0: 580a 0000 0006
> > > > > X.....
> > > > > 0: 610a 0000 0000
> > > > > a.....
> > > > > 0: 610a 0000 0001
> > > > > a.....
> > > > > 0: 610a 0000 0002
> > > > > a.....
> > > > > [s1]#
> > > > >
> > > > > Which reflects 3 clusters each with three nodes:
> > > > >
> > > > > clusterID 87 nodes 2, 3, and 4
> > > > > clusterID 88 nodes 4, 5, and 6
> > > > > clusterID 91 nodes 0, 1, and 2
> > > > >
> > > > >
> > > > > HTH,
> > > > > -B.
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > ______________________________________________________________
> > > > ______________________
> > > >
> > > >
> > > > > Shape Yahoo! in your own image. Join our Network Research
> > > > >
> > > > >
> > > > Panel today!
> > > > http://surveylink.yahoo.com/gmrs/yahoo_panel_invite.asp?a=7
> > > >
> > > >
> > > > >
> > > > >
> > > > >
> > > > _______________________________________________
> > > > Veritas-ha maillist - Veritas-ha@mailman.eng.auburn.edu
> > > > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-ha
> > > >
> > > >
> > > >
> >
_______________________________________________
Veritas-ha maillist - Veritas-ha@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-ha
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic