shown to be associated with the physical interfaces on which they were found. If a particular PVC is not shown here, you're probably not receiving LMI for that VC. Each entry shows a status, which can be one of the following: Active This status indicates that the PVC is up end to end and is functioning normally. Inactive This status indicates that a PVC is defined by the telecom switch, but you do not have an active mapping for it. If this is the PVC you're trying to use, you probably forgot to map it or mapped it incorrectly. Deleted This status indicates that you have a mapping active, but the PVC you've mapped to doesn't exist. An incorrect mapping may cause this problem. Static This status indicates that no keepalive is configured on the Frame Relay in- terface of the router. Is the PVC mapped to an interface? The show frame-relay map command shows a very concise report of the VCs that are mapped to interfaces: Router-A#sho frame map Serial0/0.10 (up) : point-to-point dlci, dlci 103 (0x67,0x1870), broadcast status defined, active Chapter 23: Frame Relay Serial0/0.102 (up) : point-to-point dlci, dlci 102 (0x66,0x1860), broadcast status defined, active If a PVC is not listed here, but it is listed in the output of the show frame-relay pvc command, you have a configuration problem. Troubleshooting Frame Relay CHAPTER 24 In my experience, there are two levels of involvement with MPLS (Multiprotocol Label Switching) networks. First, there are people who design and maintain the MPLS net- works themselves. These people generally work for service providers such as AT&T, British Telecom, and the like. Second are the people who need to use MPLS in their corporate WANs. This chapter is written for the latter category-the people who need to employ an MPLS solution in their networks, not the people who actually design them. Why? Because the target audience for this book is composed mostly of the people who work with corporate networks on a daily basis. My goal is not to help you build an MPLS network from the ground up, i