Go to main content
Oracle® Solaris Cluster 4.3 System Administration Guide

Exit Print View

Updated: June 2017
 
 

Creating, Setting Up, and Managing the Oracle Solaris Cluster SNMP Event MIB

This section describes how to create, set up, and manage the Simple Network Management Protocol (SNMP) event Management Information Base (MIB). This section also describes how to enable, disable, and change the Oracle Solaris Cluster SNMP event MIB.

The Oracle Solaris Cluster software currently supports one MIB, the event MIB. The SNMP manager software traps cluster events in real time. When enabled, the SNMP manager automatically sends trap notifications to all hosts that are defined by the clsnmphost command. Because clusters generate numerous notifications, only events with a severity of min_severity or greater are sent as trap notifications. By default, the min_severity value is set to NOTICE. The log_number value specifies the number of events to be logged in the MIB table before retiring older entries. The MIB maintains a read-only table of the most current events for which a trap has been sent. The number of events is limited by the log_number value. This information does not persist across reboots.

The SNMP event MIB is defined in the sun-cluster-event-mib.mib file and is located in the /usr/cluster/lib/mib directory. You can use this definition to interpret the SNMP trap information.

The Cluster Event SNMP Interface uses the common agent container (cacao) SNMP adaptor as its SNMP agent infrastructure. By default, the port number for the SNMP is 11161, and the default port number for the SNMP traps is 11162. These port numbers can be changed by using the cacaoadm command. See the cacaoadm (1M) man page for more information.

Creating, setting up, and managing an Oracle Solaris Cluster SNMP event MIB can involve the following tasks.

Table 18  Task Map: Creating, Setting Up, and Managing the Oracle Solaris Cluster SNMP Event MIB
Task
Instructions
Enable an SNMP event MIB
Disable an SNMP event MIB
Change an SNMP event MIB
Add an SNMP host to the list of hosts that will receive trap notifications for the MIBs
Remove an SNMP host
Add an SNMP user
Remove an SNMP user

How to Enable an SNMP Event MIB

This procedure shows how to enable an SNMP event MIB.

The phys-schost# prompt reflects a global-cluster prompt. Perform this procedure on a global cluster.

This procedure provides the long forms of the Oracle Solaris Cluster commands. Most commands also have short forms. Except for the long and short forms of the command names, the commands are identical.

  1. Assume a role that provides solaris.cluster.modify authorization.
  2. Enable the SNMP event MIB.
    phys-schost-1# clsnmpmib enable [-n node] MIB
    [–n node]

    Specifies the node on which the event MIB that you want to enable is located. You can specify a node ID or a node name. If you do not specify this option, the current node is used by default.

    MIB

    Specifies the name of the MIB that you want to enable. In this case, the MIB name must be event.

How to Disable an SNMP Event MIB

This procedure shows how to disable an SNMP event MIB.

The phys-schost# prompt reflects a global-cluster prompt. Perform this procedure on a global cluster.

This procedure provides the long forms of the Oracle Solaris Cluster commands. Most commands also have short forms. Except for the long and short forms of the command names, the commands are identical.

  1. Assume a role that provides solaris.cluster.modify authorization.
  2. Disable the SNMP event MIB.
    phys-schost-1# clsnmpmib disable -n node MIB
    –n node

    Specifies the node on which the event MIB that you want to disable is located. You can specify a node ID or a node name. If you do not specify this option, the current node is used by default.

    MIB

    Specifies the type of the MIB that you want to disable. In this case, you must specify event.

How to Change an SNMP Event MIB

This procedure shows how to change the protocol, minimum severity value, and event logging for an SNMP event MIB.

The phys-schost# prompt reflects a global-cluster prompt. Perform this procedure on a global cluster.

This procedure provides the long forms of the Oracle Solaris Cluster commands. Most commands also have short forms. Except for the long and short forms of the command names, the commands are identical.

  1. Assume a role that provides solaris.cluster.modify authorization.
  2. Change the protocol, minimum severity value, and event logging of the SNMP event MIB.
    phys-schost-1# clsnmpmib set -n node
    -p version=SNMPv3 \
    -p min_severity=WARNING \
    -p log_number=100 MIB
    –n node

    Specifies the node on which the event MIB that you want to change is located. You can specify a node ID or a node name. If you do not specify this option, the current node is used by default.

    –p version=value

    Specifies the version of SNMP protocol to use with the MIBs. You specify the value as follows:

    • version=SNMPv2

    • version=snmpv2

    • version=2

    • version=SNMPv3

    • version=snmpv3

    • version=3

    –p min_severity=value

    Specifies the minimum severity value to use with MIBs. You specify the value as follows:

    • min_severity=NOTICE

    • min_severity=WARNING

    • min_severity=ERROR

    • min_severity=CRITICAL

    • min_severity=FATAL

    –p log_number=number

    Specifies the number of events to be logged in the MIB table before retiring the older entries. The default value is 100. Values must range from 100-500. You specify the value as follows: log_number=100.

    MIB

    Specifies the name of the MIB or MIBs to which to apply the subcommand. In this case, you must specify event. If you do not specify this operand, the subcommand uses the default plus sign (+), which means all MIBs. If you use the MIB operand, specify the MIB in a space-delimited list after all other command-line options.

    For more information, see the clsnmpmib(1CL) man page.

