Monitoring Hardware

This chapter includes the following sections:

Monitoring Management Interfaces

Management Interfaces Monitoring Policy

This policy defines how the mgmt0 Ethernet interface on the fabric interconnect should be monitored. If Cisco UCS detects a management interface failure, a failure report is generated. If the configured number of failure reports is reached, the system assumes that the management interface is unavailable and generates a fault. By default, the management interfaces monitoring policy is disabled.

If the affected management interface belongs to a fabric interconnect which is the managing instance, Cisco UCS confirms that the subordinate fabric interconnect's status is up, that there are no current failure reports logged against it, and then modifies the managing instance for the end-points.

If the affected fabric interconnect is currently the primary inside of a high availability setup, a failover of the management plane is triggered. The data plane is not affected by this failover.

You can set the following properties related to monitoring the management interface:

  • Type of mechanism used to monitor the management interface.
  • Interval at which the management interface's status is monitored.
  • Maximum number of monitoring attempts that can fail before the system assumes that the management is unavailable and generates a fault message.

Important:
In the event of a management interface failure on a fabric interconnect, the managing instance may not change if one of the following occurs:
  • A path to the end-point through the subordinate fabric interconnect does not exist.
  • The management interface for the subordinate fabric interconnect has failed.
  • The path to the end-point through the subordinate fabric interconnect has failed.

Configuring the Management Interfaces Monitoring Policy

Procedure
    Step 1   Enter monitoring mode.

    UCS-A# scope monitoring

    Step 2   Enable or disable the management interfaces monitoring policy.

    UCS-A /monitoring # set mgmt-if-mon-policy admin-state {enabled | disabled}

    Step 3   Specify the number of seconds that the system should wait between data recordings.

    UCS-A /monitoring # set mgmt-if-mon-policy poll-interval

    Enter an integer between 90 and 300.
    Step 4   Specify the maximum number of monitoring attempts that can fail before the system assumes that the management interface is unavailable and generates a fault message.

    UCS-A /monitoring # set mgmt-if-mon-policy max-fail-reports num-mon-attempts

    Enter an integer between 2 and 5.
    Step 5   Specify the monitoring mechanism that you want the system to use. UCS-A /monitoring # set mgmt-if-mon-policy monitor-mechanism {mii-status | ping-arp-targets | ping-gateway
    • mii-status —The system monitors the availability of the Media Independent Interface (MII).
    • ping-arp-targets —The system pings designated targets using the Address Resolution Protocol (ARP).
    • ping-gateway —The system pings the default gateway address specified for this Cisco UCS instance in the management interface.
    Step 6   If you selected mii-status as your monitoring mechanism, configure the following properties:
    1. Specify the number of seconds that the system should wait before requesting another response from the MII if a previous attempt fails.

      UCS-A /monitoring # set mgmt-if-mon-policy mii-retry-interval num-seconds

      Enter an integer between 3 and 10.

    2. Specify the number of times that the system polls the MII until the system assumes that the interface is unavailable.

      UCS-A /monitoring # set mgmt-if-mon-policy mii-retry-count num-retries

      Enter an integer between 1 and 3.
    Step 7   If you selected ping-arp-targets as your monitoring mechanism, configure the following properties:
    1. Specify the first IP address the system pings.

      UCS-A /monitoring # set mgmt-if-mon-policy arp-target1 ip-addr

      Type 0.0.0.0 to remove the ARP target.

    2. Specify the second IP address the system pings.

      UCS-A /monitoring # set mgmt-if-mon-policy arp-target2 ip-addr

      Type 0.0.0.0 to remove the ARP target.

    3. Specify the third IP address the system pings.

      UCS-A /monitoring # set mgmt-if-mon-policy arp-target3 ip-addr

      Type 0.0.0.0 to remove the ARP target.

    4. Specify the number of ARP requests to send to the target IP addresses.

      UCS-A /monitoring # set mgmt-if-mon-policy arp-requests num-requests

      Enter an integer between 1 and 5.

    5. Specify the number of seconds to wait for responses from the ARP targets before the system assumes that they are unavailable.

      UCS-A /monitoring # set mgmt-if-mon-policy arp-deadline num-seconds

      Enter a number between 5 and 15.
    Step 8   If you selected ping-gateway as your monitoring mechanism, configure the following properties:
    1. Specify the number of times the system should ping the gateway.

      UCS-A /monitoring # set mgmt-if-mon-policy ping-requests

      Enter an integer between 1 and 5.

    2. Specify the number of seconds to wait for a response from the gateway until the system assumes that the address is unavailable.

      UCS-A /monitoring # set mgmt-if-mon-policy ping-deadline

      Enter an integer between 5 and 15.
    Step 9   Commit the transaction to the system configuration.

    UCS-A /monitoring # commit-buffer

    The following example creates a monitoring interface management policy using the Media Independent Interface (MII) monitoring mechanism and commits the transaction:

    UCS-A# scope monitoring
UCS-A /monitoring # set mgmt-if-mon-policy admin-state enabled
UCS-A /monitoring* # set mgmt-if-mon-policy poll-interval 250
UCS-A /monitoring* # set mgmt-if-mon-policy max-fail-reports 2
UCS-A /monitoring* # set mgmt-if-mon-policy monitor-mechanism set mii-status
UCS-A /monitoring* # set mgmt-if-mon-policy mii-retry-count 3
UCS-A /monitoring* # set mgmt-if-mon-policy mii-retry-interval 7
UCS-A /monitoring* # commit-buffer
UCS-A /monitoring #