Table Of Contents
Configuration Tasks for the Host
Configure the VTAM Transport Resource List Major Node
Configure the IBM TCP/IP Stack
Configuration Tasks for the Router
Assign IP Address to Network Interface
Configure the CMPC+ Subchannels
Configure the CMPC+ Transmission Groups
CMPC+ with TCP/IP Stack Example
Stack Definition in the OE Parmlib Member for HSAS
CMPC+ with TCP/IP and HSAS Stacks
TRL Major Node for TCP/IP Stack Example
TRL Major Node for HSAS Stack Example
CMPC+ TG Using Two Interfaces Example
TRL Major Node for HSAS Stack Example
show extended channel statistics
show extended channel subchannel
Cisco Multipath Channel+
Feature Summary
CMPC+ is Cisco's implementation of IBM's MPC+ feature. The Cisco Multipath Channel+ (CMPC+) feature in Cisco IOS Release 12.0(3)T supports the MPC+ features and protocols necessary to support IP. CMPC+ enables High Performance Data Transfer (HPDT). It allows TCP/IP connections to the host through Cisco Mainframe Channel Connection (CMCC) adapters, using either the TCP/IP stack or the High Speed Access Services (HSAS) IP stack.
CMPC+ offers the following support:
•
Support for TCP/IP and HSAS Transmission Group (TG)
•
Support for one IP stack per MPC+ group
•
Support for one read subchannel and one write subchannel per CMPC+ group. The read subchannel and write subchannel in an MPC+ group can be on different physical channels.
•
Support for up to 64 KB per I/O block.
•
Runs on the Channel Interface Processor (CIP) and the the Channel Port Adapter (CPA)
Up to 64 MPC+ groups can be configured on a CMCC, depending on memory configuration. CMPC+ can coexist with CMPC, TCP/IP Offload, CLAW, TN3270, and CSNA features.
shows an MVS host with a TCP/IP stack and a Cisco router configured with CMPC+ and IP.
Figure 1 MVS Host with TCP/IP Stack and Cisco Router with CMPC+
shows a scenario where a VTAM host is configured with both HSAS and TCP/IP stacks. Each stack on the host has a TG with a read and write subchannel. The CMCC adapter can be a CIP or CPA. On the outbound flow coming from the host, the Cisco router receives the MPC+ packets from the channel, removes the MPC+ headers, and transfers the packets as IP packets to the IP cloud. The router sends the packets to the appropriate interface, depending on the destination IP address in the packet.
On the inbound flow coming from the IP cloud via LAN or WAN interfaces, the IP packets are switched from the Cisco IOS software to the CMCC adapter and MPC+ headers are added to the packets. The MPC+ block of packets is then sent to the host.
Figure 2 CMPC+ IP Structure
IP communication from one IBM host to another can also be accomplished through the same CMCC adapter. illustrates IP packets going from Host 1 to Host 2 and from Host 2 to Host 1. These packets are routed through the same Route Switch Processor (RSP) in the Cisco router.
Figure 3 IP Communication Between IBM Hosts Through the Same CMCC
illustrates IP packets flowing between host 1 and host 2. IP packets can also be sent from one host to another host using different CMCC adapters.
Figure 4 IP Communication Between IBM Hosts Using Different CMCC Adapters
illustrates IP communication flowing between host 1 and host 2. IP communication can occur between two different hosts connected through two different routers.
Figure 5 IP Communication Between Hosts Through Different Routers
illustrates IP communication between a host and different IP nodes.
Figure 6 IP Communication from a Host to IP Nodes
Benefits
The following benefits are available in CMPC+:
•
Support for HPDT
•
IP connections to hosts using MPC+
•
Coexists with CMPC, CSNA, TN3270, TCP/IP Offload, and CLAW features on a CMCC
•
ESCON and Parallel Channel support
•
ESCON Director support
•
EMIF support
List of Terms
•
Cisco Mainframe Channel Connection (CMCC)—Adapter cards (CIP or CPA) used in the Cisco 7000, 7200, and 7500 series routers for mainframe channel connections.
•
Cisco Multipath Channel (CMPC)—Cisco's implementation of IBM's MPC feature.
•
Cisco Multipath Channel+ (CMPC+)—Cisco's implementation of IBM's MPC+ feature.
•
High Performance Data Transfer (HPDT)—In VTAM, a family of functions that enhance the efficiency of large message transfers for VTAM application programs.
•
High Speed Access Services (HSAS)—IBM's high-speed TCP/IP stack that exclusively uses the efficient and strategic MPC point-to-point interface to communicate with both enterprise system connection (ESCON) network devices, and Open Systems Adapter (OSA) features.
•
Multipath Channel (MPC)—IBM channel protocol that allows a channel connection consisting of multiple read-direction and write-direction subchannels.
•
Multipath Channel+ (MPC+)—IBM channel protocol that allows channel connection consisting of multiple read-direction and write-direction subchannels that enables HPDT.
•
Transmission group (TG)—A connection between adjacent nodes.
Platforms
This feature is supported on these following platforms:
•
Router Platform Requirements
•
Cisco 7200, Cisco 7000 with RSP, and Cisco 7500 routers. These routers must have Cisco IOS Release 12.0(3)T or later, CMCC (either CIP or CPA) with a minimum of 32 MB DRAM and appropriate CMCC microcode.
•
Host Platform Requirements
•
The S/390 mainframe host is supported and the following networking software must be on the host:
OS/390 1.3 or later
ACF/VTAM 4.4 or later
The following IP stacks on the mainframe are supported:
•
TCP/IP 3.3 or later
•
HSAS
Related Publications
Mainframe-related publications include the following:
•
OS/390 TCP/IP OpenEdition Configuration Guide, SC31-8304-00
•
OS/390 TCP/IP OpenEdition Planning and Release Guide, SC31-8303-00
•
OS/390 TCP/IP OpenEdition User's Guide, GC31-8305-00
•
IP Planning and Migration Guide, SC31-8512
•
IP User's Guide, C31-8514-00
•
High Speed Access Services User's Guide, GC31-8676
•
ES/390 Principles of Operation, SA22-7201
•
VTAM Network Implementation Guide, SC31-8370-00
•
VTAM Resource Definition Reference, SC31-8377-00
•
VTAM V4R4 Resource Definition Samples, SC31-8378-00
Supported MIBs and RFCs
The following Management Information Bases (MIBs) are supported for CMPC+:
•
CISCO-CIPCMPC-MIB
•
CISCO-CIPTG-MIB
For descriptions of supported MIBs and how to use MIBs, see Cisco's MIB website on CCO at http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml
No RFCs are supported.
Configuration Tasks
This section describes the following configuration tasks for CMPC+:
•
Configuration Tasks for the Host
•
Configuration Tasks for the Router
Configuration Tasks for the Host
This section contains the following host configuration tasks:
•
Configure the VTAM Transport Resource List Major Node
Configure the VTAM Transport Resource List Major Node
The CMPC+ feature supports standard Transport Resource List (TRL) major node configurations, standard TCP Profiles and OE configuration statements. The host configuration must be coordinated with the CMPC+ configuration for IP connectivity to be successful.
Following is a sample TRL configuration:
MPCPRTL VBUILD TYPE=TRLMPCPTRLE TRLE LNCTL=MPC,MAXBFRU=16, XREAD=(246), XWRITE=(247)CMPC+ requires a unique TRLE for each CMPC+ TG.
Configure the Stacks
This section provides samples for the following tasks:
•
Configure the IBM TCP/IP Stack
Configure the IBM TCP/IP Stack
Following is an excerpt of a sample TCP/IP profile. The most important configuration commands are in bold:
DEVICE mpcptrle MPCPTPLINK MPCPIP1 MPCPTP mpcptrle;telnetparmsTIMEMARK 600PORT 23DBCSTRANSFORMendtelnetparms;ASSORTEDPARMS NOFWD ENDASSORTEDPARMS;PORT20 TCP OMVS NOAUTOLOG ; FTP Server21 TCP OMVS ; FTP Server23 TCP INTCLIEN ; TELNET Server25 TCP SMTP ; SMTP Server53 TCP NAMESRV ; Domain Name Server53 UDP NAMESRV ; Domain Name Server111 TCP OMVS ; OE Portmap Server111 UDP OMVS ; OE PORtmap Server135 UDP NCSLLBD ; NCS Location Broker161 UDP SNMPD ; SNMP Agent162 UDP SNMPQE ; OE SNMPQE Agent515 TCP LPSERVE ; LPD Server520 UDP OROUTED ; OE RouteD Server750 TCP MVSKERB ; Kerberos750 UDP MVSKERB ; Kerberos751 TCP ADM@SRV ; Kerberos Admin Server2049 UDP MVSNFS ; NFS Server3000 TCP CICSTCP ; CICS SocketHOME172.18.5.3 MPCPIP1GATEWAY172.18.5.1 = MPCPIP1 4468 HOSTDEFAULTNET 172.18.5.1 MPCPIP1 4468 0;; TRANSLATEBEGINVTAM3278-2-E NSX32702 ; 24 line screen3279-2-E NSX32702 ; 24 line screen3278-3-E NSX32703 ; 32 line screen - default of NSX32702 is 24 lines3279-3-E NSX32703 ; 32 line screen - default of NSX32702 is 24 lines3278-4-E NSX32704 ; 48 line screen - default of NSX32702 is 24 lines3279-4-E NSX32704 ; 48 line screen - default of NSX32702 is 24 lines3278-5-E NSX32705 ; 132 column screen - default of NSX32702 is 803279-5-E NSX32705 ; 132 column screen - default of NSX32702 is 80DEFAULTLUSTCP20000..TCP20999 ; allow 1000 LU-LU SESSIONS on this TCPIPENDDEFAULTLUSALLOWAPPL * ; Allow access to all applicationsUSSTCP USSTCPMF MPCPIP1ENDVTAMDATASETPREFIX TCPMVS2.TCPIP1START MPCPTRLEFor the CMCC adapter, the MTU size on the DEFAULTNET statement must be 4468 or less to ensure that the CMCC adapter does not receive packets larger than the CMCC adapter's MTU.
Configure the HSAS Stack
Following are the sample OE configuration commands for configuring and activating the HSAS stack:
oeifconfig trle host-ip-addr router-ip-addr [mtu size] [netmask netmask]oeifconfig trle [up|down|detach]oeroute [flags] [add|delete] [default|dest-ip-addr gateway-ip-addr [metric]]oenetopts [+-a [config-file-name]]For HSAS, the MTU size must be set to 4468.
Configuration Tasks for the Router
This section describes the configuration tasks associated with the CMPC+ feature.
•
Assign IP Address to Network Interface
•
Configure the CMPC+ Subchannels
•
Configure the CMPC+ Transmission Groups
Assign IP Address to Network Interface
To assign an IP address to the network interface, use the following command in interface configuration mode:
Configure the CMPC+ Subchannels
To define a CMPC+ read subchannel and CMPC+ write subchannel, use the following commands in interface configuration mode on a CMCC adapter physical interface:
Step Command Purpose1
![]()
cmpc path device tg-name read
Configure the CMPC+ read subchannel.
2
![]()
cmpc path device tg-name write
Configure the CMPC+ write subchannel.
These statements define the subchannel addresses that CMPC+ uses to connect to the host and to correspond to the definitions in the TRL major network node on the host.
Use the no cmpc path device command to remove the definition of a subchannel.
Configure the CMPC+ Transmission Groups
To define a CMPC+ TG by name, use the following command in interface configuration mode on a CIP virtual interface or a CPA physical interface:
Command Purposetg tg-name [ip | hsas-ip] host-ip-addr local-ip-addr
Define IP addresses for CMPC+ connection.
The tg command defines the name of the TG. The tg-name must match the name given in the cmpc command issued in the physical interfaces on the same CMCC adapter.
Use the no tg command to delete a CMPC+ TG from the configuration and deactivate the TG.
To change any parameter of the tg statement, the statement must be removed by using the no tg tg-name command and reentered first with new parameters.
Configuration Examples
Following are the CMPC+ configuration examples shown in this section:
•
CMPC+ with TCP/IP Stack Example
•
CMPC+ with HSAS Stack Example
•
CMPC+ with TCP/IP and HSAS Stacks
•
CMPC+ TG Using Two Interfaces Example
CMPC+ with TCP/IP Stack Example
illustrates TCP/IP link for CMPC+ between a Host and a Cisco router with a CMCC adapter. The configurations for this example follow.
Figure 7 CMPC+ IP with TCP/IP
Router
The following configuration is for the CIP in the Cisco 7500 router:
hostname ipclust1!microcode CIP flash slot0:cip27-0microcode reload!interface Channel0/1no ip addressno keepalivecmpc 0170 00 TG00 READcmpc 0170 01 TG00 WRITE!interface Channel0/2ip address 80.12.165.1 255.255.255.0no ip redirectsno ip directed-broadcastip route-cache same-interfaceno ip mroute-cacheload-interval 30no keepalivetg TG00 ip 80.12.165.2 80.12.165.1In this configuration, the CMPC+ configuration is for the TCP/IP stack on the host. The host IP address of 80.12.165.2 in the TG statement corresponds to the IP address for the TCP/IP stack in the TCP/IP profile on the host. The IP address for the CIP is 80.12.165.2.
TCP/IP Profile
The following sample shows the TCP/IP Profile on the Host:
ARPAGE 5telnetparms timemark 600 port 23 dbcstransform endtelnetparmsASSORTEDPARMS NOFWD ENDASSORTEDPARMS;DEVICE mpc4b00 MPCPTPLINK MPCPLNK2 MPCPTP mpc4b00;AUTOLOGOEFTPE3ENDAUTOLOGINCLUDE TODD.MPCP.TCPIP.PROFILES(PORTS)HOME80.12.165.2 MPCPLNK2GATEWAY; NETWORK FIRST DRIVER PACKET SUBNet mask subnet value; HOP SIZE80.12.165.1 = mpcplnk2 4468 hostDEFAULTNET 80.12.165.1 mpcplnk2 4468 0BEGINVTAM; Define logon mode tables to be the defaults shipped with the latest; level of VTAM3278-3-E NSX32703 ; 32 line screen - default of NSX32702 is 24 line screen3279-3-E NSX32703 ; 32 line screen - default of NSX32702 is 24 line screen3278-4-E NSX32704 ; 48 line screen - default of NSX32702 is 24 line screen3279-4-E NSX32704 ; 48 line screen - default of NSX32702 is 24 line screen3278-5-E NSX32705 ; 132 column screen - default of NSX32702 is 80 columns3279-5-E NSX32705 ; 132 column screen - default of NSX32702 is 80 columns; Define the LUs to be used for general usersDEFAULTAPPL ECHOMVSE; DEFAULTAPPL ECHOMVSE 10.10.1.188; DEFAULTAPPL NETTMVSEDEFAULTLUSTCPE0000..TCPE9999ENDDEFAULTLUSALLOWAPPL * ; Allow all applications that have not been previously; specified to be accessedENDVTAMDATASETPREFIX TODD.MPCPstart mpc4b00In this TCP/IP profile, the DEVICE specifies the VTAM TRLE mpc4b00 and LINK specifies the link name (MPCPLNK2) associated with the IP address (80.12.165.2) for that link. The host IP address 80.12.165.2 that is specified for the TG in the router configuration must be identical to the IP address specified for the TG in the router configuration.
TRL Major Node Example
The following sample shows the TRL major node example:
TRL4B00 VBUILD TYPE=TRLMPC4B00 TRLE LNCTL=MPC,MAXBFRU=16, XREAD=(4B00), XWRITE=(4B01)In this TRL major node example, the parameter MPC4B00 must be identical to the LINK parameter in the TCP/IP profile.
CMPC+ with HSAS Stack Example
illustrates HSAS for CMPC+ between a host and a Cisco router with a CMCC adapter. The configurations for this example follow.
Figure 8 CMPC+ IP with HSAS
Router
The following sample shows the configuration for the CIP in the Cisco 7500 router:
hostname ipclust1!microcode CIP flash slot0:cip27-0microcode reload!interface Channel0/1no ip addressno keepalivecmpc 0170 00 TG00 READcmpc 0170 01 TG00 WRITE!interface Channel0/2ip address 80.12.165.1 255.255.255.0no ip redirectsno ip directed-broadcastip route-cache same-interfaceno ip mroute-cacheload-interval 30no keepalivetg TG00 hsas-ip 80.12.165.2 80.12.165.1In this configuration, the CMPC + configuration is for the HSAS stack on the host. The IP address of 80.12.165.2 on the CIP corresponds to the HSAS IP address for the HSAS stack on the host.
Stack Definition in the OE Parmlib Member for HSAS
The following example shows the HSAS communications stack defined through the BPXPRMxy member in SYS1.PARMLIB. The most important configuration statement is shown in bold.
SYS1.PARMLIB(BPXPRMxy)..FILESYSTYPE ENTRYPOINT(BPXTCINT) TYPE(CINET)NETWORK DOMAINNAME(AF_INET) DOMAINNUMBER(2) MAXSOCKETS(11000)TYPE(CINET) INADDRANYPORT(5000) INADDRANYCOUNT(4000)SUBFILESYSTYPE NAME(TCPMVSE1) ENTRYPOINT(EZBPFINI) TYPE(CINET)DEFAULTSUBFILESYSTYPE NAME(TCPMVSE2) ENTRYPOINT(EZBPFINI) TYPE(CINET)SUBFILESYSTYPE NAME(TCPMVSE3) ENTRYPOINT(EZBPFINI) TYPE(CINET)SUBFILESYSTYPE NAME(TCPMVSE4) ENTRYPOINT(EZBPFINI) TYPE(CINET)SUBFILESYSTYPE NAME(TCPMVSE5) ENTRYPOINT(EZBPFINI) TYPE(CINET)SUBFILESYSTYPE NAME(TCPMVSE6) ENTRYPOINT(EZBPFINI) TYPE(CINET)SUBFILESYSTYPE NAME(TCPMVSE7) ENTRYPOINT(EZBPFINI) TYPE(CINET)SUBFILESYSTYPE NAME(TCPMVSE8) ENTRYPOINT(EZBPFINI) TYPE(CINET)SUBFILESYSTYPE NAME(OESTACK) ENTRYPOINT(BPXUIINT) TYPE(CINET)The OpenEdition Common INET physical file system must be defined to include the HSAS communications stack (OESTACK). Whereas other IP communications stacks require a separate address space, the HSAS communications stack resides within the OpenEdition kernel.
The SUBFILESTYPE NAME(OESTACK) statement defines the HSAS stack. This statement must be coded exactly as shown in the example and only one such statement must be coded.
HSAS Configuration Example
The following sample is the HSAS configuration on the MVS host:
oeifconfig mpc4b02 80.80.165.2 80.12.165.1 mtu 4468oeroute add default 80.12.165.1TRL Major Node Example
The following sample is the TRL major node configuration:
TRL4B02 VBUILD TYPE=TRLMPC4B02 TRLE LNCTL=MPC,MAXBFRU=16, XREAD=(4B02), XWRITE=(4B03)In this TRL major node configuration, the parameter MPC4B02 must be identical to the trle parameter in the oeifconfig configuration.
CMPC+ with TCP/IP and HSAS Stacks
illustrates CMPC+ used between a Cisco router with a CMCC adapter and a Host with both TCP/IP and HSAS stacks.
Figure 9 CMPC+ with TCP/IP and HSAS Stacks
Router
The following is the CMPC+ configuration for TCP/IP and HSAS in the CPA:
hostname ipclust2!enable secret 5 $1$2Py5$GmguUvRGwLdOj2UCi6cv71enable password lab!microcode ecpa slot0:xcpa216-0.plus110698microcode reloadip subnet-zeroip host bizarre 171.69.160.37ip domain-name cisco.comip name-server 171.69.161.21!interface Channel5/0ip address 80.80.2.1 255.255.255.0no ip directed-broadcastip route-cache same-interfaceno ip mroute-cacheload-interval 30no keepalivecmpc 0180 00 TG00 READcmpc 0180 01 TG00 WRITEcmpc 0180 02 TG02 READcmpc 0180 03 TG02 WRITEtg TG00 ip 80.80.2.2 80.80.2.1tg TG02 hsas-ip 80.80.2.3 80.80.2.1In this configuration, the cmpc configuration is for the TCP/IP and HSAS stacks on the host. The IP address of 80.80.2.2 corresponds to the IP address for the TCP/IP stack in the TCP/IP profile on the host. The IP address of 80.80.2.3 corresponds to the IP address in the HSAS stack on the host.
TRL Major Node for TCP/IP Stack Example
The following sample shows the TRL major node configuration for the TCP/IP stack:
TRL4900 VBUILD TYPE=TRLMPC4900 TRLE LNCTL=MPC,MAXBFRU=6,REPLYTO=3, xREAD=(4900),WRITE=(4901)In this TRL major node example, the parameter MPC4900 must be identical to the TRLE parameter in the LINK statement in the TCP/IP profile.
TRL Major Node for HSAS Stack Example
The following sample shows the TRL major node configuration for the HSAS stack:
TRL4902 VBUILD TYPE=TRLMPC4902 TRLE LNCTL=MPC,MAXBFRU=9,REPLYTO=3, XREAD=(4902), XWRITE=(4903)In this TRL major node example, the parameter MPC4B02 must be identical to the oeifconfig statement in the TCP/IP profile.
TCP/IP Profile
The following example shows the TCP/IP Profile on the Host:
ARPAGE 5telnetparms timemark 600 port 23 dbcstransform endtelnetparmsASSORTEDPARMS NOFWD ENDASSORTEDPARMS;DEVICE mpc4900 MPCPTPLINK MPCPLNK2 MPCPTP mpc4900;INCLUDE TODD.MPCP.TCPIP.PROFILES(PORTS)HOME80.80.2.2 MPCPLNK2GATEWAY; NETWORK FIRST DRIVER PACKET SUBNet mask subnet value; HOP SIZE80.80.2.1 = mpcplnk2 4468 hostDEFAULTNET 80.80.2.1 mpcplnk2 4468 0BEGINVTAM; Define logon mode tables to be the defaults shipped with the latest; level of VTAM3278-3-E NSX32703 ; 32 line screen - default of NSX32702 is 24 line screen3279-3-E NSX32703 ; 32 line screen - default of NSX32702 is 24 line screen3278-4-E NSX32704 ; 48 line screen - default of NSX32702 is 24 line screen3279-4-E NSX32704 ; 48 line screen - default of NSX32702 is 24 line screen3278-5-E NSX32705 ; 132 column screen - default of NSX32702 is 80 columns3279-5-E NSX32705 ; 132 column screen - default of NSX32702 is 80 columns; Define the LUs to be used for general usersDEFAULTAPPL ECHOMVSF; DEFAULTAPPL NETTMVSEDEFAULTLUSTCPF0000..TCPF9999ENDDEFAULTLUSALLOWAPPL * ; Allow all applications that have not been previously; specified to be accessedENDVTAMDATASETPREFIX TODD.MPCPSTART mpc4900In this TCP/IP profile, the DEVICE specifies the VTAM TRLE mpc4900 and LINK specifies the link name (MPCPLNK2) associated with the IP address (80.8.2.2) for that link. The IP address 80.80.2.1 must be identical to the IP address specified for the TG in the router configuration.
HSAS Stack Configuration
The following example shows the OE commands for the HSAS stack configuration:
oeifconfig mpc4902 80.80.2.3 80.80.2.1 mtu 4468oeroute add default 80.80.2.1In this configuration, mpc4902 must be identical to the TRLE parameter in the oeifconfig configuration.
CMPC+ TG Using Two Interfaces Example
illustrates CMPC+ used between a Cisco router with a CIP and a Host with split TGs.
Note
The split TG configuration is only supported on a CIP with two physical interfaces.
Figure 10 CMPC+ with Split TG
Router
The following example shows the CMPC+ router configuration for a split transmission group:
interface Channel0/0no ip addressno ip directed-broadcastno keepalivecmpc 0170 00 TG00 READ!interface Channel0/1no ip addressno ip directed-broadcastno keepalivecmpc 0170 00 TG00 WRITE!interface Channel0/2ip address 80.12.165.1 255.255.255.0no ip redirectsno ip directed-broadcastip route-cache same-interfaceno ip mroute-cacheload-interval 30no keepalivetg TG00 hsas-ip 80.12.165.2 80.12.165.1!HSAS Configuration Example
The following example shows the HSAS configuration on the Host:
oeifconfig mpcsplit 80.12.165.2 80.12.165.1 mtu 4468oeroute add default 80.12.165.1TRL Major Node for HSAS Stack Example
The following example shows the TRL major node configuration for the HSAS stack:
TRLSPLIT VBUILD TYPE=TRLMPCSPLIT TRLE LNCTL=MPC,MAXBFRU=16,REPLYTO=3, XREAD=(5200), XWRITE=(4B00)In this TRL major node example, the parameter mpcsplit must be identical to the TRLE parameter in the LINK statement within the oeifconfig statement.
Command Reference
This section documents new or modified commands. All other commands used with this feature are documented in the Cisco IOS Release 12.0 command references.
•
cmpc
•
show extended channel statistics
•
show extended channel subchannel
•
tg
cmpc
Use the cmpc interface configuration command to configure a CMPC+ read subchannel and a CMPC+ write subchannel. Use the no form of this command to remove a subchannel definition and to deactivate the transmission group.
cmpc path device tg-name {read | write}
no cmpc path deviceSyntax Description
Command Mode
Interface configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 11.3. This command supports CMPC+ in Cisco IOS Release 12.0(3)T.
Each cmpc configuration command in a CMPC+ transmission group specifies the same transmission group name. The corresponding tg command specifies the same transmission group name. Together, the cmpc and tg commands make up the transmission group specification.
The cmpc command defines the read and write subchannel addresses that CMPC+ uses to connect to the host. The command corresponds to the definitions in the TRL major node on the host. Configure the cmpc command on a CMCC adapter physical interface. Configure one read subchannel and one write subchannel. If CMPC+ is configured on a CMCC adapter with two physical interfaces, the read and write CMPC+ subchannels can be configured on separate physical interfaces.
The no cmpc command deactivates the CMPC+ subchannel and all sessions using the TG are immediately terminated.
Example
The following example configures read and write subchannels on path C020 for the CMPC+ transmission group named CONFIGE:
cmpc C020 F8 CONFIGE READcmpc C020 F9 CONFIGE WRITERelated Commands
show extended channel cmpc
show extended channel tg
show extended channel subchannel
show extended channel statisticsshow extended channel cmgr
Use the show extended channel cmgr privileged EXEC command to display information about the MPC+ TG connection manager.
show extended channel slot/port cmgr [tg-name]
Syntax Description
slot
Slot number.
port
Physical channel interface port number.
cmgr
connection manager.
tg-name
(Optional) Name of the transmission group.
Command Mode
Privileged EXEC
Usage Guidelines
This command first appeared in Cisco IOS Release 12.0(3)T.
This command is valid on the CIP's virtual channel interface or the CPA's physical channel interface.
Sample Display
The following is sample output from the show extended channel cmgr command:
Router# show extended channel 3/2 cmgrCMGR:MPCPTG2 Type=PTPLocal Group Token:0500128933 Remote Group Token :0500993355Local VC Token :0500109002 Local Conn. Token :0500109003Remote VC Token :0500201002 Remote Conn. Token :0500201002VC Status :Active Connection Status :ActiveCMGR:MPCPTG3 Type=PTPLocal Group Token:050014573 Remote Group Token :05008984300Local VC Token :0500109044 Local Conn. Token :0500109066Remote VC Token :0500201095 Remote Conn. Token :0500201088VC Status :Active Connection Status :Activedescribes the fields shown in the display.
Related Commands
cmpc
show extended channel cmgrshow extended channel cmpc
Use the show extended channel cmpc privileged EXEC command to display information about each CMPC+ subchannel configured on the specified channel interface.
show extended channel slot/port cmpc [path [device]]
Syntax Description
Command Mode
Privileged EXEC
Usage Guidelines
This command first appeared in Cisco IOS Release 11.3. This command was modified in Cisco IOS Release 12.0(3)T to include CMPC+ support.
This command is valid only on the CMCC adapter physical interfaces.
Sample Display
The following sample shows output from the show extended channel cmpc command on a
Cisco 7500 router:Router# show extended channel 3/0 cmpc c020Path Dv TGName Dir Bfrs StatusCMPC C020 46 MVS2ISRA READ 10 Active+CMPC C020 47 MVS2ISRA WRITE 16 Active+CMPC C020 4A MVS2ISR1 READ 7 ActiveCMPC C020 4B MVS2ISR1 WRITE 16 ActiveCMPC C020 4C MVS2ISR2 READ 7 ActiveCMPC C020 4D MVS2ISR2 WRITE 16 ActiveCMPC C020 4E MVS2TN READ 0 InactiveCMPC C020 4F MVS2TN WRITE 0 Inactivedescribes the fields shown in the display.
Related Commands
cmpc
show extended channel cmgrshow extended channel statistics
Use the show extended channel statistics EXEC command to display statistics about subchannels on the physical interface of a CMCC. This command displays information that is specific to the interface channel devices. The information is generally useful only for diagnostic tasks performed by technical support personnel.
show extended channel slot/port statistics [path [device-address]] [connected]
Syntax Description
Command Mode
EXEC
Usage Guidelines
This command first appeared in Cisco IOS Release 10.2.
Sample Displays
The following is sample output for the show extended channel statistics command from a CMCC adapter configured with CLAW, Offload, CSNA, and CMPC+:
tanzania#show extended channel 0/1 statisticsPath:C020 -- ESTABLISHEDCommand Selective System Device CUDev Connects Retries Cancels Reset Reset Errors Busy30 5 0 0 0 3 0 031 5 0 0 0 3 0 036 27 15 1 0 3 0 037 29 6 1 0 3 0 0Blocks Bytes Dropped Blk MemdDev-Lnk Read Write Read Write Read Write wait Con30-00 0 0 0 0 0 0 0 N31-00 0 0 0 0 0 0 0 N36-00 19 6 54236 789 0 0 0 Y37-00 9 17 801 63302 0 0 0 YPath C020Total: 28 23 55037 64091 0 0 0Path:C190 -- ESTABLISHEDCommand Selective System Device CUDev Connects Retries Cancels Reset Reset Errors Busy34 12 0 0 0 5 0 035 12 0 0 0 5 0 036 251 226 6 0 5 0 037 258 14 8 0 5 0 03E 12 0 0 0 5 0 03F 12 0 0 0 5 0 0Blocks Bytes Dropped Blk MemdDev-Lnk Read Write Read Write Read Write wait Con34-00 0 0 0 0 0 0 0 N35-00 0 0 0 0 0 0 0 N36-00 236 12 3604441 1578 0 0 0 Y37-00 18 236 1602 4217913 0 0 0 Y3E-00 0 0 0 0 0 0 0 N3F-00 0 0 0 0 0 0 0 NPath C190Total: 254 248 3606043 4219491 0 0 0Adapter CardTotal: 282 271 3661080 4283582 0 0 0Last statistics 8 seconds old, next in 2 secondstanzania#
describes the fields shown in the display.
The following is sample output using the show extended channel statistics command for the CSNA path:
Router# show extended channel 0/1 statistics E200Path: E200 -- ESTABLISHEDCommand Selective System Device CUDev Connects Retries Cancels Reset Reset Errors BusyD0 217440 108293 1 0 0 0 0D1 59530 19800 1 0 0 0 0D2 1065 252 2 0 0 0 0D3 1329 16 2 0 0 0 0D4 1066 251 2 0 0 0 0D5 887 29 2 0 0 0 0DA 1073 17 2 0 0 0 373DB 410 174 2 0 0 0 0DC 1154 14 2 0 0 0 459DD 254 17 2 0 0 0 0Blocks Bytes Dropped Blk MemdDev-Lnk Read Write Read Write Read Write wait ConD0-00 109096 109095 237799616 880468 0 0 0 YD1-00 19877 19875 160688 237876362 0 0 0 YD2-00 9 12842 801 52554701 0 0 0 YD3-00 1315 8 30378114 1052 0 0 0 YD4-00 9 12842 801 52554701 0 0 0 YD5-00 860 8 17003956 1052 0 0 0 YDA-00 687 8 14617852 1052 0 0 0 YDB-00 9 3578 801 14613989 0 0 0 YDC-00 682 8 14513604 1052 0 0 0 YDD-00 9 3594 801 14679517 0 0 0 YPath E200Total: 132553 161858 314477034 373163946 0 0 0Last statistics 3 seconds old, next in 7 seconds










