cc/td/doc/product/access/acs_serv/as5400
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Advanced Configuration

Advanced Configuration

This chapter describes how to configure and use various features to extend your Cisco AS5400 network capabilities:

For advanced configurations, refer to "Comprehensive Configuration Examples."

If you are experienced using the Cisco IOS software, see "Comprehensive Configuration Examples," for a useful reference for configuration.


Note   The procedures in this chapter assume you have completed the steps in "Basic Configuration." If you skipped that chapter, read it before continuing.

Configuring Redundant Link Manager

The goal of Redundant Link Manager (RLM) is to primarily provide a virtual link management over multiple IP networks so that the Q.931 signaling protocol and other proprietary protocols can be transported on top of multiple redundant links between the Cisco signaling controller and the access server.

We recommend that all access servers should use at least two IP interfaces to connect to the primary and alternative IP interfaces of the signaling controller. Otherwise, the control traffic will be impacted by the data traffic by sharing the same interface for both types of traffic.

Configure


Command
Purpose

Step1

5400>enable
Password: password
5400# 

Enter enable mode (also called privileged EXEC mode) and enter the password.

You have entered enable mode when the prompt changes to 5400#.

Step2

5400#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
5400(config)# 

Enter global configuration mode. You have entered global configuration mode when the prompt changes to as5400(config)#.

Step3

5400(config)#rlm group 1

Specify the rlm-group (network access server) that you want to configure using the rlm group global configuration command.

Step4

5400(config-rlm-group)#interface Loopback1
5400(config-if)# ip address 10.1.1.1 255.255.255.255

Specify the IP address of the first interface.

Step5

5400(config-if)#interface Loopback2
5400(config-if)# ip address 10.1.1.2 255.255.255.255

Specify the IP address of the second interface.

Step6

5400(config-if)#rlm group 1
5400 (config-rlm-group)# 

Return to rlm group global configuration mode.

Step7

5400(config-rlm-group)#server r1-server
5400(config-rlm-group-sc)# link address 10.1.4.1 source Loopback1 weight 4
5400(config-rlm-group-sc)# link address 10.1.4.2 source Loopback2 weight 3

Specify the first device name.

Specify the link addresses and their weighting preferences.

Step8

5400(config-rlm-group-sc)#server r2-server
5400(config-rlm-group-sc)# link address 10.1.5.1 source Loopback1 weight 2
5400(config-rlm-group-sc)# link address 10.1.5.2 source Loopback2 weight 1

Specify the second device name.

Specify the link addresses and their weighting preferences.

Step9

5400(config-if)#Ctrl-Z 
5400#

Return to enable mode.

Verify

To verify you have configured the interfaces correctly:

    5400# show rlm group 1 status 
     
    RLM Group 1 Status
     User/Port: RLM_MGR/3000 
     Link State: Up         Last Link Status Reported: Up
     Next tx TID: 1         Last rx TID: 0
     Server Link Group[r1-server]:
      link [10.1.1.1(Loopback1), 10.1.4.1] = socket[active]
      link [10.1.1.2(Loopback2), 10.1.4.2] = socket[standby]
     Server Link Group[r2-server]:
      link [10.1.1.1(Loopback1), 10.1.5.1] = socket[opening]
      link [10.1.1.2(Loopback2), 10.1.5.2] = socket[opening]
    

Note the following:

    5400# show isdn status
     
    Global ISDN Switchtype = primary-ni
    ISDN Serial0:23 interface
            dsl 0, interface ISDN Switchtype = primary-ni
        Layer 1 Status:
            DEACTIVATED
        Layer 2 Status:
            TEI = 0, Ces = 1, SAPI = 0, State = TEI_ASSIGNED
        Layer 3 Status:
            0 Active Layer 3 Call(s)
        Activated dsl 0 CCBs = 0
    ISDN Serial1:23 interface
            dsl 1, interface ISDN Switchtype = primary-ni
        Layer 1 Status:
            DEACTIVATED
        Layer 2 Status:
            TEI = 0, Ces = 1, SAPI = 0, State = TEI_ASSIGNED
        Layer 3 Status:
            0 Active Layer 3 Call(s)
        Activated dsl 1 CCBs = 0
        Total Allocated ISDN CCBs = 0
    

