Configuring Cisco Mainframe Channel Connection Adapters

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).

The following topics in this section provide additional overview information about the CMCC adapters:

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.

• Cost-effective---A CPA in a Cisco 7200 series router provides industry-leading price performance.

• Simplified migration path---The CPA and CIP microcode support the same features and applications, enabling seamless migration for network expansion.

• Flexibility---The Cisco 7200 series router platform provides a great number of features and capabilities that can be used in conjunction with a CPA.

Refer to the Cisco 7200 Series Port Adapter Hardware Configuration Guidelines publication for more details.

• TCP/IP environments using CLAW---The Cisco IOS software implements the CLAW channel protocol to transport data between the mainframe and a CMCC adapter in TCP/IP environments.

For more information about configuring a CMCC adapter for CLAW, see the "Configuring CLAW and TCP/IP Offload Support" chapter in this publication.

• TCP/IP offload environments---TCP/IP offload support on a CMCC adapter provides the capability to significantly reduce the amount of overhead processing that an IBM mainframe (running the Multiple Virtual Storage (MVS), Virtual Machine (VM), or Transaction Processing Facility (TPF) operating system) must execute for handling of TCP/IP packets.

For more information about configuring a CMCC adapter to support TCP/IP offload, see the "Configuring CLAW and TCP/IP Offload Support" chapter in this publication.

• IP host backup environments---IP host backup support on a CMCC adapter allows 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.

For more information about configuring a CMCC adapter for IP host backup support, see the "Configuring CLAW and TCP/IP Offload Support" chapter in this publication.

• CSNA environments---The CSNA feature on a CMCC adapter provides support for Systems Network Architecture (SNA) protocols to the IBM mainframe.

For more information about configuring a CMCC adapter for CSNA, see the "Configuring CSNA and CMPC" chapter in this publication.

• Cisco Multipath Channel (CMPC) environments---CMPC is Cisco System's implementation of IBM's MultiPath Channel (MPC) feature on a CMCC adapter. CMPC allows VTAM to establish Advanced-Peer-to-Peer Networking (APPN) connections using both High Performance Routing (HPR) and Intermediate Session Routing (ISR) through channel-attached router platforms.

For more information about configuring a CMCC adapter for CMPC, see the "Configuring CSNA and CMPC" chapter in this publication.

• Cisco Multipath Channel+ (CMPC+) environments---CMPC+ is Cisco System's implementation of IBM's Multipath Channel+ feature on a CMCC adapter. CMPC+ supports the MPC+ features and protocols necessary to support IP and enables High Performance Data Transfer (HPDT). It allows TCP/IP connections to the host through a CMCC adapter, using either the TCP/IP stack or the High Speed Access Services (HSAS) IP stack.

For more information about configuring a CMCC adapter for CMPC+, see the "Configuring CMPC+" chapter in this publication.

• TN3270 server environments---The TN3270 server feature on a CMCC adapter provides a mapping between an SNA 3270 host and a TN3270 client connected to a TCP/IP network. From the perspective of an SNA 3270 host connected to the CMCC adapter, the TN3270 server is an SNA device that supports multiple PUs, with each PU supporting up to 255 logical units (LUs). From the perspective of a TN3270 client, the TN3270 server is a high-performance Telnet server that supports Telnet connections, negotiation and data format.

For more information about configuring a CMCC adapter to support the TN3270 server, see the "Configuring the TN3270 Server" chapter in this publication.

---

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.

---

---

Note Several SAP values are reserved for particular protocols by the IEEE, which effectively reduces the number of SAPs available outside the router to a total of 64. This is important to remember for SAP values that you configure on the CMCC adapter for communication with network entities external to the router, so that you avoid SAP conflicts. For communication outside the router, SAP values in the range of hexadecimal 04 to 9E are recommended in increments of 4. For additional guidelines on configuring SAPs, see the "SAP Configuration Guidelines" section.

---

• Source MAC address

• Destination MAC address

• Source SAP value

• Destination SAP value

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:

• If the SAP is going to be used for communication external to the router, use the following guidelines when specifying the SAP value:

  • Avoid SAPs reserved for well-known protocols.

  • Avoid a SAP of 00, which is reserved for the MAC SAP often used in the exchange of a test frame.

  • Specify SAP values in multiples of 4.

---

Note Some of the well-known SAP values for protocols are hexadecimal AA for SNAP, E0 for IPX, F0 for NetBIOS. For more information about some of these reserved SAP values, see Table 10 and Table 11.

---

• If the SAP is going to be used for communication within the router, you can maximize the number of available SAPs on an internal adapter by using multiples of 2 up to a total of 128. The CMCC adapter does not enforce the well-known values reserved for protocols and accepts any even SAP value.

• SAP 4 is commonly used as the SAP for SNA.

• CSNA can activate a maximum of 128 SAPs on the CMCC at any given time. If you are configuring the TN3270 server using a CSNA connection, the total number of SAPs open on the host plus the number of SAPs defined for PUs on the TN3270 server must be less than or equal to 128.

Reference for IEEE and Manufacturer Administered SAPs

Table 11: LSAPs Implemented by Manufacturer

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	Ungermann-Bass

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:

*************************************************************************************
* Parallel channel--CIP or CPA may be subchannel addresses 580-58F
*************************************************************************************
CHPID    PATH=((21)),TYPE=BL
CNTLUNIT CUNUMBER=0580,PATH=(21),UNIT=3088,UNITADD=((80,16)),SHARED=N,PROTOCOL=S4
IODEVICE ADDRESS=(580,16),CUNUMBER=(0580),UNIT=CTC
*************************************************************************************
* ESCON channel--CIP or CPA may be subchannel addresses D00-D0F
*************************************************************************************
CHPID    PATH=((1F)),TYPE=CNC
CNTLUNIT 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=01
CNTLUNIT CUNUMBER=0700,PATH=(1C),UNIT=3172,UNITADD=((00,16)),LINK=(C4)
IODEVICE ADDRESS=(700,16),CUNUMBER=(0700),UNIT=SCTC
 

To properly configure the channel subsystem on the router side you need to know the following information:

• Channel path, including any of the following values when applicable:

  • ESCON director output port to the mainframe

  • LPAR number

  • CUADD value

• Unit address

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:

Host A

CNTLUNIT CUNUMBER=0001, PATH=(23), LINK=1B, UNITADD=((00,64)), UNIT=SCTC, CUADD=F

Host B

CNTLUNIT CUNUMBER=0002, PATH=(29), LINK=1B, UNITADD=((00,64)), UNIT=SCTC, CUADD=A

Host C

CNTLUNIT CUNUMBER=000A, PATH=(42), UNIT=SCTC, UNITADD=((00,64))

csna 0100
 
cmpc 0100

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:

Note To avoid potential problems for those unit addresses that are originally established for use in CSNA configurations, but might later be configured for CLAW, CMPC, or CMPC+ support, it is recommended that you also disable the MIH for unit addresses that you are planning to use for CSNA. Although not required, this can prevent potential problems later on when the router environment and configurations could be changed to support a CMCC adapter feature that requires the MIH to be disabled.

This section includes the following topics:

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.

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.

Caution Using the microcode reload command as shown in step 5 forces a microcode reload on all adapters in the router and shuts down the router. Do not use this command if you are on a production network and are not prepared for a router outage.

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.
Step2	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.
Step3	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.
Step4	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: Enters global configuration mode and specifies that the CIP microcode loads from a Flash card in router slot n or from embedded Flash. Loads the image from Flash to the CIP card.
Step5	Router(config)#microcode reload	Forces a microcode reload for all adapters in the router. NoteThis command shuts down the router if you are on a live network.
Step6	Router(config)#end	Exits global configuration mode.
Step7	Router#copy running-config startup-config	Saves the running configuration as the new startup configuration in NVRAM.

CautionUsing the microcode reload command as shown in step 5 forces a microcode reload on all interfaces in the router and shuts down the router. Do not use this command if you are on a production network and are not prepared for a router outage.

To prepare the CPA, use the following commands beginning in privileged EXEC command mode:

	Command	Purpose
