From: Patrick Torney (ptorney@satx.rr.com)
Date: Sat Jun 12 2004 - 22:51:23 GMT-3
Might the MTU being >1500 be giving you fits. I was working on an ospf
adjacency issue on an online rack recently where the MTU size on the switch
had been reset to 1518 (not sure why...probably someone else's lab exercise
called for such) and that prevented OSPF adjacencies from forming... not
sure if this is any help, but the datagram being > 1500 bytes sticks out to
me...
----- Original Message -----
From: "Ty" <tycampbell@comcast.net>
To: "Sharma, Mohit" <mohit.sharma@hp.com>; "Ccielab@Groupstudy.Com"
<ccielab@groupstudy.com>
Sent: Saturday, June 12, 2004 2:10 PM
Subject: Re: Routers going crazy (ISIS??)
> You may also want to try setting one as a DIS since the frame network is
> multipoint (Similair to a DR in OSPF)
>
> isis priority < priority>
> default is 64
> this is an interface config command, just like ospf priority
> ----- Original Message -----
> From: "Sharma, Mohit" <mohit.sharma@hp.com>
> To: "Ty" <tycampbell@comcast.net>; "Ccielab@Groupstudy.Com"
> <ccielab@groupstudy.com>
> Sent: Saturday, June 12, 2004 1:16 PM
> Subject: RE: Routers going crazy (ISIS??)
>
>
> Hi,
>
> Actually I got this from the IE workbook, according to the author's
> (Brian's) the Net size should be same on all the routers and not
> necessarily start with a 49.
>
> Also as you can see from the output below the clns adjacenciea are
> forming fine.
> The only other thing I can see is this frame-realy debug-
> xFEFE(CLNS), datagramsize 1505
> 00:48:23: Serial0: broadcast search
> 00:48:23: Serial0(o): dlci 403(0x6431), pkt type 0xFEFE(CLNS),
> datagramsize 1505
> 00:48:23: broadcast dequeue
> 00:48:23: Serial0(o):Pkt sent on dlci 403(0x6431), pkt type
> 0xFEFE(CLNS), datagramsize 1505
> 00:48:23: Serial0(i): dlci 403(0x6431), pkt type 0xFEFE, datagramsize
> 1505
> 00:48:23: Serial0: broadcast search
> 00:48:23: Serial0(o): dlci 403(0x6431), pkt type 0xFEFE(CLNS),
> datagramsize 1505
> 00:48:23: broadcast dequeue
> 00:48:23: Serial0(o):Pkt sent on dlci 403(0x6431), pkt type
> 0xFEFE(CLNS), datagramsize 1505
> 00:48:23: Serial0: broadcast search
> 00:48:23: Serial0(o): dlci 403(0x6431), pkt type 0xFEFE(CLNS),
> datagramsize 1505
> 00:48:23: Serial0: broadcast search
> 00:48:23: Serial0(o): dlci 403(0x6431), pkt type 0xFEFE(CLNS),
> datagramsize 1505
> 00:48:23: broadcast dequeue
> 00:48:23: Serial0(o):Pkt sent on dlci 403(0x6431), pkt type
> 0xFEFE(CLNS), datagramsize 1505
> 00:48:23: broadcast dequeue
> 00:48:23: Serial0(o):Pkt sent on dlci 403(0x6431), pkt type
> 0xFEFE(CLNS), datagramsize 1505
> 00:48:23: Serial0(i): dlci 403(0x6431), pkt type 0xFEFE, datagramsize
> 1505
> 00:48:23: Serial0(i): dlci 403(0x6431), pkt type 0xFEFE, datagramsize
> 1505
> 00:48:23: Serial0: broadcast search
> 00:48:23: Serial0(o): dlci 403(0x6431), pkt type 0xFEFE(CLNS),
> datagramsize 1505
> 00:48:24: broadcast dequeue
> 00:48:24: Serial0(o):Pkt sent on dlci 403(0x6431), pkt type
> 0xFEFE(CLNS), datagramsize 1505
> 00:48:24: Serial0: broadcast search
> 00:48:24: Serial0(o): dlci 403(0x6431), pkt type 0xFEFE(CLNS),
> datagramsize 1505
> 00:48:24: broadcast dequeue
> 00:48:24: Serial0(o):Pkt sent on dlci 403(0x6431), pkt type
> 0xFEFE(CLNS), datagramsize 1505
> 00:48:24: Serial0(i): dlci 403(0x6431), pkt type 0xFEFE, datagramsize
> 1505
> 00:48:24: Serial0: broadcast search
> 00:48:24: Serial0(o): dlci 403(0x6431), pkt type 0xFEFE(CLNS),
> datagramsize 1505
> 00:48:24: broadcast dequeue
> 00:48:24: Serial0(o):Pkt sent on dlci 403(0x6431), pkt type
>
> This is happening like crazy on all the three routers, so I even removed
> the isis hello statemnets thinking that maybe that was causing the
> packets to be delayed.
>
> But doesn't work either way :(
>
> Thanks,
> Mohit.
>
> -----Original Message-----
> From: Ty [mailto:tycampbell@comcast.net]
> Sent: Saturday, June 12, 2004 8:09 PM
> To: Sharma, Mohit; Ccielab@Groupstudy.Com
> Subject: Re: Routers going crazy (ISIS??)
>
> make your AFI in the NSAP the same...typically it is 47 or 49
>
> ie..i changed the AFI in your config below
>
> you may wany to make the system id 6 bytes
>
> typically i use
> AFI Area -------System ID--------- N Selector
> XX. XXXX. XXXX. XXXX. XXXX. XX
>
> first 2 X's are AFI.
> next 4 is for area id
> next 12 are system id - must be unique to each system - last 2 are N
> selector..I typically leave these at 00
>
> here is how I usually do a net for ISIS
>
> int s0
> ip add 10.10.50.2 255.255.255.0
> ip router isis
>
> router isis
> net 49.0001.0100.1005.0002.00
>
> I typically transfor the IP address to equal 6 bytes ex -
>
> 10.10.10.50.2 = 010 010 050 002 = 0100.1005.0002 for a system id :-)
>
> HTH!
>
>
>
>
> Rack1R3#
> router isis
> net 47.0001.0001.0003.00
> redistribute eigrp 101
> passive-interface Loopback0
> !
>
> Rack1R4#
> router isis
> net 47.0001.0001.0004.00
> redistribute ospf 1
> passive-interface Loopback0
> no hostname dynamic
>
> Rack1R5#
> !
> router isis
> net 47.0001.0001.0005.00
> passive-interface Loopback0
>
>
>
> ----- Original Message -----
> From: "Sharma, Mohit" <mohit.sharma@hp.com>
> To: "Ty" <tycampbell@comcast.net>; "Ccielab@Groupstudy.Com"
> <ccielab@groupstudy.com>
> Sent: Saturday, June 12, 2004 12:54 PM
> Subject: RE: Routers going crazy (ISIS??)
>
>
> Here it is-
> Rack1R3#
> router isis
> net 1e.0001.0001.0003.00
> redistribute eigrp 101
> passive-interface Loopback0
> !
>
> Rack1R4#
> router isis
> net 28.0001.0001.0004.00
> redistribute ospf 1
> passive-interface Loopback0
> no hostname dynamic
>
> Rack1R5#
> !
> router isis
> net 32.0001.0001.0005.00
> passive-interface Loopback0
> !
>
> Thanks,
> Mohit.
> -----Original Message-----
> From: Ty [mailto:tycampbell@comcast.net]
> Sent: Saturday, June 12, 2004 7:49 PM
> To: Sharma, Mohit; Ccielab@Groupstudy.Com
> Subject: Re: Routers going crazy (ISIS??)
>
> could you include your isis config also ?
> ----- Original Message -----
> From: "Sharma, Mohit" <mohit.sharma@hp.com>
> To: "Ccielab@Groupstudy.Com" <ccielab@groupstudy.com>
> Sent: Saturday, June 12, 2004 12:31 PM
> Subject: Routers going crazy (ISIS??)
>
>
> > Hi All,
> > While doing a lab for ISIS my routers have suddenly gone berserk.
> > I have this setup-
> > RTR3(7500)
> > multipoint - multipoint
> > / \
> > /FR \FR
> > RTR4(2500) RTR5(2500)
> > Serial0 Serial0
> > Till the time IP was there everything was working fine, after I
> > configured ISIS, I cant ping even the spokes that are directly
> > connected. Strangely the clns adjacency is ON, also when I ping from
> > R3-R4 or R3-R5 I can see the packets coming back in the debug but ping
> > fails. Here are the configs-
> >
> > **********************************************
> > Rack1R3#interface Serial3/0
> > no ip address
> > encapsulation frame-relay
> > serial restart-delay 0
> > clockrate 64000
> > no frame-relay inverse-arp
> > end
> >
> > interface Serial3/0.53 multipoint
> > ip address 164.1.35.3 255.255.255.0
> > ip router isis
> > isis hello-multiplier 5
> > isis hello-interval 1
> > frame-relay map clns 305 broadcast
> > frame-relay map ip 164.1.35.3 305 broadcast
> > frame-relay map ip 164.1.35.5 305 broadcast
> >
> > interface Serial3/0.43 multipoint
> > ip address 164.1.34.3 255.255.255.0
> > ip router isis
> > isis hello-multiplier 5
> > isis hello-interval 1
> > frame-relay map clns 304 broadcast
> > frame-relay map ip 164.1.34.3 304 broadcast
> > frame-relay map ip 164.1.34.4 304 broadcast
> >
> > ***********************************************
> > Rack1R4#
> > interface Serial0
> > ip address 164.1.34.4 255.255.255.0
> > ip router isis
> > encapsulation frame-relay
> > no fair-queue
> > frame-relay map clns 403 broadcast
> > frame-relay map ip 164.1.34.3 403 broadcast
> > frame-relay map ip 164.1.34.4 403 broadcast
> > no frame-relay inverse-arp
> > isis hello-multiplier 5
> > isis hello-interval 1
> > End
> > Rack1R4#sh fram map
> > Serial0 (up): CLNS dlci 403(0x193,0x6430), static,
> > broadcast,
> > CISCO, status defined, active
> > Serial0 (up): ip 164.1.34.3 dlci 403(0x193,0x6430), static,
> > broadcast,
> > CISCO, status defined, active
> > Serial0 (up): ip 164.1.34.4 dlci 403(0x193,0x6430), static,
> > broadcast,
> > CISCO, status defined, active
> >
> > Rack1R4#sh clns nei
> >
> > System Id Interface SNPA State Holdtime Type
> > Protocol
> > 0001.0001.0003 Se0 DLCI 403 Up 4 L2
> > IS-IS
> >
> > Rack1R4#ping 164.1.34.3
> >
> > Type escape sequence to abort.
> > Sending 5, 100-byte ICMP Echos to 164.1.34.3, timeout is 2 seconds:
> > .
> > 00:15:45: ICMP: echo reply rcvd, src 164.1.34.3, dst 164.1.34.4.
> > 00:15:47: ICMP: echo reply rcvd, src 164.1.34.3, dst 164.1.34.4
> > 00:15:48: ICMP: echo reply rcvd, src 164.1.34.3, dst 164.1.34.4..
> > 00:15:50: ICMP: echo reply rcvd, src 164.1.34.3, dst 164.1.34.4.
> > Success rate is 0 percent (0/5)
> > Rack1R4#
> > 00:16:02: ICMP: echo reply rcvd, src 164.1.34.3, dst 164.1.34.4
> > Rack1R4#
> > 00:16:04: ICMP: echo reply rcvd, src 164.1.34.3, dst 164.1.34.4
> > Rack1R4#
> > 00:16:06: ICMP: echo reply rcvd, src 164.1.34.3, dst 164.1.34.
> >
> >
> ************************************************************************
> >
> > The same is happening on R5. IP traffic over the FR cloud is not
> > "working" at all.
> > Could somebody please tell me what is happening here. I am going
> > BONKERS.
> >
> > Many Thanks,
> > Mohit
> > P.S. I did rebooot all the routers also.
> >
> > _______________________________________________
> > ______________________
> >
> > ****** _/ ****** | Mohit Sharma
> > ***** _/ ***** | Network Implementation
> Manager(Agilent
> > Account)
> > **** _/_/_/ _/_/_/ **** | HP Operations
> > **** _/ _/ _/ _/ **** |
> > **** _/ _/ _/_/_/ **** |
> > ***** _/ ***** |
> > ****** ******* | email: mohit.sharma@hp.com
> > |
> > i n v e n t | Germany.
> > _____________________________________________________________________
> > "Choose a job you love, and you will never have to work a day in your
> > life." -Confucius
> >
> >
> _______________________________________________________________________
> > Please help support GroupStudy by purchasing your study materials
> from:
> > http://shop.groupstudy.com
> >
> > Subscription information may be found at:
> > http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Sat Jul 03 2004 - 19:40:39 GMT-3