ASR assets are qualified systems that are configured to report its hardware telemetry to an ASR Manager. For a complete list of hardware qualified for ASR, see:
http://docs.oracle.com/cd/E37710_01/nav/products.htm
This chapter provides the instructions to configure ASR assets running Oracle Solaris. Keep in mind that an active ASR Manager must be installed before configuring ASR assets. Configuring an ASR asset involves the following steps:
Verifying Assets in My Oracle Support. Your ASR Assets must be associated with a Support Identifier in My Oracle Support.
Installing Software - Solaris 10 Only. For ASR Assets running Solaris 10, you may need to install Services Tools Bundle.
Note:
As part of the ASR 5.0 release, the following directories have changed:The /opt/SUNWswasr directory is replaced by the /opt/asrmanager directory.
The /var/opt/SUNWsasm directory is replaced by the /var/opt/asrmanager directory.
Once you have access to your appropriate support identifier, you can review all hardware assets associated with it. To ensure that all ASR assets are associated with your support identifier:
Log in to My Oracle Support (https://support.oracle.com).
In the My Oracle Support Dashboard, select Settings from the More menu.
In the Settings pane on the left of the window, select Assets (located under the Administrative submenu). All assets associated with your support identifier will display.
The last column of the table shows the asset's ASR Status. There can be four values for this field:
Active: ASR is active for this asset.
Inactive: the asset has the correct ASR software installed, but it is not active. Assets can be set to inactive for any number of reasons (e.g., asset maintenance, patch updates, contract expiration).
Pending: the asset has the correct ASR software installed, but has not yet been enabled (see Approve ASR Assets in My Oracle Support).
[Empty]: The asset has not sent an ASR activation request to Oracle.
You can view information about a particular asset, and in some cases, you can update information about the asset. To view the information, click the asset's serial number. You can update the following content:
Asset Name: you can give the asset an alias to help system administrators readily identify a particular system. This option can be useful if there are many qualified assets associated with the support identifier or if you want to specifically call out an ASR Master system.
Contact Name: the name of the person responsible for the particular machine. This name should be either a system administrator, primary developer, etc. All assets configured for ASR must have a contact name. An asset cannot be enabled without this information. The Contact's Customer Support Identifier must be approved in My Oracle Support in order for the Contact to view assets.
Address: the address fields should indicate the location of the asset.
Note:
For more information on how to use My Oracle Support, click the Help link in the upper-right-hand corner.My Oracle Support includes a Message Center to show when a user action is required. If you have the correct association to a support identifier, then you will receive a message when the following ASR actions are required:
Show Assets with ASR 'No Heartbeat' Issue
This message indicates a network or connection problem with the ASR asset.
Approve ASR Assets
As new qualified hardware is associated with a support identifier, they need to be approved to be ASR assets. This message shows when an ASR asset is awaiting approval. The ASR service will not be enabled for the asset until it is approved in My Oracle Support.
If your ASR assets are running Solaris 10, then you will need to install Services Tools Bundle (STB) to enable ASR telemetry. Also, if your ASR Asset does not use ILOM for telemetry, you will need to use the asrassetmenu.sh script, which is included in the ASR Asset Bundle, to configure the asset.
Note:
If your ASR Asset system is running Solaris 11, then you can skip this section. See Activate and Register ASR Assets for Solaris 11 Systems.STB is a tool set that helps ASR obtain required information from each ASR system before you can activate them, such as obtaining the system's serial number from firmware. Follow the instructions below to install STB.
Note:
If your ASR Asset system is running Solaris 11, then STB is not required to enable ASR telemetry. However, STB is required to enable Oracle Proactive Services.Download and untar the STB bundle that is appropriate for your platform. See Oracle Services Tools Bundle (STB) - RDA/Explorer, SNEEP, ACT (Doc ID 1153444.1) to download the latest Oracle Service Tool Bundle (STB) software from My Oracle Support:
https://support.oracle.com/rs?type=doc&id=1153444.1
On the system where ASR is to be installed, open a terminal window and log in as root.
Run the install_stb.sh script. You may have to change shells to sh if the file does not execute. Also, you may have to set execute permissions on the file, as shown below:
sh chmod +x install_stb.sh ./install_stb.sh
Note:
STB will install all applications bundles by default. You can downgrade applications when invoked with the-force option in non-interactive mode. Run install_stb.sh -? to view all installation options.STB version 6.0 and higher defaults to installing all tools, a "yes" (y) response is already selected for you. As the installation progresses, you will be prompted for confirmation that you wish to install the tools.
When prompted: ”Would you like to (I)nstall, (X)tract component selections, or (E)xit,” press [Enter].
To confirm that STB is installed correctly, and that it is reporting your system's serial number correctly, run:
sneep -a
If the serial number for your system is incorrect, contact Oracle Support to resolve this problem.
Run the following command to be sure that STB is reporting your system attributes correctly:
stclient -Ex
Be sure that the following attributes are reporting as indicated:
<agent_version> must be 5.2 or above
<system> must be SunOS
<platform> must be your platform type
<serial_number> must be the serial number of your system
<product_name> must be Solaris Operating System
<container>global
<source> must be SUNWstosreg
<container>global
<source> must be SUNWsthwreg
If you are not getting the correct data, re-install STB.
Note:
If your ASR Asset does not require Solaris 10 FMA fault telemetry or uses XSCF (see Enabling M-Series XSCF Telemetry), then skip this section.The ASR Asset Bundle includes the asrassetmenu.sh script used to configure an SNMP trap host for Solaris 10 FMA on assets requiring this fault telemetry. If your asset does not require this fault source, then it does not need to be installed.
To access and install the ASR asset bundle:
Open a terminal window and log in as root on the system where the ASR Manager is installed.
Go to /opt/asrmanager/asrassetbundle directory and copy the ASRAssetBundle.<version_num-timestamp>.tar.gz file to all systems that you have identified as ASR assets.
You can copy the file to an NFS location or use a provisioning tool to distribute the file to a group of assets. Copy the ASR Asset Bundle file to any directory on the system, such as /opt or /tmp.
On each ASR asset, open a terminal window and log in as root.
Go to the directory where you copied the ASR Asset Bundle file and unzip and untar the file:
tar -xvf ASRAssetBundle.<version_num-timestamp>.tar
These procedures enable telemetry sources on your ASR assets to send hardware telemetry data to Oracle through the ASR Manager. You should have already verified what telemetry sources reside on the system, as explained in Verifying Telemetry. Depending upon what telemetry sources reside on your system, complete one or more of the following procedures:
Note:
If you want to use the ASR Manager as an asset, too, then telemetry reporting will need to be configured.If you have completed installing the ASR Manager and need to set-up telemetry reporting on the ASR Manager, go to Verifying Telemetry.
Make sure you are logged in as root on the system whose telemetry you wish to enable. This could be either an ASR Manager or an ASR asset system.
Go to the directory where you untarred the ASR asset bundle file, and then go to the specific ASR asset bundle directory. For example:
On an ASR asset: cd /file_copy_location/asrassetbundle
On an ASR Manager: cd /opt/asrmanager/asrassetbundle
Launch the ASR asset menu. As root, run the following command to display the ASR asset menu:
# ./asrassetmenu.sh Welcome to the ASR asset menu ---------------------------------------------- 1) Add a trap-destination to FMA agent 2) Remove a trap-destination from FMA agent 3) List FMA agent trap-destinations 4) Test event to verify ASR connectivity 5) Exit Please enter your selection [1-5]
Select 1 to enable FMA telemetry. Respond to the script's prompts as follows:
Please enter Hostname or IP address of ASR Manager (q to quit)
Enter the information for the ASR Manager. Whether you are enabling telemetry on the ASR Manager system or on ASR asset systems, the host name or IP entered must be for the installed ASR Manager.
Please enter SNMP port of ASR Manager (q to quit)
Press [Return] or enter another port if you have changed your port settings for ASR.
Do you want to set trap-destination [y,n,q]
Confirm the displayed information, enter Y, and press [Return].
The ASR asset menu then enables the telemetry and displays where the telemetry from this system will be sent (IP or host name of the ASR Manager).
Repeat for all ASR assets using Solaris 10 FMA telemetry.
You can incorporate ASR asset configuration into your automated provisioning process. The asrassetmenu.sh script includes command line options for setting Solaris 10 FMA trap destinations. To set a Solaris 10 FMA trap destination from the command line:
asrassetmenu.sh -solaris [destination_IP_address] [port_number]
The asrassetmenu.sh script will exit with an error status value for any of these conditions:
[destination_IP_address] not provided
[port_number] not provided
Trap destination unable to be set
SNMPget Port and community StringFMA telemetry sources (including Solaris 10) are configured to send SNMP traps to the ASR Manager when faults occur. The ASR Manager then queries the asset for fault event details using SNMPget using default port and SNMP community string. The port and community string can be changed for all assets:
Change the port number:
To show the existing FMA enrichment port:
asr> get_property snmp.request.port
To change the port:
asr> set_property snmp.request.port <port_number>
Change the community string:
To show the community string:
asr> get_property snmp.request.community
To change the community string:
asr> set_property snmp.request.community <community_string>
Restart ASR for the changes to take effect:
asr> stop asr> start
Configuration and activation of Solaris 11 ASR assets are performed concurrently. See Activate and Register ASR Assets for Solaris 11 Systems.
To enable ILOM telemetry, it must first be set up, configured, and confirmed. Do not continue with the installation unless you have confirmed the initial ILOM setup. You will need the ILOM service processor IP address to enable ILOM telemetry. Enabling ILOM telemetry involves the following steps:
For complete details on configuring ILOM to send telemetry information, refer to your ILOM documentation.
ILOM requires a network connection/route to the ASR Manager system. If you know that ILOM is already set-up and connected to the network, continue to the next step. Otherwise, continue with the tasks below.
A network connection must be made from the Net Management port on the system's service processor (SP) to the network.
An IP address must be assigned to the Net Management port. Obtain and make note of this IP address for later use in the installation.
For some systems, ILOM can be connected using Sideband Management. ILOM Sideband Management allows the same ILOM IP address to be used, but it is routed through one of the host Ethernet ports, thus eliminating the need for the physical connection to the ILOM Net Management ports. If you want to configure your ILOM system for Sideband Management, go to Optional ILOM Setup: ILOM Sideband Management. When complete, return and continue with the following instructions.
If it is not possible to connect to the ILOM network port and your system does not support Sideband Management, OHMP telemetry can be configured on the host to generate telemetry for ILOM-diagnosed faults.
ILOM telemetry supports the SNMP v3 security protocol. SNMP v3 provides security (encryption and authentication) for any communication to an ASR asset.
The minimum version of ILOM that supports the AES privacy protocol for SNMP v3 is ILOM 3.0.16 and later.
Log in to the ILOM service processor as root and change to the snmp directory:
cd /SP/services/snmp
Set a value for the engine ID:
set engineid=<engineId>
For example:
set engineid=engineid1234
Note:
The value ofengineid must be 25 characters or less.To configure your qualified ASR assets to use SNMP v3 with ILOM telemetry:
Verify your ILOM service processor can support SNMP v3. Log in to the ILOM service processor IP as root. Run the version command.
The ILOM version must be 3.0.16 or later to use SNMP v3.
Create an SNMP v3 user:
cd /SP/services/snmp/users create <UserName> authenticationprotocol=SHA authenticationpassword=<password> privacyprotocol=AES privacypassword=<password>
This user is the same created earlier in Configuring ASR Manager for SNMP v3.
Set SNMP v3 to send telemetry to the ASR Manager:
cd /SP/alertmgmt/rules/<x>
Where <x> is the alert rule slot. Refer to Enable ILOM: Command Line Interface to find the specific alert rule slot of your ILOM.
set type=snmptrap level=minor destination=<ASR Manager IP address> destination_port=162 community_or_username=<SNMP v3 user name> snmp_version=3
See Create Test Alert - ILOM to test the configuration.
Verify that the test alert is received to the ASR Manager. Check for the test alert in the ASR Manager log file:
/var/opt/asrmanager/log
Check that you have received the test Service Request confirmation e-mail. For examples of Service Request e-mail, see Auto Service Request (ASR) Email Examples (Doc ID 1963725.1) available in My Oracle Support (https://support.oracle.com):
https://support.oracle.com/rs?type=doc&id=1963725.1
ILOM Sideband Management allows ILOM telemetry to be routed through a Host Ethernet port. This shared connection using the Host Ethernet port eliminates the physical connection required for the ILOM Net Management port.
Note:
Connection to the service processor usingssh or the web interface may be lost during configuration of Sideband Management.The default ILOM network connection is through the Service Processor's dedicated network port.
Note:
ILOM Sideband Management is currently available for specific Oracle x64 and CoolThreads servers. See the list of hardware qualified for ASR for more information:http://www.oracle.com/technetwork/systems/asr/documentation/index.html
Log in to the host and confirm the mac address:
# ifconfig -a
Note:
Make sure to set the ILOM port to a connected and configured Host Ethernet port. The mac address obtained from the host is the Ethernet port that should be used.Log in to ILOM and configure ILOM trap destination to the ASR Manager. See Enable ILOM: GUI Interface or Enable ILOM: Command Line Interface for details.
Configure the ILOM for Sideband Management; select the Configuration tab and then the Network tab.
Select the ILOM Sideband Management Port by using the drop-down list to activate the desired management port. The drop-down list allows the user to change to any of the four Host Ethernet ports /SYS/MB/NETx, where x is 0 to 3.
Click Save for the changes to take effect.
The Oracle Hardware Management Pack (OHMP) allows ILOM events to be captured by the Host and forwarded through the Host network connection. This eliminates the need to network the Service Processor. The host must be configured and activated for ASR to properly forward ILOM telemetry.
Note:
The OHMP for ASR is only available for certain systems using Solaris 10. For more information about specific systems visit the Oracle ASR product page (http://www.oracle.com/asr).
The host must be activated for ASR and trap destinations configured.
Configure the host trap destination to the ASR Manager as described in Enabling FMA Telemetry for Solaris 10 ASR Assets.
Download and install the latest Oracle Service Hardware Management Pack. To download OHMP:
Log in to My Oracle Support (https://support.oracle.com).
Click the Patches & Updates tab.
In the Patch Search pane, click Product or Family (Advanced Search).
Enter Oracle Hardware Management Pack in the Product field.
In the Release drop-down menu, select the release of OHMP you want to download and click the Search button.
In the Search Results, click the Patch ID number that corresponds to your operating system (the applicable operating system is shown in the Patch description).
In the patch description, click the Download button to download the patch
Use the Oracle Hardware Management Pack Installation Guide to install OHMP. Please note the reference to CR 6977584 (Unix Installer Issue) in the Installation Issues section of the manual. When using the OHMP installer, if the installation aborts, it is likely to be due to this defect. There are two workarounds for this defect:
Use the command unsetenv DISPLAY to unset the DISPLAY variable before running the installer. The unsetenv command runs in the C shell.
Install the required components of OHMP manually rather than using the OHMP installer. The procedure for manual component installation is included in the Oracle Hardware Management Pack Installation Guide. The packages required to support OHMP telemetry are:
ORCLhmp-libs ORCLhmp-snmp ORCLhmp-hwmgmt
Refer to the list of qualified servers to determine if the version of ILOM running on your platform is supported by ASR.
Use ssh to the IP address of the ILOM network interface and log in as root.
ssh [IP_Address_of_ILOM_Interface]
Run the following command:
show /SP
or
version
Note:
If the product version is earlier than 2.x, upgrade it now to the latest ILOM version using your ILOM documentation for instructions.ASR installers have the choice of using a web-based GUI or a command-line interface to enable ILOM telemetry. Follow the procedure below for the GUI method. If command-line is desired, go to Enable ILOM: Command Line Interface.
Note:
If using OHMP, then skip this section.From a web browser, access the IP address of the ILOM interface (note: https):
https://IP_Address_of_ILOM_Interface
Log in as root.
From the menu, select Configuration, then select Alert Management.
Note:
If using ILOM on a Sun Blade 6000 series, select CMM from the left navigation pane, then select Configuration, and Alert Management.The Alert Setting screen lists 15 possible Alert IDs that can be configured to send ILOM telemetry. Alert ID slots that are occupied by existing alert settings are shown along with their alert parameters. Choose an Alert ID that is not used by selecting the radio button next to the Alert ID number.
Note:
Unused Alert IDs are mainly indicated by the disable setting in the Level column and by all zeros in the Destination Summary column.Select Edit from the Actions pull-down menu.
Note:
If using ILOM on a Sun Blade 6000 series, select the Edit button from the top of the screen.Enter data in this screen as follows:
Level: Select Minor from the pull-down menu. If removing an ILOM trap, select Disable.
Type: Select SNMP Trap from the pull-down menu.
IP Address: Enter the IP Address of the ASR Manager system.
Destination Port: Set to port 162. For ILOM versions 2.0.4.2 or lower, the port cannot be changed from the default (162).
SNMP Version: Select v2c from the pull-down menu.
Note:
If you are using ILOM 3.0.16 or above and want to enable SNMP v3, refer to Optional ILOM Setup: SNMP v3 for ASR Assets.Community Name: Enter public in the text entry field.
Click the Save button.
Repeat for each ASR asset required for ILOM telemetry.
If you have enabled all telemetry sources on an ASR Asset system, go to Activating ASR Assets.
Follow these ILOM command line procedures below to enable ILOM telemetry. If you used the GUI method, as described in the previous procedure, you do not need to complete these steps.
Note:
If using OHMP, then skip this section.Open a terminal window and ssh to the IP address of the ILOM network interface:
ssh IP_address_of_ILOM_interface
Log in as root.
Before enabling ILOM telemetry, it is important to understand that ILOM supports up to 15 user-configurable alert rules. It is one of these rules you must set to enable ILOM telemetry. Therefore, you must first choose one of these rules (1 to 15) to set. Before choosing, however, you must determine that the rule you select is not currently being used. You can use the web-based GUI method to determine this quickly, as discussed in Enable ILOM: GUI Interface. Otherwise, run the following command to determine an available alert rule slot.
For Rack Mount Servers and Blades:
-> show /SP/alertmgmt/rules/x
For the Sun Blade 6000 Chassis:
-> show /CMM/alertmgmt/rules/x
Important:
Substitute x for a rule number (1 to 15). If you see that a rule level is set to anything else but disabled, the alert rule slot is occupied. Rerun the command above and substitute the rule number with the next number in sequence (for example, 2, then 3, etc.) until you find an available alert rule slot.Once an alert rule slot is determined, run one of the following commands. Pay close attention to the following data entry points before running the command:
rules/x: For x, enter a number from 1 to 15, depending upon which alert rule slot you have determined is unoccupied using the previous step.
destination: Enter the IP address of the ASR Manager.
destination_port: Set to 162. For ILOM versions 2.0.4.2 or lower, the port cannot be changed from the default (162).
Note:
If you are removing a trap, set the level parameter todisable.For Rack Mount Servers and Blades:
-> set /SP/alertmgmt/rules/x type=snmptrap level=minor destination=[IP_of_ASR Manager] snmp_version=2c community_or_username=public destination_port=162
For the Sun Blade 6000 Chassis:
-> set /CMM/alertmgmt/rules/x type=snmptrap level=minor destination=[IP_of_ASR Manager] snmp_version=2c community_or_username=public destination_port=162
Note:
If you are using ILOM 3.0.16 or above and want to enable SNMP v3, refer to Optional ILOM Setup: SNMP v3 for ASR Assets.Repeat for each ASR Asset using ILOM telemetry.
Follow the procedures below to enable M-Series XSCF telemetry. It is assumed that a network connection to the platform's dedicated service processor (SP) is connected and configured. Do not continue with the installation unless you have confirmed the initial XSCF set-up.
Note:
Both of the M-Series XSCF service processors should be activated for ASR with their individual IP addresses used to send SNMP traps to the ASR Manager, not the failover address shared by both XSCFs.Also, as SNMP is running only on the active XSCF, a switch of the standby XSCF to the Active role is required to activate both service processors for ASR.
This procedure can also be used to remove XSCF trap destinations. For more information on XSCF, refer to the XSCF User Guide for SPARC Enterprise M3000/M4000/M5000/M8000/M9000 Servers.
Open a terminal window and initiate an ssh connection to the IP address of the XSCF network interface:
ssh IP_address_of_XSCF_interface
Log in to the XSCF console. Make sure you have platadm privileges, (run showuser -p <login name>). You can run showuser -p for a list of users with this privilege.
Disable the SNMP agent:
XSCF> setsnmp disable
Add the ASR Manager system as the trap destination:
To configure an M-Series server for SNMP v2c, run the following command:
XSCF>setsnmp addtraphost -t v2 -s public -p 162 xxx.xxx.xxx.xxx
Where:
-s = community string (default value is public)
-p = SNMP listener port (value should always be 162)
xxx.xxx.xxx.xxx = ASR Manager IP address
If you wish to remove an XSCF trap destination, run the following command to stop XSCF from sending telemetry to the ASR Manager system:
XSCF>setsnmp remtraphost -t v2 xxx.xxx.xxx.xxx
Where:
xxx.xxx.xxx.xxx = ASR Manager IP address
To configure an M-Series server for SNMP v3, run the following commands:
XSCF> setsnmpusm create -a SHA <UserName> Enter the trap authentication passphrase: Enter the trap encryption passphrase: XSCF> setsnmp addv3traphost -u <UserName> -r SHA -n <engineId> -p 162 xx.xxx.xxx.xxx Enter the trap authentication passphrase. Enter the trap encryption passphrase.
Where:
-n = SNMPv3 engine ID (must be an even amount of hexidecimal digits starting with 0x)
-p = SNMPv3 listener port (value should always be 162)
-r = authentication protocol (value should always be SHA)
-u = SNMPv3 user name
xxx.xxx.xxx.xxx = ASR Manager IP address
M-Series XSCF SNMP v3 uses the DES encryption protocol by default.
For more information, see Configuring ASR Manager for SNMP v3.
Enable the SNMP agent:
XSCF> setsnmp enable
Enable SNMP v1v2:
XSCF> setsnmp enablev1v2c <community>
community is the community string and should always be set to public.
Note:
See M-Series Servers XSCF SNMP GET Troubleshooting for troubleshooting information.Verify SNMP settings to make sure the trap destination is set, SNMP is enabled, and the FM MIB is enabled:
XSCF> showsnmp Agent Status: Enabled Agent Port: 161 System Location: Unknown System Contact: Unknown System Description: Unknown Trap Hosts: Hostname Port Type Community String Username Auth Protocol --------------- ---- ---- ---------------- -------- ------------- xxx.xxx.xxx.xxx 162 v2 public n/a n/a SNMP V1/V2c: Status: Enabled Community String: public Enabled MIB Modules: SP MIB FM MIB
Verify SNMP GET functionality. On the ASR manager, execute the following command:
asr> test_snmp_get -i <ip address of Active XSCF>
or
asr> test_snmp_get -h <host name of Active XSCF>
Note:
SNMP only runs on the active XSCF. Thetest_snmp_get command will fail if run against the standby XSCF.
The test_snmp_get command does not currently support SNMPv3.
Repeat for each M-Series ASR asset required for XSCF telemetry.
Follow the procedures below to enable Fujitsu M10 XSCF telemetry. It is assumed that a network connection to the platform's dedicated service processor (SP) is connected and configured. Do not continue with the installation unless you have confirmed the initial XSCF set-up.
Open a terminal window and initiate an ssh connection to the IP address of the XSCF 0 (LAN#0) network interface. For Building Block (BB) M10-4S configurations, this will be the IP address of LAN#0 of the Master XSCF (that is, the XSCF installed in either BB#00 or XBBOX#80, depending on the BB configuration):
ssh -l <login name> <IP_address_of_XSCF_interface>
Log in to the XSCF console. Make sure you have platadm privileges, (run showuser -p <login name>). You can run showuser -p for a list of users with this privilege.
Disable the SNMP agent:
XSCF> setsnmp disable
Add the ASR Manager system as the trap destination.
Configure Fujitsu M10 for SNMP v2c:
XSCF>setsnmp addtraphost -t v2 -s public -p 162 xx.xxx.xxx.xx
Where:
-s = community string (default value is public)
-p = SNMP trap port (value should always be 162)
Note:
The-p option can be ignored if so wished. The trap port will default to 162 on the Fujitsu M10 server.xx.xxx.xxx.xx = ASR Manager IP address
If you wish to remove an XSCF trap destination, run the following command to stop XSCF from sending telemetry to the ASR Manager system:
XSCF>setsnmp remtraphost -t v2 xx.xxx.xxx.xx
Where:
xx.xxx.xxx.xx = ASR Manager IP address
Enable the SNMP v1v2:
XSCF> setsnmp enablev1v2c <community>
Where:
<community> = community string and should always be set to public
Configure Fujitsu M10 for SNMP v3:
Configure SNMP v3 trap:
XSCF> setsnmp addv3traphost -u <UserName> -r SHA -n <engineId> -x AES xx.xxx.xxx.xxx
Enter the trap authentication passphrase.
Enter the trap encryption passphrase.
For more information, see Configuring ASR Manager for SNMP v3.
Verify SNMP settings to make sure the trap destination is set, SNMP is enabled, and the FM MIB is enabled:
XSCF> showsnmp Agent Status: Enabled Agent Port: 161 System Location: Unknown System Contact: Unknown System Description: Unknown Trap Hosts: Hostname Port Type Community String Username Auth Protocol ------------- ---- ---- ---------------- -------- ------------- xx.xxx.xxx.xx 162 v2 public n/a n/a SNMP V1/V2c: Status: Enabled Community String: public Enabled MIB Modules: SP MIB
Enable the SNMP agent:
XSCF> setsnmp enable
Once the Fujitsu M10 asset is activated/approved in My Oracle Support, send a test trap. To send a test trap from M10 XSCF, run:
XSCF> rastest -c test
Repeat for each Fujitsu M10 ASR Asset required for XSCF telemetry.
Note:
An activation event will be sent to Oracle ASR infrastructure as soon as the trap destination is configured to an ASR Manager. You do not need to activate it on the ASR Manager.Once ASR assets are activated, they will need to be enabled in My Oracle Support (see Approve ASR Assets in My Oracle Support). All assets to be activated should already have telemetry trap destinations set, as described in Enabling Telemetry Sources.
Some ASR assets are activated differently:
All other ASR asset systems are activated following the procedure below:
Note:
To enter the ASR prompt as root, typeasr on the command line. See Installing ASR Manager Software for instructions for setting the PATH environment variable.Open a terminal window and log in as root on the ASR Manager system.
Important:
Activating ASR assets is not done on the assets themselves, but rather on the ASR Manager system only.Run the following activate command for each ASR asset. Be sure to use the IP or host name of the ASR asset system.
asr> activate_asset -i [IP address]
or
asr> activate_asset -h [host name]
Log in to My Oracle Support to complete the activation process. See Approve ASR Assets in My Oracle Support for details.
Auto Activation:
If the ASR Manager receives fault telemetry from an asset that has not been previously activated, ASR automatically attempts to activate the asset as if theasr activate_asset command is executed.Use the following procedure to activate a Sun Blade system. Keep in mind that Blade systems also include the chassis within which the Blade systems are installed. Therefore, when activating, the Blade and the chassis must be activated. Chassis telemetry reports power and environmental faults, and blade telemetry reports faults specific to the blade's subsystems.
You will need the Blade serial number of the Blade chassis and the Blade systems in order to complete this procedure.
Open a terminal window and log in as root on the ASR Manager system. Important: Activating ASR Assets is not done on the assets themselves but on the ASR Manager system only.
Note:
If activating an X627x system, see Sun Blade X627x Configuration.Activate the Blade Chassis:
asr> activate_asset -i [Chassis_IP]
Activate the Blade System:
asr> activate_blade -i [Blade_IP] -c [Chassis_IP]
Repeat the activate_blade command for each Blade within the chassis that you desire to have under ASR management. Keep in mind that the Blade systems must be qualified for ASR, as specified in Qualified Sun Blade Servers:
http://docs.oracle.com/cd/E37710_01/doc.41/e37285/ch2_sun-blade.htm#QPSVR147
Log in to My Oracle Support to complete the activation process. See Approve ASR Assets in My Oracle Support for details.
Open a terminal window and log in as root on the ASR Manager system. Important: Activating ASR Assets is not done on the assets themselves but on the ASR Manager system only.
Note:
If activating an X627x system, see Sun Blade X627x Configuration.Activate the Blade Chassis:
asr> activate_asset -i [Chassis_IP]
When activating a Solaris 11 Blade host, the asradm register command must first be run on the Blade (see Activate and Register ASR Assets for Solaris 11 Systems). Following this, verify the Blade has a status of "Pending" by using the list_asset command from the ASR Manager. Copy the blade's serial number from the output of list_asset and paste for the [Blade_Serial] value. Activate the Blade System:
asr> activate_blade -s [Blade_Serial] -c [Chassis_IP]
Repeat the activate_blade command for each Blade within the chassis that you desire to have under ASR management. Keep in mind that the Blade systems must be qualified for ASR, as specified in Qualified Sun Blade Servers:
http://docs.oracle.com/cd/E37710_01/doc.41/e37285/ch2_sun-blade.htm#QPSVR147
Log in to My Oracle Support to complete the activation process. See Approve ASR Assets in My Oracle Support for details.
For the Sun X627x Blades, both the host and the service processor are ASR telemetry sources.
Note:
The Sun Blade X6275 and Sun Blade X6275 M2 servers have two Service Processors that should be configured and activated for ASR using the steps described above. Also, each blade server has two Hosts than can be configured as a secondary telemetry sourceSun Blade X627x Service Processors
Activate each Sun Blade X627x Service Processor with the command:
activate_blade -i [Service_Processor_IP] -c [Chassis_IP]
Sun Blade X627x Hosts
For Sun Blade X527x hosts, see the instructions in ASR Activation on Blade Systems and Chassis - Solaris 10 Only or ASR Activation on Blade Systems and Chassis - Solaris 11 Only depending on whether the host is running Solaris 10 or Solaris 11.
Refer to the Quick Installation Guide for Oracle Exadata Database Machine for complete information about activating ASR on Exadata Database Machines:
http://docs.oracle.com/cd/E37710_01/doc.41/e23333/toc.htm
To activate Exadata assets, run the following command:
activate_exadata [-i exadataip -h exadatahostname -l ilomip] [-?]
or
activate_exadata [-i exadataip -h exadatahostname -n ilomhostname] [-?]
The parameters are:
-i exadataip - The IP address of the database server host or storage cell.
-h exadatahostname - The host name of the database server host or storage cell.
-l ilomip - The IP address of the ILOM corresponding to the database server host or storage cell.
-n ilomhostname - The host name of the ILOM corresponding to the database server host or storage cell.
-? - Help (optional), displays help information.
Note:
For details on enabling Oracle Auto Service Request on the Oracle Exadata servers, refer to the Oracle Exadata documentation.To activate ASR on Exalogic OpenStorage Assets, use the embedded system management GUI. This is the same method for activating ASR on a standalone Sun Unified Storage 7xxx product.
To activate ASR on each Exalogic X4170 M2 server, use the asr activate_asset command from the ASR Manager. See Enabling ILOM Telemetry to configure SNMP trap destinations on each of the ILOMs.
Follow the steps below to active ASR assets for Solaris 11 systems:
Log in to the ASR asset as the root user.
Run the following command to register the endpoint URL:
For the endpoint URL to be the ASR Manager:
asradm register -e http://[asr_manager_host]:[port_number]/asr
The [port_number] is the same port that was specified when enable HTTP receiver was done on the ASR Manager (See Enabling HTTP Receiver for ASR Manager Relay, Solaris 11, and SDP2).
For the endpoint URL to be a direct connect back to Oracle:
asradm register
Notes:
Sun Blades does not support the direct connect back to Oracle.
If the same ASR Asset is using ILOM telemetry, the ILOM telemetry must go through the ASR Manager.
Enter your Oracle SSO user name and password.
Run the following command to view the status:
asradm list
The results should appear like this:
# asradm list PROPERTY VALUE Status Successfully Registered with ASR manager System Id <system identification number> Asset Id <asset identification number> User MyUserName Endpoint URL http://<asr_manager_host>:<port_number>/asr #
Note:
For Sun Blade systems, see Activate Blade Assets.Log in to My Oracle support to complete the activation. See Approve ASR Assets in My Oracle Support.
To send a test e-mail, run the following command:
asradm send test <email.address@mycompany.com>
Note:
If you need to unregister and deactivate your ASR asset, run:asradm unregister
The Virtual Operator Panel (VOP) supports Oracle ASR. Refer to the ASR section in Chapter 6, "Using the MD-VOP Interface," of the StorageTek Virtual Operator Panel User's Guide for instructions:
http://docs.oracle.com/cd/E37055_01/index.html
Oracle ASR supports the StorageTek Virtual Storage Manager (VSM). VSM products supported include V2x, V2xf, VSM4, VSM5, and VSM5C.
Note:
You should first install and register the ASR Manager before configuring the VSM as an ASR Asset. See Installing and Registering ASR Manager Software for more information.Unlike other qualified ASR Assets, the setup and configuration of VSM assets requires the involvement of an Oracle Customer Support Engineer (CSE).
To set up and activate the VSM asset for Oracle ASR:
Before configuring the VSM to use the ASR service, collect the following information:
Identify the VSM asset's IP address.
Identify the VSM asset's serial number.
Verify that the VSM asset and the ASR Manager are in the same subnet.
To engage an Oracle CSE to configure the VSM asset, you must submit a Service Request (SR):
Log in to My Oracle Support and submit an SR for an Oracle CSE to configure the VSM for ASR:
https://support.oracle.com
When you submit the SR, include the following information:
VSM asset serial number.
Service Identifier (SI).
Request the CSE reference MOS note ID 1523811.1.
When the Oracle CSE arrives to configure VSM for ASR, be prepared to provide the following VSM asset information:
IP address.
Subnet.
Netmask.
Complete ASR Activation and Verify VSM Configuration
Once the Oracle CSE has configured your VSM asset for ASR, complete ASR activation for VSM devices by running the following commands:
On the ASR Manager, activate the VSM asset with the activate_storage -d command:
To activate a single VSM asset:
asr> activate_storage -d VSM_SVA -i <IP address>
For a successful ASR Asset activation, output should look like this:
Successfully submitted activation for the asset IP Address: <IP address> Serial Number: <serial number> The e-mail address associated with the registration id for this asset's ASR Manager will receive an e-mail highlighting the asset activation status and any additional instructions for completing activation. Please use My Oracle Support http://support.oracle.com to complete the activation process. The Oracle Auto Service Request documentation can be accessed on http://oracle.com/asr.
To activate multiple VSM_SVA assets simultaneously:
asr> activate_storage -d VSM_SVA -i <IP address1>, <IP address2>, <IP address3>, <IP address4>
Output should look like this:
Please wait, discovery is in progress........ Activation process is completed Please run "list_asset" to get the list of discovered assets
Complete the activation of the VSM asset in My Oracle Support. See Approve ASR Assets in My Oracle Support.
Verify the configuration by sending a test ASR message. This step verifies that the configuration of the VSM asset is correct and that connectivity to My Oracle Support is enabled.
From the ASR Manager, run:
asr> send_test -i <VSM's IP address>
Output should look like this:
Submitted test event for asset <serial number> Verification email will be sent to asr_contact@mycompany.com
The e-mail is sent to the registered point of contact for the VSM asset.
To list all of the ASR Assets, run the following command from the ASR Manager:
asr> list_asset
Example 3-1 shows an example of how VSM assets appear in the output.
Example 3-1 ASR list_asset Command - Sample Output
Storage Assets -------------- IP_ADDRESS SERIAL_NUMBER ASR PROTOCOL SOURCE PRODUCT_NAME ----------- ------------- -------- -------- ------ ------------ 12.23.34.45 123456789012 Enabled VSHELL VSM_SVA VSM4 13.31.13.31 123456789013 Enabled VSHELL VSM_SVA VSM4 12.21.12.21 123456789014 Enabled VSHELL VSM_SVA VSM5 Please use My Oracle Support 'http://support.oracle.com' to view the activation status.
To complete the installation of ASR, you will need to log in to My Oracle Support (MOS) and approve ASR for each asset. See the "Approving ASR Activations" section of How To Manage and Approve Pending ASR Assets In My Oracle Support (Doc ID 1329200.1):
https://support.oracle.com/rs?type=doc&id=1329200.1