CORIANT-GROOVE-MIB

Description: Manages Coriant Groove optical transponder configuration, performance monitoring, and alarm objects.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

CORIANT-GROOVE-MIB is Coriant's SNMP MIB for the Groove G30 optical transponder platform, covering configuration, performance monitoring, and - most extensively in the sampled objects - fault and alarm reporting for the device. It exposes rich alarm/notification data including the affected functional entity, condition type, location, direction, severity level, service-affecting flag, and timestamps for each raised or cleared condition. This makes it central to monitoring the operational/fault status of the optical transponder hardware - surfacing hardware faults, degraded signal conditions, and their severity/service impact rather than raw performance counters. As an optical-transport product MIB it likely complements standard ITU-T/telecom performance-monitoring conventions and Coriant's broader product MIB tree ("coriant.products.fault"). It is typically deployed in optical/DWDM transport networks where NOC staff monitor Groove G30 transponders for line/card faults and service-affecting alarms. Engineers can download the CORIANT-GROOVE-MIB file directly to load it into their MIB browser.

An operator would subscribe to traps carrying notificationConditionType, notificationSeverityLevel, and notificationServiceAffect to be alerted the moment a Groove G30 transponder raises a fault, with notificationFmEntity and notificationLocation identifying exactly which component and direction (line/client side) is affected. notificationOccurrenceDateTime and notificationLastSeverityLevel let an operator track when a condition started and whether its severity has changed or cleared. A notificationServiceAffect flag of 'true' combined with a high severity would flag a fault requiring immediate attention versus a minor, non-service-affecting warning.