Alarms for Fabric Maps and Policies

GigaVUE‑FM generates alarms to track the changes in the health status of the fabric maps. That is, whenever the health status of a fabric map changes from healthy to unhealthy (or state changes within an unhealthy state), an alarm is triggered and the same can be viewed in the Alarms page.

Starting in software version 5.11.00, GigaVUE‑FM generates alarms to track the changes in the health status of the orchestrated policies. Consider the following example in which the user has created the following two policies:

Note:  Whenever an intent policy is created, a number of Fabric Mapsand internal cluster maps are created using circuit ports, stack ports and other type of ports.

OrchestratedPolicies	Fabric Maps	Cluster LevelMaps	Ports
Policy_1	Fabric_map_1	Map_1	Port_11 Port_12
		Map_2	Port_21 Port_22
	Fabric_map_2	Map_3	Port_31 Port_32
		Map_2	Port_21 Port_22
Policy 2	Fabric_map_4	Map_4	Port_41 Port_42
		Map_5	Port_51 Port_52

Refer to the following notes:

• If the health status of Port_21 (circuit port) turns red, then the following alarms are generated:
  • One port level alarm for the circuit port Port_21.
  • One cluster map level alarm for Map_2.
  • Two fabric map level alarms for Fabric_map_1 and Fabric_map_2.
  • One policy level alarm for Policy_1.
• If the health status of Port_51 (stack port) turns red, then the following alarms are generated:
  • One port level for the stack port Port_51
  • One cluster map level alarm for Map_5
  • One fabric map level alarms for Fabric_map_4
  • One policy level alarm for Policy_2