New segment created from NSX UI is stuck in "UNINITIALIZED" state.
search cancel

New segment created from NSX UI is stuck in "UNINITIALIZED" state.

book

Article ID: 419142

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

  • The new segment, "segment_name" was created from NSX UI.
  • However, this segment is stuck in "Uninitialized" state. Refreshing the segment status from UI, doesn't reflect any changes.

  • After changing the view from Policy to Manager on the UI, segment is not listed under Networking -> Logical Switches.
  • The NSX manager cluster is healthy and no alarms have been reported regarding the cluster health.
  • Checking Statistics of the segments, reports the below error: 

  • Post this, below error is reported in the alarms sections: 
    • Error: Object path(s)=[/infra/segments/segment_name] may not have been realized on enforcement point /infra/sites/default/enforcement-points/default. (Error code: 500140)
  • Fetching the segment details from the API call: GET https://<manager_IP>/policy/api/v1/infra/segments/segment_name, following details are listed:

{
            "type": "DISCONNECTED",
            "vlan_ids": [
                "VLAN"
            ],
            "transport_zone_path": "/infra/sites/default/enforcement-points/default/transport-zones/transport_zone_ID",
            "advanced_config": {
                .....
            },
            "admin_state": "UP",
            "replication_mode": "MTEP",
            "resource_type": "Segment",
            "id": "segment_id",
            "display_name": "segment_name",
            "description": "",
            "path": "/infra/segments/segment_name",
            "relative_path": "segment_name",
            "parent_path": "/infra",
            "remote_path": "",
            "unique_id": "segment_id",
            "realization_id": "segment_id",
            "owner_id": "owner_id",
            "marked_for_delete": false,
            "overridden": false,
            "_system_owned": false,
            "_protection": "NOT_PROTECTED",
            "_create_time": 12############34,
            "_create_user": "user",
            "_last_modified_time": 12############34,
            "_last_modified_user": "user",
            "_revision": 0
        }

  • After the segment was created, the consolidated state for the segment was moved to "UNINITIALIZED" and this value is not changed across the logs.

/var/log/syslog:

YYYY-MM-DDTHH:MM:SS.435Z manager NSX 5258 - [nsx@6876 audit="true" comp="nsx-manager" level="INFO" reqId="28d########################ef4f30" subcomp="manager" update="true" username="user"] UserName="user", Src="1##.##.##.###", ModuleName="PolicyConnectivity", Operation="PatchInfraSegment", Operation status="success", New value=[Segment_Details]
YYYY-MM-DDTHH:MM:SS.444Z manager NSX 5258 - [nsx@6876 audit="true" comp="nsx-manager" level="INFO" reqId="28d########################ef4f30" subcomp="manager" update="true"] UserName="user", Src="1##.##.##.###", ModuleName="Policy", Operation="PatchInfra", Operation status="success", New value=[{"enforce_revision_check":true} {"resource_type":"Infra","children":[Segment_details],"marked_for_delete":false,"overridden":false,"_revision":-1}]
YYYY-MM-DDTHH:MM:SS.570Z manager NSX 5258 POLICY [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] Updated consolidated state for intentPath:/infra/segments/segment_name to:UNINITIALIZED
......
YYYY-MM-DDTHH:MM:SS.662Z manager NSX 5258 - [nsx@6876 audit="true" comp="nsx-manager" level="INFO" reqId="88a########################1f170b" subcomp="manager" update="true" username="user"] UserName="user", Src="1##.##.##.###", ModuleName="PolicyRealizedState", Operation="RefreshRealizedState", Operation status="success", New value=[{"intent_path":"/infra/segments/segment_name"}]
YYYY-MM-DDTHH:MM:SS.694Z manager NSX 5258 - [nsx@6876 audit="true" comp="nsx-manager" level="INFO" reqId="70########################e8e0a" subcomp="manager" username="user"] UserName="user", Src="1##.##.##.###", ModuleName="Search", Operation="Search", Operation status="success", New value=[{"query":"resource_type:Segment AND path:\"/infra/segments/segment_name\"","exclude_internal_types":false,"context":"projects:ALL","page_size":1000}]

  • Edited the segment details by adding a line in the description, the status of segment then moved to "In Progress" state.

  • After editing the segment, below events are reported in the syslog files:

YYYY-MM-DDTHH:MM:SS.841Z manager NSX 5258 POLICY [nsx@6876 comp="nsx-manager" errorCode="PM511028" level="ERROR" reqId="b6########################ea11" subcomp="manager" username="admin"] Null realized object ID for segment /infra/segments/segment_name
YYYY-MM-DDTHH:MM:SS.841Z manager NSX 5258 - [nsx@6876 audit="true" comp="nsx-manager" level="INFO" reqId="b6########################ea11" subcomp="manager" username="admin"] UserName="admin", Src="1##.##.##.###", ModuleName="PolicyConnectivityStatistics", Operation="GetInfraSegmentStatistics", Operation status="failure", New value=["segment_name" {"enforcement_point_path":"/infra/sites/default/enforcement-points/default","page_size":1000,"include_mark_for_delete_objects":false}] 
YYYY-MM-DDTHH:MM:SS.843Z manager NSX 5258 SYSTEM [nsx@6876 audit="true" comp="nsx-manager" level="INFO" subcomp="manager"] UserName:'admin' ModuleName:'Policy' Operation:'GET@/api/v1/infra/segments/segment_name/statistics' Operation status: 'failure' Error: The object was not realized. Please check for any alarms on the object.
.....
YYYY-MM-DDTHH:MM:SS.108Z manager NSX 5258 SYSTEM [nsx@6876 audit="true" comp="nsx-manager" level="INFO" subcomp="manager"] UserName:'admin' ModuleName:'Policy' Operation:'GET@/api/v1/infra/segments/segment_name/statistics' Operation status: 'failure' Error: The object was not realized. Please check for any alarms on the object.
YYYY-MM-DDTHH:MM:SS.927Z manager NSX 5258 POLICY [nsx@6876 comp="nsx-manager" errorCode="PM500140" level="ERROR" reqId="522d3########################65925a" subcomp="manager" username="admin"] Object path(s)=[/infra/segments/segment_name] may not have been realized on enforcement point path=[/infra/sites/default/enforcement-points/default]
YYYY-MM-DDTHH:MM:SS.928Z manager NSX 5258 - [nsx@6876 audit="true" comp="nsx-manager" level="INFO" reqId="522d3########################65925a" subcomp="manager" username="admin"] UserName="admin", Src="1##.##.##.###", ModuleName="PolicyGroupRealization", Operation="GetGroupsForObject", Operation status="failure", New value=[{"intent_path":"/infra/segments/segment_name","sort_by":"target_display_name","sort_ascending":true,"page_size":50,"include_mark_for_delete_objects":false}]
YYYY-MM-DDTHH:MM:SS.928Z manager NSX 5258 SYSTEM [nsx@6876 audit="true" comp="nsx-manager" level="INFO" subcomp="manager"] UserName:'admin' ModuleName:'Policy' Operation:'GET@/api/v1/infra/group-associations' Operation status: 'failure' Error: Object path(s)=[/infra/segments/segment_name] may not have been realized on enforcement point path=[/infra/sites/default/enforcement-points/default].

 

Environment

VMware NSX

Cause

The realization task of the segment might have not completed successfully due to an issue with underlying proton service.

Resolution

As a workaround, please perform a rolling reboot of all 3 NSX manager nodes.

However, if the reboot of the NSX managers is not possible, please restart the proton service across all 3 manager nodes.

  • For restarting the proton service, please run the command: /etc/init.d/proton restart
  • Post restart, validate the status of the service: /etc/init.d/proton status

If the issue is not resolved after NSX manager/proton service restart, please open a support ticket with Broadcom support team. Please refer: Creating and managing Broadcom support request (SR) cases

 

Powered by Wolken Software