|
|
Multiple mainframes can be connected to a single CIP by means of an ESCON director. Often, these mainframes run using the Multiple Image Facility (MIF), which permits the physical machine to be divided into multiple logical partitions (LPARs). By defining an unused partition on another mainframe, a user can move the operating system from a failed mainframe or mainframe partition to the unused partition. By having multiple paths to each device, the move is accomplished without changing the mainframe software. This function also permits moving an IP stack between multiple operating system images.
On the CIP, each IP connection is treated as a physical device. The CIP does not support multiple paths to a single IP connection (or device). Prior to IP Host Backup, the router configuration had to be changed whenever the mainframe operating system was moved from one mainframe or LPAR to another.
The IP Host Backup feature permits the mainframe operating system to be moved from one mainframe to another without requiring a change to the router configuration at the time of the move.
This feature is supported on the following platforms:
This section describes the configuration tasks that are associated with the IP Host Backup feature:
The following sections describe how to configure the IBM channel attach interface for IP Host Backup support. With IP Host Backup, you can configure backup for each CLAW or offload device, one path at a time, or you can specify a group of IP host paths and then configure which CLAW or offload IP addresses are used with those paths. Using the second method, specifying paths, provides a short-cut to the one at a time method.
You must define the devices, or tasks, supported on the interface. Some information you need to perform this task is derived from the following host system configuration files: MVSIOCP, IOCP, and the TCPIP configuration. Refer to the section Cisco IOS Software Release 11.2 documentation for full information on matching interface configuration values with host system values.
Perform the following task in interface configuration mode:
| Task | Command |
|---|---|
| Define the CLAW parameters for this device. | claw path device-address ip-address host-name device-name host-app device-app [broadcast] [backup] |
See the section "Configuration Tasks" for samples of claw commands for different configurations.
You must define the devices, or tasks supported on the interface. Some information you need to perform this task is derived from the following host system configuration files: MVSIOCP, IOCP, and the TCP/IP configuration. Refer to the section Cisco IOS Software Release 11.2 documentation for full information on matching interface configuration values with host system values.
Perform the following task in interface configuration mode:
| Task | Command |
|---|---|
| Define the offload parameters for this device. | offload path device-address ip-address host-name device-name host-app device-app host-link device-link [broadcast] [backup] |
See the section "Configuration Tasks" for samples of offload commands for different configurations.
Perform the following task beginning in interface configuration mode:
| Task | Command |
|---|---|
| Define the backup path, or paths, for this group and enter IP host backup configuration mode. | path path [path ] |
| Define the CLAW parameters for this device. | claw device-address ip-address host-name device-name host-app device-app [broadcast] |
| Alternatively, you can define the offload parameters for this device | offload device-address ip-address host-name device-name host-app device-app host-link device-link [broadcast] |
| Exit IP host backup configuration mode and return to interface configuration mode. | exit |
The following example shows how to configure IP host backup for three mainframe hosts, Mainframe 1, Mainframe 2, and Mainframe 3. Each mainframe is configured for at least three logical partitions (LPARs). (See Figure 1.)
The intent of this backup configuration is that the system named LPAR1 will be loaded on one of the mainframes in LPAR1 on that mainframe. The DASD for that system will be shared among all the mainframes but only one of them will ever IPL the system at one time. The same holds for LPAR2 and LPAR3.
The ESCON director has the following connections:
Excerpts from the host TCP/IP profiles show how the host might be configured. Excerpts from the router configuration show how the IP host backup configuration statements are configured.
Figure 1 shows the backup connection occurring between System C and LPAR2 when System B fails. It is also possible the backup connection occurs between System A and LPAR2; however, that situation is not shown.
The DEVICE and HOME statements in the nine TCP/IP profiles are similar to the following:
LPAR1 (mainframes 1, 2, 3): DEVICE CIP1 CLAW 630 LPAR1 CIP1 NONE 20 20 4096 4096 LINK CIP1L IP 0 CIP1 HOME 198.92.5.2 CIP1L LPAR2 (mainframes 1, 2, 3): DEVICE CIP1 CLAW 730 LPAR1 CIP1 NONE 20 20 4096 4096 LINK CIP1L IP 0 CIP1 HOME 198.92.5.3 CIP1L LPAR3 (mainframes 1, 2, 3): DEVICE CIP1 CLAW 830 LPAR1 CIP1 NONE 20 20 4096 4096 LINK CIP1L IP 0 CIP1 HOME 198.92.5.4 CIP1L
On the router, the CIP card is located in slot 3 and port 1 is connected to the ESCON director. The path commands define the group of paths that are used as the IP host backup.
interface channel 3/1 ip address 198.92.5.1 255.255.255.128 path c010 c110 c210 claw 30 198.92.5.2 lpar1 cip1 tcpip tcpip path c020 c120 c220 claw 30 198.92.5.3 lpar2 cip1 tcpip tcpip path c030 c130 c230 claw 30 198.92.5.4 lpar3 cip1 tcpip tcpip
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 or modified as a result of feature enhancements:
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] [backup]| 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. |
| backup | (Optional) Enables this CLAW connection to be used as part of a backup group of CLAW connections for the specified IP address. |
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.
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 port adapter 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.
Duplicate IP addresses are invalid for non-backup 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.
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
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
Use the claw IP host backup 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 device-address ip-address host-name device-name host-app device-app [broadcast]| 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.
IP host backup configuration
This command first appeared in Cisco IOS Release 11.2BC.
CLAW devices are used to switch IP packets between a mainframe and a channel attached router.
This command defines information that is specific to the interface hardware and the IBM channels supported on the interface. It is similar to the claw interface configuration command, but it requires no path variable and the backup keyword is assumed.
You must use the path interface configuration command to specify a number of paths that belong to a backup group and enter the IP host backup configuration mode before using this form of the claw command.
At most, 128 statements can be configured per interface because each port adapter 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.
Duplicate IP addresses are invalid for non-backup configurations.
Duplicate IP addresses are permitted if they appear within a backup group of only claw or offload interface configuration commands.
The following example shows 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 198.92.10.5 sysa router1 tcpip tcpip backup claw c100 00 198.92.10.5 sysa router1 tcpip tcpip backup claw c200 00 198.92.10.5 sysa router1 tcpip tcpip backup
Shortcut form:
path c000 c100 c200 claw 00 198.92.10.5 sysa router1 tcpip tcpip
| 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. |
| backup | (Optional) Enables this offload connection to be used as part of a backup group of offload connections for the specified IP address. |
This command has no defaults.
Interface configuration
This command first appeared in Cisco IOS Release 11.0.
Offload devices provide IP connectivity to a mainframe while at the same time offloading a large part of the TCP/IP processing to the CIP. Not every mainframe TCP/IP stack supports offload.
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 processing 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
The following example shows how an IP host backup group is specified using the backup keyword:
interface Channel3/0 no ip address no keepalive shutdown offload 0100 C0 10.30.1.2 TCPIP OS2TCP TCPIP TCPIP TCPIP API backup offload 0110 C0 10.30.1.2 TCPIP OS2TCP TCPIP TCPIP TCPIP API backup offload 0120 C0 10.30.1.2 TCPIP OS2TCP TCPIP TCPIP TCPIP API backup offload 0110 C2 10.30.1.3 TCPIP OS2TCP TCPIP TCPIP TCPIP API
| 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.2BC.
Offload devices provide IP connectivity to a mainframe while at the same time offloading a large part of the TCP/IP processing to the CIP. Not every mainframe TCP/IP stack supports offload.
The offload command uses the same underlying configuration parameters as does the claw command.
The following example shows two methods for entering the same IP host backup group information. The first group of commands is the long form, using the offload interface configuration command. The second group is the shortcut, using the path interface configuration command and a offload IP host backup configuration command.
Long form:
offload c000 00 198.92.10.5 sysa router1 tcpip tcpip tcpip api backup offload c100 00 198.92.10.5 sysa router1 tcpip tcpip tcpip api backup offload c200 00 198.92.10.5 sysa router1 tcpip tcpip tcpip api backup
Shortcut form:
path c000 c100 c200 offload 00 198.92.10.5 sysa router1 tcpip tcpip tcpip api
Use the path interface configuration command to specify one or more data paths for the IP host backup. Use the no form of the command to delete a single path.
path path [path ]| 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. |
This command has no defaults.
Interface configuration
This command first appeared in Cisco IOS release 11.2BC
Up to 16 path values can be specified in the path command.
The path command places you in IP host backup configuration mode, where you can enter additional commands to define backup groups for CLAW and offload connections.
The following example shows two methods for entering the same IP host backup group information. The first group of commands is the shortcut, using the path interface configuration command and a offload IP host backup configuration command. The second group is the long form, using the offload interface configuration command.
Shortcut form:
path c000 c100 c200 offload 00 198.92.10.5 sysa router1 tcpip tcpip
Long form:
offload c000 00 198.92.10.5 sysa router1 tcpip tcpip backup offload c100 00 198.92.10.5 sysa router1 tcpip tcpip backup offload c200 00 198.92.10.5 sysa router1 tcpip tcpip backup
Use the show extended channel backup privileged EXEC command to display information about the CLAW and offload commands for each backup group configured on CIP interfaces on the Cisco 7000 with RSP7000 and Cisco 7500 series.
show extended channel slot/port backup [ip-address]| slot | Slot number. |
| port | Port number. |
| backup | Display all CLAW or OFFLOAD commands associated with the backup group. |
| ip-address | (Optional) Display information about all devices in the backup group defined by ip-address. |
The default shows information for all configured backup groups.
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 backup command:
router# show extended channel 2/0 backup
Mode Path Device IP Address 198.92.10.5
CLAW C000 00 sysa system1 tcpip tcpip
CLAW C100 00 sysa system1 tcpip tcpip
CLAW C200 00 sysa system1 tcpip tcpip
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]] [connected]| 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. |
| connected | (Optional) For each backup group, only display information about the active subchannel or the first subchannel defined in the group if none are active. |
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 2/0 statistics
Path: C000 -- ESTABLISHED
Command Selective System Device CU
Dev Connects Retries Cancels Reset Reset Errors Busy
00 1997835 1982481 4 0 2 0 0
01 737406 0 3 0 2 0 0
10 1997835 1982481 4 0 2 0 0
11 737406 0 3 0 2 0 0
Blocks Bytes Dropped Blk Memd
Dev-Lnk Read Write Read Write Read Write wait Con
00-00 9 0 288 0 8 0 0 N
00-01 2112662 0 493367031 0 0 0 0 N
Total: 2112671 0 493367319 0 8 0 0
01-00 0 6 0 192 0 0 0 N
01-01 0 2084798 0 487593175 0 0 0 N
Total: 0 2084804 0 487593367 0 0 0
10-00 9 0 288 0 8 0 0 Y
10-01 2112662 0 493367031 0 0 0 0 Y
Total: 2112671 0 493367319 0 8 0 0
11-00 0 6 0 192 0 0 0 Y
11-01 0 2084798 0 487593175 0 0 0 Y
Total: 0 2084804 0 487593367 0 0 0
Path C000
Total: 4225342 4169608 986734638 975186734 16 0 0
Path: C100 -- ESTABLISHED
Command Selective System Device CU
Dev Connects Retries Cancels Reset Reset Errors Busy
00 4230 4219 4 0 2 0 0
01 4107 0 2 0 2 0 0
10 1997835 1982481 4 0 2 0 0
11 737406 0 3 0 2 0 0
Blocks Bytes Dropped Blk Memd
Dev-Lnk Read Write Read Write Read Write wait Con
00-00 9 0 288 0 7 0 0 Y
00-01 4231 0 236366 0 0 0 0 Y
Total: 4240 0 236654 0 7 0 0
01-00 0 6 0 192 0 0 0 Y
01-01 0 4222 0 1289544 0 0 0 Y
Total: 0 4228 0 1289736 0 0 0 Y
10-00 9 0 288 0 0 0 0 Y
10-01 2112662 0 593367031 0 0 0 0 y
Total: 2112671 0 593367319 0 8 0 0
11-00 0 6 0 192 0 0 0 y
11-01 0 2084798 0 587593175 0 0 0 y
Total: 0 2084804 0 587593367 0 0 0
Path C100
Total: 2116911 2089032 593903973 588883093 15 0 0
Path: C200 -- ESTABLISHED
Command Selective System Device CU
Dev Connects Retries Cancels Reset Reset Errors Busy
00 4230 4219 4 0 2 0 0
01 4107 0 2 0 2 0 0
Blocks Bytes Dropped Blk Memd
Dev-Lnk Read Write Read Write Read Write wait Con
00-00 9 0 288 0 7 0 0 N
00-01 4231 0 236366 0 0 0 0 N
Total: 4240 0 236654 0 7 0 0
01-00 0 6 0 192 0 0 0 N
01-01 0 4222 0 1289544 0 0 0 N
Total: 0 4228 0 1289736 0 0 0
Path C200
Total: 4240 4228 236654 1289736 7 0 0
Adapter Card
Total: 6349493 7058640 1580875265 1565359563 38 0 0
Last statistics 4 seconds old, next in 6 seconds
Table 5 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 [connected]| slot | Slot number. |
| port | Port number. |
| connected | (Optional) For each backup group, only display information about the active subchannel or the first subchannel defined in the group if none are active. |
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 connected command:
router# show extended channel 2/0 subchannel connected
Channel2/0: state up
Flags: VALID ESCON LOADED MEMD_ENABLED SIGNAL
Link: C4, Buffers 0, CRC errors 0, Load count 2
Link Incident Reports
implicit 0, bit-error 0, link failed 1,
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: 21
Model: 0 Manufacturer: CSC
Plant: A Sequence : 00000C35D765
Last
Mode Path Device Sense
CLAW C100 00 198.92.10.5 SYSA ROUTER1 TCPIP 0080
BACKUP
CLAW C100 01 198.92.10.5 SYSA ROUTER1 TCPIP 0080
BACKUP
CLAW C000 10 198.92.10.6 SYSB ROUTER1 TCPIP
CLAW C000 11 198.92.10.6 SYSB ROUTER1 TCPIP
CLAW C100 10 198.92,10.7 SYSC ROUTER1 TCPIP
CLAW C100 11 198.92.10.7 SYSC ROUTER1 TCPIP
Last statistics S seconds old, next in 4 seconds
| Field | Description |
|---|---|
| Channelx/y: state | The state can be up, down, or administratively down. |
| Flags | Possible values are as follows:
|
|
Link Incident Reports | Link Incidents are errors on an ESCON channel. These errors are reported to the host operating system and are recorded here for additional information.
|
|
Neighbor node
| Describes the channel or switch.
|
|
Local node | Describes the router.
|
|
Mode | CLAW, offload, or CSNA. |
| Path, device, IP address, and names | From the CLAW command. Because CLAW and offload commands define two devices, both devices are shown. |
| Last sense | 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. |
|
|