BIANCA-BRICK-PMX-MIB
File:
BIANCA-BRICK-PMX-MIB.mib (15036 bytes)
Imported modules
Imported symbols
Defined Types
PMXIfEntry |
|
SEQUENCE |
|
|
|
|
pmxIfIndex |
INTEGER |
|
|
pmxIfSelftest |
INTEGER |
|
|
pmxIfLayer1State |
INTEGER |
|
|
pmxIfLayer1Mode |
INTEGER |
|
|
pmxIfLayer1Framing |
INTEGER |
|
|
pmxIfLayer1LineCode |
INTEGER |
|
|
pmxIfChannelMode |
INTEGER |
|
|
pmxIfLoopbackMode |
INTEGER |
|
|
pmxIfErrors |
Counter |
|
|
pmxIfPortMode |
INTEGER |
|
|
pmxIfLOS |
Counter |
|
|
pmxIfNoFAS |
Counter |
|
|
pmxIfRemoteAlarms |
Counter |
|
|
pmxIfAlarmInds |
Counter |
|
|
pmxIfCRC4Errors |
Counter |
|
|
pmxIfPositiveSlip |
Counter |
|
|
pmxIfNegativeSlip |
Counter |
|
Defined Values
org |
1.3 |
OBJECT IDENTIFIER |
|
|
|
dod |
1.3.6 |
OBJECT IDENTIFIER |
|
|
|
private |
1.3.6.1.4 |
OBJECT IDENTIFIER |
|
|
|
bintec |
1.3.6.1.4.1.272 |
OBJECT IDENTIFIER |
|
|
|
bibo |
1.3.6.1.4.1.272.4 |
OBJECT IDENTIFIER |
|
|
|
pmx |
1.3.6.1.4.1.272.4.12 |
OBJECT IDENTIFIER |
|
|
|
pmxIfTable |
1.3.6.1.4.1.272.4.12.1 |
The pmxIfTable contains information relating to the
interfaces found on the system. Each entry corresponds to
a connected primary rate interface. Entries can only be
added or deleted by the system.
Creating entries: Entries are created by the system
only when a new PMX module is installed.
Deleting entries: Entries are removed by the system
after the appropriate PMX module is removed. |
Status: mandatory |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
SEQUENCE OF |
|
|
|
|
PMXIfEntry |
|
pmxIfEntry |
1.3.6.1.4.1.272.4.12.1.1 |
Tok_String |
Status: mandatory |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
PMXIfEntry |
|
|
pmxIfIndex |
1.3.6.1.4.1.272.4.12.1.1.1 |
Unique Index of the primary rate interface. The index
is similar to slotnumber * 1000 and is also refenced in
the ifTable, the isdnIfTable and in the isdnStkTable
|
Status: mandatory |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
INTEGER |
|
|
pmxIfSelftest |
1.3.6.1.4.1.272.4.12.1.1.2 |
The result of the initial selftest of the PMX module
If the result is not succesful, the module is disabled
successful(1) All selftests succeeded;
acfa-failure(2) failure with the module ACFA Chip
m32-failure(3) failure with the module M32 Chip
mem-failure(4) failure with the module memory |
Status: mandatory |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
INTEGER |
successful(1), acfa-failure(2), m32-failure(3), mem-failure(4) |
|
pmxIfLayer1State |
1.3.6.1.4.1.272.4.12.1.1.3 |
The layer 1 state of the primary rate interface
active(F1) active, framing and synchronisation
is o.k. This is the only state where
data-transmission is possible
remote-alarm(F2) receipt of an RAI, remote alarm
indication, from the remote side;
The remote-alarm is also known as
yellow alarm or distant alarm
no-signal(F3) no signal is received, RAI will
be transmitted. NOS is also known
as red alarm .
no-sync(F4) signal is received but synchronistation
is not possible, RAI will be transmitted
The received signal may also consist
of contingous Ones
crc-error(F5) signal and synchronisation are o.k. but
signal has heavy crc errors, RAI will
be transmitted
power-on(F6) initial state after power was
switched on (transient)
resync(7) Setting Layer 1 State to resync can
be used to force resynchronisation
The Layer1states are also visible in the isdnIfTable, but
the state numbers are mapped to those of an BRI-Interface |
Status: mandatory |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
INTEGER |
active(1), remote-alarm(2), no-signal(3), no-sync(4), crc-error(5), power-on(6), resync(7) |
|
pmxIfLayer1Mode |
1.3.6.1.4.1.272.4.12.1.1.4 |
In T1 and E1 mode the primary rate interface is working
with totaly different clock frequencies, framing and
impedance. This depends on one of the jumpers on the
PMX module. For correct operation all 5 jumpers must be
in correct position.
E1 is normaly used in Europe and is similar to
PCM30, 30 channels, 2 Mbit/sec, Impedance 120 Ohm
T1 is normaly used in USA and is similar to
PCM24, 24 channels, 1.5 Mbit/sec, Impedance 100 Ohm
|
Status: mandatory |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
INTEGER |
e1(1), t1(2) |
|
pmxIfLayer1Framing |
1.3.6.1.4.1.272.4.12.1.1.5 |
In T1 and E1 mode the primary rate interface can work
with totaly different framing types on layer 1. The
framing type must match the configuration of the
first connected point e.g. the exchange or the NT
e1(1) E1 - minimum mode, CCITT Recommendation G.704
(Table 4a)
e1-crc(2) E1 , crc mode, CCITT Recommendation G.704
(Table 4b)
e1-mf(3) E1 , CCITT Recommendation G.704 (Table 4a)
with Timeslot 16 multiframing enabled
e1-mf-crc(4) E1 , CCITT Recommendation G.704 (Table 4b)
with Timeslot 16 multiframing enabled
t1-esf(5) T1 , Extended SuperFrame mode DS1
t1-d4(6) T1 , AT&T D4 format DS1
t1-framings can only be set when pmxIfLayer1Mode is t1
e1-framings can only be set when pmxIfLayer1Mode is e1
The default framing for t1 is t1-esf, the default framing
for e1 is e1-crc
Modifications of the default values are usualy not required.
Exceptions are only known for sweden and france (use e1)
|
Status: mandatory |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
INTEGER |
e1(1), e1-mf(2), e1-crc(3), e1-mf-crc(4), t1-esf(5), t1-d4(6) |
|
pmxIfLayer1LineCode |
1.3.6.1.4.1.272.4.12.1.1.6 |
In T1 mode the primary rate interface is able
to work with different line codes.
e1-hdb3(1) High Density Bipolar 3 Level Coding
This is the only valid linecoding for E1
t1-b8zs(2) Bipolar 8 Zero Substitution
B8ZS refers to the use of a specified
pattern of normal bits and bipolar
violations which are used to replace a
sequence of eight zero bits
t1-ami(3) Alternating Mark Inversion.
AMI refers to a mode wherein no zero code
suppression is present and the line encoding
does not solve the problem directly. In this
application, the higher layer must provide data
which meets or exceeds the pulse density
requirements, such as inverting HDLC data.
t1-linecodes can only be set when pmxIfLayer1Mode is t1
e1-linecodes can only be set when pmxIfLayer1Mode is e1
The default linecode for t1 is t1-b8zs
|
Status: mandatory |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
INTEGER |
e1-hdb3(1), t1-b8zs(2), t1-ami(3) |
|
pmxIfChannelMode |
1.3.6.1.4.1.272.4.12.1.1.7 |
In T1 and E1 mode the primary rate interface may work
with different channel types. Usually every timeslot
is similar to one channel but it is also possible to
bundle multiple timeslots to one channel with a higher
bandwith. This channel bundeling is currently not
supported by the switching equipment for dialup
connections of any network-provider. But usage is
possible with leased lines.
e1-standard(1) 1 D-channel 64 kbit, 30 B-channels 64kbit
bchannels are numbered from 1 to 15 and
from 16 to 31
e1-1tr6(2) 1 D-channel 64 kbit, 30 B-channels 64kbit
identical timeslotassignment as e1-standard
but bchannels are numbered from 1 to 30
e1-H0(3) 1 D-channel 64 kbit, 5 B-channels 384kbit
bchannels are numbered from 1 to 5
e1-H12(4) 1 D-channel 64 kbit, 1 B-channel 1920kbit
e1-burst(5) 1 channel 1984kbit, channel number is 0
t1-standard(6) 1 D-channel 64 kbit, 23 B-channels 64kbit
bchannels are numbered from 1 to 23
t1-H0(7) 1 D-channel 64 kbit, 4 B-channels 384kbit
bchannels are numbered from 1 to 4
t1-H11(8) 1 D-channel 64 kbit, 1 B-channel 1472kbit
t1-burst(9) 1 channel 1536kbit, channel number is 0
t1-channelmodes can only be set when pmxIfLayer1Mode is t1
e1-channelmodes can only be set when pmxIfLayer1Mode is e1
|
Status: mandatory |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
INTEGER |
e1-standard(1), e1-1tr6(2), e1-H0(3), e1-H12(4), e1-burst(5), e1-raw(6), t1-standard(10), t1-H0(11), t1-H11(12), t1-burst(13), t1-raw(14) |
|
pmxIfLoopbackMode |
1.3.6.1.4.1.272.4.12.1.1.8 |
Loopback-Mode is only required for equipment test
no-loop(1) do not loopanything, this is the
correct mode for normal operation
full-loop(2) loopback everything incl. the
signaling channel
all-channels(3) loopback all B and D-channels
only-bchannels(4) loopback only the B-channels
The loops are usualy not reversible. Reboot is required
to regain normal operation mode.
|
Status: mandatory |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
INTEGER |
no-loop(1), full-loop(2), all-channels(3), only-bchannels(4) |
|
pmxIfErrors |
1.3.6.1.4.1.272.4.12.1.1.9 |
The measured PMX interface errors since startup |
Status: mandatory |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
Counter |
|
|
pmxIfPortMode |
1.3.6.1.4.1.272.4.12.1.1.10 |
PortMode switches the CM-PRI's 'Out'-port
normal(1) 'Out'-port is disabled, this
CM-PRI is connected to 'In'
go-thru(2) 'Out'-port is enabled, this
CM-PRI is disconnected.
go-thru-tst(3) same as 'go-thru' but an internal
test loop is activated
|
Status: mandatory |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
INTEGER |
normal(1), go-thru(2), go-thru-tst(3) |
|
pmxIfLOS |
1.3.6.1.4.1.272.4.12.1.1.21 |
Loss Of Signal conditions since startup |
Status: mandatory |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
Counter |
|
|
pmxIfNoFAS |
1.3.6.1.4.1.272.4.12.1.1.22 |
Loss Of Frame Alignment conditions since startup |
Status: mandatory |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
Counter |
|
|
pmxIfRemoteAlarms |
1.3.6.1.4.1.272.4.12.1.1.23 |
Remote Alarms received since startup |
Status: mandatory |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
Counter |
|
|
pmxIfAlarmInds |
1.3.6.1.4.1.272.4.12.1.1.24 |
Alarms received since startup |
Status: mandatory |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
Counter |
|
|
pmxIfCRC4Errors |
1.3.6.1.4.1.272.4.12.1.1.25 |
CRC4 errors detected since startup |
Status: mandatory |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
Counter |
|
|
pmxIfSlipPositive |
1.3.6.1.4.1.272.4.12.1.1.26 |
Positive Slip conditions detected since startup;
flags that the frequency of receive clock is less
than frequency of internal system clock |
Status: mandatory |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
Counter |
|
|
pmxIfSlipNegative |
1.3.6.1.4.1.272.4.12.1.1.27 |
Negative Slip conditions detected since startup;
flags that the frequency of receive clock is greater
than frequency of internal system clock |
Status: mandatory |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
Counter |
|
|