Cisco IOS Release 11.1(474) Release Note and Update to Configuration Guides and Command References for the Cisco AS5200

Example

The following example enables modem status polling through the out-of-band port through
TTY line 1:

configure terminal
line 1
modem status-poll

Related Commands

modem poll retry
modem poll time

rmon alarm

To set an alarm on any MIB object in the Cisco AS5200, use the rmon alarm configuration command. Use the no form of this command to disable the alarm.

rmon alarm number variable interval {delta | absolute} rising-threshold value [event-number] falling-threshold value [event-number] [owner string]
no rmon alarm number

Syntax Description

number	Alarm number, which is identical to the alarmIndex in the alarmTable in the Remote Network Monitoring (RMON) MIB.
variable	MIB object to monitor, which translates into the alarmVariable used in the alarmTable of the RMON MIB.
interval	Time in seconds the alarm monitors the MIB variable, which is identical to the alarmValue used in the alarm table of the RMON MIB.
delta	Tests the change between MIB variables, which affects the alarmSampleType in the alarmTable of the RMON MIB.
absolute	Tests each MIB variable directly, which affects the alarmSampleType in the alarmTable of the RMON MIB.
rising-threshold value	Value at which the alarm is triggered.
event-number	(Optional) Event number to trigger when the rising or falling threshold exceeds its limit. This value is identical to the alarmRisiongEventIndex or the alarmFallingEventIndex in the alarm Table of the RMON MIB.
falling-threshold value	Value at which the alarm is reset.
owner string	(Optional) Specifies an owner for the alarm, which is identical to the alarm owner in the alarmTable of the RMON MIB.

Default

No alarms configured

Command Mode

Global configuration

Usage Guidelines

To disable the RMON alarms, you must use the no form of the command on each configured alarm. For example, enter no rmon alarm 1, where the 1 identifies which alarm is to be removed.

See RFC 1757 for more information about the RMON alarm group.

Example

The following example configures an RMON alarm using the rmon alarm command:

rmon alarm 10 ifOutErrors.1 20 delta rising-threshold 15 1 falling-threshold 0 owner 
jjohnson

This example configures RMON alarm number 10. The alarm monitors the MIB variable ifOutErrors.1 once every 20 seconds until the alarm is disabled, and checks the change in the variable's rise or fall. If the ifOutErrors.1 value shows a MIB counter increase of 15 or more, such as from 100000 to 100015, the alarm is triggered. The alarm in turn triggers event number 1, which is configured with the rmon event command. Possible events include a log entry or a SNMP trap. If the ifOutErrors.1 value changes by 0, the alarm is reset and can be triggered again.

Related Commands

rmon event
show rmon

rmon event

To add or remove an event in the RMON event table that is associated with an RMON event number, use the rmon event global configuration command. Use the no form of this command to disable RMON on the interface.

rmon event number [log] [trap community] [description string] [owner string]
no rmon event number

Syntax Description

number	Assigned event number, which is identical to the eventIndex in the eventTable in the RMON MIB.
log	(Optional) Generates an RMON log entry when the event is triggered and sets the eventType in the RMON MIB to log or log-and-trap.
trap community	(Optional) SNMP community string used for this trap. Configures the setting of the eventType in the RMON MIB for this row as either snmp-trap or log-and-trap. This value is identical to the eventCommunityValue in the eventTable in the RMON MIB.
description string	(Optional) Specifies a description of the event, which is identical to the event description in the eventTable of the RMON MIB.
owner string	(Optional) Owner of this event, which is identical to the eventDescription in the eventTable of the RMON MIB.

Default

No events configured

Command Mode

Global configuration

Usage Guidelines

This command applies only to the Cisco AS5200.

Example

The following example enables the rmon event command:

rmon event 1 log trap eventtrap description "High ifOutErrors" owner sdurham 

This example configuration creates RMON event number 1, which is defined as High ifOutErrors, and generates a log entry when the event is triggered by an alarm. The user sdurham owns the row that is created in the event table by this command. This configuration also generates a Simple Network Management Protocol (SNMP) trap when the event is triggered.

See RFC 1757 for more information about the RMON MIB.

show modem

To show modem performance statistics on an Cisco AS5200, enable the show modem EXEC command.

show modem [csm | log] [slot/modem-port | group number] [summary | at-mode]

Syntax Description

csm	(Optional) Shows the internal status of the call switching module.
log	(Optional) Shows the modem history event status performed on a manageable modem or group of modems.
slot/modem-port	(Optional) Specifies the location of a slot and modem port. If this number is not specified, statistics for all connected modems are displayed. Remember to include the forward slash (/) when entering this variable.
group number	(Optional) Specifies the location of a specific group of modems. If this number is not specified, statistics for all modems in the access server are displayed.
summary	(Optional) Displays a cumulative statistics report for all manageable modems dialing into and out of the network.
at-mode	(Optional) Displays all AT sessions connected to manageable modems.

Command Mode

EXEC

Usage Guidelines

The keywords log, summary, and at-mode apply only to manageable modems.

The number of events that you can record and view with the show modem log command is defined using the modem buffer-size command. The events stored in the buffer wrap around the event queue. You cannot clear the modem event queue.

Use the clear modem counters command to reset modem counters and clear the modem summary report of modem statistics.

Sample Displays

The following display shows output information for the show modem command:

AS5200# show modem
                 Inc calls      Out calls   Busied   Failed  No       Succ
  Mdm  Usage    Succ   Fail   Succ   Fail   Out      Dial    Answer   Pct.
  1/0     0%       0      0      0      0       0        0       0      0%
  1/1     0%       0      0      0      0       0        0       0      0%
  1/2     0%       0      0      0      0       0        0       0      0%
  1/3     0%       0      0      0      0       0        0       0      0%

Table 6 describes the fields in the previous display

Table 6 : Show Modem Field Descriptions

Field	Description
Mdm	Slot and modem port number. The following modem states can appear to the left of a slot/modem port number: b---Modem was removed from service with the modem shutdown command or the modem busyout command. R---Modem is held and isolated in a suspended state by the modem hold-reset command. B---Modem is Bad*, Bad, or the downloaded firmware has failed. D---Modem is currently downloading firmware. T---Modem is conducting a back-to-back modem test. *---Modem is connected or dialing.
Usage	Percentage of the total system uptime that all modems are in use.
Inc calls	Number of incoming calls that successfully and unsuccessfully connected to an available AS5200 integrated modem.
Out calls	Number of outgoing calls that successfully and unsuccessfully dialed out from an available AS5200 integrated modem.
Busied Out	Number of modems that have been manually removed from service.
Failed Dial	Number of modems that attempted to dial into the network but failed to make a connection.
No Answer	Number of modems that detected an incoming ring but failed to answer the call.
Succ Pct.	Successful connection percentage of total available modems.

The following example shows the statistics and current configurations for the manageable modem 1/1. A dash (-) indicates a field that is not available on nonmanageable modems. An x indicates a field that is available and active on manageable modems.

AS5200# show modem 1/1
   Mdm  Typ  Status   Tx/Rx       G  Duration  TX  RX  RTS  CTS  DSR  DCD  DTR
   1/1  V34  Idle     1200/1200   0  01:39:59   x   x   x    x    x    x    x

Modem 1/1, AS5200 Manageable Modem
Firmware (Boot) Rev: 1.0.1 (0.0.2)
Modem config: Incoming and Outgoing
Protocol: Normal, Compression: None
Management config: status and AT session polling
TX signals: -17 dBm, RX signals: -33 dBm
Last clearing of "show modem" counters 00:11:34
    0 incoming completes, 0 incoming failures, 
    0 outgoing completes, 0 outgoing failures,
    0 failed dial attempts, 0 ring no answers, 0 busied outs
    0 no dial tones, 0 dial timeouts, 0 watchdog timeouts
    0 no carriers, 0 link failures, 0 resets
    0 protocol timeouts, 0 protocol errors, 0 lost events

                     2400-      2400-14400     14400+
# of connections         0               0          0

Table 7 describes the fields in the previous display.

Table 7 : Show Modem Slot/Modem Field Descriptions

