RE: Frame-relay pvc-status and usage

Justin,

As long as FR does not have the option of adding those mappings later, i.e. you forgot to put no frame-relay inv on your interface, then you can safely ignore the other PVC status output. In the end, what shows up from 's fram map' is important.

-ryan

-----Original Message-----
From: nobody_at_groupstudy.com [mailto:nobody_at_groupstudy.com] On Behalf Of Justin Mitchell
Sent: Friday, October 30, 2009 6:25 AM
To: Cisco certification
Subject: Q: Frame-relay pvc-status and usage

It seems a common frame-relay requirement is that traffic only flow on the
required PVCs and that there are no dynamic map entries. Does the following
output meet those requirements? Mostly curious about the PVC STATUS =
ACTIVE.

I assume it says ACTIVE because both sides of the FRS are up and in theory
that is a viable DLCI, but it is UNUSED.

R2#sh fram map
Serial0/0.124 (up): ip 172.16.124.4 dlci 201(0xC9,0x3090), static,
              CISCO, status defined, active
Serial0/0.124 (up): ip 172.16.124.1 dlci 201(0xC9,0x3090), static,
              broadcast,
              CISCO, status defined, active
Serial0/0.124 (up): ip 172.16.124.2 dlci 201(0xC9,0x3090), static,
              CISCO, status defined, active
R2#sh fram pvc | i STAT
DLCI = 201, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE =
Serial0/0.124
DLCI = 203, DLCI USAGE = UNUSED, PVC STATUS = ACTIVE, INTERFACE = Serial0/0
DLCI = 204, DLCI USAGE = UNUSED, PVC STATUS = ACTIVE, INTERFACE = Serial0/0
DLCI = 205, DLCI USAGE = UNUSED, PVC STATUS = INACTIVE, INTERFACE =
Serial0/0
DLCI = 206, DLCI USAGE = UNUSED, PVC STATUS = INACTIVE, INTERFACE =
Serial0/0
R2#

-- 
Justin G. Mitchell
http://www.google.com/profiles/jgmitchell
Blogs and organic groups at http://www.ccie.net