building cisco remote access networks phần 6 ppsx

Figure 7.15 Continued.!interface Serial2.3 point-to-pointdescription frame relay to router 1 ip unnumbered Ethernet0 no ip route-cacheframe-relay interface-dlci 101 no shutdown !interfac

Trang 1

Figure 7.15 Continued.

!interface Serial2.3 point-to-pointdescription frame relay to router 1

ip unnumbered Ethernet0

no ip route-cacheframe-relay interface-dlci 101

no shutdown

!interface Serial3

no ip address

no ip route-cache

no ip mroute-cacheshutdown

!interface BRI0

no ip address

no ip route-cache

no ip mroute-cacheshutdown

!router eigrp 100network 10.0.0.0

!

ip classless

!

!banner motd ^CEstablish a Frame Relay PVCs on three routers and controltraffic flow - Router_2

^C

!line con 0exec-timeout 0 0

www.syngress.com

Continued

Trang 2

service timestamps debug uptime

service timestamps log uptime

Trang 3

!interface Serial2.4 point-to-pointdescription frame relay to router a

ip unnumbered Ethernet0

no ip route-cacheframe-relay interface-dlci 103

no shutdown

!router eigrp 100network 10.0.0.0

!

ip classless

!

!banner motd ^CEstablish a Frame Relay PVCs on three routers and controltraffic flow - Router_3

^C

!line con 0exec-timeout 0 0password xxxxlogin

line aux 0password xxxxlogin

transport input allline vty 0 4

Continued

Trang 4

Verifying Traffic Shaping

The functioning of traffic shaping configurations can be monitored through various show and debug commands These are:

■ show frame-relay pvc

■ show frame-relay lmi

■ show interface

■ show ip route

■ show traffic shap

■ show frame-relay map

■ debug frame-relay lmi Let’s look at the related output that each of these commands produces

Router1#show frame-relay pvc

PVC Statistics for interface Serial2 (Frame Relay DTE)

DLCI = 100, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE =

Serial2.1

input pkts 21 output pkts 24 in bytes 2014 out bytes 2066 dropped pkts 0 in FECN pkts 0

in BECN pkts 0 out FECN pkts 0 out BECN pkts 0

Æ shows BECN packets count

in DE pkts 0 out DE pkts 0 out bcast pkts 22 out bcast bytes 1838 pvc create time 00:12:17, last time pvc status changed 00:01:19DLCI = 102, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE =

Serial2.2

Trang 5

in BECN pkts 0 out FECN pkts 0 out BECN pkts 0

in DE pkts 0 out DE pkts 0 out bcast pkts 12 out bcast bytes 1198 pvc create time 00:11:03, last time pvc status changed 00:00:40

Router1#show frame-relay traffic

Frame Relay statistics:

ARP requests sent 0, ARP replies sent 0ARP request recvd 0, ARP replies recvd

Router1#sh frame lmi

LMI Statistics for interface Serial2 (Frame Relay DTE) LMI TYPE = ANSIInvalid Unnumbered info 0 Invalid Prot Disc 0

Invalid dummy Call Ref 0 Invalid Msg Type 0Invalid Status Message 0 Invalid Lock Shift 0Invalid Information ID 0 Invalid Report IE Len 0Invalid Report Request 0 Invalid Keep IE Len 0Num Status Enq Sent 14 Num Status msgs Rcvd 14Num Update Status Rcvd 0 Num Status Timeouts 0

Router1#show interfaces s2

Serial2 is up, line protocol is up Hardware is CD2430 in sync modeMTU 1500 bytes, BW 115 Kbit, DLY 20000 usec, rely 255/255, load 1/255Encapsulation FRAME-RELAY, loopback not set, keepalive set (10 sec)LMI enq sent 15, LMI stat recvd 15, LMI upd recvd 0, DTE LMI upLMI enq recvd 0, LMI stat sent 0, LMI upd sent 0

LMI DLCI 0 LMI type is ANSI Annex D frame relay DTE

FR SVC disabled, LAPF state downBroadcast queue 0/64, broadcasts sent/dropped 52/0, interfacebroadcasts 46

Last input 00:00:00, output 00:00:03, output hang never

Trang 6

Last clearing of “show interface” counters neverInput queue: 0/75/0 (size/max/drops); Total output drops: 0Queueing strategy: weighted fair

