Initial commit
This commit is contained in:
David Leutgeb
770
MIBS/4rf/4RF-APRISAXE-EVENTS
Normal file
770
MIBS/4rf/4RF-APRISAXE-EVENTS
Normal file
@@ -0,0 +1,770 @@
|
||||
APRISAXE-EVENTS-4RF DEFINITIONS ::= BEGIN
|
||||
|
||||
--
|
||||
-- File: $Id: 4RF-APRISAXE-EVENTS.txt,v 1.40 2007/07/20 02:50:01 ma Exp $
|
||||
--
|
||||
-- Copyright: 2004 4RF COMMUNICATIONS LTD
|
||||
--
|
||||
-- Description:
|
||||
-- Event MIB for AprisaXE project, the values in this file are not accessible
|
||||
-- except as notifications.
|
||||
--
|
||||
-- Versions:
|
||||
--
|
||||
-- Release 3
|
||||
-- Added support for 4-wire cards and configurable cross-connections
|
||||
--
|
||||
-- Notes:
|
||||
-- None
|
||||
--
|
||||
|
||||
|
||||
IMPORTS
|
||||
|
||||
-- Standard imports
|
||||
MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY, NOTIFICATION-TYPE,
|
||||
Integer32, Unsigned32, Counter32, IpAddress
|
||||
FROM SNMPv2-SMI
|
||||
TEXTUAL-CONVENTION, DisplayString
|
||||
FROM SNMPv2-TC
|
||||
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
|
||||
FROM SNMPv2-CONF
|
||||
|
||||
-- 4RF Specific imports
|
||||
fourRFAprisaXE
|
||||
FROM PRODUCTS-MIB-4RF
|
||||
FourRFAlarmStatus, FourRFAlarmSeverity, FourRFAlarmEnabled, FourRFAlarmPresent,
|
||||
FourRFImageVersion, FourRFHardwareVersion
|
||||
FROM COMMON-TC-4RF
|
||||
AprisaXEAlarmType, AprisaXECardType, AprisaXESlotNumber,
|
||||
AprisaXEDataStatus, AprisaXEPortNumber
|
||||
FROM APRISAXE-TC-4RF
|
||||
aprisaXEObjects, aprisaXEEvents
|
||||
FROM APRISAXE-MIB-4RF
|
||||
fourRFModules
|
||||
FROM MIB-4RF;
|
||||
|
||||
|
||||
-- Module Identification
|
||||
aprisaXE4RFEventModule MODULE-IDENTITY
|
||||
LAST-UPDATED "200704300000Z"
|
||||
ORGANIZATION "www.4rf.com"
|
||||
CONTACT-INFO
|
||||
"postal: 4RF Communications Ltd
|
||||
26 Glover Street
|
||||
Ngauranga
|
||||
PO Box 13-506
|
||||
Wellington 6032
|
||||
New Zealand
|
||||
|
||||
phone: +64 4 499 6000
|
||||
email: support@4rf.com"
|
||||
DESCRIPTION "Event MIB for the AprisaXE project"
|
||||
|
||||
-- Revision history
|
||||
-- (in reverse chronological order)
|
||||
|
||||
REVISION "200704300000Z"
|
||||
DESCRIPTION "Second draft"
|
||||
|
||||
REVISION "200411300334Z"
|
||||
DESCRIPTION "First draft"
|
||||
::= { fourRFModules 7 }
|
||||
|
||||
|
||||
-- Trap Values
|
||||
|
||||
aprisaXEEventValues OBJECT IDENTIFIER ::= { aprisaXEObjects 1000 }
|
||||
|
||||
|
||||
-- Alarm event values
|
||||
|
||||
aprisaXEEventAlarmStatus OBJECT-TYPE
|
||||
SYNTAX FourRFAlarmPresent
|
||||
MAX-ACCESS accessible-for-notify
|
||||
STATUS current
|
||||
DESCRIPTION "The status of an alarm event."
|
||||
::= { aprisaXEEventValues 1 }
|
||||
|
||||
aprisaXEEventAlarmSeverity OBJECT-TYPE
|
||||
SYNTAX FourRFAlarmSeverity
|
||||
MAX-ACCESS accessible-for-notify
|
||||
STATUS current
|
||||
DESCRIPTION "The severity of the alarm."
|
||||
::= { aprisaXEEventValues 2 }
|
||||
|
||||
aprisaXEEventAlarmValue OBJECT-TYPE
|
||||
SYNTAX Integer32
|
||||
MAX-ACCESS accessible-for-notify
|
||||
STATUS current
|
||||
DESCRIPTION "Indicatesthe current value."
|
||||
::= { aprisaXEEventValues 3 }
|
||||
|
||||
aprisaXEEventAlarmThreshold OBJECT-TYPE
|
||||
SYNTAX Integer32
|
||||
MAX-ACCESS accessible-for-notify
|
||||
STATUS current
|
||||
DESCRIPTION "Indicates the level at which the alarm was set."
|
||||
::= { aprisaXEEventValues 4 }
|
||||
|
||||
aprisaXEEventAlarmType OBJECT-TYPE
|
||||
SYNTAX AprisaXEAlarmType
|
||||
MAX-ACCESS accessible-for-notify
|
||||
STATUS current
|
||||
DESCRIPTION "The alarm type."
|
||||
::= { aprisaXEEventValues 5 }
|
||||
|
||||
|
||||
-- Card mismatch event values
|
||||
|
||||
aprisaXEEventCardExpected OBJECT-TYPE
|
||||
SYNTAX AprisaXECardType
|
||||
MAX-ACCESS accessible-for-notify
|
||||
STATUS current
|
||||
DESCRIPTION "The type of MUX card expected in a slot."
|
||||
::= { aprisaXEEventValues 6 }
|
||||
|
||||
aprisaXEEventCardInstalled OBJECT-TYPE
|
||||
SYNTAX AprisaXECardType
|
||||
MAX-ACCESS accessible-for-notify
|
||||
STATUS current
|
||||
DESCRIPTION "The type of MUX card found in a slot."
|
||||
::= { aprisaXEEventValues 7 }
|
||||
|
||||
aprisaXEEventCardSlot OBJECT-TYPE
|
||||
SYNTAX AprisaXESlotNumber
|
||||
MAX-ACCESS accessible-for-notify
|
||||
STATUS current
|
||||
DESCRIPTION "The slot containing the unexpected card."
|
||||
::= { aprisaXEEventValues 8 }
|
||||
|
||||
aprisaXEEventCardStatus OBJECT-TYPE
|
||||
SYNTAX FourRFAlarmPresent
|
||||
MAX-ACCESS accessible-for-notify
|
||||
STATUS current
|
||||
DESCRIPTION "Indicates whether the alarm is present or has been cleared."
|
||||
::= { aprisaXEEventValues 9 }
|
||||
|
||||
aprisaXEEventCardPort OBJECT-TYPE
|
||||
SYNTAX AprisaXEPortNumber
|
||||
MAX-ACCESS accessible-for-notify
|
||||
STATUS current
|
||||
DESCRIPTION "The port reporting the event."
|
||||
::= { aprisaXEEventValues 10 }
|
||||
|
||||
|
||||
-- Characterisation Data Status
|
||||
|
||||
aprisaXEEventCharacterisationStatus OBJECT-TYPE
|
||||
SYNTAX AprisaXEDataStatus
|
||||
MAX-ACCESS accessible-for-notify
|
||||
STATUS current
|
||||
DESCRIPTION "Indicates whether the characterisation is valid or invalid."
|
||||
::= { aprisaXEEventValues 15 }
|
||||
|
||||
|
||||
-- MIB Data Status
|
||||
|
||||
aprisaXEEventMibStatus OBJECT-TYPE
|
||||
SYNTAX AprisaXEDataStatus
|
||||
MAX-ACCESS accessible-for-notify
|
||||
STATUS current
|
||||
DESCRIPTION "Indicates whether the MIB is valid or invalid."
|
||||
::= { aprisaXEEventValues 16 }
|
||||
|
||||
|
||||
-- ***************************************************************************
|
||||
-- Traps
|
||||
-- ***************************************************************************
|
||||
|
||||
aprisaXELinkAlarmsEvents OBJECT-IDENTITY
|
||||
STATUS current
|
||||
DESCRIPTION "The events for the link alarms."
|
||||
::= { aprisaXEEvents 1 }
|
||||
|
||||
aprisaXELinkAlarmsEventsV2 OBJECT-IDENTITY
|
||||
STATUS current
|
||||
DESCRIPTION "The SNMPv2 events for the link alarms."
|
||||
::= { aprisaXELinkAlarmsEvents 0 }
|
||||
|
||||
aprisaXEThresholdAlarmEvent NOTIFICATION-TYPE
|
||||
OBJECTS { aprisaXEEventAlarmStatus,
|
||||
aprisaXEEventAlarmSeverity,
|
||||
aprisaXEEventAlarmValue,
|
||||
aprisaXEEventAlarmThreshold,
|
||||
aprisaXEEventAlarmType
|
||||
}
|
||||
STATUS current
|
||||
DESCRIPTION "Event indicating a change in state of a threshold alarm.
|
||||
It will be sent whenever the status of the alarm changes from
|
||||
noAlarm to alarmPresent and vice versa."
|
||||
::= { aprisaXELinkAlarmsEventsV2 1 }
|
||||
|
||||
|
||||
-- ***************************************************************************
|
||||
-- Receiver Traps
|
||||
-- ***************************************************************************
|
||||
|
||||
aprisaXERxSynthOutOfLockAlarmEvent NOTIFICATION-TYPE
|
||||
OBJECTS { aprisaXEEventAlarmStatus }
|
||||
STATUS current
|
||||
DESCRIPTION "Event indicating a change in state of the Rx synthesizer out of lock alarm.
|
||||
It will be sent whenever the status of the alarm changes from
|
||||
noAlarm to alarmPresent and vice versa."
|
||||
::= { aprisaXELinkAlarmsEventsV2 10 }
|
||||
|
||||
aprisaXEAlarmRxCDataEvent NOTIFICATION-TYPE
|
||||
OBJECTS { aprisaXEEventCharacterisationStatus }
|
||||
STATUS current
|
||||
DESCRIPTION "Event indicating a change in state of the receiver
|
||||
characterisation data alarm."
|
||||
::= { aprisaXELinkAlarmsEventsV2 11 }
|
||||
|
||||
aprisaXEAlarmRx12VStatusEvent NOTIFICATION-TYPE
|
||||
OBJECTS { aprisaXEEventAlarmStatus }
|
||||
STATUS current
|
||||
DESCRIPTION "Event indicating a change in state of the Rx synthesizer out of lock alarm.
|
||||
It will be sent whenever the status of the alarm changes from
|
||||
noAlarm to alarmPresent and vice versa."
|
||||
::= { aprisaXELinkAlarmsEventsV2 12 }
|
||||
|
||||
aprisaXEAlarmRxOffEvent NOTIFICATION-TYPE
|
||||
OBJECTS { aprisaXEEventAlarmStatus }
|
||||
STATUS current
|
||||
DESCRIPTION "Event indicating a change in state of receiver, when it is
|
||||
turned on or off.
|
||||
It will be sent whenever the status of the alarm changes from
|
||||
noAlarm to alarmPresent and vice versa."
|
||||
::= { aprisaXELinkAlarmsEventsV2 13 }
|
||||
|
||||
aprisaXEAlarmRxBadMibEvent NOTIFICATION-TYPE
|
||||
OBJECTS { aprisaXEEventMibStatus }
|
||||
STATUS current
|
||||
DESCRIPTION "Event indicating a change in state of the receiver
|
||||
MIB data alarm."
|
||||
::= { aprisaXELinkAlarmsEventsV2 14 }
|
||||
|
||||
|
||||
-- ***************************************************************************
|
||||
-- Transmitter Traps
|
||||
-- ***************************************************************************
|
||||
|
||||
aprisaXEAlarmTxCDataEvent NOTIFICATION-TYPE
|
||||
OBJECTS { aprisaXEEventCharacterisationStatus }
|
||||
STATUS current
|
||||
DESCRIPTION "Event indicating a change in state of the transmitter
|
||||
characterisation data alarm."
|
||||
::= { aprisaXELinkAlarmsEventsV2 20 }
|
||||
|
||||
aprisaXEAlarmTxSynthOutOfLockEvent NOTIFICATION-TYPE
|
||||
OBJECTS { aprisaXEEventAlarmStatus }
|
||||
STATUS current
|
||||
DESCRIPTION "Event indicating a change in state of the transmitter
|
||||
synthesiser out of lock alarm."
|
||||
::= { aprisaXELinkAlarmsEventsV2 21 }
|
||||
|
||||
aprisaXEAlarmTx28VStatusEvent NOTIFICATION-TYPE
|
||||
OBJECTS { aprisaXEEventAlarmStatus }
|
||||
STATUS current
|
||||
DESCRIPTION "Event indicating a change in state of the transmitter
|
||||
28V supply status alarm."
|
||||
::= { aprisaXELinkAlarmsEventsV2 22 }
|
||||
|
||||
aprisaXEAlarmTx11VStatusEvent NOTIFICATION-TYPE
|
||||
OBJECTS { aprisaXEEventAlarmStatus }
|
||||
STATUS current
|
||||
DESCRIPTION "Event indicating a change in state of the transmitter
|
||||
11V supply status alarm."
|
||||
::= { aprisaXELinkAlarmsEventsV2 23 }
|
||||
|
||||
aprisaXEAlarmTx5VStatusEvent NOTIFICATION-TYPE
|
||||
OBJECTS { aprisaXEEventAlarmStatus }
|
||||
STATUS current
|
||||
DESCRIPTION "Event indicating a change in state of the transmitter
|
||||
5V digital supply status alarm."
|
||||
::= { aprisaXELinkAlarmsEventsV2 24 }
|
||||
|
||||
aprisaXEAlarmTxAmplifierBalanceEvent NOTIFICATION-TYPE
|
||||
OBJECTS { aprisaXEEventAlarmStatus }
|
||||
STATUS current
|
||||
DESCRIPTION "Event indicating a change in state of the transmitter
|
||||
amplifier balance status alarm."
|
||||
::= { aprisaXELinkAlarmsEventsV2 25 }
|
||||
|
||||
aprisaXEAlarmTxBadMibEvent NOTIFICATION-TYPE
|
||||
OBJECTS { aprisaXEEventMibStatus }
|
||||
STATUS current
|
||||
DESCRIPTION "Event indicating a change in state of the transmitter
|
||||
MIB data alarm."
|
||||
::= { aprisaXELinkAlarmsEventsV2 26 }
|
||||
|
||||
aprisaXEAlarmTxNeg5VStatusEvent NOTIFICATION-TYPE
|
||||
OBJECTS { aprisaXEEventAlarmStatus }
|
||||
STATUS current
|
||||
DESCRIPTION "Event indicating a change in state of the transmitter
|
||||
Negative 5V digital supply status alarm."
|
||||
::= { aprisaXELinkAlarmsEventsV2 27 }
|
||||
|
||||
|
||||
-- ***************************************************************************
|
||||
-- Modem Traps
|
||||
-- ***************************************************************************
|
||||
|
||||
aprisaXEModemSyncEvent NOTIFICATION-TYPE
|
||||
OBJECTS { aprisaXEEventAlarmStatus }
|
||||
STATUS current
|
||||
DESCRIPTION "Event indicating a change in state of the modem lock."
|
||||
::= { aprisaXELinkAlarmsEventsV2 30 }
|
||||
|
||||
aprisaXEModemTDMAlignmentEvent NOTIFICATION-TYPE
|
||||
OBJECTS { aprisaXEEventAlarmStatus }
|
||||
STATUS current
|
||||
DESCRIPTION "Event indicating a change in state of the modem TDM alignment."
|
||||
::= { aprisaXELinkAlarmsEventsV2 31 }
|
||||
|
||||
aprisaXEModemDemodAlignmentEvent NOTIFICATION-TYPE
|
||||
OBJECTS { aprisaXEEventAlarmStatus }
|
||||
STATUS current
|
||||
DESCRIPTION "Event indicating a change in state of the modem demodulator alignment."
|
||||
::= { aprisaXELinkAlarmsEventsV2 32 }
|
||||
|
||||
aprisaXEModemRefAStatusEvent NOTIFICATION-TYPE
|
||||
OBJECTS { aprisaXEEventAlarmStatus }
|
||||
STATUS current
|
||||
DESCRIPTION "Event indicating a change in state of the Ref A clock."
|
||||
::= { aprisaXELinkAlarmsEventsV2 33 }
|
||||
|
||||
aprisaXEModemRefBStatusEvent NOTIFICATION-TYPE
|
||||
OBJECTS { aprisaXEEventAlarmStatus }
|
||||
STATUS current
|
||||
DESCRIPTION "Event indicating a change in state of the Ref B clock."
|
||||
::= { aprisaXELinkAlarmsEventsV2 34 }
|
||||
|
||||
aprisaXEModemUCEPresentEvent NOTIFICATION-TYPE
|
||||
OBJECTS { aprisaXEEventAlarmStatus }
|
||||
STATUS current
|
||||
DESCRIPTION "Event indicating the presence of uncorrectable errors."
|
||||
::= { aprisaXELinkAlarmsEventsV2 35 }
|
||||
|
||||
|
||||
-- ***************************************************************************
|
||||
-- QuadE1 Traps
|
||||
-- ***************************************************************************
|
||||
|
||||
aprisaXEQuadE1LOSEvent NOTIFICATION-TYPE
|
||||
OBJECTS { aprisaXEEventCardSlot,
|
||||
aprisaXEEventCardPort,
|
||||
aprisaXEEventAlarmStatus
|
||||
}
|
||||
STATUS current
|
||||
DESCRIPTION "Event indicating a change in LOS state for a port."
|
||||
::= { aprisaXELinkAlarmsEventsV2 40 }
|
||||
|
||||
aprisaXEQuadE1AISEvent NOTIFICATION-TYPE
|
||||
OBJECTS { aprisaXEEventCardSlot,
|
||||
aprisaXEEventCardPort,
|
||||
aprisaXEEventAlarmStatus
|
||||
}
|
||||
STATUS current
|
||||
DESCRIPTION "Event indicating a change in AIS state for a port."
|
||||
::= { aprisaXELinkAlarmsEventsV2 41 }
|
||||
|
||||
aprisaXEQuadE1RAIEvent NOTIFICATION-TYPE
|
||||
OBJECTS { aprisaXEEventCardSlot,
|
||||
aprisaXEEventCardPort,
|
||||
aprisaXEEventAlarmStatus
|
||||
}
|
||||
STATUS current
|
||||
DESCRIPTION "Event indicating a change in RAI state for a port."
|
||||
::= { aprisaXELinkAlarmsEventsV2 42 }
|
||||
|
||||
aprisaXEQuadE1RMAIEvent NOTIFICATION-TYPE
|
||||
OBJECTS { aprisaXEEventCardSlot,
|
||||
aprisaXEEventCardPort,
|
||||
aprisaXEEventAlarmStatus
|
||||
}
|
||||
STATUS current
|
||||
DESCRIPTION "Event indicating a change in RMAI state for a port."
|
||||
::= { aprisaXELinkAlarmsEventsV2 43 }
|
||||
|
||||
aprisaXEQuadE1TS16AISEvent NOTIFICATION-TYPE
|
||||
OBJECTS { aprisaXEEventCardSlot,
|
||||
aprisaXEEventCardPort,
|
||||
aprisaXEEventAlarmStatus
|
||||
}
|
||||
STATUS current
|
||||
DESCRIPTION "Event indicating a change in TS16AIS state for a port."
|
||||
::= { aprisaXELinkAlarmsEventsV2 44 }
|
||||
|
||||
aprisaXEQuadE1TS16LOSEvent NOTIFICATION-TYPE
|
||||
OBJECTS { aprisaXEEventCardSlot,
|
||||
aprisaXEEventCardPort,
|
||||
aprisaXEEventAlarmStatus
|
||||
}
|
||||
STATUS current
|
||||
DESCRIPTION "Event indicating a change in TS16LOS state for a port."
|
||||
::= { aprisaXELinkAlarmsEventsV2 45 }
|
||||
|
||||
aprisaXEQuadE1LOFEvent NOTIFICATION-TYPE
|
||||
OBJECTS { aprisaXEEventCardSlot,
|
||||
aprisaXEEventCardPort,
|
||||
aprisaXEEventAlarmStatus
|
||||
}
|
||||
STATUS current
|
||||
DESCRIPTION "Event indicating a change in loss of frame state for a port."
|
||||
::= { aprisaXELinkAlarmsEventsV2 46 }
|
||||
|
||||
|
||||
-- ***************************************************************************
|
||||
-- FXO Traps
|
||||
-- ***************************************************************************
|
||||
|
||||
aprisaXEFXOCodecOvldEvent NOTIFICATION-TYPE
|
||||
OBJECTS { aprisaXEEventCardSlot,
|
||||
aprisaXEEventCardPort,
|
||||
aprisaXEEventAlarmStatus
|
||||
}
|
||||
STATUS current
|
||||
DESCRIPTION "Event indicating a change in Codec Ovld state for a port."
|
||||
::= { aprisaXELinkAlarmsEventsV2 50 }
|
||||
|
||||
aprisaXEFXOBillToneOvldEvent NOTIFICATION-TYPE
|
||||
OBJECTS { aprisaXEEventCardSlot,
|
||||
aprisaXEEventCardPort,
|
||||
aprisaXEEventAlarmStatus
|
||||
}
|
||||
STATUS current
|
||||
DESCRIPTION "Event indicating a change in Billing Tone Ovld state for a port."
|
||||
::= { aprisaXELinkAlarmsEventsV2 51 }
|
||||
|
||||
aprisaXEFXOCurrentOvldEvent NOTIFICATION-TYPE
|
||||
OBJECTS { aprisaXEEventCardSlot,
|
||||
aprisaXEEventCardPort,
|
||||
aprisaXEEventAlarmStatus
|
||||
}
|
||||
STATUS current
|
||||
DESCRIPTION "Event indicating a change in Current Ovld state for a port."
|
||||
::= { aprisaXELinkAlarmsEventsV2 52 }
|
||||
|
||||
aprisaXEFXOUnplugEvent NOTIFICATION-TYPE
|
||||
OBJECTS { aprisaXEEventCardSlot,
|
||||
aprisaXEEventCardPort,
|
||||
aprisaXEEventAlarmStatus
|
||||
}
|
||||
STATUS current
|
||||
DESCRIPTION "Event indicating a change in Unplug state for a port."
|
||||
::= { aprisaXELinkAlarmsEventsV2 53 }
|
||||
|
||||
|
||||
-- ***************************************************************************
|
||||
-- FXS Traps
|
||||
-- ***************************************************************************
|
||||
|
||||
aprisaXEFXSCalibrateErrorEvent NOTIFICATION-TYPE
|
||||
OBJECTS { aprisaXEEventCardSlot,
|
||||
aprisaXEEventCardPort,
|
||||
aprisaXEEventAlarmStatus
|
||||
}
|
||||
STATUS current
|
||||
DESCRIPTION "Event indicating a common mode error during Pro-SLIC initialisation."
|
||||
::= { aprisaXELinkAlarmsEventsV2 60 }
|
||||
|
||||
aprisaXEFXSDCDCErrorEvent NOTIFICATION-TYPE
|
||||
OBJECTS { aprisaXEEventCardSlot,
|
||||
aprisaXEEventCardPort,
|
||||
aprisaXEEventAlarmStatus
|
||||
}
|
||||
STATUS obsolete
|
||||
DESCRIPTION "Event indicating a DC-DC converter error during Pro-SLIC initialisation "
|
||||
::= { aprisaXELinkAlarmsEventsV2 61 }
|
||||
|
||||
aprisaXEFXSCASLockEvent NOTIFICATION-TYPE
|
||||
OBJECTS { aprisaXEEventCardSlot,
|
||||
aprisaXEEventCardPort,
|
||||
aprisaXEEventAlarmStatus
|
||||
}
|
||||
STATUS current
|
||||
DESCRIPTION "Event indicating the FPGA has not locked onto a CAS frame. "
|
||||
::= { aprisaXELinkAlarmsEventsV2 62 }
|
||||
|
||||
|
||||
-- ***************************************************************************
|
||||
-- HSS Traps
|
||||
-- ***************************************************************************
|
||||
|
||||
aprisaXEHSSTDMLockEvent NOTIFICATION-TYPE
|
||||
OBJECTS { aprisaXEEventCardSlot,
|
||||
aprisaXEEventAlarmStatus
|
||||
}
|
||||
STATUS current
|
||||
DESCRIPTION "Event indicating an HSS TDM Lock error."
|
||||
::= { aprisaXELinkAlarmsEventsV2 70 }
|
||||
|
||||
aprisaXEHSS32MHzResetEvent NOTIFICATION-TYPE
|
||||
OBJECTS { aprisaXEEventCardSlot,
|
||||
aprisaXEEventAlarmStatus
|
||||
}
|
||||
STATUS current
|
||||
DESCRIPTION "Event indicating a 32MHz clock reset error."
|
||||
::= { aprisaXELinkAlarmsEventsV2 71 }
|
||||
|
||||
aprisaXEHSSTDMResetEvent NOTIFICATION-TYPE
|
||||
OBJECTS { aprisaXEEventCardSlot,
|
||||
aprisaXEEventAlarmStatus
|
||||
}
|
||||
STATUS current
|
||||
DESCRIPTION "Event indicating a TDM reset error."
|
||||
::= { aprisaXELinkAlarmsEventsV2 72 }
|
||||
|
||||
aprisaXEHSSPatternLossEvent NOTIFICATION-TYPE
|
||||
OBJECTS { aprisaXEEventCardSlot,
|
||||
aprisaXEEventAlarmStatus
|
||||
}
|
||||
STATUS current
|
||||
DESCRIPTION "Event indicating a Pattern Loss error."
|
||||
::= { aprisaXELinkAlarmsEventsV2 73 }
|
||||
|
||||
aprisaXEHSSRxFifoFullEvent NOTIFICATION-TYPE
|
||||
OBJECTS { aprisaXEEventCardSlot,
|
||||
aprisaXEEventAlarmStatus
|
||||
}
|
||||
STATUS current
|
||||
DESCRIPTION "Event indicating an Rx FIFO Full error."
|
||||
::= { aprisaXELinkAlarmsEventsV2 74 }
|
||||
|
||||
aprisaXEHSSRxFifoEmptyEvent NOTIFICATION-TYPE
|
||||
OBJECTS { aprisaXEEventCardSlot,
|
||||
aprisaXEEventAlarmStatus
|
||||
}
|
||||
STATUS current
|
||||
DESCRIPTION "Event indicating an Rx FIFO Empty error."
|
||||
::= { aprisaXELinkAlarmsEventsV2 75 }
|
||||
|
||||
aprisaXEHSSTxFifoFullEvent NOTIFICATION-TYPE
|
||||
OBJECTS { aprisaXEEventCardSlot,
|
||||
aprisaXEEventAlarmStatus
|
||||
}
|
||||
STATUS current
|
||||
DESCRIPTION "Event indicating a Tx FIFO Full error."
|
||||
::= { aprisaXELinkAlarmsEventsV2 76 }
|
||||
|
||||
aprisaXEHSSTxFifoEmptyEvent NOTIFICATION-TYPE
|
||||
OBJECTS { aprisaXEEventCardSlot,
|
||||
aprisaXEEventAlarmStatus
|
||||
}
|
||||
STATUS current
|
||||
DESCRIPTION "Event indicating a Tx FIFO Empty error."
|
||||
::= { aprisaXELinkAlarmsEventsV2 77 }
|
||||
|
||||
aprisaXEHSSRxClockValidEvent NOTIFICATION-TYPE
|
||||
OBJECTS { aprisaXEEventCardSlot,
|
||||
aprisaXEEventAlarmStatus
|
||||
}
|
||||
STATUS current
|
||||
DESCRIPTION "Event indicating an Rx Clock Valid error."
|
||||
::= { aprisaXELinkAlarmsEventsV2 78 }
|
||||
|
||||
aprisaXEHSSTxClockValidEvent NOTIFICATION-TYPE
|
||||
OBJECTS { aprisaXEEventCardSlot,
|
||||
aprisaXEEventAlarmStatus
|
||||
}
|
||||
STATUS current
|
||||
DESCRIPTION "Event indicating a Tx Clock Valid error."
|
||||
::= { aprisaXELinkAlarmsEventsV2 79 }
|
||||
|
||||
|
||||
-- ***************************************************************************
|
||||
-- V24 Traps
|
||||
-- ***************************************************************************
|
||||
|
||||
aprisaXEV24ControlLineLossEvent NOTIFICATION-TYPE
|
||||
OBJECTS { aprisaXEEventCardSlot,
|
||||
aprisaXEEventCardPort,
|
||||
aprisaXEEventAlarmStatus
|
||||
}
|
||||
STATUS current
|
||||
DESCRIPTION "Event indicating V24 control line aren't in sync."
|
||||
::= { aprisaXELinkAlarmsEventsV2 80 }
|
||||
|
||||
|
||||
-- ***************************************************************************
|
||||
-- Other Traps
|
||||
-- ***************************************************************************
|
||||
|
||||
aprisaXEUnexpectedCardEvent NOTIFICATION-TYPE
|
||||
OBJECTS { aprisaXEEventCardSlot,
|
||||
aprisaXEEventCardExpected,
|
||||
aprisaXEEventCardInstalled,
|
||||
aprisaXEEventCardStatus
|
||||
}
|
||||
STATUS current
|
||||
DESCRIPTION "Event indicating an mismatch between the MIB and the installed
|
||||
MUX cards. The radio will not operate correctly if the MIB and
|
||||
MUX cards do not match."
|
||||
::= { aprisaXELinkAlarmsEventsV2 100 }
|
||||
|
||||
aprisaXECLKSyncEvent NOTIFICATION-TYPE
|
||||
OBJECTS { aprisaXEEventAlarmStatus }
|
||||
STATUS current
|
||||
DESCRIPTION "Event indicating a change in state of the clock sync state."
|
||||
::= { aprisaXELinkAlarmsEventsV2 110 }
|
||||
|
||||
aprisaXENetClkConfigEvent NOTIFICATION-TYPE
|
||||
OBJECTS { aprisaXEEventAlarmStatus }
|
||||
STATUS current
|
||||
DESCRIPTION "Event indicating a change in state of the network clock config."
|
||||
::= { aprisaXELinkAlarmsEventsV2 111 }
|
||||
|
||||
aprisaXECharacterisationEEFailEvent NOTIFICATION-TYPE
|
||||
OBJECTS { aprisaXEEventCardSlot,
|
||||
aprisaXEEventCardInstalled,
|
||||
aprisaXEEventCharacterisationStatus
|
||||
}
|
||||
STATUS current
|
||||
DESCRIPTION "Event indicating a failed read of characterisation data from
|
||||
EEPROM."
|
||||
::= { aprisaXELinkAlarmsEventsV2 120 }
|
||||
|
||||
aprisaXEMibEEFailEvent NOTIFICATION-TYPE
|
||||
OBJECTS { aprisaXEEventCardSlot,
|
||||
aprisaXEEventCardInstalled,
|
||||
aprisaXEEventMibStatus
|
||||
}
|
||||
STATUS current
|
||||
DESCRIPTION "Event indicating a failed read of mib data from EEPROM."
|
||||
::= { aprisaXELinkAlarmsEventsV2 121 }
|
||||
|
||||
aprisaXEMhsbSwitchToStandbyEvent NOTIFICATION-TYPE
|
||||
OBJECTS { aprisaXEEventAlarmStatus }
|
||||
STATUS current
|
||||
DESCRIPTION "Event indicating a Monitored Hot Standby switch to Standby Event."
|
||||
::= { aprisaXELinkAlarmsEventsV2 130 }
|
||||
|
||||
aprisaXEAlternateImageTableEvent NOTIFICATION-TYPE
|
||||
OBJECTS { aprisaXEEventAlarmStatus }
|
||||
STATUS current
|
||||
DESCRIPTION "Event indicating an Alternate Image Table Event."
|
||||
::= { aprisaXELinkAlarmsEventsV2 131 }
|
||||
|
||||
aprisaXEDefaultImageTableEvent NOTIFICATION-TYPE
|
||||
OBJECTS { aprisaXEEventAlarmStatus }
|
||||
STATUS current
|
||||
DESCRIPTION "Event indicating a Default Image Table Event."
|
||||
::= { aprisaXELinkAlarmsEventsV2 132 }
|
||||
|
||||
aprisaXEUploadFailEvent NOTIFICATION-TYPE
|
||||
OBJECTS { aprisaXEEventAlarmStatus }
|
||||
STATUS current
|
||||
DESCRIPTION "Event indicating the failure of the previous upload."
|
||||
::= { aprisaXELinkAlarmsEventsV2 133 }
|
||||
|
||||
|
||||
-- ***************************************************************************
|
||||
-- Psc Traps
|
||||
-- ***************************************************************************
|
||||
|
||||
aprisaXEPscDemuxAlignmentEvent NOTIFICATION-TYPE
|
||||
OBJECTS { aprisaXEEventAlarmStatus }
|
||||
STATUS current
|
||||
DESCRIPTION "Event indicating a change in state of the PSC Demux alignment ."
|
||||
::= { aprisaXELinkAlarmsEventsV2 140 }
|
||||
|
||||
|
||||
aprisaXEPscTDMAlignmentEvent NOTIFICATION-TYPE
|
||||
OBJECTS { aprisaXEEventAlarmStatus }
|
||||
STATUS current
|
||||
DESCRIPTION "Event indicating a change in state of the PSC TDM alignment."
|
||||
::= { aprisaXELinkAlarmsEventsV2 141 }
|
||||
|
||||
aprisaXEPscMuxAlignmentErrorEvent NOTIFICATION-TYPE
|
||||
OBJECTS { aprisaXEEventAlarmStatus }
|
||||
STATUS current
|
||||
DESCRIPTION "Event indicating if the TDM mux loses alignment to the TDM bus."
|
||||
::= { aprisaXELinkAlarmsEventsV2 142 }
|
||||
|
||||
aprisaXEPscCompanionTxFailEvent NOTIFICATION-TYPE
|
||||
OBJECTS { aprisaXEEventAlarmStatus }
|
||||
STATUS current
|
||||
DESCRIPTION "Event indicating that the HRSD Companion transmitter has failed."
|
||||
::= { aprisaXELinkAlarmsEventsV2 143 }
|
||||
|
||||
aprisaXEPscSoftwareOverrideEvent NOTIFICATION-TYPE
|
||||
OBJECTS { aprisaXEEventAlarmStatus }
|
||||
STATUS current
|
||||
DESCRIPTION "Event indicating a software override of the PSC Mode Switch."
|
||||
::= { aprisaXELinkAlarmsEventsV2 144 }
|
||||
|
||||
aprisaXEPscInvalidSwitchValueEvent NOTIFICATION-TYPE
|
||||
OBJECTS { aprisaXEEventAlarmStatus }
|
||||
STATUS current
|
||||
DESCRIPTION "Event indicating that the PSC Mode Switch value is invalid."
|
||||
::= { aprisaXELinkAlarmsEventsV2 145 }
|
||||
|
||||
|
||||
-- ***************************************************************************
|
||||
-- DualE1 Traps
|
||||
-- ***************************************************************************
|
||||
|
||||
aprisaXEDualE1LOSEvent NOTIFICATION-TYPE
|
||||
OBJECTS { aprisaXEEventCardSlot,
|
||||
aprisaXEEventCardPort,
|
||||
aprisaXEEventAlarmStatus
|
||||
}
|
||||
STATUS current
|
||||
DESCRIPTION "Event indicating a change in LOS state for a port."
|
||||
::= { aprisaXELinkAlarmsEventsV2 150 }
|
||||
|
||||
aprisaXEDualE1AISEvent NOTIFICATION-TYPE
|
||||
OBJECTS { aprisaXEEventCardSlot,
|
||||
aprisaXEEventCardPort,
|
||||
aprisaXEEventAlarmStatus
|
||||
}
|
||||
STATUS current
|
||||
DESCRIPTION "Event indicating a change in AIS state for a port."
|
||||
::= { aprisaXELinkAlarmsEventsV2 151 }
|
||||
|
||||
|
||||
-- ***************************************************************************
|
||||
-- SingleE1 Traps
|
||||
-- ***************************************************************************
|
||||
|
||||
aprisaXESingleE1LOSEvent NOTIFICATION-TYPE
|
||||
OBJECTS { aprisaXEEventCardSlot,
|
||||
aprisaXEEventCardPort,
|
||||
aprisaXEEventAlarmStatus
|
||||
}
|
||||
STATUS current
|
||||
DESCRIPTION "Event indicating a change in LOS state for a port."
|
||||
::= { aprisaXELinkAlarmsEventsV2 160 }
|
||||
|
||||
aprisaXESingleE1AISEvent NOTIFICATION-TYPE
|
||||
OBJECTS { aprisaXEEventCardSlot,
|
||||
aprisaXEEventCardPort,
|
||||
aprisaXEEventAlarmStatus
|
||||
}
|
||||
STATUS current
|
||||
DESCRIPTION "Event indicating a change in AIS state for a port."
|
||||
::= { aprisaXELinkAlarmsEventsV2 161 }
|
||||
|
||||
|
||||
-- ***************************************************************************
|
||||
-- HRSD Traps
|
||||
-- ***************************************************************************
|
||||
|
||||
aprisaXEHrsdCompareOidEvent NOTIFICATION-TYPE
|
||||
OBJECTS { aprisaXEEventAlarmStatus }
|
||||
STATUS current
|
||||
DESCRIPTION "Event indicating that an OID failed its comparison check."
|
||||
::= { aprisaXELinkAlarmsEventsV2 170 }
|
||||
|
||||
aprisaXEHrsdCompanionLostEvent NOTIFICATION-TYPE
|
||||
OBJECTS { aprisaXEEventAlarmStatus }
|
||||
STATUS current
|
||||
DESCRIPTION "Event indicating that the HRSD Companion Heartbeat is lost."
|
||||
::= { aprisaXELinkAlarmsEventsV2 171 }
|
||||
|
||||
-- ***************************************************************************
|
||||
-- End Traps
|
||||
-- ***************************************************************************
|
||||
|
||||
END
|
||||
10023
MIBS/4rf/4RF-APRISAXE-MIB
Normal file
10023
MIBS/4rf/4RF-APRISAXE-MIB
Normal file
File diff suppressed because it is too large
Load Diff
1116
MIBS/4rf/4RF-APRISAXE-TC
Normal file
1116
MIBS/4rf/4RF-APRISAXE-TC
Normal file
File diff suppressed because it is too large
Load Diff
708
MIBS/4rf/4RF-COMMON-MIB
Normal file
708
MIBS/4rf/4RF-COMMON-MIB
Normal file
@@ -0,0 +1,708 @@
|
||||
COMMON-4RF DEFINITIONS ::= BEGIN
|
||||
|
||||
--
|
||||
-- File: $Id: 4RF-COMMON-MIB.txt,v 1.23 2007/07/11 22:04:16 di Exp $
|
||||
--
|
||||
-- Copyright: 2004 4RF COMMUNICATIONS LTD
|
||||
--
|
||||
-- Description:
|
||||
-- Common MIB sub-tree for 4RF Communications Ltd., used by all products.
|
||||
-- It defines some useful TEXT-CONVENTIONS and basic MIB objects relating
|
||||
-- to 4RF products.
|
||||
--
|
||||
-- Versions:
|
||||
--
|
||||
-- Notes:
|
||||
-- None
|
||||
--
|
||||
|
||||
IMPORTS
|
||||
|
||||
-- Standard imports
|
||||
MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY, NOTIFICATION-TYPE,
|
||||
Integer32, Unsigned32, Counter32, IpAddress
|
||||
FROM SNMPv2-SMI
|
||||
TEXTUAL-CONVENTION, DisplayString, DateAndTime
|
||||
FROM SNMPv2-TC
|
||||
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
|
||||
FROM SNMPv2-CONF
|
||||
|
||||
-- 4RF Specific imports
|
||||
fourRFCommon
|
||||
FROM PRODUCTS-MIB-4RF
|
||||
FourRFImageVersion, FourRFSerialNumber, FourRFResetType,
|
||||
FourRFProcessResultType, FourRFTftpFileName, FourRFFileSize,
|
||||
FourRFImageStatus, FourRFImageType, FourRFWebUserEnabled,
|
||||
FourRFWebUserGroup, FourRFTimeZone
|
||||
FROM COMMON-TC-4RF
|
||||
fourRFGeneric, fourRFModules
|
||||
FROM MIB-4RF;
|
||||
|
||||
|
||||
-- Module Identification
|
||||
fourRFCommonModule MODULE-IDENTITY
|
||||
LAST-UPDATED "200704300000Z"
|
||||
ORGANIZATION "www.4rf.com"
|
||||
CONTACT-INFO
|
||||
"postal: 4RF Communications Ltd
|
||||
26 Glover Street
|
||||
Ngauranga
|
||||
PO Box 13-506
|
||||
Wellington 6032
|
||||
New Zealand
|
||||
|
||||
phone: +64 4 499 6000
|
||||
email: support@4rf.com"
|
||||
DESCRIPTION "Common 4RF MIB Objects."
|
||||
|
||||
-- Revision history
|
||||
-- (in reverse chronological order)
|
||||
|
||||
REVISION "200704300000Z"
|
||||
DESCRIPTION "Second draft"
|
||||
|
||||
REVISION "200502110000Z"
|
||||
DESCRIPTION "First draft"
|
||||
::= { fourRFModules 3 }
|
||||
|
||||
|
||||
--
|
||||
-- Currently the MIB is still being defined, all objects are placed
|
||||
-- under fourRFExperimental, when the MIB has been completed these
|
||||
-- objects will be moved to fourRFGeneric.
|
||||
--
|
||||
|
||||
|
||||
fourRFGroups OBJECT-IDENTITY
|
||||
STATUS current
|
||||
DESCRIPTION "The root of the OID sub-tree for the 4RF common object groups."
|
||||
::= { fourRFCommon 1 }
|
||||
|
||||
fourRFObjects OBJECT-IDENTITY
|
||||
STATUS current
|
||||
DESCRIPTION "The root of the OID sub-tree for the 4RF common objects."
|
||||
::= { fourRFCommon 2 }
|
||||
|
||||
fourRFEvents OBJECT-IDENTITY
|
||||
STATUS current
|
||||
DESCRIPTION "The root of the OID sub-tree for the 4RF common events."
|
||||
::= { fourRFCommon 3 }
|
||||
|
||||
fourRFEventsV2 OBJECT-IDENTITY
|
||||
STATUS current
|
||||
DESCRIPTION "The root of the OID sub-tree for the 4RF common events."
|
||||
::= { fourRFEvents 0 }
|
||||
|
||||
|
||||
-- ***************************************************************************
|
||||
-- Basic terminal details
|
||||
--
|
||||
-- The name, location and contact details are stored in the MIB-II System
|
||||
-- entries sysName, sysLocation and sysContact respectively.
|
||||
--
|
||||
-- ***************************************************************************
|
||||
|
||||
fourRFSystem OBJECT IDENTIFIER ::= { fourRFObjects 1 }
|
||||
|
||||
fourRFSystemID OBJECT-TYPE
|
||||
SYNTAX DisplayString ( SIZE (0..255) )
|
||||
MAX-ACCESS read-write
|
||||
STATUS current
|
||||
DESCRIPTION "The terminal identifier, user defined."
|
||||
::= { fourRFSystem 1 }
|
||||
|
||||
fourRFSystemSoftwareVersion OBJECT-TYPE
|
||||
SYNTAX FourRFImageVersion
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION "The terminal software version details."
|
||||
::= { fourRFSystem 2 }
|
||||
|
||||
fourRFSystemIpAddress OBJECT-TYPE
|
||||
SYNTAX IpAddress
|
||||
MAX-ACCESS read-write
|
||||
STATUS current
|
||||
DESCRIPTION "IP address of terminal, care should be taken when changing
|
||||
this value."
|
||||
::= { fourRFSystem 3 }
|
||||
|
||||
fourRFSystemRemoteIpAddress OBJECT-TYPE
|
||||
SYNTAX IpAddress
|
||||
MAX-ACCESS read-write
|
||||
STATUS current
|
||||
DESCRIPTION "IP address of remote terminal, this is the other end of the
|
||||
radio link. This must be configured at commissioning."
|
||||
::= { fourRFSystem 4 }
|
||||
|
||||
fourRFSystemSubnetMask OBJECT-TYPE
|
||||
SYNTAX IpAddress
|
||||
MAX-ACCESS read-write
|
||||
STATUS current
|
||||
DESCRIPTION "The subnet mask for the terminal. This must be configured at
|
||||
commissioning."
|
||||
::= { fourRFSystem 5 }
|
||||
|
||||
fourRFSystemDefaultGateway OBJECT-TYPE
|
||||
SYNTAX IpAddress
|
||||
MAX-ACCESS read-write
|
||||
STATUS current
|
||||
DESCRIPTION "The default gateway for the terminal. This must be configured
|
||||
at commissioning."
|
||||
::= { fourRFSystem 6 }
|
||||
|
||||
fourRFSystemIpAssignment OBJECT-TYPE
|
||||
SYNTAX INTEGER { useDHCP (0),
|
||||
userAssigned (1)
|
||||
}
|
||||
MAX-ACCESS read-write
|
||||
STATUS current
|
||||
DESCRIPTION "This indicates how the terminal IP address is configured.
|
||||
This must be configured at commissioning. The IP address can
|
||||
be assigned manually or by a DHCP server."
|
||||
::= { fourRFSystem 7 }
|
||||
|
||||
fourRFSystemDateAndTime OBJECT-TYPE
|
||||
SYNTAX Unsigned32
|
||||
MAX-ACCESS read-write
|
||||
STATUS current
|
||||
DESCRIPTION "This indicates the current time from the terminal's real-time clock,
|
||||
the time is measured in seconds since Midnight GMT on January 1 1970."
|
||||
::= { fourRFSystem 8 }
|
||||
|
||||
fourRFSystemTftpServerAddress OBJECT-TYPE
|
||||
SYNTAX IpAddress
|
||||
MAX-ACCESS read-write
|
||||
STATUS current
|
||||
DESCRIPTION "IP address of TFTP server used for uploading and downloading files."
|
||||
::= { fourRFSystem 9 }
|
||||
|
||||
fourRFSystemSerialNumber OBJECT-TYPE
|
||||
SYNTAX FourRFSerialNumber
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION "The unique serial number for the terminal."
|
||||
::= { fourRFSystem 10 }
|
||||
|
||||
fourRFSystemLastReset OBJECT-TYPE
|
||||
SYNTAX FourRFResetType
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION "The type of the last system reset."
|
||||
::= { fourRFSystem 11 }
|
||||
|
||||
fourRFSystemTimeZone OBJECT-TYPE
|
||||
SYNTAX Integer32
|
||||
MAX-ACCESS read-write
|
||||
STATUS current
|
||||
DESCRIPTION "This indicates the offset from UTC time in minutes."
|
||||
::= { fourRFSystem 12 }
|
||||
|
||||
fourRFSystemSyslogAddress OBJECT-TYPE
|
||||
SYNTAX IpAddress
|
||||
MAX-ACCESS read-write
|
||||
STATUS current
|
||||
DESCRIPTION "The IP address of a remote syslogd server used to log system events."
|
||||
::= { fourRFSystem 13 }
|
||||
|
||||
fourRFSystemSyslogPort OBJECT-TYPE
|
||||
SYNTAX Unsigned32
|
||||
MAX-ACCESS read-write
|
||||
STATUS current
|
||||
DESCRIPTION "The port to use when logging to a remote syslogd, the default is port 514."
|
||||
::= { fourRFSystem 14 }
|
||||
|
||||
fourRFSystemTimeDaylightSavings OBJECT-TYPE
|
||||
SYNTAX INTEGER { daylightSavingsDisabled (0),
|
||||
daylightSavingsEnabled (1)
|
||||
}
|
||||
MAX-ACCESS read-write
|
||||
STATUS current
|
||||
DESCRIPTION "Indicates whether daylight savings is in use."
|
||||
::= { fourRFSystem 15 }
|
||||
|
||||
fourRFSystemTimeZoneGMTOffset OBJECT-TYPE
|
||||
SYNTAX FourRFTimeZone
|
||||
MAX-ACCESS read-write
|
||||
STATUS current
|
||||
DESCRIPTION "This indicates the timezone offset from GMT."
|
||||
::= { fourRFSystem 16 }
|
||||
|
||||
fourRFSystemMACAddress OBJECT-TYPE
|
||||
SYNTAX DisplayString ( SIZE (0..32) )
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION "The MAC Address for the terminal."
|
||||
::= { fourRFSystem 17 }
|
||||
|
||||
fourRFSystemLocalRadioBIpAddress OBJECT-TYPE
|
||||
SYNTAX IpAddress
|
||||
MAX-ACCESS read-write
|
||||
STATUS current
|
||||
DESCRIPTION "IP address of local Radio B terminal, this is the partner
|
||||
radio of a SD link. This must be configured at commissioning."
|
||||
::= { fourRFSystem 18 }
|
||||
|
||||
fourRFSystemRemoteRadioBIpAddress OBJECT-TYPE
|
||||
SYNTAX IpAddress
|
||||
MAX-ACCESS read-write
|
||||
STATUS current
|
||||
DESCRIPTION "IP address of remote Radio B terminal, this is the partner
|
||||
radio of a SD link. This must be configured at commissioning."
|
||||
::= { fourRFSystem 19 }
|
||||
|
||||
fourRFSystemLocalRadioAIpAddress OBJECT-TYPE
|
||||
SYNTAX IpAddress
|
||||
MAX-ACCESS read-write
|
||||
STATUS current
|
||||
DESCRIPTION "IP address of local Radio A terminal, this is the partner
|
||||
radio of a SD link. This must be configured at commissioning."
|
||||
::= { fourRFSystem 20 }
|
||||
|
||||
fourRFSystemGroup OBJECT-GROUP
|
||||
OBJECTS { fourRFSystemID,
|
||||
fourRFSystemSoftwareVersion,
|
||||
fourRFSystemIpAddress,
|
||||
fourRFSystemRemoteIpAddress,
|
||||
fourRFSystemSubnetMask,
|
||||
fourRFSystemDefaultGateway,
|
||||
fourRFSystemIpAssignment,
|
||||
fourRFSystemDateAndTime,
|
||||
fourRFSystemTftpServerAddress,
|
||||
fourRFSystemSerialNumber,
|
||||
fourRFSystemLastReset,
|
||||
fourRFSystemTimeZone,
|
||||
fourRFSystemSyslogAddress,
|
||||
fourRFSystemSyslogPort,
|
||||
fourRFSystemTimeDaylightSavings,
|
||||
fourRFSystemTimeZoneGMTOffset,
|
||||
fourRFSystemMACAddress,
|
||||
fourRFSystemLocalRadioBIpAddress,
|
||||
fourRFSystemRemoteRadioBIpAddress,
|
||||
fourRFSystemLocalRadioAIpAddress
|
||||
}
|
||||
STATUS current
|
||||
DESCRIPTION "The 4RF common system settings group."
|
||||
::= { fourRFGroups 1 }
|
||||
|
||||
|
||||
-- ***************************************************************************
|
||||
-- System reset handling
|
||||
--
|
||||
-- These MIB entries allow the system to be reset, currently two types
|
||||
-- of reset are possible, shutdown and a restart. It may be that other
|
||||
-- options should be supported to reset just the Linux software or to
|
||||
-- perform a complete hardware reset. A reset can be instigated immediately
|
||||
-- or at a specified time. In the case of a timed reset the reset may be
|
||||
-- cancelled if required.
|
||||
--
|
||||
-- An SNMP trap reset4RFEvent will be generated just before the reset is
|
||||
-- performed.
|
||||
--
|
||||
-- ***************************************************************************
|
||||
|
||||
fourRFReset OBJECT IDENTIFIER ::= { fourRFObjects 2 }
|
||||
|
||||
fourRFResetType OBJECT-TYPE
|
||||
SYNTAX INTEGER { none (0),
|
||||
softReset (1),
|
||||
hardReset (2)
|
||||
}
|
||||
MAX-ACCESS read-write
|
||||
STATUS current
|
||||
DESCRIPTION "Identifies the type of reset operation:
|
||||
none - do nothing!
|
||||
hardReset - complete reset of all components
|
||||
softReset - reset of the CPU only, traffic is unaffected.
|
||||
|
||||
The values mirror the ResetType textual convention but the
|
||||
user cannot instigate a watchdog reset. This value is not
|
||||
therefore not allowed."
|
||||
::= { fourRFReset 1 }
|
||||
|
||||
fourRFResetTime OBJECT-TYPE
|
||||
SYNTAX Unsigned32
|
||||
MAX-ACCESS read-write
|
||||
STATUS current
|
||||
DESCRIPTION "Identifies the time of a delayed reset operation. This allows an
|
||||
absolute time to be specified based on the system real-time clock.
|
||||
The time is measured in seconds since Midnight GMT on January 1 1970."
|
||||
::= { fourRFReset 2 }
|
||||
|
||||
fourRFResetCommand OBJECT-TYPE
|
||||
SYNTAX INTEGER { none (0),
|
||||
resetNow (1),
|
||||
timedReset (2),
|
||||
cancelReset (3)
|
||||
}
|
||||
MAX-ACCESS read-write
|
||||
STATUS current
|
||||
DESCRIPTION "Command to instigate or cancel a system reset, the reset may
|
||||
happen immediately or at a specified time. Only a timed reset
|
||||
can be cancelled."
|
||||
::= { fourRFReset 3 }
|
||||
|
||||
fourRFResetGroup OBJECT-GROUP
|
||||
OBJECTS { fourRFResetType,
|
||||
fourRFResetTime,
|
||||
fourRFResetCommand
|
||||
}
|
||||
STATUS current
|
||||
DESCRIPTION "The 4RF common reset group."
|
||||
::= { fourRFGroups 2 }
|
||||
|
||||
|
||||
-- ***************************************************************************
|
||||
-- MIB configuration backup/restore
|
||||
--
|
||||
-- These objects are used to control the backup of the MIB configuration
|
||||
-- data. The configuration is downloaded to the TFTP server as a backup.
|
||||
--
|
||||
-- SNMP traps will be generated each time a backup is performed to
|
||||
-- indicate whether the file transfer was successful or not.
|
||||
--
|
||||
-- ***************************************************************************
|
||||
|
||||
fourRFMibBackup OBJECT IDENTIFIER ::= { fourRFObjects 3 }
|
||||
|
||||
fourRFMibBackupFile OBJECT-TYPE
|
||||
SYNTAX FourRFTftpFileName
|
||||
MAX-ACCESS read-write
|
||||
STATUS current
|
||||
DESCRIPTION "Path and file name for remote (TFTP) backup, relative to TFTP root."
|
||||
::= { fourRFMibBackup 1 }
|
||||
|
||||
fourRFMibBackupCommand OBJECT-TYPE
|
||||
SYNTAX INTEGER { none (0),
|
||||
remoteBackup (1),
|
||||
localBackup (2)
|
||||
}
|
||||
MAX-ACCESS read-write
|
||||
STATUS current
|
||||
DESCRIPTION "Configuration command to backup a configuration setting the value
|
||||
to localBackup or remoteBackup will instigate the backup. A local
|
||||
backup simply stores the current MIB configuration into Flash memory
|
||||
in the terminal. A remoteBackup uploads the MIB configuration to the
|
||||
currently specified TFTP server"
|
||||
::= { fourRFMibBackup 2 }
|
||||
|
||||
fourRFMibBackupResult OBJECT-TYPE
|
||||
SYNTAX FourRFProcessResultType
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION "Configuration backup status, if no backup has been performed the
|
||||
value is none otherwise the result from the last backup will be
|
||||
returned. If a backup is in progress executing is returned."
|
||||
::= { fourRFMibBackup 3 }
|
||||
|
||||
fourRFMibBackupGroup OBJECT-GROUP
|
||||
OBJECTS { fourRFMibBackupFile,
|
||||
fourRFMibBackupCommand,
|
||||
fourRFMibBackupResult
|
||||
}
|
||||
STATUS current
|
||||
DESCRIPTION "The 4RF common configuration backup group."
|
||||
::= { fourRFGroups 3 }
|
||||
|
||||
|
||||
-- ***************************************************************************
|
||||
-- File upload handling, files will always be uploaded to the backup location
|
||||
-- in flash so we don't overwrite the currently running image/configuration.
|
||||
-- This means we don't need to specify a target location for the download.
|
||||
--
|
||||
-- It is possible to upload four types of files, a kernel image, a root file
|
||||
-- system, MIB configuration and firmware (FPGA). The images may have extra
|
||||
-- data added to allow the version information to be determined easily or
|
||||
-- this could be coded into the file name. File uploads are always performed
|
||||
-- immediately.
|
||||
--
|
||||
-- ***************************************************************************
|
||||
|
||||
fourRFUpload OBJECT IDENTIFIER ::= { fourRFObjects 4 }
|
||||
|
||||
fourRFUploadType OBJECT-TYPE
|
||||
SYNTAX FourRFImageType
|
||||
MAX-ACCESS read-write
|
||||
STATUS current
|
||||
DESCRIPTION "Identifies the type of image to be uploaded."
|
||||
::= { fourRFUpload 1 }
|
||||
|
||||
fourRFUploadFile OBJECT-TYPE
|
||||
SYNTAX FourRFTftpFileName
|
||||
MAX-ACCESS read-write
|
||||
STATUS current
|
||||
DESCRIPTION "Path and file name for remote (TFTP) upload/download, relative
|
||||
to the TFTP server root."
|
||||
::= { fourRFUpload 2 }
|
||||
|
||||
fourRFUploadCommand OBJECT-TYPE
|
||||
SYNTAX INTEGER { none (0),
|
||||
upload (1)
|
||||
}
|
||||
MAX-ACCESS read-write
|
||||
STATUS current
|
||||
DESCRIPTION "Command used to instigate a file upload."
|
||||
::= { fourRFUpload 3 }
|
||||
|
||||
fourRFUploadResult OBJECT-TYPE
|
||||
SYNTAX FourRFProcessResultType
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION "Status of a file upload, this will have to be polled to follow
|
||||
the upload progress."
|
||||
::= { fourRFUpload 4 }
|
||||
|
||||
fourRFUploadGroup OBJECT-GROUP
|
||||
OBJECTS { fourRFUploadType,
|
||||
fourRFUploadFile,
|
||||
fourRFUploadCommand,
|
||||
fourRFUploadResult
|
||||
}
|
||||
STATUS current
|
||||
DESCRIPTION "The 4RF common file upload group."
|
||||
::= { fourRFGroups 4 }
|
||||
|
||||
|
||||
--
|
||||
-- Image table, gives details of all the images currently stored in flash.
|
||||
-- The details include the image type, status and version. Only one image of
|
||||
-- each kernel or rootfs type may be active at any time. We may have one or more
|
||||
-- inactive images however.
|
||||
--
|
||||
-- The approach here allows the different elements making up the running
|
||||
-- software to be updated and configured independently. It also also makes
|
||||
-- it easier to handle more than two images if required.
|
||||
--
|
||||
-- Example
|
||||
--
|
||||
-- imageIndex imageType imageStatus imageVersion
|
||||
-- 1 kernel active 2.4.20
|
||||
-- 2 rootfs inactive version 1
|
||||
-- 3 kernel inactive 2.4.21
|
||||
-- 4 configuration active Working version 5.0 29/6/03
|
||||
--
|
||||
-- MIB images are not stored in this table
|
||||
--
|
||||
|
||||
fourRFImageTable OBJECT-TYPE
|
||||
SYNTAX SEQUENCE OF FourRFImageTableEntry
|
||||
MAX-ACCESS not-accessible
|
||||
STATUS current
|
||||
DESCRIPTION "This table is used to report the image information for each
|
||||
image stored in flash."
|
||||
::= { fourRFObjects 5 }
|
||||
|
||||
fourRFImageTableEntry OBJECT-TYPE
|
||||
SYNTAX FourRFImageTableEntry
|
||||
MAX-ACCESS not-accessible
|
||||
STATUS current
|
||||
DESCRIPTION "Identifies the image table index."
|
||||
INDEX { fourRFImageIndex }
|
||||
::= { fourRFImageTable 1 }
|
||||
|
||||
FourRFImageTableEntry ::= SEQUENCE {
|
||||
fourRFImageIndex Integer32,
|
||||
fourRFImageType INTEGER,
|
||||
fourRFImageStatus INTEGER,
|
||||
fourRFImageSize Unsigned32,
|
||||
fourRFImageVersion OCTET STRING
|
||||
}
|
||||
|
||||
fourRFImageIndex OBJECT-TYPE
|
||||
SYNTAX Integer32
|
||||
MAX-ACCESS not-accessible
|
||||
STATUS current
|
||||
DESCRIPTION "The image table index."
|
||||
::= { fourRFImageTableEntry 1 }
|
||||
|
||||
fourRFImageType OBJECT-TYPE
|
||||
SYNTAX FourRFImageType
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION "The type of image, kernel, rootfs or firmware."
|
||||
::= { fourRFImageTableEntry 2 }
|
||||
|
||||
fourRFImageStatus OBJECT-TYPE
|
||||
SYNTAX FourRFImageStatus
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION "The image status, if current then the image is the current
|
||||
running image. If selected the image will be used following
|
||||
the next system reboot."
|
||||
::= { fourRFImageTableEntry 3 }
|
||||
|
||||
fourRFImageSize OBJECT-TYPE
|
||||
SYNTAX FourRFFileSize
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION "The image size in bytes."
|
||||
::= { fourRFImageTableEntry 4 }
|
||||
|
||||
fourRFImageVersion OBJECT-TYPE
|
||||
SYNTAX FourRFImageVersion
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION "The image version, string which can be used to identify the
|
||||
image. This may include the firmware type, version number or
|
||||
the build date. The exect format of this string will product
|
||||
and/or image specific."
|
||||
::= { fourRFImageTableEntry 5 }
|
||||
|
||||
|
||||
-- ***************************************************************************
|
||||
-- The following objects allow the status of an image to be updated. A new
|
||||
-- image can be selected to run. The new image will pnly be used following
|
||||
-- a system reboot.
|
||||
--
|
||||
-- ***************************************************************************
|
||||
|
||||
fourRFImageControl OBJECT IDENTIFIER ::= { fourRFObjects 6 }
|
||||
|
||||
fourRFImageTableIndex OBJECT-TYPE
|
||||
SYNTAX Integer32
|
||||
MAX-ACCESS read-write
|
||||
STATUS current
|
||||
DESCRIPTION "The image table index, the table entry to be updated."
|
||||
::= { fourRFImageControl 1 }
|
||||
|
||||
fourRFImageTableCommand OBJECT-TYPE
|
||||
SYNTAX INTEGER { none (0),
|
||||
deactivateImage (1),
|
||||
activateImage (2),
|
||||
deleteImage (3)
|
||||
}
|
||||
MAX-ACCESS read-write
|
||||
STATUS current
|
||||
DESCRIPTION "Allows an image to be activated or deactivated, activating an
|
||||
image will change its state to selected but the new image will
|
||||
only be used following a reboot of the system."
|
||||
::= { fourRFImageControl 2 }
|
||||
|
||||
fourRFImageControlGroup OBJECT-GROUP
|
||||
OBJECTS { fourRFImageTableIndex,
|
||||
fourRFImageTableCommand
|
||||
}
|
||||
STATUS current
|
||||
DESCRIPTION "The 4RF common image control group."
|
||||
::= { fourRFGroups 6 }
|
||||
|
||||
|
||||
-- ***************************************************************************
|
||||
-- Web User Management
|
||||
--
|
||||
-- These objects are used to control webaccess to the terminal. It allows
|
||||
-- users to be added, deleted and modified.
|
||||
--
|
||||
-- ***************************************************************************
|
||||
|
||||
fourRFWebUserManagementTable OBJECT-TYPE
|
||||
SYNTAX SEQUENCE OF FourRFWebUserEntry
|
||||
MAX-ACCESS not-accessible
|
||||
STATUS current
|
||||
DESCRIPTION "This table is used to view and modify the current web
|
||||
interface users. Up to 16 different users may be defined."
|
||||
::= { fourRFObjects 7 }
|
||||
|
||||
fourRFWebUserEntry OBJECT-TYPE
|
||||
SYNTAX FourRFWebUserEntry
|
||||
MAX-ACCESS not-accessible
|
||||
STATUS current
|
||||
DESCRIPTION "Identifies the user management table index."
|
||||
INDEX { fourRFWebUserIndex }
|
||||
::= { fourRFWebUserManagementTable 1 }
|
||||
|
||||
FourRFWebUserEntry ::= SEQUENCE {
|
||||
fourRFWebUserIndex Integer32,
|
||||
fourRFWebUserName OCTET STRING,
|
||||
fourRFWebUserPassword OCTET STRING,
|
||||
fourRFWebUserGroup INTEGER,
|
||||
fourRFWebUserEnabled INTEGER,
|
||||
fourRFWebUserPasswordConfirm OCTET STRING
|
||||
}
|
||||
|
||||
fourRFWebUserIndex OBJECT-TYPE
|
||||
SYNTAX Integer32 (0..10)
|
||||
MAX-ACCESS not-accessible
|
||||
STATUS current
|
||||
DESCRIPTION "The user management table index."
|
||||
::= { fourRFWebUserEntry 1 }
|
||||
|
||||
fourRFWebUserName OBJECT-TYPE
|
||||
SYNTAX DisplayString ( SIZE (0..32) )
|
||||
MAX-ACCESS read-write
|
||||
STATUS current
|
||||
DESCRIPTION "The web user name."
|
||||
::= { fourRFWebUserEntry 2 }
|
||||
|
||||
fourRFWebUserPassword OBJECT-TYPE
|
||||
SYNTAX OCTET STRING ( SIZE (4..32) )
|
||||
MAX-ACCESS read-write
|
||||
STATUS current
|
||||
DESCRIPTION "The password entry of a given user."
|
||||
::= { fourRFWebUserEntry 3 }
|
||||
|
||||
fourRFWebUserGroup OBJECT-TYPE
|
||||
SYNTAX FourRFWebUserGroup
|
||||
MAX-ACCESS read-write
|
||||
STATUS current
|
||||
DESCRIPTION "The group to which the user belongs."
|
||||
::= { fourRFWebUserEntry 4 }
|
||||
|
||||
fourRFWebUserEnabled OBJECT-TYPE
|
||||
SYNTAX FourRFWebUserEnabled
|
||||
MAX-ACCESS read-write
|
||||
STATUS current
|
||||
DESCRIPTION "Determines if the user is enabled."
|
||||
::= { fourRFWebUserEntry 5 }
|
||||
|
||||
fourRFWebUserPasswordConfirm OBJECT-TYPE
|
||||
SYNTAX OCTET STRING ( SIZE (4..32) )
|
||||
MAX-ACCESS read-write
|
||||
STATUS current
|
||||
DESCRIPTION "Dummy OID used for password confirmation in the web management interface."
|
||||
::= { fourRFWebUserEntry 6 }
|
||||
|
||||
|
||||
-- ***************************************************************************
|
||||
-- Common traps
|
||||
--
|
||||
-- ***************************************************************************
|
||||
|
||||
--
|
||||
-- Reset event, triggered when the terminal is about to reset.
|
||||
--
|
||||
|
||||
fourRFResetEvent NOTIFICATION-TYPE
|
||||
OBJECTS { fourRFResetType }
|
||||
STATUS current
|
||||
DESCRIPTION "Event indicating that a system reset is about to occur."
|
||||
::= { fourRFEventsV2 1 }
|
||||
|
||||
--
|
||||
-- Backup status event, used to indicate whether a MIB configuration backup
|
||||
-- to the TFTP server was successful
|
||||
--
|
||||
|
||||
fourRFMibBackupStatusEvent NOTIFICATION-TYPE
|
||||
OBJECTS { fourRFMibBackupFile,
|
||||
fourRFMibBackupCommand,
|
||||
fourRFMibBackupResult
|
||||
}
|
||||
STATUS current
|
||||
DESCRIPTION "Event indicating the status of a configuration backup operation."
|
||||
::= { fourRFEventsV2 2 }
|
||||
|
||||
--
|
||||
-- Upload status event, used to indicate whether a file upload from
|
||||
-- the TFTP server was successful
|
||||
--
|
||||
|
||||
fouRFUploadStatusEvent NOTIFICATION-TYPE
|
||||
OBJECTS { fourRFUploadFile,
|
||||
fourRFUploadType,
|
||||
fourRFUploadResult
|
||||
}
|
||||
STATUS current
|
||||
DESCRIPTION "Event indicating the status of a file upload operation."
|
||||
::= { fourRFEventsV2 3 }
|
||||
|
||||
END
|
||||
448
MIBS/4rf/4RF-COMMON-TC
Normal file
448
MIBS/4rf/4RF-COMMON-TC
Normal file
@@ -0,0 +1,448 @@
|
||||
COMMON-TC-4RF DEFINITIONS ::= BEGIN
|
||||
|
||||
--
|
||||
-- File: $Id: 4RF-COMMON-TC.txt,v 1.27 2007/05/07 00:19:51 pk Exp $
|
||||
--
|
||||
-- Copyright: 2004 4RF COMMUNICATIONS LTD
|
||||
--
|
||||
-- Description:
|
||||
-- Common MIB sub-tree for 4RF Communications Ltd., used by all products.
|
||||
-- It defines some useful TEXT-CONVENTIONS relating to 4RF products.
|
||||
--
|
||||
-- Versions:
|
||||
--
|
||||
-- Notes:
|
||||
-- None
|
||||
--
|
||||
|
||||
IMPORTS
|
||||
|
||||
-- Standard imports
|
||||
MODULE-IDENTITY, OBJECT-IDENTITY
|
||||
Integer32, Unsigned32, Counter32
|
||||
FROM SNMPv2-SMI
|
||||
TEXTUAL-CONVENTION, DisplayString, DateAndTime
|
||||
FROM SNMPv2-TC
|
||||
|
||||
-- 4RF Specific imports
|
||||
fourRFGeneric, fourRFModules
|
||||
FROM MIB-4RF;
|
||||
|
||||
|
||||
-- Module Identification
|
||||
fourRFCommonTCModule MODULE-IDENTITY
|
||||
LAST-UPDATED "200704300000Z"
|
||||
ORGANIZATION "www.4rf.com"
|
||||
CONTACT-INFO
|
||||
"postal: 4RF Communications Ltd
|
||||
26 Glover Street
|
||||
Ngauranga
|
||||
PO Box 13-506
|
||||
Wellington 6032
|
||||
New Zealand
|
||||
|
||||
phone: +64 4 499 6000
|
||||
email: support@4rf.com"
|
||||
DESCRIPTION "Common 4RF MIB Textual Conventions."
|
||||
|
||||
-- Revision history
|
||||
-- (in reverse chronological order)
|
||||
|
||||
REVISION "200704300000Z"
|
||||
DESCRIPTION "Second draft"
|
||||
|
||||
REVISION "200402130000Z"
|
||||
DESCRIPTION "First draft"
|
||||
::= { fourRFModules 4 }
|
||||
|
||||
|
||||
--
|
||||
-- LED control types
|
||||
--
|
||||
|
||||
FourRFSimpleLedState ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION "The possible states for a simple LED."
|
||||
SYNTAX INTEGER { off (0),
|
||||
on (1)
|
||||
}
|
||||
|
||||
FourRFTriColourLedState ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION "The possible states of a three-colour LED."
|
||||
SYNTAX INTEGER { off (0),
|
||||
green (1),
|
||||
red (2),
|
||||
orange (3) }
|
||||
|
||||
|
||||
--
|
||||
-- Basic alarm control types
|
||||
--
|
||||
|
||||
FourRFAlarmSeverity ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION "The possible alarm severities, not all values need be used."
|
||||
SYNTAX INTEGER { noSeverity (0),
|
||||
-- informational (1),
|
||||
-- warning (2),
|
||||
minor (3),
|
||||
major (4)
|
||||
-- critical (5)
|
||||
}
|
||||
|
||||
FourRFAlarmPresent ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION "The possible alarm states, alarmPresent indicates that the
|
||||
alarm is active."
|
||||
SYNTAX INTEGER { noAlarmPresent (0),
|
||||
alarmPresent (1)
|
||||
}
|
||||
|
||||
FourRFAlarmEnabled ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION "Indicates whether an alarm is enabled or not, it may be useful
|
||||
to allow specific alarms to be enabled or disabled by the user."
|
||||
SYNTAX INTEGER { disabled (0),
|
||||
enabled (1)
|
||||
}
|
||||
|
||||
FourRFAlarmStatus ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION "This is used to identify current alarm status."
|
||||
SYNTAX INTEGER { noAlarm (0),
|
||||
informationAlarm (1),
|
||||
warningAlarm (2),
|
||||
minorAlarm (3),
|
||||
majorAlarm (4),
|
||||
criticalAlarm (5)
|
||||
}
|
||||
|
||||
FourRFMHSBStatus ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION "This is used to give the state of an MHSB terminal."
|
||||
SYNTAX INTEGER { notAvailable (0),
|
||||
active (1),
|
||||
standby (2)
|
||||
}
|
||||
|
||||
FourRFMHSBCommand ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION "This is used to send a command to an MHSB terminal."
|
||||
SYNTAX INTEGER { noCommand (0),
|
||||
clearSwitchedAlarm (1),
|
||||
forceSwitchover (2)
|
||||
}
|
||||
|
||||
|
||||
--
|
||||
-- Hardware version - an 8 bit integer value
|
||||
--
|
||||
|
||||
FourRFHardwareVersion ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION "The hardware version details."
|
||||
SYNTAX DisplayString ( SIZE (0..32) )
|
||||
|
||||
|
||||
--
|
||||
-- Terminal/Module Serial Number
|
||||
--
|
||||
|
||||
FourRFSerialNumber ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION "A module/terminal serial number format xxxx-xxx."
|
||||
SYNTAX OCTET STRING ( SIZE (8) )
|
||||
|
||||
|
||||
--
|
||||
-- Reset types
|
||||
--
|
||||
|
||||
FourRFResetType ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION "The possible types of reset."
|
||||
SYNTAX INTEGER { none (0),
|
||||
softReset (1),
|
||||
hardReset (2),
|
||||
watchdogReset (3)
|
||||
}
|
||||
|
||||
|
||||
--
|
||||
-- Image details
|
||||
--
|
||||
|
||||
FourRFImageType ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION "The possible image types to upload."
|
||||
SYNTAX INTEGER { none (0),
|
||||
kernel (1),
|
||||
rootfs (2),
|
||||
mib (3),
|
||||
configuration (4),
|
||||
firmware (5)
|
||||
}
|
||||
|
||||
FourRFImageStatus ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The possible image status values, currentImage means it is the running.
|
||||
selectedImage means that the image has been selected and will be used
|
||||
following the next reboot of the system, currentNotSelected means that
|
||||
the image is currently in use but won't be following a reboot."
|
||||
SYNTAX INTEGER { inactiveImage (0),
|
||||
currentImage (1),
|
||||
currentNotSelected (2),
|
||||
selectedImage (3)
|
||||
}
|
||||
|
||||
FourRFImageVersion ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION "The image version details."
|
||||
SYNTAX DisplayString ( SIZE (0..64) )
|
||||
|
||||
|
||||
--
|
||||
-- Other Types
|
||||
--
|
||||
|
||||
FourRFProcessResultType ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION "The possible states for a process which takes time to complete."
|
||||
SYNTAX INTEGER { none (0),
|
||||
executing (1),
|
||||
writingToFlash (2),
|
||||
succeeded (3),
|
||||
failed (4)
|
||||
}
|
||||
|
||||
FourRFTftpFileName ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION "The name of a file to transfered using TFTP."
|
||||
SYNTAX DisplayString ( SIZE (0..255) )
|
||||
|
||||
FourRFFileSize ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION "A size of a file in bytes."
|
||||
SYNTAX Unsigned32
|
||||
|
||||
|
||||
--
|
||||
-- Useful Radio Related Types
|
||||
--
|
||||
|
||||
FourRFFrequency ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION "A frequency value in Hz."
|
||||
SYNTAX Unsigned32
|
||||
|
||||
FourRFTxPower ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION "A transmitter power value in dBm."
|
||||
SYNTAX INTEGER { noPower (0),
|
||||
dbm10 (10),
|
||||
dbm11 (11),
|
||||
dbm12 (12),
|
||||
dbm13 (13),
|
||||
dbm14 (14),
|
||||
dbm15 (15),
|
||||
dbm16 (16),
|
||||
dbm17 (17),
|
||||
dbm18 (18),
|
||||
dbm19 (19),
|
||||
dbm20 (20),
|
||||
dbm21 (21),
|
||||
dbm22 (22),
|
||||
dbm23 (23),
|
||||
dbm24 (24),
|
||||
dbm25 (25),
|
||||
dbm26 (26),
|
||||
dbm27 (27),
|
||||
dbm28 (28),
|
||||
dbm29 (29),
|
||||
dbm30 (30),
|
||||
dbm31 (31),
|
||||
dbm32 (32),
|
||||
dbm33 (33),
|
||||
dbm34 (34),
|
||||
dbm35 (35),
|
||||
dbm36 (36),
|
||||
dbm37 (37),
|
||||
dbm38 (38),
|
||||
dbm39 (39),
|
||||
dbm40 (40)
|
||||
}
|
||||
|
||||
FourRFChannelWidth ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION "The possible channel width values."
|
||||
SYNTAX INTEGER { invalidChannel (0),
|
||||
channel20KHz (1),
|
||||
channel25KHz (2),
|
||||
channel50KHz (3),
|
||||
channel75KHz (4),
|
||||
channel100KHz (5),
|
||||
channel125KHz (6),
|
||||
channel150KHz (7),
|
||||
channel200KHz (9),
|
||||
channel250KHz (10),
|
||||
channel400KHz (13),
|
||||
channel500KHz (20),
|
||||
channel800KHz (25),
|
||||
channel1MHz (30),
|
||||
channel1point25MHz (33),
|
||||
channel1point35MHz (35),
|
||||
channel1point75MHz (40),
|
||||
channel2MHz (42),
|
||||
channel2point5MHz (45),
|
||||
channel3point5MHz (50),
|
||||
channel5point25MHz (55),
|
||||
channel7MHz (60),
|
||||
channel14MHz (70)
|
||||
}
|
||||
|
||||
FourRFNetworkClockStatus ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION "The possible modulation types for the radio."
|
||||
SYNTAX INTEGER { active (0),
|
||||
inactive (1),
|
||||
holdover (2)
|
||||
}
|
||||
|
||||
FourRFRSSI ::= TEXTUAL-CONVENTION
|
||||
DISPLAY-HINT "d-1"
|
||||
STATUS current
|
||||
DESCRIPTION "A receiver RSSI value, in dBm."
|
||||
SYNTAX Integer32(-2000..2000)
|
||||
|
||||
FourRFSNR ::= TEXTUAL-CONVENTION
|
||||
DISPLAY-HINT "d-2"
|
||||
STATUS current
|
||||
DESCRIPTION "A signal to noise ratio in dBm."
|
||||
SYNTAX Integer32
|
||||
|
||||
FourRFModulationType ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION "The possible modulation types for the radio."
|
||||
SYNTAX INTEGER { modQPSK (0),
|
||||
mod16QAM (1),
|
||||
mod32QAM (2),
|
||||
mod64QAM (3),
|
||||
mod128QAM (4),
|
||||
mod256QAM (5),
|
||||
|
||||
-- Modulation off
|
||||
modNone (6)
|
||||
}
|
||||
|
||||
FourRFTemperature ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION "A temperature value in degrees Celcius."
|
||||
SYNTAX Integer32
|
||||
|
||||
FourRFErrorCounter ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION "An error counter, e.g. for the uncorrectable error count."
|
||||
SYNTAX Counter32
|
||||
|
||||
FourRFRfBand ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION "This is used to identify the frequency band of the transmitter
|
||||
The bands are:
|
||||
330 to 400 MHz (300 MHz)
|
||||
400 to 470 MHz (400 MHz)
|
||||
1350 to 1550 MHz (1400 MHz) ."
|
||||
SYNTAX INTEGER { invalidBand (0),
|
||||
band300MHz (10),
|
||||
band400MHz (20),
|
||||
band700MHz (24),
|
||||
band800MHz (26),
|
||||
band900MHz (28),
|
||||
band1400MHz (30)
|
||||
}
|
||||
|
||||
FourRFFanStatus ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION "This is used to identify current fan status."
|
||||
SYNTAX INTEGER { notFitted (0),
|
||||
fanOkay (1),
|
||||
fanFailed (2)
|
||||
}
|
||||
|
||||
FourRFClockSource ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION "This is used to identify the clock source for the terminal."
|
||||
SYNTAX INTEGER { networkClock (0),
|
||||
linkClock (1),
|
||||
internalClock (2)
|
||||
}
|
||||
|
||||
FourRFNetworkClockSelect ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION "This is used to select the priority of the clocks to use."
|
||||
SYNTAX INTEGER { none (0),
|
||||
primary (1),
|
||||
secondary (2)
|
||||
}
|
||||
|
||||
FourRFLoopback ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION "This is used to control loopback or monitor status."
|
||||
SYNTAX INTEGER { loopbackOff (0),
|
||||
loopbackOn (1)
|
||||
}
|
||||
|
||||
|
||||
--
|
||||
-- Web User Handling
|
||||
--
|
||||
|
||||
FourRFWebUserGroup ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION "This is used to identify the group to which a web user belongs."
|
||||
SYNTAX INTEGER { readOnlyGroup (0),
|
||||
readWriteGroup (1),
|
||||
adminGroup (2)
|
||||
}
|
||||
|
||||
FourRFWebUserEnabled ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION "This is used to identify whether a web user is enabled."
|
||||
SYNTAX INTEGER { userDisabled (0),
|
||||
userEnabled (1)
|
||||
}
|
||||
|
||||
FourRFTimeZone ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION "This is used to assign an offset in minutes based on GMT timezone."
|
||||
SYNTAX INTEGER { gmtMinusTwelve (-720),
|
||||
gmtMinusEleven (-660),
|
||||
gmtMinusTen (-600),
|
||||
gmtMinusNine (-540),
|
||||
gmtMinusEight (-480),
|
||||
gmtMinusSeven (-420),
|
||||
gmtMinusSix (-360),
|
||||
gmtMinusFive (-300),
|
||||
gmtMinusFour (-240),
|
||||
gmtMinusThreePointFive (-210),
|
||||
gmtMinusThree (-180),
|
||||
gmtMinusTwo (-120),
|
||||
gmtMinusOne (-60),
|
||||
gmt (0),
|
||||
gmtPlusOne (60),
|
||||
gmtPlusTwo (120),
|
||||
gmtPlusThree (180),
|
||||
gmtPlusFour (240),
|
||||
gmtPlusFive (300),
|
||||
gmtPlusSix (360),
|
||||
gmtPlusSeven (420),
|
||||
gmtPlusEight (480),
|
||||
gmtPlusNine (540),
|
||||
gmtPlusTen (600),
|
||||
gmtPlusEleven (660),
|
||||
gmtPlusTwelve (720),
|
||||
gmtPlusThirteen (800)
|
||||
}
|
||||
|
||||
END
|
||||
104
MIBS/4rf/4RF-MIB
Normal file
104
MIBS/4rf/4RF-MIB
Normal file
@@ -0,0 +1,104 @@
|
||||
MIB-4RF DEFINITIONS ::= BEGIN
|
||||
|
||||
--
|
||||
-- File: $Id: 4RF-MIB.txt,v 1.3 2007/05/02 00:26:45 pk Exp $
|
||||
--
|
||||
-- Copyright: 2002 4RF COMMUNICATIONS LTD
|
||||
--
|
||||
-- Description:
|
||||
-- Top-level MIB sub-tree for 4RF Communications Ltd.
|
||||
--
|
||||
-- Versions:
|
||||
--
|
||||
-- Notes:
|
||||
-- None
|
||||
--
|
||||
|
||||
IMPORTS
|
||||
|
||||
-- Standard imports
|
||||
MODULE-IDENTITY, OBJECT-IDENTITY, enterprises
|
||||
FROM SNMPv2-SMI;
|
||||
|
||||
|
||||
-- Module Identification
|
||||
fourRFRootModule MODULE-IDENTITY
|
||||
LAST-UPDATED "200704300000Z"
|
||||
ORGANIZATION "www.4rf.com"
|
||||
CONTACT-INFO
|
||||
"postal: 4RF Communications Ltd
|
||||
26 Glover Street
|
||||
Ngauranga
|
||||
PO Box 13-506
|
||||
Wellington 6032
|
||||
New Zealand
|
||||
|
||||
phone: +64 4 499 6000
|
||||
email: support@4rf.com"
|
||||
DESCRIPTION "The root MIB module for 4RF Communications Ltd."
|
||||
|
||||
-- Revision history
|
||||
-- (in reverse chronological order)
|
||||
|
||||
REVISION "200704300000Z"
|
||||
DESCRIPTION "Second draft"
|
||||
|
||||
REVISION "200402130000Z"
|
||||
DESCRIPTION "First draft"
|
||||
::= { fourRFModules 1 }
|
||||
|
||||
|
||||
--
|
||||
--
|
||||
-- Root of OID sub-tree for 4RF as assigned by IANA
|
||||
--
|
||||
-- This value MUST NOT BE MODIFIED
|
||||
--
|
||||
--
|
||||
|
||||
fourRFRoot OBJECT-IDENTITY
|
||||
STATUS current
|
||||
DESCRIPTION "The root of the OID sub-tree for 4RF Communications Ltd."
|
||||
::= { enterprises 14817 }
|
||||
|
||||
|
||||
--
|
||||
-- Top Level OID Registrations
|
||||
--
|
||||
|
||||
fourRFRegistrations OBJECT-IDENTITY
|
||||
STATUS current
|
||||
DESCRIPTION "Sub-tree for registrations."
|
||||
::= { fourRFRoot 1 }
|
||||
|
||||
fourRFModules OBJECT-IDENTITY
|
||||
STATUS current
|
||||
DESCRIPTION "Sub-tree for module registrations."
|
||||
::= { fourRFRoot 2 }
|
||||
|
||||
fourRFGeneric OBJECT-IDENTITY
|
||||
STATUS current
|
||||
DESCRIPTION "Sub-tree for common object and event definitions."
|
||||
::= { fourRFRoot 3 }
|
||||
|
||||
fourRFProducts OBJECT-IDENTITY
|
||||
STATUS current
|
||||
DESCRIPTION "Sub-tree for specific object and event definitions."
|
||||
::= { fourRFRoot 4 }
|
||||
|
||||
fourRFCapabilities OBJECT-IDENTITY
|
||||
STATUS current
|
||||
DESCRIPTION "Sub-tree for agent profiles/capabilities."
|
||||
::= { fourRFRoot 5 }
|
||||
|
||||
fourRFRequirements OBJECT-IDENTITY
|
||||
STATUS current
|
||||
DESCRIPTION "Sub-tree for management application requirements."
|
||||
::= { fourRFRoot 6 }
|
||||
|
||||
fourRFExperimental OBJECT-IDENTITY
|
||||
STATUS current
|
||||
DESCRIPTION "Sub-tree for experimental definitions."
|
||||
::= { fourRFRoot 7 }
|
||||
|
||||
END
|
||||
84
MIBS/4rf/4RF-PRODUCTS-MIB
Normal file
84
MIBS/4rf/4RF-PRODUCTS-MIB
Normal file
@@ -0,0 +1,84 @@
|
||||
PRODUCTS-MIB-4RF DEFINITIONS ::= BEGIN
|
||||
|
||||
--
|
||||
-- File: $Id: 4RF-PRODUCTS-MIB.txt,v 1.3 2007/05/02 00:26:45 pk Exp $
|
||||
--
|
||||
-- Copyright: 2002 4RF COMMUNICATIONS LTD
|
||||
--
|
||||
-- Description:
|
||||
-- Products MIB sub-tree for 4RF Communications Ltd. It defines the root
|
||||
-- identifiers for all 4RF SNMP managed products.
|
||||
--
|
||||
-- Versions:
|
||||
--
|
||||
-- Notes:
|
||||
-- None
|
||||
--
|
||||
|
||||
IMPORTS
|
||||
|
||||
-- Standard imports
|
||||
MODULE-IDENTITY, OBJECT-IDENTITY, enterprises
|
||||
FROM SNMPv2-SMI
|
||||
|
||||
-- 4RF Specific imports
|
||||
fourRFModules, fourRFProducts, fourRFExperimental
|
||||
FROM MIB-4RF;
|
||||
|
||||
|
||||
-- Module Identification
|
||||
fourRFProductsModule MODULE-IDENTITY
|
||||
LAST-UPDATED "200704300000Z"
|
||||
ORGANIZATION "www.4rf.com"
|
||||
CONTACT-INFO
|
||||
"postal: 4RF Communications Ltd
|
||||
26 Glover Street
|
||||
Ngauranga
|
||||
PO Box 13-506
|
||||
Wellington 6032
|
||||
New Zealand
|
||||
|
||||
phone: +64 4 499 6000
|
||||
email: support@4rf.com"
|
||||
DESCRIPTION
|
||||
"4RF product registrations, all 4RF SNMP managed products have
|
||||
a root identifier specified here."
|
||||
|
||||
-- Revision history
|
||||
-- (in reverse chronological order)
|
||||
|
||||
REVISION "200704300000Z"
|
||||
DESCRIPTION "Second draft"
|
||||
|
||||
REVISION "200402130000Z"
|
||||
DESCRIPTION "First draft"
|
||||
::= { fourRFModules 2 }
|
||||
|
||||
|
||||
--
|
||||
-- OID Registrations
|
||||
--
|
||||
|
||||
|
||||
--
|
||||
-- Currently the MIB is still being defined, all objects are placed
|
||||
-- under fourRFExperimental, when the MIB has been completed these
|
||||
-- objects will be moved to fourRFProducts.
|
||||
--
|
||||
|
||||
fourRFCommon OBJECT-IDENTITY
|
||||
STATUS current
|
||||
DESCRIPTION "Sub-tree for common elements."
|
||||
::= { fourRFExperimental 1 }
|
||||
|
||||
fourRFAprisa OBJECT-IDENTITY
|
||||
STATUS current
|
||||
DESCRIPTION "Sub-tree for Aprisa/AprisaView."
|
||||
::= { fourRFExperimental 2 }
|
||||
|
||||
fourRFAprisaXE OBJECT-IDENTITY
|
||||
STATUS current
|
||||
DESCRIPTION "Sub-tree for AprisaXE."
|
||||
::= { fourRFExperimental 3 }
|
||||
|
||||
END
|
||||
Reference in New Issue
Block a user