Field	Description
Mdm	Slot and modem number.
Typ	Modulation type.
Status	Current status of the modem. Possible values include Conn---Modem is connected to a remote host. Bad---Inoperable state, which is configured by the modem bad command. Bad*---Inoperable state, which is configured by the modem startup-test command during initial power-up testing. Reset---Modem is in reset mode. D/L---Modem is downloading firmware. Bad FW---Downloaded modem firmware is not operational. Busy---Modem is out of service and not available for calls. Idle---Modem is ready for incoming and outgoing calls.
Tx/Rx	Transmission and receiving speed for the most recently connected call.
G	Modem group number assigned to the modem. The group number 0 means the modem is not part of any group.
Duration	Time duration of the current call or the last call.
Modem functions	The following modem functions are displayed on manageable modems. A field that is available and turned on is marked with an x. An unavailable field is marked with a dash (-). TX---Transmit Data. The DTE transmits data to the DCE. RX---Receive Data. The DCE receives data from the DTE. RTS---Request To Send. The DTE signals to the DCE that the DTE accepts data into its buffers. CTS---Clear To Send. The DCE signals to the DTE that the DCE accepts data into its buffers. DSR---Data Set Ready. The modem is ready to start communication. DCD---Data Carrier Detect. The DCE indicates to the DTE that a call is present and established with a remote modem. Dropping the DCD function terminates the session. DTR---Data Terminal Ready. The DTE indicates to the DCE that it accepts calls.
Firmware	Installed modem firmware.
Modem config	Current modem configuration, which includes the fields Incoming, Outgoing, Incoming and Outgoing, and Unknown.
Protocol	Protocol the modem is running such as Normal, Direct, reliable/MNP, and reliable/LAPM (Link Access Procedure for Modems).
Compression	Compression algorithm running on the modem, such as None, V42bis, and MNP class 5.
Management config	Indicates if the modem is configured for out-of-band port polling.
TX signals	Analog signal levels that the modem transmits for signal-to-noise ratio.
RX signals	Analog signal levels that the modem receives for signal-to-noise ratio.
Last clearing of "show modem" counters	Last time the modem's counters were cleared using the clear modem counters command. A summary of modem events also appears. Incoming completes and failures---Total number of incoming connection requests that the modem answered and successfully or unsuccessfully connected with the remote DCE. Outgoing completes and failures---Total number of outgoing connection requests that the modem dialed and successfully or unsuccessfully connected with the remote DCE. Failed dial attempts---Number of times the modem attempted to dial out but the call failed to leave the modem. Ring no answers---Number of times the integrated modem detected ringing but did not answer the incoming call. Busied outs---Number of times the integrated modem was intentionally taken out of service (for example, the modem busyout command was enabled on the modem). No dial tones---Number of times the dial-out attempt failed because the modem failed to detect a dial tone. Dial timeouts---Number of times the modem has timed out while attempting to dial. Watchdog timeouts---Number of times the modem internal watchdog timer has expired. No carriers---Number of times the modem disconnected because no carrier was present. Link failures---Number of times the modem has detected a link failure. Resets---Number of times the modem has been reset. Protocol timeouts and errors---Number times the modem protocol failed to make a call connection. Lost events---Number of incomplete modem events performed by the modem.
# of connections	Speed summary of the number of calls that have connected since the system has been up. Speed categories are 2400 bps, 2400--14400 bps, and 14400+ bps.

The following example displays example output for a nonmanageable modem. Notice that unavailable fields are marked with dashes (-):

AS5200# show modem 1/1
   Mdm  Typ  Status   Tx/Rx       G  Duration  TX  RX  RTS  CTS  DSR  DCD  DTR
   1/1   -   Idle    19200/19200  0  00:01:05   -   -   -    -    -    -    -
 
Modem 1/1, AS5200 Non-Manageable Modem
Firmware (Boot) Rev: Unknown
Modem config: Unknown
Management config: Not Manageable Modem

Last clearing of "show modem" counters never
- incoming completes, - incoming failures
- outgoing completes, - outgoing failures,
0 failed dial attempts, 0 ring no answers, 0 busied outs
0 no dial tones, 0 dial timeouts, 0 watchdog timeouts
- no carriers, - link failures, 0 resets
- protocol timeouts, - protocol errors, - lost events
 
                     2400-      2400-14400     14400+
# of connections       -             -           -

The following example displays the call switching module information for modem 1/2:

