- access-expression through asptime
- bridge acquire through bstun route all apip
- certificate reload through csna
- default-profile through dspu vdlc start
- enable (TN3270) through lu termination
- mac-address through vsrb remote-peer netbios-output-list
- sap-priority through servercert
- show access-expression through show extended channel udp-stack
- show fras through shutdown (TN3270)
- sna enable-host (Token Ring, Ethernet, Frame Relay, FDDI) through source-bridge max-in-hops
- source-bridge max-out-hops through x25 pvc qllc
- Appendix: Ethernet Type Codes
- certificate reload
- channel-protocol
- claw (backup)
- claw (primary)
- clear alps circuits
- clear alps counters
- clear bridge
- clear bridge multicast
- clear dlsw circuit
- clear dlsw history
- clear dlsw local-circuit
- clear dlsw reachability
- clear dlsw statistics
- clear dlsw transparent
- clear drip counters
- clear extended counters
- clear ncia circuit
- clear ncia client
- clear ncia client registered
- clear netbios-cache
- clear rif-cache
- clear source-bridge
- clear sse
- clear vlan statistics
- client ip
- client ip lu
- client ip pool
- client lu maximum
- client pool
- cmpc
- csna
certificate reload
To configure Secure Socket Layer (SSL) Encryption Support enabled to read the profile security certificate from the file specified in the servercert command, use the certificate reload command in customer profile configuration mode.
certificate reload
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Profile configuration
Command History
Usage Guidelines
There is not a no form for this command.
The TN3270 server must be configured for security.
Examples
The following example configures the TN3270 server with SSL Encryption Support to read the profile security certificate from the file specified in the servercert command:
certificate reload
Related Commands
|
|
|
|---|---|
servercert |
Specifies the location of the TN3270 server's security certificate in the Flash memory. |
channel-protocol
To define a data rate of either 3 MBps or 4.5 MBps for Parallel Channel Interfaces, use the channel-protocol command in interface configuration mode. To return to the default rate of 3 MBps, use the no form of this command.
channel-protocol [s | s4]
no channel-protocol
Syntax Description
s |
(Optional) Specifies a data rate of 3 MBps. |
s4 |
(Optional) Specifies a data rate of 4.5 MBps. |
Defaults
If no value is specified, the default data rate for the Parallel Channel Adapter (PCA) and the Parallel Channel Port Adapter (PCPA) is 3 MBps.
Command Modes
Interface configuration
Command History
Usage Guidelines
This command is valid on Parallel Channel Interfaces.
Examples
The following example specifies a data rate of 4.5 MBps for the interface:
channel-protocol s4
claw (backup)
To configure a Common Link Access for Workstations (CLAW) device (read and write subchannel) for communication with a mainframe TCP/IP stack in offload mode and configure individual members of a CLAW backup group for the IP Host Backup feature, use the claw command in IP host backup configuration mode. To remove the CLAW device, use the no form of this command.
claw path device-address ip-address host-name device-name host-app device-app [broadcast]
no claw device-address
Syntax Description
Defaults
No default behavior or values.
Command Modes
IP host backup configuration
Command History
Usage Guidelines
This command defines information that is specific to the hardware interface and the IBM channels supported on the interface.
CLAW devices are used to switch IP packets between a mainframe and a channel-attached router.
At most, 128 statements can be configured per interface because each interface is limited to 256 subchannels. Each CLAW device uses a read channel and a write channel. There is also a restriction of 64 unique paths.
A limit of 32 CLAW device configuration commands is recommended.
Duplicate IP addresses are invalid for nonbackup configurations.
Duplicate IP addresses are permitted if they appear within a backup group of only claw or offload interface configuration commands. All configuration commands in one backup group must specify the backup keyword.
You can use the path interface configuration command to specify a number of paths that belong to a backup group. In that case, a claw IP host backup configuration command is used that needs no path variable or backup keyword.
Examples
The following examples show two methods for entering the same IP host backup group information. The first group of commands is the long form, using the claw interface configuration command. The second group is the shortcut, using the path interface configuration command and a claw IP host backup configuration command.
Long form:
claw c000 00 10.92.10.5 sysa router1 tcpip tcpip
claw c100 00 10.92.10.5 sysa router1 tcpip tcpip
claw c200 00 10.92.10.5 sysa router1 tcpip tcpip
Shortcut form:
path c000 c100 c200
claw 00 10.92.10.5 sysa router1 tcpip tcpip
Related Commands
claw (primary)
To configure a Common Link Access for Workstations (CLAW) device (read and write subchannel) for communication with a mainframe TCP/IP stack in IP datagram mode and also configure individual members of a CLAW backup group for the IP Host Backup feature, use the claw command in interface configuration mode. To remove the CLAW device, use the no form of this command.
claw path device-address ip-address host-name device-name host-app device-app [broadcast] [backup]
no claw path device-address
Syntax Description
Defaults
No default behavior or values.
Command Modes
Interface configuration
Command History
Usage Guidelines
This command defines information that is specific to the hardware interface and the IBM channels supported on the interface. When used with the path command, the claw command provides a quick way to configure a CLAW backup group.
CLAW devices are used to switch IP packets between a mainframe and a channel-attached router.
At most, 128 statements can be configured per interface because each interface is limited to 256 subchannels. Each CLAW device uses a read channel and a write channel. There is also a restriction of 64 unique paths.
A limit of 32 CLAW device configuration commands is recommended.
Duplicate IP addresses are invalid for nonbackup configurations.
Duplicate IP addresses are permitted if they appear within a backup group of only claw or offload interface configuration commands. All configuration commands in one backup group must specify the backup keyword.
You can use the path interface configuration command to specify a number of paths that belong to a backup group. In that case, a claw IP host backup configuration command is used that needs no path variable or backup keyword. You can use the packed value as an optional keyword for the host-app and device-app arguments.
Examples
The following example shows how to enable IBM channel attach routing on channel interface 3/0, which is supporting an ESCON direct connection to the mainframe:
interface channel 3/0
ip address 172.18.4.49 255.255.255.248
claw c020 F4 172.18.4.52 HOSTB RTRA TCPIP TCPIP
The following example shows how to enable CLAW packing:
interface Channel 3/0
ip address 172.18.4.49 255.255.255.248
claw c010 F2 172.18.4.50 HOSTA RTRA PACKED PACKED
The following example shows how an IP host backup group is specified using the backup keyword:
interface Channel3/0
no ip address
no keepalive
no shutdown
claw 0100 C0 10.30.1.2 CISCOVM EVAL TCPIP TCPIP backup
claw 0110 C0 10.30.1.2 CISCOVM EVAL TCPIP TCPIP backup
claw 0120 C0 10.30.1.2 CISCOVM EVAL TCPIP TCPIP backup
claw 0110 C2 10.30.1.3 CISCOVM EVAL TCPIP TCPIP
Related Commands
clear alps circuits
To remove configured Airline Product Set (ALPS) circuits, use the clear alps circuits command in user EXEC or privileged EXEC mode.
clear alps circuits [ipaddr address | name string]
Syntax Description
ipaddr address |
(Optional) Clear ALPS circuits for peer with specified IP address. |
name string |
(Optional) Clear ALPS circuits for peer with specified name. |
Defaults
If no IP address or name is specified, the command clears all ALPS circuits.
Command Modes
EXEC
Command History
Examples
The following example clears the ALPS circuit named CKT1:
Router# clear alps circuits name CKT1
Related Commands
|
|
|
|---|---|
alps auto-reset |
Automatically resets a nonresponsive ALC ASCU in the DOWN state. |
show alps circuits |
Displays the status of the ALPS circuits. |
clear alps counters
To clear all counters relevant to the ALPS feature, use the clear alps counters command in user EXEC or privileged EXEC mode.
clear alps counters
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC
Privileged EXEC
Command History
Examples
The following example clears all counters for the ALPS feature:
Router# clear alps counters
Related Commands
clear bridge
To remove any learned entries from the forwarding database and to clear the transmit and receive counts for any statically or system-configured entries, use the clear bridge command in privileged EXEC mode.
clear bridge bridge-group
Syntax Description
bridge-group |
Bridge group number specified in the bridge protocol command. |
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Examples
The following example shows the use of the clear bridge command:
Router# clear bridge 1
Related Commands
|
|
|
|---|---|
bridge address |
Filters frames with a particular MAC-layer station source or destination address. |
bridge protocol |
Defines the type of Spanning Tree Protocol. |
clear bridge multicast
To clear transparent bridging multicast state information, use the clear bridge multicast command in user EXEC or privileged EXEC mode.
clear bridge [bridge-group] multicast [router-ports | groups | counts] [group-address] [interface-unit] [counts]
Syntax Description
Defaults
No default behavior or values.
Command Modes
User EXEC
Privileged EXEC
Command History
Usage Guidelines
If you do not specify arguments or keywords as part of the command, the command clears router ports, group ports, and counts for all configured bridge groups.
Use the show bridge multicast command to list transparent bridging multicast state information, then use specific pieces of state information in the clear bridge multicast command.
Examples
The following example clears router ports, group ports, and counts for bridge group 1:
Router# clear bridge 1 multicast
The following example clears the group and count information for the group identified as 235.145.145.223, interface Ethernet 0/3 for bridge group 1:
Router# clear bridge 1 multicast groups 235.145.145.223 Ethernet0/3 counts
Related Commands
|
|
|
|---|---|
bridge cmf |
Enables CMF for all configured bridge groups. |
show bridge multicast |
Displays transparent bridging multicast state information. |
clear dlsw circuit
To cause all data-link switching plus (DLSw+) circuits to be closed, use the clear dlsw circuit command in privileged EXEC configuration mode.
clear dlsw circuit [circuit-id]
Syntax Description
circuit-id |
Circuit ID for a specific remote circuit. The valid range is from 0 to 4294967295. |
Command Modes
Privileged EXEC
Command History
Usage Guidelines
A user can specify a circuit ID of a specific circuit to clear rather than clearing all circuits.
This command also drops the associated Logical Link Control, type 2 (LLC2) session. The command usage should be used with caution and under the advice of a Cisco engineer.
Examples
The following example closes all DLSw+ circuits:
Router# clear dlsw circuit
clear dlsw history
To clear all currently inactive circuits from the DLSw+ circuit history, use the clear dlsw history privileged EXEC command.
clear dlsw history
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Examples
The following example clears all inactive circuits from the DLSW+ circuit history:
clear dlsw history
clear dlsw local-circuit
To cause all locally-switched DLSw+ circuits to be closed, use the clear dlsw local-circuit privileged EXEC command.
clear dlsw local-circuit [circuit-id]
Syntax Description
circuit-id |
Circuit ID for a specific remote circuit. The valid range is 0 to 4294967295. |
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
A user can specify a circuit ID of a specific circuit to clear rather than clearing all local-switched circuits.
This command also drops the associated LLC2 session. The command usage should be used with caution and under the advice of a Cisco engineer.
Examples
The following example closes the locally-switched DLSw+ circuit with ID number 100:
clear dlsw local-circuit 100
clear dlsw reachability
To remove all entries from the data-link switching plus (DLSw+) reachability cache, use the clear dlsw reachability command in privileged EXEC configuration mode.
clear dlsw reachability
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command does not affect existing sessions.
Examples
The following example removes all entries from the DLSw+ reachability cache:
Router# clear dlsw reachability
clear dlsw statistics
To reset to zero the number of frames that have been processed in the local, remote, and group cache, use the clear dlsw statistics command in privileged EXEC configuration mode.
clear dlsw statistics
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Examples
The following example resets to zero the number of frames in the local, remote, and group cache:
Router# clear dlsw statistics
clear dlsw transparent
To clear DLSw+ transparent local MAC entries, use the clear dlsw transparent privileged EXEC command.
clear dlsw transparent
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command is designed to be used in networks that employ DLSw+ Ethernet redundancy without transparent mappings.
Examples
The following example clears DLSw+ transparent local MAC entries:
clear dlsw transparent
clear drip counters
To clear duplicate ring protocol (DRiP) counters from the Route Switch Module (RSM) interfaces, use the clear drip counters command in privileged EXEC mode.
clear drip counters
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the clear drip counters command if you want to check whether the router is receiving any packets. The counters will start at 0. If the counters are incrementing, DRiP is active on the router.
Examples
The following example clears DRiP counters:
Router# clear drip counters
Related Commands
|
|
|
|---|---|
interface vlan |
Configures a Token Ring or Ethernet interface on the RSM. |
show drip |
Displays the status of the DRiP database. |
clear extended counters
To clear the extended interface counters associated with Cisco Mainframe Channel Connection (CMCC) features, use the clear extended counters command in user EXEC or privileged EXEC mode.
clear extended counters [channel slot/port [csna | icmp-stack | ip-stack | llc2 | statistics | tcp-connections | tcp-stack | tg | tn3270-server | udp-stack]]
Syntax Description
Command Modes
User EXEC
Privileged EXEC
Command History
Usage Guidelines
This command is valid on both the physical and virtual channel interfaces. To clear counters for a selected CMCC feature, you must specify the channel interface on which the feature is configured or running.
Counters displayed using the show extended channel EXEC command are cleared using this command.
Entering any form of this command will prompt the user for a confirmation before clearing any counters. A "CLEAR-5-EXT_COUNT" message is displayed to indicate completion of the command.
These counters will be cleared in the show commands and remain uncleared when obtained through the Simple Network Management Protocol (SNMP) interface.
Examples
The following example shows how to clear the extended interface counters:
Router# clear extended counters
Related Commands
clear ncia circuit
To drop a specified native client interface architecture (NCIA) circuit, use the clear ncia circuit command in privileged EXEC configuration mode.
clear ncia circuit [id-number]
Syntax Description
id-number |
(Optional) Number assigned to identify the circuit. If no circuit ID number is specified, the command drops all circuits. |
Command Modes
Privileged EXEC
Command History
Usage Guidelines
If no circuit ID number is specified, the command drops all circuits.
Examples
The following example clears the active NCIA circuit identified as 791F8C:
Router# clear ncia circuit 791F8C
Related Commands
|
|
|
|---|---|
show ncia circuits |
Displays the state of all circuits involving this MAC address as a source and destination. |
clear ncia client
To terminate a specified active client connection, use the clear ncia client command in privileged EXEC configuration mode.
clear ncia client [ip-address]
Syntax Description
ip-address |
(Optional) IP address of the client. If no IP address is specified in the command, the command terminates all active client connections. |
Command Modes
Privileged EXEC
Command History
Usage Guidelines
If no IP address is specified in the command, the command terminates all active client connections.
Examples
The following example terminates the active connection to the client identified by the IP address 10.2.20.126:
Router# clear ncia client 10.2.20.126
Related Commands
|
|
|
|---|---|
show ncia client |
Displays the status of the NCIA client. |
clear ncia client registered
To release the control block of a specified registered client after terminating the active connection to it, use the clear ncia client registered command in privileged EXEC configuration mode.
clear ncia client registered [ip-address]
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
If no IP address is specified in the command, the command releases the control blocks of all registered clients after terminating any active connections to them.
Examples
The following example terminates the active connection to the registered client identified by the IP address 10.2.20.126 and releases its control block:
Router# clear ncia client registered 10.2.20.126
Related Commands
|
|
|
|---|---|
show ncia client |
Displays the status of the NCIA client. |
clear netbios-cache
To clear the entries of all dynamically learned NetBIOS names, use the clear netbios-cache command in privileged EXEC mode.
clear netbios-cache
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The Cisco IOS software automatically learns NetBIOS names. This command clears those entries. This command will not remove statically defined name cache entries.
Examples
The following example clears all dynamically learned NetBIOS names:
Router# clear netbios-cache
Related Commands
clear rif-cache
To clear the entire Routing Information Field (RIF) cache, use the clear rif-cache command in privileged EXEC mode.
clear rif-cache
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Some entries in the RIF cache are dynamically added and others are static.
Examples
The following example clears the entire RIF cache:
Router# clear rif-cache
Related Commands
clear source-bridge
To clear the source-bridge statistical counters, use the clear source-bridge command in privileged EXEC mode.
clear source-bridge
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Examples
The following example clears the source-bridge statistical counters:
Router# clear source-bridge
Related Commands
|
|
|
|---|---|
clear bridge |
Removes any learned entries from the forwarding database and clears the transmit and receive counts for any statically or system-configured entries. |
clear sse
To reinitialize the Silicon Switch Processor (SSP) on the Cisco 7000 series routers with RSP7000, use the clear sse command in privileged EXEC mode.
clear sse
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The silicon switching engine (SSE) is on the SSP board in the Cisco 7000 series routers with RSP7000.
Examples
The following example re initializes the SSP:
Router# clear sse
clear vlan statistics
To remove virtual LAN statistics from any statically or system-configured entries, use the clear vlan statistics command in privileged EXEC mode.
clear vlan statistics
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Examples
The following example clears VLAN statistics:
Router# clear vlan statistics
Related Commands
|
|
|
|---|---|
show vlan counters |
Displays the software-cached counter values. |
client ip
To add an IP subnet to a client subnet response-time group, use the client ip command in response-time configuration mode. To remove an IP subnet from a client subnet response-time group, use the no form of this command.
client ip ip-address [ip-mask]
no client ip ip-address [ip-mask]
Syntax Description
Defaults
The default mask is 255.255.255.255.
Command Modes
Response-time configuration
Command History
Examples
The following example adds an IP subnet to a client subnet response-time group:
tn3270-server
response-time group acctg
client ip 10.1.2.3 255.0.0.0
Related Commands
client ip lu
To define a specific logical unit (LU) or range of LUs to a client at the IP address or subnet, use the client ip lu command in TN3270 PU configuration mode. To cancel this definition, use the no form of this command.
client [printer] ip ip-address [ip-mask] lu first-locaddr [last-locaddr]
no client [printer] ip ip-address [ip-mask] lu first-locaddr [last-locaddr]
Syntax Description
Defaults
No LUs are nailed. They are all available to any client.
Command Modes
TN3270 PU configuration mode
Command History
Usage Guidelines
This command is valid only on the virtual channel interface. Multiple statements can be configured for one IP address or nail type either on one PU or multiple PUs. But each LU can appear in only 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 nonnailed IP address cannot request an LU that is configured as nailed.
The command will be rejected if some of the local address are already nailed. If the local address are in use by other remote clients, the nailing statement will take effect only when the local address 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 local address was specified, to cancel this definition the whole range of local address must be specified. There is no way to cancel only one local address if a whole range of local address was configured.
Examples
In the following example, local address from 1 to 50 are reserved for remote devices in the 10.69.176.0 subnet:
interface channel 2/2
tn3270-server
pu BAGE4
client ip 10.69.176.28 255.255.255.0 lu 1 50
In the following example, local address 1 to 40 are reserved for screen devices in the 10.69.176.0 subnet, and 41 to 50 are reserved for printers in that subnet:
interface channel 2/2
tn3270-server
pu BAGE4
client ip 10.69.176.28 255.255.255.0 lu 1 40
client printer ip 10.69.176.28 255.255.255.0 lu 41 50
In the following example, an attempt to cancel a definition is rejected because it does not specify the full range of local address and the second attempt fails to specify the correct nail type:
interface channel 2/2
tn3270-server
pu BAGE4
client printer ip 10.69.176.50 255.255.255.0 lu 1 100
no client printer ip 10.69.176.50 255.255.255.0 lu 1
%Invalid LU range specified
no client ip 10.69.176.50 255.255.255.0 lu 1 100
%client ip 10.69.176.50 nail type not matched with configured nail type printer
Related Commands
|
|
|
|---|---|
pu (DLUR) |
Creates a PU entity that has no direct link to a host and enters DLUR PU configuration mode. |
client ip pool
To nail clients to pools, use the client ip pool command in listen-point configuration mode. To remove clients from pools, use the no form of this command.
client ip ip-address [ip-mask] pool poolname
no client ip ip-address [ip-mask] pool poolname
Syntax Description
Defaults
No clients are nailed to pools.
Command Modes
Listen-point configuration
Command History
Usage Guidelines
If the pool is configured while logical unit (LU)s are in use, existing clients are allowed to complete their sessions. A pool name can be identical to an LU name. When assigning an LU, the TN3270 server searches the LU name space first for specific requests, such as connections that specify a device name on CONNECT or LU name in the terminal type negotiation. The request is assumed to be directed to the specific LU rather than to the pool. Make sure the name spaces do not clash.
Examples
The following is an example of the client ip pool command that nails the client at IP address 10.1.2.3 with an IP mask of 255.255.255.0 to the pool named POOL-1:
tn3270-server
pool POOL-1 cluster layout 10s1p
listen-point 172.18.4.18
client ip 10.1.2.3 255.255.255.0 pool POOL-1
Related Commands
client lu maximum
To limit the number of logical unit (LU) sessions that can be established for each client IP address or IP subnet address, use the client lu maximum TN3270 server configuration command. To remove a single LU limit associated with a particular IP address, use the no form of this command.
client [ip-address [ip-mask]] lu maximum number
no client [ip-address [ip-mask]]
Syntax Description
Defaults
The default is that there is no limit on the number of concurrent sessions from one client IP address.
The default value for the ip-mask argument is 255.255.255.255.
In the no form of this command, the default value for the number argument is 65535.
Command Modes
TN3270 server configuration
Command History
Usage Guidelines
This command is valid only on the virtual channel interface. 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 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 the no client command to specify an unlimited number of LU sessions. The lu maximum keyword is optional in the no form of the command.
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.
Examples
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 from 10.1.1.64 through 10.1.1.127) are limited to a maximum of five LU sessions while other clients with IP addresses in the subnet 10.1.1.0 are limited to a maximum of four 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
Related Commands
|
|
|
|---|---|
maximum-lus |
Limits the number of LU control blocks that will be allocated for TN3270 server use. |
client pool
To nail clients to pools, use the client pool command in listen-point configuration mode. To remove clients from pools, use the no form of this command.
client {[ip ip-address [ip-mask]] | [name DNS-name [DNS-domain-identifier]] | [domain-name DNS-domain] | [domain-id DNS-domain-identifier]} pool poolname
no client {[ip ip-address [ip-mask]] | [name DNS-name [DNS-domain-identifier]] | [domain-name DNS-domain] | [domain-id DNS-domain-identifier]} pool poolname
Syntax Description
Defaults
No default behavior or values.
Command Modes
Listen-point configuration
Command History
Usage Guidelines
If the pool is configured while logical units (LU)s are in use, existing clients are allowed to complete their sessions. A pool name can be identical to an LU name. When assigning an LU, the TN3270 server searches the LU name space first for specific requests, such as connections that specify a device name on CONNECT or LU name in the terminal type negotiation. The request is assumed to be directed to the specific LU rather than to the pool. Make sure the LU names do not conflict.
Examples
Nailing Clients to Pools by IP Address
The following is an example of the client pool command with the ip keyword configured. The command nails the client at IP address 10.1.2.3 with an IP mask of 255.255.255.0 to the pool named POOL-1:
tn3270-server
pool POOL-1 cluster layout 10s1p
listen-point 172.18.4.18
client ip 10.1.2.3 255.255.255.0 pool POOL-1
Nailing Clients to Pools by Device Name
The following is an example of the client pool command with the name keyword configured. The command nails the client at device name user1.cisco.com to the pool named POOL-2:
tn3270-server
pool POOL-2 cluster layout 4s1p
listen-point 172.18.5.168
pu T240CA 91922363 token-adapter 31 12 rmac 4000.4000.0001
allocate lu 1 pool POOL-2 clusters 1
client name user1.cisco.com pool POOL-2
Nailing Clients to Pools by Device Name Using a Domain ID
The following is an example of the client pool command with the name keyword and the optional DNS-domain-identifier argument configured. The command nails the client at device name lucy-isdn49.cisco.com to the pool named POOL-2:
tn3270-server
domain-id 23 .cisco.com
pool POOL-2 cluster layout 4s1p
listen-point 172.18.5.168
pu T240CA 91922363 token-adapter 31 12 rmac 4000.4000.0001
allocate lu 1 pool POOL-2 clusters 1
client name lucy-isdn49 23 pool POOL-2
Nailing Clients to Pools by Domain Name
The following is an example of the client pool command with the domain-name keyword configured. The command nails any client at domain name cisco.com to the pool named POOL-2:
tn3270-server
pool POOL-2 cluster layout 4s1p
listen-point 172.18.5.168
pu T240CA 91922363 token-adapter 31 12 rmac 4000.4000.0001
allocate lu 1 pool POOL-2 clusters 1
client domain-name .cisco.com pool POOL-2
Nailing Clients to Pools by Domain Name Using a Domain ID
The following is an example of the client pool command with the domain-id keyword configured. The command nails any client at domain name cisco.com to the pool named POOL-2:
tn3270-server
domain-id 23 .cisco.com
pool POOL-2 cluster layout 4s1p
listen-point 172.18.5.168
pu T240CA 91922363 token-adapter 31 12 rmac 4000.4000.0001
allocate lu 1 pool POOL-2 clusters 1
client domain-id 23 pool POOL-2
Related Commands
cmpc
To configure a Cisco Multipath Channel (CMPC or CMPC+) read subchannel and a CMPC (or CMPC+) write subchannel, use the cmpc command in interface configuration mode. To remove a subchannel definition and to deactivate the transmission group, use the no form of this command.
cmpc path device tg-name {read | write}
no cmpc path device
Syntax Description
Defaults
No default is specified.
Command Modes
Interface configuration
Command History
Usage Guidelines
Each cmpc configuration command in a given CMPC or CMPC+ TG specifies the same TG name. The corresponding tg command specifies the same TG name. Together, the cmpc and tg commands make up the TG specification.
The cmpc command defines the read/write subchannel addresses that CMPC or CMPC+ uses to connect to the host. The command corresponds to the definitions in the TRL major node on the host. Configure the cmpc command on a Cisco Mainframe Channel Connection (CMCC) adapter physical interface. Configure one read subchannel and one write subchannel. If CMPC or CMPC+ is configured on a CMCC adapter with two physical interfaces, the read and write CMPC or CMPC+ subchannels may be configured on separate physical interfaces.
The no cmpc command deactivates the CMPC or CMPC+ subchannel. If the TG is used for a non-High-Performance Routing (HPR) connection, all sessions using the TG will be terminated immediately. If the TG is an HPR connection, all sessions using the TG will be terminated if no other HPR connection is available to the host.
Examples
The following example configures a read and a write subchannel on path C020 for the CMPC or CMPC+ TG named CONFIGE:
cmpc C020 F8 CONFIGE READ
cmpc C020 F9 CONFIGE WRITE
Related Commands
csna
To configure Systems Network Architecture (SNA) support on a Cisco Mainframe Channel Connection (CMCC) physical channel interface, use the csna command in interface configuration mode. This command is used to specify the path and device or subchannel on a physical channel of the router to communicate with an attached mainframe. To delete the Cisco Systems Network Architecture (CSNA) device path, use the no form of this command.
csna path device [maxpiu value] [time-delay value] [length-delay value]
no csna path device
Syntax Description
Defaults
maxpiu value: 20470 bytes
time-delay value: 10 ms
length-delay value: 20470 bytes
Command Modes
Interface configuration
Command History
Usage Guidelines
The maxpiu, time-delay and length-delay keywords control the characteristics of host-bound traffic for the CSNA subchannel. The channel protocol used by CSNA allows multiple SNA frames to be blocked into one channel I/O block, reducing the channel bandwidth utilization and mainframe and CMCC adapter process utilization.
The maxpiu keyword allows you to set the maximum size of a host-bound channel I/O block.
The time-delay keyword instructs the CSNA subchannel to delay sending the channel I/O block for the specified time in milliseconds, from the time the first SNA packet is blocked. This can increase the network latency for an SNA packet by up to the specified time delay.
The length-delay keyword instructs the CSNA subchannel to delay sending the channel I/O block until it contains the number of bytes specified by the length-delay keyword. An accumulated block is sent to the mainframe if one of the following conditions is true:
•Time delay expires
•Channel I/O block reaches the length-delay size
•Channel I/O block reaches the maxpiu size.
A time delay value of 0 instructs the CSNA subchannel to send SNA packets to the mainframe as soon as they are received from the network. A length delay value of 0 instructs the CSNA subchannel to ignore this parameter.
The no csna command deactivates and removes the CSNA subchannel configuration. It also deactivates all Logical Link Control, type 2 (LLC2) sessions established over the subchannel.
Examples
The following example shows CSNA, offload, and Common Link Access for Workstations (CLAW) configured on a channel interface. CSNA has no dependencies to CLAW, offload, or CMPC.
interface channel 1/0
no ip address
no keepalive
offload c700 c0 172.18.1.127 TCPIP OS2TCP TCPIP TCPIP TCPIP API
claw C700 c2 172.18.1.219 EVAL CISCOVM AAA BBB
csna c700 c4
csna c700 c5 maxpiu 65535 time-delay 100 length-delay 65535
csna c700 c6 maxpiu 65535 time-delay 100
Feedback