Dial Configuration Guide, Cisco IOS Release 15.5M&T

Split Dial Shelves Feature

The split dial shelves feature provides for doubling the throughput of the Cisco AS5800 access server by splitting the dial shelf slots between two router shelves, each router connected to one Dial Shelf Controller (DSC), two of which must be installed in the system. Each router shelf is configured to control a certain set from the range of the dial shelf slots. Each router shelf will operate as though any other slots in the dial shelf contained no cards, even if there is a card in them, because they are controlled by the other router shelf. Thus the configuration on each router shelf would affect only the “owned” slots.

Each router shelf should own modem cards and trunk cards. Calls received on a trunk card belonging to one router shelf cannot be serviced by a modem card belonging to the other router shelf. Each router shelf operates like a single Cisco AS5800 access server system, as if some slots are unavailable.

Refer to the section “Configuring Dial Shelf Split Mode” for more information about configuring split dial shelves.

Configuring the Shelf ID

The Cisco AS5800 consists of a router shelf and a dial shelf. To distinguish the slot/port number on the Cisco AS5800, you must specify the shelf number. The default shelf number is 0 for the router shelf and 1 for the dial shelf.

Caution You must reload the Cisco AS5800 for the new shelf number to take effect. Because the shelf number is part of the interface names when you reload, all NVRAM interface configuration information is lost.

---

Normally you do not need to change the shelf IDs; however, if you do, we recommend that you change the shelf number when you initially access the setup facility. For information on the setup facility, refer to the Cisco AS5800 Universal Access Server Software Installation and Configuration Guide.

If you are booting the router shelf from the network (netbooting), you can change the shelf numbers using the shelf-id command.

To configure the dial shelf, you save and verify the configuration in EXEC mode, and enter shelf-id commands in global configuration mode, as indicated in the following steps:

If you are booting the router shelf from Flash memory, use the following commands beginning in EXEC mode:

Configuring Redundant DSC Cards

The Redundant Dial Shelf Controller feature consists of two DSC cards on a Cisco AS5800 dial shelf. The DSC cards provide clock and power control to the dial shelf cards. Each DSC card provides the following:

• Master clock for the dial shelf
• Fast Ethernet link to the router shelf
• Environmental monitoring of the feature boards
• Bootstrap images on start-up for the feature boards

The Redundant Dial Shelf Controller feature is automatically enabled when two DSC cards are installed. DSC redundancy is supported with Cisco AS5800 software at the Dial Shelf Interconnect Protocol (DSIP) level.

This feature enables a Cisco AS5800 dial shelf to use dual DSCs for full redundancy. A redundant configuration allows for one DSC to act as backup to the active card, should the active card fail. This increases system availability by preventing loss of service. The redundant DSC functionality is robust under high loads and through DSC or software crashes and reloads. The redundant DSC functionality is driven by the following events:

• User actions
• Control messages
• Timeouts
• Detection of component failures
• Error and warning messages

DSC redundancy provides maximum system availability by preventing loss of service if one of the DSCs fails. There is no load sharing between the Broadband Inter-Carrier Interfaces (BICI). One BIC is used as a backup, carrying only control traffic, such as keepalives, until there is a switchover.

Before starting this configuration task:

• Your Cisco AS5800 router shelf and dial shelf must be fully installed, with two DSC cards installed on the dial shelf.
• Your Cisco AS5800 access server must be running Cisco IOS Release 12.1(2)T.
• The external DSC clocking port must be configured identically on both router shelves and must be physically connected to both DSCs. This assures that if a DSC card needs replacing or if the backup DSC card becomes primary, clocking remains stable.

Synchronizing to the System Clocks

The time-division multiplexing (TDM) bus in the backplane on the dial shelf must be synchronized to the T1/E1 clocks on the trunk cards. The Dial Shelf Controller (DSC) card on the daily shelf provides hardware logic to accept multiple clock sources as input and use one of them as the primary source to generate a stable, PPL synchronized output clock. The input clock can be any of the following sources:

• Trunk port in slots 0 through 5—up to 12 can be selected (2 per slot)
• An external T1 or E1 clock source fed directly through a connector on the DSC card
• A free-running clock from an oscillator in the clocking hardware on the DSC card

For dual (redundant) DSC cards, the external DSC clocking port should be configured so that the clock signal fed into both DSCs is identical.

To configure the external clocks, use the following commands from the router shelf login beginning in global configuration mode. One external clock is configured as the primary clock source, and the other is configured as the backup clock source.

Verifying External Clock Configuration