AS5200# show modem csm 1/2
MODEM_INFO: slot 1, port 2, unit 130, modem_mask=0x0004, modem_port_offset=0
tty_hwidb=0x00000000, modem_tty=0x004370A8, mgmt_tty=0x004370A8, modem_pool=0x0041D99C
csm_status(0): CSM_STATUS_UNLOCKED
csm_state(0x00000000)=CSM_OC_STATE, csm_event_proc=0x0005B448
invalid_event_count=0, wdt_timeout_count=0
wdt_timestamp_started is not activated
wait_for_dialing:False, wait_for_bchan:False
pri_chnl=TDM_ISDN_STREAM(s0, c0), modem_chnl=TDM_ISDN_STREAM(s0, c0)
dchan_idb_start_index=0, dchan_idb_index=0, call_id=0x0000, bchan_num=0
csm_event=CSM_EVENT_NONE, cause=0x0000, phone_num=
ring_indicator=0, oh_state=0, oh_int_enable=0, modem_reset=0
ring_no_answer=0, ic_failure=0, ic_complete=0
dial_failure=0, oc_failure=0, oc_complete=0
oc_busy=0, oc_no_dial_tone=0, oc_dial_timeout=0
remote_link_disc=0, busyout=0, modem_reset=0
call_duration_started=00:00:00, call_duration_ended=00:00:00, 
total_call_duration=00:00:00
The calling party phone number = 4082968388
The called party phone number = 4085267406

Table 8 describes the most useful fields in the previous display.

Table 8 : Show Modem Call Switching Module Field Descriptions

Field	Description
MODEM_INFO	Displays internal data structure information.
csm_status	Displays the status of the call switching module. Possible displays include unlocked, active call, busyout req, shutdown, bad modem, modem hold, back-to-back, file downloading, and reset.
csm_state	Displays the current state of the call switching module. Possible states include idle and connected. Incoming calls are marked IC and outgoing calls are marked OC.
Modem counters	Counters for different modem events.
The calling party phone number The called party phone number	Phone numbers for the dialing integrated modem and the remote modem.

The following example shows the event log status for a manageable modem and identifies the time elapsed since each modem event was performed (for example, 01:02:41 means the modem event occurred 1 hour, 2 minutes, and 41 seconds ago):

AS5200# show modem log 1/1
Modem 1/1 Events Log:
  00:02:41: Startup Response: Brasil Modem
            Modem (boot) firmware = 1.0.23 (1.0.5)
  00:02:41: Control Reply: 0xFE01
  00:02:41: RS232 event: 
            RTS=On, DTR=Off, CTS=On
            DSR=On, DCD=On, RI=Off, TST=Off
            changes: RTS=No change, DTR=Changed, CTS=Changed
            changes: DSR=Changed, DCD=Changed, RI=No change, TST=No change
  00:02:41: Modem Activity event: Data Active
  00:02:41: RS232 event: 
            RTS=On, DTR=Off, CTS=On
            DSR=On, DCD=On, RI=Off, TST=Off

            changes: RTS=No change, DTR=No change, CTS=No change
            changes: DSR=No change, DCD=No change, RI=No change, TST=No change
  00:02:42: Modem State event: Idle
  00:02:42: End connection event: Retransmits for MNP block (TX/RX) = 0/0
            Duration = 0:00:00, Number of TX/RX char = 0/0
            Local Disc Reason = Unknown, Remote Disc Reason = Unknown
  00:02:29: DTR event: DTR On
  00:02:29: RS232 event: 
            RTS=On, DTR=On, CTS=On
            DSR=On, DCD=On, RI=Off, TST=Off
            changes: RTS=No change, DTR=Changed, CTS=No change
            changes: DSR=No change, DCD=No change, RI=No change, TST=No change
  00:02:34: ISDN outgoing called number: 16664200
  00:02:34: Modem State event: Dialing/Answering
  00:02:22: Modem State event: Waiting for Carrier
  00:01:58: Modem State event: Connected
  00:01:58: Connection event: TX/RX Speed = 26400/26400, Modulation = V34
            Direction = Originate, Protocol = reliable/MNP, Compression = V42bis
  00:01:58: Modem Analog signal event: TX = -13, RX = -14, Signal to noise = -40
  00:01:58: RS232 event: 
            RTS=On, DTR=On, CTS=On
            DSR=On, DCD=Off, RI=Off, TST=Off
            changes: RTS=No change, DTR=No change, CTS=No change
            changes: DSR=No change, DCD=Changed, RI=No change, TST=No change
  00:00:57: Modem State event: Disconnecting
  00:00:57: Modem Activity event: Data Active
  00:00:57: End connection event: Retransmits for MNP block (TX/RX) = 0/0
            Duration = 0:00:59, Number of TX/RX char = 30/2061
            Local Disc Reason = Remote Link Disc, Remote Disc Reason = DTR Drop
  00:00:57: Modem State event: Idle

