Monitor

This chapter contains the following topics:

Monitoring Switch

The Switch menu includes the following submenus:

Viewing Switch CPU Information

To view the switch CPU information from the Cisco DCNM Web UI, perform the following steps:

Procedure

Step 1

Choose Monitor > Switch > CPU.

The CPU window is displayed. This window displays the CPU information for the switches in that scope.

Step 2

You can use the drop-down to filter the view by Last 10 Minutes, Last Hour, Last Day, Last Week, Last Month, and Last Year.

Step 3

In the Switch column, click the switch name to view the Switch Dashboard.

Step 4

Click the chart icon in the Switch column to view the CPU utilization.

You can also change the chart timeline to Last 10 Minutes, Last Hour, Last Day, Last Week, Last Month, and Last Year. You can choose the chart type and chart options to show as well.

Viewing Switch Memory Information

To view the switch memory information from the Cisco DCNM Web UI, perform the following steps:

Procedure

Step 1

Choose Monitor > Switch > Memory.

The memory panel is displayed. This panel displays the memory information for the switches in that scope.
Step 2

Use the drop-down to filter the view by Last 10 Minutes, Last Hour, Last Day, Last Week, Last Month, and Last Year.

Step 3

Click the chart icon in the Switch column to see a graph of the memory usage of the switch.

Step 4

In the Switch column, click the switch name to view the Switch Dashboard.

Step 5

You can use the drop-down to view the chart in different time lines. Use the chart icons to view the memory utilization chart in varied views.

Viewing Switch Traffic and Errors Information

To view the switch traffic and errors information from the Cisco DCNM Web UI, perform the following steps:

Procedure

Step 1

Choose Monitor > Switch > Traffic.

The Switch Traffic panel is displayed. This panel displays the traffic on that device for the past 24 hours.

Step 2

Use the drop-down to filter the view by 24 hours, Week, Month, and Year.

Step 3

Click the Export icon in the upper-right corner to export the data into a spreadsheet.

Step 4

Click Save.

Step 5

Click the switch name to view the Switch Dashboard section.

Viewing Switch Temperature

Cisco DCNM includes the module temperature sensor monitoring feature, using which you can view the sensor temperature of a switch. You can choose an interval by which to filter the sensor list. The default interval is Last Day. Only sensors that have historical temperature data is shown in the list. You can choose between Last ten Minutes, Last Hour, Last Day, Last Week, and Last Month.

Note

It is not necessary to configure the LAN credentials under the Configure > Credentials Management > LAN Credentials screen to fetch the temperature monitoring data from the switches.

To view the switch temperature information from the Cisco DCNM Web UI, perform the following steps:

Procedure

Step 1

Choose Monitor > Switch > Temperature.

The Switch Temperature window is displayed with the following columns.

  • Scope: The sensor belongs to a switch, which is part of a fabric. The fabric that it belongs to is shown as its scope. When the scope selector at the top of Cisco DCNM is used, the sensor list is filtered by that scope.
  • Switch: Name of the switch the sensor belongs to.
  • IP Address: IP Address of the switch.
  • Temperature Module: The name of the sensor module.
  • Avg/Range: The first number is the average temperature over the interval that is specified at the top of the table. The second set of numbers is the range of the temperature over that interval.
  • Peak: The maximum temperature over the interval
Step 2

From this list, each row has a chart icon, which you can click.

A chart is displayed, which shows historical data for the sensor. The interval for this chart can be changed as well, between 24 hours, 1 week, and 1 month.

Enabling Temperature Monitoring

You can enable the temperature monitoring feature for LAN switches from the LAN Collections screen, and for the SAN switches by setting a few properties under Administration > DCNM Server > Server Properties screens.

Enabling Temperature Monitoring for LAN Switches

  1. From the menu bar, choose Administration > Performance Setup > LAN Collections.

  2. Select the Temperature Sensor check box.

  3. Select the type of LAN switches for which you want to collect performance data.

  4. Click Apply to save the configuration.

Viewing Accounting Information

To view the accounting information from the Cisco DCNM Web UI, perform the following steps:

Procedure

Step 1

