Oracle Auto Service Request (ASR) is designed to automatically request Oracle service when specific faults occur. This chapter identifies the features and enhancements provided by Oracle Auto Service Request Release 5.4.
The Oracle ASR Manager Release 5.4 software upgrade is quick to install and is available for download from
All customers are urged to upgrade to this release at their earliest convenience. See ASR Manager Auto Update for instructions on how to upgrade to the latest version of the ASR Manager.
Note:Support for Oracle Auto Service Request is limited to the current release and the two previous releases. Oracle now supports ASR 5.4, 5.3, and 5.2.1. It is recommended that you upgrade to the latest version. See ASR Manager Auto Update for more information.
The Oracle Auto Service Request Release 5.4 includes the following features:
Oracle Secure File Transfer (SFT) is now part of ASR Manager. SFT is now part of the ASR Manager download and no longer has a dependency on Oracle Automated Service Manager (OASM). See the Oracle Secure File Transport User's Guide for details.
ASR Manager now supports IPv6 on the customer's network. See ASR Manager on IPv6 for details.
list_asset command has been improved to show asset parent/child relationships (if appropriate and when available) as well as list last heartbeat information.
test_connection command has been updated to include HTTP listener details if it has been enabled.
The local SNMP Service Request (SR) notification capability has been expanded to include notification for any ASR SR updates to an already open SR if desired.
Corrects known issues where ASR auto-update and diagnostic bundle gather does not work for ASR Managers using an ASR Manager Relay.
Adds serial number as a valid argument to the
asr disable command has been enhanced to allow the user to select a time period (1 - 48 hours) for auto enable of the ASR Manager assets after the selected time period. See Disabling and Enabling ASR Auto Update for details.
Corrects a known issue with ASR Manager 5.3 where the first time the
show_version command is run
log4j:WARN warning messages are displayed.
The Oracle Auto Service Request Release 5.3 includes the following features:
The ability to layer ASR Managers (ASRMs) has been added. The following layering scenarios are now supported:
Any http/s ASR client --> ASRM --> Oracle Transport
Any http/s ASR client --> ASRM --> ASRM Relay --> Oracle Transport
AND within a given customer network:
Any http/s ASR client --> ASRMa --> ASRM Relay --> Oracle Transport
Any http/s ASR client --> ASRMb --> ASRM Relay --> Oracle Transport
Any http/s ASR client --> ASRM[n] --> ASRM Relay --> Oracle Transport
All ASR Managers in the examples above have to be ASR version 5.3 or greater.
See Enabling HTTP Receiver for ASR Manager Relay, Solaris 11, and SDP2 for additional details.
Numerous improvements and enhancements to ASR auto-update, including:
Removes the requirement that selinux tools and rpm-build is configured and enabled on Linux systems. Linux sites can now auto update without these components.
Improved error information and messaging.
Corrects two issues with the
-q option not functioning correctly.
Adds checks for leading or trailing spaces and tabs.
Corrects an issue for Solaris sites auto updated from ASR Manager 5.0.3 to ASR Manager 5.2 where the
activate_blade commands are not working.
Corrects an issue where some sites auto updated to ASR Manager 5.2 incorrectly received a warning notification that the auto update process did not complete. This incorrect warning notification will not be received for future auto updates.
Corrects an issue where for some ASR Manager 5.2 sites the
show_version command is resulting in log4j errors being written to the console.
Warning messages for the
show_version command: The first time the
show_version command is run using ASR Manager 5.3,
log4j:WARN warning messages will be displayed. These warnings are benign and can be ignored. Running the command again resolves the issue.
Transport URL change required: The following two end points are no long valid for use:
You may need to update your configuration to use transport.oracle.com (220.127.116.11).
Instructions for how to determine if this change is needed and how to make the change is provided in My Oracle Support (MOS) Doc ID 1954819.1: