Idea ID 1674504
We are running OOB Inventory Scanner jobs in our environment and have noticed an issue with Primary IP Attribute.
Customer has enabled both IPV4 and IPV6 on their end machines but their default Is IPv4. It seems Inventory scanner job is always treating the IPV6 address as the default IP.
It seems Inventory scanner job is always treating the IPV6 address as the default IP
We discussed this issue with CPE, CPE mentioned that for Inventory scanner job, the primary IP is decided based on NIC Type and wireless/non-wireless configuration. IPV4 or IPV6 is not the deciding factor for primary IP.
This is current design for finding the primary IP implemented in code.
IP v6 is being taken in priority if there are 2 types of IP for same interface.
As a workaround Customer may use the enrichment rules for example.
As discussed this is a customization request to set IPv4 as primary IP.
One ER is needed for this issue.
** System information ***
Server version: 11.0 build: 12
OS: Windows NT (unknown) version 10.0
DB: [ucmdb] at SQLServer on [spgsmonsql:1535] with userName [ucmdbadmin] with password [*******]
No hotfix/binaries are applied
HA: Is_ha_enabled = true
Cluster_name = sqlserver_ucmdb
Cluster_nodes_names = [SPGSHPEUD_1535221574134]
Cluster_node_number = 1
Customers [Total of 1 customer(s)]:
[Customer ID: 1, Name: Default Client, CP: 26.00.85Description: Default Client, Config ID: 2]
Probe: IntegrationService, version: 11.0.12, build: 12
Probe: SPHQHPEUDP, version: 11.0.12, build: 12
Probe: SPGSHPEUDP, version: 11.0.12, build: 12
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.