ODA (Oracle Database Appliance): Configuring ASR on version 2.5.0.0.0 and above

Asset ID:	1-71-1523660.1
Update Date:	2018-04-22
Keywords:

Solution Type Technical Instruction Sure

Solution 1523660.1 : ODA (Oracle Database Appliance): Configuring ASR on version 2.5.0.0.0 and above

Applies to:

Oracle Database Appliance Software - Version 2.5.0.0 to 2.10.0.0
Oracle Database Appliance - Version All Versions and later
Information in this document applies to any platform.

Goal

The aim of this bulletin is provide the steps for ASR (Oracle Auto Service Request) configuration on ODA (Oracle Database Appliance) HA (High Availability) version 2.5.0.0.0 and above

Solution

Configuring ASR on version 2.5.0.0.0 and above

Starting with ODA (Oracle Database Appliance) version 2.5.0.0.0 it's possible to configure ASR (Oracle Auto Service Request) using the "oakcli" interface.

Starting with ODA version 2.5.0.0.0, ASR is supporting also an external ASR manager

Configuring ASR during the deploy

You need to enter the following "Oracle Appliance Manager" needed ASR information

ASR

Where

- PROXY server name
The proxy server is a server (a computer system or an application) that acts as an intermediary for requests from ASR client to the oracle transport server (https://transport.oracle.com)

- PROXY server port
It's the server port where the proxy is listening clients requests (by default is the port 80)

- PROXY user ID
It's the userID used to login in the proxy server (if needed)

- PROXY password
It's the userID proxy password to login in the proxy server (if needed)

- Oracle Online Account Username
It's an email address used to login on MOS (My Oracle Support)

- Oracle Online Account Password
It's the password to login on MOS (My Oracle Support)

Note:
if you are configuring ASR inside oracle network:
- the PROXY entries should be empty as the oracle ASR transport server is achievable anyway
- the ASR user ID/ASR password is your MOS (My Oracle Support) account

- You can choose to configure External ASR:

internal - it will setup ASR with an ASR manager running on node1 (SC0)
external - it will setup ASR with an external ASR manager (the external ASR manager IP and Port are required)

- Beginning with ASR 4.1, ILOM telemetry supports the SNMP v3 security protocol. SNMP v3 provides security (encryption and authentication) for any communication between an ASR Asset and OASM.
You can choose to configure SNMP Version2 or Version3, by default we are using SNMP Version2.
Configuring SNMP V3, you must provide the "ILOM engine ID", this must be 25 characters string or less.

Example:
NODE0 ILOM Engine Id: engineid_0
NODE1 ILOM Engine Id: engineid_1

Note:
the ILOM SNMPv3 user "odasnmpv3user" will be added automatically

Configure ASR post deploy

Use the oakcli configure asr command to configure Auto Service Request (ASR) on Oracle Database Appliance.

Syntax

oakcli configure asr [-h]

# oakcli configure asr -h
Usage:
oakcli configure asr

    asr         - configures asr

                 Additional Info:
                 It is an interactive script and requires the following input:
                   PROXY server name
                   PROXY server port
                   PROXY user ID
                   PROXY password
                   ASR user ID
                   ASR password

                   ASR Manager : IP
                   ASR Manager : Port

- PROXY server name
The proxy server is a server (a computer system or an application) that acts as an intermediary for requests from ASR client to the oracle transport server (https://transport.oracle.com)

- PROXY server port
It's the server port where the proxy is listening clients requests (by default is the port 80)

- PROXY user ID
It's the userID used to login in the proxy server (if needed)

- PROXY password
It's the userID proxy password to login in the proxy server (if needed)

- ASR user ID
It's an email address used to login on MOS (My Oracle Support): "Oracle Online Account Username"

- ASR password
It's the password to login on MOS (My Oracle Support): "Oracle Online Account Password"

- ASR Manager : IP
It's the external ASR manager IP address

ASR Manager : Port
- It's the external ASR manager port where it's listening ASR client requests

The oakcli configure asr command initiates an interactive script that requests information to implement ASR on your Oracle Database Appliance:

You can choose one of the following options:

internal - it will setup ASR with an ASR manager running on node1 (SC0)
external - it will setup ASR with an external ASR manager (the external ASR manager IP and Port are required)
deinstall - it will deinstall ASR from both nodes

Example:
NODE0 ILOM Engine Id: engineid_0
NODE1 ILOM Engine Id: engineid_1

Note:
the ILOM SNMPv3 user "odasnmpv3user" will be added automatically

ASR Configuration example

# oakcli configure asr
INFO : Logging all actions in /opt/oracle/oak/onecmd/tmp/zaoda101-20140520085309.log and traces in /opt/oracle/oak/onecmd/tmp/zaoda101-20140520085309.trc
Please enter
1 to setup Internal ASR
2 to setup External ASR
3 to Deinstall ASR
0 to Exit
[1]:1
Setting up ssh for root...
Please enter the root password:

re-enter the root password:

..........done
Enter proxy server name: myproxy.domain
Enter Proxy Server Port number: 8080
Enter proxy user id: myproxyuser
Enter proxy password:
Enter proxy password again:
Enter Oracle Online Account Username:roger.cittoff@oracle.com
Enter Oracle Online Account Password:
Re-enter Oracle Online Account Password:
Enter Port number of ASR Manager[1162]:
Enter SNMP version v2/v3[v2]:
--------------------Summary Of Parameters Entered To Configure Internal ASR--------------------
Proxy Server Name:
Proxy Server Port number:
Proxy User Id:
Proxy Password:
ASR User Id: roger.cittoff@oracle.com
ASR Manager Port: 1162
SNMP Version: v2
NODE0 Ip:10.162.69.91
NODE1 Ip:10.162.69.92
Do you want to reset input parameters? Enter 'y' to reset or 'n' or any other key to continue. (y/n)[n]:

How to check the State of ASR Installation/Configuration

For diagnostic purposes, it may be necessary to check the state of various application bundles installed on the ASR Manager system using the following procedure.

1. Enter the following command:

export JAVA_HOME=/usr/java/default
export PATH=$PATH:/opt/SUNWswasr/bin

asr diag

2. Review the results of this command below along with the settings you should see:

# asr diag

id    State       Bundle
152    ACTIVE      com.sun.svc.asr.sw_4.4.0
                Fragments=153, 154
153    RESOLVED    com.sun.svc.asr.sw-frag_4.4.0
                Master=152
154    RESOLVED    com.sun.svc.asr.sw-rulesdefinitions_4.4.0
                Master=152
156    ACTIVE      com.sun.svc.asr.sw.http.AsrHttpReceiver_1.0.0
                Fragments=157
157    RESOLVED    com.sun.svc.asr.sw.http-frag_1.0.0
                Master=156

151    ACTIVE      com.sun.svc.ServiceActivation_4.4.0

3. If any of these states are incorrect, enter the following commands:

asr stop
asr start

4. Repeat steps 1 to 3.

5. The ASR manager must be registered with the transport server as showed by following command:

# asr show_reg_status
Registered with ASR backend.

6. To be sure that ASR can send information to the transport server. This command sends a test message (ping) to the transport server.

# asr test_connection

i.e.:

# asr test_connection

Connecting to endpoint @ https://transport.oracle.com/v1/queue/sasm-ping
Sending ping message.
Ping message sent.
test_transport completed successfully.

7. You ASR asset must be registered with your ASR Manager, you could check this issuing:

# asr list_asset

i.e. (on ODA V1 BareMetal):

# asr list_asset

IP_ADDRESS      HOST_NAME                    SERIAL_NUMBER                  ASR      PROTOCOL SOURCE         PRODUCT_NAME
--------------- ---------------------------- ------------------------------ -------- --------- -------------- ------------------------------
10.170.79.98    oda-02-c                     1130FMW00D                     Enabled SNMP      ILOM           SUN FIRE X4370 M2 SERVER
10.170.79.97    oda-01-c                     1130FMW00D                     Enabled SNMP      ILOM           SUN FIRE X4370 M2 SERVER
10.170.79.91    oda101                       1130FMW00D                     Enabled SNMP      FMA            SUN FIRE X4370 M2 SERVER x86/x64 System
10.170.79.92    oda102                       1130FMW00D                     Enabled SNMP      FMA            SUN FIRE X4370 M2 SERVER x86/x64 System

Please use My Oracle Support 'http://support.oracle.com' to view the activation status.

i.e. (on ODA V1 Virtualized Platform, only ILOM Source is active):

# asr list_asset

IP_ADDRESS      HOST_NAME                    SERIAL_NUMBER                  ASR      PROTOCOL SOURCE         PRODUCT_NAME
--------------- ---------------------------- ------------------------------ -------- --------- -------------- ------------------------------
10.170.79.98    oda-02-c                     1130FMW00D                     Enabled SNMP      ILOM           SUN FIRE X4370 M2 SERVER
10.170.79.97    oda-01-c                     1130FMW00D                     Enabled SNMP      ILOM           SUN FIRE X4370 M2 SERVER

Please use My Oracle Support 'http://support.oracle.com' to view the activation status.

i.e. (on ODA X3-2 Virtualized Platform, only ILOM Source is active):

Note:
if an asset above is missing, this is identified as bug 16689839. Workaround: manually activate the assets, issuing the following command:

/opt/SUNWswasr/bin/asr activate_asset -h <hostname>

i.e.:
/opt/SUNWswasr/bin/asr activate_asset -h oda-02-c

If you are running on a virtualized platform workaround is to first get the both the ilom ips manually by logging into dom0 of each node and executing below command

/usr/bin/ipmitool sunoem getval /X/network/ipaddress

Once you have the ilom ip, log into dom1 node1 (or Where asr manager is installed) and execute below command to activate asset

/opt/SUNWswasr/bin/asr activate_asset -i node1_ilom_ip
/opt/SUNWswasr/bin/asr activate_asset -i node2_ilom_ip

8. Submit a test event

# asr send_test

i.e.:

# asr send_test -h oda101

Submitted test event for asset oda101
Verification email will be sent to rcitton@oracle.com

9. Validate your ASR configuration

oakcli validate -c asr

# oakcli validate -c asr
INFO: oak Asr information and Validations
RESULT: /opt/oracle/oak/conf/asr.conf exist
RESULT: ASR Manager ip:10.139.154.17
RESULT: ASR Manager port:1162
SUCCESS: ASR configuration file validation successfully completed
RESULT: /etc/hosts has entry 141.146.156.46 transport.oracle.com

RESULT: ilom alertmgmt level is set to minor
RESULT: ilom alertmgmt type is set to snmptrap
RESULT: alertmgmt snmp_version is set to 2c
RESULT: alertmgmt community_or_username is set to public
RESULT: alertmgmt destination is set to 10.139.154.17
RESULT: alertmgmt destination_port is set to 1162
SUCCESS: Ilom snmp confguration for asr set correctly
RESULT: notification trap configured to ip:10.139.154.17
RESULT: notification trap configured to port:1162
SUCCESS: Asr notification trap set correctly
INFO: IP_ADDRESS      HOST_NAME                      SERIAL_NUMBER                  ASR      PROTOCOL SOURCE         PRODUCT_NAME
INFO: --------------- ------------------------------ ------------------------------ -------- --------- -------------- ------------------------------
10.170.79.98    oda-02-c                     1130FMW00D                     Enabled SNMP      ILOM           SUN FIRE X4370 M2 SERVER
10.170.79.97    oda-01-c                     1130FMW00D                     Enabled SNMP      ILOM           SUN FIRE X4370 M2 SERVER
INFO: Please use My Oracle Support 'http://support.oracle.com' to view the activation status.
SUCCESS: asr log level is already set to Fine.
RESULT: Registered with ASR backend.
RESULT: test connection successfully completed.
RESULT: submitted test event for asset:10.139.154.17

RESULT: bundle com.sun.svc.asr.sw is in active state
RESULT: bundle com.sun.svc.asr.sw-frag is in resolved state
RESULT: bundle com.sun.svc.asr.sw-rulesdefinitions is in resolved state
RESULT: bundle com.sun.svc.ServiceActivation is in active state
SUCCESS: ASR diag successfully completed

References

<BUG:16689839> - LNX64-112-CMT: OAKCLI CONFIGURE ASR: INTERNAL: ASR LIST_ASSET SHOWS NO ASSETS
<NOTE:1329200.1> - How To Manage and Approve Pending Oracle Auto Service Request (ASR) Assets In My Oracle Support

Attachments

This solution has no attachment