How to Enable an SNMP Host to Receive SNMP Traps on a Node

This procedure shows how to add an SNMP host on a node to the list of hosts that will receive trap notifications for the MIBs.

The phys-schost# prompt reflects a global-cluster prompt. Perform this procedure on a global cluster.

This procedure provides the long forms of the Oracle Solaris Cluster commands. Most commands also have short forms. Except for the long and short forms of the command names, the commands are identical.

  1. Assume a role that provides solaris.cluster.modify authorization.
  2. Add the host to the SNMP host list of a community on another node.
    phys-schost-1# clsnmphost add -c SNMPcommunity [-n node] host
    –c SNMPcommunity

    Specifies the SNMP community name that is used in conjunction with the hostname. The host is a system in the network which can be configured to receive the traps

    You must specify the SNMP community name SNMPcommunity when you add a host to a community other than public. If you use the add subcommand without the –c option, the subcommand uses public as the default community name.

    If the specified community name does not exist, this command creates the community.

    –n node

    Specifies the name of the cluster node of the SNMP host that is provided access to the SNMP MIBs in the cluster. You can specify a node name or a node ID. If you do not specify this option, the default is the node where the command is run.

    host

    Specifies the name, IP address, or IPv6 address of a host that is provided access to the SNMP MIBs in the cluster. This can be a host outside the cluster or a cluster node itself trying to get SNMP traps.

How to Disable an SNMP Host From Receiving SNMP Traps on a Node

This procedure shows how to remove an SNMP host on a node from the list of hosts that will receive trap notifications for the MIBs.

The phys-schost# prompt reflects a global-cluster prompt. Perform this procedure on a global cluster.

This procedure provides the long forms of the Oracle Solaris Cluster commands. Most commands also have short forms. Except for the long and short forms of the command names, the commands are identical.

  1. Assume a role that provides solaris.cluster.modify authorization.
  2. Remove the host from the SNMP host list of a community on the specified node.
    phys-schost-1# clsnmphost remove -c SNMPcommunity -n node host
    remove

    Removes the specified SNMP host from the specified node.

    –c SNMPcommunity

    Specifies the name of the SNMP community from which the SNMP host is removed.

    –n node

    Specifies the name of the cluster node on which the SNMP host is removed from the configuration. You can specify a node name or a node ID. If you do not specify this option, the default is the node where the command is run.

    host

    Specifies the name, IP address, or IPv6 address of the host that is removed from the configuration. This can be a host outside the cluster or a cluster node itself trying to get SNMP traps.

    To remove all hosts in the specified SNMP community, use a plus sign (+) for host with the –c option. To remove all hosts, use the plus sign (+) for host.

How to Add an SNMP User on a Node

This procedure shows how to add an SNMP user to the SNMP user configuration on a node.

The phys-schost# prompt reflects a global-cluster prompt. Perform this procedure on a global cluster.

This procedure provides the long forms of the Oracle Solaris Cluster commands. Most commands also have short forms. Except for the long and short forms of the command names, the commands are identical.

  1. Assume a role that provides solaris.cluster.modify authorization.
  2. Add the SNMP user.
    phys-schost-1# clsnmpuser create -n node -a authentication -f password user
    –n node

    Specifies the node on which the SNMP user is added. You can specify a node ID or a node name. If you do not specify this option, the current node is used by default.

    –a authentication

    Specifies the authentication protocol that is used to authorize the user. The value of the authentication protocol can be SHA or MD5.

    –f password

    Specifies a file that contains the SNMP user passwords. If you do not specify this option when you create a new user, the command prompts for a password. This option is valid only with the add subcommand.

    You must specify user passwords on separate lines in the following format:

    user:password

    Passwords cannot contain the following characters or a space:

    • ; (semicolon)

    • : (colon)

    • \ (backslash)

    • \n (newline)

    user

    Specifies the name of the SNMP user that you want to add.

How to Remove an SNMP User From a Node

This procedure shows how to remove an SNMP user from the SNMP user configuration on a node.

The phys-schost# prompt reflects a global-cluster prompt. Perform this procedure on a global cluster.

This procedure provides the long forms of the Oracle Solaris Cluster commands. Most commands also have short forms. Except for the long and short forms of the command names, the commands are identical.

  1. Assume a role that provides solaris.cluster.modify authorization.
  2. Remove the SNMP user.
    phys-schost-1# clsnmpuser delete -n node user
    –n node

    Specifies the node from which the SNMP user is removed. You can specify a node ID or a node name. If you do not specify this option, the current node is used by default.

    user

    Specifies the name of the SNMP user that you want to remove.