/usr/cluster/bin/clsnmpmib -V
/usr/cluster/bin/clsnmpmibsubcommand [] -?
/usr/cluster/bin/clsnmpmib [subcommand] [options] -v [mib]
/usr/cluster/bin/clsnmpmib disable [-n node[,…]] {+ | mib …}
/usr/cluster/bin/clsnmpmib enable [-n node[,…]] {+ | mib …}
/usr/cluster/bin/clsnmpmib export [-n node[,…]]
[-o {- | clconfigfile}] [+ | mib …]
/usr/cluster/bin/clsnmpmib list [-n node[,…]] [+ | mib …]
/usr/cluster/bin/clsnmpmib set [-p name=value] […]
[-n node[,…] {+ | mib …}
/usr/cluster/bin/clsnmpmib show [-n node[,…]] [+ | mib …]
The clsnmpmib command administers existing Oracle Solaris Cluster Simple Network Management Protocol (SNMP) Management Information Bases (MIBs) on the current node. To create SNMP hosts that can administer the MIBs, see the clsnmphost(1CL) man page. To define SNMP Version 3 (SNMPv3) users who can access the MIBs when using the SNMPv3 protocol, see the clsnmpuser(1CL) man page.
The general form of this command is as follows:
clsnmpmib [subcommand] [options] [operands]
You can omit subcommand only if options specifies the option –? or – V.
Each option of this command has a long form and a short form. Both forms of each option are provided with the description of the option in the OPTIONS section.
See the Intro(1CL) man page for more information.
Oracle Solaris Cluster currently supports one MIB, the Event MIB. The Oracle Solaris Cluster SNMP Event MIB notifies an SNMP manager of cluster events in real time. When enabled, the Oracle Solaris Cluster Event MIB automatically sends trap notifications to all hosts that are defined by the clsnmphost command. The Oracle Solaris Cluster Event MIB sends trap notifications on port 11162. The SNMP tree is viewed on port 11161.
You can specify the min_severity or log_number values using the clsnmpmib set subcommand. Because clusters generate numerous event 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.
You can use this command only in the global zone.
The following subcommands are supported:
Disables one or more of the cluster MIBs on the specified nodes.
You can use this subcommand only in the global zone.
If you do not specify the –n option, only MIBs on the current node are disabled. When a MIB is disabled, you cannot access the MIB tables, and the MIB does not send any trap notifications.
Users other than superuser require solaris.cluster.modify role-based access control (RBAC) authorization to use this subcommand. See the rbac (5) man page.
Enables one or more cluster MIBs on the specified node.
You can use this subcommand only in the global zone.
If you do not specify the –n option, only MIBs on the current node are enabled. To limit the MIBs that are enabled, use the mib operand.
When you enable a MIB, you enable all of its functionality. However, some further configuration might be necessary for all of the MIB features to be fully functional. For example, the MIB cannot send trap notifications if no hosts have been configured. For information about configuring the SNMP host, see the clsnmphost(1CL) man page man page.
Users other than superuser require solaris.cluster.modify RBAC authorization to use this subcommand. See the rbac (5) man page.
Exports the cluster MIB configuration information.
You can use this subcommand only in the global zone.
Use the –n option to specify one or more nodes from which to export the MIB configuration information. If you use export without the –n option, the subcommand exports only MIB configuration information from the current node. By default, this subcommand exports configuration information from all MIBs on the current node. To refine the output further, specify the name of one or more MIBs for which you need configuration information.
For more information about the output format from the export subcommand, see the clconfiguration(5CL) man page. By default all output is sent to the standard output. Use the –o option followed by a file name to redirect the output to the file.
Users other than superuser require solaris.cluster.read RBAC authorization to use this subcommand. See the rbac (5) man page.
Displays a list of cluster MIBs on the specified nodes.
You can use this subcommand only in the global zone.
Use the –n option to specify the nodes for the cluster MIBs that you want to list. If you use the list subcommand without the –n option, the subcommand lists only the MIBs on the current node. To limit the MIBs that are listed, specify the name of one or more MIBs that you want to list.
Users other than superuser require solaris.cluster.read RBAC authorization to use this subcommand. See the rbac (5) man page.
Changes the SNMP protocol, min_severity, or log_number setting that is used on one or more of the MIBs on the specified nodes.
You can use this subcommand only in the global zone.
By default, this subcommand changes all MIBs on the nodes. If you do not specify the node, only the SNMP property for the MIBs on the current node is modified. You must specify the SNMP properties by using the –p option. All MIBs use the following default property values: protocol:SNMPv2, min_severity:NOTICE, log_number:100. The set subcommand changes the protocol, min_severity, or log_number setting of all the MIBs, unless you use the mib operand to specify MIB names.
Users other than superuser require solaris.cluster.modify RBAC authorization to use this subcommand. See the rbac (5) man page.
Displays information for MIBs on the specified nodes.
You can use this subcommand only in the global zone.
The show subcommand displays the name of the MIB, its SNMP protocol version, min_severity value, or log_number value. By default, this subcommand shows information for all MIBs on the nodes.
Users other than superuser require solaris.cluster.read RBAC authorization to use this subcommand. See the rbac (5) man page.
The following options are supported:
Displays help information.
You can specify this option with or without a subcommand.
If you use this option without a subcommand, the list of available subcommands is displayed.
If you use this option with a subcommand, the usage options for that subcommand are displayed.
When you use this option, no other processing is performed.
Specifies a node or a list of nodes. You can specify each node as a node name or a node ID. All forms of the clsnmpmib command accept this option. You can use the –n option to specify on which node[s] you want the action to be performed. Without the –n option, the command assumes the current node.
Specifies the location where information about the cluster MIB configuration is to be written. This location can be a file or the standard output. To specify the standard output, specify the minus sign (-) instead of a file name. If you specify the standard output, all other standard output for the command is suppressed. If you do not specify the –o option, the output is sent to the standard output. You can specify this option only with the export subcommand.
Configuration information is written in the format that is defined in the clconfiguration(5CL) man page.
Specifies the version of the SNMP protocol to use with the MIBs. Oracle Solaris Cluster supports the SNMPv2 and SNMPv3 protocol versions.
Specifies the minimum severity value. Only events having values equal to or above the min_severity value will be logged in the MIB table, and for these events the trap will be sent to the configured hosts.
Specifies the number of events to be logged in the MIB table before retiring the older entries.
Multiple instances of –p name=value are allowed.
You can set the following property with this option:
Specifies the version of the 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
Specifies the minimum severity value to use with MIBs. You specify the values as follows:
min_severity=NOTICE
min_severity=WARNING
min_severity=ERROR
min_severity=CRITICAL
min_severity=FATAL
Either upper or lower case values are permitted.
Specifies the number of events to be logged in the MIB table before retiring the older entries. The default value is 100. The values must range from 100–500. You specify the value as follows:
log_number=number
Displays the version of the command.
Do not specify this option with subcommands, operands, or other options because they are ignored. The –V option displays only the version of the command. No other operations are performed.
Prints verbose information to the standard output.
You can specify this option with any form of the command, although some subcommands might not produce expanded output. For example, the export subcommand does not produce expanded output when you specify the verbose option.
The following operands are supported:
Specifies the name of the MIB or MIBs to which to apply the subcommand. 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.
All cluster MIBs.
If the command is successful for all specified operands, it returns zero (CL_NOERR). If an error occurs for an operand, the command processes the next operand in the operand list. The returned exit code always reflects the error that occurred first.
This command returns the following exit status codes:
No error
The command that you issued completed successfully.
Not enough swap space
A cluster node ran out of swap memory or ran out of other operating system resources.
Invalid argument
You typed the command incorrectly, or the syntax of the cluster configuration information that you supplied with the –i option was incorrect.
Permission denied
The object that you specified is inaccessible. You might need superuser or RBAC access to issue the command. See the su(1M) and rbac(5) man pages for more information.
Internal error was encountered
An internal error indicates a software defect or other defect.
I/O error
A physical input/output error has occurred.
No such object
The object that you specified cannot be found for one of the following reasons:
The object does not exist.
A directory in the path to the configuration file that you attempted to create with the –o option does not exist.
The configuration file that you attempted to access with the –i option contains errors.
The following command lists all MIBs on the cluster node.
# clsnmpmib list EventExample 2 Enabling a MIB
The following command enables the Event MIB on the current node.
# clsnmpmib enable event
The names of cluster MIBs are not case sensitive.
Example 3 Changing the ProtocolThe following command changes the protocol of the Event MIB on cluster node phys-cluster-2 to SNMPv3.
# clsnmpmib set -n phys-cluster-2 -p version=SNMPv3 Event
If you use the –n option, you can alternatively use the node ID instead of the node name.
Example 4 Showing the ConfigurationThe following command displays the configuration information on cluster nodes phys-cluster-1 and phys-cluster-2.
# clsnmpmib show -n phys-cluster-1,phys-cluster-2 --- SNMP MIB Configuration on myhost --- SNMP MIB Name: phys-cluster-1 State: Event Enabled: yes Protocol: SNMPv3 min_severity: 1 log_number: 100 SNMP MIB Name: phys-cluster-2 State: Event Enabled: yes Protocol: SNMPv3 min_severity: 3 log_number: 250Example 5 Changing the Min Severity Value
The following command changes the min_severity of the Event MIB on cluster node phys-cluster-2 to WARNING.
# clsnmpmib set -n phys-cluster-2 -p min_severity=WARNING Event
If you use the –n option, you can alternatively use the node ID instead of the node name.
Example 6 Changing the Log_Number ValueThe following command changes the log_number of the Event MIB on cluster node phys-cluster-2 to 250.
# clsnmpmib set -n phys-cluster-2 -p log_number=250 Event
If you use the –n option, you can alternatively use the node ID instead of the node name.
See attributes(5) for descriptions of the following attributes:
|
Oracle Solaris Cluster SNMP Event MIB definition file
clsnmphost(1CL), clsnmpuser(1CL), Intro(1CL), cluster(1CL), sceventmib(1M), scha_calls(3HA), attributes(5) , rbac(5) , clconfiguration(5CL)
The superuser can run all forms of this command.
All users can run this command with the –? (help) or –V (version) option.
To run the clsnmpmib command with other subcommands, users other than superuser require RBAC authorizations. See the following table.
|