A.05.70 HP Insight Remote Support Advanced and Remote Device Access Security Overview (October 2011, 5900-1735)

C:\Program Files\HP\RemoteSupport\bin> iseeinterfaces.exe -send_support_information -test_event
9F0C94C1-5515-4328-A6C4-CE68FA7A103C
A successful run will return a globally unique identifier (GUID) as shown in the example. Any other return
value is a failure.
2.9.4.2 Remote Support Software Management data center
If the IP addresses were configured in the firewall, connectivity for RSSWM can be verified as follows:
With a web browser on the CMS/host device, connect to the following RSSWM software URLs. You will
see a certificate error, this is expected. Note that on rare occasions a system may not be accessible due to
periodic maintenance and upgrade.
• https://rsswm-software1.atlanta.hp.com/site/
• https://rsswm-software2.atlanta.hp.com/site/
• https://rsswm-software.houston.hp.com/site/
If the communications between the CMS/host device do not use a proxy server, use telnet to verify the
connectivity to the RSSWM policy addresses. If a proxy server is used, it is not possible to manually check
this connectivity for each address; please use the procedure in the next section.
telnet rsswm-policy1.atlanta.hp.com 443
telnet rsswm-policy2.atlanta.hp.com 443
telnet rsswm-policy.houston.hp.com 443
If a URL rule was configured in the firewall, verify RSSWM connectivity from the RSSWM UI:
1. Select Start → All Programs → Hewlett-P ackard → Remote Support Software Manager → Remote
Support Software Manager User Interface.
2. Select the Actions screen.
3. Click the Test button to test connectivity.
4. A screen will show the results when the connectivity test is complete.
This verifies that whatever IP address comes back from the RSSWM data center as the active site, the RSSWM
agent can communicate with that address.
2.10 Levels of Data Collection
Data collection levels are a set of non-deterministic guidelines to help categorize the deployment models
and potential services enabled by deployment of tools. Four levels are currently defined:
• Device Discovery (Level 0):
Determine if an endpoint device is reachable across the network. For example, ICMP ECHO and ECHO
REPLY messages and traceroute probes are used to determine network reachability. No credentials are
required for this type of probing.
• Identity Collection (Level 1):
Utilize network protocol such as SNMP to properly identify an endpoint device manufacturer, model
and serial number. Public credentials such as SNMP community strings are used for probing the managed
devices.
• Configuration Collection (Level 2):
Utilize standard network protocols such as SNMP and WBEM to get attributes from the endpoint device,
for example operating system type and version, kernel parameters, and installed software. This
information will then be used to deliver as many remote support services as possible. Non-privileged
2.10 Levels of Data Collection 27