1, last time pvc status changed 00:44:01 [output truncated] For every PVC, there is a paragraph that shows the status of the PVC and the interface on which it was discovered. Notice that PVCs that have been assigned to subinterfaces are shown to be active on those subinterfaces. All other PVCs are 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 interface 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.103 (up) : point-to-point dlci, dlci 103 (0x67,0x1870), broadcast status defined, active Serial0/0.102 (up) : point-to-point dlci, dlci 102 (0x66,0x1860), broadcast status defined, active If a PVC is not listed here, but is listed in the output of the show frame-relay pvc command, you have a configuration problem. Troubleshooting Frame Relay PART V Security and Firewalls This section covers security topics, including ACLs and authentication, as well as general firewall theory and configuration. Cisco PIX firewalls are used for examples. This section is composed of the following chapters: Chapter 23, Access Lists Chapter 24, Authentication in Cisco Devices Chapter 25, Firewall Theory Chapter 26, PIX Firewall Configuration CHAPTER 23 Access Lists The technical name for an acces