|
|
This chapter provides an introduction to the Cisco Mainframe Channel Connection Adapters (CMCCs) and provides information about the basic tasks required to configure any CMCC adapter on a Cisco router. This information is described in the following sections:
Details about configuring the Cisco IOS features that are supported by the CMCCs are described in the related chapters of this publication. For more information about the functions supported on a CMCC, see the "Supported Environments" section.
For hardware technical descriptions and information about installing the router interfaces, refer to the hardware installation and maintenance publication for your product. For a complete description of the CMCC adapter commands in this chapter, refer to the Cisco IOS Bridging and IBM Networking Command Reference (Volume 2 of 2). To locate documentation of other commands that appear in this chapter, use the command reference master index or search online.
To identify the hardware platform or software image information associated with a feature, use the Feature Navigator on Cisco.com to search for information about the feature or refer to the software release notes for a specific release. For more information, see the "Identifying Platform Support for Cisco IOS Software Features" section in the "Using Cisco IOS Software" chapter.
Each type of adapter (CIP or CPA) supports both ESCON and parallel channel attachment to the host and can eliminate the need for a separate front-end processor (FEP).
Figure 247 shows the type of channel connections and environments supported by the CMCC adapters.
The following topics in this section provide additional overview information about the CMCC adapters:
A single CIP can support up to two physical channel interfaces in any combination of either PCA or ECA. Each CIP is pre-configured with the appropriate channel adapters at manufacturing time.
The Cisco 7000 with RSP7000 and Cisco 7500 series routers support online insertion and removal (OIR), which allows you to install or remove CIPs while the system is operating.
The CIP provides the following primary benefits:
Each CPA provides a single channel interface (with a single I/O connector) for Cisco 7200 series routers. In some situations, this eliminates the need for a separate FEP.
The only differences between CMCC software applications running on the CIP and a CPA are performance and capacity. The performance difference is based upon differences in the internal bus architecture of a CIP and a CPA, and the capacity difference is based on the difference in maximum memory configurations (128 MB for CIP and 32 MB for CPA). For more information about differences between the CIP and CPA, see the "Differences between the CIP and CPA" section.
The Cisco 7200 series router supports online insertion and removal (OIR), which allows you to install or remove port adapters while the system is operating.
 |