Note the following information for Serial 0:23 (the first half of the messages):

The second half of the messages display information for Serial 1:23.


Tips If you are having trouble:



Configuring ISL for VLAN Routing

Use the Inter-Switch Link (ISL) to connect multiple Virtual LANs (VLANs) using the Ethernet Media Access Control (MAC) and Ethernet media.

Configure


Command
Purpose

Step1

5400>enable
Password: password
5400# 

Enter enable mode (also called privileged EXEC mode).

Enter the password.

You have entered enable mode when the prompt changes to 5400#.

Step2

5400#configure terminal
Enter configuration commands, one per line. End
with CNTL/Z.
5400(config)#

Enter global configuration mode. You have entered global configuration mode when the prompt changes to 5400(config)#.

Step3

5400(config)#interface fastethernet 0/0
 

Enter the FastEthernet interface configuration mode.

Step4

5400(config-if)#no shut

Enable FastEthernet.

Step5

5400(config)#interface fastethernet0/0.x

Enter the FastEthernet subinterface x, where x is an integer value.

Step6

5400(config-subif)#encapsulation isl n

Set ISL encapsulation to the VLAN identifier (n is a value between 1 and 1000).

Step7

5400(config-subif)#ipx network ipx-number

Set the virtual IPX1 network number for the VLAN ID. Ipx-number is an eight-digit hexadecimal number that uniquely identifies a network cable segment. Number range is 1 to FFFFFFFD.

Step8

5400(config-subif)#Ctrl-Z 
5400#

Return to enable mode.

1IPX = Internetwork Packet Exchange.

Verify

To verify the VLAN setup (VLAN ID, network address, protocol, and packets received and transmitted):

    5400# show vlan
     Virtual LAN ID:  10 (Inter Switch Link Encapsulation)
     vLAN Trunk Interface:   FastEthernet0/0.10      
     Protocols Configured:   Address:              Received:        Transmitted:
              X           10.00e0.1e6b.2f03         3                   5
    

Tips If packets are not being routed:

    5400# debug vlan packets
    Virtual LAN packet information debugging is on
     
    vLAN: ISL packet received bearing color ID 16 on FastEthernet0
          which has no subinterface configured to route or bridge ID 16.
    



Configuring IPX Networks

Configure the IPX networks for dial-in remote IPX users.

Configure


Command
Purpose

Step1

5400#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
5400(config)#

Enter global configuration mode. You have entered global configuration mode when the prompt changes to 5400(config)#.

Step2

5400(config)# ipx routing
5400(config)# interface loopback 0
5400(config-if)# ipx network FEFEFE
5400(config-if)# exit
5400(config)# interface ethernet 0
5400(config-if)# ipx network 123ABCD encapsulation SAP
5400(config-if)# exit
5400(config)# interface group-Async 1
5400(config-if)# group-range 1 48 [or] for E1 PRI
5400(config-if)# group-range 1 60
Building configuration...
5400(config-if)# ipx ppp-client Loopback 0
5400(config-if)# exit

Enable IPX clients to access network resources by dialing through the access server over ISDN.

Step3

5400(config)# interface dialer 1
5400(config-if)# ipx ppp-client Loopback 0

Create a dialer interface. This is the parent interface for all of the ISDN interfaces (this was set using the dialer rotary-group 1 command in the IP configuration).

Step4

5400(config-if)# dialer map ipx FEFEFE.0000.0c00.1234 name jordan 
5400(config-if)# dialer map ipx FEFEFE.0000.0c00.4567 name rodman 
5400(config-if)# dialer map ipx FEFEFE.0000.0c00.89AB name colin 
5400(config-if)# exit

Create a dialer map for the single IPX network address that contains all the dial-in users (for example, FEFEFE). The map for each IPX address differs and is activated by each dial-in user's login sessions.

For IP configurations, dialer mapping is automatically constructed when the access server receives a user's name and address. However, when you use IPX configuration, you must statically configure each user name's IPX address.

Step5

5400(config)# dialer-list 1 protocol ipx permit
5400(config)# exit

Enable IPX packets to reset the idle timer.

Step6

5400# copy running-config startup-config
#########[OK]

This completes the configuration for IPX. Save the running configuration to the start-up configuration.

The access server will boot with your configuration at the next power up.

Verify

To verify the IPX routing is enabled:

5400# configure terminal
5400(config)# show ipx interface serial 1:23
Serial1:23 is up, line protocol is up
  IPX address is 2A.00e0.1e6b.2f6e [up]
  Delay of this IPX network, in ticks is 6 throughput 0 link delay 0
  IPXWAN processing not enabled on this interface.
  IPX SAP update interval is 1 minute(s)
  IPX type 20 propagation packet forwarding is disabled
  Incoming access list is not set
  Outgoing access list is not set
  IPX helper access list is not set
  SAP GNS processing enabled, delay 0 ms, output filter list is not set
  SAP Input filter list is not set
  SAP Output filter list is not set
  SAP Router filter list is not set
  Input filter list is not set
  Output filter list is not set
  Router filter list is not set
  Netbios Input host access list is not set
  Netbios Input bytes access list is not set
  Netbios Output host access list is not set
  Netbios Output bytes access list is not set
  Updates each 60 seconds, aging multiples RIP: 3 SAP: 3 
  SAP interpacket delay is 55 ms, maximum size is 480 bytes
  RIP interpacket delay is 55 ms, maximum size is 432 bytes
  Watchdog spoofing is disabled, SPX spoofing is disabled, idle time 60
  IPX accounting is disabled
  IPX fast switching is configured (disabled)
  RIP packets received 0, RIP packets sent 1
  SAP packets received 0, SAP packets sent 0

Tips If you are having trouble:



Configuring AppleTalk

Configure AppleTalk to enable Macintosh clients to access network resources by dialing through the access server over ISDN.

Configure


Command
Purpose

Step1

5400#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
5400(config)#

Enter global configuration mode. You have entered global configuration mode when the prompt changes to 5400(config)#.

Step2

5400(config)#appletalk routing
5400(config)# appletalk virtual-net 2 ATCP Zone

Enable AppleTalk routing and set the AppleTalk zone ATCP1 on network 2 (your network number and zones may differ).

All users that dial in to the system will belong to the AppleTalk network 2 in the AppleTalk zone ATCP Zone. All the dial-in users will look as though they are on a single network. Links will not have their own network numbers. This applies to configurations using PPP instead of ARAP2 encapsulation.

Step3

5400(config)#appletalk cable-range 1-1 1.120
5400(config-if)# appletalk zone Ethernet
5400(config-if)# exit
5400(config)# exit

Set the AppleTalk cable range and the AppleTalk zone on the Ethernet interface.

Step4

5400# copy running-config startup-config
#########[OK]

Complete configuration for AppleTalk operation. Save the running configuration to the startup configuration.

1ATCP = AppleTalk Control Protocol.
2ARAP = AppleTalk Remote Access Protocol.

Verify

To verify the AppleTalk interface is up and running:

    5400# show appletalk interface serial 0/0
    Serial0/0 is up, line protocol is up
      AppleTalk address is 10.1, Valid
      AppleTalk zone is "dolzone"
      AppleTalk discarded 37 packets due to output errors
      AppleTalk address gleaning is not supported by hardware
      AppleTalk route cache is disabled, Dial on Demand specified
    