Choose Monitor > Switch > Accounting.

The fabric name or the group name along with the accounting information is displayed.

Step 2

Select Advanced Filter beside the filter icon to search the accounting information by Source, Username,Time, and Description. Or select Quick Filter to search under each column.

Step 3

You can also select a row and click the Delete icon to delete accounting information from the list.

Step 4

You can use the Print icon to print the accounting details and use the Export icon to export the data to a Microsoft Excel spreadsheet.

Viewing Events Information

To view the events and syslog from the Cisco DCNM Web UI, perform the following steps:

Procedure

Step 1

Choose Monitor > Switch > Events.

The fabrics along with the switch name and the events details are displayed.

The Count column displays the number of times the same event has occurred during the time period as shown in the Last Seen and First Seen columns.

Click a switch name in the Switch column to view the switch dashboard.

Step 2

Select an event in the table and click the Add Suppressor icon to open the shortcut of adding an event suppressor rule.

Step 3

Select one or more events from the table and click the Acknowledge icon to acknowledge the event information for the fabric.

  • After you acknowledge the event for a fabric, the acknowledge icon is displayed in the Ack column next to the fabric.
Step 4

Select the fabric and click the Unacknowledge icon to cancel an acknowledgment for a fabric.

Step 5

Select Advanced Filter beside the filter icon to search the accounting information by Source, Username,Time, and Description. Or select Quick Filter to search under each column.

Step 6

Select a fabric and use the Delete icon to delete the fabric and event information from the list.

Step 7

Click the Print icon to print the event details.

Step 8

Click the Export to Excel icon to export the data.

Monitoring LAN

The LAN menu includes the following submenus:

Monitoring Performance Information for Ethernet

To monitor the performance information for ethernet from the Cisco DCNM Web UI, perform the following steps:

Procedure

Step 1

Choose Monitor > LAN > Ethernet.

The Ethernet window is displayed.

Step 2

You can use the drop-down to filter the view by Last 10 Minutes, Last Hour, Last Day, Last Week, Last Month, and Last Year.

There are variations to this procedure. In addition to these basic steps, you can also perform the following steps:

  • Select the name of an Ethernet port from the Name column to see a graph of the traffic across that Ethernet port for the past 24 hours. You can change the time range for this graph by selecting it from the drop-down list in the upper-right corner.

  • To export the data into a spreadsheet, click the Export icon in the upper-right corner and click Save.

  • Use the chart icons to view the traffic chart in varied views. You can also use the icons to Append, Predict, and Do not interpolate data.

    Note 

    Set the pmchart.doInterpolate property in the Server Properties window to false to use the Do not interpolate data option.

  • For the Rx/Tx calculation, see the following Rx/Tx calculation.

    Note 
    The conversion for Fabrics is 10 bit = 1 byte and for LAN traffic, the conversion is 8 bit = 1 byte.

    • Average Rx/Tx % = Average Rx/Tx divided by Speed * 100

    • Peak Rx/Tx % = Peak Rx/Tx divided by Speed * 100

Note 
If the performance tables do not contain any data, see the Thresholds section to turn on performance data collection.
Note 

To change traffic display unit from bytes to bits, From Cisco DCNM Web UI, choose Administration > DCNM Server > Server Properties, enter value as true for pm.showTrafficUnitAsbit property, and click Apply Changes.

Monitoring ISL Traffic and Errors

To monitor the ISL traffic and errors from the Cisco DCNM Web UI, perform the following steps:

Procedure

Step 1

Choose Monitor > LAN > Link.

The ISL Traffic and Errors window is displayed. This panel displays the ISL information for the end devices in that scope. You can reduce or expand the scope of what is displayed by using the scope menu.

Step 2

You can use the drop-down to filter the view by Last 10 Minutes, Last Hour, Last Day, Last Week, Last Month, and Last Year.

Note 
NaN (Not a Number) in the data grid means that the data is not available.

