IBM Books

Network Utility User's Guide


Chapter 15. Channel Gateway Example Configuration Details

This chapter contains diagrams and configuration parameter tables for several of the example channel gateway network configurations in Chapter 14, "Channel Gateway". The parameter values shown are from real working test configurations.

For an explanation of the columns and conventions in the configuration parameter tables, see Example Configuration Table Conventions.

The Network Utility World Wide Web pages contain binary configuration files that match these configuration parameter tables. To access these files, follow the Download link from:

http://www.networking.ibm.com/networkutility

The configurations documented in this chapter are:

Table 15-1. Cross-Reference of Example Configuration Information

Configuration Description Parameter Table
ESCON Channel Gateway Table 15-2
Parallel Channel Gateway Table 15-3
Channel Gateway (APPN and IP over MPC+) Table 15-4

Figure 15-1. ESCON Channel Gateway

View figure.

Table 15-2. ESCON Channel Gateway

See page "ESCON Channel Gateway" for a description and Figure 15-1 for a diagram of this configuration.

Configuration Program Navigation


Configuration Program Values


Command-Line Commands


Notes


Devices
Adapters
Slots


Slot 1: 2-Port TR
Slot 2: ESCON

See "add device" on next row


1


Devices
Adapters
Ports


Slot 1
Port 1: Interface 0: TR
Slot 2
Port 1: Interface 1: ESCON

Config>add dev tok
Config>add dev esc


2


Devices
Interfaces


Interface 0
MAC address: 400022AA0001

Config>net 0
TKR config>set phy 40:00:22:AA:00:01



Devices
Channel Adapters
ESCON Interfaces
ESCON Interfaces


Interface 2 (new definition)
Base Network Number: 1
Protocol Type: LSA
Maximum Data Frame: 2052
LAN Net Number: 0
(click on Add to create interface 2)

Config>net 1
ESCON Config>add lsa 
(added as interface 2)
ESCON Add Virtual>maxdata 2052
ESCON Add Virtual>net 0

(continue in same session with next row)


3,4,5


Devices
Channel Adapters
ESCON Interfaces
ESCON Subchannels


Interface 2 (highlight LSA interface)
Device Address: E4
Link Address: EF
(click on Add)

ESCON Add Virtual>subchannel add
ESCON Add LSA Subchannel>device E4
ESCON Add LSA Subchannel>link EF

(type exit twice and then list all)


6


Devices
Channel Adapters
ESCON Interfaces
ESCON Interfaces


Interface 3 (new definition)
Base Network Number: 1
Protocol Type: LCS
LAN Type: Token Ring
Maximum Data Frame: 2052
MAC Address: 400022AA0009
(click on Add to create interface 3)

Config>net 1
ESCON Config>add lcs

(added as interface 3)

ESCON Add Virtual>lantype token
ESCON Add Virtual>Maxdata 2052
ESCON Add Virtual>mac 40:00:22:AA:00:09

(continue in same session with next row)



Devices
Channel Adapters
ESCON Interfaces
ESCON Subchannels


Interface 3 (highlight LCS interface)
Device Address: E0
Link Address: EF
(click on Add)

ESCON Add Virtual>subchannel add
ESCON Config LCS Subchannel>device E0
ESCON Config LCS Subchannel>link EF

(type exit twice and then list all)


7


System
General


System name: NU_A
Location: XYZ
Contact: Administrator

Config>set host
Config>set location
Config>set contact




System
SNMP Config
General


SNMP (checked)

Config>p snmp
SNMP Config>enable snmp



System
SNMP Config
Communities
General


Community name: admin
Access type: Read-write trap
Community view: All

SNMP Config>add community
SNMP Config>set comm access write



Protocols
IP
General


Internal address: 172.128.252.1
Router ID: 172.128.1.1

Config>p ip
IP config>set internal 172.128.252.1
IP config>set router-id 172.128.1.1



Protocols
IP
Interfaces


Interface 0 (TR slot 1 port 1)
IP address: 172.128.1.1
Subnet mask: 255.255.255.0
Interface 3 (LCS interface)
IP address: 192.10.22.3
Subnet mask: 255.255.255.0

IP config>add address

(once per i/f)


8


Protocols
IP
OSPF
General


OSPF (checked)

Config>p ospf
OSPF Config>enable ospf


8


Protocols
IP
OSPF
Area Configuration
General


Area number: 0.0.0.0
Stub area (not checked)

OSPF Config>set area



Protocols
IP
OSPF
AS Boundary Routing


AS Boundary Routing
(checked to enable)
Import direct routes
(checked to enable)