Tips If you are having trouble, you can troubleshoot the AppleTalk protocol by using its debug commands to view information for the errors, events, and packets and check the Gateway name, access server name, and if the virtual access interface is up.

    5400# debug ppp negot
    PPP protocol negotiation debugging is on
    5400#
    %LINK-3-UPDOWN: Interface Async1, changed state to up
    PPP Async1: treating connection as a dedicated line
    ppp: sending CONFREQ, type = 2 (CI_ASYNCMAP), value = 0xA0000
    ppp: sending CONFREQ, type = 3 (CI_AUTHTYPE), value = 0xC223/5
    ppp: sending CONFREQ, type = 5 (CI_MAGICNUMBER), value = 0xAB1BAB3
    PPP Async1: state = REQsent fsm_rconfack(0xC021): rcvd id 7
    ppp: config ACK received, type = 2 (CI_ASYNCMAP), value = 0xA0000
    ppp: config ACK received, type = 3 (CI_AUTHTYPE), value = 0xC223
    ppp: config ACK received, type = 5 (CI_MAGICNUMBER), value = 0xAB1BAB3
    ppp: config ACK received, type = 7 (CI_PCOMPRESSION)
    ppp: config ACK received, type = 8 (CI_ACCOMPRESSION)
    PPP Async1: received config for type = 1 (MRU) value = 1500 acked
    PPP Async1: received config for type = 2 (ASYNCMAP) value = 0x0 acked
    PPP Async1: received config for type = 5 (MAGICNUMBER) value = 0x565CFA6A acked
    PPP Async1: received config for type = 7 (PCOMPRESSION) acked
    PPP Async1: received config for type = 8 (ACCOMPRESSION) acked
    ipcp: sending CONFREQ, type = 2 (CI_COMPRESSTYPE), slots = 15, csid = 0
    ipcp: sending CONFREQ, type = 3 (CI_ADDRESS), Address = 171.60.199.193
    Resetting ATCP
    atcp: sending CONFREQ, type = 6 (CI_AT_SERVERINFO), values = 119132, 6
    atcp: sending CONFREQ, type = 7 (CI_AT_ZONEINFO), values = 1191B3, 9
    atcp: sending CONFREQ, type = 8 (CI_AT_DEFAULT_ROUTER), values = 5, C7
    .
    
    5400# show int async 1/0
    Async1 is up, line protocol is up 
      Hardware is Async Serial
      Interface is unnumbered.  Using address of Ethernet0 (171.60.199.193)
      MTU 1500 bytes, BW 38 Kbit, DLY 100000 usec, rely 255/255, load 1/255
      Encapsulation PPP, loopback not set, keepalive not set
      DTR is pulsed for 5 seconds on reset
      LCP Open
      Open: IPCP, ATALKCP
      Last input 00:00:01, output 00:00:08, output hang never
      Last clearing of "show interface" counters 07:17:22
      Input queue: 1/75/0 (size/max/drops); Total output drops: 0
      Queueing strategy: weighted fair
      Output queue: 0/64/0 (size/threshold/drops) 
         Conversations  0/9 (active/max active)
         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
         753 packets input, 22232 bytes, 0 no buffer
         Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
         0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
         638 packets output, 37821 bytes, 0 underruns
         0 output errors, 0 collisions, 3 interface resets
         0 output buffer failures, 0 output buffers swapped out
         0 carrier transitions
    

    5400# show apple int async 1
    Async1 is up, line protocol is up
      AppleTalk port is in client-mode
      AppleTalk discarded 3 packets due to input errors
      AppleTalk address gleaning is not supported by hardware
      AppleTalk route cache is disabled, port down
    

    5400# debug appletalk events
    AppleTalk Events debugging is on
    *Aug 15:56:06.907: AT: RTMP GC complete (0 PDBs freed, 0 PDBs waiting)
    *Aug 15:17:56:06.927: AT: Connected GC complete (0 PDBs freed, 0 PDBs waiting)
    
    5400# debug appletalk ?
    	arp	Appletalk address resolution protocol
    	aurp-connection	AURP connection
    	aurp-packet	AURP packets
    	aurp-update	AURP routing updates
    	domain	AppleTalk Domain function
    	eigrp-all	All AT/EIGRP functions
    	eigrp-external	AT/EIGRP external functions
    	eigrp-hello	AT/EIGRP hello functions
    	eigrp-packet	AT/EIGRP packet debugging
    	eigrp-query	AT/EIGRP query functions
    	eigrp-redistribution	AT/EIGRP route redistribution
    	eigrp-request	AT/EIGRP external functions
    	eigrp-target	Appletalk/EIGRP for targeting address
    	eigrp-update	AT/EIGRP update functions
    	errors	Information about errors
    	events	Appletalk special events
    	fs	Appletalk fast-switching
    	iptalk	IPTalk encapsulation and functionality
    	load-balancing	AppleTalk load-balancing
    	macip	MacIP functions
    	nbp	Name Binding Protocol (NBP) functions
    	packet	Per-packet debugging
    	redistribution	Route Redistribution
    	remap	AppleTalk Remap function
    	responder	AppleTalk responder debugging
    	routing	(RTMP&EIGRP) functions
    	rtmp	(RTMP) functions
    	zip	Zone Information Protocol functions
    



