This release introduces a series of bulk statistics for monitoring the health of the DI-network on a VPC-DI platform. This information is similar to that provided in the output of the show cloud monitor di-network summary Exec mode command.
A new mon-di-net schema has been introduced in this release with the following statistics:
src-card – Source card slot number on which monitoring has been performed.
dest-card – Destination card slot number to which traffic was routed.
total-pkts-5mins – Total number of packets sent over the past 5 minutes.
total-drops-5mins – Total number of packets that were dropped over the past 5 minutes.
total-pkts-60mins – Total number of packets sent over the past 60 minutes.
total-drops-60mins – Total number of packets that were dropped over the past 60 minutes.
total-pkts – Total number of all packets sent.
total-pkts-jumbo – Total number of jumbo packets sent.
total-drops – Total number of jumbo and non-jumbo test packets that were dropped.
total-drops-jumbo – Number of jumbo test packets that were dropped.
latency-warnings – Total number of times the latency has exceeded the threshold.
long-rtt – Longest Round Trip Time (RTT) in milliseconds.
average-rtt – Average Round Trip Time (RTT) in milliseconds.
The new mon-di-net BulkStats Mode command has been added to configure the collection of statistics for the Mon-DI-Net schema.
See the Bulk Statistics chapter in the System Administration Guide for information about configuring bulk statistic collection.
DI-Network Heartbeat Thresholds
This feature adds the capability to define thresholds for the internal DI-network for percentage heartbeat loss in order to monitor the card-to-card network health in a VPC-DI deployment.
When heartbeat loss (on any of the cards) crosses a set limit of threshold, this feature raises alarms/SNMP trap to indicate the loss.
The internal High Availability Task (HAT) tracks the percentage heartbeat loss over the past 5 minutes and past 60 minutes between cards and can generate SNMP alarms if a threshold has been crossed or a previous alarm has been cleared.
There can be multiple cards in the system and any card can raise this same trap ID but with different card information.
The scope of this funtionality is across the system. It is not specific to any service and is configured at the Global Configuration mode.
The following steps describe how to configure threshold levels to generate SNMP alarms if the percentage of heartbeats lost exceeds the configured level.
The internal High Availability Task (HAT) is alway monitoring the heartbeats across the VMs on the internal DI-Network. This information can be displayed at any time using the show cloud monitor di-network summary Exec mode command.
For supplemental information related to this feature, refer to the Global Configuration Mode Commands section of the Command Line Reference.
The following alarms/traps are generated when these thresholds are exceeded:
ThreshHatHb5MinLoss / ThreshClearHatHb5MinLoss.
ThreshHatHb60MinLoss / ThreshClearHatHb60MinLoss.
See the SNMP MIB Reference for more details about these alarms/traps.
Saving Your Configuration
When you configure thresholds they are not permanent unless you save the changes. When you have completed configuring thresholds, save your configuration to flash memory, an external memory device, and/or a network location using the Exec mode command save configuration. For additional information on how to verify and save configuration files, refer to the System Administration Guide and the Command Line Interface Reference.