There are variations to this procedure. In addition to these basic steps, you can perform the following steps to view detailed information for ISLs:

  • To change the time range for this graph, select it from the drop-down list in the upper-right corner.

  • To view the detailed information for a specific period, drag the slider control to choose the time interval for which you need the information.

  • Use the chart icons to view the traffic chart in varied views. You can also use the icons to Append, Predict, and Do not interpolate data.

    Note 

    Set the pmchart.doInterpolate property in the Server Properties window to false to use the Do not interpolate data option.

  • To export the data into a spreadsheet, choose Export from the drop-down list in the Chart menu and then click Save.

  • For the Rx/Tx calculation, see the following Rx/Tx calculation.

    Note 
    The conversion for Fabrics is 10 bit = 1 byte and for LAN traffic, the conversion is 8 bit = 1 byte.

    • Average Rx/Tx % = Average Rx/Tx divided by Speed * 100

    • Peak Rx/Tx % = Peak Rx/Tx divided by Speed * 100

Note 
If the performance tables do not contain any data, see the Performance Setup Thresholds section to turn on performance.

Monitoring a vPC

The virtual port channel (vPC) feature enables you to view the links that are physically connected to different devices as a single port channel. A vPC is an extended form of a port channel which allows you to create redundancy and increase bisectional bandwidth by enabling multiple parallel paths between nodes and allowing load balancing traffic. Traffic is distributed among two single device vPC endpoints. If there is an inconsistency in the vPC configurations, the vPC does not function correctly.


Note

To view the vPC in vPC Performance, both primary and secondary device should be designated to the user. If either one kind of switch is not designated, vPC information is isplayed.

Cisco DCNM Web Client > Monitor> vPC displays only consistent vPCs displays both the consistent and inconsistent vPCs.

You can identify the inconsistent vPCs and resolve the inconsistencies in each vPC by using the Cisco DCNM Web UI > Configure > Deploy > vPC Peer and Web Client > Configure > Deploy > vPC.

Table 1 displays the following vPC configuration details in the data grid view.

Table 1. vPC Performance

Column

Description

Search box

Enter any string to filter the entries in their respective column.

vPC ID

Displays vPC ID's configured device.

Domain ID

Displays the domain ID of the vPC peer switches.

Multi Chassis vPC EndPoints

Displays the multi-chassis vPC endpoints for each vPC ID under a vPC domain.

Primary vPC Peer - Device Name

Displays the vPC Primary device name.

Primary vPC Peer - Primary vPC Interface

Displays the primary vPC interface.

Primary vPC Peer - Capacity

Displays the capacity for the primary vPC peer.

Primary vPC Peer - Avg. Rx/sec

Displays the average receiving speed of primary vPC peer.

Primary vPC Peer - Avg. Tx/sec

Displays the average sending speed of primary vPC peer.

Primary vPC Peer - Peak Util%

Displays the peak utilization percentage of primary vPC peer.

Secondary vPC Peer - Device Name

Displays the vPC secondary device name.

Secondary vPC Interface

Displays the secondary vPC interface.

Secondary vPC Peer - Capacity

Displays the capacity for the secondary vPC peer.

Secondary vPC Peer - Avg. Rx/sec

Displays the average receiving speed of secondary vPC peer.

Secondary vPC Peer - Avg. Tx/sec

Displays the average sending speed of secondary vPC peer.

Secondary vPC Peer - Peak Util%

Displays the peak utilization percentage of secondary vPC peer.

You can use this feature as following:

Monitoring vPC Performance

You can view the relationship among consistent virtual port channels (vPCs). You can view the statistics of all member interfaces and the aggregate of the statistics at the port-channel level.


Note

This tab only displays consistent vPCs.

To view the VPC performance information from the Cisco DCNM Web UI, perform the following steps:

Procedure
Step 1

Choose Monitor > LAN > vPC.

The vPC Performance statistics is displayed. The aggregated statistics of all vPCs are displayed in a tabular manner.

Step 2

Click the vPC ID.

The vPC topology, vPC Details, Peer-link Details, and Peer-link Status are displayed.

