Table Of Contents
transmit-buffers backing-store
show ip interface
To display the usability status of interfaces configured for IP, use the show ip interface command in privileged EXEC mode.
show ip interface [type number] [brief]
Syntax Description
type
(Optional) Interface type.
number
(Optional) Interface number.
brief
(Optional) Displays a summary of the usability status information for each interface.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The Cisco IOS software automatically enters a directly connected route in the routing table if the interface is usable. A usable interface can send and receive packets. If an interface is not usable, the directly connected routing entry is removed from the routing table. Removing the entry allows the software to use dynamic routing protocols to determine backup routes to the network, if any.
If the interface can provide two-way communication, the line protocol is marked "up." If the interface hardware is usable, the interface is marked "up."
If you specify an optional interface type, you see information for that specific interface.
If you specify no optional arguments, you see information on all the interfaces.
When an asynchronous interface is encapsulated with PPP or Serial Line Internet Protocol (SLIP), IP fast switching is enabled. A show ip interface command on an asynchronous interface encapsulated with PPP or SLIP displays a message indicating that IP fast switching is enabled.
The show ip interface brief command can be used to view a summary of the router interfaces. This command displays the IP address, interface status, and additional information.
Examples
The following examples from Cisco IOS Release 12.3(14)YM2 show:
•
Configuration information on interface Gigabit Ethernet0/3, where the IP flow egress feature is configured on the output side (where packets go out of the interface) and the policy route-map named PBR_NAME is configured on the input side (where packets come into the interface).
•
The highlighted arrows (for documentation purposes only) show the configured output and input features and the additional MPF interface information.
Router# show running-config interface g 0/3interface GigabitEthernet0/3ip address 10.1.1.1 255.255.0.0ip flow egress <== outputip policy route-map PBR_NAME <== inputduplex autospeed automedia-type gbicnegotiation autoendRouter# show ip interface g 0/3GigabitEthernet0/3 is up, line protocol is upInternet address is 10.1.1.1/16Broadcast address is 255.255.255.255Address determined by setup commandMTU is 1500 bytesHelper address is not setDirected broadcast forwarding is disabledOutgoing access list is not setInbound access list is not setProxy ARP is enabledLocal Proxy ARP is disabledSecurity level is defaultSplit horizon is enabledICMP redirects are always sentICMP unreachables are always sentICMP mask replies are never sentIP fast switching is enabledIP fast switching on the same interface is disabledIP Flow switching is disabledIP CEF switching is enabledIP Feature Fast switching turbo vectorIP VPN Flow CEF switching turbo vectorIP multicast fast switching is enabledIP multicast distributed fast switching is disabledIP route-cache flags are Fast, CEFRouter Discovery is disabledIP output packet accounting is disabledIP access violation accounting is disabledTCP/IP header compression is disabledRTP/IP header compression is disabledPolicy routing is enabled, using route map PBRNetwork address translation is disabledBGP Policy Mapping is disabledIP Multi-Processor Forwarding is enabled <======== MPF informationIP Input features, "PBR",are not supported by MPF and are IGNOREDIP Output features, "NetFlow",are not supported by MPF and are IGNOREDThe following example identifies a downstream VRF. The highlighted line (for documentation purposes only) identifies the downstream VRF.
Router# show ip interface vi 3Virtual-Access3 is up, line protocol is upInterface is unnumbered. Using address of Loopback2 (10.0.0.8)Broadcast address is 255.255.255.255Peer address is 10.8.1.1MTU is 1492 bytesHelper address is not setDirected broadcast forwarding is disabledOutgoing access list is not setInbound access list is not setProxy ARP is enabledLocal Proxy ARP is disabledSecurity level is defaultSplit horizon is enabledICMP redirects are always sentICMP unreachables are always sentICMP mask replies are never sentIP fast switching is enabledIP fast switching on the same interface is enabledIP Flow switching is disabledIP CEF switching is enabledIP Feature Fast switching turbo vectorIP VPN CEF switching turbo vectorVPN Routing/Forwarding "U"Downstream VPN Routing/Forwarding "D"IP multicast fast switching is disabledIP multicast distributed fast switching is disabledIP route-cache flags are Fast, CEFRouter Discovery is disabledIP output packet accounting is disabledIP access violation accounting is disabledTCP/IP header compression is disabledRTP/IP header compression is disabledPolicy routing is disabledNetwork address translation is disabledWCCP Redirect outbound is disabledWCCP Redirect inbound is disabledWCCP Redirect exclude is disabledBGP Policy Mapping is disabledTable 53 describes the significant fields shown in the display.
The following is sample output from the show ip interface brief command:
Router# show ip interface briefInterface IP-Address OK? Method Status ProtocolEthernet0 10.108.00.5 YES NVRAM up upEthernet1 unassigned YES unset administratively down downLoopback0 10.108.200.5 YES NVRAM up upSerial0 10.108.100.5 YES NVRAM up upSerial1 10.108.40.5 YES NVRAM up upSerial2 10.108.100.5 YES manual up upSerial3 unassigned YES unset administratively down down
Related Commands
show pas eswitch address
To display the Layer 2 learned addresses for an interface, use the show pas eswitch address EXEC command.
show pas eswitch address [ethernet | fastethernet] [slot/port]
Syntax Description
ethernet | fastethernet
(Optional) Specify the type of interface.
slot
(Optional) Slot number of the interface.
port
(Optional) Interface number.
Command Modes
EXEC
Command History
Examples
The following sample output shows that the first PA-12E/2FE interface (listed below as port 0) in port adapter slot 3 has learned the Layer 2 address 00e0.f7a4.5100 for bridge group 30 (listed below as BG 30):
Router# show pas eswitch address fastethernet 3/0U 00e0.f7a4.5100, AgeTs 56273 s, BG 30 (vLAN 0), Port 0show rif
To display the current contents of the RIF cache, use the show rif EXEC command.
show rif
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Examples
The following is sample output from the show rif command:
Router# show rifCodes: * interface, - static, + remoteHardware Addr How Idle (min) Routing Information Field5C02.0001.4322 rg5 - 0630.0053.00B05A00.0000.2333 TR0 3 08B0.0101.2201.0FF05B01.0000.4444 - - -0000.1403.4800 TR1 0 -0000.2805.4C00 TR0 * -0000.2807.4C00 TR1 * -0000.28A8.4800 TR0 0 -0077.2201.0001 rg5 10 0830.0052.2201.0FF0In the display, entries marked with an asterisk (*) are the router/bridge's interface addresses. Entries marked with a dash (-) are static entries. Entries with a number are cached entries. If the RIF timeout is set to something other than the default of 15 minutes, the timeout is displayed at the top of the display.
Table 55 describes significant fields shown in the display.
show service-module serial
To display the performance report for an integrated CSU/DSU, use the show service-module serial privileged EXEC command.
show service-module serial number [performance-statistics [interval-range]]
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command applies to the 2- and 4-wire 56/64-kbps CSU/DSU module and FT1/T1 CSU/DSU module. The performance-statistics keyword applies only to the FT1/T1 CSU/DSU module.
Examples
The following sample output shows CSU/DSU performance statistics on a Cisco 2524 or Cisco 2525 router for intervals 30 to 32. Each interval is 15 minutes long. All the data is zero because no errors were discovered on the T1 line:
Router# show service-module serial 1 performance-statistics 30-32Total Data (last 58 15 minute intervals):0 Line Code Violations, 0 Path Code Violations0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail SecsData in current interval (131 seconds elapsed):0 Line Code Violations, 0 Path Code Violations0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail SecsData in Interval 30:0 Line Code Violations, 0 Path Code Violations0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail SecsData in Interval 31:0 Line Code Violations, 0 Path Code Violations0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail SecsData in Interval 32:0 Line Code Violations, 0 Path Code Violations0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail SecsThe following example is sample output from the show service-module serial command:
Router1# show service-module serial 0Module type is T1/fractionalHardware revision is B, Software revision is 1.1 ,Image checksum is 0x2160B7C, Protocol revision is 1.1Receiver has AIS alarm,Unit is currently in test mode:line loopback is in progressFraming is ESF, Line Code is B8ZS, Current clock source is line,Fraction has 24 timeslots (64 Kbits/sec each), Net bandwidth is 1536 Kbits/sec.Last user loopback performed:remote loopbackFailed to loopup remoteLast module self-test (done at startup): PassedLast clearing of alarm counters 0:05:50loss of signal : 1, last occurred 0:01:50loss of frame : 0,AIS alarm : 1, current duration 0:00:49Remote alarm : 0,Module access errors : 0,Total Data (last 0 15 minute intervals):Line Code Violations, 0 Path Code Violations0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail SecsData in current interval (351 seconds elapsed):1466 Line Code Violations, 0 Path Code Violations25 Slip Secs, 49 Fr Loss Secs, 40 Line Err Secs, 1 Degraded Mins0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 49 Unavail SecsRouter1# show service-module serial 1Module type is 4-wire Switched 56Hardware revision is B, Software revision is 1.00,Image checksum is 0x44453634, Protocol revision is 1.0Connection state: active,Receiver has loss of signal, loss of sealing current,Unit is currently in test mode:line loopback is in progressCurrent line rate is 56 Kbits/secLast user loopback performed:dte loopbackduration 00:00:58Last module self-test (done at startup): PassedLast clearing of alarm counters 0:13:54oos/oof : 3, last occurred 0:00:24loss of signal : 3, current duration 0:00:24loss of sealing curren: 2, current duration 0:04:39loss of frame : 0,rate adaption attempts: 0,The following example shows sample output from the show service-module serial command issued on a Cisco 3640 modular access router:
router# show service-module serial 0/1Module type is 4-wire Switched 56Hardware revision is B, Software revision is 1.00,Image checksum is 0x42364436, Protocol revision is 1.0Connection state: IdleReceiver has no alarms.CSU/DSU Alarm mask is 0Current line rate is 56 Kbits/secLast module self-test (done at startup): PassedLast clearing of alarm counters 4d02hoos/oof : 0,loss of signal : 0,loss of sealing curren: 0,loss of frame : 0,rate adaptation attemp: 0,The following example shows sample output from the show service-module serial command issued on a Cisco 1605 router:
router# show service-module serial 0Module type is 4-wire Switched 56Hardware revision is B, Software revision is 1.00,Image checksum is 0x42364436, Protocol revision is 1.0Receiver has oos/oof, loss of signal,CSU/DSU Alarm mask is 4Current line rate is 56 Kbits/secLast module self-test (done at startup): PassedLast clearing of alarm counters 1d02hoos/oof : 1, current duration 1d02hloss of signal : 1, current duration 1d02hloss of frame : 0,rate adaptation attemp: 0,Table 56 describes the fields displayed by the show service-module serial command.
Related Commands
show smf
To display the configured software MAC address filter (SMF) on various interfaces of a router, use the show smf EXEC command.
show smf [interface-name]
Syntax Description
interface-name
Displays information about the specified interface. Choices can include atm, ethernet, fastethernet, null, serial, tokenring, and async.
Command Modes
EXEC
Command History
Usage Guidelines
The SMF is active whenever the router is doing bridging or IRB. MAC address filtering can be used as a security feature in bridging or switching environments.
Examples
The following is sample output from the show smf command:
R2-81-7206#sh smfSoftware MAC address filter on FastEthernet0/0.2Hash Len Address Matches Act Type0x00: 0 ffff.ffff.ffff 0 RCV Physical broadcast0x0C: 0 0100.0c00.0000 0 RCV ISL vLAN Multicast0x2A: 0 0900.2b01.0001 0 RCV DEC spanning tree0xA6: 0 0010.a6ae.6000 0 RCV Interface MAC address0xC1: 0 0100.0ccc.cccd 0 RCV SSTP MAC address0xC2: 0 0180.c200.0000 0 RCV IEEE spanning tree0xC2: 1 0180.c200.0000 0 RCV IBM spanning tree0xC2: 2 0100.0ccd.cdce 0 RCV VLAN Bridge STPNTable 57 describes the fields shown in this display.
shutdown (controller)
To disable the Channelized T3 Interface Processor (CT3IP) in Cisco 7500 series routers, use the shutdown (controller) configuration command. To restart a disabled CT3IP, use the no form of this command.
shutdown
no shutdown
Syntax Description
This command has no arguments or keywords.
Defaults
Enabled
Command Modes
Controller configuration
Command History
Usage Guidelines
Shutting down the CT3IP disables all functions on the interface and sends a blue alarm to the network. This command marks the interface as unavailable. To check if the CT3IP is disabled, use the show controller t3 command.
Examples
The following example shuts down the CT3IP:
controller t3 9/0/0shutdownRelated Commands
shutdown (hub)
Use the shutdown (hub) configuration command to shut down a port on an Ethernet hub of a Cisco 2505 or Cisco 2507. Use the no form of this command to restart the disabled hub.
shutdown
no shutdown
Syntax Description
This command has no arguments or keywords.
Command Modes
Hub configuration
Command History
Examples
The following example shuts down hub 0, ports 1 through 3:
hub ethernet 0 1 3shutdownRelated Commands
shutdown (interface)
To disable an interface, use the shutdown configuration command. To restart a disabled interface, use the no form of this command.
shutdown
no shutdown
Syntax Description
This command has no arguments or keywords.
Defaults
Enabled
Command Modes
Interface configuration
Command History
Usage Guidelines
The shutdown command disables all functions on the specified interface. On serial interfaces, this command causes the DTR signal to be dropped. On Token Ring interfaces, this command causes the interface to be deinserted from the ring. On FDDI interfaces, this command causes the optical bypass switch, if present, to go into bypass mode.
This command also marks the interface as unavailable. To check whether an interface is disabled, use the EXEC command show interfaces. An interface that has been shut down is shown as administratively down in the display from this command.
Examples
The following example turns off Ethernet interface 0:
interface ethernet 0 shutdownThe following example turns the interface back on:
interface ethernet 0 no shutdownRelated Commands
Configures an interface type and enters interface configuration mode.
Displays statistics for all interfaces configured on the router or access server.
smt-queue-threshold
To set the maximum number of unprocessed FDDI station management (SMT) frames that will be held for processing, use the smt-queue-threshold global configuration command. Use the no form of this command to restore the queue to the default.
smt-queue-threshold number
no smt-queue-threshold
Syntax Description
number
Number of buffers used to store unprocessed SMT messages that are to be queued for processing. Acceptable values are positive integers.
Defaults
The default threshold value is equal to the number of FDDI interfaces installed in the router.
Command Modes
Global configuration
Command History
Usage Guidelines
This command helps ensure that the routers keep track of FDDI upstream and downstream neighbors, particularly when a router includes more than one FDDI interface.
In FDDI, upstream and downstream neighbors are determined by transmitting and receiving SMT Neighbor Information Frames (NIFs). The router can appear to lose track of neighbors when it receives an SMT frame and the queue currently contains an unprocessed frame. This occurs because the router discards incoming SMT frames if the queue is full. Discarding SMT NIF frames can cause the router to lose its upstream or downstream neighbor.
Note
Examples
The following example specifies that the SMT queue can hold ten messages. As SMT frames are processed by the system, the queue is decreased by one:
smt-queue-threshold 10snmp trap illegal-address
To issue an SNMP trap when a MAC address violation is detected on an Ethernet hub port of a Cisco 2505, Cisco 2507, or Cisco 2516 router, use the snmp trap illegal-address hub configuration command. Use the no form to disable this function.
snmp trap illegal-address
no snmp trap illegal-address
Syntax Description
This command has no arguments or keywords.
Defaults
No SNMP trap is issued.
Command Modes
Hub configuration
Command History
Usage Guidelines
In addition to setting the snmp trap illegal-address command on the Ethernet hub, you can set the frequency that the trap is sent to the network management station (NMS). This is done on the NMS via the Cisco Repeater MIB. The frequency of the trap can be configured for once only or at a decaying rate (the default). If the decaying rate is used, the first trap is sent immediately, the second trap is sent after one minute, the third trap is sent after two minutes, and so on until 32 minutes at which time the trap is sent every 32 minutes. If you use a decaying rate, you can also set the trap acknowledgment so the trap will be acknowledged after it is received and will no longer be sent to the network management station.
Because traps are not reliable, additional information on a port basis is provided by the Cisco Repeater MIB. The network management function can query the following information: the last illegal MAC source address, the illegal address trap acknowledgment, the illegal address trap enabled, the illegal address first heard (timestamp), the illegal address last heard (timestamp), the last illegal address trap count for the port, and the illegal address trap total count for the port.
In addition to issuing a trap when a MAC address violation is detected, the port is also disabled as long as the MAC address is invalid. The port is enabled and the trap is no longer sent when the MAC address is valid (that is, either the address was configured correctly or learned).
Examples
The following example enables an SNMP trap to be issued when a MAC address violation is detected on hub ports 2, 3, or 4. SNMP support must already be configured on the router.
hub ethernet 0 2 4snmp trap illegal-addressRelated Commands
source-address
To configure source address control on a port on an Ethernet hub of a Cisco 2505 or Cisco 2507, use the source-address hub configuration command. To remove a previously defined source address, use the no form of this command.
source-address [mac-address]
no source-address
Syntax Description
Defaults
Disabled
Command Modes
Hub configuration
Command History
Usage Guidelines
If you omit the MAC address, the hub uses the value in the last source address register, and if the address register is invalid, it will remember the first MAC address it receives on the previously specified port, and allow only packets from that MAC address onto that port.
Examples
The following example configures the hub to allow only packets from MAC address 1111.2222.3333 on port 2 of hub 0:
hub ethernet 0 2source-address 1111.2222.3333The following example configures the hub to use the value of the last source address register. If the address register is invalid, it will remember the first MAC address it receives on port 2, and allow only packets from the learned MAC address on port 2:
hub ethernet 0 2source-addressRelated Commands
speed
To configure the speed for a Fast Ethernet interface, use the speed interface configuration command. Use the no form of this command to disable a speed setting.
speed {10 | 100 | auto}
no speed
Syntax Description
Defaults
100 Mbps
Command Modes
Interface configuration
Command History
Usage Guidelines
The auto negotiation capability is turned on for the Fast Ethernet interface by either configuring the speed auto interface configuration command or the duplex auto interface configuration command.
Table 58 describes the system's performance for different combinations of the duplex and speed modes. The specified duplex command configured with the specified speed command produces the resulting system action.
Examples
The following example shows the configuration options for the speed command:
router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.router(config)# interface fastethernet 0router(config-if)# speed ?10 Force 10 Mbps operation100 Force 100 Mbps operationauto Enable AUTO speed configurationRelated Commands
squelch
To extend the Ethernet twisted-pair 10BaseT capability beyond the standard 100 meters on the Cisco 4000 platform, use the squelch interface configuration command. To restore the default, use the no form of this command.
squelch {normal | reduced}
no squelch {normal | reduced}
Syntax Description
Defaults
Normal range
Command Modes
Interface configuration
Command History
Examples
The following example extends the twisted-pair 10BaseT capability on the cable attached to Ethernet interface 2:
interface ethernet 2 squelch reducedt1 bert
To enable or disable a BERT test pattern for a T1 channel on the Channelized T3 Interface Processor (CT3IP) in Cisco 7500 series routers, use the t1 bert controller configuration command. To disabled a BERT test pattern, use the no form of this command.
t1 channel bert pattern {0s | 1s | 2^15 | 2^20 | 2^23} interval minutes
no t1 channel bert pattern {0s | 1s | 2^15 | 2^20 | 2^23} interval minutes
Syntax Description
Defaults
No BERT test is performed.
Command Modes
Controller configuration
Command History
Usage Guidelines
The BERT test patterns from the CT3IP are framed test patterns (that is, the test patterns are inserted into the payload of the framed T1 signal).
To view the BERT results, use the show controller t3 or show controller t3 brief EXEC command. The BERT results include the following information:
•
•
•
•
•
•
When the T1 channel has a BERT test running, the line state is DOWN. Also, when the BERT test is running and the Status field is Not Sync, the information in the total bit errors field is not valid. When the BERT test is done, the Status field is not relevant.
The t1 bert command is not written to NVRAM because it is only used for testing the T1 channel for a short predefined interval and to avoid accidentally saving the command, which could cause the interface not to come up the next time the router reboots.
Note
Examples
The following example runs a BERT test pattern of all zeros for 30 minutes on T1 channel 6 on the CT3IP in slot 9:
controller t3 9/0/0t1 6 bert pattern 0s interval 30t1 clock source
To specify where the clock source is obtained for use by each T1 channel on the Channelized T3 Interface Processor (CT3IP) in Cisco 7500 series routers, use the t1 clock source controller configuration command.
t1 channel clock source {internal | line}
Syntax Description
channel
Number between 1 and 28 that indicates the T1 channel.
internal
Specifies that the internal clock source is used. This is the default.
line
Specifies that the network clock source is used.
Defaults
Internal
Command Modes
Controller configuration
Command History
Usage Guidelines
If you do not specify the t1 clock source command, the default clock source of internal is used by all the T1s on the CT3IP.
You can also set the clock source for the CT3IP by using the clock source (CT3IP) controller configuration command.
Note
Examples
The following example sets the clock source for T1 6 and T1 8 on the CT3IP to line:
controller t3 9/0/0t1 6 clock source linet1 8 clock source lineRelated Commands
Specifies where the clock source is obtained for use by the CT3IP in Cisco 7500 series routers.
t1 external
To specify that a T1 channel on the Channelized T3 Interface Processor (CT3IP) in Cisco 7500 series routers is used as an external port so the T1 channel can be further multiplexed on the Multichannel Interface Processor (MIP) or other multiplexing equipment, use the t1 external controller configuration command. Use the no form of this command to remove a T1 as an external port.
t1 external channel [cablelength feet] [linecode ami | b8zs]
no t1 external channel
Syntax Description
Defaults
No external T1 is specified.
Command Modes
Controller configuration
Command History
Usage Guidelines
The first three T1 channels (1, 2, and 3) of the CT3IP can be broken out to the DSUP-15 connectors on the CPT3IP so the T1 channel can be further demultiplexed by the MIP on the same router or on another router.
After you configure the external T1 channel, you can continue configuring it as a channelized T1 (also referred to as fractional T1) from the MIP. All channelized T1 commands might not be applicable to the T1 interface. After you configure the channelized T1 on the MIP, you can continue configuring it as you would a normal serial interface. All serial interface commands might not be applicable to the T1 interface.
The line coding on the T1 channel and the MIP must be the same. Because the default line coding format on the T1 channel is B8ZS and the default line coding on the MIP is AMI, you must change the line coding on the MIP or on the T1 so that they match.
To determine if the external device connected to the external T1 port is configured and cabled correctly before configuring an external port, use the show controller t3 command and locate the line Ext1... in the display output. The line status can be one of the following:
•
•
•
Note
Note
Examples
The following example configures the T1 1 on the CT3IP as an external port using AMI line coding and a cable length of 300 feet:
controller t3 9/0/0t1 external 1 cablelength 300 linecode amiRelated Commands
t1 fdl ansi
To enable the one-second transmission of the remote performance reports via the Facility Data Link (FDL) per ANSI T1.403 for a T1 channel on the Channelized T3 Interface Processor (CT3IP) in Cisco 7500 series routers, use the t1 fdl ansi controller configuration command. Use the no form of this command to disable the performance report.
t1 channel fdl ansi
no t1 channel fdl ansi
Syntax Description
Defaults
Disabled
Command Modes
Controller configuration
Command History
Usage Guidelines
The t1 fdl ansi command can be used only if the T1 framing type is extended superframe (ESF).
To display the remote performance report information, use the show controllers t3 remote performance command.
Note
Examples
The following example generates the performance reports for T1 channel 8 on the CT3IP:
controller t3 9/0/0t1 8 fdl ansiRelated Commands
t1 framing
To specify the type of framing used by the T1 channels on the Channelized T3 Interface Processor (CT3IP) in Cisco 7500 series routers, use the t1 framing controller configuration command.
t1 channel framing {esf | sf}
Syntax Description
Defaults
Extended super frame (ESF)
Command Modes
Controller configuration
Command History
Usage Guidelines
If you do not specify the t1 framing command, the default ESF is used.
Note
Examples
The following example sets the framing for the T1 6 and T1 8 on the CT3IP to sf:
controller t3 9/0/0t1 6 framing sft1 8 framing sft1 linecode
To specify the type of line coding used by the T1 channels on the Channelized T3 Interface Processor (CT3IP) in Cisco 7500 series routers, use the t1 linecode controller configuration command.
t1 channel linecode {ami | b8zs}
Syntax Description
Defaults
B8ZS
Command Modes
Controller configuration
Command History
Usage Guidelines
If you do not specify the t1 linecode command, the default B8ZS is used.
AMI Line Coding
If you select ami line coding for the T1 channel, you must also invert the data on the T1 channel by using the invert data interface command. This is required because the T1 channel is bundled into the T3 signal, so there are no local T1 line drivers and receivers associated with it. Therefore, the t1 channel linecode ami command does not modify local line driver settings. Rather, it advises the CT3IP what line code the remote T1 is using. The CT3IP uses this information solely for the purpose of determining whether or not to enable the pulse density enforcer for that T1 channel.
B8ZS Line Coding
When you select b8zs line coding, the pulse density enforcer is disabled. When you select ami line coding, the pulse density enforcer is enabled. To avoid having the pulse density enforcer corrupt data, the T1 channel should be configured for inverted data.
Note
Examples
The following example sets the line coding for T1 channel 16 on the CT3IP to AMI:
controller t3 9/0/0t1 16 linecode amiexitinterface serial 9/0/0:16invert dataRelated Commands
Loops packets through a CSU/DSU, over a DS3 link or a channelized T1 link, to the remote CSU/DSU and back.
t1 test
To break out a T1 channel on the Channelized T3 Interface Processor (CT3IP) in Cisco 7500 series routers to the test port for testing, use the t1 test controller configuration command. Use the no form of this command to remove the T1 channel from the test port.
t1 test channel [cablelength feet] [linecode {ami | b8zs}]
no t1 test channel
Syntax Description
Defaults
No test port is configured
Command Modes
Controller configuration
Command History
Usage Guidelines
You can use the T1 test port available on the CT3IP to break out any of the 28 T1 channels for testing (for example, 24-hour BERT testing as is commonly done by telephone companies before a line is brought into service).
The T1 test port is also available as an external port. For more information on configuring an external port, see the t1 external controller configuration command.
To determine if the external device connected to the T1 test port is configured and cabled correctly before configuring a test port, use the show controller t3 command and locate the line Ext1... in the display output. The line status can be one of the following:
•
•
•
Note
Note
Examples
The following example configures T1 6 on the CT3IP as a test port using the default cable length and line coding:
controller t3 9/0/0t1 test 6Related Commands
t1 timeslot
To specify the timeslots and data rate used on each T1 channel on the Channelized T3 Interface Processor (CT3IP) in Cisco 7500 series routers, use the t1 timeslot controller configuration command. Use the no form of this command to remove the configured T1 channel.
t1 channel timeslot range [speed {56 | 64}]
no t1 channel timeslot
Syntax Description
Defaults
No timeslots are specified for the T1 channel.
Command Modes
Controller configuration
Command History
Usage Guidelines
You must specify the timeslots used by each T1 channel.
Note
Examples
The following example assigns timeslots 1 through 24 to T1 1 for full T1 bandwidth usage:
controller t3 9/0/0t1 1 timeslots 1-24The following example assigns timeslots 1 to 5 and 20 to 23 to T1 6 for fractional T1 bandwidth usage:
controller t3 9/0/0t1 6 timeslots 1-5,20-23The following example configures T1 8 for n x 56 (where n is 24) bandwidth usage:
controller t3 9/0/0t1 8 timeslots 1-24 speed 56t1 yellow
To enable detection and generation of yellow alarms for a T1 channel on the Channelized T3 Interface Processor (CT3IP) in Cisco 7500 series routers, use the t1 yellow controller configuration command. Use the no form of this command to disable the detection and generation of yellow alarms.
t1 channel yellow {detection | generation}
no t1 channel yellow {detection | generation}
Syntax Description
channel
Number between 1 and 28 that indicates the T1 channel.
detection
Detect yellow alarms.
generation
Generate yellow alarms.
Defaults
Yellow alarms are detected and generated on the T1 channel.
Command Modes
Controller configuration
Command History
Usage Guidelines
If the T1 framing type is superframe (SF), you should consider disabling yellow alarm detection because the yellow alarm can be incorrectly detected with SF framing.
Note
Examples
The following example disables the yellow alarm detection on T1 channel 6 on the CT3IP:
controller t3 9/0/0t1 6 framing sfno t1 6 yellow detectiontest interface fastethernet
Use the test interface fastethernet EXEC command to test the Fast Ethernet interface by causing the interface to ping itself.
test interface fastethernet number
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
This command sends pings from the specified interface to itself. Unlike the ping command, the test interface fastethernet command does not require the use of an IP address.
Examples
The following example tests a Fast Ethernet interface on a Cisco 4500:
test interface fastethernet 0Related Commands
test service-module
To perform self-tests on an integrated CSU/DSU serial interface module, such as a 4-wire, 56/64 kbps CSU/DSU, issue the test service-module privileged EXEC command.
test service-module type number
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
A series of tests are performed on the CSU/DSU, which include a ROM checksum test, RAM test, EEPROM checksum test, flash checksum test, and a DTE loopback with an internal pattern test. These self-tests are also performed at power on.
This command cannot be used if a DTE loopback, line loopback, or remote loopback is in progress.
Data transmission is interrupted for five seconds when you issue this command. To view the output of the most recent self-tests, enable the show service-module command.
Examples
This example performs a self test on serial interface 0:
Router# test service-module serial 0SERVICE_MODULE(0): Performing service-module self testSERVICE_MODULE(0): self test finished: PassedRelated Commands
Clears the interface counters.
Resets an integrated CSU/DSU.
Displays the performance report for an integrated CSU/DSU.
timeslot
To enable framed mode serial interface on a G.703 E1 port adapter, an FSIP, or an E1-G.703/G.704 serial port adapter, use the timeslot interface configuration command. To restore the default, use the no form of this command or set the start slot to 0.
timeslot start-slot - stop-slot
no timeslot
Syntax Description
Defaults
A G.703 E1 interface is configured for unframed mode.
Command Modes
Interface configuration
Command History
10.3
This command was introduced.
11.1 CA
This command was modified to include the E1-G.703/G.704 serial port adapter and Cisco 7200 series routers.
Usage Guidelines
This command applies to Cisco 4000, 7000, 7200, and 7500 series routers. G.703 E1 interfaces have two modes of operation, framed and unframed. When in framed mode, the range from start-slot to stop-slot gives the number of 64-kbps slots in use. There are 32 64-kbps slots available.
In framed mode, timeslot 16 is not used for data. To use timeslot 16 for data, use the ts16 interface command.
Examples
The following example enables framed mode on a serial interface on a G.703 E1 port adapter or a E1-G.703/G.704 port adapter:
interface serial 3/0timeslot 1-3Related Commands
Controls the use of timeslot 16 for data on a G.703 E1 interface or on an E1-G703/G.704 serial port adapter.
transmit-buffers backing-store
To buffer short-term traffic bursts that exceed the bandwidth of the output interface, use the transmit-buffers backing-store interface configuration command. To disable this function, use the no form of this command.
transmit-buffers backing-store
no transmit-buffers backing-store
Syntax Description
This command has no arguments or keywords.
Defaults
The default is off, unless weighted fair queueing is enabled on the interface. If weighted fair queueing is enabled on the interface, the transmit-buffers backing-store command is enabled by default.
Command Modes
Interface configuration
Command History
Usage Guidelines
If the transmit-buffers backing-store command is enabled and a full hardware transmit queue is encountered, packets are swapped out of the original memory device (MEMD) into a system buffer in DRAM. If the transmit-buffers backing-store command is not enabled and the output hold queue is full, packets are dropped instead of being copied if a full hardware transmit queue is encountered. In both cases, the original MEMD buffer is freed so that it can be reused for other input packets.
To preserve packet order, the router checks the output hold queue and outputs previously queued packets first.
Examples
The following example shows how to enable the transmit-buffers backing-store command on a FDDI interface:
Router(config)# interface fddi 3/0Router(config-if)# transmit-buffers backing-storeRelated Commands
transmit-clock-internal
When a DTE does not return a transmit clock, use the transmit-clock-internal interface configuration command to enable the internally generated clock on a serial interface on a Cisco 7200 series or Cisco 7500 series. Use the no form of this command to disable the feature.
transmit-clock-internal
no transmit-clock-internal
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Interface configuration
Command History
Examples
The following example enables the internally generated clock on serial interface 3/0 on a Cisco 7000 series or Cisco 7200 series router:
interface serial 3/0transmit-clock-internaltransmitter-delay
To specify a minimum dead-time after transmitting a packet, use the transmitter-delay interface configuration command. Use the no form of this command restores the default.
transmitter-delay delay
no transmitter-delay
Syntax Description
Defaults
0 flags or microseconds
Command Modes
Interface configuration
Command History
Usage Guidelines
This command is especially useful for serial interfaces that can send back-to-back data packets over serial interfaces faster than some hosts can receive them.
The transmitter delay feature is implemented for the following Token Ring cards: CSC-R16, CSC-R16M, CSC-1R, CSC-2R, and CSC-CTR. For the first four cards, the command syntax is the same as the existing command and specifies the number of milliseconds to delay between sending frames that are generated by the router. Transmitter delay for the CSC-CTR uses the same syntax, but specifies a relative time interval to delay between transmission of all frames.
Examples
The following example specifies a delay of 300 microseconds on serial interface 0:
interface serial 0 transmitter-delay 300ts16
To control the use of time slot 16 for data on a G.703 E1 interface or on a E1-G703/G.704 serial port adapter, use the ts16 interface configuration command. To restore the default, use the no form of this command.
ts16
no ts16
Syntax Description
This command has no arguments or keywords.
Defaults
Time slot 16 is used for signaling.
Command Modes
Interface configuration
Command History
10.3
This command was introduced.
11.1 CA
This command was modified to include the E1-G.703/G.704 serial port adapter and Cisco 7200 series routers.
Usage Guidelines
This command applies to Cisco 4000, 7000, 7200, and 7500 series routers. By default, time slot 16 is used for signaling. Use this command to configure time slot 16 to be used for data. When in framed mode, in order to get all possible subframes or timeslots, you must use the ts16 command.
Examples
The following example configures time slot 16 to be used for data on a G.703 E1 interface or a E1-G.703/G.704 serial port adapter:
ts16Related Commands
Enables framed mode serial interface on a G.703 E1 port adapter, an FSIP, or an E1-G.703/G.704 serial port adapter.
tunnel checksum
To enable encapsulator-to-decapsulator checksumming of packets on a tunnel interface, use the tunnel checksum interface configuration command. To disable checksumming, use the no form of this command.
tunnel checksum
no tunnel checksum
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Interface configuration
Command History
Usage Guidelines
This command currently applies to generic route encapsulation (GRE) only. Some passenger protocols rely on media checksums to provide data integrity. By default, the tunnel does not guarantee packet integrity. By enabling end-to-end checksums, the routers will drop corrupted packets.
Examples
In the following example, all protocols will have encapsulator-to-decapsulator checksumming of packets on the tunnel interface:
tunnel checksumtunnel destination
To specify the destination for a tunnel interface, use the tunnel destination interface configuration command. To remove the destination, use the no form of this command.
tunnel destination {hostname | ip-address}
no tunnel destination
Syntax Description
hostname
Name of the host destination
ip-address
IP address of the host destination expressed in decimal in four-part, dotted notation
Defaults
No tunnel interface destination is specified.
Command Modes
Interface configuration
Command History
Usage Guidelines
You cannot have two tunnels using the same encapsulation mode with exactly the same source and destination address. The workaround is to create a loopback interface and source packets off of the loopback interface. Refer to Network Protocols, Part 2 for more information on AppleTalk Cayman tunneling.
Examples
The following example enables Cayman tunneling:
interface tunnel0tunnel source ethernet0tunnel destination 131.108.164.19tunnel mode caymanThe following example enables GRE tunneling:
interface tunnel0appletalk cable-range 4160-4160 4160.19appletalk zone Engineeringtunnel source ethernet0tunnel destination 131.108.164.19tunnel mode gre ipRelated Commands
tunnel key
To enable an ID key for a tunnel interface, use the tunnel key interface configuration command. To remove the ID key, use the no form of this command.
tunnel key key-number
no tunnel key
Syntax Description
Defaults
Disabled
Command Modes
Interface configuration
Command History
Usage Guidelines
This command currently applies to generic route encapsulation (GRE) only. Tunnel ID keys can be used as a form of weak security to prevent misconfiguration or injection of packets from a foreign source.
Note
Note
Examples
The following example sets the tunnel key to 3:
tunnel key 3tunnel mode
To set the encapsulation mode for the tunnel interface, use the tunnel mode interface configuration command. To set to the default, use the no form of this command.
tunnel mode {aurp | cayman | dvmrp | eon | gre | ipip [decapsulate-any] | iptalk | mpls | nos}
no tunnel mode
Syntax Description
Defaults
GRE tunneling
Command Modes
Interface configuration
Command History
10.0
This command was introduced.
10.3
The following keywords were added:
•
•
•
11.2
The optional decapsulate-any keyword was added.
Usage Guidelines
You cannot have two tunnels using the same encapsulation mode with exactly the same source and destination address. The workaround is to create a loopback interface and source packets off of the loopback interface.
Cayman tunneling implements tunneling as designed by Cayman Systems. This enables our routers to interoperate with Cayman GatorBoxes. With Cayman tunneling, you can establish tunnels between two routers or between our router and a GatorBox. When using Cayman tunneling, you must not configure the tunnel with an AppleTalk network address. This means that there is no way to ping the other end of the tunnel.
Use DVMRP when a router connects to a mrouted router to run DVMRP over a tunnel. It is required to configure Protocol-Independent Multicast (PIM) and an IP address on a DVMRP tunnel.
Generic route encapsulation (GRE) tunneling can be done between our routers only. When using GRE tunneling for AppleTalk, you configure the tunnel with an AppleTalk network address. This means that you can ping the other end of the tunnel.
Examples
The following example enables Cayman tunneling:
interface tunnel 0tunnel source ethernet 0tunnel destination 131.108.164.19tunnel mode caymanThe following example enables GRE tunneling:
interface tunnel 0appletalk cable-range 4160-4160 4160.19appletalk zone Engineeringtunnel source ethernet0tunnel destination 131.108.164.19tunnel mode gre ipRelated Commands
tunnel sequence-datagrams
To configure a tunnel interface to drop datagrams that arrive out of order, use the tunnel sequence-datagrams interface configuration command. To disable this function, use the no form of this command.
tunnel sequence-datagrams
no tunnel sequence-datagrams
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Interface configuration
Command History
Usage Guidelines
This command currently applies to generic route encapsulation (GRE) only. This command is useful when carrying passenger protocols that behave poorly when they receive packets out of order (for example, LLC2-based protocols).
Examples
The following example configures the tunnel to drop datagrams that arrive out of order:
tunnel sequence-datagramstunnel source
To set a tunnel interface's source address, use the tunnel source interface configuration command. To remove the source address, use the no form of this command.
tunnel source {ip-address | type number}
no tunnel source
Syntax Description
Defaults
No tunnel interface's source address is set.
Command Modes
Interface configuration
Command History
Usage Guidelines
You cannot have two tunnels using the same encapsulation mode with exactly the same source and destination address. The workaround is to create a loopback interface and source packets off of the loopback interface.
When using tunnels to Cayman boxes, you must set the tunnel source to an explicit IP address on the same subnet as the Cayman box, not the tunnel itself.
Examples
The following example enables Cayman tunneling:
interface tunnel0tunnel source ethernet0tunnel destination 131.108.164.19tunnel mode caymanThe following example enables GRE tunneling:
interface tunnel0appletalk cable-range 4160-4160 4160.19appletalk zone Engineeringtunnel source ethernet0tunnel destination 131.108.164.19tunnel mode gre ipRelated Commands
tx-queue-limit
To control the number of transmit buffers available to a specified interface on the MCI and SCI cards, use the tx-queue-limit interface configuration command.
tx-queue-limit number
Syntax Description
Defaults
Defaults depend on the total transmit buffer pool size and the traffic patterns of all the interfaces on the card. Defaults and specified limits are displayed with the show controllers mci EXEC command.
Command Modes
Interface configuration
Command History
Usage Guidelines
This command should be used only under the guidance of a technical support representative.
Examples
The following example sets the maximum number of transmit buffers on the interface to 5:
interface ethernet 0 tx-queue-limit 5Related Commands
Guest
