|
|
Use the commands in this chapter to configure IBM channel attach interface features. For hardware technical descriptions and for information about installing the router interfaces, refer to the hardware installation and maintenance publication for your particular product.
For interface configuration information and examples, refer to the "Configuring IBM Channel Attach" chapter of the Bridging and IBM Networking Configuration Guide.
For a conversion table of the modular products and Cisco 7000 family processors, refer to the "Platform Support" appendix of the Configuration Fundamentals Command Reference.
| adapter-number | Number in the range 0 to 17 that uniquely identifies the relative adapter number (ADAPNO) on this interface. This value must correspond to the ADAPNO parameter configured in the corresponding virtual telecommunications access method (VTAM) XCA definition. |
| mac-address | Media access control (MAC) address of this relative adapter. This is a hexadecimal value in the form of xxxx.xxxx.xxxx. |
This command has no defaults.
Internal LAN configuration
This command first appeared in Cisco IOS Release 11.0.
Before you can configure an internal adapter interface, you must use the bridge-group internal LAN configuration command or the source-bridge internal LAN configuration command to configure the bridging type. The only way to get packets to the Channel Interface Processor (CIP) Systems Network Architecture (SNA) feature is through bridging. These two commands are identical to their interface configuration forms.
For transparent bridging, the bridge-group statements identify the interfaces in the same bridge group. Frames are sent only to the interface in the same bridge group.
For source-route bridging, the source-bridge statements identify the interfaces in the same ring group. Frames are sent only to interfaces in the same ring group.
An Ethernet internal LAN can have a bridge-group command.
A Token Ring or FDDI internal LAN can have either a bridge-group or a source-bridge command, but not both.
The following example configures an Ethernet internal LAN adapter on relative adapter 12 and MAC address 87AD.0462.3FDE:
interface channel 1/2 lan ethernet 20 bridge-group 1 adapter 12 87AD.0462.3FDE
You can use the master indexes or search online to find documentation of related commands.
bridge-group
llc2
name
source-bridge
lan
Use the channel-protocol interface configuration command to define a data rate of either 3 megabytes per second or 4.5 megabytes per second for the Parallel Channel Adapter (PCA) card.
channel-protocol [s | s4]| s | (Optional) Specifies a data rate of 3 megabytes per second. |
| s4 | (Optional) Specifies a data rate of 4.5 megabytes per second. |
If no value is specified, the default data rate for the PCA is 3 megabytes per second.
Interface configuration
This command first appeared in Cisco IOS Release 10.3.
This command is valid for a PCA adapter card configured on a CIP on the Cisco 7000 with RSP7000 and Cisco 7500 series.
The following command specifies a data rate of 4.5 megabytes per second for the interface:
channel-protocol s4
Use the claw interface configuration command to establish the IBM channel attach configuration for an ESCON Channel Adapter (ECA) interface or bus-and-tag Parallel Channel Adapter (PCA) interface on the Cisco 7000 with RSP7000 and Cisco 7500 series.
claw path device-address ip-address host-name device-name host-app device-app [broadcast]| path | Hexadecimal value in the range 0x0000 to 0xFFFF. This value specifies the data path and consists of two digits for the physical connection (either on the host or on the ESCON director switch); one digit for the control unit logical address, and one digit for the channel logical address. If not specified in the IOCP, the control unit logical address and channel logical address default to 0. |
| device-address | Hexadecimal value in the range 0x00 to 0xFE. This is the unit address associated with the control unit number and path as specified in the host IOCP file. The device address must have an even value. |
| ip-address | IP address specified in the HOME statement of the host TCP/IP application configuration file. |
| host-name | Host name specified in the device statement in the host TCP/IP application configuration file. |
| device-name | CLAW workstation name specified in the device statement in the host TCP/IP application configuration file. |
| host-app | Host application name as specified in the host application file. When connected to the IBM TCP host offerings, this value will be tcpip, which is the constant specified in the host TCP/IP application file. When attached to other applications, this value must match the value hard coded in the host application. |
| device-app | CLAW workstation application specified in the host TCPIP application. When connected to the IBM TCP host offerings, this value will be tcpip, which is the constant specified in the host TCP/IP application file. When attached to other applications, this value must match the value hard coded in the host application. |
| broadcast | (Optional) Enables broadcast processing for this subchannel. |
This command has no defaults.
Interface configuration
This command first appeared in Cisco IOS Release 10.3.
This command defines information that is specific to the interface hardware and the IBM channels supported on the interface.
The following example shows how to enable IBM channel attach routing on the CIP port 0, which is supporting a directly connected ESCON channel:
interface channel 3/0 ip address 198.92.0.1 255.255.255.0 claw 0100 00 198.92.0.21 CISCOVM EVAL TCPIP TCPIP
Use the client TN3270 configuration command to limit the number of LU sessions that can be established from a client IP address. Use the no form of this command to remove a single LU limit associated with a particular IP address.
client [ip [ip-mask]] lu maximum number| ip | (Optional) IP address of the client. The ip value is optional when setting the maximum number of LU sessions. If no IP address is specified then the limit is applied to all clients. |
| ip-mask | (Optional) IP network mask for the client. The default is 255.255.255.255 |
| number | (Optional and ignored in no form of the command) Maximum number of LU sessions. The allowed value is from 0 to 65535. |
The default is that there is no limit on the number of concurrent sessions to one client IP address.
In the no form of this command, the default number is 65535.
TN3270 configuration
This command first appeared in Cisco IOS Release 11.2 BC.
An instance of the client (lu limit) command on a given tn3270-server is uniquely identified by the ip-mask and the logical AND of the ip address with that mask. For example, if the command is entered as the following:
client 10.1.1.62 255.255.255.192 lu maximum 2
then it will be stored (and subsequently displayed by write term) as:
client 10.1.1.0 255.255.255.192 lu maximum 2
The maximum specified on the command can be changed simply by reissuing the command with the new value. It is not necessary to remove the command first.
When you use the no client command, only the corresponding client lu maximum statement is removed, as identified by the IP address and IP address mask combination. You cannot use no client to specify an unlimited number of LU sessions.
For example, if a service bureau has 8000 clients and each client IP address is limited to four LU sessions, you will never need more than 32000 concurrent LU definitions even when the service is running at 100 percent capacity.
The following example limits all clients to a maximum of two LU sessions:
client lu maximum 2
The following example limits a client at IP address 10.1.1.28 to a maximum of three LU sessions:
client 10.1.1.28 lu maximum 3
The LU limit can be applied to different subnets as shown in the following example. The most exact match to the client IP address is chosen. Clients with IP addresses that reside in the subnet 10.1.1.64 (those with IP addresses in the range of 10.1.1.64 through 10.1.1.127) are limited to a maximum of 5 LU sessions while other clients with IP addresses in the subnet 10.1.1.0 are limited to a maximum of 4 LU sessions.
client 10.1.1.0 255.255.255.0 lu maximum 4 client 10.1.1.64 255.255.255.192 lu maximum 5
The following example prevents an LU session for the client at IP address 10.1.1.28:
client 10.1.1.28 lu maximum 0
You can use the master indexes or search online to find documentation of related commands.
Use the client TN3270 PU configuration mode command to define a range of locaddrs to be reserved for remote devices. Use the no form of this command to cancel this definition.
client [printer] ip ip-address [mask] lu first-locaddr [last-locaddr]| printer | (Optional) Specifies that a client connection from the nailed IP addresses will be nailed to one of the specified LUs only if the client-session negotiates a model type of 328n, where n is any alphanumeric character. Moreover, it ensures that a printer matching the IP address condition can only use an LU nailed as a printer LU.
If the printer keyword is not specified for any client statement that has this IP address set, all model types can use this range of LUs. |
| ip-address | Specifies remote client IP address. |
| mask | The mask applied to the remote device address. Multiple client IP addresses in the same subnet can be nailed to the same range of locaddrs. |
| first-locaddr | Defines a single locaddr to nail. |
| last-locaddr | (Optional) Defines the end range of inclusive locaddrs to be nailed from first-locaddr to last-locaddr. |
The default is that no LUs are nailed. They are all available to any client.
TN3270 PU configuration mode
This command first appeared in Cisco IOS Release 11.2 BC.
Multiple statements can be configured for one IP address or nail type either on one PU or multiple PUs. But each LU can only appear in one client statement.
A client with a nailed IP address can request one of the nailed LUs via the TN3270 device name. If the requested LU is not available then the connection is rejected.
A client with a nailed IP address cannot request an LU outside the range of nailed LUs for its type (screen or printer).
A client with a non-nailed IP address cannot request an LU that is configured as nailed.
The command will be rejected if some of the locaddrs are already nailed. If the locaddrs are currently in use by other remote clients, the nailing statement will take effect only when the locaddr is made available.
To cancel the definition, the no client form of the command must be entered exactly as the client command was originally configured. If a range of locaddrs was specified, to cancel this definition the whole range of locaddrs must be specified. There is no way to cancel only one locaddr if a whole range of locaddrs was configured.
In the following example, locaddrs 1 to 50 are reserved for remote devices in the 171.69.176.0 subnet:
interface channel 2/2 tn3270-server pu BAGE4 client ip 171.69.176.28 255.255.255.0 lu 1 50
In the following example, locaddrs 1 to 40 are reserved for screen devices in the 171.69.176.0 subnet, while 41 to 50 are reserved for printers in that subnet:
interface channel 2/2 tn3270-server pu BAGE4 client ip 171.69.176.28 255.255.255.0 lu 1 40 client printer ip 171.69.176.28 255.255.255.0 lu 41 50
In the following example, there is an attempt to cancel a definition but this is rejected because it does not specify the full range of locaddrs and the second attempt fails to specify the correct nail type:
interface channel 2/2 tn3270-server pu BAGE4 client printer ip 171.69.176.50 255.255.255.0 lu 1 100 no client printer ip 171.69.176.50 255.255.255.0 lu 1 %Invalid LU range specified no client ip 171.69.176.50 255.255.255.0 lu 1 100 %client ip 171.69.176.50 nail type not matched with configured nail type printer
Use the cmpc interface configuration command to configure a CMPC read subchannel and a CMPC write subchannel. Use the no form of this command to remove a subchannel definition and to deactivate the transmission group.
cmpc path device tg-name {read | write}| path | A four-digit hexadecimal value ranging from 0x0000 to 0xFFFF. For PCA (Bus and Tag) use the value 0x0100. |
| device | A two-digit hexadecimal value that specifies the device address of the CPMC subchannel. |
| tg-name | The name of the CMPC transmission group. The maximum length of the name is 8 characters. |
| {read | write} | The same value, read or write, as specified in the TRL major node. |
No default is specified.
Interface configuration
This command first appeared in Cisco IOS Release 11.2 F.
The hexadecimal path value specifies the data path and consists of two digits for the physical connection (either on the mainframe or on the ESCON Director Switch), one digit for the channel logical address, and one digit for the control unit address.
Each cmpc configuration command in a given CMPC transmission group specifies the same transmission group name. The corresponding tg command specifies the same transmission group name. Together, the cmpc and tg commands make up the transmission group specification.
The cmpc command defines the read/write subchannel addresses that CMPC uses to connect to the host. The command corresponds to the definitions in theTRL major node on the host. Configure the CMPC command on the CIP physical interfaces, slot/0 or slot/1, and not on the CIP internal LAN interface, slot/2. Because CMPC uses read and write subchannel pairs, you can configure the CMPC subchannels on different CIP physical interfaces as long as they are on the same CIP.
The no cmpc command deactivates the CMPC transmission group. If the transmission group is used for a non-HPR connection, all sessions using the TG will be terminated immediately. If the transmission group is an HPR connection, all sessions using the transmission group will be terminated if no other HPR connection is available to the host.
The following example configures a read and a write subchannel on path C020 for the CMPC transmission group named CONFIGE:
cmpc C020 F8 CONFIGE READ cmpc C020 F9 CONFIGE WRITE
You can use the master indexes or search online to find documentation of related commands.
Use the csna interface configuration command to specify the path and device/subchannel on a physical channel of the Cisco 7000 with RSP7000 and Cisco 7500 series router to communicate with an attached mainframe. Use the no form of this command to delete the CIP SNA (CSNA) path.
csna path device [maxpiu value] [time-delay value] [length-delay value]| path | Four-digit hexadecimal value in the range 0x0000 to 0xFFFF. This value specifies the data path and consists of two digits for the physical connection (either on the mainframe or on the ESCON director switch): one digit for the control unit address, and one digit for the channel logical address. The control unit address and channel logical address must be specified. For PCA, use the value 0x0100. |
| device | Device address transmitted on the channel path to select the channel-attached device. For PCA (bus-and-tag), this value refers to the subchannel defined in the XCA major node on the host system. |
| maxpiu value | (Optional) Maximum packet size in bytes that will be transmitted on the interface. The range is 4096 to 65535. The default is 20470 bytes. |
| time-delay value | (Optional) Number of milliseconds to delay before transmitting a received packet on the interface. The range is 0 to 100. The default is 10 ms. |
| length-delay value | (Optional) Amount of data to accumulate, in bytes, before transmitting on the interface. The range is 0 to 65535. The default is 20470 bytes. |
maxpiu value: 20470 (0x4ff6) bytes
time-delay value: 10 ms
length-delay value: 20470 (0x4ff6) bytes
Interface configuration
This command first appeared in Cisco IOS Release 11.0.
This command is valid for an ESCON or PCA card configured on a CIP on the Cisco 7000 with RSP7000 and Cisco 7500 series. This command is required for CSNA support over a physical channel.
Use the maxpiu, time-delay, and length-delay keywords to adjust the CIP interface transmission characteristics. You can set the maximum size of packet that the interface will transmit to match the packet size accepted by the host system. You can adjust the delay between the time a packet is received on one of the CIP internal interfaces and transmitted to the host. You can also adjust the transmit-to-host delay by changing the amount of data the CIP accumulates before transmitting to the host.
Changes to the delay values take effect immediately. Any change to the maximum packet size will take effect after the channel is reinitialized. A length-delay value of 0 sends the packet as soon as possible.
Using the no csna command terminates all subchannels (path and devices) configured on the channel and all Logical Link Control, type 2 (LLC2) sessions established over the subchannels.
The following example shows CSNA, offload, and CLAW configured on the CIP in slot 1, port 0. CSNA can be configured by itself, without dependency on offload or CLAW:
interface channel 1/0 no ip address no keepalive offload c700 c0 172.18.1.217 TCPIP OS2TCP TCPIP TCPIP TCPIP API claw C700 A0 192.18.1.219 EVAL CISCOVM AAA BBB csna 0100 10 csna 0100 11 csna 0100 12
Use the dlur TN3270 configuration command to enable the Systems Network Architecture (SNA) session switch function on the CIP, or to enter dependent logical unit requester (DLUR) configuration mode. Use the no form of this command to disable the SNA session switch function and discard all parameter values associated with the SNA session switch.
dlur| fq-cpname | Fully qualified control point (CP) name used by the SNA session switch and the logical unit (LU) name for the DLUR function. This name must be unique among APPN nodes in the network including other fq-cpname values specified on all other TN3270 servers running under the Cisco IOS software. |
| fq-dlusname | Fully qualified name of the primary choice for the dependent LU server (DLUS). This is the name of an LU, usually a CP, in an APPN host. The fq-dlusname value can be repeated and shared across servers. |
No DLUR function is enabled.
TN3270 configuration
This command first appeared in Cisco IOS Release 11.2.
If the SNA session switch function is already enabled, the dlur command with no arguments puts you in DLUR configuration mode.
Several parameters in the DLUR configuration mode consist of fully qualified names, as defined by the APPN architecture. Fully qualified names consist of two case-insensitive alphanumeric strings, separated by a period. However, for compatibility with existing APPN products, including VTAM, the characters "#" (pound), "@" (at), and "$" (dollar) are allowed in the fully qualified name strings. Each string is from one to eight characters long; for example, RA12.NODM1PP. The portion of the name before the period is the NETID and is shared between entities in the same logical network.
The no dlur command hierarchically deletes all resources defined beneath it.
The following command performs two functions: It enters DLUR configuration mode; and it enables the DLUR function and defines the LU name for the DLUR as SYD.TN3020 and the primary choice for DLUS as SYD.VMG. Note that the NETID portion of both names is the same:
dlur SYD.TN3020 SYD.VMG
Use the dlus-backup DLUR configuration command to specify a backup DLUS for the DLUR function. Use the no form of this command to remove a backup DLUS name.
dlus-backup dlusname2| dlusname2 | Fully qualified name of the backup DLUS for the DLUR. |
No backup DLUS is specified.
DLUR configuration
This command first appeared in Cisco IOS Release 11.2.
Only one backup DLUS can be specified per CIP. If the backup DLUS specified in the dlus-backup command is in use when a no dlus-backup is issued, the connection is not torn down.
Several parameters in the DLUR configuration mode consist of fully qualified names, as defined by the APPN architecture. Fully qualified names consist of two case-insensitive alphanumeric strings, separated by a period. However, for compatibility with existing APPN products, including VTAM, the characters "#" (pound), "@" (at), and "$" (dollar) are allowed in the fully qualified name strings. Each string is from one to eight characters long; for example, RA12.NODM1PP. The portion of the name before the period is the NETID and is shared between entities in the same logical network.
The following command specifies SYD.VMX as the backup DLUS:
dlus-backup SYD.VMX
Use the generic-pool TN3270 configuration command to specify whether or not left-over LUs will be made available to TN3270 sessions that do not request a specific LU or LU pool through TN3270E. Use the no form of this command to selectively remove the permit or deny condition of generic pool use.
generic-pool {permit | deny}| permit | Left-over LUs should be made available to TN3270 users wanting generic sessions. This value is the default. |
| deny | Left-over LUs should not be given to a generic pool. The physical unit (PU) is not automatically fully populated with 255 LOCADDR definitions. The default is the value configured in TN3270 configuration mode. |
In TN3270 configuration mode, generic pool use is permitted.
In PU configuration mode, the default is the value currently configured in TN3270 configuration mode.
TN3270 configuration
PU configuration
This command first appeared in Cisco IOS Release 11.2.
A left-over 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 generic-pool in TN3270 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 configuration mode, the no generic-pool command reverts to the default, which permits generic pool use.
The command takes effect immediately. If generic-pool deny 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 generic-pool permit is specified, any inactive LUs are immediately available for dynamic connections. Moreover, any active LUs that were dynamic previously (before generic-pool deny was issued) return to being dynamic.
The following command permits generic LU pool use:
generic-pool permit
Use the idle-time TN3270 configuration command to specify how many seconds of LU inactivity, from both host and client, before the TN3270 session is disconnected. Use the no form of this command to cancel the idle time period and return to the default.
idle-time seconds| seconds | Number of seconds, from 0 to 65535. A value of 0 means the session is never disconnected. |
The default in TN3270 configuration mode is that the session is never disconnected (0).
The default in PU configuration mode is the value currently configured in TN3270 configuration mode.
TN3270 configuration
PU configuration
This command first appeared in Cisco IOS Release 11.2.
The idle-time command can be entered in either TN3270 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 currently 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 between 600 and 900 seconds are immediately disconnected.
The following command sets an idle-time disconnect value of 10 minutes:
idle-time 600
The following command entered in TN3270 configuration mode sets the default idle-time disconnect value to 0, or never disconnect:
no idle-time
Use the interface channel global configuration command to specify a channel attach interface and enter interface configuration mode.
interface channel slot/port| slot | Specifies the slot number where the CIP is located. The value is in the range 0 to 5. |
| port | Specifies the port number where the CIP is located. The value is in the range 0 to 2. Port 0 and 1 are for physical interfaces. Port 2 is for configuring an internal LAN interface on the CIP. |
This command has no defaults.
Global configuration
This command first appeared in Cisco IOS Release 11.0. It is used only on the Cisco 7000 with RSP7000 and Cisco 7500 series.
The following example shows how to enter interface configuration mode for a CIP in slot 2 and begin configuring port 0:
interface channel 2/0
You can use the master indexes or search online to find documentation of related commands.
claw
cmpc
csna
lan
max-llc2-sessions
offload
tn3270-server
Use the ip precedence command to specify the precedence level for IP traffic in the TN3270 server. The no form of this command removes the precedence value.
ip precedence {screen | printer} value| screen | Specifies the precedence is for screen devices. |
| printer | Specifies the precedence is for printer devices. |
| value | Sets the precedence priority. A value between 0 and 7, with 7 being the highest priority. The default is 0. |
The default is a precedence value of 0 for both screens and printers.
TN3270 server configuration mode
TN3270 PU configuration mode
This command first appeared in Cisco IOS Release 11.2 BC.
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.
The following example assigns a precedence value of 3 to printers:
ip precedence printer 3
You can use the master indexes or search online to find documentation of related commands.
Use the ip tos command to specify the TOS level for IP traffic in the TN3270 server. The no form of this command removes the TOS value.
ip tos {screen | printer} value| screen | Specifies the TOS is for screen devices. |
| printer | Specifies the TOS is for printer devices. |
| value | Sets the TOS priority. A value between 0 and 15. The default is 0. |
The default is a TOS value of 0 for both screens and printers.
TN3270 server configuration mode
TN3270 PU configuration mode
This command first appeared in Cisco IOS Release 11.2 BC.
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 63 shows the values described in RFC 1349.
| Value | Definition | Action |
|---|---|---|
| 0 | All normal. | Use default metric. |
| 8 | Minimize delay. | Use delay metric. |
| 4 | Maximize throughput. | Use default metric. |
| 2 | Maximize reliability. | Use reliability metric. |
| 1 | Minimize monetary cost. | Use cost metric. |
| Other | Not defined. | Reserved for future use. |
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 either 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 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 pu PUS2 ip tos screen 0
You can use the master indexes or search online to find documentation of related commands.
Use the keepalive TN3270 configuration command to specify how many seconds of inactivity elapse before transmission of a DO TIMING-MARK to the TN3270 client. Use the no form of this command to cancel the keepalive period and return to the default.
keepalive seconds| seconds | Number of seconds, from 0 to 65535. A value of 0 means no keepalive signals are sent. The default is 1800 seconds (30 minutes). |
The default in TN3270 configuration mode is 1800 seconds (30 minutes).
The default in PU configuration mode is the value currently configured in TN3270 configuration mode.
TN3270 configuration
PU configuration
This command first appeared in Cisco IOS Release 11.2.
The keepalive command can be entered in either TN3270 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 keepalive command entered in PU configuration mode will restore the keepalive value entered in TN3270 command mode.
If the client does not reply within 30 minutes of the transmission of 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.
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 will usually take much less than 30 minutes.
The keepalive command affects currently active and future TN3270 sessions. For example, reducing the value to a smaller nonzero value will cause an immediate burst of DO TIMING-MARKs on those sessions that have been inactive for a period of time greater than the new, smaller value.
The following command sets an keepalive disconnect value of 15 minutes (900 seconds):
keepalive 900
The following command entered in TN3270 configuration mode sets the keepalive disconnect value to 1800 seconds, the default:
no keepalive
| type | Interface type for this internal LAN: ethernet, tokenring, or fddi. |
| lan-id | A number 0 to 31 that uniquely identifies this internal LAN on this CIP. This value must be unique between all internal LANs of the same interface type on a CIP. |
This command has no defaults.
Interface configuration
This command first appeared in Cisco IOS Release 11.0.
An internal LAN can be configured only on CIP interface port 2. Interface port 2 represents an internal port on the CIP. You receive an error message if you attempt to configure an internal LAN on any CIP port other than port 2.
The following example shows how to configure an internal LAN Ethernet with a LAN ID of 20 on the CIP in slot 1, port 2:
interface channel 1/2 lan ethernet 20
Use the link DLUR SAP configuration command to define and activate a link to a host. Use the no form of this command to delete the link definition.
link name [rmac rmac] [rsap rsap]| name | Link name, from one to eight alphanumeric characters. The first character must be alphabetic. The name must be unique within the DLUR function. |
| rmac | (Optional) Remote MAC address of the form xxxx.xxxx.xxxx in hexadecimal. If not specified, a loopback link to another SAP on the same internal LAN adapter is assumed. |
| rsap | (Optional) Remote SAP address, 04 to FC in hexadecimal. The rsap value must be even and should be a multiple of 4, but this requirement is not enforced. The rsap value default is 04. |
No DLUR link is defined.
The default remote SAP address is 04 (hexadecimal).
DLUR SAP configuration
This command first appeared in Cisco IOS Release 11.2.
The combination of rmac and rsap must be unique within the DLUR SAP function. These values can only be changed by deleting the link definition, using the no link command, and recreating the link definition.
For a link via a channel on this CIP, the TN3270 server and the hosts should open different adapters in the same internal LAN. Using different adapters avoids any contention for SAP numbers, and is also necessary if you configure duplicate MAC addresses for fallback CSNA access to the host. By configuring the adapters in the same internal LAN, you achieve the same performance--bypassing the DLC stacks--as looping back on a single adapter.
The following command defines a link name and a remote SAP address:
link LINK5 rsap 08
The 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 0 adapter 0 4000.0000.0001 adapter 1 4000.0000.0002 tn3270-server dlur ... lsap token-adapter 1 link HOST rmac 4000.0000.0001 rsap 4
Use the lsap DLUR configuration command to create a SAP in the SNA session switch, or to enter DLUR SAP configuration mode. Use the no form of this command to delete a SAP and all SNA session switch links using the internal LAN interface.
lsap| type | Internal adapter type on the CIP card, which corresponds to the value specified in the lan internal LAN configuration command. The currently supported type is token-adapter. |
| adapter-number | Internal adapter interface on the CIP card, which is the same value specified in the adapter internal LAN configuration command. |
| lsap | (Optional) Local SAP number, 04 to FC, in hex. The value must be even and should normally be a multiple of four. It must be unique within the internal adapter in that no other 802.2 clients of that adapter, in the router or in a host, should be allocated the same SAP. The default value is C0. |
The default value for lsap is hexadecimal C0.
DLUR configuration
This command first appeared in Cisco IOS Release 11.2.
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 CIP internal LAN interface are used in the lsap command.
However, the lan type keyword is a little different. Where the type on the lan command is tokenring, the corresponding type 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.
The following command defines an adapter type, an adapter number, and a local SAP:
lsap token 0 B0
You can use the master indexes or search online to find documentation of related commands.
Use the max-llc2-sessions internal adapter configuration command to specify the number of concurrent LLC2 sessions that will be supported on the CIP interface. Use the no form of this command to remove a value.
max-llc2-sessions numberSyntax Description
| number | A value in the range 0 to 4000. If no value is specified, the default is 256. |
The default number of sessions is 256.
Internal adapter configuration
This command first appeared in Cisco IOS Release 11.0.
The maximum number of LLC2 sessions can be configured only on CIP interface port 2. To specify an unlimited number of LLC2 sessions, either omit this command from the adapter configuration on CIP interface port 2, or use a value of 0.
When configured for an unlimited number of LLC2 sessions, the actual number of sessions is determined by the available memory on the CIP.
The following example limits the maximum number of LLC2 sessions to 212:
max-llc2-sessions 212
Use the maximum-lus TN3270 configuration command to limit the number of LU control blocks that will be allocated for TN3270 server use. Use the no form of this command to restore the default value.
maximum-lus number| number | Maximum number of LU control blocks allowed. The allowed range is 0 to 32000. However, the practical upper limit for concurrently operating TN3270 sessions depends on the hardware and usage characteristics. The default is 2100. |
Because of the license structure, the default is 2100, which represents the limit of the lower-priced license (2000) plus a five percent buffer. If you configure a value greater than the default, a license reminder is displayed.
TN3270 configuration
This command first appeared in Cisco IOS Release 11.2.
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 PU is inactivated by DACTPU or by using the no pu command.
If the number of LUs in use reaches 94% of the current setting of maximum-lus, a warning message is displayed on the console. To prevent annoyance, 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 ACTLU from the SSCP host.
By limiting the number of LU control blocks allocated, you can make sure enough memory is available to support other CIP 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 CIP, 32 MB of memory will support 4000 LUs. To support more than 4000 LUs, we recommend 64 MB of memory.
The following command allows 5000 LU control blocks to be allocated:
maximum-lus 5000
You can use the master indexes or search online to find documentation of related commands.
client (lu limit)
pu (DLUR)
pu (direct)
Use the name internal adapter configuration command to give a name to the internal adapter. Use the no form of the command to remove the name assigned to an internal adapter.
name name| name | Name that identifies this internal adapter. Consists of up to 8 characters that does not include blanks. |
This command has no defaults.
Internal adapter configuration
This command first appeared in Cisco IOS Release 11.0.
The following example assigns a name to an internal adapter interface:
name VTAM_B14
| path | Hexadecimal value in the range 0x0000 to 0xFFFF. This value specifies the data path and consists of two digits for the physical connection (either on the host or on the ESCON director switch): one digit for the control unit address, and one digit for the channel logical address. If not specified in the IOCP, the control unit address and channel logical address default to 0. |
| device-address | Hexadecimal value in the range 0x00 to 0xFE. This is the unit address associated with the control unit number and path as specified in the host IOCP file. The device address must have an even value. |
| ip-address | IP address specified in the host TCP/IP application configuration file. |
| host-name | Host name specified in the device statement in the host TCP/IP application configuration file. |
| device-name | CLAW workstation name specified in the device statement in the host TCP/IP application configuration file. |
| host-app | Host application name as specified in the host application file. When connected to the IBM TCP host offerings, this value will be tcpip, which is the constant specified in the host TCP/IP application file. When attached to other applications, this value must match the value hard-coded in the host application. |
| device-app | CLAW workstation application specified in the host TCP/IP application. When connected to the IBM TCP host offerings, this value will be tcpip, which is the constant specified in the host TCP/IP application file. When attached to other applications, this value must match the value hard-coded in the host application. |
| host-link | Host application name providing the CLAW API link. For IBM compatible offload software, this will always be tcpip. |
| device-link | CLAW workstation application name providing the CLAW API link. For IBM compatible offload software, this will always be api. |
| broadcast | (Optional) Enables broadcast processing for this subchannel. |
This command has no defaults.
Interface configuration
This command first appeared in Cisco IOS Release 11.0.
The offload command uses the same underlying configuration parameters as does the claw command.
The following example shows how to enable IBM channel attach offload routing on the CIP port 0, which is supporting a directly connected ESCON channel:
interface channel 3/0 ip address 198.92.0.1 255.255.255.0 offload 0100 00 198.92.0.21 CISCOVM EVAL TCPIP TCPIP TCPIP API
Use the preferred-nnserver DLUR configuration command to specify a preferred network node (NN) as server. Use the no form of this command to remove the preference.
preferred-nnserver name| name | A fully qualified name of a NN. |
This command has no defaults.
DLUR configuration
This command first appeared in Cisco IOS Release 11.2.
Fully qualified names consist of two case-insensitive alphanumeric strings, separated by a period. However, for compatibility with existing APPN products, including VTAM, the characters "#" (pound), "@" (at), and "$" (dollar) are allowed in the fully qualified name strings. Each string is from one to eight characters long; for example, RA12.NODM1PP. The portion of the name before the period is the NETID and is shared between entities in the same logical network.
When no preferred server is specified, the DLUR will request NN server support from the first suitable node with which it makes contact. If refused, it will try the next one, and so on.
If a preferred server is specified, then DLUR will wait a short time to allow a link to the preferred server to materialize. If the preferred server is not found in that time, any suitable node can be used, as above.
DLUR will not relinquish the current NN server merely because the preferred server becomes available.
The following command selects SYD.VMX as the preferred NN server:
preferred-nnserver SYD.VMX
Use the pu DLUR configuration command to create a PU entity that has no direct link to a host or to enter PU configuration mode. Use the no form of this command to remove the PU entity.
pu pu-name| pu-name | Name that uniquely identifies this PU. |
| idblk-idnum | This value must match the idblk-idnum value defined at the host. The value must be unique within the subarea; however, the TN3270 server generally cannot tell which remote hosts are in which subareas, so the server only enforces uniqueness within the set of DLUR PUs. |
| ip-address | IP address that the clients should use as host IP address to map to LU sessions under this PU. |
No PU is defined.
DLUR configuration
This command first appeared in Cisco IOS Release 11.2.
If the PU is already created, the pu pu-name command with no arguments puts you in PU configuration mode. In this mode you can modify an existing PU DLUR entity.
A typical usage for the IP address is to reserve an IP address per host application. For example, clients wanting to connect to TSO specify an IP address that will be defined with PUs that have LOGAPPL=TSO.
The following sequence of commands define three PUs. Two of the PUs share the same IP address and the third PU has a separate IP address:
pu p0 05D99001 192.195.80.40 pu p1 05D99002 192.195.80.40 pu p2 05D99003 192.195.80.41
Use the pu TN3270 configuration command to create a PU entity that has its own direct link to a host, or to enter PU configuration mode. Use the no form of this command to remove the PU entity.
pu pu-name idblk-idnum ip-address type adapter-number lsap [rmac rmac] [rsap rsap]| pu-name | Name that uniquely identifies this PU. |
| idblk-idnum | This value must match the IDBLK-IDNUM value defined at the host. The value must be unique within the subarea; however, the TN3270 Server cannot tell which remote hosts are in which subareas and does not enforce the unique value requirement. |
| ip-address | IP address that the clients should use as host IP address to map to LU sessions under this PU. |
| type | Internal adapter type on the CIP card, which corresponds to the value specified in the lan internal LAN configuration command. The currently supported type is token-adapter. |
| adapter-number | Internal adapter interface on the CIP card, which is the same value specified in the adapter internal LAN configuration command. |
| lsap | Local SAP number in hexadecimal, ranging from 04 to FC. The value must be even, and must be unique within the internal adapter so that no other 802.2 clients of that adapter, in the router or in a host, should be allocated the same SAP. Other direct links from TN3270 server direct PUs may use the same value on the internal adapter as long as the remote MAC or SAP is different. |
| rmac rmac | (Optional) Remote MAC address. The remote MAC address of the form xxxx.xxxx.xxxx hexadecimal, specifying the MAC address of the remote host. If not specified, a loopback link to another SAP on the same internal LAN adapter is assumed. |
| rsap rsap | (Optional) Remote SAP address. The remote SAP address is a one- or two-character hexadecimal string, ranging from 04 to FC, specifying the SAP address of the remote host. The default is 04. |
| lu-seed lu-name-stem | (Optional) Provides an LU name that the client can use when a specific LU name request is needed. The format can be x...x## or x...x### where x..x is an alphanumeric string. When ## is specified, it is replaced with the LU LOCADDR in hexadecimal digits to form the complete LU name. When ### is specified, decimal digits are used, padded with leading zeroes to make three characters. The first x must be alphabetic and the entire string, including the # symbols, must not exceed 8 characters. |
No PU is defined.
The default remote SAP address is 04 (hexadecimal).
TN3270 configuration
This command first appeared in Cisco IOS Release 11.2.
If the PU is already created, the pu pu-name command with no arguments puts you in PU configuration mode, where you can modify an existing PU entity.
The pu (direct) 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 CIP internal LAN interface are used in the pu command.
For a link via a channel on this CIP, the TN3270 server and the hosts should open different adapters in the same internal LAN. Using different adapters avoids any contention for SAP numbers, and is also necessary if you configure duplicate MAC addresses for fallback CSNA access to the host. By configuring the adapters in the same internal LAN, you achieve the same performance--bypassing the DLC stacks--as looping back on a single adapter.
The following commands configure the TN3270 server to be active, and has one PU, CAPPU1, trying to connect in. An LU seed using hexadecimal digits is defined.
tn3270-server pu CAPPU1 05D18101 10.14.20.34 token-adapter 3 rmac 4000.0501.0001 lu-seed CAP01L##
The 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 0 adapter 0 4000.0000.0001 adapter 1 4000.0000.0002 tn3270-server pu PU1 05d00001 10.0.0.1 token-adapter 1 8 rmac 4000.0000.0001 rsap 4
You can use the master indexes or search online to find documentation of related commands.
Use the show extended channel cmpc privileged EXEC command to display information about each CMPC subchannel configured on the specified CIP interface.
show extended channel slot/port cmpc [path [device]]| slot | Slot number. |
| port | Port number, which must be 0 or 1. |
| path | (Optional) A 4-digit hexadecimal value in the ranging from 0x0000 to 0xFFFF. For PCA (Bus and Tag) use the value 0x0100. If specified, status for all CMPC devices for the specified path will be displayed. If not specified, status for all CMPC devices for all paths under that interface will be displayed. |
| device | (Optional) A 2-digit hexadecimal value that specifies a device address of the CPMC subchannel. If specified, only status for that CMPC device will be displayed. If not specified, status for all CMPC devices for the specified path will be displayed. |
Privileged EXEC
This command first appeared in Cisco IOS Release 11.2 BC.
This command is valid only on the CIP physical interfaces, slot/0 or slot/1.
The following is sample output on a Cisco 7500 router from the show extended channel cmpc command:
router# show extended channel 3/0 cmpc c020
Path Dv TGName Dir Bfrs Status
CMPC C020 46 MVS2ISRA READ 10 Active
CMPC C020 47 MVS2ISRA WRITE 16 Active
CMPC C020 4A MVS2ISR1 READ 7 Active
CMPC C020 4B MVS2ISR1 WRITE 16 Active
CMPC C020 4C MVS2ISR2 READ 7 Active
CMPC C020 4D MVS2ISR2 WRITE 16 Active
CMPC C020 4E MVS2TN READ 0 Inactive
CMPC C020 4F MVS2TN WRITE 0 Inactive
Table 64 describes the fields shown in the display.
| Field | Description |
|---|---|
| Path | CMPC channel path configured. |
| Dv | CMPC subchannel device configured. |
| TGName | Transmission group name configured for the CMPC subchannel. |
| Dir | Identifies this CMPC subchannel as READ or WRITE. |
| Bfrs | On the read subchannel, this is the number of 4 K-size pages that VTAM has allocated for each Read. This will match the MAXBFRU value configured in the VTAM TRL major node. On the write subchannel, this is the maximum number of 4 K pages VTAM can write to the CIP for a single channel I/O. The value will always be 16 for the write subchannel because the CIP always allows VTAM to write up to 64 KB per channel I/O. |
| Status | State of the CMPC subchannel. Valid values are:
|
Use the show extended channel icmp-stack privileged EXEC command to display information about the Internet Control Message Protocol (ICMP) stack running on the CIP interfaces in a Cisco 7000 with RSP7000 and Cisco 7500 series.
show extended channel slot/port icmp-stack [ip-address]| slot | Slot number. |
| port | Port number. |
| ip-address | (Optional) Offload IP address. |
Privileged EXEC
This command first appeared in Cisco IOS Release 11.0.
The following is sample output on the Cisco 7000 with RSP7000 from the show extended channel icmp-stack command:
router# show extended channel 4/0 icmp-stack
ICMP Statistics for IP Address 198.92.1.120
InMsgs : 200 InErrors : 201 InDestUnreachs: 202
InTimeExcds : 203 InParmProbs : 204 InSrcQuenchs : 205
InRedirects : 206 InEchos : 207 OutEchoReps : 213
OutTimestamps : 214 OutTimestampReps: 215 OutAddrMasks : 216
OutAddrMaskReps: 217
ICMP Statistics for IP Address 198.92.1.121
InMsgs : 201 InErrors : 202 InDestUnreachs: 203
InTimeExcds : 204 InParmProbs : 205 InSrcQuenchs : 206
InRedirects : 207 InEchos : 208 OutEchoReps : 214
OutTimestamps : 215 OutTimestampReps: 216 OutAddrMasks : 217
OutAddrMaskReps: 218
Use the show extended channel ip-stack privileged EXEC command to display information about the IP stack running on the CIP interfaces in a Cisco 7000 with RSP7000 and Cisco 7500 series.
show extended channel slot/port ip-stack [ip-address]| slot | Slot number. |
| port | Port number. |
| ip-address | (Optional) IP address specified by the offload interface configuration command. |
Privileged EXEC
This command first appeared in Cisco IOS Release 11.0.
The following is sample output on the Cisco 7000 with RSP7000 from the show extended channel ip-stack command:
router# show extended channel ip-stack
IP Statistics for IP Address 198.92.1.120
Forwarding : fowarding DefaultTTL : 2 InReceives : 3
InHdrErrors : 4 InAddrErrors : 5 ForwDatagrams: 6
InUnknownProtos: 7 InDiscards : 8 InDelivers : 1313371
OutRequests : 10 OutDiscards : 11 OutNoRoutes : 12
ReasmTimeout : 13 ReasmReqds : 14 ReasmOKs : 15
ReasmFails : 16 FragOKs : 17 FragFails : 18
FragCreates : 19 RoutingDiscards: 20
IP Statistics for IP Address 198.92.1.121
Forwarding : nofoward DefaultTTL : 3 InReceives : 4
InHdrErrors : 5 InAddrErrors : 6 ForwDatagrams: 7
InUnknownProtos: 8 InDiscards : 9 InDelivers : 1313371
OutRequests : 11 OutDiscards : 12 OutNoRoutes : 13
ReasmTimeout : 14 ReasmReqds : 15 ReasmOKs : 16
ReasmFails : 17 FragOKs : 18 FragFails : 19
FragCreates : 20 RoutingDiscards: 21
Use the show extended channel llc2 privileged EXEC command to display information about the LLC2 sessions running on the CIP interfaces in a Cisco 7000 with RSP7000 and Cisco 7500 series.
show extended channel slot/port llc2 [admin | oper | stats] [lmac [lsap [rmac [rsap]]]]| slot | Slot number. |
| port | Port number. |
| admin | (Optional) Shows configured values. This is the default. |
| oper | (Optional) Shows operational values. |
| stats | (Optional) Shows statistics. |
| lmac | (Optional) Local MAC address. |
| lsap | (Optional) Local service access point (SAP) address, 0 to 256. |
| rmac | (Optional) Remote MAC address. |
| rsap | (Optional) Remote SAP address, 0 to 256. |
The default is admin.
Privileged EXEC
This command first appeared in Cisco IOS Release 11.0.
The default mode of this command is to show the admin (configured) values.
The following is sample output on the Cisco 7000 with RSP7000 from the show extended channel llc2 command:
router# show extended channel 2/2 llc2 admin
Vlan Token 0 vadapter 0 0004.0004.0004
t1-time = 1000 tpf-time = 1000 trej-time = 3200 tbusy-tim = 9600
idle-time =60000 local-win = 7 recv-wind = 7 N2 = 8
N1 = 1033 ack-delay = 100 ack-max = 3 nw = 0
Use the show extended channel statistics privileged EXEC command to display information about the CIP interfaces on the Cisco 7000 with RSP7000 and Cisco 7500 series. This command displays information that is specific to the interface hardware. The information is generally useful only for diagnostic tasks performed by technical support personnel.
show extended channel slot/port statistics [path [device-address]]| slot | Slot number. |
| port | Port number. |
| path | (Optional) Hexadecimal value in the range 0x0000 to 0xFFFF. This specifies the data path and consists of two digits for the physical connection (either on the host or on the ESCON Director switch): one digit for the control unit address, and one digit for the channel logical address. If not specified, the control unit address and channel logical address default to 0. |
| device-address | (Optional) Hexadecimal value in the range 0x00 to 0xFE. This value is the unit address associated with the control unit number and path as specified in the host IOCP file. For CLAW and offload support, the device address must have an even value. |
The data path default for the control unit address and the channel logical address is 0.
Privileged EXEC
This command first appeared in Cisco IOS Release 10.3.
The following is sample output on the Cisco 7000 with RSP7000 from the show extended channel statistics command:
router# show extended channel 3/0 statistics
Path: C300 - ESTABLISHED
Command Selective System Device CU
Dev Connects Retries Cancels Reset Reset Errors Busy
60 92 85 5 4 1 0 0
61 94 0 4 3 1 0 0
Blocks Bytes Dropped Blk Fail
Dev-Lnk Read Write Read Write Read Write memd Con
60-00 6 0 192 0 8 0 0 Y
60-01 82 0 7373 0 0 0 0 Y
Total: 88 0 7565 0 8 0 0
61-00 0 4 0 128 0 0 0 Y
61-01 0 85 0 9081 0 0 0 Y
Total: 0 89 0 9209 0 0 0
Path C300
Total: 88 89 7565 9209 8 0 0
Last stats 8 seconds old, next in 2 seconds
Table 65 describes the fields shown in the display.
| Field | Description |
|---|---|
| Path | The path from the CLAW, offload, or CSNA configuration. It tells which port on the switch is used by the channel side of the configuration. |
| Dev | The device address for each device. For CLAW you get two device addresses. In the configuration statement, you only specify the even address. Both CLAW and offload get two devices and CSNA gets 1. |
| Connects | The number of times the channel started a channel program on the device. |
| Command Retries | The number of times the CIP either had no data to send to the channel (for the read subchannel) or the number of times the CIP had no buffers to hold data from the channel (for the write subchannel). Every command retry that is resumed results in a connect. A command retry may be ended via a cancel. |
| Cancels | The host requested any outstanding operation to be terminated. It is a measure of the number of times the host program was started. |
| Selective Reset | Selective reset affects only one device, whereas a system reset affects all devices on the given channel. It is a reset of the device. On VM this will occur whenever you have a device attached and issue a CP IPL command. |
| System Reset | The number of times the system Initial program load (IPL) command was issued. The command is always issued when the ECA is initialized, and when the channel is taken off line. |
| Device Errors | Errors detected by the ECA or PCA due to problems on the link. This value should always be 0. |
| CU Busy | The number of times the adapter returned a control unit busy indication to the host. This occurs after a cancel or reset if the host requests an operation before the CIP has finished processing the cancel or reset. |
| Dev-Lnk | The first number is the device address. The second number is the logical link. Link 0 is always used for CLAW control messages. For IP datagram mode, link 1 is for actual datagram traffic.
For offload, link 2 is for API traffic. For CSNA, the Dev-Lnk is not relevant. |
| Blocks Read/Blocks Write | CLAW uses the even subchannel for reads and the odd subchannel for writes. Each count is one IP datagram or one control message. |
| Bytes Read/Bytes Write | Bytes is the sum of the bytes in the blocks. |
| Dropped Blk Read/Write | If the router switch processor sends data to the CIP faster than it can send it to the channel, then the block is dropped. High values mean the host is not running fast enough. There are drops on write too. A write drop will occur if the CIP fails to get a MEMD buffer n times for a given block. See Failed memd counter. |
| Failed memd | The number of times the CIP could not obtain a MEMD buffer on the first try. If this value is high, try allocating more large buffers. The memd information does not apply to CSNA devices. |
| Con | For link 0, connect of Y means the system validation has completed. For all other links, it means the connection request sequence has completed. Con is an abbreviation for connected. For CSNA devices, a value of Y is displayed when the CSNA device status becomes setupComplete. For all other states, the Con shows a value of N. |
Use the show extended channel subchannel privileged EXEC command to display information about the CIP interfaces on the Cisco 7000 with RSP7000 and Cisco 7500 series. This command displays information that is specific to the interface hardware. The information displayed is generally useful only for diagnostic tasks performed by technical support personnel.
show extended channel slot/port subchannel| slot | Slot number. |
| port | Port number. |
Privileged EXEC
This command first appeared in Cisco IOS Release 10.3.
The following is sample output on the Cisco 7000 with RSP7000 from the show extended channel subchannel command:
router# show extended channel 3/0 subchannel
Channel3/0: state up
Flags: VALID ESCON LOADED RQC_PEND MEMD_ENABLED
Link: C4, Buffers 0, CRC errrors 0, Load count 1
Link Incident Reports
implicit 0, bit-error 0, link failed 0,
NOS 0, sequence timeout 0, invalid sequence 0
Neighbor Node - VALID
Class: Switch Type Number : 009033 Tag: C4
Model: 001 Manufacturer: IBM
Plant: 51 Sequence : 000000010067
Local Node - VALID
Class: CTCA-standalone Type Number : C7000 Tag: 30
Model: 0 Manufacturer: CSC
Plant: 17 Sequence : 00000C04953F
Last
Mode Path Device Sense
CLAW C300 60 198.92.1.58 CISCOVM AUBURN TCPIP TCPIP 0000
CLAW C300 61 198.92.1.58 CISCOVM AUBURN TCPIP TCPIP 0080
Last stats 1 seconds old, next in 9 seconds
The first line describes the status of the specified CIP and port. The status can be up, down, or administratively down:
Channel3/0: state up
The next line describes the flags on the CIP:
Flags: VALID ESCON LOADED RQC_PEND MEMD_ENABLED
The next line displays Link Incident Reports:
Link Incident Reports
implicit 0, bit-error 0, link failed 0,
NOS 0, sequence timeout 0, invalid sequence 0
Link Incidents are errors on an ESCON channel. These errors are reported to the host operating system and are recorded here for additional information.
Implicit incidents indicate a recoverable error occurred in the ECA.
Bit errors indicate the bit error rate threshold was reached. The bit error rate threshold is 15 error bursts within 5 minutes. An error burst is defined as a time period of 1.5+/-.5 seconds during which one or more code violations occurred. A code violation error is caused by an incorrect sequence of 10 bit characters.
Link failed means a loss of synchronization or light has occurred.
NOS means the channel or switch transmitted the Not Operational Sequence.
Sequence timeout occurs when a connection recovery timeout occurs or when waiting for the appropriate response while in the transmit off-line sequence (OLS) state.
Invalid Sequence occurs when a UD or UDR is recognized in the wait for offline sequence state. UD is an unconditional disconnect and UDR is an unconditional disconnect response.
The neighbor node describes the channel or switch. The local node describes the router. The VALID flag shows information has been exchanged between the router and channel or switch.
The information displayed under Neighbor Node is as follows:
Neighbor Node - VALID
Class: Switch Type Number : 009033 Tag: C4
Model: 001 Manufacturer: IBM
Plant: 51 Sequence : 000000010067
Class will be switch or channel depending on whether the connection is a switched point-to-point connection or a point-to-point connection. The type number describes the model of switch or processor. The TAG describes the physical location of the connector. Model is a further classification of type. Manufacturer describes who made switch or processor. Plant and sequence are manufacturer specific information to uniquely define this one device.
The information displayed under Local Node is as follows:
Local Node - VALID
Class: CTCA-standalone Type Number : C7000 Tag: 30
Model: 0 Manufacturer: CSC
Plant: 17 Sequence : 00000C04953F
The class will be CTCA. The type number and model define the router. The tag is the slot and port where the channel interface processor resides. Manufacturer will always be CSC (for Cisco Systems). Plant is the location where the CIP was manufactured. Sequence is the base Ethernet address assigned to the route processor (RP).
The last three lines show currently configured information for the inbound and outbound channel connections:
Last
Mode Path Device Sense
CLAW C300 60 198.92.1.58 CISCOVM AUBURN TCPIP TCPIP 0000
CLAW C300 61 198.92.1.58 CISCOVM AUBURN TCPIP TCPIP 0080
Mode can be CLAW, offload, or CSNA. Path, device, IP address, and names are from the CLAW command. Because CLAW and offload commands define two devices, both devices are shown. Last sense is the two bytes of sense data transmitted to the host at the time of the last unit exception. Normally the value will be 0000 if no unit exception has occurred, or 0080 to indicate that a resetting event has occurred. Resetting events occur whenever an ESCON device starts unless the first command is a 0x02 read command. The CLAW read subchannel always starts with a 0x02 read command so a resetting event will not occur.
Use the show extended channel tcp-stack privileged EXEC command to display information about the TCP stack running on the CIP interfaces in a Cisco 7000 with RSP7000 and Cisco 7500 series.
show extended channel slot/port tcp-stack [ip-address]| slot | Slot number. |
| port | Port number. |
| tcp-stack | IP address for the TCP stack on the CIP. |
| ip-address | (Optional) IP address specified in an offload interface configuration command or tn3270-server PU configuration command. |
Privileged EXEC
This command first appeared in Cisco IOS Release 11.0.
The following is sample output on the Cisco 7000 with RSP7000 from the show channel tcp-stack command:
router# show extended channel tcp-stack
TCP Statistics for IP Address 198.92.1.120
RtoAlgorithm: other RtoMin : 101 RtoMax : 102
MaxConn : 103 ActiveOpens : 104 PassiveOpens: 105
AttemptFails: 106 EstabResets : 107 CurrEstab : 108
InSegs : 109 OutSegs : 110 RetransSegs : 111
InErrs : 112 OutRsts : 113
TCP Statistics for IP Address 198.92.1.121
RtoAlgorithm: constant RtoMin : 102 RtoMax : 103
MaxConn : 104 ActiveOpens : 105 PassiveOpens: 106
AttemptFails: 107 EstabResets : 108 CurrEstab : 109
InSegs : 110 OutSegs : 111 RetransSegs : 112
InErrs : 113 OutRsts : 114
Use the show extended channel tg privileged EXEC command to display configuration, operational information, and statistics information for CMPC transmission groups configured on the specified CIP internal LAN interface.
show extended channel slot/2 tg [oper | stats] [detailed] [tg-name]| slot/2 | Slot number. |
| oper | (Optional) Operational parameters for the CMPC transmission group values. |
| stats | (Optional) Statistical values for the CMPC transmission group. |
| detailed | (Optional) Additional LLC information about the CMPC transmission group. |
| tg-name | (Optional) Information for the specified tg-name. |
Privileged EXEC
This command first appeared in Cisco IOS Release 11.2 BC.
If neither the oper or stats arguments are specified, operational values will be displayed.
The following is sample output on a Cisco 7500 router from the show extended channel tg oper command:
router# show extended channel 3/2 tg oper detailed MVS2-TG1
CMPC-TG: MVS2-TG1 Status: ACTIVE
Adapter:token 1 RMAC:4000.4040.1996 LSAP:04 RSAP:04
TGN :21 Local CP: NETA.MVS2 Remote CP: NETA.CALEB
MaxIn :4105 MaxOut :4105
HPR :NO HPR LSAP:04 HPR RSAP :00
RIF :0830.1FF1.0041.00A0
Connection LLC2 Information:
t1-time = 1000 tpf-time = 1000 trej-time = 3200 tbusy-tim = 9600
idle-time =60000 local-win = 7 recv-wind = 7 N2 = 8
N1-Send = 1033 N1-Rcv = 1033 ack-delay = 100 ack-max = 3
Nw = 0 Ww = 7
Last Ww Cause = other
Connection Time: 00:00:00 UTC Jan 1 1970
Last modified: 00:00:00 UTC Jan 1 1970
Table 66 describes the fields shown in the display.
| Field | Description |
|---|---|
| Status | Connection status of the CMPC transmission group. Valid values are:
|
|
Adapter | Identifies the CIP internal MAC adapter configured for this CMPC transmission group. The MAC address configured for this adapter is the local MAC address for the CMPC transmission group LLC connection. |
| RMAC | Remote MAC address configured for the CMPC transmission group LLC connection. |
| LSAP | Local SAP configured for the CMPC transmission group LLC connection. |
| RSAP | Remote SAP configured for the CMCP transmission group LLC connection. |
| TGN | Transmission group number for this CMPC transmission group LLC connection. This value is extracted from the XID3 negotiation exchange. |
| Local CP | Control point name for VTAM. The name is extracted from XID3s received from VTAM. |
| Remote CP | Control point name for the remote node connected by this CMPC transmission group. The name is extracted from XID3 received from the remote node. |
| MaxIn | Maximum PIU the remote node is allowed to send to VTAM. The value is the max PIU field in the XID3s received from VTAM. |
| MaxOut | Maximum PIU VTAM is allowed to send to the remote node. The value is the lowest of the max PIU field in the XID3 received from the remote node, the LF (length field) size in the RIF and the CIP virtual interface MTU size. |
| HPR | Valid values are YES and NO. If HPR is active on this CMPC transmission group, then the value will display YES. |
| HPR LSAP | Local SAP value used for HPR traffic. This value will be the same as the configured local SAP value. |
| HPR RSAP | Remote SAP value used for HPR traffic. This value is extracted from the XID3s during the connection negotiation between VTAM and the remote node. |
| RIF | Routing information field. If the CMPC transmission group LLC connection is established using source-route bridging, then the RIF used for the connection is displayed here. |
The following is sample output on a Cisco 7500 router from the show extended channel tg stats command:
router# show extended channel 3/2 tg stats detail MVS2-TG1
CMPC-TG:MVS2ISR1
IFramesIn :51 IFramesOut :41
IBytesIn :4378 IBytesOut :51803
UIFramesIn :0 UIFramesOut :0
UIBytesIn :0 UIBytesOut :0
TESTRspsIn :1 TESTCmdsOut :1
XIDCmdsIn :3 XIDCmdsOut :3
XIDRspsIn :0 XIDRspsOut :0
ConnectReqs :2 ConnectInds :0
ConnectRsps :2 ConnectCnfms:0
DISCReqs :1 DISCInds :0
SweepReqsIn :0 SweepReqsOut:0
SweepRspsIn :0 SweepRspsOut:0
Wraps :0
LastSeqNoIn :9 LastSeqNoOut:7
LastSeqNoFailureCause : None
TimeSinceLastSeqNoFailure : never
LLC2 Connection Statistics:
LAN Token 0 Adapter 1 4000.cdcd.cdcd
Local SAP=04 Remote MAC=4000.4040.1996 Remote SAP=04
LocalBusies = 0 RemoteBusies = 0
IFramesIn = 51 IFramesOut = 41
IOctetsIn = 4378 IOctetsOut = 51803
SFramesIn = 0 SFramesOut = 0
REJsIn = 0 REJsOut = 0
RetransmitsOut = 0 WwCountChanges = 0
The following is sample output on a Cisco 7500 router from the show extended channel tg stats command when the interface is shut down:
router# show extended channel 3/2 tg stats detail MVS2-TG1
CIP LLC-TG:MVS2ISR1 -Statistics Not Available
Table 67 describes the fields shown in the display.
| Field | Description |
|---|---|
| IFramesIn | Number of connection-oriented PIUs received by this CMPC transmission group from the remote network node. |
| IFramesOut | Number of connection-oriented PIUs sent by this CMPC transmission group to the remote network node. |
| UIFramesIn | Number of connectionless PIUs (HPR frames) received by this CMPC transmission group from the remote network node. |
| UIFramesOut | Number of connectionless PIUs (HPR frames) sent by this CMPC transmission group to the remote network node. |
| TestRspsIn | Number of TEST responses received for this CMPC transmission group. |
| TestCmdsOut | Number of TEST commands sent by this CMPC transmission group to the configured remote MAC address. |
| XidCmdsIn | Number of XID commands received for this CMPC transmission group. |
| XidCmdsOut | Number of XID commands sent by this CMPC transmission group. |
| XidRspsIn | Number of XID responses received for this CMPC transmission group. |
| XidRspsOut | Number of XID responses sent by this CMPC transmission group. |
| SweepReqsIn | Number of CMPC sweep requests received from VTAM on this CMPC transmission group. |
| SweepReqsOut | Number of CMPC sweep requests sent to VTAM on the CMPC transmission group. |
| SweepRspsIn | Number of CMPC responses received from VTAM on this CMPC transmission group. |
| SweepRspsOut | Number of CMPC responses sent to VTAM on this CMPC transmission group. |
| IBytesIn | Number of bytes for connection-oriented PIUs received by this CMPC transmission group from the remote network node. |
| IBytesOut | Number of bytes for connection-oriented PIUs sent by this CMPC transmission group to the remote network node. |
| UIBytesIn | Number of bytes for connectionless PIUs received by this CMPC transmission group from the remote network node. |
| UIBytesOut | Number of bytes for connectionless PIUs sent by this CMPC transmission group to the remote network node. |
| ConnectReqs | Number of connect requests received from the host by this CMPC transmission group. |
| ConnectInds | Number of connect indications sent to the host by this CMPC transmission group. |
| ConnectRsps | Number of connect responses received from the host by this CMPC transmission group. |
| ConnectCnfms | Number of connect confirms sent to the host by this CMPC transmission group. |
| DISCReqs | Number of disconnect requests received from the host by this CMPC transmission group. |
| DISCInds | Number of disconnect indications sent to the host by this CMPC transmission group. |
| Wraps | The number of times the sequence numbers wrapped for this CMPC transmission group. |
| LastSeqNoIn | The sequence number on the last CMPC data block sent to the host from this CMPC transmission group. |
| LastSeqNoOut | The sequence number on the last CMPC data block received from the host for this CMPC transmission group. |
| LastSeqNoFailureCause | The cause of the last sequence number failure for this CMPC transmission group. Valid values are as follows:
|
|
TimeSinceLastSeqNoFailure | Time since the last CMPC sequence number failure for this CMPC transmission group. If there have been no failures, "never" is displayed. |
Use the show extended channel tn3270-server privileged EXEC command to display current server configuration parameters and the status of the PUs defined in each TN3270 server.
show extended channel slot/2 tn3270-server| slot/2 | Specifies a particular CIP in the router where slot is the slot number. The port value for a TN3270 server is always 2. |
Privileged EXEC
This command first appeared in Cisco IOS Release 11.2.
The following is sample output on the Cisco 7000 with RSP7000 from the show extended channel tn3270-server command:
router#show extended channel 3/2 tn3270-server< connection stats > server-ip:tcp lu in-use connect disconn fail host tcp 172.28.1.106:23 510 1 12 11 0 54 40 172.28.1.107:23 511 0 0 0 0 0 0 172.28.1.108:23 255 0 0 0 0 0 0 total 1276 1 configured max_lu 20000 idle-time 0 keepalive 1800 unbind-action disconnect tcp-port 23 generic-pool permit no timing-mark dlur MPX.GOANCP status NOTQRYD SHUT dlus MPX.NGMVMPC name(index) ip:tcp xid state link destination r-lsap EXT2(1) 172.28.1.106:23 05D18092 ACTIVE tok 0 4000.7470.00e7 08 04 PUS10(2) 172.28.1.107:23 05D19010 ACTIVE tok 0 4000.7470.00e7 08 2C PUS11(3) 172.28.1.107:23 05D19011 ACTIVE tok 0 4000.7470.00e7 08 28 PUS12(4) 172.28.1.108:23 05D19012 ACTIVE tok 0 4000.7470.00e7 08 24 PUS9(5) 172.28.1.109:23 05D18509 SHUT tok 0 4001.3745.1088 04 40 SDTF(7) 172.28.1.107:23 12345678 ACTIVE tok 0 0800.5a4b.1cbc 04 08 TEST(8) 172.28.1.106:23 05D18091 ACTIVE tok 0 4000.7470.00e7 08 30 INT1(6) 172.28.1.106:23 05D18091 SHUT dlur
Table 68 describes significant fields in the display. Those fields not described correspond to configured values.
| Field | Description |
|---|---|
| SERVER-IP:TCP | IP address and TCP port number, listening point, configured on one or more PUs. |
| LU number | Total number of LUs available for this listening point. |
| IN-USE number | Number of LUs currently in use. |
| CONNECT number | Total number of connect ins since the TN3270 feature was started. |
| DISCONN number | Total number of disconnects since the TN3270 feature was started. |
| FAIL number | Total number of failed connects since the TN3270 feature was started. |
| RESPONSE TIME, HOST number | The average response time from the host across all sessions through this server IP address. This is measured from sending CD to the host to receiving the reply. |
| RESPONSE TIME, TCP number | Average response time from the clients on this server IP address. This is measured only when TIMING MARKs are sent. If no timing-mark is configured, they are only sent on special occasions, such as Bind. |
| IDLE-TIME number | Configured idle-time for this PU. |
| KEEPALIVE number | Configured keepalive for this PU. |
| UNBIND-ACTION type | Configured unbind action for LUs on this PU. |
| TCP-PORT number | Configured TCP port number. |
| GENERIC-POOL type | Configured generic-pool for LUs on this PU. |
| DLUR fq-cpname | Configured fully qualified DLUR CP name. |
| STATUS | Possible dlur-dlus-status values and their meanings are:
reset--The DLUR-DLUS pipe is reset. pnd-actv--The DLUR-DLUS pipe is pending active. active--The DLUR-DLUS pipe is active. pnd-inac--The DLUR-DLUS pipe is pending inactive. |
| DLUS fq-dlusname | Currently active DLUS. |
| NAME pu-name | This is the name of the PU as configured. |
| IP:TCP ip-addr:tcpport | IP address and TCP port number configured for the PU. |
| XID number | Configured XID - idblk and idnum. |
| STATE value | Possible STATE values and their meanings are:
|
|
LINK type | LINK type is either internal adapter type and internal adapter number or dlur if it is a SNA Session Switch PU. |
| DESTINATION mac-address or PU-name | If a direct PU, then it is the destination MAC address, otherwise, it is the name of the partner PU. |
| R-LSAP number number | Remote and local SAP values. |
Use the show extended channel tn3270-server client-ip-address privileged EXEC command to display information about all clients at a specific IP address.
show extended channel slot/2 tn3270-server client-ip-address ip-address [disconnected || slot/2 | (Optional) Specifies a particular CIP in the router where slot is the slot number. The port value for a TN3270 server will always be 2. |
| ip-address | IP address of the client. |
| disconnected | (Optional) Shows all clients with ip-address in disconnected state. Disconnected state refers to an LU session state of ACTIVE or INACTIVE. In this case, the ip-address refers to the client that last used the LU. |
| in-session | (Optional) Shows all clients with ip-address in active session state. Active session state refers to an LU session state of ACT/SESS. |
| pending | (Optional) Shows all clients with ip-address in pending state. Pending session state refers to an LU session state of P-SDT, P-ACTLU, P-NTF/AV, P-NTF/UA, P-RESET, P-PSID, P-BIND, P-UNBIND, WT-UNBND, WT-SDT or UNKNOWN. |
Privileged EXEC
This command first appeared in Cisco IOS Release 11.2.
Note that this command does not show information about LUs that have never been connected.
The following is sample output on the Cisco 7000 with RSP7000 from the show extended channel tn3270-server client-ip-address command. The example shows only active sessions because no other session types exist at this client IP address.
router# show extended channel 3/2 tn3270-server client-ip 192.195.80.40
lu name client-ip:tcp nail state model frames in out idle for
1 PUS11001 192.195.80.40:3169 Y ACT/SESS 327804 5 5 0:5:47
pu is PUS11, lu is DYNAMIC type 2, negotiated TN3270
bytes 155 in, 1758 out; RuSize 1024 in, 3840 out; NegRsp 0 in, 0 out
pacing window 0 in, 1 out; credits 0 in, queue-size 0 in, 0 out
The following is sample output using the disconnected argument:
Router# show extended channel 2/2 tn3270 client-ip 10.14.1.21 disconnected
Total 2 clients found using 10.14.1.21
The following is sample output using the in-session argument:
Router# show extended channel 2/2 tn3270 client-ip 10.14.1.21 in-session
Note: if state is ACT/NA then the client is disconnected
lu name client-ip:tcp nail state model frames in out idle for
3 PU1L03 10.14.1.21:35215 N ACT/SESS 327804 317 316 0:0:1
pu is PU1, lu is DYNAMIC type 2, negotiated TN3270
bytes 12167 in, 225476 out; RuSize 2048 in, 1536 out; NegRsp 0 in, 0 out
pacing window 0 in, 1 out; credits 0 in, queue-size 0 in, 0 out
Note: if state is ACT/NA then the client is disconnected
lu name client-ip:tcp nail state model frames in out idle for
4 PU1L04 10.14.1.21:35216 N ACT/SESS 327804 317 316 0:0:1
pu is PU1, lu is DYNAMIC type 2, negotiated TN3270
bytes 12167 in, 225476 out; RuSize 2048 in, 1536 out; NegRsp 0 in, 0 out
pacing window 0 in, 1 out; credits 0 in, queue-size 0 in, 0 out
Note: if state is ACT/NA then the client is disconnected
Total 2 clients found using 10.14.1.21
The following is sample output using the pending argument:
Router# show extended channel 2/2 tn3270 client-ip 10.14.1.21 pending
Total 2 clients found using 10.14.1.21
Table 69 describes significant fields in the display.
| Field | Description |
|---|---|
| lu locaddr | LOCADDR of the LU. |
| name lu-name | If the PU is directly connected, then the name shown is the one generated by the seed. If DLUR, then only the unqualified portion is shown. The NETID portion will be the same as the current DLUS. |
| client-ip:tcp ip-address:port | Client's IP address and TCP port number |
| nail | Status of LU nailing, either Y or N |
| state lu-state | The LU state and their meanings are:
|
|
MODEL model | IBM 3278 model type of client; blank if STATIC LU. |
| FRAMES IN number | Number of frames sent inbound to the host. |
| FRAMES OUT number | Number of frames sent outbound from the host. |
| IDLE FOR time | Time the client has been idle. The time is in HH:MM:SS. |
| PU IS pu-name | Name of the PU. |
| LU IS type | Whether LU is DYNAMIC or STATIC. |
| NEGOTIATED type | Whether client is TN3270 or TN3270E. |
| BYTES IN / OUT number/number | Total number of bytes sent to/received from the host. |
| RUSIZE IN / OUT number/number | RU size as configured in the bind. |
| NEGRSP IN / OUT number/number | Number of SNA negative responses sent to/received from the host. |
| PACING WINDOW IN / OUT number/number | SNA pacing window as configured in the bind. |
| CREDITS IN number | Number of frames that can be sent inbound without requiring an isolated pacing response. |
| QUEUE SIZE IN number | Indicates the number of SNA frames waiting to be sent to the host that are blocked and are waiting for a pacing response. |
| QUEUE SIZE OUT number | SNA frames not yet acknowledged by an isolated pacing response by the TN3270 server. |
Use the show extended channel tn3270-server dlur privileged EXEC command to display information about the SNA session switch.
show extended channel slot/2 tn3270-server dlur| slot/2 | Specifies a particular CIP in the router where slot is the slot number. The port value for a TN3270 server will always be 2. |
Privileged EXEC
This command first appeared in Cisco IOS Release 11.2.
The following is sample output on the Cisco 7000 with RSP7000 from the show extended channel tn3270-server dlur command:
router# show extended channel 3/2 tn3270-server dlur
dlur MPX.GOANCP
current dlus MPX.NGMVMPC dlur-dlus status ACTIVE
preferred dlus MPX.NGMVMPC backup dlus MPX.NGMVMPB
preferred server MPX.NGMVMPA
lsap token-adapter 0 5C vrn MPX.LAN4 status ACTIVE
link P390 remote 4000.7470.00e7 08 status ACTIVE
Table 70 describes significant fields in the display.
| Field | Description |
|---|---|
| DLUR fq-luname | Fully qualified CP name used by the SNA session switch and the LU name for the DLUR function configured as the fq-cpname on the dlur statement. |
| CURRENT DLUS fq-luname | Name of the currently active DLUS, either the primary DLUS or the backup DLUS. |
| DLUR-DLUS STATUS dlur-status | Possible dlur-dlus-status values and their meanings are:
|
|
PREFERRED-DLUS fq-luname | Name of the DLUS as configured on the DLUR statement. |
| BACKUP-DLUS fq-luname | Name of the DLUS that is used if the preferred DLUS is unavailable. |
| PREFERRED SERVER fq-luname | Fully qualified name of the preferred network node server. |
| LSAP | Configured value for the local SAP on the configured internal adapter. Token-adapter specifies the type of internal adapter used. |
| VRN fq-name | Name of the connection network as configured by the vrn statement for this LSAP and internal adapter pair. |
| LSAP...STATUS status | Possible sap-status values and their meanings are:
|
|
LINK name | Name of the configured link. If not a configured link, then the name is an invented name, @DLURnn. |
| REMOTE mac sap | Remote MAC and SAP for this link. |
| LINK...STATUS status | Possible link-status values and their meanings are:
|
Use the show extended channel tn3270-server dlurlink privileged EXEC command to display information about the DLUR components.
show extended channel slot/2 tn3270-server dlurlink name| slot/2 | Specifies a particular CIP in the router where slot is the slot number. The port value for a TN3270 server will always be 2. |
| name | Name of the SNA session switch link to be displayed. |
Privileged EXEC
This command first appeared in Cisco IOS Release 11.2.
The following is sample output on the Cisco 7000 with RSP7000 from the show extended channel tn3270-server dlurlink command:
router# show extended channel 3/2 tn3270-server dlurlink P390
lsap token-adapter 0 5C vrn MPX.LAN4 status ACTIVE
link P390 remote 4000.7470.00e7 08 status ACTIVE
partner MPX.NGMVMPC tgn 1 maxdata 1033
Table 71 describes significant fields in the display.
| Field | Description |
|---|---|
| LSAP...VRN...STATUS status | Possible sap-status values and their meanings are:
|
|
LINK name | Name is an invented name, @DLURnn, if not a configured link. |
| LINK ...STATUS status | Possible link-status values and their meanings are:
|
|
PARTNER name | CP name of the remote node for this link. |
| TGN tg-number | Transmission group number for this link. Because the SNA session switch only supports 1 transmission group per pair of CP names, it is typically 0 or 1. |
| MAXDATA maxdata | Maximum frame size allowed on this link. |
Use the show extended channel tn3270-server nailed-ip privileged EXEC command to display mappings between a nailed client IP address and nailed LUs.
show extended channel slot/2 tn3270-server nailed-ip ip-address| slot/2 | Slot number. |
| ip-address | Specifies remote client IP address. |
Privileged EXEC
This command first appeared in Cisco IOS Release 11.2 BC.
The following is sample output on the Cisco 7000 with RSP7000 from the show extended channel tn3270-server nailed-ip command:
router# show extended channel 3/2 tn3270-server nailed-ip 172.28.0.0
172.28.1.0 255.255.255.192 pu BAGE1 lu 1 50
172.28.1.80 255.255.255.248 pu BAGE2 lu 100 200 printer
172.28.1.83 pu BAGE3 lu 1 60 printer
172.28.1.82 pu BAGE1 lu 100 200
| Field | Description |
|---|---|
| 172.28.1.0 | IP address of the nailed client. |
| 255.255.255.192 | Network mask for the range of configured nailed clients. |
| pu BAGE1 | PU name under which the client command was configured. |
| lu 1 50 | LU LOCADDR range showing first LOCADDR and last LOCADDR. There need not be a last LOCADDR if only a single LOCADDR rather than a range is configured. |
| printer | Type of device being nailed to the LOCADDRs. If printer is specified, only clients which are printers are nailed to the LOCADDRs. If screen is specified, only clients that are screens are nailed to the LOCADDRs. If neither is specified, both screens and printers can use the LOCADDRs. A printer client is any client with a device type of "328*". A screen client is a client with any other device type. |
Use the show extended channel tn3270-server pu privileged EXEC command to display the PU configuration parameters, statistics and all the LUs currently attached to the PU.
show extended channel slot/2 tn3270-server pu pu-name| extended channel slot/2 | (Optional) Specifies a particular CIP in the router where slot is the slot number. The port value for a TN3270 server will always be 2. |
| pu-name | PU name that uniquely identifies this PU. |
Privileged EXEC
This command first appeared in Cisco IOS Release 11.2.
The display shown depends on whether the PU is a direct PU or a SNA session switch PU.
The following is sample output on the Cisco 7000 with RSP7000 from the show extended channel tn3270-server pu command for a direct PU:
router# show extended channel 3/2 tn3270-server pu BAGE1
name(index) ip:tcp xid state link destination r-lsap
BAGE1(1) 172.28.1.82:23 05D18081 ACTIVE tok 0 4000.7470.00e7 08 10
idle-time 0 keepalive 1800 unbind-act discon generic-pool perm
bytes 560 in, 3765 out; frames 20 in, 27 out; NegRsp 0 in, 0 out
actlus 12, dactlus 0, binds 2
lu name client-ip:tcp nail state model frames in out idle for
1 BAGE1001 never connected Y ACTIVE 1 1 4:50:44
2 BAGE1002 never connected Y ACTIVE 1 1 4:50:44
3 BAGE1003 192.195.80.40:2077 N ACT/SESS 327804 5 5 5:4:36
4 BAGE1004 192.195.80.40:2644 Y ACTIVE 327804 5 5 0:36:7
client ip mask nail-type lu first lu last
192.195.80.40 255.255.255.0 screen 1 2
192.195.80.40 255.255.255.0 printer 4
The following is sample output on the Cisco 7000 with RSP7000 from the show extended channel tn3270-server pu command for a SNA session switch PU:
router# show extended channel 3/2 tn3270-server pu INT1
name(index) ip:tcp xid state link destination r-lsap
INT1(5) 172.28.1.106:23 05D18091 ACTIVE dlur MPX.GOAN1
idle-time 0 keepalive 0 unbind-act discon generic-pool perm
bytes 50 in, out; frames 87 in, 2 out; NegRsp 3 in, 0 out
actlus 2, dactlus 0, binds 0
lu name client-ip:tcp state model frames in out idle for
1 GOAN1X01 never connected ACTIVE 1 1 0:32:14
2 GOAN1X02 never connected ACTIVE 1 1 0:32:14
Table 73 describes significant fields in the display.
| Field | Description |
|---|---|
| name (index) pu-name (index) | Name and index of the PU as configured. |
| ip:tcp ip-addr:tcpport | IP address and TCP port number configured for the PU. |
| xid number | Configured XID - idblk and idnum. |
| state pu-state | Possible state values and their meanings are as follows:
|
|
link type | LINK type is either internal adapter type and internal adapter number or dlur if it is a SNA Session Switch PU. |
| destination mac-address or pu-name | If a direct PU, then it is the destination MAC address, otherwise, it is the name of the partner PU. |
| r-lsap number number | Remote and local SAP values. |
| idle-time number | Configured idle-time for this PU. |
| keepalive number | Configured keepalive for this PU. |
| unbind-act type | Configured unbind action for LUs on this PU. |
| generic-pool type | Configured generic-pool for LUs on this PU. |
| bytes in / out number/number | Total number of bytes sent to/received from the host for this PU. |
| frames in / out number/number | Total number of frames sent to/received from the host for this PU. |
| NegRsp in / out number/number | Total number of SNA negative responses sent to/received from the host. |
| actlus number | Total number of ACTLUs received from the host. |
| dactlus number | Total number of DACTLUs received from the host. |
| binds number | Total number of BINDs received from the host. |
| lu number | LOCADDR of the LU. |
| name lu-name | Name of the TN3270 LU. |
| client-ip:tcp ip-addr:tcpport | Client's IP address and TCP port number. |
| nail | Status of LU nailing, either Y or N |
| state lu-state
| The LU states and their meanings are:
|
|
model model | IBM 3278 model type of client. |
| frames in number | Number of frames sent inbound to the host. |
| frames out number | Number of frames sent outbound from the host. |
| idle for time | Time the client has been idle. The time is in HH:MM:SS. |
| client ip | Remote client IP address. |
| mask | Current network mask. |
| nail-type | LU nailing type, screen or printer. |
| lu first | First LU address in the range. |
| lu last | Last LU address in the range, if one is specified in the client configuration command. |
Use the show extended channel tn3270-server pu lu privileged EXEC command to display information about the TN3270 server LUs running on CIP interface in a Cisco 7000 with RSP7000 and Cisco 7500 series.
show extended channel slot/2 tn3270-server pu pu-name lu locaddr [history]| slot/2 | Specifies a particular CIP in the router where slot is the slot number. The port value for a TN3270 server will always be 2. |
| pu-name | PU name that uniquely identifies this PU. |
| locaddr | LU LOCADDR that uniquely identifies the LU. |
| history | (Optional) Displays the LU trace history. |
Privileged EXEC
This command first appeared in Cisco IOS Release 11.2.
The following is sample output on the Cisco 7000 with RSP7000 from the show extended channel tn3270-server pu lu command for a direct PU:
router# show extended channel 3/2 tn3270 pu ext2 lu 3
lu name client-ip:tcp state model frames in out idle for
3 EXT2003 171.69.176.77:3829 ACTIVE 327902E 8 9 0:4:43
pu is EXT2, lu is DYNAMIC type 0, negotiated TN3270
bytes 203 in, 2954 out; RuSize 0 in, 0 out; NegRsp 1 in, 0 out
pacing window 0 in, 1 out; credits 0 in, queue-size 0 in, 0 out
The following is sample output on the Cisco 7000 with RSP7000 from the show extended channel tn3270-server pu lu command for a SNA session switch PU:
router# show extended channel 3/2 tn3270 pu int1 lu 1
lu name client-ip:tcp state model frames in out idle for
1 GOAN1X01 171.69.176.77:3828 ACTIVE 4 4 0:4:51
pu is INT1, lu is STATIC type 0, negotiated TN3270E
bytes 74 in, 1219 out; RuSize 0 in, 0 out; NegRsp 0 in, 0 out
pacing window 0 in, 0 out; credits 0 in, queue-size 0 in, 0 out
The following is sample output on the Cisco 7000 with RSP7000 from the show extended channel tn3270-server pu lu history command:
router# show extended channel 3/2 tn3270 pu pus20 lu 1 history
lu name client-ip:tcp state model frames in out idle for
1 PUS20001 192.195.80.40:2480 ACT/SESS 327804 5 4 0:0:8
pu is PUS20, lu is DYNAMIC type 2, negotiated TN3270
bytes 155 in, 1752 out; RuSize 1024 in, 3840 out; NegRsp 0 in, 0 out>pacing window 0 in, 1 out; credits 0 in, queue-size 0 in, 0 out
traces:
Client connect req
Reply PSID pos rsp
actlu req
bind req
sdt req
OUT len=12 2Dxxxxxxxx456B80000D0201
IN len=25 xxxxxxxxxx45EB80000D0201000000
OUT len=53 2Dxxxxxxxx466B800031010303B1
IN len=10 2D0001010646EB800031
OUT len=10 2D00010106476B8000A0
IN len=10 2D0001010647EB8000A0
OUT len=1677 2Cxxxxxxxx010381C07EC7114040
IN len=9 2C0001010001838100
Table 74 describes significant fields in the display.
| Field | Description |
|---|---|
| LU locaddr | LOCADDR of the LU. |
| NAME lu-name | Name of the TN3270 LU. |
| CLIENT-IP:TCP ip-addr:tcpport | Client's IP address and TCP port number. |
| STATE lu-state
| The LU state and their meanings are:
|
|
MODEL model | 3278 model type of client; blank if STATIC LU. |
| FRAMES IN number | Number of frames sent inbound to the host. |
| FRAMES OUT number | Number of frames sent outbound from the host. |
| IDLE FOR time | Time the client has been idle. The time is in HH:MM:SS. |
| PU IS pu-name | Name of the PU. |
| LU IS type | Whether LU is DYNAMIC or STATIC. |
| NEGOTIATED type | Whether client is TN3270 or TN3270E. |
| BYTES IN / OUT number/number | Total number of bytes sent to/received from the host. |
| RUSIZE IN / OUT number/number | RU size as configured in the bind. |
| NEGRSP IN / OUT number/number | Number of SNA negative responses sent to/received from the host. |
| PACING WINDOW IN / OUT number/number | SNA pacing window as configured in the bind. |
| CREDITS IN number | Number of frames that can be sent inbound without requiring an isolated pacing response. |
| QUEUE SIZE IN number | If non-zero, indicates the number of SNA frames waiting to be sent to the host which are blocked, waiting for a pacing response. |
| QUEUE SIZE OUT number | SNA frames not yet acknowledged by an isolated pacing response by the TN3270 server. |
Use the show extended channel udp-listeners privileged EXEC command to display information about the User Datagram Protocol (UDP) listener sockets running on the CIP interfaces in a Cisco 7000 with RSP7000 and Cisco 7500 series.
show extended channel slot/port udp-listeners [ip-address]| slot | Slot number. |
| port | Port number. |
| udp-listeners | Specifies UDP listener port display. |
| ip-address | (Optional) IP address specified in an offload interface configuration command. |
Privileged EXEC
This command first appeared in Cisco IOS Release 11.0.
The following is sample output on the Cisco 7000 with RSP7000 from the show channel udp-listeners command:
router#show extended channel 4/0 udp-listeners 198.92.1.120UDP Listener: IP Address 198.92.1.120 LocalPort 0 UDP Listener: IP Address 198.92.1.120 LocalPort 1 UDP Listener: IP Address 198.92.1.120 LocalPort 2 UDP Listener: IP Address 198.92.1.120 LocalPort 3 UDP Listener: IP Address 198.92.1.120 LocalPort 4 router#show extended channel 4/0 udp-listeners198.92.1.121UDP Listener: IP Address 198.92.1.121 LocalPort 0 UDP Listener: IP Address 198.92.1.121 LocalPort 1 UDP Listener: IP Address 198.92.1.121 LocalPort 2 UDP Listener: IP Address 198.92.1.121 LocalPort 3 UDP Listener: IP Address 198.92.1.121 LocalPort 4
Use the show extended channel udp-stack privileged EXEC command to display information about the UDP stack running on the CIP interfaces in a Cisco 7000 with RSP7000 and Cisco 7500 series.
show extended channel slot/port udp-stack [ip-address]| slot | Slot number. |
| port | Port number. |
| udp-stack | Selects UDP stack display. |
| ip-address | (Optional) IP address specified in an offload interface configuration command. |
Privileged EXEC
This command first appeared in Cisco IOS Release 11.0.
The following is sample output on the Cisco 7000 with RSP7000 from the show extended channel udp-stack command:
router# show extended channel udp-stack
UDP Statistics for IP Address 198.92.1.120
InDatagrams : 300 NoPorts : 301
InErrors : 302 OutDatagrams: 303
UDP Statistics for IP Address 198.92.1.121
InDatagrams : 301 NoPorts : 302
InErrors : 303 OutDatagrams: 304
Use the show interfaces channel privileged EXEC command to display information about the CIP interfaces on the Cisco 7000 with RSP7000 and Cisco 7500 series. This command displays information that is specific to the interface hardware. The information displayed is generally useful for diagnostic tasks performed by technical support personnel only.
show interfaces channel slot/port [accounting]| slot | Slot number. |
| port | Port number. |
| accounting | (Optional) Shows interface accounting information. |
Privileged EXEC
This command first appeared in Cisco IOS Release 10.3.
The following is sample output on the Cisco 7000 with RSP7000 from the show interfaces channel command:
Router#show interfaces channel 3/0Channel3/0 is up, line protocol is up Hardware is cxBus IBM Channel Internet address is 198.92.1.145, subnet mask is 255.255.255.248 MTU 4096 bytes, BW 0 Kbit, DLY 0 usec, rely 255/255, load 1/255 Encapsulation CHANNEL, loopback not set, keepalive not set ECA type daughter card Data transfer rate 12 Mbytes Number of subchannels 1 Last input never, output never, output hang never Last clearing of "show interface" counters 0:00:04 Output queue 0/0, 0 drops; input queue 0/75, 0 drops Five minute input rate 0 bits/sec, 0 packets/sec Five minute output rate 0 bits/sec, 0 packets/sec 0 packets input, 0 bytes, 0 no buffer Received 0 broadcasts, 0 runts, 0 giants 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort 0 packets output, 0 bytes, 0 underruns 0 output errors, 0 collisions, 0 interface resets, 0 restarts
Table 75 describes the fields shown in the display.
| Field | Description |
|---|---|
| Channel... is {up | down | administratively down} | Indicates whether the interface hardware is currently active (whether synchronization is achieved on an ESCON channel, or whether operational out is enabled on a parallel channel) and whether it has been taken down by an administrator. |
| line protocol is {up | down | administratively down} | Indicates whether the software processes that handle the line protocol think the line is usable (that is, whether keepalives are successful). |
| Hardware is | Hardware type. |
| Internet address is | IP address and subnet mask. |
| MTU | Maximum transmission unit of the interface. |
| BW | Bandwidth of the interface in kilobits per second. |
| DLY | Delay of the interface in microseconds. |
| rely | Reliability of the interface as a fraction of 255 (255/255 is 100% reliability), calculated as an exponential average over 5 minutes. |
| load | Load on the interface as a fraction of 255 (255/255 is completely saturated), calculated as an exponential average over 5 minutes. The calculation uses the value from the bandwidth interface configuration command. |
| Encapsulation | Encapsulation method assigned to interface. |
| loopback | Indicates whether loopbacks are set or not. |
| keepalive | Indicates whether keepalives are set or not. |
| daughter card | Type of adapter card. |
| Data transfer rate | Rate of data transfer. |
| Number of subchannels | Number of subchannels. |
| Last input | Number of hours, minutes, and seconds since the last packet was successfully received by an interface. Useful for knowing when a dead interface failed. |
| Last output | Number of hours, minutes, and seconds since the last packet was successfully transmitted by an interface. |
| output hang | Number of hours, minutes, and seconds (or never) since the interface was last reset because of a transmission that took too long. When the number of hours in any of the "last" fields exceeds 24 hours, the number of days and hours is printed. If that field overflows, asterisks are printed. |
| Last clearing | The time at which the counters that measure cumulative statistics (such as number of bytes transmitted and received) shown in this report were last reset to zero. Note that variables that might affect routing (for example, load and reliability) are not cleared when the counters are cleared. These asterisks (***) indicate the elapsed time is too large to be displayed. 0:00:00 indicates the counters were cleared more than 231ms (and less than 232ms) ago. |
| Output queue, drops input queue, drops | Number of packets in output and input queues. Each number is followed by a slash, the maximum size of the queue, and the number of packets dropped due to a full queue. |
| Five minute input rate, Five minute output rate | Average number of bits and packets transmitted per second in the last 5 minutes. |
| packets input | Total number of error-free packets received by the system. |
| bytes input | Total number of bytes, including data and MAC encapsulation, in the error free packets received by the system. |
| no buffer | Number of received packets discarded because there was no buffer space in the main system. Compare with ignored count. Broadcast storms on Ethernets and bursts of noise on serial lines are often responsible for no input buffer events. |
| broadcasts | Total number of broadcast or multicast packets received by the interface. |
| runts | Number of packets that are discarded because they are smaller than the medium's minimum packet size. |
| giants | Number of packets that are discarded because they exceed the medium's maximum packet size. |
| input errors | Total number of no buffer, runts, giants, CRCs, frame, overrun, ignored, and abort counts. Other input-related errors can also increment the count, so that this sum may not balance with the other counts. |
| CRC | Number of code violation errors seen on the ESCON interface, where a received transmission character is recognized as invalid. On a parallel interface, the number of parity errors seen. |
| frame | Number of packets received incorrectly having a CRC error and a noninteger number of octets. This value is always 0. |
| overrun | Number of times the serial receiver hardware was unable to hand received data to a hardware buffer because the input rate exceeded the receiver's ability to handle the data. This value is always 0. |
| ignored | Number of received packets ignored by the interface because the interface hardware ran low on internal buffers. These buffers are different than the system buffers mentioned previously in the buffer description. Broadcast storms and bursts of noise can cause the ignored count to be incremented. |
| abort | Illegal sequence of one bits on a serial interface. This usually indicates a clocking problem between the serial interface and the data link equipment. This value is always 0. |
| packets output | Total number of messages transmitted by the system. |
| bytes | Total number of bytes, including data and MAC encapsulation, transmitted by the system. |
| underruns | Sum of all errors that prevented the final transmission of datagrams out of the interface being examined. Note that this may not balance with the sum of the enumerated output errors, as some datagrams may have more than one error, and others may have errors that do not fall into any of the specifically tabulated categories. |
| output errors | Number of output errors. |
| collisions | Number of collisions detected. This value is always 0. |
| interface resets | Number of times an interface has been completely reset. This can happen if packets queued for transmission were not sent within several seconds. On a serial line, this can be caused by a malfunctioning modem that is not supplying the transmit clock signal, or by a cable problem. If the system notices that the carrier detect line of a serial interface is up, but the line protocol is down, it periodically resets the interface in an effort to restart it. Interface resets can also occur when an interface is looped back or shut down.
On the Channel Interface Processor (CIP), this may occur if the host software is not requesting data |
| restarts | Number of times the controller was restarted because of errors. |
Use the shutdown interface configuration command to shutdown a physical interface or the internal LAN interface on the CIP when you are in interface configuration mode. The shutdown command also shuts down TN3270 entities, such as PU, DLUR, and DLUR SAP, depending on which configuration mode you are in when the command is issued. Use the no form of this command to restart the interface or entity. The entity affected depends on the mode in which the command is issued.
shutdownThis command has no arguments or keywords.
The interface or entity is enabled.
CIP interface configuration
TN3270 configuration
PU configuration
DLUR configuration
DLUR SAP configuration
This command first appeared in Cisco IOS Release 11.2.
In CIP interface configuration mode, the command applies to the entire CIP.
In TN3270 configuration mode, the command applies to the whole TN3270 Server.
In PU configuration mode, the command applies to the DLUR or direct PU.
In DLUR configuration mode, the command applies to the whole DLUR subsystem.
In DLUR SAP configuration, mode the command applies to the local SAP.
The following command issued in TN3270 configuration mode shuts down the entire TN3270 server:
shutdown
Use the tcp-port TN3270 configuration command to override the default TCP port setting of 23. Use the no form of this command to restore the default.
tcp-port port-number| port-number | A valid TCP port number in the range of 0 to 65534. The default is 23, which is the IETF standard. The value 65535 is reserved by the TN3270 server. |
In TN3270 configuration mode, the default is 23.
In PU configuration mode the default is the value currently configured in TN3270 configuration mode.
TN3270 configuration
PU configuration
This command first appeared in Cisco IOS Release 11.2.
The tcp-port command can be entered in either TN3270 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. The tcp-port command affects only future TN3270 sessions.
The no tcp-port command entered in PU configuration mode removes the override.
The following command entered in TN3270 configuration mode returns the TCP port value to 23:
no tcp-port
Use the tg interface configuration command to define LLC connection parameters for the CMPC transmission group. Use the no form of this command to remove the specified transmission group from the configuration, which also deactivates the transmission group.
tg name llc type adapter-number lsap [rmac rmac] [rsap rsap]| name | The name of the CMPC transmission group. The maximum length of the name is eight characters. This must match the name specified on the cmpc statements. |
| llc | Specifies that this TG is connected to the LLC stack on the CIP card. |
| type | Internal adapter type on the CIP card, which corresponds to the value specified in the lan internal LAN configuration command. The currently supported type is token-adapter. |
| adapter-number | Internal adapter number on the CIP card, which is the same value specified in the adapter internal LAN configuration command. |
| lsap | Local SAP number, 04 to FC, in hexadecimal. The value must be even and should normally be a multiple of four. It must be unique within the internal adapter in that no other IEEE 802.2 clients of that adapter, in the router or in a host, can use the same SAP. |
| rmac rmac | (Optional) Remote MAC address of the form xxxx.xxxx.xxxx in hexadecimal. If not specified, a loopback link to another SAP on the same internal LAN adapter is assumed. |
| rsap rsap | (Optional) Remote SAP address, 04 to FC in hexadecimal. The rsap value must be even and should be a multiple of 4, but this requirement is not enforced. The rsap value default is 04. |
The lsap and rsap values default to 04.
Interface configuration
This command first appeared in Cisco IOS Release 11.2 BC.
The tg command defines an LLC connection with a complete addressing 4-tuple. The lsap, rmac, and rsap are specified explicitly by parameters. The lmac is the local MAC address of the adapter referred to by the type and adapter-number parameters.
To change any parameter of the tg command, the TG must be removed by using no tg name.
The no tg command removes the CMPC transmission group from the configuration. If the transmission group is used for a non-HPR connection, all sessions using the TG will be terminated immediately. If the transmission group is an HPR connection, all sessions using the transmission group will be terminated if no other HPR connection is available to the host.
This command is valid only on the CIP internal interface, slot/2.
The following example configures a transmission group name and includes the rmac and rsap parameters:
tg LAGUNAA llc token-adapter 1 18 rmac 4000.0000.beef rsap 14
You can use the master indexes or search online to find documentation of related commands.
Use the tn3270-server interface configuration command to start the TN3270 server on a CIP or to enter TN3270 configuration mode. Use the no form of this command to disable all TN3270 server activity on a CIP.
tn3270-serverThis command has no arguments or keywords.
No TN3270 server function is enabled.
Interface configuration
This command first appeared in Cisco IOS Release 11.2.
Only one TN3270 server can run on a CIP. It will always be configured on port 2, which is the internal LAN interface port.
The no tn3270-server command shuts down TN3270 server immediately. All active sessions will be disconnected and all DLUR and PU definitions deleted from the router configuration. To restart a TN3270 server, you must reconfigure all parameters.
The following command starts the TN3270 server and enters TN3270 configuration mode:
tn3270-server
Use the timing-mark TN3270 configuration mode command to select whether a WILL TIMING-MARK is transmitted when the host application needs an SNA response (definite or pacing response). Use the no form of the command to turn off WILL TIMING-MARK transmission except as used by the keepalive function.
timing-markThis command has no arguments or key words.
No WILL TIMING-MARKS are transmitted except by keepalive.
TN3270 configuration
This command first appeared in Cisco IOS Release 11.2.
If timing-mark is configured the TN3270 server will send WILL TIMING-MARK as necessary to achieve an end-to-end response protocol. Specifically, TIMING-MARK will be sent if any of the following are true:
The use of the timing-mark command can degrade performance. Some clients do not support timing-mark used in this way. Therefore, timing-mark should only be configured where both of the following are true:
The following command enables TIMING-MARK transmission:
timing-mark
Use the unbind-action TN3270 configuration command to select what action to take when the TN3270 server receives an UNBIND. Use the no form of this command to restore the default.
unbind-action {keep | disconnect}| keep | No automatic disconnect will be made by the server upon receipt of an UNBIND. |
| disconnect | Session will be disconnected upon receipt of an UNBIND. |
In TN3270 configuration mode, the default is disconnect.
In PU configuration mode the default is the value currently configured in TN3270 configuration mode.
TN3270 configuration
PU configuration
This command first appeared in Cisco IOS Release 11.2.
The unbind-action command can be entered in either TN3270 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. The unbind-action command affects currently active and future TN3270 sessions.
The no unbind-action command entered in PU configuration mode removes the override.
The unbind-action command affects currently active and future TN3270 sessions.
The following command prevents automatic disconnect:
unbind-action keep
Use the vrn DLUR SAP configuration command to tell the SNA session switch which connection network the internal adapter interface on the CIP card belongs to. Use the no form of this command to remove a network name.
vrn vrn-name| vrn-name | Fully qualified name. |
The adapter is not considered to be part of a connection network.
DLUR SAP configuration
This command first appeared in Cisco IOS Release 11.2.
The vrn command is used to discover routes without having to configure all possible links.
A connection network is also known as a shared-access transport facility (SATF). This means, at the MAC level, that all nodes in the network can reach each other using the same addressing scheme and without requiring the services of SNA session routing. A bridged LAN (whether source-route or transparent) is an example. Such a network is represented in the APPN topology as a kind of node, termed a virtual routing node (VRN).
To make use of this function, all APPN nodes must use the same VRN name for the SATF.
Refer to the VTAM operating system documentation for your host system for additional information regarding the VTAM VNGROUP and VNNAME parameters on the PORT statement of an XCA major node.
Several parameters in the DLUR configuration mode consist of fully qualified names, as defined by the APPN architecture. Fully qualified names consist of two case-insensitive alphanumeric strings, separated by a period. However, for compatibility with existing APPN products, including VTAM, the characters "#" (pound), "@" (at), and "$" (dollar) are allowed in the fully qualified name strings. Each string is from one to eight characters long; for example, RA12.NODM1PP. The portion of the name before the period is the NETID and is shared between entities in the same logical network.
The following command sets a VRN name for the TN3270 internal adapter on the CIP:
vrn SYD.BLAN25
adapter
lan
|
|