-
Cisco IOS Bridging and IBM Networking Command Reference, Volume 2 of 2: IBM Networking, Release 12.3
-
IBM Networking Commands: A through B
-
IBM Networking Commands: C through D
-
IBM Networking Commands: D
-
IBM Networking Commands: E through O
-
IBM Networking Commands: P through S
-
IBM Networking Commands: S
-
IBM Networking Commands: show ext through show ext
-
IBM Networking Commands: show fra through show txc
-
IBM Networking Commands: S through X
-
Table Of Contents
sna enable-host (Token Ring, Ethernet, Frame Relay, FDDI)
sna host (Token Ring, Ethernet, FDDI, RSRB, VDLC)
source-bridge remote-peer frame-relay
source-bridge remote-peer interface
stun route address interface dlci
stun route address interface serial
stun route all interface serial
stun schema offset length format
shutdown (CMCC)
To shut down an interface or the virtual interface on the Cisco Mainframe Channel Connection (CMCC) adapter when the router is in interface configuration mode, use the shutdown command in interface configuration mode. The shutdown TN3270 server command also shuts down TN3270 entities, such as physical unit (PU), Dependent Logical Unit Requestor (DLUR), and DLUR service access point (SAP), depending on which configuration mode the router is in when the command is issued. To restart the interface or entity, use the no form of this command. The entity affected depends on the mode in which the command is issued.
shutdown
no shutdown
Syntax Description
This command has no arguments or keywords.
Defaults
The interface or entity is enabled.
Command Modes
Interface configuration
Command History
Usage Guidelines
When using this command on a channel interface, the command applies to the entire CMCC adapter.
Examples
The following example issued in interface configuration mode shuts down the entire CMCC adapter:
shutdownshutdown (TN3270)
To shut down TN3270 entities, such as physical unit (PU), Dependent Logical Unit Requestor (DLUR), and DLUR service access point (SAP), use the shutdown command in the appropriate TN3270 server command modes. To restart the interface or entity, use the no form of this command.
shutdown
no shutdown
Syntax Description
This command has no arguments or keywords.
Defaults
The interface or entity is enabled.
Command Modes
TN3270 server configuration
PU configuration
DLUR configuration
DLUR PU configuration
DLUR SAP configuration
Listen-point configuration
Listen-point PU configuration
Command History
Usage Guidelines
The shutdown TN3270 command shuts down the TN3270 entities according to which configuration mode the router is in when the command is issued.
•
In TN3270 server configuration mode, the command shuts down the entire TN3270 server function.
•
•
•
•
Examples
The following example issued in TN3270 server configuration mode shuts down the entire TN3270 server:
shutdownsna enable-host (QLLC)
To enable an X.121 subaddress for use by the Systems Network Architecture (SNA) Service Point feature on the interface, use the sna enable-host command in interface configuration mode. To disable SNA Service Point on the interface, use the no form of this command.
sna enable-host qllc x121-subaddress
no sna enable-host qllc x121-subaddress
Syntax Description
qllc
Required keyword for Qualified Logical Link Control (QLLC) data-link control.
x121-subaddress
X.121 subaddress.
Defaults
No default X.121 subaddress is specified.
Command Modes
Interface configuration
Command History
Examples
In the following example, X.121 subaddress 320108 is enabled for use by host connections:
sna enable-host qllc 320108Related Commands
sna enable-host (SDLC)
To enable a Synchronous Data Link Control (SDLC) address for use by host connections, use the sna enable-host command in interface configuration mode. To cancel the definition, use the no form of this command.
sna enable-host sdlc sdlc-address
no sna enable-host sdlc sdlc-address
Syntax Description
Defaults
No default SDLC address is specified.
Command Modes
Interface configuration
Command History
Examples
In the following example, SDLC address C1 is enabled for use by host connections:
encapsulation sdlcsdlc role secondarysdlc address c1sna enable-host sdlc c1Related Commands
encapsulation sdlc
Configures an SDLC interface.
sna host (SDLC)
Defines a link to a Systems Network Architecture (SNA) host over an SDLC connection.
sna enable-host (Token Ring, Ethernet, Frame Relay, FDDI)
To enable Systems Network Architecture (SNA) on the interface, use the sna enable-host command in interface configuration mode. To disable SNA on the interface, use the no form of this command.
sna enable-host [lsap lsap-address]
no sna enable-host [lsap lsap-address]
Syntax Description
lsap
(Optional) Activate a local service access point (SAP) as an upstream SAP, for both receiving ConnectIn attempts and for starting ConnectOut attempts.
lsap-address
(Optional) The default is 12.
Defaults
The default LSAP parameter is 12.
Command Modes
Interface configuration
Command History
Examples
The following example enables SNA on the interface and specifies that the local SAP (LSAP) 10 will be activated as an upstream SAP:
sna enable-host lsap 10Related Commands
sna host (Frame Relay)
To define a link to a Systems Network Architecture (SNA) host over a Frame Relay connection, use the sna host command in global configuration mode. To cancel the definition, use the no form of this command.
sna host host-name xid-snd xid dlci dlci-number [rsap remote-sap] [lsap local-sap] [interface slot/port] [window window-size] [maxiframe max-iframe] [retries retry-count] [retry-timeout retry-timeout] [focalpoint]
no sna host host-name xid-snd xid dlci dlci-number [rsap remote-sap] [lsap local-sap] [interface slot/port] [window window-size] [maxiframe max-iframe] [retries retry-count] [retry-timeout retry-timeout] [focalpoint]
Syntax Description
Defaults
The default remote SAP is 4.
The default local SAP is 12.
The default window size is 7.
The default maximum I-frame size is 1472.
The default retry count is 255.
The default retry timeout is 30 seconds.Command Modes
Global configuration
Command History
Examples
The following example defines a link to a Systems Network Architecture (SNA) host:
sna host CNM01 xid-snd 05d00001 dlci 200 rsap 4 lsap 4Related Commands
sna enable-host (Token Ring, Ethernet, Frame Relay, FDDI)
Enables SNA on the interface.
sna start
Initiates a connection to a remote resource.
sna host (QLLC)
To define a link to a Systems Network Architecture (SNA) host over an X.25 or Qualified Logical Link Control (QLLC) connection, use the sna host command in global configuration mode. To cancel the definition, use the no form of this command.
sna host host-name xid-snd xid x25 remote-x121-addr [qllc local-x121-subaddr] [interface slot/port] [window window-size] [maxiframe max-iframe] [retries retry-count] [retry-timeout retry-timeout] [focalpoint]
no sna host host-name xid-snd xid x25 remote-x121-addr [qllc local-x121-subaddr] [interface slot/port] [window window-size] [maxiframe max-iframe] [retries retry-count] [retry-timeout retry-timeout] [focalpoint]
Syntax Description
Defaults
The default remote SAP is 4.
The default window size is 7.
The default maximum I-frame size is 1472.
The default retry count is 255.
The default retry timeout is 30 seconds.Command Modes
Global configuration
Command History
Examples
The following example defines a link to a Systems Network Architecture (SNA) host:
sna host MLM1 xid-snd 05d00001 x25 320108 qllc 08Related Commands
sna enable-host (QLLC)
Enables an X.121 subaddress for use by the SNA Service Point feature on the interface.
sna start
Initiates a connection to a remote resource.
sna host (SDLC)
To define a link to a Systems Network Architecture (SNA) host over an Synchronous Data Link Control (SDLC) connection, use the sna host command in global configuration mode. To cancel the definition, use the no form of this command.
sna host host-name xid-snd xid sdlc sdlc-addr [rsap remote-sap] [lsap local-sap] [interface slot/port] [window window-size] [maxiframe max-iframe] [retries retry-count] [retry-timeout retry-timeout] [focalpoint]
no sna host host-name xid-snd xid rmac remote-mac [rsap remote-sap] [lsap local-sap] [interface slot/port] [window window-size] [maxiframe max-iframe] [retries retry-count] [retry-timeout retry-timeout] [focalpoint]
Syntax Description
Defaults
The default remote SAP is 4.
The default local SAP is 12.
The default window size is 7.
The default maximum I-frame size is 1472.
The default retry count is 255.
The default retry timeout is 30 seconds.Command Modes
Global configuration
Command History
Examples
The following example defines a link to a Systems Network Architecture (SNA) host:
sna host CNM01 xid-snd 05d00001 sdlc c1 rsap 4 lsap 4 focalpointRelated Commands
sna enable-host (SDLC)
Enables an Synchronous Data Link Control (SDLC) address for use by host connections.
sna start
Initiates a connection to a remote resource.
sna host (Token Ring, Ethernet, FDDI, RSRB, VDLC)
To define a link to a Systems Network Architecture (SNA) host over Token Ring, Ethernet, FDDI, remote source-route bridging (RSRB), or virtual data-link control connections, use the sna host command in global configuration mode. To cancel the definition, use the no form of this command.
sna host host-name xid-snd xid rmac remote-mac [rsap remote-sap] [lsap local-sap] [interface slot/port] [window window-size] [maxiframe max-iframe] [retries retry-count] [retry-timeout retry-timeout] [focalpoint]
no sna host host-name xid-snd xid rmac remote-mac [rsap remote-sap] [lsap local-sap] [interface slot/port] [window window-size] [maxiframe max-iframe] [retries retry-count] [retry-timeout retry-timeout] [focalpoint]
Syntax Description
Defaults
The default remote SAP is 4.
The default local SAP is 12.
The default window size is 7.
The default maximum I-frame size is 1472.
The default retry count is 255.
The default retry timeout is 30 seconds.Command Modes
Global configuration
Command History
Examples
The following example defines a link to a Systems Network Architecture (SNA) host:
sna host CNM01 xid-snd 05d00001 rmac 4001.3745.1088 rsap 4 lsap 4 focalpointRelated Commands
sna rsrb enable-host
To enable an remote source-route bridging (RSRB) service access point (SAP) for use by the Systems Network Architecture (SNA) Service Point feature, use the sna rsrb enable-host command in global configuration mode. To disable the RSRB SAP, use the no form of this command.
sna rsrb enable-host [lsap local-sap]
no sna rsrb enable-host [lsap local-sap]
Syntax Description
Defaults
The default local SAP address is 12.
Command Modes
Global configuration
Command History
Examples
In the following example, the local SAP address 10 of the RSRB is enabled for use by the ibm3745 host physical unit (PU):
source-bridge ring-group 99source-bridge remote-peer 99 tcp 10.10.13.1source-bridge remote-peer 99 tcp 10.10.13.2sna rsrb 88 1 99 4000.FFFF.0001sna rsrb enable-host lsap 10sna host ibm3745 xid-snd 06500001 rmac 4000.3745.0001 lsap 10interface serial 0ip address 10.10.13.1 255.255.255.0Related Commands
sna host (Token Ring, Ethernet, FDDI, RSRB, VDLC)
Defines a link to an SNA host over Token Ring, Ethernet, FDDI, RSRB, or virtual data-link control (VDLC) connections.
sna rsrb start
To specify that an attempt will be made to connect to the remote resource defined by the host name through the remote source-route bridging (RSRB), use the sna rsrb start command in global configuration mode. To cancel the definition, use the no form of this command.
sna rsrb start host-name
no sna rsrb start host-name
Syntax Description
Defaults
No default behavior or values
Command Modes
Global configuration
Command History
Usage Guidelines
Before issuing this command, you must enable the correct local service access point (SAP) with the appropriate enable command (sna rsrb enable-host).
Examples
In the following example, the Systems Network Architecture (SNA) Service Point will initiate a connection with the ibm3745 host physical unit (PU) across the RSRB link:
source-bridge ring-group 99source-bridge remote-peer 99 tcp 10.10.13.1source-bridge remote-peer 99 tcp 10.10.13.2sna rsrb 88 1 99 4000.FFFF.0001sna rsrb enable-host lsap 10sna host ibm3745 xid-snd 06500001 rmac 4000.3745.0001 lsap 10sna rsrb start ibm3745interface serial 0ip address 10.10.13.1 255.255.255.0Related Commands
sna rsrb
To specify the entities that the Systems Network Architecture (SNA) feature will simulate at the remote source-route bridge (RSRB), use the sna rsrb command in interface configuration mode. To cancel the specification, use the no form of this command.
sna rsrb local-virtual-ring bridge-number target-virtual-ring virtual-macaddr
no sna rsrb local-virtual-ring bridge-number target-virtual-ring virtual-macaddr
Syntax Description
Defaults
No default behavior or values
Command Modes
Interface configuration
Command History
Usage Guidelines
You can specify the bridge number no more than once in any configuration.
Examples
The following example identifies a LAN:
sna rsrb 88 1 99 4000.FFFF.0001Related Commands
sna rsrb start
Specifies that an attempt will be made to connect to the remote resource defined by the host name through the remote source-route bridging (RSRB).
sna start
To initiate a connection to a remote resource, use the sna start command in interface configuration mode. To cancel the connection attempt, use the no form of this command.
sna start [resource-name]
no sna start [resource-name]
Syntax Description
Defaults
No default behavior or values
Command Modes
Interface configuration
Command History
Usage Guidelines
Before issuing this command, you must enable the correct address using the sna enable-host command.
Examples
The following example initiates a connection to CNM01:
sna start CNM01Related Commands
sna vdlc
To identify the local virtual ring and virtual MAC address that will be used to establish Systems Network Architecture (SNA) host connections over data-link switching plus (DLSw+) using virtual data-link control, use the sna vdlc command in global configuration mode. To cancel the definition, use the no form of this command.
sna vdlc ring-group virtual-mac-address
no sna vdlc ring-group virtual-mac-address
Syntax Description
ring-group
Local virtual ring number identifying the source-route bridging (SRB) ring group.
virtual-mac-address
Virtual MAC address that represents the SNA virtual data-link control.
Defaults
No default behavior or values
Command Modes
Global configuration
Command History
Usage Guidelines
The virtual data-link control local virtual ring must have been previously configured using the source-bridge ring-group command.
The virtual data-link control virtual MAC address must be unique within the DLSw+ network.
To avoid an address conflict on the virtual MAC address, use a locally administered address in the form 4000.xxxx.xxxx.
Examples
The following is an example of an SNA Service Point configuration that uses virtual data-link control over DLSw+:
source-bridge ring-group 99dlsw local-peer peer-id 10.10.16.2dlsw remote-peer 0 tcp 10.10.16.1sna vdlc 99 4000.4500.01f0sna vdlc enable-host lsap 12sna host HOST-B xid-snd 065bbbb0 rmac 4000.7000.01f1 rsap 4 lsap 12 focalpointsna vdlc start HOST-Binterface serial 3description IP connection to dspu7kip address 10.10.16.2 255.255.255.0clockrate 4000000Related Commands
sna vdlc enable-host
To enable a service access point (SAP) for use by the Systems Network Architecture (SNA) Service Point feature, use the sna vdlc enable-host command in global configuration mode. To disable the SAP, use the no form of this command.
sna vdlc enable-host [lsap local-sap]
no sna vdlc enable-host [lsap local-sap]
Syntax Description
Defaults
The default local SAP address is 12.
Command Modes
Global configuration
Command History
Examples
In the following example, the local SAP address 12 is enabled for use by the host physical unit (PU) HOST-B:
source-bridge ring-group 99dlsw local-peer peer-id 10.10.16.2dlsw remote-peer 0 tcp 10.10.16.1sna vdlc 99 4000.4500.01f0sna vdlc enable-host lsap 12sna host HOST-B xid-snd 065bbbb0 rmac 4000.7000.01f1 rsap 4 lsap 12 focalpointsna vdlc start HOST-Binterface serial 3description IP connection to dspu7kip address 10.10.16.2 255.255.255.0clockrate 4000000Related Commands
sna vdlc start
To specify that an attempt will be made to connect to the remote resource defined by the host name through virtual data-link control (VDLC), use the sna vdlc start command in global configuration mode. To cancel the definition, use the no form of this command.
sna vdlc start host-name
no sna vdlc start host-name
Syntax Description
Defaults
No default behavior or values
Command Modes
Global configuration
Command History
Usage Guidelines
Before issuing this command, you must enable the correct local service access point (SAP) with the sna vdlc enable-host command.
Examples
In the following example, the Systems Network Architecture (SNA) Service Point feature uses virtual data-link control to initiate a connection with the host physical unit (PU) HOST-B:
source-bridge ring-group 99dlsw local-peer peer-id 10.10.16.2dlsw remote-peer 0 tcp 10.10.16.1sna vdlc 99 4000.4500.01f0sna vdlc enable-host lsap 12sna host HOST-B xid-snd 065bbbb0 rmac 4000.7000.01f1 rsap 4 lsap 12 focalpointsna vdlc start HOST-Binterface serial 3description IP connection to dspu7kip address 10.10.16.2 255.255.255.0clockrate 4000000Related Commands
sna vdlc
Identifies the local virtual ring and virtual MAC address that will be used to establish SNA host connections over data-link switching plus (DLSw+) using VDLC.
snasw cpname
To define a control point (CP) name for SNASw, use the snasw cpname command in global configuration mode. To deactivate SNASw and remove the CP definition, use the no form of this command.
snasw cpname {netid.cpname | netid [hostname | ip-address interface-name]} [hung-pu-awareness timer-value] [hung-session-awareness timer-value] [locate-timeout timeout-value] [max-pacing-window max-value] [remove-rscvs] [station-segmentation]
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 by using the snasw stop privileged EXEC command which enables you to stop and restart SNASw without losing the SNASw configuration. If you use no snasw cpname, all SNASw configuration commands that were entered will be lost.
Coding a CP name is required for SNASw. Only one snasw cpname command is allowed at a time. You cannot change the snasw cpname command without first deleting the previous definition by using the no form of the command. If SNASw is active, the no form deactivates it. If SNASw is inactive, using 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 Loopback0snasw dlcfilter
To filter frames being captured, use the snasw dlcfilter command in global configuration mode. To disable the filtering of frames arriving and leaving Switching Services (SNASw), use the no form of this command.
snasw dlcfilter [link linkname [session session-address]] [port portname] [rmac mac-address-value [session session-address]] [rtp rtp-name [session session-address]] [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
12.0(5)XN
This command was introduced.
12.0(7)T
This command was integrated into Cisco IOS Release 12.0 T.
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.
Up to four different types of filters can be in place at once. If multiple filters are coded for all filters except the type filter, the frame must to pass only a single filter to be included in the trace. If the type filter is coded, the frame must pass the type filter and at least one of the other filters that is coded to be included in the trace.
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
snasw dlctrace
To trace frames arriving and leaving Switching Services (SNASw), use the snasw dlctrace command in global configuration mode. To deactivate the capture of frame data and free the storage buffer used to capture the data, use the no form of this command.
snasw dlctrace [buffer-size buffer-size-value] [file filename [timestamp]] [frame-size frame-size-value | auto-terse] [format [brief | detail | analyzer]] [nostart]
no snasw dlctrace
Syntax Description
Defaults
Tracing is off.
If a value for the buffer-size-value argument is not specified, then the default is 500, creating a 500-KB buffer.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.
When the analyzer format is used, portions of the frame are reconstructed from their actual representation on the data link. Because of this format, portions of the data in the header portion of the frame are modified. Specifically, if Routing Information Field (RIF) data was present on the actual data-link frame, that information is omitted in the dlctrace. In addition, information in the Logical Link Control (LLC) header (for example, Nr, Ns counts) is not reliably transferred to the traced frame. However, the remainder of the frame, including all Systems Network Architecture (SNA) content, is a reliable representation of the frame as it appeared on the actual upstream or downstream link.
Examples
The following are examples of how to configure the snasw dlctrace command:
snasw dlctracesnasw dlctrace buffer-size 5000 file tftp://10.69.120.21/dlcfiles/dlc/trcRelated Commands
snasw dlus
To specify parameters related to Dependent Logical Unit Requestor (DLUR) or Dependent Logical Unit Server (DLUS) functionality, use the snasw dlus command in global configuration mode. To remove the data specified in a previous snasw dlus command, use the no form of this command.
snasw dlus primary-dlus-name [backup backup-dlus-name] [prefer-active] [retry interval count] [once]
no snasw dlus
Syntax Description
Defaults
If the prefer-active keyword 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
12.0(5)XN
This command was introduced.
12.0(7)T
This command was integrated into Cisco IOS Release 12.0 T.
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.
The prefer-active keyword supersedes the once keyword, which means that if the prefer-active keyword is configured and there is an active DLUS, then all DLUS services requests will be negotiated only with the active DLUS. The DLUR will not send DLUS service requests to other DLUSs. In this situation, the once keyword has no effect.
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 3snasw dump
To copy problem determination logs and traces from internal buffers to an external file server, use the snasw dump command in privileged EXEC mode.
snasw dump {all | dlctrace | ipstrace | summary-ipstrace | pdlog}
Syntax Description
Command Modes
Privileged EXEC
Defaults
No default behavior or values
Command History
12.0(5)XN
This command was introduced.
12.0(7)T
This command was integrated into Cisco IOS Release 12.0 T.
Usage Guidelines
The snasw dump command is used for gathering trace files for diagnosis by Cisco personnel or onsite trace analysis.
If the output file size exceeds 32MB, the first 32MB will be in the file with the name filename, the next 32MB will be in the file with the name filename.01, and so on. Note that with formatting, the output may be of different size than the buffer-size.
Before you use FTP, make sure you configure the ip ftp username and ip ftp password command to a valid user and password on the system to which the file is being sent.
Examples
The following are examples of how to enter the snasw dump command:
Router# snasw dump allRouter# snasw dump dlctraceRelated Commands
snasw event
To indicate which normal events are logged to the console, use the snasw event command in global configuration mode. To return the events to their default state, use the no form of this command.
snasw event [cpcp] [dlc] [implicit-ls] [port]
no snasw event
Syntax Description
Defaults
By default, only defined links and Dependent Logical Unit Server (DLUS) events are sent to the pdlog or console.
Command Modes
Global configuration
Command History
12.0(5)XN
This command was introduced.
12.0(7)T
This command was integrated into Cisco IOS Release 12.0 T.
12.1(6)
The defined-ls keyword was deleted.
Examples
The following example shows how to configure the snasw event command:
snasw event implicit-lssnasw ip-precedence
To define IP type of service (ToS) precedence settings to be mapped to Advanced Peer-to-Peer Networking (APPN) priorities, use the snasw ip-precedence command in global configuration mode. To remove the precedence settings, use the no form of this command.
snasw ip-precedence link link-setting network network-setting high high-setting medium medium-setting low low-setting
no snasw ip-precedence link link-setting network network-setting high high-setting medium medium-setting low low-setting
Syntax Description
Defaults
No default behavior or values
Command Modes
Global configuration
Command History
Examples
The following is an example of how to configure the snasw ip-precedence command:
snasw ip-precedence link 7 network 7 high 7 medium 7 low 7snasw ipsfilter
To filter interprocess signal trace elements being traced using the snasw ipstrace or debug snasw ips command, use the snasw ipsfilter command in global configuration mode. To remove all filtering, use the no form of this command.
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
12.0(5)XN
This command was introduced.
12.0(7)T
This command was integrated into Cisco IOS Release 12.0 T.
Usage Guidelines
The command defaults to no InterProcess Signal (IPS) trace filtering.
Examples
The following is an example of how to configure the snasw ipsfilter command:
snasw ipsfilter ds ssRelated Commands
snasw ipstrace
To set up a trace buffer and begin tracing InterProcess Signal (IPS) trace elements, use the snasw ipstrace command in global configuration mode. To turn off the capture of trace elements and to free the trace buffer, use the no form of this command.
snasw ipstrace [buffer-size buffer-size-value] [file filename timestamp]
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 Switching Services (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. The IPS 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 command in global configuration mode. To remove the configuration of upstream links, use the no form of this command.
snasw link linkname port portname rmac mac-address | ip-dest ip-address [rsap sap-value] [nns] [tgp [high | low | medium | secure]] [nostart]
no snasw link linkname
Syntax Description
Defaults
The destination SAP value defaults to 4.
The default TG characteristic profile is medium and nonsecure.
Command Modes
Global configuration
Command History
12.0(5)XN
This command was introduced.
12.0(7)T
This command was integrated into Cisco IOS Release 12.0 T.
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 establish downstream connections to client workstations and devices that are serviced by the SNA switch. Configure client workstations and devices to connect into the SNA switch by configuring an outbound connection on these devices that specifies the MAC address of a port that is active on SNASw. SNASw then creates the downstream link dynamically when the workstation or device connects to SNASw.
If using the ip-dest keyword and using a DNS name instead of an IP address, the DNS name is resolved to an IP address at the time the definition is entered (or the time SNASw is started) and will remain resolved to that same address for the duration that SNASw is active. The DNS name is not resolved to an IP address each time the link is restarted.
If the link fails and SNASw switches to a non-preferred NNS (one without the nns keyword configured), SNASw will return CP-CP sessions to the preferred NNS when the NNS link becomes active again. Also, when the nns keyword is configured on a link, that link can be automatically restarted, even after the snasw stop link command is issued. See the snasw stop link command for details.
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
show snasw link
Shows the SNASw link objects.
snasw port
Specifies the DLCs used by SNASw.
snasw location
To configure the location of a resource, use the snasw location command in global configuration mode. To disable the location of a resource, use the no form of this command.
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
12.0(5)XN
This command was introduced.
12.0(7)T
This command was integrated into Cisco IOS Release 12.0 T.
12.2
Support was added for wildcards in the cpname argument.
Usage Guidelines
The snasw location command is typically used when a low-entry networking node (LEN) node link is established with a destination logical unit (LU). The snasw location command allows Switching Services (SNASw) to route session requests over the LEN node link to the resources named.
When a LEN node connects into an SNASw node, SNASw dynamically learns the CP name of the LEN and places it in its directory. In addition, SNASw dynamically learns the LU names of all LUs on the LEN that initiate independent sessions. Only define the location when an independent logical unit (ILU) on a LEN device is not sharing the node's CP name and does not initiate the first session. In all other cases the LU's location will be learned dynamically.
The directory entry is created the next time the LEN node connects. If there is already a link to the LEN node active and you add a new SNASw location statement, it will not take effect until the next time the LEN CP connects.
Do not use the snasw location command to predefine the location of any resource that can be found dynamically using Advanced Peer-to-Peer Networking (APPN) searches (for example, resources on upstream APPN nodes or upstream or downstream ENs).
It is permissible to use the wildcard character "*" in location definitions to allow a definition to generate name associations for multiple devices. When the wildcard character is used for this purpose, the * symbol must be coded in both the resource-name and the cpname argument. If any real device attaches with a CP name that matches the nonwildcard portion of the owning-cp cpname keyword—argument pair specified, a location association will be made that replaces the wildcard characters of the CPname in the position of the resource-name argument. For example, if a definition snasw location NETA.LU*01 owning-cp NETA.CP* is coded and CP with the name NETA.CPABCD connects, then the resource name NETA.LUABCD01 will be defined to SNASw with owning-cp NETA.CPABCD.
You can also use the wildcard character "*" in location definitions to allow a specific device to connect under different CP names, but a single device cannot connect under multiple CP names at the same time. In this case, the * symbol must be used in only the cpname argument and not the resource-name argument. When the device connects with a CP name that matches the nonwildcard portion of the cpname argument, a corresponding location association will be made for the resource-name argument with that CP name.
Examples
The following is an example of how to configure the snasw location command:
snasw location NETA.INDEPLU owning-cp NETA.LENHOSTARelated Commands
snasw mode
To define a new mode and associate it with an existing Class of Service (COS), use the snasw mode command in global configuration mode. To delete the mode, use the no form of this command.
snasw mode mode cos cos
no snasw mode mode cos cos
Syntax Description
Defaults
No default behavior or values
Command Modes
Global configuration
Command History
Examples
The following is an example of how to configure the snasw mode command:
snasw mode abcmode cos #INTERsnasw msgdump
To enable automatic dumping of the data-link control (DLC) trace, InterProcess Signal (IPS) trace, and problem determination log when a specified Systems Network Architecture (SNA) Switching Services (SNASw) message is displayed, use the snasw msgdump command in global configuration mode. To disable automatic dumping, use the no form of this command.
snasw msgdump message
no snasw msgdump message
Syntax Description
Defaults
No default behavior or values
Command Modes
Global configuration
Command History
Usage Guidelines
The snasw msgdump command is only invoked the first time the target message is encountered. To trigger automatic dumping after this first instance of the target message, unconfigure and reconfigure the command by entering the no snasw msgdump command followed by the snasw msgdump command.
When the message dump is invoked, an SNA Alert is sent to the local node's Alert focal point. To verify the existance of an Alert focal point, use the show snasw node command and look at the value of the "Alert focal point" entry.
Usually, SNASw will have an Alert focal point when the router's has an active upstream link to a network node server.
If that link is active and there is still no focal point, enter the following command in the NetView mainframe application:
FOCALPT CHANGE,FPCAT=ALERT,TARGET=cpnamewhere cpname is either the CP name of the NN server for SNASw or the CP name of SNASw itself.
The Alert ID of the SNA Alert sent is x'DAED5B0B'.
Examples
The following example shows how to use the snasw msgdump command:
snasw msgdump %SNASW-6-CS_LOG_60snasw pathswitch
To force an High-Performance Routing (HPR) pathswitch for an Realtime Transport Protocol (RTP) connection, use the snasw pathswitch command in privileged EXEC mode.
snasw pathswitch [rtp-connection-name | all]
Syntax Description
Defaults
No default behaviors or values
Command Modes
Privileged EXEC
Command History
12.0(5)XN
This command was introduced.
12.0(7)T
This command was integrated into Cisco IOS Release 12.0 T.
Usage Guidelines
If a specific connection name is coded, and no such connection is known to Switching Services (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.
Use the snasw pathswitch command if you want to force a switch back to a primary route when it recovers, and the session seems to be hung.
There is not a no form for this command.
Examples
The following is an example of how to execute the snasw pathswitch command:
Router# snasw pathswitch @R000006Related Commands
snasw pdlog
To control message logging to the console and the Systems Network Architecture (SNA) problem determination log cyclic buffer, use the snasw pdlog command in global configuration mode. To remove previous pdlog configurations, use the no form of this command.
snasw pdlog [problem | exception | info] [buffer-size buffer-size-value] [file filename [timestamp]]
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 Switching Services (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
snasw port
To specify the data-link control (DLC)s used by Switching Services (SNASw), use the snasw port command in global configuration mode. To delete a previously configured port, use the no form of this command.
HPR-IP Ports
snasw port port-name hpr-ip interface-name [hostname v4-or-v6-hostname] [ldlc [liveness-time t1-retry-time t1-retry-count]] [maxbtu max-btu-size] [vnname virtual-node-name [no-limres]] [nostart]
no snasw port port-name
VDLC and Virtual Token Ring Ports
snasw port port-name {vdlc ring-group mac mac-address | virtual-TokenRing-interface-name} [conntype nohpr | len | dyncplen | dialoutlen] [hpr-sap hpr-sap-value] [max-links link-limit-value] [maxbtu max-btu-size] [nns-required] [sap sap-value] [vnname virtual-node-name [no-limres]] [nostart]
no snasw port port-name
All Other Types of Ports
snasw port port-name interface-name [conntype nohpr | len | dyncplen | dialoutlen] [nns-required] [hpr-sap hpr-sap-value] [max-links link-limit-value] [maxbtu max-btu-size] [sap sap-value] [vnname virtual-node-name [no-limres]] [nostart]
no snasw port port-name
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
Note
The interface must be defined before the ports that use them are defined and activated.
SNASw does not support EtherChannel interfaces (neither port-channel interfaces nor Fast Ethernet interfaces configured with the channel-group command). Do not try to configure a SNASw port with either of these EtherChannel interface types.The interface must be defined before the ports that use the interface are defined and activated. When using the hostname keyword, the hostname must be defined on the interface and be resolved locally by either ip host or ipv6 host commands or by a Domain Name Server before the SNASw port is configured.
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.CONNETsnasw port HOSTEE hpr-ip Loopback0 vnname NETA.CONNET hostname Loop0ipRelated Commands
snasw link
Configures upstream links.
show snasw port
Displays the SNASw port objects.
snasw rtp pathswitch-timers
To tune the RealTime Transport Protocol (RTP) pathswitch timers for an SNASwitch, use the snasw rtp pathswitch-timers command in global configuration mode. To restore the default settings for the RTP pathswitch timers, use the no form of this command.
snasw rtp pathswitch-timers low-priority medium-priority high-priority network-priority
no snasw rtp pathswitch-timers
Syntax Description
Defaults
low-priority: 480 seconds
medium-priority: 240 seconds
high-priority: 120 seconds
network-priority: 60 secondsCommand Modes
Global configuration
Command History
Usage Guidelines
The arguments for this command should be tuned to match the values specified at the other end of the RTP connection. This endpoint could be another SNA switch router or any other High-Performance Routing (HPR)-capable control point, which will most often be an IBM z/OStm mainframe. In this case, you should match the settings of the HPRPST start option.
The value for each pathswitch timer value must be greater than or equal to the value for the next highest priority timer argument. In other words, the low-priority argument >= medium-priority argument >= high-priority argument >= network-priority argument.
Examples
The following example tunes the RTP pathswitch timers:
router(config)# snasw rtp pathswitch-timers 160 80 40 20snasw start arbdata
To start the collection of adaptive rate-based (ARB) algorithm data for a particular Rapid Transport Protocol (RTP) connection, use the snasw start arbdata command in privileged EXEC mode.
snasw start arbdata local-tcid
Syntax Description
Defaults
No default behaviors or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command to start the writing of ARB data debug messages (for the RTP specified by local-tcid) to the router log. ARB data is particularly useful for tracking down RTP performance problems, but it can generate a very large number of log entries. For this reason it should be started only when you have already configured the commands no logging console debug and logging buffered debug (with a buffer size large enough so that the required data is does not overflow). You can collect data for more than one RTP at the same time by issuing this command once for each desired RTP local tcid. You can stop the ARB debug data messages for a particular RTP connection by issuing the snasw stop arbdata command.
Examples
The following is an example of the snasw start arbdata command:
Router# snasw start arbdata 000000000500045ARelated Commands
show snasw rtp
Displays the local tcid for each RTP connection.
snasw stop arbdata
Stops the collection of ARB algorithm data for a specific RTP connection.
snasw start cp-cp
To initiate a request to start control point (CP)-CP sessions with a partner CP, use the snasw start cp-cp command in privileged EXEC mode.
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
12.0(5)XN
This command was introduced.
12.0(7)T
This command was integrated into Cisco IOS Release 12.0 T.
Usage Guidelines
Use the snasw start cp-cp command if CP-CP sessions fail permanently or temporarily, but beyond the time frame 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.
Typically, Switching Services (SNASw) automatically activates CP-CP sessions as necessary and the snasw start cp-cp command is rarely needed. Frequent CP-CP session failure beyond the time frame for automatic session retry indicates a problem, and should be reported.
Examples
The following is an example of the snasw start cp-cp command:
Router# snasw start cp-cp NETA.CMCHOSTRelated Commands
snasw start
To start Switching Services (SNASw), use the snasw start command in privileged EXEC mode.
snasw start
Syntax Description
This command has no arguments or keywords.
Defaults
No default behaviors or values
Command Modes
Privileged EXEC
Command History
12.0(5)XN
This command was introduced.
12.0(7)T
This command was integrated into Cisco IOS Release 12.0 T.
Usage Guidelines
If not enough memory exists to start SNASw, a message indicating lack of memory is issued. A control point (CP) name must be configured with the snasw cpname command before SNASw will start.
Examples
The following is an example of the snasw start command:
Router# snasw startRelated Commands
show snasw node
Displays details and statistics of the SNASw operation.
snasw stop
Shuts down SNASw.
snasw start link
To start an inactive defined link, use the snasw start link command in privileged EXEC mode.
snasw start link linkname
Syntax Description
Defaults
No default behaviors or values
Command Modes
Privileged EXEC
Command History
12.0(5)XN
This command was introduced.
12.0(7)T
This command was integrated into Cisco IOS Release 12.0 T.
Usage Guidelines
Use the snasw start link command to initiate a connection sequence for a link that is defined but not active. Unless the nostart command 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:
Router# snasw start link CMCHOST1Related Commands
show snasw link
Displays the Switching Services (SNASw) link objects.
snasw stop link
Stops an active link.
snasw start port
To start an inactive port, use the snasw start port command in privileged EXEC mode.
snasw start port portname
Syntax Description
Defaults
No default behaviors or values
Command Modes
Privileged EXEC
Command History
12.0(5)XN
This command was introduced.
12.0(7)T
This command was integrated into Cisco IOS Release 12.0 T.
Usage Guidelines
Use the snasw start port command to enable a port that is defined to the configuration but is not active. Unless the nostart command 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:
Router# snasw start port TOKEN0Related Commands
show snasw port
Displays the Switching Services (SNASw) port objects.
snasw stop port
Stops an active port.
snasw stop
To shut down Switching Services (SNASw), use the snasw stop command in privileged EXEC mode.
snasw stop
Syntax Description
This command has no arguments or keywords.
Defaults
No default behaviors or values
Command Modes
Privileged EXEC
Command History
12.0(5)XN
This command was introduced.
12.0(7)T
This command was integrated into Cisco IOS Release 12.0 T.
Usage Guidelines
Use the snasw stop command to terminate all sessions, stop all ports and links, and shut down SNASw. When you enter this command, you are prompted for confirmation.
Examples
The following is an example of the snasw stop command:
Router# snasw stopRelated Commands
snasw stop arbdata
To stop the collection of adaptive rate-based (ARB) algorithm data for a particular Rapid Transport Protocol (RTP) connection, use the snasw stop arbdata command in privileged EXEC mode.
snasw stop arbdata local-tcid
Syntax Description
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command to stop the writing of ARB data debug messages (for the RTP specified by local-tcid) to the router log. ARB data is particularly useful for tracking down RTP performance problems. Once you have stopped the ARB data messages, you can run the show logging command in privileged EXEC mode to dump them for Cisco customer assistance to evaluate.
Examples
The following is an example of the snasw stop arbdata command:
Router# snasw stop arbdata 000000000500045ARelated Commands
show logging
Shows the contents of the standard system logging message buffer.
show snasw rtp
Displays the local tcid for each RTP connection.
snasw stop cp-cp
To terminate control point (CP)-CP sessions with a partner CP, use the snasw stop cp-cp command in privileged EXEC mode.
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
12.0(5)XN
This command was introduced.
12.0(7)T
This command was integrated into Cisco IOS Release 12.0 T.
Usage Guidelines
If the primary National Number (NN) server (uplink) fails, CP-CP sessions are established with a backup, if one is available. When the link to the primary recovers, Switching Services (SNASw) retains the CP-CP sessions established with the backup and does not automatically switch back to the primary. To force SNASw to switch back to the primary, use the snasw stop cp-cp command. (If the link to the backup fails, SNASw does switch back to the primary automatically.)
You can also use the snasw stop cp-cp command to clear some fault scenarios, such as hung or nonresponsive CP sessions, allowing the Systems Network Architecture (SNA) switch to potentially restart sessions with the same or alternate destination logical unit (LU).
Examples
The following is an example of the snasw stop cp-cp command:
Router# snasw stop cp-cp NETA.CMCHOSTRelated Commands
snasw start cp-cp
Initiates a request to start CP-CP sessions with a partner CP.
snasw stop link
To stop an active link, use the snasw stop link command in privileged EXEC mode.
snasw stop link linkname
Syntax Description
Defaults
No default behaviors or values
Command Modes
Privileged EXEC
Command History
12.0(5)XN
This command was introduced.
12.0(7)T
This command was integrated into Cisco IOS Release 12.0 T.
Usage Guidelines
Use the snasw stop link command to deactivate a link to a specified partner control point (CP). All High-Performance Routing (HPR) sessions established using the link are disconnected. HPR sessions are disrupted only if no alternate route is available.
Normally a link stopped with the snasw stop link command must be restarted by issuing the snasw start link command. However, it will be automatically restarted under the following conditions:
•
•
Examples
The following is an example of the snasw stop link command:
Router# snasw stop link CMCHOST1Related Commands
snasw stop port
To stop an active port, use the snasw stop port command in privileged EXEC mode.
snasw stop port portname
Syntax Description
Defaults
No default behaviors or values
Command Modes
Privileged EXEC
Command History
12.0(5)XN
This command was introduced.
12.0(7)T
This command was integrated into Cisco IOS Release 12.0 T.
Usage Guidelines
Use the snasw stop port command to disable a specified port without removing it from the configuration. All High-Performance Routing (HPR) sessions established using the port and all links are shut down on the port. HPR sessions are disrupted only if no alternate route is available.
Examples
The following is an example of the snasw stop port command:
Router# snasw stop port TOKEN0Related Commands
snasw stop session
To terminate an active session, use the snasw stop session command in privileged EXEC mode.
snasw stop session pcid
Syntax Description
Defaults
No default behaviors or values
Command Modes
Privileged EXEC
Command History
12.0(5)XN
This command was introduced.
12.0(7)T
This command was integrated into Cisco IOS Release 12.0 T.
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.
You can also use the snasw stop session command to free a small amount of memory if the session is no longer being used to transport data and you do not expect to use the session later.
Examples
The following is an example of the snasw stop session command:
Router# snasw stop session C3BBD36EA9CBA1AFRelated Commands
source-bridge cos-enable
To force the Cisco IOS software to read the contents of the format identification (FID) frames to prioritize traffic when using TCP, use the source-bridge cos-enable command in global configuration mode. To disable prioritizing, use the no form of this command.
source-bridge cos-enable
no source-bridge cos-enable
Syntax Description
This command has no arguments or keywords.
Defaults
Enabled
Command Modes
Global configuration
Command History
Usage Guidelines
Use this command to prioritize your Systems Network Architecture (SNA) traffic across the backbone network. All your important front-end processor (FEP) traffic can flow on high-priority queues. This is useful only between FEP-to-FEP (physical unit [PU] 4-to-PU 4) communications (across the non-SNA backbone).
Note
Examples
The following example enables CoS for prioritization of SNA traffic across a network:
source-bridge cos-enableRelated Commands
source-bridge remote-peer tcp
Identifies the IP address of a peer in the ring group with which to exchange source-bridge traffic using TCP.
source-bridge fst-peername
To set up a Fast-Sequenced Transport (FST) peer name, use the source-bridge fst-peername command in global configuration mode. To disable the IP address assignment, use the no form of this command.
source-bridge fst-peername local-interface-address
no source-bridge fst-peername local-interface-address
Syntax Description
Defaults
Disabled
Command Modes
Global configuration
Command History
Usage Guidelines
This command is the first step to configuring a remote source-route bridge to use FST.
Examples
The following example sets up an FST peer name:
source-bridge fst-peername 10.136.64.98Related Commands
source-bridge keepalive
To assign the keepalive interval of the remote source-bridging peer, use the source-bridge keepalive command in interface configuration mode. To cancel previous assignments, use the no form of this command.
source-bridge keepalive seconds
no source-bridge keepalive
Syntax Description
seconds
Keepalive interval in seconds. The valid range is from 10 to 300. The default value is 30 seconds.
Defaults
30 seconds
Command Modes
Interface configuration
Command History
Examples
The following example sets the keepalive interval to 60 seconds:
source-bridge keepalive 60Related Commands
source-bridge largest-frame
To configure the largest frame size that is used to communicate with any peers in the ring group, use the source-bridge largest-frame command in global configuration mode. To cancel previous assignments, use the no form of this command.
source-bridge largest-frame ring-group size
no source-bridge largest-frame ring-group
Syntax Description
Defaults
No frame size is assigned.
Command Modes
Global configuration
Command History
Usage Guidelines
The Cisco IOS software negotiates all transit routes down to the specified size or lower. Use the size argument with this command to prevent timeouts in end hosts by reducing the amount of data they must send in a fixed interval. For example, in some networks containing slow links, it would be impossible to send an 8-KB frame and receive a response within a few seconds. These are standard defaults for an application on a 16-Mb Token Ring. If the frame size is lowered to 516 bytes, then only 516 bytes must be sent and a response received in 2 seconds. This feature is most effective in a network with slow links. The legal values for this argument are 516, 1500, 2052, 4472, 8144, 11407, and 17800 bytes.
Examples
The following example sets the largest frame that can be sent through a ring group to 1500 bytes:
source-bridge largest-frame 8 1500Related Commands
source-bridge ring-group
Defines or removes a ring group from the configuration.
source-bridge passthrough
To configure some sessions on a few rings to be locally acknowledged and the remaining to pass through, use the source-bridge passthrough command in global configuration mode. To disable passthrough on all the rings and allow the session to be locally acknowledged, use the no form of this command.
source-bridge passthrough ring-group
no source-bridge passthrough ring-group
Syntax Description
Defaults
Disabled
Command Modes
Global configuration
Command History
Usage Guidelines
Use this command in conjunction with the source-bridge remote-peer tcp command that has the local-ack keyword specified, which causes every new Logical Link Control, type 2 (LLC2) session to be locally terminated. If a machine on the Token Ring attempts to start an LLC2 session to an end host that exists on the ring-group value specified in the source-bridge passthrough command, the session will "pass through" and not use local acknowledgment for LLC2.
If you specify pass through for a ring, LLC2 sessions will never be locally acknowledged on that ring. This is true even if a remote peer accessing the ring has set the local-ack keyword in the source-bridge remote-peer tcp command. The source-bridge passthrough command overrides any setting in the source-bridge remote-peer tcp command.
You can define more than one source-bridge passthrough command in a configuration.
Examples
The following example configures the router to use local acknowledgment on remote peer at 10.1.1.2 but pass through on rings 9 and 4:
source-bridge ring-group 100source-bridge remote-peer 100 tcp 10.1.1.1source-bridge remote-peer 100 tcp 10.1.1.2 local-acksource-bridge passthrough 9source-bridge passthrough 4Related Commands
source-bridge qllc-local-ack
To enable or disable Qualified Logical Link Control (QLLC) local acknowledgment for all QLLC conversion connections, use the source-bridge qllc-local-ack command in global configuration mode. To disable this capability, use the no form of this command.
source-bridge qllc-local-ack
no source-bridge qllc-local-ack
Syntax Description
This command has no arguments or keywords.
Defaults
QLLC local acknowledgment is disabled.
Command Modes
Global configuration
Command History
Usage Guidelines
In a remote source-route bridged topology, QLLC local acknowledgment is used to configure the QLLC conversion router (connecting the remote X.25 devices) to exchange local acknowledgment information with the Token Ring router (on the Token Ring side of the cloud). This Token Ring device has been configured for Logical Link Control, type 2 (LLC2) local acknowledgment using the source-bridge remote-peer tcp local-ack command.
You must issue the source-bridge qllc-local-ack command only on the QLLC conversion router. When this command is issued, all of the QLLC conversion sessions are locally acknowledged at the Token Ring interface of the Token Ring router with which it is communicating using QLLC conversion.
Examples
The following configuration indicates that the local router (10.108.2.2) QLLC conversion sessions will be locally acknowledged at the remote router:
source-bridge ring-group 100source-bridge remote-peer 100 tcp 10.108.1.1 local-acksource-bridge remote-peer 100 tcp 10.108.2.2source-bridge qllc-local-ackRelated Commands
source-bridge remote-peer frame-relay
To specify a point-to-point direct encapsulation connection, use the source-bridge remote-peer frame-relay command in global configuration mode. To disable previous interface assignments, use the no form of this command.
source-bridge remote-peer ring-group frame-relay interface name number [mac-address] [dlci-number] [lf size]
no source-bridge remote-peer ring-group frame-relay interface name number
Syntax Description
Defaults
No point-to-point direct encapsulation connection is specified.
Command Modes
Global configuration
Command History
Usage Guidelines
Use this command to identify the interface over which to send source-route bridged traffic to another router in the ring group. A serial interface does not require that you include a MAC-level address; all other types of interfaces do require MAC addresses.
You must specify one source-bridge remote-peer command for each peer router that is part of the virtual ring. You must also specify one source-bridge remote-peer command to identify the IP address of the local router.
It is possible to mix all types of transport methods within the same ring group.
Note
Examples
The following example sends source-route bridged traffic over serial interface 0 and Ethernet interface 0:
! send source-route bridged traffic over serial 0source-bridge remote-peer 5 frame-relay interface serial 0! specify MAC address for source-route bridged traffic on Ethernet 0source-bridge remote-peer 5 interface Ethernet 0 0000.0c00.1234Related Commands
source-bridge remote-peer fst
To specify a Fast-Sequenced Transport (FST) encapsulation connection, use the source-bridge remote-peer fst command in global configuration mode. To disable the previous assignments, use the no form of this command.
source-bridge remote-peer ring-group fst ip-address [lf size]
no source-bridge remote-peer ring-group fst ip-address
Syntax Description
Defaults
No FST encapsulation connection is specified.
Command Modes
Global configuration
Command History
Usage Guidelines
The two peers using the serial-transport method will function correctly only if there are routers at the end of the serial line that have been configured to use the serial transport. The peers must also belong to the same ring group.
You must specify one source-bridge remote-peer command for each peer router that is part of the virtual ring. You must also specify one source-bridge remote-peer command to identify the IP address of the local router.
Examples
In the following example, the source-bridge-fst-peername command specifies an IP address of 10.136.64.98 for the local router. The source-bridge ring-group command assigns the device to a ring group. The source-bridge remote-peer fst command specifies ring group number 100 for the remote peer at IP address 10.136.64.97.
source-bridge fst-peername 10.136.64.98 source-bridge ring-group 100 source-bridge remote-peer 100 fst 10.136.64.97source-bridge remote-peer interface
When specifying a point-to-point direct encapsulation connection, use the source-bridge remote-peer interface command in global configuration mode. To disable previous interface assignments, use the no form of this command.
source-bridge remote-peer ring-group interface name number [mac-address] [lf size]
no source-bridge remote-peer ring-group interface name number
Syntax Description
Defaults
No point-to-point direct encapsulation connection is specified.
Command Modes
Global configuration
Command History
Usage Guidelines
Use this command to identify the interface over which to send source-route bridged traffic to another router or bridge in the ring group. A serial interface does not require that you include a MAC-level address; all other types of interfaces do require MAC addresses.
It is possible to mix all types of transport methods within the same ring group.
Note
Examples
The following example shows how to send source-route bridged traffic over serial interface 0 and Ethernet interface 0:
! send source-route bridged traffic over serial 0source-bridge remote-peer 5 interface serial 0! specify MAC address for source-route bridged traffic on Ethernet 0source-bridge remote-peer 5 interface ethernet 0 0000.0c00.1234Related Commands
source-bridge remote-peer tcp
To identify the IP address of a peer in the ring group with which to exchange source-bridge traffic using TCP, use the source-bridge remote-peer tcp command in global configuration mode. To remove a remote peer for the specified ring group, use the no form of this command.
source-bridge remote-peer ring-group tcp ip-address [lf size] [tcp-receive-window wsize] [local-ack] [priority]
no source-bridge remote-peer ring-group tcp ip-address
Syntax Description
Defaults
No IP address is identified.
The default window size is 10240 bytes.
Command Modes
Global configuration
Command History
10.0
This command was introduced.
11.1
The tcp-receive-window keyword was added.
Usage Guidelines
If you change the default TCP receive window size on one peer, you must also change the receive window size on the other peer. Both sides of the connection should have the same window size.
If you configure one peer for LLC2 local acknowledgment, you need to configure both peers for LLC2 local acknowledgment. If only one peer is so configured, unpredictable results occur.
You must specify one source-bridge remote-peer command for each peer router that is part of the virtual ring. You must also specify one source-bridge remote-peer command to identify the IP address of the local router.
The two peers using the serial-transport method will function correctly only if there are routers at the end of the serial line that have been configured to use the serial transport. The peers must also belong to the same ring group.
Examples
In the following example, the remote peer with IP address 10.108.2.291 belongs to ring group 5. It also uses LLC2 local acknowledgment, priority, and remote source-route bridging (RSRB) protocol version 2:
! identify the ring group as 5source-bridge ring-group 5! remote peer at IP address 10.108.2.291 belongs to ring group 5, uses! tcp as the transport, is set up for local acknowledgment, and uses prioritysource-bridge remote-peer 5 tcp 10.108.2.291 local-ack priorityThe following example shows how to locally administer and acknowledge LLC2 sessions destined for a specific remote peer:
! identify the ring group as 100source-bridge ring-group 100! remote peer at IP address 10.1.1.1 does not use local acknowledgmentsource-bridge remote-peer 100 tcp 10.1.1.1! remote peer at IP address 10.1.1.2 uses local acknowledgmentsource-bridge remote-peer 100 tcp 10.1.1.2 local-ack!interface tokenring 0source-bridge 1 1 100Sessions between a device on Token Ring 0 that must go through remote peer 10.1.1.2 use local acknowledgment for LLC2, but sessions that go through remote peer 10.1.1.1 do not use local acknowledgment (that is, they "pass through").
Related Commands
source-bridge sdllc-local-ack
To activate local acknowledgment for SDLC Logical Link Control. Cisco (SDLLC) sessions on a particular interface, use the source-bridge sdllc-local-ack command in global configuration mode. To deactivate local acknowledgment for SDLLC sessions, use the no form of this command.
source-bridge sdllc-local-ack
no source-bridge sdllc-local-ack
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Global configuration
Command History
Usage Guidelines
This command must be issued only on a router with a serial interface. Once the command is issued, all SDLLC sessions between the two devices will be locally acknowledged. You cannot selectively choose which SDLLC sessions are to be locally acknowledged and which are not. Also, local acknowledgment is not supported when the Logical Link Control, type 2 (LLC2) station is attached to Ethernet rather than to Token Ring.
Note
Examples
The following example activates local acknowledgment for SDLLC sessions:
source-bridge ring-group 100source-bridge remote-peer 100 tcp 10.108.1.1 local-acksource-bridge remote-peer 100 tcp 10.108.2.2source-bridge sdllc-local-acksource-bridge tcp-queue-max
To modify the size of the backup queue for remote source-route bridging, use the source-bridge tcp-queue-max command in global configuration mode. To return to the default value, use the no form of this command.
source-bridge tcp-queue-max number
no source-bridge tcp-queue-max
Syntax Description
number
Number of packets to hold in any single outgoing TCP queue to a remote router. The default is 100 packets.
Defaults
The default number of packets is 100.
Command Modes
Global configuration
Command History
Usage Guidelines
This backup queue determines the number of packets that can wait for transmission to a remote ring before packets start being thrown away.
Examples
If, for example, your network experiences temporary bursts of traffic using the default packet queue length, the following command raises the limit from 100 to 150 packets:
source-bridge tcp-queue-max 150state-tracks-signal
To allow the channel interface state to track the state of the physical interface signal on a Channel Port Adapter (CPA), use the state-tracks-signal command in interface configuration mode. To disable tracking of the physical interface signal on a CPA interface, use the no form of this command.
state-tracks-signal
no state-tracks-signal
Syntax Description
This command has no arguments or keywords.
Defaults
The physical interface signal is not tracked.
Command Modes
Interface configuration
Command History
Usage Guidelines
The state-tracks-signal command is useful in environments where you are using Hot Standby Router Protocol (HSRP) or Simple Network Management Protocol (SNMP) alerts to monitor channel interface status.
The state-tracks-signal command is valid only on channel interfaces which combine the functions of both a physical and virtual interface. The ESCON Channel Port Adapter (ECPA) and Parallel Channel Port Adapter (PCPA) are examples of this type of channel interface. The command is not valid for the Channel Interface Processor (CIP), which has a separate channel interface for the virtual channel functions.
When the state-tracks-signal command is used on an interface that has been started by the no shutdown command, then the state of the channel interface is reported according to the status of the physical channel interface signal. If the physical channel interface signal is not present, then the channel interface status is DOWN/DOWN.
When the no state-tracks-signal command is enabled on the channel interface (the default), and the interface has been started by the no shutdown command, the channel interface status is always reported as UP/UP, even when there is no signal present on the physical connection. This configuration is useful for TN3270 server environments that are operating in a mode without any physical channel interface connections.
Examples
The following example specifies that the channel interface state tracks the physical channel interface signal and reports the channel interface state according to the presence or absence of the physical interface signal when the interface has been started by the no shutdown command:
interface channel 5/0state-tracks-signalstun group
To place each serial tunnel (STUN)-enabled interface on a router in a previously defined STUN group, use the stun group command in interface configuration mode. To remove an interface from a group, use the no form of this command.
stun group group-number
no stun group group-number
Syntax Description
Defaults
Disabled
Command Modes
Interface configuration
Command History
Usage Guidelines
Before using this command, perform the following steps:
•
•
•
Packets only travel between STUN-enabled interfaces that are in the same group. Once a given serial link is configured for the STUN function, it is no longer a shared multiprotocol link. All traffic that arrives on the link is transported to the corresponding peer as determined by the current STUN configuration.
Examples
The following example places serial interface 0 in STUN group 2, which is defined to run the Synchronous Data Link Control (SDLC) transport:
! sample stun peer-name global commandstun peer-name 10.108.254.6! sample protocol-group command telling group 2 to use the SDLC protocolstun protocol-group 2 sdlc!interface serial 0! sample ip address subcommandno ip address! sample encapsulation stun subcommandencapsulation stun! place interface serial0 in previously defined STUN group 2stun group 2! enter stun route commandstun route 7 tcp 10.108.254.7Related Commands
stun keepalive-count
To define the number of times to attempt a peer connection before declaring the peer connection to be down, use the stun keepalive-count command in global configuration mode. To cancel the definition, use the no form of this command.
stun keepalive-count count
no stun keepalive-count
Syntax Description
Defaults
No default behavior or values
Command Modes
Global configuration
Command History
Examples
The following example sets the number of times to retry a connection to a peer to 4:
stun keepalive-count 4Related Commands
stun peer-name
To enable serial tunnel (STUN) for an IP address, use the stun peer-name command in global configuration mode. To disable STUN for an IP address, use the no form of this command.
stun peer-name ip-address cls
no stun peer-name ip-address cls
Syntax Description
ip-address
IP address by which this STUN peer is known to other STUN peers.
cls
Use Cisco Link Services (CLS) to access the Frame Relay network.
Defaults
STUN is disabled.
Command Modes
Global configuration
Command History
Usage Guidelines
Use this command to enable any further STUN features. After using this command, perform the following steps:
•
•
•
Examples
The following example assigns IP address 10.108.254.6 as the STUN peer:
stun peer-name 10.108.254.6 clsRelated Commands
stun protocol-group
To create a protocol group, use the stun protocol-group command in global configuration mode. To remove an interface from the group, use the no form of this command.
stun protocol-group group-number {basic | sdlc [sdlc-tg] | schema}
no stun protocol-group
Syntax Description
Defaults
No protocol group established.
Command Modes
Global configuration
Command History
Usage Guidelines
Use the sdlc keyword to specify an SDLC protocol. You must specify either the sdlc or the sdlc-tg keyword before you can enable SDLC local acknowledgment. SDLC local acknowledgment is established with the stun route address tcp command.
Use the basic keyword to specify a non-SDLC protocol, such as high-level data link control (HDLC).
Use the schema keyword to specify a custom protocol. The custom protocol must have been previously created with the stun schema command.
Use the optional sdlc-tg keyword, in conjunction with the sdlc keyword, to establish an SNA TG. A TG is a set of protocol groups providing parallel links to the same pair of IBM establishment controllers. This provides redundancy of paths. In case one or more links go down, an alternate path will be used. All serial tunnel (STUN) connections in a TG must connect to the same IP address. SDLC local acknowledgment must be enabled.
Note
Examples
The following example specifies that group 7 will use the Synchronous Data Link Control (SDLC) STUN protocol to route frames within that group:
stun protocol-group 7 sdlcThe following example specifies that group 5 use the basic protocol, wherein the serial addressing is unimportant and you have a point-to-point link:
stun protocol-group 5 basicRelated Commands
stun quick-response
To enable serial tunnel (STUN) quick-response, which can be used with local acknowledgment, use the stun quick-response command in global configuration mode. To disable STUN quick-response, use the no form of this command.
stun quick-response
no stun quick-response
Syntax Description
This command has no arguments or keywords.
Defaults
STUN quick-response is disabled.
Command Modes
Global configuration
Command History
Usage Guidelines
This command is used with local acknowledgment (local ack).
When STUN quick-response is enabled, the router responds to an exchange identification (XID) or a Set Normal Response Mode (SNRM) request with a Disconnect Mode (DM) response when the device is not in the CONNECT state. The request is then passed to the remote router and, if the device responds, the reply is cached. The next time the device is sent an XID or SNRM, the router replies with the cached DM response.
Note
Examples
The following example enables STUN quick-response:
stun quick-responseRelated Commands
stun remote-peer-keepalive
To enable detection of the loss of a peer, use the stun remote-peer-keepalive command in global configuration mode. To disable detection, use the no form of this command.
stun remote-peer-keepalive seconds
no stun remote-peer-keepalive
Syntax Description
seconds
Keepalive interval, in seconds. The range is from 1 to 300 seconds. The default is 30 seconds.
Defaults
30 seconds
Command Modes
Global configuration
Command History
Examples
In the following example, the remote peer keepalive interval is set to 60 seconds:
stun remote-peer-keepalive 60Related Commands
stun keepalive-count
Defines the number of times to attempt a peer connection before declaring the peer connection to be down.
stun route address interface dlci
To configure direct Frame Relay encapsulation between serial tunnel (STUN) peers with Synchronous Data Link Control (SDLC) local acknowledgment, use the stun route address interface dlci command in interface configuration mode. To disable the configuration, use the no form of this command.
stun route address sdlc-addr interface frame-relay-port dlci number localsap local-ack cls
no stun route address sdlc-addr interface frame-relay-port dlci number localsap local-ack cls
Syntax Description
Defaults
The configuration is disabled.
Command Modes
Interface configuration
Command History
Examples
The following command enables Frame Relay encapsulation between STUN peers with SDLC local acknowledgment:
stun route address c1 interface serial1 dlci 22 04 local-ackRelated Commands
stun route all interface serial
Encapsulates and forwards all STUN traffic using high-level data link control (HDLC) encapsulation on a serial interface.
stun route address interface serial
To forward all high-level data link control (HDLC) traffic on a serial interface, use the stun route address interface serial command in interface configuration mode. To disable this method of HDLC encapsulation, use the no form of this command.
stun route address address-number interface serial number [direct]
no stun route address address-number interface serial number
Syntax Description
address-number
Address of the serial interface.
number
Number assigned to the serial interface.
direct
(Optional) Forwards all HDLC traffic on a direct serial tunnel (STUN) link.
Defaults
The configuration is disabled.
Command Modes
Interface configuration
Command History
Examples
In the following example, serial frames with a STUN route address of 4 are forwarded through serial interface 0 using HDLC encapsulation:
stun route address 4 interface serial 0In the following example, serial frames with STUN route address 4 are propagated through serial interface 0 using STUN encapsulation:
stun route address 4 interface serial 0 directRelated Commands
stun route all interface serial
Encapsulates and forwards all STUN traffic using HDLC encapsulation on a serial interface.
stun route address tcp
To specify TCP encapsulation and optionally establish Synchronous Data Link Control (SDLC) local acknowledgment (SDLC transport) for serial tunnel (STUN), use the stun route address tcp command in interface configuration mode. To disable this method of TCP encapsulation, use the no form of this command.
stun route address address-number tcp ip-address [local-ack] [priority] [tcp-queue-max] [passive]
no stun route address address-number tcp ip-address [local-ack] [priority] [tcp-queue-max] [passive]
Syntax Description
Defaults
TCP encapsulation is not established; TCP queue size default is 100.
Command Modes
Interface configuration
Command History
10.0
This command was introduced.
11.1
The tcp-queue-max keyword was added.
12.0
The passive keyword was added.
Usage Guidelines
SDLC transport participates in SDLC windowing and resending through support of local acknowledgment. SDLC sessions require that end nodes send acknowledgments for a set amount of data frames received before allowing further data to be sent. Local acknowledgment provides local termination of the SDLC session, so that control frames no longer travel the WAN backbone networks. This means that end nodes do not time out, and a loss of sessions does not occur.
Examples
In the following example, a frame with a source-route address of 10 is propagated using TCP encapsulation to a device with an IP address of 10.108.8.1:
stun route address 10 tcp 10.108.8.1Related Commands
stun route all interface serial
To encapsulate and forward all serial tunnel (STUN) traffic using high-level data link control (HDLC) encapsulation on a serial interface, use the stun route all interface serial command in interface configuration mode. To disable this method of encapsulation, use the no form of this command.
stun route all interface serial number [direct]
no stun route all interface serial number [direct]
Syntax Description
number
Number assigned to the serial interface.
direct
(Optional) Indicates that the specified interface is also a direct STUN link, rather than a serial connection to another peer.
Defaults
No default behavior or values
Command Modes
Interface configuration
Command History
Usage Guidelines
An appropriately configured router must exist on the other end of the designated serial line. The outgoing serial link still can be used for other kinds of traffic (the frame is not TCP encapsulated). This mode is used when TCP/IP encapsulation is not needed or when higher performance is required. Enter the serial line number connected to the router for the number argument.
Examples
In the following example, all traffic on serial interface 0 is propagated using STUN encapsulation:
stun route all interface serial 0In the following example, serial interface 1 is a direct STUN link, not a serial connection to another peer:
stun route all interface serial 1 directRelated Commands
stun route address interface serial
Forwards all HDLC traffic on a serial interface.
stun route all tcp
To forward all serial tunnel (STUN) traffic on an interface regardless of which address is contained in the serial frame, use the stun route all tcp command in interface configuration mode with TCP encapsulation. To disable traffic from being forwarded with this method of encapsulation, use the no form of this command.
stun route all tcp ip-address [passive]
no stun route all tcp ip-address [passive]
Syntax Description
Defaults
Disabled
Command Modes
Interface configuration
Command History
Usage Guidelines
TCP/IP encapsulation allows movement of serial frames across arbitrary media types and topologies. This is particularly useful for building shared, multiprotocol enterprise network backbones.
Examples
In the following example, all STUN traffic received will be propagated through the bridge:
stun route all tcp 10.108.10.1stun schema offset length format
To define a protocol other than Synchronous Data Link Control (SDLC) for use with serial tunnel (STUN), use the stun schema offset length format command in global configuration mode. To disable the new protocol, use the no form of this command.
stun schema name offset constant-offset length address-length format format-keyword
no stun schema name offset constant-offset length address-length format format-keyword
Syntax Description
Defaults
No protocol is defined.
Command Modes
Global configuration
Command History
Usage Guidelines
Use this command before defining the protocol group (stun protocol-group command). The serial protocol you define must meet the following criteria:
•
•
•
•
Examples
In the following example, a protocol named new-sdlc is created. In the protocol frame structure, the constant offset is 0, the address length is 1 byte, and the address format is hexadecimal.
stun schema new-sdlc offset 0 length 1 format hexadecimalRelated Commands
priority-list protocol stun address
Establishes STUN queueing priorities based on the address of the serial link.
stun protocol-group
Creates a protocol group.
stun sdlc-role primary
To assign the router the role of Synchronous Data Link Control (SDLC) primary node, use the stun sdlc-role primary command in interface configuration mode. To disable the primary node role assignment, use the no form of this command.
stun sdlc-role primary
no stun sdlc-role
Syntax Description
This command has no arguments or keywords.
Defaults
No role is assigned.
Command Modes
Interface configuration
Command History
Usage Guidelines
Primary nodes poll secondary nodes in a predetermined order.
If the router is connected to a cluster controller, for example a 3x74, it should appear as a front-end processor (FEP) such as a 37x5, and must be assigned the role of a primary node.
Examples
The following example assigns the router the role of SDLC primary node:
stun sdlc-role primaryRelated Commands
stun sdlc-role secondary
To assign the router the role of Synchronous Data Link Control (SDLC) secondary node, use the stun sdlc-role secondary command in interface configuration mode. To disable the assignment, use the no form of this command.
stun sdlc-role secondary
no stun sdlc-role
Syntax Description
This command has no arguments or keywords.
Defaults
No secondary role is assigned.
Command Modes
Interface configuration
Command History
Usage Guidelines
Secondary nodes respond to polls sent by the SDLC primary by sending any outgoing data they may have.
If the router is connected to a front-end processor (FEP), for example a 37x5, it should appear as a cluster controller such as a 3x74, and must be assigned the role of a secondary node.
Examples
The following example assigns the router the role of SDLC secondary node:
stun sdlc-role secondaryRelated Commands
tcp-port
To override the default TCP port setting of 23, use the tcp-port command in TN3270 server, Dependent Logical Unit Requestor (DLUR) physical unit (PU), or PU configuration mode. To restore the default, use the no form of this command.
tcp-port port-number
no tcp-port
Syntax Description
port-number
A valid TCP port number in the range from 0 to 65534. The default is 23, which is the Internet Engineering Task Force (IETF) standard. The value 65535 is reserved by the TN3270 server.
Defaults
TN3270 server configuration mode: 23.
PU configuration mode: the value configured in TN3270 server configuration mode.
Command Modes
TN3270 server configuration
DLUR PU configuration
PU configuration
Command History
Usage Guidelines
The tcp-port command is valid only on the virtual channel interface, and it can be entered in either TN3270 server, DLUR PU or PU configuration mode. A value entered in TN3270 mode applies to all PUs for that TN3270 server, except as overridden by values entered in PU configuration mode. The tcp-port command affects only future TN3270 sessions.
The tcp-port command entered in DLUR PU configuration mode applies to all PUs defined under DLUR configuration mode.
The no tcp-port command entered in PU configuration mode removes the override. In this mode, the tcp-port command applies only to the specified PU.
Examples
The following example entered in TN3270 server configuration mode returns the TCP port value to 23:
no tcp-portRelated Commands
tg (CMPC)
To define Logical Link Control (LLC) connection parameters for the Cisco Multipath Channel (CMPC) transmission group, use the tg command in interface configuration mode. To remove the specified transmission group from the configuration, which also deactivates the transmission group, use the no form of this command.
tg tg-name llc token-adapter adapter-number lsap [rmac rmac] [rsap rsap]
no tg tg-name llc
Syntax Description
Defaults
The lsap and rsap values default to 04.
Command Modes
Interface configuration
Command History
Usage Guidelines
The tg (CMPC) command is valid only on the virtual channel interface. This command defines an LLC connection with a complete addressing 4-tuple. The lsap, rmac, and rsap arguments are specified explicitly by parameters. The lmac argument is the local MAC address of the adapter referred to by the type and adapter-number arguments.
To change any parameter of the tg (CMPC) command, first remove the existing TG by using the no tg command.
The no tg command removes the CMPC TG from the configuration. If the TG is used for a High-Performance Routing (HPR) connection, all sessions using the TG will be terminated immediately. If the TG is an HPR connection, all sessions using the TG will be terminated if no other HPR connection is available to the host.
Examples
The following example configures a TG name and includes values for the rmac and rsap arguments:
tg LAGUNAA llc token-adapter 1 18 rmac 4000.0000.beef rsap 14Related Commands
adapter
Configures internal adapters.
lan
Configures an internal LAN on a CMCC adapter interface and enters internal LAN configuration mode.
tg (CMPC+)
To define IP connection parameters for the Cisco Multipath Channel (CMPC+) transmission group, use the tg command in interface configuration mode. To remove the specified transmission group from the configuration and deactivate the transmission group, use the no form of this command.
tg tg-name {ip | hsas-ip} host-ip-addr local-ip-addr [broadcast]
no tg tg-name {ip | hsas-ip}
Syntax Description
Command Modes
Interface configuration
Command History
Usage Guidelines
The tg (CMPC+) command is valid only on the Channel Interface Processor (CIP)'s virtual channel interface and the Channel Port Adapter (CPA)'s physical channel interface. This command defines either an IP connection or an HSAS IP connection.
To change any parameter of the tg (CMPC+) command, first remove the existing TG must be removed first by using no tg name command. At a minimum, tg-name must be specified to avoid ambiguity.
The no tg command removes the CMPC+ TG from the configuration. All sessions using the TG are terminated immediately.
Examples
The following example configures a TG name for an HSAS stack configured with CMPC+:
interface Channel0/2ip address 10.12.165.1 255.255.255.0no ip redirectsno ip directed-broadcastip route-cache same-interfaceno ip mroute-cacheno keepalivetg TG00 hsas-ip 10.12.165.2 10.12.165.1The following example configures a TG name for an IP stack configured with CMPC+:
interface Channel0/2ip address 10.12.165.1 255.255.255.0no ip redirectsno ip directed-broadcastip route-cache same-interfaceno ip mroute-cacheno keepalivetg TG00 ip 10.12.165.2 10.12.165.1Related Commands
cmpc
Configures a CMPC (or CMPC+) read subchannel and a CMPC (or CMPC+) write subchannel.
tg delay
To configure the duration of time the router is to wait before ending an Multi-Path Channel (MPC) block and sending it to the host, use the tg delay command in interface configuration mode. To restore the default duration of time, use the no form of this command.
tg tg-name delay delay
no tg tg-name delay
Syntax Description
Defaults
10 milliseconds
Command Modes
Interface configuration
Command History
Usage Guidelines
By default, the tg delay command does not appear in the running configuration. It is displayed in the configuration only when configured for a nondefault value.
Examples
The following example configures a TG delay of 20 milliseconds:
router(config)# interface channel 0/2router(config-if)# tg TG00 delay 20The following example resets the TG delay to the default of 10 milliseconds:
router(config-if)# no tg TG00 delayRelated Commands