Step1	Router>enable	Enters the privileged EXEC mode command interpreter.
Step2	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.
Step3	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.
Step4	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.
Step5	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. NoteThese commands shut down the router if you are on a live network.
Step6	Router(config)#end	Exits global configuration mode.
Step7	Router#copy running-config startup-config	Saves the running configuration as the new startup configuration in NVRAM.

*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 Kbytes of main memory
 
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCreading 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:

	Command	Purpose
Step1	Router#show controllers cbus	Displays images loaded on the CIP card.
Step2	Router#show controllers channel slot/port	Displays the currently loaded and running microcode version for each CPA in the router.
Step3	Router#show running-config	Displays the contents of the configuration file.

NoteDo not use the show microcode command to verify the loaded microcode image. The show microcode command displays the default microcode images for the version of Cisco IOS software that you are running, which does not necessarily correspond to the image that you have loaded.

Command	Purpose
Router(config)#interface channel slot/port	Selects the interface and enters interface configuration mode. The port value differs by the type of CMCC adapter: CIP---Port value corresponds to 0 or 1 for the physical interface, and 2 for the virtual interface. CPA---Port value corresponds to port 0.

To configure the parallel data rate on the router, use the following command in interface configuration mode:

Command	Purpose
Router(config-if)#channel-protocol [s | s4]	(Optional) Defines the data transfer rate for parallel channel interfaces. The available options for this command are: s---Specifies that the parallel channel interface operates at a rate of 3 MBps, or 36864 kbps. This is the default. s4---Specifies that the parallel channel interface operates at a rate of 4.5 MBps.

Mainframe Configuration Tip

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.

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.

Command	Purpose
Router#show controllers cbus	Displays the cbus internal state for the Cisco 7000 with RSP7000 and Cisco 7500 series routers. Also included in the display is CIP-specific information such as the currently loaded microcode, currently loaded microcode application segments, and load metrics (such as CPU and memory statistics).
Router#show controllers channel [slot/port]	Displays CPA-specific information, including the currently loaded microcode.
Router#show extended channel slot/port backup [ip-address]	Displays information about CLAW and offload commands for each backup group.
Router#show extended channel slot/port cmgr [tg-name]	Displays information about the MPC+ TG connection manager.
Router#show extended channel slot/port cmpc [path [device]]	Displays information about each CMPC or CMPC+ subchannel configured on the specified CMCC adapter interface.
Router#show extended channel slot/port connection-map llc2	Displays the number of active LLC2 connections for each SAP and the mapping of the internal MAC adapter and the SAP to the resource that activated the SAP.
Router#show extended channel slot/port csna [admin | oper | stats] [path [device]]	Displays information about the CSNA subchannels configured on the specified CMCC adapter interface.
Router#show extended channel slot/port llc2 [admin | oper | stats] [lmac [lsap [rmac [rsap]]]]	Displays information about the LLC2 sessions running on the CMCC adapter interfaces.
Router#show extended channel slot/port max-llc2-sessions	Displays information about the number of LLC2 sessions supported on the CMCC adapter.
Router#show extended channel slot/port icmp-stack [ip-address]	Displays information about the ICMP stack running on the CMCC adapter interfaces.
Router#show extended channel slot/port ip-stack [ip-address]	Displays information about the IP stack running on the CMCC adapter interfaces
Router#show extended channel slot/port llc2 [admin | oper | stats] [lmac [lsap [rmac [rsap]]]]	Displays information about the LCC2 sessions running on the CMCC adapter interfaces.
Router#show extended channel slot/port packing names [path [device]]	Displays CLAW packing names and their connection state.
Router#show extended channel slot/port packing stats [path[device]]	Displays CLAW packing statistics.
Router#show extended channel slot/port statistics [path [device]] [connected]	Displays information about CMCC adapter interfaces for diagnostic purposes.
Router#show extended channel slot/port subchannel [connected]	Displays information about the CMCC adapter interfaces
Router#show extended channel slot/port tcp-connections [[loc-ip-addr [loc-port [rem-ip-addr [rem-port]] [detail | summary]	Displays information about the TCP sockets on a channel interface.
Router#show extended channel slot/port tcp-stack [ip-address]	Displays information about the TCP stack running on the CMCC adapter interfaces.
Router#show extended channel slot/port tg [oper | stats] [detailed] [tg-name]	Displays configuration, operational, and statistics information for CMPC and CMPC+ transmission groups configured on a specified CMCC adapter internal LAN interface.
Router#show extended channel slot/port tn3270-server	Displays current configuration parameters and the status of the PUs defined in each TN3270 server.
Router#show extended channel slot/port tn3270-server client-ip-address ip-address [disconnected | in-session | pending]	Displays information about all clients at a specific IP address.
Router#show extended channel slot/port tn3270-server dlur	Displays information about the SNA session switch.
Router#show extended channel slot/port tn3270-server dlurlink name	Displays information about the DLUR components.
Router#show extended channel slot/port tn3270-server nailed-ip ip-address	Displays mappings between a nailed client IP address and nailed LUs.
Router#show extended channel slot/virtual channel tn3270-server pu pu-name [cluster]	Displays information about the client LUs associated with a specified PU including the cluster layout and pool name.
Router#show extended channel slot/port tn3270-server pu pu-name lu locaddr [history]	Displays information about the TN3270 server LUs running on CMCC adapter interfaces.
Router#show extended channel slot/port udp-listeners [ip-address]	Displays information about the UDP listener sockets on the CMCC adapter interfaces.
Router#show extended channel slot/virtual channel tn3270-server response-time application [appl-name [detail]]	Displays information about each client group application for the specified VTAM appl name. List each member of the client group with its individual response-time statistics.
Router#show extended channel slot/virtual channel tn3270-server response-time global	Displays information about the global client groups.
Router#show extended channel slot/virtual/channel tn3270-server response-time link [link-name]	Displays information about the specified per-host-link client group.
Router#show extended channel slot/virtual channel tn3270-server response-time listen-point	Displays information about listen-point type client groups.
Router#show extended channel slot/virtual channel tn3270-server response-time subnet [ip-mask [detail]]	Displays information about the specified client group.
Router#show extended channel slot/port udp-stack [ip-address]	Displays information about the UDP stack running on the CMCC adapter interfaces.
Router#show interfaces channel slot/port accounting	Displays the number of packets for each protocol type that has been sent through the channel interface.
Router#show version	Displays the hardware configuration, software version, names and sources of configuration files, and boot images.

