1211 jack Respected Contributor.
Respected Contributor.
190 views

(SM) Support Tip:How SM get IP address for hostname

Scenario:

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

and http://www.avajava.com/tutorials/lessons/how-do-i-use-a-host-name-to-look-up-an-ip-address.html for its usage.

​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)

 

Activity

Total Transaction Delay (seconds)

Measured

10Mb

/

50ms

10Mb

/

100ms

4Mb

/

100ms

1.54Mb

/

150ms

1.54Mb

/

250ms

10Mb

/

500ms

Load the SM login page

0.002

0.153

0.303

0.305

0.461

0.761

1.503

Load the SM-ESS login page

0.310

0.717

1.117

1.130

1.563

2.363

4.317

Login in as falcon

1.217

2.072

2.922

2.962

3.919

5.619

9.722

Login in as BOB.HELPDESK

1.353

2.228

3.078

3.120

4.081

5.781

9.878

Login in as an ESS user

1.045

2.020

2.970

3.012

4.074

5.974

10.570

Open incident queue as falcon

0.350

0.454

0.554

0.560

0.677

0.877

1.354

Open New Incident as falcon

0.048

0.204

0.354

0.363

0.538

0.838

1.554

Submit New Incident as falcon

0.671

0.775

0.875

0.882

1.001

1.201

1.675

Search and open Incident for update as falcon

0.306

0.521

0.721

0.748

1.018

1.418

2.321

Save Incident update as falcon

0.401

0.558

0.708

0.718

0.897

1.197

1.908

Register New Interaction as falcon

0.104

0.260

0.410

0.419

0.594

0.894

1.610

Submit New Interaction as falcon

1.353

1.457

1.557

1.564

1.681

1.881

2.357

Search and open Interaction for update as falcon

0.420

0.619

0.819

0.839

1.093

1.493

2.419

Save Interaction update as falcon

0.537

0.642

0.742

0.751

0.874

1.074

1.542

Open New Change(RFC) as falcon

1.482

3.435

5.335

5.425

7.562

11.362

20.535

Submit New Change (RFC) as falcon

0.351

0.558

0.758

0.769

1.000

1.400

2.358

Open New Problem as falcon

0.154

0.669

1.169

1.195

1.764

2.764

5.169

Submit New Problem as falcon

0.720

0.926

1.126

1.138

1.368

1.768

2.726

 

PS: Network latency and bandwidth simulation is between Browser and Web tier .

Labels (1)
0 Likes
2 Replies
Trusted Contributor.. mweisenburger Trusted Contributor..
Trusted Contributor..

Re: (SM) Support Tip:How SM get IP address for hostname

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.

Greets

Matthias

0 Likes
Micro Focus Expert
Micro Focus Expert

Re: (SM) Support Tip:How SM get IP address for hostname

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:

Parameter: ws_endpoint

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.

Parameter

ws_endpoint

Description

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?

No

Default value

" "

The default value is an empty string.

Possible values

https://<lbhost>:<lbport>

or

http://<lbhost>:<lbport>

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.

Example usage

Command line: sm -ws_endpoint:https://mysite.hp.com:13080

Initialization file: ws_endpoint:https://mysite.hp.com:13080

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.