cc/td/doc/product/software/ios121/121cgcr/ibm_c
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Configuring CMPC+

Configuring CMPC+

Cisco Multipath Channel+ (CMPC+) is Cisco's implementation of IBM's Multipath Channel+ (MPC+) feature. The CMPC+ feature in Cisco IOS Release 12.0(3)T and later supports the MPC+ features and protocols necessary to support IP. This chapter provides information about configuring CMPC+ support on the Channel Interface Processor (CIP) and Channel Port Adapter (CPA) types of Cisco Mainframe Channel Connection (CMCC) adapters on a Cisco router.

This information is described in the following sections:

For a complete description of the CMPC+ commands in this chapter, refer to the "CSNA, CMPC, and CMPC+ Commands" chapter of the Cisco IOS Bridging and IBM Networking Command Reference, Volume II. To locate documentation of other commands that appear in this chapter, use the command reference master index or search online.

Overview of CMPC+

CMPC+ enables High Performance Data Transfer (HPDT). It allows TCP/IP connections to the host through CMCC adapters, using either the TCP/IP stack or the High Speed Access Services (HSAS) IP stack.

CMPC+ offers the following support:

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.

Figure 278 shows an MVS host with a TCP/IP stack and a Cisco router configured with CMPC+ and IP.


Figure 278: MVS Host with TCP/IP Stack and Cisco Router with CMPC+


Figure 279 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 279: CMPC+ IP Structure


IP communication from one IBM host to another can also be accomplished through the same CMCC adapter. Figure 280 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 280: IP Communication Between IBM Hosts Through the Same CMCC


Figure 281 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 281: IP Communication Between IBM Hosts Using Different CMCC Adapters


Figure 282 illustrates IP communication flowing between Host 1 and Host 2. IP communication can occur between two different hosts connected through two different routers.


Figure 282: IP Communication Between Hosts Through Different Routers


Figure 283 illustrates IP communication between a host and different IP nodes.


Figure 283: IP Communication from a Host to IP Nodes


Benefits of CMPC+

CMPC+ provides the following benefits:

Preparing to Configure CMPC+

The following topics in this section provide information that is useful when you are planning to configure CMPC+ support:

Hardware and Software Requirements

This section provides information about the router and mainframe requirements to support CMPC+.

Router Requirements

The CMPC+ feature is supported on the following router platforms and requires the appropriate CMCC microcode and a minimum of 32 MB DRAM on the CMCC adapter:

You must configure the CMPC+ feature on the physical interface of a CMCC adapter. For a CIP, the physical interface is either 0 or 1. For the CPA adapters, ECPA and PCPA, the physical interface is port 0.

Mainframe Requirements

CMPC+ establishes channel connectivity to a S/390 mainframe host using the Virtual Telecommunications Access Method (VTAM) and IP stacks. The following software versions of S/390, VTAM, and IP stacks are required to configure CMPC+ on a CMCC adapter:

Operating System and VTAM Requirements

IP Stack Requirements

CMPC+ requires one of the following IP stacks on the mainframe:

Mainframe Host Configuration Considerations

Configuring CMPC+ support requires that you perform tasks for configuration of the mainframe and the router sides of the network environment.

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 CMPC+ support requires the close coordination between these job functions at a customer site.

This chapter contains information for both the network engineer and the MVS systems programmer to properly configure the network devices for CMPC+ support. The tasks for configuring CMPC+ support are organized by whether they are host-related configuration tasks or router-related configuration tasks. In addition, a topic for correlating the mainframe and router configuration is provided so that you can identify the dependencies between the host and router configuration elements and be sure that they are set up correctly.

Defining the Channel Subsystem for the Router

To establish the path and allocate the range of subchannel addresses that the CMCC adapter can use for the CMPC+ feature, you need to specify the channel subsystem definitions in the Input/Output Control Program (IOCP) or Hardware Configuration Definition (HCD).

For more information about the statements that might be defined in an IOCP file for parallel channels and ESCON channels on the CIP or CPA, see the "Defining the Channel Subsystem for the Router" section in the "Configuring Cisco Mainframe Channel Connection Adapters" chapter of this publication.

Disabling the Missing Interrupt Handler

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

For information about how to disable the MIH for the unit addresses being used for your CMCC adapter configuration, see the section "Disabling the Missing Interrupt Handler" section in the "Configuring Cisco Mainframe Channel Connection Adapters" chapter of this publication.

Related Publications

The following mainframe-related publications might be useful when configuring the mainframe to support CMPC+ on a CMCC adapter in the router:

Configuring CMPC+ Support

This section describes the configuration tasks that are required to install CMPC+ support on the mainframe and router and includes the following topics:

CMPC+ Configuration Guidelines

To configure the CMPC+ feature, you must configure the host VTAM parameters, the TCP/IP or HSAS stacks on the host, and the CMCC adapter. Consider the following guidelines as you prepare to configure CMPC+ support:

CMPC+ Host Configuration Task List

This section contains the following host configuration tasks:

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

To define the TRL, you must have two valid subchannel addresses configured in the IOCP or HCD on the host that can be used for the read and write subchannels. The read/write subchannels that you configure in the TRL should correlate with the unit addresses configured in the device argument of the cmpc commands. CMPC+ requires a unique TRLE for each CMPC+ TG.

Figure 284 shows an example of a typical TRL configuration.


Figure 284: Sample Transport Resource List Major Node 
JECTRLG VBUILD TYPE=TRL
JCTRLG74 TRLE LNCTL=MPC,                                                X
              MAXBFRU=16,                                               X
              REPLYTO=25.5,                                             X
              MPCLEVEL=NOHPDT,                                          X
              READ=(274),                                               X
              WRITE=(275)

In this example, device 274 has been configured for read and 275 has been configured for write.
Devices 274 and 275 must be available subchannels in the IOCP or HCD definition for the CMCC adapter connection.

You should activate the TRL before activating the corresponding local major node. The following example shows the command to activate a TRL, where the ID parameter specifies the name of the TRL:

v net,act,id=jectrlg,update=add
Note The argument "update=add" is preferred and is the default for later versions of VTAM. The argument "update=all" can cause inactive TRLEs to be deleted unexpectedly from ISTTRL. However, "update=all" must be used if you change an active TRL data set and want the changes to become active.

The following commands are useful for displaying the current list of TRLEs:

For details on how to configure the TRL major node, see the following IBM documents:

Configuring the Stacks

This section provides samples for the following tasks:

Configuring the IBM TCP/IP Stack

Following is an excerpt of a sample TCP/IP profile. The most important configuration commands are in bold:

    DEVICE JCTRLG74 MPCPTP
LINK JECIP1   MPCPTP JCTRLG74
;
telnetparms
  TIMEMARK 600
  PORT 23
  DBCSTRANSFORM
endtelnetparms
;
ASSORTEDPARMS NOFWD ENDASSORTEDPARMS
;
PORT
    20 TCP OMVS      NOAUTOLOG ; FTP Server
    21 TCP OMVS                ; FTP Server
    23 TCP INTCLIEN            ; TELNET Server 3.4
    25 TCP SMTP                ; SMTP Server
    53 TCP NAMESRV             ; Domain Name Server
    53 UDP NAMESRV             ; Domain Name Server
   111 TCP OMVS                ; OE Portmap Server
   111 UDP OMVS                ; OE PORtmap Server
   135 UDP NCSLLBD             ; NCS Location Broker
   161 UDP SNMPD               ; SNMP Agent
   162 UDP SNMPQE              ; OE SNMPQE Agent
   515 TCP LPSERVE             ; LPD Server
   520 UDP OROUTED             ; OE RouteD Server
   750 TCP MVSKERB             ; Kerberos
   750 UDP MVSKERB             ; Kerberos
   751 TCP ADM@SRV             ; Kerberos Admin Server
   751 UDP ADM@SRV             ; Kerberos Admin Server
  2049 UDP MVSNFS              ; NFS Server
  3000 TCP CICSTCP             ; CICS Socket
HOME
    172.18.20.51   JECIP1
GATEWAY
    172.18.20.49 = JECIP1 32000 HOST
    DEFAULTNET  172.18.20.49  JECIP1 4468 0
;
; TRANSLATE
BEGINVTAM
 3278-2-E NSX32702 ; 24 line screen
 3279-2-E NSX32702 ; 24 line screen
 3278-3-E NSX32703 ; 32 line screen - default of NSX32702 is 24 lines
 3279-3-E NSX32703 ; 32 line screen - default of NSX32702 is 24 lines
 3278-4-E NSX32704 ; 48 line screen - default of NSX32702 is 24 lines
 3279-4-E NSX32704 ; 48 line screen - default of NSX32702 is 24 lines
 3278-5-E NSX32705 ; 132 column screen - default of NSX32702 is 80
 3279-5-E NSX32705 ; 132 column screen - default of NSX32702 is 80
DEFAULTLUS
      TCP20000..TCP20999  ; allow 1000 LU-LU SESSIONS on this TCPIP
  ENDDEFAULTLUS
ALLOWAPPL * ; Allow access to all applications 
USSTCP USSTCPMG JECIP1
ENDVTAM
DATASETPREFIX TCPMVSG.TCPIP4
START JCTRLG74

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


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


 CMPC+ Router Configuration Task List


 This section describes the configuration tasks associated with the CMPC+ feature.



 Assigning an IP Address to the Network Interface


 To assign an IP address to the network interface, use the following command in interface configuration mode:


  



Command
Purpose



Router(config-if)#ip address ip-address mask 
secondary 


 Assigns an IP address to the network interface.














 Configuring the CMPC+ Subchannels


 Configuring the CMPC+ subchannels establishes the physical path between the CMCC interface and the mainframe channel. 


 To define a CMPC+ read subchannel and CMPC+ write subchannel, use the following commands beginning in global configuration mode:


  




Command
Purpose




Step1 


Router(config)#interface channel 
slot/port


 Selects the interface on which to configure CMPC. The port value differs by the type of CMCC adapter:


  • CIP---port value corresponds to the physical interface, which is port 0 or 1.
    

  • CPA---port value corresponds to port 0.
    






Step2 


Router(config-if)#cmpc path device tg-name read 


 Defines the CMPC+ read subchannel device with the following arguments:


  • path---Four-digit value that represents the channel path for the device. The path value is always 0100 for parallel channels.
    

  • device---Unit address for the device on the subchannel.
    

  • tg-name---Name of the CMPC+ transmission group, up to 8 characters.
    






Step3 


Router(config-if)#cmpc path device tg-name write 

 Defines the CMPC+ write subchannel device with the following arguments:


  • path---Four-digit value that represents the channel path for the device. The path value is always 0100 for parallel channels.
    

  • device---Unit address for the device on the subchannel. This unit address must be a different address than the unit address for the CMPC+ read subchannel.
    

  • tg-name---Name of the CMPC+ transmission group, up to eight characters. 
    















 Use the no cmpc path device command to remove the definition of a subchannel. 


 Mainframe Configuration Tips





For detailed information about how to determine the path and device values for the cmpc command, see the "Correlating Channel Configuration Parameters" section in the "Configuring Cisco Mainframe Channel Connection Adapters" chapter in this guide.





 Configuring 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
Purpose




Step1 


Router(config)#interface channel slot/port


 Selects the interface on which to configure the CMPC+ transmission group. The port value differs by the type of CMCC adapter:


  • CIP---port value corresponds to the virtual interface, which is port 2.
    

  • CPA---port value corresponds to port 0.
    






Step2 


Router(config-if)#tg tg-name [ip | hsas-ip] 
host-ip-addr local-ip-addr broadcast 


 Defines the type of IP stack and the IP addresses for the CMPC+ connection with the following arguments:


  • tg-name---Name (up to 8 characters) of the transmission group. This name must match the name specified in the cmpc commands.
    

  • ip---TCP/IP stack connection for the transmission group. 
    

  • hsas-ip---HSAS IP stack connection for the transmission group.
    

  • host-ip-addr---IP address of the channel-attached host using this transmission group. This address must match the IP address in the HOME statement of the host's TCP/IP profile, or the host address in the source-IP-address argument of the oeifconfig command for HSAS on the host.
    

  • local-ip-addr---IP address configured on the virtual interface of the CMCC adapter. This address must match the IP address for the router in the DEFAULTNET statement of the host's TCP/IP profile, or the router address in the destination-IP-address argument of the oeifconfig command for HSAS on the host.
    

  • broadcast---Routing updates enabled to the host.
    















 Use the no tg command to remove a CMPC+ transmission group from the configuration, which will deactivate the named CMPC+ transmission group. To change any parameter of the tg statement, the statement must be removed by using the no tg tg-name command.


 Router Configuration Tip



 The name that you specify for the transmission group must match the name that you specify in the tg-name argument of the cmpc commands on the physical interface of the same CMCC adapter.


 Mainframe Configuration Tips





 Correlating the Mainframe and Router Configuration


 Table 16 shows a summary of the configuration elements on the router and host that must be correlated for proper operation of CMPC+. The column labeled "Configuration Element" identifies the type of entity to be configured. The columns labeled "Router Configuration" and "Mainframe Configuration" identify the related parameters on the router and the mainframe whose values must be compatible or match.


  

Table16: Relationship of Configuration Elements for CMPC+




Configuration Element
Router Configuration
Mainframe Configuration



 Subchannels


 path and device arguments of the cmpc command


 RESOURCE PARTITION, CHPID, and CNTLUNIT statements of the IOCP definition defining the following parameters for the CMPC+ channel path:


  • LPAR number (if defined) in the RESOURCE PARTITION and CHPID statements---Specify in the 3rd digit of the path argument in the router cmpc command.
    

  • CUADD value (if defined) in the CNTLUNIT statement---Specify in the 4th digit of the path argument in the router cmpc command.
    

  • Available device address in the UNITADD parameter of the CNTLUNIT statement---Specify in the device argument of the router cmpc command.
    





 Read/write subchannels


 device argument for the cmpc read command 


 device argument for the cmpc write command 


 Subchannel for the READ parameter of the TRL major node


 Subchannel for the WRITE parameter of the TRL major node




 Host IP address


 host-ip-addr argument for the tg (CMPC+) command


  • For TCP/IP profile configuration---HOME statement
    

  • For HSAS configuration---source-IP-address argument of the oeifconfig command
    





 Router IP address


 local-ip-addr argument for the tg (CMPC+) command


  • For TCP/IP profile configuration---DEFAULTNET statement
    

  • For HSAS configuration---destination-IP-address argument of the oeifconfig command
    















 Verifying a CMPC+ Configuration Using TCP/IP

 
 Configuring CMPC+ includes tasks for both the mainframe and the router. This section describes the steps to verify that you have successfully configured CMPC+ on a CIP. It provides procedures to verify connectivity from the router perspective and from the host perspective, and includes troubleshooting tips as a guide when the configuration verification fails.


 This section includes the following topics:



 Initial Host and Router Configuration Using the TCP/IP Stack


 When using the TCP/IP stack, consider that you begin verification with the following configurations on the host and router:








NoteThe verification procedures assume that the VTAM major node is defined, but not yet activated.






Figure285: TRL Major Node Definition

JECTRLG VBUILD TYPE=TRL
JCTRLG74 TRLE LNCTL=MPC,                                                X
              MAXBFRU=16,                                               X
              REPLYTO=25.5,                                             X
              MPCLEVEL=NOHPDT,                                          X
              READ=(274),                                               X
              WRITE=(275)                                               X



Figure286: Host TCP/IP Stack Configuration in PROFILE.TCPIP

DEVICE JCTRLG74 MPCPTP
LINK JECIP1   MPCPTP JCTRLG74
;
telnetparms
  TIMEMARK 600
  PORT 23
  DBCSTRANSFORM
endtelnetparms
;
ASSORTEDPARMS NOFWD ENDASSORTEDPARMS
;
PORT
    20 TCP OMVS      NOAUTOLOG ; FTP Server
    21 TCP OMVS                ; FTP Server
    23 TCP INTCLIEN            ; TELNET Server 3.4
    25 TCP SMTP                ; SMTP Server
    53 TCP NAMESRV             ; Domain Name Server
    53 UDP NAMESRV             ; Domain Name Server
   111 TCP OMVS                ; OE Portmap Server
   111 UDP OMVS                ; OE PORtmap Server
   135 UDP NCSLLBD             ; NCS Location Broker
   161 UDP SNMPD               ; SNMP Agent
   162 UDP SNMPQE              ; OE SNMPQE Agent
   515 TCP LPSERVE             ; LPD Server
   520 UDP OROUTED             ; OE RouteD Server
   750 TCP MVSKERB             ; Kerberos
   750 UDP MVSKERB             ; Kerberos
   751 TCP ADM@SRV             ; Kerberos Admin Server
   751 UDP ADM@SRV             ; Kerberos Admin Server
  2049 UDP MVSNFS              ; NFS Server
  3000 TCP CICSTCP             ; CICS Socket
HOME
    172.18.20.51   JECIP1
GATEWAY
    172.18.20.49 = JECIP1 32000 HOST
    DEFAULTNET  172.18.20.49  JECIP1 4472 0
;
; TRANSLATE
BEGINVTAM
 3278-2-E NSX32702 ; 24 line screen
 3279-2-E NSX32702 ; 24 line screen
 3278-3-E NSX32703 ; 32 line screen - default of NSX32702 is 24 lines
 3279-3-E NSX32703 ; 32 line screen - default of NSX32702 is 24 lines
 3278-4-E NSX32704 ; 48 line screen - default of NSX32702 is 24 lines
 3279-4-E NSX32704 ; 48 line screen - default of NSX32702 is 24 lines
 3278-5-E NSX32705 ; 132 column screen - default of NSX32702 is 80
 3279-5-E NSX32705 ; 132 column screen - default of NSX32702 is 80
DEFAULTLUS
      TCP20000..TCP20999  ; allow 1000 LU-LU SESSIONS on this TCPIP
  ENDDEFAULTLUS
ALLOWAPPL * ; Allow access to all applications 
USSTCP USSTCPMG JECIP1
ENDVTAM
DATASETPREFIX TCPMVSG.TCPIP4
START JCTRLG74



Figure287: Initial Router Configuration on a CIP

interface channel 2/1
 no ip address
 no ip directed-broadcast
 no keepalive
!
interface channel 2/2
 ip address 172.18.20.49 255.255.255.248
 no ip redirects
 no ip directed-broadcast
 no keepalive
 tx-queue-limit 100






NoteThe initial router configuration shows the configuration prior to configuring the CMPC+ feature.




 Verifying CMPC+ Channel Connectivity


 If you have defined the channel paths for the router at the mainframe host in the IOCP or HCD, you can begin to configure the router for CMPC+ support and verify connectivity at the channel level first. Isolating this level of verification is useful when the VTAM configuration is not completed, but you want to establish that the router can successfully communicate with the host.


 Verifying channel connectivity confirms the following aspects of the router configuration:



 This section includes the following tasks:



 Verifying CMPC+ Channel Connectivity From the Router


 The steps in this section show how to verify the CMPC+ channel configuration beginning with configuring the cmpc commands on the router's physical interface. The following assumptions are made for the procedure described in this section:








NoteBefore you begin on the router, run the debug channel events command so that you can verify the messages on the router console.




 To verify CMPC+ channel connectivity, perform the following steps:



Step 1	 From the router, configure the cmpc commands on the physical interface according to your site's requirements as shown in the following example:


interface channel 2/1
cmpc C190 74 MVSG-TCP READ
cmpc C190 75 MVSG-TCP WRITE
 

 Confirm that you receive messages stating "Device Initialized," similar to the following displays:


PA1 MPC C190-74 Device initialized
PA1 MPC C190-75 Device initialized
 


Step 2	 Configure the CMPC+ transmission group according to your site's requirements as shown in the following example:


interface channel 2/2
tg MVSG-TCP ip 172.18.20.51 172.18.20.49
 

 Confirm that you receive a message stating that the CMPC+ transmission group is "Initialized," similar to the following display:


CMPC-TG MVSG-TCP initialized
 


Step 3	 To verify that the channel is up and the line protocol is up, go to EXEC command mode and run the show interfaces channel command as shown in the following example:


show interfaces channel 2/1
 


Step 4	 To verify that the physical channel is up, run the show extended channel statistics command as shown in the following example:


show extended channel 2/1 statistics
 

 Verify that the path field in the output for the CMPC+ devices shows "ESTABLISHED," which means that the physical channel is up.



Step 5	 If your show command output matches the values described in Step 3 and Step 4, then the channel connection between the mainframe and the router is established. If you cannot confirm the values, see the "Troubleshooting Tips for Channel Connectivity" section.





 



 Verifying CMPC+ Channel Connectivity From the Host


 After CMPC+ has been configured on the router, you can also verify channel connectivity from the host by performing the following steps:



Step 1	 From the host, verify that the devices are online using the following sample command to display the device 274 for a range of two (or 274-275):


d u,,,274,2
 


Step 2	 If the devices are offline, then vary the devices online according to your site's configuration as shown in the following sample commands:


v 274,online
v 275,online






NoteThe CHPID for the device should already be active on the host. 





Step 3	 If the devices come online, then the channel connection between the mainframe and the router is established. If the device does not come online, or you receive the message "No paths physically available," see the "Troubleshooting Tips for Channel Connectivity" section.





 



 Troubleshooting Tips for Channel Connectivity


 There are several indicators on the router and the mainframe that indicate that the channel connection is not available.



 Recommended Actions



 If you determine that the channel connection is not available, review the following tasks to be sure that you have performed them correctly:



 If none of these recommended actions allow you to establish the channel connection, check your CMCC LED indicators and the physical channel connection.


 Verifying Communication Between the Host and Router Using TCP/IP


 After the VTAM TRL major node definition is installed, the TCP/IP stack is configured, and the router is configured, you can verify communication between the host and router.


 This section includes the following verification procedures:



 Verifying Communication From the Host Using TCP/IP


 This procedure describes how to verify from the host that the VTAM TRL major node definition is configured and activated.


 To verify communication with VTAM using CMPC+, perform the following steps:



Step 1	 Activate the TRLE using the following sample command:


v net,act,id=JCTRLG74,update=add
 

 Verify that you receive the following console messages:


IST097I VARY ACCEPTED
IST093I ISTTRL ACTIVE
 


Step 2	 Display the TRL status using the following command:


d net,trl
 

 Verify that the TRLE is present but not active, as shown in the following console message:


IST1314I TRLE=JCTRLG74 STATUS=NEVAC CONTROL=MPC
 


Step 3	 Start the TCP/IP task using the following sample command:


s TCPMVSG4
 

 Verify that the TCP/IP task starts, the TRLE device and HSAS stack initializes and the interfaces are active as shown in the following console messages:


$HASP100 TCPMVSG4 ON STCINRDR
  IEF695I START TCPMVSG4 WITH JOBNAME TCPMVSG4 IS ASSIGNED TO USER
  OMVSKERN, GROUP OMVSGRP
  $HASP373 TCPMVSG4 STARTED
  IEF403I TCPMVSG4 - STARTED - TIME=11.33.21
  IEE252I MEMBER CTIEZB00 FOUND IN SYS1.OS390R7.PARMLIB
  EPW0250I EPWPITSK: FFST INITIALIZATION FOR TCP COMPLETE
  EZZ0300I OPENED PROFILE FILE DD:PROFILE
  EZZ0309I PROFILE PROCESSING BEGINNING FOR DD:PROFILE
  EZZ0316I PROFILE PROCESSING COMPLETE FOR FILE DD:PROFILE
  EZZ0334I IP FORWARDING IS DISABLED
  EZZ0335I ICMP WILL NOT IGNORE REDIRECTS
  EZZ0337I CLAWUSEDOUBLENOP IS CLEARED
  IEF196I IEF237I 0275 ALLOCATED TO TP0275
  EZZ0345I STOPONCLAWERROR IS DISABLED
  EZZ4202I OPENEDITION-TCP/IP CONNECTION ESTABLISHED FOR TCPMVSG4
  BPXF206I ROUTING INFORMATION FOR TRANSPORT DRIVER TCPMVSG4 HAS BEEN
  INITIALIZED OR UPDATED.
  IEF196I IEF237I 0274 ALLOCATED TO TP0274
  EZZ4313I INITIALIZATION COMPLETE FOR DEVICE JCTRLG74
  EZZ4324I CONNECTION TO 172.18.20.49 ACTIVE FOR DEVICE JCTRLG74
  EZB6473I TCP/IP STACK FUNCTIONS INITIALIZATION COMPLETE.
  EZAIN11I ALL TCPIP INTERFACES FOR PROC TCPMVSG4 ARE ACTIVE.
 




 



 Verifying Communication From the Router Using TCP/IP


 This procedure describes how to verify communication with the VTAM TRL major node and the TCP/IP stack from the router.


 To verify communication with VTAM from the router, perform the following steps:



Step 1	 Run the show extended channel statistics command as shown in the following example:


show extended channel 2/1 statistics
 

 Verify that the following is displayed in these fields of the output for the CMPC+ devices:




Step 2	 To verify that the CMPC+ subchannels are active, run the show extended channel cmpc command as shown in the following example:


show extended channel 2/0 cmpc
 


Step 3	 To verify the operational status and configuration of the CMPC+ transmission groups, run the show extended channel tg command as shown in the following example:


show extended channel 2/2 tg detailed MVSG-TCP
 


Step 4	 When the TCP/IP task has been started at the host, verify that you receive a message stating that the connection is activated as shown in the following example:


MVSG-TCP: Tcp/Ip Connection Activated
 


Step 5	 To confirm that you can establish a connection to the host, run the following ping command at the router console and specify the IP address that is configured in the HOME statement of the TCP/IP profile (Figure 286):


router# ping 172.18.20.51
 

 Verify that you receive a successful response to the ping command as shown in the following example:


Sending 5, 100-byte ICMP Echos to 172.18.20.51, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 12/12/12 ms
 

 For information about other commands that are useful when diagnosing or monitoring your CMPC+ connection, see the "Monitoring and Maintaining CMPC+" section. 





 



 Troubleshooting Tips from the Host Using TCP/IP


 This section describes recommended actions for the following problems that might occur during verification of communication between the host and router.


 From the host, you receive the following messages when you start the TCP/IP task:


    $HASP100 TCPMVSG4 ON STCINRDR
  IEF695I START TCPMVSG4 WITH JOBNAME TCPMVSG4 IS ASSIGNED TO USER
  OMVSKERN, GROUP OMVSGRP
  $HASP373 TCPMVSG4 STARTED
  IEF403I TCPMVSG4 - STARTED - TIME=11.40.57
  IEE252I MEMBER CTIEZB00 FOUND IN SYS1.OS390R7.PARMLIB
  EPW0250I EPWPITSK: FFST INITIALIZATION FOR TCP COMPLETE
  EZZ0300I OPENED PROFILE FILE DD:PROFILE
  EZZ0309I PROFILE PROCESSING BEGINNING FOR DD:PROFILE
  EZZ0316I PROFILE PROCESSING COMPLETE FOR FILE DD:PROFILE
  EZZ0334I IP FORWARDING IS DISABLED
  EZZ0335I ICMP WILL NOT IGNORE REDIRECTS
  EZZ4308I ERROR: CODE=80103016 DURING ACTIVATION OF DEVICE JCTRLG74.
  DIAGNOSTIC CODE: 02
  EZZ0337I CLAWUSEDOUBLENOP IS CLEARED
  EZZ0345I STOPONCLAWERROR IS DISABLED
  EZZ4202I OPENEDITION-TCP/IP CONNECTION ESTABLISHED FOR TCPMVSG4
  BPXF206I ROUTING INFORMATION FOR TRANSPORT DRIVER TCPMVSG4 HAS BEEN
  INITIALIZED OR UPDATED.
  EZB6473I TCP/IP STACK FUNCTIONS INITIALIZATION COMPLETE.
  EZAIN11I ALL TCPIP INTERFACES FOR PROC TCPMVSG4 ARE ACTIVE.
  EZZ0400I TELNET/VTAM (SECOND PASS) BEGINNING FOR FILE: DD:PROFILE
  EZZ6025I TELNET SEARCH OF USSTCPMG FAILED, RC = 00000004 RSN = 00000004
  EZZ6003I TELNET LISTENING ON PORT    23
  EZZ0403I TELNET/VTAM (SECOND PASS) COMPLETE FOR FILE: DD:PROFILE
  EZZ6027I TELNET TRANSFORM INITIALIZATION FAILED, RC: FFFF
  EZZ6028I TELNET TRANSFORM HAS ENDED

 Recommended Action



 Verify that the TRL major node is active at the host.


 Troubleshooting Tips from the Router Using TCP/IP


 This section describes recommended actions for the following problems that might occur during verification of communication between the host and router.



    Sending 5, 100-byte ICMP Echos to 172.18.20.51, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)

 Recommended Actions





    %CIP2-6-MSG: slot2 %MPC-6-CMPCP_CV_LOG: MVSG-TCP: Event/State
PRE_VcActInd/PRS_Reset
%CIP2-3-MSG: slot2 %MPC-3-CMPCP_CV_ERR2: Possible Config error:
  Rcvd Host Local IP: 172.18.20.51, Expected: 172.18.20.52

 Recommended Action





    %CIP2-6-MSG: slot2 %MPC-6-CMPCP_CV_LOG: MVSG-TCP: Event/State
PRE_VcActInd/PRS_Reset
%CIP2-3-MSG: slot2 %MPC-3-CMPCP_CV_ERR2: Possible Config error:
  Rcvd protocol: TCP/IP, Expected: HSAS/IP

 Recommended Action



 Verifying a CMPC+ Configuration Using HSAS

 
 Configuring CMPC+ includes tasks for both the mainframe and the router. This section describes the steps to verify that you have successfully configured CMPC+ on a CIP. It provides procedures to verify connectivity from the router perspective and from the host perspective, and includes troubleshooting tips as a guide when the configuration verification fails.


 This section includes the following topics:



 Initial Host and Router Configuration Using the HSAS Stack


 When using the HSAS stack, consider that you begin verification with the following configurations on the host and router:








NoteThe verification procedures assume that the VTAM major node is defined, but not yet activated.






Figure288: TRL Major Node Definition

HSASTRLG VBUILD TYPE=TRL
HSASTR72 TRLE  LNCTL=MPC,MAXBFRU=16,                                   X
               READ=(272),                                             X
               WRITE=(273)



Figure289: Initial Router Configuration on a CIP

interface Channel2/1
 no ip address
 no ip directed-broadcast
 no keepalive
!
interface Channel2/2
 ip address 172.18.20.49 255.255.255.248
 no ip redirects
 no ip directed-broadcast
 no keepalive
 tx-queue-limit 100






NoteThe initial router configuration shows the configuration prior to configuring the CMPC+ feature.




 Verifying CMPC+ Channel Connectivity


 If you have defined the channel paths for the router at the mainframe host in the IOCP or HCD, you can begin to configure the router for CMPC+ support and verify connectivity at the channel level first. Isolating this level of verification is useful when the VTAM configuration is not completed, but you want to establish that the router can successfully communicate with the host.


 Verifying channel connectivity confirms the following aspects of the router configuration:



 Verifying CMPC+ Channel Connectivity From the Router


 The steps in this section show how to verify the CMPC+ channel configuration beginning with running the cmpc command on the router's physical interface. The following assumptions are made for the procedure described in this section:








NoteBefore you begin on the router, run the debug channel events command so that you can verify the messages on the router console.




 To verify CMPC+ channel connectivity, perform the following steps:



Step 1	 From the router, configure the cmpc commands on the physical interface according to your site's requirements as shown in the following example:


interface channel 2/1
cmpc C190 72 MVSG-HSA READ
cmpc C190 73 MVSG-HSA WRITE
 

 Confirm that you receive messages stating "Device Initialized," similar to the following displays:


PA1 MPC C190-72 Device initialized
PA1 MPC C190-73 Device initialized
 


Step 2	 Configure the CMPC+ transmission group according to your site's requirements as shown in the following example:


interface channel 2/2
tg MVSG-HSA ip 172.18.20.50 172.18.20.49
 

 Confirm that you receive a message stating that the CMPC+ transmission group is "Initialized," similar to the following display:


CMPC-TG MVSG-HSA initialized
 


Step 3	 To verify that the channel is up and the line protocol is up, go to EXEC command mode and run the show interfaces channel command as shown in the following example:


show interfaces channel 2/1
 


Step 4	 To verify that the physical channel is up, run the show extended channel statistics command as shown in the following example:


show extended channel 2/1 statistics
 

 Verify that the path field in the output for the CMPC+ devices shows "ESTABLISHED," which means that the physical channel is up.



Step 5	 If your show command output matches the values described in Step 3 and Step 4, then the channel connection between the mainframe and the router is established. If you cannot confirm the values, see the "Troubleshooting Tips for Channel Connectivity" section.





 



 Verifying CMPC+ Channel Connectivity From the Host


 After CMPC+ has been configured on the router, you can also verify channel connectivity from the host by performing the following steps:



Step 1	 From the host, verify that the devices are online using the following sample command to display the device 272 for a range of two (or 272-273):


d u,,,272,2
 


Step 2	 If the devices are offline, then vary the devices online according to your site's configuration as shown in the following sample commands:


v 272,online
v 273,online






NoteThe CHPID for the device should already be active on the host. 





Step 3	 If the devices come online, then the channel connection between the mainframe and the router is established. If the device does not come online, or you receive the message "No paths physically available," see the "Troubleshooting Tips for Channel Connectivity" section.





 



 Troubleshooting Tips for Channel Connectivity


 There are several indicators on the router and the mainframe that indicate that the channel connection is not available.



 Recommended Actions



 If you determine that the channel connection is not available, review the following tasks to be sure that you have performed them correctly:



 If none of these recommended actions allow you to establish the channel connection, check your CMCC LED indicators and the physical channel connection.


 Verifying Communication Between the Host and Router Using HSAS


 After the VTAM TRL major node definition is installed and the router is configured, you can configure the HSAS stack on the host and verify communication between the host and router.


 This section includes the following verification procedures:



 Verifying Communication From the Host Using HSAS


 This procedure describes how to verify from the host that the VTAM TRL major node definition is configured and activated.


 To verify communication with VTAM using CMPC+, perform the following steps:



Step 1	 Activate the TRLE using the following sample command:


v net,act,id=HSASTR72,update=add
 

 Verify that you receive the following console messages:


IST097I VARY ACCEPTED
IST093I ISTTRL ACTIVE
 


Step 2	 Display the TRL status using the following command:


d net,trl
 

 Verify that the TRLE is present but not active, as shown in the following console message:


IST1314I TRLE=HSASTR72 STATUS=NEVAC CONTROL=MPC
 


Step 3	 From the TSO/ISPF menu at the host, enter Open Edition by typing L8.4.



Step 4	 To configure the HSAS stack on the host, type the oeifconfig command as shown in the following example:


oeifconfig hsastr72 172.18.20.50 172.18.20.49 mtu 4468
 


Step 5	 Display the HSAS configuration using the following command:


oenetstat -r
 

 Verify that you receive a display similar to the following messages:


Destination     Gateway         Flags  Refs        Use Unreach Interface
172.18.20.49    172.18.20.49    UH        0          0       0 HSASTR72
172.18.20.50    *               UHL       0          0       0 HSASTR72
127.0.0.0       *               UL        0          0       0 LO0




 



 Verifying Communication From the Router Using HSAS


 This procedure describes how to verify communication with the VTAM TRL major node and the HSAS stack from the router.


 To verify communication with VTAM from the router, perform the following steps:



Step 1	 Run the show extended channel statistics command as shown in the following example:


show extended channel 2/1 statistics
 

 Verify that the following is displayed in these fields of the output for the CMPC+ devices:




Step 2	 To verify that the CMPC+ subchannels are active, run the show extended channel cmpc command as shown in the following example:


show extended channel 2/0 cmpc
 


Step 3	 To verify the operational status and configuration of the CMPC+ transmission groups, run the show extended channel tg command as shown in the following example:


show extended channel 2/2 tg detailed MVSG-HSA
 


Step 4	 When the HSAS task is configured at the host, verify that you receive a message stating that the connection is activated as shown in the following example:


MVSG-HSA: Hsas/Ip Connection Activated
 


Step 5	 To confirm that you can establish a connection to the host, run the following ping command at the router console and specify the IP address that is configured in the oeifconfig command at the host:


router# ping 172.18.20.50
 

 Verify that you receive a successful response to the ping command as shown in the following example:


Sending 5, 100-byte ICMP Echos to 172.18.20.50, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 12/12/16 ms
 

 For information about other commands that are useful when diagnosing or monitoring your CMPC+ connection, see the "Monitoring and Maintaining CMPC+" section.





 



 Troubleshooting Tips From the Router Using HSAS


 This section describes recommended actions for the following problems that might occur during verification of communication between the host and router.



 Recommended Action





    %CIP2-6-MSG: slot2 %MPC-6-CMPCP_CV_LOG: MVSG-HSA: Event/State
PRE_VcActInd/PRS_Reset
%CIP2-3-MSG: slot2 %MPC-3-CMPCP_CV_ERR2: Possible Config error:
  Rcvd Local Addr: 172.18.20.49, Expected: 172.18.20.51

 Recommended Action



Verify that the IP address for the router in the oeifconfig command matches the local IP address that you specified in the router's tg configuration command.





    %CIP2-6-MSG: slot2 %MPC-6-CMPCP_CV_LOG: MVSG-HSA: Event/State
PRE_VcActInd/PRS_Reset
%CIP2-3-MSG: slot2 %MPC-3-CMPCP_CV_ERR2: Possible Config error:
  Rcvd protocol: HSAS/IP, Expected: TCP/IP
 

 Recommended Action



Verify that the router's tg configuration command specifies the hsas-ip protocol keyword and not ip.




 Monitoring and Maintaining CMPC+

 
 The following topics in this section provide information about the different commands that you can use to monitor and maintain the CMCC interfaces that are configured for CMPC+:



 Monitoring Interface Status


 To monitor CMCC adapter interface status, you can display information about the interface, including the version of the software and the hardware, the controller status, and statistics about the interfaces. In addition, you can display information about feature-related statistics on the CMCC adapter. This section lists some additional commands that are useful when monitoring CMCC adapter interfaces that are configured for CMPC+. 


 For a complete list of the show commands that are related to monitoring CMCC adapter interfaces, see the "Configuring Cisco Mainframe Channel Connection Adapters" chapter in this guide. To display the full list of show commands, enter show ? at the EXEC prompt.


 To display information related to CMPC+ configurations, use the following commands in EXEC mode:


  



Command
Purpose



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+ (and CMPC) subchannel configured on the specified CMCC adapter interface.




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.














 Clearing Counters for CMPC+


 You can reset the statistics counters that are displayed in the output of the show extended channel commands. You can reset the counters associated with an interface or a particular feature on the interface. If you are monitoring a particular threshold or statistic for a CMPC+ transmission group and need to reset a related counter, you can clear all those counters related to the transmission group. 


 For information about clearing other counters on the CMCC adapter interface, see the "Configuring Cisco Mainframe Channel Connection Adapters" chapter in this guide.


 To clear the transmission group counters associated with CMPC+ on the CMCC adapters, use the following command in privileged EXEC mode:


  



Command
Purpose



Router#clear extended counters channel slot/port tg 


 Clears counters for statistics associated with transmission groups in the CMPC+ (and CMPC) features on the specified slot/port. The port value differs by the type of CMCC adapter:


  • CIP---port value corresponds to the virtual interface, which is port 2.
    

  • CPA---port value corresponds to the physical interface, which is port 0.
    




















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




 Configuration Examples 

 
 Following are the CMPC+ configuration examples shown in this section:



 CMPC+ with TCP/IP Stack Example


 Figure 290 illustrates TCP/IP link for CMPC+ between a Host and a Cisco router with a CMCC adapter. The configurations for this example follow.



Figure290: 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-4
microcode reload
!
interface Channel0/1
no ip address
no keepalive
cmpc 0170 00 TG00 READ
cmpc 0170 01 TG00 WRITE
!
interface Channel0/2
ip address 80.12.165.1 255.255.255.0
no ip redirects
no ip directed-broadcast
ip route-cache same-interface
no ip mroute-cache
load-interval 30
no keepalive
 
tg TG00     ip 80.12.165.2 80.12.165.1
 

 In 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 5
telnetparms timemark 600 port 23 dbcstransform endtelnetparms
ASSORTEDPARMS NOFWD ENDASSORTEDPARMS
;
DEVICE mpc4b00  MPCPTP
LINK MPCPLNK2 MPCPTP mpc4b00
;
AUTOLOG
  OEFTPE3
ENDAUTOLOG
INCLUDE TODD.MPCP.TCPIP.PROFILES(PORTS)
HOME
  80.12.165.2   MPCPLNK2
GATEWAY
; NETWORK    FIRST     DRIVER    PACKET   SUBNet mask    subnet value
;             HOP                 SIZE
 80.12.165.1   =    mpcplnk2 4468host
DEFAULTNET 80.12.165.1 mpcplnk244680
BEGINVTAM
    ; Define logon mode tables to be the defaults shipped with the latest
    ; level of VTAM
  3278-3-E NSX32703 ; 32 line screen - default of NSX32702 is 24 line screen
  3279-3-E NSX32703 ; 32 line screen - default of NSX32702 is 24 line screen
  3278-4-E NSX32704 ; 48 line screen - default of NSX32702 is 24 line screen
  3279-4-E NSX32704 ; 48 line screen - default of NSX32702 is 24 line screen
  3278-5-E NSX32705 ; 132 column screen - default of NSX32702 is 80 columns
  3279-5-E NSX32705 ; 132 column screen - default of NSX32702 is 80 columns
    ; Define the LUs to be used for general users
  DEFAULTAPPL ECHOMVSE
; DEFAULTAPPL ECHOMVSE 10.10.1.188
; DEFAULTAPPL NETTMVSE
  DEFAULTLUS
      TCPE0000..TCPE9999
  ENDDEFAULTLUS
  ALLOWAPPL * ; Allow all applications that have not been previously
              ; specified to be accessed
ENDVTAM
DATASETPREFIX TODD.MPCP
start mpc4b00

 In 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



 The following sample shows the TRL major node example:


    TRL4B00 VBUILD TYPE=TRL