Note In this chapter, references to CPA correspond to both the ECPA and the PCPA. |
The CPA provides the following primary benefits:
Refer to the Cisco 7200 Series Port Adapter Hardware Configuration Guidelines publication for more details.
Table 10 illustrates the differences between the CMCC adapters.
| Product Differences | CIP | ECPA | PCPA |
|---|---|---|---|
Cisco 7500 | Cisco 7200 | Cisco 7200 | |
ESCON | ESCON | Parallel | |
2 | 1 | 1 | |
128 MB | 32 MB | 32 MB | |
Cisco IOS Release 10.2 and later | Cisco IOS Release 11.3(3)T and later | Cisco IOS Release 11.3(3)T and later | |
2 | 0 | 0 | |
Yes | Disabled—Use the state-tracks-signal command to enable | Disabled—Use the state-tracks-signal command to enable |
The CMCC adapters provide support for the following environments:
This section provides guidelines to consider when preparing to configure a CMCC adapter. It includes limitations on the number of entities that you can configure on a CMCC adapter and provides information about correlating host configuration elements with your router configuration.
These guidelines are provided in the following subsections:
Each CMCC adapter can support the following number of configuration entities:
|
Note Although a CMCC adapter can technically support up to 32 internal LANs, the limit of up to 18 internal adapters on a CMCC adapter makes 18 internal LANs the practical limit. |
Configuring Cisco IOS software application features on a CMCC adapter for communication with the mainframe host requires the configuration of SAPs. SAPs are used by the CMCC adapter to establish communication with the Virtual Telecommunications Access Method (VTAM) on the mainframe and to identify Logical Link Control (LLC) sessions on a CMCC's internal adapter.
To uniquely identify an LLC session, a combination of the following four entities are used in a CMCC adapter. This combination of values is sometimes referred to as the MAC/SAP quadruple:
When you are configuring SAPs on a CMCC, it is important to remember how the SAP is used in combination with these other entities to establish a unique LLC session. In order for the LLC session to be unique, there cannot be an LLC session that duplicates all four values of the MAC/SAP quadruple. In fact, only one of the values needs to be unique to qualify the particular session. Understanding this requirement is a key factor in successfully configuring a CMCC adapter to support multiple entities.
To establish the LLC sessions between external network traffic and a feature such as CSNA on a CMCC adapter in the router, an internal LAN along with an internal adapter is defined. MAC addresses are established for the internal adapters that are defined on the internal LAN in the CMCC. An internal LAN can have multiple internal adapters, and therefore, multiple MAC addresses associated with it. When LLC sessions on the CMCC are established using the same internal adapter (and therefore, the same MAC address) and are destined for the same SAP and MAC address, the source SAP must uniquely identify the session.
Consider the following guidelines when configuring SAPs on a CMCC adapter:
The information in Table 11 and Table 12 is useful as a reference for understanding some of the administered LSAPs that might be encountered on the network external to the router. Remember that these are not values that the CMCC adapter enforces, and they do not specifically pertain to limitations in configuring the CMCCs.
| LSAP | Description |
|---|---|
00 | Null |
02 | Individual LLC Sublayer Management function |
03 | Group LLC Sublayer Management function |
06 | ARPANET IP |
0E | Proway Network Management and Initialization |
42 | IEEE 802.1 Bridge Spanning-Tree Protocol |
4E | EIA RS-511 Manufacturing Message Service |
7E | Cisco IOS 8208 (X.25 over IEEE 802.2) |
8E | Proway Active Station List |
AA | Subnetwork Access Protocol (SNAP) |
FE | Cisco IOS Network Layer Protocol |
FF | Global LSAP |
| LSAP | Description |
|---|---|
04 | IBM SNA Path control (individual) |
05 | IBM SNA Path control (group) |
18 | Texas Instruments |
80 | XNS |
86 | Nestar |
98 | ARPANET (ARP) |
BC | Banyan Vines |
E0 | Novell |
F0 | IBM NetBIOS |
F4 | IBM LAN Management (individual) |
F5 | IBM LAN Management (group) |
F8 | IBM Remote Program Load (RPL) |
FA |
Often in the mixed network environment of mainframes and LANs, an MVS systems programmer installs and maintains the mainframe side of the network, while a network engineer manages the routers on the LAN side of the network. In such an environment, the successful configuration of the CMCC adapter and its supported features requires the close coordination between these job functions at a customer site.
This section contains information for both the network engineer and the MVS systems programmer to properly configure the channel subsystem for the router and includes the following topics:
Other chapters in this publication that discuss configuration of supported features on a CMCC adapter provide additional information about host-related and router-related configuration tasks associated with that feature.
The following sample configuration shows the CHPID, CNTLUNIT, and IODEVICE statements that might be defined in an IOCP file for parallel channels and ESCON channels on the CIP or CPA. The parameters in bold indicate values that might vary by the type of channel being defined.
************************************************************************************** Parallel channel--CIP or CPA may be subchannel addresses 580-58F*************************************************************************************CHPID PATH=((21)),TYPE=BLCNTLUNIT CUNUMBER=0580,PATH=(21),UNIT=3088,UNITADD=((80,16)),SHARED=N,PROTOCOL=S4IODEVICE ADDRESS=(580,16),CUNUMBER=(0580),UNIT=CTC************************************************************************************** ESCON channel--CIP or CPA may be subchannel addresses D00-D0F*************************************************************************************CHPID PATH=((1F)),TYPE=CNCCNTLUNIT CUNUMBER=0D00,PATH=(1F),UNIT=3172,UNITADD=((00,16))IODEVICE ADDRESS=(D00,16),CUNUMBER=(0D00),UNIT=SCTC************************************************************************************** ESCON channel with ESCON director--CIP or CPA may be subchannel addresses 700-70F*************************************************************************************CHPID PATH=((1C)),TYPE=CNC,SWITCH=01CNTLUNIT CUNUMBER=0700,PATH=(1C),UNIT=3172,UNITADD=((00,16)),LINK=(C4)IODEVICE ADDRESS=(700,16),CUNUMBER=(0700),UNIT=SCTC
In addition, the UNIT types specified in the CNTLUNIT and IODEVICE statements differ for parallel and ESCON channels. The ESCON director also implements the additional parameters for SWITCH and LINK to identify a number for the ESCON director and specify the port in the ESCON director to which the router is connected.
|
Note In the format of a real IOCP file, all of the CHPID, CNTLUNIT, and IODEVICE statements are organized into separate groups, and are not listed one after the other as shown. You can correlate the statements in a real IOCP file by using the PATH parameter to associate the CHPID definition with a corresponding CNTLUNIT statement, and using the CUNUMBER parameter to correlate the IODEVICE and the CNTLUNIT statements. |
To properly configure the channel subsystem on the router side you need to know the following information:
This information is defined on the host in the IOCP. In versions of MVS 5.2 and later, an HCD might be used as an alternative method to define this information. To locate this information or to configure it on the mainframe host, contact your site's systems programmer.
When you define CLAW, CSNA, CMPC or CMPC+, and Offload parameters on a CMCC adapter, you must supply path information and device address information to support routing on an IBM channel. The path information can be simple, in the case of a channel directly attached to a router using bus and tag cables, or more complex when the path includes an ESCON director switch or multiple image facility (EMIF) support.
This example shows the syntax for the CMCC adapter commands that require subchannel information, which is configured in the path and device arguments of the following commands:
claw path device ip-address host-name device-name host-app device-app
[broadcast]
csna path device [maxpiu value][time-delay value][length-delay value]
cmpc path device tg-name {read | write}
offload path device ip-address host-name device-name host-ip-link device-ip-link
host-api-link device-api-link [broadcast] [backup]
The path argument in each of the commands is a four-digit hexadecimal value that concatenates the path value (2 digits), EMIF partition number (1 digit), and control unit logical address (1 digit) as described in Table 13.
For bus and tag channel connections, the path value is always 0100. You do not need the information in Table 13 to determine the path value.
| Path Argument Breakdown | Values | Description |
|---|---|---|
Path digits | 01-FF | For a directly attached ESCON channel or any Parallel channel this value is 01, unless a systems programmer has configured another value. For a channel attached through an ESCON director switch, specify the outbound port number in the first two digits of the path argument. This is the port which, from the router point of view, exits the switch and attaches to the host. |
EMIF partition number digit | 0-F | For a Parallel channel, this value is 0. For a directly attached ESCON channel, the value might be non-zero. If the host is running in Logical Partition (LPAR) mode and the CHPID is defined as shared, specify the partition number in this digit of the path argument. |
Control unit logical address digit | 0-F | For a Parallel channel, this value is 0. For a directly attached ESCON channel, the value might be non-zero. If the CUADD value is specified in the IOCP CNTLUNIT statement, specify that value in this digit of the path argument. |
Consider the network configuration in Figure 248, where two host systems connect to the ESCON director switch on paths 23 and 29. The channels both exit the switch on path 1B and attach to Router A. Note that the path between Host A and Host B is dynamically switched within the ESCON director. Host C is attached directly to Router B through path 42.
The IOCP control unit statements to configure the channel paths shown in Figure 248 might look similar to the following sample configuration statements:
Sample IOCP Control Unit Statements for Host A
CNTLUNIT CUNUMBER=0001, PATH=(23), LINK=1B, UNITADD=((00,64)), UNIT=SCTC, CUADD=F
Sample IOCP Control Unit Statements for Host B
CNTLUNIT CUNUMBER=0002, PATH=(29), LINK=1B, UNITADD=((00,64)), UNIT=SCTC, CUADD=A
Sample IOCP Control Unit Statements for Host C
CNTLUNIT CUNUMBER=000A, PATH=(42), UNIT=SCTC, UNITADD=((00,64))
|
Note A mainframe systems programmer can provide you with the actual IOCP values for your site's configuration. |
Using the above IOCP values as an example and following the guidelines provided in Table 13, the following path argument is used as shown in the example csna or cmpc commands for the two channel attachments to Router A:
csna 150F csna 190A cmpc 150F cmpc 190A
In Figure 248 the ESCON director ports 15 and 19 are the channel attachments from the ESCON director to each host. Note that the outbound ports from the ESCON director to the host are the values used in the first 2 digits of the path argument.
The following path argument is used for the directly attached channel to Router B, as shown in the example csna or cmpc commands:
csna 0100 cmpc 0100
The UNITADD parameter in the CNTLUNIT macro of the IOCP file defines the valid range for device addresses. For example, a UNITADD parameter of (00,64) means that the first valid device address is 00 and the number of devices is 64. In the hexadecimal notation used by channel configuration commands this translates to a range of 00 to 3F.
Using that unit address information, the example csna and cmpc commands now add values for the device arguments to the two channel attachments to Router A:
csna 150F 00 csna 190A 01 cmpc 150F 02 cmpc 150F 03 cmpc 190A 03 cmpc 190A 04
The following example csna and cmpc commands show the path and device arguments for the directly attached channel to Router B:
csna 0100 00 cmpc 0100 01 cmpc 0100 02
|
Note In this example, if you configure CSNA and CMPC on the same CMCC port then you must use unique unit addresses. Also, CMPC requires two unit addresses for the device argument. One unit address is used in a cmpc command to define the read subchannel, and one is used in a second cmpc command to define the write subchannel. The device addresses do not need to be consecutive. |
Example 1
In this first example, the IODEVICE ADDRESS value is 800. Using this number you can locate the IODEVICE ADDRESS statement in the IOCP file, which points you to the CNTLUNIT statement that contains the device argument values for the claw, csna, cmpc or offload commands:
IODEVICE ADDRESS=(0800,256),CUNUMBR=(0012),UNIT=SCTC **** Address 800 points to CUNUMBR 0012 in the following statement CNTLUNIT CUNUMBR=0012,PATH=(28),UNIT=SCTC,UNITADD=((00,256)) **** A valid value for the device argument is the UNITADD value of 00
From this example, the csna command would be similar to the following:
csna 0100 00
Example 2
In this example the mainframe systems programmer provides an available IODEVICE ADDRESS of 350, which does not directly correspond to a value in the IOCP file, but is within a range of 64 addresses beginning at device address 340 (as shown in the IODEVICE ADDRESS=(340,64) statement). The value 350 is at an offset of 10 from the beginning value of 340 in this statement:
IODEVICE ADDRESS=(0340,64),CUNUMBR=(0008),UNIT=SCTC IODEVICE ADDRESS=(0380,64),CUNUMBR=(0009),UNIT=SCTC **** Address 350 is in the range of 64 addresses beginning at address 340 corresponding **** to CUNUMBER 0008 CNTLUNIT CUNUMBR=0008,PATH=(24),UNIT=SCTC,UNITADD=((40,64)),SHARED=N, X **** The device is the UNITADD value of 40, offset by 10, which is 50
To determine the unit address for the device argument value in the claw, csna, cmpc or offload commands, you must use the same offset that you determined for the IODEVICE ADDRESS and calculate the UNITADD parameter from the corresponding CNTLUNIT statement. In this example, CUNUMBR=0008 is the corresponding CNTLUNIT statement for IODEVICE ADDRESS 350. The first unit address in that CNTLUNIT statement is 40 (in parameter UNITADD), which correlates to the first IODEVICE ADDRESS of 340. To determine the corresponding unit address for IODEVICE ADDRESS 350, determine the value at offset 10 from 40, which is 50.
In this example, the csna command would be similar to the following:
csna 0100 50
When you are connecting mainframe hosts running MVS or VM with a CMCC adapter and its associated Cisco IOS software features in a router, you must disable the missing interrupt handler (MIH) on the host to prevent the host from waiting for an input/output (I/O) operation to complete. Disabling the MIH is required to properly operate CLAW, CMPC, and CMPC+ features on a CMCC adapter.
This section includes the following topics:
For additional information about disabling the MIH, refer to the IBM publication Transmission Control Protocol/Internet Protocol TCP/IP Version 2 Release 2.1 for MVS: Planning and Customization (publication SC31-6085 or later).
|
Note The statement IOS=xx specifies that xx is the suffix of the IECIOS member that contains the configuration. For example, the statement IOS=01 points to the IECIOS01 member. If this statement is not included in the IEASYS file, you can specify it dynamically using the /SET IOS=xx command on the command line. For more information, see your site's systems programmer. |
To disable the MIH on an MVS host, perform the following steps:
MIH TIME=00:00:00, DEV=(yyy-yyy)
This configures the MVS host to disable the MIH every time that MVS is restarted (an Initial Program Load (IPL) is performed).
Step 2 To dynamically change the MIH value for the currently active MVS operating system, issue the following command at the command line:
/SETIOS MIH DEV=xxx, TIME=00:00
Step 3 To display the currently enabled MIH value, issue the following command at the command line:
/D IOS,MIH
|
Note If you are using Dynamic Reconfiguration Management (DRM), type DYNAMIC=NO in the device statement. This value can be YES for IBM TCP/IP version 3.2. |
To disable the MIH on a VM host, perform the following steps:
SET MITIME yyy-yyy 00:00
or
SET MITIME yyy-yyy OFF
This configures the VM host to disable the MIH every time that VM is restarted (an Initial Program Load (IPL) is performed).
Step 2 To dynamically change the MIH value for the currently active VM operating system, issue either of the commands shown in Step 1 at the command line.
Step 3 To display the currently enabled MIH value, issue the following command at the command line:
Q MITIME
|
Note For VM or MVS Guests under VM, code V=R (Real mode) for the Guest so that the CLAW channel programs build properly. For more information, see your site's systems programmer. |
This section describes some of the global tasks that apply to configuring any CMCC adapter. Information about configuring features on a CMCC adapter are described in the related chapters of this guide.
This section includes the following configuration tasks:
See the "CPA Microcode Load Configuration Examples" section for examples.
Beginning with Cisco IOS Release 11.1, the CIP microcode (or CIP image) no longer is bundled with the Cisco IOS software. You must have Flash memory installed on the Route Switch Processor (RSP) card to use the IBM channel-attachment features in Cisco IOS Release 11.1 and later.
The CIP image is preloaded on Flash cards for all Cisco 7000 with RSP7000 and Cisco 7500 series routers ordered with the CIP option for Cisco IOS Release 11.1 and later.
Use the commands in this section if you are loading the CIP microcode image for the first time, or for all adapters in your router.
To prepare the CIP, use the following commands beginning in privileged EXEC command mode:
| Command | Purpose | |
|---|---|---|
Step 1 | Router>enable | Enters the privileged EXEC mode command interpreter. |
Step 2 | Router#copy tftp:filename [bootflash: | slot0: | slot1:]filename | Copies the CIP microcode image from a server to either of the Flash memory cards. The source of the file is tftp:filename. Use the appropriate command for your system. You must be running Cisco IOS Release 11.1 or later prior to executing a copy tftp command. |
Step 3 | Router#configure terminal | From privileged EXEC command mode, enters global configuration mode and specifies that the console terminal is the source of the configuration subcommands. |
Step 4 | Router(config)#microcode cip flash slotn:cipxx-yy or Router(config)#microcode cip flash bootflash:cipxx-yy | Configures the router to load the Flash image to the CIP:
|
Step 5 | Router(config)#microcode reload | Forces a microcode reload for all adapters in the router. Note This command shuts down the router if you are on a live network. |
Step 6 | Router(config)#end | Exits global configuration mode. |
Step 7 | Router#copy running-config startup-config | Saves the running configuration as the new startup configuration in NVRAM. |
Beginning with Cisco IOS Release 11.1, the CIP microcode (or CIP image) no longer is bundled with the Cisco IOS software. You must have Flash memory installed on the RSP card to use the IBM channel-attachment features in Cisco IOS Release 11.1 and later.
The CIP image is preloaded on Flash cards for all Cisco 7000 with RSP7000 and Cisco 7500 series routers ordered with the CIP option for Cisco IOS Release 11.1 and later.
Use the commands in this section if you are upgrading the CIP image in your router.
To upgrade the CIP microcode, use the following commands beginning in privileged EXEC command mode:
To prepare the CPA, use the following commands beginning in privileged EXEC command mode:
| Command | Purpose | |
|---|---|---|
Step 1 | Router>enable | Enters the privileged EXEC mode command interpreter. |
Step 2 | Router#copy tftp:filename [bootflash: | slot0: | slot1:]filename | Copies the CPA microcode image from a server to either of the Flash memory cards. The source of the file is tftp:filename. Use the appropriate command for your system. You must be running Cisco IOS Release 11.1 or later prior to executing a copy tftp command. |
Step 3 | Router#configure terminal | From privileged EXEC command mode, enters global configuration mode and specifies that the console terminal is the source of the configuration subcommands. |
Step 4 | Router(config)#microcode {ecpa | pcpa}
slotn:xcpaxx-yy
| Loads the microcode from an individual microcode image that is stored as a file on a Flash memory card on a CPA adapter. The slot argument of the command specifies the slot location and filename of the microcode image, such as slot0:xcpa26-1. |
Step 5 | Router(config)#microcode reload or Router#microcode reload all | From global configuration mode, loads the CPA microcode image for all of the adapters in the router. or From privileged EXEC mode, forces a microcode reload for all CPA adapters. Note These commands shut down the router if you are on a live network. |
Step 6 | Router(config)#end | Exits global configuration mode. |
Step 7 | Router#copy running-config startup-config | Saves the running configuration as the new startup configuration in NVRAM. |
The CPA microcode image is preloaded on Flash memory cards for Cisco 7200 series routers for Cisco IOS Release 11.3(3)T and later. You may be required to copy a new image to Flash memory when a new microcode image becomes available. Use the commands in this section if you are upgrading or loading a microcode image other than the default image for a particular CPA adapter.
To prepare the CPA, use the following commands beginning in privileged EXEC command mode:
*Oct 1 13:37:28.078: %SYS-5-RELOAD: Reload requested System Bootstrap, Version 11.1(2) [nitin 2], RELEASE SOFTWARE (fc1) Copyright (c) 1994 by cisco Systems, Inc. SLOT 2 RSP2 is system master RSP2 processor with 65536 KB of main memory CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC CCCCCCCCCCCCCCCCCCCCCCCCCCCCCreading the file into memory... Self decompressing the image : ########################################################################################## ########################################################################################## ################### [OK] %DBUS-3-NOSUPPORT: No driver support in this image for CIP2 in slot 4 (card type 13) - disabled %RSP-3-NOSTART: No microcode for CIP2 card, slot 4 %SYS-4-CONFIG_NEWER: Configurations from version 12.0 may not be correctly understood. %DBUS-3-NOSUPPORT: No driver support in this image for CIP2 in slot 4 (card type 13) - disabled %RSP-3-NOSTART: No microcode for CIP2 card, slot 4
The Cisco IOS software loads either the default CIP or CPA microcode image, or the image specified in the microcode command. If you want to confirm the microcode image that is loaded on the router, use the show controllers cbus command for the CIP or the show controllers channel command for the CPA to display the loaded microcode images.
To verify the CIP or CPA microcode, use the following commands beginning in privileged EXEC command mode:
Some CMCC adapter software features are configured on a virtual port. On the CIP adapter cards installed in a Cisco 7000 with RSP7000 or a Cisco 7500 series router, there are up to two physical ports, numbered 0 and 1, and a virtual port, numbered 2. However, on the CPA installed in a Cisco 7200 series router, the single physical port and the virtual port are configured using the same port number ID, number 0.
When you configure a parallel channel-attached interface (such as a PCA on a CIP or a PCPA on a CPA) that uses bus-and-tag connections, you can specify a data rate of either 3 MBps or 4.5 MBps.
Note that the unit of measure for this command is megabytes per second (MBps). When you use the show interface channel command, the data rate is shown in the BW field (for bandwidth) in kilobits per second (kbps). For example, a channel data rate of 3 MBps is shown as 36864 kbps in the output for the show interface channel command.
To configure the parallel data rate on the router, use the following command in interface configuration mode:
The channel-protocol command has a corollary parameter called PROTOCOL in the CNTLUNIT statement of the mainframe IOCP definition. The PROTOCOL parameter in the IOCP definition specifies the maximum speed of a bus-and-tag channel connection for the corresponding CSNA device in the router. Note that even if the CNTLUNIT statement in the IOCP specifies a value of PROTOCOL=S4 (4.5 MBps), the channel interface will operate at 3 MBps if at the router you use the default value or specify s in the channel-protocol command. Therefore, if you want to configure a channel speed of 4.5 MBps, be sure to specify a value of s4 for both the PROTOCOL parameter in the IOCP and the channel-protocol command in the router.
If you want to use Hot Standby Router Protocol (HSRP) or SNMP alerts to monitor channel interface status for an ECPA or PCPA channel interface, use the following command in interface configuration mode to enable physical interface signal tracking:
| Command | Purpose |
|---|---|
Router(config-if)#state-tracks-signal | Enables tracking of the physical interface signal for an ECPA or PCPA channel interface. |
The state-tracks-signal command is valid only on channel interfaces which combine the functions of both a physical and virtual interface. The ECPA and PCPA are examples of this type of channel interface. The command is not valid for the CIP, which has a separate channel interface for the virtual channel functions.
You can perform the tasks in the following sections to monitor and maintain the interfaces:
Perform the following commands in EXEC mode to display information associated with each command. All commands are applicable to all CMCC adapter interfaces (CIP and CPA), unless it is mentioned that they are specific to a particular CMCC adapter. Commands are listed in alphabetic order.
There are several commands that you can use on a CMCC adapter to clear statistics counters by interface or by feature, or to reset the hardware logic on an interface.
| Command | Purpose |
|---|---|
Router#clear counters [type slot/port] | Clears interface counters on the router. |
|
Note This command does not clear counters retrieved using Simple Network Management Protocol (SNMP), but only those seen with the EXEC show interfaces command. |
You can reset the statistics counters that are displayed in the output of the show extended channel commands by a particular feature on the interface.
|
Note This command does not clear counters retrieved using Simple Network Management Protocol (SNMP), but only those seen with the EXEC show extended channel commands. |
| Command | Purpose |
|---|---|
Router#clear interface [type slot/port] |
In Cisco IOS Release 12.0(4.1) and later, you can use the state-tracks-signal configuration command to control how you want the state of the CPA's channel interface to be reported. The state-tracks-signal command is useful in environments where you are using HSRP or SNMP alerts to monitor channel interface status.
To enable physical interface signal tracking, use the following command in interface configuration mode:
| Command | Purpose |
|---|---|
Router(config-if)#state-tracks-signal | Enables tracking of the physical interface signal for an ECPA or PCPA channel interface. |
When the state-tracks-signal command is used on an interface that is configured for no shutdown, then the state of the channel interface is reported according to the status of the physical channel interface signal. If the physical channel interface signal is not present, then the channel interface status is DOWN/DOWN.
When the channel interface is configured for no state-tracks-signal (the default) and no shutdown, the channel interface status is always reported as UP/UP, even when there is no signal present on the physical connection. This configuration is useful for TN3270 server environments that are operating in a mode without any physical channel interface connections.
You can disable an interface on a CMCC adapter. Disabling an interface disables all of the functions on the specified interface and marks the interface as unavailable on all monitoring command displays. This information is communicated to other network servers through all dynamic routing protocols. The interface will not be mentioned in any routing updates. On a CMCC adapter with an ESCON interface, a command is sent to the host to inform it of the impending shutdown. On the CMCC adapter's Parallel interface, the shutdown command disables the adapter card's transceivers and the interface stops responding to all commands.
It is recommended that you shut down a channel interface for some of the following reasons:
To shut down an interface and then restart it, use the following commands in interface configuration mode:
| Command | Purpose | |
|---|---|---|
Step 1 | Router(config-if)#shutdown | Shuts down an interface. |
Step 2 | Router(config-if)#no shutdown | Enables an interface. |
| Command | Purpose | |
|---|---|---|
Step 1 | Router(config)#ip domain-name name Router(config)#ip name-server | Configures the router FTP services. |
Step 2 | Router(config)#exception slot [slot] protocol//:host/filename | Configures the CMCC adapter core dump feature. |
|
Note The exception slot command is only supported on the Cisco 7000 with RSP7000 and Cisco 7500 series routers. On the Cisco 7200 series routers, only FTP is supported. |
While the router is running, you can use the write EXEC command to write the contents of a CMCC adapter that is not halted:
| Command | Purpose |
|---|---|
Router#write | Writes the contents of a CMCC adapter. |
|
Note The output obtained by the exception slot command can be interpreted by a qualified Cisco technical support person. |
The following example shows output from running the copy tftp command to copy a new image to Flash memory:
Router#copy tftp:xcpa26-2 slot0:xcpa26-2 Address or name of remote host []? neptune Translating "neptune"...domain server (10.20.30.10) [OK] Destination filename [xcpa26-2]? Accessing tftp://neptune/xcpa26-2... Loading motto/xcpa26-2 from 10.20.30.10 (via Fast Ethernet0/0): ! Expanding slot0:xcpa26-2_kernel_xcpa (343148 bytes): !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Expanding slot0:xcpa26-2_seg_802 (237848 bytes): !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Expanding slot0:xcpa26-2_seg_cmpc (319960 bytes): !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Expanding slot0:xcpa26-2_seg_csna (89856 bytes): !!!!!!!!!!!!!!!!!! Expanding slot0:xcpa26-2_seg_eca (461424 bytes): !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Expanding slot0:xcpa26-2_seg_offload (80344 bytes): !!!!!!!!!!!!!!!! Expanding slot0:xcpa26-2_seg_pca (69376 bytes): !!!!!!!!!!!!!! Expanding slot0:xcpa26-2_pseg_push (15936 bytes): !!! Expanding slot0:xcpa26-2_seg_tcpip (158896 bytes): !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Expanding slot0:xcpa26-2_seg_tn3270 (601784 bytes): !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!! [OK - 2387456/4774912 bytes] 2387456 bytes copied in 110.588 secs (21704 bytes/sec) router#
After copying a CMCC ucode image to flash memory, a directory command of the flash device displays the following:
Router#dir slot0: Directory of slot0:/ 1 -rw- 1 Aug 18 1998 12:29:12 xcpa26-2 2 -rw- 344438 Aug 18 1998 12:29:12 xcpa26-2.kernel_xcpa 3 -rw- 237848 Aug 18 1998 12:29:37 xcpa26-2.seg_802 4 -rw- 319960 Aug 18 1998 12:29:56 xcpa26-2.seg_cmpc 5 -rw- 89856 Aug 18 1998 12:30:15 xcpa26-2.seg_csna 6 -rw- 461424 Aug 18 1998 12:30:20 xcpa26-2.seg_eca 7 -rw- 80344 Aug 18 1998 12:31:03 xcpa26-2.seg_offload 8 -rw- 69376 Aug 18 1998 12:31:07 xcpa26-2.seg_pca 9 -rw- 15936 Aug 18 1998 12:31:11 xcpa26-2.seg_push 10 -rw- 158896 Aug 18 1998 12:31:12 xcpa26-2.seg_tcpip 11 -rw- 601784 Aug 18 1998 12:31:32 xcpa26-2.seg_tn3270 7995392 bytes total (5614116 bytes free)
The following example loads the microcode from an individual microcode image that is stored as a file in the PCMCIA card in slot 0:
Router(config)# microcode ecpa slot0:xcpa26-2 Router(config)# microcode reload
Posted: Mon Jan 14 17:52:47 PST 2002
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
