From: Darby Weaver (darbyweaver@yahoo.com)
Date: Sat Apr 21 2007 - 23:39:26 ART
Of course, you see this and cannot get 0.0.0.0
mapping.
Rack01R1(config-if)#do sh fram map
Serial1/0 (down): ip 1.1.1.2 dlci 102(0x66,0x1860),
static,
broadcast,
CISCO, status defined, inactive
Rack01R1(config-if)#
*Apr 22 02:36:24.175: Serial0/0/0(i): dlci
115(0x1C31), pkt type 0x2000, datagramsize 324
*Apr 22 02:36:24.215: Serial0/0/0(i): dlci
105(0x1891), pkt type 0x2000, datagramsize 324
Rack01R1(config-if)#
*Apr 22 02:36:26.807: Serial0/0/0(i): dlci
115(0x1C31), NLPID 0x3CC(IP), datagramsize 332
*Apr 22 02:36:26.847: Serial0/0/0(i): dlci
105(0x1891), NLPID 0x3CC(IP), datagramsize 332
*Apr 22 02:36:26.891: Serial0/0/0(i): dlci
105(0x1891), pkt type 0x800, datagramsize 332
Rack01R1(config-if)#do sh debug
Frame Relay:
Frame Relay packet debugging is on
Condition 1: interface Se0/0/0 (1 flags triggered)
Flags: Se0/0/0
Rack01R1(config-if)#do sh
*Apr 22 02:36:43.707: Serial0/0/0(i): dlci
115(0x1C31), NLPID 0x3CC(IP), datagramsize 332
*Apr 22 02:36:43.747: Serial0/0/0(i): dlci
105(0x1891), NLPID 0x3CC(IP), datagramsize 332
*Apr 22 02:36:43.791: Serial0/0/0(i): dlci
105(0x1891), pkt type 0x800, datagramsize 332
Rack01R1(config-if)#do sh run int s0/0/0
Building configuration...
Current configuration : 118 bytes
!
interface Serial0/0/0
ip address 1.1.1.1 255.255.255.0
encapsulation frame-relay
frame-relay lmi-type cisco
end
Rack01R1(config-if)#do sh fram map
*Apr 22 02:37:00.815: Serial0/0/0(o): dlci
115(0x1C31), pkt encaps 0x0300 0x8000 0x0000 0x806
(ARP), datagramsize 34
*Apr 22 02:37:00.815: FR: Sending INARP Request on
interface Serial0/0/0 dlci 115 for link 7(IP)
*Apr 22 02:37:00.815: Serial0/0/0(o): dlci
105(0x1891), pkt encaps 0x0300 0x8000 0x0000 0x806
(ARP), datagramsize 34
*Apr 22 02:37:00.815: FR: Sending INARP Request on
interface Serial0/0/0 dlci 105 for link 7(IP)
*Apr 22 02:37:00.867: broadcast dequeue
*Apr 22 02:37:00.867: Serial0/0/0(o):Pkt sent on dlci
115(0x1C31), pkt encaps 0x300 0x8000 0x0 0x806
(ARP), datagramsize 34
*Apr 22 02:37:00.867: broadcast dequeue
Rack01R1(config-if)#do sh fram map
Serial1/0 (down): ip 1.1.1.2 dlci 102(0x66,0x1860),
static,
broadcast,
CISCO, status defined, inactive
Rack01R1(config-if)#
*Apr 22 02:37:00.867: Serial0/0/0(o):Pkt sent on dlci
105(0x1891), pkt encaps 0x300 0x8000 0x0 0x806
(ARP), datagramsize 34
*Apr 22 02:37:00.887: Serial0/0/0(i): dlci
115(0x1C31), pkt encaps 0x0300 0x8000 0x0000 0x806
(ARP), datagramsize 34
*Apr 22 02:37:00.887: Serial0/0/0: frame relay INARP
received
*Apr 22 02:37:00.891: Serial0/0/0(i): dlci
105(0x1891), pkt encaps 0x0300 0x8000 0x0000 0x806
(ARP), datagramsize 34
*Apr 22 02:37:00.895: Serial0/0/0: frame relay INARP
received
Rack01R1(config-if)#
*Apr 22 02:37:03.731: Serial0/0/0(i): dlci
115(0x1C31), pkt encaps 0x0300 0x8000 0x0000 0x806
(ARP), datagramsize 30
*Apr 22 02:37:03.731: Serial0/0/0: frame relay INARP
received
*Apr 22 02:37:03.811: Serial0/0/0(i): dlci
115(0x1C31), NLPID 0x3CC(IP), datagramsize 332
*Apr 22 02:37:03.851: Serial0/0/0(i): dlci
105(0x1891), NLPID 0x3CC(IP), datagramsize 332
*Apr 22 02:37:03.903: Serial0/0/0(i): dlci
105(0x1891), pkt type 0x800, datagramsize 332
Rack01R1(config-if)#
*Apr 22 02:37:20.703: Serial0/0/0(i): dlci
115(0x1C31), NLPID 0x3CC(IP), datagramsize 332
*Apr 22 02:37:20.747: Serial0/0/0(i): dlci
105(0x1891), NLPID 0x3CC(IP), datagramsize 332
*Apr 22 02:37:20.791: Serial0/0/0(i): dlci
105(0x1891), pkt type 0x800, datagramsize 332
Rack01R1(config-if)#
*Apr 22 02:37:24.167: Serial0/0/0(i): dlci
115(0x1C31), pkt type 0x2000, datagramsize 324
*Apr 22 02:37:24.207: Serial0/0/0(i): dlci
105(0x1891), pkt type 0x2000, datagramsize 324
Now my router is sending and receiving inarp requests
and yet when I perform a sh fram map - I'm not seeing
the inverse arp mappings.
Hmmm...
Now I guess I'll shut the int. Disable Frame-relay
and start over and see what is happening.
I thought I would get my inverse arp mappings.
--- "Todd, Douglas M." <DTODD@PARTNERS.ORG> wrote:
> UGH!!! This is driving me nuts....
>
> Rack1R1(config)#default int s1/0
> Building configuration...
> % Invalid input detected at '^' marker.
> %Cannot remove PVC as being referenced by map
> statement
> % Error(s) seen setting interface Serial1/0 to it's
> default config
> Rack1R1(config)#
>
> pasted the config back on:
>
> in a 60 seconds the 0.0.0.0's come back again.
>
> NEXT:
> Shut the interface:
> removed the config
> pasted the config
> no sh the interface
> they are back again...
>
> Even after a reload they come back.
>
> DMT
>
>
>
>
>
>
>
> -----Original Message-----
> From: John Jones [mailto:acer0001@gmail.com]
> Sent: Sat 4/21/2007 1:22 PM
> To: Todd, Douglas M.
> Cc: Victor Cappuccio; ccielab@groupstudy.com
> Subject: Re: Frame-relay issues:
>
> Shut down the interface, change the encapsulation to
> another protocol, say
> PPP, bring the interface up again. This should clear
> all mappings. Shut down
> interface again and specify encap frame. Setup your
> fr maps again, save
> to nvram, and then bring up the interface; your
> mapping should be correct.
> If not, a reboot of the router is needed to remove
> the mappings to 0.0.0.0.
>
> HTH,
>
> John
>
>
> On 4/21/07, Todd, Douglas M. <DTODD@partners.org>
> wrote:
> >
> > Thanks-
> >
> > I have already disabled inverse arp on the
> physical interfaces. Seems the
> > router is still building a table for those DLCIs
> which are not used in
> > this lab.
> > I am getting ospf/pim adjs from routers which are
> in different networks
> > even
> > with inverse arp disabled on the physical
> interfaces.
> >
> > DMT
> >
> >
> >
> > -----Original Message-----
> > From: Victor Cappuccio
> [mailto:victor@ccbootcamp.com]
> > Sent: Sat 4/21/2007 10:45 AM
> > To: Todd, Douglas M.; ccielab@groupstudy.com
> > Subject: RE: Frame-relay issues:
> >
> >
> > Good Point of reference
> >
> >
>
http://www.groupstudy.com/archives/ccielab/200503/msg00398.html
> >
> >
> >
> > thanks,
> > Victor Cappuccio.-
> > Network Learning Inc - A Cisco Sponsored
> Organization (SO) YES! We take
> > Cisco Learning credits!
> > victor@ccbootcamp.com
> > http://www.ccbootcamp.com (Cisco Training and
> Rental Racks)
> > http://www.ccbootcamp.com/groupstudy.html
> (groupstudy member discounts!)
> > Voice: 702-968-5100
> > FAX: 702-446-8012
> >
> >
> >
> >
> > -----Original Message-----
> > From: nobody@groupstudy.com on behalf of Todd,
> Douglas M.
> > Sent: Sat 4/21/2007 7:35
> > To: ccielab@groupstudy.com
> > Subject: FW: Frame-relay issues:
> >
> > All:
> >
> > I am getting these bogus frame-relay maps on 2
> routers. I have reloaded
> > the
> > router w/the interfaces shutdown with the
> configuration below. It's like
> > frame-relay arp is "kind" of working when it's not
> enabled at all on the
> > interface.
> >
> > Ideas?
> >
> > Thanks..
> > Rack1R1#sh run int s1/0
> > Building configuration...
> >
> > Current configuration : 321 bytes
> > !
> > interface Serial1/0
> > ip address 136.1.15.1 255.255.255.0
> > ip pim sparse-dense-mode
> > encapsulation frame-relay
> > ip ospf authentication message-digest
> > ip ospf message-digest-key 1 md5 CISCO
> > ip ospf network point-to-point
> > no arp frame-relay
> > frame-relay map ip 136.1.15.5 105 broadcast
> > no frame-relay inverse-arp
> > end
> > Rack1R1#sh frame-relay map
> > Serial1/0 (up): ip 0.0.0.0 dlci 102(0x66,0x1860)
> > broadcast,
> > CISCO, status defined, active
> > Serial1/0 (up): ip 0.0.0.0 dlci 103(0x67,0x1870)
> > broadcast,
> > CISCO, status defined, inactive
> > Serial1/0 (up): ip 0.0.0.0 dlci 104(0x68,0x1880)
> > broadcast,
> > CISCO, status defined, active
> > Serial1/0 (up): ip 136.1.15.5 dlci
> 105(0x69,0x1890), static,
> > broadcast,
> > CISCO, status defined, active
> > Serial1/0 (up): ip 0.0.0.0 dlci 113(0x71,0x1C10)
> > broadcast,
> > CISCO, status defined, inactive
> > Rack1R1#
> >
> >
> >
> >
> >
> > The information transmitted in this electronic
> communication is intended
> > only
> > for the person or entity to whom it is addressed
> and may contain
> > confidential
> > and/or privileged material. Any review,
> retransmission, dissemination or
> > other
> > use of or taking of any action in reliance upon
> this information by
> > persons or
> > entities other than the intended recipient is
> prohibited. If you received
> > this
> > information in error, please contact the
> Compliance HelpLine at
> > 800-856-1983 and
> > properly dispose of this information.
> >
> >
> >
> >
> >
> >
> >
> > The information transmitted in this electronic
> communication is intended
> > only
> > for the person or entity to whom it is addressed
> and may contain
> > confidential
> > and/or privileged material. Any review,
> retransmission, dissemination or
> > other
> > use of or taking of any action in reliance upon
> this information by
> > persons or
> > entities other than the intended recipient is
> prohibited. If you received
> > this
> > information in error, please contact the
> Compliance HelpLine at
> > 800-856-1983 and
> > properly dispose of this information.
> >
> >
>
This archive was generated by hypermail 2.1.4 : Tue May 01 2007 - 08:28:36 ART