OSPF config>enable as
  Import direct routes

(Accept other defaults)


9


Protocols
IP
OSPF
Interfaces


Interface 0
OSPF (checked)

OSPF Config>set interface
  Interface IP address:  172.128.1.1
  Attaches to area: 0.0.0.0

(Accept other defaults)


Notes:

  1. add dev defines a single port, not an adapter.

  2. The configuration program assigns an interface number to all ports of an adapter automatically and you delete the ones you do not want to use. From the command line, you type the add dev command for each port you want to use, and the interface number (also known as "net number") is the output of the command.

  3. When you select an interface of type LSA, the "LAN type" field is disabled (gets grayed out) and the "LAN net number" and "loopback" checkbox appears.

  4. The "LAN number" field is disabled because a value is assigned by the router automatically. This value must be configured in the host definition for "ADAPTNO".

  5. When you "Add" the interface, a new interface will be generated and it will be assigned the next available interface number.

  6. The values that you enter when configuring the subchannels must match values configured at the host. See Chapter 18, Sample Host Definitions for examples of how to match these values.

  7. When you add subchannels for an LCS virtual interface, it is only necessary to define one subchannel although LCS requires two. LCS automatically uses the next subchannel in addition to the one defined here. LCS uses the even device address (E0 in this case) as the write subchannel and the odd address (E1) as the read subchannel.

  8. You can also use RIP in place of OSPF.

  9. You need to import direct routes into OSPF from the ESCON interface because OSPF is not enabled on the ESCON interface. Instead, the subnet on the ESCON interface is imported into OSPF in the Network Utility and then propagated to the network. This is necessary to prevent error messages from occurring at the host if the Network Utility sends the OSPF updates over the LCS connection. TCP/IP at the host does not (yet) support Link State Advertisements from an OSPF router.

Figure 15-2. Parallel Channel Gateway

View figure.

Table 15-3. Parallel Channel Gateway

See page "Parallel Channel Gateway" for a description and Figure 15-2 for a diagram of this configuration.

Configuration Program Navigation


Configuration Program Values


Command-Line Commands


Notes


Devices
Adapters
Slots


Slot 1: 2-Port TR
Slot 2: Parallel Channel Adapter (PCA)

See "add device" on next row


1


Devices
Adapters
Ports


Slot 1/Port 1: Interface 0: TR
Slot 2/Port 1: Interface 1: PCA

Config>add dev tok
Config>add dev PCA


2


Devices
Interfaces


Interface 0
MAC address: 400022AA0001

Config>net 0
TKR config>set phy 40:00:22:AA:00:01



Devices
Channel Adapters
PCA Interfaces
PCA Interfaces


Interface 2 (new definition)
Base Network Number: 1
Protocol Type: LSA
LAN Net Number: 0
(click on Add to create interface 2)

Config>net 1
PCA Config>add lsa

(added as interface 2)

PCA Add Virtual>net 0

(continue in same session with next row)


3,4,5


Devices
Channel Adapters
PCA Interfaces
PCA Subchannels


Interface 2 (highlight LSA interface)
Device Address: 00
Subchannel type: read/write
(click on Add)

PCA Add Virtual>subchannel add
PCA Add LSA Subchannel>device 00

(Type exit twice and then list all)


6


Devices
Channel Adapters
PCA Interfaces
PCA Interfaces


Interface 3 (new definition)
Base Network Number: 1
Protocol Type: LCS
MAC Address: 400022AA0009
(click on Add to create interface 3)

Config>net 1
PCA Config>add lcs 
(added as interface 3):
PCA Add Virtual>mac 40:00:22:AA:00:09

(continue in same session with next row)



Devices
Channel Adapters
PCA Interfaces
PCA Subchannels


Interface 3 (highlight LCS interface)
Device Address: 02
Subchannel type: write
(click on Add)

PCA Add Virtual>subchannel add
PCA Add LCS Subchannel>device 02

(Type exit twice and then list all)


7


System
General


System name: NU_A
Location: XYZ
Contact: Administrator

Config>set host
Config>set location
Config>set contact




System
SNMP Config
General


SNMP (checked)

Config>p snmp
SNMP Config>enable snmp



System
SNMP Config
Communities
General


Community name: admin
Access type: Read-write trap
Community view: All

SNMP Config>add community
SNMP Config>set comm access write



Protocols
IP
General


Internal address: 172.128.252.1
Router ID: 172.128.1.1

Config>p ip
IP config>set internal 172.128.252.1
IP config>set router-id 172.128.1.1



Protocols
IP
Interfaces