Output queue: 0/1000/64/0 (size/max total/threshold/drops) Conversations 0/1/256 (active/max active/max total)Reserved Conversations 0/0 (allocated/max allocated)

5 minute input rate 0 bits/sec, 0 packets/sec

5 minute output rate 0 bits/sec, 0 packets/sec

66 packets input, 4724 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants, 0 throttles

0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort

75 packets output, 5758 bytes, 0 underruns

0 output errors, 0 collisions, 5 interface resets

0 output buffer failures, 0 output buffers swapped out

2 carrier transitionsDCD=up DSR=up DTR=up RTS=up CTS=up

i ISIS, L1 ISIS level1, L2 ISIS level2, * candidate default

-U - per-user static route, o - ODR

Gateway of last resort is not set

10.0.0.0/24 is subnetted, 5 subnets

D 10.2.2.0 [90/2195456] via 10.140.1.1, 00:03:45, Serial1

D 10.3.3.0 [90/2195456] via 10.140.2.2, 00:03:46, Serial0

C 10.1.1.0 is directly connected, Ethernet0

C 10.140.2.0 is directly connected, Serial0

C 10.140.1.0 is directly connected, Serial1

Trang 7

Router1#sh frame-relay traffic Frame Relay statistics:

ARP requests sent 0, ARP replies sent 0ARP request recvd 0, ARP replies recvd 0

Router1# show traffic-shape Æ shows traffic shaping related statistics

Access Target Byte Sustain Excess Interval

DLCI = 100, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE =Serial2.1

in DE pkts 0 out DE pkts 0 out bcast pkts 215 out bcast bytes 17200

Shaping adapts to BECN Æ shows what type of traffic shaping used

pvc create time 00:26:06, last time pvc status changed 00:15:07

Trang 8

====================

Router1#debug frame-relay lmi

Frame Relay LMI debugging is on

Displaying all Frame Relay LMI data

05:37:40: Serial2(out): StEnq, myseq 108, yourseen 107, DTE up

05:37:40: KA IE 3, length 2, yourseq 108, myseq 108

05:37:51: Serial2(out): StEnq, myseq 109, yourseen 108, DTE up

Trang 9

05:38:00: 00 75 95 01 01 00 03 02 6E 6D 05:38:00:

05:38:00: Serial2(in): Status, myseq 11005:38:00: RT IE 1, length 1, type 005:38:00: KA IE 3, length 2, yourseq 110, myseq 11005:38:00: PVC IE 0x7 , length 0x3 , dlci 100, status 0x2 05:38:00: PVC IE 0x7 , length 0x3 , dlci 102, status 0x2 ip05:38:10: Serial2(out): StEnq, myseq 111, yourseen 110, DTE up05:38:10: datagramstart = 0x647D20, datagramsize = 14

05:38:10: FR encap = 0x0001030805:38:10: 00 75 95 01 01 01 03 02 6F 6E 05:38:42: Serial2.2(o):Pkt sent on dlci 102(0x1861), pkt type0x800(IP), datagramsize 64

05:38:43: Serial2.1: broadcast search05:38:43: Serial2.1(o): dlci 100(0x1841), pkt type 0x800(IP),datagramsize 64

05:38:43: broadcast dequeue05:38:43: Serial2.1(o):Pkt sent on dlci 100(0x1841), pkt type0x800(IP), datagramsize 64

05:38:46: Serial2(i): dlci 100(0x1841), pkt type 0x800, datagramsize 6405:38:46: Serial2.1: Broadcast on DLCI 100 link 65(CDP)

05:38:46: Serial2.1(o): dlci 100(0x1841), pkt type 0x2000(CDP),datagramsize 279

05:38:46: broadcast dequeue05:38:46: Serial2.1(o):Pkt sent on dlci 100(0x1841), pkt type0x2000(CDP), datagramsize 279

05:38:46: Serial2(i): dlci 102(0x1861), pkt type 0x800, datagramsize 6405:38:46: Serial2.2: broadcast search

05:38:46: Serial2.2(o): dlci 102(0x1861), pkt type 0x800(IP),datagramsize 64

05:38:46: broadcast dequeue05:38:46: Serial2.2(o):Pkt sent on dlci 102(0x1861), pkt type0x800(IP), datagramsize 64

