Steps for using the intranode management network (CHPID type OSM)

The intranode management network (INMN) is an IPv6 network that provides connectivity between network management applications within a zEnterprise® node. The INMN can be accessed through 1000BASE-T Ethernet OSA-Express3 or later adapters that are configured with channel path ID (CHPID) type OSM.

Before you begin

The stack must be enabled for IPv6. For information about enabling a stack for IPv6, see Steps for enabling IPv6 on a stack for access to the intranode management network.

To access the INMN, the IBM® zEnterprise 196 (z196) central processor complex (CPC) and the logical partition (LPAR) must be configured as members of an ensemble. For information about using the ENSEMBLE start option to specify that an LPAR is a member of an ensemble, see z/OS Communications Server: SNA Resource Definition Reference.

If the stack is enabled for IPv6 and the LPAR is configured as a member of an ensemble, Communications Server automatically configures, locates, and activates up to two interfaces (named EZ6OSM01 and EZ6OSM02) onto the INMN. Each of these interfaces is an IPv6 interface that has only a link-local IP address. You cannot configure static or dynamic routes over OSA-Express for Unified Resource Manager (OSM) interfaces.

The INMN is intended for only authorized applications, such as those performing platform Performance Management functions. For more information about these applications, see IBM z Systems Ensemble Planning Guide.

Procedure

Perform the following steps to use the INMN:

Authorize the application to the EZB.OSM.sysname.tcpname resource. To use IOCTL calls to retrieve information about an OSM interface or to send or receive data over an OSM interface, an application must have READ authorization to the EZB.OSM.sysname.tcpname resource. If used on this image, authorize the application to this resource.
Reserve the UDP port that the platform management application is to use to listen for multicast traffic over the INMN.
Authorize any user IDs to this resource that might issue diagnostic commands, such as Ping and Traceroute, over OSM interfaces to verify connectivity.
If you enable IP security for IPv6, you can configure a security class for IP filtering that applies to all OSM interfaces. Use the OSMSECCLASS parameter on the IPCONFIG6 statement. This enables you to configure filter rules for traffic over the EZ6OSM01 and EZ6OSM02 interfaces.
If the multicast address that is used by the platform management application is configured into a network access zone, then give the user ID for this application read permission to the resource profile for that zone.