What is the packet size of a ping when sent by eHealth?

Document ID : KB000045529
Last Modified Date : 14/02/2018
Show Technical Document Details

Introduction: 

The default ping packet size for eHealth is not the default 32 byte size but a 100 byte size.

Background:  

This change from the default can lead to some problems in some restrictive environments.  End devices may be set to only respond to the default size and firewalls may restrict anything beyond the default size.  This will generally show up in polling errors such as: No Response to Ping.

Environment:  

All current supported eHealth versions and their associated operating systems

Information: 

eHealth uses a non-default packet payload size of 100 bytes.  While this may not be a big deal for most, some users may find that their environments either cannot handle this size or may restrict the transmission of pings of this size.  This will begin to show up as discovery and polling errors such as No Response to Ping as the first thing eHealth by default does is send out a ping during a discover or poll.

 

One thing that you can take a look at is if you can send the ping to the end device in question manually.  You can first run a default (32 byte) ping then a 100 byte ping and see if there is any difference.  Here is how you can use the ping command based on Operating System to send a differing size payload size.  Please note that in the below example for Unix 100(128) means a 100 byte payload with a 32 byte header.

 

Windows:

> ping -l 100 localhost

Pinging localhost [::1] with 100 bytes of data:

Reply from ::1: time<1ms

Reply from ::1: time<1ms

Reply from ::1: time<1ms

Reply from ::1: time<1ms

Ping statistics for ::1:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 0ms, Maximum = 0ms, Average = 0ms

 

Unix:

$ ping -s 100 localhost

PING localhost (127.0.0.1) 100(128) bytes of data.

108 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.055 ms

108 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.077 ms

108 bytes from localhost (127.0.0.1): icmp_seq=3 ttl=64 time=0.056 ms

108 bytes from localhost (127.0.0.1): icmp_seq=4 ttl=64 time=0.083 ms

 

--- localhost ping statistics ---

4 packets transmitted, 4 received, 0% packet loss, time 3382ms

rtt min/avg/max/mdev = 0.055/0.067/0.083/0.016 ms

 

Additional Information:

 

You can also reference the CA eHealth Administration guide for a higher overview of the above procedure as well as what to do next.  This can be accessed via the eHealth bookshelf at support.ca.com.  In the current revision of the guide, 6.3.2.07 you will find the relevant section on page 105 with a heading of 'Resolve “No Response to Ping” Polling Error'.