From: Scott Morris (smorris@ipexpert.com)
Date: Sat Nov 24 2007 - 22:23:25 ART
Well... Let's look at it a different way. You wouldn't receive any
unsolicited DLCI announcements. So one-way LMI can't be an issue. The full
status update is a DTE (client) driven event. So if you send it out but
can't receive a reply, it's moot. If you can't send it out but CAN receive
replies (which won't occur) then it's also moot. :)
The frame switch will only declare things deleted that it hears about. If
you as a router think you should get a response but cannot, then you'll set
things to inactive. If you can't hear/get anything and don't expect to,
you'll set it to deleted, or local, or static depending on circumstances.
Most people don't dive down to this level enough to truly care (grin). I'm
surprised that information was in a Security CCIE book anyway, but it may be
based on the older blueprint.
Scott
_____
From: Tarun Pahuja [mailto:pahujat@gmail.com]
Sent: Saturday, November 24, 2007 11:19 AM
To: smorris@ipexpert.com
Cc: Ron Lim; Cisco certification
Subject: Re: Frame Relay Status - deleted
I happen to know one of the authors of the Cisco Press book. I will pass on
the findings to him. Physical problems could be a lot of things(loose cable,
bad cable, cable with incorrect specifications, damaged cable, etc), all of
these could effect LMI propagation to the router from the FR switch causing
confusion between the FR switch and the router in terms of the DLCIs
configured on the connected interface on the switch. A simple reboot can not
demonstrate or take into account all physical problems.
But, we do get the point, if the DLCI configured on the router does not
exist on the connected interface on the FR switch, then the FR Switch will
simply declares that DCLI deleted.
Thanks,
Tarun
On 11/24/07, Scott Morris <smorris@ipexpert.com> wrote:
Don't always believe what you read.... Physical problems leading to
down/down will not show deleted but up/down (LMI problems) will.
R4(config)#do sh frame pvc
PVC Statistics for interface Serial0/0/0 (Frame Relay DTE)
Active Inactive Deleted Static
Local 9 0 0 0
Switched 0 0 0 0
Unused 0 0 0 0
R4(config)#int s0/0/0
R4(config-if)#frame map ip 150.100.24.6 <http://150.100.24.6/> 666 broad
R4(config-if)#exit
R4(config)#int s0/0/0.1 point-to-point
R4(config-subif)#frame int 777
R4(config-fr-dlci)#exit
R4(config-subif)#exit
R4(config)#do sh frame pvc | in 666|777
DLCI = 666, DLCI USAGE = LOCAL, PVC STATUS = DELETED, INTERFACE =
Serial0/0/0
DLCI = 777, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE =
Serial0/0/0.1
a couple minutes later....
R4(config)#do sh frame pvc | in STATUS
DLCI = 402, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0/0/0
DLCI = 405, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0/0/0
DLCI = 406, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0/0/0
DLCI = 412, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0/0/0
DLCI = 415, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0/0/0
DLCI = 416, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0/0/0
DLCI = 422, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0/0/0
DLCI = 425, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0/0/0
DLCI = 426, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0/0/0
DLCI = 666, DLCI USAGE = LOCAL, PVC STATUS = DELETED, INTERFACE =
Serial0/0/0
DLCI = 777, DLCI USAGE = LOCAL, PVC STATUS = DELETED, INTERFACE =
Serial0/0/0.1
Change LMI...
R4(config)#int s0/0/0
R4(config-if)#frame lmi-type ansi
Soon....
R4(config-if)#
*Nov 24 01:17:39.018: %LINEPROTO-5-UPDOWN: Line protocol on Interface
Serial0/0/0, changed state to down
Now look:
R4(config-if)#do sh frame pvc | in STATUS
DLCI = 402, DLCI USAGE = LOCAL, PVC STATUS = INACTIVE, INTERFACE =
Serial0/0/0
DLCI = 405, DLCI USAGE = LOCAL, PVC STATUS = INACTIVE, INTERFACE =
Serial0/0/0
DLCI = 406, DLCI USAGE = LOCAL, PVC STATUS = INACTIVE, INTERFACE =
Serial0/0/0
DLCI = 412, DLCI USAGE = LOCAL, PVC STATUS = INACTIVE, INTERFACE =
Serial0/0/0
DLCI = 415, DLCI USAGE = LOCAL, PVC STATUS = INACTIVE, INTERFACE =
Serial0/0/0
DLCI = 416, DLCI USAGE = LOCAL, PVC STATUS = INACTIVE, INTERFACE =
Serial0/0/0
DLCI = 422, DLCI USAGE = LOCAL, PVC STATUS = INACTIVE, INTERFACE =
Serial0/0/0
DLCI = 425, DLCI USAGE = LOCAL, PVC STATUS = INACTIVE, INTERFACE =
Serial0/0/0
DLCI = 426, DLCI USAGE = LOCAL, PVC STATUS = INACTIVE, INTERFACE =
Serial0/0/0
DLCI = 666, DLCI USAGE = LOCAL, PVC STATUS = DELETED, INTERFACE =
Serial0/0/0
DLCI = 777, DLCI USAGE = LOCAL, PVC STATUS = DELETED, INTERFACE =
Serial0/0/0.1
R4(config-if)#
It still remembers what was learned before... Only changes what is/was
working.
Reload and see what happens...
R4#sh frame pvc | in STATUS
DLCI = 666, DLCI USAGE = LOCAL, PVC STATUS = DELETED, INTERFACE =
Serial0/0/0
DLCI = 777, DLCI USAGE = LOCAL, PVC STATUS = DELETED, INTERFACE =
Serial0/0/0.1
R4#
No learned ones at all, but still DELETED state.
R4#sh int s0/0/0 | in up
Serial0/0/0 is up, line protocol is down
LMI enq sent 15, LMI stat recvd 0, LMI upd recvd 0, DTE LMI down
LMI enq recvd 0, LMI stat sent 0, LMI upd sent 0
DCD=up DSR=up DTR=up RTS=up CTS=up
R4#
Try changing things at physical now. If you can touch the frame switch,
just shut the interface down.
R4#
*Nov 24 01:26:14.891: %LINK-3-UPDOWN: Interface Serial0/0/0, changed state
to down
Now you'll have down/down.
R4#sh frame pvc | in STATUS
DLCI = 666, DLCI USAGE = LOCAL, PVC STATUS = DELETED, INTERFACE =
Serial0/0/0
DLCI = 777, DLCI USAGE = LOCAL, PVC STATUS = DELETED, INTERFACE =
Serial0/0/0.1
Nothing really changed, so try reloading...
R4#sh int s0/0/0 | in up|down
Serial0/0/0 is down, line protocol is down
LMI enq sent 0, LMI stat recvd 0, LMI upd recvd 0, DTE LMI down
LMI enq recvd 0, LMI stat sent 0, LMI upd sent 0
FR SVC disabled, LAPF state down
DCD=down DSR=down DTR=up RTS=up CTS=down
R4#
R4#sh frame pvc | in STATUS
DLCI = 666, DLCI USAGE = LOCAL, PVC STATUS = INACTIVE, INTERFACE =
Serial0/0/0
DLCI = 777, DLCI USAGE = LOCAL, PVC STATUS = INACTIVE, INTERFACE =
Serial0/0/0.1
R4#
So physical problems will yield INACTIVE. LMI problems will yield DELETED.
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 <http://www.ipexpert.com/>
_____
From: Tarun Pahuja [mailto:pahujat@gmail.com]
Sent: Saturday, November 24, 2007 9:28 AM
To: smorris@ipexpert.com
Cc: Ron Lim; Cisco certification
Subject: Re: Frame Relay Status - deleted
I am referring to Cisco CCIE security Practical studies book, Page 124:
http://books.google.com/books?id=eskSfkT3QMkC
<http://books.google.com/books?id=eskSfkT3QMkC&pg=PA124&lpg=PA124&dq=pvc+act
ive+inactive+deleted&source=web&ots=QYkn_oTBUh&sig=Okj7F9FyhAXhiWoJt5aINnUy0
ec#PPA124,M1>
&pg=PA124&lpg=PA124&dq=pvc+active+inactive+deleted&source=web&ots=QYkn_oTBUh
&sig=Okj7F9FyhAXhiWoJt5aINnUy0ec#PPA124,M1
Thanks,
Tarun
On 11/24/07, Scott Morris <smorris@ipexpert.com
<mailto:smorris@ipexpert.com> > wrote:
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 <http://www.ipexpert.com/>
-----Original Message-----
From: nobody@groupstudy.com <mailto:nobody@groupstudy.com> [mailto:
<mailto:nobody@groupstudy.com> 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 < <mailto:gottobeccie@gmail.com>
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 <http://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 <http://131.1.12.1/> 255.255.255.0
<http://255.255.255.0/>
> encapsulation frame-relay
> frame-relay map ip 131.1.12.2 <http://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 <http://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 <http://131.1.12.2/> 255.255.255.0
<http://255.255.255.0/>
> encapsulation frame-relay
> frame-relay map ip 131.1.12.1 <http://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
<http://www.groupstudy.com/list/CCIELab.html>
This archive was generated by hypermail 2.1.4 : Sat Dec 01 2007 - 06:37:31 ART