All MIBs › FSS-COMMON-LOG
Organization: Fujitsu Network Communications, Inc.
Last Updated: 2016-01-20
Category: Technology: Logging/Syslog, Vendor: Fujitsu
Description: Fujitsu Network Communications MIB defining common logging objects and event notification structures for FSS platforms.
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.
What Is FSS-COMMON-LOG?
FSS-COMMON-LOG is a Fujitsu Network Communications vendor MIB defining common condition, alarm, and logging structures shared across the FSS (1Finity) family of optical/transport networking products. It exposes standing alarm tables and condition-qualifier objects that represent current fault conditions on managed network elements, including alarm object identity, alarm type, severity, service effect, and physical location. Its purpose is fault/status monitoring: fssStandingAlarmXTable entries (fssStdAlarmObjectIndex, fssStdAlarmType, fssStdAlarmSeverity, fssStdAlarmServEffect, fssStdAlarmLocn) let an operator see every currently active alarm condition on the device, its severity, and whether it affects service, which is central to spotting hardware or software faults on the transport platform. It is explicitly a shared/common module, depended upon by other Fujitsu 1Finity product-specific MIBs that reuse its alarm and condition-qualifier definitions rather than redefining them. It is deployed in Fujitsu 1Finity optical transport network elements where centralized alarm/fault visibility across many line cards or subsystems is required. Engineers can download the FSS-COMMON-LOG file directly to load it into their MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in FSS-COMMON-LOG. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.
Supported Devices
- Fujitsu Network Communications 1Finity optical/transport network elements
Monitoring Examples
An operator would walk fssStandingAlarmXTable to enumerate all currently standing alarms, checking fssStdAlarmSeverity and fssStdAlarmServEffect to prioritize which faults are service-affecting versus informational. fssStdAlarmObjectName and fssStdAlarmLocn pinpoint exactly which physical object (e.g. a line card or port) raised the alarm, and fssStdAlarmType identifies the fault category, such as a loss-of-signal or hardware failure condition, enabling rapid dispatch of a repair action.
What Can Be Monitored
- standing alarm list
- alarm severity
- service-affecting status
- alarm object/location identification
- alarm/condition type
Imported Objects
From FSS-COMMON-SMI
| fssCommon | OBJECT-IDENTITY |
From FSS-COMMON-TC
| FCCondEffect | |
| FCCondType | |
| FCDirection | |
| FCLocation | |
| FCObjectName | |
| FCServEffect | |
| FCSeverity | |
| FCStdObjectIndex | |
| FCStdTypeIndex | |
| FCTcCondType | |
| FCTcaCondType | |
| FCTimePeriod | |
| FCTrapHistIndex | |
| FCTrapType |
From SNMPv2-CONF
| MODULE-COMPLIANCE | |
| NOTIFICATION-GROUP | |
| OBJECT-GROUP |
From SNMPv2-SMI
| MODULE-IDENTITY | |
| NOTIFICATION-TYPE | |
| OBJECT-TYPE | |
| Unsigned32 |
From SNMPv2-TC
| DateAndTime | |
| DisplayString | |
| RowPointer |
OIDs
RFC description
Event notification and alarm condition definitions for Fujitsu 1Finity network communication devices.
Start monitoring Fujitsu 1Finity optical/transport network elements 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.