snmp reference manual for solaris - fujitsu€¦ · reference manual for solaris redakteur fujitsu...
TRANSCRIPT
© S
iem
ens
Nix
dorf
Info
rmat
ion
ssys
tem
e A
G 1
997
Pfa
d: C
:\Doc
umen
ts a
nd
Set
tings
\who
dgso
n\M
y D
ocum
ent
s\w
ork
ing\
SN
MP
_May
_02
\snm
p.vo
r
Produktfamilie
PRIMECLUSTER™
SNMPReference Manual for Solaris
RedakteurFujitsu Siemens Computers GmbH München81730 Muniche-mail: email: [email protected].: (089) 636-00000Fax: (++49) 700 / 372 00000U42127-J-Z100-2-76Sprachen: En
Edition May 2002
© S
iem
ens
Nix
dorf
Info
rmat
ion
ssys
tem
e A
G 1
997
Pfa
d: C
:\Doc
umen
ts a
nd
Set
tings
\who
dgso
n\M
y D
ocum
ent
s\w
ork
ing\
SN
MP
_May
_02
\snm
p.vo
r
Comments… Suggestions… Corrections…The User Documentation Department would like to know your opinion on this manual. Your feedback helps us to optimize our documentation to suit your individual needs.
Fax forms for sending us your comments are included at the back of the manual.
There you will also find the addresses of the relevant User Documentation Department.
Copyright and Trademarks
Copyright © 2000, 2001, 2002 Fujitsu Siemens Computers Inc. and Fujitsu LIMITED.
All rights reserved.Delivery subject to availability; right of technical modifications reserved.
All hardware and software names used are trademarks of their respective manufacturers.
This manual was produced bycognitas. Gesellschaft für Technik-Dokumentation mbHwww.cognitas.de
This manual is printed on paper treated with chlorine-free bleach.
© S
iem
ens
Nix
dor
f In
form
atio
nssy
ste
me
AG
19
95
Pfa
d: C
:\Doc
ume
nts
and
Set
ting
s\w
hod
gson
\My
Do
cum
ents
\wor
king
\SN
MP
_M
ay_0
2\sn
mp.
ivz
Contents1 Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1 Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.2 Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.2.1 Notation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.2.1.1 Prompts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.2.1.2 Manual page section numbers . . . . . . . . . . . . . . . . . . . 21.2.1.3 The keyboard . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.2.1.4 Typefaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.2.1.5 Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.2.1.6 Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.2.2 Command syntax . . . . . . . . . . . . . . . . . . . . . . . . . 31.3 Important . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3 Subagents . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73.1 ClusterView subagent . . . . . . . . . . . . . . . . . . . . . . . 73.2 Cluster Foundation subagent . . . . . . . . . . . . . . . . . . . 83.3 Scalable Internet Services subagent . . . . . . . . . . . . . . . 83.4 Reliant Monitor Services subagent . . . . . . . . . . . . . . . . 8
4 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94.2 Installing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94.2.1 Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94.2.2 .dat files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
5 Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
6 MIBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
U42127-J-Z100-2-76
Contents
U42127-J-Z100-2-76
© S
iem
ens
Nix
dorf
Info
rma
tions
syst
em
e A
G 1
997
Pfa
d: C
:\Doc
ume
nts
and
Set
tings
\wh
odg
son\
My
Doc
ume
nts\
wor
kin
g\S
NM
P_
May
_02\
snm
p.k0
1
1 PrefaceThis manual is for the PRIMECLUSTER SNMP product. This manual is intended for developers, system administrators, and support personnel.
1.1 Documentation
The documentation listed in this section contains information relevant to PRIMECLUSTER and can be ordered through your Fujitsu Siemens sales representative.
In addition to this manual, the following manuals are also available for PRIMECLUSTER:
● Installation Guide—Provides instructions for installing PRIMECLUSTER.
● Cluster Foundation Configuration and Administration—Provides instructions for configuring and administering the PRIMECLUSTER Cluster Foundation.
● RMS Configuration and Administration—Provides instructions for writing configuration files and scripts, writing custom (generic) files for special resources, and administering RMS.
● Scalable Internet Services Configuration and Administration—Provides infor-mation on configuring and administering SIS.
● Release Notice—Available on the PRIMECLUSTER CD-ROM by means of start.html. This document contains the latest information at the time of the product release.
● readme for Emanate—Available on the Control CD-ROM, which contains the Emanate product. This document contains the latest information at the time of release.
U42127-J-Z100-2-76 1
Conventions Preface
1.2 Conventions
To standardize the presentation of material, this manual uses a number of notational, typographical, and syntactical conventions.
1.2.1 Notation
This manual uses the following notational conventions.
1.2.1.1 Prompts
Command line examples that require system administrator (or root) rights to execute are preceded by the system administrator prompt, the hash sign (#). Entries that do not require system administrator rights are preceded by a dollar sign ($).
1.2.1.2 Manual page section numbers
References to the operating system commands are followed by their manual page section numbers in parentheses for example, cp(1).
1.2.1.3 The keyboard
Keystrokes that represent nonprintable characters are displayed as key icons such as [Enter] or [F1]. For example, [Enter] means press the key labeled Enter; [Ctrl-b] means hold down the key labeled Ctrl or Control and then press the [B] key.
1.2.1.4 Typefaces
The following typefaces highlight specific elements in this manual.
Typeface Usage
Constant Width
Computer output and program listings; commands, file names, manual page names and other literal programming elements in the main body of text.
Italic Variables that you must replace with an actual value.
Bold Items in a command line that you must type exactly as shown.
2 U42127-J-Z100-2-76
Preface Conventions
© S
iem
ens
Nix
dorf
Info
rma
tions
syst
em
e A
G 1
997
Pfa
d: C
:\Doc
ume
nts
and
Set
tings
\wh
odg
son\
My
Doc
ume
nts\
wor
kin
g\S
NM
P_
May
_02\
snm
p.k0
1
Typeface conventions are shown in the following examples.
1.2.1.5 Example 1
Several entries from an /etc/passwd file are shown below:
root:x:0:1:0000-Admin(0000):/:sysadm:x:0:0:System Admin.:/usr/admin:/usr/sbin/sysadmsetup:x:0:0:System Setup:/usr/admin:/usr/sbin/setupdaemon:x:1:1:0000-Admin(0000):/:
1.2.1.6 Example 2
To use the cat(1) command to display the contents of a file, enter the following command line:
$cat file
1.2.2 Command syntax
The command syntax observes the following conventions.
Symbol Name Meaning
[ ] Brackets Enclose an optional item.
{ } Braces Enclose two or more items of which only one is used. The items are separated from each other by a vertical bar (|).
| Vertical bar When enclosed in braces, it separates items of which only one is used. When not enclosed in braces, it is a literal element indicating that the output of one program is piped to the input of another.
( ) Parentheses Enclose items that must be grouped together when repeated.
... Ellipsis Signifies an item that may be repeated. If a group of items can be repeated, the group is enclosed in parentheses.
U42127-J-Z100-2-76 3
Important Preface
1.3 Important
Material of particular interest is preceded by one of the following symbols in this manual:
I Contains important information about the subject at hand.
V Caution
Indicates a situation that can cause harm to data.
4 U42127-J-Z100-2-76
© S
iem
ens
Nix
dorf
Info
rma
tions
syst
em
e A
G 1
997
Pfa
d: C
:\Doc
ume
nts
and
Set
tings
\wh
odg
son\
My
Doc
ume
nts\
wor
kin
g\S
NM
P_
May
_02\
snm
p.k0
2
2 OverviewThe PRIMECLUSTER SNMP product collects and reports information and statistics on the status and configuration of PRIMECLUSTER products. The information can be queried by any SNMP management station. The PRIMECLUSTER products that currently display information by means of SNMP are as follows:
● Cluster Foundation (CF)
● Scalable Internet Services (SIS)
● Reliant Monitor Services (RMS)
The PRIMECLUSTER SNMP product consists primarily of MIBs (Management Information Bases) and subagents. MIBs are files that define what information will be provided via SNMP. Subagents are programs that perform the following tasks:
● Query PRIMECLUSTER components
● Use the queried information to fill in the MIB structures
● Allow an SNMP management station to display the information
Normally a subagent collects information for one MIB; however, the fscHaCl MIB has some of its information collected by the RMS subagent and some collected by the ClusterView (CV) subagent.
U42127-J-Z100-2-76 5
Overview
6 U42127-J-Z100-2-76
© S
iem
ens
Nix
dorf
Info
rma
tions
syst
em
e A
G 1
997
Pfa
d: C
:\Doc
ume
nts
and
Set
tings
\wh
odg
son\
My
Doc
ume
nts\
wor
kin
g\S
NM
P_
May
_02\
snm
p.k0
3
3 SubagentsSubagents are processes that query and display information. Subagents usually collect information for one MIB. A notable exception is the fscHaCl MIB (described below), which has some of its information collected by the RMS subagent and some of its information collected by the ClusterView (CV) subagent. The subagents that come with the PRIMECLUSTER SNMP product are as follows:
● ClusterView subagent (cvagt)
● Cluster Foundation (CF) subagent (cfagt)
● Scalable Internet Services (SIS) subagent (sisagt)
● Reliant Monitor Services (RMS) subagent (rmsagt)
For diagnostic purposes, the subagents can be started with the following parameters:
I Unexpected errors are written to the log file.
3.1 ClusterView subagent
The CV MIB and subagent provide information about the configuration and status of cluster-wide entities. This subagent runs on all nodes in the cluster. The information from the subagent on each node is essentially identical. The CV subagent generates an SNMP trap when a state change is detected on any node.
-D Turns on debug mode (written to the log file).
-T Turns on trap debug mode (written to the log file).
-l logfile Specifies an alternate path and filename of the log file. By default the log file has the following path name:/var/opt/SMAW/SMAWrcmib/log/subagent_name.log
U42127-J-Z100-2-76 7
Cluster Foundation subagent Subagents
3.2 Cluster Foundation subagent
The CF MIB and subagent display detailed information about the CF status on each node in the cluster. This subagent displays the CF configuration, status, and statistical information about a node’s routes, interconnect devices, and message passing. SNMP traps are generated when a route or interconnect device has a state change (when a route goes down).
3.3 Scalable Internet Services subagent
The SIS MIB and subagent display information about the SIS configuration and status. This subagent generates an SNMP trap when a change in state of a SIS service is detected. The SIS subagent is only available on 64-bit platforms.
3.4 Reliant Monitor Services subagent
The RMS MIB and subagent display detailed information about the RMS config-uration that is running on a system. This MIB and subagent provides details about the high-availability (HA) applications that are running under the control of RMS. An SNMP trap is generated when an HA application has a state change.
8 U42127-J-Z100-2-76
© S
iem
ens
Nix
dorf
Info
rma
tions
syst
em
e A
G 1
997
Pfa
d: C
:\Doc
ume
nts
and
Set
tings
\wh
odg
son\
My
Doc
ume
nts\
wor
kin
g\S
NM
P_
May
_02\
snm
p.k0
4
4 Installation
4.1 Prerequisites
Before running the SNMP product, ensure that PRIMECLUSTER is installed and running. Refer to the PRIMECLUSTER Installation Guide for more infor-mation on installing PRIMECLUSTER.
The subagents are built using the Emanate subagent development toolkit from SNMP Research; therefore, you need to run the Emanate master agent on each node in the cluster. The Emanate master SNMP agent can be found on the CD-SYS-SPARC CD-ROM. Refer to the Emanate master agent readme for more information.
The following packages must be installed:
● SMAWadapt—Starts Solaris SNMP on an alternate port
● SMAWsnmpm—Emanate master agent
● SMAWmngrs—Emanate tools
● SMAWcf—Cluster Foundation
4.2 Installing
The PRIMECLUSTER SNMP MIBs and subagents are shipped as part of the package file SMAWrcmib. To install the product, execute pkgadd on the SMAWrcmib package file.
The SMAWrcmib package is installed into the /opt/SMAW/SMAWrcmib directory. The default location for log files produced by each subagent is /var/opt/SMAW/SMAWrcmib/log.
4.2.1 Scripts
The script /etc/init.d/S99rcmib is used to start or stop the subagents. This script is linked to appropriate /etc/rc* directories so that the subagents are started or stopped when the system is booted or shut down. To manually start
U42127-J-Z100-2-76 9
Installing Installation
(load) or stop (unload) the subagents, the script /opt/SMAW/SMAWrcmib/dep/S99rcmib can be executed with either the load or unload argument.
4.2.2 .dat files
When the PRIMECLUSTER SNMP package is installed, the subagentinfo.dat (for example, cvinfo.dat) files in /opt/SMAW/SMAWrcmib/conf are merged into the /etc/snmp/mgr/snmpinfo.dat file. The snmpinfo.dat is used by the Emanate master agent to cross-reference a MIB variable to its unique SNMP OID. The merging of these .dat files is done automatically when the package is installed. If for some reason the /etc/snmp/mgr/snmpinfo.dat file is destroyed, these files will need to be merged again (see the Emanate utility mergeinfo).
10 U42127-J-Z100-2-76
© S
iem
ens
Nix
dorf
Info
rma
tions
syst
em
e A
G 1
997
Pfa
d: C
:\Doc
ume
nts
and
Set
tings
\wh
odg
son\
My
Doc
ume
nts\
wor
kin
g\S
NM
P_
May
_02\
snm
p.k0
5
5 ExamplesThe following is an example snmp walk of the cvNodeTable of the CV MIB:
% getmany -v1 <host> public cvNodeTablecvNodeName.1 = maxwellcvNodeName.2 = newtoncvPersistentNodeName.1 = maxwellcvPersistentNodeName.2 = newtoncvNodeState.1 = UPcvNodeState.2 = UPcvNodeOS.1 = SolariscvNodeOS.2 = SolariscvNodeCPU.1 = SparccvNodeCPU.2 = Sparc
The following is an example snmp get of the cvClusterName variable of the CV MIB:
% getone -v1 $TARGET_HOST public cvClusterName.0cvClusterName.0 = SNMP_TEST
U42127-J-Z100-2-76 11
Examples
12 U42127-J-Z100-2-76
© S
iem
ens
Nix
dorf
Info
rma
tions
syst
em
e A
G 1
997
Pfa
d: C
:\Doc
ume
nts
and
Set
tings
\wh
odg
son\
My
Doc
ume
nts\
wor
kin
g\S
NM
P_
May
_02\
snm
p.k0
6
6 MIBsThe following figures show the hierarchical details of the SNMP MIBs.
Figure 1: CV MIB hierarchical tree
cvServiceEntry(1)cvNodeEntry(1)
fscPrimeCluster(43)
cvObjects(1)
cvNumberOfNodes(1)cvClusterName(2)cvClusterDescription(3)cvClusterState(4)cvClusterLastStateChange(5)cvMasterNodeName(6)cvClusterVersion(7)cvClusterUpTime(8)cvQuorumState(9)cvQuorumMethod(10)cvQuorumSet(11)cvQuorumDetailState(12)cvShutdownServiceState(13)
all-online(1)partial-online(2)rebuilding(3)unknown(4)
true(1)false(2)
cvNodeTable(20)cvServiceTable(21)cvProductTable(22)cvNodegroupTable(23)cvTraps(30)cvConformance(40)
true(1)false(2)
cvServiceNumber(1)cvServiceName(2)cvServiceState(3)cvServiceProductIdx(4)cvServiceActiveNodesIdx(5)cvServiceInstalledNodesIdx(6)cvServiceType(7)cvServiceSubType(8)
cvProductNumber(1)cvProductName(2)cvProductState(3)cvProductActiveNodesIdx(4)cvProductInstalledNodesIdx(5)
cvNodegroupIndex(1)cvNodegroupName(2)cvNodegroupNumber(3)
cvProductEntry(1)
cvNodeNumber(1)cvNodeName(2)cvPersistentNodeName(3)cvNodeState(4)cvNodeDescription(5)cvNodeOS(6)cvNodeOSVersion(7)cvNodeCPU(8)
cvClusterStateChanged(21) cvNodeStateChanged(22) cvServiceStateChanged(23) cvProductStateChanged(24)
unknown(1)other(2)up(3)down(4)
unknown(1)other(2)up(3)down(4)
U42127-J-Z100-2-76 13
MIBs
Figure 2: CF MIB hierarchical tree
cfRouteEntry(1)
cfNodeEntry(1)
cfObject(2)
cfClusterName(1)
cfLocalNodeName(2)
cfLocalNodeNumber(3)
cfNodeVersion(4)
cfNodeTable(5)
cfRouteTable(6)
cfDeviceTable(7)
cfIcfStatTable(8)
cfGenStatTable(9)
cfNodeInfoTraps(10)
cfRouteIndex(1)cfRouteNodeName(2)cfRouteNumber(3)cfRouteSrcDev(4)cfRouteDestDev(5)cfRouteType(6)cfRouteState(7)cfRouteDestAddr(8)
cfDeviceEntry(1)
cfDeviceIndex(1)cfDeviceNumber(2)cfDeviceName(3)cfDeviceType(4)cfDeviceSpeed(5)cfDeviceMTU(6)cfDeviceState(7)cfDeviceConfigured(8)cfDeviceAddress(9)
cfIcfStatIndex(1)cfIcfStatTargetNode(2)cfIcfDataPktsTx(3)cfIcfEnqPktsTx(4)cfIcfAckPktsTx(5)cfIcfNackPktsTx(6)cfIcfHtbtReqPktsTx(7)cfIcfHtbtRplyPktsTx(8)cfIcfSynPktsTx(9)cfIcfSynAckPktsTx(10)cfIcfSqePktsTx(11)cfIcfEchoPktsTx(12)cfIcfNoSvcPktsTx(13)cfIcfDataPktsRx(14)cfIcfEnqPktsRx(15)cfIcfAckPktsRx(16)cfIcfNackPktsRx(17)cfIcfHtbtReqPktsRx(18)cfIcfHtbtRplyPktsRx(19)cfIcfSynPktsRx(20)cfIcfSynAckPktsRx(21)cfIcfSqePktsRx(22)cfIcfEchoPktsRx(23)cfIcfNoSvcPktsRx(24)cfIcfErrorFromInterfaceOnTx(25)cfIcfNodeNotConfigdYet(26)cfIcfGenerationMismatch(27)cfIcfMsgDroppedFailedUnpack(28)cfIcfRxOutOfSeqMsgs(29)cfIcfRetransmitSendQueueRequests(30)cfIcfAckTxAttempts(31)cfIcfRxDuplicatePktDropped(32)cfIcfRxPktWBadSvcTypeDropped(33)cfIcfDataFragmentsTxted(34)cfIcfAllocateFuncFailures(35)cfIcfInputFuncFailures(36)cfIcfFfreeFuncCallsTxDone(37)cfIcfSfreeFuncCallsGotAck(38)cfIcfSynTimeouts(39)cfIcfRegularHeartbeatTimeouts(40)cfIcfRequestedHeartbeatTimeouts(41)cfIcfMsgsQuicklyDeferred(42)cfIcfMsgsDeferred(43)cfIcfServiceSwitchedRoute(44)cfIcfRepliesRerouted(45)cfIcfInputBusy(46)
cfGenStatIndex(1)cfGenStatName(2)cfGenStatValue(3)
cfNodeStateChanged(41)cfRouteStateChanged(42)cfDeviceStateChanged(43)cfDeviceConfiguredChanged(44)
cfNodeIndex(1)cfNodeName(2)cfNodeNumber(3)cfNodeState(4)cfNodeOS(5)cfNodeCPU(6)
cfGenStatEntry(1)
cfIcfStatEntry(1)
14 U42127-J-Z100-2-76
MIBs
© S
iem
ens
Nix
dorf
Info
rma
tions
syst
em
e A
G 1
997
Pfa
d: C
:\Doc
ume
nts
and
Set
tings
\wh
odg
son\
My
Doc
ume
nts\
wor
kin
g\S
NM
P_
May
_02\
snm
p.k0
6
Figure 3: SIS MIB hierarchical tree
sisInterfaceSvcEntry(1)
sisInterfaceEntry(1)sisInterfaceTable(2)
sisInterfaceSvcTable(3)
sisServiceTable(4)
sisConnTable(5)
sisGenStatTable(6)
sisServiceTraps(7)
sisServiceEntry(1)
sisNodeIndex(1)sisNodeId(2)sisNodeName(3)sisNodeType(4)sisNodeState(5)
sisGenStatEntry(1)
sisConnEntry(1)
sisInterfaceIndex(1)sisInterfaceAddr(2)sisInterfaceType(3)sisInterfaceNetMask(4)sisInterfacePreferredGW(5)sisInterfaceActiveGW(6)sisInterfaceState(7)sisInterfaceProxyFailoverNodeList(8)
sisInterfaceSvcIndex(1)sisInterfaceSvcVipAddr(2)sisInterfaceSvcName(3)sisInterfaceSvcScheduling(4)sisInterfaceSvcNodeList(5)sisInterfaceSvcActiveNode(6)sisInterfaceSvcType(7)
sisServiceIndex(1)sisServiceService(2)sisServiceNode(3)sisServiceProto(4)sisServiceState(5)sisServiceConCount(6)sisServiceSuspends(7)
sisConnIndex(1)sisConnNodeId(2)sisConnNodeName(3)sisConnLocalAddr(4)sisConnForeignAddr(5)sisConnGatewayNodeName(6)
sisGenStatIndex(1)sisGenStatName(2)sisGenStatValue(3)
sisServiceStateChanged(4)sisNodeStateChanged(5)
sisInterfaceEntry(1)sisInterfaceTable(2)
sisObject(4)
U42127-J-Z100-2-76 15
MIBs
Figure 4: RMS MIB hierarchical tree
rmsApplicationTable(1)
rmsSystemTable(1)rmsSystems(3)
rmsApplications(4)
rmsResources(5)
rmsResSysRelTable(7)
rmsResourceAttributes(8)
rmsClusterConfigurationFile(1)rmsClusterExclusiveAccess(2)rmsClusterLastUpdate(3)rmsClusterAction(4)
rmsSystemName(1)rmsSystemDescription(2)rmsSystemState(3)rmsSystemOS(4)rmsSystemOSVersion(5)rmsSystemClusterName(6)rmsSystemAction(7)
rmsClusterInfo(2)
rmsObjects(1) rmsConformance(3)rmsNotifications(2)
unknown(1)other(2)access(3)noAccess(4)
rmsCompliances(1)rmsGroups(2)
rmsSystemEntry(1)
rmsApplicationEntry(1)
rmsResourceTable(2) rmsResourceEntry(1)
rmsApplicationType(1)rmsApplicationSystemList(2)rmsApplicationAction(3)msApplicationActionOnSystem(4)
rmsResSysRelEntry(1) rmsResSysRelInfo(1)
rmsResourceAttributesNumber(1)
rmsResourceAttributeTable(2)
rmsResourceAttributeName(1)rmsResourceAttributeValue(2)
rmsResourceAttributeEntry(1)
rmsSystemInterfaceNumber(1)
rmsSystemInterfaceTable(2) rmsSystemInterfaceEntry(1)rmsSystemInterface(9)
unknown(1)other(2)access(3)noAccess(4)
unknown(1)start(2)stop(3)shutdown(4)
unknown(1)start(2)forcestart(3)clear(4)stop(5)enable(6)disable(7)
rmsResourceWorkSystem(1)rmsResourceSubApplication(2)rmsResourceIsSubApplication(3)rmsResourceNoDisplay(4)rmsResourceAction(5)
unknown(1)preonline(2)online(3)postonline(4)preoffline(5)offline(6)postoffline(7)
unknown(1)other(2)yes(3)no(4)
rmsSystemInterfaceTableIndex(1)rmsSystemInterfaceName(2)rmsSystemInterfaceType(3)rmsSystemInterfaceIPName(4)rmsSystemInterfaceState(5)
16 U42127-J-Z100-2-76
MIBs
© S
iem
ens
Nix
dorf
Info
rma
tions
syst
em
e A
G 1
997
Pfa
d: C
:\Doc
ume
nts
and
Set
tings
\wh
odg
son\
My
Doc
ume
nts\
wor
kin
g\S
NM
P_
May
_02\
snm
p.k0
6
Figure 5: HA Cluster MIB Hierarchical tree
fscHaClClusterInfo(2)
fscHaClSystems(3)
fscHaClApplications(4)
fscHaClResources(5)
fscHaClSubAgentInfo(1)
fscHaClObjects(1) fscHaClNotifications(2)
fscHaClResSysRelTable(7)
fscHaClSubAgentVersion(1)fscHaClSubAgentDescription(2)fscHaClSubAgentType(3)fscHaClSubAgentInfoOperScope(4)fscHaClSubAgentNotificationOperScope(5)fscHaClSubAgentInfoAdminScope(6)fscHaClSubAgentNotificationAdminScope(7)fscHaClSubAgentLocalNodeName(8)
fscHaClAppSysRelTable(6)
fscHaClConformance(3)
fscHaClTraps(0)
fscHaClClusterInfAvailable(1)fscHaClClusterInfNotAvailable(2)fscHaClMonitorStateChanged(3)fscHaClSystemStateChanged(4)fscHaClApplicationStateChanged(5)fscHaClResourceStateChanged(6)
fscHaClCompliances(1)fscHaClGroups(2)
fscHaClCompliance(1)
fscHaClSubAgentGroup(1)fscHaClClusterGroup(2)fscHaClTableNumberGroup(3fscHaClSystemGroup(4)fscHaClApplicationGroup(5)fscHaClResourceGroup(6)fscHaClApplSysRelGroup(7)fscHaClResSysRelGroup(9)fscHaClNotificationsGroup1(10fscHaClNotificationsGroup2(1
fscHaClClusterName(1)fscHaClClusterDescription(2)fscHaClClusterType(3)fscHaClClusterVersion(4)fscHaClClusterVendor(5)fscHaClClusterMonitoringState(6)
fscHaClSystemNumber(1)fscHaClSystemTable(2) fscHaClSystemEntry(1)
fscHaClSystemName(1)fscHaClSystemDescription(2)fscHaClSystemState(3)fscHaClSystemOS(4)fscHaClSystemOSVersion(5)
fscHaClApplicationNumber(1)fscHaClApplicationTable(2 fscHaClApplicationEntry(1)
fscHaClApplicationName(1)fscHaClApplicationDescription(2)fscHaClApplicationState(3)fscHaClApplicationWorkSystem(4)
fscHaClResourceNumber(1)fscHaClResourceTable(2) fscHaClResourceEntry(1)
fscHaClResourceName(1)fscHaClResourceDescription(2)fscHaClResourceState(3)fscHaClResourceTypeDescr(4)
fscHaClAppSysRelEntry(1) fscHaClAppSysRelState(1)
fscHaClResSysRelEntry(1) fscHaClResSysRelState(1)
unknown(1)other(2)emanate(3)
unknown(1)other(2)all(3)subset(4)local(5)all(6)
all(3)subset(4)local(5)all(6)
unknown(1)other(2)rms(3)niplexAF(4)
unknown(1)other(2)up(3)down(4)runningup(5)runningdown(6)pending(7)
unknown(1)other(2)up(3)down(4)crashed(5)
unknown(1)other(2)undefined(3)online(4)offline(5)down(6)faulted(7)
U42127-J-Z100-2-76 17
MIBs
18 U42127-J-Z100-2-76
© S
iem
ens
Nix
dor
f In
form
atio
nssy
ste
me
AG
19
97
Pfa
d: C
:\Doc
ume
nts
and
Set
ting
s\w
hod
gson
\My
Do
cum
ents
\wor
king
\SN
MP
_M
ay_0
2\sn
mp.
six
Index
.dat files 10
Ccfagt 7Cluster Foundation 5Cluster Foundation MIB 14ClusterView MIB 13ClusterView subagent 5, 7cvagt 7
Ddebug mode 7documentation, additional 1
EEmanate master agent 9Emanate subagent development
toolkit 9examples 11
FfscHaCl MIB 5, 7
HHigh Availability Cluster MIB 17
Iinstalling SNMP 9
Llog file 7
Ooverview 5
Ppkgadd 9
RReliant Monitor Services 5Reliant Monitor Services MIB 16rmsagt 7
SScalable Internet Services 5Scalable Internet Services MIB 15scripts 9sisagt 7SMAWrcmib 9SNMP MIBs 9SNMP trap 7subagents 5, 7
Ttrap debug mode 7
U42127-J-Z100-2-76 19
Index
20 U42127-J-Z100-2-76
© S
iem
ens
Nix
dorf
Info
rma
tions
syst
em
e A
G 1
997
Pfa
d: C
:\Doc
ume
nts
and
Set
tings
\wh
odg
son\
My
Doc
ume
nts\
wor
kin
g\S
NM
P_
May
_02\
snm
p.na
c
Comments on PRIMECLUSTER SNMP
U42127-J-Z100-2-76
CommentsSuggestionsCorrections
✁
Submitted by
Fujitsu Siemens Computers GmbHUser Documentation81730 MunichGermany
Fax: (++49) 700 / 372 00000
email: [email protected]://manuals.mchp.siemens.de
© S
iem
ens
Nix
dorf
Info
rma
tions
syst
em
e A
G 1
997
Pfa
d: C
:\Doc
ume
nts
and
Set
tings
\wh
odg
son\
My
Doc
ume
nts\
wor
kin
g\S
NM
P_
May
_02\
snm
p.na
c
Comments on PRIMECLUSTER SNMP
U42127-J-Z100-2-76
CommentsSuggestionsCorrections
✁
Submitted by
Fujitsu Siemens Computers GmbHUser Documentation81730 MunichGermany
Fax: (++49) 700 / 372 00000
email: [email protected]://manuals.mchp.siemens.de