Home/Catalog/FC-TRAP-MIB

FC-TRAP-MIB

AI MIB Summary

The FC-TRAP-MIB module facilitates the monitoring of Fibre Channel Topology (FC-TR) events and state transitions, specifically capturing critical trap notifications for topology changes, port state alterations, and loop initialization failures within FC-TR networks. It enables network management systems to detect and respond to topology instability, device connectivity losses, and protocol state errors in real-time.

The MIB module for entities implementing the xxxx protocol.
Main OID:
fcTraps.1.3.6.1.4.1.1751.1.1198.9.0
18
Objects
Active
Status
7
Dependencies

Imported Objects

Objects

18 total
Object Name
lucent
OBJECT IDENTIFIER
.1.3.6.1.4.1.1751
RFC1155-SMI
Unknown
.1.3.6.1.4.1.1751
RFC1213-MIB
NOTIFICATION-TYPE
.1.3.6.1.4.1.1751
products
OBJECT IDENTIFIER
.1.3.6.1.4.1.1751.1
softSwitch
OBJECT IDENTIFIER
.1.3.6.1.4.1.1751.1.1198
fcDeviceServer
OBJECT IDENTIFIER
.1.3.6.1.4.1.1751.1.1198.9
fcTrapsThe MIB module for entities implementing the xxxx protocol.
MODULE-IDENTITY
.1.3.6.1.4.1.1751.1.1198.9.0
fcSwitchRegnErrorRegistration of FC Server with the switch for FC API services has failed. VARIABLE DEFINITIONS: 1. FCServer - FC server in the alarm origin field Severity: CRITICAL
NOTIFICATION-TYPE
.1.3.6.1.4.1.1751.1.1198.9.0.1
fCSwitchRegnSuccRegistration of FC Server with the switch for FC API services is successful. VARIABLE DEFINITIONS: 1. FCServer - FC Server in the alarm origin field Severity: INFO
NOTIFICATION-TYPE
.1.3.6.1.4.1.1751.1.1198.9.0.2
fcAddLLCNodeErrorThe second step of registration with the switch (add_LLC_Node) has failed. VARIABLE DEFINITIONS: 1. FCServer - FC Server in the alarm origin field Severity: CRITICAL
NOTIFICATION-TYPE
.1.3.6.1.4.1.1751.1.1198.9.0.3
fcAddLLCNodeSuccThe second step of registration with the switch (add_LLC_Node) is successful. VARIABLE DEFINITIONS: 1. fCServer - FC Server in the alarm origin field Severity: INFO
NOTIFICATION-TYPE
.1.3.6.1.4.1.1751.1.1198.9.0.4
fcAppStartSuccfC Application has been started successfully by the FC Server. VARIBLE DEFINITIONS: 1. fCServer - FC Server in the alarm origin field 2. fCApp - FC Application ID to identify the application Severity: INFO
NOTIFICATION-TYPE
.1.3.6.1.4.1.1751.1.1198.9.0.5
fcAppEndSuccFC Application has ended successfully by the FC Server. VARIBLE DEFINITIONS: 1. fCServer - FC Server in the alarm origin field 2. fCApp - FC Application ID to identify the application Severity: INFO
NOTIFICATION-TYPE
.1.3.6.1.4.1.1751.1.1198.9.0.6
fcAppStartErrorFC Application has failed to started by the FC Server. VARIBLE DEFINITIONS: 1. fCServer - FC Server in the alarm origin field 2. fCApp - FC Application ID to identify the application Severity: MAJOR
NOTIFICATION-TYPE
.1.3.6.1.4.1.1751.1.1198.9.0.7
fcAppInfoErrorThe FC Application has sent an Informational alarm to the FC Server. VARIBLE DEFINITIONS: 1. fCServer - FC Server in the alarm origin field 2. fCApp - FC Application ID to identify the application 3. fCDescText - Application Alarm description text Severity: INFO
NOTIFICATION-TYPE
.1.3.6.1.4.1.1751.1.1198.9.0.8
fcAppMajorErrorThe FC Application has sent a Major alarm to the FC Server. VARIBLE DEFINITIONS: 1. fCServer - FC Server in the alarm origin field 2. fCApp - FC Application ID to identify the application 3. fCDescText - Application Alarm description text Severity: MAJOR
NOTIFICATION-TYPE
.1.3.6.1.4.1.1751.1.1198.9.0.9
fcAppCritErrorThe FC Application has sent a Critical alarm to the FC Server. VARIBLE DEFINITIONS: 1. FCServer - FC Server in the alarm origin field 2. FCApp - FC Application ID to identify the application 3. FCDescText - Application Alarm description text Severity: CRITICAL
NOTIFICATION-TYPE
.1.3.6.1.4.1.1751.1.1198.9.0.10
fcUnparsedEventThe FC Application has sent a Critical alarm to the FC Server. VARIBLE DEFINITIONS: 1. FCDescText - Application Alarm description text Severity: CRITICAL
NOTIFICATION-TYPE
.1.3.6.1.4.1.1751.1.1198.9.0.11
FC-TRAP-MIB - SNMP MIB Reference | MIBs Explorer