d received on the Frame Relay interfaces. As always, be very careful when issuing debug commands on production devices. These commands can cause large or busy routers to stop functioning due to the increased CPU load. When you run the debug frame-relay lmi command, a small status message (which is not of much use) is sent every 10 seconds, and a summary of all the VCs present on the link is sent every 30 seconds. You'll recognize this message by the ob- vious inclusion of lines beginning with PVC or SVC: Router-A#debug frame lmi Frame Relay LMI debugging is on Displaying all Frame Relay LMI data Router-A# 00:33:05: Serial0/0(out) StEnq, myseq 197, yourseen 196, DTE up 00:33:05: datagramstart = 0x3CE9B74, datagramsize = 13 00:33:05: FR encap = 0xFCF10309 00:33:05: 00 75 01 01 01 03 02 C5 C4 00:33:05: Chapter 23: Frame Relay 00:33:05: Serial0/0(in): Status, myseq 197, pak size 13 00:33:05: RT IE 1, length 1, type 1 00:33:05: KA IE 3, length 2, yourseq 197, myseq 197 00:33:15: Serialo/o(out) StEnq, myseq 198, yourseen 197, DTE up 00:33:15: datagramstart = 0x3CEA1B4, datagramsize = 13 00:33:15: FR encap = 0xFCF10309 00:33:15: 00 75 01 01 00 03 02 C6 C5 00:33:15: 00:33:15: Serialo/o(in): Status, myseq 198, pak size 53 00:33:15: RT IE 1, length 1, type 0 00:33:15: KA IE 3, length 2, yourseq 198, myseq 198 00:33:15: PVC IE 0x7 , length 0x6 , dlci 102, status 0x2 , bw 0 00:33:15: PVC IE 0x7 , length 0x6 dlci 103, status 0x2 , bw 0 00:33:15: PVC IE 0x7 , length 0x6 dlci 104, status 0x0 bw 0 00:33:15: PVC IE 0x7 , length 0x6 dlci 105, status 0x0 bw 0 00:33:15: PVC IE 0x7 , length 0x6 dlci 106, status 0x0 bw 0 00:33:25: Serial0/0(out): StEnq, myseq 199, yourseen 198, DTE up 00:33:25: datagramstart = 0x3CEA574, datagramsize = 13 00:33:25: FR encap = 0xFCF10309 00:33:25: 00 75 01 01 01 03 02 C7 C6 In this example, the Frame Relay switch is advertising five PVCs. The status of each is 0x0 or 0x2. 0x0 means that the VC is configured on the Frame Relay switch, but is not active. This occurs most commonly because the far-end de- 