-
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
enable (TN3270)
To turn on security in the TN3270 server, use the enable command in security configuration mode.
enable
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Security configuration
Command History
Usage Guidelines
There is not a no form for this command.
If the security command has been disabled, then issuing this command does not affect existing connections.
This command is not displayed in the show running-config command output because the security functionality is enabled by default.
Examples
The following example turns on security in the TN3270 server:
enableRelated Commands
security (TN3270)
Enables security on the TN3270 server.
disable (TN3270)
Turns off security in the TN3270 server.
encapsulation alc
To specify that the P1024B Airline Control (ALC) protocol will be used on the serial interface, use the encapsulation alc command in interface configuration mode. To remove ALC protocol handling from the serial interface, and return the default encapsulation high-level data link control (HDLC) to the interface, use the no form of this command.
encapsulation alc
no encapsulation alc
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Interface configuration
Command History
Usage Guidelines
The encapsulation alc command causes any agent-set control unit (ASCU) configuration to be removed from the interface. As each ASCU defined on the interface is removed it is also unlinked from the ASCU circuit it belongs to. All data frames queued for sending to the ASCU are destroyed.
This command must be entered prior to any ASCU configuration. Note that all timer and counter values are applicable to all ASCUs on the interface.
Examples
The following example specifies that the ALC protocol is used:
encapsulation alcRelated Commands
show interfaces
Displays statistics for the interfaces configured on a router or access server.
encapsulation bstun
To configure block serial tunnel (BSTUN) on a particular serial interface, use the encapsulation bstun command in interface configuration mode. To disable the BSTUN function on the interface, use the no form of this command.
encapsulation bstun
no encapsulation bstun
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Interface configuration
Command History
Usage Guidelines
The encapsulation bstun command must be configured on an interface before any further BSTUN or Bisync commands are configured for the interface.
You must use this command to enable BSTUN on an interface. Before using this command, perform the following two tasks:
•
Enable BSTUN on a global basis by identifying BSTUN on IP addresses. The command is bstun peer-name.
•
After using the encapsulation bstun command, use the bstun group command to place the interface in the previously defined protocol group.
Examples
The following example configures the BSTUN function on serial interface 0:
interface serial 0no ip addressencapsulation bstunRelated Commands
encapsulation sdlc
To configure an Synchronous Data Link Control (SDLC) interface, use the encapsulation sdlc command in interface configuration mode. To deactivate the command, use the no form of this command.
encapsulation sdlc
no encapsulation sdlc
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Interface configuration
Command History
Usage Guidelines
The encapsulation sdlc command must be used to configure an SDLC interface if you plan to implement data-link switching plus (DLSw+) or Frame Relay access support.
SDLC defines two types of network nodes: primary and secondary. Primary nodes poll secondary nodes in a predetermined order. Secondaries then send if they have outgoing data. When configured as primary and secondary nodes, Cisco routers are established as SDLC stations. Use the sdlc role interface configuration command to establish the role as primary or secondary.
In the IBM environment, a front-end processor (FEP) is the primary station and establishment controllers (ECs) are secondary stations. In a typical scenario, an EC may be connected to dumb terminals and to a Token Ring network at a local site. At the remote site, an IBM host connects to an IBM FEP, which can also have links to another Token Ring LAN. Typically, the two sites are connected through an SDLC leased line.
If a router is connected to an EC, it takes over the function of the FEP, and must therefore be configured as a primary SDLC station. If the router is connected to a FEP, it takes the place of the EC, and must therefore be configured as a secondary SDLC station.
Examples
The following example configures an SDLC interface:
interface serial 2/6no ip addressencapsulation sdlcRelated Commands
sdlc role
Establishes the router to be either a primary or secondary SDLC station.
encapsulation sdlc-primary
To configure the router as the primary Synchronous Data Link Control (SDLC) station if you plan to configure the SDLC Logical Link Control (SDLLC) media translation feature, use the encapsulation sdlc-primary command in interface configuration mode. To deactivate the command, use the no form of this command.
encapsulation sdlc-primary
no encapsulation sdlc-primary
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Interface configuration
Command History
Usage Guidelines
The encapsulation sdlc-primary or encapsulation sdlc-secondary command must be used to configure an SDLC interface. To use the encapsulation sdlc-primary command, first select the interface on which you want to enable SDLC. Then establish the router as a primary station. Next, assign secondary station addresses to the primary station using the sdlc address command.
SDLC defines two types of network nodes: primary and secondary. Primary nodes poll secondary nodes in a predetermined order. Secondaries then send if they have outgoing data. When configured as primary and secondary nodes, Cisco routers are established as SDLC stations.
In the IBM environment, a front-end processor (FEP) is the primary station and establishment controllers (ECs) are secondary stations. In a typical scenario, an EC may be connected to dumb terminals and to a Token Ring network at a local site. At the remote site, an IBM host connects to an IBM FEP, which can also have links to another Token Ring LAN. Typically, the two sites are connected through an SDLC leased line.
If a router is connected to an EC, it takes over the function of the FEP, and must therefore be configured as a primary SDLC station. If the router is connected to an FEP, it takes the place of the EC, and must therefore be configured as a secondary SDLC station.
Examples
The following example shows how to configure serial interface 0 on your router to allow two SDLC secondary stations to attach through a modem-sharing device (MSD) with addresses C1 and C2:
! enter a global command if you have not alreadyinterface serial 0encapsulation sdlc-primarysdlc address c1sdlc address c2Related Commands
encapsulation sdlc-secondary
To configure the router as a secondary Synchronous Data Link Control (SDLC) station if you plan to configure the SDLC Logical Link Control (SDLLC) media translation feature, use the encapsulation sdlc-secondary command in interface configuration mode. To deactivate the command, use the no form of this command.
encapsulation sdlc-secondary
no encapsulation sdlc-secondary
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Interface configuration
Command History
Usage Guidelines
An encapsulation sdlc-primary or encapsulation sdlc-secondary command must be used to configure an SDLC interface. To use the encapsulation sdlc-secondary command, select the interface on which you want to enable SDLC. Then establish the router as a secondary station. Next, assign secondary station addresses to the primary station using the sdlc address command.
SDLC defines two types of network nodes: primary and secondary. Primary nodes poll secondary nodes in a predetermined order. Secondaries then send if they have outgoing data. When configured as primary and secondary nodes, Cisco devices are established as SDLC stations.
In the IBM environment, a front-end processor (FEP) is the primary station and establishment controllers (ECs) are secondary stations. In a typical scenario, an EC may be connected to dumb terminals and to a Token Ring network at a local site. At the remote site, an IBM host connects to an IBM FEP, which can also have links to another Token Ring LAN. Typically, the two sites are connected through an SDLC leased line.
If a router is connected to an EC, it takes over the function of the FEP, and must therefore be configured as a primary SDLC station. If the router is connected to a FEP, it takes the place of the EC, and must therefore be configured as a secondary SDLC station.
Examples
The following example establishes the router as a secondary SDLC station:
interface serial 0encapsulation sdlc-secondaryRelated Commands
encapsulation stun
To enable serial tunnel (STUN) encapsulation on a specified serial interface, use the encapsulation stun command in interface configuration mode.
encapsulation stun
Syntax Description
This command has no arguments or keywords.
Defaults
STUN encapsulation is disabled.
Command Modes
Interface configuration
Command History
Usage Guidelines
Use this command to enable STUN on an interface. Before using this command, perform the following two tasks:
•
•
After using the encapsulation stun command, use the stun group command to place the interface in the previously defined protocol group.
To disable stun encapsulation, configure the default interface encapsulation using the encapsulation command and specify HDLC as the encapsulation type
There is not a no form for this command.
Examples
This partial configuration example shows how to enable serial interface 5 for STUN traffic:
! sample stun peer name and stun protocol-group global commandsstun peer-name 10.108.254.6stun protocol-group 2 sdlc!interface serial 5! sample ip address commandno ip address! enable the interface for STUN; must specify encapsulation stun! command to further configure the interfaceencapsulation stun! place interface serial 5 in previously defined STUN group 2stun group 2! enter stun route commandstun route 7 tcp 10.108.254.7Related Commands
encapsulation uts
To specify that the P1024C Universal Terminal Support (UTS) protocol will be used on the serial interface, use the encapsulation uts command in interface configuration mode. To remove P1024C UTS protocol handling from the serial interface and return the default encapsulation high-level data link control (HDLC) to the interface, use the no form of this command.
encapsulation uts
no encapsulation uts
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Interface configuration
Command History
Usage Guidelines
The encapsulation uts command causes any agent-set control unit (agent-set control unit (ASCU)) configuration to be removed from the interface. As each ASCU defined on the interface is removed it is also unlinked from the ASCU circuit it belongs to. All data frames queued for sending to the ASCU are destroyed.
This command must be entered prior to any ASCU configuration. Note that all timer and counter values are applicable to all ASCUs on the interface.
Examples
The following example specifies that the P1024C UTS protocol is used:
encapsulation utsRelated Commands
show interfaces
Displays statistics for all interfaces configured on a router or access server.
encryptorder
To specify the security encryption algorithm for the Secure Socket Layer (SSL) Encryption Support feature, use the encryptorder command in profile configuration mode.
encryptorder [RC4] [RC2] [RC5] [DES] [3DES]
Syntax Description
Defaults
The default encryption order is RC4, RC2, RC5, DES, 3DES for domestic software. The default encryption order is RC4, RC2, DES for exportable software.
Command Modes
Profile configuration
Command History
Usage Guidelines
There is not a no form for this command.
These algorithms may be entered in any order, but can be specified only once per encryptorder command.
Exportable versions of software cannot accept the 3DES or RC5 encryption algorithms.
Examples
The following example specifies RC4, DES, and RC2 as the encryption algorithms:
tn3270securityprofile DOMESTIC SSLencryptorder RC4 DES RC2exception slot
To provide a core dump of a Cisco Mainframe Channel Connection (CMCC) adapter, use the exception slot command in global configuration mode. To disable the core dump, use the no form of this command.
exception slot [slot] protocol://host/filename
no exception slot [slot] protocol://host/filename
Syntax Description
Defaults
No default behavior or values
Command Modes
Global configuration
Command History
Usage Guidelines
This command is supported only on the Cisco 7000 with RSP7000 and Cisco 7500 series routers.
You must configure FTP services on the router before you can create a CMCC adapter core dump.
Do not exceed your host limits on filename length. Two characters are added to the filename, slot, where slot is the slot number.
Examples
The following example shows how to configure a router to perform a CMCC adapter core dump. Assuming the Channel Interface Processor (CIP) is installed in slot 3, the filename cipdump.3 will be written to the host.
ip domain-name cisco.comip name-server 168.69.161.21ip ftp username tech1ip ftp password tech1exception slot ftp://168.18.2.196/cipdumpRelated Commands
frame-relay map bstun
To configure block serial tunnel (BSTUN) over Frame Relay for pass-through, use the frame-relay map bstun command in interface configuration mode. To cancel the configuration, use the no form of this command.
frame-relay map bstun dlci
no frame-relay map bstun dlci
Syntax Description
Defaults
No default behavior or values
Command Modes
Interface configuration
Command History
Usage Guidelines
Direct encapsulation over Frame Relay is supported only for an encapsulation type of cisco, configured using the encapsulation frame-relay command.
Examples
The following example maps BSTUN traffic to DLCI number 16:
frame-relay map bstun 16Related Commands
frame-relay map llc2
To configure block serial tunnel (BSTUN) over Frame Relay when using Bisync local acknowledgment, use the frame-relay map llc2 command in interface configuration mode. To cancel the configuration, use the no form of this command.
frame-relay map llc2 dlci
no frame-relay map llc2 dlci
Syntax Description
dlci
Frame Relay data-link connection identifier (DLCI) number on which to support local acknowledgment.
Defaults
No default behavior or values
Command Modes
Interface configuration
Command History
Usage Guidelines
Direct encapsulation over Frame Relay is supported only for an encapsulation type of cisco, configured using the encapsulation frame-relay command.
Examples
The following example maps BSTUN traffic to data-link connection identifier (DLCI) number 16:
frame-relay map dlci 16Related Commands
frame-relay map rsrb
To specify the data-link connection identifier (DLCI) number onto which the remote source-route bridging (RSRB) traffic is to be mapped, use the frame-relay map rsrb command in interface configuration mode. To cancel the RSRB map, use the no form of this command.
frame-relay map rsrb dlci
no frame-relay map rsrb
Syntax Description
Defaults
No default behavior or values
Command Modes
Interface configuration
Command History
Usage Guidelines
Direct encapsulation over Frame Relay is supported only for an encapsulation type of cisco, configured using the encapsulation frame-relay command.
Examples
The following example shows RSRB traffic mapped to DLCI number 30:
frame-relay map rsrb 30Related Commands
fras backup dlsw
To configure an auxiliary route between the end stations and the host for use as a backup when the data-link connection identifier (DLCI) connection to the Frame Relay network is lost, use the fras backup dlsw command in interface configuration mode. To cancel the backup configuration, use the no form of this command.
fras backup dlsw virtual-mac-address target-ring-number host-mac-address [retry retry-number]
no fras backup dlsw virtual-mac-address target-ring-number host-mac-address [retry retry-number]
Syntax Description
Defaults
Frame Relay access support (FRAS) dial backup over data-link switching plus (DLSw+) is disabled. The default number of retries is 5.
Command Modes
Interface configuration
Command History
Usage Guidelines
Configure DLSw+ as normally required. Specify the optional keyword dynamic at the end of the dlsw remote-peer configuration command to enable the peer relationship to be established only when needed (for example, when the fras backup dlsw command becomes active).
Examples
The following example configures FRAS dial backup over DLSw+:
fras backup dlsw 4000.1000.2000 200 1000.5aed.1f53Related Commands
fras ban
To associate bridging over a Frame Relay network using boundary access node (BAN), use the fras ban command in interface configuration mode. To cancel each association, use the no form of this command.
fras ban local-ring bridge-number ring-group ban-dlci-mac dlci dlci1 [dlci2 ... dlci5] [bni mac-addr]
no fras ban local-ring bridge-number ring-group ban-dlci-mac dlci dlci1 [dlci2 ... dlci5] [bni mac-addr]
Syntax Description
Defaults
No default behavior or values
Command Modes
Interface configuration
Command History
Usage Guidelines
Multiple fras ban commands may be configured; however, each fras ban command must use a unique DLCI MAC address.
You must configure the source-bridge ring-group command in global configuration mode prior to configuring the fras ban command.
Examples
The following example shows Frame Relay access support (FRAS) BAN support for Token Ring and serial interfaces:
source-bridge ring-group 200!interface serial 0mtu 4000encapsulation frame-relay ietfframe-relay lmi-type ansiframe-relay map llc2 16frame-relay map llc2 17fras ban 120 1 200 4000.1000.2000 dlci 16 17!interface tokenring 0source-bridge 100 5 200Related Commands
source-bridge ring-group
Defines or removes a ring group from the configuration.
fras ddr-backup
To configure an auxiliary interface for use as a backup when the primary Frame Relay link to the Frame Relay WAN fails, use the fras ddr-backup command in interface configuration mode. To cancel the backup configuration, use the no form of this command.
fras ddr-backup interface interface dlci-number
no fras ddr-backup
Syntax Description
interface interface
Interface over which the backup connection is made.
dlci-number
Data-link connection identifier (DLCI) number of the session.
Defaults
Frame Relay access support (FRAS) DLCI backup is disabled by default.
Command Modes
Interface configuration
Command History
Examples
The following example configures FRAS DLCI backup on serial interface 1:
fras ddr-backup interface serial 1 188Related Commands
fras map llc
To associate an Logical Link Control (LLC) connection with a Frame Relay data-link connection identifier (DLCI), use the fras map llc command in interface configuration mode. To disable the association, use the no form of this command.
fras map llc lan-lsap serial interface frame-relay dlci dlci fr-rsap
no fras map llc lan-lsap serial interface frame-relay dlci dlci fr-rsap
Syntax Description
Defaults
The default state is Frame Relay access support (FRAS) boundary network node (BNN) enhancement is disabled.
Command Modes
Interface configuration
Command History
Usage Guidelines
If the destination SAP specified by the end station is equal to the lan-lsap value, the router associates the LLC (LAN) connection with the Frame Relay DLCI.
The MAC address and the SAP address of the end station are no longer required for the BNN enhanced configuration.
Examples
In the FRAS BNN enhancement, the revised fras map llc command achieves the same result as using multiple fras map llc commands in the original FRAS BNN implementation. The following example provides one map definition for both end stations:
fras map llc 4 Serial 0 frame-relay dlci 16 04Related Commands
fras map sdlc
To associate an Synchronous Data Link Control (SDLC) link with a Frame Relay data-link connection identifier (DLCI), use the fras map sdlc command in interface configuration mode. To cancel the association, use the no form of this command.
fras map sdlc sdlc-address serial port frame-relay dlci fr-lsap fr-rsap [pfid2 | afid2 | fid4]
no fras map sdlc sdlc-address serial port frame-relay dlci fr-lsap fr-rsap [pfid2 | afid2 | fid4]
Syntax Description
Defaults
No default behavior or values
Command Modes
Interface configuration
Command History
Usage Guidelines
You can map multiple SDLC links to a DLCI.
Examples
The following example associates an SDLC link with a Frame Relay DLCI:
fras map sdlc c1 serial 0 frame-relay 200 4 4Related Commands
frame-relay map llc2
Configures block serial tunnel (BSTUN) over Frame Relay when using Bisync local acknowledgment.
fras-host ban
To enable the Frame Relay access support (FRAS) Host function for boundary access node (BAN), use the fras-host ban command in interface configuration mode. To disable the FRAS Host BAN functionality, use the no form of this command.
fras-host ban interface hmac hmac [bni bni]
no fras-host ban
Syntax Description
Defaults
The FRAS Host function for BAN is disabled for the Frame Relay subinterface.
The default bni value is 4FFF.0000.0000.
Command Modes
Interface configuration
Command History
Examples
The following example enables the FRAS Host function for BAN:
fras-host ban Serial0 hmac 4001.3745.0001Related Commands
fras-host bnn
To enable the Frame Relay access support (FRAS) Host function for boundary network node (BNN), use the fras-host bnn command in interface configuration mode. To disable the FRAS Host function, use the no form of this command.
fras-host bnn interface fr-lsap sap vmac virt-mac hmac hmac [hsap hsap]
no fras-host bnn
Syntax Description
Defaults
FRAS Host for BNN is disabled for the Frame Relay subinterface.
Command Modes
Interface configuration
Command History
Examples
The following example enables the FRAS Host function for BNN:
fras-host bnn Serial0 fr-lsap 04 vmac 4005.3003.0000 hmac 4001.3745.0001Related Commands
fras-host dlsw-local-ack
To enable Logical Link Control, type 2 (LLC2) local termination for Frame Relay access support (FRAS) Host connections using the virtual Token Ring, use the fras-host dlsw-local-ack command in interface configuration mode. To disable LLC2 local termination, use the no form of this command.
fras-host dlsw-local-ack
no fras-host dlsw-local-ack
Syntax Description
This command has no arguments or keywords.
Defaults
The default state is FRAS Host LLC2 local termination disabled.
Command Modes
Interface configuration
Command History
Examples
The following example enables LLC2 local termination for FRAS Host connections using the virtual Token Ring:
fras-host dlsw-local-ackRelated Commands
generic-pool
To specify whether leftover logical unit (LU)s will be made available to TN3270 sessions that do not request a specific LU or LU pool through TN3270E, use the generic-pool command in TN3270 server configuration mode. To selectively remove the permit or deny condition of generic pool use, use the no form of this command.
generic-pool {permit | deny}
no generic-pool
Syntax Description
Defaults
In TN3270 server configuration mode, generic pool use is permitted.
In PU configuration mode, the default is the value configured in TN3270 server configuration mode.
Command Modes
TN3270 server configuration
Listen-point configuration
Listen-point PU configuration
Dependent Logical Unit Requestor (DLUR) PU configuration
PU configurationCommand History
Usage Guidelines
This command is valid only on the virtual channel interface.
A leftover LU is defined as one for which all of the following conditions are true:
•
•
All LUs in the generic pool are, by definition, DDDLU capable.
Values entered for the generic-pool in the TN3270 server configuration mode apply to all PUs for that TN3270 server but can be changed in PU configuration mode.
In PU configuration mode, a no generic-pool command will restore the generic-pool value entered in TN3270 command mode.
In TN3270 server configuration mode, the no generic-pool command reverts to the default, which permits generic pool use.
The command takes effect immediately. If the generic-pool deny command is specified on a PU, no further dynamic connections to it will be allowed. Existing sessions are unaffected, but as they terminate the LUs will not become available for dynamic connections.
Similarly, if the generic-pool permit command is specified, any inactive LUs are immediately available for dynamic connections. Moreover, any active LUs that were dynamic previously (before the generic-pool deny command was issued) return to being dynamic.
Examples
The following example permits generic LU pool use:
generic-pool permitRelated Commands
client ip lu
Defines a specific LU or range of LUs to a client at the IP address or subnet.
idle-time
To specify seconds of logical unit (LU) inactivity, from both host and client, before the TN3270 session is disconnected, use the idle-time command in TN3270 server configuration mode. To cancel the idle time period and return to the default, use the no form of this command.
idle-time seconds
no idle-time
Syntax Description
seconds
Idle time in seconds, from 0 to 65535. A value of 0 means the session is never disconnected.
Defaults
The default in TN3270 server configuration mode is that the session is never disconnected (0).
The default in PU configuration mode is the value configured in TN3270 server configuration mode.
Command Modes
TN3270 server configuration
Listen-point configuration
Listen-point PU configuration
Dependent Logical Unit Requestor (DLUR) PU configuration
PU configurationCommand History
Usage Guidelines
The idle-time command is valid only on the virtual channel interface, and can be entered in either TN3270 server configuration mode 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.
A no idle-time command entered in PU configuration mode will restore the idle-time value entered in TN3270 command mode.
The idle-time command affects active and future TN3270 sessions. For example, if the idle-time value is reduced from 900 seconds to 600 seconds, sessions that have been idle for 600 to 900 seconds are immediately disconnected.
Note
In TN3270 server configuration mode, the idle-time command applies to all PUs supported by the TN3270 server.
In listen-point configuration mode, the idle-time command applies to all PUs defined at the listen point.
In listen-point PU configuration mode, the idle-time command applies only to the specified PU.
In DLUR PU configuration mode, the idle-time command applies to all PUs defined under DLUR configuration mode.
In PU configuration mode, the idle-time command applies only to the specified PU.
Examples
The following command sets an idle-time disconnect value of 10 minutes:
idle-time 600The following command entered in TN3270 server configuration mode sets the default idle-time disconnect value to 0, or never disconnect:
no idle-timeRelated Commands
interface channel
To specify a channel-attached interface and enter interface configuration mode, use the interface channel command in global configuration mode.
interface channel slot/port
Syntax Description
slot
Slot number where the Cisco Mainframe Channel Connection (CMCC) adapter is located. The slash mark is required.
port
Interface where the CMCC adapter is located.
Defaults
No default behavior or values
Command Modes
Global configuration
Command History
Examples
The following example shows how to enter interface configuration mode for a CIP in slot 2 and begin configuring port 0:
interface channel 2/0Related Commands
interface virtual-tokenring
To create a virtual Token Ring interface, use the interface virtual-tokenring command in interface configuration mode. To cancel the configuration, use the no form of this command.
interface virtual-tokenring number
no interface virtual-tokenring
Syntax Description
Defaults
No default behavior or values
Command Modes
Interface configuration
Command History
Examples
The following example configures the virtual Token Ring interface:
interface virtual-tokenring 0Related Commands
ip precedence (TN3270)
To specify the precedence level for voice over IP traffic in the TN3270 server, use the ip precedence command in TN3270 server configuration mode. To remove the precedence value, use the no form of this command.
ip precedence {screen | printer} value
no ip precedence {screen | printer}
Syntax Description
Defaults
The default is a precedence value of 0 for both screens and printers.
Command Modes
TN3270 server configuration
Listen-point configuration
Listen-point PU configuration
Dependent Logical Unit Requestor (DLUR) PU configuration
PU configurationCommand History
Usage Guidelines
This command is valid only on the virtual channel interface. Precedence values applied in TN3270 PU configuration mode override values applied in TN3270 server configuration mode.
You can enter new or different values for IP precedence without first using the no form of this command.
During initial Telnet negotiations to establish, or bind, the session an IP precedence value of 0 and IP ToS value of 0 is used. These values are used until the bind takes place. When the session is a type 2 bind, the TN3270 client is assumed to be a screen; otherwise the client is assumed to be a printer.
In TN3270 server configuration mode, the ip precedence command applies to all PUs supported by the TN3270 server.
In listen-point configuration mode, the ip precedence command applies to all PUs defined at the listen point.
In listen-point PU configuration mode, the ip precedence command applies only to the specified PU.
In DLUR PU configuration mode, the ip precedence command applies to all PUs defined under DLUR configuration mode.
In PU configuration mode, the ip precedence command applies only to the specified PU.
Examples
The following example assigns a precedence value of 3 to printers:
ip precedence printer 3Related Commands
ip tos
To specify the type of service (ToS) level for IP traffic in the TN3270 server, use the ip tos command in TN3270 server configuration mode. To remove the ToS value, use the no form of this command.
ip tos {screen | printer} value
no ip tos {screen | printer}
Syntax Description
screen
Specifies that the ToS is for screen devices.
printer
Specifies that the ToS is for printer devices.
value
Sets the ToS priority. A value from 0 to 15. The default is 0.
Defaults
The default is a ToS value of 0 for both screens and printers.
Command Modes
TN3270 server configuration
Listen-point configuration
Listen-point PU configuration
Dependent Logical Unit Requestor (DLUR) PU configuration
PU configurationCommand History
Usage Guidelines
This command is valid only on the virtual channel interface. ToS values applied in TN3270 PU configuration mode override values applied in TN3270 server configuration mode.
The default ToS values for screen and printer are 0. However, RFC 1349 recommends different default values. Specifically, the RFC recommends a default minimize screen delay value of 8 and a default maximize printer throughput value of 4. You must configure these values using the ip tos command if you want to comply to the defaults as stated in the RFC.
Table 3 shows the values described in RFC 1349.
.
During initial Telnet negotiations to establish, or bind, the session, an IP precedence value of 0 and IP ToS value of 0 is used. These values are used until the bind takes place. When the session is a type 2 bind, the TN3270 client is assumed to be a screen; otherwise the client is assumed to be a printer.
When you use the no form of the command, the ToS value is set to 0 for that configuration mode or the value set at a previous (higher) configuration mode is used. For example, if you are at the TN3270 PU configuration mode and issue a no ip tos screen command, any value you configured previously at the TN3270 server configuration mode will take effect.
You can enter new or different values for ToS without first using the no form of this command.
In TN3270 server configuration mode, the ip tos command applies to all PUs supported by the TN3270 server.
In listen-point configuration mode, the ip tos command applies to all PUs defined at the listen point.
In listen-point PU configuration mode, the ip tos command applies only to the specified PU.
In DLUR PU configuration mode, the ip tos command applies to all PUs defined under DLUR configuration mode.
In PU configuration mode, the ip tos command applies only to the specified PU.
Examples
In the following example, the TN3270 server ToS screen value is set to 10 and a specific PU ToS screen value is set to 0:
interface channel 3/2 tn3270-server ip tos screen 8 ip tos printer 4 up PUS2 ip tos screen 0Related Commands
ip precedence (TN3270)
Specifies the precedence level for IP traffic in the TN3270 server.
keepalive (TN3270)
To specify how many seconds of inactivity elapse before the TN3270 server sends a DO TIMING-MARK or Telnet no operation (nop) to the TN3270 client, use the keepalive command in TN3270 server configuration mode. To cancel the keepalive period and return to the previously configured siftdown value or the default, use the no form of this command.
keepalive seconds [send {nop | timing-mark [max-response-time]}]
no keepalive
Syntax Description
Defaults
The default behavior is to send timing marks with a keepalive interval of 1800 seconds (30 minutes). If you specify only the keepalive interval, the TN3270 server sends timing marks.
The default value of the send timing-mark max-response-time command is 30 seconds if the keepalive interval is greater than or equal to 30 seconds. If the value of the keepalive interval is less than 30 seconds, then the default max-response-time value is the value of the interval.
Command Modes
TN3270 server configuration
Listen-point configuration
Listen-point PU configuration
Dependent Logical Unit Requestor (DLUR) PU configuration
PU configurationCommand History
11.2
This command was introduced.
12.0(5)T
The send {nop | timing-mark [max-response-time]} keywords and argument were added.
Usage Guidelines
The keepalive command is valid only on the virtual channel interface. This command can be entered in one of four command modes (TN3270 configuration, listen-point configuration, listen-point PU configuration, 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 the other supported configuration modes. A no keepalive command entered in a subsequent configuration mode will restore the keepalive value entered in the previous command mode.
In Cisco IOS releases prior to 12.0(5)T in which the keepalive command is supported, you cannot specify the period of time in which the client must respond to the DO TIMING-MARK before the TN3270 server disconnects the session. By default in prior releases, if the client does not reply within 30 minutes of sending the DO TIMING-MARK, the TN3270 server disconnects the TN3270 session. (The DO TIMING-MARK is a Telnet protocol operation that does not affect the client operation.)
With the addition of the send timing-mark max-response-time keywords in Cisco IOS Release 12.0(5)T, you can specify the period of time in which the client must respond to the DO TIMING-MARK before being disconnected by the server. If you do not specify a value for the max-response-time argument, the default value is determined by the size of the keepalive interval. The default is 30 seconds if the keepalive interval is greater than or equal to 30 seconds. If the value of the keepalive interval is less than 30 seconds, then the default max-response-time is the value of the interval.
If the IP path to the client is broken, the TCP layer will detect the failure to acknowledge the DO TIMING-MARK and initiate disconnection. This action usually takes much less than 30 seconds.
The keepalive command affects active and future TN3270 sessions. For example, reducing the keepalive interval to a lower nonzero value causes an immediate burst of DO TIMING-MARKs on those sessions that have been inactive for a period of time greater than the new, lower value.
Use the keepalive send nop command when you are using older TN3270 clients that do not support TIMING-MARK or are DOS-based clients. When you use the keepalive send nop command to monitor the client connection, no response is required by the client to the TN3270 server. However, the TCP/IP stack can detect that the physical connection still exists. This command is useful for those clients that can be swapped out when a DO TIMING-MARK has been sent by the TN3270 server. If the client is swapped out and cannot respond to the DO TIMING-MARK from the TN3270 server, the session is disconnected. However, if the client is swapped out and the Telnet nop command is sent by the server, the physical connection is still verifiable by the TCP/IP stack and the client remains connected to the server.
If your client supports the use of timing marks and is not subject to being swapped out, then using timing marks is preferable to the Telnet nop command for keepalive monitoring. The required response by TN3270 clients to timing marks sent by the server provides a better indication of the health of the client/server connection.
In TN3270 server configuration mode, the keepalive command applies to all PUs supported by the TN3270 server.
In listen-point configuration mode, the keepalive command applies to all PUs defined at the listen point.
In listen-point PU configuration mode, the keepalive command applies only to the specified PU.
In DLUR PU configuration mode, the keepalive command applies to all PUs defined under DLUR configuration mode.
In PU configuration mode, the keepalive command applies only to the specified PU.
Examples
The following example specifies that the TN3270 server sends a DO TIMING-MARK in 15-minute (900-second) intervals and the client must respond within 30 seconds (the default value for the timing-mark max-response-time command when not specified):
keepalive 900The following example entered in TN3270 server configuration mode specifies that the TN3270 server sends a DO TIMING-MARK in 30-minute (1800-second) intervals (the default interval) and the client must respond within 30 seconds (the default for the timing-mark max-response-time command when not specified):
no keepaliveThe following example specifies that the TN3270 server sends a DO TIMING-MARK in 40-minute (2400-second) intervals and the client must respond within 1 minute (60 seconds):
keepalive 2400 send timing-mark 60Consider the following example in which the keepalive command is configured in more than one command mode. In this example the keepalive command is configured in TN3270 server configuration mode, and then in listen-point physical unit (PU) configuration mode. The keepalive command values specified under the listen-point PU override the keepalive 300 value specified under the tn3270-server for PU1. In this example, all other PUs except PU1 use the value of the keepalive 300 command specified in TN3270 server configuration mode.
tn3270-serverkeepalive 300listen-point 10.10.10.1 tcp-port 40pu PU1 94223456 tok 1 08keepalive 10 send timing-mark 5pu PU2 94223457 tok 2 12Related Commands
keylen
To specify the maximum bit length for the encryption keys for Secure Socket Layer (SSL) Encryption Support, use the keylen 128 command in profile configuration mode. To disable this specification and thereby set the key length to the default of 40 bits, use the no form of this command or keylen 40.
keylen {40 | 128}
no keylen [40 | 128]
Syntax Description
40
Specifies the bit length for the encryption keys to 40.
128
Specifies the bit length for the encryption keys to 128. The default is 40 bits.
Defaults
The default encryption key length is 40 bits.
Command Modes
Profile configuration.
Command History
Usage Guidelines
Exportable software versions cannot accept encryption key lengths greater than 40 bits.
The length is optional on the no form of this command. Entering the no form of this command with no length resets the length to the default value of 40 bits.
If the key length is changed, all new connections will use the new value. If an active session renegotiates its security specifications, it will use the new key length value.
Examples
The following example specifies the maximum encryption key length value to 128 bits:
tn3270-serversecurityprofile DOMESTIC SSLencryptorder RC4 DES RC2keylen 128lan
To configure an internal LAN on a Cisco Mainframe Channel Connection (CMCC) adapter interface and enter internal LAN configuration mode, use the lan command in interface configuration mode. To remove an internal LAN interface, use the no form of this command.
lan type lan-id
no lan type lan-id
Syntax Description
Defaults
No default behavior or values
Command Modes
Interface configuration
Command History
Usage Guidelines
Token Ring is the only type of internal LAN supported.
This command is valid only on the virtual channel interface. All internal adapters configured on the internal LAN must be removed before the internal LAN can be removed.
A CMCC internal LAN can be configured as a SRB LAN. This allows Logical Link Control (LLC) packets to be bridged between the CMCC adapter and Cisco IOS, providing a means to link the internal LAN to Cisco IOS Systems Network Architecture (SNA) features such as source-route bridging (SRB), data-link switching plus (DLSw+), remote source-route bridging (RSRB), SDLC Logical Link Control (SDLLC), Qualified Logical Link Control (QLLC), Advanced Peer-to-Peer Networking (APPN), and source-route translational bridging (SR/TLB).
An internal LAN can be configured only on a virtual channel interface of a CMCC adapter. You enter first internal LAN configuration mode by issuing the command for an internal LAN that already exists or when you first configure an internal LAN. In internal LAN configuration mode, the router prompt appears as follows:
router (cfg-lan-type x) #In this syntax, type is the specified internal LAN type and x is the specified value for the lan-id.
Examples
The following example shows how to configure an internal LAN Token Ring with a LAN ID of 20 on the channel interface 1/2:
interface channel 1/2lan tokenring 20Related Commands
lan-name
To specify a name for the LAN that is attached to the interface, use the lan-name command in interface configuration mode. This name is included in any Alert sent to the Systems Network Architecture (SNA) host when a problem occurs on this interface or LAN. To revert to the default name, use the no form of this command.
lan-name lan-name
no lan-name lan-name
Syntax Description
lan-name
Name used to identify the LAN when you send Alerts to the SNA host. The default LAN name is the name of the interface.
Defaults
The default name used for the LAN is the name of the interface.
Command Modes
Interface configuration
Command History
Examples
The following example identifies a LAN:
lan-name LAN1Related Commands
link (TN3270)
To define and activate a link to a host, use the link command in Dependent Logical Unit Requestor (DLUR) service access point (SAP) configuration mode. To delete the link definition, use the no form of this command.
link name [rmac rmac] [rsap rsap]
no link name
Syntax Description
Defaults
No DLUR link is defined.
The default remote SAP address is 04 (hexadecimal).Command Modes
DLUR SAP configuration
Command History
Usage Guidelines
This command is valid only on the virtual channel interface. The combination of the rmac and rsap value must be unique within the DLUR SAP function. These values can be changed only by deleting the link definition, using the no link command, and recreating the link definition.
For a link via a channel on this Cisco Mainframe Channel Connection (CMCC) adapter, the TN3270 server and the hosts should open different adapters. Using different adapters avoids any contention for SAP numbers, and is also necessary if you configure duplicate MAC addresses for fallback Cisco Systems Network Architecture (CSNA) or Cisco Multipath Channel (CMPC) access to the host.
Examples
The following example defines a link name and a remote SAP address:
link LINK5 rsap 08The following example shows different adapter numbers configured on the same internal LAN to avoid SAP contention. The host uses SAP 4 on Token Ring adapter 0.
lan tokenring 0adapter 0 4000.0000.0001adapter 1 4000.0000.0002tn3270-serverdlur ...lsap token-adapter 1link HOST rmac 4000.0000.0001 rsap 4Related Commands
adapter
Configures internal adapters.
client pool
Nails clients to pools.
lsap
Creates a SAP in the SNA session switch and enters DLUR SAP configuration mode.
listen-point
To define an IP address for the TN3270 server, use the listen-point command in TN3270 server configuration mode. To remove a listen-point for the TN3270 server, use the no form of this command.
listen-point ip-address [tcp-port number]
no listen-point ip-address [tcp-port number]
Syntax Description
Defaults
The default tcp-port number is 23.
Command Modes
TN3270 server configuration
Command History
11.2(18)BC
This command was introduced.
12.0(5)T
This command was integrated into Cisco IOS Release 12.0(5)T.
Usage Guidelines
Use the listen-point command to create a unique listen point for every IP address and TCP-port pair. In this mode, the IP address and the TCP port are no longer configured in the PU. Configure the PUs under the appropriate listen point. The other siftdown configuration commands remain the same.
For example, in the old configuration the following statements were used to configure the IP address and TCP port in the PU:
tn3270-serverpu PU1 94223456 10.10.10.1 tok 1 08tcp-port 40keepalive 10In the new listen-point configuration, the following statements are used to configure the IP address and TCP port at the listen point:
tn3270-serverlisten-point 10.10.10.1 tcp-port 40pu PU1 94223456 tok 1 08keepalive 10You can also use the listen-point configuration to assign the same IP address to multiple PUs. In the old configuration the following statements were used:
tn3270-serverpu PU1 94201231 10.10.10.2 tok 1 10pu PU2 94201232 10.10.10.3 tok 1 12pu PU3 94201234 10.10.10.3 tok 1 14pu PU4 94201235 10.10.10.4 tok 1 16tcp-port 40pu PU5 94201236 10.10.10.4 tok 2 08In the new listen point configuration, the old statements are replaced by the following configuration commands. In this example, PU2 and PU3 are grouped into one listen point because they have the same IP address. Note that even though PU4's IP address is identical to PU5's IP address, they are not configured within the same listen point because the listen point indicates a unique IP address and TCP port pair. If you do not specify the TCP port, the default port value is 23.
tn3270-serverlisten-point 10.10.10.2pu PU1 94201231 tok 1 10listen-point 10.10.10.3pu PU2 94201232 tok 1 12pu PU3 94201234 tok 1 14listen-point 10.10.10.4pu PU5 94201236 tok 2 08listen-point 10.10.10.4 tcp-port 40pu PU4 94201235 tok 1 16The next example shows how the configuration changes for a Dependent Logical Unit Requestor (DLUR) PU. In this mode, the DLUR PU is no longer configured under DLUR, but is configured in the listen point.
In the old configuration, the following statements were used:
tn3270-serverdlur NETA.RTR1 NETA.HOSTdlus-backup NETA.HOSTlsap token-adapter 15 08link MVS2TN rmac 4000.b0ca.0016pu PU1 017ABCDE 10.10.10.6These statements are replaced by the following statements in the new listen-point configuration. The keyword dlur differentiates the listen point direct PU from the listen point DLUR PU. The DLUR configuration must be completed before you configure the PU in the listen point. Any siftdown commands configured within the scope of the listen point are automatically inherited by the PUs that are configured within the scope of that listen point. To override the siftdown configurations, you can explicitly configure the siftdown configuration commands within the scope of the listen-point PU.
tn3270-serverdlur NETA.RTR1 NETA.HOSTdlus-backup NETA.HOSTlsap token-adapter 15 08link MVS2TN rmac 4000.b0ca.0016listen-point 10.10.10.6pu PU1 017ABCDE dlurExamples
The following example of the listen-point command shows PU7 grouped into the listen point at IP address 10.10.10.1 and TCP port 40:
tn3270-serverlisten-point 10.10.10.1 tcp-port 40pu PU7 94201237 tok 1 17Related Commands
llc2 ack-delay-time
To set the amount of time the Cisco IOS software waits for an acknowledgment before sending the next set of information frames, use the llc2 ack-delay-time command in internal adapter configuration mode. To revert to the default setting, use the no form of this command.
llc2 ack-delay-time milliseconds
no llc2 ack-delay-time milliseconds
Syntax Description
milliseconds
Number of milliseconds the software allows incoming information frames to stay unacknowledged. The minimum is 1 ms and the maximum is 60000 ms. The default is 100 ms.
Defaults
100 ms
Command Modes
Internal adapter configuration
Command History
Usage Guidelines
Upon receiving an information frame, each Logical Link Control, type 2 (LLC2) station starts a timer. If the timer expires, an acknowledgment will be sent for the frame, even if the number of received frames in the llc2 ack-max command has not been reached. Experiment with the value of the llc2 ack-delay-time command to determine the configuration that balances acknowledgment network overhead and quick response time (by receipt of timely acknowledgments).
Use this command in conjunction with the llc2 ack-max command to determine the maximum number of information frames the Cisco IOS software can receive before sending an acknowledgment.
Examples
In the following example, the software allows a 100-ms delay before I-frames must be acknowledged:
! enter a global command, if you have not alreadyinterface tokenring 0! sample ack-max commandllc2 ack-max 3! allow a 100 millisecond delay before I-frames must be acknowledgedllc2 ack-delay-time 100At time 0, two information frames are received. The llc2 ack-max amount of three has not been reached, so no acknowledgment for these frames is sent. If a third frame, which would force the software to send an acknowledgment, is not received in 100 ms, an acknowledgment will be sent anyway, because the llc2 ack-delay timer expires. At this point, because all frames are acknowledged, the counter for the ack-max purposes will be reset to zero.
Related Commands
llc2 ack-max
To control the maximum amount of information frames the Cisco IOS software can receive before it must send an acknowledgment, use the llc2 ack-max command in internal adapter configuration mode. To revert to the default setting, use the no form of this command.
llc2 ack-max packet-count
no llc2 ack-max packet-count
Syntax Description
packet-count
Maximum number of packets the software will receive before sending an acknowledgment. The minimum is 1 packet and the maximum is 127 packets. The default is 3 packets.
Defaults
Three packets
Command Modes
Internal adapter configuration
Command History
Usage Guidelines
An Logical Link Control, type 2 (LLC2)-speaking station can send only a predetermined number of frames before it must wait for an acknowledgment from the receiver. If the receiver waits until receiving a large number of frames before acknowledging any of them, and then acknowledges them all at once, overhead is reduced on the network.
For example, an acknowledgment for five frames can specify that all five have been received, as opposed to sending a separate acknowledgment for each frame. To keep network overhead low, make this parameter as large as possible.
However, some LLC2-speaking stations expect this number to be low. Some NetBIOS-speaking stations expect an acknowledgment to every frame. Therefore, for these stations, this number is best set to 1. Experiment with this parameter to determine the best configuration.
Examples
In the following example, the software is configured to receive up to seven frames before it must send an acknowledgment. Seven frames is the maximum allowed by Systems Network Architecture (SNA) before a reply must be received:
! enter a global command, if you have not alreadyinterface tokenring 0! receive up to seven frames before sending an acknowledgmentllc2 ack-max 7! sample delay-time commandllc2 ack-delay-time 100Related Commands
llc2 dynwind
To enable dynamic window congestion management, use the llc2 dynwind command in interface configuration mode. To cancel the configuration, use the no form of this command.
llc2 dynwind [nw nw-number] [dwc dwc-number]
no llc2 dynwind [nw nw-number] [dwc dwc-number]
Syntax Description
Defaults
The default nw-number value is 4.
The default dwc-number value is 1.Command Modes
Interface configuration
Command History
Examples
The following example specifies that to increment the working window six frames must be received, and the working window value should be set to 1 when BECN occurs:
llc2 dynwind nw 6 dwc 1llc2 idle-time
To control the frequency of polls during periods of idle time (no traffic), use the llc2 idle-time command in internal adapter configuration mode. To revert to the default setting, use the no form of this command.
llc2 idle-time milliseconds
no llc2 idle-time milliseconds
Syntax Description
Defaults
10000 ms
Command Modes
Internal adapter configuration
Command History
Usage Guidelines
Periodically, when no information frames are being sent during an LLC2 session, LLC2 stations are sent a Receiver Ready frame to indicate that they are available. Set the value for this command low enough to ensure a timely discovery of available stations, but not too low, or you will create a network overhead with too many Receiver Ready frames.
Examples
In the following example, the Cisco IOS software waits 20,000 ms before sending a Receiver Ready ("are you there") frame:
! enter a global command, if you have not already interface tokenring 0! wait 20000 milliseconds before sending receiver-ready framesllc2 idle-time 20000Related Commands
llc2 local-window
To control the maximum number of information frames the Cisco IOS software sends before it waits for an acknowledgment, use the llc2 local-window command in internal adapter configuration mode. To revert to the default setting, use the no form of this command.
llc2 local-window packet-count
no llc2 local-window packet-count
Syntax Description
packet-count
Maximum number of packets that can be sent before the software must wait for an acknowledgment. The minimum is 1 packet and the maximum is 127 packets. The default is 7 packets.
Defaults
Seven packets
Command Modes
Internal adapter configuration
Command History
Usage Guidelines
An Logical Link Control, type 2 (LLC2)-speaking station can send only a predetermined number of frames before it must wait for an acknowledgment from the receiver. Set this number to the maximum value that can be supported by the stations with which the router communicates. Setting this value too large can cause frames to be lost, because the receiving station may not be able to receive all of them.
Examples
In the following example, the software will send as many as 30 information frames through Token Ring interface 1 before it must receive an acknowledgment:
! enter a global command, if you have not alreadyinterface tokenring 1llc2 local-window 30Related Commands
llc2 n1
To specify the maximum size of an I-frame, use the llc2 n1 command in internal adapter configuration mode. To revert to the default setting, use the no form of this command.
llc2 n1 bytes
no llc2 n1
Syntax Description
bytes
Maximum size of an I-frame. The valid range is from 1 to 4105 bytes. The default is 4105 bytes.
Defaults
The default maximum I-frame size is 4105 bytes.
Command Modes
Internal adapter configuration
Command History
Examples
The following example sets the maximum I-frame size to 2057 bytes:
! enter a global command, if you have not alreadyinterface tokenring 1! maximum I-frame size of 2057 bytesllc2 n1 2057Related Commands
show llc2
Displays the Logical Link Control, type 2 (LLC2) connections active in the router.
llc2 n2
To control the amount of times the Cisco IOS software retries sending unacknowledged frames or repolls remote busy stations, use the llc2 n2 command in internal adapter configuration mode. To revert to the default setting, use the no form of this command.
llc2 n2 retry-count
no llc2 n2
Syntax Description
retry-count
Number of times the software retries operations. The minimum is 1 retry and the maximum is 255 retries. The default is 8 retries.
Defaults
Eight retries
Command Modes
Internal adapter configuration
Command History
Usage Guidelines
An Logical Link Control, type 2 (LLC2) station must have some limit to the number of times it will resend a frame when the receiver of that frame has not acknowledged it. After the software is told that a remote station is busy, it will poll again based on the retry-count value. When this retry count is exceeded, the LLC2 station terminates its session with the other station. Set this parameter to a value that balances between frame checking and network performance.
Examples
In the following example, the software will resend a frame up to four times through Token Ring interface 1 before it must receive an acknowledgment. Because you generally do not need to change the retry limit, this example shows you how to reset the limit to the default of 8.
! enter a global command, if you have not alreadyinterface tokenring 1! retry value of 8llc2 n2 8Related Commands
llc2 nw
To increase the window size for consecutive good I-frames received, use the llc2 nw internal adapter configuration command. To revert to the default setting, use the no form of this command.
llc2 nw window-size-increase
no llc2 nw
Syntax Description
window-size-increase
Number of frames to increase the window size for consecutive good I-frames received (0 is disabled). The allowed range is from 1 to 7. The default is 0.
Defaults
0 (disabled)
Command Modes
Internal adapter configuration
Command History
11.0
This command was introduced.
12.1
The allowed range was changed to from 0 to 31.
Examples
In the following example, the window size for Token Ring interface 1 is increased by 1 frame when consecutive good I-frames are received:
! enter a global command, if you have not alreadyinterface tokenring 1! increase window size by 1llc2 nw 1Related Commands
Displays the LLC2 connections active in the router.
Invokes dynamic windowing logic for a link station when the router receives an RNR from the remote link station.
llc2 recv-window
To control the number of frames in the receive window, use the llc2 recv-window command in internal adapter configuration mode. To revert to the default setting, use the no form of this command.
llc2 recv-window frame-count
no llc2 recv-window
Syntax Description
Defaults
Seven frames
Command Modes
Internal adapter configuration
Command History
Examples
In the following example, the receive window for Token Ring interface 1 contains 11 frames:
! enter a global command, if you have not alreadyinterface tokenring 1! 11 frames in the receive windowllc2 recv-window 11Related Commands
show llc2
Displays the Logical Link Control, type 2 (LLC2) connections active in the router.
llc2 rnr-activated
To invoke dynamic windowing logic for a link station when the router receives an RNR from the remote link station, use the llc2 rnr-activated internal adapter configuration command. To disable dynamic windowing logic, use the no form of this command.
llc2 rnr-activated
no llc2 rnr-activated
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Internal adapter configuration
Command History
Usage Guidelines
The llc2 nw command must be enabled before the llc2 rnr-activated command can be configured.
Examples
In the following example, the llc2n rnr-activated command is enabled on Adapter 0 4000.cafe.0000:
interface Channel4/2max-llc2-rcvbuffs 750lan TokenRing 12source-bridge 16 1 500adapter 0 4000.cafe.0000llc2 Nw 31llc2 rnr-activatedadapter 1 4000.cafe.0001Related Commands
Increases the window size for consecutive good I-frames received.
Configures the number of receive DMA buffers that are used by the LLC2 stack on the CIP/XCPA.
llc2 send-window
To control the number of frames in the send window, use the llc2 send-window command in internal adapter configuration mode. To revert to the default setting, use the no form of this command.
llc2 send-window frame-count
no llc2 send-window
Syntax Description
Defaults
Seven frames
Command Modes
Internal adapter configuration
Command History
Examples
In the following example, the send window for Token Ring interface 1 contains 11 frames:
! enter a global command, if you have not alreadyinterface tokenring 1! 11 frames in the send windowllc2 send-window 11Related Commands
show llc2
Displays the Logical Link Control, type 2 (LLC2) connections active in the router.
llc2 t1-time
To control the amount of time the Cisco IOS software will wait before resending unacknowledged information frames, use the llc2 t1-time command in internal adapter configuration mode. To revert to the default setting, use the no form of this command.
llc2 t1-time milliseconds
no llc2 t1-time milliseconds
Syntax Description
milliseconds
Number of milliseconds the software waits before resending unacknowledged information frames. The minimum is 1 ms and the maximum is 60000 ms. The default is 1000 ms.
Defaults
1000 ms
Command Modes
Internal adapter configuration
Command History
Usage Guidelines
Use this command in conjunction with the llc2 n2 command to provide a balance of network monitoring and performance. Ensure that enough time is allowed to account for the round trip between the router and its Logical Link Control, type 2 (LLC2)-speaking stations under heavy network loading conditions.
Examples
In the following example, the software will wait 4000 ms before resending an unacknowledged frame through Token Ring interface 2:
! enter a global command, if you have not alreadyinterface tokenring 2! wait 4000 milliseconds before retransmitting a frame through tokenring 2llc2 t1-time 4000Related Commands
llc2 tbusy-time
To control the amount of time the Cisco IOS software waits until repolling a busy remote station, use the llc2 tbusy-time command in internal adapter configuration mode. To revert to the default setting, use the no form of this command.
llc2 tbusy-time milliseconds
no llc2 tbusy-time milliseconds
Syntax Description
milliseconds
Number of milliseconds the software waits before repolling a busy remote station. The minimum is 1 ms and the maximum is 60000 ms. The default is 9600 ms.
Defaults
9600 ms
Command Modes
Internal adapter configuration
Command History
Usage Guidelines
An Logical Link Control, type 2 (LLC2) station can to notify other stations that it is temporarily busy, so the other stations will not attempt to send any new information frames. The frames sent to indicate this are called Receiver Not Ready (RNR) frames. Change the value of this parameter only to increase the value for LLC2-speaking stations that have unusually long busy periods before they clear their busy status. Increasing the value will prevent the stations from timing out.
Examples
In the following example, the software will wait up to 12,000 ms before attempting to poll a remote station through Token Ring interface 0 to learn the station's status:
! enter a global command, if you have not alreadyinterface tokenring 0! wait 12000 milliseconds before polling a station through tokenring 0llc2 tbusy-time 12000Related Commands
llc2 tpf-time
To set the amount of time the Cisco IOS software waits for a final response to a poll frame before resending the poll frame, use the llc2 tpf-time command in internal adapter configuration mode. To revert to the default setting, use the no form of this command.
llc2 tpf-time milliseconds
no llc2 tpf-time milliseconds
Syntax Description
Defaults
1000 ms
Command Modes
Internal adapter configuration
Command History
Usage Guidelines
When a command is sent that must receive a response, a poll bit is sent in the frame. This is the receiving station's clue that the sender is expecting some response from it, be it an acknowledgment of information frames or an acknowledgment of more administrative tasks, such as starting and stopping the session. Once a sender gives out the poll bit, it cannot send any other frame with the poll bit set until the receiver replies with a frame containing a final bit set. If the receiver is faulty, it may never return the final bit to the sender. Therefore, the sender could be waiting for a reply that will never come. To avoid this problem, when a poll-bit-set frame is sent, a transmit-poll-frame (TPF) timer is started. If this timer expires, the software assumes that it can send another frame with a poll bit.
Usually, you will not want to change this value. If you do, the value should be larger than the T1 time, set with the llc2 t1-time command. The T1 time determines how long the software waits for receipt of an acknowledgment before sending the next set of frames.
Examples
Although you generally will not want to change the transmit-poll-frame (TPF) time, this example sets the TPF time to 3000 ms. Because the TPF time should be larger than the Logical Link Control, type 2 (LLC2) T1 time, this example shows the TPF time as double the LLC2 T1 time.
! enter a global command, if you have not alreadyinterface tokenring 0! send a poll bit set through tokenring 0 after a 3000 ms delayllc2 tpf-time 3000! wait 1500 milliseconds for an acknowledgment before resending I-framesllc2 t1-time 1500Related Commands
llc2 trej-time
To control the amount of time the Cisco IOS software waits for a correct frame after sending a reject command to the remote Logical Link Control, type 2 (LLC2) station, use the llc2 trej-time command in internal adapter configuration mode. To revert to the default setting, use the no form of this command.
llc2 trej-time milliseconds
no llc2 trej-time milliseconds
Syntax Description
Defaults
3200 ms
Command Modes
Internal adapter configuration
Command History
Usage Guidelines
When an LLC2 station sends an information frame, a sequence number is included in the frame. The LLC2 station that receives these frames will expect to receive them in order. If it does not, it can reject a frame and indicate which frame it is expecting to receive instead. Upon sending a reject, the LLC2 station starts a reject timer. If the frames are not received before this timer expires, the session is disconnected.
Examples
In the following example, the software will wait up to 1000 ms to receive a previously rejected frame before resending its reject message to the station that sent the frame:
! enter a global command, if you have not alreadyinterface tokenring 0! wait 1000 milliseconds before resending a reject message through tokenring 0llc2 trej-time 1000Related Commands
llc2 xid-neg-val-time
To control the frequency of exchange of identification (XID) transmissions by the Cisco IOS software, use the llc2 xid-neg-val-tim command in internal adapter configuration mode. To revert to the default setting, use the no form of this command.
llc2 xid-neg-val-time milliseconds
no llc2 xid-neg-val-time milliseconds
Syntax Description
Defaults
0 ms
Command Modes
Internal adapter configuration
Command History
Usage Guidelines
Do not change the llc2 xid-neg-val-time value unless requested by your technical support representative.
LLC2-speaking stations can communicate XID frames to each other. These frames identify the stations at a higher level than the MAC address and also can contain information about the configuration of the station. These frames are typically sent only during setup and configuration periods when it is deemed that sending them is useful. The greatest frequency at which this information is transferred is controlled by this timer.
Examples
The following example shows how to reset the frequency of XID transmissions to the default of
0 ms:! enter a global command, if you have not alreadyinterface tokenring 0! set the frequency of XID transmissions to 0llc2 xid-neg-val-time 0Related Commands
llc2 xid-retry-time
To set the amount of time the Cisco IOS software waits for a reply to exchange of identification (XID) frames before dropping the session, use the llc2 xid-retry-time command in internal adapter configuration mode. To revert to the default setting, use the no form of this command.
llc2 xid-retry-time milliseconds
no llc2 xid-retry-time milliseconds
Syntax Description
milliseconds
Number of milliseconds (ms) the software waits for a reply to XID frames before dropping a session. The minimum is 1 ms and the maximum is 60000 ms. The default is 60000 ms.
Defaults
60000 ms
Command Modes
Internal adapter configuration
Command History
Usage Guidelines
Set this value greater than the value of the T1 time or the time the software waits for an acknowledgment before dropping the session. T1 time is set with the llc2 t1-time command.
Examples
The following example sets the software to wait up to 60,000 ms for a reply to XID frames it sent to remote stations (which resets the value to its default):
! enter a global command, if you have not alreadyinterface tokenring 0! wait 60000 milliseconds for a reply to XID framesllc2 xid-retry-time 60000Related Commands
locaddr-priority
To assign a remote source-route bridging (RSRB) priority group to an input interface, use the locaddr-priority command in interface configuration mode. To remove the RSRB priority group assignment from the interface, use the no form of this command.
locaddr-priority list-number
no locaddr-priority list-number
Syntax Description
Defaults
No RSRB priority group is assigned.
Command Modes
Interface configuration
Command History
Usage Guidelines
You must use the priority-list protocol command to assign priorities to the ports as shown in Table 4.
Table 4 Common RSRB Services and Their Port Numbers
RSRB high priority
1996
RSRB medium priority
1987
RSRB normal priority
1988
RSRB low priority
1989
Examples
In the following example, Token Ring interface 0 is assigned the RSRB priority group 1; LU 01 is assigned a medium priority and maps to TCP port 1996; LU 02 has been assigned a normal priority and maps to TCP port 1987; LU 03 has been assigned a low priority and maps to TCP port 1988; and LU 04 has been assigned high priority and maps to TCP port 1989:
source-bridge ring-group 2624source-bridge remote-peer 2624 tcp 10.0.0.1source-bridge remote-peer 2624 tcp 10.0.0.2 local-ack prioritylocaddr-priority-list 1 01 mediumlocaddr-priority-list 1 02 normallocaddr-priority-list 1 03 lowlocaddr-priority-list 1 04 high!priority-list 1 protocol ip low tcp 1996priority-list 1 protocol ip high tcp 1987priority-list 1 protocol ip medium tcp 1988priority-list 1 protocol ip normal tcp 1989!interface tokenring 0source-bridge 2576 8 2624locaddr-priority 1Related Commands
locaddr-priority-list
To map logical units (LUs) to queueing priorities as one of the steps to establishing queueing priorities based on LU addresses, use the locaddr-priority-list command in global configuration mode. To remove that priority queueing assignment, use the no form of this command. You use this command in conjunction with the priority list command.
locaddr-priority-list list-number address-number queue-keyword [dsap ds] [dmac dm] [ssap ss] [smac sm]
no locaddr-priority-list list-number address-number queue-keyword [dsap ds] [dmac dm] [ssap ss] [smac sm]
Syntax Description
Defaults
No mapping.
Command Modes
Global configuration
Command History
10.0
This command was introduced.
11.0
The following keywords were added:
•
•
Usage Guidelines
Use this command to map LUs to queueing priorities. Once you establish the priority for each LU, you can assign a priority to a TCP port. Hence you establish a mapping between the LUs and queueing priorities, and queueing priorities and TCP ports.
It is preferable to prioritize NetBIOS traffic below Systems Network Architecture (SNA) traffic, but by default NetBIOS traffic is assigned the high priority on TCP port 1996.
Examples
In the following example, Token Ring interface 0 is assigned the remote source-route bridging (RSRB) priority group 1; LU 01 is assigned a medium priority and maps to TCP port 1996; LU 02 has been assigned a normal priority and maps to TCP port 1987; LU 03 has been assigned a low priority and maps to TCP port 1988; and LU 04 has been assigned high priority and maps to TCP port 1989:
source-bridge ring-group 2624source-bridge remote-peer 2624 tcp 10.0.0.1source-bridge remote-peer 2624 tcp 10.0.0.2 local-ack prioritylocaddr-priority-list 1 01 mediumlocaddr-priority-list 1 02 normallocaddr-priority-list 1 03 lowlocaddr-priority-list 1 04 high!priority-list 1 protocol ip low tcp 1996priority-list 1 protocol ip high tcp 1987priority-list 1 protocol ip medium tcp 1988priority-list 1 protocol ip normal tcp 1989!interface tokenring 0source-bridge 2576 8 2624locaddr-priority 1The following example shows how to establish queueing priorities based on the address of the serial link on a serial tunnel (STUN) connection. Note that you must use the priority-group command in interface configuration mode to assign a priority group to an input interface.
stun peer-name 10.108.254.6stun protocol-group 1 sdlclocaddr-priority-list 1 02 highlocaddr-priority-list 1 03 highlocaddr-priority-list 1 04 mediumlocaddr-priority-list 1 05 low!interface serial 0no ip addressencapsulation stunstun group 1stun route address 4 interface serial 0 directlocaddr priority 1priority-group 1Related Commands
locaddr-priority
Assigns an RSRB priority group to an input interface.
priority-list protocol
Establishes queueing priorities based on the protocol type.
lsap
To create a service access point (SAP) in the Systems Network Architecture (SNA) session switch and enter Dependent Logical Unit Requestor (DLUR) SAP configuration mode, use the lsap DLUR configuration command. To delete a SAP and all SNA session switch links using the internal LAN interface, use the no form of this command.
lsap type adapter-number [lsap]
no lsap type adapter-number [lsap]
Syntax Description
Defaults
The default value for the lsap argument is hexadecimal C0.
Command Modes
DLUR configuration
Command History
Usage Guidelines
The lsap command is valid only on the virtual channel interface. If the SAP in the SNA session switch function is already created, the lsap command with no arguments puts you in DLUR SAP configuration mode.
The lsap command can be entered only in DLUR configuration mode.
The lsap command uses values that are defined in two other commands: the lan internal LAN configuration command and the adapter internal LAN configuration command. The lan type and adapter adapter-number values configured on the Cisco Mainframe Channel Connection (CMCC) internal LAN interface are used in the lsap command. However, the lan type keyword is a little different. Where the value for the type argument on the lan command is tokenring, the corresponding value for the type argument on lsap is token-adapter. This emphasizes that the number that follows is an adapter number, not a lan number.
The no lsap command hierarchically deletes any links using it. Any sessions using those links are lost.
Examples
The following example defines an adapter type, an adapter number, and a local SAP:
lsap token 0 B0Related Commands
adapter
Configures internal adapters.
client pool
Nails clients to pools.
keylen
Specifies the maximum bit length for the encryption keys for SSL Encryption Support.
lu deletion
To specify whether the TN3270 server sends a REPLY-PSID poweroff request to virtual telecommunications access method (VTAM) to delete the correspondinglogical unit (LU) when a client disconnects, use the lu deletion command in TN3270 server configuration mode. To remove LU deletion from the current configuration scope, use the no form of this command.
lu deletion {always | normal | non-generic | never | named}
no lu deletion
Syntax Description
Defaults
The default keyword is never.
Command Modes
TN3270 server configuration—The lu deletion command at this level applies to all PUs supported by the TN3270 server.
Listen-point configuration—The lu deletion command at this level applies to all PUs defined at the listen point.
Listen-point PU configuration—The lu deletion command at this level applies only to the specified PU.
Dependent Logical Unit Requestor (DLUR) PU configuration—The lu deletion command at this level applies to all PUs defined under DLUR configuration mode.
PU configuration—The lu deletion command at this level applies only to the specified PU.
Note
Command History
11.2(18)BC
This command was introduced.
12.0(5)T
This command was integrated into Cisco IOS Release 12.0 T.
12.1(5)T
This command was modified to add the named keyword.
Usage Guidelines
Use the always keyword of the lu deletion command when you have only screen LUs, and they are all different sizes. This prevents screen LUs from attaching to a previously used LU with an incompatible screen size.
Use the normal keyword of the lu deletion command when you have both screen and printer LUs. This is important because printers are acquired by the host application, and not logged on manually. If VTAM deletes the LU, then there is nothing for a host application (such as CICS) to acquire.
You can use the non-generic mode of LU deletion if VTAM can support deletion of specifically named LUs. (The support of this mode is not available in VTAM, as of VTAM version 4.4.1.)
Use the never mode of LU deletion when you have only screen LUs and they all use the same screen size.
Use the named keyword of the lu deletion command when you have configured dynamic LU names from the TN3270 server side.
Examples
Following is an example of the lu deletion command specifying that the TN3270 server send a REPLY-PSID poweroff request to delete only screen LUs upon session disconnect for any PUs supported by the TN3270 server:
tn3270-serverlu deletion normalFollowing is an example of the lu deletion command configuring a listen-point PU to define Dependent Logical Unit Requestor (DLUR) PUs using dynamic LU naming:
tn3270-serverlisten-point 172.18.4.18pu pu1 05D9901 dlurlu deletion namedRelated Commands
lu termination
To specify whether a TERMSELF or UNBIND request/response unit (RU) is sent by the TN3270 server when a client turns off a device or disconnects, use the lu termination command in TN3270 server configuration mode. To remove LU termination from the current configuration scope, use the no form of this command.
lu termination {termself | unbind}
no lu termination
Syntax Description
Defaults
unbind is the default.
Command Modes
TN3270 server configuration
Listen-point configuration
Listen-point PU configuration
Dependent Logical Unit Requestor (DLUR) PU configuration
PU configuration
Note
Command History
11.2(18)BC
This command was introduced.
12.0(5)T
This command was integrated into Cisco IOS Release 12.0(5)T.
Usage Guidelines
Use the termself keyword when you want to be sure that the application terminates the session when the LU disconnects. This is important for certain applications such as Customer Information Control System (CICS).
If you use the unbind keyword for session termination with applications such as CICS, virtual telecommunications access method (VTAM) security problems can arise. When CICS terminates a session from an UNBIND request, the application may reestablish a previous user's session with a new user, who is now assigned to the same freed LU.
In TN3270 server configuration mode, the lu termination command applies to all PUs supported by the TN3270 server.
In listen-point configuration mode, the lu termination command applies to all PUs defined at the listen point.
In listen-point PU configuration mode, the lu termination command applies only to the specified PU.
In DLUR PU configuration mode, the lu termination command applies to all PUs defined under DLUR configuration mode.
In PU configuration mode, the lu termination command applies only to the specified PU.
Examples
Following is an example of the lu termination configuration command to force termination of the session when an LU disconnects for any PUs supported by the TN3270 server:
tn3270-serverlu termination termselfmaximum-lus
To limit the number of logical unit (LU) control blocks that will be allocated for the TN3270 server, use the maximum-lus command in TN3270 server configuration mode. To restore the default value, use the no form of this command.
maximum-lus number
no maximum-lus
Syntax Description
Defaults
Because of the license structure, the default is 2100, which represents the limit of the lower-priced license (2000) plus a 5 percent buffer. If you configure a value greater than the default, a license reminder is displayed.
Command Modes
TN3270 server configuration
Command History
Usage Guidelines
The maximum-lus command is valid only on the virtual channel interface. Although the value may be varied at any time, reducing it below the current number of LU control blocks will not release those blocks until a physical unit (PU) is inactivated by Deactivate Physical Unit (DACTPU) or by using the no pu command.
If the number of LUs in use reaches 94 percent of the current setting, a warning message is displayed on the console. To prevent redundant messages, the threshold for generating such messages is raised for a period.
The TN3270 server attempts to allocate one LU control block for each LU activated by the hosts. In the case of dynamic definition of dependent LU (DDDLU) the control block is allocated when the client requests the LU, in anticipation of an activate logical unit (ACTLU) from the system services control points (SSCP) host.
By limiting the number of LU control blocks allocated, you can make sure enough memory is available to support other Cisco Mainframe Channel Connection (CMCC) functions. The control blocks themselves take about 1K bytes per LU. During session activity, a further 2K per LU may be needed for data. On a Channel Interface Processor (CIP), 32 MB of memory will support 4000 LUs. To support more than 4000 LUs, we recommend 64 MB of memory. On an XCPA, 8 MB of memory supports 1000 LUs.
Examples
The following example allows 5000 LU control blocks to be allocated:
maximum-lus 5000Related Commands
max-llc2-rcvbuffs
To configure the number of receive DMA buffers that are used by the LLC2 stack on the CIP/XCPA, use the max-llc2-rcvbuffs internal adapter configuration command. Use the no form of this command to revert to the default setting.
max-llc2-rcvbuffs buffers
no max-llc2-rcvbuffs buffers
Syntax Description
buffers
The number of receive DMA buffers that are used by the LLC2 stack on the CIP/XCPA. The allowed range is from 500 to 1250 in multiples of 50. The default is 500.
Defaults
500 buffers
Command Modes
Virtual interface configuration
Command History
Examples
The following example configures the max-llc2-rcvbuffs for 750 buffers on Channel interface 4/2:
interface Channel4/2max-llc2-rcvbuffs 750lan TokenRing 12source-bridge 16 1 500adapter 0 4000.cafe.0000llc2 Nw 31llc2 rnr-activatedadapter 1 4000.cafe.0001Related Commands
Increases the window size for consecutive good I-frames received.
Invokes dynamic windowing logic for a link station when the router receives an RNR from the remote link station.
max-llc2-sessions
To specify the maximum number of Logical Link Control, type 2 (LLC2) sessions supported on the Cisco Mainframe Channel Connection (CMCC) adapter, use the max-llc2-sessions command in interface configuration mode. To restore the default value, use the no form of this command.
max-llc2-sessions number
no max-llc2-sessions number
Syntax Description
number
A value in the range from 1 to 6000 Logical Link Control (LLC) sessions. If this command is not configured, the default is 256 sessions.
Defaults
The default number of sessions is 256.
Command Modes
Interface configuration
Command History
Usage Guidelines
This command is configured on the virtual interface of a Channel Interface Processor (CIP), and the physical interface of a Channel Port Adapter (CPA). If you do not configure this parameter on the CMCC adapter, then the limit of LLC2 sessions is 256.
This command will fail if not enough memory is available on the CMCC adapter to support the specified number of LLC2 sessions.
Note
Examples
The following example limits the maximum number of LLC2 sessions to 212:
max-llc2-sessions 212
name
To assign a name to the internal adapter, use the name command in internal adapter configuration mode. To remove the name assigned to an internal adapter, use the no form of this command.
name name
no name name
Syntax Description
name
Name that identifies this internal adapter. The name consists of up to eight characters (not including blank spaces).
Defaults
No default behavior or values
Command Modes
Internal adapter configuration
Command History
Examples
The following example assigns a name to an internal adapter interface:
name VTAM_B14Related Commands
ncia
To stop or start a native client interface architecture (NCIA) server, use the ncia command in privileged EXEC mode.
ncia {start | stop}
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
As soon as the NCIA server is configured, it begins running. If an NCIA server is configured and the configuration is stored in the NVRAM of the router, when the router boots up, the server is started automatically. Issuing the ncia start command when a server is already running causes the router to display the message:
NCIA server is running already!There is not a no form for this command.
Examples
The following example stops an active NCIA server:
Router# ncia stopRelated Commands
ncia client
To configure a native client interface architecture (NCIA) client on a Cisco router, use the ncia client command in global configuration mode. To remove the configuration, use the no form of this command.
ncia client server-number client-ip-address virtual-mac-address [sna | all]
no ncia client server-number client-ip-address virtual-mac-address [sna | all]
Syntax Description
Defaults
No NCIA client is configured.
Command Modes
Global configuration
Command History
Usage Guidelines
You must use the ncia server command to configure an NCIA server on the router before using the ncia client command to configure an NCIA client.
The purpose in configuring a client is so the NCIA server can connect outward to a client. When an end station on the LAN side tries to connect to a client, the end station sends an explorer. When the server receives this explorer, the server tries to match the MAC address in the client database. If it finds a match, the server then connects to that client. If the ability for the server to connect outward to clients is not needed, there is no reason to configure any clients.
Each client is assigned a MAC address from the pool created by the ncia server command. There are two exceptions to this guideline:
•
When a client configured with a MAC address outside the pool connects to the server, the client's configured MAC address is used, rather than allocating a new one from the pool.
•
The MAC address is recognized during the "capability exchange" period when the client establishes a session with the NCIA server. Normally, it is not necessary to configure any client. The server accepts a connection from any unconfigured client. If the unconfigured client does not have its own MAC address, a MAC address from the pool will be assigned to it. If the unconfigured client has its own MAC address, that MAC address is used. If the client has its own MAC address and it is configured using the ncia client command, the two MAC addresses must match; otherwise, the connection will not be established.
If you do not specify the all keyword as the supported traffic type when you configure an NCIA client, the client only supports only SNA traffic.
Examples
The following example configures an NCIA client on a router:
ncia client 1 10.2.20.5 1111.2222.3333Related Commands
ncia server
Configures an NCIA server on a Cisco router.
dlsw local-peer
Defines the parameters of the data-link switching plus (DLSw+) local peer.
ncia rsrb
To configure an remote source-route bridging (RSRB) ring to associate with an native client interface architecture (NCIA) server on a Cisco router, use the ncia rsrb command in global configuration mode. To remove the configuration, use the no form of this command.
ncia rsrb virtual-ring local-bridge local-ring ncia-bridge ncia-ring virtual-mac-address
no ncia rsrb
Syntax Description
Defaults
No RSRB ring is configured.
Command Modes
Global configuration
Command History
Usage Guidelines
You must use the ncia server command to configure an NCIA server on the router before using the ncia rsrb command to configure an RSRB ring to associate with the server.
Examples
The following example configures a virtual ring to associate with an NCIA server on a Cisco router:
source-bridge ring-group 22source-bridge ring-group 44ncia rsrb 44 4 33 3 22 1111.1111.2222Related Commands
ncia server
Configures an NCIA server on a Cisco router.
source-bridge ring-group
Defines or removes a ring group from the configuration.
ncia server
To configure an native client interface architecture (NCIA) server on a Cisco router, use the ncia server command in global configuration mode. To remove the configuration, use the no form of this command.
ncia server server-number server-ip-address server-virtual-mac-address virtual-mac-address virtual-mac-range [inbound-only] [keepalive seconds] [tcp_keepalive minutes]
no ncia server
Syntax Description
Defaults
No NCIA server is configured.
Command Modes
Global configuration
Command History
Usage Guidelines
Before configuring an NCIA server, you must use the dlsw local-peer command to configure a data-link switching plus (DLSw+) local peer on this router. Depending on your network design, you may need to use the ncia client command to configure an NCIA client on this router (optional), or use the ncia rsrb command to configure an remote source-route bridging (RSRB) ring to associate with this router (optional).
If you use the inbound-only keyword, there is no need to configure any NCIA clients (the server does not make out-going connections).
In a downstream physical unit (DSPU) configuration, before a client can establish a connection to a downstream physical unit (PU), such as a PC or workstation, the MAC address of the server (server-virtual-mac-address) must be defined at the PC or workstation as the destination MAC address. This MAC address appears as the server MAC address in the output of the show ncia circuits command.
Examples
The following example configures an NCIA server on a Cisco router:
ncia server 1 10.2.20.4 4000.3174.0001 4000.0000.0001 128 keepalive 0 tcp_keepalive 0Related Commands
offload (backup)
To configure a backup group of offload devices, use the offload command in IP host backup configuration mode. To cancel the offload task on the Cisco Mainframe Channel Connection (CMCC) adapter, use the no form of this command.
offload device-address ip-address host-name device-name host-ip-link device-ip-link host-api-link device-api-link [broadcast]
no offload path device-address
Syntax Description
Defaults
No default behavior or values
Command Modes
IP host backup configuration
Command History
Usage Guidelines
Along with the path command, the offload backup command provides a quick way to configure an offload backup group.
Offload devices provide IP connectivity to a mainframe while offloading a large part of the TCP/IP processing to the CMCC adapter. Not every mainframe TCP/IP stack supports offload.
The offload command in IP host backup configuration mode uses the same underlying configuration parameters as the claw command in IP host backup configuration mode.
Examples
The following examples show two methods for entering the same IP host backup group information. The first group of commands is the long form, using the offload interface configuration command. The second group is the shortcut, using the path interface configuration command and an offload IP host backup configuration command.
Long form:
offload c000 00 10.92.10.5 sysa router1 tcpip tcpip tcpip api backupoffload c100 00 10.92.10.5 sysa router1 tcpip tcpip tcpip api backupoffload c200 00 10.92.10.5 sysa router1 tcpip tcpip tcpip api backupShortcut form:
path c000 c100 c200offload 00 10.92.10.5 sysa router1 tcpip tcpip tcpip apiRelated Commands
offload (primary)
To configure an offload device (read and write subchannel) for communication with a mainframe TCP/IP stack in offload mode and configure individual members of an offload backup group for the IP Host Backup feature, use the offload command in interface configuration mode. To cancel the offload task on the Cisco Mainframe Channel Connection (CMCC) adapter, use the no form of this command.
offload path device-address ip-address host-name device-name host-ip-link device-ip-link host-api-link device-api-link [broadcast] [backup]
no offload path device-address
Syntax Description
Defaults
No default behavior or values
Command Modes
Interface configuration
Command History
Usage Guidelines
Offload devices provide IP connectivity to a mainframe while offloading a large part of the TCP/IP processing to the CMCC adapter. Not every mainframe TCP/IP stack supports offload.
The offload command uses the same underlying configuration parameters as does the claw command.
Examples
The following example shows how to enable IBM channel attach offload processing on a CMCC adapter's physical channel interface that is supporting a directly connected ESCON channel:
interface channel 3/0ip address 10.92.0.1 255.255.255.0offload 0100 00 10.92.0.21 CISCOVM EVAL TCPIP TCPIP TCPIP APIThe following example shows how an IP host backup group is specified using the backup keyword:
interface Channel3/0no ip addressno keepaliveshutdownoffload 0100 C0 10.30.1.2 TCPIP OS2TCP TCPIP TCPIP TCPIP API backupoffload 0110 C0 10.30.1.2 TCPIP OS2TCP TCPIP TCPIP TCPIP API backupoffload 0120 C0 10.30.1.2 TCPIP OS2TCP TCPIP TCPIP TCPIP API backupoffload 0110 C2 10.30.1.3 TCPIP OS2TCP TCPIP TCPIP TCPIP APIRelated Commands
offload alias
To assign a virtual IP address to a real IP address for an offload device on a Cisco Mainframe Channel Connection (CMCC) adapter, use the offload alias command in interface configuration mode. To remove the alias IP address, use the no form of this command.
offload alias real-ip alias-ip
no offload alias real-ip alias-ip
Syntax Description
real-ip
Real IP address of the offload-supported device.
alias-ip
Virtual IP address for the offload-supported device.
Defaults
No default behavior or values
Command Modes
Interface configuration
Command History
Usage Guidelines
Configure the offload alias command after you configure TCP/IP offload support on a CMCC adapter.
You can configure up to 8 different alias IP addresses for each real IP address of an offload device. You can assign the same alias IP address to multiple real IP addresses.
Examples
The following example configures TCP/IP offload support on a CMCC adapter for a host located at real IP address 10.10.21.3 with an alias IP address of 10.2.33.88:
interface channel 3/1offload E180 80 10.10.21.3 IPCLUST IPCLUST TCPIP TCPIP TCPIP APIoffload alias 10.10.21.3 10.2.33.88Related Commands
