![]() |
Cisco IOS Wide-Area Networking Command Reference
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
show smds addresses through waas export
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Contents
show smds addresses through waas export show smds addressesTo display the individual addresses and the interface they are associated with, use the show smds addresses privileged EXEC command. Command History
show smds mapTo display all Switched Multimegabit Data Service (SMDS) addresses that are mapped to higher-level protocol addresses, use the show smds map privileged EXEC command. Command History
ExamplesThe following is sample output from the show smds map command:
Router# show smds map
Serial0: ARP maps to e180.0999.9999.FFFF multicast
Serial0: IP maps to e180.0999.9999.FFFF 172.16.42.112 255.255.255.0 multicast
Serial0: IPX 1ABC.000.0c00.d8db maps to c111.1111.1111.1111 -- dynamic, TTL: 4 min
The table below describes the fields shown in the output.
show smds trafficTo display statistics about Switched Multimegabit Data Service (SMDS) packets the router has received, use the show smds traffic privileged EXEC command. Command History
ExamplesThe following is sample output from the show smds traffic command:
Router# show smds traffic
624363 Input packets
759695 Output packets
2 DXI heartbeat sent
0 DXI heartbeat received
0 DXI DSU polls received
0 DXI DSU polls sent
0 DXI invalid test frames
0 Bad BA size errors
0 Bad Header extension errors
65 Invalid address errors
1 Bad tag errors
The table below describes the fields shown in the output.
show srcpTo display Simple Resource Coordination Protocol (SRCP) information, use the show srcp command in user EXEC or privileged EXEC mode. show vc-groupTo display the names of all virtual circuit (VC) groups, use the show vc-groupcommand in user EXEC or privileged EXEC mode. Command History
show vfiTo display information related to a virtual forwarding instance (VFI), use the show vfi command in privileged EXEC mode.
show
vfi
[checkpoint [summary] | mac static address | memory [detail] | name vfi-name [checkpoint | mac static address] | neighbor ip-addr vcid vcid mac static address]
Syntax Description
Command History
ExamplesThe following example shows status for a VFI named VPLS-2. The VC ID in the output represents the VPN ID; the virtual circuit is identified by the combination of the destination address and the virtual circuit ID.
Router# show vfi name VPLS-2
VFI name: VPLS-2, state: up
VPN ID: 100
Local attachment circuits:
Vlan2
Neighbors connected via pseudowires:
Peer Address VC ID Split-horizon
10.1.1.1 2 Y
10.1.1.2 2 Y
10.2.2.3 2 N
The table below describes the significant fields shown in the display.
The following is sample output from the show vfi command. For the Virtual Private LAN Service (VPLS) autodiscovery feature, the command output from the command output includes autodiscovery information, as shown in the following example:
Router# show vfi
Legend: RT= Route-target, S=Split-horizon, Y=Yes, N=No
VFI name: VPLS1, state: up, type: multipoint
VPN ID: 10, VPLS-ID: 9:10
RD: 9:10, RT: 10.10.10.10:150
Local attachment circuits:
Ethernet0/0.2
Neighbors connected via pseudowires:
Peer Address VC ID Discovered Router ID S
10.7.7.1 10 10.7.7.1 Y
10.7.7.2 10 10.1.1.2 Y
10.7.7.3 10 10.1.1.3 Y
10.7.7.4 10 10.1.1.4 Y
10.7.7.5 10 - Y
VFI name: VPLS2 state: up, type: multipoint
VPN ID: 11, VPLS-ID: 10.9.9.9:2345
RD: 10:11, RT: 10.4.4.4:151
Local attachment circuits:
Ethernet0/0.3
Neighbors connected via pseudowires:
Peer Address VC ID Discovered Router ID S
10.7.7.1 11 10.7.7.1 Y
10.7.7.2 11 10.1.1.5 Y
The table below describes the significant fields in the output related to VPLS autodiscovery.
The following is sample output from the show vfi command for a specified VFI named H-VPLS-A-VFI. Because the optional name keyword is entered, the checkpoint information for the specific VFI is displayed. Router# show vfi name H-VPLS-A-VFI checkpoint
VFI Active RP
Checkpointing: Allowed
ISSU Client id: 2092, Session id: 65543, Compatible with peer
VFI VFI AC VFI PW
Bulk-sync 1 1 3
Checkpoint failures: 0 3 21
Recovered at switchover: 0 0 0
Recovery failures: 0 0 0
Legend: C=Checkpointed
VFI name: H-VPLS-A-VFI, state: up, type: multipoint
VPN ID: 12, Internal ID 1 C
Local attachment circuits:
Vlan200 16387 / 8195 C
Neighbors connected via pseudowires:
Peer ID VC ID SSM IDs
10.0.0.12 12 4096 / 12292 C
10.0.0.15 12 8193 / 16389 C
10.0.0.14 12 12290 / 20486 C
The table below describes the significant fields shown in the display.
The following is sample output from the show vfi command using the memory and detail keywords.
Router# show vfi memory detail
VFI memory In-use Asked-For/Allocated Count Size Cfg/Max
----------------------------------------------------------------------------
VFI structs In-use Asked-For/Allocated Count Size Cfg/Max
----------------------------------------------------------------------------
vfi_context_t : -- --/-- -- 52 --/--
vfi_circuit_retry : -- --/-- -- 24 --/--
Total allocated: 0.000 Mb, 0 Kb, 0 bytes
The table below describes the significant fields shown in the display.
show waas acceleratorTo display information about WAAS Express accelerators, use the show waas accelerator command in privileged EXEC mode. Syntax Description
ExamplesThe following is sample output from the show waas accelerator command: Router# show waas accelerator
Accelerator Config State Operational State
----------- ------------ -----------------
http-express Enabled Shutdown
cifs-express Disabled Shutdown
ssl-express Disabled Shutdown
The table below describes the fields shown in the display.
The following is sample output from the show waas accelerator cifs-express command: Router# show waas accelerator cifs-express
Accelerator Config State Operational State
------------ ------------ -----------------
cifs-express Disabled Shutdown
CIFS-Express:
Accelerator Config Item Value
----------------------- -----
Read-Ahead Optimization Enabled
Read-Ahead size: 190
Async-Write Optimization Enabled
Quota threshold: 20
Ads Negative Cache Optimization Enabled
Timeout: 3
The table below describes the significant fields shown in the display.
The following is sample output from the show waas accelerator http-express command: Router# show waas accelerator http-express
Accelerator Config State Operational State
------------ ------------ -----------------
http-express Disabled Shutdown
HTTP-Express:
Accelerator Config Item Value
----------------------- -----
Suppress Server Encoding Disabled
DRE Hints Enabled
Metadatacache Disabled
MaxAge 86400
MinAge 60
Filter-extension All
Redirect Enabled
Unauthorized Enabled
Conditional Enabled
HTTPS Metadatacache Disabled
The table below describes the significant fields shown in the display.
The following is sample output from the show waas accelerator ssl-express command. The fields in the display are self-explanatory. Router# show waas accelerator ssl-express
Accelerator Config State Operational State
------------ ------------ -----------------
ssl-express Enabled Running
Related Commands
show waas alarmsTo display WAAS Express status and alarms, use the show waas alarms command in privileged EXEC mode. Usage GuidelinesUse this command to display the status of the WAAS Express device and display the alarms that are enabled in the system. ExamplesThe following output from the show waas alarms command shows that alarms are enabled when the WAAS Express feature license expires: Device# show waas alarms
Alarms
Connection limit exceeded: off
Too many peers discovered: off
WAAS license expired: off
WAAS license revoked: off
WAAS license deleted: on
WAAS SSL-Express CA enrolled trustpoint deleted: off
WAAS SSL-Express router certificate deleted: off
High CPU: off
The table below describes the significant fields shown in the display. Related Commands
show waas auto-discoveryTo display autodiscovery information for the WAAS Express device, use the show waas auto-discovery command in privileged EXEC mode. Command DefaultAutodiscovery information for the WAAS Express device is displayed with the associated connection states. Usage GuidelinesUse this command to display connections being optimized and connections on which optimization is being negotiated. ExamplesThe following is sample output from the show waas auto-discovery list command: Router> enable Router# show waas auto-discovery list E: Established, S: Syn, A: Ack, F: Fin, R: Reset M: eMbryonic s: sent, r: received, O: Options, P: Passthrough Src-IP:Port Dst-IP:Port Orig-St Term-St 192.168.111.111:65531 192.168.200.200:65531 Sr SOs The table below describes the significant fields shown in the display.
The following is sample output from the show waas auto-discovery blacklist command: Router> enable Router# show waas auto-discovery blacklist Server IP Insert Time State 192.168.111.111:65531 Tue Jul 27 16:16:19 2010 Grey The table below describes the significant fields shown in the display.
Related Commands
show waas cache http-express metadatacacheTo display WAAS Express HTTP metadata cache entries, use the show waas cache http-express metadatacache command in privileged EXEC mode.
show waas cache http-express metadatacache
{all | conditional-response | redirect-response | unauthorized-response}
ExamplesThe following is sample output from the show waas cache http-express metadatacache all command: Device# show waas cache http-express metadatacache all
Redirect cache
Active HTTP entries: 0, Active HTTPS entries: 0 Max Entries: 400
Conditional cache
Active HTTP entries: 0, Active HTTPS entries: 0 Max Entries: 2800
Unauthorized cache
Active HTTP entries: 0, Active HTTPS entries: 0 Max Entries: 800
The table below describes the fields shown in the display.
Related Commands
show waas connectionTo display WAAS Express connection details, use the show waas connection command in privileged EXEC mode.
show
waas
connection
[closed]
[conn-id conn-id]
[client-ip client-ip]
[client-port client-port]
[server-ip server-ip]
[server-port server-port]
[peer-id peer-id]
[brief | detailed]
Syntax Description
ExamplesThe following is sample output from the show waas connection command: Device# show waas connection
ConnID Source IP:Port Dest IP:Port PeerID Accel
1 192.168.20.99:51558 192.168.40.99:80 0021.5586.13df TLD
The following is sample output from the show waas connection detailed command: Device# show waas connection detailed
connection ID: 6
Peer Id: 0016.9d39.20bd
Connection Type: External
Start Time: 03:16:07 UTC Jan 7 2012
Source IP Address: 192.168.22.99
Source Port Number: 43526
Destination IP Address: 192.168.42.99
Destination Port Number: 443
Application Name: SSL
Classifier Name: HTTPS
Peer Policy: TFO
Configured Policy: TFO
Negotiated Policy: TFO, LZ, DRE
Configured Accelerator: SSL-Express
Derived Accelerator: SSL-Express
Applied Accelerator: SSL-Express, HTTP-Express
Hist. Accelerator: None
Bytes Read Orig: 1905360
Bytes Written Orig: 1054
Bytes Read Opt: 28103
Bytes Written Opt: 56378
Auto-discovery information:
Orig-St E
Term-St EO
TFO information:
TFO Frames Read: 215
TFO Frames Written: 232
LZ section
Encode stats
Bytes in 265204
Bytes out 37421
Bypass bytes 8988
Compression gain 85%
Avg Latency in Cef 0 usec
Avg Latency in Proc 722 usec
Decode stats
Bytes in 68
Bytes out 72
Bypass bytes 9642
Compression gain 5%
Avg Latency in Cef 0 usec
Avg Latency in Proc 1 usec
DRE section
Encode stats
R-tx total 0
R-tx chunk-miss 0
R-tx collision 0
Bytes in 1884160
Bytes out 273638
Bypass bytes 467
Compression gain 85%
Avg latency 1774 usec
Decode stats
Nacks generated 0
Bytes in 72
Bytes out 25
Bypass bytes 0
Compression gain 0%
Avg latency 53 usec
SSL-Express AO section
LAN Bytes read 1905360
LAN Bytes written 1054
WAN Bytes read 28103
WAN Bytes written 58250
LAN Handshake Bytes read 262
LAN Handshake Bytes written 932
WAN Handshake Bytes read 1362
WAN Handshake Bytes written 340
C2S version SSL 3.0
W2W version TLS 1.0
C2S cipher rsa-with-aes-128-cbc-sha
W2W cipher rsa-with-aes-128-cbc-sha
HTTP-Express AO section
LAN Bytes read 1884627
LAN Bytes written 25
WAN Bytes read 25
WAN Bytes written 1884627
The following is sample output from the show waas connection closed detailed command: Device# show waas connection closed detailed
connection ID: 2
Peer Id: 0016.9d39.2209
Connection Type: External
Start Time: 18:44:53 PDT Dec 22 2011
End Time: 18:44:54 PDT Dec 22 2011
End Reason: Closed.
Source IP Address: 192.168.12.99
Source Port Number: 38798
Destination IP Address: 192.168.32.99
Destination Port Number: 8080
Application Name: Web
Classifier Name: HTTP
Peer Policy: TFO, LZ, DRE
Configured Policy: TFO, LZ, DRE
Negotiated Policy: TFO, LZ, DRE
Configured Accelerator: HTTP-Express
Derived Accelerator: HTTP-Express
Applied Accelerator: HTTP-Express, SSL-Express
Hist. Accelerator: None
Bytes Read Orig: 691
Bytes Written Orig: 1969
Bytes Read Opt: 2910
Bytes Written Opt: 1301
Auto-discovery information:
Orig-St E
Term-St EO
TFO information:
TFO Frames Read: 4
TFO Frames Written: 2
TFO EOT State: CONN_CLOSE
TFO EOT: RS AR RR AS LFR LFS WFR WFS
LZ section
Encode stats
Bytes in 0
Bytes out 0
Bypass bytes 400
Compression gain 0%
Avg Latency in Cef 0 usec
Avg Latency in Proc 13 usec
Decode stats
Bytes in 329
Bytes out 393
Bypass bytes 63
Compression gain 16%
Avg Latency in Cef 2 usec
Avg Latency in Proc 3 usec
DRE section
Encode stats
R-tx total 0
R-tx chunk-miss 0
R-tx collision 0
Bytes in 0
Bytes out 0
Bypass bytes 314
Compression gain 0%
Avg latency 0 usec
Decode stats
Nacks generated 0
Bytes in 399
Bytes out 332
Bypass bytes 0
Compression gain 0%
Avg latency 23 usec
SSL-Express AO section
LAN Bytes read 548
LAN Bytes written 1892
WAN Bytes read 2688
WAN Bytes written 1030
LAN Handshake Bytes read 314
LAN Handshake Bytes written 1509
WAN Handshake Bytes read 2077
WAN Handshake Bytes written 392
C2S version SSL 3.0
W2W version TLS 1.0
C2S cipher dhe-rsa-with-aes-256-cbc-sha
W2W cipher rsa-with-aes-128-cbc-sha
HTTP-Express AO section
LAN Bytes read 310
LAN Bytes written 328
WAN Bytes read 332
WAN Bytes written 314
The table below describes the significant fields shown in the displays.
Related Commands
show waas statistics acceleratorTo display statistical information about WAAS Express accelerators, use the show waas statistics accelerator command in privileged EXEC mode.
show waas statistics accelerator
{cifs-express [detail] | http-express [default | https] | ssl-express [ciphers | debug | peering]}
Syntax Description
ExamplesThe following is sample output from the show waas statistics accelerator cifs-express detail command: Router# show waas statistics accelerator cifs-express detail
CIFS-Express AO Statistics detail
Parameter Value
--------- -----
Time Accelerator was started: 00:54:12 UTC Dec 5 2007
Time Statistics were Last Reset/Cleared: 00:54:12 UTC Dec 5 2007
Total Handled Connections: 0
Total Optimized Connections: 0
Total Connections Handed-off with Compression Policies Unchanged: 0
Total Dropped Connections: 0
Current Active Connections: 0
Maximum Active Connections: 0
Total LAN bytes read: 0
Total LAN bytes written: 0
Total WAN bytes read: 0
Total WAN bytes written: 0
Local replies: 0
Messages received from the LAN: 0
Messages sent to the LAN: 0
Messages received from the WAN: 0
Messages sent to the WAN: 0
Disk space query Messages sent to the WAN: 0
Unsupported dialects / CIFS version: 0
Currently active unsupported dialects / CIFS version: 0
Unsupported due to signing: 0
Total Number of Bytes Read by Clients: 0
Total Number of Bytes Written by Clients: 0
Total Number of Bytes Read from File Servers: 0
Total Number of Bytes Written to File Servers: 0
Number of current active commands: 0
Request types Frequency
------------- ---------
CLOSE: 0
OPEN_ANDX: 0
READ_ANDX: 0
WRITE_ANDX: 0
TRANS2: 0
NT_TRANS: 0
TREE_CONNECT: 0
TREE_DISCONNECT: 0
NEGOTIATE: 0
SETUP_ANDX: 0
LOGOFF_ANDX: 0
NT_CREATE_ANDX: 0
WRITE: 0
CANCEL: 0
RENAME: 0
LOCKING_ANDX: 0
SESSION_SETUP WITH TREE_CONNECT: 0
ECHO: 0
OTHER ANDX: 0
OTHER: 0
Read Ahead:
Parameter Value
--------- -----
Passed through FIDs: 0
Optimized FIDs: 0
Reads served: 0
Local replies: 0
Accelerated replies: 0
Passed through replies: 0
Read-aheads sent: 0
Served file ranges: 0
No fid: 0
Wrong locking level: 0
Optimization disabled: 0
Optimization disabled (pipeline): 0
Read-ahead processing error: 0
Invalidate LRU cache due to out of buf: 0
Read-ahead responses with NULL fid: 0
Allocates RA buffers: 0
RA buffers pending for delete: 0
Async Write:
Parameter Value
--------- -----
Writes served: 0
Local replies: 0
Not a file: 0
No oplock: 0
No quota: 0
Andx command: 0
No tid: 0
Outstanding writes: 0
Async errors: 0
Negative-Cache:
Parameter Value
--------- -----
Current entries: 0
Entries added: 0
Entries removed: 0
ADS opens served: 0
Local replies: 0
Entry timed out: 0
Not in cache: 0
Invalidated: 0
Flow miss-match: 0
Not a file or ADS: 0
The table below describes the significant fields shown in the display.
Related Commands
show waas statistics aoimTo display WAAS Express peer information and negotiated capabilities, use the show waas statistics aoim command in privileged EXEC mode. ExamplesThe following example shows how to display WAAS peer information and negotiated capabilities: Device> enable Device# show waas statistics aoim Total number of peer syncs: 1 Current number of peer syncs in progress: 0 Number of peers: 1 Number of local application optimizations (AO): 3 Number of AO discovery successful: 1 Number of AO discovery failure: 0 Local AO statistics Local AO: TFO Total number of incompatible connections: 0 Version: 0.11 Registered: Yes Local AO: HTTP Total number of incompatible connections: 0 Version: 1.1 Registered: Yes Local AO: SSL Total number of incompatible connections: 0 Version: 1.0 Registered: Yes Peer AOIM Statistics Number of Peers: 1 Peer: 0021.5586.1399 Peer IP: 50.0.0.2 Peer Expiry Time: 00:00:04 Peer Compatible: Yes Peer active connections: 0 Peer Aoim Version: 1.0 Peer sync in progress: No Peer valid: Yes Peer Software Version: 4.4.0(b168) Peer AOs: Peer AO: TFO Compatible: Yes Version: 0.20 Peer AO: HTTP Compatible: Yes Version: 1.3 Peer AO: SSL Compatible: Yes Version: 1.0 The table below describes the significant fields shown in the display.
Related Commands
show waas statistics applicationTo display WAAS Express policy application statistics, use the show waas statistics applicationcommand in privileged EXEC mode. ExamplesThe following is sample output from the show waas statistics applicationcommand:: Router> enable Router# show waas statistics application waas-default Application: waas-default TCP Data Volumes Connection Type Inbound Outbound Opt TCP Plus 5054526 13969693 Orig TCP Plus 35202552 35202552 Opt TCP Only 0 0 Orig TCP Only 0 0 Internal Client 0 0 Internal Server 0 0 TCP Connection Counts Connection Type Active Completed Opt TCP Plus 0 18 Opt TCP Only 0 0 Internal Client 0 0 Internal Server 0 0 Pass Through Connection Counts Connection Type Completed PT Asymmetric 0 PT Capabilities 0 PT Intermediate 0 PT_Other 0 Connection Reset: 0 Cleared connections 0 The table below describes the significant fields shown in the display.
Related Commands
show waas statistics auto-discoveryTo display the autodiscovery statistics for a WAAS Express device, use the show waas statistics auto-discoverycommand in privileged EXEC mode. Usage GuidelinesUse this command to display statistics for autodiscovery states, success, and failures. ExamplesThe following is sample output from the show waas statistics auto-discovery command: Router> enable Router# show waas statistics auto-discovery Packets: Total Sent: 3 Total Received: 3 Ack dropped in synack received state: 0 Non Syn dropped in nostate state: 0 Aoim sync syn-ack drop: 0 Aoim sync ack drop: 0 Auto discovery failure: Total Failure: 0 Insufficient option space: 0 Invalid connection state: 0 Sequence number override: 0 Connection split failed: 0 Set sequence number failed: 0 Get sequence number failed: 0 Setting BIC failed: 0 External module init failed: 0 Deleting options failed: 0 Set window size failed: 0 AOIM handover failed: 0 AOIM force sync failed: 0 AOIM peer addition failed: 0 AOIM synchronization reset: 0 TFO handover failed: 0 Setting timestamp failed: 0 Setting window scale failed: 0 Setting send window failed: 0 Setting sack failed: 0 Setting keepalive failed: 0 FD association failed: 0 Auto discovery success SYN retransmission: Zero retransmit: 1 One retransmit: 0 Two+ retransmit: 0 Auto discovery Miscellaneous: RST received: 0 SYNs with our device id: 0 Zero device ID: 0 Non standard option length: 0 Replication mode turned on: 0 ADM mode turned on: 0 Capabilities mismatch: 0 Intermediate device: 0 Invalid option content: 0 Version mismatch: 0 Peer AOIM incompatible: 0 Peer AOIM in progress: 0 AOIM peertable full: 0 AOIM multiple sync request passthrough: 0 No peer: 0 Missing Ack conf: 0 The table below describes the significant fields shown in the display.
The following is sample output from the show waas statistics auto-discovery blacklist command: Router> enable Router# show waas statistics auto-discovery blacklist Auto-Discovery Blacklist Table Statistics Operation Status: 1 Total Lookups: 0 Hits: 0 Miss (Grey Entry): 0 Miss (No Entry): 0 Table Insertions: 0 Total Entries (Free & Used): 1024 Current Free Entries: 1024 Current Used Entries: 0 Peak Used Entries: 0 Oldest Entry Hold Time (sec): 3600 IP Address Retrieval Failure: 0 Unexpected Threshold: 0 The table below describes the significant fields shown in the display.
Related Commands
show waas statistics classTo display statistical information about the class in WAAS Express, use the show waas statistics classcommand in privileged EXEC mode. Usage GuidelinesThis command displays statistical information about the class specified in WAAS Express. If a class name is not specified, the command displays the output for all the classes in WAAS Express. ExamplesThe following is sample output from the show waas statistics class command: Router> enable Router# show waas statistics class Number of Classes : 3 Class FTP-Control TCP Data Volumes Connection Type Inbound Outbound Opt TCP Plus 0 0 Orig TCP Plus 0 0 Opt TCP Only 0 0 Orig TCP Only 0 0 Internal Client 0 0 Internal Server 0 0 TCP Connection Counts Connection Type Active Completed Opt TCP Plus 0 0 Opt TCP Only 0 0 Internal Client 0 0 Internal Server 0 0 Pass Through Connection Counts Connection Type Completed PT Asymmetric 0 PT Capabilities 11 PT Intermediate 0 PT_Other 0 Connection Reset: 0 Class waas-default TCP Data Volumes Connection Type Inbound Outbound Opt TCP Plus 0 0 Orig TCP Plus 0 0 Opt TCP Only 0 0 Orig TCP Only 0 0 Internal Client 0 0 Internal Server 0 0 TCP Connection Counts Connection Type Active Completed Opt TCP Plus 0 0 Opt TCP Only 0 0 Internal Client 0 0 Internal Server 0 0 Pass Through Connection Counts Connection Type Completed PT Asymmetric 0 PT Capabilities 0 PT Intermediate 0 PT_Other 0 Connection Reset: 0 Class FTP-Data TCP Data Volumes Connection Type Inbound Outbound Opt TCP Plus 722 573 Orig TCP Plus 0 24 Opt TCP Only 0 0 Orig TCP Only 0 0 Internal Client 0 0 Internal Server 0 0 TCP Connection Counts Connection Type Active Completed Opt TCP Plus 0 4 Opt TCP Only 0 0 The table below describes the significant fields shown in the display.
Related Commands
show waas statistics dreTo display WAAS Express Data Redundancy Elimination (DRE) statistics for a WAAS Express device, use the show waas statistics dre command in privileged EXEC mode. ExamplesThe following is sample output from the show waas statistics dre command: Device# show waas statistics dre
DRE Status: Enabled
Cache
Cache Status: Ready
Oldest data age: 00:07:35
Total data storage size: 1468006400
Total index size: 11513600
AckQ size: 5242880
AckQ in storage: 0
AckQ full: 0
AckQ high: 0
WaitQ size: 0
WaitQ in storage: 0
Connections
Total: 24
Active: 0
Encode Statistics
Dre msgs: 0
R-tx total: 0
R-tx chunk-miss: 0
R-tx collision: 0
Bytes in: 67344
Bytes out: 8840
Bypass bytes: 35714
Bytes Matched: 59355
Bytes Skipped: 0
Compression gain: 86%
Average latency: 2191 usec
Encode Message Size Distribution:
0-1K = 4 %
1-5K = 31 %
5-15K = 14 %
15-25K = 0 %
25-40K = 0 %
>40K = 0 %
Decode Statistics
Dre msgs: 318
Nacks generated: 0
Bytes in: 8494760
Bytes out: 13780812
Bypass bytes: 35556
Compression gain: 38%
Average latency: 1471 usec
Decode Message Size Distribution:
0-1K = 4 %
1-5K = 0 %
5-15K = 5 %
15-25K = 9 %
25-40K = 23 %
>40K = 55 %
The following is sample output from the show waas statistics dre peer command: Device# show waas statistics dre peer
DRE Status: Enabled
Current number of connected peers 0
Current number of active peers 1
Peer-ID 0016.9d38.ca1d
Hostname WAE2.cisco.com
IP reported from peer 20.0.0.2
Peer version 4.4.0(b167)
Cache:
Cache in storage 614017 B
Age 21:22:40
AckQ:
AckQ in storage 0 B
WaitQ:
WaitQ in storage 756 B
WaitQ size 0 B
Sync-clock:
Local-head 457161116 ms
Local-tail 457438528 ms
Remote-head 372192000 ms
Remote-head-safe 4294967296 ms
Encode Statistics
DRE msgs: 64
R-tx total: 0
R-tx chunk-miss: 0
R-tx collision: 0
Bytes in: 67344
Bytes out: 8840
Bypass bytes: 35714
Compression gain: 86%
Decode Statistics
DRE msgs: 14
Bytes in: 490
Bytes out: 416
Bypass bytes: 0
Compression gain: 0%
Nacks generated: 0
The table below describes the significant fields shown in the displays.
Related Commands
show waas statistics errorsTo display error statistics for a WAAS Express device, use the show waas statistics errors command in privileged EXEC mode. ExamplesThe following example shows how to display WAAS Express error statistics: Device# show waas statistics errors
Unexpected EOT message: 0
TFO close failure: 0
DRE message delayed for transmission: 0
Invalid input for TFO decode: 0
RST ignored because EOT ACK sent: 0
RST ignored because EOT REQ sent: 0
Unknown TCP Control packet received: 0
DRE encode failed: 0
Connection reset by peer: 0
Connection timed out: 0
No data to read: 0
Buffer allocation failed: 0
Error reading input particle: 0
Received control packet when expecting data: 0
Return value not handled: 0
Lock condition: 0
Out of transmit buffers: 0
Error received from L4F: 0
Error writing data: 0
Error processing data: 0
Error processing control packet: 0
Error sending data: 0
Unable to find peer in table: 0
Flow semaphore acquisition failures: 0
Encryption/decryption failure: 0
Error processing SSL packet: 0
SSL-Express AO failed to allocate packet: 0
SSL-Express AO failed to allocate sub-block: 0
SSL-Express AO received invalid packet: 0
SSL-Express AO vector copy failed: 0
SSL-Express AO invalid record length in LAN-WAN: 0
SSL-Express AO invalid record length in WAN-LAN: 0
SSL-Express AO failed to retrieve sub-block: 0
SSL-Express AO invalid session received on WAN: 0
SSL-Express AO invalid packet in pipe queue: 0
SSL-Express AO invalid packet in receive queue: 0
SSL-Express AO encountered misbehaving client: 0
SSL-Express AO Packet enqueue to queue failed: 0
SSL-Express AO Connection closed during SSL handshake: 0
SSL-Express AO Connection reset when pending data: 0
SSL-Express AO received invalid protocol in key-packet:0
SSL-Express AO session create failed: 0
SSL-Express AO received invalid SSL record: 0
SSL-Express AO session delete failed: 0
SSL-Express AO failed to load key-packet: 0
SSL-Express AO memory allocation failed: 0
SSL-Express AO W2W handshake failed: 0
SSL-Express AO encountered rehandshake on W2W session: 0
SSL-Express AO W2W session setup failed: 0
SSL-Express AO received invalid module: 0
SSL-Express AO Encrypt/decrypt allocation failures: 0
The table below describes the significant fields shown in the display.
Related Commands
show waas statistics globalTo display global statistics for a WAAS Express device, use the show waas statistics global command in privileged EXEC mode. ExamplesThe following example shows how to display global statistics for a WAAS Express device: Device# show waas statistics global
TCP Data Volumes
Connection Type Inbound Outbound
Opt TCP Plus 0 0
Orig TCP Plus 0 0
Opt TCP Only 244 161
Orig TCP Only 0 0
Internal Client 0 0
Internal Server 0 0
TCP Connection Counts
Connection Type Active Completed
Opt TCP Plus 0 0
Opt TCP Only 0 1
Internal Client 0 0
Internal Server 0 0
Pass Through Connection Counts
Connection Type Completed
PT Asymmetric 0
PT Capabilities 0
PT Intermediate 0
PT_Other 0
Connection Reset: 1
Cleared connections 0
The table below describes the significant fields shown in the display.
Related Commands
show waas statistics lzTo display the Lempel-Ziv compression statistics for a WAAS Express device, use the show waas statistics lzcommand in privileged EXEC mode. ExamplesThe following example shows how to display WAAS Express LZ statistics: Router> enable Router# show waas statistics lz LZ Status: Enabled Memory used 30328 KB Connections Total: 75 Active: 0 Encode Statistics Bytes in: 0 Bytes out: 0 Bypass bytes: 10886 Compression gain: 0% Average latency in CEF path: 0 usec Average latency in process path: 293 usec Decode Statistics Bytes in: 25595 Bytes out: 71977 Bypass bytes: 776 Compression gain: 64% Average latency in CEF path: 37 usec Average latency in process path: 9 usec The table below describes the significant fields shown in the display.
Related Commands
show waas statistics pass-throughTo display the pass-through statistics for a WAAS Express device, use the show waas statistics pass-throughcommand in privileged EXEC mode. ExamplesThe following is sample output from the show waas statistics pass-through command: Router> enable Router# show waas statistics pass-through Pass Through Statistics: Overall: 1 No Peer: 0 Rejected due to Capabilities: 0 Rejected due to Resources: 0 Interface Application config: 1 Interface Global config: 0 Asymmetric setup: 0 Peer sync was in progress: 0 IOS WAAS is intermediate router: 0 Internal error: 0 Other end is in black list: 0 AD version mismatch: 0 Incompatable AO: 0 Connection limit exceeded: 0 AOIM peertable full: 0 AOIM multiple sync request passthrough: 0 Others: 0 The table below describes the significant fields shown in the display.
Related Commands
show waas statistics peerTo display inbound and outbound statistics for peer Wide-area Application Engines (WAEs) devices, use the show waas statistics peercommand in privileged EXEC mode. Command DefaultInbound and outbound statistics are displayed for all peer WAE devices. Current optimized connections are not displayed. Usage GuidelinesUse this command to display inbound and outbound statistics for all peer WAE devices. ExamplesThe following is sample output from the show waas statistics peer command: Router> enable Router# show waas statistics peer Number of Peers : 1 Peer: 0021.5586.13df TCP Data Volumes Connection Type Inbound Outbound Opt TCP Plus 765708 2698 Orig TCP Plus 335 10486305 Opt TCP Only 0 0 Orig TCP Only 0 0 Internal Client 0 0 Internal Server 0 0 TCP Connection Counts Connection Type Active Completed Opt TCP Plus 0 2 Opt TCP Only 0 0 Internal Client 0 0 Internal Server 0 0 Pass Through Connection Counts Connection Type Completed PT Asymmetric 0 PT Capabilities 0 PT Intermediate 0 PT_Other 0 Connection Reset: 1 Connection Closed: 0 The table below describes the significant fields shown in the display.
Related Commands
show waas statusExamplesThe example below shows the status of WAAS Express. The fields in the output are self-explanatory. Device# show waas status
IOS Version: 15.2(2.16)T
WAAS Express Version: 2.0.0
WAAS Enabled Interface Policy Map
GigabitEthernet0/0 waas_global
WAAS Feature License
License Type: Permanent
DRE Status : Enabled
LZ Status : Enabled + Entropy
CIFS-Express AO Status : Enabled
SSL-Express AO Status : Enabled
HTTP-Express AO Status : Enabled
Maximum Flows : 200
Total Active connections : 1
Total optimized connections : 1
The possible values for the License Type field include:
If the License Type field is EvalRightToUse, the show waas status command output also displays the Evaluation total period and Evaluation period left fields. If the License Type field is RightToUse, the show waas status command output does not display the Evaluation total period and Evaluation period left fields. Related Commands
show waas tokenTo display the value of the WAAS Express configuration token, use the show waas alarms command in privileged EXEC mode. ExamplesThe following is sample output from the show waas token command: Router> enable Router# show waas token Config Token: 1292 The table below describes the significant field shown in the display. Related Commands
show x25 contextTo display operating configuration status details of an X.25 link, use the show x25 context command in privileged EXECmode.
show
x25
context
[xot | interface serial number [dlci number] | cmns-interface-type number [mac mac-address]]
Syntax Description
Command History
XOT: ExampleThe following is sample output from the show x25 context command with the xotkeyword:
Router# show x25 context xot
XOT Access-group 2
PROFILE mod128 station DXE/DTE, address 2222, state R1, modulo 128, timer 0
Defaults: idle VC timeout 0
input/output window sizes 80/80, packet sizes 256/256
Timers: T20 180, T21 200, T22 180, T23 180
RESTARTs 0/0 CALLs 5+0/7+0/0+0 DIAGs 0/0
XOT Access-group 3
station DXE/DTE, address <none>, state R1, modulo 8, timer 0
Defaults: idle VC timeout 0
input/output window sizes 2/2, packet sizes 128/128
Timers: T20 180, T21 200, T22 180, T23 180
RESTARTs 0/0 CALLs 21+0/50+0/0+0 DIAGs 0/0
The following is sample output from the show x25 contextcommand:
Router# show x25 context interface serial 1
Serial1 DLCI 20
PROFILE DCE, address <none>, state R1, modulo 8, timer 0
Defaults: idle VC timeout 0
input/output window sizes 2/2, packet sizes 128/128
Timers: T10 60, T11 180, T12 60, T13 60
Channels: Incoming-only none, Two-way 1-1024, Outgoing-only none
RESTARTs 1/0 CALLs 0+0/0+0/0+0 DIAGs 0/0
LAPB DCE, state CONNECT, modulo 8, k 7, N1 12056, N2 20
T1 3000, T2 0, interface outage (partial T3) 0, T4 0
VS 7, VR 6, tx NR 6, Remote VR 7, Retransmissions 0
Queues: U/S frames 0, I frames 0, unack. 0, reTx 0
IFRAMEs 111/118 RNRs 0/0 REJs 0/0 SABM/Es 14/1 FRMRs 0/0 DISCs 0/0
The following is sample output from the show x25 context command when the X.25 Failover feature is configured. The "Fail-over delay" field appears when the primary interface has gone down and come back up again. The number of seconds indicates the time remaining until the secondary interface will reset.
Router# show x25 context
Serial1 DLCI 33
PROFILE dxe/DCE, address 3032, state R1, modulo 8, timer 0
Defaults:idle VC timeout 0
input/output window sizes 2/2, packet sizes 128/128
Timers:T20 180, T21 200, T22 180, T23 180
Channels:Incoming-only none, Two-way 1-4095, Outgoing-only none
RESTARTs 12/0 CALLs 5+4/0+0/0+0 DIAGs 0/0
Fail-over delay:16 seconds remaining on Dialer0
LAPB dxe/DCE, state CONNECT, modulo 8, k 7, N1 12056, N2 20
T1 3000, T2 0, interface outage (partial T3) 0, T4 0
VS 1, VR 1, tx NR 1, Remote VR 1, Retransmissions 0
Queues:U/S frames 0, I frames 0, unack. 0, reTx 0
IFRAMEs 97/88 RNRs 0/0 REJs 0/0 SABM/Es 55490/12 FRMRs 186/0 DISCs
The following table describes significant fields shown in the displays.
1 DTE = data terminal equipment 2 DCE = data communications equipment
show x25 cugTo display information about all closed user groups (CUGs) or specific CUGs (defined by the local or network CUG number), use the show x25 cug command in privileged EXEC mode. Syntax Description
Command History
Usage GuidelinesYou must designate either the local CUG or the network CUG by the choice of keyword. Within that designation you can view all CUGs or a specific CUG defined by its local or network CUG identifier. CUG Selection Facility Suppress Option: ExampleThe following is sample output for the show x25 cug command when CUG selection facility is suppressed for all CUGs on serial interface 1/2 and for the preferential CUG on the X.25 profile named "cug".
Router# show x25 cug local-cug
X.25 Serial1/2, 2 CUGs subscribed with no public access
CUG selection facility suppressed for all CUGs
local-cug 100 <-> network-cug 10
local-cug 1 <-> network-cug 11
PROFILE cug, 2 CUGs subscribed with incoming public access
CUG selection facility suppressed for preferential CUG
local-cug 0 <-> network-cug 0 , preferential
local-cug 100 <-> network-cug 100
local-cug 200 <-> network-cug 200
Local CUG: ExampleThe following sample output from the show x25 cug local-cugcommand displays information about all local CUGs on configured on the router.
Router# show x25 cug local-cug
X.25 Serial1/1, 3 CUGs subscribed with no public access
local-cug 99 <-> network-cug 9999, no-incoming, preferential
local-cug 100 <-> network-cug 1000
local-cug 101 <-> network-cug 1001
PROFILE cugs, 2 CUGs subscribed with with incoming public access
local-cug 1 <-> network-cug 10, no-outgoing
local-cug 2 <-> network-cug 20, no-incoming, preferential
Line: 129 aux 0 , 1 CUGs subscribed with outgoing public access
local-cug 1 <-> network-cug 10
Line: 130 vty 0 , 4 CUGs subscribed with incoming and outgoing public access
local-cug 1 <-> network-cug 10
local-cug 50 <-> network-cug 5, preferential
local-cug 60 <-> network-cug 6, no-incoming
local-cug 70 <-> network-cug 7, no-outgoing
Line: 131 vty 1 , 1 CUGs subscribed with no public access
local-cug 1 <-> network-cug 10
Network CUG: ExampleThe following is sample output from the show x25 cug network-cugcommand specifically for network number 10 showing that local CUG 1 is associated with it.
Router# show x25 cug network-cug 10
X.25 Serial1/2, 5 CUGs subscribed with no public access
network-cug 10 <-> local-cug 1
PROFILE cugs, 2 CUGs subscribed with no public access
network-cug 10 <-> local-cug 1 , no-outgoing
Line: 129 aux 0 , 1 CUGs subscribed with no public access
network-cug 10 <-> local-cug 1
Line: 130 vty 0 , 4 CUGs subscribed with incoming and outgoing public access
network-cug 10 <-> local-cug 1
Line: 131 vty 1 , 1 CUGs subscribed with no public access
network-cug 10 <-> local-cug 1
The table below describes the significant fields shown in the displays.
show x25 hunt-groupTo display hunt groups and view detailed interface statistics and distribution methods, use the show x25 hunt-groupcommand in privileged EXEC mode. Command History
Usage GuidelinesUse the clear counters or the clear x25commands in EXEC mode to clear the count of VCs in use in the "status" field and the number of bytes of data transmitted and received in the "traffic" field. Since the "uses" field is a hunt-group-specific counter, it will not be cleared using the clear counters or clear x25commands. The "uses" field is only cleared at boot time or when the hunt group is defined. ExamplesThe following is sample output from the show x25 hunt-groupcommand:
Router# show x25 hunt-group
ID Type Target uses status traffic(out/in)
=================================================================================
HG1 rotary Serial1 2 next 1158/1691
Serial2 2 next 1328/2146
xot 172.17.125.54 2 last_used 137/3154
xot 172.17.125.34 1 next 137/3154
HG2 vc-count Serial2 4 5 VCs 6921/1364
Serial3 2 1 VC 70/1259
The table below describes significant fields shown in the display.
show x25 interfaceTo display information about virtual circuits (VCs) that use an X.25 interface and, optionally, about a specified virtual circuit, use the show x25 interface EXEC command. Syntax Description
Command History
ExamplesThe following show x25 interface sample output displays X.25 information about VCs on serial interface 0:
Router# show x25 interface serial 0
SVC 1, State: D1, Interface: Serial0
Started 00:13:52, last input 00:00:05, output never
Connects 3334 <-> ip 3.3.3.4
Call PID ietf, Data PID none
Window size input: 7, output: 7
Packet size input: 512, output: 512
PS: 0 PR: 6 ACK: 1 Remote PR: 0 RCNT: 5 RNR: no
P/D state timeouts: 0 timer (secs): 0
data bytes 0/2508 packets 0/54 Resets 0/0 RNRs 0/0 REJs 0/0 INTs 0/0
SVC 32, State: D1, Interface: Serial0.11
Started 00:16:53, last input 00:00:37, output 00:00:28
Connects 3334 <-> clns
Call PID cisco, Data PID none
Window size input: 7, output: 7
Packet size input: 512, output: 512
PS: 5 PR: 4 ACK: 4 Remote PR: 4 RCNT: 0 RNR: no
P/D state timeouts: 0 timer (secs): 0
data bytes 378/360 packets 21/20 Resets 0/0 RNRs 0/0 REJs 0/0 INTs 0/0
show x25 mapTo display information about configured address maps, use the show x25 map command in privileged EXEC mode. Command History
Record Boundary Preservation: ExamplesThe following is sample output of the show x25 map command for a router that is configured with record boundary preservation (RBP) using the x25 pvc rbp remotecommand:
Router# show x25 map
Serial1/0:-> rbp, destination host 10.0.0.33 port 9999
PVC, 1 VC:1/P
The following is sample output of the show x25 map command for a router that is configured with RBP using the x25 map rbp remotecommand:
Router# show x25 map
Serial3/0:12132 -> rbp, destination host 10.0.0.32 port 9999
permanent, 1 VC:1024
The following is sample output of the show x25 map command for a router that is configured with RBP using the x25 pvc rbp localcommand:
Router# show x25 map
Serial3/0:<- rbp, listening at port 9999
PVC, 1 VC:2/P
The following is sample output of the show x25 map command for a router that is configured with RBP using the x25 map rbp localcommand:
Router# show x25 map
Serial1/0:12131 <- rbp, listening at port 9999
permanent, 1 VC:1
The table below describes significant fields shown in the display.
Typical X.25 Maps: ExampleThe following is sample output from the show x25 map for five maps that were configured with the x25 map command:
Router# show x25 map
Serial0: X.121 1311001 <--> ip 172.20.170.1
PERMANENT, BROADCAST, 2 VCS: 3 4
Serial0: X.121 1311005 <--> appletalk 128.1
PERMANENT
Serial1: X.121 2194441 cud hello <--> pad
PERMANENT, windowsize 5 5, accept-reverse, idle 5
Serial1: X.121 1311005 <--> bridge
PERMANENT, BROADCAST
Serial2: X.121 001003 <--> apollo 1.3,
appletalk 1.3,
ip 172.20.1.3,
decnet 1.3,
novell 1.0000.0c04.35df,
vines 00000001:0003,
xns 1.0000.0c04.35df,
clns
PERMANENT, NVC 8, 1 VC: 1024
The display shows that five maps have been configured for a router: two for serial interface 0, two for serial interface 1, and one for the serial interface 2 (which maps eight protocols to the host). The table below describes significant fields shown in the display.
show x25 profileTo view details of X.25 profiles on your router, use the show x25 profilecommand in privileged EXEC mode. Command History
Usage GuidelinesWhen the X.25 profile name is not specified, the output shows all configured profiles for a given interface. ExamplesThe following sample output from the show x25 profilecommand displays details about the X.25 profile called "XOT-DEFAULT":
Router# show x25 profile XOT-DEFAULT
X.25 profile name: XOT-DEFAULT
In use by:
Access-group 2
Access-group 10
PROFILE dxe/DTE, address 12345, state R/Inactive, modulo 128, timer 0
Defaults: idle VC timeout 0
input/output window sizes 20/20, packet sizes 256/256
Timers: T20 180, T21 200, T22 180, T23 180
Channels: Incoming-only none, Two-way 1-4095, Outgoing-only none
The following sample output from the show x25 profilecommand displays all profiles configured on the same interface:
Router# show x25 profile
X.25 profile name:NetworkNodeA
Number of references:2
In use by:
Annex G:Serial1 DLCI 20
Annex G:Serial1 DLCI 30
PROFILE DCE, address <none>, state R/Inactive, modulo 128, timer 0
Defaults:idle VC timeout 5
input/output window sizes 2/2, packet sizes 128/128
Timers:T10 60, T11 180, T12 60, T13 60
Channels:Incoming-only none, Two-way 1-128, Outgoing-only none
LAPB DCE, modulo 8, k 7, N1 default, N2 20
T1 3000, T2 0, interface outage (partial T3) 0, T4 0
X.25 profile name:NetworkNodeB
Number of references:1
In use by:
Annex G:Serial1 DLCI 40
PROFILE DTE, address 1111, state R/Inactive, modulo 8, timer 0
Defaults:idle VC timeout 0
input/output window sizes 2/2, packet sizes 128/128
Timers:T20 180, T21 200, T22 180, T23 180
Channels:Incoming-only none, Two-way 1-1024, Outgoing-only none
LAPB DTE, modulo 8, k 7, N1 default, N2 20
T1 3000, T2 0, interface outage (partial T3) 0, T4 0
The following table describes significant fields shown in the display.
3 DTE = data terminal equipment 4 DCE = data communications equipment
show x25 remote-red
To display the one-to-one mapping of the host IP addresses and the remote Blacker Front End (BFE) device's IP addresses, use the show x25 remote-redcommand in privileged EXEC mode. show x25 routeCommand History
ExamplesThe following example shows output from the show x25 route command:
Router# show x25 route
# Match Substitute Route To
1 dest ^1311001$ Serial0, 0 uses
2 dest ^1311002$ xot 172.20.170.10
3 dest 444 xot dns \0
4 dest 555 xot dns \0
The table below describes significant fields shown in the display.
show x25 servicesTo display information pertaining to the X.25 services, use the show x25 services command in user EXEC or privileged EXEC mode. Command History
ExamplesThe following is sample output from the show x25 services command:
Router# show x25 services
X.25 software, Version 3.0.0.
3 configurations supporting 3 active contexts
VCs allocated, freed and in use: 7 - 0 = 7
VCs active and idle: 4, 3
XOT software, Version 2.0.0.
VCs allocated, freed and in use: 2 - 1 = 1
connections in-progress: 0 outgoing and 0 incoming
active VCs: 1, connected to 1 remote hosts
Related Commands
show x25 vcTo display information about active switched virtual circuits (SVCs) and permanent virtual circuits (PVCs), use the show x25 vc command in privileged EXEC mode. Command History
Usage GuidelinesTo examine a particular virtual circuit number, add an LCN argument to the show x25 vc command. This command displays information about virtual circuits (VCs). VCs may be used for a number of purposes, such as the following:
The connectivity information displayed will vary according to the traffic carried by the VC. For multiprotocol circuits, the output varies depending on the number and identity of the protocols mapped to the X.121 address and the encapsulation method selected for the circuit. Record Boundary Preservation: ExampleThe following is sample output of the show x25 vc command for a PVC configured with record boundary preservation (RBP):
Router# show x25 vc
PVC 2, State:D1, Interface:Serial3/0
Started 00:08:08, last input 00:00:01, output 00:00:01
recordsize:1500, connected
local address 10.0.0.1 port 9999; remote address 10.0.0.5 port 11029
deferred ack:1
Window size input:2, output:2
Packet size input:128, output:128
PS:2 PR:2 ACK:1 Remote PR:2 RCNT:1 RNR:no
P/D state timeouts:0 timer (secs):0
data bytes 8000/8000 packets 80/80 Resets 9/0 RNRs 0/0 REJs 0/0 INTs 0/0
The following table describes the fields shown in the sample output that are typical for virtual circuits.
5 The ITU-T carries out the functions of the former Consultative Committee for International Telegraph and Telephone (CCITT).
The following table describes the fields specific to VCs configured with record boundary preservation.
The following is sample output of the show x25 vc command used on an encapsulated traffic circuit:
Router# show x25 vc 1024
SVC 1024, State: D1, Interface: Serial0
Started 0:00:31, last input 0:00:31, output 0:00:31
Connects 170090 <-->
compressedtcp 172.20.170.90
ip 172.20.170.90
Call PID multi, Data PID ietf
Reverse charged
Window size input: 2, output: 2
Packet size input: 128, output: 128
PS: 5 PR: 5 ACK: 4 Remote PR: 5 RCNT: 1 RNR: FALSE
Window is closed
P/D state timeouts: 0 Timer (secs): 0
data bytes 505/505 packets 5/5 Resets 0/0 RNRs 0/0 REJs 0/0 INTs 0/0
The following table describes the connection fields specific to encapsulation traffic.
The following is sample output of the show x25 vc command used on a virtual circuit carrying locally switched X.25 traffic:
Router# show x25 vc
PVC 1, State: D1, Interface: Serial2
Started 0:01:26, last input never, output never
PVC <--> Serial1 PVC 1, connected
Window size input: 2, output: 2
Packet size input: 128, output: 128
PS: 0 PR: 0 ACK: 0 Remote PR: 0 RCNT: 0 RNR: FALSE
P/D state timeouts: 0 Timer (secs): 0
data bytes 0/0 packets 0/0 Resets 0/0 RNRs 0/0 REJs 0/0 INTs 0/0
SVC 5, State: D1, Interface: Serial2
Started 0:00:16, last input 0:00:15, output 0:00:15
Connects 170093 <--> 170090 from Serial1 VC 5
Window size input: 2, output: 2
Packet size input: 128, output: 128
PS: 5 PR: 5 ACK: 4 Remote PR: 5 RCNT: 1 RNR: FALSE
P/D state timeouts: 0 Timer (secs): 0
data bytes 505/505 packets 5/5 Resets 0/0 RNRs 0/0 REJs 0/0 INTs 0/0
The following table describes the connection fields for virtual circuits carrying locally switched X.25 traffic.
The following is sample output of the show x25 vc command used on a virtual circuit carrying locally switched PVC-to-SVC X.25 traffic:
Router# show x25 vc
PVC 5, State: D1, Interface: Serial0
Started 4d21h, last input 00:00:14, output 00:00:14
Connects 101600 <--> 201700 from Serial2 VC 700
D-bit permitted
Window size input: 2, output: 2
Packet size input: 128, output: 128
PS: 5 PR: 5 ACK: 4 Remote PR: 5 RCNT: 1 RNR: no
P/D state timeouts: 0 timer (secs): 0
data bytes 1000/1000 packets 10/10 Resets 1/0 RNRs 0/0 REJs 0/0 INTs 0/0
SVC 700, State: D1, Interface: Serial2
Started 00:00:16, last input 00:00:16, output 00:00:16
Connects 101600 <--> 201700 from Serial0 PVC 5
Window size input: 2, output: 2
Packet size input: 128, output: 128
PS: 5 PR: 5 ACK: 5 Remote PR: 4 RCNT: 0 RNR: no
P/D state timeouts: 0 timer (secs): 103
data bytes 500/500 packets 5/5 Resets 0/0 RNRs 0/0 REJs 0/0 INTs 0/0
The following table describes the connection fields for virtual circuits carrying locally switched X.25 traffic between PVCs and SVCs.
The following is sample output from the show x25 vc command used on a virtual circuit carrying remotely switched X.25 traffic:
Router# show x25 vc
PVC 2, State: D1, Interface: Serial2
Started 0:01:25, last input never, output never
PVC <--> [172.20.165.92] Serial2/0 PVC 1 connected
XOT between 172.20.165.95, 1998 and 172.20.165.92, 27801
Window size input: 2, output: 2
Packet size input: 128, output: 128
PS: 0 PR: 0 ACK: 0 Remote PR: 0 RCNT: 0 RNR: FALSE
P/D state timeouts: 0 Timer (secs): 0 Reassembly (bytes): 0
Held Fragments/Packets: 0/0
data bytes 0/0 packets 0/0 Resets 0/0 RNRs 0/0 REJs 0/0 INTs 0/0
SVC 6, State: D1, Interface: Serial2
Started 0:00:04, last input 0:00:04, output 0:00:04
Connects 170093 <--> 170090 from
XOT between 172.20.165.91, 1998 and 172.20.165.92, 27896
Window size input: 2, output: 2
Packet size input: 128, output: 128
PS: 5 PR: 5 ACK: 4 Remote PR: 5 RCNT: 1 RNR: FALSE
P/D state timeouts: 0 Timer (secs): 0 Reassembly (bytes): 0
Held Fragments/Packets: 0/0
data bytes 505/505 packets 5/5 Resets 0/0 RNRs 0/0 REJs 0/0 INTs 0/0
The following table describes the connection fields for virtual circuits carrying remotely switched X.25 traffic.
The following table lists the PVC states that can be reported. These states are also reported by the debug x25 command in PVC-SETUP packets (for remote PVCs only). Some states apply only to remotely switched PVCs.
show x25 xotTo display information for all X.25 over TCP (XOT) virtual circuits that match a given criterion, use the show x25 xot command in privileged EXEC mode.
show
x25
xot
[local ip-address [port port]]
[remote ip-address [port port] | access-group [access-group-number] ]
Syntax Description
Command History
ExamplesThe following show x25 xot sample output displays information about all XOT virtual circuits:
Router# show x25 xot
SVC 11, State: D1, Interface: [10.2.2.2,1998/10.2.2.1,11002]
Started 00:00:08, last input 00:00:08, output 00:00:08
Line: 0 con 0 Location: Host: 5678
111 connected to 5678 PAD <--> XOT 2.2.2.2,1998
Window size input: 2, output: 2
Packet size input: 128, output: 128
PS: 2 PR: 3 ACK: 3 Remote PR: 2 RCNT: 0 RNR: no
P/D state timeouts: 0 timer (secs): 0
data bytes 54/18 packets 2/3 Resets 0/0 RNRs 0/0 REJs 0/0 INTs 0/0\
The following example shows sample output for the show x25 xot command with the access-group keyword:
Router# show x25 xot access-group
xot access-group 1 using built-in default configuration
xot access-group 10 using x.25 profile ocean
xot access-group 55 using x.25 profile river
show x28 hunt-groupTo display the members and status of each member in an X.28 hunt group, use the show x28 hunt-groupcommand in user EXEC or privileged EXEC mode. ExamplesThe following example displays the configuration of four hunt ("rotary") groups and the current status of their member lines:
Router# show x28 hunt-group
ID Type HG-Address TTy Address Uses status
=============================================================================
1 RRA 23456 97 34567 2 INUSE
98 12345 0 NXTUSE
100 - 0 INUSEO
102 456789 0 IDLE
2 QBR,FIF - 99 - 0 UNAVL
3 QUE,FIF - 101 - 0 NXTUSE
4 FIF 56789 103 67890 0 UNAVL
104 789012 0 UNAVL
show x29 access-listsTo display X.29 access lists, use the show x29 access-lists command in user EXEC or privileged EXEC mode. Command History
ExamplesThe following is sample output from the show x29 access-lists command:
Router# show x29 access-lists
X29 access list 10
permit 192.0.2.0
X29 access list 20
deny 192.0.2.255
X29 access list 50
permit 192.0.2.10
The table below describes the significant fields shown in the display.
show xconnectTo display information about xconnect attachment circuits and pseudowires, use the show xconnect command in user EXEC or privileged EXEC mode.
show
xconnect
{{all | interface type number} [detail] | peer ip-address {all | vcid vcid-value} [detail] | pwmib [peer ip-address vcid-value]}
Cisco IOS SR and S Trains
show
xconnect
{{all | interface type number | memory | rib} [detail] [checkpoint] | peer ip-address {all | vcid vcid-value} [detail] | pwmib [peer ip-address vcid-value]}
monitor
Cisco uBR10012 Router and Cisco uBR7200 Series Universal Broadband Routers
show
xconnect
{all | peer ip-address {all | vcid vcid-value} | pwmib [peer ip-address vcid-value]}
[detail]
Syntax DescriptionCommand History
Usage GuidelinesYou can use the show xconnect command to display, sort, and filter basic information about all xconnect attachment circuits and pseudowires. You can use the show xconnect command output to help determine the appropriate steps required to troubleshoot an xconnect configuration problem. More specific information about a particular type of xconnect can be displayed using the commands listed in the "Related Commands" table. ExamplesThe following example shows the show xconnect all command output in the brief (default) display format:
Router# show xconnect all
Legend: XC ST=Xconnect State, S1=Segment1 State, S2=Segment2 State
UP=Up, DN=Down, AD=Admin Down, IA=Inactive, SB=Standby, RV=Recovering, NH=No Hardware
XC ST Segment 1 S1 Segment 2 S2
------+---------------------------------+--+---------------------------------+--
UP ac Et0/0(Ethernet) UP mpls 10.55.55.2:1000 UP
UP ac Se7/0(PPP) UP mpls 10.55.55.2:2175 UP
UP pri ac Se6/0:230(FR DLCI) UP mpls 10.55.55.2:2230 UP
IA sec ac Se6/0:230(FR DLCI) UP mpls 10.55.55.3:2231 DN
UP ac Se4/0(HDLC) UP mpls 10.55.55.2:4000 UP
UP ac Se6/0:500(FR DLCI) UP l2tp 10.55.55.2:5000 UP
UP ac Et1/0.1:200(Eth VLAN) UP mpls 10.55.55.2:5200 UP
UP pri ac Se6/0:225(FR DLCI) UP mpls 10.55.55.2:5225 UP
IA sec ac Se6/0:225(FR DLCI) UP mpls 10.55.55.3:5226 DN
IA pri ac Et1/0.2:100(Eth VLAN) UP ac Et2/0.2:100(Eth VLAN) UP
UP sec ac Et1/0.2:100(Eth VLAN) UP mpls 10.55.55.3:1101 UP
UP ac Se6/0:150(FR DLCI) UP ac Se8/0:150(FR DLCI) UP
The following example shows the show xconnect all command output in the detailed display format:
Router# show xconnect all detail
Legend: XC ST=Xconnect State, S1=Segment1 State, S2=Segment2 State
UP=Up, DN=Down, AD=Admin Down, IA=Inactive, SB=Standby, RV=Recovering, NH=No HardwareXC
ST Segment 1 S1 Segment 2 S2
------+---------------------------------+--+---------------------------------+--
UP ac Et0/0(Ethernet) UP mpls 10.55.55.2:1000 UP
Interworking: ip Local VC label 16
Remote VC label 16
pw-class: mpls-ip
UP ac Se7/0(PPP) UP mpls 10.55.55.2:2175 UP
Interworking: ip Local VC label 22
Remote VC label 17
pw-class: mpls-ip
UP pri ac Se6/0:230(FR DLCI) UP mpls 10.55.55.2:2230 UP
Interworking: ip Local VC label 21
Remote VC label 18
pw-class: mpls-ip
IA sec ac Se6/0:230(FR DLCI) UP mpls 10.55.55.3:2231 DN
Interworking: ip Local VC label unassigned
Remote VC label 19
pw-class: mpls-ip
SB ac Se4/0:100(FR DLCI) UP mpls 10.55.55.2:4000 SB
Interworking: none Local VC label 18
Remote VC label 19
pw-class: mpls
UP ac Se6/0:500(FR DLCI) UP l2tp 10.55.55.2:5000 UP
Interworking: none Session ID: 34183
Tunnel ID: 62083
Peer name: pe-iou2
Protocol State: UP
Remote Circuit State: UP
pw-class: l2tp
UP ac Et1/0.1:200(Eth VLAN) UP mpls 10.55.55.2:5200 UP
Interworking: ip Local VC label 17
Remote VC label 20
pw-class: mpls-ip
UP pri ac Se6/0:225(FR DLCI) UP mpls 10.55.55.2:5225 UP
Interworking: none Local VC label 19
Remote VC label 21
pw-class: mpls
IA sec ac Se6/0:225(FR DLCI) UP mpls 10.55.55.3:5226 DN
Interworking: none Local VC label unassigned
Remote VC label 22
pw-class: mpls
IA pri ac Et1/0.2:100(Eth VLAN) UP ac Et2/0.2:100(Eth VLAN) UP
Interworking: none Interworking: none
UP sec ac Et1/0.2:100(Eth VLAN) UP mpls 10.55.55.3:1101 UP
Interworking: none Local VC label 23
Remote VC label 17
pw-class: mpls
UP ac Se6/0:150(FR DLCI) UP ac Se8/0:150(FR DLCI) UP
Interworking: none Interworking: none
Sample Output for All Xconnect Attachment Circuits and Pseudowires on a Cisco uBR10012 Router in the Brief Display FormatThe following is sample output from the show xconnect all command in the brief (default) display format for all xconnect attachment circuits and pseudowires on a Cisco uBR10012 router:
Router# show xconnect all
Legend: XC ST=Xconnect State S1=Segment1 State S2=Segment2 State
UP=Up DN=Down AD=Admin Down IA=Inactive
SB=Standby RV=Recovering NH=No Hardware
XC ST Segment 1 S1 Segment 2 S2
------+---------------------------------+--+---------------------------------+--
UP ac Bu254:2001(DOCSIS) UP mpls 10.76.1.1:2001 UP
UP ac Bu254:2002(DOCSIS) UP mpls 10.76.1.1:2002 UP
UP ac Bu254:2004(DOCSIS) UP mpls 10.76.1.1:2004 UP
DN ac Bu254:22(DOCSIS) UP mpls 101.1.0.2:22 DN
Sample Output for All Xconnect Attachment Circuits and Pseudowires on a Cisco uBR10012 Router in the Brief Display Format in Cisco IOS Release 12.2(33)SCFThe following is sample output from the show xconnect command in the brief (default) display format for all xconnect attachment circuits and pseudowires on a Cisco uBR10012 router in Cisco IOS Release 12.2(33)SCF:
Router# show xconnect all
Legend: XC ST=Xconnect State S1=Segment1 State S2=Segment2 State
UP=Up DN=Down AD=Admin Down IA=Inactive
SB=Standby RV=Recovering NH=No Hardware
XC ST Segment 1 S1 Segment 2 S2
------+---------------------------------+--+---------------------------------+--
DN ac Bu254:55(DOCSIS) DN mpls 10.2.3.4:55 DN
UP ac Bu254:1000(DOCSIS) UP mpls 10.2.3.4:1000 UP
UP ac Bu254:400(DOCSIS) UP mpls 10.76.2.1:400 UP
DN ac Bu254:600(DOCSIS) DN mpls 10.76.2.1:600 DN
UP ac Bu254:1800(DOCSIS) UP mpls 10.76.2.1:1800 UP
DN ac Bu254:45454(DOCSIS) DN mpls 10.76.2.1:45454 DN
Sample Output for All Xconnect Attachment Circuits and Pseudowires on a Cisco uBR10012 Router in the Detailed Display FormatThe following is sample output from the show xconnect command in the detailed display format for all xconnect attachment circuits and pseudowires on a Cisco uBR10012 router:
Router# show xconnect all detail
Legend: XC ST=Xconnect State S1=Segment1 State S2=Segment2 State
UP=Up DN=Down AD=Admin Down IA=Inactive
SB=Standby RV=Recovering NH=No Hardware
XC ST Segment 1 S1 Segment 2 S2
------+---------------------------------+--+---------------------------------+--
UP ac Bu254:2001(DOCSIS) UP mpls 10.76.1.1:2001 UP
Interworking: ethernet Local VC label 40
Remote VC label 110
pw-class:
UP ac Bu254:2002(DOCSIS) UP mpls 10.76.1.1:2002 UP
Interworking: ethernet Local VC label 41
Remote VC label 88
pw-class:
UP ac Bu254:2004(DOCSIS) UP mpls 10.76.1.1:2004 UP
Interworking: ethernet Local VC label 42
Remote VC label 111
pw-class:
DN ac Bu254:22(DOCSIS) UP mpls 101.1.0.2:22 DN
Interworking: ethernet Local VC label 39
Remote VC label unassigned
pw-class:
Sample Output for All Xconnect Attachment Circuits and Pseudowires on a Cisco uBR10012 Router in the Detailed Display Format in Cisco IOS Release 12.2(33)SCFThe following is sample output from the show xconnect command in the detailed display format for all xconnect attachment circuits and pseudowires on a Cisco uBR10012 router in Cisco IOS Release 12.2(33)SCF:
Router# show xconnect all detail
Legend: XC ST=Xconnect State S1=Segment1 State S2=Segment2 State
UP=Up DN=Down AD=Admin Down IA=Inactive
SB=Standby RV=Recovering NH=No Hardware
XC ST Segment 1 S1 Segment 2 S2
------+---------------------------------+--+---------------------------------+--
DN ac Bu254:55(DOCSIS) DN mpls 10.2.3.4:55 DN
Interworking: ethernet Local VC label unassigned
Remote VC label unassigned
pw-class:
UP ac Bu254:1000(DOCSIS) UP mpls 10.2.3.4:1000 UP
Interworking: ethernet Local VC label 33
Remote VC label 36
pw-class:
UP ac Bu254:400(DOCSIS) UP mpls 10.76.2.1:400 UP
Interworking: ethernet Local VC label 35
Remote VC label 194
pw-class:
DN ac Bu254:600(DOCSIS) DN mpls 10.76.2.1:600 DN
Interworking: ethernet Local VC label unassigned
Remote VC label 120
pw-class:
UP ac Bu254:1800(DOCSIS) UP mpls 10.76.2.1:1800 UP
Interworking: ethernet Local VC label 24
Remote VC label 132
pw-class:
DN ac Bu254:45454(DOCSIS) DN mpls 10.76.2.1:45454 DN
Interworking: ethernet Local VC label unassigned
Remote VC label 54
pw-class:
The table below describes the significant fields shown in the displays.
The additional fields displayed in the detailed output are self-explanatory. VPLS Autodiscovery Feature ExampleFor the VPLS Autodiscovery feature, issuing the show xconnect rib command provides RIB details, as shown in the following example:
Router# show xconnect rib
Local Router ID: 10.0.0.0
+- Origin of entry (I=iBGP/e=eBGP)
| +- Imported without a matching route target (Yes/No)?
| | +- Provisioned (Yes/No)?
| | | +- Stale entry (Yes/No)?
| | | |
v v v v
O I P S VPLS-ID Target ID Next-Hop Route-Target
-+-+-+-+----------------------+---------------+--------------+-------------
I Y N N 66:66 10.0.0.1 10.1.1.2 66:66
I Y N N 66:66 10.1.1.2 10.1.1.3 66:66
I N Y N 1:1 10.1.1.1 10.1.1.1 2:2
I N Y N 1:1 10.1.1.1 10.1.1.3 2:2
I N Y N
The table below describes the significant fields shown in the display.
For VPLS Autodiscovery, issuing the show xconnect rib detail command provides more information about the routing information base, as shown in the following example:
Router# show xconnect rib detail
Local Router ID: 10.9.9.9
VPLS-ID 10:123, TID 10.7.7.7
Next-Hop: 10.7.7.7
Hello-Source: 10.9.9.9
Route-Target: 10:123
Incoming RD: 10:10
Forwarder: vfi VPLS1
Origin: BGP
Provisioned: Yes
VPLS-ID 10:123, TID 10.7.7.8
Next-Hop: 10.7.7.8
Hello-Source: 10.9.9.9
Route-Target: 10:123
Incoming RD: 10:11
Forwarder: vfi VPLS1
Origin: BGP
Provisioned: No
VPLS-ID 10.100.100.100:1234, TID 0.0.0.2
Next-Hop: 10.2.2.2, 10.3.3.3, 10.4.4.4
Hello-Source: 10.9.9.9
Route-Target: 10.111.111.111:12345, 10.8.8.8:345
Incoming RD: 10:12
Forwarder: vfi VPLS2
Origin: BGP
Provisioned: Yes
VPLS-ID 10.100.100.100:1234, TID 10.13.1.1
Next-Hop: 10.1.1.1
Hello-Source: 10.9.9.9
Route-Target: 10.111.111.111:12345
Incoming RD: 10:13
Forwarder: vfi VPLS2
Origin: BGP
Provisioned: Yes
The table below describes the significant fields shown in the display.
L2VPN VPLS Inter-AS Option B ExamplesThe following is sample output from the show xconnect rib command when used in a Layer 2 Virtual Private Network (L2VPN) VPLS Inter-AS Option B configuration:
Router# show xconnect rib
Local Router ID: 10.9.9.9
+- Origin of entry (I=iBGP/e=eBGP)
| +- Provisioned (Yes/No)?
| | +- Stale entry (Yes/No)?
| | |
v v v
O P S VPLS-ID Target ID Next-Hop Route-Target
-+-+-+------+---------------+---------------+---------------+-------------
I Y N 1:1 10.11.11.11 10.11.11.11 1:1
I Y N 1:1 10.12.12.12 10.12.12.12 1:1
The table below describes the significant fields shown in the display.
The following is sample output from the show xconnect rib detail command when used in an ASBR configuration. On an ASBR, the show xconnect rib detail command displays the Layer 2 VPN BGP network layer reachability information (NLRI) received from the BGP peers. The display also shows the signaling messages received from the targeted LDP sessions for a given target attachment individual identifier (TAII).
Router# show xconnect rib detail
Local Router ID: 10.1.1.3
VPLS-ID: 1:1, Target ID: 10.1.1.1
Next-Hop: 10.1.1.1
Hello-Source: 10.1.1.3
Route-Target: 2:2
Incoming RD: 10.0.0.0:1
Forwarder:
Origin: BGP
Provisioned: Yes
SAII: 10.0.0.1, LDP Peer Id: 10.255.255.255, VC Id: 1001 ***
SAII: 10.1.0.1, LDP Peer Id: 10.255.255.255, VC Id: 1002 ***
After the passive TPE router receives the BGP information (and before the passive TPE router receives the LDP label), the peer information will be displayed in the output of the show xconnect rib command. The peer information will not be displayed in the show mpls l2transport vc command because the VFI AToM xconnect has not yet been provisioned. Therefore, for passive TPEs, the entry "Passive : Yes" is added to the output from the show xconnect rib detail command. In addition, the entry "Provisioned: Yes" is displayed after the neighbor xconnect is successfully created (without any retry attempts). In the sample output, the two lines beginning with "SAII" show that this ASBR is stitching two provider PE routers (10.0.0.1 and 10.1.0.1) to the TAII 10.1.1.1. The table below describes the significant fields shown in the display.
The following is sample output from the show xconnect rib checkpoint command. Autodiscovered pseudowire information is checkpointed to the standby Route Processor (RP). The show xconnect rib checkpoint command displays that pseudowire information.
Router# show xconnect rib checkpoint
Xconnect RIB Active RP:
Checkpointing : Allowed
Checkpointing epoch: 1
ISSU Client id: 2102, Session id: 108, Compatible with peer
Add entries send ok : 14
Add entries send fail : 0
Delete entries send ok : 2
Delete entries send fail: 0
+- Checkpointed to standby (Yes/No)?
| +- Origin of entry (I=iBGP/e=eBGP)
| | +- Imported without a matching route target (Yes/No)?
| | |
v v v
C O I VPLS-ID Target ID Next-Hop Route-Target
-+-+-+---------------------+---------------+--------------+----------------
N I Y 66:66 10.1.1.1 10.1.1.3 66:66
N I Y 66:66 10.1.1.2 10.1.1.3 66:66
Y I N 1:1 10.1.1.1 10.1.1.1 2:2
Y I N 1:1 10.1.1.1 10.1.1.3 2:2
Y I N 1:1 10.1.1.2 10.1.1.3 2:2
The table below describes the significant fields shown in the display.
The following is sample output from the show xconnect monitor command. Router# show xconnect monitor
Load for five secs: 0%/0%; one minute: 0%; five minutes: 0% Time source is hardware calendar, *21:00:39.098 GMT Fri May 6 2011
Peer IP Local IP State VC Refs
---------------- -------------------------------- ----- -------
10.1.1.2 10.1.1.1 Up 1
10.1.1.3 10.1.1.1 Up 1
Related Commands
shutdown (FR-ATM)To shut down a Frame Relay-ATM Network Interworking (FRF.5) connection or a Frame Relay-ATM Service Interworking (FRF.8) connection, use the shutdown command in FRF.5 or FRF.8 connect configuration mode. To disable disconnection, use the no form of this command. Command History
Usage GuidelinesAn FRF.5 or FRF.8 connection must be manually shut down once the interworking connection is created by use of the shutdown command. FRF.5 Shutdown: ExampleThe following example shows how to shut down an FRF.5 connection: Router(config)# connect network-2 interface serial0/1 16 atm3/0 0/32 network-interworking . . . Router(config-frf5)# shutdown skeptical interval (OTV)To configure a Cisco nonstop forwarding (NSF) helper functionality with an adjacency, use the skeptical interval command in OTV IS-IS instance configuration mode. To return to the default NSF helper setting, use the no form of this command. Syntax Description
Usage GuidelinesNSF is not supported with the neighbor when you configure the skeptical interval command with a value other than 0. If you configure the skeptical interval 0 command, NSF is always supported with the neighbor. smds addressTo specify the Switched Multimegabit Data Service (SMDS) individual address for a particular interface, use the smds addresscommand in interface configuration mode. To remove the address from the configuration file, use the no form of this command. Command History
Usage GuidelinesAll addresses for SMDS service are assigned by the service provider, and can be assigned to individuals and groups. Addresses are entered in the Cisco SMDS configuration software using an E prefix for multicast addresses and a C prefix for unicast addresses. Cisco IOS software expects the addresses to be entered in E.164 format, which is 64 bits. The first 4 bits are the address type, and the remaining 60 bits are the address. If the first 4 bits are 1100 (0xC), the address is a unicast SMDS address, which is the address of an individual SMDS host. If the first 4 bits are 1110 (0xE), the address is a multicast SMDS address, which is used to broadcast a packet to multiple end points. The 60 bits of the address are in binary-coded decimal (BCD) format. Each 4 bits of the address field presents a single telephone number digit, allowing for up to 15 digits. At a minimum, you must specify at least 11 digits (44 bits). Unused bits at the end of this field are filled with ones.
smds dxiTo enable the Data Exchange Interface (DXI) version 3.2 support, use the smds dxi command in interface configuration mode. To disable the DXI 3.2 support, use the no form of this command. Command History
Usage GuidelinesAdding this command to the configuration enables the DXI version 3.2 mechanism and encapsulates SMDS packets in a DXI frame before they are transmitted. DXI 3.2 adds an additional 4 bytes to the SMDS packet header to communicate with the SMDS data service unit (SDSU). These bytes specify the frame type. The interface expects all packets to arrive with DXI encapsulation. The DXI 3.2 support also includes the heartbeat process as specified in the SIG-TS-001/1991 standard, revision 3.2. The heartbeat (active process) is enabled when both DXI and keepalives are enabled on the interface. The echo (passive process) is enabled when DXI is enabled on the interface. The heartbeat mechanism automatically generates a heartbeat poll frame every 10 seconds. This default value can be changed with the keepalive (LMI) command. Fast switching of DXI frames is supported, but Interim Local Management Interface (ILMI) is not.
smds enable-arpTo enable dynamic Address Resolution Protocol (ARP), use the smds enable-arp interface configuration command. The multicast address for ARP must be set before this command is issued. To disable the interface once ARP has been enabled, use the no form of this command. Command History
smds gleanTo enable dynamic address mapping for Internet Packet Exchange (IPX) over Switched Multimegabit Data Service (SMDS), use the smds glean interface configuration command. To disable dynamic address mapping for IPX over SMDS, use the no form of this command. Syntax Description
Command History
Usage GuidelinesThe smds gleancommand uses incoming packets to dynamically map SMDS addresses to higher-level protocol addresses. Therefore the need for static map configuration for the IPX protocol is optional rather than mandatory. However, any static map configuration overrides the dynamic maps. If a map is gleaned and it already exists as a dynamic map, the timer for the dynamic map is reset to the default value or the user-specified value. smds multicastTo assign a multicast Switched Multimegabit Data Service (SMDS) E.164 address to a higher-level protocol, use the smds multicastcommand in interface configuration mode. To remove an assigned multicast address, use the no form of this command. Command History
Usage GuidelinesWhen configuring DECnet, you must enter all four DEC keywords (decnet, decnet_router-L1, decnet_router-L2, and decnet_node) in the configuration. The table below lists the high-level protocols supported by the smds multicast command.
For IP, the IP NETwork and MASK fields are no longer required. The Cisco IOS software accepts these arguments, but ignores the values. These were required commands for the previous multiple logical IP subnetworks configuration. The software continues to accept the arguments to allow for backward compatibility, but ignores the contents. smds multicast arpTo map the Switched Multimegabit Data Service (SMDS) address to a multicast address, use the smds multicast arp interface configuration command. To disable this feature, use the no form of this command.
smds
multicast
arp
smds-address
[ip-address mask]
no
smds
multicast
arp
smds-address
[ip-address mask]
Command History
Usage GuidelinesThis command is used only when an Address Resolution Protocol (ARP) server is present on a network. When broadcast ARPs are sent, SMDS first attempts to send the packet to all multicast ARP SMDS addresses. If none exist in the configuration, broadcast ARPs are sent to all multicast IP SMDS multicast addresses. If the optional ARP multicast address is missing, each entered IP multicast command is used for broadcasting. smds multicast bridgeTo enable spanning-tree updates, use the smds multicast bridge interface configuration command. To disable this function, use the no form of this command. Command DefaultNo multicast SMDS address is defined. Spanning tree updates are disabled for transparent bridging across SMDS networks. Command History
Usage GuidelinesTo allow transparent bridging of packets across serial and High-Speed Serial Interface (HSSI ) interfaces in an SMDS network, the SMDS interface must be added to an active bridge group. Also, standard bridging commands are necessary to enable bridging on an SMDS interface. When the smds multicast bridge command is added to the configuration, broadcast packets are encapsulated with the specified SMDS multicast address configured for bridging. Two broadcast Address Resolution Protocol (ARP) packets are sent to the multicast address. One is sent with a standard (SMDS) ARP encapsulation, while the other is sent with the ARP packet encapsulated in an 802.3 MAC header. The native ARP is sent as a regular ARP broadcast. Cisco's implementation of IEEE 802.6i transparent bridging for SMDS supports 802.3, 802.5, and FDDI frame formats. The router can accept frames with or without frame check sequence (FCS). Fast-switched transparent bridging is the default and is not configurable. If a packet cannot be fast switched, it is process switched. In Cisco IOS Release 10.2 software (or earlier), bridging over multiple logical IP subnetworks is not supported. Bridging of IP packets in a multiple logical IP subnetworks environment is unpredictable. smds multicast ipTo map a Switched Multimegabit Data Service (SMDS) group address to a secondary IP address, use the smds multicast ip interface configuration command. To remove the address map, use the no form of this command.
smds
multicast
ip
smds-address
[ip-address mask]
no
smds
multicast
ip
smds-address
[ip-address mask]
Command DefaultThe IP address and mask default to the primary address of the interface if they are left out of the configuration. Command History
Usage GuidelinesThis command allows a single SMDS interface to be treated as multiple logical IP subnetworks. If taking advantage of the multiple logical IP subnetworks support in SMDS, you can use more than one multicast address on the SMDS interface (by entering multiple commands). However, each smds multicast ip command entry must be associated with a different IP address on the SMDS interface. Broadcasts can be sent on the SMDS interface by means of the multicast address. By sending broadcasts in this manner, the router is not required to replicate broadcasts messages to every remote host. In addition, the higher-level protocols such as Open Shortest Path First (OSPF) and Intermediate System-to-Intermediate System (IS-IS) can use the multicast capability by sending one update packet or routing packet to the multicast address. If the optional IP address and mask arguments are not present, the SMDS address and multicast address are associated with the primary IP address of the interface. This association allows the command to be backward compatible with earlier versions of the software. If an Address Resolution Protocol (ARP) multicast address is missing, each entered IP multicast command is used for broadcasting. The ARP multicast command has the same format as the IP multicast command and is typically used only when an ARP server is present in the network. ExamplesThe following example configures an interface with two subinterfaces to support two different IP subnets with different multicast addresses to each network: interface serial 2/0 encapsulation smds smds address C120.1111.2222.4444 interface serial 2/0.1 multipoint smds addr c111.3333.3333.3333 ip address 2.2.2.1 255.0.0.0 smds multicast ip e222.2222.2222.2222 smds enable-arp interface serial 2/0.2 multipoint smds addr c111.2222.3333.3333.3333 ip address 2.3.3.3 255.0.0.0 smds multicast ip E180.0999.9999.FFFF smds enable-arp smds static-mapTo configure a static map between an individual Switched Multimegabit Data Service (SMDS) address and a higher-level protocol address, use the smds static-mapcommand in interface configuration mode. To remove the map, use the no form of this command with the appropriate arguments.
smds
static-map
protocol
protocol-address
smds-address
[broadcast]
no
smds
static-map
protocol
protocol-address
smds-address
[broadcast]
Syntax Description
Command History
Usage GuidelinesThe smds static-map command provides pseudobroadcasting by allowing the use of broadcasts on those hosts that cannot support SMDS multicast addresses. ExamplesThe following example illustrates how to enable pseudobroadcasting. The router at address C120.4444.9999 will receive a copy of the broadcast request because the broadcast keyword is specified with the smds static-map command. The host at address 172.16.1.15 is incapable of receiving multicast packets. The multicasting is simulated with this feature. interface hssi 0 encapsulation smds smds address C120.1111.2222.FFFF ip address 172.16.1.30 255.255.255.0 smds static-map ip 172.16.1.15 C120.4444.9999.FFFF broadcast smds enable-arp The following example illustrates how to enable multicasting. In addition to IP and ARP requests to E100.0999.9999, the router at address C120.4444.9999 will also receive a copy of the multicast request. The host at address 172.16.1.15 is incapable of receiving broadcast packets. interface hssi 0 encapsulation smds smds address C120.1111.2222.FFFF ip address 172.16.1.30 255.255.255.0 smds multicast ip E100.0999.999.FFFF smds static-map ip 172.16.1.15 C120.4444.9999.FFFF smds enable-arp snmp-server enable traps waasTo enable Simple Network Management Protocol (SNMP) traps for WAAS Express, use the snmp-server enable traps waas command in global configuration mode. To disable the SNMP traps for WAAS Express, use the no form of this command.
snmp-server enable traps waas
[cpu-throttle-on] [cpu-throttle-off] [license-deleted] [license-expired] [license-revoked] [peer-overload] [tfo-conn-overload]
no snmp-server enable traps waas
[cpu-throttle-on] [cpu-throttle-off] [license-deleted] [license-expired] [license-revoked] [peer-overload] [tfo-conn-overload]
Syntax Description
ExamplesThe following example shows how to enable traps to delete WAAS Express licenses and TFO overload: Device# enable Device# configure terminal Device(config)# snmp-server enable traps waas license-deleted tfo-conn-overload Related Commands
spf-interval (OTV)To configure the minimum interval between shortest path first (SPF) computations, use the spf-interval command in OTV IS-IS instance configuration mode. To remove the configuration for the SPF interval, use the no form of this command. Command DefaultLayer 2 is configured, by default, with SPF intervals of 5 seconds, 50 milliseconds, and 200 milliseconds for the spf-max-wait, spf-initial-wait, and spf-second-wait arguments, respectively. status admin-down disconnectTo configure Layer 2 tunneling (L2TUN) sessions to disconnect upon attachment circuit (AC) shutdown, use the status admin-down disconnect command in pseudowire class configuration mode. To disable disconnection of L2TUN sessions upon AC shutdown, use the no form of this command. Usage GuidelinesUse the show l2tp session command to determine whether the sessions are disconnected. ExamplesThe following example shows how to enter pseudowire class configuration mode to configure a pseudowire configuration template named ether-pw and configure L2TUN sessions to disconnect on AC shutdown. Router> enable Password: Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# pseudowire-class ether-pw Router(config-pw)# status admin-down disconnect Router(config-pw)# end Related Commands
suppress-server-encoding enableTo suppress server side encoding, use the suppress-server-encoding enable command in WAAS HTTP configuration mode. To enable server side encoding, use the no form of this command. Usage GuidelinesA client uses the Accept-Encoding header in the HTTP request it sends to indicate the types of compressions it supports. The values usually sent by the client include identity, gzip, deflate and compress. When server side encoding is suppressed, the client side WAAS Express removes the values of this header, and the server does not compress the data it sends. WAAS Express uses the suppression of server side encoding mechanism to provide better compression on HTTP response from the server and also frees the server from the additional computation required to compress responses. Before you can enable the suppress-server-encoding enable command, use the following commands: tfo auto-discovery blacklistTo configure a blacklist with autodiscovery for WAAS Express, use the tfo auto-discovery blacklistcommand in parameter-map configuration mode. To remove the configuration, use the no form of this command.
tfo
auto-discovery
blacklist
{enable | hold-time minutes}
no
tfo
auto-discovery
blacklist
{enable | hold-time minutes}
Usage GuidelinesA server is blacklisted by WAAS Express if the server is not able to receive TCP packets with options because of the TCP packets with options being blocked by network devices such as firewalls. WAAS Express learns not to send TCP packets with options to these blacklisted servers. Use this command to enable, configure, and integrate a blacklist with autodiscovery and specify the hold time for a blacklist in WAAS Express. Blacklists enable you to get the benefit of WAAS Express if there are devices in your network that discard TCP packets with options. Autodiscovery allows a WAAS Express device to automatically discover and connect to a new file server when a Common Internet File System (CIFS) request is received. The autodiscovery of peer WAAS Express devices is achieved using TCP options. These TCP options are recognized and understood only by WAAS Express devices and are ignored by non-WAAS Express devices. ExamplesThe following example configures autodiscovery by enabling the blacklist and setting the hold time for 100 minutes: Router(config)# parameter-map type waas waas_global Router(config-profile)# tfo auto-discovery blacklist enable Router(config-profile)# tfo auto-discovery blacklist hold-time 100 Related Commands
tfo optimizeTo configure the compression for WAAS Express, use the tfo optimize command in parameter-map configuration mode. To remove the compression, use the no form of this command.
tfo
optimize
{full | dre{yes | no compression{lz | none}}}
no
tfo
optimize
[full | dre{yes | no compression{lz | none}}]
Usage GuidelinesUse this command to specify a compression technology to reduce the size of data. WAAS Express uses the following compression technologies to help you transmit data over your WAN: These compression technologies reduce the size of transmitted data by removing redundant information before sending the shortened data stream over the WAN. By reducing the amount of transferred data, WAAS compression can reduce network utilization and application response times. LZ compression operates on smaller data streams and keeps limited compression history. DRE operates on significantly larger streams (typically tens to hundreds of bytes or more) and maintains a much larger compression history. Large chunks of redundant data is common in file system operations when files are incrementally changed from one version to another or when certain elements are common to many files, such as file headers and logos. ExamplesThe following example turns off the DRE compression and turns on the LZ compression: Router(config)# parameter-map type waas waas_global Router(config-profile)# tfo optimize dre no compression lz Related Commands
threshold deTo configure the threshold at which discard eligible (DE)-marked packets will be discarded from switched permanent virtual circuits (PVCs) on the output interface, use the threshold de command in Frame Relay congestion management configuration mode. To remove the threshold configuration, use the no form of this command. Command History
Usage GuidelinesYou must enable Frame Relay congestion management on the interface before congestion management parameters will be effective. To enable Frame Relay congestion management and to enter Frame Relay congestion management configuration mode, use the frame-relay congestion-management interface command. You must enable Frame Relay switching, using the frame-relay switching global command, before the threshold decommand will be effective on switched PVCs. ExamplesThe following example shows how to configure a DE threshold of 40% on serial interface 1. interface serial1 encapsulation frame-relay frame-relay congestion-management threshold de 40 Related Commands
threshold ecnTo configure the threshold at which explicit congestion notification (ECN) bits will be set on packets in switched permanent virtual circuits (PVCs) on the output interface, use the threshold ecn command in Frame Relay congestion management configuration mode. To remove the threshold configuration, use the no form of this command. For Frame Relay Switching
threshold
ecn
{bc | be}
percentage
no
threshold
ecn
{bc | be}
percentage
For Frame Relay over MPLS
threshold
ecn
percentage
no
threshold
ecn
percentage
Syntax Description
Command History
Usage GuidelinesYou must enable Frame Relay congestion management on the interface before congestion management parameters will be effective. To enable Frame Relay congestion management and to enter Frame Relay congestion management configuration mode, use the frame-relay congestion-management interface command. Frame Relay Switching Guidelines
Frame Relay Switching: ExampleThe following example shows how to configure a Be threshold of 0 and a Bc threshold of 20 percent on serial interface 1. interface serial1 encapsulation frame-relay frame-relay congestion-management threshold ecn be 0 threshold ecn bc 20 timeout setupTo configure the amount of time allowed to set up a control channel with a remote provider edge (PE) router at the other end of a Layer 2 pseudowire, use the timeout setupcommand in L2TP class configuration mode. To disable the configured value, use the no form of this command. Usage GuidelinesUse this command to configure the amount of time that can be spent attempting to establish a control channel. vc-groupTo assign multiple Frame Relay data-link connection identifiers (DLCIs) to a virtual circuit (VC) group for Frame Relay-to-ATM Network Interworking (FRF.5), use the vc-group command in global configuration mode. To disable the VC group assignments, use the no form of this command. Command History
Usage GuidelinesThis command specifies the Frame Relay DLCIs in the VC group and maps them to the Frame Relay-SSCS DLCIs. If the optional FR-SSCS DLCI value is not specified, its value is the same as the Frame Relay DLCI. The vc-group command requires that you enter the following arguments in VC-group configuration mode to provide a map between Frame Relay DLCIs and Frame Relay-SSCS DLCIs: fr-interface-name fr-dlci [fr-sscs-dlci] ExamplesThe following example shows how to configure an FRF.5 many-to-one connection. The vc-group command maps Frame Relay DLCI 16, 17, 18, and 19 to a VC group named "friends": Router(config)# vc-group friends Router(config-vc-group)# serial0 16 1 6 Router(config-vc-group)# serial0 17 17 Router(config-vc-group)# serial0 18 18 Router(config-vc-group)# serial0 19 19 vpls-idTo assign an identifier to the Virtual Private LAN Service (VPLS) domain, use the vpls-id command in L2 VFI configuration mode. To revert to the default VPLS ID, use the no form of this command.
vpls-id
{autonomous-system-number : nn | ip-address : nn}
no
vpls-id
{autonomous-system-number : nn | ip-address : nn}
Usage GuidelinesVPLS Autodiscovery automatically generates a VPLS ID using the Border Gateway Protocol BGP autonomous system number and the configured VFI VPN ID. You can use the vpls-id command to change the automatically generated VPLS ID. The Label Distribution Protocol (LDP) uses the VPLS ID when signaling VPLS autodiscovered neighbors. The VPLS ID identifies the VPLS domain. Only one VPLS ID can be configured per virtual forwarding instance (VFI), and the same VPLS ID cannot be configured in multiple VFIs on the same provider edge (PE) router. The manually configured VPLS ID replaces the internally generated VPLS ID. The manually configured VPLS ID also changes the automatically generated route target (RT). The vpls-id command defines the attachment group identifier (AGI) for the VPLS domain. Therefore, all provider edge (PE) routers in the same VPLS domain must use the same VPLS ID. For interautonomous system configurations, you must manually configure the VPLS ID instead of using the automatically generated VPLS ID, because all PE routers do not share the same autonomous system number. waas cm-register urlTo register a device with the WAAS Central Manager, use the waas cm-register url command in privileged EXEC mode. Usage GuidelinesUse this command to register a device with the WAAS Central Manager. Before enabling this command, the WCM certificate must be installed on the router.
The values for the url argument can be one of the following: ExamplesThe following example shows how to register a device with the WAAS Central Manager: Router> enable Router# waas cm-register url https://192.0.2.1:8443/wcm/register Related Commands
waas configTo restore or remove WAAS Express default configurations, use the waas config command in privileged EXEC mode. Usage GuidelinesUse this command to either restore the default configurations or remove the configurations. This command works only if WAAS Express is not enabled on any interface. ExamplesThe following example shows how to restore the WAAS Express default configuration: Router> enable Router# waas config restore-default Related Commands
waas enableTo enable Wide-Area Application Services (WAAS) Express on a WAN interface, use the waas enable command in interface configuration mode. To disable WAAS Express on a WAN interface, use the no form of this command. Usage GuidelinesThe waas enable command must be explicitly applied on each WAN interface. You can enable WAAS Express by using either the default class and policy maps created automatically or the class and policy maps that you define. waas exportTo associate a NetFlow exporter with WAAS Express which is used to export WAAS fields in the NetFlow v9 records, use the waas exportcommand in global configuration mode. To remove the association, use the no form of this command.
waas
export
{name exporter-name | timeout timeout-value}
no
waas
export
{name exporter-name | timeout timeout-value}
Usage GuidelinesUse this command to associate a NetFlow exporter with WAAS Express and export fields to NetFlow v9 records. Use the timeout argument to set the timeout value for exporting long living connection. ExamplesThe following example shows how to associate a NetFlow exporter named exporter1. Router> enable Router# configure terminal Router(config)# flow exporter exporter1 Router(config)# destination 209.165.200.225 Router(config)# waas export name exporter1 Related Commands
waas-ssl-trustpointTo associate a trustpoint with Secure Sockets Layer (SSL)-Express accelerator, use the waas-ssl-trustpoint command in WAAS SSL configuration mode. To associate SSL-Express accelerator with a self-enrolled trustpoint, use the no form of this command. Usage GuidelinesThe trustpoint associated with SSL-Express accelerator should already exist. You can create a trustpoint by using the crypto pki trustpoint command. An identity certificate should be enrolled under this trustpoint for WAAS Express to accept this configuration. This identity certificate is then used for the peering session established by the SSL-Express accelerator between WAAS Express devices. SSL-Express accelerator, if enabled, generates a self-enrolled trustpoint and configures the trustpoint name using the waas-ssl-trustpoint command in the following situations:
Before you can enable the waas-ssl-trustpoint command, use the following commands: ExamplesThe following example shows how to associate a trustpoint with SSL-Express accelerator: Device(config)# parameter-map type waas waas_global Device(config-profile)# accelerator ssl-express Device(config-waas-ssl)# enable Device(config-waas-ssl)# waas-ssl-trustpoint ssl-tp Related Commands
1 DTE = data terminal equipment 2 DCE = data communications equipment 3 DTE = data terminal equipment 4 DCE = data communications equipment 5 The ITU-T carries out the functions of the former Consultative Committee for International Telegraph and Telephone (CCITT). © 2012 Cisco Systems, Inc. All rights reserved.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|