Interface 0 (TR slot 1 port 1)
IP address: 172.128.1.1
Subnet mask: 255.255.255.0
Interface 3 (LCS interface)
IP address: 192.10.22.3
Subnet mask: 255.255.255.0

IP config>add address

(once per i/f)


8


Protocols
IP
OSPF
General


OSPF (checked)

Config>p ospf
OSPF Config>enable ospf


8


Protocols
IP
OSPF
Area Configuration
General


Area number: 0.0.0.0
Stub area (not checked)

OSPF Config>set area



Protocols
IP
OSPF
AS Boundary Routing


AS Boundary Routing
(checked to enable)
Import direct routes
(checked to enable)

OSPF Config>enable as
  Import direct routes

(Accept other defaults)


9


Protocols
IP
OSPF
Interfaces


Interface 0
OSPF (checked)

OSPF Config>set interface
  Interface IP address:  172.128.1.1
  Attaches to area: 0.0.0.0

(Accept other defaults)


Notes:

  1. add dev defines a single port, not an adapter.

  2. The configuration program assigns an interface number to all ports of an adapter automatically and you delete the ones you do not want to use. From the command line, you type the add dev command for each port you want to use, and the interface number (also known as "net number") is the output of the command.

  3. When you select an interface of type LSA, the "LAN type" field is disabled (gets grayed out) and the "LAN net number" and "loopback" checkbox appears.

  4. The "LAN number" field is disabled because a value is assigned by the router automatically. This value must be configured in the host definition for "ADAPTNO".

  5. When you "Add" the interface, a new interface will be generated and it will be assigned the next available interface number.

  6. The values that you enter when configuring the subchannels must match values configured at the host. See Chapter 18, Sample Host Definitions for examples of how to match these values.

  7. When you add subchannels for an LCS virtual interface, it is only necessary to define one subchannel although LCS requires two. LCS automatically uses the next subchannel in addition to the one defined here. LCS uses the even device address (02 in this case) as the write subchannel and the odd address (03) as the read subchannel.

  8. You can also use RIP in place of OSPF.

  9. You need to import direct routes into OSPF from the PCA interface because OSPF is not enabled on the PCA interface. Instead, the subnet on the PCA interface is imported into OSPF in the Network Utility and then propagated to the network. This is necessary to prevent error messages from occurring at the host if the Network Utility sends the OSPF updates over the LCS connection. TCP/IP at the host does not (yet) support Link State Advertisements from an OSPF router.

Network Utility provides three ways of operating the LCS interface:

The following example illustrates an LCS Passthrough configuration:

*t 6
Gateway user configuration
config>add dev esc
Device Slot #(1-8) [1] ?3
Adding ESCON Channel device in slot 3 port 1 as interface #4
Use "net 4" to configure ESCON Channel parameters
Config>net 4
ESCON Config>add lcs
ESCON Add Virtual>?
LANtype
MAC address
MAXdata
BLKtimer
ACKlen
SUBchannels
ENable 3172 Emulation
Exit
ESCON Add Virtual>enable
Enabling LCS 3172 Emulation for network 5.
Please set the Network link using the "Net" command.
ESCON Add Virtual>?
BLKtimer
ACKlen
SUBchannels
DISable 3172 Emulation
NET link
Exit
ESCON Add Virtual>net 0
ESCON Add Virtual>sub add
       
Please add or configure one subchannel for an LCS virtual interface. 
Although LCS requires two subchannels, it is only necessary to specify
one subchannel.  An adjacent subchannel will be chosen such that the
two subchannels will form a sequential pair with the write subchannel
(device address is even) before the read subchannel (device address
is odd).
ESCON Config LCS subchannel>?
LINk address (ESCD Port)
LPAR number
CU logical address
Device address
Exit
ESCON
ESCON Config LCS Subchannel>link f7
ESCON Config LCS Subchannel>lpar 0
ESCON Config LCS Subchannel>cu 0
ESCON Config LCS Subchannel>dev 20
ESCON Config LCS Subchannel>ex
ESCON Add Virtual>ex
>
ESCON Config>list
Net   5   Protocol: LCS    LAN type: Token Ring         LAN number: 0
          3172 Emulation is enabled  
          MAC address: Obtained from net 0
          Block timer:    5 ms   ACK length:    10 bytes
ESCON config>list all
Net   5   Protocol: LCS    LAN type: Token Ring         LAN number: 0
          3172 Emulation is enabled
          MAC address: Obtained from net 0
          Block timer:    5 ms   ACK length:    10 bytes
          Read Subchannels:
          Sub  0   Dev addr: 21  LPAR: 0  Link addr: F7    CU addr: 0
          Write Subchannels:
          Sub  1   Dev addr: 20  LPAR: 0  Link addr: F7    CU addr:  0
 
