Downloads |
Table Of Contents
HPR Capable SNA Routing Services
Dynamic CP Name Generation Support
Responsive Mode Adaptive Rate-Based Flow Control
Trap MIB Support for Advanced Network Management Awareness
LAN and IP-Focused Connection Types
Token Ring, Ethernet, and FDDI
Connection to Frame Relay Transport Technologies
Connection to Channel Interface Processor and Channel Port Adapter
Transport over DLSw+ Supported Media
DLC Switching Support for Access to SDLC and QLLC
Native IP Data-Link Control (HPR/IP)
Reduced Configuration Requirements
Increased Management Capabilities
Supported MIBs, RFCs, and Standards
Defining a SNASw Control Point Name
Defining a SNASw Partner LU Location
Starting SNASw and SNASw Ports and Links
Stopping SNASw and SNASw Ports and Links
Monitoring and Maintaining SNASw
SNASw over Token Ring without HPR Configuration Example
SNASw over Token Ring with HPR Configuration Example
SNASw Connecting to a CIP over VirtualToken Ring with SRB Configuration Example
SNASw over HPR/IP Configuration Example
SNASw using Local Switching with QLLC Configuration Example
SNASw using Local Switching with SDLC Configuration Example
SNASw with Ethernet LAN Emulation over ATM Configuration Example
SNASw with SRB Frame Relay (Frame Relay BAN Support) Configuration Example
SNASw with FRAS Host (Downstream Frame Relay BNN Support) Configuration Example
SNA Switching Services
This feature module describes the SNA Switching Services (SNASw) feature and includes the following major sections:
•
Supported MIBs, RFCs, and Standards
•
Feature Overview
Note
SNASw provides an easier way to design and implement networks with Systems Network Architecture (SNA) routing requirements. Previously, this network design was accomplished using Advanced Peer-to-Peer Networking (APPN) with full network node (NN) support in the Cisco router. This type of support provided the SNA routing functionality needed, but was inconsistent with the trends in Enterprise networks today. The corporate intranet is replacing the SNA WAN. Enterprises are replacing their traditional SNA network with an IP infrastructure that supports traffic from a variety of clients, using a variety of protocols, requiring access to applications on a variety of platforms, including SNA applications on Enterprise servers.
While SNA routing is still required when multiple servers must be accessed, the number of nodes required to perform this function is decreasing as the IP infrastructure grows and as the amount of native SNA traffic in the network decreases.
SNASw enables an enterprise to develop their IP infrastructure, while meeting SNA routing requirements.
The number of NNs in the network and the amount of broadcast traffic are reduced. Configuration is simplified, and SNA data traffic can be transported within the IP infrastructure. The following features provide this functionality:
•
•
HPR Capable SNA Routing Services
SNASw provides the following SNA routing functions:
•
•
•
•
•
•
•
•
Branch Extender
SNASw features use branch network nodes (BrNNs). The Branch Extender (BEX) function enhances scalability and reliability of SNA routing nodes by eliminating topology updates and broadcast directory storms that can cause network instability. BEX appears as an NN to downstream end node (EN), low-entry networking (LEN) node, and PU 2.0 devices, while also appearing as an EN to upstream devices. The BEX function eliminates APPN topology and APPN broadcast search flows between SNASw nodes and the SNA data hosts in the network. This feature is key to providing a reliable turn-key installation because the network administrator no longer needs to develop in-depth knowledge of the level and characteristics of broadcast directory search and topology update traffic in the network. Such knowledge and analysis was commonly required to build successful networks utilizing NN technology without BEX.
illustrates the BEX functionality.
Figure 1 BEX Functionality
Enterprise Extender (HPR/IP)
SNASw also supports the Enterprise Extender (EE) function. EE offers SNA HPR support directly over IP networks. EE also uses connectionless User Datagram Protocol (UDP) transport. SNA COS and transmission priority are maintained by mapping the transmission priority to the IP precedence and by mapping transmission priority to separate UDP port numbers, allowing the IP network to be configured based on these elements. Cisco's IP prioritization technologies, such as weighted fair queuing (WFQ), prioritize the traffic through the IP network. EE support on the IBM Communications Server for S/390 allows users to build highly reliable SNA routed networks that run natively over an IP infrastructure directly to the Enterprise servers. These network designs reduce points of failure in the network and provide reliable SNA networks.
illustrates the EE functionality.
Figure 2 EX Functionality
Usability Features
SNASw contains the following usability features designed to make SNA networks easier to design and maintain:
•
•
Dynamic CP Name Generation Support
When scaling the SNASw function to hundreds or thousands of nodes, many network administrators find that defining a unique control point (CP) name on each node provides unnecessary configuration overhead. Dynamic CP name generation offers the ability to use the Cisco IOS hostname as the SNA CP name or to generate a CP name from an IP address. These facilities reuse one SNASw configuration across many routers and eliminate the specific configuration coordination previously required to configure a unique CP name for each SNA node in the network. However, the ability to explicitly configure each CP name still exists.
Dynamic SNA BTU Size
Most SNA node implementations require specific tuning of the SNA basic transmit unit (BTU) in the configuration. SNASw analyzes the interface maximum transfer units (MTUs) of the interfaces it uses and dynamically assigns the best MTU values for that specific port. For served dependent PU 2.0 devices, SNASw uses the downstream MAXDATA value from the host and dynamically sets the SNA BTU for that device to the MAXDATA value.
DLUR Connect-Out
SNASw can receive connect-out instructions from the IBM Communications Server for S/390. This function allows the system to dynamically connect-out to devices that are configured on the host with the appropriate connect-out definitions. This feature allows connectivity to SNA devices in the network that were traditionally configured for connect-out from the host.
Note
Responsive Mode Adaptive Rate-Based Flow Control
Early HPR implementations failed to perform well in environments subject to packet loss (for example, Frame Relay, IP transport) and performed poorly when combined with other protocols in multiprotocol networks. SNASw implements the second-generation HPR flow control architecture, called Responsive Mode Adaptive Rate-Based (ARB) architecture. Responsive Mode ARB addresses all the drawbacks of the earlier ARB implementation, providing faster ramp-up, better tolerance of lost frames, and better tolerance of multiprotocol traffic.
User-Settable Port Limits
SNASw offers full control over the number of devices supported by a specific node. The max-links configuration on the SNASw port controls the number of devices that are served by this node. When the max-links limit is reached, SNASw no longer responds to explorers attempting to establish new connections. SNASw allows load sharing among different SNASw nodes that offer service to the same SNA MAC addresses.
Management Enhancements
SNASw contains the following enhanced tools for managing SNA networks:
•
Console Message Archiving
Messages issued by SNASw are archived in a buffer log that is queried and searched on the console or transferred to a file server for analysis. Each message has a single line that identifies the nature of the event that occurred. The buffer log also maintains more detailed information about the message issued.
Data-Link Tracing
SNA frames entering or leaving SNASw are traced to the console or to a cyclic buffer. These frames are analyzed at the router or transferred to a file server for analysis. The trace is sent to a file server in a SNA-formatted text file or in binary format readable by existing traffic analysis applications. SNASw also captures record frames natively, eliminating the need for network analyzers to capture network events for analysis.
Interprocess Signal Tracing
The SNASw internal information is traced in binary form, offering valuable detailed internal information to Cisco support personnel. This information helps diagnose suspected defects in SNASw.
Trap MIB Support for Advanced Network Management Awareness
SNASw supports the APPN Trap MIB, which proactively sends traps with information about changes in SNA resource status. This implementation reduces the frequency of SNMP polling necessary to manage SNA devices in the network.
LAN and IP-Focused Connection Types
SNASw supports several connection types to serve all SNA connectivity options, including the following types:
•
•
Token Ring, Ethernet, and FDDI
SNASw natively supports connectivity to Token Ring, Ethernet, and FDDI networks. In this configuration mode, the MAC address used by SNASw is the local configured or default MAC address of the interface.
Virtual Token Ring
Using virtual Token Ring allows SNASw access to source-route bridging (SRB), which allows the following configuration:
•
•
Attachment to Local LANs
Virtual Token Ring allows you to connect to local LAN media through SRB technology. Because there is no limit to the number of virtual Token Ring interfaces that can connect to a specific LAN, this technology allows configuration of multiple MAC addresses, which respond to SNA requests over the same LAN. When using native LAN support, SNASw responds only to requests that target the MAC address configured on the local interface. Virtual Token Ring and SRB allow SNASw to respond to multiple MAC addresses over the same physical interface.
Connection to Frame Relay Transport Technologies
Virtual Token Ring and SRB connect SNASw to a SNA Frame Relay infrastructure. FRAS host and SRB Frame Relay are configured to connect virtual Token Ring interfaces that offer SNASw support for Frame Relay boundary access node (BAN) or boundary network node (BNN) technology.
Connection to Channel Interface Processor and Channel Port Adapter
Virtual Token Ring and SRB can be used to connect SNASw to the Channel Interface Processor (CIP) or Channel Port Adapter (CPA) in routers that support those interfaces.
Virtual Data-Link Control
SNASw uses Virtual Data-Link Control (VDLC) to connect to DLSw+ transport and local switching technologies. VDLC is used for a number of connectivity options, including the following two:
•
•
Transport over DLSw+ Supported Media
Using VDLC, SNASw gains full access to the DLSw+ transport facilities, including DLSw+ transport over IP networks, DLSw+ transport over direct interfaces, and DLSw+ support of direct Frame Relay encapsulation (without using IP).
DLC Switching Support for Access to SDLC and QLLC
Through VDLC, SNASw gains access to devices connecting through SDLC and QLLC. This access allows devices connecting through SDLC and QLLC access to SNASw.
Native IP Data-Link Control (HPR/IP)
SNASw support for the EE function provides direct HPR over UDP connectivity. This support is configured for any interface that has a configured IP address. HPR/IP uses the interface IP address as the source address for IP traffic originating from this node.
Benefits
Scalable APPN Networks
With the BEX function, the number of network nodes and the amount of broadcast traffic are reduced.
IP Infrastructure Support
Limiting SNASw routers to the data center and using the BEX function eliminates SNA broadcasts from the IP network. With EE, SNA traffic is routed using the IP routing infrastructure while maintaining end-to-end SNA services.
Reduced Configuration Requirements
By eliminating NNs and using the BEX function, configuration tasks are minimized. Additionally, Cisco has enhanced its auto-configuration capability to eliminate previously required commands.
Network Design Simplicity
By placing all SNA routers in the data center, few SNA routers are required, and they can be easily configured using virtually identical configurations.
Improved Availability
By adding Cisco-unique capabilities to connect-out and distribute traffic across multiple ports, access to resources is improved and traffic can be distributed across multiple ports. Additionally, by supporting the newest HPR ARB flow control algorithm, bandwidth management for SNA traffic is improved.
Increased Management Capabilities
Two new traces, interprocess and data-link, provide an easier way to view SNASw activity. The APPN Trap MIB allows the user to notify the operator in event of a debilitating problem. Console message archiving provides better tracking of network activity. The ability to format traces in a format so that they are readable by other management products simplify network management because results are more readily available.
Architectural Compliance
Even though SNASw is easier to use and SNASw networks are easier to design, SNASw interfaces with APPN implementations on the market: ENs, NNs, and LEN nodes. It also provides full DLUR support to allow older resources to take advantage of the APPN architecture.
Restrictions
Memory Requirements
SNASw requires sufficient memory to perform properly. describes the SNASw memory requirements.
Supported Platforms
SNASw features are supported on the following platforms:
•
•
•
•
•
•
•
Supported MIBs, RFCs, and Standards
MIBs
•
•
•
For descriptions of supported MIBs and how to use MIBs, see the Cisco MIB web site on CCO at http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml.
RFCs
•
Standards
•
Configuration Tasks
To configure SNASw in your network, perform the tasks discussed in the following sections. Because of the hierarchical nature of SNASw definitions, configure SNASw in the order specified. Definition of an SNASw cpname and at least one SNASw port are required. The other tasks are optional. Depending on your network, they may need to be configured.
•
•
•
•
•
•
•
Defining a SNASw Control Point Name
A SNASw CP definition is required to use SNASw. This definition adds the fully qualified CP name for the node. The fully qualified CP name for the node is a combination of a network identifier and a CP name. The network identifier is typically configured to match the identifier configured in the SNA hosts in the network. The CP name identifies this node uniquely within the particular subnetwork.
To define a SNASw CP name, use the following command in global configuration mode:
[ip-address interface-name]Defines an SNASw CP name.
Note
Configuring a DLUS
If you plan to use DLUR to provide services for dependent LUs connected to this SNASw node, you must configure at least one primary DLUS. In addition, you can configure node-wide defaults for the DLUS and backup DLUS that this node contacts.
To specify DLUR or DLUS services for this CP name, use the following command in SNASw control point configuration mode:
Specifies the parameters related to DLUR/DLUS functionality.
Configuring DLC Support
There are several ways that SNASw enables connectivity over different interface types. In the simplest cases, using automatically configured real LAN interfaces enables default interface definitions. SNASw is also capable of connecting to virtual interfaces that are not preconfigured on the router.
Virtual Token Ring interfaces are useful for connections to a CIP/CPA in the same router and for connectivity to Frame Relay transport solutions via SRB. Multiple virtual Token Ring interfaces allow SNASw to respond to multiple MAC addresses through the same real router LAN interface. Use the following commands to configure a virtual interface:
Defining a SNASw Port
A SNASw port definition associates SNA capabilities with a specific interface that SNASw will use. Each interface that is used for SNASw communications requires an SNASw port definition statement.
Note
A port may also be associated with the VDLC or HPR/IP features. The VDLC feature enables SNASw to send and receive traffic to other Cisco IOS software features such as DLSw+. If a port is associated with a VDLC interface, that port does not take an interface name as generally required by the snasw port command.
The HPR/IP feature establishes SNASw links over IP networks. If a port is associated with an HPR/IP interface, then you must configure HPR/IP first, followed by the interface name.
To associate a port with a specific interface, use the following command in global configuration mode:
Note
Warning
Changing active SNASw interfaces might interrupt SNASw connections.
Defining a SNASw Link
In many cases, if the partner node is initiating the connection, a link definition is not necessary. A link definition is built dynamically when the partner node initiates the connection. Links typically need to be defined for upstream connectivity. Downstream devices initiate connectivity into SNASw; therefore, a link definition is not necessary to downstream devices.
In SNASw link configuration, you must associate the link with the SNASw port that it will use. For all traditional links, the snasw link command must be associated with a remote MAC address. The MAC address identifies the partner address to which SNASw attempts to establish a link. For all HPR/IP links, the command is associated with a remote IP address. The IP address identifies the partner address to which SNASw attempts to establish a link.
To define a SNASw logical link, use the following command in global configuration mode:
Defines a SNASw logical link.
Defining a SNASw Partner LU Location
The SNASw directory stores names of resources and their owners. Usually this information is learned dynamically using Locate searches. You might wish to manually define the location of specific resources. SNASw is known for its dynamic capabilities, not its need for system definition. For this reason, and for easier management, define location names only when necessary.
When a LEN node is attached to a SNASw node, all destination resources that reside on the LEN node must be defined to SNASw if the resource is to be the target of a session request. This definition enables the LEN node resources to be reached through SNASw.
To define a resource location, use the following command in global configuration mode:
Configures the location of a resource.
Note
Starting SNASw and SNASw Ports and Links
SNASw starts automatically when a CP name is configured. SNASw ports and links are also automatically started once they are configured. If stopped, they can be restarted using one of the following privileged EXEC commands:
Router# snasw startStarts SNASw.
Activates the specified SNASw link.
Activates the specified SNASw port.
Stopping SNASw and SNASw Ports and Links
Unless otherwise defined with the nostart operand, SNASw and SNASw port and link definitions are started automatically when SNASw starts. To stop SNASw or to stop SNASw ports and links when making configuration changes or when resetting the ports or links, use one of the following commands in privileged EXEC mode:
Router# snasw stopDeactivates SNASw.
Deactivates the specified SNASw link.
Deactivates the specified SNASw port.
Note
Verifying SNASw
To verify that you have SNA connectivity between the router and each host system, enter the
ping sna command, specifying the mode and the link name:ping sna -m IBMRDB STARW.BUDDHAMonitoring and Maintaining SNASw
You can monitor the status and configuration of SNASw by issuing any of the following commands in privileged EXEC mode:
Troubleshooting Tips
You can troubleshoot SNASw by issuing any of the following commands in privileged EXEC mode:
You can also troubleshoot SNASw by issuing any of the following commands in global configuration mode:
Configuration Examples
This section provides the following configuration examples:
•
•
•
•
•
•
•
•
•
SNASw over Token Ring without HPR Configuration Example
illustrates a basic SNASw link over Token Ring without HPR. In this figure, Port TOK0 is used for upstream links toward the host, and Port TOK1 is used for downstream devices connecting to SNASw. These devices are configured to connect to 4000.1234.abcd.
Figure 3 SNASw over Token Ring without HPR
The configuration for SNASw over Token Ring without HPR is as follows:
interface TokenRing0/0no ip addressno ip directed-broadcastno ip route-cacheno ip mroute-cachering-speed 16interface TokenRing0/1mac-address 4000.1234.abcdno ip addressno ip directed-broadcastno ip route-cacheno ip mroute-cachering-speed 16snasw cpname NETA.ROUTERCPsnasw dlus NETA.HOSTCMC1 backup NETA.HOSTCMC2snasw port TOK0 TokenRing0/0 conntype nohprsnasw port TOK1 TokenRing0/1 conntype nohprsnasw link HOSTCMC1 port TOK0 rmac 4000.aaaa.ccccsnasw link HOSTCMC2 port TOK0 rmac 4000.aaaa.ddddSNASw over Token Ring with HPR Configuration Example
illustrates a basic SNASw link over Token Ring with HPR support. In this figure, Port TOK0 is used for upstream links toward the host, and Port TOK1 is used for downstream devices connecting to SNASw. These devices are configured to connect to 4000.1234.abcd.
Figure 4 SNASw over Token Ring with HPR
The configuration for SNASw over Token Ring without HPR is as follows:
interface TokenRing0/0no ip addressno ip directed-broadcastno ip route-cacheno ip mroute-cachering-speed 16interface TokenRing0/1mac-address 4000.1234.abcdno ip addressno ip directed-broadcastno ip route-cacheno ip mroute-cachering-speed 16snasw cpname NETA.ROUTERCPsnasw dlus NETA.HOSTCMC1 backup NETA.HOSTCMC2snasw port TOK0 TokenRing0/0snasw port TOK1 TokenRing0/1snasw link HOSTCMC1 port TOK0 rmac 4000.aaaa.ccccsnasw link HOSTCMC2 port TOK0 rmac 4000.aaaa.ddddSNASw Connecting to a CIP over VirtualToken Ring with SRB Configuration Example
In , SNASw co-exists with CSNA CIP channel support in the same router. Two adapters are opened on the CIP, one from HOSTCMC1 on adapter 1 and one from HOSTCMC2 on adapter2. SNASw is configured to connect these two hosts through port CIP via the SRB infrastructure. In addition, SNASw has two ports configured for downstream devices to connect. Using this configuration, SNASw responds to downstream clients connecting to 4000.1234.1088 and 4000.1234.1089 through a single Token Ring interface (Token Ring 0/0). The router's hostname is used to derive an SNASw CP name, which is NETA.SNASWRT1.
Figure 5 SNASw Connecting to a CIP over Virtual Token Ring with SRB
The configuration for SNASw connecting to a CIP over virtual Token Ring with SRB is as follows:
hostname snaswrt1!source-bridge ring-group 100source-bridge ring-group 200!interface Channel2/1no ip addressno keepalivecsna E040 70csna E020 72!interface Channel2/2no ip addressno keepalivelan TokenRing 0source-bridge 101 1 100adapter 0 4000.0000.ccccadapter 1 4000.0000.dddd!interface TokenRing0/0no ip addressring-speed 16source-bridge 201 1 200source-bridge spanning!interface Virtual-TokenRing0no ip addressno ip directed-broadcastring-speed 16source-bridge 102 1 100source-bridge spanning!interface Virtual-TokenRing1mac-address 4000.1234.1088no ip addressno ip directed-broadcastring-speed 16source-bridge 202 1 200source-bridge spanning!interface Virtual-TokenRing2mac-address 4000.1234.1089no ip addressno ip directed-broadcastring-speed 16source-bridge 203 1 200!snasw cpname NETA hostnamesnasw dlus NETA.HOSTCMC1 backup NETA.HOSTCMC2snasw port CIP Virtual-TokenRing0snasw port DOWNSTRM Virtual-TokenRing1 conntype no-hprsnasw port DOWNSTRM Virtual-TokenRing2 conntype no-hprsnasw link HOSTCMC1 port CIP rmac 4000.0000.ccccsnasw link HOSTCMC2 port CIP rmac 4000.0000.ddddSNASw over HPR/IP Configuration Example
illustrates a basic SNASw link over HPR/IP on the upstream connections to the host. The downstream devices connect through Token Ring 0/0.
Figure 6 SNASw over HPR/IP
The configuration for SNASw over HPR/IP is as follows:
interface Ethernet1/0ip address 172.18.49.28 255.255.255.0no ip directed-broadcastno ip route-cacheno ip mroute-cache!interface TokenRing0/0mac-address 4000.1234.1088no ip addressno ip directed-broadcastno ip route-cacheno ip mroute-cachering-speed 16!snasw cpname NETA.ROUTERCPsnasw dlus NETA.HOSTCMC1 backup NETA.CMCHOST2snasw port HPRIP hpr-ip Ethernet1/0snasw port TOK0 TokenRing0/0snasw link HOSTCMC1 port HPRIP ip-dest 172.18.51.1snasw link HOSTCMC2 port HPRIP ip-dest 172.18.51.2SNASw using Local Switching with QLLC Configuration Example
illustrates a basic SNASw link using local switching with QLLC.
Figure 7 SNASw using Local Switching with QLLC
Note
The configuration for SNASw link using Local Switching with QLLC is as follows:
!source-bridge ring-group 70dlsw local-peer!interface Serial4/0no ip addressno ip directed-broadcastencapsulation x25no ip mroute-cacheno keepaliveqllc accept-all-callsclockrate 19200qllc dlsw vmacaddr 4000.1111.1111 partner 4000.2222.2222!snasw cpname NETA.ROUTERCPsnasw port VDLCP vdlc 70 mac 4000.2222.2222 conntype nohprSNASw using Local Switching with SDLC Configuration Example
illustrates a basic SNASw link using local switching with SDLC.
Figure 8 SNASw using Local Switching with SDLC
Note
The configuration for SNASw link using local switching with SDLC is as follows:
!source-bridge ring-group 1689dlsw local-peer!interface Serial1no ip addressno ip directed-broadcastencapsulation sdlcno ip route-cacheno ip mroute-cacheno keepaliveclockrate 9600sdlc role primarysdlc vmac 4000.3174.0000sdlc address C2sdlc sdlc-largest-frame C2 521sdlc xid C2 05DABBBAsdlc partner 4000.4500.00f0 C2sdlc dlsw C2!snasw cpname NETA.ROUTERCOsnasw port SDLC vdlc 1689 mac 4000.4500.00f0SNASw with Ethernet LAN Emulation over ATM Configuration Example
In , downstream stations connect in SNASw over ATM (Ethernet LANE). Upstream connectivity is achieved using DLSw+ for connections to the host systems. Downstream devices connect to the standby MAC address on the ATM sub-interface.
Figure 9 SNASw with Ethernet LANE over ATM
The configuration for SNASw with Ethernet LANE over ATM is as follows:
!source-bridge ring-group 111dlsw local-peer peer-id 10.56.56.1 keepalive 10 promiscuousdlsw remote-peer 0 tcp 10.56.56.2!interface ATM2/0mtu 1500no ip addressno ip directed-broadcastatm clock INTERNALatm pvc 1 0 5 qsaalatm pvc 2 0 16 ilmiatm pvc 60 1 36 aal5nlpidno atm ilmi-keepalive!interface ATM2/0.1 multipointno ip directed-broadcastlane client ethernet REDno cdp enable!interface ATM2/0.2 multipointip address 10.10.50.60 255.255.255.0no ip redirectsno ip directed-broadcastlane client ethernet BLUEno cdp enablestandby 1 priority 200 preemptstandby 1 authentication xxxxstandby 1 mac-address 000b.e291.0000standby 1 ip 10.10.50.70!interface Serial3/1ip address 10.56.56.1 255.255.255.0no ip directed-broadcastencapsulation pppno keepaliveno fair-queueclockrate 56000!snasw cpname NETA.ROUTERCPsnasw dlus NETA.SJMVS3 backup NETA.HOSTCMC2snasw port ATM202 ATM2/0.2 conntype nohprsnasw port DLSWP vdlc 111 mac 4000.0189.0016 conntype nohprsnasw link HOSTCMC1 port DLSWP rmac 4000.aaaa.ccccsnasw link HOSTCMC2 port DLSWP rmac 4000.aaaa.dddd!SNASw with SRB Frame Relay (Frame Relay BAN Support) Configuration Example
illustrates how to combine SNASw and SRB over Frame Relay functionality to provide native RFC 1490 connectivity over Frame Relay BAN. The host is configured to respond to 4000.aaaa.cccc through the Frame Relay connection over Serial1. Downstream would be configured to connect into VirtualTokenRing0.
Figure 10 SNASw with SRB Frame Relay (Frame Relay BAN Support)
The configuration for SNASw with SRB Frame Relay (Frame Relay BAN Support) is as follows:
source-bridge ring-group 100source-bridge ring-group 200!interface TokenRing0no ip addressno ip directed-broadcastring-speed 16source-bridge 202 1 200!interface Virtual-TokenRing0mac-address 4000.1234.1001no ip addressno ip directed-broadcastring-speed 16source-bridge 201 1 200!interface Serial1encapsulation frame-relay!interface serial 1.1 point-to-pointframe-relay interface-dlci 30 ietfsource-bridge 101 1 100!interface Virtual-TokenRing1mac-address 4000.1111.2222no ip addressno ip directed-broadcastring-speed 16source-bridge 102 1 100source-bridge spanning!snasw cpname NETA.ROUTERCPsnasw port frame virtual tokenring 1 conntype nohprsnasw link HOSTFRAM port FRAME rmac 4000.aaaa.ccccOn the CIP router, configure the following:
source-bridge ring-group 300interface serial 1/0encapsulation frame-relay!interface serial 1/0.1 point-to-pointframe-relay interface 30 ieftsource-bridge 101 1 300!interface channel 2/1no ip-addressno keep alivecsna E040 70!interface serial channel 2/2no ip-addressno keep alivelan tokenring 0source-bridge 301 1 300adapter 0 4000.aaaa.ccccSNASw with FRAS Host (Downstream Frame Relay BNN Support) Configuration Example
illustrates how to connect a downstream Frame Relay BNN device (FRAD) over native RFC 1490 in SNASw.
Figure 11 SNASw with FRAS Host (Downstream Frame Relay BNN Support)
Note
The configuration SNASw with FRAS Host (Downstream Frame Relay BNN Support) is as follows:
source-bridge ring-group 200interface serial 1/2no ip-addressencapsulation frame-relay letfframe-relay map llc2 17!interface virtual-tokenring 0mac-address 4000.1234.1001ring-speed 16source-bridge 201 1 200!interface virtual-tokenring 1ring-speed 16source-bridge 202 1 200fras-host bnn serial 1/2 fr-lsap 04 umac 4000.1234.2002 hmac 4000.1234.1001Command Reference
This section documents the new commands that configure the SNASw feature.
•
In Cisco IOS Release 12.0(1)T or later, you can search and filter the output for show and more commands. This functionality is useful when you need to sort through large amounts of output, or if you want to exclude output that you do not need to see.
To use this functionality, enter a show or more command followed by the "pipe" character (|), one of the keywords begin, include, or exclude, and an expression that you want to search or filter on:
command | {begin | include | exclude} regular-expression
Following is an example of the show atm vc command in which you want the command output to begin with the first line where the expression "PeakRate" appears:
show atm vc | begin PeakRate
For more information on the search and filter functionality, refer to the Cisco IOS Release 12.0(1)T feature module titled CLI String Search.
ping sna
To initiate an APPC session with a named partner node and to run the APING transaction program to check network integrity and timing characteristics, use the ping sna privileged EXEC command.
ping sna [-1] [-c consecutive packets] [-i number-iterations] [-m mode] [-n] [-r] [-s size]
[-t tpname] [-u userid] destinationSyntax Description
Defaults
No default behaviors or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The ping sna command requires the destination to support the APING transaction program for the ping to succeed.
Examples
The following is an example of the ping sna command contact the destination NETA.CP001:
ping sna NETA.CP001Related Commands
show snasw class-of-service
To display the COS definitions predefined to SNASw, use the show snasw class-of-service command.
show snasw class-of-service [brief | detail]
Syntax Description
Defaults
No default behaviors or values.
Command History
Examples
The following is an example of the show snasw class-of-service command:
show snasw class-of-serviceThis command provides the following output:
Number of class of service definitions 7SNA Classes of ServiceName Trans. Pri. Node Rows TG Rows-------- ----------- --------- -------1> #BATCH Low 8 82> #INTER High 8 83> CPSVCMG Network 8 84> #BATCHSC Low 8 85> #CONNECT Medium 8 86> #INTERSC High 8 87> SNASVCMG Network 8 8r2612a52#show snasw class-of-service detailNumber of class of service definitions 71>Class of service name #BATCHTransmission priority LowNumber of node rows 8Number of TG rows 81.1>Node row weight 5Congestion min NoCongestion max NoRoute additional resistance min 0Route additional resistance max 31Related Commands
show snasw connection-network
To display the connection networks (virtual nodes) currently known to SNASw, use the show snasw connection-network command.
show snasw connection-network [brief | detail]
Syntax Description
Defaults
No default behaviors or values.
Command History
Examples
The following is an example of the show snasw connection-network command:
show snasw connection-networkThis command provides the following output:
Connection network definitions 1SNA Connection NetworksResource Name Attached Ports Port Name(s)----------------- -------------- --------------------------------1> CISCO.VN 1 TR0r3620a52#show snasw connection-network detailConnection network definitions 11>Connection network name CISCO.VNEffective capacity 16 MbpsCost per connect time 0Cost per byte 0Propagation delay 384 microsecondsUser defined parameter 1 128User defined parameter 2 128User defined parameter 3 128Security Nonsecure1.1>Port name TR0Related Commands
show snasw directory
To display the SNASw directory entries, use the show snasw directory command.
show snasw directory [name resourcenamefilter] [brief | detail]
Syntax Description
Defaults
No default behaviors or values.
Command History
Examples
The following is an example of the show snasw directory command:
show snasw directoryThis command provides the following output:
Total Directory Entries 2SNA Directory EntriesResource Name Owning CP Name NN Server Entry Type----------------- ----------------- ----------------- ----------1> CISCO.A CISCO.A CISCO.B Registry2> CISCO.B CISCO.B CISCO.B Homer2612a52#show snasw directory detailTotal Directory Entries 21>Resource name CISCO.ANN server name CISCO.BEntry type RegistryLocation Local to this domainResource owner's CP name CISCO.AApparent resource owner's CP nameWildcard Explicit2>Resource name CISCO.BNN server name CISCO.BEntry type HomeLocation Local to this nodeResource owner's CP name CISCO.BApparent resource owner's CP nameWildcard ExplicitRelated Commands
show snasw dlctrace
To display the captured DLC trace information to the console, use the show snasw dlctrace command.
show snasw dlctrace [all | last number-records | next number-records] [brief | detail]
[filter filter-string] [id recordid]Syntax Description
Defaults
If id recordid is specified, next is the default parameter; if not, last is the default parameter.
Command History
Examples
The following is an example of the show snasw dlctrace command:
show snasw dlctrace id 2467 next S/B next 20This command provides the following output:
DLC Trace Output2467 LINKT In sz:43 HPR +Rsp IPM slctd nws:00072468 LINKT In sz:212 HPR +Rsp IPM slctd nws:00072469 LINKT In sz:52 HPR CP CAPABILITIES2470 LINKT In sz:221 HPR CP CAPABILITIES2471 LINKT Out sz:282 HPR MIS2472 LINKT Out sz:43 HPR +Rsp IPM slctd nws:00072473 LINKT In sz:154 HPR Rq Bind CISCO.B CISCO.A2474 LINKT In sz:323 HPR Rq Bind CISCO.B CISCO.A2475 LINKT Out sz:361 HPR MIS2476 LINKT Out sz:132 HPR +Rsp Bind2477 LINKT In sz:102 HPR fmh5 CP CAPABILITIES2478 LINKT In sz:271 HPR fmh5 CP CAPABILITIES2479 LINKT Out sz:282 HPR MIS2480 LINKT Out sz:43 HPR +Rsp IPM slctd nws:00072481 LINKT Out sz:291 HPR MIS2482 LINKT Out sz:52 HPR CP CAPABILITIES2483 LINKT In sz:43 HPR +Rsp IPM slctd nws:00072484 LINKT In sz:212 HPR +Rsp IPM slctd nws:00072485 LINKT Out sz:45 HPR2486 LINKT In sz:45 HPRr3620a52#show snasw dlctrace detailDLC Trace Output2486 LINKT In sz:45 HPR10:08:36.14, 14 March 19930000 C60080FF 00000000 00010000 00000400 *F...............*0010 0A000000 00000001 7E050E00 00000000 *........=.......*0020 01000001 7E000000 00000000 00 *....=........ *Related Commands
Traces frames arriving and leaving SNASw.
Filters frames captured by the snasw dcltrace or debug snasw dlc debug commands.
show snasw dlus
To display the SNASw DLUS objects, use the show snasw dlus command.
show snasw dlus [brief | detail]
Syntax Description
Defaults
No default behaviors or values.
Command History
Examples
The following is an example of the show snasw dlus command:
show snasw dlusThis command provides the following output:
Number of Dependent LU Servers2SNA Dependent LU ServersDLUS Name Default? Backup? Pipe State PUs----------------- -------- ------- ---------------- -------1> NETA.SJMVS3 Yes No Active 12> NETA.SJMVS4 No Yes Inactive 0dlur2#show snas dlus detailNumber of Dependent LU Servers21>DLUS name NETA.SJMVS3Is this the default DLUS YesIs this the backup default DLUS NoPipe state ActiveNumber of active PUs 1DLUS pipe statistics:REQACTPUs sent 1REQACTPU responses received 1ACTPUs received 1ACTPU responses sent 1DACTPUs received 0DACTPU responses sent 0REQDACTPUs sent 0REQDACTPU responses received 0ACTLUs received 16ACTLU responses sent 1DACTLUs received 0DACTLU responses sent 0SSCP-PU MUs sent 0SSCP-PU MUs received 0SSCP-LU MUs sent 19SSCP-LU MUs received 3Related Commands
show snasw ipstrace
To display the interprocess signal trace on the router console, use the show snasw ipstrace command.
show snasw ipstrace [all | next number-records | last number-records] [filter filter-string]
[id recordid]Syntax Description
Defaults
No default behaviors or values.
Command History
Examples
The following is an example of the show snasw ipstrace command:
show snasw ipstraceThis command provides the following output:
423452 : DLC_UI_MU : PC(2350000) -> DLC(2300000) Q 203/14/1993 10:11:36.1800000000 00000000 61BB3F50 00800000 00000000 00000000 00000000 00000000000000FF 000000FF 00000000 00000000 05010000 000000FF 50130000 002D00D202340000 03000000 00000000 61BB3FB0 00140050 0000017E 000100FF 0000000000000000 01000000 00000000 00000000 0000017E 00000000 00000000 0000000000000000 00000000 00000000 00000000 00000000 00000000 00000000 0000000000000000 00000000 00000000 00000000 00000000 00000000 00000000 0000000000000000 00000000 00000000 00000000 00C6C600 80FF0000 00000001 0000000004000A00 00000000 00017E05 0E000000 01000100 00017E00 00000000 00000000Related Commands
Sets up a trace buffer and begins tracing IPS trace elements
Filters interprocess signal trace elements being traced via the snasw ipstrace or debug snasw ips commands.
show snasw link
To display the SNASw link objects, use the show snasw link command.
show snasw link [brief | detail] [cpname cpnamefilter] [name linknamefilter]
[port portnamefilter] [rmac macfilter] [xid xidfilter]Syntax Description
Defaults
No default behaviors or values.
Command History
Examples
The following is an example of the show snasw link command:
show snasw linkThis command provides the following output:
Number of links 1SNA Links HPRLink Name State Port Name Adjacent CP Name Node Type Sess Sup--------- ------- --------- ---------------- ------------ ---- ---1> LINKT Active TR0 CISCO.B Network Node 0 Yesr3620a52#show snasw link detailNumber of links 11>Link name LINKTPort name TR0DLC type Token-ringDestination DLC Address 000B.1AA4.9280.04Link state ActiveLink substate ActiveNumber of active sessions traversing link 0Adjacent Node Id X'FFF00000'Max send frame data (BTU) size 4400Adjacent node CP name CISCO.BAdjacent node type Network NodeCP-CP session support YesLink station role SecondaryTransmission group number 21Limited resource NoEffective capacity 16 MbpsCost per connect time 0Cost per byte 0Propagation delay 384 microsecondsUser defined parameter 1 128User defined parameter 2 128User defined parameter 3 128Security NonsecureRouting Information FieldPrimary DLUS NameBackup DLUS NameDownstream PU NameRetry link station YesDynamic link station NoAdjacent node is a migration node NoLink station statistics:Total XID bytes sent 466Total XID bytes received 344Total XID frames sent 5Total XID frames received 4Total data bytes sent 752Total data bytes received 685Total data frames sent 8Total data frames received 9Total session control frames sent 0Total session control frames received 0Total number of successful XID exchanges 1Total number of unsuccessful XID exchanges 0Related Commands
show snasw lu
To display the SNASw dependent LUs, use the show snasw lu command.
show snasw lu [brief | detail] [name luname] [pu puname]
Syntax Description
Defaults
No default behaviors or values.
Command History
Examples
The following is an example of the show snasw lu command:
show snasw luThis command provides the following output:
Number of DLUR LUs 1SNA DLUR LUsLU Name PU Name DLUS PLU Name-------- -------- ----------------- -----------------1> LL910101 PL9101 NETA.SJMVS3 NETA.ITPECHOSdlur2#show snasw lu detailNumber of DLUR LUs 11>LU name LL910101PU name PL9101DLUS name NETA.SJMVS3Primary LU name NETA.ITPECHOSLU location DownstreamRelated Commands
Displays the SNASw PUs that require or request SSCP-PU services.
Displays the SNASw DLUS objects.
show snasw mode
To display modes predefined to SNASw, use the show snasw mode command.
show snasw mode
Syntax Description
There are no keywords or arguments for this command.
Defaults
No default behaviors or values.
Command History
Examples
The following is an example of the show snasw mode command:
show snasw modeThis command provides the following output:
Number of modes 8SNA ModesName Associated COS--------- --------------1> #BATCH #BATCH2> #INTER #INTER3> CPSVCMG CPSVCMG4> #CONNECT5> #BATCHSC #BATCHSC6> #INTERSC #INTERSC7> CPSVRMGR SNASVCMG8> SNASVCMG SNASVCMGRelated Commands
show snasw node
To display details and statistics of the SNASw operation, use the show snasw node command.
show snasw node
Syntax Description
There are no keywords or arguments for this command.
Defaults
No default behaviors or values.
Command History
Examples
The following is an example of the show snasw node command:
show snasw nodeThis command provides the following output:
Node type Branch Network NodeNode name CISCO.ACP alias CISCONode ID X'FFF00000'Time active 12 mins, 57 secsDefined LS good XID exchanges 1Defined LS bad XID exchanges 0Dynamic LS good XID exchanges 0Dynamic LS bad XID exchanges 0Number of active ISR sessions 0DLUR release level 1Branch extender architecture version 1Mode to COS mapping supported NoMS includes Multiple Domain Support YesMDS send alert queue size 10Maximum locates 10000Directory cache size 10000Maximum directory entries (0 is unlimited) 0Locate timeout in seconds (0 is no timeout) 0COS cache size 8Topology database routing tree cache size 8Topology database routing tree cache use limit 1Maximum nodes stored in database (0 unlimited) 0Maximum TGs stored in database (0 unlimited) 0Maximum allowed ISR sessions 22000Maximum receive RU size for ISR sessions 61440Maximum receive pacing window 7Storing endpoint RSCVs for debug YesStoring ISR RSCVs for debug NoStoring DLUR RSCVs for debug NoDLUR support YesHPR support YesRelated Commands
show snasw pdlog
To display entries in the cyclical problem determination log to the console, use the show snasw pdlog command.
show snasw pdlog [brief | detail] [all | next number-records| last number-records]
[filter filterstring] [id recordid]Syntax Description
Defaults
No default behaviors or values.
Command History
Examples
The following is an example of the show snasw pdlog command:
show snasw pdlogThis command provides the following output:
Problem Determination Log Output**** 00000014 - AUDIT 512:727 (0) ****CP-CP sessions establishedAdjacent CP name = CISCO.A1015 compliant = 01Topology awareness of CP-CP sessions support = 01CP Capabilities :000C12C1 00000000 82844000>From ../dcl/nssrcctp.c 589 :at 0:10:24, 1 March 93Related Commands
Controls logging of messages to the console and the SNA problem determination log cyclic buffer.
show snasw port
To display the SNASw port objects, use the .show snasw port command.
show snasw port [brief | detail] [name portnamefilter]
Syntax Description
Defaults
No default behaviors or values.
Command History
Examples
The following is an example of the show snasw port command:
show snasw portThis command provides the following output:
Number of ports 3SNA PortsName State SAP HPR-SAP Interface-------- -------- --- ------- ---------------------1> ETH0 Active x04 xC8 Ethernet0/02> SER1 Active xC8 Serial0/03> TR0 Active x04 xC8 TokenRing0/0r3620a52#show snasw port detailNumber of ports 31>Port name ETH0Interface name Ethernet0/0DLC name ETH0Port state ActiveSAP X'04'HPR SAP X'C8'Port type Shared Access Transport FacilityPort number 0Link station role NegotiableLimited resource NoMax send frame data (BTU) size 1436Maximum receive BTU size 1436Effective capacity 16 MbpsCost per connect time 0Cost per byte 0Propagation delay 384 microsecondsUser defined parameter 1 128User defined parameter 2 128User defined parameter 3 128Security NonsecureTotal available link stations 3000Number reserved for inbound link stations 0Number reserved for outbound link stations 0HPR support NoHPR requires link level error recovery NoRetry link stations YesMaximum activation attempts 0Implicit links are uplink to End Nodes NoActivation XID exchange limit 9Non-activation XID exchange limit 5Target pacing window size 7Related Commands
show snasw pu
To display the SNASw PUs that require or request SSCP-PU services, use the show snasw pu command.
show snasw pu [brief | detail] [dlus dlusfilter] [name punamefilter]
Syntax Description
Defaults
No default behaviors or values.
Command History
Examples
The following is an example of the show snasw pu command:
show snasw puThis command provides the following output:
Number of DLUR PUs 1SNA DLUR PUsPU Name PU ID State Defined DLUS Current DLUS-------- -------- -------- ----------------- -----------------1> PL9101 19103001 Active NETA.SJMVS3dlur2#show snasw pu detailNumber of DLUR PUs 11>PU name PL9101Define DLUS nameBackup DLUS nameActive DLUS name NETA.SJMVS3PU ID (IDBLK/IDNUM) X'19103001'PU location DownstreamPU status ActiveDLUS session state ActiveAutomatic Network Shutdown support StopDLUS retry timeout (seconds) 0DLUS retry limit 0DLUS pipe PCID X'FC0B862E4B1CE8FB'DLUS pipe CP Name NETA.DLUR2Related Commands
show snasw rtp
To display the SNASw RTP connections, use the show snasw rtp command.
show snasw rtp [brief | detail] [class-of-service cosname] [name connectionnamefilter]
[tcid tcidconnection]Syntax Description
Defaults
No default behaviors or values.
Command History
Examples
The following is an example of the show snasw rtp command:
show snasw rtpThis command provides the following output:
Number of RTP connections 1SNA RTP ConnectionsLocal TCID (hex) Remote TCID (hex) Remote CP Name COS---------------- ----------------- ----------------- --------1> 0000000001000000 0000000001000000 CISCO.B CPSVCMGr3620a52#show snasw rtp detailNumber of RTP connections 11>Local NCEID X'4052303030303031'Local TCID X'0000000001000000'Remote TCID X'0000000001000000'Remote CP name CISCO.BClass of service name CPSVCMGLiveness timer 180Short request timer 704Number of short request timeouts 0Total bytes sent 484Total bytes received 484Total bytes resent 0Total bytes discarded 0Total packets sent 24Total packets received 25Total packets resent 0Total packets discarded 0Total Session Connector frames sent 2Total Session Connector frames received 2Number of invalid SNA frames received 0Number of gaps detected 0Minimum send rate 1597Current send rate 1597Maximum send rate 1597Minimum receive rate 0Current receive rate 0Maximum receive rate 0Burst size 8192Smoothed round trip delay time 352Last round trip delay time 8Number of active sessions 2Link name of first hop LINKTPerforming ISR boundary function NoRTP connection type CP-CP sessionRSCV Length 18Route CISCO.A<-tg21-> CISCO.BRelated Commands
show snasw session
To display the SNASw session objects, use the show snasw session command.
show snasw session [local | dlur | intermediate] [name sessionnamefilter] [pcid pcidfilter]
[brief | detail | intermediate]Syntax Description
Defaults
No default behaviors or values.
Command History
Examples
The following is an example of the show snasw session command:
show snasw sessionThis command provides the following output:
Number of local endpoint sessions 4SNA Local Endpoint SessionsPCID (hex) Partner LU Name Link Name Mode COS---------------- ----------------- --------- -------- -------1> F4276146FE1472AB CISCO.C @I000003 CPSVCMG CPSVCMG2> F42754959A918058 CISCO.C @I000003 CPSVCMG CPSVCMG3> F4276146FE1472AA CISCO.A @R000002 CPSVCMG CPSVCMG4> F4276DF74485118B CISCO.A @R000002 CPSVCMG CPSVCMGNumber of intermediate sessions 2SNA Intermediate SessionsPCID (hex) Primary LU Name Secondary LU Name Mode COS---------------- ----------------- ----------------- -------- -------1> F42754959A918059 CISCO.C CISCO.A SNASVCMG SNASVCMG2> F42754959A91805A CISCO.C CISCO.A #INTER #INTERNumber of intermediate DLUR sessions 0SNA DLUR Assisted Intermediate SessionsPCID (hex) Primary LU Name Secondary LU Name Mode COS---------------- ----------------- ----------------- -------- -------r2612a52#show snasw session detailNumber of local endpoint sessions 41>Partner LU name CISCO.CMode name CPSVCMGClass of service name CPSVCMGTransmission priority NetworkCarried over a limited resource NoPolarity PrimaryContention CONWINNERSSCP ID received in ACTPU X'000000000000'Session timeout period (ms) 0Outbound LFSID (SIDH,SIDL,ODAI) X'02',X'00',B'0'Procedure correlator ID (PCID) X'F4276146FE1472AB'PCID generator CP name CISCO.BFID2 Session ID X'F4276146FE1472AB'Link name @I000003Session statistics:Maximum send RU size 1152Maximum receive RU size 1152Total data frames sent 3Total data frames received 1Total FMD data frames sent 3Total FMD data frames received 1Total bytes sent 511Total bytes received 15Max send pacing window 7Max receive pacing window 7Current send pacing window 7Current receive pacing window 7Related Commands
show snasw statistics
To display the SNASw node-wide information, use the show snasw statistics command.
show snasw statistics
Syntax Description
There are no keywords or arguments for this command.
Defaults
No default behaviors or values.
Command History
Examples
The following is an example of the show snasw statistics command:
show snasw statisticsThis command provides the following output:
SNASw Subsystem Uptime 3 hrs, 19 mins, 36 secsDirectory Statistics:Maximum number of cache entries 10000Current number of cache entries 0Current number of home entries 2Current number of registry entries 4Total number of entries in directory 6Total cache hits 0Total cache misses 0Number of directed locates sent 2Number of directed locates returned not found 0Number of directed locates received 0Number of broadcast locates sent 0Number of broadcast locates returned not found 0Number of broadcast locates received 0Number of locates outstanding 0Toplogy Statistics:Maximum number of nodes 0Current number of nodes 4Total number of received TDUs 0Total number of sent TDUs 0Total received TDUs with lower RSN 0Total received TDUs with equal RSN 0Total received TDUs with higher RSN 0Total received TDUs with higher odd value RSN 0Total node state changes requiring TDUs 0Total database inconsistencies detected 0Total number of timer based TDUs generated 0Total number of node records purged 0Total received TG updates with lower RSN 0Total received TG updates with equal RSN 0Total received TG updates with higher RSN 0Total received TG updates with higher odd RSN 0Total TG state changes requiring TG updates 5Total TG database inconsistencies detected 0Total number of timer TG updates generated 0Total number of TG records purged 0Total number of routes calculated 2Total number of routes rejected 0Total number of cache hits in route calculation 0Total number of cache misses in rte calculation 7Total number of TDU wars detected 0Number of processes 23CPU/Memory usage per SNA Switch processProcess Name CPU Time (ms) Memory Used (bytes)----------------------------------- ------------- -------------------1> NOF API 20 202> N-Base allocated memory 0 794843> Buffer Manager (BM) 12 2324> Node Operator Facility (NOF) 152 131885> Address Space Manager (ASM) 28 12966> Address Space (AS) 24 07> Session Services (SS) 36 16768> Directory Services (DS) 92 5500369> Configuration Services (CS) 48 914810> Management Services (MS) 4 25211> Multiple Domain Support (MDS) 0 379212> Topology & Routing Services (TRS) 24 2236813> Session Connector Manager (SCM) 12 223214> Session Connector (SCO) 0 123215> Session Manager (SM) 56 1341616> Resource Manager (RM) 64 017> Presentation Services (PS) 68 018> Half Session (HS) 29 019> Path Control (PC) 188 5071220> Data Link Control (DLC) 112 14421> Dependent LU Requester (DR) 12 703222> High Performance Routing (HPR) 12 363223> Rapid Transport Protocol (RTP) 116 18460Related Commands
show snasw summary-ipstrace
To display the continuously running "footprint" summary interprocess signal trace on the router console, use the show snasw summary-ipstrace command.
show snasw summary-ipstrace [all | next number-records | last number-records] [id recordid]
[filter filter-string]Syntax Description
Defaults
No default behaviors or values.
Command History
Examples
The following is an example of the show snasw summary-ipstrace command:
show snasw summary-ipstraceThis command provides the following output:
IPS Trace Output433414 : VERB_SIGNAL : SCM(20E0000) -> TRS(20D0000) Q 1433415 : VERB_SIGNAL : --(0) -> TRS(20D0000) Q 1433416 : VERB_SIGNAL : TRS(20D0000) -> SS(2080000) Q 1433417 : VERB_SIGNAL : --(0) -> SS(2080000) Q 1433418 : VERB_SIGNAL : SS(2080000) -> CS(20A0000) Q 2433419 : VERB_SIGNAL : --(0) -> CS(20A0000) Q 2433420 : VERB_SIGNAL : CS(20A0000) -> --(2040000) Q 1433421 : VERB_SIGNAL : --(0) -> --(2040000) Q 1433422 : VERB_SIGNAL : --(0) -> NOF(2050000) Q 80433423 : VERB_SIGNAL : --(0) -> NOF(2050000) Q 80433424 : VERB_SIGNAL : NOF(2050000) -> DS(2090000) Q 1433425 : VERB_SIGNAL : --(0) -> DS(2090000) Q 1433426 : VERB_SIGNAL : DS(2090000) -> --(2040000) Q 1433427 : VERB_SIGNAL : --(0) -> --(2040000) Q 1433428 : VERB_SIGNAL : --(0) -> NOF(2050000) Q 80433429 : VERB_SIGNAL : --(0) -> NOF(2050000) Q 80433430 : VERB_SIGNAL : NOF(2050000) -> TRS(20D0000) Q 1433431 : VERB_SIGNAL : --(0) -> TRS(20D0000) Q 1433432 : VERB_SIGNAL : TRS(20D0000) -> --(2040000) Q 1433433 : VERB_SIGNAL : --(0) -> --(2040000) Q 1Related Commands
show snasw topology
To display the SNASw topology records, use the show snasw topology command.
show snasw topology [name cpnamefilter] [brief | detail]
Syntax Description
Defaults
No default behaviors or values.
Command History
Examples
The following is an example of the show snasw topology command:
show snasw topologyThis command provides the following output:
Number of topology entries 3SNA Topology EntriesDest. Node Name Type TG# TG Type TG Status----------------- ---- --- ---------------- ---------------------1> CISCO.A EN 21 Downlink to BrNN CP-CP sessions active2> CISCO.C EN 21 Downlink to BrNN CP-CP sessions active3> CISCO.VN VRN 1 Neutral link Activer2612a52#show snasw topology detailNumber of topology entries 31>Destination node name CISCO.ADestination node type End NodeTransmission Group Number 21Destination addressResource Sequence Number 6TG status CP-CP sessions activeActive CP-CP sessions for this TG YesIs this a branch TG YesBranch link type Downlink to BrNNEffective capacity 16 MbpsCost per connect time 0Cost per byte 0Propagation delay 384 microsecondsUser defined parameter 1 128User defined parameter 2 128User defined parameter 3 128Security NonsecureRelated Commands
snasw cpname
To define a control point name for SNASw, use the snasw cpname global configuration command. Use the no form of this command to deactivate SNASw and remove the control point definition.
snasw cpname netid.name | netid [hostname] [ip-address interface-name]
no snasw cpname
Syntax Description
Defaults
No default behavior or values.
Command Modes
Global configuration
Command History
Usage Guidelines
You can also deactivate SNASw without removing the snasw cpname definition using the snasw stop privileged EXEC command.
Coding of a cpname is required for SNASw. Only one snasw cpname command is allowed at a time. The snasw cpname command cannot be changed without first deleting the previous definition using the no form of the command. If SNASw is active, the no form deactivates it. If it is inactive, snasw cpname activates it.
Examples
The following are examples of how to configure the snasw cpname command:
snasw cpname NETA.BRANCH5snasw cpname NETBANK2.DLUR0005snasw cpname NETWORKA hostnamesnasw cpname NETA.CP ip-address Loopback0Related Commands
Starts SNASw via the privileged EXEC command.
Shuts down SNASw via the privileged EXEC command.
snasw dlcfilter
To filter frames being captured, use the snasw dlcfilter global configuration command. Use the no form of this command to disable the filtering of frames arriving and leaving SNASw.
snasw dlcfilter [link linkname [session session address]] [port portname]
[rmac mac-address-value [session session address]] [rtp rtpname]
[[type] [cls] [hpr-cntl] [hpr-data] [isr] [xid]]no snasw dlcfilter
Syntax Description
Defaults
This command defaults to no filtering, and all frames are traced.
Command Modes
Global configuration
Command History
Usage Guidelines
The snasw dlcfilter command is typically used to limit the output of the snasw dlctrace command to a manageable amount of trace data. Running the snasw dlctrace consumes CPU and memory. Using the snasw dlctrace command limits the CPU and memory consumption to only the frames that are targeted for tracing.
Examples
The following are examples of how to configure the snasw dlcfilter command:
snasw dlcfilter link cmc1linksnasw dlcfilter rmac 4001.1234.1001snasw dlcfilter type xidRelated Commands
Traces frames arriving and leaving SNASw.
Displays real-time DLC trace data to the console.
Dumps trace and problem determination logs to a file server.
snasw dlctrace
To trace frames arriving and leaving SNASw, use the snasw dlctrace global configuration command. Use the no form of this command to deactivate the capture of frame data and frees the storage buffer used to capture the data.
snasw dlctrace [buffer-size buffer-size-value] [file filename]
[frame-size frame-size-value] [format brief | detail | analyzer]no snasw dlctrace
Syntax Description
Defaults
Tracing is off.
Command Modes
Global configuration
Command History
Usage Guidelines
Use the snasw dlctrace command when directed by service personnel or when analysis of frame data entering and leaving SNASw is necessary.
The snasw dlctrace command copies frames into a memory buffer, which can degrade router performance. Therefore, care should be taken when using this command. When issued on a highly used system, the snasw dlcfilter command should be used in conjunction with the snasw dlctrace command to limit the output of the trace.
Use the snasw dump command to dump the trace data to a file server or the show snasw dlctrace command to display captured frames on the console.
Examples
The following are examples of how to configure the snasw dlctrace command:
snasw dlctracesnasw dlctrace buffer-size 5000 file tftp://171.69.120.21/dlcfiles/dlc/trcRelated Commands
Filters frames being captured using the snasw dlctrace or debug snasw dlc commands.
Dumps the trace to a file server.
Displays the captured DLC trace information on the console.
snasw dlus
To specify parameters related to DLUR/DLUS functionality, use the snasw dlus global configuration command. Use the no form of this command to remove the data specified in a previous snasw dlus command.
snasw dlus primary-dlus-name [backup backup-dlus-name] [prefer-active]
[retry interval | count]no snasw dlus
Syntax Description
Defaults
If the prefer-active argument is not specified, each connected downstream station will attempt to connect to the primary DLUS or backup DLUS until the device receives DLUS services.
Command Modes
Global configuration
Command History
Usage Guidelines
Only one snasw dlus command is allowed at a time. The snasw dlus command cannot be changed without first deleting the previous definition using the no form of the command. DLUS configuration is required if dependent LUs are to be supported by SNASw.
Examples
The following are examples of how to configure the snasw dlus command:
snasw dlus NETA.HOST1 backup NETA.HOST2snasw dlus NETBANK2.CDERM34 prefer-active retry 30 3Related Commands
snasw dump
To copy problem determination logs and traces from internal buffers to an external file server, use the snasw dump privileged EXEC command.
snasw dump all | dlctrace | ipstrace | summary-ipstrace | pdlog
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The snasw dump command is used for gathering trace files for diagnosis by Cisco personnel or onsite trace analysis.
Examples
The following are examples of how to configure the snasw dump command:
snasw dump allsnasw dump dlctraceRelated Commands
snasw event
To indicate which normal events are logged to the console, use the snasw event global configuration command. Use the no form of this command to return the events to their default state.
snasw event [cpcp] [defined-ls] [dlc] [implicit-ls] [port]
no snasw event
Syntax Description
Defaults
The following events are sent to the pdlog/console:
•
•
Command Modes
Global configuration
Command History
Examples
The following example shows how to configure the snasw event command:
snasw event defined-ls implicit-lssnasw ipsfilter
To filter interprocess signal trace elements being traced via snasw ipstrace or debug snasw ips, use the snasw ipsfilter global configuration command. Use the no form of this command to remove all filtering.
snasw ipsfilter [as] [asm] [bm] [ch] [cpc] [cs] [di] [dlc] [dma] [dr] [ds]
[es] [ha] [hpr] [hs] [lm] [mds] [ms] [nof] [pc] [ps] [pu] [px] [rm] [rtp]
[ru] [scm] [sco] [sm] [spc] [ss] [trs]no snasw ipsfilter
Syntax Description
Defaults
No default behavior or values.
Command Modes
Global configuration
Command History
Usage Guidelines
The command defaults to no IPS trace filtering.
Examples
The following is an example of how to configure the snasw ipsfilter command:
snasw ipsfilter ds ssRelated Commands
Traces internal interprocess signal information within SNASw.
Displays captured ipstrace information to the console.
Displays realtime ipstrace information to the console.
snasw ipstrace
To set up a trace buffer and begin tracing IPS trace elements, use the snasw ipstrace global configuration command.Use the no form of this command to turn off the capture of trace elements and to free the trace buffer.
snasw ipstrace [buffer-size buffer-size-value] [file filename]
no snasw ipstrace
Syntax Description
Defaults
This command defaults to no tracing with no cyclic buffer allocated.
Command Modes
Global configuration
Command History
Usage Guidelines
Use the snasw ipstrace command when directed by SNASw personnel.
The snasw ipstrace command copies frames into a memory buffer, which can affect router performance. Therefore, care should be taken when using this command.
The ipstrace information is stored in a cyclic buffer allocated out of main processor memory. Use the snasw dump command to dump the binary trace information to a file server or the show snasw ipstrace command to display captured IPS trace information to the console. TheIPS trace is a low-level internal trace.
Examples
The following is an example of how to configure the snasw ipstrace command:
snasw ipstrace buffer-size 1000 file tftp://myhost/path/fileRelated Commands
snasw link
To configure upstream links, use the snasw link global configuration command. Use the no form of this command to remove the configuration of upstream links.
snasw link linkname port portname rmac mac-address | ip-dest ip-address
[rsap sap-value] [nns] [tgp [high | low | medium]] [nostart]no snasw link linkname
Syntax Description
Defaults
The destination SAP value defaults to 4.
Command Modes
Global configuration
Command History
Usage Guidelines
Use the snasw link command to configure upstream connections to SNA data hosts, services, and DLUS nodes. Do not use this command to connect to client workstations and devices serviced by the SNA switch. Client workstations and devices should be configured to connect into the SNA switch by configuring an outbound connection on these devices which specifies the MAC address of a port active on SNASw.
Examples
The following are examples of how to configure the snasw link command:
snasw link LINKCMC1 port TOKENO rmac 4000.333.4444 rsap 8snasw link HOSTIP port HPRIP ip-dest 172.18.3.44Related Commands
snasw location
To configure the location of a resource, use the snasw location global configuration command. Use the no form of this command to disable the location of a resource.
snasw location resource-name owning-cp cpname
no snasw location resource-name
Syntax Description
Defaults
No default behaviors or values.
Command Modes
Global configuration
Command History
Usage Guidelines
The snasw location command is typically used when a LEN node link is established with a partner node. The snasw location command allows SNASw to route session requests over the LEN node link to the resources named.
Examples
The following is an example of how to configure the snasw location command:
snasw location NETA.INDEPLU owning-cp NETA.LENHOSTARelated Commands
snasw pathswitch
To force an HPR pathswitch for an RTP connection, use the snasw pathswitch privileged EXEC command.
snasw pathswitch rtp-connection-name
Syntax Description
rtp-connection-name
Specifies the RTP connection to path-switch. This is an eight-byte string. You can obtain the rtp-connection-name from the show snasw rtp command.
Defaults
No default behaviors or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
If a specific connection name is coded, and no such connection is known to SNASw, the snasw pathswitch command is ignored and a message is issued. Use the snasw pathswitch command to force an HPR pathswitch for sessions that use this node as an RTP endpoint.
Examples
The following is an example of how to configure the snasw pathswitch command:
snasw pathswitch @R000006Related Commands
snasw pdlog
To control message logging to the console and the SNA problem determination log cyclic buffer, use the snasw pdlog global configuration command. Use the no form of this command to remove previous pdlog configurations.
snasw pdlog [problem | exception | info] [buffer-size buffer-size-value] [file filename]
no snasw pdlog
Syntax Description
Defaults
If not coded, the snasw pdlog command defaults to an active 500 KB cyclic buffer. Problems, exceptions, and informational messages are always sent to the buffer. By default, only problems go to the console.
Command Modes
Global configuration
Command History
Usage Guidelines
Use the snasw pdlog command to customize the type of information you prefer to see on the router console from the SNASw feature.
Examples
The following is an example of how to configure the snasw pdlog command:
snasw pdlog exception buffer-size 200 file tftp://my host/files/trace.pdlogRelated Commands
Displays entries in the cyclical problem determination log to the console.
Dumps trace and problem determination logs to a file server.
snasw port
To specify the DLCs used by SNASw, use the snasw port global configuration command. Use the no form of this command to delete a previously configured port.
snasw port portname [hpr-ip | vdlc ring-group mac mac-address] interfacename
[conntype | nohpr | len | dyncplen] [dlus-required] [hpr-sap hpr-sap-value]
[max-links link-limit-value] [sap sap-value] [vnname virtual-node-name] [nns] [nostart]no snasw port portname
Syntax Description
Defaults
No default behaviors or values.
Command Modes
Global configuration
Command History
Usage Guidelines
More than one port can be configured (with different port names). A configured port cannot be redefined without first deleting the port using the no form of the port command.
Note
Examples
The following are examples of how to configure the snasw port command:
snasw port SRBG Virtual-TokenRing0 conntype nohprsnasw port UPSTREAM TokenRing1/1snasw port dlswport vdlc 30 mac 4000.33333.4444snasw port HPRIP hpr-ip Loopback0snasw port TRVLAN Vlan1/1 vnname NETA.CONNETRelated Commands
Displays the SNASw link and port associated with that link.
Displays the SNASw port objects.
snasw start
To start SNASw, use the snasw start privileged EXEC command.
snasw start
Syntax Description
There are no keywords or arguments for this command.
Defaults
No default behaviors or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
If not enough memory exists to start SNASw, a message indicating lack of memory is issued. A cpname must be configured with the snasw cpname command before SNASw will start.
Examples
The following is an example of the snasw start command:
snasw startRelated Commands
snasw start cp-cp
To initiate a request to start CP-CP sessions with a partner CP via privileged EXEC command, use the snasw start cp-cp privileged EXEC command.
snasw start cp-cp cpname
Syntax Description
cpname
Indicates the fully qualified CP name of the adjacent node with which CP-CP sessions should be started.
Defaults
No default behaviors or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The functionality is necessary because it is possible for CP-CP sessions to fail permanently or temporarily, but beyond the timeframe for automatic CP-CP session retry. If the current state of the node mandates that CP-CP sessions cannot be started to the partner (for example, CP-CP sessions already exist on a different upstream link) or no active adjacent CP matches the cpname named, the command fails.
Examples
The following is an example of the snasw start cp-cp command:
snasw start cp-cp NETA.CMCHOSTRelated Commands
snasw start link
To start an inactive defined link, use the snasw start link privileged EXEC command.
snasw start link linkname
Syntax Description
Defaults
No default behaviors or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the snasw start link command to initiate a connection sequence for a link that is defined but not currently active. Unless nostart is configured on the link definition, a link is started automatically. Use this command to start links that have nostart configured or links that have been stopped using the snasw stop link privileged EXEC command.
Examples
The following is an example of the snasw start link command:
snasw start link CMCHOST1Related Commands
snasw start port
To start an inactive port, use the snasw start port privileged EXEC command.
snasw start port portname
Syntax Description
portname
Indicates the name of the port as configured or shown in the show snasw port command.
Defaults
No default behaviors or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the snasw start port command to enable a port that is defined to the configuration but is not currently active. Unless nostart is configured on the port definition, a port is started automatically. Use this command to start ports that have nostart configured or ports that have been stopped using the snasw stop port privileged EXEC command.
Examples
The following is an example of the snasw start port command:
snasw start port TOKEN0Related Commands
snasw stop
To shut down SNASw, use the snasw stop privileged EXEC command.
snasw stop
Syntax Description
There are no keywords or arguments for this command.
Defaults
No default behaviors or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the snasw stop command to terminate all sessions, stop all ports and links, and shut down SNASw.
Examples
The following is an example of the snasw stop command:
snasw stopRelated Commands
snasw stop cp-cp
To terminate CP-CP sessions with a partner CP, use the snasw stop cp-cp privileged EXEC command.
snasw stop cp-cp cpname
Syntax Description
cpname
Indicates the fully qualified CP name of the adjacent node with which CP-CP sessions should be stopped.
Defaults
No default behaviors or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Forcing a CP-CP session termination can be used to clear some fault scenarios such as hung or nonresponsive CP sessions, allowing the SNA switch to potentially restart sessions with the same or alternate partner node.
Examples
The following is an example of the snasw stop cp-cp command:
snasw stop cp-cp NETA.CMCHOSTRelated Commands
snasw stop link
To stop an active link, use the snasw stop link privileged EXEC command.
snasw stop link linkname
Syntax Description
Defaults
No default behaviors or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
If connectivity to a specified partner CP is no longer desired, the link can be deactivated with this command. All non-HPR sessions established using this link are disconnected
Examples
The following is an example of the snasw stop link command:
snasw stop link CMCHOST1Related Commands
snasw stop port
To stop an active port, use the snasw stop port privileged EXEC command.
snasw stop port portname
Syntax Description
Defaults
No default behaviors or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the snasw stop port command to disable a specified port without removing it from the configuration. All non-HPR sessions established using this port and all links are shut down on the port.
Examples
The following is an example of the snasw stop port command:
snasw stop port TOKEN0Related Commands
snasw stop session
To terminate a session that is no longer desirable to have active, use the snasw stop session privileged EXEC command.
snasw stop session pcid fqcpname netid-destination
Syntax Description
pcid
Procedure correlator ID in 16-digit hexadecimal form.
fqcpname
Fully qualified cpname of the node that generates the PCID.
netid.destination
Fully qualified primary LU name.
Defaults
No default behaviors or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The snasw stop session command is used to clear sessions that are active but in an indeterminate or hung state or if the session partner is not responsive.
Examples
The following is an example of the snasw stop session command:
snasw stop session C3BBD36EA9CBA1AF neta.mvsdRelated Commands
Debug Commands
This section documents the new debug commands used for the SNASw feature.
debug snasw dlc
To display frame information entering and leaving SNASw in a real time to the console, use the debug snasw dlc command.
debug snasw dlc detail
Syntax Description
detail
Indicates that in addition to a one line description of the frame being displayed an entire hexadecimal dump of the frame will follow.
Defaults
By default, a one-line description of the frame is displayed.
Warning
The debug snasw dlc command displays the same trace information available from the snasw dlctrace command. The snasw dlctrace command is the preferred method for gathering this trace information because it is written to a capture buffer instead of directly to the console. The debug snasw dlc command should be used only when it is certain that excessive output will not go to the console.
Command History
Examples
The following is an example of the debug snasw dlc command:
debug snasw dlcThis command provides the following output:SequenceNumber Size of ISR/Link SNA BTU HPR Description of frame343 MVSD In sz:134 ISR fmh5 DLUR Rq ActPU NETA.APPNRA29344 MVSD Out sz:12 ISR +Rsp IPM slctd nws:0008345 @I000002 Out sz:18 ISR Rq ActPU346 MVSD Out sz:273 ISR fmh5 TOPOLOGY UPDATE347 @I000002 In sz:9 ISR +Rsp Data348 @I000002 In sz:12 ISR +Rsp IPM slctd nws:0002349 @I000002 In sz:29 ISR +Rsp ActPU350 MVSD Out sz:115 ISR fmh5 DLUR +Rsp ActPU351 MVSD In sz:12 ISR +Rsp IPM slctd nws:0007352 MVSD In sz:88 ISR fmh5 DLUR Rq ActLU NETA.MARTLU1353 MVSD Out sz:108 ISR fmh5 REGISTER354 @I000002 Out sz:27 ISR Rq ActLU NETA.MARTLU1Related Commands
Captures trace frames entering and leaving the SNASw feature.
Filters frames traced by the snasw dlctrace or debug snasw dlc commands.
debug snasw ips
To display internal signal information realtime to the console, use the debug snasw ips command.
debug snasw ips
Syntax Description
There are no keywords or arguments for this command.
Defaults
By default, a one-line description of the interprocess signal is displayed.
Warning
The debug snasw ips command displays the same trace information available from the snasw ipstrace command. Output from this debug command can be large. The snasw ipstrace command is the preferred method for gathering this trace information because it is written to a capture buffer instead of being written directly to the console. The debug snasw ips command should only be used when it is certain that the output will not cause excessive data to appear on the console. The debug snasw dlc command displays the same trace information available via the snasw dlctrace command. The snasw dlctrace command is the preferred method for gathering this trace information because it is written to a capture buffer instead of directly to the console. The debug snasw dlc command should only be used when it is certain that the output will not cause excessive data to be output to the console.
Command History
Examples
The following is an example of the debug snasw ips command:
debug snasw ipsThis command provides the following output:SequenceNumber Sending ReceivingSignal Name Process Process Queue11257 : DEALLOCATE_RCB : --(0) -> RM(2130000) Q 411258 : RCB_DEALLOCATED : RM(2130000) -> PS(22E0000) Q 211259 : RCB_DEALLOCATED : --(0) -> PS(22E0000) Q 211260 : VERB_SIGNAL : PS(22E0000) -> DR(20F0000) Q 211261 : FREE_SESSION : --(0) -> RM(2130000) Q 211262 : BRACKET_FREED : RM(2130000) -> HS(22FB0001) Q 211263 : BRACKET_FREED : --(0) -> HS(22FB0001) Q 211264 : VERB_SIGNAL : --(0) -> DR(20F0000) Q 211265 : DLC_MU : DLC(2340000) -> PC(22DD0001) Q 211266 : DLC_MU : --(0) -> PC(22DD0001) Q 2Related Commands
debug snasw link
To display detailed link FSM information for all links entering and leaving SNASw in real time to the console, use the debug snasw link command.
debug snasw link
Syntax Description
There are no keywords or arguments for this command.
Defaults
None.
Warning
The The output from the debug snasw link command can be large. The command should only be used when a minimal number of links are active to avoid excessive console data.
Command History
Examples
The following is an example of the debug snasw link command:
debug snasw linkThis command provides the following output:grandpa#snas start link moetok0grandpa#03:31:38:SNASW LinkFsm:CepMap 1AD80001, Input=DCL_CONNECT_OUT,OldState=Reset, NewState=ConnOut, Action=A03:31:38:SNASW LinkFsm:CepMap 1AD80001, Input=CLS_OPNSTN(pos),OldState=ConnOut, NewState=Open, Action=C03:31:38:SNASW LinkFsm:CepMap 1AD80001, Input=DCL_SEND_XID,OldState=Open, NewState=Open, Action=K03:31:38:SNASW LinkFsm:CepMap 1AD80001, Input=CLS_XID_RSP(pos),OldState=Open, NewState=Open, Action=L03:31:38:SNASW LinkFsm:CepMap 1AD80001, Input=DCL_SEND_XID,OldState=Open, NewState=Open, Action=K03:31:38:SNASW LinkFsm:CepMap 1AD80001, Input=CLS_XID_RSP(pos),OldState=Open, NewState=Open, Action=L03:31:38:SNASW LinkFsm:CepMap 1AD80001, Input=DCL_SEND_XID,OldState=Open, NewState=Open, Action=K03:31:38:SNASW LinkFsm:CepMap 1AD80001, Input=CLS_XID_RSP(pos),OldState=Open, NewState=Open, Action=L03:31:38:SNASW LinkFsm:CepMap 1AD80001, Input=DCL_SEND_XID,OldState=Open, NewState=Open, Action=K03:31:38:SNASW LinkFsm:CepMap 1AD80001, Input=CLS_XID_RSP(pos),OldState=Open, NewState=Open, Action=L03:31:38:SNASW LinkFsm:CepMap 1AD80001, Input=DCL_SET_MODE,OldState=Open, NewState=SentSetMode, Action=N03:31:38:SNASW LinkFsm:CepMap 1AD80001, Input=CLS_CONNECT_CNF(pos),OldState=SentSetMode, NewState=Active(1), Action=P03:31:38:%SNASW-3-EVENT:Link station MOETOK0 activated03:31:38:SNASW LinkFsm:CepMap 1AD80001, Input=CLS_PONG,OldState=Active(1), NewState=Active(1), Action=Z03:31:38:SNASW LinkFsm:CepMap 1AD80001, Input=DCL_MU,OldState=Active(1), NewState=Active(1), Action=T03:31:38:SNASW LinkFsm:CepMap 1AD80001, Input=CLS_OPNSTN_UI(pos),OldState=Active(1), NewState=Active(2), Action=S03:31:38:SNASW LinkFsm:CepMap 1AD80001, Input=CLS_DATA_IND,OldState=Active(2), NewState=Active(2), Action=XRelated Commands
debug snasw port
To display detailed port FSM information for all ports entering and leaving SNASw in a real time to the console, use the debug snasw port command.
debug snasw port
Syntax Description
There are no keywords or arguments for this command.
Defaults
None.
Command History
Examples
The following is an example of the debug snasw port command:
debug snasw portThis command provides the following output:grandpa#snas start port tok0grandpa#03:39:15:SNASW PortFsm:SapMap 1A820002, Input=CreateDLC,OldState=Reset, NewState=PendingEnable, Action=A03:39:15:SNASW PortFsm:SapMap 1A820002, Input=ClsEnable.Cnf(pos),