To verify that the primary clock is running, enter the show dial-shelf clocks privileged EXEC command:

For more information on configuring external clocks, refer to the Cisco document Managing Dial Shelves.

Configuring Dial Shelf Split Mode

This section describes the procedure required to transition a router from normal mode to split mode and to change the set of slots a router owns while it is in split mode. Since the process of switching the ownership of a slot from one router to the other is potentially disruptive (when a feature board is restarted, all calls through that card are lost), a router shelf cannot take over a slot until ownership is relinquished by the router that currently claims ownership, either by reconfiguring the router or disconnecting that router or its associated DSC.

The dial shelf is split by dividing the ownership of the feature boards between the two router shelves. You must configure the division of the dial shelf slots between the two router shelves so that each router controls an appropriate mix of trunk and modem cards. Each router shelf controls its set of feature boards as if those were the only boards present. There is no interaction between feature boards owned by one router and feature boards owned by the other router.

Split mode is entered when the dial-shelf split slots command is parsed on the router shelf. This can occur when the router is starting up and parsing the stored configuration, or when the command is entered when the router is already up. Upon parsing the dial-shelf split slots command, the router frees any resources associated with cards in the slots that it no longer owns, as specified by exclusion of slot numbers from the slot-numbers argument. The router should be in the same state as if the card had been removed from the slot; all calls through that card will be terminated. The configured router then informs its connected DSC that it is in split mode, and which slots it claims to own.

In split mode, a router shelf by default takes half of the 2048 available TDM timeslots. The TDM split mode is configured using the dial-shelf split backplane-ds0 command. (The dial-shelf split slot command must be defined for the dial-shelf split backplane-ds0 command to be active.) If the dial-shelf split slots command is entered when the total number of calls using timeslots exceeds the number that would normally be available to the router in split mode, the command is rejected. This should occur only when a change to split mode is attempted, in which the dial shelf has more than 896 calls in progress (more than half of the 1,792 available timeslots). Otherwise, a transition from normal mode to split mode can be made without disturbing the cards in the slots that remain owned, and calls going through those cards will stay up.

To configure a router for split dial shelf operation, perform the following steps:

Step 1 Ensure that both DSCs and both router shelves are running the same Cisco IOS image.

Note Having the same version of Cisco IOS running on both DSCs and both router shelves is not mandatory; however, it is a good idea. There is no automatic checking that the versions are the same.

Step 2 Schedule a time when the Cisco AS5800 can be taken out of service without unnecessarily terminating calls in progress. The entire procedure for transitioning from normal mode to split mode should require approximately one hour if all the hardware is already installed.

Step 3 Busy out all feature boards and wait for your customers to log off.

Step 4 Reconfigure the existing router shelf to operate in split mode.

Step 5 Enter the dial-shelf split slots command, specifying the slot numbers that are to be owned by the existing router shelf.

Step 6 Configure the new router shelf to operate in split mode on other feature boards.

Step 7 Enter the dial-shelf split slots command, specifying the slot numbers that are to be owned by the new router shelf. Do not specify any of the slot numbers that you specified in Step 6. The range of valid slot numbers is 0 through 11.

To perform this step, enter the following command in global configuration mode:

Step 8 Install the second DSC, if it has not already been installed.

Step 9 Connect the DSIP cable from the second DSC to the new router shelf.

Step 10 Ensure that split mode is operating properly.

Enter the show dial-shelf command for each router. This command has been extended so that the response indicates that the router shelf is running in split mode and which slots the router shelf owns. The status of any cards in any owned slots is shown, just as they are in the present show dial-shelf command. When in split mode, the output will be extended as in the following example:

Step 11 Enable all feature boards to accept calls once again.

Changing Slot Sets

You can change the sets of slots owned by the two router shelves while they are in split mode by first removing slots from the set owned by one router, and then adding them to the slot set of the other router. The changed slot set information is sent to the respective DSCs, and the DSCs determine which slots have been removed and which added from the new slot set information. It should be clear that moving a slot in this manner will disconnect all calls that were going through the card in that slot.

To perform this task, enter the following commands as needed:

When a Slot Is Removed

The router shelf that is losing the slot frees any resources and clears any state associated with the card in the slot it is relinquishing. The DSC reconfigures its hub to ignore traffic from that slot, and if there is a card in the slot, it will be reset. This ensures that the card frees up any TDM resource it might be using and allows it to restart under control of the router shelf that is subsequently configured to own the slot.

When a Slot Is Added

