C H A P T E R 6 - Managed Object Hierarchy Software Modules

C H A P T E R 6

Managed Object Hierarchy Software Modules

This chapter provides a high-level description of the Release 2 Management Object Hierarchy (MOH) Software Modules for the Netra CT platform. It describes the software module interfaces and their major internal modules. It consists of:

Software Module Design

Software Services

Software Module MBeans

Software Modules in the SNMP View

Software Module Design

The software services in the system are monitored by software modules which are part of the Information Module layer objects.

Software services are either reliable services (such as RNFS, RBS, or CGTP) or unreliable services (such as TFTP, or NIS). The software services can be a software subsystem such as a network stack (TCP, IP, UDP); an I/O driver such as a network driver; or network processes or network daemons such as NFS.

Some software services are only available on certain CPU boards. For example, CGTP is available for both the host and the satellite CPU boards, but RBS or RNFS are only available on the host CPU board.

The software module interacts with the OS platform through Java interfaces to:

Monitor OS platform software services for software status, such as installed/not installed or configured/not configured

Monitor software service subsystems and daemons for status, such as running /not running

Provide traps and notifications for events related to the status of software services

The software module also provides APIs for management applications to configure the monitoring of software services, such as setting error thresholds, setting polling intervals, starting and stopping polling, and setting maximum retry-counts for the recovery of the daemons.

Software Services

The software modules monitor the following software services:

CGTP	RDHCP
Ethernet Interface Statistics	RNFS
NIS	SNDR
PMS	TCP, IP, UDP
Platform Management Service (PICLD on Solaris)	TFTP
RDHCP	UFS
RNFS

Software Module MBeans

This section describes the Software Module MBeans for each of the software services that the MOH Software Modules monitor. As specified by the Java Management extensions for instrumentation, all attributes and operations are explicitly listed in an MBean interface. This interface must have the same name as the class that implements it, followed by the MBean suffix. Since the interface and its implementation are usually in different files, there are two files which make up a standard MBean.

These MBeans and their public APIs provide the management interface to manage the applications. All the specific MBeans below are extended from the SoftwareServiceMbean. For more specific information, refer to the Java documents for the APIs that are distributed as part of the Netra CT MOH package. See Viewing the Netra CT Management Agent API Online for details.

SoftwareMonitorMBean

The SoftwareMonitorMBean is an object that clients can use to discover all the software services in the system. The SoftwareMonitorMBean contains the method getSoftwareServiceList() which returns the list of software services.

DaemonMBean

This class provides the name of the daemon, the state of the daemon, and the daemon recovery try count.

SoftwareServiceMBean

The SoftwareServiceMBean provides the base class from which other ServiceMBeans are extended. The SoftwareServiceMBean provides the following:

Name of the services

Status of the service (up or down)

Getting and setting polling intervals

Starting the polling

Stopping the polling

Getting and setting the number of excessive error intervals. This number is the threshold that determines if an event is sent to a client. If an error count exceeds this number, an error event is sent. There will be no more error events until the error condition disappears or a clear event is sent. For example, assume that the error threshold is set at 5% error per total transaction and the number of excessive intervals is set at 3. If the error exceeds 5% in more than 3 consecutive polling intervals, a file system error event is sent to the client.

Getting a list of DaemonMBeans that support the service, if any.

NfsServiceMBean

The NfsServiceMBean enables the client to monitor the NFS services. A client can get and set the maximum error threshold, get and set the threshold for excessive error intervals, and get the list of NFS mount failures.

UfsServiceMbean

The UfsServiceMBean enables the client to monitor the UFS services. A client can get and set the maximum threshold of the file system usage percentage, get and set the threshold for the number of excessive usage intervals, and query the list of file systems exceeding the usage threshold.

TcpServiceMBean

The TcpServiceMBean enables the client to monitor the TCP services. A client can get status and statistics for the TCP network layer, get and set intervals and thresholds for gathering the statistics, start and stop polling, and get a list of daemons supporting the service.

UdpServiceMBean

The UdpServiceMBean enables the client to monitor the UPD services. A client can get status and statistics for the UDP network layer, get and set intervals and threshold for gathering the statistics, start and stop polling, and get a list of daemons supporting the service.

IpServiceMBean

The IpServiceMBean enables the client to monitor the IP services. A client can get status and statistics for the IP network layer, get and set intervals and thresholds for gathering the statistics, start and stop polling, and get a list of daemons supporting the service.

EtherIfStatsMBean

The EtherIfStatsMbean monitors the Ethernet drivers, and monitors the interface for transmitter and receiver error counts. A client can set and get the maximum error threshold, set and get the threshold for number of excessive intervals, and query for the list of Ethernet interfaces in error.

CgtpServiceMBean

The CgtpServiceMBean enables the client to monitor the CGTP services. A client can get status and statistics for the IP network layer, list and get state of associated Ethernet physical interfaces, get and set intervals and thresholds for gathering the statistics, start and stop polling, and get a list of daemons supporting the service.

RnfsServiceMBean

The RnfsServiceMBean enables the client to monitor the RNFS services. A client can get status and statistics for the UDP network layer, get and set intervals and thresholds for gathering the statistics, start and stop polling, and get a list of daemons supporting the service.

Software Modules in the SNMP View

The SNMP view is supported through the Host Resources MIB. The SNMP client can query for the software services using the Host Resource Software Running table, and can query for the software services that are installed in the local system using the Host Resource Software Installed table.

Host Resources MIB

The Host Resources MIB is defined in RFC 2790.

Host Resources Running Software Table (hrSWRunTable)

The Host Resources Running Software Table contains information about the software that is running on the network element (for example, NFS, TFTP, and CGTP). When an application or daemon under the monitor is running, the MOH Software Module adds an entry into the hrSWRunTable and will send to the client the netraCtRunningSwCreated trap. When an application or a daemon stops running, the MOH Software Module sends the netraCtRunningSwChanged trap with hrSWRunStatus is invalid. The MOH Software Module only deletes the entry from the hrSWRunTable and sends the netraCtRunningSwDeleted trap when the service is uninstalled from the system.

Host Resources Installed Software Table (hrSWInstalledTable)

The Host Resources Installed Software Table contains information about the software installed on the network element (for example, installation packages related to NFS, CGTP, and so on). netraCtInstalledSwCreated, netraCtInstalledSwDeleted and netraCtInstalledSwChanged are traps sent to the client corresponding to the software package installed event, software package uninstalled event, and different version of the existing software package installed event.

SNMP Traps

The SNMP management software has the ability to send traps, or messages, to an application when one or more conditions have been met. Generally, a trap is an unsolicited network packet sent from an agent that usually reports some unexpected error condition.

TABLE 6-1 describes the SNMP traps found in the Netra CT SNMP MIB.

TABLE 6-1 SUN-SNMP-NETRA-CT-MIB Traps
SNMP Trap	Description
netraCtHwHighTempAlarm	Indicates that a high temperature condition has occurred on the hardware unit associated with the specified index.
netraCtHwUnitUp	Indicates that the operational state of the specified hardware unit has transitioned to up.
netraCtHwUnitDown	Indicates that the operational state of the specified hardware unit has transitioned to down.
netraCtHwUnitCreated	Indicates that the specified hardware unit has been installed at the specified location.
netraCtHwUnitDeleted	Indicates that the specified hardware unit has been removed or uninstalled from the specified location.
netraCtInstalledSwCreated	Indicates that the specified software package has been installed.
netraCtInstalledSwDeleted	Indicates that the specified software package has been removed.
netraCtRunningSwCreated	Indicates that the specified software has been started.
netraCtRunningSwDeleted	Indicates that the specified software has been stopped.

TABLE 6-2 defines the standard SNMP traps found in the RFC123-MIB.

TABLE 6-2 RFC1213-MIB Traps
SNMP Trap	Description
coldStart	Signifies that the entity, acting in an agent role, is reinitializing itself and that its configuration might have been altered.
warmStart	Signifies that the entity, acting in an agent role, is reinitializing itself such that its configuration is unaltered.
linkUp	Signifies that the entity, acting in an agent role, has detected that the ifOperStatus object for one of its communication links left the down state and transitioned into some other state (but not into the notPresent state). This other state is indicated by the included value of ifOperStatus.
linkDown	Signifies that the entity, acting in an agent role, has detected that the ifOperStatus object for one of its communication links is about to enter the down state from some other state (but not from the notPresent state). This other state is indicated by the included value of ifOperStatus.