Configuring VPDN

Virtual private dial-up networking (VPDN) enables users to configure secure networks that take advantage of Internet service providers (ISPs) that tunnel a company's remote access traffic through the ISP cloud.

Remote offices or mobile users can connect to their home network using local third-party dial-up services. The dial-up service provider agrees to forward the company's traffic from the ISP point of presence (POP) to a company-run home gateway. Network configuration and security remains in the control of the client. The dial-up service provider provides a virtual connection between the company's sites.


Note   The MMP feature uses VPDN to connect multiple PPP sessions for which individual dial-in calls have arrived on different stack group members. VPDN provides speed and reliability for the setup and shutdown of Multilink PPP.

Configure


Command
Purpose

Step1

5400>enable
Password: password
5400# 

Enter enable mode (also called privileged EXEC mode) and enter the password.

You have entered enable mode when the prompt changes to 5400#.

Step2

5400#configure terminal
Enter configuration commands, one per line. End
with CNTL/Z.
5400(config)#

Enter global configuration mode. You have entered global configuration mode when the prompt changes to 5400(config)#.

Step3

5400(config)#vpdn enable

Enable virtual private dial-up networking.

Step4

5400(config)#vpdn outgoing domain1.com nas1 ip 172.21.9.18
5400(config)# vpdn outgoing domain2.com nas2 ip 173.22.10.19

Specify the name and IP address of the remote host and the name to use when authenticating a tunnel for forwarding traffic to the remote host on a virtual private dial-up network. In this example, two remote hosts are specified.

Step5

5400(config-line)#Ctrl-Z 
5400#

Return to enable mode.

Verify

To verify your VPDN configuration:

    5400# show vpdn
    Active L2F tunnels = 2
     
    NAS Name        Gateway Name    NAS CLID   Gateway CLID   State
    test-mmp        test-gateway       272          272        open
    192.168.1.99    192.168.1.119    
     
    L2F MIDs = 10
    Name                       NAS Name      Interface    MID      State
    rw56                       test-mmp       Vi238        1       open
    rw55                       test-mmp       Vi240        3       open
    rw54                       test-mmp       Vi242        4       open
    rw57                       test-mmp       Vi246        7       open
    rw57                       test-mmp       Vi248        8       open
    rw54                       test-mmp       Vi245        13      open
    rw55                       test-mmp       Vi244        14      open
    rw16                       test-mmp       Vi249        97      open
    rw16                       test-mmp       Vi251        98      open
    rw56                       test-mmp       Vi250        100     open
    

Tips If you are having trouble:

        5400# debug vpdn ?
          error        VPDN Protocol errors
          event        VPDN event
          l2f-errors   L2F protocol errors
          l2f-events   L2F protocol events
          l2f-packets  L2F protocol packets
          packet       VPDN packet
    
        5400# debug vpdn event
          VPN events debugging is on
             *May 15 17:55:49.367: %LINK-3-UPDOWN: Interface Virtual-Access239,      
          changed state to down
          *May 15 17:55:49.547: Virtual-Access249 VPN reset
          *May 15 17:55:49.547: %LINK-3-UPDOWN: Interface Virtual-Access249,
          changed state to down
    
