-
Cisco IOS Interface and Hardware Component Command Reference, Release 12.3 T
-
Introduction
-
Interface and Hardware Component Commands: A through C
-
Interface and Hardware Component Commands: D through H
-
Interface and Hardware Component Commands: I through L
-
int_m1gt_1
-
Interface and Hardware Component Commands: M through R
-
Interface and Hardware Component Commands: scramble through show chassis
-
Interface and Hardware Component Commands: show compress through show hub
-
Interface and Hardware Component Commands: show interfaces through show interfaces vg-anylan
-
Interface and Hardware Component Commands: show ipc through syscon source-interface
-
Interface and Hardware Component Commands: T through Y
-
Table Of Contents
service single-slot-reload-enable
service-module 56k clock source
service-module 56k data-coding
service-module 56k network-type
service-module 56k remote-loopback
service-module 56k switched-carrier
service-module analysis-module reload
service-module analysis-module reset
service-module analysis-module session
service-module analysis-module shutdown
service-module analysis-module status
service-module backup interface
service-module content-engine reload
service-module content-engine reset
service-module content-engine session
service-module content-engine shutdown
service-module content-engine status
service-module external ip address
service-module ip default-gateway
service-module routing redistribute
service-module satellite backup
service-module satellite configuration
service-module satellite cw-mode
service-module satellite status
service-module t1 cablelength short
service-module t1 clock source
service-module t1 remote-alarm-enable
service-module t1 remote-loopback
scramble
To enable scrambling (encryption) of the payload on a T3 or E3 controller or on the PA-T3 and PA-E3 port adapters, use the scramble command in interface configuration mode. To disable scrambling, use the no form of this command.
scramble
no scramble
Syntax Description
This command has no arguments or keywords.
Defaults
Scrambling is disabled.
Command Modes
Interface configuration
Command History
Usage Guidelines
T3/E3 scrambling is used to assist clock recovery on the receiving end. Scrambling is designed to randomize the pattern of 1s and 0s carried in the physical layer frame. Randomizing the digital bits can prevent continuous, nonvariable bit patterns—in other words, long strings of all 1s or all 0s. Several physical layer protocols rely on transitions between 1s and 0s to maintain clocking.
Scrambling can prevent some bit patterns from being mistakenly interpreted as alarms by switches placed between the Data Service Units (DSUs).
The local interface configuration must match the remote interface configuration. For example, if you enable scrambling on the local port, you must also do the same on the remote port.
To verify that scrambling is configured on the interface, use the show controllers serial or the show interfaces serial commands.
For T3 controllers, all the DSU modes support scrambling except Clear mode.
For E3 controllers, only Kentrox mode supports scrambling.
Examples
The following example enables scrambling on the PA-E3 port adapter in slot 1, port adapter slot 0, interface 0:
Router(config)# interface serial 1/0/0Router(config-if)# scrambleThe following example enables scrambling on the controller in slot 1, port 0:
Router(config)# interface serial 1/0Router(config-if)# scrambleRelated Commands
show controllers serial
Displays information that is specific to the serial controllers.
show interfaces serial
Displays information that is specific to the interface hardware.
serial restart-delay
To set the amount of time that the router waits before trying to bring up a serial interface when it goes down, use the serial restart-delay command in interface configuration mode. To restore the default, use the no form of the command.
serial restart-delay count
no serial restart-delay
Syntax Description
count
Frequency, in milliseconds, at which the hardware is reset. Range is from 0 to 900. Default is 0.
Defaults
0 milliseconds
Command Modes
Interface configuration
Command History
11.2 P
This command was introduced.
12.2(4)T
The count value was changed to set time in milliseconds rather than in seconds.
Usage Guidelines
The router resets the hardware each time the serial restart timer expires. This command is often used with the dial backup feature and with the pulse-time command, which sets the amount of time to wait before redialing when a DTR dialed device fails to connect.
When the count value is set to the default of 0, the hardware is not reset when it goes down. In this way, if the interface is used to answer a call, it does not cause DTR to drop, which can cause a communications device to disconnect.
Examples
The following example shows how to set the restart delay on serial interface 0 to 0:
Router(config)# interface serial 0Router(config-if)# serial restart-delay 0Related Commands
pulse-time
Enables pulsing DTR signal intervals on the serial interfaces.
show interfaces serial
Displays information about a serial interface.
service single-slot-reload-enable
To enable single line card reloading for all line cards in the Cisco 7500 series router, use the service single-slot-reload-enable command in global configuration mode. To disable single line card reloading for the line cards in the Cisco 7500 series router, use the no form of this command.
service single-slot-reload-enable
no service single-slot-reload-enable
Syntax Description
This command has no arguments or keywords.
Defaults
Single line card reloading is disabled.
Command Modes
Global configuration
Command History
12.0(13)S
This command was introduced.
12.1(5)T
This command was integrated into Cisco IOS Release 12.1(5)T.
Examples
In the following example, single line card reloading is enabled for all lines cards on the Cisco 7500 series router:
Router(config)# service single-slot-reload-enableRelated Commands
show diag
Displays hardware information for a networking device.
show running-config
Displays configuration information.
service-module 56k clock rate
To configure the network line speed for a serial interface on a 4-wire, 56/64-kbps CSU/DSU module, use the service-module 56k clock rate command in interface configuration mode. To enable a network line speed of 56 kbps, which is the default, use the no form of this command.
service-module 56k clock rate speed
no service-module 56k clock rate speed
Syntax Description
Defaults
56 kbps
Command Modes
Interface configuration
Command History
Usage Guidelines
The 56-kbps line speed is available in switched mode, which is enabled using the service-module 56k network-type interface configuration command on the 4-wire CSU/DSU. If you have a 2-wire CSU/DSU module, the default is automatically set to switched mode.
The 64-kbps line speed cannot be used with back-to-back digital data service (DDS) lines. The subrate line speeds are determined by the service provider.
The auto keyword enables the CSU/DSU to decipher current line speed from the sealing current running on the network. Use the auto keyword only when transmitting over telco DDS lines and the clocking source is taken from the line.
Examples
The following example displays two routers connected in back-to-back DDS mode. However, notice that at first the configuration fails because the auto option is used. Later in the example the correct matching configuration is issued, which is 38.4 kbps.
Router1(config)# interface serial 0Router1(config-if)# service-module 56k clock source internalRouter1(config-if)# service-module 56k clock rate 38.4Router2(config-if)# service-module 56k clock rate autoRouter1# ping 10.1.1.2Type escape sequence to abort.Sending 5, 100-byte ICMP Echos to 10.1.1.2, timeout is 2 seconds:.....Success rate is 0 percent (0/5)Router2(config-if)# service-module 56k clock rate 38.4Router1# ping 10.1.1.2Type escape sequence to abort.Sending 5, 100-byte ICMP Echos to 10.1.1.2, timeout is 2 seconds:!!!!!Success rate is 100 percent (5/5), round-trip min/avg/max = 52/54/56 msWhen transferring from DDS mode to switched mode, you must set the correct clock rate, as shown in the following example:
Router2(config-if)# service-module 56k network-type ddsRouter2(config-if)# service-module 56k clock rate 38.4Router2(config-if)# service-module 56k network-type switched% Have to use 56k or auto clock rate for switched mode% Service module configuration command failed: WRONG FORMAT.Router2(config-if)# service-module 56k clock rate auto% WARNING - auto rate will not work in back-to-back DDS.Router2(config-if)# service-module 56k network-type switchedRelated Commands
service-module 56k clock source
To set up the clock source on a serial interface for a 4-wire, 56/64-kbps CSU/DSU module, use the service-module 56k clock source command in interface configuration mode. To specify that the clocking come from the line, use the no form of this command.
service-module 56k clock source {line | internal}
no service-module 56k clock source {line | internal}
Syntax Description
line
Uses the clocking provided by the active line coming in to the router. This is the default.
internal
Uses the internal clocking provided by the hardware module.
Defaults
Line clock
Command Modes
Interface configuration
Command History
Usage Guidelines
In most applications, the CSU/DSU should be configured with the clock source line command. For back-to-back configurations, configure one CSU/DSU with the clock source internal command and the other with clock source line command.
Examples
The following example configures internal clocking and transmission speed at 38.4 kbps.
Router(config)# interface serial 0Router(config-if)# service-module 56k clock source internalRouter(config-if)# service-module 56k clock rate 38.4Related Commands
service-module 56k data-coding
To prevent application data from replicating loopback codes when operating at 64 kbps on a 4-wire CSU/DSU, use the service-module 56k data-coding command in interface configuration mode. To enable normal transmission, use the no form of this command.
service-module 56k data-coding {normal | scrambled}
no service-module 56k data-coding {normal | scrambled}
Syntax Description
Defaults
Normal data transmission
Command Modes
Interface configuration
Command History
Usage Guidelines
Enable the scrambled configuration only in 64-kbps digital data service (DDS) mode. If the network type is set to switched, the configuration is refused.
If you transmit scrambled bit codes, both CSU/DSUs must have this command configured for successful communication.
Examples
The following example scrambles bit codes or user data before transmission:
Router(config)# interface serial 0Router(config-if)# service-module 56k clock rate 64Router(config-if)# service-module 56k data-coding scrambledRelated Commands
Configures the network line speed for a serial interface on a 4-wire, 56/64-kbps CSU/DSU module.
service-module 56k network-type
To transmit packets in switched dial-up mode or digital data service (DDS) mode using a serial interface on a 4-wire, 56/64-kbps CSU/DSU module, use the service-module 56k network-type command in interface configuration mode. To transmit from a dedicated leased line in DDS mode, use the no form of this command.
service-module 56k network-type {dds | switched}
no service-module 56k network-type {dds | switched}
Syntax Description
Defaults
DDS is enabled for the 4-wire CSU/DSU.
Switched is enabled for the 2-wire CSU/DSU.Command Modes
Interface configuration
Command History
Usage Guidelines
In switched mode, you need additional dialer configuration commands to configure dial-out numbers. Before you enable the service-module 56k network-type switched command, both CSU/DSUs must use a clock source coming from the line and have the clock rate configured to auto or 56 kbps. If the clock rate is not set correctly, this command will not be accepted.
The 2-wire and 4-wire, 56/64-kbps CSU/DSU modules use V.25 bis dial commands to interface with the router. Therefore, the interface must be configured using the dialer in-band command. Data terminal ready (DTR) dial is not supported.
Note
Any loopbacks in progress are terminated when switching between modes.
Examples
The following example configures transmission in switched dial-up mode:
Router(config)# interface serial 0Router(config-if)# service-module 56k clock rate autoRouter(config-if)# service-module 56k network-type switchedRouter(config-if)# dialer in-bandRouter(config-if)# dialer string 5550111Router(config-if)# dialer-group 1Related Commands
service-module 56k remote-loopback
To enable the acceptance of a remote loopback request on a serial interface on a 2- or 4-wire, 56/64-kbps CSU/DSU module, use the service-module 56k remote-loopback command in interface configuration mode. To disable the module from entering loopback, use the no form of this command.
service-module 56k remote-loopback
no service-module 56k remote-loopback
Syntax Description
This command has no arguments or keywords.
Defaults
Enabled
Command Modes
Interface configuration
Command History
Usage Guidelines
The no service-module 56k remote-loopback command prevents the local CSU/DSU from being placed into loopback by remote devices on the line. The line provider is still able to put the module into loopback by reversing sealing current. Unlike the T1 module, the 2- or 4-wire, 56/64-kbps CSU/DSU module can still initiate remote loopbacks with the no form of this command configured.
Examples
The following example enables transmitting and receiving remote loopbacks:
Router(config)# interface serial 0Router(config-if)# service-module 56k remote-loopbackRelated Commands
loopback remote (interface)
Loops packets through a CSU/DSU, over a DS3 link or a channelized T1 link, to the remote CSU/DSU and back.
service-module 56k switched-carrier
To select a service provider to use with a 2- or 4-wire, 56/64-kbps dial-up serial line, use the service-module 56k switched-carrier command in interface configuration mode. To enable the default service provider, use the no form of this command.
service-module 56k switched-carrier {att | sprint | other}
no service-module 56k switched-carrier {att | sprint | other}
Syntax Description
Defaults
ATT is enabled on the 4-wire, 56/64-kbps CSU/DSU module.
Sprint is enabled on the 2-wire, switched 56-kbps CSU/DSU module.Command Modes
Interface configuration
Command History
Usage Guidelines
On a Sprint network, echo-canceler tones are sent during call setup to prevent the echo cancelers from damaging digital data. The transmission of echo-canceler tones may increase call setup times by 8 seconds on the 4-wire module. Having echo cancellation enabled does not affect data traffic.
This configuration command is ignored if the network type is DDS.
Examples
The following example configures AT&T as a service provider:
Router(config)# interface serial 0Router(config-if)# service-module 56k network-type switchedRouter(config-if)# service-module 56k switched-carrier attRelated Commands
Sends packets in switched dial-up mode or DDS mode using a serial interface on a 4-wire, 56/64-kbps CSU/DSU module.
service-module analysis-module reload
To perform a graceful halt and reboot of the Network Analysis Module (NAM) software on the NM-NAM network module, use the service-module analysis-module reload command in privileged EXEC mode.
service-module analysis-module slot/unit reload
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The service-module analysis-module reload command is the Cisco IOS equivalent of the reboot NAM CLI command. These commands can be used to initiate the NAM software upgrade process or to access the NAM helper image.
Examples
The following example shows how to gracefully halt and reboot the NAM application software:
Router# service-module analysis-module 1/0 reloadDo you want to proceed with reload?[confirm]Trying to reload Service Module Analysis-Module1/0.Related Commands
service-module analysis-module reset
To reset the hardware on the Network Analysis Module (NM-NAM), use the service-module analysis-module reset command in privileged EXEC mode.
service-module analysis-module slot/unit reset
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the service-module analysis-module reset command to bring up the NM-NAM after it has been shut down using the service-module analysis-module shutdown command.
Examples
The following example shows how to reset the hardware on the NM-NAM:
Router# service-module analysis-module 1/0 resetUse reset only to recover from shutdown or failed stateWarning:May lose data on the hard disc!Do you want to reset?[confirm]Trying to reset Service Module Analysis-Module1/0.Related Commands
service-module analysis-module session
To access the Network Analysis Module (NAM) console from the router, use the service-module analysis-module session command in privileged EXEC mode.
service-module analysis-module slot/unit session [clear]
Syntax Description
Defaults
The router cannot access the NAM console.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
When entered without the clear keyword, this command opens a NAM console session from the router.
Examples
Opening a NAM console Session
The following example shows how to open a NAM console session when the NM-NAM is installed in router slot 2:
Router# service-module analysis-module 2/0 sessionTrying 10.1.1.1, 2065 ... Open<Press Return>Cisco Network Analysis Module (NM-NAM)nam1.cisco.com login: rootPassword: <password>Terminal type: vt100Cisco Network Analysis Module (NM-NAM) Console, 3.2(0.9)Copyright (c) 1999-2003 by Cisco Systems, Inc.WARNING! Default password has not been changed!root@nam1.cisco.com#Clearing the NAM Console Line
The following example shows how to clear the NAM console line when the NM-NAM is installed in router slot 1:
Router# service-module analysis-module 1/0 session clear[confirm][OK]Related Commands
ssh
Starts an encrypted session with a remote networking device.
telnet
Logs in to a host that supports Telnet.
service-module analysis-module shutdown
To gracefully halt the operating system on the Network Analysis Module (NM-NAM), use the service-module analysis-module shutdown command in privileged EXEC mode.
service-module analysis-module slot/unit shutdown [no-confirm]
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The service-module analysis-module shutdown command properly brings down the operating system of the Network Analysis Module (NM-NAM) to protect the network module's hard drive. When the operating system has been shut down, the NM-NAM can be removed from the router.
At the confirmation prompt, press Enter to confirm the action or n to cancel.
If you enter the no-confirm keyword, the confirmation prompt does not appear.
Examples
Gracefully Halt the Operating System with Confirmation
The following example shows how to gracefully halt the operating system of the NM-NAM in slot 1:
Router# service-module analysis-module 1/0 shutdownShutdown is used for Online removal of Service Module.Do you want to proceed with shutdown?[confirm]Use service module reset command to recover from shutdown.Gracefully Halt the Operating System — No Confirmation
The following example shows how to gracefully halt the operating system of the NM-NAM in slot 2 without any user confirmation:
Router# service-module analysis-module 2/0 shutdown no-confirmUse service module reset command to recover from shutdown.Related Commands
service-module analysis-module status
To display hardware and software status information about the Network Analysis Module (NM-NAM), use the service-module analysis-module status command in privileged EXEC mode.
service-module analysis-module slot/unit status
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the service-module analysis-module status command to:
•
•
Examples
The command in the following example displays information about the NM-NAM in router slot 1:
Router# service-module analysis-module 1/0 statusService Module is Cisco Analysis-Module1/0Service Module supports session via TTY line 33Service Module is in Steady stateGetting status from the Service Module, please wait...Cisco Network Analysis Module (NM-NAM), version 3.2(0.8)Related Commands
service-module backup interface
To configure an interface as a secondary or dial backup to the satellite interface, use the service module backup interface command in satellite interface configuration mode. To remove the backup interface configuration, use the no form of this command.
service module backup interface interface
no service module backup interface interface
Syntax Description
Defaults
No default behavior or values
Command Modes
Satellite interface configuration
Command History
Examples
The following example shows how to set interface async 1 as the backup to the satellite link:
Router(config-if)# service-module backup interface async1Related Commands
service-module backup mode
Sets the terrestrial backup mode for the Cisco IP VSAT satellite WAN network module (NM-1VSAT-GILAT).
service-module backup mode
To set the terrestrial dial backup mode for the Cisco IP VSAT satellite WAN network module (NM-1VSAT-GILAT), use the service-module backup mode command in satellite interface configuration mode. To return to the router (default) dial backup mode, use the no form of this command.
service-module backup mode [hub | router]
no service-module backup mode
Syntax Description
Defaults
Router dial backup mode
Command Modes
Satellite interface configuration
Command History
Usage Guidelines
Hub Dial Backup Mode
Hub dial backup mode maintains TCP connections during transitions between primary and backup links. Note, however, that hub dial backup mode provides backup for the satellite link, but not for the NM-1VSAT-GILAT network module hardware, the router satellite interface, or other router interfaces. If the satellite link goes down (for example, because of rain fade) in hub dial backup mode, the NM-1VSAT-GILAT network module connects to the hub using dial-on-demand routing (DDR). Common DDR backup links use ISDN BRIs, modems on auxiliary ports, and T1/E1 lines.
The NM-1VSAT-GILAT network module always encapsulates packets using a satellite backbone protocol before sending the packets over the satellite link. In hub dial backup mode, the NM-1VSAT-GILAT network module continues to encapsulate the packets using the satellite backbone protocol before sending the packets over the dial backup link to the hub; this is how hub dial backup mode maintains TCP connections during transitions between the primary satellite link and the dial backup link. Therefore, hub dial backup mode works only when the NM-1VSAT-GILAT network module itself is functioning properly.
Router Dial Backup Mode
If the satellite link goes down in router dial backup mode, the router uses DDR to send data out a different interface. Unlike hub dial backup mode, router dial backup mode does these things:
•
•
Examples
The following example shows how to specify hub backup mode:
Router(config-if)# service-module backup mode hubThe following example shows how to specify router backup mode:
Router(config-if)# service-module backup mode routerRelated Commands
service-module backup interface
Specifies the interface to use to back up the satellite interface.
service-module content-engine reload
To perform a graceful halt and reboot of a content engine (CE) network module operating system, use the service-module content-engine reload command in privileged EXEC mode.
service-module content-engine slot/unit reload
Syntax Description
Command Modes
Privileged EXEC
Command History
12.2(11)YT
This command was introduced.
12.2(13)T
This command was integrated into Cisco IOS Release 12.2(13)T.
Usage Guidelines
At the confirmation prompt, press Enter to confirm the action or n to cancel.
Examples
The following example gracefully halts and reboots the CE network module operating system in slot 1:
Router# service-module content-engine 1/0 reloadDo you want to proceed with reload?[confirm]Related Commands
service-module content-engine reset
To reset the hardware on a content engine (CE) network module, use the service-module content-engine reset command in privileged EXEC mode.
service-module content-engine slot/unit reset
Syntax Description
Command Modes
Privileged EXEC
Command History
12.2(11)YT
This command was introduced.
12.2(13)T
This command was integrated into Cisco IOS Release 12.2(13)T.
Usage Guidelines
At the confirmation prompt, press Enter to confirm the action or n to cancel.
Note
state because you may lose data.Examples
The following example resets the hardware on the CE network module in slot 1:
Router# service-module content-engine 1/0 resetUse reset only to recover from shutdown or failed state
Warning: May lose data on the hard disc!
Do you want to reset?[confirm]
Related Commands
service-module content-engine session
To access a content engine (CE) network module console and begin a configuration session, use the service-module content-engine session command in privileged EXEC mode.
service-module content-engine slot/unit session [clear]
Syntax Description
Command Modes
Privileged EXEC
Command History
12.2(11)YT
This command was introduced.
12.2(13)T
This command was integrated into Cisco IOS Release 12.2(13)T.
Usage Guidelines
Only one session at a time is allowed into the content engine from the internal CE network-module-side interface. This interface provides console access to the CE network module from the router command-line interface (CLI) by initiating a reverse Telnet connection that uses the IP address of the CE interface and the terminal (TTY) line associated with the CE network module. The TTY line number is calculated using the formula (n*32) + 1, where n is the number of the chassis slot that contains the CE network module. The CE interface must be up before you can use this command.
Once a session is started, you can perform any CE configuration task. You first access the CE console in a user-level shell. To access the privileged EXEC command shell, where most commands are available, use the enable command. Note that this is a Cisco Application and Content Networking System (ACNS) software command, not a Cisco IOS software command.
CE configuration tasks are described in the documentation for Cisco Application and Content Networking Software, Release 4.2. Initial CE configuration tasks are covered in the Cisco Content Delivery Networking Products Getting Started Guide, section 6, "Perform an Initial Startup Configuration."
After you finish CE configuration and exit the CE console session, use this command with the clear keyword to clear the session. At the confirmation prompt, press Enter to confirm the action or n to cancel.
Examples
The following example shows a CE session being opened for a CE network module in slot 2:
Router# service-module content-engine 2/0 session
Trying 10.10.10.1, 2129 ... OpenCE-netmodule con now availablePress RETURN to get started!CE-netmodule> enableCE-netmodule#The following example clears the session that had been used to configure the CE in the network module in slot 1:
Router# service-module content-engine 1/0 session clear[confirm][OK]Related Commands
service-module content-engine shutdown
To gracefully halt a content engine (CE) network module, use the service-module content-engine shutdown command in privileged EXEC mode.
service-module content-engine slot/unit shutdown
Syntax Description
Command Modes
Privileged EXEC
Command History
12.2(11)YT
This command was introduced.
12.2(13)T
This command was integrated into Cisco IOS Release 12.2(13)T.
Usage Guidelines
At the confirmation prompt, press Enter to confirm the action or n to cancel.
The service-module content-engine shutdown command brings down the operating system of the specified content engine network module in an orderly fashion to protect the network module's hard drive. When the system has been shut down, the network module can be removed from the router.
Examples
The following example gracefully halts the CE network module in slot 1:
Router# service-module content-engine 1/0 shutdownShutdown is used for Online removal of Service Module.Do you want to proceed with shutdown?[confirm]Use service module reset command to recover from shutdown.Related Commands
service-module content-engine status
To display configuration information related to the hardware and software on the content engine (CE) side of a CE network module, use the service-module content-engine status command in privileged EXEC mode.
service-module content-engine slot/unit status
Syntax Description
Command Modes
Privileged EXEC
Command History
12.2(11)YT
This command was introduced.
12.2(13)T
This command was integrated into Cisco IOS Release 12.2(13)T.
Usage Guidelines
Use the service-module content-engine status command to:
•
•
•
Examples
The following example displays information for a CE network module in router slot 1:
Router# service-module content-engine 1/0 statusService Module is Cisco Content-Engine1/0Service Module supports session via TTY line 33Service Module is in Steady stateGetting status from the Service Module, please wait..Application and Content Networking Software (ACNS)Copyright (c) 1999-2002 by Cisco Systems, Inc.Application and Content Networking Software Release 4.2.2 (build b3 May 6 2002)Version: ce2636-sw-<unknown-version>Compiled 18:03:40 May 6 2002 by engineerCompile Time Options: PPSystem was restarted on Mon Jan 7 20:30:37 1980.The system has been up for 8 minutes, 30 seconds.Core CPU is GenuineIntel Pentium III (Coppermine) (rev 8) running at 498MHz.246 Mbytes of Physical memory.2 FastEthernet interfaces1 Console interfaceList of disk drives:disk00: Normal (h00 c00 i00 l00) 19075MB( 18.6GB)Related Commands
service-module external ip address
To define the IP address for the external LAN interface on a content engine (CE) network module, use the service-module external ip address command in content-engine interface configuration mode. To delete the IP address associated with this interface, use the no form of this command.
service-module external ip address external-ip-addr subnet-mask
no service-module external ip address
Syntax Description
external-ip-addr
IP address of the external LAN interface on a CE network module.
subnet-mask
Subnet mask to append to the IP address.
Defaults
No default behavior or values
Command Modes
Content-engine interface configuration
Command History
12.2(11)YT
This command was introduced.
12.2(13)T
This command was integrated into Cisco IOS Release 12.2(13)T.
Examples
The following example defines an IP address for the external LAN interface on the CE network module in slot 1:
Router(config)# interface content-engine 1/0Router(config-if)# service-module external ip address 172.18.12.28 255.255.255.0Router(config-if)# exitRelated Commands
service-module ids-sensor
To reboot, reset, enable console access to, shutdown, and monitor the status of the Cisco Intrusion Detection System (IDS) network module, use the service-module ids-sensor command in privileged EXEC mode.
service-module ids-sensor slot/port {reload | reset | session | shutdown | status}
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
If a confirmation prompt is displayed, press Enter to confirm the action or n to cancel.
The Cisco IDS network module is also referred to as the NM-CIDS.
Examples
The following example gracefully halts and reboots the operating system on the Cisco IDS network module in slot 1:
Router# service-module ids-sensor 1/0 reloadDo you want to proceed with reload?[confirm]The following example resets the hardware on the Cisco IDS network module in slot 1. A warning is displayed.
Router# service-module ids-sensor 1/0 resetUse reset only to recover from shutdown or failed stateWarning: May lose data on the hard disk!Do you want to reset?[confirm]
Caution
the Cisco IDS network module. You can use the reset command safely in other situations.
The following example enables console access to the Cisco IDS network module operating system in slot 1:
Router# service-module ids-sensor 1/0 sessionThe following example shuts down IDS applications that are running on the Cisco IDS network module in slot 1:
Router# service-module ids-sensor 1/0 shutdownTrying 10.10.10.1, 2129 ... Open%SERVICEMODULE-5-SHUTDOWN2:Service module IDS-Sensor1/0 shutdown completeThe following example shows the status of the Cisco IDS software:
Router# service-module ids-sensor 1/0 statusService Module is Cisco IDS-Sensor1/0Service Module supports session via TTY line 33Service Module is in Steady stateGetting status from the Service Module, please wait...Service Module Version information received, Major ver = 1, Minor ver= 1Cisco Systems Intrusion Detection System Network ModuleSoftware version: 4.1(1)S42(0.3)Model: NM-CIDSMemory: 254676 KBRelated Commands
service-module ip address
To define the IP address for the internal network-module-side interface on a content engine network module (NM-CE-BP) or Cisco IP VSAT satellite WAN network module (NM-1VSAT-GILAT), use the service-module ip address command in content-engine interface configuration mode or satellite interface configuration mode. To delete the IP address associated with this interface, use the no form of this command.
service-module ip address nm-side-ip-address subnet-mask
no service-module ip address
Syntax Description
Defaults
No default behavior or values
Command Modes
Content-engine interface configuration
Satellite interface configurationCommand History
Usage Guidelines
Content Engine Network Module (NM-CE-BP)
There are no usage guidelines for this command.
Cisco IP VSAT Satellite WAN Network Module (NM-1VSAT-GILAT)
For the NM-1VSAT-GILAT network module, the service-module ip address command is typically not used. The NM-1VSAT-GILAT network module IP address is automatically configured when you enter the ip address command in satellite interface configuration mode to configure the IP address and subnet mask of the router satellite interface with these conditions:
•
•
If you use this method to configure the IP address for the router satellite interface, the system automatically configures the IP address and subnet mask on the NM-1VSAT-GILAT network module with these results:
•
•
You can override the automatically configured IP address and mask by manually entering the service-module ip address command.
Note
Examples
This section provides the following examples:
•
Content Engine Network Module (NM-CE-BP) Example
The following example shows how to define an IP address for the internal network-module-side interface on the CE network module in slot 1:
Router(config)# interface content-engine 1/0Router(config-if)# service-module ip address 172.18.12.26 255.255.255.0Router(config-if)# exitCisco IP VSAT Satellite WAN Network Module (NM-1VSAT-GILAT)
Example—Manually Configuring the IP AddressIn the following example, the router satellite interface is assigned an IP address (10.0.0.7), the last octet of which does not leave a remainder of 2 when divided by 4. The system displays a message to manually configure the IP address for the NM-1VSAT-GILAT network module. Notice that the IP addresses for both the router satellite interface and the NM-1VSAT-GILAT network module appear in the running configuration.
Router(config)# interface satellite 1/0Router(config-if)# ip address 10.0.0.7 255.255.255.0%VSAT-6-PIMINCOMPADDR:The IP address configured on Satellite1/0requires a manually configured IP address for the satellite moduleRouter(config-if)# service-module ip address 10.0.0.6 255.255.255.0Router(config-if)# endRouter# show running-config | begin SatelliteRouter(config)# interface Satellite 1/0Router(config-if)# ip address 10.0.0.7 255.255.255.0Router(config-if)# service-module ip address 10.0.0.6 255.255.255.0...Cisco IP VSAT Satellite WAN Network Module (NM-1VSAT-GILAT)
Example—Using the Automatically Configured IP AddressIn the following example, the router satellite interface IP address is configured as 10.0.0.6. Because the last octet of the IP address leaves a remainder of 2 when divided by 4, the system automatically configures the IP address for the NM-1VSAT-GILAT network module.
Although the NM-1VSAT-GILAT network module IP address and mask do not appear in the router configuration, you know that the IP address is 1 less than the IP address of the router satellite interface and has a subnet mask of /30. In this case, the NM-1VSAT-GILAT network module is automatically configured with the following IP address and mask: 10.0.0.5 255.255.255.252.
!Router(config)# interface Satellite 1/0Router(config-if)#ip address 10.0.0.6 255.255.255.0!Cisco IP VSAT Satellite WAN Network Module (NM-1VSAT-GILAT)
Example—Overriding the Automatically Configured IP AddressIn the following example, the router satellite interface IP address is configured as 10.0.0.6. Because the last octet of the IP address leaves a remainder of 2 when divided by 4, the system automatically configures the IP address and mask for the NM-1VSAT-GILAT network module as 10.0.0.5 255.255.255.252.
Nevertheless, the NM-1VSAT-GILAT network module IP address and mask are manually configured as 10.0.0.1 255.255.255.0 to override the automatically derived IP address and mask. Notice that the IP addresses for both the router satellite interface and the NM-1VSAT-GILAT network module appear in the running configuration.
!Router(config)# interface Satellite 1/0Router(config-if)# ip address 10.0.0.6 255.255.255.0Router(config-if)# service-module ip address 10.0.0.1 255.255.255.0!Related Commands
service-module ip default-gateway
To define a default gateway (router) for a content engine (CE) network module, use the service-module ip default-gateway command in content-engine interface configuration mode. To remove the default gateway from the CE configuration, use the no form of this command.
service-module ip default-gateway gw-ip-addr
no service-module ip default-gateway
Syntax Description
Defaults
No default behavior or values
Command Modes
Content-engine interface configuration
Command History
12.2(11)YT
This command was introduced.
12.2(13)T
This command was integrated into Cisco IOS Release 12.2(13)T.
Examples
The following example configures a default gateway for the CE network module in slot 1:
Router(config)# interface content-engine 1/0Router(config-if)# service-module ip default-gateway 172.18.12.1Router(config-if)# exitRelated Commands
service-module ip redundancy
To link the primary HSRP interface status to that of the satellite interface, use the service-module ip redundancy command in satellite interface configuration mode. To remove the link between the primary HSRP interface status and the satellite interface status, use the no form of this command.
service-module ip redundancy group-name
no service-module ip redundancy group-name
Syntax Description
group-name
Name of the hot standby group. This name must match the hot standby group name configured for the primary HSRP interface, which is typically an Ethernet interface.
Defaults
HSRP is disabled.
Command Modes
Satellite interface configuration
Command History
Usage Guidelines
Use the service-module ip redundancy command only when you have two Cisco IP VSAT satellite WAN network modules (NM-1VSAT-GILAT) on separate HSRP-redundant routers that connect to the same outdoor unit (ODU).
This command enables the satellite interface to spoof the line protocol UP state.
Examples
The following example shows how to link the primary HSRP interface status to that of the satellite interface:
service-module ip redundancy grp-hsrpRelated Commands
service-module routing redistribute
To enable the router to send its routing database to the satellite network central hub, use the service-module routing redistribute command in satellite interface configuration mode. To prevent the router from sending its routing database over the satellite network, use the no form of this command.
service-module routing redistribute
no service-module routing redistribute
Syntax Description
This command has no arguments or keywords.
Defaults
The router is enabled to send its routing database to the hub.
Command Modes
Satellite interface configuration
Command History
Usage Guidelines
The service-module routing redistribute command is used on a VSAT router, that is, an earthbound modular access router equipped with a Cisco IP VSAT satellite WAN network module (NM-1VSAT-GILAT) that connects to a satellite network. When VSAT route updates are enabled, the NM-1VSAT-GILAT network module uses Router Blade Configuration Protocol (RBCP) messages to communicate VSAT routing table changes to the hub.
Entering the no service-module routing redistribute command is useful when you do not want the hub to be aware of all the routes known by the VSAT router, such as when Network Address Translation (NAT) is configured on the router.
The hub must learn the remote VSAT routing database for the satellite network to function properly. Therefore, if you enter the no service-module routing redistribute command, one of the following actions is required:
•
•
Examples
The following example shows how to prevent the VSAT router from sending its routing database to the satellite network central hub:
Router(config-if)# no service-module routing redistributeservice-module satellite backup
To test the hub dial backup connection for the Cisco IP VSAT satellite WAN network module (NM-1VSAT-GILAT), use the service-module satellite backup command in privileged EXEC mode.
service-module satellite slot/unit backup {initiate | terminate}
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The service-module satellite backup command is used only when you configure hub dial backup for the Cisco IP VSAT satellite WAN network module (NM-1VSAT-GILAT).
Normally, the hub dial backup connection comes up only when the satellite link goes down (for example, because of a rain-fade event). The service-module satellite backup command allows you to artificially bring down the satellite link to test the hub dial backup connection.
Examples
The following example shows how to initiate a satellite backup test:
Router# service-module satellite 1/0 backup initiateThe following example shows how to terminate a running satellite backup test:
Router# service-module satellite 1/0 backup terminateRelated Commands
service-module satellite configuration
To enter satellite initial configuration mode, use the service-module satellite configuration command in user EXEC or privileged EXEC mode.
service-module satellite slot/unit configuration
Syntax Description
slot
Router chassis slot in which the network module is installed.
/unit
Interface number. For NM-1VSAT-GILAT network modules, always use 0.
Defaults
No default behavior or values.
Command Modes
User EXEC
Privileged EXECCommand History
Usage Guidelines
You need a password from your satellite service provider to enter satellite initial configuration mode.
The parameters that you configure in satellite initial configuration mode are saved directly to the network module and do not appear in the router configuration, even though you configure the parameters through the Cisco IOS CLI.
To view the parameter values that were configured in satellite initial configuration mode, use one of the following commands:
•
•
Note
Examples
The following example shows how to enter satellite initial configuration mode:
Router> service-module satellite 1/0 configurationPassword: <mypassword>Reminder:changing any parameters will result in a software reset of the module.Router(sat-init-config)>Related Commands
service-module satellite cw-mode
To enable or disable continuous wave mode, use the service-module satellite cw-mode command in satellite interface configuration mode.
service-module satellite slot/unit cw-mode {off | on frequency frequency [time time]}
Syntax Description
Defaults
Continuous wave mode is disabled.
If the time is not specified, continuous wave mode continues until turned off.Command Modes
Privileged EXEC
Command History
Usage Guidelines
Continuous wave mode can be enabled only when the Cisco IP VSAT satellite WAN network module (NM-1VSAT-GILAT) is in boot mode.
When continuous wave mode is enabled, the NM-1VSAT-GILAT network module transmits unmodulated carrier waves that can be used for dish antenna orientation adjustments and for signal quality measurements.
Note
Examples
The following example shows how to enable continuous wave mode for 2 minutes, at 900000 kilohertz:
Router# service-module satellite 1/0 cw-mode on frequency 900000 time 120CW mode obtained.The following example shows how to disable continuous wave mode:
Router# service-module satellite 1/0 cw-mode offCW mode released.The following example shows the message that appears when you try to enable continuous wave mode while the NM-1VSAT-GILAT network module is not in boot mode:
Router# service-module satellite 1/0 cw-mode on frequency 900000 time 120% CW mode NOT obtained! Valid during boot mode only.service-module satellite status
To display status information related to the hardware and software on the Cisco IP VSAT satellite WAN network module (NM-1VSAT-GILAT), including the initial configuration parameters, use the service-module satellite status command in privileged EXEC mode.
service-module satellite slot/unit status [log]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the service-module satellite status command to troubleshoot the Cisco IP VSAT satellite WAN network module (NM-1VSAT-GILAT).
Examples
See Table 15 for service-module satellite status command output field descriptions.
This section provides the following examples:
Normal Operation Example
The following example shows that the link to the hub (backbone status) is up, as is expected in normal working conditions:
Router# service-module satellite 2/0 statusGetting status from the satellite module, please wait..Software Versions, OS:14.2.2, RSP:1.5.1.3, MBC:1.0.0.5HW Version:00008100CPA Number:6204, HPS CPA:1, HSP Link:2AA Group: 258, SW Group: 512, Download: YESService Module Uptime:00:06:40, Router Uptime:1 day, 20 hours, 26 minutesCurrent router clocktime:*03:11:22.641 UTC Tue Dec 2 2003Oper Mode:OPERATIONAL, In Dial Backup:NO, Standby:NO, One-Way:NORBCP Received Packets:44, RBCP Sent Packets:41Bit Error Rate:0e-0, Signal to Noise Ratio:12.4453IP Address/Mask:10.22.1.1/255.255.255.252Service Module MAC:00:A0:AC:00:20:60RX Lock:LOCKED, Sync Lock:LOCKEDBackBone Status:UP, Two-Way Mode:YES, DA/RA Mode:RAOutbound Modulation Type:DVB, OB Code Rate:3/4Outbound Unicast Packets:61, OB Multicast Packets:23547Outbound ID:2, OB PID:514, OB Freq:1201000, OB Bit Rate:30000000Outbound Sync IP address: 172.22.0.3Inbound Start Freq:1201176, IB Stop Freq:1209336Inbound Data Rate:307200, IB Freq Offset:0Inbound Packets:3553BackBone Hub Link Status:UPBackBone Received Packets:1, BB Sent:3552BackBone Received Retransmitted:0, BB Sent Retrans:0Service Module Eth RX:3550, TX:47110Service Module Eth Multicast RX:1, Multicast TX:23563Bufs Configured:5000, Bufs Free:4951Internal Software State parameters:Service Module SW State Var:3General IOS FSM:LINK_UP, HSRP FSM:ACTIVE, HSRP VSAT Mode:ACTIVELost Beats Total:0, Lost Beats This Retry:0VOIP DA calls:NONEBoot Mode Example
The following example shows that the NM-1VSAT-GILAT network module is in boot mode after a software reset, so that the link to the hub (backbone status) is down:
Router# service-module satellite 1/0 statusGetting status from the satellite module, please wait..Software Versions, OS:0.0.0, RSP:1.0.0.5, MBC:0.0.0.0HW Version:001D1757CPA Number:6204, HPS CPA:0, HSP Link:2AA Group: 258, SW Group: 512, Download: YESService Module Uptime:00:00:14, Router Uptime:1 day, 20 hours, 19 minutesCurrent router clocktime:*03:04:38.017 UTC Tue Dec 2 2003Oper Mode:BOOT, In Dial Backup:NO, Standby:NO, One-Way:NORBCP Received Packets:1, RBCP Sent Packets:8Bit Error Rate:0e-0, Signal to Noise Ratio:12.4453IP Address/Mask:172.27.1.54/255.255.255.252Service Module MAC:00:A0:AC:00:20:60RX Lock:LOCKED, Sync Lock:NOT LOCKEDBackBone Status:DOWN, Two-Way Mode:YES, DA/RA Mode:RAOutbound Modulation Type:DVB, OB Code Rate:3/4Outbound Unicast Packets:0, OB Multicast Packets:0Outbound ID:2, OB PID:514, OB Freq:1201000, OB Bit Rate:30000000Outbound Sync IP address: 172.22.0.3Inbound Start Freq:1201176, IB Stop Freq:1209336Inbound Data Rate:307200, IB Freq Offset:0COUNTERS OMITTED. Not available at this time.Internal Software State parameters:Service Module SW State Var:3General IOS FSM:LINK_DOWN, HSRP FSM:ACTIVE, HSRP VSAT Mode:ACTIVELost Beats Total:0, Lost Beats This Retry:0VOIP DA calls:NONESoftware Reset Example
The following example shows what appears during the beginning stages of a software reset:
Router# service-module satellite 2/0 statusGetting status from the satellite module, please wait..% Satellite2/0 card is busy. Status is not available. Try later.Hub Dial Backup Example
The following example shows that the hub dial backup link is being used instead of the satellite link. Note, however, that hub dial backup keeps the backbone status up. In hub dial backup mode, the NM-1VSAT-GILAT network module connects to the hub over a specified dial backup link and maintains TCP connections.
Router# service-module satellite 1/0 statusGetting status from the satellite module, please wait..Software Versions, OS:14.2.3, RSP:1.5.1.3, MBC:1.0.0.5HW Version:00008100CPA Number:3201, HPS CPA:1, HSP Link:2AA Group: 258, SW Group: 512, Download: YESService Module Uptime:02:09:38, Router Uptime:2 hours, 10 minutesCurrent router clocktime:*19:28:20.195 UTC Wed Apr 7 2004Oper Mode:OPERATIONAL, In Dial Backup:YES, Standby:NO, One-Way:NORBCP Received Packets:31511, RBCP Sent Packets:31358Bit Error Rate:0e-0, Signal to Noise Ratio:12.4453IP Address/Mask:10.0.0.100/255.255.255.0Service Module MAC:00:A0:AC:00:20:66RX Lock:LOCKED, Sync Lock:NOT LOCKEDBackBone Status:UP, Two-Way Mode:YES, DA/RA Mode:RAOutbound Modulation Type:DVB, OB Code Rate:3/4Outbound Unicast Packets:39944, OB Multicast Packets:45612Outbound ID:2, OB PID:514, OB Freq:1201000, OB Bit Rate:30000000Outbound Sync IP address: 172.22.0.3Inbound Start Freq:1201176, IB Stop Freq:1209336Inbound Data Rate:307200, IB Freq Offset:0Inbound Packets:8281BackBone Hub Link Status:UPBackBone Received Packets:37894, BB Sent:39162BackBone Received Retransmitted:1, BB Sent Retrans:12Service Module Eth RX:37840, TX:129000Service Module Eth Multicast RX:202, Multicast TX:45970Bufs Configured:5000, Bufs Free:4949Internal Software State parameters:Service Module SW State Var:3General IOS FSM:LINK_UP, HSRP FSM:N/A, HSRP VSAT Mode:N/ALost Beats Total:0, Lost Beats This Retry:0VoIP Example
The following example shows the status of VoIP calls. Note that dedicated access (DA) mode is in use, and you can see the bandwidth (26 kilobits per second) being used on the DA channels.
Router# service-module satellite 1/0 statusGetting status from the satellite module, please wait..Software Versions, OS:14.2.3, RSP:1.5.1.3, MBC:1.0.0.5HW Version:00008100CPA Number:6202, HPS CPA:1, HSP Link:2AA Group: 258, SW Group: 512, Download: YESService Module Uptime:00:34:53, Router Uptime:2 days, 21 hours, 23 minutesCurrent router clocktime:*08:33:51.301 UTC Mon Feb 16 2004Oper Mode:OPERATIONAL, In Dial Backup:NO, Standby:NO, One-Way:NORBCP Received Packets:335, RBCP Sent Packets:332Bit Error Rate:0e-0, Signal to Noise Ratio:12.4453IP Address/Mask:10.2.0.2/255.255.0.0Service Module MAC:00:A0:AC:00:20:67RX Lock:LOCKED, Sync Lock:LOCKEDBackBone Status:UP, Two-Way Mode:YES, DA/RA Mode:DAOutbound Modulation Type:DVB, OB Code Rate:3/4Outbound Unicast Packets:758, OB Multicast Packets:139823Outbound ID:2, OB PID:514, OB Freq:1201000, OB Bit Rate:30000000Outbound Sync IP address: 172.22.0.3Inbound Start Freq:1201176, IB Stop Freq:1209336Inbound Data Rate:307200, IB Freq Offset:0Inbound Packets:346BackBone Hub Link Status:UPBackBone Received Packets:335, BB Sent:288BackBone Received Retransmitted:0, BB Sent Retrans:0Service Module Eth RX:356, TX:280163Service Module Eth Multicast RX:1, Multicast TX:139918Bufs Configured:5000, Bufs Free:4951Internal Software State parameters:Service Module SW State Var:3General IOS FSM:LINK_UP, HSRP FSM:N/A, HSRP VSAT Mode:N/ALost Beats Total:0, Lost Beats This Retry:0VOIP DA calls:Call ID BW (kb) Dst Port Src Port Dest Addr======== ======= ======== ======== ==============16075 26 18310 16866 172.20.0.2Firmware Debug Log Example
The following example includes the firmware debug message log:
Router# service-module satellite 1/0 status logGetting status from the satellite module, please wait..Software Versions, OS:14.2.3, RSP:1.5.1.3, MBC:1.0.0.5HW Version:00008100CPA Number:1203, HPS CPA:1, HSP Link:2AA Group: 258, SW Group: 512, Download: YESService Module Uptime:19:01:32, Router Uptime:1 week, 4 days, 16 hours,15 minutesCurrent router clocktime:*15:12:45.310 UTC Mon May 13 2002Oper Mode:OPERATIONAL, In Dial Backup:NO, Standby:NO, One-Way:NORBCP Received Packets:9279, RBCP Sent Packets:9276Bit Error Rate:0e-0, Signal to Noise Ratio:12.4453IP Address/Mask:172.20.0.6/255.255.255.0Service Module MAC:00:A0:AC:00:20:72RX Lock:LOCKED, Sync Lock:LOCKEDBackBone Status:UP, Two-Way Mode:YES, DA/RA Mode:RAOutbound Modulation Type:DVB, OB Code Rate:3/4Outbound Unicast Packets:11099797, OB Multicast Packets:429401Outbound ID:2, OB PID:514, OB Freq:1201000, OB Bit Rate:30000000Outbound Sync IP address: 172.22.0.3Inbound Start Freq:1201176, IB Stop Freq:1209336Inbound Data Rate:307200, IB Freq Offset:0Inbound Packets:674619BackBone Hub Link Status:UPBackBone Received Packets:11084921, BB Sent:93899BackBone Received Retransmitted:352, BB Sent Retrans:2Service Module Eth RX:10001424, TX:18532485Service Module Eth Multicast RX:2615, Multicast TX:431486Bufs Configured:5000, Bufs Free:1240Internal Software State parameters:Service Module SW State Var:3General IOS FSM:LINK_UP, HSRP FSM:N/A, HSRP VSAT Mode:N/ALost Beats Total:4, Lost Beats This Retry:0VOIP DA calls:NONELast forced reset log from card===============================bb 01 e3 a3 28 00 00 10 00 01 ff 6f f0 00 00 1000 00 2a aa 00 4f f9 5f c4 00 00 01 2a ff ff ffff 00 00 80 00 01 ff 6f f0 00 00 00 00 01 ff 76b0 01 e3 a3 28 00 00 90 02 00 00 00 00 00 00 0013 00 18 84 1c 00 00 00 00 01 e3 a3 28 00 2b 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 2b 00 00 01 ff 76 b0 00 2a a2 80 00 00 8888 00 00 90 02 00 0a 7f 58 00 00 00 00 00 00 0000 40 00 00 43 20 00 00 00 00 00 00 00 01 ff 76b0 00 00 00 00 01 ff 70 20 ff ff ffTable 15 describes the significant fields shown in the displays.
Related Commands
service-module service-engine
To enter the Cisco Unity Express command environment using a network module (NM) or an Advanced Integration Module (AIM) card module, use the service-module service-engine command in privileged EXEC mode.
service-module service-engine slot/port session
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
12.2(15)ZJ
This command was introduced for NMs.
12.3(4)T
This command was integrated into Cisco IOS Release 12.3(4)T.
12.3(7)T
Support was added for AIMs.
Usage Guidelines
This command may be used for only NMs and AIMs running Cisco Unity Express. If your system does not have this hardware, then you will be unable to enter this command.
The no form of this command (no service-module service-engine) is not available. You can enter the exit command to return to the router.
Examples
The following example shows the command for enabling the Cisco Unity Express command environment using either a NM or AIM located in slot 4, port 0:
Router# service-module service-engine 4/0 sessionRouter# Trying 172.18.106.66, 2129 ... Openservice-module t1 cablelength short
To set transmission attenuation for shorter cable lengths, use the service-module t1 cablelength short command in interface configuration mode. To disable transmission attenuation for shorter cable lengths, use the no form of this command.
service-module t1 cablelength short {110ft | 220ft | 330ft | 440ft | 550ft | 660ft}
no service-module t1 cablelength short
Syntax Description
Defaults
No default behavior or values
Command Modes
Interface configuration
Command History
12.2(15)ZL
This command was introduced.
12.3(2)T
This command was integrated into Cisco IOS Release 12.3(2)T.
Usage Guidelines
This command is intended only for the Version 2 card, WIC-1-DSU-T1 V2, as part of the service-module t1 configuration options.
Use this command to configure the transmission (tx) attenuation for cables whose length is shorter than or equal to 660 feet. The related command, service-module t1 lbo, is used to define the line-build-out values for cable lengths longer than 660ft. At any time, only one, either the short configuration or the lbo configuration, can exist. They cannot co-exist. The configuration of one command will cause the effect of the other command to cease and only the new command will be in effect.
Examples
The following example shows how to set the short cablelength to 220 feet.
Router(config)# interface serial 0/0Router(config-if)# service-module t1 cablelength short 220ftRelated Commands
service-module t1 lbo
Configures the CSU line-build-out (lbo) on a fractional T1/T1 DSU/CSU module.
service-module t1 clock source
To specify the clock source for the fractional T1/T1 CSU/DSU module, use the service-module t1 clock source command in interface configuration mode. To return to the default line clock, use the no form of this command.
service-module t1 clock source {internal | line}
no service-module t1 clock source
Syntax Description
Defaults
Line clock
Command Modes
Interface configuration
Command History
Examples
The following example sets an internal clock source on serial line 0:
Router(config)# interface serial 0Router(config-if)# service-module t1 clock source internalRelated Commands
Sets up the clock source on a serial interface for a 4-wire, 56/64-kbps CSU/DSU module.
service-module t1 data-coding
To guarantee the ones density requirement on an alternate mark inversion (AMI) line using the fractional T1/T1 module, use the service-module t1 data-coding command in interface configuration mode. To enable normal data transmission, use the no form of this command.
service-module t1 data-coding {inverted | normal}
no service-module t1 data-coding
Syntax Description
inverted
Inverts bit codes by changing all 1 bits to 0 bits and all 0 bits to 1 bits.
normal
Requests that no bit codes be inverted before transmission. This is the default.
Defaults
Normal transmission
Command Modes
Interface configuration
Command History
Usage Guidelines
Data inversion is used to guarantee the ones density requirement on an AMI line when using bit-oriented protocols such as High-Level Data Link Control (HDLC), PPP, X.25, and Frame Relay. If the time slot speed is set to 56 kbps, this command is rejected because line density is guaranteed when transmitting at 56 kbps. Use this command with the 64-kbps line speed.
If you transmit inverted bit codes, both CSU/DSUs must have this command configured for successful communication.
Examples
The following example inverts bit codes using a time slot speed of 64 kbps:
Router(config)# interface serial 0Router(config-if)# service-module t1 timeslots all speed 64Router(config-if)# service-module t1 data-coding invertedRelated Commands
Selects the linecode for the fractional T1/T1 module.
Defines time slots that constitute a fractional T1/T1 (FT1/T1) channel.
service-module t1 fdl
To set the facilities data link (FDL) parameter to either ATT or ANSI, use the service-module t1 fdl command in interface configuration mode. To ignore the FDL parameter, use the no form of this command.
service-module t1 fdl {ansi | att}
no service-module t1 fdl
Syntax Description
Defaults
Determined by the telephone company
Command Modes
Interface configuration
Command History
Usage Guidelines
The default is no service-module t1 fdl. The ansi or att options are determined by your service provider or telephone company.
Examples
The following example sets the FDL parameter to ANSI:
Router(config)# interface serial 0Router(config-if)# service-module t1 fdl ansiservice-module t1 framing
To select the frame type for a line using the fractional T1/T1 (FT1/T1) module, use the service-module t1 framing command in interface configuration mode. To revert to the default, Extended Super Frame, use the no form of this command.
service-module t1 framing {esf | sf}
no service-module t1 framing {esf | sf}
Syntax Description
esf
Specifies extended super frame (ESF) as the T1 frame type. This is the default.
sf
Specifies D4 super frame (SF) as the T1 frame type.
Defaults
esf
Command Modes
Interface configuration
Command History
Usage Guidelines
Use this command in configurations in which the router communicates with FT1/T1 data lines. The service provider determines which framing type, either esf or sf, is required for your circuit.
Examples
The following example enables Super Frame as the FT1/T1 frame type:
Router(config-if)# service-module t1 framing sfservice-module t1 lbo
To configure the CSU line-build-out (LBO) on a fractional T1/T1 CSU/DSU module, use the service-module t1 lbo command in interface configuration mode. To disable line-build-out, use the no form of this command.
service-module t1 lbo {-15 db | -7.5 db | none}
no service-module t1 lbo {-15 db | -7.5 db | none}
Syntax Description
-15 db
Decreases outgoing signal strength by 15 dB.
-7.5 db
Decreases outgoing signal strength by 7.5 dB.
none
Transmits packets without decreasing outgoing signal strength.
Defaults
Disabled
Command Modes
Interface configuration
Command History
Usage Guidelines
Use this command to decrease the outgoing signal strength to an optimum value for a fractional T1 line receiver. The ideal signal strength should be -15 dB to -22 dB, which is calculated by adding the phone company loss, cable length loss, and line build out.
You may use this command in back-to-back configurations, but it is not needed on most actual T1 lines.
Examples
The following example sets the LBO to -7.5 dB:
Router(config)# interface serial 0Router(config-if)# service-module t1 lbo -7.5 dbservice-module t1 linecode
To select the line code for the fractional T1/T1 module, use the service-module t1 linecode command in interface configuration mode. To select the default, the B8ZS line code, use the no form of this command.
service-module t1 linecode {ami | b8zs}
no service-module t1 linecode {ami | b8zs}
Syntax Description
ami
Specifies alternate mark inversion (AMI) as the line code.
b8zs
Specifies binary 8 zero substitution (B8ZS) as the line code. This is the default.
Defaults
The default line code is B8ZS.
Command Modes
Interface configuration
Command History
Usage Guidelines
Configuring B8ZS is a method of ensuring the ones density requirement on a T1 line by substituting intentional bipolar violations in bit positions four and seven for a sequence of eight zero bits. When the CSU/DSU is configured for AMI, you must guarantee the ones density requirement in your router configuration using the service-module t1 data-coding inverted command or the service-module t1 time slots speed 56 command.
Your T1 service provider determines which line code, either ami or b8zs, is required for your T1 circuit.
Examples
The following example specifies AMI as the line code:
Router(config)# interface serial 0Router(config-if)# service-module t1 linecode amiRelated Commands
Guarantees the ones density requirement on an AMI line using the fractional T1/T1 module.
Defines time slots that constitute a fractional T1/T1 (FT1/T1) channel.
service-module t1 remote-alarm-enable
To generate remote alarms (yellow alarms) at the local CSU/DSU or detect remote alarms sent from the remote CSU/DSU, use the service-module t1 remote-alarm-enable command in interface configuration mode. To disable remote alarms, use the no form of this command.
service-module t1 remote-alarm-enable
no service-module t1 remote-alarm-enable
Syntax Description
This command has no arguments or keywords.
Defaults
Remote alarms are disabled.
Command Modes
Interface configuration
Command History
Usage Guidelines
Remote alarms are transmitted by the CSU/DSU when it detects an alarm condition, such as a red alarm (loss of frame) or blue alarm (unframed ones). The receiving CSU/DSU then knows that there is an error condition on the line.
With D4 Super Frame configured, a remote alarm condition is transmitted by setting the bit 2 of each time slot to zero. For received user data that has the bit 2 of each time slot set to zero, the CSU/DSU interprets the data as a remote alarm and interrupts data transmission, which explains why remote alarms are disabled by default. With Extended Super Frame configured, the remote alarm condition is signalled out of band in the facilities data link.
You can see if the FT1/T1 CSU/DSU is receiving a remote alarm (yellow alarm) by issuing the show service-module serial command.
Examples
The following example enables remote alarm generation and detection:
Router(config)# interface serial 0Router(config-if)# service-module t1 remote-alarm-enableRelated Commands
Selects the frame type for a line using the fractional T1/T1 (FT1/T1) module.
show service-module serial
Displays performance statistics for an integrated CSU/DSU.
service-module t1 remote-loopback
To specify that the fractional T1/T1 DSU/CSU module enters loopback mode when it receives a loopback code on the line, use the service-module t1 remote-loopback command in interface configuration mode. To disable remote loopbacks, use the no form of this command.
service-module t1 remote-loopback {full | payload v54}
no service-module t1 remote-loopback {full | payload v54
Syntax Description
Use the full keyword to enable the standard loopup codes, which use a 1-in-5 pattern for loopup and a
1-in-3 pattern for loopdown. Use the payload v54 keywords to enable the v54 pseudo-random loopup codes for loopup and v54 pseudo-random loopdown codes for loopdown.Defaults
Full and payload loopbacks with standard loopup codes
Command Modes
Interface configuration
Command History
11.2
This command was introduced.
12.3(2)T
The provision for an alternate loopback code was removed.
Usage Guidelines
The no form of this command disables loopback requests. For example, the no service-module t1 remote-loopback full command ignores all full-bandwidth loopback transmissions and requests.
Configuring the no form of the command might not prevent telco line providers from looping your router in extended super frame (esf) mode because fractional T1/T1 lines use facilities data link messages to initiate loopbacks.
To have the loopback remote commands on the FT1/T1 CSU/DSU module function successfully, you need to enable the service-module t1 remote-loopback command.
Note
1-in-3 pattern for loopdown. Use the payload v54 keywords to enable the v54 pseudorandom codes for
loopup and v54 pseudorandom codes for loopdown.Examples
The following example shows how to configure two routers connected back-to-back through a fractional T1/T1 line to enter loopback mode:
Router(config)# interface serial 0/0Router(config-if)# service-module t1 remote-loopback fullRouter(config-if)# loopback remote full!%SERVICE_MODULE-5-LOOPUPREMOTE: Unit Serial0/0 - Remote unit placed in loopbackRouter(config-if)# no loopback remote%SERVICE_MODULE-5-LOOPDOWNREMOTE: Unit Serial0/0 - Remote loopback test cancelledThe following example shows how to configure two routers connected back-to-back through a fractional T1/T1 line to enter loopback mode and generate or detect payload-loopback commands:Router(config-if)# service-module t1 remote-loopback payload v54Router(config-if)# loopback remote payload%%SERVICE_MODULE-5-LOOPUPREMOTE: Unit Serial0/0 - Remote unit placed in loopbackRelated Commands
loopback remote (interface)
Loops packets through a DSU/CSU to a remote DSU/CSU and back over a channelized T1 link.
service-module t1 timeslots
To define time slots that constitute a fractional T1/T1 (FT1/T1) channel, use the service-module t1 timeslots command in interface configuration mode. To resume the default setting (all FT1/T1 time slots transmit at 64 kbps), use the no form of this command.
service-module t1 timeslots {range | all} [speed {56 | 64}]
no service-module t1 timeslots {range | all}
Syntax Description
Defaults
64 kbps is the default for all time slots.
Command Modes
Interface configuration
Command History
Usage Guidelines
This command specifies which time slots are used in fractional T1 operation and determines the amount of bandwidth available to the router in each FT1/T1 channel.
The time-slot range must match the time slots assigned to the channel group. Your service provider defines the time slots that comprise a channel group.
To use the entire T1 line, enable the service-module t1 timeslots all command.
Examples
The following example displays a series of time-slot ranges and a speed of 64 kbps:
Router(config-if)# service-module t1 timeslots 1-10,15-20,22 speed 64Related Commands
Guarantees the ones density requirement on an AMI line using the fractional T1/T1 module.
Selects the linecode for the fractional T1/T1 module.
set ip df
To change the Don't Fragment (DF) bit value in the IP header, use the set ip df command in route-map configuration mode. To disable changing the DF bit value, use the no form of this command.
set ip df {0 | 1}
no set ip df {0 | 1}
Syntax Description
0
Sets the DF bit to 0 (clears the DF bit ) and allows packet fragmentation.
1
Sets the DF bit to 1 which prohibits packet fragmentation.
Defaults
The DF bit value is not changed in the IP header.
Command Modes
Route-map configuration
Command History
Usage Guidelines
Using Path MTU Discovery (PMTUD) you can determine an MTU value for IP packets that avoids fragmentation. If ICMP messages are blocked by a router, the path MTU is broken and packets with the DF bit set are discarded. Use the set ip df command to clear the DF bit and allow the packet to be fragmented and sent. Fragmentation can slow the speed of packet forwarding on the network but access lists can be used to limit the number of packets on which the DF bit will be cleared.
Note
IP header (IPid) to zero when the DF bit is set. If the router should clear the DF bit on such a packet
and if that packet should subsequently be fragmented, then the IP receiver will probably be unable
to correctly reassemble the original IP packet.Examples
The following example shows how to clear the DF bit to allow fragmentation. In this example a router is blocking ICMP messages and breaking the path MTU. Using policy routing both the inbound and outbound packets on interface serial 0 will have their DF bit set to 0 which allows fragmentation.
interface serial 0ip policy route-map clear-df-bitroute-map clear-df-bit permit 10match ip address 111set ip df 0access-list 111 permit tcp any anyRelated Commands
ip tcp path-mtu-discovery
Enables Path MTU Discovery.
route-map
Defines a route map to control where packets are output.
show alarm-interface
To display the alarm interface controller (AIC) configuration setting and the information sent to the Cisco IOS software by the AIC, use the show alarm-interface command in privileged EXEC mode.
show alarm-interface [slot-number] [summary]
Syntax Description
slot-number
(Optional) Slot number in which the AIC was placed.
summary
(Optional) Selects the summary format for the output message.
Defaults
Displays verbose message output and displays all AICs in all slot numbers on the router.
Command Modes
Privileged EXEC
Command History
12.2(2)XG
This command was introduced on the Cisco 2600 series and Cisco 3600 series.
12.2(8)T
This command was integrated into Cisco IOS Release 12.2(8)T.
Examples
The following is sample output from the show alarm-interface summary command:
Router# show alarm-interface 5 summaryAlarm Interface Card in Slot 5:Configured IP address:10.2.130.102Status: KEEPALIVE TIMER EXPIREDAlarm Interface Card in Slot 5:Configured IP address:10.2.130.102Status:KEEPALIVE TIMER EXPIREDThe following is an example of a verbose show alarm-interface display:
Router# show alarm-interface 4Alarm Interface Card in Slot 4:Configured IP address: 10.10.10.2Status: RUNNINGTimer expires in < 11 min.Reported version: 00 00 00 01Expected version: 00 00 00 01Last Self Test result: READYLast Start-Up message:----------<AIC>: Hardware Version 1, Revision A Software Version 2, Revision A 1.0.1 Installed and running, POST passed.----------Last Status severity: 0Last Status message:----------Status----------Table 16 describes significant fields shown in this output.
Related Commands
show aps
To display information about the current automatic protection switching (APS) feature, use the show aps command in privileged EXEC mode.
show aps
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the show aps command on a router configured with a working interface. In this example, POS interface 0/0/0 is configured as a working interface in group 1, and the interface is selected (that is, active).
Router1# show apsPOS0/0/0 working group 1 channel 1 Enabled SelectedThe following is sample output from the show aps command on a router configured with a protect interface. In this example, POS interface 2/0/0 is configured as a protect interface in group 1, and the interface is not selected (the ~ indicates that the interface is not active). The output also shows that the working channel is located on the router with the IP address 10.1.6.1 and that the interface is currently selected (that is, active).
Router2# show apsPOS2/0/0 protect group 1 channel 0 bidirectional ~SelectedRx_K1= 0, Rx_K2= 0 Tx_K1= 0 Tx_K2= 5Working channel 1 at 10.1.6.1 EnabledFor the K1 field (8 bits), the first 4 bits indicate the channel number that has made the request, and the last 4 bits map to the requests (local or external) listed in Table 17. For the K2 field (8 bits), the first 4 bits indicate the channel number bridged onto the protect line, the next bit is the architecture used, and the last 3 bits indicate the mode of operation or non-APS use listed in Table 17.
show cable bundle
To display the forwarding table for the specified interface, use the show cable bundle command in privileged EXEC mode.
show cable bundle bundle-number forwarding-table
Syntax Description
bundle-number
Specifies the bundle identifier. Valid range is from 1 to 255.
forwarding-table
Displays the forwarding table for the specified interface.
Command Modes
Privileged EXEC
Command History
Examples
In the following example, a cable bundle of 25 is specified:
Router# show cable bundle 25 forwarding-tableMAC address Interface0050.7366.17ab Cable3/00050.7366.1803 Cable3/00050.7366.1801 Cable3/0Table 18 describes the significant fields shown in the display.
Table 18 show cable bundle Field Descriptions
MAC address
Media Access Control ID for each interface in the bundle.
Interface
The cable interface slot and port number.
Related Commands
show cem
To display circuit emulation (CEM) statistics, use the show cem command in privileged EXEC mode.
show cem {slot/port/channel | summary}
Syntax Description
Command Modes
Privileged EXEC
Command History
Examples
The following example shows a summary of some of the configuration parameters of the CEM channels.
Router(config-cem)# show cem summarycem summaryCSTATE: CEM stateLSTATE: line stateOSTATE: operational statePSIZE: payload-sizePCOMP: payload-compressionDPROT: data-protectionCEM CSTATE LSTATE OSTATE PSIZE PCOMP DPROT----------------------------------------------------------------------2/0/0 shutdown up config-incomplete 256 disabled disabled2/1/0 shutdown up config-incomplete 256 disabled disabled2/2/0 shutdown up config-incomplete 256 disabled disabled2/3/0 shutdown up config-incomplete 256 disabled disabled4/0/1 up up active 96 enabled disabled4/0/2 up up active 96 enabled disabled4/0/3 up up active 96 enabled disabled4/0/4 up up active 96 enabled disabled4/0/5 up up active 96 enabled disabled4/0/6 up up active 96 enabled disabled4/0/7 up up active 96 disabled disabled4/0/8 up up active 96 disabled disabled4/0/9 up up active 96 disabled disabled4/0/10 up up active 96 disabled disabled4/0/11 up up active 96 disabled disabled4/0/12 up up active 96 disabled disabled4/0/13 up up active 96 disabled disabled4/0/14 up up active 96 disabled disabled4/1/1 down down config-incomplete 96 enabled disabled4/1/2 down down config-incomplete 96 enabled disabled4/1/3 down down config-incomplete 96 enabled disabled4/1/4 down down config-incomplete 96 enabled disabled4/1/5 down down config-incomplete 96 enabled disabled4/1/6 down down config-incomplete 96 enabled disabled4/1/7 down down config-incomplete 96 disabled disabled4/1/8 down down config-incomplete 96 disabled disabled4/1/9 down down config-incomplete 96 disabled disabled4/1/10 down down config-incomplete 96 disabled disabled4/1/11 down down config-incomplete 96 disabled disabled4/1/12 down down config-incomplete 96 disabled disabled4/1/13 down down config-incomplete 96 disabled disabled4/1/14 down down config-incomplete 96 disabled disabledTable 19 describes the significant fields shown in the display.
Related Commands
cem
Enters circuit emulation configuration mode.
clear cem
Clears CEM statistics.
show chassis
To display processor and memory information, use the show chassis command in privileged EXEC mode.
show chassis [clocks | slot slot-number | split]
Syntax Description
clocks
(Optional) Displays trunk (T1/E1) clock information.
slot slot-number
(Optional) Displays slot-specific information.
split
(Optional) Displays split-related data.
Command Modes
Privileged EXEC
Command History
12.2(2)XB1
This command was introduced on the Cisco AS5850 universal gateway.
12.2(11)T
This command was integrated into Cisco IOS Release 12.2(11)T.
Usage Guidelines
You must enter this command from one of the route-switch-controller (RSC) cards.
Use the show chassis command to display additional output relevant to handover-split mode. Command output shows the RSC card to be configured with all slots of the entire chassis, regardless of configured ownership. Slots owned by the peer RSC are shown in the ignore state, properly configured and ready to go.
Examples
The following example shows output for a system in handover-split mode. Each RSC is shown to be configured with all slots in the entire chassis, regardless of whether the RSC actually owns the slot. Slots that are not owned by an RSC are shown to be in the ignore state. The RSC from which the command is entered owns slots 0 to 5, but has configured for it all slots (0 to 5 and 8 to 13—all slots except those in which the RSCs are inserted). Entries for slots 8 and 10 show the designator "ignore."
Router# show chassisSystem is in handover-split mode, RSC in slot 6.!Slots owned: 0 1 2 3 4 5Slots configured: 0 1 2 3 4 5 8 9 10 11 12 13Slots owned by other: 8 9 10 11 12 13Slot Board CPU DRAM I/O Memory State ElapsedType Util Total (free) Total (free) Time5 UP324 0%/0% 26814176( 20%) 33554432( 45%) Up 01:02:548 CT3_UP216 0( 0%) 0( 0%) Ignore 01:05:1910 UP324 0( 0%) 0( 0%) Ignore 01:05:19The following example shows output for a system in classic-split mode. The RSC from which the command is entered owns slots 0 to 5, and has configured for it only those same slots 0 to 5.
Router# show chassisSystem is in classic-split mode, RSC in slot 6.Slots owned: 0 1 2 3 4 5Slots configured: 0 1 2 3 4 5Slots owned by other: 8 9 10 11 12 13The following example shows details for the card in slot 0:
Router# show chassis slot 0Slot: 0, Type: 24 E1 Ports (700)CPU utilization: 0%/0% (5 secs); 0% (1 min); 0% (5 mins)Memory: Total(b) Used(b) Free(b) Lowest(b) Largest(b)Processor 59304928 16307688 42997240 42817836 42819352I/O 67108864 8200288 58908576 58515056 58515004State: IOS up; elapsed time in state: 13:28:35Flags:FB_FLAGS_PRESENTFB_FLAGS_LINECARDFB_FLAGS_ANALYZEDFB_FLAGS_CHECKPOINTInserted: 13:39:30 agoLast update: 00:00:08 agoTable 20 describes significant fields shown in this output.
Table 20 show chassis Fields Descriptions
Related Commands