The following example shows the cumulative system statistics for all manageable modems on the access server:

AS5200# show modem summary
         Incoming calls       Outgoing calls      Busied   Failed   No    Succ
Usage  Succ   Fail  Avail   Succ   Fail  Avail    Out      Dial     Ans   Pct.
5%     2      0     12      0      0      0         0        0     0    100%

Table 9 describes the fields in the previous display.

Table 9 : Show Modem Summary Field Descriptions

Fields	Descriptions
Incoming and Outgoing calls	Calls dialing into and out of the modem. Usage---Percentage of the total system uptime that all the modems are in use. Succ---Total calls successfully connected. Fail---Total calls that did not successfully connect. Avail---Total modems available for use in the system.
Busied Out	Total number of times the modems were taken out of service with the modem busy command or the modem shutdown command.
Failed Dial	Total number of attempts the modems did not hang up or there was no dial tone.
No Ans	Total number of times call ringing was detected, but the calls were not answered by a modem.
Succ Pct.	Successful connection percentage of total available modems.

The following example shows the sample display for modem group 1, which is composed of modem 1/0 through modem 1/23:

AS5200# show modem group 1
              Incoming calls       Outgoing calls    Busied   Failed  No    Succ
Grp  Usage  Succ   Fail  Avail   Succ   Fail  Avail  Out      Dial    Ans   Pct.
1     0%     0      0     24      0      0     24       0        0    0     0%
 
Modem Group 1: 1/0, 1/1, 1/2, 1/3, 1/4, 1/5, 1/6, 1/7, 1/8, 1/9, 1/10, 1/11, 1/12, 1/13, 
1/14, 1/15, 1/16, 1/17, 1/18, 1/19, 1/20, 1/21, 1/22, 1/23

The following example shows all the directly connected sessions currently using the internal out-of-band ports on the integrated manageable modems:

AS5200# show modem at-mode
Active AT-MODE management sessions:
Modem    User's Terminal
1/1   0 cty 0

show tdm connections

To display a snapshot of the time division multiplexer (TDM) bus connection memory in an Cisco AS5200, use the show tdm connections EXEC command.

show tdm connections [motherboard | slot number]

Syntax Description

motherboard	(Optional) Motherboard in the Cisco AS5200.
slot number	(Optional) Slot number.

Command Mode

EXEC

Usage Guidelines

The show tdm connections command shows the connection memory for all TDM bus connections in the access server if you do not limit the display to the motherboard or a slot.

Sample Display

The following example shows source stream 3 (ST3) channel 2 switched out of stream 6 (ST6) channel 2:

AS5200# show tdm connections motherboard
MT8980 motherboard unit 0, Control Register = 0x1F, ODE Register = 0x06
Connection Memory for ST6:
Ch0:  0x62, Ch1:  0x00, Ch2:  0x00, Ch3:  0x00
Ch4:  0x00, Ch5:  0x00, Ch6:  0x00, Ch7:  0x00
Ch8:  0x00, Ch9:  0x00, Ch10: 0x00, Ch11: 0x00
Ch12: 0x00, Ch13: 0x00, Ch14: 0x00, Ch15: 0x00
Ch16: 0x00, Ch17: 0x00, Ch18: 0x00, Ch19: 0x00
Ch20: 0x00, Ch21: 0x00, Ch22: 0x00, Ch23: 0x00
Ch24: 0x00, Ch25: 0x00, Ch26: 0x00, Ch27: 0x00
Ch28: 0x00, Ch29: 0x00, Ch30: 0x00, Ch31: 0x00

