SPIDCOM-ALARM-MIB

All MIBs › SPIDCOM-ALARM-MIB

Organization: SPiDCOM

Last Updated: 2002-07-15

Category: SPiDCOM

Description: Defines alarm objects and threshold conditions for SPiDCOM powerline networking equipment.

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 SPIDCOM-ALARM-MIB?

SPIDCOM-ALARM-MIB is a vendor MIB from SPiDCOM Technologies covering alarm objects and threshold-based fault conditions for SPiDCOM powerline networking (HomePlug/PLC) equipment. It exposes fault/alarm data: a tree of alarm definitions and threshold conditions used to flag abnormal operating states on the powerline communication device. As an alarm-monitoring MIB it is directly about surfacing hardware and/or link fault conditions -- such as a monitored parameter crossing a configured threshold -- so operators can be alerted to problems, though without concrete object names its exact hardware coverage (e.g. temperature vs. link quality) cannot be confirmed. It likely depends on general SNMPv2 notification conventions (SNMPv2-MIB, NOTIFICATION-TYPE) since it centers on alarm/threshold reporting. It is typically deployed on SPiDCOM powerline communication (PLC) modems and adapters used in broadband-over-powerline or smart grid access networks. Engineers can download the SPIDCOM-ALARM-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in SPIDCOM-ALARM-MIB. 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

SPiDCOM powerline communication (PLC) modem/adapter

Monitoring Examples

No sample objects were provided for this module, so no concrete object or table names can be cited with confidence. In practice an operator would likely poll an alarm status table to see which threshold-based alarms are currently active on a powerline device, using that to detect degraded line conditions or hardware faults on the PLC link. Any specific object names beyond this general description would be speculative given the lack of grounding data.

What Can Be Monitored

active alarm conditions
alarm threshold status
fault condition tree state

Imported Objects

From SNMPv2-CONF

NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-SMI

Counter32
Integer32
IpAddress
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE
TimeTicks
Unsigned32

From SNMPv2-TC

DateAndTime
DisplayString
TEXTUAL-CONVENTION

How to Use in IPNetwork Monitor

Example using neAlarmTrapCounter OID:

Select a SPiDCOM powerline communication (PLC) modem/adapter (alarm/threshold fault status) as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type neAlarmTrapCounter into the Find box to locate it in the OID tree, then select it and click OK. This object counts only the traps sent under node neAlarmTrap. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases sharply between polls relative to its normal baseline, since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.

OIDs

OID symbolic	OID numeric	Type	Access	Description
neAlarm	1.3.6.1.4.1.22764.2.1			Definition of the MIB tree structure to manage the Alarm Monitoring.
neAlarmActiveGroup	1.3.6.1.4.1.22764.2.1.13			The object regarding active alarms
U32 neAlarmActiveLastTrapIndex	1.3.6.1.4.1.22764.2.1.2	Unsigned32	read-only	This is the Alarm Index sent for which the last trap was sent
I32 neAlarmActivePhoto	1.3.6.1.4.1.22764.2.1.4	Integer32	read-write	When the manager sets this object, the agent sends all the active alarms from neAlarmtable to the manager.
STR neAlarmAdditionalText	1.3.6.1.4.1.22764.2.1.1.1.2	DisplayString	read-only	neAlarmDescription is a brief description of a given alarm. E.g. Tributary 1 Card Fail.
INT neAlarmAlreadyPresent	1.3.6.1.4.1.22764.2.1.1.1.8	INTEGER	read-only	This field could be use to know if alarm already there.
STR neAlarmDescription	1.3.6.1.4.1.22764.2.1.1.1.4	DisplayString	read-only	neAlarmDescription represents a description of the Alarm, as per [X.733]
neAlarmEntry	1.3.6.1.4.1.22764.2.1.1.1		not-accessible	neAlarmMibEntry: an entry in neAlarmMibTable.
neAlarmGroup	1.3.6.1.4.1.22764.2.1.11			The objects you can find in this MIB.
U32 neAlarmIndex	1.3.6.1.4.1.22764.2.1.1.1.1	Unsigned32	read-only	neAlarmIndex is a unique identifier for an alarm on a given type of NE. The association between the alarmIndex and the alarm for the type of NE is described in the NE MIB. For example for the SRA L it is in the NETVIEWER SRAL 16X2 MIB.
STR neAlarmManagedObject	1.3.6.1.4.1.22764.2.1.1.1.6	DisplayString	read-only	neAlarmManagedObject represents the managed Object values for the alarms.
ITU neAlarmProbableCause	1.3.6.1.4.1.22764.2.1.1.1.3	ItuAlarmProbableCause	read-only	neAlarmProbablecause represents the probable cause values for the alarms as per [X.733].
INT neAlarmStatus	1.3.6.1.4.1.22764.2.1.1.1.7	INTEGER	read-write	If neAlarmStatus is active(1) the current alarm is active for the NE. If neAlarmStatus is inactive(2), the current alarm is inactive (normality) for the NE. If neAlarmStatus is notAffected(3), the current alarm is not significant for the NE.
neAlarmTable	1.3.6.1.4.1.22764.2.1.1		not-accessible	neAlarmTable represents all the possible alarms on the NE, stating the probable cause, the alarm type and the perceived severity as per [X.733]. Note that each entry is significant until neAlarmIsApplicable is applicable(1). Entries should never be removed unless the NE they refer to disconnected NEs. To invalidate an entry the Agent sets neAlarmIsApplicable to notApplicable(0). before invalidating the entry, the agent sets the neAlarmPerceivedSeverity to cleared.
TIK neAlarmTimeStamp	1.3.6.1.4.1.22764.2.1.1.1.9	TimeTicks	read-only	The alarm timestamp.
neAlarmTrap	1.3.6.1.4.1.22764.2.1.10
C32 neAlarmTrapCounterEx	1.3.6.1.4.1.22764.2.1.10.2	Counter32	read-only	This object counts only the traps sent under node neAlarmTrap.
IP neAlarmTrapDestiIp	1.3.6.1.4.1.22764.2.1.10.4	IpAddress	read-write	The @IP where traps are sent
U32 neAlarmTrapDestiPort	1.3.6.1.4.1.22764.2.1.10.5	Unsigned32	read-write	The UDP port where traps are sent
NET neAlarmTrapFilter	1.3.6.1.4.1.22764.2.1.10.3	NeTrapFilter	read-write	If trapFilterOn, the agent sends no traps under node neAlarmTrap.
ITU neAlarmType	1.3.6.1.4.1.22764.2.1.1.1.5	ItuAlarmType	read-only	neAlarmType represents the event type values for the alarms as per [X.733].
I32 neClearTerminatedAlarms	1.3.6.1.4.1.22764.2.1.3	Integer32	read-write	When the manager sets this object, the agent deletes its alarms which status is terminated

RFC description

Manages alarm monitoring with ITU X.733 probable cause definitions and alarm state tracking.

Start monitoring SPiDCOM powerline communication (PLC) modem/adapter (alarm/threshold fault 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.

Download SPIDCOM-ALARM-MIB