The vPC Consistency, Peer-link Consistency, and vPC Type2 Consistency for the vPC are displayed.

  • Click the vPC Details tab, you can view the parameter details of vPC Basic Setting and Layer 2 Settings for both Primary and Secondary vPC devices.

  • Click the Peer-link Details tab, to view the parameter details of peer-link vPC Global Setting and STP Global Settings for both Primary and Secondary vPC devices.

  • Click the Peer-link Status tab, the vPC Consistency, and Peer-Link Consistency status is displayed. The parameter details of Role Status and vPC Peer keep-alive Status for both Primary and Secondary vPC devices is also displayed.

Step 3

Click the peer-link icon in front of the Device Name in the Primary vPC peer or Secondary vPC peer column to view its member interface.

Step 4

Click the Show Chart icon of the corresponding interface to view its historical statistics.

The traffic distribution statistics appear at the bottom of the vPC window. By default, the Cisco DCNM Web Client displays the historical statistics for 24 hours.

There are variations to this procedure. In addition to these basic steps, you can also perform the following steps to view detailed information for flows:

  • To change the time range for this graph, select it from the drop-down list in the upper right corner.

  • To view the detailed information for a specific period, drag the slider control to choose the time interval for which you need the information.

  • Use the chart icons to view the traffic chart in varied views.

  • You can also use the icons to Append, Predict, and Do not interpolate data.

    Note 

    Set the pmchart.doInterpolate property in the Server Properties window to false to use the Do not interpolate data option.

  • To print the vPC Utilization data, click the Print icon in the upper-right corner. The vPC Utilization page appears.

  • To export the data into a spreadsheet, click the Export icon in the upper-right corner and click Save File.

Note 
If the performance tables do not contain any data, see the Thresholds section to turn on performance data collection.

Alarms

The Alarms menu includes the following submenus:

Viewing Alarms and Events

You can view the alarms, cleared alarms, and events.

Procedure

Step 1

Choose Monitor > Alarms > View.

Step 2

Choose any of the following tabs.

  • Alarms: This tab displays the alarms that are generated for various categories. This tab displays information such as ID (optional), Severity, Failure Source, Name, Category, Acknowledged, Creation Time, Last Updated (optional), Policy, and Message. You can specify the Refresh Interval in this tab. You can select one or more alarms and then acknowledge or unacknowledge their status using the Change Status drop-down list. In addition, you can select one or more alarms and then click the Delete button to delete them.
  • Cleared Alarms: This tab displays the cleared alarms. This tab displays information such as ID (optional), Severity, Failure Source, Name, Category, Acknowledged, Creation Time, Cleared At (optional), Cleared By, Policy, and Message. You can select one or more alarms and then click the Delete button to delete them.
  • Events: This tab displays the events that are generated for the switches. This tab displays information such as Ack, Acknowledged user, Group, Switch, Severity, Facility, Type, Count, Last Seen, and Description. You can select one or more events and then acknowledge or unacknowledge their status using the Change Status drop-down list. In addition, you can select one or more alarms and then click the Delete button to delete them. If you want to delete all events, click the Delete All button.

Monitoring and Adding Alarm Policies


Note

  • Alarm policies are stored in compute nodes. Therefore, run the appmgr backup command on each compute node in addition to taking a backup of DCNM.

You can forward alarms to registered SNMP listeners in DCNM. From Cisco DCNM web UI, choose Administration > DCNM Server > Server Properties, enter an external port address in alarm.trap.listener.address field, click Apply Changes, and restart DCNM services.


Note

Ensure that you select Forwarding check box in Alarm Policy creation dialog window to enable forwarding alarms to external SNMP listener.

You can add alarm policies for the following:

  • Device Health: Device health policies enable you to create alarms when Device ICMP Unreachable, Device SNMP Unreachable, or Device SSH Unreachable. Also, these policies enable you to monitor chassis temperature, CPU, and memory usage.

  • Interface Health: Interface health policies enable you to monitor Up or Down, Packet Discard, Error, Bandwidth details of the interfaces. By default all interfaces are selected for monitoring.

  • Syslog Alarm: Syslog Alarm Policy defines a pair of Syslog messages formats; one which raises the alarm, and one which clears the alarm.

Procedure

Step 1

Choose Monitor > Alarms > Alarm Policies.

Step 2

