SNMP Network Management Station Considerations
8-26
Express5800/
ftServer
: System Administrator’s Guide for the Linux Operating System
bringing the device into an Online state for fault-tolerant operations. A partnered device
on an ftServer system typically reaches a Simplex state (if its partner is missing or not
functioning) or a Duplex state. The interpretation of Duplex depends on the individual
device type, as shown in
Table 8-1
.
You can use ftlSNMP to track and log these states, and to control some operations.
See
Table 8-2
for a complete list of operational states.
SNMP Network Management Station Considerations
The ftlSNMP package provides SNMP subagents. Net-SNMP and ftlSNMP do not
provide an SNMP-capable network management station (NMS). However, you can use
a commercial or open source NMS to manage the Net-SNMP and ftlSNMP packages
remotely; you can also manage these packages directly from a remote system using
Net-SNMP. The SRA-ftLinux-MIB file must be provided on the managing host(s) and
must support the
Express Builder
release installed on the managed system(s). If
different systems use different Linux operating system releases, the SRA-ftLinux-MIB
file must reconcile differences or your SNMP NMS will not be able to manage
mismatched object IDs. The SRA-ftLinux-MIB file for a later Linux operating system
release will likely work with the earlier Linux operating system releases but may
require some adjustment for different defined objects in the
/proc
file system.
The MIBs in ASN.1 encoded text form are located in
/opt/ft/mibs
,
usr/share/snmp/mibs
, and subordinate directories by default. Note that the
SRA-ftLinux-MIB file is present in the
/opt/ft/mibs
directory and is named
SRA-ftLinux-MIB.txt.
Load all of the MIB files you require into the SNMP NMS; certainly, SRA-ftLinux-MIB
will be necessary to manage ftServer objects. Configure the SNMP NMS to avoid
verbose OID (object ID) printouts that may clutter the display. The minimum part of the
OID needs to be displayed to provide the object’s unique name.
Table 8-1. Meaning of
Duplex
for ftServer System Components
Component
Meaning of Duplex
CPU element
A partner CPU element is present and online, and the two partners are
synchronized and running in lockstep.
I/O element
A partner I/O element is present, online, and able to become primary (to
assume
active compatibility
).
I/O Device
A partner I/O device (for example, an Ethernet adapter) is present,
online, and available for failover.
Disk Drive
A partner disk drive is online, and the partitions of the two partners are
mirrored and synchronized.