To interpret the hexadecimal number 0x62 into meaningful information, you must translate it into binary code. These two hexadecimal numbers represent a connection from any stream and a channel on any stream. The number 6 translates into the binary code 0110, which represents the third-source stream. The number 2 translates into the binary code 0010, which represents the second-source channel.

Stream 6 (ST6) channel 0 is the destination for source stream 3 (ST3) channel 2 in this example.

show tdm data

To display a snapshot of the time division multiplexer (TDM) bus data memory in an Cisco AS5200, use the show tdm connections EXEC command.

show tdm data [motherboard | slot number]

Syntax Description

motherboard	(Optional) Motherboard in the Cisco AS5200.
slot number	(Optional) Slot number.

Command Mode

EXEC

Usage Guidelines

The data memory for all TDM bus connections in the access server is displayed if you do not specify a motherboard or slot.

Sample Display

The following example shows a snapshot of TDM memory where the normal ISDN idle pattern (0x7E) is present on all channels of the TDM device resident on the motherboard:

AS5200# show tdm data motherboard
MT8980 motherboard unit 0, Control Register = 0x1F, ODE Register = 0x06
Data Memory for ST0:
Ch0:  0x7E, Ch1:  0x7E, Ch2:  0x7E, Ch3:  0x7E
Ch4:  0x7E, Ch5:  0x7E, Ch6:  0x7E, Ch7:  0x7E
Ch8:  0x7E, Ch9:  0x7E, Ch10: 0x7E, Ch11: 0x7E
Ch12: 0x7E, Ch13: 0x7E, Ch14: 0x7E, Ch15: 0x7E
Ch16: 0x7E, Ch17: 0x7E, Ch18: 0x7E, Ch19: 0x7E
Ch20: 0x7E, Ch21: 0x7E, Ch22: 0x7E, Ch23: 0x7E
Ch24: 0x7E, Ch25: 0x7E, Ch26: 0x7E, Ch27: 0x7E
Ch28: 0x7E, Ch29: 0x7E, Ch30: 0x7E, Ch31: 0x7E
Data Memory for ST1:
Ch0:  0x7E, Ch1:  0x7E, Ch2:  0x7E, Ch3:  0x7E
Ch4:  0x7E, Ch5:  0x7E, Ch6:  0x7E, Ch7:  0x7E
Ch8:  0x7E, Ch9:  0x7E, Ch10: 0x7E, Ch11: 0x7E
Ch12: 0x7E, Ch13: 0x7E, Ch14: 0x7E, Ch15: 0x7E
Ch16: 0x7E, Ch17: 0x7E, Ch18: 0x7E, Ch19: 0x7E
Ch20: 0x7E, Ch21: 0x7E, Ch22: 0x7E, Ch23: 0x7E
Ch24: 0x7E, Ch25: 0x7E, Ch26: 0x7E, Ch27: 0x7E
Ch28: 0x7E, Ch29: 0x7E, Ch30: 0x7E, Ch31: 0x7E

test modem back-to-back

To diagnose a modem that may not be functioning properly in an Cisco AS5200, use the test modem back-to-back EXEC command.

test modem back-to-back {first-slot/modem-number} {second-slot/modem-number}

Syntax Description

first-slot/modem-number	Slot and modem number of the first test modem. Remember to include the forward slash (/) when entering this variable.
second-slot/modem-number	Slot and modem number of the second test modem. Remember to include the forward slash (/) when entering this variable.

Default

Disabled

Command Mode

EXEC

Usage Guidelines

Use this command to perform back-to-back testing of two modems. You might need to enable this command on several different combinations of modems to determine which one is not functioning properly.

Example

The following example shows how to perform a back-to-back modem test between modem 2/0 and modem 2/1 and removes modem 2/1, which is associated with TTY line 26, from all dial-in and dial-out services:

AS5200# test modem back-to-back 2/0 2/1
back2back 2/0 2/1
Repetitions (of 10-byte packets) [1]: 
AS5200#
%MODEM-5-B2BCONNECT: Modems (2/0) and (2/1) connected in back-to-back test: 
CONNECT9600/REL-MNPM
%MODEM-5-B2BMODEMS: Modems (2/0) and (2/1) completed back-to-back test: success/packets 
= 2/2

