Risks, Limitations And Assumptions

  • The application can handle Critical/Recovery failure notifications for the following cases when App Failure Notifications are enabled in the configuration:

    • Connectivity Exception
    • Authentication Exception

  • The application sends duplicate or repeat failure alert notifications every six hours.

  • The unique ID for the firewall is now managed by the Policy API instead of the Manager API. During migration of NSX-T devices from manager to policy mode, firewalls created using the Manager API are removed, and new firewalls using the Policy API are created.

  • The application does not control monitoring pause/resume actions based on the above alerts. Metrics are used to monitor resources and generate alerts based on threshold values.

  • Event/Alert polling for VMware NSX-T starts only when Event/Alert Polling is enabled in the configuration. Note:

    • Event/Alert polling is supported only for VMware NSX-T Alarms.
    • When a status value present in the Event/Alert Cleared Status field occurs, OpsRamp creates an Ok alert. Otherwise, OpsRamp creates an alert based on the Event/Alert Severity Filter and Event/Alert Severity Mappings in the Event/Alert Polling configuration.
    • The application publishes event polling alerts on the root resource if Alert on root resource is checked in the configuration; otherwise, alerts are published on the respective resource.
    • The default values for the Event/Alert Cleared Status configuration field are: ACKNOWLEDGED, SUPPRESSED, RESOLVED.
    • Possible VMware NSX-T status values are: OPEN, ACKNOWLEDGED, SUPPRESSED, RESOLVED.
    • Default and possible values for the Event/Alert Severity Filter configuration are: CRITICAL, HIGH, MEDIUM, LOW.
    • Default mappings are provided to map VMware NSX-T Severities with OpsRamp Severities in the Event/Alert Severity Mapping configuration.
    • Users can modify severity mappings at any time from the application configuration page. Possible OpsRamp Severities are: Critical, Warning, Ok, and Info.

  • The Template Applied Time is displayed only if the collector profile (Classic and NextGen Gateway) is version 18.1.0 or higher.

  • The application supports both Classic Gateway and NextGen Gateway.

  • The following are possible reasons why tunnel status-related metrics for a Transport Node may be missing:

    • Transport nodes connected only to VLAN transport zones do not have tunnel status metrics.
    • Tunnels are not set up when no NSX-backed or overlay VM is connected to the host.
    • The BFD module may be in an error state and may have wiped all BFD tunnel-related information.
    Transport node tunnel status-related metrics
    • nsxt_transportNode_TunnelStatus
    • nsxt_transportNode_TunnelUpCount
    • nsxt_transportNode_TunnelDownCount
    • nsxt_transportNode_BfdAdminDownCount
    • nsxt_transportNode_BfdDownCount
    • nsxt_transportNode_BfdInitCount
    • nsxt_transportNode_BfdUpCount
    • nsxt_transportNode_BfdNoDiagnosticCount
    • nsxt_transportNode_BfdControlDetectionTimeExpiredCount
    • nsxt_transportNode_BfdEchoFunctionFailedCount
    • nsxt_transportNode_BfdForwardPlaneResetCount
    • nsxt_transportNode_BfdPathDownCount
    • nsxt_transportNode_BfdConcatenatedPathDownCount
    • nsxt_transportNode_BfdAdministrativeDownCount
    • nsxt_transportNode_BfdReverseConcatenatedPathDownCount
    • nsxt_transportNode_BfdNeighbourSignalledSessionDownCount

  • Latest snapshot metric support is available from Gateway version 14.0.0.