Working with the sysGroup table

This section contains information on the sysGroup table, including the configuration file directive values, an output example of the sysGroup table and associated notes . Links to related information appear at the end of this section.

• Looking at object IDs for the configuration file directives
• Reviewing an example of System table output
• Looking at object IDs of the snmpGroup table
• Reviewing an output example of the SNMP table
• Finding related information

Looking at object IDs for the configuration file directives

The following object IDs reflect the values for the directives in the configuration file, httpd.conf:

• sysDescr - A textual description of the entity. This value should include the full name and version identification of the system hardware type, software operating system, and networking software. A textual description of the IBM HTTP Server and the Simple Network Management Protocol (SNMP) module.
• sysObjectID - The vendor's identification of the network allocated within the Structure of Management Information (SMI) enterprise subtree.
• sysUpTime - The time, in hundredths of a second, since the network management portion of the system was last reinitialized
• sysContact - The textual identification of the contact person for this person. If no contact information is known, the value is the zero-length string.
• sysLocation - An administratively assigned name for this managed node. By convention, this is the fully-qualified domain name of the node. If the name is unknown, the value is the zero-length string.
• sysServices - A value which indicates the set of services that this entity can potentially offer. The value is a sum. This sum initially takes the value zero, Then, for each layer, L, in the range 1 through 7 that this node performs transactions for, 2 raised to (L - 1) is added to the sum. For example, a node which performs only routing functions has a value of 4 (2^(3-1)). In contrast, a node which is a host offering application service has a value of 72 (2^(4-1) + 2^(7-1)).

  In the context of the Internet suite of protocols, calculate values accordingly:

Layer		Functionality
1		Physical (for example, repeaters)
2		Datalink and subnetwork (for example, bridges)
3		Internet (for example, supports IP)
4		End-to-end (for example, supports TCP)
7		Applications (for example, supports Simple Management Transport Protocol)

For systems including Open Systems Interconnection (OSI) protocols, you can also count layers 5 and 6.

Reviewing an example of System table output:

An example of System table output follows:

Looking at object IDs of the snmpGroup table

The following list provides explanations of each object ID located in the snmpGroup table:

• snmpInPkts - The total number of messages delivered to the SNMP entity from the transport service.
• snmpInBadVersions - The total number of SNMP messages delivered to the SNMP entity, for an unsupported SNMP version.
• snmpInBadCommunityNames - The total number of SNMP messages delivered to the SNMP entity which used an SNMP community name not known to said entity.
• snmpInBadCommunityUses - The total number of SNMP messages delivered to the SNMP entity which represented an SNMP operation which was not allowed by the SNMP community named in the message.
• snmpInASNParseErrs - The total number of ASN.1 or basic encoding rules (BER) errors encountered by the SNMP entity when decoding received SNMP messages.
• snmpEnableAuthenTraps - Indicates whether the SNMP entity is permitted to generate authenticationFailure traps. The value of this object overrides any configuration information; it provides a means where you can disable all authenticationFailure traps.

  It is strongly recommended that you store this object in nonvolatile memory so that it remains constant across reinitializations of the network management system.

• snmpSilentDrops - The total number of GetRequest-PDUs, GetNextRequest-PDUs, GetBulkRequest-PDUs, SetRequest-PDUs, and InformRequest-PDUs delivered to the SNMP entity that were silently dropped. The size of a reply containing an alternate Response-PDU with an empty variable-bindings field was greater than either a local constraint, or the maximum message size associated with the originator of the request.
• snmpProxyDrops - The total number of GetRequest-PDUs, GetNextRequest-PDUs, GetBulkRequest-PDUs, SetRequest-PDUs, and InformRequest-PDUs delivered to the SNMP entity that were silently dropped.

Reviewing an output example of the SNMP Table:

An output example of the SNMP table follows:

     (Back to the top)