Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
Proper IP address are not getting populated for Linux server which happens to be running Docker engine - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Proper IP address are not getting populated for Linux server which happens to be running Docker engine
KB0727893

Proper IP address are not getting populated for Linux server which happens to be running Docker engine


1760 Views Last updated : Nov 16, 2022 public Copy Permalink
KB Summary by Now Assist

Issue

"IP Address" field is not getting set with the correct IP for CI with multiple IP addresses.

Logic used by Discovery to "IP Address" value on CI and Network Adapter Card

The fact that Docker is installed on the device is not meaningful here.

There are two scenarios.

Scenario #1

When there are multiple IP addresses with each one configured for a different Network Adapter (thus different MAC address)

If it is discovered in the Identification network payload that the original IP address is still enabled on the source target despite not being the most recent source target of the scan, discovery of the source target when the IP address is already set in the Configuration Item (CI) will not update the IP address.

The alternative IP address must be disabled on the source target in order to update it, or the CI's ip address field can be cleared, followed by a new scan using the chosen target.

Scenario #2

When there are multiple IP addresses configured on the same Network Adapter Card

In the Network Adapter record, only one IP address is permitted per MAC due to discovery.

The creation of numerous (IP addresses) to one (NIC) records and their subsequent relation to a CI are not permitted by discovery.

When this occurs, the first IP address listed will ultimately be the one used for the CI ip address field.

Both scenarios are out of the box (OOTB) behavior.

Example

This is an example for the second scenario

Note the same MAC address but multiple IP addresses returned in the payload.

=>"name":"docker0","mac_address":"00:50:52:f9:8a:a3","ip_addresses":[{"ip_address":"172.17.0.1" 
=>"name":"eth0","mac_address":"00:50:52:f9:8a:a3","ip_addresses":[{"ip_address":"10.249.138.163" 
=> "00:50:52:f9:8a:a3" = "00:50:52:f9:8a:a3" 


"Linux - Identity" Network Adapter Payload snippett:

{"related_data":{"adapters":[{"name":"docker0","mac_address":"00:50:52:f9:8a:a3","ip_addresses":[{"ip_address":"172.17.0.1","ip_version":4,"netmask":"255.255.0.0"},{"ip_address":"fe80::42:fdff:fecd:c6a3","ip_version":6,"netmask":"64"}],"ip_address":"172.17.0.1","netmask":"255.255.0.0","routes":{"ifRoutes":[{"dest_ip_network":"172.17.0.0/16","router_interface":"docker0"}],"gwRoutes":[]}},{"name":"eth0","mac_address":"00:50:52:f9:8a:a3","ip_addresses":[{"ip_address":"10.249.138.163","ip_version":4,"netmask":"255.255.255.0"},{"ip_address":"fe80::250:52ff:fef9:8aa3","ip_version":6,"netmask":"64"}],"ip_address":"10.249.138.163","netmask":"255.255.255.0","ip_default_gateway":"10.249.138.1","routes":{"ifRoutes":[{"dest_ip_network":"10.249.138.0/24","router_interface":"eth0"},{"dest_ip_network":"169.254.0.0/16","router_interface":"eth0"}],"gwRoutes":[{"dest_ip_network":"0.0.0.0/0","next_hop_ip_address":"10.249.138.1","route_interface":"eth0"}]}}],"default_gateway":"10.249.138.1"}} 
</output>


The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.