If there are no configuration conflicts, and there is a card present in the added slot, a dial-shelf OIR insertion event is sent to the router shelf, which processes the event the same as it always does. The card in the added slot is reset by the DSC to ensure a clean state, and the card downloads its image from the router shelf that now owns it.

If the other router shelf and the other DSC claim ownership of the same slot, the command adding the slot should be rejected. However, should a configuration conflict exist, error messages are sent to both routers and the card is not reset until one of the other router shelves and its DSC stop claiming ownership of the slot. Normally, this will not happen until you issue a dial-shelf split slots remove command surrendering the ownership claim on the slot by one of the routers.

Leaving Split Mode

Split mode is exited when the dial shelf configuration is changed by a no dial-shelf split slots command. When the split dial shelf line is removed, the router shelf will start using all of the TDM timeslots. Feature boards that were not owned in split mode and that are not owned by the other router will be reset. Cards in slots that are owned by the other router will be reset, but only after the other DSC has been removed or is no longer claiming the slots. The split dial shelf configuration should not be removed while the second router shelf is still connected to the dial shelf.

When a router configured in split mode fails, all calls associated with the failed router are lost. Users cannot connect back in until the failed router recovers and is available to accept new incoming calls; however, the other split mode router shelf will continue to operate normally.

Troubleshooting Split Dial Shelves

The system will behave as configured as soon as the configuration is changed. The exception is when there is a misconfiguration, such as when one router is configured in split mode and the other router is configured in normal mode, or when both routers are configured in split mode and both claim ownership of the same slots.

Problems can arise if one of the two routers connected to a dial shelf is not configured in split mode, or if both are configured in split mode and both claim ownership of the same slots. If the state of the second router is known when the dial-shelf split slots command is entered and the command would result in a conflict, the command is rejected.

If a conflict in slot ownership does arise, both routers will receive warning messages until the conflict is resolved. Any card in a slot which is claimed by both routers remains under the control of the router that claimed it first, until you can resolve the conflict by correcting the configuration of one or both routers.

It should be noted that there can also be slots that are not owned by either router (orphan slots). Cards in orphan slots cannot boot up until one of the two routers claims ownership of the slot because neither DSC will download bootstrap images to cards in unowned orphan slots.

Managing a Split Dial Shelf

If you are installing split dial shelf systems, a system controller is available that provides a single system view of multiple point of presences (POPs). The system controller for the Cisco AS5800 Universal Access Server includes the Cisco 3640 router running Cisco IOS software. The system controller can be installed at a remote facility so that you can access multiple systems through a console port or Web interface.

There are no new MIBs or MIB variables required for the split dial shelf configuration. A split dial shelf appears to Simple Network Management Protocol (SNMP) management applications as two separate Cisco AS5800 systems. One console to manage the whole system is not supported—you must have a console session per router shelf (two console sessions) to configure each split of the Cisco AS5800. The system controller must manage a split dial shelf configuration as two separate Cisco AS5800 systems.

The normal mode configuration of the Cisco AS5800 requires the dial shelf and router shelf IDs to be different. In a split system, four unique shelf IDs are desirable, one for each router shelf and one for each of the slot sets; however, a split system will function satisfactorily if the router shelf IDs are the same. If a system controller is used to manage a split dial shelf configuration, the two routers must have distinct shelf IDs, just as they must when each router has its own dial shelf.

You can download software configurations to any Cisco AS5800 using SNMP or a Telnet connection. The system controller also provides performance monitoring and accounting data collection and logging.

In addition to the system controller, a network management system with a graphical user interface (GUI) runs on a UNIX SPARC station and includes a database management system, polling engine, trap management, and map integration.

To manage a split dial shelf, enter the following commands in EXEC mode as needed:

Executing Commands Remotely

Although not recommended, it is possible to connect directly to the system console interface in the DSC to execute dial shelf configuration commands. All commands necessary for dial shelf configuration, and show, and debug command tasks can be executed remotely from the router console. A special command, execute-on, is provided for this purpose. This command enables a special set of EXEC mode commands to be executed on the router or the dial shelf. This command is a convenience that avoids connecting the console to the DSC. For a list of commands you can execute using execute-on, refer to the command description in the Cisco IOS Dial Technologies Command Reference.

To enter a command that you wish to execute on a specific card installed in the dial shelf while logged onto the router shelf console, use the following commands in privileged EXEC mode as needed:

Verifying DSC Configuration

To verify that you have started the redundant DSC feature, enter the show redundancy privileged EXEC command:

Monitoring and Maintaining the DSCs

To monitor and maintain the DSC cards, use the following commands in privileged EXEC mode, as needed:

Troubleshooting DSIP

There are a number of show commands available to aid in troubleshooting dial shelves. Use the following EXEC mode commands to monitor DSI and DSIP activity as needed:

The privileged EXEC mode show dsi command can also be used to troubleshoot, as it displays the status of the DSI adapter, which is used to physically connect the router shelf and the dial shelf to enable DSIP communications.

The following is an example troubleshooting scenario:

Problem: The router shelf boots, but there is no communication between the router and dial shelves.

Step 1 Run the show dsip transport command.

Step 2 Check the “DSIP registered addresses” column. If there are zero entries there, there is some problem with the Dial Shelf Interconnect (DSI). Check if the DSI is installed in the router shelf.

Step 3 If there is only one entry and it is our own local address, then first sanity check the physical layer. Make sure that there is a physical connection between the RS and DS. If everything is fine from cabling point of view, go to step 3.

Step 4 Check the DSI health by issuing the show dsi command. This gives a consolidated output of DSI controller and interface. Check for any errors like runts, giants, throttles and other usual FE interface errors.

Diagnosis: If an entry for a particular dial shelf slot is not found among the registered addresses, but most of other card entries are present, the problem is most likely with that dial shelf slot. The DSI hardware on that feature board is probably bad.

Downloading SPE Firmware from the Cisco.com FTP Server to a Local TFTP Server

Note You must be a registered Cisco user to log in to the Cisco Software Center.

You can download software from the Cisco Systems Cisco.com FTP server using an Internet browser or using an FTP application. Both procedures are described.

Using an Internet Browser

Step 1 Launch an Internet browser.

Step 2 Bring up the Cisco Software Center home page at the following URL (this is subject to change without notice):

http://www.cisco.com/kobayashi/sw-center/

Step 3 Click Access Software (under Cisco Software Products) to open the Access Software window.

Step 4 Click Cisco AS5400 Series or Cisco AS5800 Series software.

Step 5 Click the SPE firmware you want and download it to your workstation or PC. For example, to download SPE firmware for the universal access server, click Download Universal Images.

Step 6 Click the SPE firmware file you want to download, and then follow the remaining download instructions. If you are downloading the SPE firmware file to a PC, make sure that you download the file to the c:/tftpboot directory; otherwise, the download process does not work.

Step 7 When the SPE firmware is downloaded to your workstation, transfer the file to a Trivial File Transfer Protocol (TFTP) server in your LAN using a terminal emulation software application.

Step 8 When the SPE firmware is downloaded to your workstation, transfer the file to a TFTP server somewhere in your LAN using a terminal emulation software application.

Using an FTP Application

Note The directory path leading to the SPE firmware files on cco.cisco.com is subject to change without notice. If you cannot access the files using an FTP application, try the Cisco Systems URL http://www.cisco.com/cgi-bin/ibld/all.pl?i=support&c=3.

Step 1 Log in to the Cisco.com FTP server called cco.cisco.com:

Step 2 Enter your registered username and password (for example, harry and letmein):

Step 3 Specify the directory path that holds the SPE firmware you want to download. For example, the directory path for the Cisco AS5400 SPE firmware is /cisco/access/5400:

Step 4 Enter the ls command to view the contents of the directory:

Step 5 Specify a binary image transfer:

Step 6 Copy the SPE firmware files from the access server to your local environment with the get command.

Step 7 Quit your terminal session:

Step 8 Enter the ls -al command to verify that you successfully transferred the files to your local directory:

Step 9 Transfer these files to a local TFTP or remote copy protocol (RCP) server that your access server or router can access.

Copying the SPE Firmware File from the Local TFTP Server to the SPEs

The procedure for copying the SPE firmware file from your local TFTP server to the Cisco AS5400 NextPort DFCs or Cisco AS5800 UPCs is a two-step process. First, transfer the SPE firmware to the access server’s Flash memory. Then, configure the SPEs to use the upgrade firmware. The upgrade occurs automatically, either as you leave configuration mode, or as specified in the configuration.

These two steps are performed only once. After you copy the SPE firmware file into Flash memory for the first time, you should not have to perform these steps again.

Note Because the SPE firmware is configurable for individual SPEs or ranges of SPEs, the Cisco IOS software automatically copies the SPE firmware to each SPE each time the access server restarts.

To transfer SPE Firmware to Flash memory, perform the following task to download the Universal SPE firmware to Flash memory:

Step 1 Check the image in the access server Flash memory:

Step 2 Enter the copy tftp flash command to download the code file from the TFTP server into the access server Flash memory. You are prompted for the download destination and the remote host name.

Step 3 Enter the show flash command to verify that the file has been copied into the access server Flash memory:

Specifying a Country Name

To set the Cisco AS5400 NextPort DFCs or Cisco AS5800 UPCs to be operational for call set up, you must specify the country name. To specify the country name, use the following command in global configuration mode:

Configuring Dial Split Shelves (AS5800 Only)

The Cisco AS5800 access server requires a split dial shelf configuration using two router shelves to achieve the maximum capacity of 2048 port connections using the seven UPCs and three T3 + 1 T1 trunks. A new configuration command is available to define the split point:

dial-shelf split backplane-ds0 option

The options for this command come in pairs, and vary according to the desired configuration. You will need to log in to each router shelf and separately configure the routers for the intended load. In most circumstances it is recommended that the predefined options are selected. These options are designed to be matched pairs as seen below.

The dial-shelf split slot 0 3 4 5 command must be defined for the dial-shelf split backplane-ds0 option command to be active. You may also select the user defined option to define your own split.

Even if your system is already using a split dial shelf configuration, configuring one router shelf to handle two T3 trunks and the other router to handle the third trunk requires you to take the entire access server out of service. Busyout all connections before attempting to reconfigure. The configuration must be changed to setup one pool of TDM resources that can be used by either DMM cards or UPCs, and a second pool of two streams that contains TDM resources that can only be used by UPCs.

You may have more trunk capacity than 2048 calls. It is your decision how to provision the trunks so the backplane capacity is not exceeded. If more calls come in than backplane DS0 capacity for that half of the split, the call will be rejected and an error message printed for each call. This cannot be detected while a new configuration is being built because the router cannot tell which T1 trunks are provisioned and which are not. The user may want some trunks in hot standby.

The DMM, HMM, and VoIP cards can only use 1792 DS0 of the available 2048 backplane DS0. The UPC and trunk cards can use the full 2048 backplane DS0. The show tdm splitbackplane command will show the resources in two groups, the first 1792 accessible to all cards, and the remaining 256 accessible only to UPC and trunk cards.

For more information about split dial shelf configuration, refer to the Cisco AS5800 Universal Access Server Split Dial Shelf Installation and Configuration Guide and the hardware installation guides that accompanied your Cisco AS5800 Universal Access Server.

Configuring SPEs to Use an Upgraded Firmware File

To configure the SPEs to use the upgraded firmware file, use the following commands beginning in privileged EXEC mode to display the firmware version number:

Note The copy ios-bundled command is not necessary with UPCs or NextPort DFCs. By default, the version of SPE firmware bundled with the Cisco IOS software release transfers to all SPEs not specifically configured for a different SPE firmware file.

Disabling SPEs

To disable specific SPEs in the Cisco AS5400 NextPort DFCs or Cisco AS5800 UPCs, use the following commands starting in global configuration mode:

Rebooting SPEs

To reboot specified SPEs, use the following command in privileged EXEC mode:

Configuring Lines

To configure the lines to dial in to your network, use the following commands beginning in global configuration mode:

Configuring Ports

This section describes how to configure Cisco AS5800 UPC or Cisco AS5400 NextPort DFC ports. You need to be in port configuration mode to configure these ports. The port configuration mode allows you to shut down or put individual ports or ranges of ports in busyout mode. To configure Cisco AS5800 UPC or Cisco AS5400 NextPort DFC ports, perform the following tasks beginning in global configuration mode:

Verifying SPE Line and Port Configuration

To verify your SPE line configuration, enter the show spe command to display a summary for all the lines and ports:

Step 1 Enter the show spe command to display a summary for all the lines and ports:

Step 2 Enter the show line command to display a summary for a single line.

AS5400

AS5800

Note If you are having trouble, make sure that you have turned on the protocols for If you are having trouble, make sure that you have turned on the protocols for connecting to the lines (transport input all) and that your access server is configured for incoming and outgoing calls (modem inout).

Configuring SPE Performance Statistics

Depending on the configuration, call record is displayed on the console, or the syslog, or on both. The log contains raw data in binary form, which must be viewed using the show commands listed in the section “Monitoring SPE Performance Statistics.” You can configure some aspects of history events by using one of the following commands in global configuration mode:

Clearing Log Events

To clear some or all of the log events relating to the SPEs as needed, use the following privileged EXEC mode commands:

Troubleshooting SPEs