ESCON Config

The following example illustrates the t 5 prompt with 3172 Emulation enabled:

LCS> list all
 
LCS Virtual Adapter
LCS Information for Net 5
--- ----------- --- --- --
LAN Type: Token-Ring           LAN Number: 0
Local Read Subchannel number:  1
Local Write Subchannel number: 0
MAC Address: 08005AFE0144
LCS 3172 Emulation to net 0
Status: Down

Figure 15-3 shows how the parameters correlate between the host and the Network Utility for an LCS interface definition.

Figure 15-3. Host/Network Utility Parameter Relationships - LCS

View figure.

Notes:

  1. LCS uses a pair of subchannels, one for reading and one for writing. When configuring the subchannels used by the LCS interface, you actually need to specify only one subchannel address. LCS automatically assigns two adjacent subchannels for the LCS connection, one for the read (device address is odd) and one for the write (device address is even).

  2. The device address specified in the Network Utility LCS interface definition must be within the range specified in the UNITADD parameter in the CNTLUNIT macro from the IOCP. For example, the UNITADD parameter in Figure 15-3 shows that 32 (decimal) device addresses starting at E0 (hex) are being reserved for the Network Utility definition. A device address of E0 has been specified for the Network Utility LCS interface. The Network Utility will automatically allocate E1 also. Since E0 and E1 are in the range E0 to FF hex, this is OK as long as no other device (or interface on this Network Utility) tries to use these same subchannels.

  3. The value specified in the DEVICE statement in the host TCP/IP profile must be within the range specified in the ADDRESS parameter in the IODEVICE macro from the IOCP. For example, the DEVICE statement in the host TCP/IP profile in Figure 15-3 is 1E0 hex, which is in the range 1E0 to 1FF that the ADDRESS parameter in the IODEVICE statement specifies.

  4. The values specified for the ADDRESS parameter in the IODEVICE macro and the UNITADD parameter in the CNTLUNIT macro are related by convention only. In this example, the value for the ADDRESS parameter has been determined from the value for the UNITADD parameter by prepending a logical channel identifier (1 in this case) to the UNITADD value. This will often be the case. However, when defining the device address on the Network Utility LCS definition, use the UNITADD parameter and not the ADDRESS parameter to determine the valid range of values.

See Chapter 18, "Sample Host Definitions" for more explanation and samples of host definitions for this interface type.

For a complete look at the configuration parameters needed for this scenario, see Table 13-2.

Figure 15-4. Channel Gateway (APPN & IP over MPC+)

View figure.

Table 15-4. Channel Gateway (APPN & IP over MPC+)

See page "Channel Gateway (APPN and IP over MPC+)" for a description and Figure 15-4 for a diagram of this configuration.

Configuration Program Navigation


Configuration Program Values


Command-Line Commands


Notes


Devices
Adapters
Slots


Slot 1: 2-Port TR
Slot 2: ESCON

See "add device" on next row


1


Devices
Adapters
Ports


Slot 1/Port 1: Interface 0: TR
Slot 2/Port 1: Interface 1: ESCON

Config>add dev tok
Config>add dev esc


2


Devices
Interfaces


Interface 0
MAC address: 400022AA0001



Config>net 0
TKR config>set phy 40:00:22:AA:00:01



Devices
Channel Adapters
ESCON Interfaces
ESCON Interfaces


Interface 2 (new definition)
Base Network Number: 1
Protocol Type: MPC+
(click on Add to create interface 2)

Config>net 1
ESCON Config>add mpc

(added as interface 2)

ESCON Add Virtual>

(continue in same session with next row)


3


Devices
Channel Adapters
ESCON Interfaces
ESCON Subchannels


(highlight interface 2)
Device Address: F0
Link Address: EF
Subchannel type: Read
(click on Add to define subchannel)


Device Address: F1
Link Address: EF
Subchannel type: Write
(click on Add to define subchannel)

ESCON Add Virtual>sub addr
ESCON Add MPC+ Read Subchannel>dev f0
ESCON Add MPC+ Read Subchannel>link ef
ESCON Add MPC+ Read Subchannel>exit
ESCON Add Virtual>sub addw
ESCON Add MPC+ Write Subchannel>dev f1
ESCON Add MPC+ Write Subchannel>link ef

(type exit twice and then list all)


4


System
General


System name: NU_A
Location: XYZ
Contact: Administrator

Config>set host
Config>set location
Config>set contact



System
SNMP Config
General


SNMP (checked)

