From: Scott Morris (smorris@ipexpert.com)
Date: Fri Nov 23 2007 - 22:31:00 ART
Now, I could be remembering things wrong (I don't have routers in front of
me at the moment) but I'm pretty sure that if you have a physical problem or
not receiving LMI you get an INACTIVE status because it can't be
verified.... If you get a link up/up but no LMI, you'll get LOCAL or STATIC
(part of how we do back-to-back frame).
But you are correct for the misconfiguration part, as noted before, that if
you don't match the frame switch things will be bad.
HTH,
Scott Morris, CCIE4 (R&S/ISP-Dial/Security/Service Provider) #4713, JNCIE-M
#153, JNCIS-ER, CISSP, et al.
CCSI/JNCI-M/JNCI-ER
VP - Technical Training - IPexpert, Inc.
IPexpert Sr. Technical Instructor
A Cisco Learning Partner - We Accept Learning Credits!
Telephone: +1.810.326.1444
Fax: +1.810.454.0130
http://www.ipexpert.com
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Tarun Pahuja
Sent: Friday, November 23, 2007 5:14 PM
To: Ron Lim
Cc: Cisco certification
Subject: Re: Frame Relay Status - deleted
Ron,
I will list all possible states for a PVC in frame-relay and what
they mean:
Active : Your PVC is active and can pass traffic.
Inactive: Your local connection to FR is operational,but the remote router's
connection is not operational
Deleted: You are not receiving LMIs,physical layer encountered a problem or
Misconfiguration(mismatch of DLCI values between the switch and the router).
HTH,
Tarun
On 11/23/07, Ron Lim <gottobeccie@gmail.com> wrote:
>
> Hi all,
>
> I kept encountering frame relay status being deleted on serial interface.
>
> R1 <-> FR SW <-> R2
>
> R1
> ===
> R1#sh frame map
> Serial0/0/0 (up): ip 131.1.12.2 dlci 102(0x66,0x1860), static,
> broadcast,
> CISCO, status deleted
> R1#sh run int s0/0/0
> Building configuration...
>
> Current configuration : 166 bytes
> !
> interface Serial0/0/0
> ip address 131.1.12.1 255.255.255.0
> encapsulation frame-relay
> frame-relay map ip 131.1.12.2 102 broadcast no frame-relay inverse-arp
> end
>
> R1#sh ver | inc Ver
> Cisco IOS Software, 2800 Software (C2800NM-ADVENTERPRISEK9_SNA-M),
> Version 12.4(10a), RELEASE SOFTWARE (fc2)
> ROM: System Bootstrap, Version 12.4(1r) [hqluong 1r], RELEASE SOFTWARE
> (fc1)
> R1#
>
> FR SW
> ======
> FR_SW#sh ver | inc Ver
> IOS (tm) C2600 Software (C2600-I-M), Version 12.2(28a), RELEASE
> SOFTWARE
> (fc2)
> ROM: System Bootstrap, Version 11.3(2)XA3, PLATFORM SPECIFIC RELEASE
> SOFTWARE (fc1)
> ROM: C2600 Software (C2600-I-M), Version 12.2(28a), RELEASE SOFTWARE
> (fc2)
> X.25 software, Version 3.0.0.
> FR_SW#
>
> R2
> ===
> R2#sh frame map
> Serial0/0/0 (up): ip 131.1.12.1 dlci 201(0xC9,0x3090), static,
> broadcast,
> CISCO, status deleted
> R2#sh run int s0/0/0
> Building configuration...
>
> Current configuration : 166 bytes
> !
> interface Serial0/0/0
> ip address 131.1.12.2 255.255.255.0
> encapsulation frame-relay
> frame-relay map ip 131.1.12.1 201 broadcast no frame-relay inverse-arp
> end
>
> R2#sh ver | inc Ver
> Cisco IOS Software, 2800 Software (C2800NM-ADVENTERPRISEK9_SNA-M),
> Version 12.4(10a), RELEASE SOFTWARE (fc2)
> ROM: System Bootstrap, Version 12.3(8r)T7, RELEASE SOFTWARE (fc1) R2#
>
> How could I resolve this issue?
>
> Thank you.
>
> Regards,
> Ron
>
> ______________________________________________________________________
> _ Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Sat Dec 01 2007 - 06:37:31 ART