05:38:47: Serial2.1: broadcast search05:38:47: Serial2.1(o): dlci 100(0x1841), pkt type 0x800(IP),datagramsize 64

Trang 10

05:38:47: Serial2(i): dlci 100(0x1841), pkt type 0x2000, datagramsize279

Ethernet0 is up, line protocol is up

Hardware is Lance, address is 0010.7be8.7e84 (bia 0010.7be8.7e84)Internet address is 10.1.1.3/24

MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec, rely 255/255, load1/255

Encapsulation ARPA, loopback not set, keepalive set (10 sec)ARP type: ARPA, ARP Timeout 04:00:00

Last input never, output 00:00:03, output hang neverLast clearing of “show interface” counters neverQueueing strategy: fifo

Output queue 0/40, 0 drops; input queue 0/75, 0 drops

0 input packets with dribble condition detected

0 babbles, 0 late collision, 0 deferred

0 lost carrier, 0 no carrier

================

Serial2 is up, line protocol is up

Hardware is CD2430 in sync modeMTU 1500 bytes, BW 115 Kbit, DLY 20000 usec, rely 255/255, load 1/255

Trang 11

Encapsulation FRAME-RELAY, loopback not set, keepalive set (10 sec)

LMI enq sent 138, LMI stat recvd 138, LMI upd recvd 0, DTE LMI upLMI enq recvd 0, LMI stat sent 0, LMI upd sent 0

LMI DLCI 0 LMI type is ANSI Annex D frame relay DTE

FR SVC disabled, LAPF state downBroadcast queue 0/64, broadcasts sent/dropped 623/0, interfacebroadcasts 577

Last input 00:00:01, output 00:00:00, output hang neverLast clearing of “show interface” counters never

Input queue: 0/75/0 (size/max/drops); Total output drops: 0Queueing strategy: weighted fair

2 carrier transitionsDCD=up DSR=up DTR=up RTS=up CTS=upSerial2.1 is up, line protocol is up Hardware is CD2430 in sync modeDescription: frame relay to router bInterface is unnumbered Using address of Ethernet0 (10.1.1.3)MTU 1500 bytes, BW 115 Kbit, DLY 20000 usec, rely 255/255, load 1/255Encapsulation FRAME-RELAY

Serial2.2 is up, line protocol is up Hardware is CD2430 in sync modeDescription: frame relay to router cInterface is unnumbered Using address of Ethernet0 (10.1.1.3)MTU 1500 bytes, BW 115 Kbit, DLY 20000 usec, rely 255/255, load 1/255

Trang 12

Encapsulation FRAME-RELAYSerial3 is administratively down, line protocol is down

Hardware is CD2430 in sync modeMTU 1500 bytes, BW 115 Kbit, DLY 20000 usec, rely 255/255, load 1/255Encapsulation HDLC, loopback not set, keepalive set (10 sec)

Last input never, output never, output hang neverLast clearing of “show interface” counters neverInput queue: 0/75/0 (size/max/drops); Total output drops: 0Queueing strategy: weighted fair

0 carrier transitionsDCD=down DSR=down DTR=down RTS=down CTS=down

Router1#show frame-relay lmi

LMI Statistics for interface Serial2 (Frame Relay DTE) LMI TYPE = ANSIInvalid Unnumbered info 0 Invalid Prot Disc 0

Invalid dummy Call Ref 0 Invalid Msg Type 0Invalid Status Message 0 Invalid Lock Shift 0Invalid Information ID 0 Invalid Report IE Len 0Invalid Report Request 0 Invalid Keep IE Len 0Num Status Enq Sent 139 Num Status msgs Rcvd 139Num Update Status Rcvd 0 Num Status Timeouts 0

Router1#sh frame-relay pvc

Trang 13

in DE pkts 0 out DE pkts 0 out bcast pkts 322 out bcast bytes 25768

Shaping adapts to BECN

pvc create time 00:33:42, last time pvc status changed 00:22:43

Router1#sh frame-relay map Serial2.1 (up): point-to-point dlci, dlci 100(0x64,0x1840), broadcast

shows the mapping of DLCI

status defined, activeSerial2.2 (up): point-to-point dlci, dlci 102(0x66,0x1860), broadcast

status defined, active

Router1#show frame-relay traffic

