1. Using Oracle Infrastructure Monitoring
  2. Discovery
  3. Add Oracle ES2 Ethernet Switches

Add Oracle ES2 Ethernet Switches

You can add Oracle ES2 Ethernet Switch entities using the Add Entity UI or using the cloud agent command line interface (omcli) with the appropriate JSON files.

Step 1: Prepare Oracle ES2 Ethernet Switch for monitoring.

Prerequisites

SNMPv1/v2 or SNMPv3 credentials needed for monitoring.

If SNMPv1/v2 is used, you must provide the SNMP community string that was entered during ES2 configuration along with IP address of the Cloud Agent which will be used for appliance monitoring.

If SNMPv3 used, you must provide the SNMPv3 user, plus authentication method (SHA or MD5) password if authentication is used, plus the privilege method (only DES is supported) and privilege password if privilege is used. All of this needs to be manually configured beforehand in the appliance.

Read-only access is adequate for the ES2 monitoring.

Step 2: Decide how you want to add the Oracle ES2 Ethernet Switch.

You can add Oracle ES2 Ethernet Switch entities using one of two ways:

  • Add them from UI
  • Use the agent's omcli add_entity command with the appropriate JSON files

Adding Entities from the UI

  1. From the Management Cloud main menu, select Administration, Discovery, and then Add Entity. The Add Entity page displays.
  2. Select the Oracle ES2 Ethernet Switch Entity Type.
  3. Enter the following UI properties.
    Oracle ES2 Ethernet Switch UI Fields
    • Entity Name: Name of this entity displayed in the Oracle Management Cloud console.
    • Dispatch URL: snmp://<Fully qualified host name or IP address of Oracle ES2 Ethernet Switch>
    • SNMP Port: Port where Oracle ES-2 Ethernet Switch listens for SNMP requests - 161 by default (optional)
    • SNMP Timeout: Timeout for SNMP requests in seconds - 30 secs by default (optional)
    • Cloud Agent: Cloud agent monitoring the host where the Oracle ES2 Ethernet Switch is installed.

    Monitoring Credentials

    SNMP V1/V2

    • Community String: Community String for SNMP communication

    SNMP V3

    • Username: SNMPv3 username.
    • Authorization Password: Password used for authentication
    • Authorization Protocol: Protocol used for authentication. (MD5 or SHA)
    • Privacy Password: password used for encryption

See Add Entities from the Console for detailed instructions on using the Add Entity UI.

Using omcli and the Appropriate JSON Files

  1. Download and extract the required JSON file(s) from the master JSON zip file. See the table below for the specific JSON files you'll need.
  2. Edit the file(s) and specify the requisite properties shown below.
    Oracle ES2 Ethernet Switch JSON Files and Properties

    Definition File: omc_es2_sample.json

    • omc_dispatch_url: snmp://<Fully qualified host name or IP address of Oracle ES2 Ethernet Switch>
    • omc_snmp_port: Port where Oracle ES-2 Ethernet Switch listens for SNMP requests - 161 by default (optional)
    • omc_snmp_timeout: Timeout for SNMP requests in seconds - 30 secs by default (optional)
    • omc_snmp_version: SNMP version used to monitor Oracle ES-2 Ethernet Switch (2c or 3) - 2c by default (optional)

    Credential Files

    Choose the credential JSON file according to the SNMP version credentials you’re using (SNMP v2c or SNMP v3).

    omc_es2_snmpv2_sample_creds.json

    SNMP v2c

    • COMMUNITY: SNMPv2c community string.

    omc_es2_snmpv3_sample_creds.json

    SNMP v3

    • authUser: SNMPv3 username.
    • authPwd: Password used for authentication.
    • authProtocol: Protocol used for authentication - supply either MD5 or SHA.
    • privPwd: Password used for encryption.
  3. Add the entity using omcli.
    omcli add_entity agent DEFINITION_FILE [-credential_file CREDENTIAL_FILE [-encryption_method_gpg]]
  4. Verify the status of the newly added entity. 
    omcli status_entity agent DEFINITION_FILE

See step 4. Adding Entities to Your Service of Add Entities Using JSON Files for more information.

Step 3: (Optional but recommended) Set up alerts.

To enable lights-out monitoring, you can set up alert rules to generate alerts and send notifications if your entities have performance issues.

See Set Up Alert Rules and Set Up Alert Thresholds and Notifications.

Troubleshooting

If you run into any issues regarding discovery or monitoring of Oracle ES2 Ethernet Switch, see the following: