The Oracle Private Cloud Appliance components that are qualified as ASR assets are:
Server compute nodes
NM2-36P Sun Datacenter InfiniBand Expansion Switches
ZFS Storage Appliance
There is no ASR support for the Oracle Switch ES1-24 switches and Oracle Fabric Interconnect F1-15s in Oracle Private Cloud Appliance Release 2.3. The two management nodes also must not be activated.
This section provides the instructions to activate each type of Oracle Private Cloud Appliance ASR asset.
The ASR activation mechanism requires operations in two separate locations. First the compute node ILOMs are configured to send SNMP traps to the ASR Manager when a failure occurs. Then the ASR Manager is configured to recognize the ILOMs as assets and accept their input. Follow the procedure below to activate the compute nodes as ASR assets.
Activating Compute Nodes as ASR Assets
Using SSH, log into the compute node ILOM as
root
.Go to the alert rules directory and display rule set 2.
CautionAs of Release 2.2.1 the ILOM rule set 1 is used by the Oracle PCA controller software. The first available rule set is typically set 2.
-> cd /SP/alertmgmt/rules /SP/alertmgmt/rules -> show 2 /SP/alertmgmt/rules/2 Targets: Properties: type = snmptrap level = disable destination = 0.0.0.0 destination_port = 0 community_or_username = public snmp_version = 1 testrule = (Cannot show property) ->
If the rule set is available (destination = 0.0.0.0), configure it for ASR. Otherwise, look for the next available rule set.
Define a new rule set with the following properties:
-> cd 2 ->
set level=minor destination=192.168.4.216 destination_port=1162 snmp_version=2c
-> show /SP/alertmgmt/rules/2 Targets: Properties: type = snmptrap level = minor destination = 192.168.4.216 destination_port = 1162 community_or_username = public snmp_version = 2c testrule = (Cannot show property) Commands: cd set show ->The destination property is a virtual IP in the appliance management network, shared by both management nodes, but active only on the master.
Use a space character to separate rule set properties.
Activate the compute node as an ASR asset in ASR Manager.
Using SSH, log into the master management node.
Activate the asset by adding its ILOM IP to the ASR configuration with the following command:
# /opt/SUNWswasr/bin/asr activate_asset –i
<asset_ilom_ip>
CautionVerify that you are activating the asset with the IP address of its ILOM, and not the IP assigned to another network interface.
Repeat this procedure for each compute node you wish to activate as an ASR asset.
The ASR activation mechanism requires operations in two separate locations. First the switches' ILOMs are configured to send SNMP traps to the ASR Manager when a failure occurs. Then the ASR Manager is configured to recognize the ILOMs as assets and accept their input. Follow the procedure below to activate the NM2-36P Sun Datacenter InfiniBand Expansion Switches as ASR assets.
Activating InfiniBand Switches as ASR Assets
Using SSH, log into the NM2-36P Sun Datacenter InfiniBand Expansion Switch ILOM as
root
.Launch the Service Processor shell.
[root@ilom-ovcasw19r1 ~]# spsh ->
Go to the alert rules directory and display rule set 2.
CautionAs of Release 2.2.1 the ILOM rule set 1 is used by the Oracle PCA controller software. The first available rule set is typically set 2.
-> cd /SP/alertmgmt/rules /SP/alertmgmt/rules -> show 2 /SP/alertmgmt/rules/2 Targets: Properties: type = snmptrap level = disable destination = 0.0.0.0 destination_port = 0 community_or_username = public snmp_version = 1 testrule = (Cannot show property) Commands: cd set show ->
Define a new rule set with the following properties:
-> cd 2 ->
set level=minor destination=192.168.4.216 destination_port=1162 snmp_version=2c
Set 'level' to 'minor' Set 'destination' to '192.168.4.216' Set 'destination_port' to '1162' Set 'snmp_version' to '2c' -> show /SP/alertmgmt/rules/2 Targets: Properties: type = snmptrap level = minor destination = 192.168.4.216 destination_port = 1162 community_or_username = public snmp_version = 2c testrule = (Cannot show property) Commands: cd set show ->The destination property is a virtual IP in the appliance management network, shared by both management nodes, but active only on the master.
Rule set properties are space-separated.
Make sure that SNMP version 2c is enabled on the switch.
-> cd /SP/services/snmp /SP/services/snmp -> show /SP/services/snmp Targets: communities mibs users Properties: engineid = (none) port = 161 servicestate = enabled sets = disabled v1 = disabled v2c = disabled v3 = enabled Commands: cd set show ->
set v2c=enabled
Activate the NM2-36P Sun Datacenter InfiniBand Expansion Switch as an ASR asset in ASR Manager.
Using SSH, log into the master management node.
Activate the asset by adding its ILOM IP to the ASR configuration with the following command:
# /opt/SUNWswasr/bin/asr activate_asset –i
<asset_ilom_ip>
Repeat this procedure for the second InfiniBand switch in order to activate it as an ASR asset.
The ZFS Storage Appliance differs from the other ASR assets
because it runs its own ASR Manager, and relays its ASR data to
the Oracle backend systems through the outbound
connection of the master management node. To achieve this,
Oracle Private Cloud Appliance relies on the tinyproxy
HTTP
and HTTPS proxy daemon. ASR requires
tinyproxy
version 1.8.3 or later to be
installed and properly configured on both management nodes. See
Section 6.4, “Configuring TinyProxy”.
For detailed information about enabling ASR on the ZFS Storage Appliance, refer to the ASR documentation and the support note with Doc ID 1285455.1.
You must set up the ZFS Storage Appliance to relay its ASR data through the ASR Manager on the master management node, using the following proxy settings:
inet addr: 192.168.4.216
broadcast: 192.168.4.255
mask: 255.255.255.0
port: 8888
Enabling ASR from the CLI on the Active Storage Controller
Using SSH and an account with superuser privileges, log into the master management node, and then log into the active storage controller from there.
NoteThe data center IP address used in this procedure is an example.
The two storage controllers of the ZFS Storage Appliance use the IP addresses
192.168.4.1
and192.168.4.2
.# ssh root@10.100.1.101 root@10.100.1.101's password: [root@ovcamn05r1 ~]# ssh root@192.168.4.1 ovcasn01r1:> ls Properties: showcode = false showstack = false exitcoverage = false showmessage = true asserterrs = false Children: analytics => Manage appliance analytics configuration => Perform configuration actions maintenance => Perform maintenance actions raw => Make raw XML-RPC calls shares => Manage shares status => View appliance status
Work your way down the configuration tree to the SCRK service.
ovcasn01r1:> configuration ovcasn01r1:configuration> services ovcasn01r1:configuration services> scrk ovcasn01r1:configuration services scrk> ls Properties: <status> = disabled soa_id = soa_password = proxy_on = false proxy_host = proxy_user = proxy_password =
Use the set command to make the following eight changes.
NoteMake sure you have an active user account on My Oracle Support, because you need the user name and password to set the configuration parameters.
ovcasn01r1:configuration services scrk> set soa_id=
<registered-MOS-user>
ovcasn01r1:configuration services scrk> set soa_password=<MOS-user-password>
ovcasn01r1:configuration services scrk> set proxy_on=true ovcasn01r1:configuration services scrk> set proxy_host=192.168.4.216:8888 ovcasn01r1:configuration services scrk> set proxy_user=root ovcasn01r1:configuration services scrk> set proxy_password=Welcome1 ovcasn01r1:configuration services scrk> set updatecheck_on=false ovcasn01r1:configuration services scrk> set time_updatecheck=7dCommit the configuration changes and then verify that the new settings are correct.
ovcasn01r1:configuration services scrk> commit ovcasn01r1:configuration services scrk> show Properties: <status> = online soa_id = first.last@oracle.com soa_password = ******** proxy_on = true proxy_host = 192.168.4.216:8888 proxy_user = root proxy_password = ******** updatecheck_on = false time_updatecheck = 7d