McData Fibre Switch

This connector discovers the enclosure and fiber-channel ports of McData SAN switches as well as various environment sensors (temperatures, fans, power supplies, etc.). It relies on the SNMP protocol.

This connector supersedes:

FibreAllianceSwitch^[2]

blade^[3] enterprise^[4] hardware^[5] mcdata^[6] storage^[7]

Target

Typical platform: McData SAN

Operating system: Storage System

Prerequisites

Leverages: McData SNMP Agent (EF-6000-MIB)

Technology and protocols: SNMP

Examples

CLI

metricshub HOSTNAME -t storage -c +McData --snmp v2c --community public

metricshub.yaml

resourceGroups:
  <RESOURCE_GROUP>:
    resources:
      <HOSTNAME-ID>:
        attributes:
          host.name: <HOSTNAME> # Change with actual host name
          host.type: storage
        connectors: [ +McData ] # Optional, to load only this connector
        protocols:
          snmp:
            version: v2c # Read documentation for v1, v2c and v3
            community: public # or probably something more secure

Connector Activation Criteria

The McData Fibre Switch connector will be automatically activated, and its status will be reported as OK if all the below criteria are met:

An SNMP Get-Next on the OID 1.3.6.1.4.1.289.2.1.1.2.2.1.1 must return a value in the same subtree

Metrics

Type	Collected Metrics	Specific Attributes
blade	`hw.status{hw.type="blade", state="degraded\|failed\|ok"}` `hw.status{hw.type="blade", state="present"}`	`blade_name` `hw.parent.type` `id` `info` `model` `name` `serial_number`
enclosure	`hw.status{hw.type="enclosure", state="present"}`	`id` `model` `name` `serial_number` `type` `vendor`
fan	`hw.status{hw.type="fan", state="degraded\|failed\|ok"}` `hw.status{hw.type="fan", state="present"}`	`hw.parent.type` `id` `info` `name` `sensor_location`
network	`hw.errors{hw.type="network"}` `hw.network.bandwidth.limit` `hw.network.full_duplex` `hw.network.io{direction="receive"}` `hw.network.io{direction="transmit"}` `hw.network.packets{direction="receive"}` `hw.network.packets{direction="transmit"}` `hw.network.up` `hw.status{hw.type="network", state="degraded\|failed\|ok"}` `hw.status{hw.type="network", state="present"}`	`bandwidth` `device_type` `hw.parent.id` `hw.parent.type` `id` `name` `physical_address` `physical_address_type` `serial_number` `vendor`
other_device	`hw.status{hw.type="other_device", state="degraded\|failed\|ok"}` `hw.status{hw.type="other_device", state="present"}`	`device_type` `hw.parent.type` `id` `info` `name`
power_supply	`hw.status{hw.type="power_supply", state="degraded\|failed\|ok"}` `hw.status{hw.type="power_supply", state="present"}`	`hw.parent.type` `id` `info` `name` `power_supply_type`
temperature	`hw.status{hw.type="temperature", state="degraded\|failed\|ok"}` `hw.status{hw.type="temperature", state="present"}`	`hw.parent.id` `hw.parent.type` `id` `name` `sensor_location`

Search Results for {{siteSearch | truncate:'50'}}

No results.

MetricsHub
MetricsHub Enterprise 1.0.02

Description

Target

Prerequisites

Examples

CLI

metricshub.yaml

Connector Activation Criteria

Metrics

Search Results for {{siteSearch | truncate:'50'}}

MetricsHub MetricsHub Enterprise 1.0.02

Search Results for {{siteSearch | truncate:'50'}}

MetricsHub
MetricsHub Enterprise 1.0.02