|
|
Logical unit (LU) address mapping allows a client IP address to be mapped, or "nailed," to one or more LU local addresses on one or more physical units (PUs) by means of router configuration commands. You can control the relationship between the TN3270 client and the LU.
Clients from traditional TN3270 (non-TN3270E) devices can connect to specific LUs, which overcomes a limitation of TN3270 devices that cannot specify a "CONNECT LU." LU nailing is useful for TN3270E clients, because you can perform the configuration at the router, providing central control, rather than at the client.
To maintain a configuration file that exceeds 128 KB there are two alternatives. The configuration file can be stored compressed in NVRAM. Or, the configuration file can be stored in Flash memory that is either internal Flash or on a PCMCIA card.
The service compress-config global command specifies that the configuration file is to be stored compressed in NVRAM. Once the configuration file has been compressed, the router functions normally. A show startup-config EXEC command expands the configuration before displaying it. When the system is booted, it recognizes that the configuration file is compressed and will expand it and proceed normally.
The example below compresses a 129 KB configuration file to 11 KB.
router# copy running-config startup-config Building configuration... Compressing configuration from 129648 bytes to 11077 bytes [OK]
The size of the configuration must not exceed three times the NVRAM size. For a 128 KB-size NVRAM, the largest expanded configuration file size is 384 KB.
If the boot ROMs do not recognize a compressed configuration, the following message is displayed:
Boot ROMs do not support NVRAM compression Config NOT written to NVRAM
Note that you must first issue a copy startup-config slot0:router-config command prior to the boot config slot0:router-config command to create the Flash configuration file. After you have created the Flash configuration file, update the Flash again.
For example, the following commands store the configuration file in Flash memory:
copy startup-config slot0:router-config conf t boot buffersize <bytes> boot config slot0:router-config copy running-config startup-config
Care must be taken when editing or changing a large configuration. Flash memory space is used every time a copy running-config startup-config is issued. Because file management for Flash memory, such as optimizing free space, is not done automatically you must pay close attention to available Flash memory. Cisco recommends that you use a large-capacity Flash card of at least 20 MB.
Where a client or set of clients is nailed to a set of more than one LU, the same logic applies. If the configured LU nailing maps a screen client to a set of LUs, the LU nailing algorithm attempts to match the client to a previously used LU that was most recently used with the same terminal model type as requested by the client for this connection. If a match is found, that LU is used. If a match is not found, any LU in the set that is not currently in use is chosen. If there is no available LU in the set, the connection is rejected.
For example, the following LUs are nailed to clients at address 192.195.80.40, and LUs BAGE1004 and BAGE1005, which were connected but are now disconnected.
lu name client-ip:tcp nail state model frames in out idle for 1 BAGE1001 192.195.80.40:3822 Y P-BIND 327904E 4 4 0:22:35 2 BAGE1002 192.195.80.40:3867 Y ACT/SESS 327904E 8 7 0:21:20 3 BAGE1003 192.195.80.40:3981 Y ACT/SESS 327803E 13 14 0:10:13 4 BAGE1004 192.195.80.40:3991 Y ACT/NA 327803E 8 9 0:0:7 5 BAGE1005 192.195.80.40:3997 Y ACT/NA 327805 8 9 0:7:8
If a client at IP address 192.195.80.40 requests a terminal model of type IBM-3278-5, LU BAGE1005 will be selected over BAGE1004.
lu name client-ip:tcp nail state model frames in out idle for 1 BAGE1001 192.195.80.40:3822 Y P-BIND 327904E 4 4 0:23:29 2 BAGE1002 192.195.80.40:3867 Y ACT/SESS 327904E 8 7 0:22:14 3 BAGE1003 192.195.80.40:3981 Y ACT/SESS 327803E 13 14 0:11:7 4 BAGE1004 192.195.80.40:3991 Y ACT/NA 327803E 8 9 0:1:1 5 BAGE1005 192.195.80.40:4052 Y ACT/SESS 327805 13 14 0:0:16
This feature is supported on the following platforms:
To configure LU nailing, perform the following task in TN3270 PU configuration mode:
| Task | Command |
|---|---|
| Configure the IP address and nail type and specify the locaddr range. | client [printer] ip ip-address [mask] lu first-locaddr [last-locaddr] |
The client command allows a client with multiple TN3270 connections from the same IP address to nail their screen connections to LUs that are configured as screen LUs at the host and to nail printer connections to LUs that are configured as printers at the host. When the connection is made, a device type of "328*" is matched to a printer definition, and any other device type is matched to a screen definition.
This section provides sample configurations for configuring the LU Nailing feature. Refer to the following configuration examples:
The following example shows a direct PU and a DLUR PU configured with the same listening point. The PUs are configured with the same nailed client IP address.
tn3270-server pu PU1 05D18081 172.28.1.82 ... client ip 192.195.80.40 lu 1 10 dlur pu PU2 05D190B3 172.28.1.82 client ip 192.195.80.40 lu 1 10
Assuming each PU has three static LUs, which are ACTLU enabled and not connected, then these LUs will be the first to be nailed. That is, the first six connections from client IP address 192.195.80.40 will use the static LUs and subsequent connections will use the remaining dynamic LUs.
In the following example, locaddrs 1 to 50 are reserved for all remote screen 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
To remove a nailing definition, the complete range of locaddrs must be specified as configured. So for the example above, the following command would remove the lu nailing definition.
no client ip 171.69.176.28 255.255.255.0 lu 1 50
If an attempt is made to remove a subset of the range of configured locaddrs then the command is rejected.
no client ip 171.69.176.28 255.255.255.0 lu 1 20 % client ip 171.69.176.28 lu not matched with configured lu 1 50
This section documents new commands. All other commands used with this feature are documented in the Cisco IOS Release 11.2 command references. The following commands have been added as a result of feature enhancements:
The following commands have been modified as a result of feature enhancements:
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 ip-address | Specifies remote client IP address. |
| mask | Mask applied to the remote device address. Multiple client IP addresses in the same subnet can be nailed to the same range of locaddrs. |
| lu 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 F.
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 and providing no TN3270 device name will be connected as described under "LU Nailing and Model Matching".
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 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 F.
The following is sample output 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
Table 1 describes significant fields in the display.
| 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 which 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 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 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 ext c2/2 tn3270 client 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 ext c2/2 tn3270 client 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 ext c2/2 tn3270 client 10.14.1.21 pending
Total 2 clients found using 10.14.1.21
Table 2 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 | 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 | Indicates whether LU is DYNAMIC or STATIC. |
| NEGOTIATED type | Indicates whether client is TN3270 or TN3270E. |
| BYTES IN / OUT number/number | Total number of bytes sent to and 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 and 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. |
| 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. |
Privileged EXEC
The display shown depends on whether the PU is a direct PU or a SNA session switch PU.
The following is sample output 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 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 nail state model frames in out idle for
1 GOAN1X01 never connected yes ACTIVE 1 1 0:32:14
2 GOAN1X02 never connected yes ACTIVE 1 1 0:32:14
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
Table 3 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. |
Support for the following Cisco proprietary MIBs has been enhanced:
|
|