DEPNODE-MIB: View SNMP OID List / Download MIB

This entity's table of dependent secondary nodes attached to IBM SP switch networks.

Configuration information for a dependent secondary node on SP switch network.

Identifier assigned to this node in its system's administrative environment.

Relative node number assigned to this node in the SP system. Note that this is distinct from switch node number.

Opaque correlator assigned in the SP system for this node's switch connection.

Indicates whether ARP is enabled for the partition of the switch network that contains the associated dependent secondary node. NOTE: An SNMP Agent may be responsible for switch nodes in several SP system partitions, and ARP may be enabled in none, some, or all of the partitions. A value of disabled(1) indicates that ARP is not to be used to resolve network protocol addresses to switch node numbers for the switch network. Instead, the mapping of IP addresses to switch node numbers is determined via the algorithm in the description of ibmSPDepIPHostOffset. A value of enabled(2) indicates that ARP is to be used to resolve network protocol addresses to switch node numbers for the switch network. Enumeration: 'disabled': 1, 'enabled': 2.

The switch node number of the associated SP switch interface. In common networking terminology, this is the physical address for the interface on the SP switch network, and is also called the Node Device ID in the SP dependent node architecture.

The IP address for the associated SP switch interface.

The subnet mask associated with the IP address of this entry. The value of the mask is an IP address with all the network bits set to 1 and all the host bits set to 0.

The maximum number of bytes in the data portion of link-layer packets for IP datagrams on the SP switch network.

This value is the difference between switch node numbers and the host portion of the corresponding IP addresses when ARP is disabled on the SP switch network. It is the value to subtract from the host portion of an IP address to calculate the corresponding switch node number.

This value indicates the final configuration state of the corresponding SP switch interface. Enumeration: 'driverLoadFailed': 3, 'notConfigured': 1, 'fullyConfigured': 6, 'firmwareLoadFailed': 2, 'diagnosticFailed': 4, 'microcodeLoadFailed': 5.

The fully-qualified domain name of the SP system partition that contains this dependent node. This name is administratively assigned in the SP system.

This value indicates the state of the dependent node with respect to its capability to handle Switch Manager protocol via its SP switch interface. A value of nodeUp(1) indicates that the node has been reinitialized or reconfigured sufficiently to handle the Switch Manager protocol to unfence the node if it were previously fenced from the SP switch network. A value of nodeDown(2) indicates that the node is no longer able to handle Switch Manager protocol messages on the SP switch network. Enumeration: 'nodeDown': 2, 'nodeUp': 1.

The send port number for packets from the adjacent switch chip to the dependent node. The dependent node needs this value to build the packet that it sends to the adjacent switch chip to trigger that chip to reply with a clock synchronization packet.

This value is an estimate of how many clock cycles elapse before a clock synchronization packet sent from the adjacent switch chip to the dependent node results in loading of the switch time-of-day register for the node. The dependent node needs this value to build the packet that it sends to the adjacent switch chip to trigger that chip to reply with a clock synchronization packet.

This value indicates the desired state of the dependent node with respect to its capability to handle Switch Manager protocol via its SP switch interface. If the dependent node is not in the desired state, then the SNMP Agent triggers actions to change its state to the desired state. A value of up(1) indicates that the node should be initialized and configured sufficiently to handle the Switch Manager protocol. A value of down(2) indicates that the node should be reset such that it is not able to receive and handle Switch Manager protocol messages on the SP switch network. A value of reconfigure(3) indicates that the SNMP Agent must send the switchInfoNeeded trap to request new SP switch configuration information for the dependent node. This causes the SNMP Manager to send the new configuration information for the dependent node MIB objects via set-request PDU(s). Once the new values are set by the SNMP Manager, the SNMP Agent reinitializes and reconfigures the dependent node sufficiently to handle the Switch Manager protocol. Enumeration: 'down': 2, 'up': 1, 'reconfigure': 3.

A switchInfoNeeded trap signifies that the sending protocol entity needs SP switch configuration information for a dependent secondary node within the sender's configuration.

A switchConfigState trap indicates the final configuration state of a dependent secondary node's SP switch interface.

A switchNodeUp trap indicates that a dependent secondary node in the sender's configuration has just been reinitialized or reconfigured and is able to handle SP Switch Manager protocol messages.

A switchNodeDown trap indicates that a dependent secondary node in the sender's configuration is no longer able to handle Switch Manager protocol messages on the switch network.