MPC4B00  TRLE  LNCTL=MPC,MAXBFRU=16,X
               READ=(4B00),X
               WRITE=(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


 Figure 291 illustrates HSAS for CMPC+ between a host and a Cisco router with a CMCC adapter. The configurations for this example follow.



Figure291: 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-4
microcode reload
!
interface Channel0/1
no ip address
no keepalive
cmpc 0170 02 TG00 READ
cmpc 0170 03 TG00 WRITE
!
interface Channel0/2
ip address 80.12.165.1 255.255.255.0
no ip redirects
no ip directed-broadcast
ip route-cache same-interface
no ip mroute-cache
load-interval 30
no keepalive
tg TG00 hsas-ip 80.12.165.2 80.12.165.1

 In 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)
     DEFAULT
SUBFILESYSTYPE 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



 The following sample is the HSAS configuration on the MVS host:


    oeifconfig mpc4b02 80.80.165.2 80.12.165.1 mtu 4468
oeroute add default 80.12.165.1

 TRL Major Node



 The following sample is the TRL major node configuration:


    TRL4B02 VBUILD TYPE=TRL
MPC4B02 TRLE  LNCTL=MPC,MAXBFRU=16,X
               READ=(4B02),X
               WRITE=(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 Example


 Figure 292 illustrates CMPC+ used between a Cisco router with a CMCC adapter and a host with both TCP/IP and HSAS stacks.



Figure292: 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$GmguUvRGwLdOj2UCi6cv71
enable password lab
!
microcode ecpa slot0:xcpa216-0.plus110698
microcode reload
ip subnet-zero
ip host bizarre 171.69.160.37
ip domain-name cisco.com
ip name-server 171.69.161.21
!
interface Channel5/0
 ip address 80.80.2.1 255.255.255.0
 no ip directed-broadcast
 ip route-cache same-interface
 no ip mroute-cache
 load-interval 30
 no keepalive
 cmpc 0180 00 TG00 READ
 cmpc 0180 01 TG00 WRITE
cmpc 0180 02 TG02 READ
 cmpc 0180 03 TG02 WRITE
 tg TG00     ip 80.80.2.2 80.80.2.1
 tg TG02     hsas-ip 80.80.2.3 80.80.2.1
 

 In 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



 The following sample shows the TRL major node configuration for the TCP/IP stack:


    TRL4900 VBUILD TYPE=TRL
MPC4900 TRLE  LNCTL=MPC,MAXBFRU=6,REPLYTO=3,x
               READ=(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



 The following sample shows the TRL major node configuration for the HSAS stack:


    TRL4902  VBUILD TYPE=TRL 
MPC4902  TRLE  LNCTL=MPC,MAXBFRU=9,REPLYTO=3,X
               READ=(4902), X
               WRITE=(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 5
telnetparms timemark 600 port 23 dbcstransform endtelnetparms
ASSORTEDPARMS NOFWD ENDASSORTEDPARMS
;
DEVICE mpc4900  MPCPTP
LINK MPCPLNK2 MPCPTP mpc4900
;
INCLUDE TODD.MPCP.TCPIP.PROFILES(PORTS)
HOME
80.80.2.2     MPCPLNK2
GATEWAY
; NETWORK    FIRST     DRIVER    PACKET   SUBNet mask    subnet value
;HOPSIZE 
 80.80.2.1=mpcplnk24468host
DEFAULTNET80.80.2.1mpcplnk244680
BEGINVTAM
; Define logon mode tables to be the defaults shipped with the latest
; level of VTAM
3278-3-E NSX32703 ; 32 line screen - default of NSX32702 is 24 line screen
3279-3-E NSX32703 ; 32 line screen - default of NSX32702 is 24 line screen
3278-4-E NSX32704 ; 48 line screen - default of NSX32702 is 24 line screen
3279-4-E NSX32704 ; 48 line screen - default of NSX32702 is 24 line screen
3278-5-E NSX32705 ; 132 column screen - default of NSX32702 is 80 columns
3279-5-E NSX32705 ; 132 column screen - default of NSX32702 is 80 columns
    ; Define the LUs to be used for general users
DEFAULTAPPL ECHOMVSF
; DEFAULTAPPL NETTMVSE
DEFAULTLUS
TCPF0000..TCPF9999
ENDDEFAULTLUS
ALLOWAPPL * ; Allow all applications that have not been previously
              ; specified to be accessed
ENDVTAM
DATASETPREFIX TODD.MPCP
 
START mpc4900

 In 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 4468
oeroute add default 80.80.2.1

 In this configuration, mpc4902 must be identical to the TRLE parameter in the oeifconfig configuration. 


 CMPC+ TG Using Two Interfaces Example


 Figure 293 illustrates CMPC+ used between a Cisco router with a CIP and a host with split TGs.







NoteThe split TG configuration is only supported on a CIP with two physical interfaces.






Figure293: CMPC+ with Split TG 

 


 Router



 The following example shows the CMPC+ router configuration for a split transmission group:


    interface Channel0/0
 no ip address
 no ip directed-broadcast
 no keepalive
 cmpc 0170 00 TG00 READ
!
interface Channel0/1
 no ip address
 no ip directed-broadcast
 no keepalive
 cmpc 0170 00 TG00 WRITE
!
interface Channel0/2
 ip address 80.12.165.1 255.255.255.0
 no ip redirects
 no ip directed-broadcast
 ip route-cache same-interface
 no ip mroute-cache
 load-interval 30
 no keepalive
 tg TG00hsas-ip 80.12.165.2 80.12.165.1
! 

 HSAS Configuration



 The following example shows the HSAS configuration on the Host:


    oeifconfig mpcsplit 80.12.165.2 80.12.165.1 mtu 4468
oeroute add default 80.12.165.1

 TRL Major Node for HSAS Stack



 The following example shows the TRL major node configuration for the HSAS stack:


    TRLSPLIT VBUILD TYPE=TRL                                                
MPCSPLIT TRLE  LNCTL=MPC,MAXBFRU=16,REPLYTO=3,X
               READ=(5200),X
               WRITE=(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. 





hometocprevnextglossaryfeedbacksearchhelp


Posted: Thu Jul 20 10:23:36 PDT 2000

Copyright 1989-2000©Cisco Systems Inc.