From: Kevin Baumgartner (kbaumgar@xxxxxxxxx)
Date: Mon Jan 08 2001 - 22:21:41 GMT-3
I think that the mac-address you choose might be in the range of a
multicast address.
A better choose might have been 0005.0005.0005. or just 5.5.5 since it will
drop the
leading zero's.
Kevin
At 07:55 PM 1/8/01 -0500, Connary, Julie Ann wrote:
>Hi All,
>
>I fixed this by doing what Padhu did, I changed by node address. Why did I
>do this, I noticed when
>I was setting up some static routes as follows:
>
>ipx route default 6005.5555.5555.5555
>
>that it kept saying multicast was not allowed. THat triggered my brain so I
>changed all my ipx routing statements to be
>of the form:
>
>ipx routing 0000.0000.5555
>
>instead of
>
>ipx routing 5555.5555.5555
>
>That resolved both my static route problem and my frame-relay problem.
>
>Now I am assuming since the even addresses worked but the odd ones did not
>that the multicast bit
>must be the 1st bit in the 2nd octet? i.e.
>
>
>00000000 00000000 00000000 00000001
>
>since each hex number translates to 8 bits.
>
>any thoughts - I'm reading Caslow again.
>
>Julie ann
>
> >From: "Padhu (LFG)" <padhu@steinroe.com>
> >To: jconnary <jconnary@cisco.com>
> >Subject: RE: ipx weirdness over frame-relay
> >Date: Mon, 8 Jan 2001 15:01:44 -0600
> >X-Mailer: Internet Mail Service (5.5.2650.21)
> >
> >i changed mine to 0002.0002.0002 and works fine
> >
> >-----Original Message-----
> >From: Shaun Nicholson [mailto:Shaun.Nicholson@kp.org]
> >Sent: Monday, January 08, 2001 2:46 PM
> >To: jconnary
> >Cc: ccielab
> >Subject: Re: ipx weirdness over frame-relay
> >
> >
> >I know why and I can't explain it.
> >The router sees the IPX number 2222.2222.2222 and 5555.5555.5555 as well as
> >all other matching numbers as a multicast address I dont know why but try to
> >define a static sap and it wont let you. It says that its a multicast
> >address.
> >Use the address 2.2.2 or 5.5.5 as your IPX internal address and it will
> >work.
> >
> >Shaun
> >
> >
> >
> >
> >jconnary@cisco.com on 01/08/2001 03:39:00 PM
> >To: ccielab@groupstudy.com@Internet
> >cc: (bcc: Shaun Nicholson/MD/KAIPERM)
> >Subject: ipx weirdness over frame-relay
> >
> >Hi,
> >
> >has anyone seen the following IPX problem where you can ping from one
> >spoke to another spoke but not vice-versa?
> >It looks like R5 is treating the ipx ping from each spoke differently. Why?
> >I think it is the OS versions - but very wierd.
> >
> >
> >
> > S0 ipx network 200 on E0
> > /---------------------------R2 ipx routing 2222.2222.2222
> > /
> >R5 ipx routing 5555.5555.5555
> > \
> > \-------------------------------R3 ipx routing 3333.3333.3333
> > S0 ipx network 333 on Token 0
> >
> >
> >R5 is the frame hub.
> >R5 has no ipx split-horizon eigrp 1
> >R5 uses subinterfaces
> >R2 and R3 can see each others routes via EIGRP.
> >
> >Frame is ipx network 5130
> >
> >R2 can ping R3 on Frame network 5130
> >R2 can ping R3's token interface 333
> >R5 can ping R2 and R3 on Frame
> >R5 can ping R2 E0 and R3 token interfaces
> >
> >R3 CANNOT ping R2 frame or Ethernet 0 interface.
> >
> >A debug ipx packet on R5 shows the following when pinging from R3 to R2:
> >
> >IPX: Se0.1:5130.3333.3333.3333->5130.2222.2222.2222 ln=100 tc=00, rcvd,
> >tc:00->0
> >1
> >IPX: Se0.1:5130.3333.3333.3333->5130.2222.2222.2222 ln=100 tc=01,
> >gw=Se0.1:5130.
> >2222.2222.2222
> >IPX: Se0.1:5130.2222.2222.2222->5130.3333.3333.3333 ln=100 tc=00, rcvd
> >IPX: Se0.1:5130.2222.2222.2222->5130.3333.3333.3333 ln=100 tc=00, local
> >IPX: Se0.1:5130.3333.3333.3333->5130.2222.2222.2222 ln=100 tc=00, rcvd,
> >tc:00->0
> >1
> >IPX: Se0.1:5130.3333.3333.3333->5130.2222.2222.2222 ln=100 tc=01,
> >gw=Se0.1:5130.
> >2222.2222.2222
> >IPX: Se0.1:5130.2222.2222.2222->5130.3333.3333.3333 ln=100 tc=00, rcvd
> >IPX: Se0.1:5130.2222.2222.2222->5130.3333.3333.3333 ln=100 tc=00, local
> >IPX: Se0.1:5130.3333.3333.3333->5130.2222.2222.2222 ln=100 tc=00, rcvd,
> >tc:00->0
> >1
> >IPX: Se0.1:5130.3333.3333.3333->5130.2222.2222.2222 ln=100 tc=01,
> >gw=Se0.1:5130.
> >2222.2222.2222
> >IPX: Se0.1:5130.2222.2222.2222->5130.3333.3333.3333 ln=100 tc=00, rcvd
> >IPX: Se0.1:5130.2222.2222.2222->5130.3333.3333.3333 ln=100 tc=00, local
> >
> >IPX: Se0.1:5130.3333.3333.3333->5130.2222.2222.2222 ln=100 tc=00, rcvd,
> >tc:00->0
> >1
> >IPX: Se0.1:5130.3333.3333.3333->5130.2222.2222.2222 ln=100 tc=01,
> >gw=Se0.1:5130.
> >2222.2222.2222
> >IPX: Se0.1:5130.2222.2222.2222->5130.3333.3333.3333 ln=100 tc=00, rcvd
> >IPX: Se0.1:5130.2222.2222.2222->5130.3333.3333.3333 ln=100 tc=00, local
> >IPX: Se0.1:5130.3333.3333.3333->5130.2222.2222.2222 ln=100 tc=00, rcvd,
> >tc:00->0
> >1
> >IPX: Se0.1:5130.3333.3333.3333->5130.2222.2222.2222 ln=100 tc=01,
> >gw=Se0.1:5130.
> >2222.2222.2222
> >IPX: Se0.1:5130.2222.2222.2222->5130.3333.3333.3333 ln=100 tc=00, rcvd
> >IPX: Se0.1:5130.2222.2222.2222->5130.3333.3333.3333 ln=100 tc=00, local
> >
> >
> >Now look at a debug when I ping from R2 to R3 - notice how it looks like R5
> >is directly answering the pings:
> >
> >IPX: Se0.1:5130.2222.2222.2222->5130.3333.3333.3333 ln=100 tc=00, rcvd
> >IPX: Se0.1:5130.2222.2222.2222->5130.3333.3333.3333 ln=100 tc=00, local
> >IPX: local:5130.5555.5555.5555->5130.2222.2222.2222 ln=100 tc=00,
> >gw=Se0.1:5130.
> >2222.2222.2222
> >IPX: Se0.1:5130.2222.2222.2222->5130.3333.3333.3333 ln=100 tc=00, rcvd
> >IPX: Se0.1:5130.2222.2222.2222->5130.3333.3333.3333 ln=100 tc=00, local
> >IPX: local:5130.5555.5555.5555->5130.2222.2222.2222 ln=100 tc=00,
> >gw=Se0.1:5130.
> >2222.2222.2222
> >IPX: Se0.1:5130.2222.2222.2222->5130.3333.3333.3333 ln=100 tc=00, rcvd
> >IPX: Se0.1:5130.2222.2222.2222->5130.3333.3333.3333 ln=100 tc=00, local
> >IPX: local:5130.5555.5555.5555->5130.2222.2222.2222 ln=100 tc=00,
> >gw=Se0.1:5130.
> >2222.2222.2222
> >IPX: Se0.1:5130.2222.2222.2222->5130.3333.3333.3333 ln=100 tc=00, rcvd
> >IPX: Se0.1:5130.2222.2222.2222->5130.3333.3333.3333 ln=100 tc=00, local
> >IPX: local:5130.5555.5555.5555->5130.2222.2222.2222 ln=100 tc=00,
> >gw=Se0.1:5130.
> >2222.2222.2222
> >IPX: Se0.1:5130.2222.2222.2222->5130.3333.3333.3333 ln=100 tc=00, rcvd
> >IPX: Se0.1:5130.2222.2222.2222->5130.3333.3333.3333 ln=100 tc=00, local
> >IPX: local:5130.5555.5555.5555->5130.2222.2222.2222 ln=100 tc=00,
> >gw=Se0.1:5130.
> >2222.2222.2222
> >
> >
> >
> >R5 ipx setup: (System image file is "flash:c2500-ds-l.112-4.f1.bin", booted
> >via flash)
> >
> >ipx routing 5555.5555.5555
> >!
> >interface Serial0.1 multipoint
> > ip address 137.20.100.34 255.255.255.224
> > ipx network 5130
> > no ipx split-horizon eigrp 1
> > frame-relay map ipx 5130.2222.2222.2222 501 broadcast
> > frame-relay map ip 137.20.100.33 501 broadcast
> > frame-relay map ip 137.20.100.35 503 broadcast
> > frame-relay map ipx 5130.3333.3333.3333 503 broadcast
> >!
> >ipx router eigrp 1
> > network 5130
> > network 695
> >!
> >!
> >ipx router rip
> > no network 5130
> > no network 695
> >
> >
> >
> >R2 IPX setup: (System image file is "flash:/c2500-ds-l.112-4.f1.bin",
> >booted via flash)
> >
> >ipx routing 2222.2222.2222
> >interface Serial0
> > ip address 137.20.100.33 255.255.255.224
> > no ip mroute-cache
> > encapsulation frame-relay
> > ip ospf priority 0
> > keepalive 15
> > ipx network 5130
> > clock rate 2000000
> > frame-relay map ip 137.20.100.34 105 broadcast
> > frame-relay map ip 137.20.100.35 105 broadcast
> > frame-relay map ipx 5130.3333.3333.3333 105 broadcast
> > frame-relay map ipx 5130.5555.5555.5555 105 broadcast
> > frame-relay lmi-type ansi
> >
> >
> >ipx router eigrp 1
> > network 5130
> >!
> >!
> >ipx router rip
> > no network 5130
> >
> >
> >
> >R3 ipx setup: (System image file is "flash:c2500-ds56-l.112-21.bin",
> >booted via flash)
> >
> >ipx routing 3333.3333.3333
> >interface Serial0
> > ip address 137.20.100.35 255.255.255.224
> > encapsulation frame-relay
> > ip ospf priority 0
> > keepalive 15
> > ipx network 5130
> > no fair-queue
> > clockrate 2000000
> > frame-relay map ipx 5130.2222.2222.2222 305 broadcast
> > frame-relay map ip 137.20.100.33 305 broadcast
> > frame-relay map ip 137.20.100.34 305 broadcast
> > frame-relay map ipx 5130.5555.5555.5555 305 broadcast
> > frame-relay lmi-type ansi
> >
> >ipx router eigrp 1
> > network 5130
> >!
> >!
> >ipx router rip
> > no network 5130
> >
> >------------------------------------------------------------------------
> > Julie Ann Connary
> > | | Network Consulting Engineer
> > ||| ||| Federal Support Program
> > .|||||. .|||||. 13635 Dulles Technology Drive,
> >Herndon VA 20171
> > .:|||||||||:.:|||||||||:. Pager: 1-888-642-0551
> > c i s c o S y s t e m s Email: jconnary@cisco.com
> >
> >------------------------------------------------------------------------
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:27:24 GMT-3