(SM) Support Tip:How SM get IP address for hostname
Some customer find SM take long time to get IP address for hostname. For example if host has several NIC cards, the network flow will be firstly obtain the IP addresses from DHCP server, then sending request to DNS server to bind the ip address and the host name.
From SM deign code we can know ,SM will call the java function getCanonicaHostName, this function will call InetAddress.getLocalHost().getCanonicaHostName() in which will do the following:
1.Check local host cache, ttl of localhost cache is 5 seconds, it will call getAddressesFromNameService if longer than 5 seconds, this function will first check hosts file firstly, if host name not specified in hosts file, then it will go to dns server.
2.If from last time to now local cache have been read less than 5 seconds,hostname will be set according to local cache.
And here InetAddress.getByName is one function provided by JAVA libarary, you can refer to http://download.java.net/jdk7/archive/b123/docs/api/java/net/InetAddress.html
How to let SM get IP address for hostname quickly:
You can use below method to let SM get IP address for hostname quickly
1.add host name in hosts file.
2.add ws_endpoint in sm.ini file.
Also if customer have network latency issue, it will also cause SM take long time to get IP address for hostname. Below is the OOB network latency test data from CPE testing team.
You can use it to check if CU has network latency issue.
OOB test result (see below table) show that the main contributor to the perceived delay at the client is the network latency. Link bandwidth is less important, but keep in mind that these values are relevant in the context of an ideal network with no congestion. If congestion occurs, bandwidth can also become important. Also, the data is for an OOB system so the absolute numbers might not be accurate for the customer implementation. However, we believe that the deltas between the delays in the same row should still be relevant in most cases.
For detail calculation method, it highly based on below input and it makes calculation difficult.
- SM data customizations performed, which might affect the message numbers and sizes for each transaction
- Average number of users on each site and average network activity of these users
- Typical user behaviors and user distribution in system
- Other traffic flowing on the network (non SM)
- Type of service from the provider (leased line with fixed bandwidth, L2 VPN, L3 VPN etc)
Total Transaction Delay (seconds)
Load the SM login page
Load the SM-ESS login page
Login in as falcon
Login in as BOB.HELPDESK
Login in as an ESS user
Open incident queue as falcon
Open New Incident as falcon
Submit New Incident as falcon
Search and open Incident for update as falcon
Save Incident update as falcon
Register New Interaction as falcon
Submit New Interaction as falcon
Search and open Interaction for update as falcon
Save Interaction update as falcon
Open New Change(RFC) as falcon
Submit New Change (RFC) as falcon
Open New Problem as falcon
Submit New Problem as falcon
PS: Network latency and bandwidth simulation is between Browser and Web tier .
Hi 1211 jack,
could you please give some details to the sm.ini option ws_endpoint?
I was not able to find thi parameter in my 9.40 help center.
The parameter is not documented in 9.4x however it will be documented in a future release. This is the documentation from the 'future' help server:
Startup parameters change the behavior of the HPE Service Manager server. You can always set a startup parameter from the server's operating system command prompt.
This parameter specifies the web services end point. This parameter overwrites useIPInWSDL and preferredFQHN.
Valid if set from
Server's operating system command prompt
Initialization file (sm.ini)
Requires restart of the Service Manager server?
The default value is an empty string.
For example, https://<FQDN of the HWLB virtual server>:<Port of HWLB virtual server>/SM/7/ws/ChangeManagement.wsdl. In this example, the ws_endpoint parameter refers to the boldface part.
Command line: sm -ws_endpoint:https://mysite.hp.com:13080
Initialization file: ws_endpoint:https://mysite.hp.com:13080