This section provides troubleshooting information for your SPEs regardless of service type mode.

Note SPE ports that pass the diagnostic test are marked as Pass, Fail, and Unkn. Ports that fail the diagnostic test are marked as Bad. These ports cannot be used for call connections. Depending on how many ports are installed, the diagnostic tests may take from 5 to 10 minutes to complete.

• Enter the port modem startup-test command to perform diagnostic testing for all modems during the system's initial startup or rebooting process. To disable the test, enter the no port modem startup-test command.
• Enter the port modem autotest command to perform diagnostic testing for all ports during the system’s initial startup or rebooting process.To disable the test, enter the no port modem autotest command.

You may additionally configure the following options:

– Enter the port modem autotest minimum ports command to d efine the minimum number of free ports available for autotest to begin.

– Enter the port modem autotest time hh : mm interval command to enable autotesting time and interval.

– Enter the port modem autotest error threshold command to define the maximum number of errors detected for autotest to begin.

• Enter the show port modem test command to displays results of the SPE port startup test and SPE port auto-test.

When an SPE port is tested as Bad, you may perform additional testing by conducting a series of internal back-to-back connections and data transfers between two SPE ports. All port test connections occur inside the access server. For example, if mobile users cannot dial into port 2/5 (which is the sixth port on the NextPort DFC in the second chassis slot), attempt a back-to-back test with port 2/5 and a known-functioning port such as port 2/6.

• Enter the test port modem back-to-back slot / port slot / port command to perform internal back-to-back port tests between two ports sending test packets of the specified size.

Note You might need to enable this command on several different combinations of ports to determine which one is not functioning properly. A pair of operable ports successfully connects and completes transmitting data in both directions. An operable port and an inoperable port do not successfully connect with each other.

A sample back-to-back test might look like the following:

Tip You may reboot the port that has problems using the clear spe EXEC command.

• Enter the spe recovery { port-action { disable | recover | none } | port-threshold num-failures } command to perform automatic recovery (removal from service and reloading of SPE firmware) of ports on an SPE at any available time.

An SPE port failing to connect for a certain number of consecutive times indicates that a problem exists in a specific part or the whole of SPE firmware. Such SPEs have to be recovered by downloading firmware. Any port failing to connect num-failures times is moved to a state based on the port-action value, where you can choose to disable (mark the port as Bad) or recover the port when the SPE is in the idle state and has no active calls. The default for num-failures is 30 consecutive call failures.

Tip You may also schedule recovery using the spe download maintenance command.

• Enter the spe download maintenance time hh : mm | stop-time hh : mm | max-spes number | window time-period | expired-window { drop-call | reschedule } command to perform a scheduled recovery of SPEs.

The download maintenance activity starts at the set start time and steps through all the SPEs that need recovery and the SPEs that need a firmware upgrade and starts maintenance on the maximum number of set SPEs for maintenance. The system waits for the window delay time for all the ports on the SPE to become inactive before moving the SPE to the Idle state. Immediately after the SPE moves to Idle state, the system starts to download firmware. If the ports are still in use by the end of window delay time, depending upon the expired-window setting, connections on the SPE ports are shutdown and the firmware is downloaded by choosing the drop-call option, or the firmware download is rescheduled to the next download maintenance time by choosing the reschedule option. This process continues until the number of SPEs under maintenance is below max-spes, or until stop-time (if set), or until all SPEs marked for recovery or upgrade have had their firmware reloaded.

Monitoring SPE Performance Statistics

This section documents various SPE performance statistics for the Cisco AS5400 NextPort DFCs or Cisco AS5800 UPCs:

• SPE Events and Firmware Statistics
• Port Statistics
• Digital SPE Statistics
• SPE Modem Statistics

SPE Events and Firmware Statistics

To view SPE events and firmware statistics for the Cisco AS5400 NextPort DFCs or Cisco AS5800 UPCs, use one or more of the following commands in privileged EXEC mode:

Port Statistics

To view port statistics for the Cisco AS5400 NextPort DFCs or Cisco AS5800 UPCs, use the following commands in privileged EXEC mode as needed:

Digital SPE Statistics

To view digital SPE statistics for the Cisco AS5400 NextPort DFCs, use one or more of the following commands in privileged EXEC mode:

SPE Modem Statistics

To view SPE modem statistics for the Cisco AS5400 NextPort DFCs or Cisco AS5800 UPCs, use one or more of the following commands in privileged EXEC mode:

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental

© 2007–2009 Cisco Systems, Inc. All rights reserved.