Table Of Contents
Monitoring Resource Availability on Cisco AS5300, AS5400, and AS5800 Universal Access Servers
Supported Standards, MIBs, and RFCs
Enabling ISDN PRI Requested Channel Not Available Traps
Monitoring Resource Availability on Cisco AS5300, AS5400, and AS5800 Universal Access Servers
November 27, 2000
This feature module describes enhancements to improve visibility into the line and modem status for the network access server (NAS).
This document includes the following sections:
•
Supported Standards, MIBs, and RFCs
Feature Overview
NAS modem health is supported by the following features:
•
The purpose of these combined feature enhancements is to monitor and maintain NAS modem health. These features have been developed to monitor the NAS health conditions at the digital signal level zero (DS-0) level, PRI bearer channel level, and modem level.
DS-0 Busyout Traps
DS-0 busyout traps are generated when there is a request to busyout a DS-0, when there is a request to take a DS-0 out of busyout mode, or when busyout completes and the DS-0 is out-of-service. DS-0 busyout traps are generated at the DS-0 level for both channel associated signaling (CAS) and ISDN configured lines. This feature is enabled and disabled by command-line interface (CLI) and MIBs. DS-0 busyout traps are disabled by default and are supported on Cisco AS5300, Cisco AS5400, and Cisco AS5800 universal access servers.
Modem Health Traps
Modem health traps are generated when a modem port is bad, disabled, reflashed, or shut down, or when there is a request to busyout the modem. This feature is enabled and disabled by CLI and the CISCO-MODEM-MGMT-MIB. Modem health traps are disabled by default and are supported on the Cisco AS5300, Cisco AS5400, and Cisco AS5800.
ISDN PRI Requested Channel Not Available Traps
ISDN PRI channel not available traps are generated when a requested DS-0 channel is not available, or when there is no modem available to take the incoming call. This feature is available only for ISDN PRI interfaces. This feature is enabled and disabled by CLI for ISDN traps and the CISCO-ISDN-MIB. ISDN PRI channel not available traps are disabled by default and are supported on the Cisco AS5300, Cisco AS5400, and Cisco AS5800.
Show Controllers Timeslots
The show controllers command is augmented with the keyword timeslots to display the channel state in detail. This feature shows whether the DS-0 channels of a particular controller are in idle, in-service, maintenance, or busyout state. This enhancement applies to both CAS and ISDN PRI interfaces and is supported on the Cisco AS5300 and Cisco AS5400 only.
DS-1 Loopback Traps
DS-1 loopback traps are generated when a DS-1 line goes into loopback mode. This feature is enabled and disabled by CLI and the CISCO-POP-MGMT-MIB. DS-1 loopback traps are disabled by default and are supported on the Cisco AS5300 and Cisco AS5400 only.
Benefits
•
•
Restrictions
Customers must provide their own management tools.
Related Documents
•
•
•
•
•
•
•
•
Supported Platforms
•
•
•
Supported Standards, MIBs, and RFCs
Standards
No new or modified standards are supported by this feature.
MIBs
•
•
•
•
To obtain lists of supported MIBs by platform and Cisco IOS release, and to download MIB modules, go to the Cisco MIB web site on Cisco Connection Online (CCO) at
http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml.RFCs
No new or modified RFCs are supported by this feature.
Prerequisites
The SNMP manager must already have been installed on your workstation, and the SNMP agent must be configured on the NAS by entering the following commands:
snmp-server community public ROsnmp-server host 10.1.2.3 publicRefer to the Cisco IOS Configuration Guide Master Index, Release 12.1T for more information about these commands.
Enabling Tasks
The following sections contain NAS modem health feature enabling tasks.
•
•
•
•
Enabling DS-0 Busyout Traps
To generate DS-0 busyout traps, enter the following command in global configuration mode.
Generates a trap when there is a request to busyout a DS-0 or to indicate when busyout finishes.
Enabling ISDN PRI Requested Channel Not Available Traps
To generate ISDN PRI requested channel not available traps, enter the following command in global configuration mode.
Generates a trap when the NAS rejects an incoming call on an ISDN PRI interface because the channel is not available.
Enabling Modem Health Traps
To generate modem health traps, enter the following command in global configuration mode.
Enabling DS-1 Loopback Traps
To generate DS-1 loopback traps, enter the following command in global configuration mode.
Generates a trap when the DS-1 line goes into loopback mode.
Verifying Enabled Traps
Use the show run command to verify that the traps are enabled. The following output indicates that all the traps are enabled:
Router(config)# show runsnmp-server enable traps ds0-busyoutsnmp-server enable traps isdn chan-not-availsnmp-server enable traps modem-healthsnmp-server enable traps ds1-loopbackTroubleshooting Tips
To troubleshoot the traps, turn on the debug switch for SNMP packets by entering the following in privileged EXEC mode:
Router# debug snmp packetsCheck the resulting output to see that the SNMP trap information packet is being sent. The output will vary based on the kind of packet sent or received:
Router# debug snmp packetsSNMP: Packet received via UDP from 10.5.4.1 on Ethernet0SNMP: Get-next request, reqid 23584, errstat 0, erridx 0sysUpTime = NULL TYPE/VALUEsystem.1 = NULL TYPE/VALUEsystem.6 = NULL TYPE/VALUESNMP: Response, reqid 23584, errstat 0, erridx 0sysUpTime.0 = 2217027system.1.0 = Cisco Internetwork Operating System Softwaresystem.6.0 =SNMP: Packet sent via UDP to 10.5.4.1You can also use trap monitoring and logging tools like snmptrapd, with debugging flags turned on, to monitor output.
Configuration Examples
This section shows sample configuration output with all the traps turned on:
Building configuration...Current configuration:!! Last configuration change at 12:27:30 pacific Thu May 25 2000!version 12.1service timestamps debug uptimeservice timestamps log uptimeno service password-encryption!hostname router!aaa new-modelaaa authentication ppp default group radiusenable password <password>!spe 1/0 1/7firmware location system:/ucode/mica_port_firmwarespe 2/0 2/7firmware location system:/ucode/mica_port_firmware!!resource-pool disable!!!!!clock timezone PDT -8clock calendar-validno modem fast-answermodem country mica usamodem link-info poll time 60modem buffer-size 300ip subnet-zero!isdn switch-type primary-5essisdn voice-call-failure 0!!!controller T1 0framing esfclock source line primarylinecode b8zspri-group timeslots 1-24!controller T1 1framing esflinecode b8zsds0-group 0 timeslots 1-24 type e&m-fgbcas-custom 0!controller T1 2shutdownclock source line secondary 2!controller T1 3shutdownclock source line secondary 3!controller T1 4shutdownclock source line secondary 4!controller T1 5shutdownclock source line secondary 5!controller T1 6shutdownclock source line secondary 6!controller T1 7shutdownclock source line secondary 7!!!interface Loopback0ip address 10.5.4.1!interface Ethernet0no ip addressshutdown!interface Serial0no ip addressshutdown!interface Serial1no ip addressshutdown!interface Serial2no ip addressshutdown!interface Serial3no ip addressshutdown!interface Serial0:23no ip addressip mroute-cacheisdn switch-type primary-5essisdn incoming-voice modemno cdp enable!interface FastEthernet0ip address 10.5.4.1duplex fullspeed autono cdp enable!interface Group-Async1ip unnumbered FastEthernet0encapsulation pppip tcp header-compression passiveno ip mroute-cacheasync mode interactivepeer default ip address pool swattestno fair-queueppp authentication chapppp multilinkgroup-range 1 192!interface Dialer1ip unnumbered FastEthernet0encapsulation pppip tcp header-compression passivedialer-group 1peer default ip address pool swattestpulse-time 0no cdp enable!ip local pool swattest 10.5.4.1ip default-gateway 10.5.4.1ip classless!dialer-list 1 protocol ip permitsnmp-server engineID local 00000009020000D058890CF0snmp-server community public ROsnmp-server packetsize 2048snmp-server enable traps ds0-busyoutsnmp-server enable traps isdn chan-not-availsnmp-server enable traps modem-healthsnmp-server enable traps ds1-loopbacksnmp-server host 10.5.4.1 public!radius-server host 10.5.4.1 auth-port 1645 acct-port 1646radius-server retransmit 3radius-server key <password>!!line con 0transport input noneline 1 192autoselect pppmodem InOuttransport preferred nonetransport input alltransport output noneline aux 0line vty 0 4endCommand Reference
This section documents new or modified commands that support NAS modem health. All other commands used with this feature are documented in the Cisco IOS Release 12.1 command reference publications.
show controllers
To show the channel associated signaling (CAS) and ISDN PRI state in detail, use the show controllers timeslots privileged EXEC command.
show controllers t1/e1 controller number timeslots timeslot range
Syntax Description
controller number
Controller number of CAS or ISDN PRI time slot. Range 0 through 7.
timeslot range
Time slot range 1 through 31 for E1, 1 through 24 for T1.
Defaults
This command is disabled by default.
Command Modes
EXEC
Command History
10.0
This command was introduced.
12.1(3)T
The timeslots keyword was added.
12.1(5)T
Support for Cisco AS5400 universal access servers was added.
Usage Guidelines
Use the show controllers t1/e1 timeslots command to display the CAS and ISDN PRI channel state in detail. This command shows whether the DS-0 channels of a controller are in idle, in-service, maintenance, or busyout states. Enter the show controllers t1/e1 command to display statistics about the T1 or E1 links.
Examples
The following example shows that the CAS state is enabled on the Cisco AS5300 with a T1 PRI card:
DA-Slot1# show controllers t1 1 timeslots 1-24T1 1 is up:Loopback: NONEDS0 Type Modem <-> Service Channel Rx TxState State A B C D A B C D-----------------------------------------------------------------------------------------1 cas-modem 1 in insvc connected 1 1 1 1 1 1 1 12 cas - - insvc idle 0 0 0 0 0 0 0 03 cas - - insvc idle 0 0 0 0 0 0 0 04 cas - - insvc idle 0 0 0 0 0 0 0 05 cas - - insvc idle 0 0 0 0 0 0 0 06 cas - - insvc idle 0 0 0 0 0 0 0 07 cas - - insvc idle 0 0 0 0 0 0 0 08 cas - - insvc idle 0 0 0 0 0 0 0 09 cas - - insvc idle 0 0 0 0 0 0 0 010 cas - - maint static-bo 0 0 0 0 1 1 1 111 cas - - maint static-bo 0 0 0 0 1 1 1 112 cas - - maint static-bo 0 0 0 0 1 1 1 113 cas - - maint static-bo 0 0 0 0 1 1 1 114 cas - - maint static-bo 0 0 0 0 1 1 1 115 cas - - maint static-bo 0 0 0 0 1 1 1 116 cas - - maint static-bo 0 0 0 0 1 1 1 117 cas - - maint static-bo 0 0 0 0 1 1 1 118 cas - - maint static-bo 0 0 0 0 1 1 1 119 cas - - maint dynamic-bo 0 0 0 0 1 1 1 120 cas - - maint dynamic-bo 0 0 0 0 1 1 1 121 cas - - maint dynamic-bo 0 0 0 0 1 1 1 122 unused23 unused24 unusedThe following example shows that the ISDN PRI state is enabled on the Cisco AS5300 with a T1 PRI card:
Router# show controller t1 2 time 1-24T1 2 is up:Loopback: NONEDS0 Type Modem <-> Service Channel Rx TxState State A B C D A B C D---------------------------------------------------------------------------1 pri - - insvc idle2 pri - - insvc idle3 pri - - insvc idle4 pri - - insvc idle5 pri - - insvc idle6 pri - - insvc idle7 pri - - insvc idle8 pri - - insvc idle9 pri - - insvc idle10 pri - - insvc idle11 pri - - insvc idle12 pri - - insvc idle13 pri - - insvc idle14 pri - - insvc idle15 pri - - insvc idle16 pri - - insvc idle17 pri - - insvc idle18 pri - - insvc idle19 pri - - insvc idle20 pri - - insvc idle21 pri-modem 2 in insvc busy22 pri-modem 1 out insvc busy23 pri-digi - in insvc busy24 pri-sig - - outofsvc reservedsnmp-server enable traps
To enable the router to send SNMP traps and information, use the snmp-server enable traps global configuration command. Use the no form of this command to disable SNMP notifications.
snmp-server enable traps [notification-type] [notification-option]
no snmp-server enable traps [notification-type] [notification-option]
Syntax Description
Defaults
This command is disabled by default. Most notification types are disabled. However, some notification types cannot be controlled with this command. For example, some notification types are always enabled. Other notification types are enabled by a different command. For example, the linkUpDown notifications are controlled by the snmp trap link-status command.
If you enter this command with no notification-type keywords, the default is to enable all notification types controlled by this command.
Command Modes
Global configuration
Command History
Usage Guidelines
This command is useful for disabling notifications that are generating a large amount of uninteresting or useless noise.
SNMP notifications can be sent as traps or inform requests. This command enables both traps and inform requests for the specified notification types.
If you do not enter an snmp-server enable traps command, no notifications controlled by this command are sent. In order to configure the router to send these SNMP notifications, you must enter at least one snmp-server enable traps command. If you enter the command with no keywords, all notification types are enabled. If you enter the command with a keyword, only the notification type related to that keyword is enabled. In order to enable multiple types of notifications, you must issue a separate snmp-server enable traps command for each notification type and notification option.
The snmp-server enable traps command is used in conjunction with the snmp-server host command. Use the snmp-server host command to specify which host or hosts receive SNMP notifications. In order to send notifications, you must configure at least one snmp-server host command.
For a host to receive a notification controlled by this command, both the snmp-server enable traps command and the snmp-server host command for that host must be enabled. If the notification type is not controlled by this command, only the appropriate snmp-server host command must be enabled.
The notification types used in this command all have an associated MIB object that allows them to be globally enabled or disabled. Not all of the notification types available in the snmp-server host command have notificationEnable MIB objects, so some of these notification types cannot be controlled using the snmp-server enable command.
Examples
The following example enables the router to send all traps to the host specified by the name myhost.cisco.com, using the community string defined as "public":
snmp-server enable trapssnmp-server host myhost.cisco.com publicThe following example enables the router to send Frame Relay and environmental monitor traps to the host myhost.cisco.com using the community string "public":
snmp-server enable traps frame-relaysnmp-server enable traps envmon temperaturesnmp-server host myhost.cisco.com publicThe following example does not send traps to any host. The BGP traps are enabled for all hosts, but the only traps enabled to be sent to a host are ISDN traps (which are not enabled in this example).
snmp-server enable traps bgpsnmp-server host bob public isdnThe following example enables the router to send all inform requests to the host labeled myhost.cisco.com using the community string defined as "public":
snmp-server enable trapssnmp-server host myhost.cisco.com informs version 2c publicThe following example sends HSRP MIB traps to the host myhost.cisco.com using the community string "public."
snmp-server enable hsrpsnmp-server host myhost.cisco.com traps version 2c public hsrpGlossary
CLI—command-line interface. Interface that allows the user to interact with the operating system by entering commands and optional arguments. The UNIX operating system and DOS provide CLIs. Compare with GUI.
DS-0—Digital signal level zero. Framing specification used in transmitting digital signals over a single channel at 64 kbps on a T1 facility. Compare with DS-1.
DS-1—Digital signal level. Framing specification used in transmitting digital signals at 1.544 Mbps on a T1 facility (in the United States) or at 2.108 Mbps on an E1 facility (in Europe). Compare with DS-0.
DSX-1—Cross-connection point for DS-1 signals.
MIB—Management Information Base. Database of network management information that is used and maintained by a network management protocol such as SNMP or CMIP. The value of a MIB object can be changed or retrieved using SNMP or Common Management Information Protocol (CMIP) commands, usually through a GUI network management system. MIB objects are organized in a tree structure that includes public (standard) and private (proprietary) branches.
NAS—Network access server. A Cisco platform system (or collection of platforms) that interfaces between a packet environment and a circuit environment. A type of access device.
Guest