IBM® APPN® MIB Tables

Implementing Tables from IBM Management Information Block (MIB) gives details on implementing the tables from the IBM® APPN® management information block (MIB), as defined by RFC1593. The table defines:
  • Node Operator Facility QUERY verb used to implement each MIB table
  • Input parameter settings
  • Any filtering operations required

(The mapping between the returned parameters and the MIB tables variables can be derived from the definition of the Node Operator Facility QUERY verbs). Personal Communications or Communications Server does not currently support the ibmappnNodePortDlcTraceTable and the ibmappnLsStatusTable MIB tables.

Table 1. Implementing Tables from IBM® Management Information Block (MIB)
IBM® MIB Table Node Operator Facility Verb and MIB Table Variables Input Parameter Settings
ibmappnNodePortTable QUERY_PORT port_name ibmappnNodePortName
ibmappnNodePortIpTable (Note 1)
ibmappnNodePortDlsTable QUERY_PORT

(select entries with
dlc_type of AP_SDLC)

 port_name ibmappnNodePortDlsName
ibmappnNodePortTrTable QUERY_PORT port_name ibmappnNodePortTrName
ibmappnNodeLsTable QUERY_LS ls_name ibmappnNodeLsName
ibmappnNodeLsIpTable (Note 1)
ibmappnNodeLsDlsTable QUERY_LS

(select entries with
dlc_type of AP_SDLC)

 ls_name ibmappnNodeLsDlsName
ibmappnNodeLsTrTable QUERY_LS ls_name ibmappnNodeLsTrName
ibmappnNnTopoRouteTable QUERY_COS cos_name ibmappnNnTopoRouteCos
ibmappnNnAdjNodeTable QUERY_ADJACENT_NN adj_nncp_name ibmappnNnAdjNodeAdjName
ibmappnNnTopologyTable QUERY_NN_TOPOLOGY_NODE
node_name
ibmappnNnNodeName
node_type
AP_LEARN_ AP_LEARN_NODE

NODE

frsn
0
ibmappnNnTgTopologyTable QUERY_NN_TOPOLOGY_TG
owner
ibmappnNnTgOwner
owner_type
AP_LEARN_NODE AP_LEARN_

NODE

dest
ibmappnNnTgDest
dest_type
AP_LEARN_NODE AP_LEARN_

NODE

tg_num
ibmappnNnTgNum
frsn
0
ibmappnNnTopologyFRTable QUERY_NN_TOPOLOGY_NODE
node_name
ibmappnNnFRNode
node_type
AP_LEARN_NODE AP_LEARN_

NODE

frsn
ibmappnNnFRFrsn
ibmappnNnTgTopologyFRTable QUERY_NN_TOPOLOGY_TG
owner
ibmappnNnTgFROwner
owner_type
AP_LEARN_NODE AP_LEARN_

NODE

dest
ibmappnNnTgFRDest
dest_type
AP_LEARN_NODE AP_LEARN_

NODE

tg_num
ibmappnNnTgFRNum
frsn
ibmappnNnTgFRFrsn
ibmappnLocalTgTable QUERY_LOCAL_TOPOLOGY
dest
ibmappnLocalTGDest
dest_type
AP_LEARN_NODE AP_LEARN_

NODE

tg_num
ibmappnLocalTgNum
ibmappnLocalEnTable QUERY_LOCAL_TOPOLOGY

(select entries with
unique dest) (Note 2)
dest
ibmappnLocalEnName
dest_type
AP_END_NODE
dest_type
AP_LEARN_NODE AP_LEARN_

NODE

ibmappnLocalEnTgTable QUERY_LOCAL_TOPOLOGY (Note 3)
dest
ibmappnLocalEnTgOrigin
dest_type
AP_LEARN_NODE AP_LEARN_

NODE

tg_num
ibmappnLocalEnTgNum
ibmappnDirTable QUERY_DIRECTORY_LU lu_name ibmappnDirLuName
ibmappnCosModeTable QUERY_MODE_TO_COS_MAPPING mode_name ibmappnCosModeName
ibmappnCosNameTable QUERY_COS cos_name ibmappnCosName
Note:
  1. Personal Communications or Communications Server does not support IP as a DLC type.
  2. Entries with the same dest are ordered consecutively by QUERY_LOCAL_TOPOLOGY.
  3. The ibmappnLocalEnTgTable views TGs from the attached end node's perspective (that is, as a TG from the end node). However, a network node compliant with the current level of the APPN® architecture only stores end node TG information for TGs between itself and directly attached end nodes. Therefore all the entries in this table have ibmappnLocalEnTgDest set to the name of the local node (ibmappnNodeCpName).