The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This module provides information about Nonstop Routing (NSR), Transmission Control Protocol (TCP), and User Datagram Protocol (UDP) transports on Cisco ASR 9000 Series Aggregation Services Routers .
If you have specific requirements and need to adjust the NSR, TCP, or UDP values, refer to the Transport Stack Commands on IP Addresses and Services Command Reference for Cisco ASR 9000 Series Routers.
 Note |
For a complete description of the transport configuration commands listed in this module, refer to the Cisco ASR 9000 Series Aggregation Services Router IP Addresses and Services Command Reference publication. |
|
Release |
Modification |
|---|---|
|
Release 3.7.2 |
This feature was introduced. |
|
Release 6.3.3 |
XIPC Queue Drop Detection and Correction feature was introduced for TCP. |
The following prerequisites are required to implement NSR, TCP, UDP, Transports:
You must be in a user group associated with a task group that includes the proper task IDs. The command reference guides include the task IDs required for each command. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
To configure NSR, TCP, and UDP transports, you must understand the following concepts:
Nonstop Routing (NSR) is provided for Open Shortest Path First (OSPF) and Label Distribution Protocol (LDP) protocols for the following events:
Route Processor (RP) failover
Process restart for either OSPF, LDP, or TCP
In-service software upgrades (ISSU)
In the case of the RP failover, NSR is achieved by for both TCP and the applications (OSPF or LDP).
NSR is a method to achieve High Availability (HA) of the routing protocols. TCP connections and the routing protocol sessions are migrated from the active RP to standby RP after the RP failover without letting the peers know about the failover. Currently, the sessions terminate and the protocols running on the standby RP reestablish the sessions after the standby RP goes active. Graceful Restart (GR) extensions are used in place of NSR to prevent traffic loss during an RP failover but GR has several drawbacks.
You can use the nsr process-failures switchover command to let the RP failover be used as a recovery action when the active TCP or active LDP restarts. When standby TCP or LDP restarts, only the NSR capability is lost till the standby instances come up and the sessions are resynchronized but the sessions do not go down. In the case of the process failure of an active OSPF, a fault-management policy is used. For more information, refer to Implementing OSPF on Routing Configuration Guide for Cisco ASR 9000 Series Routers.
TCP is a connection-oriented protocol that specifies the format of data and acknowledgments that two computer systems exchange to transfer data. TCP also specifies the procedures the computers use to ensure that the data arrives correctly. TCP allows multiple applications on a system to communicate concurrently, because it handles all demultiplexing of the incoming traffic among the application programs.
Any IP protocol other than TCP or UDP is known as a RAW protocol.
For most sites, the default settings for the TCP, UDP, and RAW transports need not be changed.
The User Datagram Protocol (UDP) is a connectionless transport-layer protocol that belongs to the IP family. UDP is the transport protocol for several well-known application-layer protocols, including Network File System (NFS), Simple Network Management Protocol (SNMP), Domain Name System (DNS), and TFTP.
Any IP protocol other than TCP, UDP, is known as a RAW protocol.
For most sites, the default settings for the TCP, UDP, and RAW transports need not be changed.
During external port scanning on ports 19 and 20, the UDP packets dropped by Nmap tool without sending an ICMP response, cause uncertainty in identifying the true state of the ports. The port states can be open, closed, or filtered.
Due to no response from the target system, the port states might misclassify as open instead of a closed or filtered state, and can lead to a false-positive situation.
|
Platform |
Start of Range |
End of Range |
Availability |
|---|---|---|---|
|
Cisco IOS XR 64-bit Operating System |
15000 |
57344 |
Available |
|
Cisco IOS XR 64-bit Operating System |
57345 |
65535 |
Reserved |
|
Cisco IOS XR 32-bit Operating System |
15000 |
65535 |
Available |
This section contains the following procedure:
This task allows you to configure failover as a recovery action to process failures of active instances.
When the active TCP or the NSR client of the active TCP terminates or restarts, the TCP sessions go down. To continue to provide NSR, failover is configured as a recovery action. If failover is configured, a switchover is initiated if the active TCP or an active application (for example, LDP, OSPF, and so forth) restarts or terminates.
For information on how to configure MPLS Label Distribution Protocol (LDP) for NSR, refer to the MPLS Configuration Guide for Cisco ASR 9000 Series Routers.
For information on how to configure NSR on a per-process level for each OSPF process, refer to the Routing Configuration Guide for Cisco ASR 9000 Series Routers.
Note |
Before performing this procedure, enable RP isolation using the isolation enable command for improved troubleshooting. Without enabling RP isolation, the failing process will not generate the logs required to find the root cause of the failure. |
| Command or Action | Purpose | |
|---|---|---|
|
Step 1 |
configure |
|
|
Step 2 |
nsr process-failures switchover Example: |
Configures failover as a recovery action for active instances to switch over to a standby route processor (RP) to maintain nonstop routing (NSR. |
|
Step 3 |
commit |
Congestion avoidance techniques monitor network traffic loads in an effort to anticipate and avoid congestion at common network bottlenecks. Congestion avoidance is achieved through packet dropping. Extended IPC (XIPC) Tail drop is one of the more commonly used congestion avoidance mechanisms. Tail drop treats all traffic equally and does not differentiate between classes of service. Queues fill during periods of congestion. When the output queue is full and tail drop is in effect, packets are dropped until the congestion is eliminated and the queue is no longer full.
This feature introduces XIPC as a new policer, and culprit session falls into this bucket and is policed heavily. This feature improves the serviceability of the XIPC queues owned by TCP. To perform this, the TCP monitors and identifies the sessions that are receiving more data. TCP revisits the statistics at regular intervals, and based on the data, it decides whether the sessions need to be policed or added to default policer rate. Therefore, other sessions are given a fair chance to use the XIPC queue, and high-data sessions are throttled down at hardware.
To detect the culprit session, TCP internal queue size is considered along with rate-limit. If the overall queue size reaches the threshold value and per session rate-limit value is exceeded then the culprit sessions in that queue are detected.
After applying the dynamic policer, culprit sessions may flap. As per the TCP dumpfiles and logs, this is an expected behavior. If a culprit BGP session has aggressive timers (KA 3 sec and Hold timer 9 sec), even then the sessions may flap and we may not verify the LPTS packet drops using the show lpts commands.
The following configuration enables XIPC tail drop on TCP:
RP/0/0/CPU0:Router (config)# tcp num-thread Ingress-threads-TCP max-threads
RP/0/0/CPU0:Router (config)# pak-rate tcp stats-start [rate-limit packet rate | max-pkt-size max-pkt-size-value max-pak-rate max-pak-rate-value]
The following example displays the statistics of TCP packet rate.
RP/0/RSP0/CPU0:Router# show tcp pak-rate stats
PR - Number of packets in 30 sec (display, if more than Rate-limit)
MPR - Maximum size packets in 30 sec (display, if more than Maximum packet rate)
Time Foreign Address Local Address VRF PR MPR
----------------------------------------------------------------------------------------------------------------------------
Nov 19 15:56:08.464 6.6.13.7:179 6.6.13.6:23898 0x60000000 18767 1502
Nov 19 15:56:08.464 6.6.1.7:46922 6.6.1.6:179 0x60000000 107802 8932
Note |
|
The following example verifies the sessions statistics at XIPC policer-index level and per-session level.
RP/0/RSP0/CPU0:Router# show lpts pifib hardware police location 0/3/cPU0 | i XIPC
Accept Drop
XIPC 97 Local 1000 9600 3912960 368661 01234567
RP/0/RSP0/CPU0:Router# show lpts pifib hardware police location 0/3/cPU0 | i XIPC
Accept Drop
XIPC 97 Local 1000 9600 0 0 01234567
Note |
Statistics are cleared when last session under this policer index is removed. |
The following example verifies the sessions statistics at XIPC policer and also provides the entries present in the hardware.
RP/0/RSP0/CPU0:Router# show lpts pifib hardware entry statistics location 0/3/cpu0 | i 6.6.1.7,
Accept/Drop
1754 IPV4 default TCP any LU(30) 4021290/456698 any, 179 6.6.1.7, 46922
2584 IPV4 default TCP any LU(30) 0/0 any, 179 6.6.1.7, any
The following sections provide references related to configuring NSR, TCP, and UDP transports.
|
Related Topic |
Document Title |
|---|---|
|
the Cisco ASR 9000 Series Router Transport Stack commands: complete command syntax, command modes, command history, defaults, usage guidelines, and examples |
Transport Stack Commands in the IP Addresses and Services Command Reference for Cisco ASR 9000 Series Routers |
|
the Cisco ASR 9000 Series Router MPLS LDP commands: complete command syntax, command modes, command history, defaults, usage guidelines, and examples |
MPLS Label Distribution Protocol Commands in the MPLS Command Reference for Cisco ASR 9000 Series Routers |
|
the Cisco ASR 9000 Series Router OSPF commands: complete command syntax, command modes, command history, defaults, usage guidelines, and examples |
OSPF Commands in the Routing Command Reference for Cisco ASR 9000 Series Routers |
|
MPLS Label Distribution Protocol feature information |
Implementing MPLS Label Distribution Protocol in the MPLS Configuration Guide for Cisco ASR 9000 Series Routers |
|
OSPF feature information |
Implementing OSPF in the Routing Configuration Guide for Cisco ASR 9000 Series Routers |
|
Standards |
Title |
|---|---|
|
No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature. |
— |
|
MIBs |
MIBs Link |
|---|---|
| — |
To locate and download MIBs, use the Cisco MIB Locator found at the following URL and choose a platform under the Cisco Access Products menu: https://mibs.cloudapps.cisco.com/ITDIT/MIBS/servlet/index |
|
RFCs |
Title |
|---|---|
|
No new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified by this feature. |
— |
|
Description |
Link |
|---|---|
|
The Cisco Technical Support website contains thousands of pages of searchable technical content, including links to products, technologies, solutions, technical tips, and tools. Registered Cisco.com users can log in from this page to access even more content. |
|
Feature Name |
Release Information |
Feature Description |
|---|---|---|
|
TCP Dump File Converter |
Release 24.2.1 |
You can now convert an entire TCP dump of packet traces in binary files into readable formats such as text or cap, which makes it easier to analyze them for troubleshooting using third-party or open-source tools. This feature saves time and effort by preventing the need to examine each packet for failure. This feature introduces the tcp dump-file convert command. |
TCP dump file converter is a tool that converts tcp ios-xr dump-files in binary format to user-friendly format such as pcap or text.
It proves especially useful when you disable Non-Stop Routing (NSR) or experience a session flap on your router. During such incidents, by default, the tcp process running on the router promptly stores the latest 200 packet traces in binary format within a temporary folder.
TCPdump packet traces also includes data about the configured routing protocols and the overall network traffic traversing your system. This data equips you with the necessary insights to identify and resolve issues within your network infrastructure, facilitating proactive network troubleshooting.
You can view the packet traces binary files in the user-readable format using the following methods:
You can use the show tcp dump-file <binary filename> command to view each binary file in text format manually. For more information, refer to View Binary Files in Text Format Manually.
This process consumes much time, as you have to view each file manually one after another.
From Release 24.2.1, you can convert all stored packet traces in binary files into a user-readable format such as pcap, text, or both using the tcp dump-file convert command. For more information, refer to Convert Binary Files to Readable Format Using TCP Dump File Converter.
This active approach greatly improves the efficiency and ease of packet analysis during network troubleshooting.
Routers only store the most recent 200 message exchanges that occurred right before the session termination, when NSR is disabled, or during a session flap.
You can view only one binary file in text format using the show tcp dump-file <binary filename> command.
When the NSR is disabled, the tcp dump files are stored only for major protocols like border gateway protocol (BGP), multicast source discovery protocol (MSDP), and multiprotocol label switching label distribution protocol (MPLS LDP).
|
Step 1 |
View the list of packet traces in binary files stored in the tcpdump folder using the show tcp dump-file list all command. Example: |
|
Step 2 |
View each packet traces binary file in text format using the show tcp dump-file <binary filename> command. Example:The above sample displays only a part of the actual output; the actual output displays more details. |
|
Step 1 |
Execute the tcp dump-file convert all-formats all command to convert the tcp dump packet traces in binary files into pcap and text formats. Example:By default, the router stored the converted files in the "decoded_dumpfiles" folder on the "hard disk". Using the location node-id and file <file path> keywords, you can save the converted TCP dump file to your desired location. For example, tcp dump-file convert all-formats all location 0/RP0/CPU0 file /harddisk:/demo2 . For more information, refer to System Management Command Reference for Cisco NCS 5500 Series Routers tcp dump-file convert command. |
|
Step 2 |
To view the converted text file in the CLI, use the run cat <text file path> command. Example:The above sample displays only a part of the actual output; the actual output displays more details. |
|
Step 3 |
Use remote file copy commands like scp from your lab server to copy the converted packet traces from the router to your local computer and view the converted pcap file. |
Feedback