Config>p snmp
SNMP Config>enable snmp



System
SNMP Config
Communities
General


Community name: admin
Access type: Read-write trap
Community view: All

SNMP Config>add community
SNMP Config>set comm access write


5


Protocols
IP
General


Internal address: 172.128.252.1
Router ID: 172.128.1.1

Config>p ip
IP config>set internal 172.128.252.1
IP config>set router-id 172.128.1.1



Protocols
IP
Interfaces


Interface 0 (TR slot 1 port 1)
IP address: 172.128.1.1
Subnet mask: 255.255.255.0
Interface 2 (MPC+ interface)
IP address: 16.49.48.204
Subnet mask: 255.255.255.0

IP config>add address
(once per i/f)



Protocols
IP
OSPF
General


OSPF (checked)

Config>p ospf
OSPF Config>enable ospf


6


Protocols
IP
OSPF
Area Configuration
General


Area number: 0.0.0.0
Stub area (not checked)

OSPF Config>set area



Protocols
IP
OSPF
AS Boundary Routing


AS Boundary Routing
(checked to enable)
Import direct routes
(checked to enable)

OSPF Config>enable as
  Import direct routes

(Accept other defaults)


7


Protocols
IP
OSPF
Interfaces


Interface 0
OSPF (checked)

OSPF Config>set interface
  Interface IP address:  172.128.1.1
  Attaches to area: 0.0.0.0

(Accept other defaults)



Protocols
APPN
General


APPN network node (checked to enable)
Network ID: STFNET
Control point name: NUGW

Config>p appn
APPN config> set node
  Enable APPN
  Network ID: STFNET
  Control point name: NUGW

(Accept other defaults)



Protocols
APPN
Interfaces


(highlight Interface 0 Token Ring)
(click on the configure tab)
Define APPN port (checked to enable)
Port name: TR001

APPN config>add port
  APPN Port Link Type: TOKEN RING
  Port name: TR001
  Enable APPN

(Accept other defaults)




Protocols
APPN
Interfaces


(highlight Interface 0 Token Ring)
(click on the Link stations tab)
TRTG001 (new definition)
General-1 Tab:
Link station name: TRTG001
General-2 Tab:
MAC address of adjacent node:
400022AA0011
Adjacent Node Type:
APPN Network Node
(click on Add to create the Link station)

APPN config>add link
  Port name for the link station: TR001
  Station name: TRTG001
  MAC address of adjacent node: 400022AA0011

(Accept other defaults)


8


Protocols
APPN
Interfaces


(highlight Interface 2 ESCON-MPC+)
(click on the configure tab)
Define APPN port (checked to enable)
Port name: MPC001

APPN config>add port
  APPN Port Link Type: MPC
  Interface Number: 2
  Port name: MPC001
  Enable APPN

(Accept other defaults)




Protocols
APPN
Interfaces


(highlight Interface 2 ESCON-MPC+)
(click on the Link stations tab)
MPCTG001 (new definition)
General-1 Tab:
Link station name: MPCTG001
General-2 Tab:
Adjacent Node Type:
APPN Network Node
(click on Add to create the Link station)

APPN config>add link
  Port name for the link station: MPC001
  Station name: MPCTG001
  Adjacent Node Type: 0 = APPN Network Node

(Accept other defaults)



Notes:

  1. add dev defines a single port, not an adapter.

  2. The configuration program assigns an interface number to all ports of an adapter automatically and you delete the ones you do not want to use. From the command line, you type the add dev command for each port you want to use, and the interface number (also known as "net number") is the output of the command.

  3. When you "Add" the interface, a new interface will be generated and it will be assigned the next available interface number.

  4. The values that you enter when configuring the subchannels must match values configured at the host. See Chapter 18, Sample Host Definitions for examples of how to match these values.

  5. You need a write-capable SNMP community only if you want to download configuration files from the configuration program directly into the router. SNMP is not required to TFTP a configuration file to the router.

  6. You can also use RIP in place of OSPF.

  7. You need to import direct routes into OSPF from the ESCON interface because OSPF is not enabled on the ESCON interface. Instead, the subnet on the ESCON interface is imported into OSPF in the Network Utility and then propagated to the network. This is necessary to prevent error messages from occurring at the host if the Network Utility sends the OSPF updates over the MPC+ connection. TCP/IP at the host does not (yet) support Link State Advertisements from an OSPF router.

  8. The destination MAC address in this example is the local router on the right-hand side of the campus backbone in Figure 15-4. This router is also configured to be an APPN network node.


[ Top of Page | Previous Page | Next Page | Table of Contents ]