asr : unable to contact service tags on asset xxxx
Oracle Auto Service Request (ASR) is a nice secure support feature that automatically generates a service request for specific hardware faults. Oracle ASR can improve system availability through expedited diagnostics and priority service request handling.
Unfortunately, to make it work correctly, there are some tips to know and which are not well documented.
ASR is supposed to be configured by the Oracle Database Appliance Manager Configurator (Java-based tool) but, unfortunately, this tool doesn’t test the ASR configuration and moreover it wont tell you anything if something went wrong during the component setup.
Here is what I’ve got after the base configuration:
[root@oda01:/] asr list_asset IP_ADDRESS HOST_NAME SERIAL_NUMBER ASR PROTOCOL SOURCE PRODUCT_NAME --------------- --------------- ----------------- -------- --------- --------- ------------------------------ 10.248.4.71 oda01 XXXXXML0CR Enabled SNMP FMA SUN FIRE X4170 M3 x86/x64 System 10.248.4.70 oda02 XXXXXML0FH Enabled SNMP FMA SUN FIRE X4170 M3 x86/x64 System Please use My Oracle Support 'http://support.oracle.com' to view the activation status.
Everything looks good but, in fact, it’s not ! You may ask why ?
Because… the asset list is also supposed to include the ILOM interfaces !
Here is the expected result:
[root@oda01:/] asr list_asset IP_ADDRESS HOST_NAME SERIAL_NUMBER ASR PROTOCOL SOURCE PRODUCT_NAME --------------- --------------- ----------------- -------- --------- --------- ------------------------------ 10.100.177.136 oda01ilom XXXXXML0CR Enabled SNMP ILOM SUN FIRE X4170 M3 10.248.4.71 oda01 XXXXXML0CR Enabled SNMP FMA SUN FIRE X4170 M3 x86/x64 System 10.100.177.135 oda02ilom XXXXXML0FH Enabled SNMP ILOM SUN FIRE X4170 M3 10.248.4.70 oda02 XXXXXML0FH Enabled SNMP FMA SUN FIRE X4170 M3 x86/x64 System Please use My Oracle Support 'http://support.oracle.com' to view the activation status.
PS. Keep in mind that FMA = Fault Management Architecture, this mechanism diagnoses and predicts component failures before they actually occur. This technology is incorporated into both the hardware and software of the server.
Ok so now, let’s see what’s wrong.
In fact, as you can see on the schema hereafter, the ilom interface(s) and bond0 are not on the same network and no luck, there is a firewall inbetween.
That’s the point, the ilom interface(s) needs to be able to talk to the ASR agent located on the O/S. Indeed, even if it’s ilom which detect any hardware failure, it will always send it (in snmp) to the ASR agent which will deal with and will send the alarm to Oracle.
That’s why when trying to add the interface manually, I’m getting the following error message:
[root@oda01:/] /opt/SUNWswasr/bin/asr activate_asset -h oda01ilom Unable to contact Service Tags on asset oda01ilom Please check if Service Tags is installed, running, and network accessible.
So, now, let’s see which port(s) needs to be open.
First, you can verified which port is used and configured for ASR via these commands.
[root@oda01:~] ipmitool sunoem cli "show /SP/alertmgmt/rules/1" Connected. Use ^D to exit. -> show /SP/alertmgmt/rules/1 /SP/alertmgmt/rules/1 Targets: Properties: type = snmptrap level = minor destination = 10.248.4.71 destination_port = 1162 <-------------- community_or_username = public snmp_version = 2c testrule = (Cannot show property) Commands: cd set show -> Session closed [root@oda01:~] cat /opt/oracle/oak/conf/asr.conf 10.248.4.71; 1 ; public ; 1162
So the first port to open is the 1162. This is the ASR SNMP Port.
The second one is the Service Tags listener used for Asset activation (supposed hence to be used only one time), this remains always the same and this is the 6481.
OK so now, we just have to open these ports and to test again:
[root@oda01:/] /opt/SUNWswasr/bin/asr activate_asset -h oda01ilom Successfully submitted activation for the asset Host Name: oda01ilom IP Address: 10.100.177.136 Serial Number: XXXXXML0FH 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 comple 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.
Now that every components are correctly dealt by ASR, let’s generate some test alarms.
To this end, there are 2 possibilities:
The first one is to generate an alarm from the ILOM interface and the second one directly from ASR.
Anyway, both will generate the same alarm and you should receive an email just telling you that the test is successful 😀
[root@oda01:/] ipmitool sunoem cli "set /SP/alertmgmt/rules/1 testrule=true" Connected. Use ^D to exit. -> set /SP/alertmgmt/rules/1 testrule=true Set 'testrule' to 'true' -> Session closed Disconnected [root@oda01:/] oakcli test asr Please select one of the following to generate ASR test trap[1 .. 4]: 1 => Generate snmptrap test alert from ilom management 2 => Generate disk alert test 3 => Generate TESTSRCREATE snmptrap 4 => Generate test trap using 'oakcli test pd_xx BAD' 1 Setting Asr log level to Fine. Wait ... ASR log level is already set to Fine Successfully set alertmanagement property 'testrule' to 'true' Generated and sent test trap successfully using snmptrap test alert from ilom management Please check the log files "/var/opt/SUNWsasm/log/sw-asr-accepted.log.*" at ASR Manager Host
That’s all Folks 🙂
You will find extra information on the Oracle website:
Leave a comment