Select the Enable Alarms check box to enable alarm policies.

Step 3

From the Add drop-down list, choose any of the following:

  • Device Health Policy: Select the devices for which you want to create policies. Specify the policy name, description, CPU Utilization parameters, Memory Utilization parameters, Environment Temperature parameters, device availability, and device features. Under Device Features, you can select the BFD, BGP, and HSRP protocols. When these check boxes are selected, alarms are triggered for the following traps: BFD- ciscoBfdSessDown, ciscoBfdSessUp, BGP- bgpEstablishedNotification, bgpBackwardTransNotification, cbgpPeer2BackwardTransition (), cbgpPeer2EstablishedNotification, and HSRP- cHsrpStateChange. Please refer https://snmp.cloudapps.cisco.com/Support/SNMP/do/BrowseOID.do?local=en for detailed trap OID definition.
  • Interface Health Policy: Select the devices for which you want to create policies. Specify the policy name, description, link-state, Bandwidth (In/Out), Inbound errors, Outbound errors, Inbound Discards, and Outbound Discards.
  • Syslog Alarm Policy: Select the devices for which you want to create policies and then specify the following parameters.

    • Devices: Define the scope of this policy. Select individual devices or all devices to apply this policy.

    • Policy Name: Specify the name for this policy. It must be unique.

    • Description: Specify a brief description for this policy.

    • Severity: Define the severity level for this syslog alarm policy. Choices are: Critical, Major, Minor, and Warning.

    • Identifier: Specify the identifier portions of the raise & clear messages.

    • Raise Regex: Define the format of a syslog raise message. The syntax is as follows: Facility-Severity-Type: Message

    • Clear Regex: Define the format of a syslog clear message. The syntax is as follows: Facility-Severity-Type: Message

    The Regex definitions are simple expressions but not a complete regex. Variable regions of text are noted using $(LABEL) syntax. Each label represents a regex capture group (.+), which corresponds to one or more characters. The variable texts found in both raise and clear messages are used to associate the two messages. An Identifier is a sequence of one or more labels that appear in both messages. An Identifier is used to match a clear syslog message to the syslog message that raised the alarm. If the text appears only in one of the messages, it can be noted with a label and exclude it from the identifier.

    Example: A policy with "Value": "ID1-ID2",

    "syslogRaise": "SVC-5-DOWN: $(ID1) module $(ID2) is down $(REASON)"

    "syslogClear": "SVC-5-UP: $(ID1) module $(ID2) is up."

    In the example, ID1 and ID2 labels can be marked as an identifier to find the alarm. This identifier will be found in corresponding syslog messages. Label “REASON” is in the raise but not in the clear message. This label can be excluded from the identifier, as it has no impact on the syslog message to clear the alarm.

    Table 2. Example 1

    Identifier

    ID1-ID2

    Raise Regex

    ETHPORT-5-IF_ADMIN_UP: Interface Ethernet15/1 is admin up .

    Clear Regex

    ETHPORT-5-IF_DOWN_NONE: Interface Ethernet15/1 is down (Transceiver Absent)

    In the above example, the regex expressions are part of the syslog messages that appear in the terminal monitor.

    Table 3. Example 2

    Identifier

    ID1-ID2

    Raise Regex

    ETH_PORT_CHANNEL-5-PORT_DOWN: $(ID1): $(ID2) is down

    Clear Regex

    ETH_PORT_CHANNEL-5-PORT_UP: $(ID1): $(ID2) is up

    Table 4. Example 3

    Identifier

    ID1-ID2

    Raise Regex

    ETHPORT-5-IF_SFP_WARNING: Interface $(ID1), High Rx Power Warning

    Clear Regex

    ETHPORT-5-IF_SFP_WARNING: Interface $(ID1), High Rx Power Warning cleared

Step 4

Click OK to add the policy.

Syslog Messages in Terminal Monitor and Console

The following examples show how the syslog messages appear in the terminal monitor and the console. The regex expression is matched with the part of the syslog messages after the % sign. 

