Browse FAQs

Direct Ethernet devices/sites will not connect in Management Console when using a leading zero in the IP address octets

Published date: 25 September 2019

Issue
Ethernet devices/sites added in Management Console with a leading zero for the IP address octet will not connect.

Product Line
Power Monitoring Expert 9.0
Power Monitoring Expert 8.x
Power Monitoring Expert 7.2.x
StruxureWare Power Monitoring 7.0.x
ION Enterprise 6.0.1

Environment
Management Console

Cause
Windows utilities can accept IP addresses comprised of decimal, octal, or hexadecimal numbers. The IP address numbers can be written in hexadecimal and octal, by prefixing them with 0x and 0, respectively. These features continue to be supported by software until today, even though they are seen as non-standard.  This will cause issues if you unintentionally use a leading zero in a decimal octet. With a leading zero, the number is typically resolved by these utilities as an octal number, specifying the incorrect IP address.

Resolution
When configuring IP addresses in Management Console, decimal format is desired.

The different IP address formats can be found below:
10.172.58.101 (decimal)
012.0254.072.0145 (octal)
0xA.0xAC.0x3A.0x65 (hexadecimal)

For example:
A device may have the IP address of 10.172.58.101 in decimal. However, the user configures the IP address to be 10.172.058.101 or 010.172.058.101 in Management Console. This would in turn specify the respective IP octets in octal which is not the desired result. Therefore, the user will need to delete the leading zeros for Management Console to connect properly.

Was this helpful?

What can we do to improve the information ?

Can't find what you are looking for?

Reach out to our customer care team to receive information on technical support, assistance for complaints and more.