4 Post-Discovery Configuration and Verification
-
Verify SNMP Subscription of the Oracle Management Agent to Exadata Storage Server
-
Convert SNMP V2 to V3 at Scale for All Hardware Components in Exadata
Additionally, verify that all the components of Exadata Database Machine are discovered, up, and running. Also, ensure that the components are placed in the rack slots.
It is recommended that you review the logs to verify the successful completion of the discovery process. For the list of logs that you can review and their locations, see Review Logs.
If you encounter issues during discovery, then to troubleshoot them, see Discovery Troubleshooting and EMCLI Discovery Issues in the troubleshooting section.
Verify SNMP Subscription of the Oracle Management Agent to Exadata Storage Server
Exadata Storage Server SNMP configuration is performed using the cellcli
command and can be run in batch using dcli
from a compute node.
Note:
-
During the discovery process, you can optionally provide the necessary
root
credentials to subscribe for SNMP traps from Exadata Storage Servers. If you have done so, then you can skip the remaining steps of this section and proceed with Verify SNMP Configuration for InfiniBand Switch Targets. -
While the
public
string is used for the SNMP examples in the following sections, it is supported to use any valid SNMP community string. -
Use SNMP V3 subscriptions for IPv6-based Exadata Storage Server targets because of limitations in the SNMP V1 protocol.
-
The SNMP receivelet listens on a single address and port for all monitored targets. The port is the UDP port with the same number as the TCP port used in the
EMD_URL
.By default, the SNMP receivelet listens on all addresses; if the property
SnmpRecvletListenNIC
is set in theemd.properties
file, the receivelet will attempt to resolve the value as either a name or IP address, and listen on only that address.This parameter is independent of
AgentListenOnAllNICs
andEMD_URL
because in some installations, the Agent may need to communicate with the OMS and with managed targets on different networks.
Using the ALTER CELL
Command
While using the ALTER
CELL
command, all existing subscribers must be specified along with the
new subscriber being added. Any existing subscribers not specified will be removed
from the configuration. Similarly, you can also modify the
notificationPolicy
or notificationMethod
attributes.
While using the ALTER CELL
command, the host=
and community=
attribute values should be quoted, and type=
is NOT quoted.
If you are using the DCLI utility to set up SNMP configuration, then any command containing punctuation, which will be interpreted by the local shell, must be enclosed with double quotation marks. If the command includes the following characters, then outer quotation marks and escape characters are required:
- $ (dollar sign)
- ' (quotation mark)
- < (less than)
- > (greater than)
- ( ) (parentheses)
The backslash (\) is the escape character that allows the characters to be passed to the cellcli utility without being interpreted by the remote shell.
Exadata Storage Server supports SNMP v1/v2 and v3 version based alert notifications
to the subscribers. To receive alerts in the SNMPv3 version, the monitoring agents
must be added to the snmpsubscriber list using a
snmpuser
.
cellcli command to create a snmpuser
:
# alter cell snmpuser = ((name=XXXXXX, authprotocol=sha, authpassword=*, privprotocol=AES, privpassword=*));
In the above command:
- name: User name
- Use only
*
for the password values in the command. - authProtocol: Authentication protocol. The supported
protocol is SHA. The authProtocol must be specified for the
snmpuser
attribute. The system prompts for the authentication password. The authentication password must have 8 to 12 alphanumeric characters. - privProtocol: Encryption protocol. The protocol options are none, AES, or DES. When the privProtocol attribute is not specified, the default value is none . The system prompts for an encryption password if the encryption protocol is specified. The password is exactly 8 alphanumeric characters, and they are case sensitive.
cellcli command to subscribe the monitoring agents for receiving SNMPv1 alert notifications:
# alter cell snmpsubscriber=((host=<Agent_Host>,port=<Agent_Port>,community=****))
cellcli command to subscribe the monitoring agents for receiving SNMPv3 alert notifications:
# alter cell snmpsubscriber=((host=<Agent_Host>,port=<Agent_Port>, snmpUser=XXXXXXX, type=v3))
In the above two commands:
- Agent_Host: Exadata Storage Server monitoring agent installed host
- Agent_Port: Exadata Storage Server monitoring agent port
- snmpUser is the one that is created using
snmpuser
attribute on Exadata Storage Server.
Check Current SNMP Configuration
Check the current SNMP configuration using the following cellcli
commands:
If SNMP configuration is not available, then configure it. See SNMP Configuration Missing in the troubleshooting section.
Verify SSH Connectivity Using
cellcli
To begin monitoring using
cellcli
, open a new terminal and verify whether the SSH
connectivity was successfully established:
$ ssh -l cellmonitor <cell_ipaddress> cellcli -e 'list cell detail'
-
If you are not prompted for any password, then you can assume that the connectivity is established.
-
If you are asked to confirm whether you want to continue connecting, specify Yes.
Verify SNMP Configuration for InfiniBand Switch Targets
The SNMP configuration for Enterprise Manager monitoring of InfiniBand Switches is done automatically as part of the Enterprise Manager guided discovery process. It is good practice, however, to verify that SNMP configuration has been successful.
Note:
-
During the discovery process, you can optionally provide the necessary
root
credentials to set up SNMP trap for the InfiniBand Switch. If you have done so, then you can skip the remaining steps of this section. -
ilom-admin
is the preferred user when discovering an InfiniBand Switch target for full monitoring.root
user can also be used for full monitoring. If the switch is discovered usingroot
orilom-admin
user, the community string provided during discovery is added to the switch, if it doesn't exist already. -
During SNMP V3 discovery, the V3 user added by the (discovery) user during discovery is added to the switch if the discovery is performed using root or the
ilom-admin
user.
To verify the InfiniBand Switch SNMP configuration for Enterprise Manager monitoring:
snmpget -v 1 -c <community_string> <hostname_of_IB_switch> 1.3.6.1.4.1.42.2.70.101.1.1.9.1.1.5
For example:
$ snmpget -v 1 -c public my_IB_switch.my_company.com 1.3.6.1.4.1.42.2.70.101.1.1.9.1.1.5
SNMPv2-SMI::enterprises.42.2.70.101.1.1.9.1.1.5 = INTEGER: 1
Note:
If the Timeout message is displayed as output for the above command, then it means that the InfiniBand Switch is not yet configured for SNMP. To configure SNMPv3 user and SNMP community, see Create an SNMPv3 User in IB Switches and Create SNMP Community for InfiniBand Switch Targets in the prerequisites section.
Note:
To remove the subscription, follow steps 1 to 5 in Create SNMP Community for InfiniBand Switch Targets (step 3 is not needed). In step 5, set the Agent compute node host name to 0.0.0.0 and the port to 0.
Verify the Cisco Ethernet Switch SNMP Configuration
Run the snmpwalk
command line utility or equivalent
tool to verify the Cisco Switch configuration.
Run the following commands to fetch and display the data from the Cisco switch:
$ snmpget –v 1 –c <community_string> <hostname_of_cisco_switch> 1.3.6.1.4.1.9.2.1.56.0 $ snmpget –v 2c –c <community_string> <hostname_of_cisco_switch> 1.3.6.1.4.1.9.2.1.56.0
Note:
If a timeout message is displayed as an output for the above command, then it means that the Cisco Switch is not yet configured correctly.
If the Cisco Ethernet Switch SNMP configuration is missing, then see Set Up SNMP Subscription for Cisco Ethernet Switch Targets in the troubleshooting section.
Verify the PDU SNMP Configuration
Use the snmpwalk
command line utility or equivalent tool to verify the PDU configuration.
Run the following command to fetch and display the data from PDU:
snmpget –v 1 –c <community_string> <hostname_of_pdu> 1.3.6.1.4.1.2769.1.2.3.1.1.1.0
Note:
If a timeout message is displayed as an output for the above command, then it means that the PDU is not yet configured correctly.
If the PDU SNMP configuration is missing, then see Set Up SNMP for Power Distribution Unit (PDU) Targets in the troubleshooting section.
Convert SNMP V2 to V3 at Scale for All Hardware Components in Exadata
Migrate the already discovered Exadata environments configured with SNMP v2 to use SNMP v3 without having to rediscover or manually perform the related operations.
-
To query the list of targets and their SNMP subscription status, create an input file by entering the information about the database machine target. Following is an example input file:
configMap.dbmTargetName=<DB Machine Target Name> # ## Credentials credMap.agentCred=<Agent Credentials> credMap.computenodeIlomCred=<Compute Node ILOM Credentials> credMap.computenodeSnmpV3Cred=<Compute Node SNMP V3 Credentials> credMap.cellMonitorCred=<Storage Server Admin Credentials> credMap.cellSnmpV3Cred=<Storage Server SNMP V3 Credentials> credMap.pduHttpCred=<PDU Credentials> credMap.pduSnmpV3Cred=<PDU SNMP V3 Credentials> credMap.ciscoIosCred=<CISCO Switch IOS Credentials> credMap.ciscoSnmpV3Cred=<CISCO Switch SNMP V3 Credentials> credMap.ibIlomCred=<IB Switch ILOM Credentials> credMap.ibSnmpV3Cred=<IB Switch SNMP V3 Credentials>
For the details about the values to provide for the parameters in the inputs file, see the table below.
-
Run the following EMCLI command to list all the targets in the Database Machine along with their SNMP subscription status:
emcli submit_procedure -name=DBMachineListSnmpSubscription -input_file="<input_file_path>"
-
To set up SNMP V3 on all relevant targets in the Database Machine, create an input file by entering the information about the database machine target. Following is an example input file:
configMap.dbmTargetName=<DB Machine Target Name> configMap.overridePassword=Y configMap.overrideProtocols=Y # ## Credentials credMap.agentCred=<Agent Credentials> credMap.computenodeIlomCred=<Compute Node ILOM Credentials> credMap.computenodeAdminCred=<Compute Node Admin Credentials> credMap.computenodeSnmpV3Cred=<Compute Node SNMP V3 Credentials> credMap.cellMonitorCred=<Storage Server Admin Credentials> credMap.cellSnmpV3Cred=<Storage Server SNMP V3 Credentials> credMap.pduHttpCred=<PDU Credentials> credMap.pduSnmpV3Cred=<PDU SNMP V3 Credentials> credMap.ciscoIosCred=<CISCO Switch IOS Credentials> credMap.ciscoSnmpV3Cred=<CISCO Switch SNMP V3 Credentials> credMap.ibIlomCred=<IB Switch ILOM Credentials> credMap.ibSnmpV3Cred=<IB Switch SNMP V3 Credentials>
For the details about the values to provide for the parameters in the inputs file, see the table below.
-
Run the following EMCLI command to set up SNMP V3 on all the targets:
emcli submit_procedure -name=DBMachineUpdateSnmpSubscription -input_file="<input_file_path>"
Details of the parameters used in the input file:
Parameter | Mandatory | Description |
---|---|---|
configMap.dbmTargetName |
Yes | Database Machine name whose SNMP monitoring mechanism needs to be updated |
configMap.overridePassword |
No | Flag to decide if the target's authorization and privacy
protocols' password should be updated with the SNMP monitoring
credentials provided in the input file. Default value
N . This flag is applicable only for
DBMachineUpdateSnmpSubscription .
|
configMap.overrideProtocols |
No | Flag to decide if the target's authorization and privacy
protocols should be updated with the SNMP monitoring credentials
provided in the input file. Default value N . This flag
is applicable only for
DBMachineUpdateSnmpSubscription .
|
credMap.agentCred |
Yes | Agent credentials for compute node SNMP subscription. Format: <EM_USER>:<agent_named_creds> |
credMap.cellMonitorCred |
No | Storage server Admin credentials. Format:
<EM_USER>:<cell_admin_named_creds> and must be
of Type ExaCreds , ExaCLICred , or
ExaSSHCreds .
|
credMap.cellnodeSnmpV3Cred |
No | Storage server SNMP V3 credentials. Format:
<EM_USER>:<cell_snmp_named_creds> and must be of
Type SNMPV3Creds .
|
credMap.ciscoIosCred |
No | CISCO switch IOS credentials. Format:
<EM_USER>:<cisco_named_creds> and must be of Type
cisco_creds , cisco_key_auth_creds ,
or cisco_private_key_auth_creds .
|
credMap.ciscoSnmpV3Cred |
No | CISCO switch SNMP V3 credentials. Format:
<EM_USER>:<cisco_snmp_named_creds> and must be
of Type SNMPV3Creds .
|
credMap.computenodeAdminCred |
No | Compute node Admin credentials. Format:
<EM_USER>:<compute_admin_named_creds> and must
be of Type ssh_creds .
|
credMap.computenodeIlomCred |
No | Compute node ILOM credentials. Format:
<EM_USER>:<compute_ilom_named_creds> and must be
of Type ilom_creds ,
ilom_key_auth_creds , or
ilom_private_key_auth_creds .
|
credMap.computenodeSnmpV3Cred |
No | Compute node SNMP V3 subscription credentials. Format:
<EM_USER>:<compute_snmp_named_creds> and must be
of Type SNMPV3Creds |
credMap.ibIlomCred |
No | IB switch ILOM credentials. Format:
<EM_USER>:<ib_named_creds> and must be of Type
ilom_creds , ilom_key_auth_creds ,
or ilom_private_key_auth_creds .
|
credMap.ibSnmpV3Cred |
No | IB switch SNMP V3 credentials. Format:
<EM_USER>:<ib_snmp_named_creds> and must be of
Type SNMPV3Creds .
|
credMap.pduHttpCred |
No | PDU credentials. Format:
<EM_USER>:<pdu_http_named_creds> and must be of
Type http .
|
credMap.pduSnmpV3Cred |
No | PDU SNMP V3 credentials. Format:
<EM_USER>:<pdu_snmp_named_creds> and must be of
Type SNMPV3Creds .
|