Security Explorer - Stale VM-IP entry update

Products

• VMware vDefend Firewall with Advanced Threat Prevention

Issue/Introduction

Stale VM IP still reflecting on the SSP UI-> Security Explorer -> VM-Info page
- Stale API call output using VM-ID# /5xyxyxyx3-4xyf-2cxy-2xy4-3xyxyx0a1c9dyc ( UUID from VM-Info / virtual-machine page in SSP-UI)
https://<SSP-FQDN>/intelligence/visualization/compute//5xyxyxyx3-4xyf-2cxy-2xy4-3xyxyx0a1c9dyc/compute-context/compute-info?compute_type_param=VM
{
   "name": "vm-vm",
    "tags": [],
    "last_updated_time": 1769514971836,
   "uuid": "55xyxyxyx3-4xyf-2cxy-2xy4-3xyxyx0a1c9dyc",
    "os_detail": {
        "os_type": "LINUX",
        "os_display_value": "Ubuntu Linux (64-bit)"
    },
    "product_type": "Ubuntu Linux (64-bit)",
   "computer_name": "vm-vm",
    "ip_address": [
       "10.xy.xy.50",
       "10.xy.xy.11w",
       "yx80::xy0:5xyf:fx4y:1xyx"
    ],
    "bios_id": "4214a250-3e9b-decd-7eed-fc5c546b5f4f",
    "transport_nodes": [
        {
           "id": "yxyxyxy-fxyxyx-4xyx-bxyz8-xyzxusxz06",
           "name": "esx.vcf",
            "tags": []
        }
    ]

Environment

SSP 5.x

Cause

NSX holding stale entry leading to information being populated. 

Resolution

Work-Around
- Check the Segment/network the NSX-Vm is connected to.
- Login to NSX-UI ->  Segment -> Search for the segment
- To view the ports and interfaces associated with the VM, click on Ports and Interfaces under the Segment section.
- View Realized Bindings to list out all the IP bindings that been discovered.
- Locate and move the stale/old IP binding to Ignored bindings, leaving the new active Ip binding under realized binding list.
- Under Ignored binding, delete permanently the IP from the ignored binding list. 

Additional Information

NSX Reference Article
https://knowledge.broadcom.com/external/article/329047