Frame Relay statistics:

ARP requests sent 0, ARP replies sent 0ARP request recvd 0, ARP replies recvd 0Router1#

Trang 14

ATM Connections

This section covers ATM connectivity in wide area networks, where ATM is very widely used Major telecommunication carriers build voice and data backbones using ATM technology The major benefits of ATM are Quality of Service (QoS), which is required for voice and video traffic ATM provides fixed size cells of 53 bytes These cells consist of a 5-byte header and a 48- byte payload The fixed cell size provides predictability and allows ATM to operate extremely efficiently ATM is especially useful for time-delay sensi- tive applications such as voice and video

ATM Overview

ATM is the building block of Broadband ISDN (B-ISDN) services The opment of optical technologies was a major consideration in its technologies ATM is a technology developed to address the needs of both voice and data technologies; in voice technologies, there should be guaranteed bandwidth on a per call basis for a call to be reliable In data technologies, the traffic is bursty Voice packets are usually small compared to data packets.

devel-To address the requirements of both, ATM Forum and other standards anizations agreed to 53-byte cell, with a 5-byte header, and 48-byte payload ATM technologies scales well at higher speeds like OC-3, OC-12, etc Some of the features of ATM are:

org-■ The edge devices provide error and flow control.

■ There is no error control on data field within the network, due to low transmission error rates on fiber

■ There is no flow control on links within the network

■ It is connection-oriented at the lowest level.

■ All information is transferred in a virtual circuit assigned for the duration of the connection.

■ A fixed cell (packet) size permits high-speed switching nodes.

■ There is no constraint on data services (segmentation).

■ It has an efficient cell structure for bandwidth allocation, and quality of service.

ATM Packet Format

Table 7.8 depicts the ATM cell format

Trang 15

Table 7.8 ATM Cell Format

Header 5 bytes (8 bits = 1 byte) Payload 48 bytes

4 bits 8 bits 16 bits 3 bits 1 bit 8 bits Data

GFC Generic Flow VPI Virtual Path Identifier—VPI is 8 bits, which gives 256 virtual paths VCI Virtual Circuit Identifier—VCI is 16 bits, which gives 65K virtual circuits PTI Payload Type Indicator

CLP Cell Loss—CLP is the cell loss priority bit, which if set, can discard

the packet This is similar to the DE (Discard Eligibility) bit in Frame Relay

HEC Header Error Control—HEC is the check sum error control on the

header itself HEC is also used as a synchronizing delimiter; after three HEC matches the transmission is synchronized

Payload Data

ATM Adaptation Layer (AAL) The ATM Adaptation Layer (AAL) provides mapping of higher layer applica- tion data to and from the ATM cell The services AAL provides are a SAR (Segmentation Assembly and Re-assembly) layer; also it detects lost cells and errors in cells through a 4-bit sequence number protection Several AAL types are defined, with each type consisting of a separate SAR sublayer:

■ AAL Type 1 Used for connection-oriented, constant-bit-rate

services and is used for circuit emulation.

■ AAL Type 2 Used for connection-oriented, variable-bit-rate

services, and is used for video applications.

■ AAL Type 3/4 AAL Type 3 and 4 are combined; they are designed

for data applications and support both connectionless and tion oriented applications.

connec-■ AAL Type 5 A more commonly used protocol, applied to VBR

(Variable Bit Rate) type traffic AAL Type 5 is used for signaling and frame relay over ATM.

The AAL provides the benefits of error detection, circuit emulation, and connectionless or connection-oriented services depending on the type of AAL used.

Trang 16

ATM Virtual Circuits

ATM virtual circuits are built on top of a VPI/VCI combination A VC

bundle inside of a VP is used to differentiate traffic (like voice, video, and data) VPI/VCI are significant on a physical link between a pair of ATM switches These circuits are unidirectional, and need mapping in reverse directions to complete conversation between two end-node devices Circuits can be established as PVCs or SVCs More popularly used circuits are PVCs, which need mapping and configuration at each ATM switch along the path SVCs are more dynamic; hence they build and tear the sessions automatically

Figure 7.17 illustrates that on a given physical ATM network, the VP are the virtual paths that are uniquely identified through VPI In every virtual path, multiple virtual channels can be defined VPI is 8 bits long (256 virtual paths), and VCI is 16 bits long (64K circuits), thus providing 256* 64k circuits The number of channels available gives the granularity

needed to provide QoS Each circuit is a VPI/VCI combination VPI zero (VPI=0) is reserved

PVC Mapping and Circuit Buildup

Table 7.8 and Figure 7.18 demonstrate the process of PVC mapping and circuit buildup Notice how the Ports, VCI, and VPI in the table relate and map to the switch diagram Remember PVCs need to be manually configured on each switch.

Table 7.8 PVC mapping and circuit emulation.

Input Port VPI VCI Port Output VPI VCI

Trang 17

In the case of Cisco routers with an AIP ATM interface, the PVCs are mapped point-to-point, or point-to-multipoint

Configuring ATM Configuring routers for ATM is similar to any other interface on Cisco routers Set up the interface subsystem in the configuration mode, by typing the interface-related detailed syntax Figure 7.19 illustrates how to build an ATM network; configurations follow in Figures 7.20 and 7.21

ATM switch 1 ATM switch 2

ATM switch 3

S1,P 2 going to P1

of sw3 with VPI=20,VCI=10

Vpi=10,vci=

20 comming

to P1, sw1

Vpi=30,vci=15 comming toP3 - SW1-P1-SW2

P4 SW1 going to P3 of sw3 with VPI=31,VCI=16

E0

AIP1/0

Branch1-1 E0 192.168.2.1/24 ATM 1/0 192.168.102.1/24 ISDN No 222222

Host A 192.168.2.2

SERVER A 10.1.1.2

Trang 18

Figure 7.20 Router1 configuration.

Router1

!

version 12.0

service timestamps debug uptime

service timestamps log uptime

Trang 19

!router igrp 1network 10.0.0.0

!

ip classless

no ip http server

!end

Figure 7.21 Router2 configuration.

Router2

!version 12.0service timestamps debug uptimeservice timestamps log uptime

no service password-encryption

!hostname Router2

!

!network-clock base-rate 56k

Trang 21

Verifying and Troubleshooting ATM Connections

The methodology applied in troubleshooting ATM networks is by using show and debug commands relevant to ATM Various commands that can

be used to monitor an ATM network include the following:

Router1#show atm ?arp-server ATM ARP Server Tableclass-links ATM vc-class linksilmi-configuration Display Top level ILMIilmi-status Display ATM Interface ILMI informationinterface Interfaces and ATM informationmap ATM static mapping

pvc ATM PVC informationsignalling ATM Signaling commandssvc ATM SVC informationtraffic ATM statistics

vc ATM VC information

vp ATM VP informationRouter1#show int atm 0

ATM0 is up, line protocol is up Hardware is PQUICC Atom1

MTU 1500 bytes, sub MTU 1500, BW 1536 Kbit, DLY 20000 usec, reliability 255/255, txload 1/255, rxload 1/255

Encapsulation ATM, loopback not set -Æshows the encapsulation mode

on the interfaceKeepalive not supported Encapsulation(s):, PVC mode

1024 maximum active VCs, 2 current VCCs Æ shows Virtual channels supported

VC idle disconnect time: 300 secondsLast input 00:00:00, output never, output hang neverLast clearing of “show interface” counters neverInput queue: 0/75/0 (size/max/drops); Total output drops: 0Queueing strategy: weighted fair

Trang 22

The following command shows the details on the sub-interface atm 0.1.

Router1# show int atm 0.1

ATM0.1 is up, line protocol is up

Hardware is PQUICC Atom1Internet address is 10.0.23.2/24MTU 1500 bytes, BW 1536 Kbit, DLY 20000 usec, reliability 255/255, txload 1/255, rxload 1/255

Encapsulation ATM

12 packets input, 874 bytes

15 packets output, 1106 bytes

0 OAM cells input, 0 OAM cells output

The following command shows traffic across the ATM link.

Router1#SHOW ATM traffic

13 Input packets

14 Output packets

0 Broadcast packets

0 Packets received on non-existent VC

0 Packets attempted to send on non-existent VC

0 OAM cells received

F5 InEndloop: 0, F5 InSegloop: 0, F5 InAIS: 0, F5 InRDI: 0

F4 InEndloop: 0, F4 InSegloop: 0, F4 InAIS: 0, F4 InRDI: 0

0 OAM cells sent

Trang 23

F5 OutEndloop: 0, F5 OutSegloop: 0, F5 OutRDI: 0F4 OutEndloop: 0, F4 OutSegloop: 0, F4 OutRDI: 0

0 OAM cell drops

The following command shows the PVC status.

0.1 my-data-pv 0 100 PVC SNAP UBR 64 UP0.2 my-voice-p 0 200 PVC VOICE VBR 384 192

ip 10.0.23.3 maps to VC 1, VPI 0, VCI 100, ATM0.1

ATM Debug Commands:

Router1#debug atm ?aal-crc Display CRC error packetsarp Show ATM ARP eventscompress ATM Compressionerrors ATM errorsevents ATM or FUNI Eventsilmi Show ILMI eventsoam Dump OAM Cellspacket ATM or FUNI packetspvcd Show PVCD eventssig-all ATM Signalling allsig-api ATM Signalling apisig-error ATM Signalling errorssig-events ATM Signalling events

Trang 24

sig-ie ATM Signalling information elementssig-packets ATM Signalling packets

smap-all ATM Signalling Static Map allsmap-error ATM Signalling Static Map errorssmap-events ATM Signalling Static Map eventsstate ATM or FUNI VC States

Let’s look at some ATM debug commands that will further aid in bleshooting ATM implementations.

trou-The debug atm packet Command

The debug atm packet command will display all ATM packets.

Router1#debug atm packet

ATM packets debugging is on

Displaying all ATM packets

Log Buffer (4096 bytes):

04:45:47: %SYS-5-CONFIG_I: Configured from console by console

Trang 25

04:46:06: %LINK-5-CHANGED: Interface ATM0, changed state toadministratively down

04:46:07: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changed

state to down

04:46:21: ATM0.1(O):

VCD:0x1 VPI:0x0 VCI:0x64 DM:0x100 SAP:AAAA CTL:03 OUI:000000 TYPE:0800Length:0x56

Shows the 1/100 (64hex) pvc sending an ip packet type0800.

04:46:21: 45C0 004A 0000 0000 0209 96EA 0A00 1702 FFFF FFFF 1105 0001

0003 0000 0000 04:46:21: 53C9 0002 0000 0064 0003 E805 DCFF 0100 0003 00FF FFFF 0100

0501 1043 6973 04:46:21: 0017 0000 07D0 0019 6E05 DCFF 0100 04:46:21:

04:46:22: ATM0.1(O): —o –Outgoing packet

VCD:0x1 VPI:0x0 VCI:0x64 DM:0x100 SAP:AAAA CTL:03 OUI:000000 TYPE:0806Length:0x20

Arp packet type 0806

04:46:22: 0013 0800 0000 0008 0400 0004 0A00 1702 0000 0000 04:46:22:

04:46:22: ATM0.1(I):

VCD:0x1 VPI:0x0 VCI:0x64 Type:0x0 SAP:AAAA CTL:03 OUI:000000 TYPE:0806Length:0x20

04:46:22: 0013 0800 0000 0009 0400 0004 0A00 1703 0A00 1702 04:46:22:

04:46:23: %LINK-3-UPDOWN: Interface ATM0, changed state to up

04:46:24: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changed

Trang 26

04:46:34: 8030 0002 0000 0834 0019 6E05 DCFF 0101 0003 0000 0064 0003E805 DCFF 0100

Router1#no debug atm packet

ATM packets debugging is off

The debug atm state Command

Use the debug atm state command to see changes in the state of the ATM

VCs.

Router1#debug atm state

ATM VC States debugging is on

Log Buffer (4096 bytes):

04:48:40: %LINK-5-CHANGED: Interface ATM0, changed state to

Trang 27

04:49:13: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changedstate to up

The following conversation provides ATM VC states.

04:51:08: Changing vc 0/100vc-state to ATM_VC_SHUTTING_DOWN04:51:08: Changing vc 0/100vc-state to ATM_VC_NOT_IN_SERVICE04:51:08: Changing vc 0/100vc-state to ATM_VC_NOT_IN_SERVICE04:51:08: Changing vc 0/200vc-state to ATM_VC_SHUTTING_DOWN04:51:08: Changing vc 0/200vc-state to ATM_VC_NOT_IN_SERVICE04:51:08: Changing vc 0/200vc-state to ATM_VC_NOT_IN_SERVICE04:51:10: %LINK-5-CHANGED: Interface ATM0, changed state toadministratively down

