The realization state for a T0 shows the "logical router port configuration realization error" for edge transport nodes.

Products

• VMware NSX

Issue/Introduction

Symptoms:

You may notice realization failure with the error in realization of a T0 logical router port. If using policy API, this is transient and will resolve when T0-T1 plumbing completes.

curl -X GET -k -u admin:<password> https://<NSX Manager IP>/policy/api/v1/gobal-infra/tier-0s/GlobalT0-1/state
{
  "tier0_state" : {
    "state" : "error",
    "details" : [ {
      "sub_system_id" : "cf401023-9c0f-4275-886c-bd393ca1cXXXX",
      "sub_system_type" : "TransportNode",
      "state" : "error",
      "failure_message" : "logical router port configuration realization error",
      "failure_code" : 5104
    },

RuntimeStatusMsg for COMPONENT_ID_EDGE_AGENT_L3 -

        {
            "object_type" : "vmware.nsx.nestdb.RuntimeStatusMsg",
            "value" : {
                "component_id" : "COMPONENT_ID_EDGE_AGENT_L3",
                "realization_error" : [
                    {
                        "error_id" : "EDGE_AGENT_LOG_ROUTER_PORT_CONFIG_FAILURE",
                        "meta_info" : "logical router port configuration realization error",
                        "affected_entity" : [
                            "51a0d5fe-41d6-44a4-b510-50b2e14bXXXX"
                        ]
                    }
                ]
            }
        }

"failure_message":"Internal error occurred on transport node ad372270-edae-451a-afca-9a90cbafXXXX.","failure_code":5104}

Environment

VMware NSX-T Data Center

Resolution

This issue is resolved in:

VMware NSX-T Data Center 2.5.3.
VMware NSX-T Data Center 3.0.3.
VMware NSX-T Data Center 3.1.1.



Workaround:

• Workaround: If you are using management plane or management plane APIs, delete the logical router port created on T0 for connecting to a T1, or complete the connectivity with a T1.

Additional Information

Impact/Risks:
Customer may notice realization failure with the error in realization of a T0 LRP. If user is using MP, they need to delete the LRP created on T0 for connecting to a T1, or complete the connectivity with a T1. If user is using policy API, this is transient and will resolve when T0-T1 plumbing completes.