Related Command

modem bad

Update to Debug Command Reference

Add the following commands to the Cisco IOS Release 11.1 Debug Command Reference:

• debug modem csm
  

• debug modem oob
  

• debug modem trace
  

• debug tdm
  

debug modem csm

To debug an AS5200 modem's call switching module, use the debug modem csm EXEC command. Use the no form of this command to disable debug output.

debug modem csm [slot/modem-port | group group-number]
no debug modem csm [slot/modem-port | group group-number]

Syntax Description

slot/modem-port	(Optional) Slot and modem port number. Remember to include the forward slash (/) when entering this variable.
group group-number	(Optional) Modem group.

Command Mode

EXEC

Usage Guidelines

Use the debug modem csm command to troubleshoot call switching problems. Once you enable this command, the whole sequence of switching of incoming calls and outgoing calls can be traced on the screen.

Sample Displays

The following example shows call switching module (csm) trace output when the debug modem csm is configured and an incoming call enters the modem:

AS5200(config)# service timestamps debug uptime
AS5200(config)# end
AS5200# debug modem csm

Modem Management Call Switching Module debugging is on
AS5200#
00:04:09:  ccpri_ratetoteup bear rate is 10
00:04:09: CSM_MODEM_ALLOCATE: slot 1 and port 0 is allocated.
00:04:09: MODEM_REPORT(0001): DEV_INCALL at slot 1 and port 0
00:04:09: CSM_PROC_IDLE: CSM_EVENT_ISDN_CALL at slot 1, port 0
00:04:11: CSM_RING_INDICATION_PROC: RI is on
00:04:13: CSM_RING_INDICATION_PROC: RI is off
00:04:15: CSM_PROC_IC1_RING: CSM_EVENT_MODEM_OFFHOOK at slot 1, port 0

The following example shows csm trace output when the debug modem csm command is configured and an outgoing call is dialed from modem 1/2 into the network:

atdt16665202
00:11:21: CSM_PROC_IDLE: CSM_EVENT_MODEM_OFFHOOK at slot 1, port 2
00:11:21: T1_MAIL_FROM_NEAT: DC_READY_RSP: mid = 1, slot = 0, unit = 0
00:11:21: CSM_PROC_OC1_REQUEST_DIGIT: CSM_EVENT_DIGIT_COLLECT_READY at slot 1, port 2
00:11:24: T1_MAIL_FROM_NEAT: DC_FIRST_DIGIT_RSP: mid = 1, slot = 0, unit = 0
00:11:24: CSM_PROC_OC2_COLLECT_1ST_DIGIT: CSM_EVENT_GET_1ST_DIGIT at slot 1, port 2
00:11:27: T1_MAIL_FROM_NEAT: DC_ALL_DIGIT_RSP: mid = 1, slot = 0, unit = 0
00:11:27: CSM_PROC_OC3_COLLECT_ALL_DIGIT: CSM_EVENT_GET_ALL_DIGITS (16665202) at slot 1, 
port 2
00:11:27:  ccpri_ratetoteup bear rate is 10
00:11:27: MODEM_REPORT(A000): DEV_CALL_PROC at slot 1 and port 2
00:11:27: CSM_PROC_OC4_DIALING: CSM_EVENT_ISDN_BCHAN_ASSIGNED at slot 1, port 2

debug modem oob

To debug an AS5200 modem's out-of-band port, use the debug modem oob EXEC command. Use the no form of this command to disable debug output.

debug modem oob [slot/modem-port | group group-number]
no debug modem oob [slot/modem-port | group group-number]

Syntax Description

slot/modem-port	(Optional) Slot and modem port number. Remember to include the forward slash (/) when entering this variable.
group group-number	(Optional) Modem group.

Command Mode

EXEC

Usage Guidelines

Entering the debug modem oob command without specifying a slot and modem number debugs all out-of-band ports in the AS5200, which produces an excessive amount of output information.

The message types and sequence numbers that appear in the command's output are initiated by the modem oob protocol and used by software developers for debugging purposes.

Sample Display

The following example debugs the out-of-band port on modem 2/0, which creates modem startup messages between the network management software and the modem:

AS5200# debug modem oob 2/0
MODEM(2/0): One message sent --Message type:3, Sequence number:0
MODEM(2/0): Modem DC session data reply
MODEM(2/0): One mes%sage sent --Message type:83, Sequence number:1
MODEM(2/0): DC session event = 
MODEM(2/0): One message sent --Message type:82, Sequence number:2
MODEM(2/0): No status changes since last polled
MODEM(2/0): One message sent --Message type:3, Sequence number:3
MODEM(2/0): Modem DC session data reply
MODEM(2/0): One message sent --Message type:83, Sequence number:4

debug modem trace

To debug an AS5200 modem's call trace, use the debug modem trace EXEC command. Use the no form of this command to disable debug output.

debug modem trace [normal | abnormal | all] [slot/modem-port | group group-number]
no debug modem trace [normal | abnormal | all] [slot/modem-port | group group-number]

Syntax Description

normal	(Optional) Uploads the call trace to the syslog server on normal call termination (for example, a local user hangup or a remote user hangup).
abnormal	(Optional) Uploads the call trace to the syslog server on abnormal call termination (for example, any call termination other than normal termination, such as a lost carrier or a watchdog timeout).
all	(Optional) Uploads the call trace on all normal and abnormal call termination.
slot/modem-port	(Optional) Slot and modem port number. Remember to include the forward slash (/) when entering this variable.
group group-number	(Optional) Modem group.

Command Mode

EXEC

Usage Guidelines

The debug modem trace command applies only to manageable modems, which are modems that support modem polling and sending AT commands.

Sample Display

The following example is sample output from the debug modem trace abnormal command:

AS5200# debug modem trace abnormal 1/14

Modem 1/14 Abnormal End of Connection Trace. Caller 123-4567
    Start-up Response: AS5200 Modem, Firmware 1.0
    Control Reply: 0x7C01
    DC session response: brasil firmware 1.0
    RS232 event:
    DSR=On, DCD=On, RI=Off, TST=Off
    changes: RTS=No change, DTR=No change, CTS=No change
    changes: DSR=No change, DCD=No change, RI=No change, TST=No change
    Modem State event: Connected
    Connection event: Speed = 19200, Modulation = VFC
    Direction = Originate, Protocol = reliable/LAPM, Compression = V42bis
    DTR event: DTR On
    Modem Activity event: Data Active
    Modem Analog signal event: TX = -10, RX = -24, Signal to noise = -32
    End connection event: Duration = 10:34-11:43,
    Number of xmit char =       67, Number of rcvd char = 88, Reason: Watchdog Time-out.

debug tdm

To display time division multiplexer (TDM) bus connection information each time a connection is made on the Cisco AS5200, use the debug tdm EXEC command. Use the no form of this command to disable debug output.

debug tdm
no debug tdm

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

Usage Guidelines

If you are losing channel data between the dual T1 Primary Rate Interfaces (PRI) and any termination points, such as an Ethernet or modem point, enable the debug tdm command.

This command displays the TDM bus connection information for each TDM device installed in the access server. One TDM device exists on the PRI board, on the motherboard, and on each modem board. Expect up to 256 TDM connections to be displayed on your terminal when this command is enabled.

Example

The following example enables the debug tdm command:

debug tdm
dialtone connection requested.
TDM(reg: 0x2138100): Close connection to STo7, channel 1
TDM(reg: 0x2138100): Connect STi3, channel 1 to STo7, channel 1

Cisco Connection Online (CCO)

Cisco Connection Online (CCO), formerly Cisco Information Online (CIO), is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional content and services.

Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco's customers and business partners. CCO services include product information, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.

CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously---a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CCO supports Zmodem, Kermit, Xmodem, FTP, Internet e-mail, and fax download options, and is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.

You can access CCO in the following ways:

• WWW: http://www.cisco.com.
  

• Telnet: cco.cisco.com.
  

• Modem: From North America, 408 526-8070; from Europe, 33 1 64 46 40 82. Use the following terminal settings: VT100 emulation; databits: 8; parity: none; stop bits: 1; and baud rates up to 14.4 kbps.
  

For a copy of CCO's Frequently Asked Questions (FAQ), contact ccohelp@cisco.com. For additional information, contact ccoteam@cisco.com.