-
Cisco IOS Dial Technologies Command Reference, Release 12.3
-
Introduction
-
Dial Technologies Commands: A through cas-group
-
Dial Technologies Commands: channel through cpp
-
Dial Technologies Commands: disconnect through H
-
Dial Technologies Commands: initiate through ipx
-
Dial Technologies Commands: isdn all through isdn x25
-
Dial Technologies Commands: L
-
Dial Technologies Commands: M
-
Dial Technologies Commands: N through pptp
-
Dial Technologies Commands: pri through R
-
Dial Technologies Commands: script through show dial
-
Dial Technologies Commands: show dsc through show line
-
Dial Technologies Commands: show modem through show nbf
-
Dial Technologies Commands: show port through show resource
-
Dial Technologies Commands: show sessions through show vtemplate
-
Dial Technologies Commands: shutdown through X
-
Table Of Contents
show interfaces serial bchannel
show interfaces virtual-access
show ip interface virtual-access
show dsc clock
To display information about the dial shelf controller clock, use the show dsc clock command in privileged EXEC mode with the line card execute (execute-on) command.
execute-on slot-number show dsc clock
Syntax Description
slot-number
Displays information for a specific slot. Slot number (12 or 13) must be occupied by a DSC card.
Command Modes
EXEC
Command History
Usage Guidelines
You must use the show dsc clock command from the router using the execute-on command.
Examples
The following is sample output from the show dsc clock command:
Router# execute-on slot 12 show dsc clockRouter#Primary Clock:--------------Slot: 3, Port 1, Line 0, Priority = 3 up since 00:37:56Time elapsed since last failure of the primary = 00:38:59Backup clocks:Source Slot Port Line Priority Status State--------------------------------------------------------------Trunk 1 2 0 10 Good ConfiguredAll feature boards present are getting good clock from DSCTable 47 describes the significant fields shown in the display.
Related Commands
show dsi
To display information about the dial shelf interconnect (DSI) port adapter parameters, use the show dsi command in privileged EXEC mode with the line card execute (execute-on) command.
execute-on show dsi
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The dial shelf interconnect (DSI) port adapter connects the Cisco 5814 dial shelf to the Cisco 7206 router shelf. The DSI port adapter allows data transfers between the dial shelf and the router shelf. Data is converted into packets by the feature cards, transmitted to a hub on the dial shelf controller card, and from there sent to the router shelf. Conversely, packets from the router shelf are sent to the dial shelf controller card, where they are transmitted over the backplane to the modem and trunk cards. The show dsi command is used to show information about the dial shelf interconnect hardware, interface, physical link, PCI registers, and address filters.
Examples
The following is sample output from the show dsi command:
Router# execute-on slot 1 show dsiDSI-Tx-FastEthernet0 is up, line protocol is upHardware is DEC21140A, address is 0008.26b7.b008 (bia 0008.26b7.b008)MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec, rely 255/255, load 1/255Encapsulation ARPA, loopback not set, keepalive set (10 sec)Half-duplex, 100Mb/s, 100BaseTX/FXARP type: ARPA, ARP Timeout 04:00:00Last input 01:17:09, output 00:00:00, output hang neverLast clearing of "show interface" counters neverQueueing strategy: fifoOutput queue 0/40, 0 drops; input queue 0/75, 0 drops5 minute input rate 0 bits/sec, 0 packets/sec5 minute output rate 0 bits/sec, 0 packets/sec6 packets input, 596 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants, 0 throttles0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort0 watchdog, 0 multicast0 input packets with dribble condition detected6170 packets output, 813483 bytes, 0 underruns0 output errors, 0 collisions, 1 interface resets0 babbles, 0 late collision, 0 deferred0 lost carrier, 0 no carrier0 output buffer failures, 0 output buffers swapped outDSI-Rx-FastEthernet1 is up, line protocol is upHardware is DEC21140A, address is 0008.26b7.b008 (bia 0008.26b7.b008)MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec, rely 255/255, load 1/255Encapsulation ARPA, loopback not set, keepalive set (10 sec)Full-duplex, 100Mb/s, 100BaseTX/FXARP type: ARPA, ARP Timeout 04:00:00Last input 00:00:00, output never, output hang neverLast clearing of "show interface" counters neverQueueing strategy: fifoOutput queue 0/40, 0 drops; input queue 0/75, 0 drops5 minute input rate 0 bits/sec, 0 packets/sec5 minute output rate 0 bits/sec, 0 packets/sec6280 packets input, 362493 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants, 0 throttles0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort0 watchdog, 0 multicast0 input packets with dribble condition detected0 packets output, 0 bytes, 0 underruns0 output errors, 0 collisions, 1 interface resets0 babbles, 0 late collision, 0 deferred0 lost carrier, 0 no carrier0 output buffer failures, 0 output buffers swapped outInterface DSI-Tx-FastEthernet0Hardware is DEC21140Adec21140_ds=0x604C9FC4, registers=0x3C000000, ib=0x1912E00rx ring entries=128, tx ring entries=256rxring=0x1912F00, rxr shadow=0x604CA16C, rx_head=6, rx_tail=0txring=0x1913740, txr shadow=0x604CA398, tx_head=138, tx_tail=138, tx_count=0PHY link upCSR0=0xFE024882, CSR3=0x1912F00, CSR4=0x1913740, CSR5=0xFC660000CSR6=0x320CA002, CSR7=0xFFFFA261, CSR8=0xE0000000, CSR9=0xFFFDC3FFCSR11=0xFFFE0000, CSR12=0xFFFFFF09, CSR15=0xFFFFFEC8DEC21140 PCI registers:bus_no=0, device_no=1CFID=0x00091011, CFCS=0x02800006, CFRV=0x02000022, CFLT=0x0000FF00CBIO=0x00000001, CBMA=0x48000000, CFIT=0x28140100, CFDA=0x00000000MII registers:Register 0x00: FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFFRegister 0x08: FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFFRegister 0x10: FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFFRegister 0x18: FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFFthrottled=0, enabled=0, disabled=0rx_fifo_overflow=0, rx_no_enp=0, rx_discard=0tx_underrun_err=0, tx_jabber_timeout=0, tx_carrier_loss=0tx_no_carrier=0, tx_late_collision=0, tx_excess_coll=0tx_collision_cnt=0, tx_deferred=0, fatal_tx_err=0, tbl_overflow=0HW addr filter: 0x604CABC4, ISL DisabledEntry= 0: Addr=FFFF.FFFF.FFFFEntry= 1: Addr=FFFF.FFFF.FFFFEntry= 2: Addr=FFFF.FFFF.FFFFEntry= 3: Addr=FFFF.FFFF.FFFFEntry= 4: Addr=FFFF.FFFF.FFFFEntry= 5: Addr=FFFF.FFFF.FFFFEntry= 6: Addr=FFFF.FFFF.FFFFEntry= 7: Addr=FFFF.FFFF.FFFFEntry= 8: Addr=FFFF.FFFF.FFFFEntry= 9: Addr=FFFF.FFFF.FFFFEntry=10: Addr=FFFF.FFFF.FFFFEntry=11: Addr=FFFF.FFFF.FFFFEntry=12: Addr=FFFF.FFFF.FFFFEntry=13: Addr=FFFF.FFFF.FFFFEntry=14: Addr=FFFF.FFFF.FFFFEntry=15: Addr=0008.26B7.B008Interface DSI-Rx-FastEthernet1Hardware is DEC21140Adec21140_ds=0x604DDA4C, registers=0x3C000800, ib=0x1A01FC0rx ring entries=128, tx ring entries=256rxring=0x1A020C0, rxr shadow=0x604DDBF4, rx_head=55, rx_tail=0txring=0x1A02900, txr shadow=0x604DDE20, tx_head=2, tx_tail=2, tx_count=0PHY link upCSR0=0xFE024882, CSR3=0x1A020C0, CSR4=0x1A02900, CSR5=0xFC660000CSR6=0x320CA202, CSR7=0xFFFFA261, CSR8=0xE0000000, CSR9=0xFFFDC3FFCSR11=0xFFFE0000, CSR12=0xFFFFFF09, CSR15=0xFFFFFEC8DEC21140 PCI registers:bus_no=0, device_no=2CFID=0x00091011, CFCS=0x02800006, CFRV=0x02000022, CFLT=0x0000FF00CBIO=0x00000001, CBMA=0x48000800, CFIT=0x28140100, CFDA=0x00000000MII registers:Register 0x00: FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFFRegister 0x08: FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFFRegister 0x10: FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFFRegister 0x18: FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFFthrottled=0, enabled=0, disabled=0rx_fifo_overflow=0, rx_no_enp=0, rx_discard=0tx_underrun_err=0, tx_jabber_timeout=0, tx_carrier_loss=0tx_no_carrier=0, tx_late_collision=0, tx_excess_coll=0tx_collision_cnt=0, tx_deferred=0, fatal_tx_err=0, tbl_overflow=0HW addr filter: 0x604DE64C, ISL DisabledEntry= 0: Addr=FFFF.FFFF.FFFFEntry= 1: Addr=FFFF.FFFF.FFFFEntry= 2: Addr=FFFF.FFFF.FFFFEntry= 3: Addr=FFFF.FFFF.FFFFEntry= 4: Addr=FFFF.FFFF.FFFFEntry= 5: Addr=FFFF.FFFF.FFFFEntry= 6: Addr=FFFF.FFFF.FFFFEntry= 7: Addr=FFFF.FFFF.FFFFEntry= 8: Addr=FFFF.FFFF.FFFFEntry= 9: Addr=FFFF.FFFF.FFFFEntry=10: Addr=FFFF.FFFF.FFFFEntry=11: Addr=FFFF.FFFF.FFFFEntry=12: Addr=FFFF.FFFF.FFFFEntry=13: Addr=FFFF.FFFF.FFFFEntry=14: Addr=FFFF.FFFF.FFFFEntry=15: Addr=0008.26B7.B008Table 48 describes the significant fields shown in the display.
Table 48 show dsi Field Descriptions
FastEthernet0 ... is up
... is administratively downIndicates whether the interface hardware is currently active and if it has been taken down by an administrator.
line protocol is
Indicates whether the software processes that handle the line protocol consider the line usable or if it has been taken down by an administrator.
Hardware
Hardware type (for example, MCI Ethernet, SCI,1 CBus2 Ethernet) and address.
Internet address
Internet address followed by subnet mask.
MTU
Maximum Transmission Unit of the interface.
BW
Bandwidth of the interface in kilobits per second.
DLY
Delay of the interface in microseconds.
rely
Reliability of the interface as a fraction of 255 (255/255 is 100% reliability), calculated as an exponential average over 5 minutes.
load
Load on the interface as a fraction of 255 (255/255 is completely saturated), calculated as an exponential average over 5 minutes.
Encapsulation
Encapsulation method assigned to interface.
ARP type:
Type of Address Resolution Protocol assigned.
loopback
Indicates whether loopback is set or not.
keepalive
Indicates whether keepalives are set or not.
Last input
Number of hours, minutes, and seconds since the last packet was successfully received by an interface. Useful for knowing when a dead interface failed.
output
Number of hours, minutes, and seconds since the last packet was successfully transmitted by the interface. Useful for knowing when a dead interface failed.
output hang
Number of hours, minutes, and seconds (or never) since the interface was last reset because of a transmission that took too long. When the number of hours in any of the "last" fields exceeds
24 hours, the number of days and hours is printed. If that field overflows, asterisks are printed.Last clearing
Time at which the counters that measure cumulative statistics (such as number of bytes transmitted and received) shown in this report were last reset to zero. Note that variables that might affect routing (for example, load and reliability) are not cleared when the counters are cleared.
*** indicates the elapsed time is too large to be displayed.
0:00:00 indicates the counters were cleared more than 231ms (and less than 232ms) ago.Output queue, input queue, drops
Number of packets in output and input queues. Each number is followed by a slash, the maximum size of the queue, and the number of packets dropped due to a full queue.
5 minute input rate,
5 minute output rateAverage number of bits and packets transmitted per second in the last 5 minutes. If the interface is not in promiscuous mode, it senses network traffic it sends and receives (rather than all network traffic).
The 5-minute input and output rates should be used only as an approximation of traffic per second during a given 5-minute period. These rates are exponentially weighted averages with a time constant of 5 minutes. A period of four time constants must pass before the average will be within two percent of the instantaneous rate of a uniform stream of traffic over that period.
packets input
Total number of error-free packets received by the system.
bytes
Total number of bytes, including data and MAC encapsulation, in the error free packets received by the system.
no buffer
Number of received packets discarded because there was no buffer space in the main system. Compare with ignored count. Broadcast storms on Ethernets and bursts of noise on serial lines are often responsible for no input buffer events.
Received ... broadcasts
Total number of broadcast or multicast packets received by the interface.
runts
Number of packets that are discarded because they are smaller than the medium's minimum packet size. For instance, any Ethernet packet that is less than 64 bytes is considered a runt.
giants
Number of packets that are discarded because they exceed the medium's maximum packet size. For example, any Ethernet packet that is greater than 1518 bytes is considered a giant.
input errors
Includes runts, giants, no buffer, CRC, frame, overrun, and ignored counts. Other input-related errors can also cause the input errors count to be increased, and some datagrams may have more than one error; therefore, this sum may not balance with the sum of enumerated input error counts.
CRC
Cyclic redundancy checksum generated by the originating LAN station or far-end device does not match the checksum calculated from the data received. On a LAN, this usually indicates noise or transmission problems on the LAN interface or the LAN bus itself. A high number of CRCs is usually the result of collisions or a station transmitting bad data.
frame
Number of packets received incorrectly having a CRC error and a noninteger number of octets. On a LAN, this is usually the result of collisions or a malfunctioning Ethernet device.
overrun
Number of times the receiver hardware was unable to hand received data to a hardware buffer because the input rate exceeded the receiver's ability to handle the data.
ignored
Number of received packets ignored by the interface because the interface hardware ran low on internal buffers. These buffers are different than the system buffers mentioned previously in the buffer description. Broadcast storms and bursts of noise can cause the ignored count to be increased.
abort
Number of packets whose receipt was aborted.
watchdog
Number of times watchdog receive timer expired. It happens when receiving a packet with length greater than 2048.
multicast
Number of multicast packets received.
input packets with dribble condition detected
Dribble bit error indicates that a frame is slightly too long. This frame error counter is incremented just for informational purposes; the router accepts the frame.
packets output
Total number of messages transmitted by the system.
bytes
Total number of bytes, including data and MAC encapsulation, transmitted by the system.
underruns
Number of times that the transmitter has been running faster than the router can handle. This may never be reported on some interfaces.
output errors
Sum of all errors that prevented the final transmission of datagrams out of the interface being examined. Note that this may not balance with the sum of the enumerated output errors, as some datagrams may have more than one error, and others may have errors that do not fall into any of the specifically tabulated categories.
collisions
Number of messages retransmitted due to an Ethernet collision. This is usually the result of an overextended LAN (Ethernet or transceiver cable too long, more than two repeaters between stations, or too many cascaded multiport transceivers). A packet that collides is counted only once in output packets.
interface resets
Number of times an interface has been completely reset. This can happen if packets queued for transmission were not sent within several seconds. On a serial line, this can be caused by a malfunctioning modem that is not supplying the transmit clock signal, or by a cable problem. If the system notices that the carrier detect line of a serial interface is up, but the line protocol is down, it periodically resets the interface in an effort to restart it. Interface resets can also occur when an interface is looped back or shut down.
restarts
Number of times a Type 2 Ethernet controller was restarted because of errors.
babbles
The transmit jabber timer expired.
late collision
Number of late collisions. Late collision happens when a collision occurs after transmitting the preamble.
deferred
Deferred indicates that the chip had to defer while ready to transmit a frame because the carrier was asserted.
lost carrier
Number of times the carrier was lost during transmission.
no carrier
Number of times the carrier was not present during the transmission.
output buffer failures
Number of failed buffers and number of buffers swapped out.
1 SCI = Single Cell Input
2 CBus = Command Bus
Related Commands
show dsip
To display all information about the Distributed System Interconnect Protocol (DSIP) on a Cisco AS5800, use the show dsip command in EXEC mode.
show dsip
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Usage Guidelines
Your Cisco AS5800 universal access server uses a protocol used by the Cisco 7206 router shelf to communicate back and forth with the Cisco 5814 dial shelf controller card(s) and feature cards. Although dial shelf interconnect (DSI) configuration is transparent to the user, there are several show commands to help you view your setup, and debug commands to help you troubleshoot your system.
To display a subset of this information, use the show dsip clients, show dsip nodes, show dsip ports, show dsip queue, show dsip tracing, show dsip transport, and show dsip version commands.
Examples
The following is sample output from the show dsip command. For a description of the fields shown in the sample output, refer to the individual show dsip commands listed in the "Usage Guidelines" section.
Router# show dsipDSIP Transport Statistics:IPC : input msgs=8233, bytes=699488; output msgs=8233, bytes=483558total consumed ipc msgs=682; total freed ipc msgs = 682transmit contexts in use = 11, free = 245, zombie = 0, invalid = 0ipc getmsg failures = 0, ipc timeouts=0core getbuffer failures=0, api getbuffer failures=0dsip test msgs rcvd = 2770, sent = 0CNTL: input msgs=1112, bytes=91272; output msgs=146, bytes=8760getbuffer failures=0DATA: input msgs=0, bytes=0; output msgs=426, bytes=5112DSIP Private Buffer Pool Hits = 0DSIP Registered Addresses:Shelf0 : Master: 00e0.b093.2238, Status=localShelf1 : Slot1 : 0007.5387.4808, Status=remoteShelf1 : Slot5 : 0007.5387.4828, Status=remoteShelf1 : Slot6 : 0007.5387.4830, Status=remoteShelf1 : Slot7 : 0007.5387.4838, Status=remoteShelf1 : Slot8 : 0007.5387.4840, Status=remoteShelf1 : Slot9 : 0007.5387.4848, Status=remoteShelf1 : Slot11: 0007.5387.4858, Status=remoteShelf1 : Slot12: 0007.4b67.8260, Status=remoteDSIP Clients:-------------ID Name0 Console1 Clock2 Modem3 Logger4 Trunk5 Async data6 TDM7 Dial shelf manager8 Environment Mon9 DSIP TestDsip Local Ports:----------------Client:Portname Portid In-Msgs Bytes Last-i/pConsole:Master 10004 0 0 neverClock:Master 10005 29 3464 00:00:40Modem:Master 10006 90 70162 00:23:44Logger:Master 10007 0 0 neverTrunk:Master 10008 1765 140480 00:00:08Async data:Master 10009 0 0 neverTDM:Master 1000A 7 112 00:24:19Dial shelf manager:Master 1000B 28 4752 00:00:36DSIP Test:Master 1000C 2922 2922 00:00:00Dsip Remote Ports:-----------------Client:Portname Portid Out-Msgs Bytes Last-o/p Last-actClock:Slave1 101005F 1 24 00:24:21 00:24:21Trunk:Slave1 1010061 12 1776 00:24:21 00:24:21Modem:Slave5 1050050 96 2148 00:23:56 00:24:19Modem:Slave6 1060050 105 2040 00:24:00 00:24:22Modem:Slave7 1070050 106 2188 00:23:56 00:24:20Modem:Slave8 1080050 112 2212 00:24:13 00:24:35Modem:Slave9 1090050 115 2224 00:24:09 00:24:35Modem:Slave11 10B0050 107 2192 00:24:09 00:24:32Clock:Slave12 10C000D 1 24 00:24:37 00:24:37Dial shelf manager:Slave12 10C000E 28 4752 00:00:49 00:24:35DSIP Test:Slave12 10C000F 0 0 never 00:24:35DSIP ipc queue:---------------There are 0 IPC messages waiting for acknowledgement in the transmit queue.There are 0 messages currently in use by the system.DSIP ipc seats:---------------There are 9 nodes in this IPC realm.ID Type Name Last LastSent Heard10000 Local IPC Master 0 01060000 DSIP Seat:Slave6 10 1010C0000 DSIP Seat:Slave12 2963 131080000 DSIP Seat:Slave8 10 101090000 DSIP Seat:Slave9 10 101010000 DSIP Seat:Slave1 16 161070000 DSIP Seat:Slave7 10 1010B0000 DSIP Seat:Slave11 10 101050000 DSIP Seat:Slave5 10 10DSIP version information:------------------------Local DSIP major version = 3, minor version = 2All DS slots are running DSIP versions compatible with RSLocal Clients Registered Versions:------------------------------------Client Name Major Version Minor VersionConsole 3 2Clock 1 1Modem 0 0Logger No version No versionTrunk No version No versionAsync data No version No versionTDM No version No versionDSIP Test No version No versionMismatched Remote Client Versions:-----------------------------------Related Commands
show dsip clients
To display information about Distributed System Interconnect Protocol (DSIP) clients, use the show dsip clients command in EXEC mode.
show dsip clients
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Usage Guidelines
Use this command to see whether a client is actually registered with DSIP and using its services.
Consider the following example: a client "Trunk" seems to be defunct on a particular node with absolutely no input/output activity. The command show dsip ports does not show any Trunk port among its local ports though all other client ports show up. The problem might be that the Trunk client did not even register with DSIP. To confirm this, use the show dsip clients command.
Examples
The following is sample output from the show dsip clients command. This command lists the clients.
Router# show dsip clientsID Name0 Console1 Clock2 Modem3 Logger4 Trunk5 Async data6 TDM7 Dial shelf manager8 Environment Mon9 DSIP TestRelated Commands
show dsip nodes
To display information about the processors running the Distributed System Interconnect Protocol (DSIP), use the show dsip nodes command in EXEC mode.
show dsip nodes
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Usage Guidelines
Use show dsip nodes to see the nodes (slots) connected by DSIP and the node specific sequence numbers. The former information is also available from show dsip transport. The sequence numbers are useful for support engineers while debugging a problem.
Examples
The following is sample output from the show dsip nodes command:
Router# show dsip nodesDSIP ipc nodes:---------------There are 9 nodes in this IPC realm.ID Type Name Last LastSent Heard10000 Local IPC Master 0 01130000 DSIP Dial Shelf:Slave12 12 121080000 DSIP Dial Shelf:Slave1 1 110A0000 DSIP Dial Shelf:Slave3 1 110C0000 DSIP Dial Shelf:Slave5 1 110D0000 DSIP Dial Shelf:Slave6 1 110E0000 DSIP Dial Shelf:Slave7 1 110F0000 DSIP Dial Shelf:Slave8 1 11100000 DSIP Dial Shelf:Slave9 1 1Table 49 describes the significant fields shown in the display.
Related Commands
show dsip ports
To display information about local and remote ports, use the show dsip ports command in EXEC mode.
show dsip ports [local | remote [slot]]
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
The DSIP communication going through the IPC stack uses ports. The creation of a port returns a 32-bit port ID which is the endpoint for communication between two IPC clients.
The show dsip ports command is used to check clients that are up and running:
•
To see the local ports that are created and the activity on them.
•
If no options are specified, information is displayed for both local and remote ports.
Examples
The following is sample output from the show dsip ports command:
Router# show dsip portsDsip Local Ports:----------------Client:Portname Portid In-Msgs Bytes Last-i/pConsole:Master 10004 0 0 neverClock:Master 10005 16 1800 00:00:05Modem:Master 10006 90 70162 00:10:08Logger:Master 10007 0 0 neverTrunk:Master 10008 792 62640 00:00:03Async data:Master 10009 0 0 neverTDM:Master 1000A 7 112 00:10:44Dial shelf manager:Master 1000B 15 2256 00:00:27DSIP Test:Master 1000C 1294 1294 00:00:00Dsip Remote Ports:-----------------Client:Portname Portid Out-Msgs Bytes Last-o/p Last-actClock:Slave1 101005F 1 24 00:10:46 00:10:46Trunk:Slave1 1010061 12 1776 00:10:46 00:10:46Modem:Slave5 1050050 96 2148 00:10:21 00:10:44Modem:Slave6 1060050 105 2040 00:10:25 00:10:48Modem:Slave7 1070050 106 2188 00:10:21 00:10:45Modem:Slave8 1080050 112 2212 00:10:25 00:10:47Modem:Slave9 1090050 115 2224 00:10:39 00:11:05Modem:Slave11 10B0050 107 2192 00:10:39 00:11:02Clock:Slave12 10C000D 1 24 00:11:07 00:11:07Dial shelf manager:Slave12 10C000E 15 2256 00:00:45 00:11:05DSIP Test:Slave12 10C000F 0 0 never 00:11:05Table 50 describes the significant fields shown in the display.
Related Commands
show dsip queue
To display the number of IPC messages in the transmission queue waiting for acknowledgment, use the show dsip queue command in EXEC mode.
show dsip queue
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Usage Guidelines
IPC is inter-process communication. Processes communicate by exchanging messages held in queue buffers. Use the show dsip queue to display the status of these queue buffers.
Examples
The following is sample output from the show dsip queue command when the system is operating correctly:
Router# show dsip queueDSIP ipc queue:---------------There are 0 IPC messages waiting for acknowledgment in the transmit queue.There are 0 messages currently in use by the system.Related Commands
show dsip tracing
To display Distributed System Interconnect Protocol (DSIP) tracing buffer information, use the show dsip tracing command in EXEC mode.
show dsip tracing [control | data | ipc] [slot | entries entry-number [slot]]
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
This feature allows logging of DSIP media header information. Use the show dsip tracing command to obtain important information of the various classes of DSIP packets (Control/Data/IPC) coming in. You must first use the debug dsip tracing command then use the show dsip tracing command to display the logged contents. To clear the information, use the clear dsip tracing command.
Examples
The following is sample output from the show dsip tracing command:
Router# debug dsip tracingDSIP tracing debugging is onRouter#Router# show dsip tracingDsip Control Packet Trace:----------------------------------------------------------------------------Dest:00e0.b093.2238 Src:0007.5387.4808 Type:200B SrcShelf:1 SrcSlot:1 MsgType:0 MsgLen:82 Timestamp: 00:00:03----------------------------------------------------------------------------Dest:00e0.b093.2238 Src:0007.5387.4838 Type:200B SrcShelf:1 SrcSlot:7 MsgType:0 MsgLen:82 Timestamp: 00:00:03----------------------------------------------------------------------------Dest:00e0.b093.2238 Src:0007.4b67.8260 Type:200B SrcShelf:1 SrcSlot:12 MsgType:0 MsgLen:82 Timestamp: 00:00:03----------------------------------------------------------------------------Dest:00e0.b093.2238 Src:0007.5387.4858 Type:200B SrcShelf:1 SrcSlot:11 MsgType:0 MsgLen:82 Timestamp: 00:00:03----------------------------------------------------------------------------Dest:00e0.b093.2238 Src:0007.5387.4848 Type:200B SrcShelf:1 SrcSlot:9 MsgType:0 MsgLen:82 Timestamp: 00:00:03Table 51 describes the significant fields shown in the display.
Related Commands
show dsip transport
To display information about the Distributed System Interconnect Protocol (DSIP) transport statistics for the control/data and IPC packets and registered addresses, use the show dsip transport command in EXEC mode.
show dsip transport
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Examples
The following is sample output from the show dsip transport command:
Router# show dsip transportDSIP Transport Statistics:IPC : input msgs=4105, bytes=375628; output msgs=4105, bytes=248324total consumed ipc msgs=669; total freed ipc msgs = 669transmit contexts in use = 11, free = 245, zombie = 0, invalid = 0ipc getmsg failures = 0, ipc timeouts=0core getbuffer failures=0, api getbuffer failures=0dsip test msgs rcvd = 1200, sent = 0CNTL: input msgs=488, bytes=40104; output msgs=68, bytes=4080getbuffer failures=0DATA: input msgs=0, bytes=0; output msgs=426, bytes=5112DSIP Private Buffer Pool Hits = 0DSIP Registered Addresses:Shelf0 : Master: 00e0.b093.2238, Status=localShelf1 : Slot1 : 0007.5387.4808, Status=remoteShelf1 : Slot5 : 0007.5387.4828, Status=remoteShelf1 : Slot6 : 0007.5387.4830, Status=remoteShelf1 : Slot7 : 0007.5387.4838, Status=remoteShelf1 : Slot8 : 0007.5387.4840, Status=remoteShelf1 : Slot9 : 0007.5387.4848, Status=remoteShelf1 : Slot11: 0007.5387.4858, Status=remoteShelf1 : Slot12: 0007.4b67.8260, Status=remoteRouter#Table 52 describes the significant fields shown in the display: