Insight Remote Support Advanced for NonStop
example below, 2012 is changed to 2016, extending the expiration date for WEBES to five
years from the current date.
Service Provider Company Name: Hewlett-Packard Company
Service Provider Employee Name: employee_name
Service Provider Employee ID#: 0000000
Please enter new service obligation start date <MMM d, yyyy>[Mar 4, 2011]
Please enter service obligation term end date <MMM d, yyyy>[Mar 3, 2012] Mar 3, 2016
4. Upon entering the new end date, the command displays the new term length (5 years instead
of 1) and prompts you to confirm. A response of “y” completes the command, a response of
“n” repeats the process, allowing you to change the values.
Service Obligation term: 5 years, 0 days, 16 hours, 43 minutes, 9 seconds
Is this correct [y]: y
After responding “y” to complete the command, additional details are displayed (as illustrated
in the example that follows), including the current WEBES obligation settings and history of
changes:
Is this correct [y]: y
Current Obligation Settings:
Service Obligation: Valid
Service Obligation Number: silent
System Serial Number: silent
Service Provider Company Name: Hewlett-Packard Company
Obligation Start Date: Fri Mar 04 07:16:50 MST 2011
Obligation Ending Date: Thu Mar 03 00:00:00 MST 2016
Time left on Obligation: 5 years, 0 days, 16 hours, 42 minutes, 19 seconds
History of changes:
Fri Mar 04 07:17:40 MST 2011: J. Smith (0000000) of Hewlett-Packard Company
Obligation settings changed to start Fri Mar 04 07:16:50 MST 2011 to Thu Mar 03 00:00:00 MST 2016 (5
years, 0 days, 16 hours, 43 minutes, 9 seconds)
...
5. In order for these service obligation changes to take effect, you must stop and restart the
DESTA service, as described under step 4 of the NonStop-Specific Tasks.
NOTE: You can extend the date by performing the command again at any time, but the term
end date can be no greater than five years out from the date that you perform the command.
Remove Incident Report Delivery Paths for Failed CMS or CMS to be
Replaced
This procedure is optional because OSM automatically detects any failed paths to CMS from the
delivery result of the Periodic IRs that are created and sent, by default, every 24 hours. OSM
creates a dial-out alarm “Incident Report Delivery Failure” for the failed path(s). If, after ten days,
the path to a particular CMS remains unresponsive, that path is deleted from the OSM configuration
and OSM no longer tries to send IRs through that path. However, if you are removing or replacing
a CMS and want to avoid receiving failed path EMS events and alarms/dialouts for up to ten days
it would take for those paths to be deleted automatically, you can use the following procedure to
manually delete paths that will no longer be used:
1. If the CMS that will be taken out of service is still accessible and working: from within HP SIM
on that CMS, delete any NonStop system(s) being monitored by Insight Remote Support
Advanced.
2. From any CMS or PC with access, log on to the OSM Service Connection for each NonStop
system that was deleted and perform the Test Incident Report Delivery Paths action (located
under the System object). Reply Yes to the “Delete the failed path” question, then click OK.
3. If you are replacing an old CMS with a new one, discover the NonStop system(s) from within
HP SIM on the new CMS, then complete the NonStop-specific Insight Remote Support Advanced
configuration process, beginning with step 9.
20 Ongoing Operational Considerations