Sources for this description
MIBdepot
Parsed from xylo-modem.mib.txt · avaya · XYLO-MODEM-MIB
Source file: Download xylo-modem.mib.txt
OID reference
1.3.6.1.4.1.15.2.100.7.1.1.5
Current State of the modem. State explaination are: busy(1) - Modem is handling a call. avail(2) - modem is idle and available. busiedOut(3) - modem is taken out of service by the system manager. failed(4) - Boot-up diagnostic has marked this modem as failed. crashed(5) - The driver has determined this modem as failed…
Identification
{1 3 6 1 4 1 15 2 100 7 1 1 5}
| Value | Name |
|---|---|
| 1 | busy |
| 2 | available |
| 3 | busiedOut |
| 4 | failed |
| 5 | crashed |
| 6 | outOfService |
At least one MIB declaration places this object in a table row. A value belongs to a row instance; its suffix depends on the row's INDEX or AUGMENTS definition.
In XYLO-MODEM-MIB, the row index mdmNumber is declared as INTEGER. A non-negative index value is encoded as one numeric subidentifier. An instance has the form .1.3.6.1.4.1.15.2.100.7.1.1.5.<mdmNumber>. Use an index value actually present on the device and permitted by its MIB. Other definitions can differ.
snmpwalk [connection options] DEVICE .1.3.6.1.4.1.15.2.100.7.1.1.5
Replace the placeholders with your connection and authentication options. Available permissions and device support can differ from the MIB.
Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Parsed from xylo-modem.mib.txt · avaya · XYLO-MODEM-MIB
Source file: Download xylo-modem.mib.txt
Historical records
mdmStatStatus OBJECT-TYPE
SYNTAX INTEGER {
busy(1),
available(2),
busiedOut(3),
failed(4),
crashed(5),
outOfService(6)
}
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Current State of the modem.
State explaination are:
busy(1) - Modem is handling a call.
avail(2) - modem is idle and available.
busiedOut(3) - modem is taken out of service by the
system manager.
failed(4) - Boot-up diagnostic has marked this modem
as failed.
crashed(5) - The driver has determined this modem as
failed.
outOfService(6) - The modem was taken out of service
automatically.
This MIB object corresponds to the status reported by
the na/admin command `modem -m <modem number>'."
::= { mdmStatEntry 5 }
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.15.2.100.7.1.1.1 | mdmStatAssign | 0 | 0 | A call progress counter, displayed by CLI command 'inmoderr'. Number of times this modem has been assigned to a call. |
| 1.3.6.1.4.1.15.2.100.7.1.1.2 | mdmStatChat | 0 | 0 | A call progress counter, displayed by CLI command 'inmoderr'. Number of times this modem has been told to answer. |
| 1.3.6.1.4.1.15.2.100.7.1.1.3 | mdmStatDcd | 0 | 0 | A call progress counter, displayed by CLI command 'inmoderr'. Number of times this modem has established a connection. |
| 1.3.6.1.4.1.15.2.100.7.1.1.4 | mdmStatConsecFail | 0 | 0 | A call progress counter, displayed by CLI command 'inmoderr'. Number of consecutive times this modem has failed to establish a co… |
| 1.3.6.1.4.1.15.2.100.7.1.1.6 | mdmStatTotCalls | 0 | 0 | The total number of calls handled by this modem. This counter is reset to zero after system reboot or after the modem is reset. |
| 1.3.6.1.4.1.15.2.100.7.1.1.7 | mdmStatTotFailures | 0 | 0 | The total number of calls failed to be answered by this modem. This counter is reset to zero after system reboot or after the mo… |