| Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback |
| Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
||
 |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Solution Type Technical Instruction Sure Solution 2136384.1 : How to Install and Configure ASR for Netra Modular System (NMS) Image 1.0.1
In this Document
Applies to:Netra Modular System - Version All Versions to All Versions [Release All Releases]Information in this document applies to any platform. GoalThis document contains step to successfully install and configure ASR on NMS image 1.0.1. SolutionIntroduction and Background NMS components consist of up to 30 Compute Nodes, 6 Ethernet Switches, and the FMM. All components contain an ILOM. Each ILOM produces a number of faults. Each ILOM can be configured to take advantage of its fault diagnosis. By capturing then forwarding error telemetry via ASR resulting in Auto creation of service requests. NMS is unique in that the Compute Node, and Switch ILOM’s are only accessed from within the Frame itself. The FMM ILOM does have the ability to connect outside of the Frame. Access is also done from within the Frames internal network. This unique configuration requires that the ASR Manager reside on one of the Compute Nodes. Compute Node Host SW can and does connect outside of the Frame. There are two Compute Nodes known as FSA’s. These are located at elevations 3 and 4. As noted above all the Compute Nodes, Switches, and FMM access ILOM through the internal Frame network. All internal ILOM IP’s are predefined. A list of all IP’s and elevations are in Appendix A. For a tutorial on ASR and all relevant Documentation go here. ASR For NMS Installation and Configuration. NOTE: Support for ASR Requires NMS SW 1.0.1 and ASR 5.0.5
The following sections will show · How to install ASR Manager on an FSA
1.1 Download the current version of SW ASRManager 5.3 - p21479181_530_Linux-x86-64.zip (Download site) 1.2 Uncompress and install ASR Manager SW 1.2.1 # unzip p21479181_530_Linux-x86-64.zip # unzip p21479181_530_Linux-x86-64.zip
Archive: p21479181_530_Linux-x86-64.zip inflating: asrmanager-5.3.0-20150702153106.rpm inflating: license_agreement.htm inflating: readme.html Change to the directory location where the RPM has been copied to. 1.2.2 # rpm -i asrmanager-5.3.0-20150702153106.rpm rpm -i asrmanager-5.3.0-20150702153106.rpm ASR Manager (pid 62070) is RUNNING. The ASR Manager application is installed in '/opt/asrmanager'. Log files are located in '/var/opt/asrmanager'. Checking ASR Manager status ....Installation of asrmanager was successful.
2.1 Start the ASR Manager Menu to Register the ASR Manager with Oracles back end services. # /opt/asrmanager/bin/asr
register OR register [-e asr-manager-relay-url]: register ASR unregister : unregister ASR show_reg_status : show ASR registration status list_registration : list ASR Manager registrations test_connection : test connection to Oracle activate_asset [-i ip] [-h hostname] [-s subnet] [-?] : activates and enables the asset activate_blade [-i bladeIP -c chassisIP] [-?] OR activate_blade [-s bladeSN -c chassisIP] [-?] : activates and enables the blade activate_exadata [-i exadataIP -h exadatahostname -l ilomIP] [-?] OR activate_exadata [-i exadataIP -h exadatahostname -n ilomhostname] [-?] : activates and enables the exadata activate_storage [-d device type] [-i ip] [-?] : activates and enables the Storage Device deactivate_asset [-i ip] [-h hostname] [-s subnet] [-?] : deactivates and deletes the asset enable_asset [-i ip] [-h hostname] [-s subnet] [-?] : enables the asset disable_asset [-i ip] [-h hostname] [-s subnet] [-?] : disables the asset list_asset [-i ip] [-h hostname] [-s subnet] [-hb heartbeat] [-c csv_output] [-?] : lists ASR assets send_test [-i ip] [-h hostname] [-?] : send test alert heartbeat : send ASR Manager heartbeat stop : stop ASR Manager start : start ASR Manager restart : restart ASR Manager status : status of ASR Manager enable_http_receiver : enable HTTP Receiver [-p port] [-?] : Enable HTTP Receiver disable_http_receiver : disable HTTP Receiver show_http_receiver : display current configuration status of HTTP Receiver show_version [-?] : show ASR Manager and rules version Information. autoupdate [-?] : Auto update ASR Manager and rules bundle software. restore [-?] : Restore ASR Manager to previous version. set_notification_trap [-i ipAddress -p port -c community] [-h hostname -p port -c community] [-?] : set ASR Notification trap configuration show_notification_trap : show ASR Notification trap configuration delete_notification_trap [-i ipAddress] [-h hostname] [-?] : delete ASR Notification trap configuration enable_autoupdate [-?] : Enable Auto update. disable_autoupdate [-?] : Disable Auto update. enable_remote_request [-?] : Enable Remote Request feature. disable_remote_request [-?] : Disable Remote Request feature. set_loglevel [trace, debug, info, warn, error] : set the logging level to trace or debug or info or warn or error get_loglevel : get the logging level set_logfilecount [1-20] : set the log file count to any number between 1 and 20 get_logfilecount : get the log file count enable_audit_log : enable audit logging disable_audit_log : disable audit logging set_audit_log_days [1-30] : Set how many days of audit logs to keep before rolling over (accepts any number between 1 to 30) get_audit_log_days : Get how many days of audit logs are kept enable_asr_manager : enable ASR Manager disable_asr_manager : disable ASR Manager add_snmpv3_user -u userName -e engineId[,engineId2, ...] -pp privacyProtocol : Add SNMPv3 user show_snmpv3_user : show SNMPv3 user validate_snmpv3_user : validate SNMPv3 user delete_snmpv3_user : delete SNMPv3 user add_engine_id -e engineId[,engineId2, ...] : add SNMPv3 engineId delete_engine_id -e engineId[,engineId2, ...] : delete SNMPv3 engineId enable_snmpv1v2c : enable SNMPv1/v2c disable_snmpv1v2c : disable SNMPv1/v2c send_diag -sr <SR Number>[-?] : Collect Diagnostics bundle from ASR manager and send it to the Oracle ASR Infrastructure. test_snmp_get [-i ipAddress] [-h hostname] : Test SNMP GET access on the asset for FMA or M-series XSCF show_log_collection_status [-?] : Show Diagnostics file collection/upload status. Usage: set_diag_bundle_dir <Directory Name> : Set the diagnositics bundle directory for temporarily storing SR diag bundles. exit help : display a list of commands ? : display a list of commands asr> register 1) transport.oracle.com If a proxy server is required for HTTPS communication to the internet, enter the information below. If no proxy is needed, enter - An Oracle Single Sign On (OSSO) account is required for data submission. Username []: pxxx.dxxxxx@oracle.com Contacting transport servers. Please wait... ASR Manager Registration complete To configure ASR Manager in a High Availability configuration reference the ASR user and install Guide located here.
Note a: The FMM uses XML as its Telemetry source. The ASR Manager Relay configuration is required to receive XML from the FMM and then forward to Oracles back end services. Before the FMM can be configured the ASR Manager is configured as a relay. Note b: ServiceTag activation for ASR is not supported for the FMM. 3.1 From the ASR Manager Menu enable the ASR Manager as a Relay, using the enable HTTP Receiver and specifying a Port. #/opt/asrmanager/bin/asr asr> show_http_receiver
Note: If DNS is not configured / enabled on the ASR Manager the following error message is received. asr> enable_http_receiver -p 7777 3.1.1 If DNS is not available, then set up the HTTP manually. Run the following commands. # /opt/asrmanager/bin/asr set_property org.osgi.service.http.host <asr manager IP> org.osgi.service.http.host is set to xx.xxx.xxx.xx Verify status asr> show_http_receiver To register an ASR Manager or Solaris 11 server to this ASR Manager Relay, use:
Note: At this time configuring XML as a Telemetry source is not supported.
4.1 ASR Activation. From the ASR Manager Menu activate Compute Nodes. Using each nodes predefined Ilom IP Address for activation. # /opt/asrmanager/bin/asr asr> activate_asset -i 10.10.0.13 After activating compute nodes. Use list_asset to show all activated assets. asr> list_asset IP_ADDRESS HOST_NAME SERIAL_NUMBER ASR PROTOCOL SOURCE PRODUCT_NAME Please use My Oracle Support 'http://support.oracle.com' to view the activation status. Note: You must complete the ASR Activation in MOS. MOS Activation Document found here.
4.2 Configuring SNMP as the Telemetry source Note: Configure alertmgmt rule 3 to forward traps from the compute nodes Ilom to the ASR Manager installed and configured on FSA node. Do NOT use rule 1 or 2. They are reserved for FSA Management SW.
Host IP of the ASR Manager is used to Identify SNMP Trap destination. On each node login to Ilom as root user. -> cd /SP/alertmgmt/rules -> show 3 Commands: 4.3 How to send a Test Trap Logged into the compute node Ilom as root go to rule 3 and initiate creation of test case using testrule. -> cd /SP/alertmgmt/rules/3 -> Test email should be received by MOS owner.
Note: At this time configuring XML as a Telemetry source is not supported.
Configure Switches ES2-64/72 - Minimum switch configuration contains 2 ES2-64. In addition, up to 4 ES2-72 switches are possible. 5.1 ASR Activation. From the ASR Manager Menu activate Switches Using each switches predefined Ilom IP Address for activation. asr> activate_asset -i 10.10.1.12
Switch-Hostname-sp : 1 service tags Successfully submitted activation for the asset Host Name: <switch-hostname>-sp IP Address: 10.10.1.12 Serial Number: A987654321 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. After activating switches. Use list_asset to show all activated assets. asr> list_asset IP_ADDRESS HOST_NAME SERIAL_NUMBER ASR PROTOCOL SOURCE PRODUCT_NAME 5.2 Configure snmp as the Telemetry Source Note: Configure alertmgmt rule 3 to forward traps from the Switches Ilom to the ASR Manager installed and configured on FSA node. Do NOT use rule 1 or 2. They are reserved for FSA Management SW.
Host IP of the ASR Manager is used to Identify SNMP Trap destination. On each switch login to Ilom as root user. -> cd /SP/alertmgmt/rules -> show 3 5.3 How to send a Test Trap Logged into the switch Ilom as root go to rule 3 and initiate creation of test case using testrule. -> cd /SP/alertmgmt/rules/3
-> -> set testrule=true Set 'testrule' to 'true' -> Test email should be received by MOS owner.
6.1 ASR activation and configuring XML Configuring FMM to forward error telemetry in the form of XML over HTTP Note: FMM must use XML as the Telemetry source ServiceTags and snmp is Not supported.
Next configure asr-notify. Configuring asr-notify sets the activation of the FMM and configures XML as the Telemetry source. Note: In this example we are Not using a proxy-host, -user, or -password. If your environment requires a proxy these values will also need to be set. Our configuration will consist of endpoint, username, and password.
Endpoint = FSA hostname or IP address of the FSA where the ASR Manager resides. Login to the FMM Ilom as root -> cd /FMM/clients/asr -> ls Targets: Commands: cd -> set endpoint=http://<ASRM IP Address>:7777/asr username=pxxx.dxxxxx@oracle.com password=userpasswd Set state to enabled Verify state of XML activation -> show /FMM/clients/asr Commands: -> show Commands: Now use list_asset from the asr menu to verify activated assets asr> list_asset IP_ADDRESS HOST_NAME SERIAL_NUMBER ASR PROTOCOL SOURCE PRODUCT_NAME Please use My Oracle Support 'http://support.oracle.com' to view the activation status.
Note: You must complete the ASR Activation in MOS. MOS Activation Document found here.
FMM is now activated on the ASR Manager.
Appendix A – NMS Component Location and IP Address
Attachments This solution has no attachment |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||