leaf-9516# terminal monitor
leaf-9516# conf t
leaf-9516(config)# int e15/1-32
leaf-9516(config-if-range)# no shut
2019 Aug 2 04:41:27 leaf-9516 %ETHPORT-5-IF_ADMIN_UP: Interface
Ethernet15/1 is admin up .
2019 Aug 2 04:41:27 leaf-9516 %ETHPORT-5-IF_DOWN_NONE: Interface
Ethernet15/1 is down (Transceiver Absent)
2019 Aug 2 04:41:27 leaf-9516 %ETHPORT-5-IF_ADMIN_UP: Interface
Ethernet15/2 is admin up .
2019 Aug 2 04:41:27 leaf-9516 %ETHPORT-5-IF_DOWN_NONE: Interface
Ethernet15/2 is down (Transceiver Absent)
2019 Aug 2 04:41:28 leaf-9516 %ETHPORT-5-IF_ADMIN_UP: Interface
Ethernet15/3 is admin up .

The syslog messages in the console have a similar format as they would appear in the terminal monitor, except for the additional port information enclosed in the %$ signs. However, the regex expression is matched with the part of the syslog messages after the last % sign. 

SR-leaf1# 2019 Aug 26 23:55:45 SR-leaf1 %$ VDC-1 %$ %PLATFORM-1-
PFM_ALERT: FAN_BAD: fan6
2019 Aug 26 23:56:15 SR-leaf1 %$ VDC-1 %$ %PLATFORM-1-PFM_ALERT:
FAN_BAD: fan6
2019 Aug 26 23:56:18 SR-leaf1 %$ VDC-1 %$ %ASCII-CFG-2-CONF_CONTROL:
System ready
2019 Aug 26 23:56:25 SR-leaf1 %$ VDC-1 %$ %PLATFORM-1-PFM_ALERT:
FAN_BAD: fan6
2019 Aug 26 23:56:35 SR-leaf1 %$ VDC-1 %$ %PLATFORM-1-PFM_ALERT:
FAN_BAD: fan6
2019 Aug 26 23:56:39 SR-leaf1 %$ VDC-1 %$ %VMAN-2-ACTIVATION_STATE:
Successfully activated virtual service 'guestshell+'
2019 Aug 26 23:56:39 SR-leaf1 %$ VDC-1 %$ %VMAN-2-GUESTSHELL_ENABLED:
The guest shell has been enabled. The command 'guestshell' may be used
to access it, 'guestshell destroy' to remove it.
2019 Aug 26 23:56:45 SR-leaf1 %$ VDC-1 %$ %PLATFORM-2-FAN_REMOVED: Fan
module 5 (Serial number ) Fan5(sys_fan5) removed
2019 Aug 26 23:56:45 SR-leaf1 %$ VDC-1 %$ %PLATFORM-1-PFM_ALERT:
System will shutdown in 2 minutes 0 seconds due to fan policy
__pfm_fanabsent_any_singlefan.
2019 Aug 26 23:56:45 SR-leaf1 %$ VDC-1 %$ %PLATFORM-1-PFM_ALERT:
FAN_BAD: fan6
2019 Aug 26 23:56:54 SR-leaf1 %$ VDC-1 %$ %PLATFORM-1-PFM_ALERT:
System will shutdown in 1 minutes 40 seconds due to fan policy
__pfm_fanabsent_any_singlefan.
2019 Aug 26 23:56:54 SR-leaf1 %$ VDC-1 %$ %PLATFORM-1-PFM_ALERT:
FAN_BAD: fan6
2019 Aug 26 23:57:03 SR-leaf1 %$ VDC-1 %$ %PLATFORM-2-FANMOD_FAN_OK:
Fan module 5 (Fan5(sys_fan5) fan) ok
2019 Aug 26 23:57:03 SR-leaf1 %$ VDC-1 %$ %PLATFORM-1-PFM_ALERT:
FAN_BAD: fan6

Activating Policies

After you create new alarm policies, activate them.
Procedure
Step 1

Choose Monitor > Alarms > Policies.

Step 2

Select the policies that you want to activate and then click the Activate button.

Deactivating Policies

You can deactivate the active alarm policies.
Procedure
Step 1

Choose Monitor > Alarms > Policies.

