Alarm will be raised when edge node settings parameters in Edge Node CLI and Edge Node MP intent are found to be different. If Any one of below Edge Node Settings field is changed directly through edge CLI, then this alarm will be raised.
Edge node settings ->
Alarm will be raised when edge node vSphere settings parameters on VCenter and Edge Node MP intent are found to be different. If user changes any one of below edge VM vSphere deployment configuration field through VCenter then this alarm will be raised.
Edge VM vSphere settings ->
Alarm will be raised when edge node vSphere settings parameters on VCenter and edge node CLI parameters are found to be different than Edge Node MP intent. If user changes edge fields from both "Edge node settings" and "Edge VM vSphere settings" directly on edge CLI and VCenter respectively, then this alarm will be raised.
Alarm will be raised when user uses the vMotion to move Edge VMs. The datastore ("Storage Id"), compute cluster id ("Compute Id") parameters of Edge Node in vSphere will be changed when Edge VM is moved. Thus, when these edge node vSphere settings parameters on VCenter and Edge Node MP intent are found to be different, then alarm will be raised. Thus, if only any (or all) of below fields is changed then this alarm is raised.
If other than "Compute Id" and "Storage Id" some more "Edge VM vSphere settings" OR "Edge node settings" fields are changed, then "Edge VM vSphere Settings Mismatch" Alarm or "Edge Node Settings and vSphere Settings are changed" Alarm will be raised based on fields that are changed.
{ "node_deployment_state": { "state": "EDGE_VM_VSPHERE_SETTINGS_MISMATCH_RESOLVE", "details": [ { "sub_system_id": "EDGE_TRANSPORT_NODE_MISMATCH_ALARMS", "state": "EDGE_VM_VSPHERE_SETTINGS_MISMATCH_RESOLVE", "failure_message": " configuration on vSphere : {\"CPU Reservation in shares\":\"NORMAL_PRIORITY\",\"Storage Id\":\"datastore-14\"}, intent vSphere configuration :{\"CPU Reservation in shares\":\"LOW_PRIORITY\",\"Storage Id\":\"datastore-50\"}", "failure_code": 16087 } ], "failure_message": "", "failure_code": 0 } }
{ "node_deployment_state": { "state": "NODE_READY", "details": [] } }
{ "node_deployment_state": { "state": "NODE_READY", "details": [] } }
Note: "Edge Node MP intent" term refers to Edge Transport Node configuration data which is present in NSX-T Manager Database. We get same data as payload when we do a GET call for this edge transport node e.g. GET https://<manager-ip>/api/v1/transport-nodes/<edge-tn-id>
From NSX 4.1.1, UPT mode may be edited even when Edge maintenance mode is enabled.
As part of UPT mode realization, maintenance mode is toggled on the Edge VM.
If user edits UPT mode on edge with maintenance mode enabled, then user must disable maintenance mode, before UPT realization completes. Mismatch alarm is raised after partial UPT realization when edge has maintenance mode enabled. The alarm will resolve using NSX Value, when User disables maintenance mode on edge.