Managing and Troubleshooting the NextPort Dial Feature Card

A NextPort dial feature card [also referred to as the AS54-DFC-108NP] is a hardware card that processes digital service port technology for the Cisco AS5400. Ports on the NextPort DFC support both modem and digital services. You can manage your port connections at the NextPort slot level, service proccessing element (SPE) level or port level using monitoring, and troubleshooting commands. A port is defined as an endpoint on a DFC card through which multi-service tones & data flow.

Note For more information on the NextPort DFC, refer to the Cisco AS5400 Universal Access Server Chassis Installation Guide, Cisco AS5400 Universal Access Server Card Installation Guide, and the Cisco AS5400 Universal Access Server Regulatory Compliance and Safety Information.

Note For detailed information about NextPort Cisco IOS CLI commands, refer to the NextPort Port Service Management for Cisco AS5400 Access Servers.

The NextPort DFC introduces slot and SPE software hierarchies. On the Cisco AS5400, the hierarchy designation is slot/spe. The DFC slot is defined as a value between 1 and 7. The port values range from 0 to 107. For example, the NextPort DFC port 2/5 is the sixth port located in the second chassis slot on the Cisco AS5400. Slot 0 is reserved for the motherboard.

The user can perform the following functions on an SPE:

General configuration such as busyout, shutdown, or clear
View statistics and states
Configure auto and manual recovery process
Upgrade firmware
Retrieve trace information for ports running on an SPE

This chapter includes the following sections:

SPE Performance Statistics

Configuration

