Uplink fpeth interface mismatch during replacement alarm in NSX Manager
Article ID: 368086
Updated On:
Products
VMware NSX
Issue/Introduction
Title: Alarm for edge.uplink_fpeth_interface_mismatch_during_replacement
Event ID: edge.uplink_fpeth_interface_mismatch_during_replacement
Alarm Description:
"The mapping of uplinks to fp-eth interfaces <old edge fp-eth list> for the Edge node <edge transport node name> with UUID <edge node uuid> is not present in the new bare metal Edge fp-eth interfaces <new edge fp-eth list>."
- Purpose: An alarm will be raised when newly replaced bare metal edge fast path (fp-eth) interfaces do not match with old edge fast path interfaces
- Impact: Alarm is raised when new bare metal edge has different pnic naming than old edge. This can cause edge transport node Configuration State to be in "Pending" state upon replacement, since by default after edge replace the pnics are mapped as they were on the old edge node.
Resolution
Steps to Resolve
For 4.1.1 and higher
- The alarm mentions that a newly replaced bare metal edge node does not contain valid fast path (fp-eth) interfaces in "pnics mapping". Note down the list of available fast path (fp-eth) interfaces <new edge fp-eth list> on the newly replaced bare metal edge node from the alarm description as mentioned above. Fast path (fp-eth) interfaces are interfaces starting with prefix "fp-eth".
- Get the configuration on the newly replaced bare metal edge transport node using an API call similar to the following: GET https://<NSX Manager IP/FQDN>/api/v1/transport-nodes/<edge node UUID>.
Note: The following is a sample output for this API call. The "pnics" stanza is the important part of this output.
{
"node_id": "c####ac-0##a-11ef-ae21-0#####9a3",
"host_switch_spec": {
"host_switches": [
{
"host_switch_name": "nsxvswitch",
"host_switch_id": "c####ac-0##a-11ef-ae21-0#####9a3",
"host_switch_type": "NVDS",
"host_switch_mode": "STANDARD",
"host_switch_profile_ids": [
{
"key": "UplinkHostSwitchProfile",
"value": "5####6-6##7-4##1-###6-2#####17"
}
],
"pnics": [ <<<<<< pnics mapping
{
"device_name": "fp-eth1", <<<<<<< Check if this fast path (fp-eth) interface is present in <new edge fp-eth list> from Step 1
"uplink_name": "uplink1"
},
{
"device_name": "fp-eth2", <<<<<<< Check if this fast path (fp-eth) interface is present in <new edge fp-eth list> from Step 1
"uplink_name": "uplink2"
}
],
"is_migrate_pnics": false,
"ip_assignment_spec": {
"ip_pool_id": "7#####8-6##1-4##4-a##e-4######c4",
"resource_type": "StaticIpPoolSpec"
},
"cpu_config": [],
"transport_zone_endpoints": [
{
"transport_zone_id": "c####7-5##f-4##0-9##b-0#####3",
"transport_zone_profile_ids": [
{
"resource_type": "BfdHealthMonitoringProfile",
"profile_id": "5####b3-a##2-4##8-9##4-1######50a"
}
]
}
],
"pnics_uninstall_migration": [],
"vmk_uninstall_migration": [],
"not_ready": false
}
],
"resource_type": "StandardHostSwitchSpec"
},
"maintenance_mode": "DISABLED",
"node_deployment_info": {
"deployment_type": "PHYSICAL_MACHINE",
"node_settings": {
"hostname": "########",
"ntp_servers": [
"##.##.##.##"
],
"enable_ssh": true,
"allow_ssh_root_login": true,
"enable_upt_mode": false
},
"resource_type": "EdgeNode",
"external_id": "c#####ac-0##a-1##f-a##1-0#######9a3",
"ip_addresses": [
"##.##.##.##"
],
"id": "c####ac-0##a-1###-a##1-0######9a3",
"display_name": "########",
"_revision": 1
},
"is_overridden": false,
"failure_domain_id": "4####b0-1##d4-4##9-8##8-f######fb",
"resource_type": "TransportNode",
"id": "c####1ac-0##a-1##f-a##1-0######a3",
"display_name": "########",
"_system_owned": false,
"_protection": "NOT_PROTECTED",
"_create_time": 1714664647852,
"_create_user": "#####",
"_last_modified_time": 1714664954579,
"_last_modified_user": "#####",
"_revision": 1
} - Get the list of fast path (fp-eth) interfaces from "pnics mapping" seen in the Step 2 API payload. Some of these fast path (fp-eth) interfaces will not be present in the available fast path interfaces list <new edge fp-eth list> that was obtained in Step 1.
- You will need to update the "pnics mapping" from the available fast path interfaces list <new edge fp-eth list> that was obtained in Step 1, using an API call similar to the following: PUT https://<NSX Manager IP/FQDN>/api/v1/transport-nodes/<edge node UUID>.
Sample payload:
{Note: You must update the correct "pnics mapping" in this API payload. For example, as shown in Step 2, the GET transport node API payload shows fp-eth1 and fp-eth2 are used in "pnics mapping". The new bare metal edge node actually has fp-eth0 and fp-eth1 fast path interfaces (these will be listed in <new edge fp-eth list> from Step 1). You would need to update "pnics mapping" to use fp-eth0 and fp-eth1 fast path interfaces, which are present on the new bare metal edge node.
"node_id": "c####ac-0##a-11ef-ae21-0#####9a3",
"host_switch_spec": {
"host_switches": [
{
"host_switch_name": "nsxvswitch",
"host_switch_id": "c#####6f-0##a-4##8-b##3-8######c",
"host_switch_type": "NVDS",
"host_switch_mode": "STANDARD",
"host_switch_profile_ids": [
{
"key": "UplinkHostSwitchProfile",
"value": "5#####46-6##7-4##1-a##6-2#####e517"
}
],
"pnics": [ <<<<<< pnics mapping
{
"device_name": "fp-eth0", <<<<<<< Update device_name from list of available fast path (fp-eth) interfaces list <new edge fp-eth list> obtained in Step 1.
"uplink_name": "uplink1"
},
{
"device_name": "fp-eth1", <<<<<<< Update device_name from list of available fast path (fp-eth) interfaces list <new edge fp-eth list> obtained in Step 1.
"uplink_name": "uplink2"
}
],
"is_migrate_pnics": false,
"ip_assignment_spec": {
"ip_pool_id": "7####78-6##1-4##4-a##e-4######0c4",
"resource_type": "StaticIpPoolSpec"
},
"cpu_config": [],
"transport_zone_endpoints": [
{
"transport_zone_id": "c####ec7-5##f-4##0-9##b-0######f3",
"transport_zone_profile_ids": [
{
"resource_type": "BfdHealthMonitoringProfile",
"profile_id": "5#####3-a##2-4##8-9##4-1########0a"
}
]
}
],
"pnics_uninstall_migration": [],
"vmk_uninstall_migration": [],
"not_ready": false
}
],
"resource_type": "StandardHostSwitchSpec"
},
"maintenance_mode": "DISABLED",
"node_deployment_info": {
"deployment_type": "PHYSICAL_MACHINE",
"node_settings": {
"hostname": "s########",
"ntp_servers": [
"##.##.##.##"
],
"enable_ssh": true,
"allow_ssh_root_login": true,
"enable_upt_mode": false
},
"resource_type": "EdgeNode",
"external_id": "c####ac-0##a-11ef-ae21-0#####9a3",
"ip_addresses": [
"##.##.##.##"
],
"id": "c####ac-0##a-11ef-ae21-0#####9a3",
"display_name": "########",
"_revision": 1
},
"is_overridden": false,
"failure_domain_id": "4b0-1c#####d4-4##9-8##8-f#####aafb",
"resource_type": "TransportNode",
"id": "c#####ac-0##a-1##f-a##1-0######9a3",
"display_name": "########",
"_system_owned": false,
"_protection": "NOT_PROTECTED",
"_create_time": 1714664647852,
"_create_user": "#####",
"_last_modified_time": 1714664954579,
"_last_modified_user": "#####",
"_revision": 1
}
Note: Ensure that the newly updated fast path (fp-eth) interfaces in "pnic mapping" have appropriate underlay connectivity. - After updating the correct "pnics mapping" in Step 4, the alarm should be resolved automatically.
Additional Information
Documentation for "pnics mapping" field can be found in the following documentation:
StandardHostSwitch [Check "pnics" stanza here]
Feedback
Yes
No
Powered by
