AirPairv2cTrap-MIB
AI MIB Summary
Standard SNMP MIB module defining data structures for AirPairv2cTrap-MIB.
89
Objects
Active
Status
3
Dependencies
Imported Objects
Objects
89 total| Object Name |
|---|
apSnmpV2Notification OBJECT IDENTIFIER .1.3.6.1.4.1.7262.1.26 |
IMPORTS NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26 |
apSnmpV2Traps OBJECT IDENTIFIER .1.3.6.1.4.1.7262.1.26.0 |
coldStartV2cA coldStart trap signifies that the sending protocol entity
is reinitializing itself such that the agent's configuration
or the protocol entity implementation may be altered. NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.0 |
linkDownV2cA linkDown trap signifies that the sending protocol entity
recognizes a failure in one of the communication links
represented in the agent's configuration. NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.1 |
linkUpV2cA linkUp trap signifies that the sending protocol entity
recognizes that one of the communication links represented
in the agent's configuration has come up. NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.2 |
explicitAuthenticationFailureV2cAuthentication of the peer AirPair node has failed. The
severity is critical, the probable cause is an incorrect
authentication configuration on AirPair faulty cable
between the modem and radio, and recommended course of
action is to check both ends of the link. NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.3 |
autoNegotiationDuplexMismatchV2cThe AirPair ethernet interface has a mismatch in duplex. The
severity is major, the probable cause is an incorrect
configuration of the switch or router connected to AirPair,
or the AirPair autonegotion settings. The recommended course
of action is to check the connection. NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.4 |
modemLossOfSignalLockFromDemodulatorV2cLoss of signal lock from the demodulator. The severity is
critical, the probable cause is lost synchronization with
the far end, and recommended course of action is to check
the operational state of both ends of the link. NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.5 |
modemUncorrectedBerThresholdExceededV2cThe uncorrected BER threshold has been exceeded. The severity is major,
the probable cause is physical interference in the air link
or misalignment of the radios or severe weather conditions,
and recommended course of action is to check the line of site
between the air pair nodes. NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.6 |
modemModulatorPllLockFailureV2cModulator PLL failure. The severity is critical, the probable
cause a faulty modem card within AirPair, and recommended
course of action is to replace the modem unit. NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.7 |
modemModulatorLossOfSyncBytesV2cLoss of sync bytes at the input of the modulator. The severity
is critical, the probable cause is physical interference in the
air link, and recommended course of action is to check the line
of site between the air pair nodes. NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.8 |
modemModulatorInputFifoErrorV2cOverrun or underrun of the FIFO contained inside the modulator.
The severity is critical, the probable cause is electrical
interference, and recommended course of action is to reset the
modem unit, or relpace the modem unit. NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.9 |
modemModulatorInputDataErrorV2cAll ones or all zeroes at the input of the modulator. The severity
is critical, the probable cause is electrical interference, and
recommended course of action is to reset the modem unit, or replace
the modem unit. NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.10 |
modemSnrBelowThresholdV2cThe demodulator SNR performance worse than programmed levels. The
severity is major, the probable cause is physical interference in the
air link path or misalignment of the radios or severe weather conditions,
and recommended course of action is to check the line of site between
the air pair nodes. NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.11 |
radioPLDROLostLockV2cThe PLDRO/LO has lost lock on the radio. The severity is critical, the
probable cause a faulty radio unit within AirPair, and recommended course
of action is to replace the radio unit. NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.12 |
radioLostCommunicationV2cRS232 communication lost between AIRPAIR and the radio. The severity is
critical, the probable cause is a faulty cable between the modem and radio,
and recommended course of action is to check the connection. NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.13 |
radioMismatchV2cThe radio connected to the AIRPAIR modem does not match the frequency
programmed into the modem unit. The severity is major, the probable cause
is an incorrectly programmed modem or an incorrect radio type connected to
the modem, and recommended course of action is to check the modem frequency
settings and radio hardware version number or serial number. NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.14 |
radioPowerAmpV2cThe power amplifier on the radio is not operating within normal operating
specifications. The severity is critical, the probable cause a faulty radio
unit within AirPair, and recommended course of action is to replace the
radio unit. NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.15 |
ifTxSynthUnlockedV2cThe IF card within the modem unit has a Transmit Synthesizer which is not
locked and as a result will not transmit. The severity is critical, the
probable cause an incorrectly programmed frequency setting in the modem
or a faulty IF card, and recommended course of action is to check frequency
setting in the modem or to replace the modem unit. NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.16 |
ifRxSynthUnlockedV2cThe IF card within the modem unit has a Receive Synthesizer which is not
locked. The severity is critical, the probable cause an incorrectly
programmed frequency setting in the modem or a faulty IF card, and
recommended course of action is to check frequency setting in the modem
or to replace the modem unit. NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.17 |
ttySessionCommencedV2cA person has successfully gained access to the ascii management port (telnet,
local management port, or HTTP). The username is included in the Trap. NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.18 |
ttySessionTerminatedV2cA person has logged out of an ascii management port (telnet, local management
port, or HTTP). The username is included in the Trap. NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.19 |
rslBelowThresholdV2cThe RSL has been detected below its minimum threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.20 |
droppedFramesThresholdExceededV2cThe ethernet dropped frames threshold has been detected above its threshold value. NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.21 |
bwUtilizationThresholdExceededV2cThe ethernet bandwidth threshold has been detected above its threshold value. NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.22 |
explicitAuthFailureClearedV2cThe condition has cleared. The peer node is now authenticated. NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.23 |
autoNegDuplexMismatchClearedV2cThe condition has cleared. The Ethernet connection is not experiencing
auto-negotiation duplex mismatch. NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.24 |
lossOfSyncSigFromDemoClearedV2cThe condition has cleared. The demodulator is synchronized. NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.25 |
uncorrectedBerThresExceededClearedV2cThe condition has cleared. The demodulator uncorrected BER is now below its minimum
threshold value. NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.26 |
modemModPLLFailureClearedV2cThe condition has cleared. The modem PLL is not failing. NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.27 |
modemModLossOfSyncBytesClearedV2cThe condition has cleared. The modem is not experiencing loss of synch bytes. NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.28 |
modemModInputFifoOverUnderClearedV2cThe condition has cleared. The modem is not experiencing input FIFO
over/under runs. NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.29 |
modemModInputDataInacClearedV2cThe condition has cleared. The modem is not experiencing data inactivity. NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.30 |
snrBelowThresholdClearedV2cThe condition has cleared. SNR is now above its minimum threshold value. NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.31 |
radioPLDROLostLockClearedV2cThe condition has cleared. The radio PLDRO/LO lost lock condition has cleared. NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.32 |
radioLostCommunicationClearedV2cThe condition has cleared. RS232 communication has been re-establisted between
AIRPAIR and the radio. NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.33 |
radioMismatchClearedV2cThe condtion has cleared. The radio matches the programmed parameters in the modem. NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.34 |
radioPowerAmpClearedV2cThe condtion has cleared. The radio Power Amp is not in the failed state. NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.35 |
ifTxSynthUnlockedClearedV2cThe condtion has cleared. The IF stage transmit synthesizer is now locked. NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.36 |
ifRxSynthUnlockedClearedV2cThe condtion has cleared. The IF stage receive synthesizer is now locked. NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.37 |
rslBelowThresholdClearedV2cThe condition has cleared. RSL is now above its minimum threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.38 |
droppedFramesThresholdExceededClearedV2cThe condition has cleared.The ethernet dropped frames threshold is now
below its threshold value. NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.39 |
bwUtilizationThresholdExceededClearedV2cThe condition has cleared. The ethernet bandwidth threshold is now below
its threshold value. NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.40 |
rxIfCableLossExceededV2cThe Rx cable loss has exceeded limit. This trap is only valid when the
AirPair installation type is IDU-ODU split. NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.41 |
rxIfCableLossExceededClearedV2cThe condition has cleared. The Rx cable loss is now within limit. This trap
is only valid when the AirPair installation type is IDU-ODU split NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.42 |
txIfCableLossExceededV2cThe Tx cable loss has exceeded limit. This trap is only valid when the AirPair
installation type is IDU-ODU split NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.43 |
txIfCableLossExceededClearedV2cThe condition has cleared. The Tx cable loss is now within limit. This trap is
only valid when the AirPair installation type is IDU-ODU split NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.44 |
fan1FailedV2cThe Fan1 has failed. This trap is only valid when the AirPair installation
type is IDU-ODU split NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.45 |
fan1FailedClearedV2cThe condition has cleared. The fan1 is running normally. This trap is only
valid when the AirPair installation type is IDU-ODU split NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.46 |
fan2FailedV2cThe Fan2 has failed. This trap is only valid when the AirPair installation
type is IDU-ODU split NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.47 |
fan2FailedClearedV2cThe condition has cleared. The fan2 is running normally. This trap is only valid
when the AirPair installation type is IDU-ODU split NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.48 |
modemCardMismatchedHardwareFirmwareV2cThe modem card has incompatible hardware and firmware. The firmware will not run properly on this card. NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.49 |
modemCardMismatchedHardwareFirmwareClearedV2cThe condition has cleared. The modem card has compatible hardware and firmware. The firmware will run properly on this card. NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.50 |
atpcConfigMismatchV2cATPC configuration mismatch in the Airpair systems. ATPC is
enabled at one system, but ATPC is not enabled at the other
system. NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.51 |
atpcConfigMismatchClearedV2cATPC configuration mismatch in the Airpair systems is cleared.
Both systems enabled ATPC. NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.52 |
radioHiPwrOptM1V2cWhen hi-power radio is used, hi-power gate M1 drain current is
out of lower or upper limits. NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.53 |
radioHiPwrOptM1ClearedV2cWhen hi-power radio is used, hi-power gate M1 drain current
is between lower and upper limits. NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.54 |
radioHiPwrOptM2V2cWhen hi-power radio is used, hi-power gate M2 drain current is
out of lower or upper limits. NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.55 |
radioHiPwrOptM2ClearedV2cWhen hi-power radio is used, hi-power gate M2 drain current
is between lower and upper limits. NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.56 |
radioHiPwrTxDetectorV2cWhen hi-power radio is used, hi-power tx detector dBm value
is smaller than limit. NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.57 |
radioHiPwrTxDetectorClearedV2cWhen hi-power radio is used, hi-power tx detector dBm
value is not smaller than limit. NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.58 |
sntpServersUnreachableV2cCan't reach any of the sntp servers NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.59 |
sntpServersUnreachableClearedV2cAt least one of SNTP servers is reachable NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.60 |
rlsMismatchV2cRLS mismatch NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.61 |
rlsMismatchClearedV2cRLS mismatch cleared NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.62 |
rLSShutdownActivatedV2cRLS shutdown is activated NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.63 |
rLSShutdownActivatedClearedV2cRLS shutdown is not activated NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.64 |
frequencyFileInvalidV2cWhen the executing frequency file is invalid,
this trap is generated. NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.65 |
optionalParaNotEntFreqFileV2cwhen the optional parameters are not entered in frequency file,
and the system boots up, this trap is generated. NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.66 |
progRadioBandNotFoundFreqFileV2cwhen the executing frequency file doesn't contain the info related to programmed
radio band, this trap is generated. NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.67 |
redundancySwitchOverSuccessV2cRadio Redundancy Switch over success NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.68 |
redundancySwitchOverFailedV2cRadio Redundancy Switch over failed NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.69 |
redundancyNoAtpcSupportV2cRadio does not support atpc NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.70 |
redundancyNoAtpcSupportClearedV2cRadio does not support atpc cleared NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.71 |
redundancyInvalidFirmwareV2cRadio firmware on radio and on modem card mismatch NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.72 |
redundancyInvalidFirmwareClearedV2cRadio firmware mismatch cleared NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.73 |
redundancySwitchInitByLocalendV2cRadio switch initiated by local end NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.74 |
redundancySwitchInitByPeerV2cRadio switch initiated by peer NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.75 |
aamConfigMisMatchV2cAutomatic Adaptive modulation configuration mismatch NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.76 |
aamConfigMisMatchClearV2cAutomatic Adaptive modulation configuration mismatch cleared NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.77 |
aamQpskActiveV2cAutomatic Adaptive modulation running on QPSK modulation NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.78 |
aamQpskActiveClearedV2cAutomatic Adaptive modulation running on higher modulation NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.79 |
primaryRadioFaultyV2cPrimary radio is faulty. NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.80 |
primaryRadioFaultyClearedV2cprimary radio is not faulty anymore. NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.81 |
radioSerialNumberMismatchV2cRedundancy, Radio Serial number mismatch. NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.82 |
radioSerialNumberMismatchClearedV2cRedundancy, Radio Serial number mismatch cleared. NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.83 |
excessiveCableLossChangeV2cExcessive cable loss change NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.84 |
excessiveCableLossChangeClearedV2cExcessive cable loss change cleared NOTIFICATION-TYPE .1.3.6.1.4.1.7262.1.26.0.85 |