Figure 69. TCPI/P Based Management Configuration
All aspects of the 6611 Network Processor can be managed from a network management system based on a TCP/I P host. This includes those functions of the 6611 Network Processor that are not related to the TCP/I P protocol suite. For example, those aspects of the 6611 Network Processor routing function that relate to the DECnet, XNS, NetWare and AppleTalk protocol suites can all be managed from a network management system based on a TCP/I P host.
The 6611 Network Processor cannot be directly managed from a network management system based on a non-TCP/IP host. For example the 6611
Network Processor does not support the network management facilities that are part of the DECnet protocol suite, and therefore cannot be managed directly from a DECnet host using DECnet protocols.
However it is possible to indirectly manage the 6611 Network Processor from a network management system based on a non-TCP/IP host. For example the IBM NetView* Program is able to manage 6611 Network Processors indirectly via a suitable service point such as the IBM AIX NetView/6000 with the IBM AIX NetView Service Point. This is illustrated in Figure 70 on page 114.
Chapter 4. Managing the 6611 113
4.2.1 SNMP
r::::l
~ -~rotoco& 11-
Servi ceSNA
i-'~rotocohl 11-
ManagementNetwork
~
Point
~System
Figure 70. Example of Indirect Management
The capability to manage the 6611 Network Processor indirectly from the IBM NetView Program is described further in 4.2.4, "Using NetView to Manage 6611s via AIX NetView/6000" on page 131.
The TCP/IP capabilities provided by the 6611 Network Processor that can be used for management purposes are:
• SNM P Client and Agent
• TELNET Client and Server
• RLOGIN Client and Server
• REXEC Client and Server
• RSH Client and Server
• FTP Client and Server
Each of these capabilities is described in the following sections.
SNMP (Simple Network Management Protocol) is a network management protocol for networks that make use of the TCP/IP protocol suite. SNMP uses a network model that consists of three main elements:
• Managed Objects (things that can be managed)
• Agents (programs that provide an interface to the managed objects)
• Clients (network management systems)
Clients make use of agents to access the managed objects on their behalf.
Clients communicate with agents using SNMP.
This is illustrated in Figure 71 on page 115.
114 IBM 6611 Network Processor
~A
Figure 71. SNMP Network Management Model
The 6611 Network Processor provides an SNMP agent that can be used by SNMP clients to manage objects related to the 6611 Network Processor. The 6611 Network Processor also provides a limited function SNMP client that can be used through the System Manager to access the SNMP agent of the 6611 Network Processor and any other SNM P agents.
4.2.1.1 Management Information Base
Each object that can be managed via an SNMP agent is represented by one or more data values arranged in a data structure called the MIB (Management Information Base). Each data value within the MIB is called a MIB variable.
Examples of the types of MIB variables that are supported by the 6611 Network Processor SNMP agent include:
sysContact
The person responsible for this 6611 Network Processor, together with information on how to contact this person.
sysLocation
The physical location of this 6611 Network Processor. For example
"telephone closet, 3rd floor."
ibmdlsVirtualRingSegmentNumber
The token-ring segment number used in all frames passed to or from the IBM 6611 Network Processor Data Link Switching function.
A complete list of MIB variable types supported by the 6611 Network Processor SNMP agent is provided in the IBM 6611 Network Processor: Network
Management Reference.
The structure of the MIB is based on unique object identifiers, which are assigned to each type of MIB variable. Object identifiers are specified using ASN.1 (Abstract Syntax Notation One).
Note: ASN.1 is a language developed specifically for the description of data in a manner that is independent of the format used to store that data in a particular device. An understanding of ASN.1 is not necessary to make use of the 6611 Network Processor SNMP agent. However some familiarity with object
identifiers specified in ASN.1 is necessary to understand the structure of the MIB and configure the 6611 Network Processor SNMP agent.
All valid object identifiers are drawn from the object identifier namespace, which is administered by the ISO (International Organization for Standardization) and
Chapter 4. Managing the 6611 115
CCITT (Comite Consultatif International Telegraphique et Telephonique). The object identifier namespace is organized in a hierarchical tree structure. A subset of the highest levels of the object identifier namespace tree is illustrated in Figure 72.
J ~ I
ccitt iso joint-iso-ccitt
0 1 2
I ~ ~ I I I I I
org 3
'
-~ I I I
dod 6
'
-I
internet 1
Figure 72. Highest Levels in Object Identifier Namespace Tree
Nodes in the object identifier namespace tree are labeled using both a textual description and a number. These labels are assigned by the administrative authority that is responsible for the subtree to which the node belongs.
A subtree comprises all nodes beneath a particular node in the tree structure.
For example in Figure 72, the "org" node belongs to the subtree beneath the
"iso" node, but does not belong to the subtrees beneath the "ccitt" or
"joint-iso-ccitt" nodes.
At the highest levels of the object identifier namespace tree, the ISO is responsible for the subtree beneath the "iso" node. The CCITT is responsible for the subtree beneath the "ccitt" node, and they are jointly responsible for the subtree beneath the "joint-iso-ccitt" node.
The ISO has delegated the assignment of labels to the US Department of Defense for the subtree beneath the "dod" node and it, in turn, has delegated the assignment of labels to the Internet Activities Soard for the subtree beneath the" internet" node.
All object identifiers assigned to MIS variable types are drawn from the subtree that is beneath the" internet" node. A subset of that subtree is illustrated in Figure 73 on page 117.
116 IBM 6611 Network Processor