Step 2

Select the policies that you want to deactivate and then click the Deactivate button.

Importing Policies

You can create alarm policies using the import functionality.
Procedure
Step 1

Choose Monitor > Alarms > Policies and then click the Import button.

Step 2

Browse and select the policy file saved on your computer.

You can only import policies in text format.

Exporting Policies

You can export the alarm policies into a text file.
Procedure
Step 1

From the menu bar, choose Monitor > Alarms > Policies.

Step 2

Click the Export button and then select a location on your computer to store the exported file.

Editing Policies

Procedure
Step 1

From the menu bar, choose Monitor > Alarms > Policies.

Step 2

Select the policy that you want to edit.

Step 3

Click the Edit button and then make necessary changes.

Step 4

Click the OK button.

Deleting Policies

Procedure
Step 1

From the menu bar, choose Monitor > Alarms > Policies.

Step 2

Select the policy that you want to delete.

Step 3

Click the Delete button. The policy is deleted.

Enabling External Alarms

You can enable external alarms using one of the following methods:

  • Using Cisco DCNM Web UI

    1. From Cisco DCNM Web UI, choose Administration > DCNM Server > Server Properties.

    2. Locate the alarm.enable.external property.

    3. Enter the value in the field as true.

  • Using REST APIs

    1. Go the API documentation URL from your DCNM setup: https://<DCNM-ip>/api-docs

    2. Navigate to the Alarms section.

    3. Click POST > rest/alarms/enabledisableextalarm.

    4. Choose the body parameter value as true from the Value drop-down list.

    5. Click Try it out!.

  • Using CLI

    1. Log into the DCNM server using SSH.

    2. Set the alarm.enable.external property to true in the server.properties file.

      The filepath is /usr/local/cisco/dcm/fm/config/server.properties.

Health Monitor Alarms

Starting from Cisco DCNM Release 11.4(1), alarms are registered and created under the External alarm category by the Health Monitor.

Health Monitor: Alarm Policy

The Health Monitor external alarm category policy is automatically activated and enabled on all the devices in a fabric. The severity level of this alarm policy can be MINOR, MAJOR, or CRITICAL.

Alarms are raised and categorized as CRITICAL for the following events:

  • Elasticsearch (ES) Cluster Status is Red: Critical (For Cluster/HA mode only)

  • CPU/Memory/Disk Utilization/ES JVM Heap Used Percentage >= 90%

Alarms are raised and categorized as MAJOR for the following events:

  • ES Cluster Status is Yellow (For Cluster/HA mode only)

  • ES has unassigned shards (For Cluster/HA mode only)

  • CPU/Memory/Disk Utilization/ES JVM Heap Used Percentage >= 80% and <90%

Alarms are raised and categorized as MINOR for the following events:

  • CPU/Memory/Disk Utilization/ES JVM Heap Used Percentage >= 65% and <80%

  • Kafka: Number of partitions without active leader > 0

  • Kafka: Qualified partition leader not found. Unclear leaders > 0

Choose Monitor>Alarms>Policies to display the Health Monitor alarm policies. These alarm policies are not editable on the web UI. Click Activate or Deactivate to activate or deactivate the selected policy.

In case an alarm policy is deactivated using the GUI, any alarms created or cleared for that policy will not be displayed in the Monitor>Alarms>View tab. To delete a policy, select the checkbox next to the policy and click Delete. However, we recommend not deleting a policy from the GUI. When a fabric is deleted, the alarm policy along with all the active alarms for the devices in that fabric are deleted.

Health Monitor: Active Alarms

Choose Monitor>Alarms>View to display the active alarms.

To clear active alarms, select the checkbox next to the alarm, click Change Status and select Clear.

To delete active alarms, select the checkbox next to the alarm and click Delete.

Health Monitor: Cleared Alarms

To view the cleared alarms, select Monitor>Alarms>View>Cleared Alarms.

Click the arrow icon to display detailed information about the required alarm.

To delete a cleared alarm from the list of cleared alarms, select the checkbox next to the alarm and click Delete.

For more information on Alarms and Policies, refer Alarms.