By default, an event log is enabled and based on one event queue per SPE port. The log contains raw data in binary form, which must be viewed using the show commands listed in the "Viewing SPE Performance Statistics" section.You may configure some aspects of how the record is kept using the following global configuration mode commands (at the 5400(config)# prompt):

spe call-record modem max-userid--Requests that the access server generate a modem call record after a call is terminated, and add it to the log. To disable this function, use the no form. This replaces the modem call-record command.
spe log-size number--This command allows the user to configure the size of the history event queue buffer for manageable SPEs in the access server. The default is 100 events per port. Use the show port modem log command to view port events. It is used in the same way the modem buffer-size command is used for MICA modems.

The following privileged EXEC mode commands allow you to clear some or all of the log events relating to the SPEs (at the 5400# prompt):

clear spe log--This command allows a user to clear all event entries in the slot history event log.
clear spe counters--This command clears statistical counters for all types of services for the specified SPE, SPE range, or all the SPEs. If the user does not specify the range of SPEs or a SPE, all SPEs' statistics are cleared. It is used in the same way the clear modem counters command is used for MICA modems.
clear port log--This command allows a user to clear all event entries in the port level history event log. This command clears the entire port log. You cannot remove individual service events from the port log. You can use show port modem log or show port digital log to display specific service events, but you must use clear port log to clear the entire port log.

Viewing SPE Performance Statistics

You can view SPE statistics using the Cisco IOS software with the Cisco AS5400 access server. To view performance statistics for the NextPort DFCs, enter one or more of the following commands in privileged EXEC mode (at the 5400# prompt):

Managing Ports

This section describes how to manage NextPort ports. The user can clear ports, remove ports from service, and disable ports from dial-up service by using port configuration mode. For details on disabling a port from dial-up service, see the "Troubleshooting" section .

Clear Ports

Ports will need to be cleared if polling attempts have failed and the port is removed from operation.

Use the show spe slot/spe command to view the active ports on an SPE. To clear ports on an SPE, enter the following command in privileged EXEC mode. The user can clear all ports on the access server, all ports on a slot, or a port. This replaces the clear modem command.

The example below clears port 1 on slot 4 on the Cisco AS5400.

5400# clear port 4/1
5400# This will clear port 4/01 [confirm] yes
5400#

The example below clears all active ports on slot 4 on the Cisco AS5400.

5400# clear port 4
5400# This will clear port 4/00 - 4/107 [confirm] yes
5400#

Port Configuration Mode

Port configuration mode allows the user to enter a mode similar to the line configuration mode. This mode allows individual ports or ranges of ports to be shut down or put in busyout mode. Port configuration mode commands replace the modem range, modem busyout, and modem shutdown commands used with MICA modems.

The example below demonstrates how to enter port configuration mode for a single port on the Cisco AS5400.

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

The example below demonstrates how to enter port configuration mode for a range of ports on the Cisco AS5400.

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

Port Configuration Mode Commands

The following commands are available in port configuration mode:

busyout
--This command gracefully disables a port by waiting for the active services on the specified port to terminate. Use the no form of this command to re-enable the ports. This replaces the modem busyout command.
- Maintenance activities, such as testing, can still be performed while port is in busyout mode.
shutdown--This command clears active calls on the port. No more calls can be placed on the port. The state of the SPEs are reflected in the show spe command display. Use the no form of this command to re-enable the ports. This command replaces the modem shutdown command.

Note When a port is in busyout mode or shutdown mode, the state of the SPE is changed to the consolidated states of all the underlying ports on that SPE.

Managing SPEs

This section describes how to manage SPEs by setting the SPE country code, entering SPE configuration mode, upgrading the SPE firmware, performing busyout on SPEs, and clearing active calls on the SPEs.

SPE Country

Enter this global configuration mode command to set the SPE country code and encoding parameters for all NextPort DFCs on your Cisco AS5400. For T1 interfaces, the default is usa; for E1 interfaces, the default is e1-default. Use the no form of this command to set the country code to the default of domestic.

Note The Cisco AS5400 must be in IDLE state (no calls are active) to execute the SPE country command.

A list of all supported countries is displayed in the help file. This command replaces the modem country command.

In the following example, country code is set to E1 default.

5400(config)# spe country e1-default
5400(config)#

SPE Configuration Mode

SPE configuration mode allows the user to enter the SPE configuration mode, which is similar to the line configuration mode. The user can configure an SPE by specifying a slot and an SPE associated with the slot or, the user can choose to configure a range of SPEs by specifying the first & last SPE in the range.

The example below demonstrates how to enter SPE configuration mode on the Cisco AS5400.

5400# config t
Enter configuration commands, one per line.  End with CNTL/Z.
5400(config)# spe 1/1 1/18
5400(config-SPE)#

SPE Configuration Mode Commands

The following commands are available in SPE configuration mode:

firmware location --This command allows the user to upgrade firmware for SPEs after the new SPE firmware image. For further information on firmware upgrades, see the "Important Upgrade Commands" section.
firmware upgrade busyout | download-maintenance | reboot--This command allows the user to specify the upgrade method. Three methods of upgrade are available. Reboot requests the access server to upgrade firmware at the next reboot. Busyout waits until all calls are terminated on a SPE before upgrading the SPE to the designated firmware. Download-maintenance upgrades the firmware during the download maintenance time. For further information on firmware upgrades, see the "Important Upgrade Commands" section.
busyout--This command gracefully disables an SPE by waiting for all the active services on the specified SPE to terminate. If there are active ports on the specified SPE, the state of the SPE is changed to Busiedout. The SPE is temporarily disabled. Use the no form of this command to re-enable the SPEs.
shutdown-- This command clears active calls on all ports on the SPE. Calls can no longer be placed on the SPE because the SPE state is changed to Out-of-Service. The state of the SPEs are reflected in the show spe command display. Use the no form of this command to re-enable the ports on the SPE.

Troubleshooting

This section provides troubleshooting information that apply to your modems regardless of service type mode. You learn how to perform diagnostic tests on installed ports or SPEs, configure automatic recovery of ports on an SPE and configure a scheduled recovery of SPEs.

Configure SPE Diagnostic Tests

You can perform three types of diagnostic tests on your SPE modem:

SPE Startup Test

To perform diagnostic testing on all your installed SPE ports during the system's initial startup or rebooting process, in global configuration mode with the prompt displayed as 5400(config)# enter the following command:

: port modem startup-test--Perform diagnostic testing for all modems.

The results of the SPE port startup test are displayed in the show port modem test command's output. SPE ports that pass the diagnostic test are 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, this diagnostic test may take from 5 to 10 minutes to complete. Perform additional testing on an inoperative SPE port by executing the test port modem back-to-back command. The no port modem startup-test command disables startup testing.

SPE Auto-Test

To perform diagnostic testing on all the installed SPE ports during the system's initial startup or rebooting process, or during service, in global configuration mode with the prompt displayed as 5400(config)# enter the following command:

: port modem autotest --Perform diagnostic testing for all ports.

The results of the SPE port auto-test are displayed in the show port modem test command's output. Ports that pass the diagnostic test are marked as Idle, Busy, Downloading, and Reset, and are put into service. Ports that fail the diagnostic test are marked as Bad, and are not put into service or tested again until they are no longer marked as Bad. If all the ports of an SPE are bad, the corresponding SPE is also marked bad. These ports cannot be used for call connections. Depending on how many ports are present and not marked Bad, this diagnostic test may take from 5 to 10 minutes to complete. You may perform additional testing on an inoperative port by executing the test port modem back-to-back command. The no port modem autotest command disables testing.

You may additionally configure the following options:

port modem autotest minimum ports--Define the minimum number of free ports available for autotest to begin.
port modem autotest time hh:mm interval--Enable autotesting time and interval.
port modem autotest error threshold--Define the maximum number of errors detected for autotest to begin.

A sample diagnostic autotest setting the time at 12:45 and at 8 hour intervals looks like the following:

5400(config)# port modem autotest time 12:45 8
5400(config)#

SPE Back-to-Back 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 following command in privileged EXEC mode (the prompt is displayed as 5400#) to perform internal back-to-back port tests between two ports:

: test port modem back-to-back slot/port slot/port [num-packets]--Perform internal back-to-back port tests between two ports, sending test packets of the specified size.

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 connect and complete 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:

5400# test port modem back-to-back 2/10 3/20
Repetitions (of 10-byte packets) [1]:
*Mar  02 12:13:51.743:%PM_MODEM_MAINT-5-B2BCONNECT:Modems (2/10) and (3/20) connected in back-to-back test:CONNECT33600/V34/LAP
*Mar  02 12:13:52.783:%PM_MODEM_MAINT-5-B2BMODEMS:Modems (3/20) and (2/10) completed back-to-back test:success/packets = 2/2

A port that has been confirmed to have problems can often be fixed using the clear spe command. For more information, see the "Clear an SPE" section.

The results of the test port modem back-to-back command are displayed in the show port modem test command's output:

5400# show port modem test
 Date Time             Modem  Test               Reason            State Result
 3/02 12:00:57 PM       2/01  Back-To-Back     :STARTUP TEST      Idle  PASS
 3/02 12:00:57 PM       2/00  Back-To-Back     :STARTUP TEST      Idle  PASS
 3/02 12:00:58 PM       2/02  Back-To-Back     :STARTUP TEST      Idle  PASS
 3/02 12:00:58 PM       2/03  Back-To-Back     :STARTUP TEST      Idle  PASS
 3/02 12:00:58 PM       2/04  Back-To-Back     :STARTUP TEST      Idle  PASS
 3/02 12:00:58 PM       2/05  Back-To-Back     :STARTUP TEST      Idle  PASS
...
 3/02 12:01:14 PM       3/95  Back-To-Back     :STARTUP TEST      Idle  PASS
 3/02 12:01:14 PM       3/94  Back-To-Back     :STARTUP TEST      Idle  PASS
 3/02 12:01:15 PM       3/75  Back-To-Back     :STARTUP TEST      Idle  PASS
 3/02 12:01:15 PM       3/74  Back-To-Back     :STARTUP TEST      Idle  PASS
 3/02 12:13:52 PM       3/20  Back-To-Back     :USER INITIATED    Idle  PASS
 3/02 12:13:52 PM       2/10  Back-To-Back     :USER INITIATED    Idle  PASS
...
 3/02 12:44:00 PM      3/102  No Test (Time)   :MIN IDLE MODEMS   Idle  NOTST
 3/02 12:44:00 PM      3/103  No Test (Time)   :MIN IDLE MODEMS   Idle  NOTST
 3/02 12:44:00 PM      3/104  No Test (Time)   :MIN IDLE MODEMS   Idle  NOTST
 3/02 12:44:00 PM      3/105  No Test (Time)   :MIN IDLE MODEMS   Idle  NOTST
 3/02 12:44:00 PM      3/106  No Test (Time)   :MIN IDLE MODEMS   Idle  NOTST
 3/02 12:44:00 PM      3/107  No Test (Time)   :MIN IDLE MODEMS   Idle  NOTST
 3/02 12:44:21 PM       2/73  Back-To-Back     :TIME INTERVAL     Idle  PASS
 3/02 12:44:21 PM       2/72  Back-To-Back     :TIME INTERVAL     Idle  PASS
 3/02 12:44:21 PM       2/33  Back-To-Back     :TIME INTERVAL     Idle  PASS
 3/02 12:44:21 PM       2/32  Back-To-Back     :TIME INTERVAL     Idle  PASS
 3/02 12:44:21 PM       3/37  Back-To-Back     :TIME INTERVAL     Idle  PASS

Note The Reason column indicates why the test was started. The TIME INTERVAL is one of the triggers under autotest; the other is the error threshold.

SPE Recovery

You may configure automatic recovery (removal from service and reloading of SPE firmware) of ports on an SPE at any available time from global configuration mode as shown [the prompt is displayed as 5400(config)#]:

: spe recovery {port-action {disable | recover | none} | port-threshold num-failures}

When an SPE port fails to connect for a certain number of consecutive times, it 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 will be moved to a state based on port-action, where you can choose to disable (mark the port as Bad) or recover the port when the SPE is in IDLE and has no active calls. The default for num-failures is 30.

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

SPE Download Maintenance

You may configure a scheduled recovery of SPEs from global configuration mode as shown [the prompt is displayed as 5400(config)#]:

: spe download maintenance time hh:mm | stop-time hh:mm | max-spes num-of-spes | window time-period | expired-window {drop-call | reschedule }

Download maintenance starts at time, steps through all the SPEs that need recovery and SPEs that need a firmware upgrade and starts maintenance on max-spes at a time. It waits for the window delay time for all the ports on the SPE to become inactive before moving the SPE to the Idle state. It will download firmware immediately after the SPE moves to idle. If the ports are still in use by the end of (window), depending upon the expired-window setting, connections on the SPE ports will be shutdown and the firmware will 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 are below max-spes, or until stop-time (if set), or until all SPEs marked for recovery or upgrade have had their firmware reloaded.

Clear an SPE

The clear spe privileged EXEC mode command allows the user to manually recover a port that is frozen in a suspended state. This command causes the firmware configured for that SPE to be downloaded to the specified SPE or the range of SPEs and Power on Self Test (POST) to be executed. This command can be executed irrespective of the state of the SPEs. All active ports running on the SPE are prematurely terminated and messages are logged into the appropriate log. This replaces the clear modem command.

The following example shows a coldstart on SPE 1 on slot 1:

5400# clear spe 1/1
5400# Are you sure you want to clear SPE 1/1(Y/N)? Y

Important Upgrade Commands

There are several commands you use to upgrade SPE firmware. For examples on using the commands, see "Upgrading SPE Firmware from the Cisco CCO FTP Server" section, and "Using SPE Firmware Bundled with Cisco IOS Software" section.

Use the copy tftp flash filename command to copy any version of SPE firmware (no matter how it is obtained) into system Flash memory. You can store several versions of the SPE firmware in system Flash memory under different filenames.
Use the firmware location SPE configuration command to transfer a specified version of SPE firmware from system Flash memory to the SPEs named upon entering SPE configuration mode.
Use the firmware upgrade busyout | download-maintenance | reboot SPE configuration command to configure when the file named in the firmware location command will be loaded to the SPEs. Three methods of upgrade are available. Reboot request the access server to upgrade firmware at the next reboot. Busyout waits until all calls are terminated on a SPE before upgrading the SPE to the desired firmware. Recovery requests firmware download as configured by the recovery method command (see "SPE Recovery" section).

Note The copy ios-bundled command is not necessary with Universal Port 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.

Displaying SPE Firmware Versions

Use the show spe version command to list the versions of SPE firmware running on the SPEs, residing in system Flash memory, and bundled with Cisco IOS software. This will help you decide if you need to change the version running on the modems.

5400# show spe version
IOS-Bundled Default Firmware-Filename             Version  Firmware-Type
=====================================             =======  =============
system:/ucode/np_spe_firmware1                    0.0.6.75 SPE firmware
 
On-Flash Firmware-Filename                        Version  Firmware-Type
==========================                        =======  =============
flash:np.spe                                      0.6.4.5  SPE firmware
flash:np_6_77.spe                                 0.0.6.77 SPE firmware
flash:np_6_79.spe                                 0.0.6.79 SPE firmware
 
  SPE-# SPE-Type   SPE-Port-Range     Version    UPG Firmware-Filename
   2/00    CSMV6        0000-0005    0.0.6.75    N/A ios-bundled default
   2/01    CSMV6        0006-0011    0.0.6.75    N/A ios-bundled default
   2/02    CSMV6        0012-0017    0.0.6.75    N/A ios-bundled default
   2/03    CSMV6        0018-0023    0.0.6.75    N/A ios-bundled default
   2/04    CSMV6        0024-0029    0.0.6.75    N/A ios-bundled default
   2/05    CSMV6        0030-0035    0.0.6.75    N/A ios-bundled default
   2/06    CSMV6        0036-0041    0.0.6.77    N/A np_6_77.spe
   2/07    CSMV6        0042-0047    0.0.6.77    N/A np_6_77.spe
   2/08    CSMV6        0048-0053    0.0.6.77    N/A np_6_77.spe
   2/09    CSMV6        0054-0059    0.0.6.77    N/A np_6_77.spe
   2/10    CSMV6        0060-0065    0.0.6.77    N/A np_6_77.spe
   2/11    CSMV6        0066-0071    0.0.6.77    N/A np_6_77.spe
   2/12    CSMV6        0072-0077    0.0.6.79    N/A np_6_79.spe
   2/13    CSMV6        0078-0083    0.0.6.79    N/A np_6_79.spe
   2/14    CSMV6        0084-0089    0.0.6.79    N/A np_6_79.spe
   2/15    CSMV6        0090-0095    0.0.6.79    N/A np_6_79.spe
   2/16    CSMV6        0096-0101    0.0.6.79    N/A np_6_79.spe
   2/17    CSMV6        0102-0107    0.0.6.79    N/A np_6_79.spe

Upgrading SPE Firmware from the Cisco CCO FTP Server

Upgrading SPE firmware from the Cisco CCO FTP server is a three-step process:

Downloading the SPE firmware from Cisco CCO FTP server to a local TFTP server
Copying the SPE firmware file to the access server and SPEs
Configuring SPEs to use an Upgraded Firmware File

Download SPE Firmware from the Cisco CCO FTP Server to a Local TFTP Server

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

You can download software from the Cisco Systems CCO 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 Cisco's Software Center home page at following url (this is subject to change without notice):

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

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

Step 4 Click Cisco AS5400 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 NextPort DFC, click Download NextPort DFC 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 you download it to the c:/tftpboot directory; otherwise, the download process will not work.

Step 7 When the SPE firmware is downloaded to your workstation, transfer the file to a 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 CCO FTP server, called cco.cisco.com:

     terminal> ftp cco.cisco.com
     Connected to cio-sys.cisco.com.
     220-
     220-  Cisco Connection Online       |        |      Cisco Systems, Inc.
     220-  Email: cco-team@cisco.com   |||      |||  170 West Tasman Drive
     220-  Phone: +1.800.553.2447  .:|||||:..:|||||:.  San Jose, CA 95134
     220-
     220- NOTE: As of February 1,1997 ftp.cisco.com will now point to this
     220- service. Please be advised. To use the former ftp.cisco.com after 
     220-  February 1, connect to ftpeng.cisco.com
     220-
     220-  You may login with:
     220- + Your CCO username and password, or
     220- + A special access code followed by your e-mail address, or
     220- + "anonymous" followed by your e-mail address for guest access.
     220-
     220 cio-sys FTP server (CIOESD #103 Sun Dec 15 14:43:43 PST 1996) ready.

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

     Name (cco.cisco.com:harry): harry
     331 Password required for harry.
     Password: letmein
     230-#############################################################
     230-#  Welcome to the Cisco Systems CCO FTP server.
     230-#  This server has a number of restrictions.  If you are not familiar
     230-#  with these, please first get and read the /README or /README.TXT file.
     230-#  http://www.cisco.com/acs/info/cioesd.html  for more info.
     230-#############################################################
     230-
     230-  *****  NOTE: As of February 1, 1997, "cco.cisco.com",   *****
     230-  *****  "www.cisco.com" and "ftp.cisco.com" are now all  *****
     230- *****  logical names for the same machine.              *****
     230- *****                                                   *****
     230- *****  The old "ftp.cisco.com" is an entirely           *****
     230- *****  different machine, which is now known as        *****
     230- *****  "ftpeng.cisco.com" or "ftp-eng.cisco.com".    *****
     230- *****                                                   *****
     230- *****  In general, "ftpeng.cisco.com" is used only for ****
     230-  *****  distribution of Cisco Engineering-controlled  *****
     230-  *****  projects, such as beta programs, early field   *****
     230-  *****  trials, developing standards documents, etc.  *****
     230-  *****                                                   *****
     230-  *****  Be sure to confirm you have connected to         *****
     230-  *****  the machine you need to interact with.           *****
     230-
     230-  If you have any odd problems, try logging in with a minus sign (-) as
     230-  the first character of your password.  This will turn off a feature
     230- that may be confusing your ftp client program.
     230-  Please send any questions, comments, or problem reports about this
     230-  server to cco-team@cisco.com.
     230-
     230-  NOTE: 
     230-  o To download files from CCO, you must be running a *passive-mode*
     230-    capable FTP client.
     230-  o To drop files on this system, you must cd to the /drop directory.
     230-  o Mirrors of this server can be found at 
     230-  
     230-     + ftp://www-europe.cisco.com European (Amsterdam) 
     230-     + ftp://www-fr.cisco.com     France     (Paris)
     230-     + ftp://www-au.cisco.com     Australia  (Sydney)
     230-     + ftp://www-jp.cisco.com     Japan      (Tokyo)
     230-     + ftp://www-kr.cisco.com     Korea      (Seoul)
     230-
     230-Please read the file README
     230-  it was last modified on Sat Feb  1 12:49:31 1997 - 163 days ago
     230 User harry logged in.  Access restrictions apply.
     Remote system type is UNIX.
     Using binary mode to transfer files.

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:

     ftp> cd /cisco/access/5400
     250-Please read the file README
     250-  it was last modified on Tue May 27 10:07:38 1997 - 48 days ago
     250-Please read the file README.txt
     250-  it was last modified on Tue May 27 10:07:38 1997 - 48 days ago
     250 CWD command successful.

Step 4 View the contents of the directory with the ls command:

     ftp> ls
     227 Entering Passive Mode (192,31,7,130,218,128)
     150 Opening ASCII mode data connection for /bin/ls.
     total 2688
     drwxr-s--T   2 ftpadmin ftpcio    512 Jun 30 18:11 .
     drwxr-sr-t  19 ftpadmin ftpcio    512 Jun 23 10:26 ..
     lrwxrwxrwx  1  root     3          10 Aug   6 1996     README ->README.txt
     -rw-rw-r--   1 root     ftpcio   2304 May 27 10:07 README.txt
     -r--r--r-- 1 ftpadmin ftpint 377112 Jul 10 18:08 np-spe-upw-1.0.1.2.bin
     -r--r--r-- 1 ftpadmin ftpint 635 Jul 10 18:08 SPE-firmware.3.1.30.readme
226 Transfer complete.

Step 5 Specify a binary image transfer:

     ftp> binary
     200 Type set to I.

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:

     ftp> quit
     Goodbye.

Step 8 Verify you successfully transferred the files to your local directory:

     server% ls -al
     total 596
     -r--r--r-- 1 280208 Jul 10 18:08 np-spe-upw-1.0.1.2.bin
     server% pwd
     /auto/tftpboot

Step 9 Transfer these files to a local TFTP or RCP server that your access server or router can access.

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

The procedure for copying the SPE firmware file from your local TFTP server to the AS54-DFC-108NPs 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 will occur 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. 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.

Transfer SPE Firmware to Flash Memory

Follow these steps to download the Universal SPE firmware to Flash memory:

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

5400# show flash
System flash directory:
File  Length   Name/status
  1   4530624  c5400-js-mx 
 [498776 bytes used, 16278440 available, 16777216 total]
16384K bytes of processor board System flash (Read/Write)

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.

5400# copy tftp flash
System flash directory:
File  Length   Name/status
  1   4530624   images/c5400-js-mx  
[498776 bytes used, 16278440 available, 16777216 total]
Address or name of remote host [255.255.255.255]? jurai
Source file name? np-spe-upw-1.0.1.2.bin
Destination file name [np-spe-upw-1.0.1.2.bin]? 
Accessing file 'np_6_79.spe' on 255.255.255.255...
Loading np-spe-upw-1.0.1.2.bin from 2.2.0.1 (via Ethernet0): ! [OK]
Erase flash device before writing? [confirm] no
Copy 'np-spe-upw-1.0.1.2.bin' from server
  as 'np-spe-upw-1.0.1.2.bin' into Flash WITHOUT erase? [yes/no] yes
Loading images/np_6_79.spe from 2.2.0.1 (via Ethernet0): 
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[OK - 249108/16278440 bytes]
Verifying checksum...  OK (0xE009)
Flash device copy took 00:00:02 [hh:mm:ss]

Step 3 Verify the file has been copied into the access server Flash memory:

5400# show flash
System flash directory:
File  Length   Name/status
  1   4530624  c5400-js-mz  
  2   210104   np-spe-upw-1.0.1.2.bin
  [747948 bytes used, 16029268 available, 16777216 total]
16384K bytes of processor board System flash (Read/Write)

Configure SPEs to use an Upgraded Firmware File

Follow these steps to configure the SPEs to use the upgraded firmware:

Step 1 Enter the enable command.

5400> enable

Step 2 Enter your password.

Password: password
5400#

You are in privileged EXEC mode when the prompt changes to 5400#.

Step 3 Display SPE firmware versions to obtain the On-Flash firmware filename.

5400# show spe version
IOS-Bundled Default Firmware-Filename             Version  Firmware-Type
=====================================             =======  =============
system:/ucode/np_spe_firmware1                    0.0.6.75 SPE firmware
 
On-Flash Firmware-Filename                        Version  Firmware-Type
==========================                        =======  =============
flash:np.spe                                      0.6.4.5  SPE firmware
flash:np_6_77.spe                                 0.0.6.77 SPE firmware
flash:np_6_79.spe                                 0.0.6.79 SPE firmware
flash:np-spe-upw-1.0.1.2.bin                      1.0.1.2  SPE firmware
 
  SPE-# SPE-Type   SPE-Port-Range     Version    UPG Firmware-Filename
   2/00    CSMV6        0000-0005    0.0.6.75    N/A ios-bundled default
   2/01    CSMV6        0006-0011    0.0.6.75    N/A ios-bundled default
   2/02    CSMV6        0012-0017    0.0.6.75    N/A ios-bundled default
   2/03    CSMV6        0018-0023    0.0.6.75    N/A ios-bundled default
   2/04    CSMV6        0024-0029    0.0.6.75    N/A ios-bundled default
   2/05    CSMV6        0030-0035    0.0.6.75    N/A ios-bundled default
   2/06    CSMV6        0036-0041    0.0.6.77    N/A np_6_77.spe
   2/07    CSMV6        0042-0047    0.0.6.77    N/A np_6_77.spe
   2/08    CSMV6        0048-0053    0.0.6.77    N/A np_6_77.spe
   2/09    CSMV6        0054-0059    0.0.6.77    N/A np_6_77.spe
   2/10    CSMV6        0060-0065    0.0.6.77    N/A np_6_77.spe
   2/11    CSMV6        0066-0071    0.0.6.77    N/A np_6_77.spe
   2/12    CSMV6        0072-0077    0.0.6.79    N/A np_6_79.spe
   2/13    CSMV6        0078-0083    0.0.6.79    N/A np_6_79.spe
   2/14    CSMV6        0084-0089    0.0.6.79    N/A np_6_79.spe
   2/15    CSMV6        0090-0095    0.0.6.79    N/A np_6_79.spe
   2/16    CSMV6        0096-0101    0.0.6.79    N/A np_6_79.spe
   2/17    CSMV6        0102-0107    0.0.6.79    N/A np_6_79.spe

Step 4 Enter global configuration mode by typing the configure command. The example uses the terminal configuration option.

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

You are in global configuration mode when the prompt changes to 5400(config)#.

Step 5 Enter SPE configuration mode, which is similar to the line configuration mode. You can choose to configure a single SPE or range of SPEs by specifying the first & last SPE in the range.

5400(config)# spe slot/spe 
 
or
 
5400(config)# spe slot/spe slot/spe

You are in SPE configuration mode when the prompt changes to 5400(config-SPE)#.

Step 6 Specify the SPE firmware file in Flash memory to use for the selected SPEs. This is the firmware filename that you obtained in Step 3.

5400(config-SPE)# firmware location np-spe-upw-1.0.1.2.bin

Step 7 Specify when the SPE firmware upgrade will occur.

5400(config-SPE)# firmware upgrade busyout | download-maintenance | reboot

Step 8 Type the exit command to exit out of SPE config mode.

5400(config-SPE)# exit
5400(config)#

Step 9 Press the Enter key to verify your command registers, then type Ctrl-Z to return to privileged EXEC mode.

5400(config)# Ctrl-Z 
5400#

Step 10 Save your changes when ready.

5400# copy running-config startup-config

Using SPE Firmware Bundled with Cisco IOS Software

Use this procedure to update SPE firmware on the SPEs in your access server if you decide to use the version of SPE firmware bundled with Cisco IOS software instead of the version already mapped to your ports.

To set the SPE firmware mapping to the SPE firmware version bundled with Cisco IOS software, enter the following commands:

Step 1 Enter the enable command.

5400> enable

Step 2 Enter your password.

Password: password
5400#

You are in privileged EXEC mode when the prompt changes to 5400#

Step 3 Enter global configuration mode by typing the configure command. The example uses the terminal configuration option.

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

You are in global configuration mode when the prompt changes to 5400(config)#.

Step 4 Enter SPE configuration mode, which is similar to the line configuration mode. You can choose to delete the configuration for a single SPE or range of SPEs by specifying the first and last SPE in the range. The SPE firmware used by the SPEs will automatically revert to the version bundled with the current Cisco IOS image.

5400(config)# spe slot/spe 
 
or
 
5400(config)# spe slot/spe slot/spe

You are in SPE configuration mode when the prompt changes to 5400(config-SPE)#.

Step 5 Enter the no form of the firmware location command to revert back to the default Cisco IOS bundled SPE firmware:

5400(config-SPE)# no firmware location

Step 6 Type the exit command to exit out of SPE config mode.

5400(config-SPE)# exit
5400(config)#

Step 7 Press the Enter key to verify your command registers, then type Ctrl-Z to return to privileged EXEC mode.

5400(config)# Ctrl-Z 
5400#

Step 8 Save your changes when ready.

5400# copy running-config startup-config

This process does not delete any existing SPE firmware that resides in system Flash memory in case you later want to revert to it. If you decide to delete the code from system Flash memory, remember that all files in system Flash memory will be deleted, therefore save and restore any important files (for example, the Cisco IOS software image).

Note If the new Cisco IOS image contains the same SPE firmware as the old one, no new code will be downloaded to the SPEs.

Where to Go Next

At this point you can go to:

Chapter 5, "Advanced Configuration" to configure some advanced features on your access server.
Chapter 6, "Access Service Security" to configure security on your access server.
"Comprehensive Configuration Examples."
NextPort Port Service Management for Cisco AS5400 Access Servers

Tips 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.

See the Cisco IOS software configuration guide, feature modules, command reference publications, Dial Solutions Configuration Guide and Dial Solutions Command Reference Guide for more advanced configuration topics.

Table of Contents

Managing and Troubleshooting the NextPort Dial Feature Card

Using an Internet Browser

Using an FTP Application

Transfer SPE Firmware to Flash Memory

Configure SPEs to use an Upgraded Firmware File