04:51:11: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changedstate to down

04:51:41: Changing vc 0/100 vc-state to ATM_VC_NOT_VERIFIED 04:51:41: Changing vc 0/100 vc-state to ATM_VC_ESTABLISHING_VC04:51:41: Changing vc 0/100 vc-state to ATM_VC_NOT_VERIFIED04:51:41: Changing vc 0/100 vc-state to ATM_VC_UP

04:51:41: Changing vc 0/200 vc-state to ATM_VC_NOT_VERIFIED 04:51:41: Changing vc 0/200 vc-state to ATM_VC_ESTABLISHING_VC04:51:41: Changing vc 0/200 vc-state to ATM_VC_NOT_VERIFIED04:51:41: Changing vc 0/200 vc-state to ATM_VC_UP

04:51:43: %LINK-3-UPDOWN: Interface ATM0, changed state to up04:51:44: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changedstate to up

The debug atm ilmi Command

The debug atm ilmi command provides ilmi conversations.

Router1#debug atm ilmiSetting ILMI debug for all interfaces

Router1#conf tEnter configuration commands, one per line End with CNTL/Z

Trang 28

ILMI conversation starts here

tion error on o/g ILMI Pdu <ilmi_send_pkt> (ATM0)

04:57:33: ILMI: Unable to Send Pdu out <ilmi_send_trap> sends an SNMP trap

04:57:35: ILMI(ATM0): Sending ilmiColdStart trap

04:57:35: ILMI(ATM0): No ILMI VC found

04:57:35: ILMI: Encapsulation error on o/g ILMI Pdu <ilmi_send_pkt>(ATM0)

04:57:35: ILMI: Unable to Send Pdu out <ilmi_send_trap>

04:57:37: ILMI: Encapsulation error on o/g ILMI Pdu <ilmi_send_pkt>(ATM0)

04:57:37: ILMI: Unable to Send Pdu out <ilmi_send_trap>

04:57:38: ILMI(ATM0): Received Interface Down Shutting down ILMI 04:57:40: %LINK-5-CHANGED: Interface ATM0, changed state to

administratively down

04:57:41: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changedstate to down

04:58:01: ILMI(ATM0): Received Interface Up

Trang 29

04:58:01: ILMI: Encapsulation error on o/g ILMI Pdu <ilmi_send_pkt>

(ATM0)04:58:01: ILMI: Unable to Send Pdu out <ilmi_send_trap>

04:58:03: %LINK-3-UPDOWN: Interface ATM0, changed state to upRouter1#no debug all

Backing up Permanent Connections

Permanent connections provide connectivity between local and remote

sites Although we call them permanent connections, we all know that

nothing is ever really permanent, right? Like any other physical entity, these permanent connections are susceptible to failure The problem with these connections is that if and when they fail, all connectivity is lost, resulting in costly downtime for the remote users In order to provide fault tolerance to the remote site, you must have a backup connection in place

in case the permanent connection does fail In the event of a permanent connection failure, the backup connection should be able to kick in (trans- parent to the end-users) without any administrative intervention, and pick

up right where the failed link left off Let’s take a look at some of the ways

in which we can provide this type of backup connection.

Backup Interface The backup interface is one of the mechanisms that provides redundancy

in wide area networks The backup interface is configured in the primary interface configuration; when the primary goes down, it recognizes the loss

of signal on the primary and raises DTR on the secondary interface

Figure 7.22 illustrates how to configure the backup interface on a point-to-point link.

192.168.2.2 serial 0

BRI 0192.168.1.12tel: 2222

BRI 0192.168.1.1tel: 3333192.168.2.1 serial 0

Trang 30

backup delay 30 never

backup interface BRI0

dialer map ip 192.168.1.1 name Branch1 3333

dialer load-threshold 180 outbound

dialer-group 10

isdn switch-type basic-dms100

Tiêu đề	Configuring And Backing Up Permanent Connections
Trường học	Syngress Publishing
Chuyên ngành	Networking
Thể loại	Bài báo
Năm xuất bản	2000
Thành phố	Not specified

Định dạng
Số trang	60
Dung lượng	284,85 KB