This is sample output for the debug vpdn l2f-events command:
        5400# debug vpdn l2f-events
          L2F protocol events debugging is on
          *May 15 17:56:46.259: L2F_OPEN received
          *May 15 17:56:46.263: L2F Got a MID management packet
          *May 15 17:56:46.339: %LINK-3-UPDOWN: Interface Virtual-Access239,
          changed state to up 
    
This is sample output for the debug vpdn l2f-errors command:
        5400# debug vpdn l2f-errors
          L2F protocol errors debugging is on
          *May 15 17:57:57.827: %LINK-3-UPDOWN: Interface Virtual-Access251,
          changed state to down
    



Creating Authentication Accounts

You can create authentication accounts for other routers between the NAS and the HGW for VPDN.

On the NAS, an example is:

username NAS password <text omitted>
username HGW password <text omitted>
vpdn enable
vpdn outgoing cisco.com NAS ip X.X.X.X
 

On the HGW, an example is:

username NAS password <text omitted><text omitted>
username HGW password <text omitted>
vpdn enable
vpdn incoming NAS HGW virtual-template 1

Using Continuity Test (COT)

The COT subsystem supports the Continuity Test (COT), which is required by the SS7 network to conduct loopback and tone check testing on the path before a circuit is established. Continuity testing (COT) will detect any failure of DS0 channels. It is required for North American SS7 compliance.

Configure

There are no configuration tasks.

Verify