Command	Purpose
Router#clear counters [type slot/port]	Clears interface counters on the router.

NoteThis command does not clear counters retrieved using Simple Network Management Protocol (SNMP), but only those seen with the EXEC show interfaces command.

Command	Purpose
Router#clear extended counters channel slot/port [csna | icmp-stack | ip-stack | llc2 | statistics | tcp-connections | tcp-stack | tg | tn3270-server | udp-stack]	Clears counters for application features configured on CMCC adapters.

NoteThis 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]	Resets the hardware logic on an interface.

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.

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.

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.

It is recommended that you shut down a channel interface for some of the following reasons:

• For a CMCC adapter's ESCON interface, to change the interface type of a Cisco 7000 with RSP7000 or Cisco 7500 port online. To ensure that the system recognizes the new interface type, shut down the interface and then reenable it after changing the interface. Refer to your hardware documentation for more details.

• If you want to reload the router

• If, prior to reloading the microcode, you want to shut down the interface

• If you want to power off the router

• If it is recommended that a channel interface be shut down

To shut down an interface and then restart it, use the following commands in interface configuration mode:

	Command	Purpose
Step1	Router(config-if)#shutdown	Shuts down an interface.
Step2	Router(config-if)#no shutdown	Enables an interface.

	Command	Purpose
Step1	Router(config)#ip domain-name name Router(config)#ip name-server address Router(config)#ip ftp username name Router(config)#ip ftp password password	Configures the router FTP services.
Step2	Router(config)#exception slot [slot] protocol//:host/filename	Configures the CMCC adapter core dump feature.

NoteThe exception slot command is only supported on the Cisco 7000 with RSP7000 and Cisco7500 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.

NoteThe output obtained by the exception slot command can be interpreted by a qualified Cisco technical support person.

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 FastEthernet0/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