Use the following commands to verify COT:

    5400# show cot dsp status 1/1
    Rx Freq 2010 Hx
    Tx Freq 1780 Hx
    Tx then Tx mode
    in WaitRxOn state
     
    5400# show cot dsp config 1/1
    Rx Freq 2010 Hx
    Tx Freq 1780 Hx
    Tx then Tx mode
    Timeout value:0
    

    5400# show cot request 1/0/1
    00:19:29:COT Request@ 0x61064A20, CDB@ 0x60EBB48C, Params@0x61123DBC
    00:19:29:  request type = COT_CHECK_TONE_ON
    00:19:29:  shelf 0 appl_no 1 ds0 1
    00:19:29:  duration 100000 key FFF1 freqTx 1780 freqRx 2010
    00:19:29:  state COT_WAIT_TD_ON_CT
    00:19:29:  event_proc(0x6093B55C)
    

    5400# show cot summary
     
    router#
    08:23:24:  COT Subsystem - Request Statistics
     
    08:23:24: COT Request Type = COT_DS0_LOOPBACK_ON
    08:23:24: # of request(s)           : 4         # of restart requests(s)  : 0
    08:23:24: # of successful request(s): 4         # of invalid request(s)   : 0
    08:23:24: # of cot timeout(s)       : 0         # of dsp error(s)         : 0
    08:23:24: # of no dsp(s)            : 0         
     
    08:23:24: COT Request Type = COT_DS0_LOOPBACK_OFF
    08:23:24: # of request(s)           : 4         # of restart requests(s)  : 0
    08:23:24: # of successful request(s): 4         # of invalid request(s)   : 0
    08:23:24: # of cot timeout(s)       : 0         # of dsp error(s)         : 0
    08:23:24: # of no dsp(s)            : 0         
     
    08:23:24: COT Request Type = COT_CHECK_TONE_ON
    08:23:24: # of request(s)           : 7         # of restart requests(s)  : 0
    08:23:24: # of successful request(s): 3         # of invalid request(s)   : 2
    08:23:24: # of cot timeout(s)       : 1         # of dsp error(s)         : 0
    08:23:24: # of no dsp(s)            : 0         
     
    08:23:24: COT Request Type = COT_CHECK_TONE_OFF
    08:23:24: # of request(s)           : 0         # of restart requests(s)  : 0
    08:23:24: # of successful request(s): 0         # of invalid request(s)   : 0
    08:23:24: # of cot timeout(s)       : 0         # of dsp error(s)         : 0
    08:23:24: # of no dsp(s)            : 0         
     
     
    08:23:24: COT Request Type = COT_CUT_IN_TRANSPONDER
    08:23:24: # of request(s)           : 0         # of restart requests(s)  : 0
    08:23:24: # of successful request(s): 0         # of invalid request(s)   : 0
    08:23:24: # of cot timeout(s)       : 0         # of dsp error(s)         : 0
    08:23:24: # of no dsp(s)            : 0         
     
    08:23:24: COT Request Type = COT_CUT_OUT_TRANSPONDER
    08:23:24: # of request(s)           : 0         # of restart requests(s)  : 0
    08:23:24: # of successful request(s): 0         # of invalid request(s)   : 0
    08:23:24: # of cot timeout(s)       : 0         # of dsp error(s)         : 0
    08:23:24: # of no dsp(s)            : 0 
    

    5400# debug cot api
    COT API debugging is on
    08:29:55: cot_request_handler(): CDB@0x60DEDE14, req(COT_CHECK_TONE_ON):
    08:29:55:     shelf 0 slot 0 appl_no 1 ds0 1
    08:29:55:     freqTX 2010 freqRX 1780 key 0xFFF1 duration 60000
     
     
    5400# debug cot detail
    *Dec  4 00:46:05.251:cot_request_handler():CDB@0x6200D33C, req(COT_CHECK_TONE_ON):
    *Dec  4 00:46:05.251:    shelf 0 slot 4 appl_no 0 ds0 0
    *Dec  4 00:46:05.251:    freqTX 2010 freqRX 2010 key 0xFFF1 duration 1000000
     
    *Dec  4 00:46:05.251:cot_query_request, req is NULL
    *Dec  4 00:46:05.251: cot_copy_parameters, param 0x62BFFAF8
    *Dec  4 00:46:05.251: cot_req_handle_alloc , req 0x63182578, cot_params 0x631825F8, params 0x62BFFAF8
    *Dec  4 00:46:05.251:cot_check_tone_on:cot_req 0x63182578
    *Dec  4 00:46:05.251:COT:DSP (5/4) Allocated
    *Dec  4 00:46:05.251:COT:Request Transition to COT_WAIT_TD_ON
    *Dec  4 00:46:05.251:COT(0x6200D33C):Adding new request (0x63182578) to In Progress Q
    *Dec  4 00:46:05.251:COT(0x6200D33C):Adding COT(0x63182578) to the Q head
    *Dec  4 00:46:05.251:COT:Start Duration Timer 1000000 for Check Tone Request req 0x63182578, timer_context 0x6315B624
    *Dec  4 00:46:05.623:cot_dsp_event_handler:get_cot_q_element   0x61AFACA8
    *Dec  4 00:46:05.623:COT:Received DSP Q Event
    *Dec  4 00:46:05.623:COT:Received DSP COT Tone On - DSP (5/4)
    *Dec  4 00:46:05.623:COT:Request Transition to COT_WAIT_TD_OFF_CT
    *Dec  4 00:46:05.623:cot_queue_process return_cot_q_element:cot_q_element 0x61AFACA8,msg_type 0
    *Dec  4 00:46:05.707:cot_dsp_event_handler:get_cot_q_element   0x61AFACA8
    *Dec  4 00:46:05.707:COT:Received DSP Q Event
    *Dec  4 00:46:05.707:COT:Received DSP COT Tone Off - DSP (5/4)
    *Dec  4 00:46:05.707:Stop Duration Timer
    *Dec  4 00:46:05.707:Invoke NI2 callback to inform COT request status
    *Dec  4 00:46:05.707:In cot_callback
    *Dec  4 00:46:05.707:  returned key 0xFFF1, status = SUCCESS
    *Dec  4 00:46:05.707:Return from NI2 callback
    *Dec  4 00:46:05.707:cot_delete_request, old_req 0x63182578
    *Dec  4 00:46:05.707:cot_delete_request,req 0x63182578,req->next 0x0
    *Dec  4 00:46:05.707: cot_req_handle_dealloc, req 0x63182578,param 0x631825F8,cot_timer 0x63182640
    *Dec  4 00:46:05.707:COT:Request Transition to IDLE
    *Dec  4 00:46:05.707:cot_queue_process return_cot_q_element:cot_q_element 0x61AFACA8,msg_type 0
     
    5400# debug cot dsp
    *Dec  4 00:47:23.843:cot_check_tone_on:cot_req 0x631ED100
    *Dec  4 00:47:23.843:COT:DSP (5/5) Allocated
    *Dec  4 00:47:24.207:cot_dsp_event_handler:get_cot_q_element   0x61AFACA8
    *Dec  4 00:47:24.207:COT:Received DSP Q Event
    *Dec  4 00:47:24.207:COT:Received DSP COT Tone On - DSP (5/5)
    *Dec  4 00:47:24.207:cot_queue_process return_cot_q_element:cot_q_element 0x61AFACA8,msg_type 0
    *Dec  4 00:47:24.291:cot_dsp_event_handler:get_cot_q_element   0x61AFACA8
    *Dec  4 00:47:24.291:COT:Received DSP Q Event
    *Dec  4 00:47:24.291:COT:Received DSP COT Tone Off - DSP (5/5)
    *Dec  4 00:47:24.291:In cot_callback
    *Dec  4 00:47:24.291:  returned key 0xFFF1, status = SUCCESS
    *Dec  4 00:47:24.291:cot_queue_process return_cot_q_element:cot_q_element 0x61AFACA8,msg_type 0
    5400# debug cot queue
    *Dec  4 00:47:53.355:cot_query_request,cdb 0x6200D33C, ds0 0
    *Dec  4 00:47:53.355:cot_query_request, req is NULL
    *Dec  4 00:47:53.355: cot_copy_parameters, param 0x62BFFAF8
    *Dec  4 00:47:53.355: cot_req_handle_alloc , req 0x63182578, cot_params 0x631825F8, params 0x62BFFAF8
    *Dec  4 00:47:53.355:COT(0x6200D33C):Adding new request (0x63182578) to In Progress Q
    *Dec  4 00:47:53.355:COT(0x6200D33C):Adding COT(0x63182578) to the Q head
    *Dec  4 00:47:53.731:cot_proc_wait_td_on_ct req 0x63182578, state 2, evevnt 2
    *Dec  4 00:47:53.811:cot_proc_wait_td_off_ct req 0x63182578, state 3, evevnt 3
    *Dec  4 00:47:53.811:cot_timer_cleanup req 0x63182578
    *Dec  4 00:47:53.811:cot_timer_cleanup req 0x63182578, timer_context 0x6315B624
    *Dec  4 00:47:53.811:In cot_callback
    *Dec  4 00:47:53.811:  returned key 0xFFF1, status = SUCCESS
    *Dec  4 00:47:53.811:cot_delete_request, old_req 0x63182578
    *Dec  4 00:47:53.811:cot_delete_request,req 0x63182578,req->next 0x0
    *Dec  4 00:47:53.811: cot_req_handle_dealloc, req 0x63182578,param 0x631825F8,cot_timer 0x63182640
    

    5400# clear cot summary command
    5400#
    

Saving Configuration Changes

To prevent the loss of the access server configuration, save it to NVRAM.

Configure


Command
Purpose

Step1

5400>enable
Password: password
5400# 

Enter enable mode (also called privileged EXEC mode) and enter the password.

You have entered enable mode when the prompt changes to 5400#.

Step2

5400#copy running-config startup-config

Save the configuration changes to NVRAM so that they are not lost during resets, power cycles, or power outages.

Step3

5400(config-if)#Ctrl-Z 
5400#

Return to enable mode.

Where to Go Next

At this point you can proceed to:


Note   The following publications are available on the documentation CD-ROM that came with your access server, on the World Wide Web from Cisco's home page, or you can order printed copies.


Note   The Cisco IOS Release 12.1 documentation set is available at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/index.htm


Note   The abbreviations next to the book icons are page designators (for example, FC, FR, and so on), which are defined in a key in the index of each document to help with navigation. The bulleted lists under each module describe the major technology areas discussed in their corresponding books.


Figure 5-1: Cisco IOS Software Documentation Modules




hometocprevnextglossaryfeedbacksearchhelp
Posted: Tue Aug 15 10:43:08 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.