CISCO-WAN-AXIPOP-MIB
AI MIB Summary
Standard SNMP MIB module defining data structures for CISCO-WAN-AXIPOP-MIB.
1995
Objects
Active
Status
4
Dependencies
Imported Objects
Objects
1995 total| Object Name |
|---|
vismSigGrp OBJECT IDENTIFIER .1.3.6.1.4.1.173.7.12.6 |
vismHdlcChanTableThis table is used for maintaining the statistics info
for the HDLC channels on VISM. It also keeps track of some
configurable parameters required for proper operation of
HDLC driver in VISM. SEQUENCE OF VismHdlcChanEntry .1.3.6.1.4.1.173.7.12.6.1 |
vismHdlcChanEntryAn entry for each HDLC channel. VismHdlcChanEntry .1.3.6.1.4.1.173.7.12.6.1.1 |
vismHdlcChanNumThis object is the index of this table.
It refers to the ds0IfIndex in the dsx0VismCnfTable.ro INTEGER .1.3.6.1.4.1.173.7.12.6.1.1.1 |
vismHdlcRowStatusThis variable allows to add, delete or modify the entry.
createAndGo: Use this to add an entry in this table.
There are two case of creating a entry: 1) a ccs channel
is explicitly created for Aal2 trunking. In this case, if
the DS0 already created for PRI or GR-303 the request of
creation should be rejected.
2) A Hdlc entry will be implicitly created before creating
a LAPD entry. In this case if the DS0 is already used for
Aal2 trunking the request should be rejected. No entry in
Lapd shall be created.
active: This values is returned, once the row is created
destroy: Use this to delete an entry from this table.
According to the creation, an entry can be explicitly
destroyed or implicitly removed.rw Enumeration .1.3.6.1.4.1.173.7.12.6.1.1.2 |
vismHdlcMaxFrameSizeThis object describes the maximum frame size that is
allowed on this HDLC channel. This value is not configurable.
The value for this object is 264.rodeprecated INTEGER .1.3.6.1.4.1.173.7.12.6.1.1.3 |
vismHdlcLcnNumThis object describes LCN or the PVC channel number with
which the HDLC channel is associated with. It is applicable
only for trunking applications where the CCS frames are
transmitted to the other end point over an AAL5 PVC. For
PRI or GR-303 applications, this is not applicable since the
CCS frames in that case are backhauled to the call agent.rw INTEGER .1.3.6.1.4.1.173.7.12.6.1.1.4 |
vismHdlcXmtFramesThis object maintains the count of HDLC frames transmitted
to the HDLC channel on VISM.ro Counter .1.3.6.1.4.1.173.7.12.6.1.1.5 |
vismHdlcRcvFramesThis object maintains the count of HDLC frames received
from the HDLC channel on VISM.ro Counter .1.3.6.1.4.1.173.7.12.6.1.1.6 |
vismHdlcRcvCrcErrorsThis object describes the count of HDLC frames dropped
due to CRC errors in the frames received from the HDLC
Channel.ro Counter .1.3.6.1.4.1.173.7.12.6.1.1.7 |
vismHdlcRcvBufOverflowsThis object describes the count of HDLC receiver
buffer overflow condition. This can occur if the rate
of arrival of HDLC frames from the line is more than
the processing rate by the CPU.ro Counter .1.3.6.1.4.1.173.7.12.6.1.1.8 |
vismHdlcTxUnderflowsThis object describes the count of HDLC Tx underflow
condition.ro Counter .1.3.6.1.4.1.173.7.12.6.1.1.9 |
vismHdlcTxAbortFramesThis object describes the count of HDLC Abort frames
transmitted.ro Counter .1.3.6.1.4.1.173.7.12.6.1.1.10 |
vismHdlcRxAbortFramesThis object describes the count of HDLC Abort frames
received.ro Counter .1.3.6.1.4.1.173.7.12.6.1.1.11 |
vismCodecTemplateCnfGrp OBJECT IDENTIFIER .1.3.6.1.4.1.173.7.12.7 |
vismCodecTemplateCnfGrpTableThis table defines the DSP templates that are applicable on
a card basis. It defines the set of codecs supported in each
template and the maximum number of DS0s supported on the VISM
card for a given template. SEQUENCE OF VismCodecTemplateCnfGrpEntry .1.3.6.1.4.1.173.7.12.7.1 |
vismCodecTemplateCnfGrpEntryAn entry is defined for each set of codecs supported.
The codecs supported are a combination of :
G.711Mu (PCM - Mu-law)
G.711A (PCM - A-law)
G.726/32 (ADPCM)
G.729a (CS-ACELP - Annex A)
G.729ab (CS-ACELP - Annex B)
clearChannel (clear channel voice)
G.723.1-H
G.723.1a-H
G.723.1-L
G.723.1a-L VismCodecTemplateCnfGrpEntry .1.3.6.1.4.1.173.7.12.7.1.1 |
vismCodecTemplateNumThis attribute defines the index for the CodecTemplate
table. Template number is input at the time of configuring
a template using 'cnftemp' CLI command.ro INTEGER .1.3.6.1.4.1.173.7.12.7.1.1.1 |
vismCodecSupportedThis attribute represents a bit map of Codecs supported
in this template.
Bit 0 - represents the G.711 Mu-law codec.
Bit 1 - represents the G.711 A-law codec.
Bit 2 - represents the G.726 at rate 32 kbps.
Bit 3 - represents the G.729a codec.
Bit 4 - represents the G.729ab codec.
Bit 5 - represents clear channel.
Bit 6 - represents the G.726 at rate 16 kbps
Bit 7 - represents the G.726 at rate 24 kbps
Bit 8 - represents the G.726 at rate 40 kbps
Bit 9 - Internal use (T.38)
Bit 10 - represents the G.723.1-H codec.
Bit 11 - represents the G.723.1a-H codec.
Bit 12 - represents the G.723.1-L codec.
Bit 13 - represents the G.723.1a-L codec.
The remaining bits will be defined in future when other
types of codecs are supported.ro INTEGER .1.3.6.1.4.1.173.7.12.7.1.1.2 |
vismCodecTemplateMaxChanCountThe max. number of channels supported for this template.
Based on the codec that is of the maximum complexity, the
maximum no. of channels that can be supported with a given
set of codecs is determined and stored in this variable.ro INTEGER .1.3.6.1.4.1.173.7.12.7.1.1.3 |
vismCasGrp OBJECT IDENTIFIER .1.3.6.1.4.1.173.7.12.8 |
vismCasVariantTableThis table contains configuration information about
different CAS variants. SEQUENCE OF VismCasVariantEntry .1.3.6.1.4.1.173.7.12.8.1 |
vismCasVariantEntryAn entry in the vismCasVariantTable. Each entry consists
of configuration information for a specific CAS variant.
An entry may be created by specifying vismCasVariantName,
and vismCasFileName. Upon the creation of the table entry,
the file specified by vismCasFileName will be downloaded
and the CAS finite state machine will be initialized based
on the information contained in this file. VismCasVariantEntry .1.3.6.1.4.1.173.7.12.8.1.1 |
vismCasVariantNameThis object is a string identifier for the CAS variant.
It is used as index to the table.
The maximum length allowed is 64 bytes.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.173.7.12.8.1.1.1 |
vismCasFileNameThis object gives the name of the file which contains the signal
definition and the Finite State Machine definition for the CAS
variant. The name is supplied during the creation of the table entry.
Modifying the value of this object is not allowed.
Upon the creation of the table entry, the file will be downloaded
from a tftp server configured in the vismTftpServerDn object
and the CAS finite state machine will be initialized
based on the information contained in this file.
This object must be provided in order to create en entry in this table.rw DisplayString .1.3.6.1.4.1.173.7.12.8.1.1.2 |
vismCasTRingingThis object gives the ringing time in seconds for the Cas
Variant. The ringing will be on until this timer expires or
until an off hook is received.rwdeprecated INTEGER .1.3.6.1.4.1.173.7.12.8.1.1.3 |
vismCasDigitMethodThe default digit method to be used for digit collection.
If the digit method can not be derived from the digit map
specified by the call agent in the XGCP message, this digit
method will be used.rw Enumeration .1.3.6.1.4.1.173.7.12.8.1.1.4 |
vismCasInterdigitTpartThis object represents the partial dial timing in
seconds and is used along with a digit map as the
inter-digit timer.
The timer is not started untill the first digit is
entered, and the timer is restarted after each new
digit is entered untill either a digit map match or
mismatch occurs.rw INTEGER .1.3.6.1.4.1.173.7.12.8.1.1.5 |
vismCasInterdigitTcritThis object represents the critical timing in seconds.
If used along with a digit map, the timer is started when
the last digit is received. i.e and when no more digits
are required for a digit map match. After this timer
expires, the digit map match is assumed to be complete.
If used without a digit map, the timer is started
immediately and cancelled (but not restarted) as soon
as a digit is entered.rw INTEGER .1.3.6.1.4.1.173.7.12.8.1.1.6 |
vismCasInterdigitTMFThis object represents the interdigit timeout value for MF
digits. The timeout value is in seconds.rw INTEGER .1.3.6.1.4.1.173.7.12.8.1.1.7 |
vismCasVariantStateThis variable indicates the configuration status of the
CAS variant. When the table entry is created, downloading
of the file will be initiated and the state will be set to
configInProgress. Once the file is successfully downloaded
and the CAS finite state machine successfully initialized,
the state will be set to configured. If the initialization
fails, the state will be set to notConfigured.ro Enumeration .1.3.6.1.4.1.173.7.12.8.1.1.8 |
vismCasRowStatusThis variable allows to add, delete or modify the entry for
a CAS variant.
createAndGo: Use this to add an entry in this table, provided the
vismCasVariantName and vismCasFileName MIB objects are
available to be set.
active: This values is returned, once the row is created
destroy: Use this to delete an entry from this table.rw Enumeration .1.3.6.1.4.1.173.7.12.8.1.1.9 |
vismCasCountryCodeRepresents a case-insensitive 2-letter country code
taken from ISO-3166.rwdeprecated DisplayString .1.3.6.1.4.1.173.7.12.8.1.1.10 |
vismCasVariantSourceThis object specifies where the file defining this CAS variant
resides.
1. Unspecified. This value indicates that the location of the file is not
specified here. In this case, the location is determined
based on whether the TFTP server domain is defined on
VISM. The file is built into the firmware if no tftp
domain is defined on VISM and resides on the TFTP server
if a TFTP domain is defined on VISM.
2. Internal. Indicates that the file is built into the firmware.
3. External. Indicates that the file resides on the TFTP server
configured on VISM.rw Enumeration .1.3.6.1.4.1.173.7.12.8.1.1.11 |
vismCasXgcpVariantTableAn entry in this table is implicitly created/deleted
when an entry in vismCasVariantTable is created/deleted in
switching mode . SEQUENCE OF VismCasXgcpVariantEntry .1.3.6.1.4.1.173.7.12.8.2 |
vismCasXgcpVariantEntryAn entry in the vismCasXgcpVariantTable. VismCasXgcpVariantEntry .1.3.6.1.4.1.173.7.12.8.2.1 |
vismCasXgcpVariantNameThis object is a string identifier for the CAS variant.
It is used as index to the table.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.173.7.12.8.2.1.1 |
vismCasXgcpFileNameThis object gives the name of the file which contains the signal
definition and the Finite State Machine definition for the CAS
variant.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.173.7.12.8.2.1.2 |
vismCasXgcpMaxReXmitTimeThis object represents the maximum timeout value in milli seconds,
used for retransmitting unacknowledged XGCP messages at the
Call Agent - CAS/PBX interface. The value of this object
is settable in 10 ms increments.rw INTEGER .1.3.6.1.4.1.173.7.12.8.2.1.3 |
vismCasXgcpInitialReXmitTimeThis object represents the initial timeout value in milli seconds,
used for retransmitting unacknowledged XGCP messages at the
Call Agent - CAS/PBX interface. The value of this object
is settable in 10 ms increments.rw INTEGER .1.3.6.1.4.1.173.7.12.8.2.1.4 |
vismCasXgcpMaxRetriesThis object specifies the number of retries for a
message that exceeds vismCasXgcpMaxReXmitTime or
vismCasXgcpInitialReXmitTime.rw INTEGER .1.3.6.1.4.1.173.7.12.8.2.1.5 |
bearerConnGrp OBJECT IDENTIFIER .1.3.6.1.4.1.173.7.12.9 |
bearerConnTableThis table describes the statistical information available
on a per-bearer connection basis. These values are applicable
equally to an endpoint. However, a separate table has been
maintained instead of extending the endpoint table because
the endpoint table is the standards-based MgMib. SEQUENCE OF BearerConnEntry .1.3.6.1.4.1.173.7.12.9.1 |
bearerConnEntryEach entry in this table corresponds to a bearer connection,
that was setup by binding an endpoint with VC/CID pair, either
through CLI or SNMP. The statistical counters in this table
are generic voice quality parameters that are equally applicable
in all types of Voice Over Packet adapations (VoIP, VoAAL1 and
VoAAL2). However, they are maintained only in the PVC (trunking)
model because, these counters get reset in the switching model
on a per call basis.
The entries in this table are implicitly created/deleted at the
time of creation/deletion of entries in the Aal2Cid table. BearerConnEntry .1.3.6.1.4.1.173.7.12.9.1.1 |
bearerEndptNumThis attribute defines the index for the bearer connection Table.
This refers to the same value as the index to the mgEndpoint Table
ie. mgEndpointNumberro INTEGER .1.3.6.1.4.1.173.7.12.9.1.1.1 |
bearerCidThis attribute defines the CID (Channel ID associated with this
bearer connection.This refers to the same value as
vismAal2CidNum in the vismAal2CidCnfTable.ro INTEGER .1.3.6.1.4.1.173.7.12.9.1.1.2 |
bearerLcnThis attribute defines the PVC or LCN number to which this bearer
connection is associated with.
This refers to the same value as in vismChanNum in vismChanCnfGrp
table.ro INTEGER .1.3.6.1.4.1.173.7.12.9.1.1.3 |
bearerSentPktsThis attribute defines the count of packets sent towards the network
since setup.ro Counter .1.3.6.1.4.1.173.7.12.9.1.1.4 |
bearerRcvdPktsThis attribute defines the count of packets received from the
network since setup.ro Counter .1.3.6.1.4.1.173.7.12.9.1.1.5 |
bearerSentOctetsThis attribute defines the count of bytes sent towards the network
since this connection setup.ro Counter .1.3.6.1.4.1.173.7.12.9.1.1.6 |
bearerRcvdOctetsThis attribute defines the count of bytes received from the network
since this connection setup.ro Counter .1.3.6.1.4.1.173.7.12.9.1.1.7 |
bearerLostPktsThis attribute defines the count of packets lost in the egress
direction (from the network). This is a computed number based on the
expected number of packets and the actual number of packets arrived
from the network.
Currently this object is not used.ro Counter .1.3.6.1.4.1.173.7.12.9.1.1.8 |
bearerJitterThis attribute defines the jitter (a.k.a interarrival jitter)
This value is determined by the DSP and obtained by the HOST processor
upon querying the DSP on a periodic basis. This value is expressed
in units of milliseconds.
Currently this object is not used.ro INTEGER .1.3.6.1.4.1.173.7.12.9.1.1.9 |
bearerLatencyThis attribute defines the latency (a.k.a end-to-end average
transmission delay for a voice packet. This value is expressed
in units of milliseconds.
Currently this object is not used.ro INTEGER .1.3.6.1.4.1.173.7.12.9.1.1.10 |
bearerAal2ExtAISCntsThis object contains the number of external AIS aal2 Type3 packets
received.
External AIS - is a Alarm Indication Signal associated with a maintenance
alarm detected on a defective maintenance span, that is transmitted in
the direction of the defect as a substitute for normal signal. The purpose
is to show the downstream entities that a defect has been identified
and to prevent other maintenance alrams consequent to this first defect.
External AIS bit stream is represented by an all 1's signal.
Ref - ITU-T Rec. M.20 sec. 5.4.2 aro Counter .1.3.6.1.4.1.173.7.12.9.1.1.11 |
bearerAal2ExtRAICntsThis object contains the number of external RAI aal2 Type3 packets
received.
External RAI - is a Remote Alarm Indication signal that is transmitted
upstream from an entity that has detected defects persisting long enough
to constitute a received signal failure. Its purpose is to report in
the backward direction that there is an interruption of service in the
forward direction.
Ref - ITU-T Rec. G.704 section 2.1.3.1.3ro Counter .1.3.6.1.4.1.173.7.12.9.1.1.12 |
bearerAal2ConnAISCntsThis object contains the number of external Conn AIS aal2 Type2 packets
received.
External Conn AIS - is a Alarm Indicating Signal transmitted in the
downstream direction from the AAL type 2 connecting point that first
detects a defect affecting the AAL type 2 connection; this includes
defects indicated by lower layers.
Ref - ITU-T Rec. I.610 sec 6.2.2.1.1.1ro Counter .1.3.6.1.4.1.173.7.12.9.1.1.13 |
bearerAal2ConnRDICntsThis object contains the number of external Conn RDI (Remote Defect Ind.)
aal2 Type2 packets received.
External Conn RDI - is a signal transmitted upstream by an AAl type 2
endpoint that is in an alarm state as the result of having received
an AAL type2 connection AIS or having detected a defect that affects
the AAL type2 connection.ro Counter .1.3.6.1.4.1.173.7.12.9.1.1.14 |
bearerCntClrButtonThis object is used to clear bearerSentPkts, bearerRcvdPkts,
bearerSentOctets, and bearerRcvdOctets.rw Enumeration .1.3.6.1.4.1.173.7.12.9.1.1.15 |
vismSvcGrp OBJECT IDENTIFIER .1.3.6.1.4.1.173.7.12.10 |
vismSvcTxSetupsThis is the number of Setup messages sent to the PXM
from the VISM since VISM reset.ro Counter .1.3.6.1.4.1.173.7.12.10.1 |
vismSvcRxSetupsThis is the number of Setup messages received by the VISM
from the PXM since VISM reset.ro Counter .1.3.6.1.4.1.173.7.12.10.2 |
vismSvcTxCallProcsThis is the number of Call proceeding messages sent to the PXM
from the VISM since VISM reset.ro Counter .1.3.6.1.4.1.173.7.12.10.3 |
vismSvcRxCallProcsThis is the number of Call proceeding messages received by the VISM
from the PXM since VISM reset.ro Counter .1.3.6.1.4.1.173.7.12.10.4 |
vismSvcTxConnsThis is the number of Connect messages sent to the PXM
from the VISM since VISM reset.ro Counter .1.3.6.1.4.1.173.7.12.10.5 |
vismSvcTxConnAcksThis is the number of Connect ack messages sent to the PXM
from the VISM since VISM reset.ro Counter .1.3.6.1.4.1.173.7.12.10.6 |
vismSvcRxConnsThis is the number of Connect messages received by the VISM
from the PXM since VISM reset.ro Counter .1.3.6.1.4.1.173.7.12.10.7 |
vismSvcRxConnAcksThis is the number of Connect ack messages received by the VISM
from the PXM since VISM reset.ro Counter .1.3.6.1.4.1.173.7.12.10.8 |
vismSvcTxReleasesThis is the number of Release messages sent to the PXM
from the VISM since VISM reset.ro Counter .1.3.6.1.4.1.173.7.12.10.9 |
vismSvcTxReleaseComplsThis is the number of Release complete messages sent to the PXM
from the VISM since VISM reset.ro Counter .1.3.6.1.4.1.173.7.12.10.10 |
vismSvcRxReleasesThis is the number of Release messages received by the VISM
from the PXM since VISM reset.ro Counter .1.3.6.1.4.1.173.7.12.10.11 |
vismSvcRxReleaseComplsThis is the number of Release complete messages received by the VISM
from the PXM since VISM reset.ro Counter .1.3.6.1.4.1.173.7.12.10.12 |
vismSvcTxRestartsThis is the number of Restart messages sent to the PXM
from the VISM since VISM reset.ro Counter .1.3.6.1.4.1.173.7.12.10.13 |
vismSvcTxRestartAcksThis is the number of Restart ack messages sent to the PXM
from the VISM since VISM reset.ro Counter .1.3.6.1.4.1.173.7.12.10.14 |
vismSvcRxRestartsThis is the number of Restart messages received by the VISM
from the PXM since VISM reset.ro Counter .1.3.6.1.4.1.173.7.12.10.15 |
vismSvcRxRestartAcksThis is the number of Restart ack messages received by the VISM
from the PXM since VISM reset.ro Counter .1.3.6.1.4.1.173.7.12.10.16 |
vismSvcTxResyncStrtsThis is the number of Resync start messages sent to the PXM
from the VISM since VISM reset.ro Counter .1.3.6.1.4.1.173.7.12.10.17 |
vismSvcTxResyncStrtAcksThis is the number of Resync start ack messages sent to the PXM
from the VISM since VISM reset.ro Counter .1.3.6.1.4.1.173.7.12.10.18 |
vismSvcRxResyncStrtsThis is the number of Resync start messages received by the VISM
from the PXM since VISM reset.ro Counter .1.3.6.1.4.1.173.7.12.10.19 |
vismSvcRxResyncStrtAcksThis is the number of Resync start ack messages received by the VISM
from the PXM since VISM reset.ro Counter .1.3.6.1.4.1.173.7.12.10.20 |
vismSvcTxResyncEndsThis is the number of Resync end messages sent to the PXM
from the VISM since VISM reset.ro Counter .1.3.6.1.4.1.173.7.12.10.21 |
vismSvcTxResyncEndAcksThis is the number of Resync end ack messages sent to the PXM
from the VISM since VISM reset.ro Counter .1.3.6.1.4.1.173.7.12.10.22 |
vismSvcRxResyncEndsThis is the number of Resync end messages received by the VISM
from the PXM since VISM reset.ro Counter .1.3.6.1.4.1.173.7.12.10.23 |
vismSvcRxResyncEndAcksThis is the number of Resync end ack messages received by the VISM
from the PXM since VISM reset.ro Counter .1.3.6.1.4.1.173.7.12.10.24 |
vismSvcTxBulkResyncsThis is the number of Bulk resync messages sent to the PXM
from the VISM since VISM reset.ro Counter .1.3.6.1.4.1.173.7.12.10.25 |
vismSvcRxBulkResyncsThis is the number of Bulk resync messages received by the VISM
from the PXM since VISM reset.ro Counter .1.3.6.1.4.1.173.7.12.10.26 |
vismSvcCallProcExpiriesCall proceeding expirationsro Counter .1.3.6.1.4.1.173.7.12.10.27 |
vismSvcReleasExpiriesRelease completion expirationsro Counter .1.3.6.1.4.1.173.7.12.10.28 |
vismSvcConnExpiriesConnect expirationsro Counter .1.3.6.1.4.1.173.7.12.10.29 |
vismSvcConnAckExpiriesConnect ack expirationsro Counter .1.3.6.1.4.1.173.7.12.10.30 |
vismSvcRestartExpiriesRestart expirationsro Counter .1.3.6.1.4.1.173.7.12.10.31 |
vismSvcResyncExpiriesResync expirationsro Counter .1.3.6.1.4.1.173.7.12.10.32 |
vismCodecCnfGrp OBJECT IDENTIFIER .1.3.6.1.4.1.173.7.12.18 |
vismCodecCnfTableThis table contains configuration information about
different codecs and there packetization periods. SEQUENCE OF VismCodecCnfEntry .1.3.6.1.4.1.173.7.12.18.1 |
vismCodecCnfEntryAn entry in the vismCodecCnf table. Each entry consists
of packetization period information for a specific codec.
All the entries in this table are implicitly created when the card
comes up with appropriate default values and the user can modify the
packetization period for a particular codec any point in time. VismCodecCnfEntry .1.3.6.1.4.1.173.7.12.18.1.1 |
vismCodecCnfIndexThis object is a index to this table.
1 represents G.711u
2 represents G.711a
3 represents G.726 at rate 32 kbps
4 represents G.729a
5 represents G.729ab
6 represents clear channel
7 represents G.726 at rate 16 kbps
8 represents G.726 at rate 24 kbps
9 represents G.726 at rate 40 kbps
10 RESERVED
11 represents G.723.1-H at rate 6.4kbps
12 represents G.723.1a-H at rate 6.4kbps with SID
13 represents G.723.1-L at rate 5.3kbps
14 represents G.723.1a-L at rate 5.3kbps with SIDro Enumeration .1.3.6.1.4.1.173.7.12.18.1.1.1 |
vismCodecNameThis object holds the name of the codec
for example index 1 will have G.711u as the codec name
index 2 will have G.711a as the codec name and so on....ro DisplayString .1.3.6.1.4.1.173.7.12.18.1.1.2 |
vismCodecPktPeriodThis object gives the packetization period for a particular codec
in milli secs.
for G.711a allowed values are 10 & 20
for G.711u allowed values are 10 & 20
for G.726 at rate 32 kbps allowed values are 10 ,20 30 & 40
for G.729a allowed values are 10, 20 ,30 & 40
for G.729ab allowed values are 10, 20, 30 & 40
for clear channel allowed values are 10 and 20
for G.723 allowed values are 30 & 60
Default value for G.723 is 30 and for other codecs it is 10.rw Enumeration .1.3.6.1.4.1.173.7.12.18.1.1.3 |
vismCodecPreferenceThis object contains the user configured preference for
each codec. Lower the number, higher the preference of the
codec . Since currently we only have 14 codecs supported, the
allowed range of this object is 0-13.
If the call agent does not specify the preferred codec list
in CRCX request then the codec used will be the one of highest
preference, as configured in this object.
The default preference based on the codec type is
G729ab will have preference 1
G729a will have preference 2
G726 at rate 16 kbps will have preference 3
G726 at rate 24 kbps will have preference 4
G726 at rate 32 kbps will have preference 5
G726 at rate 40 kbps will have preference 6
G.711u will have preference 7 for T1 and will have
preference 8 for E1
G.711a will have preference 7 for E1 card and will
have preference 8 for T1
clearChannel will have preference 9
G723H will have preference 10
G723AH will have preference 11
G723L will have preference 12
G723AL will have preference 13
This object is not applicable in releases earlier than VISM2.0.1.
If the preference of a codec is zero then that codec will not
be used.rw INTEGER .1.3.6.1.4.1.173.7.12.18.1.1.4 |
vismCodecStringThe local connection option or SDP descriptor string that vism
would get from the call agent for the codec to be used will be
in the form of PCMU, PCMA, G726 at rate 32 kbps, G729a, CCD .....
where in PCMU stands for G711u
PCMA stands for G711a
and CCD stands for clear channel
This object serves as a mapping string, and the vism will use the
value configured in this object to match the SDP
descriptor string obtained for a codec in a CRCX
or MDCX message.
Since the entries in this table are implicitly created
by default the entry with codec =
G.711u will have a value of PCMU
G.711a will have a value of PCMA
clear channel will have a value of CCD
G.726 at rate 32 kbps will have G726 at rate 32 kbps
G.726 at rate 16 kbps will have G726 at rate 16 kbps
G.726 at rate 24 kbps will have G726 at rate 24 kbps
G.726 at rate 40 kbps will have G726 at rate 40 kbps
G.729a will have G729a
G.729ab will have G729ab
G.723.1-H will have G723H
G.723.1a-H will have G723AH
G.723.1-L will have G723L
G.723.1a-L will have G723ALrw DisplayString .1.3.6.1.4.1.173.7.12.18.1.1.5 |
vismCodecIanaTypeThe codecs are assigned types (numbers) by IANA.
This object will contain such a number. In future we may have
more numbers.
currently by default we have PCMU = 0
G.726 at rate 32 kbps = 2
PCMA = 8
and the rest codecs will have 96
If in a SDP string we would just receive an IANA type number and
not the codec string, then vism would use the value in
this object to derive the actual codec to be used in the bearer
path.
The valid Iana type numbers currently defined are from (0 .. 95)
So if an entry has a value of 96 that means it is not a registered
codec.In that case the actual codec will be determined by the
vism using the rtpmap in SDP string.rw INTEGER .1.3.6.1.4.1.173.7.12.18.1.1.6 |
vismSvcCnfGroups OBJECT IDENTIFIER .1.3.6.1.4.1.173.7.12.19 |
vismSvcAtmQosGrp OBJECT IDENTIFIER .1.3.6.1.4.1.173.7.12.19.1 |
vismSvcAtmQosCdvEnd-to-end cell delay variation used in voice SVC establishment.
It is used to guarantee the quality of the route selected for
a voice SVC. It is applicable to both AAL1 and AAL2 SVC connection
establishment. The value specified to this object is in
'micro-seconds'. This value is sent in voice SVC setup messages
in extended quality of services information element as the
objective value.rw INTEGER .1.3.6.1.4.1.173.7.12.19.1.1 |
vismSvcAtmQosCtdEnd-to-end maximum cell transfer delay used in voice SVC
establishment. It is used to guarantee the quality of the route
selected for a voice SVC. It is applicable to both AAL1 and AAL2
SVC connection establishment. The value specified to this object
is in 'micro-seconds'. This value is sent in voice SVC setup
messages in end-to-end transit delay information element as
the objective value.rw INTEGER .1.3.6.1.4.1.173.7.12.19.1.2 |
vismSvcAtmQosClrMaximum Cell Loss Ratio used in voice SVC establishment.
It is used to guarantee the quality of the route selected for
a voice SVC. It is applicable to both AAL1 and AAL2 SVC connection
establishment. This value is sent in voice SVC setup messages in
extended quality of services information element as maximum cell
loss ratio value.rw INTEGER .1.3.6.1.4.1.173.7.12.19.1.3 |
vismSvcTrfScalingGrp OBJECT IDENTIFIER .1.3.6.1.4.1.173.7.12.19.2 |
vismSvcTrfScalingFactorTraffic scaling Factor used to compute factored bandwidth which is
used in ATM signaling to establish voice SVC. When this value is
less than 100 it can be referred as a `discount factor' and when
more than 100 referred as an `excess factor'
It is applicable only to VBR SVC connection establishment.
The traffic scaling is not applicable to AAL2 SVC calls that
require G.711 and clear channel codecsrw INTEGER .1.3.6.1.4.1.173.7.12.19.2.1 |
vismSvcAal2CidGrp OBJECT IDENTIFIER .1.3.6.1.4.1.173.7.12.19.3 |
vismSvcAal2CidNumberThe default AAL2 Channel IDentification (CID) number
used for AAL2 SVC connections.rw INTEGER .1.3.6.1.4.1.173.7.12.19.3.1 |
vismCardCacFailuresGrp OBJECT IDENTIFIER .1.3.6.1.4.1.173.7.12.20 |
vismPortCacPvcAddFailuresTotal number of attempts to add or modify a PVC to VISM virtual port
that were rejected by port level connection admission control.ro Counter .1.3.6.1.4.1.173.7.12.20.1 |
vismPortCacSvcAddFailuresTotal number of attempts to add a SVC to VISM virtual port
that were rejected by port level connection admission control.ro Counter .1.3.6.1.4.1.173.7.12.20.2 |
vismVcCacPvcFailuresTotal number of attempts to admit voice connections over bearer PVC
connections that were rejected by voice connection admission control.
It is sum of all voice connection admission control failures
for all VISM bearer PVC connections.ro Counter .1.3.6.1.4.1.173.7.12.20.3 |
vismVcCacPvcUpspeedFailuresTotal number of attempts to upspeed voice connections over bearer PVC
connections that were rejected by Port Level Connection Admission
Control.ro Counter .1.3.6.1.4.1.173.7.12.20.4 |
vismPortCacSvcUpspeedFailuresTotal number of attempts to upspeed voice connections over bearer SVC
connections that were rejected by Port Level Connection Admission
Control.ro Counter .1.3.6.1.4.1.173.7.12.20.5 |
parSelfNode OBJECT IDENTIFIER .1.3.6.1.4.1.318.1.2.2.1.1 |
parSnNodeIdThis object specifies the node number of the node. When the network manager tries to modify the value of this object, a message is sent node state machine which propagates this information and the value gets modified only if the new node number is successfully propagated. The node number uniquely identifies a routing node in a network.rw INTEGER .1.3.6.1.4.1.318.1.2.2.1.1.1 |
parSnNodeIPThis object specifies the IP address for routing node and is used
for communication with SV+.rw IpAddress .1.3.6.1.4.1.318.1.2.2.1.1.2 |
parSnNodeNameThis object specifies the name of the node and is unique among
all the nodes in the network. Whenever the name of the node is
changed, AutoRoute has to propagate the information to the other
nodes in the network. It also specifies the name of a PAR Feeder
node.rw DisplayString .1.3.6.1.4.1.318.1.2.2.1.1.3 |
parSnRevisionThis object specifies the primary revision of the PAR running
on the node.
Format: cc.c.cc
Where: c = one ascii characterro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.318.1.2.2.1.1.4 |
parSnNodeAlarmStatusThis object specifies the type of alarm on the node.
If there is no alarm the value of this object is none(1).
If there is a minor alarm the value of this object is min(2)
If there is a major alarm the value of this object is maj(3).
If the node is unreachable the value of this object is unreach(4).ro Enumeration .1.3.6.1.4.1.318.1.2.2.1.1.5 |
parSnNumberOfTrunksThis object specifies the number of trunks attached to the node.ro INTEGER .1.3.6.1.4.1.318.1.2.2.1.1.6 |
parInterfaces OBJECT IDENTIFIER .1.3.6.1.4.1.318.1.2.2.1.2 |
parIfTableTable of all logical interfaces supported by PAR SEQUENCE OF ParIfEntry .1.3.6.1.4.1.318.1.2.2.1.2.1 |
parIfEntryEntries for logical interfaces. ParIfEntry .1.3.6.1.4.1.318.1.2.2.1.2.1.1 |
parIfLogicalInterfaceThis object specifies the logical interface number
assigned by Platform Softwarero INTEGER .1.3.6.1.4.1.318.1.2.2.1.2.1.1.1 |
parIfTypeSpecifies the type of interface - uni, nni or clock. uni(1) interface
is for user ports and trunks may be either nni or uni. Default
type of the interface is uni(1) and it can be configured to
nni(2) provided there are no connections on the port.
Type of interface can be changed from nni(2) to uni(1) if the
trunk is not added. clock type interface is one which is used derive the
clock.rw Enumeration .1.3.6.1.4.1.318.1.2.2.1.2.1.1.2 |
parIfOperStatusThis object specifies the operation status of the interface.
For interfaces of type uni(1) the status is either up(1) or
failed(3) as reported by platform.
For interfaces of type nni(2) the status is either of up(1),
added(2), failed(3) or added-failed(4).
Status up(1) indicates that the interface is configured as
trunk but the trunk is not added.
Status failed(3) indicates that the interface is configured as
trunk, the trunk is not added and platform indicates an alarm
on the interface.
Status added(2) indicates that the interface is configured as
trunk and the trunk is added.
Status added-failed(4) indicates that the interface is configured
as trunk, the trunk is added and there is an alarm on the trunk.
This alarm could be generated by PAR or reported by Platform.ro Enumeration .1.3.6.1.4.1.318.1.2.2.1.2.1.1.3 |
parIfTxBwThis object specifies the transmit bandwidth for the interface
in units of cells per second.ro INTEGER .1.3.6.1.4.1.318.1.2.2.1.2.1.1.4 |
parIfRxBwThis object specifies the receive bandwidth for the interface
in units of cells per second.ro INTEGER .1.3.6.1.4.1.318.1.2.2.1.2.1.1.5 |
parIfMaxConnThis object specifies the maximum number of connections that
can be configured over the interface.ro INTEGER .1.3.6.1.4.1.318.1.2.2.1.2.1.1.6 |
parIfHiAddrMinThis object specifies the minimum VPI that PAR can use for
configuring connection in the interface.ro INTEGER .1.3.6.1.4.1.318.1.2.2.1.2.1.1.7 |
parIfHiAddrMaxThis object specifies the maximum VPI that PAR can use for
configuring connection in the interface.ro INTEGER .1.3.6.1.4.1.318.1.2.2.1.2.1.1.8 |
parIfLoAddrMinThis object specifies the minimum VCI that PAR can use for
configuring connection in the interface.ro INTEGER .1.3.6.1.4.1.318.1.2.2.1.2.1.1.9 |
parIfLoAddrMaxThis object specifies the maximum VCI that PAR can use for
configuring connection in the interface.ro INTEGER .1.3.6.1.4.1.318.1.2.2.1.2.1.1.10 |
parTrkTableTrunk parameters SEQUENCE OF ParTrkEntry .1.3.6.1.4.1.318.1.2.2.1.2.2 |
parTrkEntryEntries for logical interfaces configured as trunks (parIfType nni). ParTrkEntry .1.3.6.1.4.1.318.1.2.2.1.2.2.1 |
parTrkIdThis object specifies the logical trunk number associated
with the trunk at the local node.ro INTEGER .1.3.6.1.4.1.318.1.2.2.1.2.2.1.1 |
parTrkStatReserveSpecifies the bandwidth reserved as Statistical Reserve on
the trunk in units of cells per second.
This object cannot take a value beyond the bandwidth capacity
of the trunk.rw INTEGER .1.3.6.1.4.1.318.1.2.2.1.2.2.1.2 |
parTrkCnfgCcRestrictThis object specifies the operators preference for routing
control plane traffic on the interface.
If the object is set to False, then the interface may be chosen
for control plane traffic. If it is True, then the interface is
not chosen, unless there is no other trunk with parIfOperStatus
added(2), in which case it is chosen regardless of the value of
this object.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.318.1.2.2.1.2.2.1.3 |
parTrkCnfgLineTypeThis object specifies the type of interface terrestrial
or satellite. The interfaces configured as terrestrial(1)
are preferred over those configured as satellite(2) for
routing control plane traffic.
This information is also used for connections for which
routing restrictions are specified.rw Enumeration .1.3.6.1.4.1.318.1.2.2.1.2.2.1.4 |
parTrkCnfgPassSyncThis object specifies whether the trunk can be used to pass
clock sync.
If the value of this object is True, clock can be synchronized
through the trunk; otherwise not.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.318.1.2.2.1.2.2.1.5 |
parTrkCnfgDerouteDelayThis object specifies the value of deroute delay timer in seconds.rw INTEGER .1.3.6.1.4.1.318.1.2.2.1.2.2.1.6 |
parTrkCnfgTrafficClassFstThis object indicates whether Foresight traffic can be routed
over the trunk. If the value is True it can be rerouted otherwise
not.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.318.1.2.2.1.2.2.1.7 |
parTrkCnfgTrafficClassFrThis object indicates whether Frame Relay traffic can be
routed over the trunk. If the value is True it can be rerouted
otherwise not.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.318.1.2.2.1.2.2.1.8 |
parTrkCnfgTrafficClassNtsThis object indicates whether Non-Time Stamped traffic can
be routed over the trunk. If the value is True it can be
rerouted otherwise not.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.318.1.2.2.1.2.2.1.9 |
parTrkCnfgTrafficClassTsThis object indicates whether Time Stamped traffic can be
routed over the trunk. If the value is True it can be rerouted
otherwise not.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.318.1.2.2.1.2.2.1.10 |
parTrkCnfgTrafficClassVoiceThis object indicates whether Voice traffic can be routed
over the trunk. If the value is True it can be rerouted
otherwise not.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.318.1.2.2.1.2.2.1.11 |
parTrkCnfgTrafficClassCbrThis object indicates whether Constant Bit Rate traffic can
be routed over the trunk. If the value is True it can be
rerouted otherwise not.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.318.1.2.2.1.2.2.1.12 |
parTrkCnfgTrafficClassVbrThis object indicates whether Variable Bit Rate traffic can
be routed over the trunk. If the value is True it can be
rerouted otherwise not.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.318.1.2.2.1.2.2.1.13 |
parTrkCnfgTrafficClassAbrThis object indicates whether Available Bit Rate traffic
can be routed over the trunk. If the value is True it can
be rerouted otherwise not.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.318.1.2.2.1.2.2.1.14 |
parTrkCnfgAdminStatusThis object can be used to add or delete the trunk. The value
of this object can be set to add(1) only if the parIfOperStatus
is up. The value can be set to delete if parIfOperStatus is
added or added-failedrw Enumeration .1.3.6.1.4.1.318.1.2.2.1.2.2.1.15 |
parTrkCnfgRoutingCostThis object specifies the cost associated with the trunk
for the purpose of routing the connections. This object has
significance if cost based routing feature is enabled.
(parCmParmsCostBased)rw INTEGER .1.3.6.1.4.1.318.1.2.2.1.2.2.1.16 |
parTrkCnfgVccConidsThe max number of routing resource available on the trunk for
VCC connections.rw INTEGER .1.3.6.1.4.1.318.1.2.2.1.2.2.1.17 |
parTrkCnfgVpcConidsThe max number of routing resource available on the trunk for
VPC connectionsrw INTEGER .1.3.6.1.4.1.318.1.2.2.1.2.2.1.18 |
parTrkLocalSlotNumberThis object specifies the slot number of the interface card
associated with the trunk at the local node.ro INTEGER .1.3.6.1.4.1.318.1.2.2.1.2.2.1.19 |
parTrkLocalPortNumberThis object specifies the port number of the interface card
associated with the trunk at the local node.ro INTEGER .1.3.6.1.4.1.318.1.2.2.1.2.2.1.20 |
parTrkLocalVTrunkIdThis object specifies the Virtual trunk of the interface card
associated with the trunk at the local node. The value of this
object is between 1 and 254, inclusive for a virtual trunk and
255 for a physical trunk.ro INTEGER .1.3.6.1.4.1.318.1.2.2.1.2.2.1.21 |
parTrkRemoteNodeIdThis object specifies the node number of the node attached to
the remote end of the trunk.ro INTEGER .1.3.6.1.4.1.318.1.2.2.1.2.2.1.22 |
parTrkRemoteTrunkIdThis object specifies the logical trunk number at the node on
the remote end of the trunk.ro INTEGER .1.3.6.1.4.1.318.1.2.2.1.2.2.1.23 |
parTrkRemoteSlotNumberThis object specifies the slot number of the interface card
to which the trunk is attached on the remote node.ro INTEGER .1.3.6.1.4.1.318.1.2.2.1.2.2.1.24 |
parTrkRemotePortNumberThis object specifies the port number of the interface card
to which the trunk is attached on the remote node.ro INTEGER .1.3.6.1.4.1.318.1.2.2.1.2.2.1.25 |
parTrkRemoteVTrunkIdThis object specifies the Virtual trunk of the interface card
associated with the trunk at the remote node. The value of this
object is between 1 and 254, inclusive for a virtual trunk and
255 for a physical trunk.ro INTEGER .1.3.6.1.4.1.318.1.2.2.1.2.2.1.26 |
parTrkRemoteNodeIPThis object specifies the IP address for the
Remote node, used for communication with NMSro IpAddress .1.3.6.1.4.1.318.1.2.2.1.2.2.1.27 |
parTrkRemoteNodeTypeSpecifies the type of the node.ro Enumeration .1.3.6.1.4.1.318.1.2.2.1.2.2.1.28 |
parTrkRemoteNodeNameThis object specifies the name of the remote node and is unique
among all the nodes in the network.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.318.1.2.2.1.2.2.1.29 |
parTrkAlarmStatusThis object specifies the severity of the alarm on the trunk.
If there is no alarm the value of this object is none(1).
If there is a minor alarm the value of this object is min(2).
If there is a major alarm on the trunk the value of this object
is maj(3).ro Enumeration .1.3.6.1.4.1.318.1.2.2.1.2.2.1.30 |
parTrkAlarmTypeThis object specifies the type of alarm on the trunk. The value
of this object has no significance if parTrunkAlarmStatus
indicates no alarm.
resources unavailable (1) indicates that the platform has not
provided the resources required to make this interface into
a trunk.
communication failure (2) indicates that message exchange
between neighboring nodes on this trunk has failed.
unknown (3) indicates that the alarm type is unknown to PAR,
for example if the platform has declared the interface in alarm
due to some physical problem with the interface.ro Enumeration .1.3.6.1.4.1.318.1.2.2.1.2.2.1.31 |
parTrkBwCapacitySpecifies the bandwidth capacity of the trunk.ro INTEGER .1.3.6.1.4.1.318.1.2.2.1.2.2.1.32 |
parTrkLineLoadSpecifies the bandwidth used by the connections routed over the trunk.ro INTEGER .1.3.6.1.4.1.318.1.2.2.1.2.2.1.33 |
parTrkLoadTableTrunk Load Information SEQUENCE OF ParTrkLoadEntry .1.3.6.1.4.1.318.1.2.2.1.2.3 |
parTrkLoadEntryLoad info for logical interfaces configured as trunks (parIfType nni). ParTrkLoadEntry .1.3.6.1.4.1.318.1.2.2.1.2.3.1 |
parTrkLoadXmtUsedCbrThis object specifies the used bandwidth in the transmit
direction for CBR traffic.ro INTEGER .1.3.6.1.4.1.318.1.2.2.1.2.3.1.1 |
parTrkLoadRcvUsedCbrThis object specifies the used bandwidth in the receive
direction for CBR trafficro INTEGER .1.3.6.1.4.1.318.1.2.2.1.2.3.1.2 |
parTrkLoadXmtUsedVbrThis object specifies the used bandwidth in the transmit
direction for VBR.ro INTEGER .1.3.6.1.4.1.318.1.2.2.1.2.3.1.3 |
parTrkLoadRcvUsedVbrThis object specifies the used bandwidth in the receive
direction for VBR.ro INTEGER .1.3.6.1.4.1.318.1.2.2.1.2.3.1.4 |
parTrkLoadXmtUsedAbrThis object specifies the used bandwidth in the transmit
direction for ABR.ro INTEGER .1.3.6.1.4.1.318.1.2.2.1.2.3.1.5 |
parTrkLoadRcvUsedAbrThis object specifies the used bandwidth in the receive
direction for ABR.ro INTEGER .1.3.6.1.4.1.318.1.2.2.1.2.3.1.6 |
parTrkLoadXmtUsedNtsThis object specifies the used bandwidth in the transmit
direction for Non-Time Stamped.ro INTEGER .1.3.6.1.4.1.318.1.2.2.1.2.3.1.7 |
parTrkLoadRcvUsedNtsThis object specifies the used bandwidth in the receive
direction for Non-Time Stamped.ro INTEGER .1.3.6.1.4.1.318.1.2.2.1.2.3.1.8 |
parTrkLoadXmtUsedTsThis object specifies the used bandwidth in the transmit
direction for Time-Stamped.ro INTEGER .1.3.6.1.4.1.318.1.2.2.1.2.3.1.9 |
parTrkLoadRcvUsedTsThis object specifies the used bandwidth in the receive
direction for Time-Stamped.ro INTEGER .1.3.6.1.4.1.318.1.2.2.1.2.3.1.10 |
parTrkLoadXmtUsedVoiceThis object specifies the used bandwidth in the transmit
direction for Voice.ro INTEGER .1.3.6.1.4.1.318.1.2.2.1.2.3.1.11 |
parTrkLoadRcvUsedVoiceThis object specifies the used bandwidth in the receive
direction for Voice.ro INTEGER .1.3.6.1.4.1.318.1.2.2.1.2.3.1.12 |
parTrkLoadXmtUsedBdataAThis object specifies the used bandwidth in the
transmit direction for Busty Data A.ro INTEGER .1.3.6.1.4.1.318.1.2.2.1.2.3.1.13 |
parTrkLoadRcvUsedBdataAThis object specifies the used bandwidth in the
receive direction for Bursty Data A.ro INTEGER .1.3.6.1.4.1.318.1.2.2.1.2.3.1.14 |
parTrkLoadXmtUsedBdataBThis object specifies the used bandwidth in the transmit
direction for Bursty Data B.ro INTEGER .1.3.6.1.4.1.318.1.2.2.1.2.3.1.15 |
parTrkLoadRcvUsedBdataBThis object specifies the used bandwidth in the receive
direction for Bursty Data B.ro INTEGER .1.3.6.1.4.1.318.1.2.2.1.2.3.1.16 |
parTrkLoadVccConidsUsedThis object specifies the number of conids used for VCCs
(not used) on the trunk.ro INTEGER .1.3.6.1.4.1.318.1.2.2.1.2.3.1.17 |
parTrkLoadVpcConidsUsedThis object specifies the number of conids Used for VPCs
(not used) on the trunk.ro INTEGER .1.3.6.1.4.1.318.1.2.2.1.2.3.1.19 |
parConnection OBJECT IDENTIFIER .1.3.6.1.4.1.318.1.2.2.1.3 |
parConnectionTableConnections Mastered or slaved by the node. SEQUENCE OF ParConnectionEntry .1.3.6.1.4.1.318.1.2.2.1.3.1 |
parConnectionEntryEntries for connections mastered or slaved by the node. ParConnectionEntry .1.3.6.1.4.1.318.1.2.2.1.3.1.1 |
parConnLocalSlotThis object specifies the slot number part of the local
endpoint connection address.ro INTEGER .1.3.6.1.4.1.318.1.2.2.1.3.1.1.1 |
parConnLocalPortThis object specifies the port number part of the local
endpoint connection address.ro INTEGER .1.3.6.1.4.1.318.1.2.2.1.3.1.1.2 |
parConnLocalVpiThis object specifies the Virtual Path Identifier part of
the local endpoint connection address.ro INTEGER .1.3.6.1.4.1.318.1.2.2.1.3.1.1.3 |
parConnLocalVciThis object specifies the Virtual Channel Identifier part
of the local endpoint connection address.ro INTEGER .1.3.6.1.4.1.318.1.2.2.1.3.1.1.4 |
parConnMasterShipThis object specifies whether this end of the connection is the master
or the slave of the connection.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.318.1.2.2.1.3.1.1.5 |
parConnLocalVcIndxThis object specifies the Virtual Connection Index at this
node. It is used by Network Management to correlate this end
of the connection with the remote end.ro INTEGER .1.3.6.1.4.1.318.1.2.2.1.3.1.1.6 |
parConnLocalEndptThis object specifies the actual physical connection endpoint
at the local node.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.318.1.2.2.1.3.1.1.7 |
parConnRemoteNodeNameThis object specifies the node name of the remote endpoint.
For a intra-switch connection or feeder connection this object
would specify the self node name.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.318.1.2.2.1.3.1.1.8 |
parConnRemoteSlotThis object specifies the slot number part of the remote
endpoint connection address.ro INTEGER .1.3.6.1.4.1.318.1.2.2.1.3.1.1.9 |
parConnRemotePortThis object specifies the port number part of the remote
endpoint connection address.ro INTEGER .1.3.6.1.4.1.318.1.2.2.1.3.1.1.10 |
parConnRemoteVpiThis object specifies the VPI part of the remote endpoint
connection address.ro INTEGER .1.3.6.1.4.1.318.1.2.2.1.3.1.1.11 |
parConnRemoteVciThis object specifies the VCI part of the remote endpoint
connection address.ro INTEGER .1.3.6.1.4.1.318.1.2.2.1.3.1.1.12 |
parConnRemoteVcIndxThis object specifies the Virtual Connection Index at the
remote node. It is used by Network Management to correlate
this end of the connection with the remote end..ro INTEGER .1.3.6.1.4.1.318.1.2.2.1.3.1.1.13 |
parConnOperStatusThis object specifies the status of connection as known and
determined by PAR. The status shall be OK if there is an abit
alarm on the connection.ro Enumeration .1.3.6.1.4.1.318.1.2.2.1.3.1.1.14 |
parConnAdminStatusThis object is used by the operator to reroute or down/up
a connection. The value of this object is up when the
connection is created. If the value of the object is set to
down(1) the connection is derouted (if it is routed) and
parConnOperStatus object is set to not routed.
If the value of the object is up (2) and it is set to reroute(3)
the connection is derouted and attempt is made to reroute the
connection. If the value of the object is down (1) and the it
is set to reroute (3), no action is performed and the object's
value does not changes. If the value of object is down(1) and
is set to up(2), an attempt is made to reroute the connection.rw Enumeration .1.3.6.1.4.1.318.1.2.2.1.3.1.1.15 |
parConnRouteThis object specifies the current path on which the connection
is routed. A value of this object is valid only if
parConnOperStatus is routed. Null string specifies that the
connection is not routed.
Format: Nodename {Trk
Where: Nodename = up to 8 characters, Trk = slot.port.vtrk,
slot = 1 or 2 characters, port = 1 or two characters, and
vtrk = 1 or two characters and is optional. The portion of
the format shown in braces {like this} can be repeated up to
10 times.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.318.1.2.2.1.3.1.1.16 |
parConnRemoteEndptThis object specifies the actual physical connection endpoint at
the remote end of the connection. It shall be known only if the
connection is a local(DAX) connection.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.318.1.2.2.1.3.1.1.17 |
parPrefRouteThis object specifies the preferred path for the connection.
Null string specifies that the connection does not have a
preferred route.
Format: Nodename {Trk
Where: Nodename = up to 8 characters, Trk = slot.port.vtrk,
slot = 1 or 2 characters, port = 1 or two characters, and
vtrk = 1 or two characters and is optional. The portion of
the format shown in braces {like this} can be repeated up to
10 times.rw DisplayString (SNMPv2-TC) .1.3.6.1.4.1.318.1.2.2.1.3.1.1.18 |
parConnFailRsnThis object specifies a reason code for the failure of the connection.ro Enumeration .1.3.6.1.4.1.318.1.2.2.1.3.1.1.19 |
parRrtFailRsnThis object specifies the Reason of failure of a connection
to route.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.318.1.2.2.1.3.1.1.20 |
parConnRstrTypThis object specifies the Route restriction of a connection.
The possible values are no restriction, terrestrial line
restriction or sattelite line restriction.ro Enumeration .1.3.6.1.4.1.318.1.2.2.1.3.1.1.21 |
parConnRstrZcsThis object specifies whether ZCS lines should be avoided
or not. The possible values are no restriction, terrestrial line
restriction or sattelite line restriction.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.318.1.2.2.1.3.1.1.22 |
parConnCosThis object specifies the COS for the connection.ro INTEGER .1.3.6.1.4.1.318.1.2.2.1.3.1.1.23 |
parNetworkClock OBJECT IDENTIFIER .1.3.6.1.4.1.318.1.2.2.1.4 |
parClockTableTable of clock sources available to PAR SEQUENCE OF ParClockEntry .1.3.6.1.4.1.318.1.2.2.1.4.1 |
parClockEntryEach entry represent a clock source iavailable to PAR ParClockEntry .1.3.6.1.4.1.318.1.2.2.1.4.1.1 |
parClockIndexThis clock index is assigned by PAR. This object is used
to index into parClockTablero INTEGER .1.3.6.1.4.1.318.1.2.2.1.4.1.1.1 |
parClockTypeSpecifies the type of clock - Primary, Secondary, Tertiaryrw Enumeration .1.3.6.1.4.1.318.1.2.2.1.4.1.1.2 |
parClockSourceSpecifies source of the clock - Internal, Interface, Externalro Enumeration .1.3.6.1.4.1.318.1.2.2.1.4.1.1.3 |
parClockCurSourceSpecifies whether clock source is a current clock source or not. The
value is true if the cloock source is current and false otherwisero TruthValue (SNMPv2-TC) .1.3.6.1.4.1.318.1.2.2.1.4.1.1.4 |
parClockSourceIdSpecifies identification of the clock - for example - if
clock source is `Interface' then this field will carry
logical interface numberrw INTEGER .1.3.6.1.4.1.318.1.2.2.1.4.1.1.5 |
parClockPathDescribes the path used for clock synchronizationro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.318.1.2.2.1.4.1.1.6 |
parConfigParms OBJECT IDENTIFIER .1.3.6.1.4.1.318.1.2.2.1.5 |
asmAlarmTableThe ASM Alarm table. The table size is
given by the value of ASMNumOfValidEntries. SEQUENCE OF AsmAlarmEntry .1.3.6.1.4.1.351.110.1.2.1 |
asmAlarmEntryAn entry in the Basis ASM Alarm Table. AsmAlarmEntry .1.3.6.1.4.1.351.110.1.2.1.1 |
asmAlarmNumThis object is the identifier of a ASM alarm
entry. The Alarm is further identified by the
objects ASMAlarmType & ASMAlarmUnitNum.ro INTEGER .1.3.6.1.4.1.351.110.1.2.1.1.1 |
asmAlarmTypeThe value for this object indicates the type
of Alarm represented in the entry of ASMAlarmTable
indexed by ASMAlarmNum.ro Enumeration .1.3.6.1.4.1.351.110.1.2.1.1.2 |
asmAlarmUnitNumThis object identifies one unit among a number of
identical units represented in ASMAlarmTable having the
same ASMAlarmType.ro INTEGER .1.3.6.1.4.1.351.110.1.2.1.1.3 |
asmAlarmThresholdThis object specifies the threshold beyond which
the alarmable unit is said to be in an abnormal state.ro INTEGER .1.3.6.1.4.1.351.110.1.2.1.1.4 |
asmAlarmSeverityThis variable specifies the severity of the alarm
to be declared when the ASMAlarmThreshold specified is
exceeded for the entry of ASMAlarmTable indexed by
ASMAlarmNum.ro Enumeration .1.3.6.1.4.1.351.110.1.2.1.1.5 |
asmUnitMeasurableThis object indicates if the alarm unit is measurable
by the AXIS shelf.ro Enumeration .1.3.6.1.4.1.351.110.1.2.1.1.6 |
asmUnitMeasuredValueThis object gives the mesaured value of the entity
addressed by asmAlarmNum if it is measurable.ro INTEGER .1.3.6.1.4.1.351.110.1.2.1.1.7 |
asmPhysicalAlarmStateThis object indicates the status of the ASM alarm
represented in this entry. It is a bitmap where a
set bit indicates an abnormal condition. A reset bit
signifies normal operation.ro INTEGER .1.3.6.1.4.1.351.110.1.2.1.1.8 |
asmClrButtonThis object when set to ASMAlarmClear causes the entry
in the ASMAlarmTable represented by ASMAlarmNum to be
cleared.rw Enumeration .1.3.6.1.4.1.351.110.1.2.1.1.9 |
asmNumOfValidEntriesThe number of valid ASMAlarmTable entries (regardless
of how many are actually configured) in the table.ro INTEGER .1.3.6.1.4.1.351.110.1.2.2 |
asmShelfAlarmStateThis object indicates whether any Shelf Alarm has been
declared in the BASIS system.ro Enumeration .1.3.6.1.4.1.351.110.1.2.3 |
atmNetPrefixGroup OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.1.4.1.1 |
atmNetPrefixTableA table implemented by the UNI Management Entity on the user-side of an
ATM UNI port, containing the network-prefix(es) for ATM-layer addresses
in effect on the user-side of the UNI. SEQUENCE OF AtmNetPrefixEntry .1.3.6.1.4.1.351.110.1.4.1.1.1 |
atmNetPrefixEntryAn entry in the table, containing information about
the ATM Prefix status. AtmNetPrefixEntry .1.3.6.1.4.1.351.110.1.4.1.1.1.1 |
axisAtmNetPrefixPortThe unique value which identifies the ILMI port.ro INTEGER .1.3.6.1.4.1.351.110.1.4.1.1.1.1.1 |
axisAtmNetPrefixPrefixThe network prefix for ATM addresses which is in effect
on the user-side of the ATM UNI port.ro NetPrefix .1.3.6.1.4.1.351.110.1.4.1.1.1.1.2 |
axisAtmNetPrefixAdminStatusAn indication of the validity of the network prefix for ATM addresses,
on the user-side of the UNI port.rw Enumeration .1.3.6.1.4.1.351.110.1.4.1.1.1.1.3 |
axisAtmNetPrefixOperStatusAn indication of the current registration state for the prefix:
registering, de-registering, success, fail.ro Enumeration .1.3.6.1.4.1.351.110.1.4.1.1.1.1.4 |
atmAddressGroup OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.1.4.1.2 |
RFC1155-SMI Unknown .1.3.6.1.4.1.351.110.1.4.1.2 |
atmAddressTableA table implemented by the network-side of an ATM UNI port, containing
the ATM-layer addresses in effect on the user-side of the UNI. SEQUENCE OF AtmAddressEntry .1.3.6.1.4.1.351.110.1.4.1.2.1 |
atmAddressEntryInformation about a single ATM-layer address in effect on the user-side
of a UNI port. AtmAddressEntry .1.3.6.1.4.1.351.110.1.4.1.2.1.1 |
axisAtmAddressPortA unique value which identifies this port. The value of
0 has the special meaning of identifying the local UNI.ro INTEGER .1.3.6.1.4.1.351.110.1.4.1.2.1.1.1 |
axisAtmAddressAtmAddressThe ATM address which is in effect on the user-side of the ATM UNI port.ro AtmAddress .1.3.6.1.4.1.351.110.1.4.1.2.1.1.2 |
axisAtmAddressStatusAn indication of the validity of the ATM address at
the user-side of the UNI port.ro Enumeration .1.3.6.1.4.1.351.110.1.4.1.2.1.1.3 |
commonPort OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.2.6 |
commonPortTableThe common port table is for the common ports. SEQUENCE OF CommonPortTableEntry .1.3.6.1.4.1.351.110.2.6.1 |
commonPortTableEntryAn entry for every common port group. CommonPortTableEntry .1.3.6.1.4.1.351.110.2.6.1.1 |
commonPortNumThis is the index to the port number.ro INTEGER .1.3.6.1.4.1.351.110.2.6.1.1.1 |
commonPortTypeThis is the type of the port.
1 - Frame Relay Port.
2 - ATM Port.
3 - IMA Port.ro Enumeration .1.3.6.1.4.1.351.110.2.6.1.1.2 |
commonPortStatusThis variable enables or disables the port
1 - disable
2 - enablero Enumeration .1.3.6.1.4.1.351.110.2.6.1.1.3 |
commonPortSpeedThis is the speed of the port in cells per second.ro INTEGER .1.3.6.1.4.1.351.110.2.6.1.1.4 |
commonPortAlarmStateThis variable states the alarm status of the port
1 - port in alarm
2 - port out of alarmro Enumeration .1.3.6.1.4.1.351.110.2.6.1.1.5 |
commonPortSignallingProtocolTypeThis variable indicates the signalling protocol type of the port.
This field is TBD. It is unused in IMATM/AUSM.ro Enumeration .1.3.6.1.4.1.351.110.2.6.1.1.6 |
commonPortSignallingStateThis variable indicates the signalling state of the port.ro Enumeration .1.3.6.1.4.1.351.110.2.6.1.1.7 |
commonPortAssocLinesThis variable indicates the list of physical lines in the port
delimited by dots.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.351.110.2.6.1.1.8 |
commonPortAssocChannelsThe variable indicates the list of channels that are used in the
ds1 frame.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.351.110.2.6.1.1.9 |
commonChannel OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.2.7 |
commonChanTableThe common port table is for the common ports. SEQUENCE OF CommonChanTableEntry .1.3.6.1.4.1.351.110.2.7.1 |
commonChanTableEntryAn entry for every common port group. CommonChanTableEntry .1.3.6.1.4.1.351.110.2.7.1.1 |
commonChanNumThis is the index to the channel number.ro INTEGER .1.3.6.1.4.1.351.110.2.7.1.1.1 |
commonConnTypeThis specifies the connection type
1 ==> Virtual Path Connection
2 ==> Virtual Channel Connectionro Enumeration .1.3.6.1.4.1.351.110.2.7.1.1.2 |
commonChanStatusThis variable indicates the state of the VC (channel)(ro Enumeration .1.3.6.1.4.1.351.110.2.7.1.1.3 |
commonAlarmStateThis is the alarm state of the port.ro INTEGER .1.3.6.1.4.1.351.110.2.7.1.1.4 |
commonChanPortNumThis variable indicates the port number associated with the
channelro INTEGER .1.3.6.1.4.1.351.110.2.7.1.1.5 |
commonChanServiceTypeThis specifies the service type
1 ==> Constant Bit Rate
2 ==> Variable Bit Rate
3 ==> Associated Bit Ratero Enumeration .1.3.6.1.4.1.351.110.2.7.1.1.6 |
commonChanIngrXmtStateThis variable indicates the transmit state of the VC (channel)
on the CellBus side (Ingress)ro Enumeration .1.3.6.1.4.1.351.110.2.7.1.1.7 |
commonChanIngrRcvStateThis variable indicates the status of port receive (Ingress)ro Enumeration .1.3.6.1.4.1.351.110.2.7.1.1.8 |
commonChanEgrXmtStateindicates the status of port transmit(Egress)ro Enumeration .1.3.6.1.4.1.351.110.2.7.1.1.9 |
commonChanEgrRcvStateIndicates the receiving state of the VC (channel) on the Cellbus
side (Egress)ro Enumeration .1.3.6.1.4.1.351.110.2.7.1.1.10 |
commonConnParm1Connection paramter 1ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.351.110.2.7.1.1.11 |
commonConnParm2Connection paramter 2ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.351.110.2.7.1.1.12 |
cardResourcePartition OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.2.9 |
cardLcnPartitionTypeThis object specified the type of partition on LCN:
1. noPartition
the totoal (G)LCNs limited by the card
2. controllerBased
available to each controller is
fixed but no reservation on each port.
The number for each controller is
specified in the smCardResPartGrpTable.
3. portControllerBased
(G)LCNs available on each port for each
controller is reserved, it is
specified in the port resouce
partition table.
NOTE: This object has to be configured before adding any
connections and once a connection is added, this object
cannot be changed until all of the connections are
deleted.rw Enumeration .1.3.6.1.4.1.351.110.2.9.1 |
cardResPartGrpTableThis table contains the configuration of all
the resource partition(s) that are on the card level,
such as (G)LCN (if the object cardLcnPartitionType is
configured as controller-based, if not, there is no
need to configure this table since it'll be useless). SEQUENCE OF CardResPartGrpEntry .1.3.6.1.4.1.351.110.2.9.2 |
cardResPartGrpEntryThis is an entry for a controller CardResPartGrpEntry .1.3.6.1.4.1.351.110.2.9.2.1 |
cardResPartCtrlrNumThis object is the index to the tablero Enumeration .1.3.6.1.4.1.351.110.2.9.2.1.1 |
cardResPartRowStatusThis object is records the status of this entryrw Enumeration .1.3.6.1.4.1.351.110.2.9.2.1.2 |
cardResPartNumOfLcnAvailThis object is configured to reserve the number of
(G)LCNs for one controller on a SM card, it can be used
on any port but the total number of connections added
on all of the ports for that particular controller
cannot exceed this number.rw INTEGER .1.3.6.1.4.1.351.110.2.9.2.1.3 |
aumClockConfig OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.3.1 |
primaryMuxClockSourcePrimary Mux Clock source for AUM card.rw Enumeration .1.3.6.1.4.1.351.110.3.1.1 |
secondaryMuxClockSourceSecondary clock source for AUM card.rw Enumeration .1.3.6.1.4.1.351.110.3.1.2 |
currentClockclock source currently selected for AUM card.rw Enumeration .1.3.6.1.4.1.351.110.3.1.3 |
clockSwitchStateclock source switched.ro Enumeration .1.3.6.1.4.1.351.110.3.1.4 |
extClockPresentStatus of External T1/E1 Clock on AUM card.ro Enumeration .1.3.6.1.4.1.351.110.3.1.5 |
extClkSrcImpedanceImpedance on external clock input for AUM card.rw Enumeration .1.3.6.1.4.1.351.110.3.1.6 |
extClkConnectorTypeThis object describes the type of connector available for connecting
the external clock source to the AUM-LM. The T3 and E3
cards are separate hence this field is not configurable
for any BNM card type except bnm-155rw Enumeration .1.3.6.1.4.1.351.110.3.1.7 |
aumAddressTranslation OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.3.2 |
aumAddressTranslationTableThis table contains address translation parameters for AXIS connections. SEQUENCE OF AumAddressTranslationEntry .1.3.6.1.4.1.351.110.3.2.1 |
aumAddressTranslationEntryThis entry exists when the connection specified by connShelfNum,
connSlotNum and connChanNum exists. AumAddressTranslationEntry .1.3.6.1.4.1.351.110.3.2.1.1 |
connShelfNumIndex to shelf list on BASIS.ro INTEGER .1.3.6.1.4.1.351.110.3.2.1.1.1 |
connSlotNumIndex to slot list on BASIS.ro INTEGER .1.3.6.1.4.1.351.110.3.2.1.1.2 |
connChanNumIndex to channel list on BASIS.ro INTEGER .1.3.6.1.4.1.351.110.3.2.1.1.3 |
aumConnTypeVirtual channel connection or Virtual Path Connectionro Enumeration .1.3.6.1.4.1.351.110.3.2.1.1.4 |
connVPINumVirtual channel connection or Virtual Path Connectionro INTEGER .1.3.6.1.4.1.351.110.3.2.1.1.5 |
aumAddressTranslationDeleteTableThis table contains address translation parameters for AXIS connections. SEQUENCE OF AumAddressTranslationDeleteEntry .1.3.6.1.4.1.351.110.3.2.2 |
aumAddressTranslationDeleteEntryThis entry controls bulk deletion of connections on a given AXIS slot. AumAddressTranslationDeleteEntry .1.3.6.1.4.1.351.110.3.2.2.1 |
delShelfNumIndex to shelf list on AXIS.rw INTEGER .1.3.6.1.4.1.351.110.3.2.2.1.1 |
delSlotNumIndex to slot list on BASIS.rw INTEGER .1.3.6.1.4.1.351.110.3.2.2.1.2 |
connNumOfValidEntriesNumber of rows in aumAddressTranslationTable.ro INTEGER .1.3.6.1.4.1.351.110.3.2.3 |
bnmCounters OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.3.3 |
bnmPortCounterTableThe counter table is for the ATM interface, initially there
is only one interface, but by making it a table multiple ATM interfaces
can be accommodated later. SEQUENCE OF BnmPortCounterEntry .1.3.6.1.4.1.351.110.3.3.1 |
bnmPortCounterEntryAn entry for DS3 ATM counters BnmPortCounterEntry .1.3.6.1.4.1.351.110.3.3.1.1 |
bnmPortCounterIndexThis specifies the BNM port being referenced.ro INTEGER .1.3.6.1.4.1.351.110.3.3.1.1.1 |
bnmPortRcvCellsThe count of Received cells at the BNM port.ro Counter .1.3.6.1.4.1.351.110.3.3.1.1.2 |
bnmPortXmtCellsThe count of cells transmitted by the BNM port.ro Counter .1.3.6.1.4.1.351.110.3.3.1.1.3 |
bnmPortCounterClrButtonThis object when set to bnmPortCounterClear causes all counters in the row
referenced by bnmPortCounterIndex to be cleared.rw Enumeration .1.3.6.1.4.1.351.110.3.3.1.1.4 |
bnmPortRcvCellRateThe number of cells received from the BNM port (trunk) per second .ro Gauge .1.3.6.1.4.1.351.110.3.3.1.1.5 |
bnmPortRcvUtilizationThe received percentage utilization of the BNM port (trunk)ro Gauge .1.3.6.1.4.1.351.110.3.3.1.1.6 |
bnmPortXmtCellRateThe number of cells transmitted to the BNM port (trunk) per second.ro Gauge .1.3.6.1.4.1.351.110.3.3.1.1.7 |
bnmPortXmtUtilizationThe transmitted percentage utilization of the BNM port (trunk)ro Gauge .1.3.6.1.4.1.351.110.3.3.1.1.8 |
bnmPortCounterNumOfValidEntriesThis object specifies the number of rows in bnmPortCounterTable.ro INTEGER .1.3.6.1.4.1.351.110.3.3.2 |
bnmCellbusXmtCellCountThis objects is a count of cells transmitted by the BNM Cell Bus Master
to the cell bus.ro Counter .1.3.6.1.4.1.351.110.3.3.3 |
bnmCellbusNoAckCellCountThis object is a count of cells transmitted by the BNM Cell Bus Master
to the cell bus for which no acknowledgement was received i.e the slave
card was missing or inactive.ro Counter .1.3.6.1.4.1.351.110.3.3.4 |
bnmCellbusGrantCountThis object is a count of receiver grants given by the BNM Cell Bus Masterro Counter .1.3.6.1.4.1.351.110.3.3.5 |
bnmEgressXmtCellCountDuringAlarmThis object is a count of cells transmitted by the Egress Engine to the port
i while a T3 Alarm condition was in effect.ro Counter .1.3.6.1.4.1.351.110.3.3.6 |
bnmEgressInvalidCellCountThis object is a count of cells with disabled channel headers, received by
the Egress Engine on the BNM and dropped.ro Counter .1.3.6.1.4.1.351.110.3.3.7 |
bnmEgressInvalidCellHdrThis object gives the header of the first invalid cell that
was dropped by the Egress Engine on the BNM since this object was
last read and/or cleared.ro INTEGER .1.3.6.1.4.1.351.110.3.3.8 |
bnmIngressInvalidCellCountThis object is a count of cells from disabled channels received by the
Ingress Engine on the BNM. This is not available in Release 1.ro Counter .1.3.6.1.4.1.351.110.3.3.9 |
bnmIngressInvalidCellHdrThis object gives the header of the first invalid cell that
was dropped by the Ingress Engine on the BNM since this object was
last read and/or cleared. This is not available in Release 1.ro INTEGER .1.3.6.1.4.1.351.110.3.3.10 |
bnmCountersClrButtonThis object clears the BNM countersrw Enumeration .1.3.6.1.4.1.351.110.3.3.11 |
ascLineCnfSigLmiGrp OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.3.4.1 |
ascCnfSigLmiGrpTableThe config table is for DS3 line interface SEQUENCE OF AscCnfSigLmiGrpEntry .1.3.6.1.4.1.351.110.3.4.1.1 |
ascCnfSigLmiGrpEntryAn entry for logical line AscCnfSigLmiGrpEntry .1.3.6.1.4.1.351.110.3.4.1.1.1 |
ascLmiCnfLineNumRefers to the logical line indexro Enumeration .1.3.6.1.4.1.351.110.3.4.1.1.1.1 |
ascLmiVpiVPI used for ATM LMI signallingro Enumeration .1.3.6.1.4.1.351.110.3.4.1.1.1.2 |
ascLmiVciVCI used for ATM LMI signallingro Enumeration .1.3.6.1.4.1.351.110.3.4.1.1.1.3 |
ascLmiEnabledThis will enable ATM LMI signalling,
or ATM LMI with the Node Status Extensionsrw Enumeration .1.3.6.1.4.1.351.110.3.4.1.1.1.4 |
ascLmiPollingEnabledThis will enable ATM LMI pollingrw Enumeration .1.3.6.1.4.1.351.110.3.4.1.1.1.5 |
ascLmiPollingIntervalStatus Enq Polling Interval in seconds
Default is 10 secondsrw INTEGER .1.3.6.1.4.1.351.110.3.4.1.1.1.6 |
ascLmiTimerT393Status Enq timeout interval in seconds
Default is 10 secondsrw INTEGER .1.3.6.1.4.1.351.110.3.4.1.1.1.7 |
ascLmiTimerT394Update Status timeout interval in seconds
Default is 10 secondsrw INTEGER .1.3.6.1.4.1.351.110.3.4.1.1.1.8 |
ascLmiMaxRetryN394Status Enq maximum retry count
Default is 3rw INTEGER .1.3.6.1.4.1.351.110.3.4.1.1.1.9 |
ascLmiMaxRetryN395Update Status maximum retry count
Default is 3rw INTEGER .1.3.6.1.4.1.351.110.3.4.1.1.1.10 |
ascLmiOperStatusOperational statusro Enumeration .1.3.6.1.4.1.351.110.3.4.1.1.1.11 |
ascCntSigLmiGrp OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.3.4.2 |
ascCntSigLmiGrpTableThe counter table is for DS3 line interface SEQUENCE OF AscCntSigLmiGrpEntry .1.3.6.1.4.1.351.110.3.4.2.1 |
ascCntSigLmiGrpEntryAn entry for logical line AscCntSigLmiGrpEntry .1.3.6.1.4.1.351.110.3.4.2.1.1 |
ascLmiCntLineNumRefers to the logical line indexro Enumeration .1.3.6.1.4.1.351.110.3.4.2.1.1.1 |
ascLmiStatusTxThe number of Status PDUs transmittedro Counter .1.3.6.1.4.1.351.110.3.4.2.1.1.2 |
ascLmiStatusEnqTxThe number of Status Enquiry PDUs transmittedro Counter .1.3.6.1.4.1.351.110.3.4.2.1.1.3 |
ascLmiStatusAckTxThe number of Status Ack PDUs transmittedro Counter .1.3.6.1.4.1.351.110.3.4.2.1.1.4 |
ascLmiUpdateStatusTxThe number of Update Status PDUs transmittedro Counter .1.3.6.1.4.1.351.110.3.4.2.1.1.5 |
ascLmiStatusRxThe number of Status PDUs receivedro Counter .1.3.6.1.4.1.351.110.3.4.2.1.1.6 |
ascLmiStatusEnqRxThe number of Status Enquiry PDUs receivedro Counter .1.3.6.1.4.1.351.110.3.4.2.1.1.7 |
ascLmiStatusAckRxThe number of Status Ack PDUs receivedro Counter .1.3.6.1.4.1.351.110.3.4.2.1.1.8 |
ascLmiUpdateStatusRxThe number of Update Status PDUs receivedro Counter .1.3.6.1.4.1.351.110.3.4.2.1.1.9 |
ascLmiInvalidPduRxThe number of Invalid PDUs received.
These are PDUs with invalid SSCOP or Q.2931 header,
or invalid Protocol Discriminatorro Counter .1.3.6.1.4.1.351.110.3.4.2.1.1.10 |
ascLmiInvalidPduLenRxThe number of PDUs received with invalid length.
ATM LMI PDU Length field plus Q.2931 Header length
does not equal actual message lengthro Counter .1.3.6.1.4.1.351.110.3.4.2.1.1.11 |
ascLmiUnknownPduRxThe number of PDUs with unknown Message Type receivedro Counter .1.3.6.1.4.1.351.110.3.4.2.1.1.12 |
ascLmiInvalidIeRxThe number of PDUs received with invalid Information Elements.
This includes IEs with invalid length and missing mandatory IEsro Counter .1.3.6.1.4.1.351.110.3.4.2.1.1.13 |
ascLmiInvalidTransactionThe number of invalid transactions.
The transaction number of a transmitted Update Status PDU does
not match the transaction number of the corresponding received
Status Ack PDU, or,
the transaction number of a transmitted Status Enq PDU does
not match the transaction number of the corresponding received
Status PDU.ro Counter .1.3.6.1.4.1.351.110.3.4.2.1.1.14 |
ascLmiTimeoutFailureThe number of timeout failuresro Counter .1.3.6.1.4.1.351.110.3.4.2.1.1.15 |
ascLmiNodeStatusTxThe number of Node Status PDUs transmittedro Counter .1.3.6.1.4.1.351.110.3.4.2.1.1.16 |
ascLmiNodeStatusAckTxThe number of Node Status Ack PDUs transmittedro Counter .1.3.6.1.4.1.351.110.3.4.2.1.1.17 |
ascLmiNodeStatusRxThe number of Node Status PDUs receivedro Counter .1.3.6.1.4.1.351.110.3.4.2.1.1.18 |
ascLmiNodeStatusAckRxThe number of Node Status Ack PDUs receivedro Counter .1.3.6.1.4.1.351.110.3.4.2.1.1.19 |
ascChanStateSigLmiGrp OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.3.4.3 |
ascChanStateSigLmiGrpTableThe ATM LMI Channel State table SEQUENCE OF AscChanStateSigLmiGrpEntry .1.3.6.1.4.1.351.110.3.4.3.1 |
ascChanStateSigLmiGrpEntryAn entry for a Channel AscChanStateSigLmiGrpEntry .1.3.6.1.4.1.351.110.3.4.3.1.1 |
ascLmiVccLineNumRefers to the line numberro Enumeration .1.3.6.1.4.1.351.110.3.4.3.1.1.1 |
ascLmiVccVpiRefers to the Virtual Path Indicatorro INTEGER .1.3.6.1.4.1.351.110.3.4.3.1.1.2 |
ascLmiVccVciRefers to the Virtual Channel Indicatorro INTEGER .1.3.6.1.4.1.351.110.3.4.3.1.1.3 |
ascLmiXmtAbitStateThis is the transmit A bit state
0 - A bit clear = not active
1 - A bit set = activero INTEGER .1.3.6.1.4.1.351.110.3.4.3.1.1.4 |
ascLmiRcvAbitStateThis is the receive A bit state
0 - A bit clear = not active
1 - A bit set = activero INTEGER .1.3.6.1.4.1.351.110.3.4.3.1.1.5 |
ascFeatures OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.3.5 |
redundancyAllowedBRAM parameter indicating whether redundancy is allowed in
this shelf.ro Enumeration .1.3.6.1.4.1.351.110.3.5.1 |
smFeatures OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.3.6 |
channelizedAllowedBRAM parameter indicating whether this card will support
DS0 channels.ro Enumeration .1.3.6.1.4.1.351.110.3.6.1 |
rateControlAllowedBRAM parameter indicating whether this card will support
foresight.ro Enumeration .1.3.6.1.4.1.351.110.3.6.2 |
svcAllowedBRAM parameter indicating whether this card will support
svc.ro Enumeration .1.3.6.1.4.1.351.110.3.6.3 |
funiAllowedBRAM parameter indicating whether this card will support
FUNI.ro Enumeration .1.3.6.1.4.1.351.110.3.6.4 |
imaAllowedBRAM parameter indicating whether this card will support
Inverse Multiplexing for ATM (IMA) featurero Enumeration .1.3.6.1.4.1.351.110.3.6.5 |
mulTrksAllowedBRAM parameter indicating whether this card will support
multiple IMA trunks feature.
A value of 1 indicates that the feature is not allowed and
a value of 2 indicates that the features is allowedro Enumeration .1.3.6.1.4.1.351.110.3.6.6 |
egrQosFeatureIf this is set to egrQosFeatureEnabled then
the various class of service viz. Hi Priority, VBR rt, etc.
as defined by the channel MIB object chanServType are supported.
If this is set to egrQosFeatureDisabled then, the priority based
queuing as defined by the channel MIB object egressQSelect is
supported.ro Enumeration .1.3.6.1.4.1.351.110.3.6.7 |
smRateControlConfig OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.3.7 |
rateUpRate Up value for this card.rw INTEGER .1.3.6.1.4.1.351.110.3.7.1 |
rateDownRate Down value for this card.rw INTEGER .1.3.6.1.4.1.351.110.3.7.2 |
rateFastDownRate Fast Down value for this card.rw INTEGER .1.3.6.1.4.1.351.110.3.7.3 |
rtdMeasurementTimeRound Trip delay measurement time in secs for this card.rw INTEGER .1.3.6.1.4.1.351.110.3.7.4 |
qirTimeoutQIR timeout in secs for this card.rw INTEGER .1.3.6.1.4.1.351.110.3.7.5 |
imatmClkCfgGrp OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.3.8 |
primaryClockSourcePrimary reference for the clock source. Each of these codes are
to be interpreted as follows:
liu-rclk0: Recovered clock from physical line 0
liu-rclk1: Recovered clock from physical line 1
liu-rclk2: Recovered clock from physical line 2
liu-rclk3: Recovered clock from physical line 3
liu-rclk4: Recovered clock from physical line 4
liu-rclk5: Recovered clock from physical line 5
liu-rclk6: Recovered clock from physical line 6
liu-rclk7: Recovered clock from physical line 7
dsx3: Recovered clock from the T3/E3 line
bp8clk: Back-plane 8 KHz clockrw Enumeration .1.3.6.1.4.1.351.110.3.8.1 |
secondaryClockSourceSecondary reference for the clock source. Each of these codes are
to be interpreted as follows:
liu-rclk0: Recovered clock from physical line 0
liu-rclk1: Recovered clock from physical line 1
liu-rclk2: Recovered clock from physical line 2
liu-rclk3: Recovered clock from physical line 3
liu-rclk4: Recovered clock from physical line 4
liu-rclk5: Recovered clock from physical line 5
liu-rclk6: Recovered clock from physical line 6
liu-rclk7: Recovered clock from physical line 7
dsx3: Recovered clock from the T3/E3 line
bp8clk: Back-plane 8 KHz clock
none : No secondary clock is configuredrw Enumeration .1.3.6.1.4.1.351.110.3.8.2 |
currentClockSourceThis object holds the current source for the clockrw Enumeration .1.3.6.1.4.1.351.110.3.8.3 |
imatmDsx3CntrsGrp OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.3.9 |
imatmDsx3PortCntrsGrpTableThe dsx3 port counters table is for the DS3 port in IMATM.
At present there is only one entry (corresponding to the
single DS3 port available). This structure has been made a
table for flexibility (although there is only one entry in
the table at present) SEQUENCE OF ImatmDsx3PortCntrsEntry .1.3.6.1.4.1.351.110.3.9.1 |
imatmDsx3PortCntrsEntryAn entry for each T3 port (total of only one entry at present) ImatmDsx3PortCntrsEntry .1.3.6.1.4.1.351.110.3.9.1.1 |
imatmDsx3PortIndexIndex to the dsx3 port numberro INTEGER .1.3.6.1.4.1.351.110.3.9.1.1.1 |
imatmDsx3PortRcvCellsNumber of cells received on the DS3 portro Counter .1.3.6.1.4.1.351.110.3.9.1.1.2 |
imatmDsx3PortXmtCellsNumber of cells transmitted on the DS3 portro Counter .1.3.6.1.4.1.351.110.3.9.1.1.3 |
imatmPortRcvInvCellsNumber of invalid cells received on the DS3 portro Counter .1.3.6.1.4.1.351.110.3.9.1.1.4 |
imatmPortCntrClrButtonThis variable is used to clear all the counters
maintained by the card for this DS3 portrw Enumeration .1.3.6.1.4.1.351.110.3.9.1.1.5 |
imatmDsx3PortLastMismatchVpiVciThis variable denotes the last mismatch VPI/VCI value that
was received over the DS3 interface.ro INTEGER .1.3.6.1.4.1.351.110.3.9.1.1.6 |
imatmPortImaCtrlMatchCellsThis variable is used to count the number of cells from the
DS3 interface that were discarded due to match with IMA
Control headerro Counter .1.3.6.1.4.1.351.110.3.9.1.1.7 |
srm3T3CnfGrp OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.3.10 |
srm3T3CnfGrpTableThe SRM 3T3 configuration table, it is the
distribution of a T3 line. SEQUENCE OF Srm3T3CnfGrpEntry .1.3.6.1.4.1.351.110.3.10.1 |
srm3T3CnfGrpEntryan entry in the T3 configuration table Srm3T3CnfGrpEntry .1.3.6.1.4.1.351.110.3.10.1.1 |
srmT3LineNumSelect T3 line number.
There is no default value for this object.ro INTEGER .1.3.6.1.4.1.351.110.3.10.1.1.1 |
srmStartT1LineNumThe start T1 number to be affected.
There is no default value for this object.ro INTEGER .1.3.6.1.4.1.351.110.3.10.1.1.2 |
srmT1RowStatusa command is used to add, delete, or modify
one or more DS1 mapping.
Default value is delete.rw Enumeration .1.3.6.1.4.1.351.110.3.10.1.1.3 |
srmTargetSlotNumspecify the target slot number to be linked.
There is no default value for this object.
For MGX8850: SRM01 services slots 1 - 6 and 9 - 14,
SRM02 services slots 17 - 22 and 25 - 30
For MGX8220: SYNTAX INTEGER (5 ..14)rw INTEGER .1.3.6.1.4.1.351.110.3.10.1.1.4 |
srmTargetSlotLineNum0 means not assigned.
There is no default value for this object.rw INTEGER .1.3.6.1.4.1.351.110.3.10.1.1.5 |
smCardUtilization OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.3.11 |
cardOversubscribedThis variable indicates the whether the card is
over subscribed or notro Enumeration .1.3.6.1.4.1.351.110.3.11.1 |
cardIngrPercentUtilPercentage Utilization of the Card in the Ingress
direction.ro INTEGER .1.3.6.1.4.1.351.110.3.11.2 |
bnmLineInterfaceMode OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.3.12 |
bnmLineInterfaceFormatThis indicates the format of the cells going out on the BNM trunk
For T3 and E3 cards its currently fixed at STI mode. BNM-155
sonet cards can take on UNI or NNI optionsrw Enumeration .1.3.6.1.4.1.351.110.3.12.1 |
imatmVpTrkGrp OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.3.13 |
imatmVpTrkMapGrp OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.3.13.1 |
imatmVpTrkMapGrpTableThe imatmVpTrkMapGrpTable entry contains the information for
mapping VPI ranges to different trunks in IMATM. SEQUENCE OF ImatmVpTrkMapGrpTableEntry .1.3.6.1.4.1.351.110.3.13.1.1 |
imatmVpTrkMapGrpTableEntryAn entry for each VPI range ImatmVpTrkMapGrpTableEntry .1.3.6.1.4.1.351.110.3.13.1.1.1 |
imatmRangeNumAn index to the VpTrkTblro INTEGER .1.3.6.1.4.1.351.110.3.13.1.1.1.1 |
imatmTrkNumThis variable refers to the trunk number on the IMATM card. The
trunk number is the same as logical port number.rw INTEGER .1.3.6.1.4.1.351.110.3.13.1.1.1.2 |
imatmTrkMinVpThis variable refers to the minimum VPI value to be configured
in the range of VPIs that are to be mapped to an IMATM trunk.rw INTEGER .1.3.6.1.4.1.351.110.3.13.1.1.1.3 |
imatmTrkMaxVpThis variable refers to the maximum VPI value to be configured
in the range of VPIs that are to be mapped to an IMATM trunk.
It should be necessarily greater than or equal to the value of
imatmTrkMinVp.rw INTEGER .1.3.6.1.4.1.351.110.3.13.1.1.1.4 |
imatmTrkOpTypeThis variable refers to the operation type for the VPI range
in question.
'disable' deletes an existing row from the table
'enable' adds a new row to the table
'modify' modifies the attributes of an existing row to the
tablerw Enumeration .1.3.6.1.4.1.351.110.3.13.1.1.1.5 |
nextRangeNumAvailThis variable indicates the next range number to be used as the
index for the VpTrkTbl.ro INTEGER .1.3.6.1.4.1.351.110.3.13.1.2 |
imatmVpTrkClrGrp OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.3.13.2 |
imatmVpTrkClrGrpTableThis table is for each trunk in IMATM and is used if the user
wishes to remove all VPI ranges for an IMATM trunk. SEQUENCE OF ImatmVpTrkClrGrpEntry .1.3.6.1.4.1.351.110.3.13.2.1 |
imatmVpTrkClrGrpEntryAn entry for each IMATM trunk ImatmVpTrkClrGrpEntry .1.3.6.1.4.1.351.110.3.13.2.1.1 |
imatmClrVpTrkNumThis variable is used to identify the IMATM trunk number on
which the 'Clear Map Table' operation needs to be done.ro INTEGER .1.3.6.1.4.1.351.110.3.13.2.1.1.1 |
imatmClrVpTrkButtonThis variable implements the 'Clear Map Table' for a specified
IMATM trunk.rw Enumeration .1.3.6.1.4.1.351.110.3.13.2.1.1.2 |
dsx3CardSpecCnfgGrp OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.3.14 |
imatmDsx3CardSpecConfigGrpTableThe dsx3 Card spec Config group table will contain all the
configuration variable for DSX3. Right now there is only one
configurable parameter in this group. Moreover this structure has
been made a table for flexibility (although there is only one entry
in the table at present). SEQUENCE OF ImatmDsx3CardSpecConfigEntry .1.3.6.1.4.1.351.110.3.14.1 |
imatmDsx3CardSpecConfigEntryEach entry gives the config parameters for the given port. ImatmDsx3CardSpecConfigEntry .1.3.6.1.4.1.351.110.3.14.1.1 |
imatmdsx3PortIndexIndex to the dsx3 port numberro INTEGER .1.3.6.1.4.1.351.110.3.14.1.1.1 |
imatmDsx3SingleBitErrCorrEnableThis variable refers to dsx3 HEC correction enabled/disabled
default is disable.rw Enumeration .1.3.6.1.4.1.351.110.3.14.1.1.2 |
pxmFeatures OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.3.15 |
vsiControllersAllowedThis respesents bit map of the VSI Controllers
supported. Currently, we have
BIT 0 - PAR
BIT 1 - PNNI
BIT 2 - TAG
(e.g. A value of 1 in BIT 0 indicates the presence of PAR )
Remaining bits are set to 0.ro INTEGER (0..'ffffff'h) .1.3.6.1.4.1.351.110.3.15.1 |
apsCardAttributesThis respesents bit map of the APS card attributes
supported. Currently, we have
BIT 0, 1 - unused
BIT 2 - APS standard protocol configured
(1 = TRUE ; 0 = FALSE)
BIT 3, 4 ,5 - unused
BIT 6 - Card HW supports APS 1+1 on two cards
(1 = TRUE ; 0 = FALSE)
BIT 7 - Card FW supports APS (1 = TRUE ; 0 = FALSE)
Remaining bits are set to 0.ro INTEGER (0..'ff'h) .1.3.6.1.4.1.351.110.3.15.2 |
trkCACEnableThis MIB variable allows one to add a new connection on
the feeder trunk even if it is over-subscribed.rw Enumeration .1.3.6.1.4.1.351.110.3.15.3 |
pxmClockConfig OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.3.16 |
pxmPrimaryMuxClockSourcePrimary Mux Clock source for PXM card.
For pxmInbandClock1 and pxmInbandClock2, the pxmPrimaryInbandClockSourceLineNumber
described the Line number that the clock is derived from.
For pxmServiceModuleClock1 and pxmServiceModuleClock2, the
pxmPrimarySMClockSourceSlotNumber described the SM slot number
For pxmExternalClock and pxmExternalClock2,
pxmPrimaryExternalClockSourcePortNumber describes the Port number from
where the clock is derived. Also the pxmExtClockPresent and
pxmExtClkConnectorType are used with the pxmExternalClock. And
pxmExtClock2Present and pxmExtClk2ConnectorType are used with
pxmExternalClock2.ro Enumeration .1.3.6.1.4.1.351.110.3.16.1 |
pxmPrimaryInbandClockSourceLineNumberIf pxmPrimaryMuxClockSource is pxmInbandClock1 (1) or pxmServiceModuleClock2 (5),
then this entry indicates Inband Line number.ro INTEGER .1.3.6.1.4.1.351.110.3.16.2 |
pxmPrimarySMClockSourceSlotNumberIf pxmPrimaryMuxClockSource is pxmServiceModuleClock1(2) or pxmServiceModuleClock2 (6),
then this entry indicates SM slot number.ro INTEGER .1.3.6.1.4.1.351.110.3.16.3 |
pxmSecondaryMuxClockSourceSecondary clock source for PXM card.
For pxmInbandClock1 and pxmInbandClock2, the pxmSecondaryInbandClockSourceLineNumber
described the Line number that the clock is derived from.
For pxmServiceModuleClock1 and pxmServiceModuleClock2, the
pxmSecondarySMClockSourceSlotNumber described the SM slot number
pxmSecondaryExternalClockSourcePortNumber describes the Port number from
where the clock is derived. Also the pxmExtClockPresent and
pxmExtClkConnectorType are used with the pxmExternalClock. And
pxmExtClockPresent2 and pxmExtClkConnectorType2 are used with
pxmExternalClock2.ro Enumeration .1.3.6.1.4.1.351.110.3.16.4 |
pxmSecondaryInbandClockSourceLineNumberIf pxmSecondaryMuxClockSource is pxmInbandClock1 (1) or pxmServiceModuleClock2 (5),
then this entry indicates Inband Line number .ro INTEGER .1.3.6.1.4.1.351.110.3.16.5 |
pxmSecondarySMClockSourceSlotNumberIf pxmSecondaryMuxClockSource is pxmServiceModuleClock1(2) or pxmServiceModuleClock2 (6),
then this entry indicates SM slot number .ro INTEGER .1.3.6.1.4.1.351.110.3.16.6 |
pxmCurrentClockClock source currently selected for PXM card.
If the pxmCurrentClock is primary then the pxmPrimaryMuxClockSource
described further the source of the clock.
If the pxmCurrentClock is secondary then the pxmSecondaryMuxClockSource
described further the source of the clock.ro Enumeration .1.3.6.1.4.1.351.110.3.16.7 |
pxmPreviousClockClock source Previously selected for PXM card.ro Enumeration .1.3.6.1.4.1.351.110.3.16.8 |
pxmExtClockPresentStatus of External T1/E1 Clock on PXM card.ro Enumeration .1.3.6.1.4.1.351.110.3.16.9 |
pxmExtClkSrcImpedanceImpedance on external clock input for PXM card.ro Enumeration .1.3.6.1.4.1.351.110.3.16.10 |
pxmExtClkConnectorTypeThis object describes the type of connector available for connecting
the external clock source to the PXM-LM.ro Enumeration .1.3.6.1.4.1.351.110.3.16.11 |
pxmClkStratumLevelThis object describes the lowest stratum level provided by the interface
the external clock source to the PXM-LM.ro Enumeration .1.3.6.1.4.1.351.110.3.16.12 |
pxmClkErrReasonThis object gives more information about clock status (if known).ro Enumeration .1.3.6.1.4.1.351.110.3.16.13 |
pxmExtClock2PresentStatus of External T1/E1 Clock on port 2 of UI-S3 back card of PXM card.ro Enumeration .1.3.6.1.4.1.351.110.3.16.14 |
pxmExtClk2SrcImpedanceImpedance on external clock input on port 2 of UI-S3 back card of PXM
card.ro Enumeration .1.3.6.1.4.1.351.110.3.16.15 |
pxmExtClk2ConnectorTypeThis object describes the type of connector available for connecting
the external clock source to the port 2 of UI-S3 back card of PXM-LM.ro Enumeration .1.3.6.1.4.1.351.110.3.16.16 |
vismConfig OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.3.17 |
vismIpGrp OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.3.17.1 |
vismIpAddressThe IP address of VISM card. Each VISM card has its own IP address.
IP address for each VISM card is required to communicate with the
Call agent. The IP address should be configured before adding
endpoints.
This object is applicable if the mode is voIP or switching.
From vism 2.0.3 release onwards this object can be
configured in any application but will be applicable only
in switching applications.rw IpAddress .1.3.6.1.4.1.351.110.3.17.1.1 |
vismSubNetMaskSUB-NETMASK of the VISM IP interface.
This object is applicable if the mode is voIP or switching.
From vism 2.0.3 release onwards this object can be
configured in any application but will be applicable only
in switching applications.rw IpAddress .1.3.6.1.4.1.351.110.3.17.1.2 |
vismControlTosThis object is used to provision the bitmask used for the
TOS (Type Of Service) octet for cells carrying the control
(xGCP ) traffic.
Default value 96 = 0x60 => Precedence = 3 and TOS nibble = 0
The bitmask can be only a byte value.rw INTEGER .1.3.6.1.4.1.351.110.3.17.1.3 |
vismBearerIpAddressThe bearer IP address of VISM card. This is an optional second
IP address of the VISM card. If this bearer IP address is defined,
the vismIpAddress automatically becomes the control IP address.
From vism 2.0.3 release onwards this object can be
configured in any application but will be applicable only
in switching applications.rw IpAddress .1.3.6.1.4.1.351.110.3.17.1.4 |
vismBearerSubNetMaskBearer SUB-NETMASK of the VISM IP interface.
This optional bearer subnet mask must be provided
when vismBearerIpAddress is provided.
From vism 2.0.3 release onwards this object can be
configured in any application but will be applicable only
in switching applications.rw IpAddress .1.3.6.1.4.1.351.110.3.17.1.5 |
vismVoIpGrp OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.3.17.2 |
vismBearerTosThis object is used to provision the bitmask used for the
TOS (Type Of Service) octet for cells carrying VoIP bearer
(RTP ) traffic.
Default value 160 = 0xA0 => Precedence = 5 and TOS nibble = 0
The bitmask can be only a byte value.rw INTEGER .1.3.6.1.4.1.351.110.3.17.2.1 |
vismRtcpRepIntervalThis attribute defines the RTCP report interval (
defined in RFC 1889). This indicates the interval at which
the RTCP reports should be sent to the participating members. The
value is expressed in units of milliseconds. The RTCP reports are not
sent at a fixed rate at this interval. Rather, this value is used as
a base value to arrive at a random number between 0.5 and 1.5 times
this value.
This interval timer also serves the purpose of RTP packets receive
timer. At every 'vismRtcpRecvMultiplier' times this interval, where
'vismRtcpRecvMultiplier'is specified in the MIB object below, a check
is made on a VoIP connection (which is in SENDRECV or RECVONLY xGCP
modes) to see if any RTP packets have been received. If not,
gateway-initiated DLCX should be sent to the Call Agent.
Currently, this interval timer is a card-specific value, which means
the value is configurable on a per card basis and not on a per call
basis.
This value is applicable for VoIP adaptation only.
From vism 2.0.3 release onwards this object can be configured in any
mode/adaptations, but will be applicable only in voip adaptation.rw INTEGER .1.3.6.1.4.1.351.110.3.17.2.2 |
vismRtpReceiveTimerThis object defines whether the RTP packets receive timer on the VISM
needs to be enabled or not. For some VoIP applications (as in
South Carolina release), if a connection is in send-recv mode or
recv-only mode, after the bearer cur-through is done, the RTP stream
should be monitored for RTP packets. If there are no packets received
within a time interval specified by 5 seconds, then a Gateway initiated
DLCX (Delete connection) should be sent on that connection.
If this object is set to enable, the RTP stream is monitored.
Otherwise, it is not monitored.
This value is applicable for VoIP adaptation only.
From vism 2.0.3 release onwards this object can be configured in any
mode/adaptations, but will be applicable only in voip adaptation.rw Enumeration .1.3.6.1.4.1.351.110.3.17.2.3 |
vismPacketizationPeriodThis object is used to provision the packetization period
to be applied.
This object is applicable for VoIP adaptation only. For
VoAAL2 adaptations, the packetization period is derived from
the profile table entry. For VoAAL1 adaptation, it is fixed
at 5.875 ms.rodeprecated Enumeration .1.3.6.1.4.1.351.110.3.17.2.4 |
vismVoIpDtmfRelayThis attribute defines whether the DTMF (Dual Tone, Multi-Frequency)
digits need to be transported to the other endpoint via NSE packets.
The value in this object will be utilised when the Call Agent does
not specify this.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.351.110.3.17.2.5 |
vismVoIpCasTransportThis attribute defines whether the CAS (ABCD bits) bits need to be
transported to the other endpoint via NSE packets.
The value in this object will be utilized when the Call Agent does not
specify this.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.351.110.3.17.2.6 |
vismVoIpTripleRedundancyThis attribute defines whether triple redundancy is enabled or not.
With triple redundancy, NSEs are sent three times at 20 ms intervals.
For reliable channels, triple redundancy can be disabled in order to
save the bandwidth and the processing overheads.
The value in this object will be utilized when the Call Agent does not
specify this.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.351.110.3.17.2.7 |
vismVoIpVADTimerThis attribute defines the hangover time for VAD in milliseconds.
Once the voice inactivity is detected, the gateway will wait for
this duration before activating silence suppression.
The value in this object will be utilized when the Call Agent does
not specify this.rw INTEGER .1.3.6.1.4.1.351.110.3.17.2.8 |
vismVoIpNTECapabilityNegotiateThis attribute defines whether the VISM has the capability to
negotiate the list of events either NSE (Named Signal Event)
or NTE (Named Telephony Events), using rtpmap and fmtpmap in
the SDP.
If the value is TRUE, then VISM will include / accept rtpmap
and fmtpmap in the SDP. Any events NSE / NTE not listed will
be interpreted as not supported.
If the value is FALSE, then VISM will neither include nor
accept rtpmap for X-NSE & X-NTE, and fmtpmap. For the backward
compatibility sake VISM will transmit DTMF digits using NSEs
if the value is FALSErw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.351.110.3.17.2.9 |
vismVoIpSIDPayloadTypeThis attribute sets the payload type of a RTP packet carrying SID
which is sent to the other end when silence is detected. The default
value is in accordance to the earlier revisions of
draft-ietf-avt-provile-new-10.txtrw INTEGER .1.3.6.1.4.1.351.110.3.17.2.10 |
vismVoIpDPvcOamCellGapThis attribute defines the inter cell gap for dual PVC OAM cells.
The value represents the time in milliseconds.rw INTEGER .1.3.6.1.4.1.351.110.3.17.2.11 |
vismVoIpDPvcRetryCntThis attribute defines the threshold for failure of a PVC. If the
number of consecutive OAM cells sent for which no ack was received
equals this number then the connection is considered failed.rw INTEGER .1.3.6.1.4.1.351.110.3.17.2.12 |
vismVoIpDPvcRecoverCntThis attribute defines the threshold for recovery of a PVC. If
the number of consecutive OAM cells sent for which ack was received
equals this number then the connection is considered recovered
from failure.rw INTEGER .1.3.6.1.4.1.351.110.3.17.2.13 |
vismRtcpRecvMultiplierThe 'vismRtcpRepInterval' MIB object specified above defines an
approximate RTCP report interval (defined in RFC 1889) which indicates
the interval in milliseconds at which the RTCP reports should be sent
to the participating members.
This MIB object, 'vismRtcpRecvMultiplier', defines how many times the
RTCP reports may fail before exception condition activity may be done.
At this number of times specified in this MIB object times the RTCP
Report Interval, a check is made on a VoIP connection (which
is in SENDRECV or RECVONLY xGCP modes) to see if any RTP packets
have been received. If not, gateway-initiated DLCX should be
sent to the Call Agent.
Currently, this interval multiplier is a card-specific value, which
means the value is configurable on a per card basis and not on a per
call basis.
This value is applicable for VoIP adaptation only.rw INTEGER .1.3.6.1.4.1.351.110.3.17.2.14 |
vismVoIpLapdTrunkPVCThis object should be used for VoIP Trunking applications and only
if the signalling type is configured to be CCS. By default the PRI
D-channel information will be sent on the control channel. If the
control network is totally seperated from the bearer network then
the user needs to set this object to 'bearer' to send his Lapd trunk
messages to the remote VISM.rw Enumeration .1.3.6.1.4.1.351.110.3.17.2.15 |
vismVoIpEventNegotiationPolicyThis attribute defines whether or not the VISM should advertise
the event codecs, NSE (Named Signal Events), NTE (Named Telephony
Events), or Cisco-rtp, in addition to the list of events specified
by the call agent.
If the value is none, then VISM will not include any more event
codecs than what has been specified by the call agent.
If the value is proprietary, then VISM can advertise proprietary
event codecs in addition to the event codecs specified by the call
agent.
If the value is all, then VISM can advertise both proprietary as well
as standard event codecs in addition to the event codecs specified by
the call agent.rw Enumeration .1.3.6.1.4.1.351.110.3.17.2.16 |
vismDspGrp OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.3.17.3 |
vismEcanCnfIdlePatternEcho Canceller pattern for Idle code.
Mu-Law : 1 - 7f, 2 - ff, 3 - 7f or ff, 4 - f7
A-Law : 1 - None, 2 - 54, 3 - 55, 4 - Programable Idle code.
DEFVAL : pattern3 (7f or ff) for Mu-law and
pattern2 (54) for A-Law.rodeprecated Enumeration .1.3.6.1.4.1.351.110.3.17.3.1 |
vismEcanCnfIdleDirectionEcho Canceller Idle Direction. This determines in
which direction the Idle code must be present.rodeprecated Enumeration .1.3.6.1.4.1.351.110.3.17.3.2 |
vismCompCnfPacketSizeCompressed output packet size - This value is used in the DSP
interface API commands to configure the DSPs for the maximum
packet size.
The valid values are 80 and 160 only.
NOTE: This object is not used currently.
In future it is applicable only if the mode is VoAAL1.
From vism 2.0.3 release onwards this object can be configured in any
mode/adaptations, but will be applicable only in aal1 adaptation.rw INTEGER .1.3.6.1.4.1.351.110.3.17.3.3 |
vismERLThis object is used to provision the return echo lost,
i.e the db loss of the echo that the DSPs are supposed
to cancel.rw Enumeration .1.3.6.1.4.1.351.110.3.17.3.4 |
vismJitterDelayModeThis object is used to provision the jitter buffer mode
to be apply to a call connection.
The possible values are:
fixed - means use a constant jitter buffer size, which
is defined by the vismJitterInitialDelay mib
variable.
adaptive - means let the DSP pick the optimal value for
the call connection.rwdeprecated Enumeration .1.3.6.1.4.1.351.110.3.17.3.5 |
vismJitterInitialDelayDefines the jitter buffer size. If the vismJitterDelayMode
is set to be fixed, the jitter buffer is fixed at this value
for the call. If vismJitterDelayMode is adaptive, this is
the initial jitter buffer size, and the DSP will adapt to
an optimal size.
The range 10,20,30,40,50,60,70,80,90,100 is applicable to
1.5 release only.
The range 1,5,10,15,20,25,30,35 .... is applicable from vism2.0
release onwards.
The valid range for template 1 : 1,10,20,30,40,50,60,70,80,90,100
The valid range for template 2 : 1,5,10,15,20,25,30,35,40,45,50,
55,60,65,70,75,80,85,90,95,100.
When the template of the card changes, either from template 1
to 2 or vice versa the value of this object will be implicitly
set to default value.rwdeprecated Enumeration .1.3.6.1.4.1.351.110.3.17.3.6 |
vismAdaptiveGainControlIf set to on, the DSP will adjust the gain of the
of the call connection to an optimal value.rw Enumeration .1.3.6.1.4.1.351.110.3.17.3.7 |
vismDspHealthThis attribute indicates the health of the DSPs. It is a
percentage of the total number of DSPs that are currently
functional. Currently No action is planned upon the failure
of a DSP chip in a card, other than resetting the card.ro INTEGER .1.3.6.1.4.1.351.110.3.17.3.8 |
vismUpspeedCodecThis object specifies the codec to be used when
fax upspeed happens.
The default value for this object is G.711u when
the line type is T1 and G.711a when the line type is
E1
This object is applicable only in the case of
VOIP applications, for AAL2 the upspeedCodec is obtained
from profile table and this object will have no
affect.rw Enumeration .1.3.6.1.4.1.351.110.3.17.3.9 |
vismPayloadTypeThis object specifies the payload type to be used when
fax upspeed happens.
IANA values (0..95) are static payload and (96..127) are
dynamic payload type.
This object is applicable only in the case of
VOIP applications, for AAL2 the upspeedCodec is obtained
from profile table and this object will have no
affect.rw INTEGER .1.3.6.1.4.1.351.110.3.17.3.10 |
vismSystemGrp OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.3.17.4 |
vismDaughterCardSerialNumA unique value for each VISM daughter card, entered in nvram
by manf. The serial No. is on the non-volatile RAM on the
VISM daughter card.ro DisplayString .1.3.6.1.4.1.351.110.3.17.4.1 |
vismDaughterCardDescriptionDescribes the VISM daughter card.ro DisplayString .1.3.6.1.4.1.351.110.3.17.4.2 |
vismDaughterCardHWRevHardware revision number for the daughter card.ro DisplayString .1.3.6.1.4.1.351.110.3.17.4.3 |
vismEcanEncodingVoice encoding type, Mu-law or A-law.
mu-law is returned for T1 lines and a-law is returned for E1 lines.ro Enumeration .1.3.6.1.4.1.351.110.3.17.4.4 |
vismModeThis attribute defines the connection model that the VISM card
is configured to operate with. This object can be modified by
CLI only. The CLI 'cnfvismmode' can be used to set this object.
VISM card will be reset after modifying this parameter
for the VISM card to come up in the new mode.
Each mode enables a set of features on the VISM card.
The feature set for each of the above modes is :
voipSwitching - VoIP mode. In this mode VISM interacts
with the Call Agent using XGCP protocol,
bearer path is VoIP (AAL5). This mode is also
used for VoIP applications that dosen't use
call agent. (VoIP Trunking)
aal2Trunking - AAL2 Trunking mode. In this mode VISM does not
interact with the Call Agent. Bearer Path is AAL2.
aal1Svc - AAL1 SVC mode. In this mode VISM interacts with
Call Agent using XGCP protocol over AAL5 control
PVCs. In this mode, bearer path is VoAAL1 and the
bearer connections are SVCs. i.e VISM dynamically
sets-up and tears down bearer connections. This
value is applicable in VISM2.0 and onwards.
switchedVoipCASBh, switchedVoipPRIBh, switchedAal2CASBh,
switchedAal2Svc and superMode are ignored.
switchedAal2Pvc - Switched and trunked AAL2 PVC with CAS xGCP
backhaul, CCS and CAS forwarding.
switchedAal2Svc - Switched AAL2 SVC with PRI backhaul.
voipAndAal1Svc - VoIP and ATM Groomer.
unknowMode - Unknown mode, when user change vismFeatureBitMap
to a combination of Features that are not in
the above modes.
This object has to be synchronized with vismFeatureBitMap.
When vismFeatureBitMag is changed this object will be implictly
set to the mode that has the right combination of features.
From Indiana release and onwards, when user change mode VISM
card is not reset and the configuration is not cleared.ro Enumeration .1.3.6.1.4.1.351.110.3.17.4.5 |
vismPrevModeThis attribute indicates the mode in which VISM was operating
before the vismMode value was changed. i.e It gives the value
of vismMode before it got changed to the current value.
When the card comes up in the default mode, the value of
vismPrevMode will be the same as vismMode.
From Indiana release and onwards, when user change mode VISM
card is not reset and the configuration is not cleared.
Therefore we don't need this object anymore.rodeprecated Enumeration .1.3.6.1.4.1.351.110.3.17.4.6 |
vismCacEnableThis attribute describes whether CAC (Connection Admission Control)
functionality needs to be applied on the VISM card, on a per PVC
basis. For some applications, the CAC functionality may not be
required and in that case, it has to be disabled on a card basis.rw Enumeration .1.3.6.1.4.1.351.110.3.17.4.7 |
vismAvailableDs0CountThis attribute describes the no. of DS0s available for new
connections on VISM. This is modified by the VISM firmware
after each connection is setup.
In indiana release the number of connections has been
increased to 248, as the number of endpoints supported has
been increased.ro INTEGER .1.3.6.1.4.1.351.110.3.17.4.8 |
vismAppliedTemplateThis attribute describes the Codec template currently configured
on the VISM card. The value refers to an index to the
vismCodecTemplate table. This template is applicable for all
connections on the card.
When a switch is made to a new template, the number of channels
(endpoints) in use will be checked to ensure the switch will not
occur if there are more endpoints active at the present time than
what the new template (vismCodecTemplateMaxChanCount) allows.
Also whenever an attempt is made to add a new endpoint for any
template, this template maximum number will limit the number of
endpoints that may be added for this template.ro INTEGER .1.3.6.1.4.1.351.110.3.17.4.9 |
vismTftpServerDnThis object holds the domain name of the tftp server from where
the cas module will download the cas files.
This domain name can be resolved internally or externally.
Before configuring this object the domain name should be added
in the mgDomainNameTable and at least one Ip address (internal
or external) should be associated with this domain name in
mgcResolutionTable.
By default, the object is set to TFTPDOMAIN.
Before the last entry corresponding to the tftp domain is deleted
from the mgDomainNameTable or the last Ip address associated with
this object is deleted from mgcResolutionTable, it should be set
to 'TFTPDOMAIN'.
If the user configures 'localhost' to be the tftp server domain
then the cas files will be downloaded from PXM.
If the user configures the domain name to be TFTPDOMIAN or
localhost then that entry need not be present in
mgDomainNameTable or mgcResolutionTable.rw DisplayString .1.3.6.1.4.1.351.110.3.17.4.11 |
vismXgcpBearerNetworkTypeThis object specifies the network type to use in order to transport
bearer traffic.
The user can configure this to IP or ATM based on where the VISM
will be located.
If the call agent specifies the network type in the MGCP local
connection options (CRCX request), then the configuration of
this object will have no effect, else the value of this object
will be used when sending CRCX response.
This object is applicable only from vism 2.0.3 release onwards.rw Enumeration .1.3.6.1.4.1.351.110.3.17.4.12 |
vismXgcpBearerVCTypeThis object specifies the vc type to use in order to transport bearer
traffic.
If the call agent specifies the VC type in the MGCP local
connection options (CRCX request), then the configuration of this
object will have no effect, else the value of this object will be
used when sending CRCX response.
This object is applicable only from vism 2.0.3 release onwards.rw Enumeration .1.3.6.1.4.1.351.110.3.17.4.13 |
vismXgcpBearerConnectionTypeThis object specifies the connection type used to transport
bearer traffic. If the BearerNetworkType is chosen to be IP
then the value of this object has to be/will be set to not-applicable.
If the call agent specifies the connection type in the MGCP local
connection options (CRCX request), then the configuration of this
object will have no effect, else the value of this object will be
used when sending CRCX response.
This object is applicable only from vism2.0.3 release onwards.rw Enumeration .1.3.6.1.4.1.351.110.3.17.4.14 |
vismBearerContinuityTimerThis object specifies the co4 (bearer continuity) timer in
millisecs.
The timer will be started in the terminating/orginating
gateway for a duration as specified in this MIB object when a
co3 message is sent from the terminating/orginating gateway to the
originating/terminating gateway.
If the terminating/originating gateway does not receive co4 as an
acknowledgement from the originating/termintaing gateway and the timer expires,
gateway initiated DLCX is sent to the call agent from the terminating/originating
gateway.
This object is applicable when the call agent feature is available.rw INTEGER (0 .. 10000) .1.3.6.1.4.1.351.110.3.17.4.15 |
vismCodecNegotiationOptionThis object helps in forming an ordered intersection
of lists and one of the lists must be used in determining
the resulting order of codecs.
Lco - local connection options
Rcd - remote connection description
Lcl - local codec list
If the value of this object is 1 then effectively
we are giving first priority to the local connection options
sent by the Call Agent, followed by remote connection
description sent by the remote gateway (CA) and the last
priority will be to local codec list stored in vism.
If the value of this object is 2 then effectively we are
giving first priority to local connection options sent
by the call agent, followed by local codec list stored
in vism and the last priority will be to remote connection
description sent by the remote gateway (or remote CA).
If the value of this object is 3 then effectively we are
giving first priority to remote connection description sent
by the remote gateway /call agent, followed by local
connection options sent by the call agent and the last priority
will be to the local codec list stored on the local gateway(vism).
If the value of this object is 4 then effectively we are
giving first priority to remote connection description sent
by the remote gateway/CA followed by local codec list stored
on the local gateway and the last priority will be to the local
connection options sent by the CA.
If the value of this object is 5 then effectively we are
giving first priority to local codec list stored on the
local gateway (vism) followed by local connection options
sent by the call agent and the last priority will be
to remote connection description sent by the remote gateway
(or remote CA).
If the value of this object is 6 then effectively we are
giving first priority to local codec list stored on the
vism followed by remote connection description sent by the
remote gateway (or remote CA) and the last priority will be to
local connection options sent by the call agent.rw Enumeration .1.3.6.1.4.1.351.110.3.17.4.16 |
vismProfileNegotiationOptionThis object helps in forming an ordered intersection
of lists and one of the lists must be used in determining
the resulting order of profiles.
Lco - local connection options
Rcd - remote connection description
Lcl - local codec list
If the value of this object is 1 then effectively
we are giving first priority to the local connection options
sent by the Call Agent, followed by remote connection
description sent by the remote gateway (CA) and the last
priority will be to local codec list stored in vism.
If the value of this object is 2 then effectively we are
giving first priority to local connection options sent
by the call agent, followed by local codec list stored
in vism and the last priority will be to remote connection
description sent by the remote gateway (or remote CA).
If the value of this object is 3 then effectively we are
giving first priority to remote connection description sent
by the remote gateway /call agent, followed by local
connection options sent by the call agent and the last priority
will be to the local codec list stored on the local gateway(vism).
If the value of this object is 4 then effectively we are
giving first priority to remote connection description sent
by the remote gateway/CA followed by local codec list stored
on the local gateway and the last priority will be to the local
connection options sent by the CA.
If the value of this object is 5 then effectively we are
giving first priority to local codec list stored on the
local gateway (vism) followed by local connection options
sent by the call agent and the last priority will be
to remote connection description sent by the remote gateway
(or remote CA).
If the value of this object is 6 then effectively we are
giving first priority to local codec list stored on the
vism followed by remote connection description sent by the
remote gateway (or remote CA) and the last priority will be to
local connection options sent by the call agent.rw Enumeration .1.3.6.1.4.1.351.110.3.17.4.17 |
vismCarrierLossPolicyThis object defines the policy that needs to be applied
when a carrier loss is detected.
This states whether to switch to the pre-upspeed codec or
to remain with the upspeed codec.
This object is applicable in case of SVCs. This object
will be applicable in case of PVC if the per PVC object -
vismChanCarrierLossPolicy (defined in vismChanCacTable)
is set to 'unspecified'.
Configuring this object will not have any affect when
card level cac is disabled (vismCacEnable).rw Enumeration .1.3.6.1.4.1.351.110.3.17.4.18 |
vismCacRejectionPolicyThis attribute defines the policy that needs to be applied
once the CAC function rejects the upspeeding of a connection,
due to a fax/modem switch-over request. The applicable options
are:
1 - To delete the connection that got rejected by CAC for upspeed
2 - To maintain the connection with the prior compression scheme.
This object is applicable in case of SVCs . This object will be
applicable in case of PVCs if the per PVC object -
vismChanCacRejectionPolicy (defined in vismChanCacTable) is set to
'unspecified'.
Configuring this object will not have any affect when
card level cac is disabled (vismCacEnable).rw Enumeration .1.3.6.1.4.1.351.110.3.17.4.19 |
vismExtDnsServerDnThis object refers to the domain name of the external DNS server
which will be used to resolve other domain name.
Currently this domain name can only be resolved internally.
Therefore, before configuring this object not only
the domain name has to be added in the mgDomainNameTable with
resolution type 'internalOnly' but also at least one IP address
has been added with this domain name in mgcResolutionTable.
Before deleting external DNS server from mgDomainNameTable or
deleting the last IP address associated with the external DNS
server this object should be set to 'NULL'. After we change
the value of this object to NULL, all the externally resolved
IP address in mgcResolutionTable will be purged.
By default this object will be set to 'NULL'.rw DisplayString .1.3.6.1.4.1.351.110.3.17.4.20 |
vismFeatureBitMapThis object denotes the bit map for VISM features. It indicates
the current features that are enabled. It should be consistant
with vismMode. When user change vismMode, this object is
implicitly set to the feature combination that inidicate to
that mode. The change of vismFeatureBitMap will not cause VISM
to reset and the configuration will not be cleared.
For each bit, value 1 means the feature is enabled, 0 means
disabled.
Bit 0 - AAL1 adaptation
Bit 1 - AAL2 adaptation
Bit 2 - AAL5 adaptation (Bearer network type is IP).
Bit 3 - Switching (with Call Agent)
Bit 4 - Trunking (without Call Agent)
Bit 5 - Bearer VC type is PVC.
Bit 6 - Bearer VC type is SVC.
Bit 7 - CAS signaling
Bit 8 - PRI backhaul
Bit 9 - CCS signaling
Bit 10 - Domain Name
For example, 0x5AC corresponds to vismMode 1 (VoipSwitching).
Currently this object is not settable, it can only be set thru
some debug commands.rw INTEGER .1.3.6.1.4.1.351.110.3.17.4.21 |
vismVADToleranceThe value in this object refers to the customer accepted
drop rate for voice connections when the bandwidth usage
exceeds allowed value.
The actual range of this object is 0.0001% - 1.00 %
The unit is in percentage, since the default is 0.01 %,
and since we cannot express such fractions
in MIB , it is being multiplied by 10000 .
However, when the underlying CAC module is notified of
the change in this object, then the value
has to be divided by a factor of 10000.
Multiplication factor 10000 is picked as someone might be
interested in a tolerance as low as 0.0001%.
This object will be applicable in case of aal2 SVCs where
the user does not add a PVC and also this object will be
applicable if the per PVC level object (vismChanVADTolerance)
is configured to have a value of zero.
Configuring this object will not have any affect when
card level cac is disabled (vismCacEnable).rw INTEGER .1.3.6.1.4.1.351.110.3.17.4.22 |
vismVADDutyCycleThis object refers to the talk-spurts duty cycle.
The unit is in percentage.
When the value of this object is to be passed
to underlying CAC module in VISM this value has to
be divided by 100.
This causes the actual range of this object to be
0.01 to 0.99 and not 0.01 to 1.00 as specified in
the range of values above. Since a value of 100
will cause a floating point exception, this value
is disallowed.
The default value is 0.61 and since we cannot
have fractions in a MIB variable the value
is being multiplied by 100 and is expressed as
61.
This object will be applicable in case of aal2 SVCs where
the user does not add a PVC and also this object will be
applicable if the per PVC level object (vismChanVADDutyCycle)
is configured to have a value of zero.
Configuring this object will not have any affect when
card level cac is disabled (vismCacEnable).rw INTEGER .1.3.6.1.4.1.351.110.3.17.4.23 |
vismAggregateTrafficClippingThis attribute defines the aggregate traffic clipping policy
which is applicable to all bearer traffic generated at VISM card.
The applicable options are:
1 - aggregate traffic clipping is disabled, VISM card traffic
management does not perform aggregate traffic clipping.
2 - aggregate traffic clipping is enabled, VISM card traffic
management performs aggregate traffic clipping.
This is applicable to only AAL2 SVC voice bearer traffic.
When aggregate traffic clipping is enabled, VISM card can discard cells
which are exceeding VISM card aggregate SVC bandwidth which is specified
as vismAggregateSvcBandwidth value.rw Enumeration .1.3.6.1.4.1.351.110.3.17.4.24 |
vismAggregateSvcBandwidthThe aggregate svc bandwidth is used for AAL2 SVC aggregate SVC
Connection Admision Control and also used for aggregate traffic
clipping at VISM card when vismAggregateTrafficClipping is enabled.
This is expressed in cells per second. This need to be configured
for AAL2 SVC aggregate bandwidth call admision control to admit
AAL2 SVC connections at VISM card.rw INTEGER .1.3.6.1.4.1.351.110.3.17.4.25 |
vismBearerContinuityTestThis attribute defines whether the bearer continuity test for a connection
will be performed at the time of call setup or not.
When the vismBearerContinuityTest is enabled, the terminating media Gateway
initiates a NSE/type 3 packet towards the originating gateway and
starts a timer defined by vismBearerContinuityTimer.
The originating gateway, on receipt of co3, responds by sending a co4
to the terminating end.
If the terminating gateway doesn't receive co4 NSE/type 3 packet with in
the time defined by co4 timer, it initiates a GW-initiated DLCX to the call
agent which in turn deletes the connection.
The value in this object will be utilised when the Call Agent does not
specify this.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.351.110.3.17.4.26 |
vismCaleaEnableThis attribute describes whether CALEA (Communication
Assistance for Law Enforcement Agency)) functionality needs
to be enabled on the VISM card. This attribute enables/disables
this feature at a card level. This command is only applicable
for CALEA enable image.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.351.110.3.17.4.27 |
vismTrapObjGrp OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.3.17.5 |
vismConfigChangeTypeBitMapConfiguration change Type BitMap used in vismTableChanged
trap and vismScalarChanged trap.
When used in vismTableChanged trap, the bits indicate the following:
bit 0 set = mgcTable changed
bit 1 set = mgEndpointTable changed
bit 2 set = mgcResolutionTable changed
bit 3 set = srcpPeerTable changed
bit 4 set = vismDsx1Table changed
bit 5 set = vismXgcpPeerTable changed
bit 6 set = xgcpPackageTable changed
bit 7 set = vismChanCacTable changed
bit 8 set = vismCasVariantTable changed
bit 9 set = vismCasXgcpVariantTable changed
bit 10 set = vismAal2CidCnfTable changed
bit 11 set = dsx0VismCnfTable changed
bit 12 set = vismHdlcChanCnfTable changed
bit 13 set = lineAssignmentTable changed
bit 14 set = vismCodecCnfTable changed
bit 15 set = vismLapdTable changed
bit 16 set = vismRudpSessionCnfTable changed
bit 17 set = aal2ProfilesGrpTable changed
bit 18 set = mgDomainNameTable changed
bit 19 set = vismPortCnfGrpTable changed
bit 20 set = mgcRedundancyGrpTable changed
bit 21 set = mgcRedundancyGrpParamTable changed
bit 22 set = srcpPeerGrpParamTable changed
bit 23 set = vismRtpConnGrpTable changed
bit 24 set = vismCodecGenParmTable changed
bit 25 set = t38FaxRelayGrpTable changed
bit 26 set = mgcRedundancyProtocolTable changed
bit 27 set = vismSessionSetTable changed
bit 28 set = vismSessionGrpTable changed
When used in vismScalarChanged trap, the bits indicate the following:
bit 0 set = mediaGateway group changed
bit 1 set = mediaGatewayEndpoint group changed
bit 2 set = mediaGatewayControllerResolution group changed
bit 3 set = srcpAdminObjects group changed
bit 4 set = vismConfig group changed
bit 5 set = vismXgcpCoreObjects group changed
bit 6 set = xgcpCoreObjects group changed
bit 7 set = xgcpExtensionObjects group changed
bit 8 set = xgcpPackageObjects group changed
bit 9 set = vismSvcAtmQosGrp Objects group changed
bit 10 set = vismSvcTrfScalingGrp Objects group changed
bit 11 set = vismSvcAal2CidGrp Objects group changed
bit 12 set = srcpAdminRetryObjects Objects group changed
bit 13 set = vismConfig IpGrp group objects changed
bit 14 set = vismConfig VoipGrp group objects changed
bit 15 set = vismConfig DspGrp group objects changed
bit 16 set = vismConfig SystemGrp group objects changed
bit 17 set = vismConfig Aal2Grp group objects changed
bit 18 set = vismConfig InteropGrp group objects changed
bit 19 set = announceControlGrp Objects group changed
bit 20 set = vismXgcpEnhancementsObjects group changed
default value is 0, no change
This MIB makes sense only in traps. A GET
on this may not return a Useful result.ro INTEGER .1.3.6.1.4.1.351.110.3.17.5.1 |
vismTrapIntIndex1This object is used only for the purpose of sending it in
the trap varbind. This object is used for two purposes:
1. When the integer index of a SMIv2 table has to be sent,
this object will be used instead of the actual index object.
The instance value of the object will be the instance value
of the actual index.
2. In the config change trap trapVismTableChange, to send the
index value of the table entry which got changed. This object
will contain the value of the first integer index.
The NMS applications should not depend on the implementation
of this object. The SNMP Requests(GET,GET-NEXT) may not be
valid for this object.ro INTEGER .1.3.6.1.4.1.351.110.3.17.5.2 |
vismTrapIntIndex2This object is used only for the purpose of sending it in
the trap varbind. This object is used for two purposes:
1. This object will be used when the SMIv2 table has two
index objects and the 2nd object is an integer. This object
will be used instead of the actual second index object. The
instance value of the object will be the instance value of
the actual second index.
2. In the config change trap trapVismTableChange, to send the
index value of the table entry which got changed. This object
will contain the value of the second integer index.
The NMS applications should not depend on the implementation
of this object. The SNMP Requests(GET,GET-NEXT) may not be
valid for this object.ro INTEGER .1.3.6.1.4.1.351.110.3.17.5.3 |
vismTrapStrIndex1This object is used only for the purpose of sending it in
the trap varbind. This object is used for two purposes:
1. When the OctetString index of a SMIv2 table has to be sent,
this object will be used instead of the actual index object.
The instance value of the object will be the instance value of
the actual index.
2. In the config change trap trapVismTableChange, to send the
index value of the table entry which got changed. This object
will contain the value of the first OctetString index.
The NMS applications should not depend on the implementation
of this object. The SNMP Requests(GET,GET-NEXT) may not be
valid for this object.ro OCTET STRING .1.3.6.1.4.1.351.110.3.17.5.4 |
vismAal2Grp OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.3.17.6 |
vismAal2SubcellMuxingThis object is a card level parameter for AAL2 adaptation and
it identifies the mutiplexing function of the AAL2 Common Part
Sublayer. When it is disabled then each CPS-Packet would fill
only one or two cells with padding. (Partial fill cells) Note
that the length field for each CPS-Packet can be up to 64bytes.
When this option is enabled then mutiple streams of CPS-Packets
are mutiplexed to a single ATM connection without partial fill
unless there is time-out. Refer to ITU-T I.363.2 for more
information.
When the muxing type changes if cids are present, then we need to
check for CAC voilation for all cids, if the CAC fails then the
change request will be rejected else the muxing status will be changed
and the vismAal2MuxingTrap will be sent and the card will be reset .
All the existing connecitons will come up in new muxing type.
when the muxing type changes while there are no cids then the
card will NOT be reset, but the vismAal2MuxingTrap will be sent.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.351.110.3.17.6.1 |
vismAal2DtmfRelayThis attribute defines whether the DTMF (Dual Tone Multi Frequency)
digits need to be transported to the other end-point or not.
The value in this object will be utilised when the Call Agent does
not specify this in CRCX.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.351.110.3.17.6.2 |
vismAal2CasTransportThis attribute defines whether the CAS (ABCD bits) bits need to be
transported to the other endpoint. In the case of switching application,
the CAS bits are backhauled to the Call Agent through xGCP-CAS protocol.
The value in this object will be utilised when the Call Agent does not
specify this in CRCX.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.351.110.3.17.6.3 |
vismAal2Type3RedundancyThis attribute defines whether the triple redundancy is supported
for type 3 packets in AAL2 SVC/PVC . When Triple redundancy is enabled ,
the type 3 packets (CAS bits, dialled digits and user state control
packets) are transmitted in triplicates with an interval defined as
per the standards I.366.2. For channels which are quite reliable,
triple redundancy can be disabled in order to save the
bandwidth and the processing overheads.
The value in this object will be utilised when the Call Agent does not
specify this in CRCX.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.351.110.3.17.6.4 |
vismAal2VADTimerThis attribute defines the hangover time for VAD in milliseconds.
Once the voice inactivity is detected, the gateway will wait for
this duration before activating silence suppression on an AAL2 SVC/PVC.
The value in this object will be utilised when the Call Agent does
not specify this in CRCX.rw INTEGER .1.3.6.1.4.1.351.110.3.17.6.5 |
vismAal2CidFillTimerThis attribute defines the time (millisecs) to wait for filling
up the cell when the next packet is not ready.
After waiting for the time configured in this object, the
cell will be sent out.
This timer has no effect when vismAal2SubcellMuxing is disabled.
This object is applicable only for aal2 adaptations.rw INTEGER .1.3.6.1.4.1.351.110.3.17.6.6 |
vismInteropGrp OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.3.17.7 |
vismXgcpSdpOstThis object is used to enable/disable building of s=,t=,o= lines
in SDP message.
If this object is set to 'enable' then it indicates that the o=, s=, t=
lines be built before sending SDP (Session Description Protocol),
if it set to 'disable' then it indicates that the o=,s=,t=
parameters need not be built for SDP.
where o field indicates the owner/creator and session identifier
s field indicates the session name
t field indicates the duration while a session is valid.rw Enumeration .1.3.6.1.4.1.351.110.3.17.7.1 |
vismDynamicPTThis object is used to enable / disable dynamic payload type
configuration on the VISM Card.rw Enumeration .1.3.6.1.4.1.351.110.3.17.7.2 |
smRasConfig OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.3.18 |
rasOamlpbkAllowedObject indicating whether RAS- OAM loopback test is enabled or
disabled for this card.rw Enumeration .1.3.6.1.4.1.351.110.3.18.1 |
rasOamlpbkFrequencyObject indicating the frequency in minutes in which RAS task sends
one OAM loopback cell per idle connection.rw INTEGER .1.3.6.1.4.1.351.110.3.18.2 |
rasOamLpbkInfo OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.3.19 |
chanPacketNumberEach trap will send status for 256 channels bitmapping the
status. This object identities the chunk of 256 channels. The channel
numbers for which the trap indicates the status is found as
chanPacketNumber * 256 + bitoffset + 16. This object cannot be set or
read.ro INTEGER .1.3.6.1.4.1.351.110.3.19.1 |
chanOAMstatus32Bit map indicating Ras_oam_lpbk test state of 32 channels from
chanPacketNumber * 256 + 16 to chanPacketNumber * 256 + 47
MSB represent lower channel and LSB represent higher channel
0 in bit position indicate lpbk test ok
1 in bit position indicate lpbk test failed
This object cannot be set or readro INTEGER .1.3.6.1.4.1.351.110.3.19.2 |
chanOAMstatus64Bit map indicating Ras_oam_lpbk test state of 32 channels from
chanPacketNumber * 256 + 48 to chanPacketNumber * 256 + 79
MSB represent lower channel and LSB represent higher channel
0 in bit position indicate lpbk test ok
1 in bit position indicate lpbk test failed
This object cannot be set or readro INTEGER .1.3.6.1.4.1.351.110.3.19.3 |
chanOAMstatus96Bit map indicating Ras_oam_lpbk test state of 32 channels from
chanPacketNumber * 256 + 80 to chanPacketNumber * 256 + 111
MSB represent lower channel and LSB represent higher channel
0 in bit position indicate lpbk test ok
1 in bit position indicate lpbk test failed
This object cannot be set or readro INTEGER .1.3.6.1.4.1.351.110.3.19.4 |
chanOAMstatus128Bit map indicating Ras_oam_lpbk test state of 32 channels from
chanPacketNumber * 256 + 112 to chanPacketNumber * 256 + 143
MSB represent lower channel and LSB represent higher channel
0 in bit position indicate lpbk test ok
1 in bit position indicate lpbk test failed
This object cannot be set or readro INTEGER .1.3.6.1.4.1.351.110.3.19.5 |
chanOAMstatus160Bit map indicating Ras_oam_lpbk test state of 32 channels from
chanPacketNumber * 256 + 144 to chanPacketNumber * 256 + 175
MSB represent lower channel and LSB represent higher channel
0 in bit position indicate lpbk test ok
1 in bit position indicate lpbk test failed
This object cannot be set or readro INTEGER .1.3.6.1.4.1.351.110.3.19.6 |
chanOAMstatus192Bit map indicating Ras_oam_lpbk test state of 32 channels from
chanPacketNumber * 256 + 176 to chanPacketNumber * 256 + 207
MSB represent lower channel and LSB represent higher channel
0 in bit position indicate lpbk test ok
1 in bit position indicate lpbk test failed
This object cannot be set or readro INTEGER .1.3.6.1.4.1.351.110.3.19.7 |
chanOAMstatus224Bit map indicating Ras_oam_lpbk test state of 32 channels from
chanPacketNumber * 256 + 208 to chanPacketNumber * 256 + 239
MSB represent lower channel and LSB represent higher channel
0 in bit position indicate lpbk test ok
1 in bit position indicate lpbk test failed
This object cannot be set or readro INTEGER .1.3.6.1.4.1.351.110.3.19.8 |
chanOAMstatus256Bit map indicating Ras_oam_lpbk test state of 32 channels from
chanPacketNumber * 256 + 240 to chanPacketNumber * 256 + 271
MSB represent lower channel and LSB represent higher channel
0 in bit position indicate lpbk test ok
1 in bit position indicate lpbk test failed
This object cannot be set or readro INTEGER .1.3.6.1.4.1.351.110.3.19.9 |
coreCardCommands OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.3.20 |
switchCoreCardA SwitchCC command either to invoke switchcc or take noAction
on the Core Card Setrw Enumeration .1.3.6.1.4.1.351.110.3.20.1 |
imaAutoRestartFeature OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.3.21 |
imaAutoRestartThis object allows the user to enable/disable the IMA
group auto-restart feature on IMA capable cards. The
effect of this object is card-wide.
A value of 1 disables the feature.
A value of 2 enables the feature.rw Enumeration .1.3.6.1.4.1.351.110.3.21.1 |
srmeCnfGrp OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.3.22 |
srmeCnfGrpTableThe SRME configuration table for bulk distribution of SRME lines. SEQUENCE OF SrmeCnfGrpEntry .1.3.6.1.4.1.351.110.3.22.1 |
srmeCnfGrpEntryan entry in the SRME Distribution configuration table SrmeCnfGrpEntry .1.3.6.1.4.1.351.110.3.22.1.1 |
srmeLineNumSelect SRME line number.
For OC3/STM1: SYNTAX INTEGER 1
There is no default value for this object.ro INTEGER .1.3.6.1.4.1.351.110.3.22.1.1.1 |
srmeStartVtNumThe start T1 or E1 number (virtual tributary) to be affected.
For OC3 with T1 tributaries: SYNTAX INTEGER (1 .. 84)
For STM1 with E1 tributaries: SYNTAX INTEGER (1 .. 63)
There is no default value for this object.ro INTEGER .1.3.6.1.4.1.351.110.3.22.1.1.2 |
srmeRowStatusCommand used to add, delete, or modify
one or more T1 or E1 mappings. Only the
srmeVtFramingType object can be modified once the
distribution link is added. To modify all other
objects, user should first delete the link and
add it again.
Default value is modify.rw Enumeration .1.3.6.1.4.1.351.110.3.22.1.1.3 |
srmeTargetSlotNumspecify the target slot number to be linked.
There is no default value for this object.
For MGX8x50: SRM01 services slots 1 - 6 and 9 - 14,
SRM02 services slots 17 - 22 and 25 - 30
For MGX8x30: service slots 3-6 and 10-13rw INTEGER .1.3.6.1.4.1.351.110.3.22.1.1.4 |
srmeTargetSlotLineNumSpecify the target slot's line to be linked.
0 means not assigned.
There is no default value for this object.rw INTEGER .1.3.6.1.4.1.351.110.3.22.1.1.5 |
srmeVtFramingTypeSpecifies the Framing Type of the target slot line.
This is applicable only if the target module is a
T1 Service Module and byte sync mapping is used on
SRME. Not applicable to E1 Service Modules.
sf: Superframe or D4
esf: Extended Superframe.
Default is esf if SRME lines are configured for byte-synchronous mapping.
Else, the default is notApplicable.rw Enumeration .1.3.6.1.4.1.351.110.3.22.1.1.6 |
serialInterface OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.4.1 |
serialInterfaceTableThis table represents Physical serial interfaces on the module SEQUENCE OF SerialInterfaceEntry .1.3.6.1.4.1.351.110.4.1.1 |
serialInterfaceEntryAn entry for the serial interface SerialInterfaceEntry .1.3.6.1.4.1.351.110.4.1.1.1 |
serialPortNumserial interface number
port 1. is always defined as debug port
port 2. on BSC can perform SLIP.ro INTEGER .1.3.6.1.4.1.351.110.4.1.1.1.1 |
serialPortTypeOn the BSC board IP stack is mounted on the manager port,
on the debug port dumb terminal can be connected
function of the ports cannot be changed, except for enabling
and disablingro Enumeration .1.3.6.1.4.1.351.110.4.1.1.1.2 |
serialPortEnableports can be enabled or diabledrw Enumeration .1.3.6.1.4.1.351.110.4.1.1.1.3 |
serialPortbpsbaud rate of the ports, each port can be config
differentrw Enumeration .1.3.6.1.4.1.351.110.4.1.1.1.4 |
serialPortNumOfValidEntriesNumber of rows in serialPortTable.
This number is equal to the number of serial ports on the module.ro INTEGER .1.3.6.1.4.1.351.110.4.1.2 |
ethernetInterface OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.4.2 |
ethernetPhysicaAddressethernet address stored in the BSC BRAM, entered by
manfacturing.ro DisplayString .1.3.6.1.4.1.351.110.4.2.1 |
x21CnfGrp OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.4.5.1 |
x21CnfGrpTableThe X21 Configuration table. The table size is
given by the value of x21LineNumofValidEntries SEQUENCE OF X21CnfGrpEntry .1.3.6.1.4.1.351.110.4.5.1.1 |
x21CnfGrpEntryAn entry in the X21 Configuration table. X21CnfGrpEntry .1.3.6.1.4.1.351.110.4.5.1.1.1 |
x21LineNumThis object is the identifier of a X.21 interface.
No defaults.
FRSM-HS2/HS2B-HSSI supports a range from 1 to 2
FRSM-HS2B-12IN1 supports a range from 1 to 8ro INTEGER .1.3.6.1.4.1.351.110.4.5.1.1.1.1 |
x21LineEnableThis variable disables, enables or modifies a line
1 - disable
2 - enable
3 - modify
Default is enable.rw Enumeration .1.3.6.1.4.1.351.110.4.5.1.1.1.2 |
x21LineTypeThis variable indicates the type X21 line type.
The line-type affects the clock
always provides the clock and DTE accepts it.
dteST is only applicable to V.35 interfaces
Default is DTE.rw Enumeration .1.3.6.1.4.1.351.110.4.5.1.1.1.3 |
x21LineRateThis variable configures the X.21/HSSI/V.35 line-rate.
Note that enumerations 51 through 108 are supported
only by FRSM-HS2/HS2B card.
default is r48Kbps on FRSM-HS2B-12IN1
default is r52Mbps on FRSM-HS2/HS2B-HSSIrw Enumeration .1.3.6.1.4.1.351.110.4.5.1.1.1.4 |
x21LineLoopbackCommandThis variable represents the loopback state
x21NoLoop
Not in the loopback state. Normal traffic can be sent
x21DiagnosticMetallicLoop
Loopbacks the line on the back-card towards the Network.
x21DiagnosticFrontcardLoop
Loopbacks the line on the frontcard toward the Network.
x21RemoteLoop
The remote NTU is in the loop back mode.
In this state, the FRSM-HS1 is sending the loopback
code to remote NTU.
Default is x21NoLoop.
Note: Before going into one of the loopbacks the state
should be x21NoLoop.rw Enumeration .1.3.6.1.4.1.351.110.4.5.1.1.1.5 |
x21LineSendCodeThis variable indicates what type of code is
being sent across the X.21/HSSI interface by the
device. The values mean:
x21NoCode: No loopback.
x21SendLoopACode:
Start sending Loop A code. Valid only if
the backcard is HSSI and the line-type is DTE.
This command loops the line module of the remote
device.
x21SendLoopBCode:
Start sending Loop B code. Valid only if the
backcard is HSSI and the line-type is DTE.
This command loops the digital section of the
remote device.
x21SendLocalLoopCode:
Start sending CCITT X.21 Loopback Type 3 code.
This is valid only if the backcard is X.21 type.
x21SendRemoteLoopCode:
Start sending CCITT X.21 Loopback Type 2 code.
This is valid only if the backcard is X.21 type.
x21SendUnLoopCode:
Sending a loopback termination request.
Valid for both HSSI and X.21 lines.
To execute any of the loop-codes the x21LineLoopbackCommand
should be set to x21RemoteLoop.
Once the x21SendUnLoopCode succeeds the x21LineLoopbackCommand
would transition back to x21NoLoop state.
Default is x21NoCode.rw Enumeration .1.3.6.1.4.1.351.110.4.5.1.1.1.6 |
x21LineLoopbackCodeDetectionEnable detection of line Loopback Codes.
In the current release, the loopback detection
is implemented only in HSSI DCE mode.
Default is codeDetectDisabled.rw Enumeration .1.3.6.1.4.1.351.110.4.5.1.1.1.7 |
x21ConnectorTypeback card type
This object is not used by FRSM-HS2/HS2Bro Enumeration .1.3.6.1.4.1.351.110.4.5.1.1.1.8 |
x21InvertClockThis object configures two options:
a) To invert the clock sent by HS1/HS2B with the TX data or not.
b) If DCE,to expect the receive clock looped back from DTE or not.
If DTE,to loop back the receive clock from DCE or not.
nonInvertedAndNotLooped(1)- a)=dont invert, b)=dont expect rcv clock/
dont loop rcv clock
invertedAndNotLooped(2) - a)=invert, b)=dont expect rcv clock/
dont loop rcv clock
nonInvertedAndLooped(3) - a)=dont invert, b)=expect rcv clock/
loop rcv clock
invertedAndLooped(4) - a)=invert, b)=expect rcv clock/
loop rcv clock
Enums 1 and 2 are applicable for X.21/HSSI/V.35 interfaces.
Enums 3 and 4 are applicable only for V.35.
Default for X.21/HSSI is nonInvertedAndNotLooped(1)
Default for V.35 is nonInvertedAndLooped(3)
This object is not used by FRSM-HS2/FRSM-HS2B-HSSI
This object is used by FRSM-HS2B-12IN1 and default
values are nonInvertedAndNotLooped(1) for X.21,
nonInvertedAndLooped(3) for V.35rw Enumeration .1.3.6.1.4.1.351.110.4.5.1.1.1.9 |
x21LineInterfaceTypeThis object indicates serial interface type.
Default is hssi.
This object is not is configurable in FRSM-HS2
and FRSM-HS2B-HSSI. It will be set hssi by
default for these cards
This object is configurable in FRSM-H2B-12IN1.
Default is v35rw Enumeration .1.3.6.1.4.1.351.110.4.5.1.1.1.10 |
x21ClkFrequencyThresholdThis object indicates user configurable percentage of
clock frequency, which is used by DTE clock monitoring
to declare clock rate out of bound alarm. This object
is valid only for X.21/v.35/HSSI DTE interfaces.
This object is supported by FRSM-HS2 and FRSM-HS2/Brw INTEGER .1.3.6.1.4.1.351.110.4.5.1.1.1.11 |
serialLineRateline rate for X.21/HSSI/V.35 interfaces
in bps. This object is supported only
by FRSM-HS2/B card, only multiples of
1000 are accepted.
Default is 48Kbps for X.21/V.35 interfaces
and 51840Kbps for HSSI interfacerw INTEGER .1.3.6.1.4.1.351.110.4.5.1.1.1.12 |
serialLineRateVariationThis object indicates line rate variation of
HSSI/X.21/V.35 DCE interfaces in ppm (parts
per million). i.e.
clock generated from DCE hardware interface =
(serialLineRate +/- (serialLineRateVariation
* 10^6)/ serialLineRate)
This object is supported only by FRSM-HS2/B cardro INTEGER .1.3.6.1.4.1.351.110.4.5.1.1.1.13 |
x21LineNumofValidEntriesThe number of X.21/HSSI configuration entries
(regardless of their current configuration) in
the x21ConfigTable table.ro INTEGER .1.3.6.1.4.1.351.110.4.5.1.2 |
x21AlmCnfGrp OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.4.5.2 |
x21AlmCnfGrpTableThe FRSM-HS1/HS2 interface alarm configuration table. SEQUENCE OF X21AlmCnfGrpEntry .1.3.6.1.4.1.351.110.4.5.2.1 |
x21AlmCnfGrpEntryAn entry in the X.21/HSSI Alarm Configuration table X21AlmCnfGrpEntry .1.3.6.1.4.1.351.110.4.5.2.1.1 |
x21AlmCnfLineNumX.21/HSSI line number.
No defaults.
FRSM-HS2/HS2B-HSSI supports a range from 1 to 2
FRSM-HS2B-12IN1 supports a range from 1 to 8rw INTEGER .1.3.6.1.4.1.351.110.4.5.2.1.1.1 |
x21SeverityThis variable is used to setup the severity of LOS or clock
mismatch alarm. Whenever the above condition arises, the
FRSM-HS1/HS2/HS2B will send the alarm with appropriate status.rw Enumeration .1.3.6.1.4.1.351.110.4.5.2.1.1.2 |
x21AlmGrp OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.4.5.3 |
x21AlmGrpTableThe X.21/HSSI interface alarm configuration table.
The size of table is given by the value of x21LineNum SEQUENCE OF X21AlmGrpEntry .1.3.6.1.4.1.351.110.4.5.3.1 |
x21AlmGrpEntryAn entry in the X21 Alarm table X21AlmGrpEntry .1.3.6.1.4.1.351.110.4.5.3.1.1 |
x21AlmLineNumThis object is the identifier (line number) of a X.21/HSSI
interface.
FRSM-HS2/HS2B-HSSI supports a range from 1 to 2
FRSM-HS2B-12IN1 supports a range from 1 to 8ro INTEGER .1.3.6.1.4.1.351.110.4.5.3.1.1.1 |
x21LineAlarmStateThis variable is a bitmap of the X21 Line ALarms
on the FRSM-HS1. A value of zero indicates no alarms.
Itemized below are the individual bits:
BitPosition Alarm
0 C/I signal is OFF (also used to indicate LOS)
1 Clock rate mismatch (used in DTE mode)
2 Internal Loopback (diagnostic loopback)
3 HSSI Local LoopA (line is in loopback)
4 HSSI Local LoopB (line is in loopback)
5 Remote Loopback (line is transmitting loopcodes)
6 For V35 DTE mode, DCD and CTS both are inactive
7 For V35 DCE mode, RTS is inactive
8 No cable attached to V35 backcard
9 Wrong cable attached to V35 backcard
If all the bit-states are 0s:
- line is not in alarm, or
- line not in loopback, or
- line is transmitting any loopback codes.ro INTEGER .1.3.6.1.4.1.351.110.4.5.3.1.1.2 |
x21LineEIAStatusIndicates the status of X.21/HSSI lines:
0x01
0x02
0x04ro INTEGER (0..'7'h) .1.3.6.1.4.1.351.110.4.5.3.1.1.3 |
x21AlarmClrButtonThis variable is used to clear all the alarms for the line.
1 = No action
2 = Clear alarmrw Enumeration .1.3.6.1.4.1.351.110.4.5.3.1.1.4 |
dsx0VismCnfTableThe entries in this table are created and deleted implicitly at the
time of adding and deleting the line. For every DS0 on a line, one
row will be created. SEQUENCE OF Dsx0VismCnfEntry .1.3.6.1.4.1.351.110.4.7.1 |
dsx0VismCnfEntryThis ds0 table contains both cas related
and non cas related parameters.
The non cas related parameters are applicable
accross all line signaling types, while the
following cas related parameters
are applicable only if the signaling type
of the line to which this ds0 belongs
is cas.
ds0IdleCode
ds0SeizedCode
ds0ReceivedCode
ds0CasVariantName
ds0CasCadenceOnTime
ds0CasCadenceOffTime
ds0InsertLocalCas
ds0LocalCasPattern
ds0CasParameterSource
ds0CasOnHookMinMakeTime
ds0CasOffHookMinMakeTime
ds0CasWinkMinMakeTime
ds0CasWinkMaxMakeTime
ds0CasWinkBreakTime
ds0CasGlareTime
ds0CasGaurdTime
ds0CasDelayImmedStart
ds0CasMinDelayDialTime
ds0CasMinStartDialTime
ds0CasFlashMinMakeTime
ds0CasFlashMaxMakeTime
ds0CasDirectionality
ds0CasGlarePolicy
ds0CasIncomingMgcpPackage
ds0CasOutgoingMgcpPackage
When the line signaling type changes from cas to non-cas and
vice versa, then the user will be forced to delete
endpoint/ccs channels associated with any ds0 on that line
When an endpoint is deleted the ds0CasVariantName associated
with that endpoint will also be implicitly deleted.
Other than that none of the above cas related parameters are
modified across line signaling type changes. Dsx0VismCnfEntry .1.3.6.1.4.1.351.110.4.7.1.1 |
ds0IfIndexThis attribute defines the index for this table.
This is derived from the following formula:
index = 31 * (Ds1# - 1) + ds0#
where : Ds1# - The T1/E1 line number in the range 1 - 8.
ds0# - The ds0 channel number ranging from
1 to 24 for T1
and 1 to 31 for E1.ro INTEGER .1.3.6.1.4.1.351.110.4.7.1.1.1 |
ds0RobbedBitSignallingThis object indicates if Robbed Bit Signalling is
turned on or off for a given ds0. This only
applies to DS0s on a DS1 link. For E1 links the
value is always off (false). For T1 links, the default
value is true if the line is configured for CAS signaling,
the default value is false if the line is configured for
CCS signaling or no signaling.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.351.110.4.7.1.1.2 |
ds0IdleCodeThis object contains the code transmitted in the
ABCD bits when the ds0 is not connected and
ds0TransmitCodesEnable is enabled. The object is
a bitmap and the various bit positions are:
Bit 0 (value 1) D bit
Bit 1 (value 2) C bit
Bit 2 (value 4) B bit
Bit 3 (value 8) A bit
This object is useful for ds0 conditioning to be
done if an alarm condition is detected from the
network side. DS0 conditioning is implemented in
the trunking application only.
This object is not applicable in the CAS backhaul
application.
From vism 2.0.3 release onwards this object can
be configured in any mode, but will be applicable
only in trunking application and will be ignored
in other applications.rw INTEGER .1.3.6.1.4.1.351.110.4.7.1.1.3 |
ds0SeizedCodeThis object contains the code transmitted in the
ABCD bits when the ds0 is connected and
ds0TransmitCodesEnable is enabled. The object is
a bitmap and the various bit positions are:
Bit 0 (value 1) D bit
Bit 1 (value 2) C bit
Bit 2 (value 4) B bit
Bit 3 (value 8) A bit
This object is useful for ds0 conditioning to be
done if an alarm condition is detected from the
network side. DS0 conditioning is implemented in
the trunking application only.
This object is not applicable in the CAS backhaul
application.
From vism 2.0.3 release onwards this object can
be configured in any mode, but will be applicable
only in trunking application and will be ignored
in other applications.rw INTEGER .1.3.6.1.4.1.351.110.4.7.1.1.4 |
ds0ReceivedCodeThis object contains the code being received in
the ABCD bits. The object is a bitmap and the
various bit positions are:
Bit 0 (value 1) D bit
Bit 1 (value 2) C bit
Bit 2 (value 4) B bit
Bit 3 (value 8) A bitro INTEGER .1.3.6.1.4.1.351.110.4.7.1.1.5 |
ds0TransmitCodesEnableThis object determines if the idle and seized
codes are transmitted. If the value of this object
is true then the codes are transmitted.
This object is not applicable in the CAS backhaul
application.rodeprecated TruthValue (SNMPv2-TC) .1.3.6.1.4.1.351.110.4.7.1.1.6 |
ds0BundleMappedThis object indicates endpoint number as specified
by mgEndpointNumber of endpoint table.
If it is not associated with any endpoint, then it
is set to -1.
It should be noted that the endpoint is associated
with bearer DS0s only. For signaling channel or DS0
as in the case of CCS channel, there is no endpoint
number associated with it and the value is set to -1.ro INTEGER .1.3.6.1.4.1.351.110.4.7.1.1.7 |
ds0IfTypeThis object indicates the interface type associated
with the ds0.
ds0 ifType is considered as bearer if it the DS0 is
used for carrying voice traffic.
ds0 ifType is considered as ccs-signaling, if the DS0
is configured as the D-channelro Enumeration .1.3.6.1.4.1.351.110.4.7.1.1.8 |
ds0CasVariantNameThis object indicates the index to the CAS variant
table. This parameter can be configured after configuring
this ds0 as an endpoint. This object cannot be modified
while connections exist on this endpoint. The CAS variant
table is used for configuring the system parameters associated
with various types of CAS signaling methods supported
on VISM.rw DisplayString .1.3.6.1.4.1.351.110.4.7.1.1.9 |
ds0CasCadenceOnTimeThis attribute describes the duration during which the digit
tone is generated.
This object is applicable only for CAS backhaul applications.
For trunking application it is not applicable.
The value is expresssed in units of milliseconds.
From vism2.0.3 release onwards this object can
configured in any application, but will be applicable
only in non-trunking applications and will be ignored
in other applications.rw INTEGER .1.3.6.1.4.1.351.110.4.7.1.1.10 |
ds0CasCadenceOffTimeThis attribute corresponds to the silence between the
digit tones.
This object is applicable only for CAS backhaul applications.
For trunking application it is not applicable.
The value is expresssed in units of milliseconds.
From vism2.0.3 release onwards this object can
configured in any application, but will be applicable
only in non-trunking applications and will be ignored
in other applications.rw INTEGER .1.3.6.1.4.1.351.110.4.7.1.1.11 |
ds0InsertLocalCasThis object tells the framer whether to force the cas bits
to a value defined by ds0LocalCasPattern or not.
If this is enabled the framer will force the cas (ABCD) bits
to a value defined in ds0LocalCasPattern by ignorning the
cas bits sent by DSP. Else the framer will transmit the cas
bits sent by DSP.
Setting of this object is not allowed when the signaling type
of this line is cas.
Also setting of this object is not allowed when the
ds0LoopbackCommand is set to RemoteLoop, because in this
situation we are suppose to loopback whatever comes from
the TDM side and not force the cas bits to something else.
This object can be set only if the line type is T1.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.351.110.4.7.1.1.12 |
ds0LocalCasPatternThis object contains the pattern that the cas (ABCD) bits will have
when ds0InsertLocalCas is enabled.rw INTEGER .1.3.6.1.4.1.351.110.4.7.1.1.13 |
ds0LoopbackCommandThis object represents the loopback type at the ds0 level.The
ds0 configuration overrides the line level configuration.
NoLoop
There is no loopback on this ds0.
LocalLoop
The data received from the ATM side is loopedback
to the ATM side.
RemoteLoop
The data from the TDM side is looped back to the
TDM side.
Setting of this object to RemoteLoop will not be allowed when
insert local cas for this ds0 (ds0InsertLocalCas object) is
enabled as we are suppose to force the cas bits to the pattern
configured in ds0LocalCasPattern, and not do loopback on the TDM side.rw Enumeration .1.3.6.1.4.1.351.110.4.7.1.1.14 |
ds0CasParameterSourceThis object indicates VISM whether to read the cas related
timer parameters from the casAppl file downloaded for that
endpoint or to read from this mib.
This gives the flexibility of configuring
different cas related timer values for different
endpoints associated with the same cas variant.
This object cannot be configured if the signaling
type for the line to which this ds0 belongs is non cas.
For a cas line this object CAN only be configured
only after associating this ds0 with an endpoint.rw Enumeration .1.3.6.1.4.1.351.110.4.7.1.1.15 |
ds0CasOnHookMinMakeTimeThis indicates the the minimum time in msecs
for which the on hook pattern should be present in order for it
to be recognised else the signal will be considered to be a
spurious signal and will be ignored.
This object cannot be configured if the signaling
type for the line to which this ds0 belongs is non cas.
For a cas line this object CAN only be configured
only after associating this ds0 with an endpoint.
This object will be applicable if ds0CasParameterSource
has a value of mibValue (2).
The allowed range for this object is 10..1000rw INTEGER .1.3.6.1.4.1.351.110.4.7.1.1.16 |
ds0CasOffHookMinMakeTimeThis indicates the minimum time in msecs for
which the off hook pattern should be present in order for it to be
recognised else the signal will be considered to be a spurious signal
and will be ignored.
This object cannot be configured if the signaling
type for the line to which this ds0 belongs is non cas.
For a cas line this object CAN only be configured
only after associating this ds0 with an endpoint
This object will be applicable if ds0CasParameterSource
has a value of mibValue (2).
The allowed range for this object is 10..1000rw INTEGER .1.3.6.1.4.1.351.110.4.7.1.1.17 |
ds0CasWinkMinMakeTimeThe wink consists of off-hook A-B bit pattern, followed
by on-hook A-B bit pattern in timed sequence.
This object indicates the minimum duration for which
the off-hook part of wink signal should persist.
This object cannot be configured if the signaling
type for the line to which this ds0 belongs is non cas.
For a cas line this object CAN only be configured
only after associating this ds0 with an endpoint
This object will be applicable if ds0CasParameterSource
has a value of mibValue (2).
The allowed range for this object is 10..1000 and the
range is in msecs.rw INTEGER .1.3.6.1.4.1.351.110.4.7.1.1.18 |
ds0CasWinkMaxMakeTimeThe wink consists of off-hook A-B bit pattern, followed
by on-hook A-B bit pattern in timed sequence.
This object indicates the maximum duration for which the
off-hook part of the wink signal should persist, if it
exceeds this time limit the signal will be considered to
be spurious and will be ignored.
This object cannot be configured if the signaling
type for the line to which this ds0 belongs is non cas.
For a cas line this object CAN only be configured
only after associating this ds0 with an endpoint
This object will be applicable if ds0CasParameterSource
has a value of mibValue (2).
The allowed range for this object is 10..3000 and the units
is in msecs.
This object should be greater than or equal to ds0CasWinkMinMakeTimerw INTEGER .1.3.6.1.4.1.351.110.4.7.1.1.19 |
ds0CasWinkBreakTimeThe wink consists of off-hook A-B bit pattern, followed
by on-hook A-B bit pattern in timed sequence.
This object indicates the minimum
duration for which the on-hook part of wink signal should persist.
This object cannot be configured if the signaling
type for the line to which this ds0 belongs is non cas.
For a cas line this object CAN only be configured
only after associating this ds0 with an endpoint
This object will be applicable if ds0CasParameterSource
has a value of mibValue (2).
The allowed range for this object is 10..1000 and the units.
is in msecs.rw INTEGER .1.3.6.1.4.1.351.110.4.7.1.1.20 |
ds0CasGlareTimeWhen the terminating gateway receives off Hook event
from the Call Agent it starts the timer specified in
this object to see if the terminating side is also
trying to originate a call. If this is true, we have
a 'glare' condition. The way glare is resolved is
thru this user programmable timer, we will not honor
any off hook events from the originating PBX during
this time.
This object cannot be configured if the signaling
type for the line to which this ds0 belongs is non CAS.
For a CAS line this object can only be configured
only after associating this ds0 with an endpoint
This object will be applicable if ds0CasParameterSource
has a value of mibValue (2).
The allowed range for this object is 10..10000 and the units
is in msecs.rw INTEGER .1.3.6.1.4.1.351.110.4.7.1.1.21 |
ds0CasGaurdTimeThe gaurd time is the duration between the end of one call
and the start of next call. This object specifies what should
be such a duration. All state changes from the PBX are ignored
for this duration. After receiving DLCX, this timer will be
started for a period as configured in this object, and will
not honor any off-hook events before the expiration of this timer.
This object cannot be configured if the signaling
type for the line to which this ds0 belongs is non cas.
For a cas line this object CAN only be configured
only after associating this ds0 with an endpoint
This object will be applicable if ds0CasParameterSource
has a value of mibValue (2).
The allowed range for this object is 10..1000 and the units
is in msecs.rw INTEGER .1.3.6.1.4.1.351.110.4.7.1.1.22 |
ds0CasDelayImmedStartThis timer indicates the time that VISM should wait before
outpulsing digits to the PBX after sending an off hook event.
This applies only to immediate start protocol.
This object cannot be configured if the signaling
type for the line to which this ds0 belongs is non cas.
For a cas line this object CAN only be configured
only after associating this ds0 with an endpoint.
This object will be applicable if ds0CasParameterSource
has a value of mibValue (2).
The allowed range for this object is 10..1000 and the units
is in msecs.rw INTEGER .1.3.6.1.4.1.351.110.4.7.1.1.23 |
ds0SignalingTypeThis attribute indicates the type of signaling on the line
to which this ds0 belongs.
CAS - Channel Associated Signaling
CCS - Common Channel Signaling
none - no signaling used.
This object will be implicitly set to line signaling
type every time it changes.ro Enumeration .1.3.6.1.4.1.351.110.4.7.1.1.24 |
ds0CasMinDelayDialTimeThis is an object for an E & M signaling protocol like wink-start for
this ds0. The difference is that the address-control signal is different
from wink. The originating VISM, on receiving a seize (AB=11) from the PBX,
responds by sending the delay-dial (AB=11) signal back to the PBX. When
the originating VISM is ready to collect the digits, it sends a start-dial
(AB=00) signal. This operation is symmetric. So the terminating VISM, on
seizing a trunk, should receive AB=11 (as an ack that the trunk is
operational). Subsequently, when it receives the start signal (AB=00) from
the connected PBX, it should outpulse the digits. The rest of the operation
is similiar to wink-start.
The allowed range for this object is 100..1000 with units in milliseconds.
In delay-dial operation, the outgoing interface (this interface), after
sending a seize signal (AB = 11), waits for the delay-dial signal (AB = 11).
The delay-dial signal, apart from acknowledging the seize signal, tells this
interface that the connected equipment is not ready for the digits yet.
This object specifies the time in milliseconds, after which incoming
AB=11 will be interpreted by this interface as the delay-dial signal.
References: Generic Requirements, GR-506-CORE, Issue 1, June 1996,
Revision 1, November 1996,
LSSGR: Signaling for Analog Interfaces
Section 11.2.3 is about 'Delay-Dial Operation' (in general)
In particular, section 11.2.3.1 ([R11-21] is about these
timing requirements.rw INTEGER .1.3.6.1.4.1.351.110.4.7.1.1.25 |
ds0CasMinStartDialTimeThis is an object for an E & M signaling protocol like wink-start for
this ds0. The difference is that the address-control signal is different
from wink. The originating VISM, on receiving a seize (AB=11) from the PBX,
responds by sending the delay-dial (AB=11) signal back to the PBX. When
the originating VISM is ready to collect the digits, it sends a start-dial
(AB=00) signal. This operation is symmetric. So the terminating VISM, on
seizing a trunk, should receive AB=11 (as an ack that the trunk is
operational). Subsequently, when it receives the start signal (AB=00) from
the connected PBX, it should outpulse the digits. The rest of the operation
is similiar to wink-start.
The allowed range for this object is 70..1000 with units in milliseconds.
In delay-dial operation, the outgoing interface (this interface), after
receiving a delay-dial signal (AB=11) from the connected equipment, waits
for the start-dial signal (AB = 00) before sending the digits to the
connected equipment. The start-dial signal tells this interface that the
connected equipment is ready for the digits. This object specifies the
time in milliseconds, after which incoming AB=00 will be interpreted by
this interface as the start dial signal.
References: Generic Requirements, GR-506-CORE, Issue 1, June 1996,
Revision 1, November 1996,
LSSGR: Signaling for Analog Interfaces
Section 11.2.3 is about 'Delay-Dial Operation' (in general)
In particular, section 11.2.3.1 ([R11-22] and [R11-23]) is
about these timing requirements.rw INTEGER .1.3.6.1.4.1.351.110.4.7.1.1.26 |
ds0CasFlashMinMakeTimeFlash is a CAS signal generated by users to request special services. The
interpretation of the flash depends on the protocol in use. The signal itself
is an on-hook followed by an off-hook. This object specifies the minimum
duration for the signal to be recognized as a flash by VISM. This duration,
expressed in milliseconds, is defined as the elapsed time between the
off-to-on-hook transition followed by the on-to-off-hook transition.
If the on-hook duration is shorter than the value of this object, the signal
will be ignored.
This object cannot be configured if the signaling type for the line to which
this ds0 belongs is non-CAS. For a CAS line, this object can only be configured
after associating this ds0 with an endpoint. If no endpoint was added for this
Ds0, any configuration attempt will be rejected.
This object will be applicable if ds0CasParameterSource
has a value of mibvalue (2).
The allowed range for this object is 50..1550 (msec).rw INTEGER .1.3.6.1.4.1.351.110.4.7.1.1.27 |
ds0CasFlashMaxMakeTimeFlash is a CAS signal generated by users to request special services. The
interpretation of the flash depends on the protocol in use. The signal itself
is an on-hook followed by an off-hook. This object specifies the maximum
duration for the signal to be recognized as a flash by VISM. This duration,
expressed in milliseconds, is defined as the elapsed time between the
off-to-on-hook transition followed by the on-to-off-hook transition.
If the on-hook duration is longer than the value of this object, the signal
will be ignored.
This object cannot be configured if the signaling type for the line to which
this ds0 belongs is non-CAS.
For a CAS line, this object can only be configured after associating this ds0
with an endpoint. This means that if no endpoint was added for this Ds0,
any configuration set attempt will be rejected, but any get will be allowed.
This object will be applicable if ds0CasParameterSource
has a value of 'mibvalue'(2).
The allowed range for this object is 50..1550 (msec.) with the additional
requirement that the value of this object should be greater than or equal
to ds0CasFlashMinMakeTime.rw INTEGER .1.3.6.1.4.1.351.110.4.7.1.1.28 |
ds0CasDirectionalityThis object specifies the direction in which CAS calls will be accepted on
this endpoint. If this object is set to incoming, then calls from the
connected PBX will be accepted by VISM on this endpoint. If set to outgoing,
VISM will send calls towards the connected PBX and not accept calls from
the PBX. For VISM to both send and receive calls on this endpoint, this
object should be set to bidirectional. The main difference between
bidirectional and one-way trunks is the occurrence of glare. On bidirectional
trunks, since both VISM and the connected PBX can seize the endpoint at
approximately the same time, glare (dual seizure) is likely to occur.
The protocol assigned to a bidirectional endpoint should be capable of
detecting and resolving glare. Wink-start and delay-dial are examples of
protocols capable of glare handling and immediate-start, ground-start and
loop-start, of those that cannot.
This object cannot be configured if the signaling type for the line to which
this ds0 belongs is non-CAS.
For a CAS line, this object can only be configured after associating this ds0
with an endpoint. This means that if no endpoint was added for this Ds0,
any configuration set attempt will be rejected, but any get will be allowed.rw Enumeration .1.3.6.1.4.1.351.110.4.7.1.1.29 |
ds0CasGlarePolicyThis object specifies how a bidirectional endpoint should resolve glare.
This object will be used only if dsx0VismDirectionality of the endpoint is
bidirectional. When glare is detected, if this object is set to controlling,
VISM will wait for the connected PBX to assert on-hook. When the connected
PBX goes on-hook, VISM proceeds to dial the numbers out waits for answer.
If this object is set to releasing, VISM indicates the glare situation to
the Call Agent (as specified by the control protocol), prepares to collect
digits from the PBX and asserts on hook. The incoming call should go through.
If the CAS protocol assigned to the endpoint cannot detect glare or if it
cannot resolve glare according to the policy provisioned via this object,
this object will not be used.
This object cannot be configured if the signaling type for the line to which
this ds0 belongs is non-CAS.
For a CAS line, this object can only be configured after associating this ds0
with an endpoint. This means that if no endpoint was added for this Ds0,
any configuration set attempt will be rejected, but any get will be allowed.rw Enumeration .1.3.6.1.4.1.351.110.4.7.1.1.30 |
ds0CasIncomingMgcpPackageThis object, in conjunction with the card level persistentXgcpEventsTable,
controls how persistent CAS events (like seize, disconnect, etc) related
to an incoming call observed on this DS0 are notified to the Media
Gateway Controller (MGC).
At the card level, the persistentXgcpEventsTable allows MGCP package-event
combinations to be configured as persistent. For example, when L/hd is added
to the persistentXgcpEventsTable, the hook-down event in line package will be
notified to the MGC every time it is observed without the MGC requesting for
that event.
Since the same CAS event can map to different MGCP events under different
packages (eg. the CAS event 'seize' can be 'sup' in 'MS' package and 'hd'
in 'BL' package) and different lines could be running different packages at
a given time, there needs to be a per-DS0 object indicating what package
should be used while notifying CAS events observed on that DS0. This object,
ds0CasIncomingMgcpPackage specifies the package that will be used while
notifying CAS events observed on an incoming call on this DS0.
This object can be set to a package name from xgcpCapabilityPackageTable whose
xgcpCapabilityPackageEnable is true or the string 'basic' indicating that one
of the basic packages in that table (G, T, L, H, R, D or M) to which the
observed event belongs can be used.
This object is used only if the protocol is MGCP. If the notification is in
response to an RQNT, VISM uses the package (and event name) that the MGC used
to request the event regardless what this object is set to.
In the absence of an RQNT, the observed CAS event is encoded according to the
package that this object specifies. A 'seize' observed on the CAS signaling
channel on this DS0, for example is encoded as 'ms/sup' if this object is
set to 'ms', 'bl/hd' if this object is set to 'bl' or as 'L/hd' if this object is
set to 'basic'. If this package/event is present in persistentXgcpEventsTable,
a notification is generated, otherwise this event is discarded.
An attempt to set this object to a package name whose
xgcpCapabilityPackageEnable is false in xgcpCapabilityPackageTable will fail.
This object is used only if the ds0CasDirectionality is set to bidirectional
or incoming.rw DisplayString .1.3.6.1.4.1.351.110.4.7.1.1.31 |
ds0CasOutgoingMgcpPackageThis object, in conjunction with the card level persistentXgcpEventsTable,
controls how persistent CAS events (like answer, disconnect, etc) related
to an outgoing call observed on this DS0 are notified to the Media
Gateway Controller (MGC).
At the card level, the persistentXgcpEventsTable allows MGCP package-event
combinations to be configured as persistent. For example, when L/hd is added
to the persistentXgcpEventsTable, the hook-down event in line package will be
notified to the MGC every time it is observed without the MGC requesting for
that event.
Since the same CAS event can map to different MGCP events under different
packages (eg. the CAS event 'answer' can be 'ans' in 'MS' package and 'hd'
in 'BL' package) and different lines could be running different packages at
a given time, there needs to be a per-DS0 object indicating what package
should be used while notifying CAS events observed on that DS0. This object,
ds0CasOutgoingMgcpPackage specifies the package that will be used while
notifying CAS events observed on an outgoing call on this DS0.
This object can be set to a package name from xgcpCapabilityPackageTable whose
xgcpCapabilityPackageEnable is true or the string 'basic' indicating that one
of the basic packages in that table (G, T, L, H, R, D or M) to which the
observed event belongs can be used.
This object is used only if the protocol is MGCP. If the notification is in
response to an RQNT, VISM uses the package (and event name) that the MGC used
to request the event regardless what this object is set to.
In the absence of an RQNT, the observed CAS event is encoded according to the
package that this object specifies. An answer observed on the CAS signaling
channel on this DS0, for example is encoded as 'ms/ans' if this object is
set to 'ms', 'bl/hd' if this object is set to 'bl' or as 'L/hd' if this object is
set to 'basic'. If this package/event is present in persistentXgcpEventsTable,
a notification is generated, otherwise this event is discarded.
An attempt to set this object to a package name whose
xgcpCapabilityPackageEnable is false in xgcpCapabilityPackageTable will fail.
This object is used only if the ds0CasDirectionality is set to bidirectional
or outgoing.rw DisplayString .1.3.6.1.4.1.351.110.4.7.1.1.32 |
ds0InputGainThis object indicates the amount of gain inserted at the receiver
side of a ds0 channel, in dB (decibel) units. The default value
of this object is 0 dB.
The input gain settings only define a gain/loss relative
to the 0 dB setting. The absolute loss at the 0 dB setting could be
implementation dependent based on the desired network loss plan.
This object can be set when there are active call going on, and
in this case the new gain will take effective immediately. It can
also be set at both unbound endpoints and bound but non-active
endpoints.rw INTEGER (-6..14) .1.3.6.1.4.1.351.110.4.7.1.1.33 |
ds0OutputAttenuationThis object contains the amount of attenuation inserted
at the transmit side of a ds0 channel, in dB (decibel) units.
The output attenuation settings only define a loss relative to
0 dB setting. The absolute loss at the 0 dB setting could be
implementation dependent based on the desired network loss plan.
This object can be set when there are active call going on,
and in this case the new gain will take effective immediately.
It can also be set at both unbound endpoints and bound but
non-active endpoints.rw INTEGER .1.3.6.1.4.1.351.110.4.7.1.1.34 |
ds0MusicThresholdThe indicates Music On Hold Threshold in dBm. Based on this
value, VISM DSP will interprete the incoming signal from TDM side
as either silence or voice, and consequently turn on or off VAD.
This object can be set when there is active call going on at the
ds0 channel, and at both unbound endpoints and bound non-active
endpoints.rw INTEGER (-70..-30) .1.3.6.1.4.1.351.110.4.7.1.1.35 |
ds0SidPacketThis object specifies whether the Silence Indication Detection
(SID) packet should be generated when silence suppression is in
active mode. The SID packet indicates the noise level during
silence, which is used as a reference to generate comfort noise
on the other side of the gateway.
This object is used for VoIP only.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.351.110.4.7.1.1.36 |
dsx0VismChanMapTableThis table is created implicitly at the time of creating and deleting
the endpoints. This table provides the mapping information from a line
and channel to obtain an index for that channel. SEQUENCE OF Dsx0VismChanMapEntry .1.3.6.1.4.1.351.110.4.7.2 |
dsx0VismChanMapEntryPlease see the above description. Dsx0VismChanMapEntry .1.3.6.1.4.1.351.110.4.7.2.1 |
dsx1LineNumThis object describes the physical line number on
VISM card.ro INTEGER .1.3.6.1.4.1.351.110.4.7.2.1.1 |
ds0ChanNumThis object describes the ds0 number or channel number
within a T1 or E1 line.
The valid channel numbers are 1 to 24 for T1 line
and 1 - 31 for E1 line.ro INTEGER .1.3.6.1.4.1.351.110.4.7.2.1.2 |
ds0ChanMapIfIndexThis object describes the ifIndex derived based on the
line number and the channel number within the line according
to the formula:
IfIndex = 31 * (Ds1# - 1) + ds0#
where : Ds1# - The T1/E1 line number in the range 1 - 8.
ds0# - The ds0 channel number ranging from
1 to 24 for T1
and 1 to 31 for E1.ro INTEGER .1.3.6.1.4.1.351.110.4.7.2.1.3 |
frPortCnfPortGrp OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.5.1.1.1.1 |
frPortCnfPortGrpTableThe config table is for logical port interface.
In FRSM-VHS, there are upto 256 entries for FRSM-2CT3
card and 2 entries for FRSM-T3/E3/HS2/T3B/E3B/HS2B-HSSI
cards and 8 entries for FRSM-HS2B-12IN1 card.
For other cards, there are upto 192 entries (for 8 DS1s)
and upto 248 entries (for 8 E1s).
For FRSM12 cards:
There are upto 12 entries. When a new row is added to this
table, the corresponding row is created in ifTable. SEQUENCE OF FrPortCnfPortGrpEntry .1.3.6.1.4.1.351.110.5.1.1.1.1.1 |
frPortCnfPortGrpEntryAn entry for logical port FrPortCnfPortGrpEntry .1.3.6.1.4.1.351.110.5.1.1.1.1.1.1 |
portNumThis is logical port number.
If we have T1 card then the maximum port number is 192
and if we have E1 card the maximum port number can be 248.
For FRSM-2CT3 card, the maximum port number is 256 and
for unchannelized FRSM-VHS cards (FRSM-T3/E3/HS2/T3B/E3B/HS2B-HSSI),
the maximum port number is 2
For FRSM-HS2B-12IN1 card, the maximum port number is 8
For FRSM12 card:
The ifIndex of the port's corresponding row in ifTable.
Byte 3 = Chassis Number, Byte 2 = Slot Number,
Byte 1 & 0 = Encoded unique number for Port.ro INTEGER .1.3.6.1.4.1.351.110.5.1.1.1.1.1.1.1 |
portLineNumThis represents the line number
For FRSM12 card:
The ifIndex of the physical line on which this port
is provisioned.rw INTEGER .1.3.6.1.4.1.351.110.5.1.1.1.1.1.1.2 |
portRowStatusThis variable enables or modifies the port
1- add
2 - del
3 - mod
For FRSM12 card:
For Snmp GET operations, only mod is returned.rw Enumeration .1.3.6.1.4.1.351.110.5.1.1.1.1.1.1.3 |
portDs0ConfigBitMapThis respesents bit map of DS0s for a line which
are used to form this logical port. Bit 0
represents DS0-1.
This entry is not used for unchannelized FRSM-VHS/FRSM12 cards.
For these cases, this field carries a value of 'ffffff'h
always.rw INTEGER (0..'ffffff'h) .1.3.6.1.4.1.351.110.5.1.1.1.1.1.1.4 |
portDs0SpeedThis represents port speed of 64 or 56
1 - speed56k
2 - speed64k
3 - unUsed.
This field is not used for unchannelised FRSM-VHS (FRSM-2T3/
FRSM-2E3/FRSM-HS2/FRSM-T3B/FRSM-E3B/FRSM-HS2B) cards; in such
cards, the portDs0Speed field carries a value of 'unUsed' always.
For FRSM12 card:
This is set to 3 - unUsed.rw Enumeration .1.3.6.1.4.1.351.110.5.1.1.1.1.1.1.5 |
portFlagsBetweenFramesNumber of flags transmitted between FR frames
For FRSM12 card:
Only the values 1 to 8 are supported. The mapping is as follows:
MIB object value No. of HDLC flags inserted
1 1
2 2
3 4
4 8
5 16
6 32
7 64
8 128rw INTEGER .1.3.6.1.4.1.351.110.5.1.1.1.1.1.1.6 |
portEqueueServiceRatioNumber of times queue 1 is serviced
for every time queue 2 is serviced.
The value 0 is supported only by FRSM-VHS.
FRSM-VHS supports two different egress queue
servicing algorithms depending on the Egress
Qos Feature.
if EgrQosFeature is ENABLED, Weighted Fair
queueing algorithm will be used to select
one queue out of 4 data queues and this
object will be set to a default value of
0 in this case and this value cannot be
modified by user.
In case of EgrQosFeature being DISABLED,
this object will be set to a default value
of 1 and can be configured to user desired
value. This value will be used to decide
number of times High priority queue has
to be serviced for every time low priority
queue is serviced.
For FRSM12 card:
There is only one scheme of egress scheduling of COS queues
within ports, which uses only two COS queues for user data.
The scheduling scheme uses a pre-defined ratio to schedule
these COS queues on a given port. This object will be
used to decide number of times High priority queue
has to be serviced for every time low priority queue
is serviced.rw INTEGER .1.3.6.1.4.1.351.110.5.1.1.1.1.1.1.7 |
portSpeedConfigured speed of port in kbpsro INTEGER .1.3.6.1.4.1.351.110.5.1.1.1.1.1.1.8 |
portAdminused to up and down the port
For FRSM12 card:
This variable will be equivalent to ifAdminStatus of
of ifTable. The write-only is not used.rw Enumeration .1.3.6.1.4.1.351.110.5.1.1.1.1.1.1.9 |
portTypeThis represents port type
For FRSM12 card:
frFUNI not Applicable. For frame-relay the ifType is
frameRelayService(44) and for frame-forward it is
frForward(158).rw Enumeration .1.3.6.1.4.1.351.110.5.1.1.1.1.1.1.10 |
portSvcStatusThis represents SVC status
For FRSM12 card: Not Supportedrw Enumeration .1.3.6.1.4.1.351.110.5.1.1.1.1.1.1.11 |
portSvcInUseThis represents port svc in use
For FRSM12 card: Not Supportedrw Enumeration .1.3.6.1.4.1.351.110.5.1.1.1.1.1.1.12 |
portSvcShareLcnThis represents port type
For FRSM12 card: Not Supportedro Enumeration .1.3.6.1.4.1.351.110.5.1.1.1.1.1.1.13 |
portSvcLcnLowThis represents low end of reserved LCN for svc
For FRSM12 card: Not Supportedro INTEGER .1.3.6.1.4.1.351.110.5.1.1.1.1.1.1.14 |
portSvcLcnHighThis represents high end of reserved LCN for svc
For FRSM12 card: Not Supportedro INTEGER .1.3.6.1.4.1.351.110.5.1.1.1.1.1.1.15 |
portSvcDlciLowThis represents low end of reserved DLCI for svc
For FRSM12 card: Not Supportedro INTEGER .1.3.6.1.4.1.351.110.5.1.1.1.1.1.1.16 |
portSvcDlciHighThis represents high end of reserved DLCI for svc
For FRSM12 card: Not Supportedro INTEGER .1.3.6.1.4.1.351.110.5.1.1.1.1.1.1.17 |
portDeleteSvcsSetting this object to 1 indicates that all the SVC
connections on the given port has to be deleted
For FRSM12 card: Not Supportedrw Enumeration .1.3.6.1.4.1.351.110.5.1.1.1.1.1.1.18 |
portIngrSvcBandWThis represents Ingress Bandwidth reserve for SVC
For FRSM12 card: Not Supportedro INTEGER .1.3.6.1.4.1.351.110.5.1.1.1.1.1.1.19 |
portEgrSvcBandWThis represents Egress Bandwidth reserve for SVC
For FRSM12 card: Not Supportedro INTEGER .1.3.6.1.4.1.351.110.5.1.1.1.1.1.1.20 |
portBERTEnableThis variable enables BERT
For FRSM12 card: Not Supportedrw Enumeration .1.3.6.1.4.1.351.110.5.1.1.1.1.1.1.21 |
portEnhancedSIWThis variable enables/disables enhanced SIW feature. Enabling
this permits support for SIW translation of Appletalk. This
feature is currently supported only in the FRSM-VHS card.
For FRSM12 card: Not Supported
This object is not required in FRSM12 since Appletalk is
supported by default in FRF.8.1 and FRSM12 supports FRF.8.1rw Enumeration .1.3.6.1.4.1.351.110.5.1.1.1.1.1.1.22 |
portM32EgrQueueThreshThis represents the M32 logical port Egress Queue threshold in bytes.
Frames will not be queued until the number of bytes in the queue is
less than the threshold. The default value is 6000. Using a very low
value could under utilize the logical port.
This is supported in FRSM 8t1e1 and FRSM 4t1e1 Service Modules only.
For FRSM12 card: Not Supportedrw INTEGER .1.3.6.1.4.1.351.110.5.1.1.1.1.1.1.23 |
portHeaderLenThis object is added for FRSM12.
The value of this object identifies the Q.922
Address field length and DLCI length for this
UNI/NNI logical port.
This object is not applicable to MGX Release 1.x.rw Enumeration .1.3.6.1.4.1.351.110.5.1.1.1.1.1.1.24 |
portFrameChkSumTypeThis object is added for FRSM12.
The value of this object identifies the CRC Length
in the HDLC Packet. Applicable for FrameForwarding
ports only.
This object is not applicable to MGX Release 1.x.rw Enumeration .1.3.6.1.4.1.351.110.5.1.1.1.1.1.1.25 |
portFileIdThe ID of the SCT file that holds module specific configuration
parameters for this FR virtual interface.
This object is not applicable to MGX Release 1.x.rw INTEGER .1.3.6.1.4.1.351.110.5.1.1.1.1.1.1.26 |
portOverSubEnableThis object is added for FRSM12.
When this object is enabled the port will be allowed
to be over subscribed.
This object is not applicable to MGX Release 1.x.rw Enumeration .1.3.6.1.4.1.351.110.5.1.1.1.1.1.1.27 |
portsUsedLine1Each bits set represents a DS0 that is used by all the
logical ports defined so far for that DS1, the most significant
byte is invalid for DS1
This is for line 1ro INTEGER (0..'ffffff'h) .1.3.6.1.4.1.351.110.5.1.1.1.1.2 |
portsUsedLine2Each bits set represents a DS0 that is used by all the
logical ports defined so far for that DS1, the most significant
byte is invalid for DS1
This is for line 2ro INTEGER (0..'ffffff'h) .1.3.6.1.4.1.351.110.5.1.1.1.1.3 |
portsUsedLine3Each bits set represents a DS0 that is used by all the
logical ports defined so far for that DS1, the most significant
byte is invalid for DS1
This is for line 3ro INTEGER (0..'ffffff'h) .1.3.6.1.4.1.351.110.5.1.1.1.1.4 |
portsUsedLine4Each bits set represents a DS0 that is used by all the
logical ports defined so far for that DS1, the most significant
byte is invalid for DS1
This is for line 4ro INTEGER (0..'ffffff'h) .1.3.6.1.4.1.351.110.5.1.1.1.1.5 |
portNextAvailableThis variable contains the next UNUSED logical port number.
This number can be used in channel config table, the
portNextAvailable gets updated if the number gets
used to create a logical port.
A '0' indicates that no more ports are available.
For FRSM12 Card: Not Supportedro INTEGER .1.3.6.1.4.1.351.110.5.1.1.1.1.6 |
portsUsedLine5Each bits set represents a DS0 that is used by all the
logical ports defined so far for that DS1, the most significant
byte is invalid for DS1
This is for line 5ro INTEGER (0..'ffffff'h) .1.3.6.1.4.1.351.110.5.1.1.1.1.7 |
portsUsedLine6Each bits set represents a DS0 that is used by all the
logical ports defined so far for that DS1, the most significant
byte is invalid for DS1
This is for line 6ro INTEGER (0..'ffffff'h) .1.3.6.1.4.1.351.110.5.1.1.1.1.8 |
portsUsedLine7Each bits set represents a DS0 that is used by all the
logical ports defined so far for that DS1, the most significant
byte is invalid for DS1
This is for line 7ro INTEGER (0..'ffffff'h) .1.3.6.1.4.1.351.110.5.1.1.1.1.9 |
portsUsedLine8Each bits set represents a DS0 that is used by all the
logical ports defined so far for that DS1, the most significant
byte is invalid for DS1
This is for line 8ro INTEGER (0..'ffffff'h) .1.3.6.1.4.1.351.110.5.1.1.1.1.10 |
frPortsUsedLineGrpTableContains a sequence of entries for each DS1 line.
each entry gives the number of DS0 slots being used
added for FRSM_VHS SEQUENCE OF FrPortsUsedLineGrpEntry .1.3.6.1.4.1.351.110.5.1.1.1.1.11 |
frPortsUsedLineGrpEntryOne entry per DS1 FrPortsUsedLineGrpEntry .1.3.6.1.4.1.351.110.5.1.1.1.1.11.1 |
frPortsUsedLineIndexThis is the Index to the table containing the portsUsedLine
for the 56 DS1sro INTEGER .1.3.6.1.4.1.351.110.5.1.1.1.1.11.1.1 |
frPortsUsedLineEach bits set represents a DS0 that is used by all the
logical ports defined so far for that DS1, the most significant
byte is invalid for DS1ro INTEGER (0..'ffffff'h) .1.3.6.1.4.1.351.110.5.1.1.1.1.11.1.2 |
frPortCnfSigLMIGrp OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.5.1.1.1.2.1 |
frPortCnfSigLMIGrpTableThe config table is for logical port interface
there are upto 248 entries (8 E1s) and 192 entries (8 T1s).
In FRSM-VHS, there are a total of 256 entries.
In FRSM12, there are 12 entries. SEQUENCE OF FrPortCnfSigLMIGrpEntry .1.3.6.1.4.1.351.110.5.1.1.1.2.1.1 |
frPortCnfSigLMIGrpEntryAn entry for logical port FrPortCnfSigLMIGrpEntry .1.3.6.1.4.1.351.110.5.1.1.1.2.1.1.1 |
lmiCnfPortNumRefers to the logical port index
For FRSM12 card:
The ifIndex of the port's corresponding row in ifTable.
Byte 3 = Chassis Number, Byte 2 = Slot Number,
Byte 1 & 0 = Encoded unique number for Port.ro INTEGER .1.3.6.1.4.1.351.110.5.1.1.1.2.1.1.1.1 |
signallingProtocolTypeThis will set the signalling protocol
1 - other
2 - noSignalling
3 - strataLMI
4 - annexAUNI
5 - annexDUNI
6 - annexANNI
7 - annexDNNI
Only noSignalling is applicable to
frame forwarding ports
For FRSM12: strataLMI is not supported for portHeaderLen of fourOctets.rw Enumeration .1.3.6.1.4.1.351.110.5.1.1.1.2.1.1.1.2 |
asynchronousUpdatesdisable - disable Asynchronous Status Updates & Unsolicited Full Status
enable - enable Asynchronous Status Updates
fsenable - enable Unsolicited Full Status
updfsenable - enable Asynchronous Status Updates & Unsolicited Full Status
The signalling parameters are not applicable for
the frame forwarding port.rw Enumeration .1.3.6.1.4.1.351.110.5.1.1.1.2.1.1.1.3 |
t391LinkIntegrityTimerInterval in seconds for NNI to do status polling
The signalling parameters are not applicable for
the frame forwarding port.rw INTEGER .1.3.6.1.4.1.351.110.5.1.1.1.2.1.1.1.4 |
t392PollingVerificationTimerInterval in seconds for UNI to expect status polling
The signalling parameters are not applicable for
the frame forwarding port.rw INTEGER .1.3.6.1.4.1.351.110.5.1.1.1.2.1.1.1.5 |
n391FullStatusPollingCounterNumber of UNI/NNI Polling cycles
The signalling parameters are not applicable for
the frame forwarding port.rw INTEGER .1.3.6.1.4.1.351.110.5.1.1.1.2.1.1.1.6 |
n392ErrorThresholdUNI/NNI Error Threshold
The signalling parameters are not applicable for
the frame forwarding port.rw INTEGER .1.3.6.1.4.1.351.110.5.1.1.1.2.1.1.1.7 |
n393MonitoredEventCountUNI/NNI Events, always greater than n392
The signalling parameters are not applicable for
the frame forwarding port.rw INTEGER .1.3.6.1.4.1.351.110.5.1.1.1.2.1.1.1.8 |
enhancedLmiThis object defines if enhanced LMI is enabled on a
logical port.
The signalling parameters are not applicable for
the frame forwarding port.rw Enumeration .1.3.6.1.4.1.351.110.5.1.1.1.2.1.1.1.9 |
portFRF1Dot2SupportThis object is added for FRSM12.
This variable enables/disables FRF 1.2 feature.
This object is not applicable to MGX Release 1.xrw Enumeration .1.3.6.1.4.1.351.110.5.1.1.1.2.1.1.1.10 |
frPortCnfSigCLLMGrp OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.5.1.1.1.2.2 |
frPortCnfSigCLLMGrpTableThe config table is for logical port interface SEQUENCE OF FrPortCnfSigCLLMGrpEntry .1.3.6.1.4.1.351.110.5.1.1.1.2.2.1 |
frPortCnfSigCLLMGrpEntryAn entry for logical port FrPortCnfSigCLLMGrpEntry .1.3.6.1.4.1.351.110.5.1.1.1.2.2.1.1 |
cllmCnfPortNumRefers to the logical port index
For FRSM12 card:
The ifIndex of the port's corresponding row in ifTable.
Byte 3 = Chassis Number, Byte 2 = Slot Number,
Byte 1 & 0 = Encoded unique number for Port.ro INTEGER .1.3.6.1.4.1.351.110.5.1.1.1.2.2.1.1.1 |
cllmEnableThis will enable CLLM
1 - disabled
2 - enabled
CLLM is not applicable for frame forwarding portsrw Enumeration .1.3.6.1.4.1.351.110.5.1.1.1.2.2.1.1.2 |
xmtCLLMStatusTimerInterval in milliseconds for CLLM to send CLLM updates
CLLM parameters are not applicable for frame forwarding portsrw INTEGER .1.3.6.1.4.1.351.110.5.1.1.1.2.2.1.1.3 |
rcvCLLMStatusTimerTimeout value for receiving CLLM updates
CLLM parameters are not applicable for frame forwarding portsro Enumeration .1.3.6.1.4.1.351.110.5.1.1.1.2.2.1.1.4 |
frPortCnfX21PortGrpTableThe config table is for X.21/HSSI logical port interface SEQUENCE OF FrPortCnfX21PortGrpEntry .1.3.6.1.4.1.351.110.5.1.1.1.3.1 |
frPortCnfX21PortGrpEntryAn entry for logical port FrPortCnfX21PortGrpEntry .1.3.6.1.4.1.351.110.5.1.1.1.3.1.1 |
x21portNumThis is logical port number.
The HSSI backcard can support upto 3 ports,
whereas the X.21 can support 4 logical ports.
No defaults.ro INTEGER .1.3.6.1.4.1.351.110.5.1.1.1.3.1.1.1 |
x21portLineNumThis represents the line number.
On FRSM-HS1 the HSSI can support 3 lines
and X.21 4 lines.
No defaults.rw INTEGER .1.3.6.1.4.1.351.110.5.1.1.1.3.1.1.2 |
x21portRowStatusThis variable adds, deletes, or modifies the port
1- add
2 - delete
3 - modify
Default is add.rw Enumeration .1.3.6.1.4.1.351.110.5.1.1.1.3.1.1.3 |
x21portFlagsBetweenFramesNumber of flags transmitted between two consecutive
HDLC frames.
Default is 1 flag.rw INTEGER .1.3.6.1.4.1.351.110.5.1.1.1.3.1.1.4 |
x21portEqueueServiceRatioNumber of times queue 1 is serviced
for every time queue 2 is serviced.
Default is 1.rw INTEGER .1.3.6.1.4.1.351.110.5.1.1.1.3.1.1.5 |
x21portSpeedPort speed in kbps. At present it is same
as line speed.
No defaults.ro INTEGER .1.3.6.1.4.1.351.110.5.1.1.1.3.1.1.6 |
x21portAdminUp/down used to up and down the port.
Default is the up state.rw Enumeration .1.3.6.1.4.1.351.110.5.1.1.1.3.1.1.7 |
x21portTypeThis represents port type. The processing of the
frames depends on the type of the port.rw Enumeration .1.3.6.1.4.1.351.110.5.1.1.1.3.1.1.8 |
x21portSvcStatusThis represents SVC statusrw Enumeration .1.3.6.1.4.1.351.110.5.1.1.1.3.1.1.9 |
x21portSvcInUseThis represents port svc in userw Enumeration .1.3.6.1.4.1.351.110.5.1.1.1.3.1.1.10 |
x21portSvcShareLcnThis represents port typero Enumeration .1.3.6.1.4.1.351.110.5.1.1.1.3.1.1.11 |
x21portSvcLcnLowThis represents low end of reserved LCN for svcro INTEGER .1.3.6.1.4.1.351.110.5.1.1.1.3.1.1.12 |
x21portSvcLcnHighThis represents high end of reserved LCN for svcro INTEGER .1.3.6.1.4.1.351.110.5.1.1.1.3.1.1.13 |
x21portSvcDlciLowThis represents low end of reserved DLCI for svcro INTEGER .1.3.6.1.4.1.351.110.5.1.1.1.3.1.1.14 |
x21portSvcDlciHighThis represents high end of reserved DLCI for svcro INTEGER .1.3.6.1.4.1.351.110.5.1.1.1.3.1.1.15 |
x21portDeleteSvcsSetting this object to 1 indicates that all the SVC
connections on the given port has to be deletedrw Enumeration .1.3.6.1.4.1.351.110.5.1.1.1.3.1.1.16 |
x21portIngrSvcBandWThis represents Ingress Bandwidth reserve for SVCro INTEGER .1.3.6.1.4.1.351.110.5.1.1.1.3.1.1.17 |
x21portEgrSvcBandWThis represents Egress Bandwidth reserve for SVCro INTEGER .1.3.6.1.4.1.351.110.5.1.1.1.3.1.1.18 |
frPortServiceQueGrpTableThe config table is for logical port interface.
In FRSM-VHS, there are 256 entries for FRSM-2CT3 card and
2 entries for FRSM-T3/E3/HS2/T3B/E3B/HS2B-HSSI cards and
8 entries for FRSM-HS2B-12IN1. The table is currently
supported only in FRSM-VHS when the object egrQosFeature
in the cardSpecific group is set to egrQosFeatureEnabled. SEQUENCE OF FrPortServiceQueGrpEntry .1.3.6.1.4.1.351.110.5.1.1.1.4.1 |
frPortServiceQueGrpEntryAn entry for logical port FrPortServiceQueGrpEntry .1.3.6.1.4.1.351.110.5.1.1.1.4.1.1 |
frServPortNumThis is the logical port number.ro INTEGER .1.3.6.1.4.1.351.110.5.1.1.1.4.1.1.1 |
portServiceQueueNoThis identifies the Q depending on the Service Type
1 High Priority Queue
2 rt VBR Queue
3 nrt VBR and ABR Queue
4 UBR Queue
queue5(5) to queue8(8) are reserved for future use
There are 8 queues but only four are being used as of now.rw Enumeration .1.3.6.1.4.1.351.110.5.1.1.1.4.1.1.2 |
portEgresQDepthIndicates the peak Egress queue depth for the logical port.
The total queue depth of all connections mapped to this queue
should not exceed this value.rw INTEGER .1.3.6.1.4.1.351.110.5.1.1.1.4.1.1.3 |
portEgresECNThreshECN threshold for the logical port. If the total queue depth of
all connections mapped to this port queue exceeds this threshold,
then the appropriate ECN bit (FECN in the downstream direction and
BECN in the upstream direction) get set.rw INTEGER .1.3.6.1.4.1.351.110.5.1.1.1.4.1.1.4 |
portEgresDEThreshDE threshold for the logical port. If the total queue depth of
all connections mapped to this port queue exceeds this threshold,
and the DE bit is set in the incoming frame, then the frame gets
dropped.rw INTEGER .1.3.6.1.4.1.351.110.5.1.1.1.4.1.1.5 |
portQBwIncDenotes the bandwidth increment for this port queue. The
bandwidth increment is the percentage of the port bandwidth
used by all connections mapped to a particular queue scaled
by the value 16384.ro INTEGER .1.3.6.1.4.1.351.110.5.1.1.1.4.1.1.6 |
portBytesDiscXceedQueFullCounter maintained for the no of bytes discarded due to
port queue depth exceeded.ro Counter .1.3.6.1.4.1.351.110.5.1.1.1.4.1.1.7 |
portBytesDiscXceedDEThreshCounter maintained for the no of bytes discarded due to
DE threshold exceeded.ro Counter .1.3.6.1.4.1.351.110.5.1.1.1.4.1.1.8 |
frPortCnfResPartGrpTableThis table contains the configuration of port resource
partition SEQUENCE OF FrPortCnfResPartGrpEntry .1.3.6.1.4.1.351.110.5.1.1.1.5.1 |
frPortCnfResPartGrpEntryAn entry for logical port FrPortCnfResPartGrpEntry .1.3.6.1.4.1.351.110.5.1.1.1.5.1.1 |
frResPartPortNumThis is the logical port number, the index to this table.
If we have T1 card then the maximum port number is 192
and if we have E1 card the maximum port number can be 248
For FRSM VHS 2CT3 the maximum port number is 256.
For FRSM12 card:
The ifIndex of the port's corresponding row in ifTable.
Byte 3 = Chassis Number, Byte 2 = Slot Number,
Byte 1 & 0 = Encoded unique number for Port.ro INTEGER .1.3.6.1.4.1.351.110.5.1.1.1.5.1.1.1 |
frResPartCtrlrNumThis is index for controller using the port
In MGX release 1.0, the value par should be used
In MGX release 2.0, the value pnni should be usedro Enumeration .1.3.6.1.4.1.351.110.5.1.1.1.5.1.1.2 |
frResPartRowStatusThis will add, delete or modify the partition.
In MGX Release1.0:
To add an entry, this object should be set to add, value for
other objects should not be specified. FRSM will choose
default values for all other objects.
In MGX Release2.0:
To add an entry, this object should be set to add, value
for frResPartCtrlrID may be specified. FRSM will choose
default values for all other objects.
Currently the value mod is not supported.
To delete an entry, this object has to be set to del.
The resource partition can be deleted only after
deleting all the connections (LCNs).rw Enumeration .1.3.6.1.4.1.351.110.5.1.1.1.5.1.1.3 |
frResPartNumOfLcnAvailThis represents number of LCNs available for this
controller and this port
FRSM VHS 2CT3 can support LCNs upto 4000.
FRSM12 can support LCNs upto 16000.rw INTEGER .1.3.6.1.4.1.351.110.5.1.1.1.5.1.1.4 |
frResPartDlciLowThis represents low end of reserved DLCIrw INTEGER .1.3.6.1.4.1.351.110.5.1.1.1.5.1.1.5 |
frResPartDlciHighThis represents high end of reserved DLCIrw INTEGER .1.3.6.1.4.1.351.110.5.1.1.1.5.1.1.6 |
frResPartIngrPctBWThe percentage of total ingress bandwidth reservedrw INTEGER .1.3.6.1.4.1.351.110.5.1.1.1.5.1.1.7 |
frResPartEgrPctBWThe percentage of total egress bandwidth reservedrw INTEGER .1.3.6.1.4.1.351.110.5.1.1.1.5.1.1.8 |
frResPartCtrlrIDThis is the controller identifier for the resource patition.
The default value is set for PNNI controller.rw INTEGER .1.3.6.1.4.1.351.110.5.1.1.1.5.1.1.9 |
frPortCntPortGrp OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.5.1.1.2.1 |
frPortCntPortGrpTableThe config table is for logical port interface
there are upto 248 entries (for 8 E1s) or 192
(for 8 T1s). In FRSM-VHS, there is support for
upto 256 entries. SEQUENCE OF FrPortCntPortGrpEntry .1.3.6.1.4.1.351.110.5.1.1.2.1.1 |
frPortCntPortGrpEntryAn entry for logical port FrPortCntPortGrpEntry .1.3.6.1.4.1.351.110.5.1.1.2.1.1.1 |
cntPortNumRefers to the logical port index
For FRSM12 card:
The ifIndex of the port's corresponding row in ifTable.
Byte 3 = Chassis Number, Byte 2 = Slot Number,
Byte 1 & 0 = Encoded unique number for Port.ro INTEGER .1.3.6.1.4.1.351.110.5.1.1.2.1.1.1.1 |
rcvPortFramesThe number of frames Received on the ingressro Counter .1.3.6.1.4.1.351.110.5.1.1.2.1.1.1.2 |
rcvPortBytesThe number of bytes Received on the ingressro Counter .1.3.6.1.4.1.351.110.5.1.1.2.1.1.1.3 |
rcvPortFramesDEThe number of frames with DE bit set Received on the ingressro Counter .1.3.6.1.4.1.351.110.5.1.1.2.1.1.1.4 |
rcvPortFramesFECNThe number of frames with FECN bit set Received on the ingressro Counter .1.3.6.1.4.1.351.110.5.1.1.2.1.1.1.5 |
rcvPortFramesBECNThe number of frames with BECN bit set Received on the ingressro Counter .1.3.6.1.4.1.351.110.5.1.1.2.1.1.1.6 |
rcvFramesDiscCRCErrorThe number of frames discarded on the ingress
due to CRC errorro Counter .1.3.6.1.4.1.351.110.5.1.1.2.1.1.1.7 |
rcvFramesDiscAlignmentErrorThe number of frames discarded on the ingress
due to Alignment errorro Counter .1.3.6.1.4.1.351.110.5.1.1.2.1.1.1.8 |
rcvFramesDiscIllegalLenThe number of frames discarded on the ingress
due to illegal lengthro Counter .1.3.6.1.4.1.351.110.5.1.1.2.1.1.1.9 |
rcvFramesDiscIllegalHeaderThe number of frames discarded on the ingress
due to illegal headerro Counter .1.3.6.1.4.1.351.110.5.1.1.2.1.1.1.10 |
rcvFramesAbortThe number of received frames abortedro Counter .1.3.6.1.4.1.351.110.5.1.1.2.1.1.1.11 |
rcvFramesUnknownDLCIThe number of frames received with an unknown DLCIro Counter .1.3.6.1.4.1.351.110.5.1.1.2.1.1.1.12 |
rcvLastUnknownDLCIThe last unknown DLCI receivedro INTEGER .1.3.6.1.4.1.351.110.5.1.1.2.1.1.1.13 |
rcvPortFramesTaggedFECNThe number of frames received that were
tagged with FECN bitro Counter .1.3.6.1.4.1.351.110.5.1.1.2.1.1.1.14 |
rcvPortFramesTaggedBECNThe number of frames received that were
tagged with BECN bitro Counter .1.3.6.1.4.1.351.110.5.1.1.2.1.1.1.15 |
rcvPortFramesTaggedDEThe number of frames received that were
tagged with DE bitro Counter .1.3.6.1.4.1.351.110.5.1.1.2.1.1.1.16 |
rcvPortFramesDiscXceedDEThreshThe number of frames discarded on the ingress
due to exceeded DE Thresholdro Counter .1.3.6.1.4.1.351.110.5.1.1.2.1.1.1.17 |
rcvPortKbpsAIRReceived Average Information Rate in KBPSro INTEGER .1.3.6.1.4.1.351.110.5.1.1.2.1.1.1.18 |
rcvBufNotAvailableThe number of times the receiver is turned offro Counter .1.3.6.1.4.1.351.110.5.1.1.2.1.1.1.19 |
xmtPortFramesThe number of frames transmittedro Counter .1.3.6.1.4.1.351.110.5.1.1.2.1.1.1.20 |
xmtPortBytesThe number of bytes transmittedro Counter .1.3.6.1.4.1.351.110.5.1.1.2.1.1.1.21 |
xmtPortFramesFECNThe number of frames transmittedc with
FECN bit already setro Counter .1.3.6.1.4.1.351.110.5.1.1.2.1.1.1.22 |
xmtPortFramesBECNThe number of frames transmitted with
BECN bit already setro Counter .1.3.6.1.4.1.351.110.5.1.1.2.1.1.1.23 |
xmtPortFramesDiscXceedQDepthThe number of frames discarded on the egress
due to exceeded queue depth
For FRSM12 Card: Not Supportedro Counter .1.3.6.1.4.1.351.110.5.1.1.2.1.1.1.24 |
xmtPortBytesDiscXceedQDepthThe number of bytes discarded on the egress
due to exceeded queue depth
For FRSM12 Card: Not Supportedro Counter .1.3.6.1.4.1.351.110.5.1.1.2.1.1.1.25 |
xmtPortFramesDuringLMIAlarmThe number of frames transmitted during
LMI logical port alarmro Counter .1.3.6.1.4.1.351.110.5.1.1.2.1.1.1.26 |
xmtPortBytesDuringLMIAlarmThe number of bytes transmitted during
LMI logical port alarmro Counter .1.3.6.1.4.1.351.110.5.1.1.2.1.1.1.27 |
xmtFramesAbortThe number of transmit frames aborted
For FRSM12 Card: Not Supportedro Counter .1.3.6.1.4.1.351.110.5.1.1.2.1.1.1.28 |
xmtFramesUnderrunThe number of frames discarded due to underrunro Counter .1.3.6.1.4.1.351.110.5.1.1.2.1.1.1.29 |
xmtPortKbpsAIRTransmit Average Information Rate in KBPSro INTEGER .1.3.6.1.4.1.351.110.5.1.1.2.1.1.1.30 |
xmtBufNotAvailableThe number of times the transmitter is turned off
For FRSM12 Card: Not Supportedro Counter .1.3.6.1.4.1.351.110.5.1.1.2.1.1.1.31 |
portClrButtonPort clear button. Resets all counters.rw Enumeration .1.3.6.1.4.1.351.110.5.1.1.2.1.1.1.32 |
rcvFramesDiscNoChanThe number of frames received when no channel is setupro Counter .1.3.6.1.4.1.351.110.5.1.1.2.1.1.1.33 |
rcvFramesDiscOverrunThe number of frames discarded in Ingress direction
due to FIFO overrun in HDLC Controller.
This object is not applicable to MGX Release 1.xro Counter .1.3.6.1.4.1.351.110.5.1.1.2.1.1.1.34 |
frPortCntSigLMIGrp OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.5.1.1.2.2.1 |
frPortCntSigLMIGrpTableThe LMI counter table is for logical port interface
there are upto 248 entries (for 8 E1s) and upto
192 entries (for 8 T1s). In FRSM-VHS, there are
upto 256 entries. SEQUENCE OF FrPortCntSigLMIGrpEntry .1.3.6.1.4.1.351.110.5.1.1.2.2.1.1 |
frPortCntSigLMIGrpEntryAn entry for logical port FrPortCntSigLMIGrpEntry .1.3.6.1.4.1.351.110.5.1.1.2.2.1.1.1 |
lmiSigPortNumRefers to the logical port index
For FRSM12 card:
The ifIndex of the port's corresponding row in ifTable.
Byte 3 = Chassis Number, Byte 2 = Slot Number,
Byte 1 & 0 = Encoded unique number for Port.ro INTEGER .1.3.6.1.4.1.351.110.5.1.1.2.2.1.1.1.1 |
rcvStatusInquiryThe number of Status Inquiry messages receivedro Counter .1.3.6.1.4.1.351.110.5.1.1.2.2.1.1.1.2 |
rcvInvalidRequestThe number of Invalid Request messages receivedro Counter .1.3.6.1.4.1.351.110.5.1.1.2.2.1.1.1.3 |
rcvUNISeqMismatchThe number of times UNI messages
with sequence number mismatches were receivedro Counter .1.3.6.1.4.1.351.110.5.1.1.2.2.1.1.1.4 |
xmtStatusThe number of times Status response messages transmittedro Counter .1.3.6.1.4.1.351.110.5.1.1.2.2.1.1.1.5 |
xmtAsynchUpdateThe number of times Asynch Status messages transmittedro Counter .1.3.6.1.4.1.351.110.5.1.1.2.2.1.1.1.6 |
uniSignalingTimeoutThe number of times UNI Status requests were not receivedro Counter .1.3.6.1.4.1.351.110.5.1.1.2.2.1.1.1.7 |
xmtStatusInquiryThe number of Status Inquiry messages transmittedro Counter .1.3.6.1.4.1.351.110.5.1.1.2.2.1.1.1.8 |
rcvStatusThe number of times Status response messages receivedro Counter .1.3.6.1.4.1.351.110.5.1.1.2.2.1.1.1.9 |
rcvAsynchUpdateThe number of times Asynch Status messages receivedro Counter .1.3.6.1.4.1.351.110.5.1.1.2.2.1.1.1.10 |
rcvNNISeqMismatchThe number of times NNI messages
with sequence number mismatches were receivedro Counter .1.3.6.1.4.1.351.110.5.1.1.2.2.1.1.1.11 |
nniSignalingTimeoutThe number of times NNI Status requests were not receivedro Counter .1.3.6.1.4.1.351.110.5.1.1.2.2.1.1.1.12 |
frPortCntSigCLLMGrp OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.5.1.1.2.2.2 |
frPortCntSigCLLMGrpTableThe CLLM counter table is for logical port interface SEQUENCE OF FrPortCntSigCLLMGrpEntry .1.3.6.1.4.1.351.110.5.1.1.2.2.2.1 |
frPortCntSigCLLMGrpEntryAn entry for logical port FrPortCntSigCLLMGrpEntry .1.3.6.1.4.1.351.110.5.1.1.2.2.2.1.1 |
cllmSigPortNumRefers to the logical port index
For FRSM12 card:
The ifIndex of the port's corresponding row in ifTable.
Byte 3 = Chassis Number, Byte 2 = Slot Number,
Byte 1 & 0 = Encoded unique number for Port.ro INTEGER .1.3.6.1.4.1.351.110.5.1.1.2.2.2.1.1.1 |
rcvFramesCLLMThe number of CLLM frames receivedro Counter .1.3.6.1.4.1.351.110.5.1.1.2.2.2.1.1.2 |
rcvBytesCLLMThe number of CLLM bytes receivedro Counter .1.3.6.1.4.1.351.110.5.1.1.2.2.2.1.1.3 |
xmtFramesCLLMThe number of CLLM frames transmittedro Counter .1.3.6.1.4.1.351.110.5.1.1.2.2.2.1.1.4 |
xmtBytesCLLMThe number of CLLM bytes transmittedro Counter .1.3.6.1.4.1.351.110.5.1.1.2.2.2.1.1.5 |
cllmFailuresThe number of times an expected CLLM message was not receivedro Counter .1.3.6.1.4.1.351.110.5.1.1.2.2.2.1.1.6 |
frPortStateGrp OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.5.1.1.3 |
frPortStateGrpTableTable of transmit/receive states of ports. SEQUENCE OF FrPortStateGrpEntry .1.3.6.1.4.1.351.110.5.1.1.3.1 |
frPortStateGrpEntryAn entry for logical port. FrPortStateGrpEntry .1.3.6.1.4.1.351.110.5.1.1.3.1.1 |
statePortNumRefers to the logical port index
For FRSM12 card:
The ifIndex of the port's corresponding row in ifTable.
Byte 3 = Chassis Number, Byte 2 = Slot Number,
Byte 1 & 0 = Encoded unique number for Port.ro INTEGER .1.3.6.1.4.1.351.110.5.1.1.3.1.1.1 |
portStateThis variable indicates the state of the
logical portro Enumeration .1.3.6.1.4.1.351.110.5.1.1.3.1.1.2 |
portSignallingStateBit 0 = 0 -> LMI O.K. or not enabled
Bit 0 = 1 -> LMI failed
Bit 1 = 0 -> CLLM O.K. or not enabled
Bit 1 = 1 -> CLLM failedro INTEGER (0..'ffffff'h) .1.3.6.1.4.1.351.110.5.1.1.3.1.1.3 |
portOversubscribedThis variable indicates the whether the port is
over subscribed or notro Enumeration .1.3.6.1.4.1.351.110.5.1.1.3.1.1.4 |
portIngrPercentUtilPercentage Utilization of the Port in the Ingress
direction.ro INTEGER .1.3.6.1.4.1.351.110.5.1.1.3.1.1.5 |
portEgrPercentUtilPercentage Utilization of the Port in the Egress
direction.ro INTEGER .1.3.6.1.4.1.351.110.5.1.1.3.1.1.6 |
frChanCnfGrp OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.5.1.2.1 |
frChanCnfGrpTableThe config table is for logical channel interface
(upto 4000 entries). The actual number of entries
supported by a card depends on the type of card.
eg: FRSM-4T1/E1 supports 256 entries
FRSM-8T1/E1 supports 1000 entries
FRSM-T3/E3/HS2/HS2B-HSSI/T3B/E3B supports 2000 entries
FRSM-2CT3/HS2B-12IN1 supports 4000 entries
FRSM12 supports 16000 entries SEQUENCE OF FrChanCnfGrpEntry .1.3.6.1.4.1.351.110.5.1.2.1.1 |
frChanCnfGrpEntryAn entry for logical channel FrChanCnfGrpEntry .1.3.6.1.4.1.351.110.5.1.2.1.1.1 |
chanNumRefers to the virtual connection index
Note that the actual range of the index
supported by a card depends on the type of card.
eg: FRSM-4T1/E1 supports a range from 16..271 (256 entries)
FRSM-8T1/E1 supports a range from 16..1015 (1000 entries)
FRSM-T3/E3/HS2/HS2B-HSSI/T3B/E3B supports a range from
16..2015 (2000 entries)
FRSM-2CT3/HS2B-12IN1 supports a range from 16..4015 (4000 entries)
For FRSM12 Card:
Byte 3 = Chassis Number, Byte 2 = Slot Number,
Byte 1 & 0 = channel Number.
Lower two bytes range from 16..16015 (16000 entries)ro INTEGER .1.3.6.1.4.1.351.110.5.1.2.1.1.1.1 |
chanRowStatusThis will add, delete or modify the channel
1 ==> ADD
2 ==> DELETE
3 ==> MODIFY
Setting this object to outOfService takes the channel
out of service or brings the channel 'down'. The channel
can be brought 'up' again by setting the object to modrw Enumeration .1.3.6.1.4.1.351.110.5.1.2.1.1.1.2 |
chanPortNumRefers to the logical ports that are possible
on this card, the user must set this variable
For FRSM12 Card:
This object contains the port's ifIndex value.rw INTEGER .1.3.6.1.4.1.351.110.5.1.2.1.1.1.3 |
dLCIThis variable is the DLCI number of the channel.
The user has to set this variable.
All the connections on the same port should have
a unique DLCI number.
Note that if we are adding a channel to a port that
has LMI signalling enabled, then we can not use DLCI
number 0(ANNEX A & D) and 1023(STRATA LMI).
For FRSM12 Card:
For FR header length of 2-bytes, DLCI range is (0 .. 1023) and
0, 1007, 1023 DLCIs cannot be used.
For FR header length of 4-bytes, DLCI range is (0 .. 8388607) and
0, 8257535 DLCIs cannot be used.rw INTEGER .1.3.6.1.4.1.351.110.5.1.2.1.1.1.4 |
egressQSelectSelects one out of two possible port queues.
The default port queue number is 1 which is the high
pririty queue.
1 = High priority queue
2 = Low priority queue
3 = Indicates that this entry is not used (eg: in FRSM-VHS,
chanServType indicates the channel service type and
would determine the queue to which the channel gets mapped)
For FRSM12 Card:
This object is used to select between the two ATM-COS queues
in the egress direction.rw Enumeration .1.3.6.1.4.1.351.110.5.1.2.1.1.1.5 |
ingressQDepthThis variable sets the max depth for queue, before
it starts dropping the cells. It is defined in
terms of number of bytes.
In all cards except the FRSM-VHS card, the range is
limited to (4510..'ffff'h).
ingressQDepth should be greater than ingressQECNThresh
and ingressQDEThresh
For FRSM12 Card: Not Supportedrw INTEGER (4510..'1fffff'h) .1.3.6.1.4.1.351.110.5.1.2.1.1.1.6 |
ingressQECNThreshThis variable sets the max depth for queue, before
it starts flow control. It is defined in terms of
number of bytes.
In all cards except the FRSM-VHS card, the range is
limited to (0..'ffff'h).
For FRSM12 Card: Not Supportedrw INTEGER (0..'1fffff'h) .1.3.6.1.4.1.351.110.5.1.2.1.1.1.7 |
ingressQDEThreshThis variable sets the max depth for queue, before
they become discard eligible. It is defined in terms of
number of bytes.
In all cards except the FRSM-VHS card, the range is
limited to (0..'ffff'h).
For FRSM12 Card: Not Supportedrw INTEGER (0..'1fffff'h) .1.3.6.1.4.1.351.110.5.1.2.1.1.1.8 |
egressQDepthThis variable sets the max depth for queue, before
it starts dropping the cells. It is defined in terms of
number of bytes.
In all cards except the FRSM-VHS card, the range is
limited to (0..'ffff'h).
egressQDepth should be greater than egressQDEThresh
and egressQECNThresh
For FRSM12 Card: Not Supportedrw INTEGER (0..'1fffff'h) .1.3.6.1.4.1.351.110.5.1.2.1.1.1.9 |
egressQDEThreshThis variable sets the max depth for queue, before
they become discard eligible. It is defined in terms of
number of bytes.
In all cards except the FRSM-VHS card, the range is
limited to (0..'ffff'h).
For FRSM12 Card: Not Supportedrw INTEGER (0..'1fffff'h) .1.3.6.1.4.1.351.110.5.1.2.1.1.1.10 |
egressQECNThreshThis variable sets the max depth for queue, before
it starts flow control. It is defined in terms of
number of bytes.
In all cards except the FRSM-VHS card, the range is
limited to (0..'ffff'h).
For FRSM12 Card: Not Supportedrw INTEGER (0..'1fffff'h) .1.3.6.1.4.1.351.110.5.1.2.1.1.1.11 |
deTaggingEnableThe default value is 2.
This variable enables DE tagging in the ingress direction only.
enable = 1
disable = 2
For FRSM12 Card:
When this object is disabled, the ingress policer will never
set the DE bit to 1 in the Frame Relay frames even if
the incoming frame exceeds the Bc bucket.rw Enumeration .1.3.6.1.4.1.351.110.5.1.2.1.1.1.12 |
cirThe default value is 2400
cir defines committed information rate
cir is in bits per second
Maximum value for cir for an E1 card is 2048000 and
for a T1 card is 1536000.
cir has to be less than or equal to the port speed.
Maximum value for cir for an E3 card is 34368000, for
a T3 card is 44736000m, and for HSSI it is 52000000.
Note that for FRSM-2CT3 card, the peak value of
permissible CIR is 1536000.
Maximum value for FRSM-HS2B-12IN1 is 10240000
Any value from 1 to 2399 will be rounded off to 2400.
For FRSM12 Card:
The range is 0-44736000 bps for T3, and
The range is 0-34368000 bps for E3.
cir can be 0 only for chanServType of uBR.rw INTEGER .1.3.6.1.4.1.351.110.5.1.2.1.1.1.13 |
bcThe default value is 5100
bc defines burst committed. bc is in bytes.
bc can not be 0 when cir is not 0.
bc has to be 0 if cir is 0.
The peak value for bc in FRSM-VHS cards is (2^21 -1),
i.e. 2097151 and for all other cards, it is 65535.
For FRSM-VHS cards, the relation between CIR and Bc should
be such that Tc is always less than 512 seconds.
For FRSM12 Card:
The range is 0-2097151rw INTEGER .1.3.6.1.4.1.351.110.5.1.2.1.1.1.14 |
beThe default value is 5100 be defines the burst excess.
be can not be 0 when cir is 0. be is in bytes.
The peak value for be in FRSM-VHS cards is (2^21 -1),
i.e. 2097151 and for all other cards, it is 65535.
For FRSM-VHS cards, setting the value of 2091751 will
cause the policing to be disabled.
For FRSM12 Card:
The range is 0-2097151rw INTEGER .1.3.6.1.4.1.351.110.5.1.2.1.1.1.15 |
ibsThe default value is 100
ibs should be less or equal to bc when cir is greater
than 0. ibs has to be 0 when cir is 0.
The peak value for ibs in FRSM-VHS cards is (2^21 -1),
i.e. 2097151 and for all other cards, it is 65535.
For FRSM12 Card: Not Supportedrw INTEGER .1.3.6.1.4.1.351.110.5.1.2.1.1.1.16 |
foreSightEnableThe default value is 2
This variable sets foreSight option
Note that when you enable foresight option then you can
modify qir, mir and pir, otherwise you CAN NOT change
these values if you are disabling foresight or if foresight
option is already disabled.
The RATE CONTROL FEATURE has to be ON in order to enable
foresight and also modify its parameter.
enable = 1
disable = 2
For FRSM12 Card: Not Supportedrw Enumeration .1.3.6.1.4.1.351.110.5.1.2.1.1.1.17 |
qirThe dafault is 160
qir is defined in fastpackets/sec and it defines
quiescent information rate for Foresight. 1 cell/sec
is equal to 16 fastpackets/sec.
Following information about cps is for reference only:
The peak value for qir in FRSM-VHS cards is 285714 cps and
for all other cards, it is 10000 cps.
For FRSM-VHS cards, cell will be the ATM cell (48 byte payload).
For FRSM12 Card: Not Supportedrw INTEGER .1.3.6.1.4.1.351.110.5.1.2.1.1.1.18 |
mirThe dafault is 160
mir is defined in fastpackets/sec and it defines
minimum information rate for Foresight. 1 cell/sec
is equal to 16 fastpackets/sec.
Following information about cps is for reference only:
The peak value for qir in FRSM-VHS cards is 285714 cps and
for all other cards, it is 10000 cps.
For FRSM-VHS cards, cell will be the ATM cell (48 byte payload).
For FRSM12 Card: Not Supportedrw INTEGER .1.3.6.1.4.1.351.110.5.1.2.1.1.1.19 |
pirThe dafault is 160
pir is defined in fastpackets/sec and it defines
peak information rate for Foresight. 1 cell/sec
is equal to 16 fastpackets/sec.
Following information about cps is for reference only:
The peak value for qir in FRSM-VHS cards is 285714 cps and
for all other cards, it is 10000 cps.
For FRSM-VHS cards, cell will be the ATM cell (48 byte payload).
For FRSM12 Card: Not Supportedrw INTEGER .1.3.6.1.4.1.351.110.5.1.2.1.1.1.20 |
chanLocRmtLpbkStateThe default is disable.
This variable enables or disables the remote loopback for each
channel.
When you enable this option on a connection (channel) then all the
cells that are coming from the network side would be looped back
toward the network and all the frames coming from the user side
would be dropped.
This channel remote loopback has nothing to do with the chanTestType
option, each one does a different function.
For example, the channel remote loopback is used for looping the data
toward the network and if this connection is terminated on an IPX
then they can put a test equipment and measure some of the
characteristics of the network.
1 = enable
2 = disable
For FRSM12 Card: Not Supportedrw Enumeration .1.3.6.1.4.1.351.110.5.1.2.1.1.1.21 |
chanTestTypeThe default is notest.
The chanTestType starts testing the continuity or delay of a connection.
It sends specific cell patterns toward the network and the terminating
end of this connection has to be an AXIS or ASI of a BPX in order for
this test to be working.
The receiving node would loop back when it receives these
cells. The test should be done in about couple of seconds. The testcon
tests the continuity of the connection and testdelay uses the same
test except that it measures for delay through the network.
To test the delay follow this procedure:
a- set chanTestType to testdelay
b- read chanTestState till it is Pass or Fail
c- Read chanRTDResult for the delay if it is Pass
*Note that the chanTestType would go back to notest when the
test is completed
To test the continuity follow this procedure:
a- set chanTestType to testcon
b- read chanTestState till it is Pass or Fail
*Note that the chanTestType would go back to notest when the
test is completed
You CAN NOT select 2 tests back to back, you have selcelt one and wait
the result and then start the other one.
SYNTAX
When you select testdelay
This is the type of the test
1 = Test Continuity
2 = Test Delay
3 = No Testrw Enumeration .1.3.6.1.4.1.351.110.5.1.2.1.1.1.22 |
chanTestStateThis shows the state of the test
When you add a connection then the chanTestState becomes notinprogress
and when you select any test, it would go to inprogress state and after
it completes the test, it will go to failed or passed state.
1 = Passed
2 = Failed
3 = In Progress
4 = Not In Progressro Enumeration .1.3.6.1.4.1.351.110.5.1.2.1.1.1.23 |
chanRTDResultThis is round trip delay in milliseconds.
When you select testdelay option for the chanTestType, the result of
the test that is measured in milliseconds can be read in chanRTDResult.ro INTEGER .1.3.6.1.4.1.351.110.5.1.2.1.1.1.24 |
chanTypesets channel type
Type 1 is frame-relay network interworking (NIW-unicast)
type 2 is service interworking with out any SDU translation
type 3 is service interworking with SDU translation
type 4 is frame-relay UNI, currently mode-1a which is ALL5
type 5 is frame forwarding
types 1,2,3 and 5 are supported as explained above
type 4 (frame-relay UNI) is NOT supported
type 6 is also supported. It means frame-relay Network
Interworking with DLCI in FRSSCS-PDU always set to 1022
For FRSM12 Card: frFUNI is not supported.rw Enumeration .1.3.6.1.4.1.351.110.5.1.2.1.1.1.25 |
chanFECNconfigsets FECN config mapEFCI valid only for SIW
The FECN bits in frame-relay are mapped to EFCI bit in the ATM
cells.rw Enumeration .1.3.6.1.4.1.351.110.5.1.2.1.1.1.26 |
chanDEtoCLPmapsets mapping of CLP bit
The DE bit is mapped to CLP bit in ATM cell
in Case 2 and 3, the DE bit is ignored and CLP bit
is set to a constant value
For FRSM12 Card:
Should not be mapCLP for chanType of frForward.rw Enumeration .1.3.6.1.4.1.351.110.5.1.2.1.1.1.27 |
chanCLPtoDEmapsets mapping of DE bit 1,2,3 valid for SIW
1,4 valid for NIW
The CLP bit is mapped to DE bit in frame-relay
in the Case of 2 and 3, the CLP bit is ignored and DE bit
is set to a constant value
ignoreCLP ignores CLP bit and DE bit remains as received.
For FRSM12 Card:
Should be ignoreCLP for chanType of frForward.
Should not be setDEzero/setDEone for chanType of frNIW
and frNIWReplace.
Should not be ignoreCLP for chanType of frSIW-transparent
and frSIW-translate.rw Enumeration .1.3.6.1.4.1.351.110.5.1.2.1.1.1.28 |
chanIngrPercentUtilthe channel ingress utilized percentagerw INTEGER .1.3.6.1.4.1.351.110.5.1.2.1.1.1.29 |
chanEgrPercentUtilthe channel egress utilized percentagerw INTEGER .1.3.6.1.4.1.351.110.5.1.2.1.1.1.30 |
chanEgrSrvRateThe channel egress cir.
Maximum value for chanEgrSrvRate for an E1 card is 2048000 and
for a T1 card is 1536000.
chanEgrSrvRate has to be less than or equal to the port speed.
Maximum value for chanEgrSrvRate for an E3 card is 34368000, for
a T3 card is 44736000m, and for HSSI it is 52000000.
Note that for FRSM-2CT3 card, the peak value of
permissible chanEgrSrvRate is 1536000.
For FRSM12 Card:
This object is used only for CAC and the range will be same
as the range for cir object. The Maximum value is 44736000m.rw INTEGER .1.3.6.1.4.1.351.110.5.1.2.1.1.1.31 |
chanOvrSubOvrRideThis MIB variable allows one to add a new connection on a port
even if it is over subscribed.
For FRSM12 Card: Not Supportedrw Enumeration .1.3.6.1.4.1.351.110.5.1.2.1.1.1.32 |
chanFrConnTypechannel connection type
1 for pvc
2 for svc
3 for spvc
4 par (only for trunk connection)
5 pnni (only for trunk connection)
6 tag (only for trunk connection)
For FRSM12 Card: Not Supportedrw Enumeration .1.3.6.1.4.1.351.110.5.1.2.1.1.1.33 |
frCDRNumberThis is the key to correlate cell/frame counts, start/end record.
For FRSM12 Card: Not Supportedrw INTEGER .1.3.6.1.4.1.351.110.5.1.2.1.1.1.34 |
frLocalVpiThis VPI together with the local VCI and NSAP represents the
local end point in this connection, this object is read only,
therefore it'll be assigned by SM to 0.ro INTEGER .1.3.6.1.4.1.351.110.5.1.2.1.1.1.35 |
frLocalVciThis VCI together with the local VPI and NSAP represents the
local end point in this connection, this object is read only,
therefore it'll be assigned by SM to be equal to DLCI.ro INTEGER .1.3.6.1.4.1.351.110.5.1.2.1.1.1.36 |
frLocalNSAPThis NSAP is 20 bytes binary, among these 20 bytes: 13 bytes
as prefix, 2 bytes for Cisco ID, 1 byte rsvd, 3 bytes for
logical interface: slot (1 byte) and port number (2 bytes),
the last byte is for SEL
For FRSM12 Card:
This object will have the NSAP format as required by the
PNNI controllerrw OCTET STRING .1.3.6.1.4.1.351.110.5.1.2.1.1.1.37 |
frRemoteVpiThis VPI together with the remote VCI and NSAP represents the
remote end point in this connectionrw INTEGER .1.3.6.1.4.1.351.110.5.1.2.1.1.1.38 |
frRemoteVciThis VCI together with the remote VPI and NSAP represents the
remote end point in this connectionrw INTEGER .1.3.6.1.4.1.351.110.5.1.2.1.1.1.39 |
frRemoteNSAPThis NSAP is 20 bytes binary, among these 20 bytes: 13 bytes
as prefix, 2 bytes for Cisco ID, 1 byte rsvd, 3 bytes for
logical interface: slot (1 byte) and port number (2 bytes),
the last byte is for SELrw OCTET STRING .1.3.6.1.4.1.351.110.5.1.2.1.1.1.40 |
frMastershipThis is used by PXM to determine if this end point is
master or slave, a new type unknown is added to identify
the SM in AXIS shelf and the SM in MGX shelf. In AXIS
shelf, user can still use addchan to add a channel without
specifying X/Y/P parameters. But in MGX shelf, if the
user uses addchan without X/Y/P set (based on this object
being set to type 3 unknown), SPM on PXM will reject
the request. It must be supplied in connection setup request.
In the feeder mode, this is always set to master.rw Enumeration .1.3.6.1.4.1.351.110.5.1.2.1.1.1.41 |
frVpcFlagThis represents the connection type, used for PXM to
identify VPC/VCC but FRSM card doesn't use it
always set to vcc for FRSM card
For FRSM12 Card:
This object is used by the PNNI controller and is
always set to VCCrw Enumeration .1.3.6.1.4.1.351.110.5.1.2.1.1.1.42 |
frConnServiceTypeThis specifies the service type
1 ==> Constant Bit Rate
2 ==> Variable Bit Rate
3 ==> Not used
4 ==> Unspecified Bit Rate
5 ==> ATM frame relay
6 ==> standard ABR
7 ==> foresight ABR
Note that this is used by PXM card, SV+ doesn't need to set it,
if not set in the connection setup request, it'll be defaulted
to ATFR type for FRSM.
Also to make it compatible with existing AUSM MIB definition,
value 3 is not used.
The following types are being added for PNNI support.
and are based on UNI 4.0
cbr1 (21) - CBR.1
vbr1rt (22) - Real time VBR.1
vbr2rt (23) - Real time VBR.2
vbr3rt (24) - Real time VBR.3
vbr1nrt(25) - Non Real time VBR.1
vbr2nrt(26) - Non Real time VBR.2
vbr3nrt(27) - Non Real time VBR.3
ubr1 (28) - UBR.1
ubr2 (29) - UBR.2
stdabr (30) - TM 4.0 compliant standard ABR
cbr2 (31) - CBR.2
cbr3 (32) - CBR.3
For FRSM12 Card:
Not Supported. Derived from chanServType.rw Enumeration .1.3.6.1.4.1.351.110.5.1.2.1.1.1.43 |
frRoutingPriorityThis is used by PXM to determine how important this
connection is when selecting connections to routerw INTEGER .1.3.6.1.4.1.351.110.5.1.2.1.1.1.44 |
frMaxCostMaximum allowed cost. It is related to Cost Based Routing.
This is used by PXM so that it won't choose a path with
a cost greater than this configured level. This is not
necessary to be provided in the connection setup request,
if not provided, the default value 255 will be used.
When used with PAR controller the valid range is 1..65535 and the
default value is 255.
When used with PNNI controller the valid range is 1..2147483647 and
the default value is 2147483647.rw INTEGER .1.3.6.1.4.1.351.110.5.1.2.1.1.1.45 |
frRestrictTrunkTypeRestricted trunk type for routing, used by PXM. It
specifies that the connection either cannot be routed over
satelite trunks, or terrestrial trunks, or it can be on
any type of trunk. It is not necessary to be provide in
the connection setup request, the default value is
norestriction(1).
For FRSM12 Card: Not Supportedrw Enumeration .1.3.6.1.4.1.351.110.5.1.2.1.1.1.46 |
frConnPCRPeak cell rate, if not provided in the connection setup
request, it'll be derived from pir.
For FRSM12 Card:
Default value is (1.44 * CIR)rw INTEGER .1.3.6.1.4.1.351.110.5.1.2.1.1.1.47 |
frConnRemotePCRPeak cell rate of the other end, if not set, will be
set to the same as local end PCR (frConnPCR). However,
note that if the CIRs for both local and remote end
are set to the different value (i.e., asymmetric conn),
then this should be set differently from local end PCR.
For FRSM12 Card:
Default value is frConnPCRrw INTEGER .1.3.6.1.4.1.351.110.5.1.2.1.1.1.48 |
frConnMCRMinimum cell rate, if not provided in the connection setup
request, it'll be derived from mir.
For FRSM12 Card:
Default value is frConnPCRrw INTEGER .1.3.6.1.4.1.351.110.5.1.2.1.1.1.49 |
frConnRemoteMCRMinimum cell rate of the other end, if not set, will be
set to the same as local end MCR (frConnMCR). However,
note that if the CIRs for both local and remote end
are set to the different value (i.e., asymmetric conn),
then this should be set differently from local end MCR.
For FRSM12 Card:
Default value is frConnMCRrw INTEGER .1.3.6.1.4.1.351.110.5.1.2.1.1.1.50 |
frConnPercentUtilThis is the expected long-term utilization of the
channel by this end-point. If this is not specified in
the connection setup request, it'll be defaulted to
100 percent
For FRSM12 Card: Not Supportedrw INTEGER .1.3.6.1.4.1.351.110.5.1.2.1.1.1.51 |
frConnRemotePercentUtilThis is the expected long-term utilization of the
channel by the other end-point. If this is not specified in
the connection setup request, it'll be set to be the same
as the local end frConnPercentUtil value assuming that the
connection is symmetric. In a asymmetric connection, this
object is supposed to be set.
For FRSM12 Card: Not Supportedrw INTEGER .1.3.6.1.4.1.351.110.5.1.2.1.1.1.52 |
frConnForeSightEnableThis object is used by the controller(PAR/PNNI/TAG) to
set up the Qbin for the connection, if this is not set,
it'll be defaulted by SM to the same as foreSightEnable
in the end point parameters.
For FRSM12 Card: Not Supportedrw Enumeration .1.3.6.1.4.1.351.110.5.1.2.1.1.1.53 |
frConnFGCRAEnableenables/disables Frame based GCRA (early packet discard).
For FRSM12 Card: Not Supportedrw Enumeration .1.3.6.1.4.1.351.110.5.1.2.1.1.1.54 |
chanServTypeThis indicates the class of the connection
1-High priority (typically CBR connections)
2- real-time VBR
3- non-real time VBR
4- Available Bit Rate
5- Unspecified Bit Rate
9- Standard ABR
There are 8 queues actually but only 4 are currently being used
(the 4 queues are for CBR, VBR-rt, <VBR-nrt and ABR>, UBR traffic).
This object is currently suuported only in FRSM-VHS and FRSM-8T1E1.
For FRSM-8T1E1, a 0 indicates that the connections are of old model
type where chanServType object is unused.
Note that chanServType is not modifiable after a channel has been
enabled
For FRSM12 Card:
The types aBR, queue6, queue7, queue8 are not supportedrw Enumeration .1.3.6.1.4.1.351.110.5.1.2.1.1.1.55 |
chanServiceRateOverrideThis variable sets the SAR IR programming option.
Foresight and chanServiceRateOverride are mutually exclusive.
For FRSM12 Card: Not Supportedrw Enumeration .1.3.6.1.4.1.351.110.5.1.2.1.1.1.56 |
chanServiceRateThis is the rate to which IR can be set to when
chanServiceRateOverride is set to enabled. If chanServiceRateOverride
is disabled then this object does not have any significance.
For FRSM-8P, this is defined in fastpackets/sec.
For FRSM-VHS, this is defined in atm cells per second.
For VHS the range in cells per second will be 10 to 400000 cps.
For FRSM12 Card: Not Supportedrw INTEGER .1.3.6.1.4.1.351.110.5.1.2.1.1.1.57 |
zeroCirConEirzeroCirConEir defines EIR value for '0' CIR connection.
If zeroCirConEir is '0', EIR is set to port speed. If zeroCirConEir
is non-zero value, EIR is set to value of this object, and this value
is used for policing in ingress direction.
This object is valid only for a zero cir connection.
zeroCirConEir has to be less than or equal to the port speed.rw INTEGER .1.3.6.1.4.1.351.110.5.1.2.1.1.1.58 |
chanRerouteThis is used by the administrator to trigger the re-routing
of the connection. The rerouting takes effect, when this object
is set to true(1). When set to false (2), no action is taken.
A get on this object always returns false (2).
This object is not applicable to MGX Release 1.x.rw Enumeration .1.3.6.1.4.1.351.110.5.1.2.1.1.1.59 |
frConnSCRSustained cell rate, Used for VBR connections setup with PNNI
controller.
For FRSM12 Card: Default value is frConnPCR
This object is not applicable to MGX Release 1.xrw INTEGER .1.3.6.1.4.1.351.110.5.1.2.1.1.1.60 |
frConnRemoteSCRSustained cell rate of the other end, Used for VBR connections
setup with PNNI controller.
For FRSM12 Card: Default value is frConnSCR
This object is not applicable to MGX Release 1.xrw INTEGER .1.3.6.1.4.1.351.110.5.1.2.1.1.1.61 |
frConnTemplateIdThis object specifies the template identifier for the connection
template associated with this connection.
The valid range for templates is 1..16.
A value of 17 indicates no template is associated with this
connection
For FRSM12 Card: Not Supported
This object is not applicable to MGX Release 1.xrw INTEGER .1.3.6.1.4.1.351.110.5.1.2.1.1.1.62 |
frConnAdminStatusThis object specifies channel admin status.
This object is not applicable to MGX Release 1.x.rw Enumeration .1.3.6.1.4.1.351.110.5.1.2.1.1.1.63 |
frChanCnfChangeCountThis object is added only for FRSM12 card.
This counter tracks the number of configuration changes
that happen on a channel. The counter is
associated only with the end point and NOT with the
connection itself.
This counter is used by the NMS to determine if a connection
configuration had been modified and requires an upload.
This functionality is conventionally achieved by time
stamping using a time-of-day clock. However, in switches
where time-of-day clock is not available, the following
scheme is used:
The upload counter is incremented, when:
* assignment of connection to an end point channel. This
happens when a connection is added and assigned this
channel number.
* de-assignment of connection from a channel number. This
happens when a connection is deleted and the
end point resource is released.
* When there is a configuration change done to the connection
that is associated with this end point channel number.
In a new system, an unutilised resouce (channel number)
has a counter value of zero. When a connection is added to
this channel end point, the counter is incremented. And is
incremented for any of the above operations. When a connection
is deleted the value of this counter is incremented and
preserved till a new connection gets associated with this
channel end point.
This object is not applicable to MGX Release 1.x.ro Counter .1.3.6.1.4.1.351.110.5.1.2.1.1.1.64 |
frChanCnfIgnoreIncomingDEThis object is added for FRSM12 card.
When this object is enabled, the incoming frames with
DE(Discard Eligible) bit set to 1 are counted in the
Bc bucket instead of Be bucket
This object is not applicable to MGX Release 1.x.rw Enumeration .1.3.6.1.4.1.351.110.5.1.2.1.1.1.65 |
frChanOamCCEnableThis object is added for FRSM12 card.
This object serves to enable or disable continuity check(CC)
on a connection endpoint. When continuity check is enabled
on an endpoint, the endpoint anticipates OAM CC cells from its
peer endpoint. OAM CC cells are sent when the peer endpoint
does not have traffic cells to send. If the connection is
idle and this endpoint has not received OAM CC cells for a
period of 3.5 +/- 0.5 seconds, it declares continuity failure.
This object serves to administratively control the CC feature.
Typical implementations (of this feature) may choose to ignore
this control or impose other conditions to actually enable CC
cell flow. However, if this object is set to false(2), then this
feature should be disabled
This object is not applicable to MGX Release 1.x.rw Enumeration .1.3.6.1.4.1.351.110.5.1.2.1.1.1.66 |
frChanStatsEnableThis object is added for FRSM12 card.
Limits imposed by software or hardware implementations
could restrict the amount of statistical data that can be
maintained in a physical entity (like a service module card).
Hence there could be a need to restrict statistics collection
to a smaller subset.
This object serves the purpose of enabling/disabling statistics
collection on a per connection basis. In implementations which
do not have such limitations, this object can be set to enable(1)
for all connections
This object is not applicable to MGX Release 1.x.rw Enumeration .1.3.6.1.4.1.351.110.5.1.2.1.1.1.67 |
frChanLocalLpbkEnableThis object is added for FRSM12 card.
This object when enabled adds a channel-level loopback
towards the port side. If the connection is in loopback,
Connection MIB (FrChanCnfGrpEntry) variables cannot be modified.
This object is not applicable to MGX Release 1.x.rw Enumeration .1.3.6.1.4.1.351.110.5.1.2.1.1.1.68 |
frChanUpcEnableThis object is added for FRSM12 card.
This object when disabled, disables Frame Relay policing.
This object is not applicable to MGX Release 1.x.rw Enumeration .1.3.6.1.4.1.351.110.5.1.2.1.1.1.69 |
frChanSlaveTypeThis object is added for FRSM12 card.
This object indicates whether a master endpoint has a persistent
slave or not. A connection with a master and a non-persistent
slave is considered a single-ended SPVC.
This object is only meaningful when 'frMastership'
contains the value of 'master(1)'. And this variable
must be used with 'frMastership' to decide
if a connection is single-ended or not.
This object is not applicable to MGX Release 1.x.rw Enumeration .1.3.6.1.4.1.351.110.5.1.2.1.1.1.70 |
frConnRemoteMBSRemote Maximum Burst Size in terms of number of cells.
This object should be set by the user in cases when
the remote end of the connection is an ATM end-point
where the Local MBS can be explicitly specified. In such
cases, this element should be set to be equal to the
remote end-point's local MBS.
This object is not applicable to MGX Release 1.x.rw INTEGER .1.3.6.1.4.1.351.110.5.1.2.1.1.1.71 |
chanNumNextAvailableThis variable contains the next UNUSED channel number
of the possible 4000 (ranging from 16 to 4015).
This number can be used in channel config table, the
ChanNumNextAvailable gets updated if the number gets
used to create a logical channel.
A '0' indicates that no more channels are available.
For FRSM12 Card: Not Supportedro INTEGER .1.3.6.1.4.1.351.110.5.1.2.1.2 |
frstdABRCnfGrpTableThe ABR config table is for logical channel interface
(upto 4000 entries). The actual number of entries
supported by a card depends on the type of card.
eg: FRSM-4T1/E1 supports 256 entries
FRSM-8T1/E1 supports 1000 entries
FRSM-T3/E3/HS2/T3B/E3B/HS2B-HSSI supports 2000 entries
FRSM-2CT3/HS2B-12IN1 supports 4000 entries
FRSM12 supports 16000 entries SEQUENCE OF FrstdABRCnfGrpEntry .1.3.6.1.4.1.351.110.5.1.2.1.3 |
frstdABRCnfGrpEntryAn entry for logical channel FrstdABRCnfGrpEntry .1.3.6.1.4.1.351.110.5.1.2.1.3.1 |
frstdABRcnfChanNumRefers to the virtual connection index
Note that the actual range of the index
supported by a card depends on the type of card.
eg: FRSM-4T1/E1 supports a range from 16..271 (256 entries)
FRSM-8T1/E1 supports a range from 16..1015 (1000 entries)
FRSM-T3/E3/HS2/T3B/E3B/HS2B-HSSI supports a range from
16..2015 (2000 entries)
FRSM-2CT3/HS2B-12IN1 supports a range from 16..4015 (4000 entries)
For FRSM12 Card:
Byte 3 = Chassis Number, Byte 2 = Slot Number,
Byte 1 & 0 = channel Number.
Lower two bytes range from 16..16015 (16000 entries)ro INTEGER .1.3.6.1.4.1.351.110.5.1.2.1.3.1.1 |
frstdABRTBETransient Buffer Exposure. The unit is number of cells.rw INTEGER .1.3.6.1.4.1.351.110.5.1.2.1.3.1.2 |
frstdABRFRTTFixed Round-Trip Time. The unit is milliseconds. Value 0 signifies
that FRTT is not available.rw INTEGER .1.3.6.1.4.1.351.110.5.1.2.1.3.1.3 |
frstdABRRDFRate Decrease Factor. This unitless value has to be inverted to
arrive at the actual value. The valid values possible are only powers
of 2; i.e. 1, 2, 4, 8 ..... 32768. The SNMP agent has to verify this
compliance.rw INTEGER .1.3.6.1.4.1.351.110.5.1.2.1.3.1.4 |
frstdABRRIFRate Increase Factor. This unitless value has to be inverted to
arrive at the actual value. The valid values possible are only powers
of 2; i.e. 1, 2, 4, 8 ..... 32768. The SNMP agent has to verify this
compliance.rw INTEGER .1.3.6.1.4.1.351.110.5.1.2.1.3.1.5 |
frstdABRNrmMaximum number of cells a source may send for each forward RM cell.
The valid values possible are only powers of 2 starting from 2;
i.e. 2, 4, 8 ..... 256. The SNMP agent has to verify this compliance.rw INTEGER .1.3.6.1.4.1.351.110.5.1.2.1.3.1.6 |
frstdABRTrmUpper bound on the time between forward RM cells for an active source.
The unit is in milliseconds.rw INTEGER .1.3.6.1.4.1.351.110.5.1.2.1.3.1.7 |
frstdABRCDFCutoff Decrease Factor. This unitless value has to be inverted
to arrive at the actual value. The valid values possible are 0
and only powers of 2; i.e., 1, 2, 4, 8, 16, 32, 64. The SNMP agent
has to verify this compliance.rw INTEGER .1.3.6.1.4.1.351.110.5.1.2.1.3.1.8 |
frstdABRADTFACR DecreaseTime Factor. Unit of this value is milliseconds.
Granularity allowed is 10 milli seconds. The SNMP agent has to
verify this compliance.rw INTEGER .1.3.6.1.4.1.351.110.5.1.2.1.3.1.9 |
frstdABRICRInitial Cell Rate is the rate at which the source
should send initially and after an idle period. This
includes the bandwidth allocated for both data cells
as well as all in-rate RM cells.
Unit is cells/sec. The Range will be 10 to 400000.
.rw INTEGER .1.3.6.1.4.1.351.110.5.1.2.1.3.1.10 |
frstdABRMCRMinimum Cell Rate is the rate at which the source
is allowed to send. This includes the bandwidth allocated
for both data cells as well as all in-rate RM cells.
Unit is cells/sec. The Range will be 10 to 400000.
.rw INTEGER .1.3.6.1.4.1.351.110.5.1.2.1.3.1.11 |
frstdABRPCRPeak Cell Rate is the rate at which the source
is allowed to send. This includes the bandwidth allocated
for both data cells as well as all in-rate RM cells.
Unit is cells/sec. The Range will be 10 to 400000.rw INTEGER .1.3.6.1.4.1.351.110.5.1.2.1.3.1.12 |
frChanStateGrp OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.5.1.2.2 |
frChanStateGrpTableTable of transmit/receive states of channels. SEQUENCE OF FrChanStateGrpEntry .1.3.6.1.4.1.351.110.5.1.2.2.1 |
frChanStateGrpEntryAn entry for FrChannelStateGrpEntry. FrChanStateGrpEntry .1.3.6.1.4.1.351.110.5.1.2.2.1.1 |
stateChanNumRefers to the virtual connection index
Note that the actual range of the index
supported by a card depends on the type of card.
eg: FRSM-4T1/E1 supports a range from 16..271 (256 entries)
FRSM-8T1/E1 supports a range from 16..1015 (1000 entries)
FRSM-T3/E3/HS2 supports a range from 16..2015 (2000 entries)
FRSM-2CT3 supports a range from 16..4015 (4000 entries)
For FRSM12 Card:
Byte 3 = Chassis Number, Byte 2 = Slot Number,
Byte 1 & 0 = channel Number.
Lower two bytes range from 16..16015 (16000 entries)ro INTEGER .1.3.6.1.4.1.351.110.5.1.2.2.1.1.1 |
chanStateThis variable indicates the LMI state of the
VC (channel)
failed(4) is added to distinguish between alarm (when the connection
in the PNNI n/w is not actually broken) and failed (when the connection
in the PNNI n/w is actually broken). This is applicable only to the
PNNI environment.ro Enumeration .1.3.6.1.4.1.351.110.5.1.2.2.1.1.2 |
xmtAbitStateThe A bit transmit state
1 - LMI off
2 - LMI on and connection is O.K.
3 - LMI on and connection has failedro Enumeration .1.3.6.1.4.1.351.110.5.1.2.2.1.1.3 |
rcvAbitStateThe A bit receive state
1 - LMI off
2 - LMI on and connection is O.K.
3 - LMI on and connection has failedro Enumeration .1.3.6.1.4.1.351.110.5.1.2.2.1.1.4 |
xmtATMStateThis variable indicates the transmit state of the
VC (channel) on the ATM side
1 - Not sending any state
2 - Sending AIS OAM state
3 - Sending FERF OAM statero Enumeration .1.3.6.1.4.1.351.110.5.1.2.2.1.1.5 |
rcvATMStateThis variable indicates the receiving state of the
VC (channel) on the ATM side
1 - Not receiving any state
2 - Receiving AIS OAM
3 - Receiving FERF OAMro Enumeration .1.3.6.1.4.1.351.110.5.1.2.2.1.1.6 |
chanStatusBitMapThis variable indicates the consolidated bit map of the channel alarm
state.
Individual bit positions are as defined below.
Bit position Fail/Alarm Reason
0 Alarm Reserved
1 Alarm n/w side AIS/RDI Rx
2 Fail Conditioned(A bit from n/w)
3 Alarm Reserved
4 Fail CC failed/RAS failed
5 Fail Mismatch
6 Alarm ingress A bit (LMI)
7 Alarm Reserved
Fail bitmap mask : 0x34
Alarm bitmap mask: 0xCB
This object is not applicable to MGX Release 1.x.ro INTEGER (0..'ff'h) .1.3.6.1.4.1.351.110.5.1.2.2.1.1.7 |
frChanCntGrp OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.5.1.2.3 |
frChanCntGrpTableThe config table is for logical channel interface
there are upto 4000 entries. SEQUENCE OF FrChanCntGrpEntry .1.3.6.1.4.1.351.110.5.1.2.3.1 |
frChanCntGrpEntryAn entry for logical channel FrChanCntGrpEntry .1.3.6.1.4.1.351.110.5.1.2.3.1.1 |
cntChanNumRefers to the virtual connection index
Note that the actual range of the index
supported by a card depends on the type of card.
eg: FRSM-4T1/E1 supports a range from 16..271 (256 entries)
FRSM-8T1/E1 supports a range from 16..1015 (1000 entries)
FRSM-T3/E3/HS2 supports a range from 16..2015 (2000 entries)
FRSM-2CT3 supports a range from 16..4015 (4000 entries)
FRSM12 supports a range from 16..16015 (16000 entries)
For FRSM12 Card: Byte 3 = Chassis Number, Byte 2 = Slot Number,
Byte 1 & 0 = channel Numberro INTEGER .1.3.6.1.4.1.351.110.5.1.2.3.1.1.1 |
rcvFramesThe number of frames Received on the ingressro Counter .1.3.6.1.4.1.351.110.5.1.2.3.1.1.2 |
rcvBytesThe number of bytes Received on the ingressro Counter .1.3.6.1.4.1.351.110.5.1.2.3.1.1.3 |
rcvFramesDEThe number of DE frames Received on the ingressro Counter .1.3.6.1.4.1.351.110.5.1.2.3.1.1.4 |
rcvBytesDEThe number of DE bytes Received on the ingressro Counter .1.3.6.1.4.1.351.110.5.1.2.3.1.1.5 |
rcvFramesDiscardThe number of frames discarded on the ingressro Counter .1.3.6.1.4.1.351.110.5.1.2.3.1.1.6 |
rcvBytesDiscardThe number of bytes discarded on the ingressro Counter .1.3.6.1.4.1.351.110.5.1.2.3.1.1.7 |
rcvFramesDiscShelfAlarmThe number of frames discarded on the ingress
due to shelf alarm
For FRSM12 Card: Not Supportedro Counter .1.3.6.1.4.1.351.110.5.1.2.3.1.1.8 |
rcvFramesDiscXceedQDepthThe number of frames discarded on the ingress
due to exceeded queue depthro Counter .1.3.6.1.4.1.351.110.5.1.2.3.1.1.9 |
rcvBytesDiscXceedQDepthThe number of bytes discarded on the ingress
due to exceeded queue depthro Counter .1.3.6.1.4.1.351.110.5.1.2.3.1.1.10 |
rcvFramesDiscXceedDEThreshThe number of frames discarded on the ingress
due to exceeded DE Thresholdro Counter .1.3.6.1.4.1.351.110.5.1.2.3.1.1.11 |
rcvFramesFECNThe number of frames received with
FECN bit already setro Counter .1.3.6.1.4.1.351.110.5.1.2.3.1.1.12 |
rcvFramesBECNThe number of frames received with
BECN bit already setro Counter .1.3.6.1.4.1.351.110.5.1.2.3.1.1.13 |
rcvFramesTaggedFECNThe number of frames received that were
tagged with FECN bitro Counter .1.3.6.1.4.1.351.110.5.1.2.3.1.1.14 |
rcvFramesTaggedBECNThe number of frames received that were
tagged with BECN bitro Counter .1.3.6.1.4.1.351.110.5.1.2.3.1.1.15 |
rcvFramesTaggedDEThe number of frames received that were
tagged with DE bitro Counter .1.3.6.1.4.1.351.110.5.1.2.3.1.1.16 |
rcvBytesTaggedDEThe number of bytes received that were
tagged with DE bitro Counter .1.3.6.1.4.1.351.110.5.1.2.3.1.1.17 |
rcvKbpsAIRReceived Average Information Rate in KBPSro INTEGER .1.3.6.1.4.1.351.110.5.1.2.3.1.1.18 |
xmtFramesThe number of frames transmittedro Counter .1.3.6.1.4.1.351.110.5.1.2.3.1.1.19 |
xmtBytesThe number of bytes transmittedro Counter .1.3.6.1.4.1.351.110.5.1.2.3.1.1.20 |
xmtFramesFECNThe number of frames transmitted with FECN bit already setro Counter .1.3.6.1.4.1.351.110.5.1.2.3.1.1.21 |
xmtFramesBECNThe number of frames transmitted with BECN bit already setro Counter .1.3.6.1.4.1.351.110.5.1.2.3.1.1.22 |
xmtFramesDEThe number of DE frames transmittedro Counter .1.3.6.1.4.1.351.110.5.1.2.3.1.1.23 |
xmtBytesDEThe number of DE bytes transmittedro Counter .1.3.6.1.4.1.351.110.5.1.2.3.1.1.24 |
xmtFramesDiscardThe number of frames discarded on the eggressro Counter .1.3.6.1.4.1.351.110.5.1.2.3.1.1.25 |
xmtBytesDiscardThe number of bytes discarded on the egress
For FRSM12 Card: Not Supportedro Counter .1.3.6.1.4.1.351.110.5.1.2.3.1.1.26 |
xmtFramesDiscXceedQDepthThe number of frames discarded on the egress
due to exceeded queue depth
For FRSM12 Card: Not Supportedro Counter .1.3.6.1.4.1.351.110.5.1.2.3.1.1.27 |
xmtBytesDiscXceedQDepthThe number of bytes discarded on the egress
due to exceeded queue depth
For FRSM12 Card: Not Supportedro Counter .1.3.6.1.4.1.351.110.5.1.2.3.1.1.28 |
xmtFramesDiscXceedDEThreshThe number of frames discarded on the egress
due to exceeded DE Threshold
For FRSM12 Card: Not Supportedro Counter .1.3.6.1.4.1.351.110.5.1.2.3.1.1.29 |
xmtFramesDiscPhyLayerFailThe number of frames discarded on the egress
due to physical layer failurero Counter .1.3.6.1.4.1.351.110.5.1.2.3.1.1.30 |
xmtFramesDiscCRCErrorThe number of frames discarded on the egress
due to CRC Errorro Counter .1.3.6.1.4.1.351.110.5.1.2.3.1.1.31 |
xmtFramesDiscReassmFailThe number of frames discarded on the egress
due to reassembly failure
For FRSM12 Card: Not Supportedro Counter .1.3.6.1.4.1.351.110.5.1.2.3.1.1.32 |
xmtFramesDiscSrcAbortThe number of frames discarded on the egress
due to source abortro Counter .1.3.6.1.4.1.351.110.5.1.2.3.1.1.33 |
xmtFramesDuringLMIAlarmThe number of frames transmitted during
LMI logical port alarmro Counter .1.3.6.1.4.1.351.110.5.1.2.3.1.1.34 |
xmtBytesDuringLMIAlarmThe number of bytes transmitted during
LMI logical port alarmro Counter .1.3.6.1.4.1.351.110.5.1.2.3.1.1.35 |
xmtFramesTaggedFECNThe number of frames transmitted that were
tagged with FECN bitro Counter .1.3.6.1.4.1.351.110.5.1.2.3.1.1.36 |
xmtFramesTaggedBECNThe number of frames transmitted that were
tagged with BECN bitro Counter .1.3.6.1.4.1.351.110.5.1.2.3.1.1.37 |
xmtKbpsAIRTransmitted Average Information Rate in KBPSro INTEGER .1.3.6.1.4.1.351.110.5.1.2.3.1.1.38 |
chanClrButtonChannel clear button. Clears Channel Counters.rw Enumeration .1.3.6.1.4.1.351.110.5.1.2.3.1.1.39 |
xmtFramesTaggedDEThe number of frames transmitted which have been DE tagged
at the far end ingress in excess of CIRro Counter .1.3.6.1.4.1.351.110.5.1.2.3.1.1.40 |
xmtBytesTaggedDEThe number of bytes transmitted which have been DE tagged
at the far end ingress in excess of CIRro Counter .1.3.6.1.4.1.351.110.5.1.2.3.1.1.41 |
rcvFramesDiscUPCThe number of frames discarded at ingress
due to the UPC measurement in excess of CIR+EIRro Counter .1.3.6.1.4.1.351.110.5.1.2.3.1.1.42 |
chanSecUpTimeThe time in seconds the PVC stay in servicero Counter .1.3.6.1.4.1.351.110.5.1.2.3.1.1.43 |
xmtFramesInvalidCPIsNumber of frames transmitted with invalid CPI header.
currently valid is 0ro Counter .1.3.6.1.4.1.351.110.5.1.2.3.1.1.44 |
xmtFramesLengthViolationsThe number of frames discarded due to violation of length in
the egress direction.ro Counter .1.3.6.1.4.1.351.110.5.1.2.3.1.1.45 |
xmtFramesOversizedSDUsThe number of frames discarded because the size is beyond
the max in the egress directionro Counter .1.3.6.1.4.1.351.110.5.1.2.3.1.1.46 |
xmtFramesUnknownProtocolsThe number of frames discarded for Unknown protocol in
the egress direction. Used only in SIW for PDUs that
are dropped.ro Counter .1.3.6.1.4.1.351.110.5.1.2.3.1.1.47 |
rcvFramesUnknownProtocolsNumber of frames discarded for Unknown protocol in the
ingress direction. Used only in SIW for PDUs that
are droppedro Counter .1.3.6.1.4.1.351.110.5.1.2.3.1.1.48 |
ausmPortCnfPortGrp OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.5.2.1.1.1 |
ausmPortCnfPortGrpTableThe config table is for logical port interface
there are 8 entries for either T1 or E1 SEQUENCE OF AusmPortCnfPortGrpEntry .1.3.6.1.4.1.351.110.5.2.1.1.1.1 |
ausmPortCnfPortGrpEntryAn entry for logical port. In AUSM (4-port card), a logical port
is same as a physical port. AusmPortCnfPortGrpEntry .1.3.6.1.4.1.351.110.5.2.1.1.1.1.1 |
ausmPortNumThis is logical port number. In AUSM (4-port card), a logical port
is same as a physical port.ro INTEGER .1.3.6.1.4.1.351.110.5.2.1.1.1.1.1.1 |
portEnableThis variable enables or disables the port
1 - disable
2 - enablerw Enumeration .1.3.6.1.4.1.351.110.5.2.1.1.1.1.1.2 |
ausmPortTypeThis variable
indicates whether UNI/NNI/STI interface
STI mode is supported only in IMATM.
vpTrkUni should be used only in IMATM when virtual trunks are
passing through IMATM (i.e. the cell format is UNI but ForeSight
information is carried in the lower 16 bits)rw Enumeration .1.3.6.1.4.1.351.110.5.2.1.1.1.1.1.3 |
ausmPortIfTypeThis variable indicates the type of interfacero Enumeration .1.3.6.1.4.1.351.110.5.2.1.1.1.1.1.4 |
ausmPortSpeedThe speed of the port in cells per secondro INTEGER .1.3.6.1.4.1.351.110.5.2.1.1.1.1.1.5 |
ausmLineNumThe line number associated with the logical port. For AUSM (4 port),
the line number is same as the logical port. In AUSM-8p, these two
can be differentrw INTEGER .1.3.6.1.4.1.351.110.5.2.1.1.1.1.1.6 |
ausmPortCnfServiceQueGrp OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.5.2.1.1.2 |
ausmPortCnfServiceQueGrpTableIn AUSM (4port): the Service queue table has 64 entries,
16 each for every port, in addition there are 4 queues for
OAM/ILMI traffic
In AUSM (8-port), the Service queue table has 128 entries,
16 each for every port, in addition there are 8 queues for
OAM/ILMI traffic SEQUENCE OF AusmPortCnfServiceQueGrpEntry .1.3.6.1.4.1.351.110.5.2.1.1.2.1 |
ausmPortCnfServiceQueGrpEntryAn entry for a single queue AusmPortCnfServiceQueGrpEntry .1.3.6.1.4.1.351.110.5.2.1.1.2.1.1 |
egrQIndexEgress queue number. In AUSM (4 port), only range from 1..12
is permissiblero INTEGER .1.3.6.1.4.1.351.110.5.2.1.1.2.1.1.1 |
servicePortNumLogical port number to which egress queue is associated.
In AUSM (4-port card), a logical port is same as a physical
port.
This is read only and queue mapping is as follows
1-16 port no 1
17-32 port no 2
33-48 port no 3
49-64 port no 4
For AUSM 8-port card, the following queue mapping is used
in addition to the above:
65-80 port no 5
81-96 port no 6
97-112 port no 7
113-128 port no 8ro INTEGER .1.3.6.1.4.1.351.110.5.2.1.1.2.1.1.2 |
egrQBinStateEgress queue staterw Enumeration .1.3.6.1.4.1.351.110.5.2.1.1.2.1.1.3 |
egrQServiceSequenceEgress queue number sequence in the priority list. In AUSM
(4 port), range from only 1..12 is permissiblerw INTEGER .1.3.6.1.4.1.351.110.5.2.1.1.2.1.1.4 |
egrQDepthMaxThe maximum depth of the egress queue. In AUSM (4 port),
range from only 1..8000 is permissiblerw INTEGER .1.3.6.1.4.1.351.110.5.2.1.1.2.1.1.5 |
egrQCLPThreshHighHigh CLP threshold of the egress queue. In AUSM (4 port),
range from only 1..8000 is permissible.This value should
be less than or equal to egrQDepthMax.rw INTEGER .1.3.6.1.4.1.351.110.5.2.1.1.2.1.1.6 |
egrQCLPThreshLowLow CLP threshold of the egress queue. In AUSM (4 port),
range from only 1..8000 is permissible. This value should
be less than or equal to egrQCLPThreshHigh.rw INTEGER .1.3.6.1.4.1.351.110.5.2.1.1.2.1.1.7 |
egrQEfciThreshThreshold of the egress queue for EFCI. In AUSM (4 port),
range from only 1..8000 is permissible.This value should
be less than or equal to egrQDepthMax.rw INTEGER .1.3.6.1.4.1.351.110.5.2.1.1.2.1.1.8 |
egrQAlgorithmThe algorithm number for the Egress queue
1-5 are valid values
'ff'h is disablerw INTEGER (1..'ff'h) .1.3.6.1.4.1.351.110.5.2.1.1.2.1.1.9 |
egrMaxBwIncThe increment for the Maximum carry for the queue. In
AUSM (8 port), range from only 1..511 is permissiblerw INTEGER .1.3.6.1.4.1.351.110.5.2.1.1.2.1.1.10 |
egrMinBwIncThe increment for the minimum carry for the queue. In
AUSM (8 port), range from only 1..511 is permissiblerw INTEGER .1.3.6.1.4.1.351.110.5.2.1.1.2.1.1.11 |
egrQCLPStatethis variable indicates the CLP state for the queuero Enumeration .1.3.6.1.4.1.351.110.5.2.1.1.2.1.1.12 |
egrQfullDiscardCellsThe number of cells discarded due to Egress Q fullro Counter .1.3.6.1.4.1.351.110.5.2.1.1.2.1.1.13 |
egrQClpSetDiscardCellsThe number of CLP set cells discarded in Egress directionro Counter .1.3.6.1.4.1.351.110.5.2.1.1.2.1.1.14 |
ausmPortCnfSig OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.5.2.1.1.3 |
ausmPortCnfSigILMIGrp OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.5.2.1.1.3.1 |
ausmPortCnfSigILMIGrpTableThe config table is for upto 8 logical port interfaces SEQUENCE OF AusmPortCnfSigILMIGrpEntry .1.3.6.1.4.1.351.110.5.2.1.1.3.1.1 |
ausmPortCnfSigILMIGrpEntryAn entry for a logical port. In AUSM (4-port card), a logical
port is same as a physical port. AusmPortCnfSigILMIGrpEntry .1.3.6.1.4.1.351.110.5.2.1.1.3.1.1.1 |
sigPortNumRefers to the logical port index. In AUSM (4-port card), a
logical port is same as a physical port.ro INTEGER .1.3.6.1.4.1.351.110.5.2.1.1.3.1.1.1.1 |
ausmSignallingProtocolTypeThis will set the signalling protocol
1 - other
2 - noSignalling
3 - ILMIrw Enumeration .1.3.6.1.4.1.351.110.5.2.1.1.3.1.1.1.2 |
signallingVpiindicates the VPI on which signalling cells
arriverw INTEGER (0..'ffffff'h ) .1.3.6.1.4.1.351.110.5.2.1.1.3.1.1.1.3 |
signallingVciindicates the VCI on which signalling cells
arriverw INTEGER (0..'ffffff'h ) .1.3.6.1.4.1.351.110.5.2.1.1.3.1.1.1.4 |
addrPrefixNetwork Prefix for the ATM addressrw NetPrefix -- from ILMI MIB .1.3.6.1.4.1.351.110.5.2.1.1.3.1.1.1.5 |
customerIdfor the INS as a read/write variablerw INTEGER .1.3.6.1.4.1.351.110.5.2.1.1.3.1.1.1.6 |
protocolRevNofor the INS as a read/write variablerw INTEGER .1.3.6.1.4.1.351.110.5.2.1.1.3.1.1.1.7 |
iLMITrapEnableEnable/disable ILMI Trap sendingrw Enumeration .1.3.6.1.4.1.351.110.5.2.1.1.3.1.1.1.8 |
minTrapIntervalnumber of seconds between trapsrw INTEGER .1.3.6.1.4.1.351.110.5.2.1.1.3.1.1.1.9 |
keepAlivePollingEnableEnable/disable Keep Alive Pollingrw Enumeration .1.3.6.1.4.1.351.110.5.2.1.1.3.1.1.1.10 |
errorThresholdN491Error Threshold (N491) valuerw INTEGER .1.3.6.1.4.1.351.110.5.2.1.1.3.1.1.1.11 |
eventThresholdN492Event Threshold (N492) valuerw INTEGER .1.3.6.1.4.1.351.110.5.2.1.1.3.1.1.1.12 |
pollingIntervalT491Polling Interval (T491) valuerw Enumeration .1.3.6.1.4.1.351.110.5.2.1.1.3.1.1.1.13 |
minEnquiryIntervalT493Minimum Enquiry Interval (T493)rw INTEGER .1.3.6.1.4.1.351.110.5.2.1.1.3.1.1.1.14 |
addrRegEnableEnable/disable ILMI Address Registrationrw Enumeration .1.3.6.1.4.1.351.110.5.2.1.1.3.1.1.1.15 |
ausmPortCnfPortImaGrp OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.5.2.1.1.4 |
ausmPortCnfPortImaGrpTableThe config table is for the IMA port (IMA group).
There are 8 entries in all. SEQUENCE OF AusmPortCnfPortImaGrpEntry .1.3.6.1.4.1.351.110.5.2.1.1.4.1 |
ausmPortCnfPortImaGrpEntryAn entry for every IMA port (total of 8 entries) AusmPortCnfPortImaGrpEntry .1.3.6.1.4.1.351.110.5.2.1.1.4.1.1 |
imaPortNumThis is the logical port number.ro INTEGER .1.3.6.1.4.1.351.110.5.2.1.1.4.1.1.1 |
imaPortEnableThis variable enables, disables or modifies the configuration of
the port
1 - delport (Disables the entire IMA group)
2 - addport (Enables the IMA group)
3 - addlinks (Adds links to an existing IMA group)
4 - dellinks (Deletes links from an existing IMA group)
5 - modify (Modifies parameters in an existing IMA group)
An IMA group is synonymous with an IMA port.
To configure an IMA port, the different lines in the IMA port
should be enabled and then the IMA port should be added using
the enumeration 'addport'.
To delete an IMA port, the enumeration 'delport' should be used.
To increase the bandwidth of an IMA group, the enumeration
'addlinks' should be used.
To decrease the bandwidth of an IMA group, the enumeration
'dellinks' should be used.
'modify' is used to change parameters other than links in the IMA
grouprw Enumeration .1.3.6.1.4.1.351.110.5.2.1.1.4.1.1.2 |
imaPortSpeedThe speed of the port in cells per second. This depends
on the nuber of links in the IMA group and the configuration of
the physical interface on each link (eg: T1, Normal E1, Clear E1 etc).ro INTEGER .1.3.6.1.4.1.351.110.5.2.1.1.4.1.1.3 |
numLinksInImaGrpThe number of links configured in the IMA group
This is same as axisImaGroupNumTxCfgLnks in Forum Compliant Imaro INTEGER .1.3.6.1.4.1.351.110.5.2.1.1.4.1.1.4 |
listOfLinksInImaGrpThe list of links in the IMA group delimited by dotsrw DisplayString .1.3.6.1.4.1.351.110.5.2.1.1.4.1.1.5 |
lcpCellsPeriodicityPeriod at wich LCP cells of the IMA protocol can be transmitted.
A value of 32 indicates that after 32 cells, one LCP cell is
transmitted on that link of the IMA group. Currently, the only
value supported is 128
This has same meaning as axisImaGroupTxFrameLength in Forum
Compliant Ima.ro INTEGER .1.3.6.1.4.1.351.110.5.2.1.1.4.1.1.6 |
lcpDelayToleranceThe number of IMA frames for which an LCP cell on any link can
be missed before the IMA state machine should remove the link
from the IMA group. At present, this is hard-coded to 1 and is
not programmable.
Not supported in Forum Compliant Imaro INTEGER .1.3.6.1.4.1.351.110.5.2.1.1.4.1.1.7 |
readPtrWrPtrDiffThe difference between the read and write pointer of a link in
the common cell buffer. A lower value reduces the latency in the
common cell buffer but also increases the probability of an IMA
group being stalled for a cell-time due to a slower link in the
IMA group
Not supported in Forum Compliant Ima.rw INTEGER .1.3.6.1.4.1.351.110.5.2.1.1.4.1.1.8 |
numRedundantLinksThe degree of resiliency in the IMA group. This indicates the number
of links the system can lose from this IMA group without bringing it
down. By default, the system can tolerate {configured #links - 1}
to go down.
Not supported in Forum Compliant Ima.rw INTEGER .1.3.6.1.4.1.351.110.5.2.1.1.4.1.1.9 |
maxTolerableDiffDelayThis indicates the maximum tolerable differential delay in milliseconds
between the various links in the IMA group. The default value is
variable and depends on the type of card with IMA feature:
For AUSM-8p:
200 milliseconds for an IMA group consisting of E1 lines
275 milliseconds for an IMA group consisting of T1 lines.
For IMATM:
50 milliseconds for an IMA group consisting of either T1/E1 lines.
This is same as axisImaGroupDiffDelayMax of Forum Compliant Ima.rw INTEGER .1.3.6.1.4.1.351.110.5.2.1.1.4.1.1.10 |
imaPortTypeThis indicates whether the port is to be configured for UNI/NNI/STI
mode. STI mode is supported only in the case of IMATM.
vpTrkUni should be used only in IMATM when virtual trunks are
passing through IMATM (i.e. the cell format is UNI but ForeSight
information is carried in the lower 16 bits)rw Enumeration .1.3.6.1.4.1.351.110.5.2.1.1.4.1.1.11 |
axisImaGroupTxAvailCellRateThe current cell rate(truncated value in cells per second) provided by
the IMA group in the transmit direction, considering all the transmit
links in the Active state.
The generic formula for the link rate with N links active is :
N * link Rate * (M-1)/M * (2048/2049), where M is the Ima Frame length.
Suppose M = 128, then following are the link rates :
In case of T1,for 8 lines the value is 28728 cells/sec.
In case of Normal E1(for 8 Lines), the value is 35920 cells/sec.
In case of Clear E1(for 8 Lines),the value is 38312 cells/sec.ro INTEGER .1.3.6.1.4.1.351.110.5.2.1.1.4.1.1.12 |
axisImaGroupSymmetrySymmetry of the IMA group.
AsymmetricOperation,AsymmetricConfiguration are not supported.rw Enumeration .1.3.6.1.4.1.351.110.5.2.1.1.4.1.1.13 |
axisImaGroupMinNumRxLinksMinimum number of receive links required to be active for the IMA
group to be in the Up state.At present since only symmetric
configuration is supported,this should be equal to
axisImaGroupMinNumTxLinks.rw INTEGER .1.3.6.1.4.1.351.110.5.2.1.1.4.1.1.14 |
axisImaGroupNeTxClkModeTransmit clocking mode used by the near-end IMA group.
ITC is not available in ausm8(B). Only default value (ctc) is supported.rw Enumeration .1.3.6.1.4.1.351.110.5.2.1.1.4.1.1.15 |
axisImaGroupAlphaValueThis indicates the 'alpha' value used to specify the number of
consecutive invalid ICP cells to be detected before moving to the
IMA HUNT state.
Only default values are supported.ro INTEGER .1.3.6.1.4.1.351.110.5.2.1.1.4.1.1.16 |
axisImaGroupBetaValueThis indicates the 'beta'value used to specify the number of
consecutive errored ICP cells to be detected before moving to the IMA
HUNT state.
Only default values are supported.ro INTEGER .1.3.6.1.4.1.351.110.5.2.1.1.4.1.1.17 |
axisImaGroupGammaValueThis indicates the 'gamma' value used to specify the number of
consecutive valid ICP cells to be detected before moving to the IMA
SYNC state from the PRESYNC state.
Only default values are supported.ro INTEGER .1.3.6.1.4.1.351.110.5.2.1.1.4.1.1.18 |
axisImaGroupNumRxCfgLnksThe Number of links that are configured to receive in this IMA
Group.ro INTEGER .1.3.6.1.4.1.351.110.5.2.1.1.4.1.1.19 |
axisImaGroupTestLinkIfIndexThis object is used to designate an interface as the test link.
A value of -1 specifies that the implementation may choose the
test link. In this case ,the implementation may also choose the
value of axisImaGroupTestPattern.rw INTEGER .1.3.6.1.4.1.351.110.5.2.1.1.4.1.1.20 |
axisImaGroupTestPatternThe value of this object is used to specify the test pattern in an
IMA group loopback operation. A value in the range 0 to 255 designates
a specific pattern. A value of -1 specifies that the implementation may
choose the value. In this case,the implementation may also choose the
value of 'axisImaGroupTestLinkIfIndex.rw INTEGER .1.3.6.1.4.1.351.110.5.2.1.1.4.1.1.21 |
axisImaGroupTestProcStatusThis object is used to enable or disable the Test Pattern Proceudre,and
to note whether at least one link failed the test.
The test is started by setting operating(2) status.If any link should
fail the test ,the IMA will set the status to linkfail(3).The linkfail(3)
state will persist until either the disabled(1) state is set or until no
instance of imaLinkTestProcStatus has the value linkfail(3).
Only the values disabled(1) and operating(2) may be written.
Writing the opersting(2) value will not cause clearing of the
linkfail(3) state.rw Enumeration .1.3.6.1.4.1.351.110.5.2.1.1.4.1.1.22 |
axisImaGroupIntegrationUpTimeIntegration UP time for alarm integration.Persisting checking time to
enter a failure alarm condition,in case of LIF,LODS,RFI-IMA fault
failure alarms.
Time in Milli Seconds.rw INTEGER .1.3.6.1.4.1.351.110.5.2.1.1.4.1.1.23 |
axisImaGroupIntegrationDownTimeIntegration DOWN time for alarm integration.Persisting clearing time to
exit the LIF,LODS,RFI-IMA failure alarm conditions.
Time in Milli seconds.rw INTEGER .1.3.6.1.4.1.351.110.5.2.1.1.4.1.1.24 |
axisImaGroupMinNumTxLinksMinimum number of transmit links required to be active for the IMA
group to be in the Up state.Eventhough the range is 1..8,this value
should be <= maximum number of configured links in IMA group.rw INTEGER .1.3.6.1.4.1.351.110.5.2.1.1.4.1.1.25 |
axisImaGroupRxImaIdThe Ima id used by the far end.ro INTEGER .1.3.6.1.4.1.351.110.5.2.1.1.4.1.1.26 |
nextPortNumAvailableIndicates the next logical port number (i.e. either ATM T1/E1 UNI
or IMA port) that is availablero INTEGER .1.3.6.1.4.1.351.110.5.2.1.1.4.2 |
ausmPortCnfResPartGrp OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.5.2.1.1.5 |
ausmPortCnfResPartGrpTableThe config table is for logical port interface
there are 4/8 entries for either T1 or E1 or AIMUX
ports
For PXM (MGX), there are 32 entries. SEQUENCE OF AusmPortCnfResPartGrpEntry .1.3.6.1.4.1.351.110.5.2.1.1.5.1 |
ausmPortCnfResPartGrpEntryAn entry for logical port AusmPortCnfResPartGrpEntry .1.3.6.1.4.1.351.110.5.2.1.1.5.1.1 |
ausmResPartPortNumThis is logical port number
In PXM, a port refers to the Logical Broadband Interface.
Refer bbIfCnfPortGrp.my for more information.ro INTEGER .1.3.6.1.4.1.351.110.5.2.1.1.5.1.1.1 |
ausmPortSvcInUseSetting this object to 1 indicates that the resources
(LCN/Local VPID/VCI/VPI) have been partitioned and INS
and SV+ are currently using this information. The resource
partition information can be changed after setting this
variable to 2.
The default value is 2 (NotInUse).rw Enumeration .1.3.6.1.4.1.351.110.5.2.1.1.5.1.1.2 |
ausmPortSvcShareLcnVpidIndicates whether or not the LCN and VPid address spaces
are shared across all the ports.
Default value is 2 (cardBased).ro Enumeration .1.3.6.1.4.1.351.110.5.2.1.1.5.1.1.3 |
ausmPortSvcLcnLowThe beginning of the LCN range reserved for SVCs.
Both the LCN low and high values apply to all ports
when the 'atmPortSvcShareLcnVpid' object is set to
2 (CardBased). When they are changed for one port the
change is applicable/propagated to all ports.rw INTEGER .1.3.6.1.4.1.351.110.5.2.1.1.5.1.1.4 |
ausmPortSvcLcnHighThe end of the LCN range reserved for SVCs.rw INTEGER .1.3.6.1.4.1.351.110.5.2.1.1.5.1.1.5 |
ausmPortSvcVpidLowThe beginning of the VPID range reserved for SVCs.
Both the VPID low and high values apply to all ports
when the 'atmPortSvcShareLcnVpid' object is set to
2 (CardBased). When they are changed for one port the
change is applicable/propagated to all ports.rw INTEGER .1.3.6.1.4.1.351.110.5.2.1.1.5.1.1.6 |
ausmPortSvcVpidHighThe end of the VPID range reserved for SVCs.rw INTEGER .1.3.6.1.4.1.351.110.5.2.1.1.5.1.1.7 |
ausmPortSvcVciLowThe beginning of the VCI range reserved for SVCs.
For VPI connections the valid VCI values are 0 - 4095rw INTEGER (0..'ffff'h) .1.3.6.1.4.1.351.110.5.2.1.1.5.1.1.8 |
ausmPortSvcVciHighThe end of the VCI range reserved for SVCs.
For VPI connections the valid VCI values are 0 -4095rw INTEGER (0..'ffff'h) .1.3.6.1.4.1.351.110.5.2.1.1.5.1.1.9 |
ausmPortSvcVpiLowThe beginning of the VCI range reserved for SVCs.rw INTEGER .1.3.6.1.4.1.351.110.5.2.1.1.5.1.1.10 |
ausmPortSvcVpiHighThe end of the VPI range reserved for SVCs.rw INTEGER .1.3.6.1.4.1.351.110.5.2.1.1.5.1.1.11 |
ausmPortIngrSvcBandWThis represents Ingress Bandwidth reserved for SVCrw INTEGER .1.3.6.1.4.1.351.110.5.2.1.1.5.1.1.12 |
ausmPortEgrSvcBandWThis represents Egress Bandwidth reserved for SVCrw INTEGER .1.3.6.1.4.1.351.110.5.2.1.1.5.1.1.13 |
ausmPortDelSvcsGrp OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.5.2.1.1.6 |
ausmPortDelSvcsGrpTableThe table is for logical port interface
there are 4/8 entries for either T1 or E1 or AIMUX
ports
For PXM (MGX), there are 32 entries. SEQUENCE OF AusmPortDelSvcsGrpEntry .1.3.6.1.4.1.351.110.5.2.1.1.6.1 |
ausmPortDelSvcsGrpEntryAn entry for logical port AusmPortDelSvcsGrpEntry .1.3.6.1.4.1.351.110.5.2.1.1.6.1.1 |
ausmDelSvcsPortNumThis is logical port number
In PXM, a port refers to the Logical Broadband Interface.
Refer bbIfCnfPortGrp.my for more information.ro INTEGER .1.3.6.1.4.1.351.110.5.2.1.1.6.1.1.1 |
ausmPortDeleteSvcsSetting this object to 1 indicates that all the SVC
connections on the given port has to be deletedrw Enumeration .1.3.6.1.4.1.351.110.5.2.1.1.6.1.1.2 |
ausmPortImaGrpRestart OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.5.2.1.1.7 |
ausmPortImaGrpRestartTableThe restart table is for the IMA port (IMA group).
There are 8 entries in all. SEQUENCE OF AusmPortImaGrpRestartEntry .1.3.6.1.4.1.351.110.5.2.1.1.7.1 |
ausmPortImaGrpRestartEntryAn entry for every IMA port (total of 8 entries) AusmPortImaGrpRestartEntry .1.3.6.1.4.1.351.110.5.2.1.1.7.1.1 |
axisImaGroupimaPortNumThis is the logical port number.ro INTEGER .1.3.6.1.4.1.351.110.5.2.1.1.7.1.1.1 |
axisImaGroupRestartImaGrpThis variable restarts the Ima grp. We have the option of
relearning the Ima id or retaining the stored ID.rw Enumeration .1.3.6.1.4.1.351.110.5.2.1.1.7.1.1.2 |
ausmPortStateGrp OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.5.2.1.2 |
ausmPortStateGrpTableThe state table for the port interface
there are 8 entries for either T1 or E1 or IMA. SEQUENCE OF AusmPortStateGrpEntry .1.3.6.1.4.1.351.110.5.2.1.2.1 |
ausmPortStateGrpEntryAn entry for logical port. In AUSM (4-port card), a logical port
is same as a physical port. AusmPortStateGrpEntry .1.3.6.1.4.1.351.110.5.2.1.2.1.1 |
ausmStatePortNumThis is logical port number. In AUSM (4-port card), a logical port
is same as a physical port.ro INTEGER .1.3.6.1.4.1.351.110.5.2.1.2.1.1.1 |
ausmPortStateThis variable indicates the status of the portro Enumeration .1.3.6.1.4.1.351.110.5.2.1.2.1.1.2 |
ausmPortOversubscribedThis variable indicates the whether the port is
over subscribed or notro Enumeration .1.3.6.1.4.1.351.110.5.2.1.2.1.1.3 |
ausmPortIngrPercentUtilPercentage Utilization of the Port in the Ingress
direction.ro INTEGER .1.3.6.1.4.1.351.110.5.2.1.2.1.1.4 |
ausmPortEgrPercentUtilPercentage Utilization of the Port in the Egress
direction.ro INTEGER .1.3.6.1.4.1.351.110.5.2.1.2.1.1.5 |
ausmPortCntPortGrp OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.5.2.1.3.1 |
ausmPortCntPortGrpTableThe config table is for logical port interface
there are 8 entries for either T1 or E1 SEQUENCE OF AusmPortCntPortGrpEntry .1.3.6.1.4.1.351.110.5.2.1.3.1.1 |
ausmPortCntPortGrpEntryAn entry for logical port AusmPortCntPortGrpEntry .1.3.6.1.4.1.351.110.5.2.1.3.1.1.1 |
ausmCntPortNumThis is the logical port number. In AUSM (4-port card), a
logical port is same as a physical port.ro INTEGER .1.3.6.1.4.1.351.110.5.2.1.3.1.1.1.1 |
ingrRcvCellsThe number of cells received in Ingress directionro Counter .1.3.6.1.4.1.351.110.5.2.1.3.1.1.1.2 |
ingrGfcErrCellsThe number of cells received in Ingress direction
with non zero-GFCro Counter .1.3.6.1.4.1.351.110.5.2.1.3.1.1.1.3 |
ingrVpiVciErrCellsThe number of cells received in Ingress direction
with unknown VpiVciro Counter .1.3.6.1.4.1.351.110.5.2.1.3.1.1.1.4 |
ingrLastUnknVpiVciThe last unknown Vpi Vci valuero INTEGER (0..'ffffff'h) .1.3.6.1.4.1.351.110.5.2.1.3.1.1.1.5 |
egrXmtCellsThe number of cells transmitted in the egress directionro Counter .1.3.6.1.4.1.351.110.5.2.1.3.1.1.1.6 |
egrPortAlarmDiscardCellsThe number of cells discarded due to port alarmro Counter .1.3.6.1.4.1.351.110.5.2.1.3.1.1.1.7 |
egrXmtClpSetCellsThe number of cells transmitted in Egress direction
with CLP bit setro Counter .1.3.6.1.4.1.351.110.5.2.1.3.1.1.1.8 |
egrXmtEfciSetCellsThe number of cells transmitted in Egress direction
with EFCI bit setro Counter .1.3.6.1.4.1.351.110.5.2.1.3.1.1.1.9 |
portXmtAisCellsThe number of AIS cells transmitted towards portro Counter .1.3.6.1.4.1.351.110.5.2.1.3.1.1.1.10 |
portXmtSgmtLpbkCellsThe number of Segment Loopback cells transmitted
towards portro Counter .1.3.6.1.4.1.351.110.5.2.1.3.1.1.1.11 |
portRcvAisCellsThe number of AIS cells received in Ingress directionro Counter .1.3.6.1.4.1.351.110.5.2.1.3.1.1.1.12 |
portRcvFerfCellsThe number of FERF cells received in Ingress directionro Counter .1.3.6.1.4.1.351.110.5.2.1.3.1.1.1.13 |
portRcvSgmtLpbkCellsThe number of Segment Loopback cells received in
Ingress directionro Counter .1.3.6.1.4.1.351.110.5.2.1.3.1.1.1.14 |
portRcvCrcErrOAMCellsThe number of OAM cells received in Ingress direction
with CRC errorro Counter .1.3.6.1.4.1.351.110.5.2.1.3.1.1.1.15 |
ausmPortClrButtonwriting a value of 2 resets all the countersrw Enumeration .1.3.6.1.4.1.351.110.5.2.1.3.1.1.1.16 |
ingrRcvClpSetCellsThe number of cells received from the port which had
the CLP bit in the ATM cell header equal to 1.ro Counter .1.3.6.1.4.1.351.110.5.2.1.3.1.1.1.17 |
ingrXmtCellsThe number of cells out of the received cells from the port
that were sent to the network. This count is taken after
policing and ingress queueing.ro Counter .1.3.6.1.4.1.351.110.5.2.1.3.1.1.1.18 |
egrRcvCellsThe number of cells received from the network
in the egress directionro Counter .1.3.6.1.4.1.351.110.5.2.1.3.1.1.1.19 |
ingrRcvCellRateThe number of cells received per second from the port
in the ingress direction. Maximum value is 5000 because
because clear E1 rate is 4830.ro Gauge .1.3.6.1.4.1.351.110.5.2.1.3.1.1.1.20 |
ingrRcvUtilizationThe percentage utilization of the port speed
in the ingress direction.ro Gauge .1.3.6.1.4.1.351.110.5.2.1.3.1.1.1.21 |
egrXmtCellRateThe number of cells received transmitted to the port
in the egress direction.ro Gauge .1.3.6.1.4.1.351.110.5.2.1.3.1.1.1.22 |
egrXmtUtilizationThe percentage utilization of the port speed
in the egress direction.ro Gauge .1.3.6.1.4.1.351.110.5.2.1.3.1.1.1.23 |
egrRcvCellRateThe number of cells received per second from the network
in the egress receive direction.ro Gauge .1.3.6.1.4.1.351.110.5.2.1.3.1.1.1.24 |
egrRcvUtilizationThe percentage utilization of the port speed
in the egress receive direction.ro Gauge .1.3.6.1.4.1.351.110.5.2.1.3.1.1.1.25 |
totalIngrQfulldiscardCellsThe total number of cells dropped on all the channels
on this port because the the ingress Q was full. Adds
up all the IngressQfull discard per channel statistics
for all the channels in the port.ro Counter .1.3.6.1.4.1.351.110.5.2.1.3.1.1.1.26 |
txFifoFullCntThis statistics provides a count of the number of times the AUSM
card tried to send a cell, but was unable to send because the
Transmit FIFO was full. Note that this is NOT a count of the number
of cells dropped. This statistics is per card statistics. This
counter is duplicated in channel count group to help monitoring.ro Counter .1.3.6.1.4.1.351.110.5.2.1.3.1.1.1.27 |
totalIngrClpSetDiscardCellsThe total number of cells with CLP=1 dropped on all the
channels on this port because of either PCR Exceeded,
SCR exceeded (with CLP tagging disabled) or CLP Hysteris.
Adds up all the IngressClpSet discard per channel statistics
for all the channels in the port.ro Counter .1.3.6.1.4.1.351.110.5.2.1.3.1.1.1.28 |
ausmPortCntSig OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.5.2.1.3.2 |
ausmPortCntSigILMIGrp OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.5.2.1.3.2.1 |
ausmPortCntSigILMIGrpTableThe config table is for physical port interface
there are 8 entries for either T1 or E1 or IMA SEQUENCE OF AusmPortCntSigILMIGrpEntry .1.3.6.1.4.1.351.110.5.2.1.3.2.1.1 |
ausmPortCntSigILMIGrpEntryAn entry for logical port. In AUSM (4-port card), a logical port
is same as a physical port. AusmPortCntSigILMIGrpEntry .1.3.6.1.4.1.351.110.5.2.1.3.2.1.1.1 |
sigCntPortNumThis is the logical port number.ro INTEGER .1.3.6.1.4.1.351.110.5.2.1.3.2.1.1.1.1 |
snmpPduReceivedThe number of snmp packets receivedro Counter .1.3.6.1.4.1.351.110.5.2.1.3.2.1.1.1.2 |
getRequestReceivedThe number of get request messages receivedro Counter .1.3.6.1.4.1.351.110.5.2.1.3.2.1.1.1.3 |
getNextRequestReceivedThe number of get-next messages receivedro Counter .1.3.6.1.4.1.351.110.5.2.1.3.2.1.1.1.4 |
setRequestReceivedThe number of set messages receivedro Counter .1.3.6.1.4.1.351.110.5.2.1.3.2.1.1.1.5 |
trapReceivedThe number of traps receivedro Counter .1.3.6.1.4.1.351.110.5.2.1.3.2.1.1.1.6 |
getResponseReceivedThe number of Keep Alive response messages receivedro Counter .1.3.6.1.4.1.351.110.5.2.1.3.2.1.1.1.7 |
getResponseTransmittedThe number of response messages transmittedro Counter .1.3.6.1.4.1.351.110.5.2.1.3.2.1.1.1.8 |
getRequestTransmittedThe number of Keep Alive get request messages transmittedro Counter .1.3.6.1.4.1.351.110.5.2.1.3.2.1.1.1.9 |
trapTransmittedThe number of trap messages transmittedro Counter .1.3.6.1.4.1.351.110.5.2.1.3.2.1.1.1.10 |
invalidPDUReceivedThe number of invalid PDUs receivedro Counter .1.3.6.1.4.1.351.110.5.2.1.3.2.1.1.1.11 |
asn1ParseErrorThe number of parse errors on ASN.1ro Counter .1.3.6.1.4.1.351.110.5.2.1.3.2.1.1.1.12 |
noSuchNameErrorThe number of errors for name not presentro Counter .1.3.6.1.4.1.351.110.5.2.1.3.2.1.1.1.13 |
tooBigErrorThe number of messages received with len > 484ro Counter .1.3.6.1.4.1.351.110.5.2.1.3.2.1.1.1.14 |
portSigClrButtonwriting a value of 2 resets all the countersrw Enumeration .1.3.6.1.4.1.351.110.5.2.1.3.2.1.1.1.15 |
ausmPortCntPortImaGrp OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.5.2.1.3.3 |
ausmPortCntPortImaGrpTableThe counter table is for the IMA groups (8 possible entries) SEQUENCE OF AusmPortCntPortImaGrpEntry .1.3.6.1.4.1.351.110.5.2.1.3.3.1 |
ausmPortCntPortImaGrpEntryAn entry for the IMA group AusmPortCntPortImaGrpEntry .1.3.6.1.4.1.351.110.5.2.1.3.3.1.1 |
imaCntPortNumThis is the logical port number.
This object does not have any default value.ro INTEGER .1.3.6.1.4.1.351.110.5.2.1.3.3.1.1.1 |
rcvAcpCellsThis is the number of ICP cells received.
This object does not have any default value.ro Counter .1.3.6.1.4.1.351.110.5.2.1.3.3.1.1.2 |
rcvAcpErrCellsThis is the number of errored ICP cells on this IMA
group.
This object does not have any default value.ro Counter .1.3.6.1.4.1.351.110.5.2.1.3.3.1.1.3 |
xmtAcpCellsThis is the number of ACP cells transmitted on this IMA group.
This object does not have any default value.
Not supported in Forum Compliant Ima.ro Counter .1.3.6.1.4.1.351.110.5.2.1.3.3.1.1.4 |
xmtAcpCellsMissedThis is the number of ACP cells that could not be transmitted on
this IMA group due to lack of resources (buffers).
This object does not have any default value.
Not supported in Forum Compliant Ima.ro Counter .1.3.6.1.4.1.351.110.5.2.1.3.3.1.1.5 |
imaGrpRcvHecErrCountThis is the number of HEC errored cells received on all the links
currently in the IMA group
This object does not have any default value.ro Counter .1.3.6.1.4.1.351.110.5.2.1.3.3.1.1.6 |
imaGrpRcvHecErrSecCountThis is the number of HEC errored seconds for the IMA group
that is the number of seconds in which at least one link in the
IMA group experienced a HEC error
This object does not have any default value.ro Counter .1.3.6.1.4.1.351.110.5.2.1.3.3.1.1.7 |
imaGrpRcvHecErrSESecCountThis is the number of severely errored seconds received on all the
links currently in the IMA group. A severely errored second
for an IMA group is defined if the following condn is true:
if (sigma (number of HEC errors of all links in IMA group) >
(HEC_SE_COUNT * nlinks)) where HEC_SE_COUNT is defined as 10
This object does not have any default value.ro Counter .1.3.6.1.4.1.351.110.5.2.1.3.3.1.1.8 |
imaCntClrButtonwriting a value of 2 resets all the counters
This object does not have any default value.rw Enumeration .1.3.6.1.4.1.351.110.5.2.1.3.3.1.1.9 |
axisImaGroupRunningSecsThe amount of time(in seconds) since this IMA group has been
in opeartion(UP or DOWN.)ro INTEGER .1.3.6.1.4.1.351.110.5.2.1.3.3.1.1.10 |
axisImaGroupUnavailSecsCount of one second intervals where IMA group traffic state
machine is down.ro INTEGER .1.3.6.1.4.1.351.110.5.2.1.3.3.1.1.11 |
axisImaGroupNeNumFailuresThe number of times a near-end group failure(Config-abort,
Insufficient-Links) has been reported since power-up or reboot.ro INTEGER .1.3.6.1.4.1.351.110.5.2.1.3.3.1.1.12 |
axisImaGroupFeNumFailuresThe number of times a far-end group failure(config-abort-FE,
Insufficient-links-FE,Blocked-FE) has been reported since power-up
or reboot.ro INTEGER .1.3.6.1.4.1.351.110.5.2.1.3.3.1.1.13 |
ausmPortStateImaGrp OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.5.2.1.4 |
ausmPortStateImaGrpTableThe state table for the IMA port interface:
there are 8 entries for the 8 (maximum possible) IMA groups SEQUENCE OF AusmPortStateImaGrpEntry .1.3.6.1.4.1.351.110.5.2.1.4.1 |
ausmPortStateImaGrpEntryAn entry for every IMA group AusmPortStateImaGrpEntry .1.3.6.1.4.1.351.110.5.2.1.4.1.1 |
imaStatePortNumThis is the logical port number
This object does not have any default valuero INTEGER .1.3.6.1.4.1.351.110.5.2.1.4.1.1.1 |
imaPortStateIndicates the state of the IMA port. The following error
conditions are currently reported:
1 - Unconfigured state
2 - Active state
3 - Bandwidth changed due to addition/deletion of links. The
addition/deletion can be triggered by either end
4 - FailedDueToACPTimeout (indicates that a timeout occurred due
to non-arrival of an ACP cell)
5 - FailedDueToMajorAlarmOnIMAGroup (issued when the bandwidth
of an IMA group falls below a certain threshold due to loss
of links from an IMA group)
6 - FailedDueToImaSigFailure (this indicates configuration
mismatch or non-arrival of LCP cells during set up of
an IMA group)
7 - FailedDueToBadDiffDelay (indicates that the differential
delay exceeded the maximum threshold)
8 - FailedDueToArbConflict (indicates that the IMA-ID could
not be resolved between the 2 ends of the IMA pipe)
9 - Receiving Local OAM AIS from peer IMA node (valid only for
network modules)
10- Receiving LOAM RDI from peer IMA node (valud only for
network modules)
20- Failed due to ILMI signalling failure
This object does not have any default valuero Enumeration .1.3.6.1.4.1.351.110.5.2.1.4.1.1.2 |
numLinksPresentInImaGroupIndicates the number of links that are currently present in
the IMA group.
This object does not have any default value
Same as axisImaGroupNumTxActLnks in Forum Compliant Ima.ro INTEGER .1.3.6.1.4.1.351.110.5.2.1.4.1.1.3 |
listLinksPresentInImaGroupIndicates the list of links currently present in the IMA
group. Different links in the IMA group are delimited by
dots. The position of each link in the displayed string indicates
the relative order of the links in the round-robin (multiplexing
order)
This object does not have any default valuero DisplayString .1.3.6.1.4.1.351.110.5.2.1.4.1.1.4 |
remoteImaIdIndicates the IMA-ID in use at the remote end when sending
LCP/ACP cells.
Same as axisImaGroupRxImaId in Forum Compliant Ima .
This object does not have any default valuero INTEGER .1.3.6.1.4.1.351.110.5.2.1.4.1.1.5 |
locImaIdIndicates the IMA-ID in use at the local end when sending
LCP/ACP cells.
This is same as axisImaGroupTxImaId in Forum Compliant Ima
This object does not have any default valuero INTEGER .1.3.6.1.4.1.351.110.5.2.1.4.1.1.6 |
imaArbitrationWinnerResult of arbitration between the two ends of the IMA pipe.
This object does not have any default value
Retaining for the backward compatibility.
Not supported in Forum Compliant Ima.ro Enumeration .1.3.6.1.4.1.351.110.5.2.1.4.1.1.7 |
imaObsDiffDelayThe observed differential delay in milliseconds between the
different physical links in the IMA group
This object does not have any default value
Same as axisImaGroupDiffDelayMaxObs in Forum Compliant Ima.ro INTEGER .1.3.6.1.4.1.351.110.5.2.1.4.1.1.8 |
imaPortOversubscribedThis variable indicates whether the port is over-subscribed or
not
This object does not have any default valuero Enumeration .1.3.6.1.4.1.351.110.5.2.1.4.1.1.9 |
imaPortIngrPercentUtilPercent Utilization of the IMA Port in the Ingress direction
This object does not have any default valuero INTEGER .1.3.6.1.4.1.351.110.5.2.1.4.1.1.10 |
imaPortEgrPercentUtilPercent Utilization of the IMA Port in the Egress direction
This object does not have any default valuero INTEGER .1.3.6.1.4.1.351.110.5.2.1.4.1.1.11 |
axisImaGroupRxAvailCellRateThe current cell-rate (truncated value in cells per second)
provided by this IMA group in the receive direction,considering
all the receive links in the active state.ro INTEGER .1.3.6.1.4.1.351.110.5.2.1.4.1.1.12 |
axisImaGroupFeStateThe current operational state of the far-end IMA group state
machine
1) notConfigured : The Group doesn't exist.This is the GSM
initial state.
2) startUp : On UM configuring the IMA group,GSM comes to
this state.
3) startUpAck : On getting the Start-up-ack from FE(this info
from received ICP cell. i.e. FE accepting the proposed group parameters by this END.),
GSM goes to this state.
4) configAbortUnsupportedM : This state is entered when FE is
not accepting the parameter M.
5) configAbortIncompatibleSymmetry : When Group symmetry is not
supported by the FE,this group is entered.
6) configAbortOther : If any of the other group parameters are
not supported by the FE,then this state is entered.
7) insufficientLinks : On getting one of the following events
from FE, when GSM is in startUpAck state,GSM moves to
insufficientLinks state.
evens : 1) Start-up-ack 2) insufficient links
3) Blocked or operational
8) blocked : For to maintenance purpose,if group is blcoked
(inhibited by UM),GSM goes to this state.
9) operational : When the group has sufficient links in both Tx and Rx directions GSM goes to this state.ro Enumeration .1.3.6.1.4.1.351.110.5.2.1.4.1.1.13 |
axisImaGroupFailureStatusThe current failure status of the IMA group(the reason why
the GTSM is in the DOWN state.
1) noFailure : The group is UP.
2) startUpNe : When the NE GSM is in startUp state.
3) startUpFe : When the FE GSM is in startUp state.
4) invalidMValueNe : If FE doesn't support M value this end
5) invalidMValueFe : When the FE M value is not supported by NE.
6) failedAssymetricNe : If FE doesn't support Assymetric
operation of the NE.
7) failedAssymetricFe : When the FE assymetry is not supported
by the NE.
8) insufficientLinksNe: When the NE is in insufficient links
state
9) insufficientLinksFe: If the FE is in insufficient links
state and if that message is conveyed to this
end by ICP cell.
10) blockedNe : If the GSM is in blocked state.
11) blockedFe : If the FE is in blocked state.
12) otherFailure: Start-up-ack and others.ro Enumeration .1.3.6.1.4.1.351.110.5.2.1.4.1.1.14 |
axisImaGroupFeTxClkModeTransmit clocking mode used by the far-end IMA group.ro Enumeration .1.3.6.1.4.1.351.110.5.2.1.4.1.1.15 |
axisImaGroupTxTimingRefLinkThe IfIndex of the transmit timing reference link to be used by the
near-end for IMA data cell clock recovery from the ATM layer.ro INTEGER .1.3.6.1.4.1.351.110.5.2.1.4.1.1.16 |
axisImaGroupRxTimingRefLinkThe IfIndex of the receive timing reference link to be used by
the near-end for IMA data cell clock recovery toward the ATM layer.ro INTEGER .1.3.6.1.4.1.351.110.5.2.1.4.1.1.17 |
axisImaGroupLastChangeThe time-of-day the IMA group last changed operational state(
i.e. value of axisImaGroupNeState changed.)
SPLAY-HINT 2d-1d-1d,1d:1d:1d.1d,1a1d:1d
field octets contents range
-
1 1-2 year 0..65536
2 3 month 1..12
3 4 day 1..31
4 5 hour 0..23
5 6 minutes 0..59
6 7 seconds 0..60
(use 60 for leap-second)
7 8 deci-seconds 0..9
8 9 direction from UTC '+' / '-'
9 10 hours from UTC 0..11
10 11 minutes from UTC 0..59
For example, Tuesday May 26, 1992 at 1:30:15 PM
EDT would be displayed as:
1992-5-26,13:30:15.0,-4:0
Note that if only local time is known,then,timezone information
(fields 8- 10) is not present.
This variable is not supported anymore in forum Ima.ro OCTET STRING( SIZE (11) ) .1.3.6.1.4.1.351.110.5.2.1.4.1.1.18 |
axisImaGroupRxFrameLengthValue of IMA frame length as received from remote IMA function.ro Enumeration .1.3.6.1.4.1.351.110.5.2.1.4.1.1.19 |
axisImaGroupLeastDelayLinkThe IfIndex of the link configured in the IMA group which has
the smallest link propagation delay. This value has meaning only
if at least 1 link has been configured in IMA group.ro INTEGER .1.3.6.1.4.1.351.110.5.2.1.4.1.1.20 |
axisImaGroupNumRxActLnksThe number of links which are configured to receive and are
currently Active in this IMA group.ro INTEGER .1.3.6.1.4.1.351.110.5.2.1.4.1.1.21 |
axisImaGroupNeStateThe current operational state of the near-end IMA group state
machine.
1) notConfigured : The Group doesn't exist.This is the GSM
initial state.
2) startUp : On UM configuring the IMA group,GSM comes to
this state.
3) startUpAck : On getting the Start-up-ack from FE(this info
from received ICP cell. i.e. FE accepting the proposed group parameters by this END.),
GSM goes to this state.
4) configAbortUnsupportedM : This state is entered when FE is
not accepting the parameter M.
5) configAbortIncompatibleSymmetry : When Group symmetry is not
supported by the FE,this group is entered.
6) configAbortOther : If any of the other group parameters are
not supported by the FE,then this state is entered.
7) insufficientLinks : On getting one of the following events
from FE, when GSM is in startUpAck state,GSM moves to
insufficientLinks state.
evens : 1) Start-up-ack 2) insufficient links
3) Blocked or operational
8) blocked : For to maintenance purpose,if group is blcoked
(inhibited by UM),GSM goes to this state.
9) operational : When the group has sufficient links in both Tx and Rx directions GSM goes to this state.ro Enumeration .1.3.6.1.4.1.351.110.5.2.1.4.1.1.22 |
axisImaGroupNumberThe number of IMA groups configured with the lines.ro INTEGER .1.3.6.1.4.1.351.110.5.2.1.4.2 |
ausmPortInterfaceGrp OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.5.2.1.5 |
ausmInterfaceConfTableThis table contains ATM local interface
configuration parameters, one entry per ATM (ausm)
interface port. SEQUENCE OF AusmInterfaceConfEntry .1.3.6.1.4.1.351.110.5.2.1.5.1 |
ausmInterfaceConfEntryThis list contains ATM interface configuration
parameters and state variables and is indexed
by ausmInterfacePortNum values of ATM interfaces. AusmInterfaceConfEntry .1.3.6.1.4.1.351.110.5.2.1.5.1.1 |
ausmInterfacePortNumThis is logical port number. In AUSM, a logical port
is same as a physical port.ro INTEGER .1.3.6.1.4.1.351.110.5.2.1.5.1.1.1 |
ausmInterfaceMyNeighborIpAddressThe IP address of the neighbor system connected to
the far end of this interface, to which a Network
Management Station can send SNMP messages, as IP
datagrams sent to UDP port 161, in order to access
network management information concerning the
operation of that system. Note that the value
of this object may be obtained in different ways,
e.g., by manual configuration, or through ILMI
interaction with the neighbor system.ro IpAddress .1.3.6.1.4.1.351.110.5.2.1.5.1.1.2 |
ausmChanCnfGrp OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.5.2.2.1 |
ausmChanCnfGrpTableThe config table is for logical channel interface
there are 1000 entries for the 8 logical ports in AUSM (8-port)
and 256 entries for the 4 logical ports in AUSM (4-port card).
In AUSM (4-port card), a logical port is same as a physical
port. SEQUENCE OF AusmChanCnfGrpEntry .1.3.6.1.4.1.351.110.5.2.2.1.1 |
ausmChanCnfGrpEntryAn entry for logical channel AusmChanCnfGrpEntry .1.3.6.1.4.1.351.110.5.2.2.1.1.1 |
ausmChanNumRefers to the virtual connection index. In AUSM (4-port card),
valid range is from 16..271.ro INTEGER .1.3.6.1.4.1.351.110.5.2.2.1.1.1.1 |
ausmChanRowStatusThis will add, delete or modify the channel
1 ==> ADD
2 ==> DELETE
3 ==> MODIFY
Setting this object to outOfService takes the channel
out of service or brings the channel 'down'. The channel
can be brought 'up' again by setting the object to modrw Enumeration .1.3.6.1.4.1.351.110.5.2.2.1.1.1.2 |
chanConnTypeThis specifies the connection type
1 ==> Virtual Path Connection
2 ==> Virtual Channel Connectionrw Enumeration .1.3.6.1.4.1.351.110.5.2.2.1.1.1.3 |
chanServiceTypeThis specifies the service type
1 ==> Constant Bit Rate
2 ==> Variable Bit Rate
3 ==> Available Bit Rate
4 ==> Unspecified Bit Rate
5 ==> Real-Time Variable Bit Raterw Enumeration .1.3.6.1.4.1.351.110.5.2.2.1.1.1.4 |
chanConnDescA string that has been defined to give a
descriptive name to the connectionrw DisplayString .1.3.6.1.4.1.351.110.5.2.2.1.1.1.5 |
chanSvcFlagThis specifies the connection type
1 ==> SVC connection
2 ==> PVC connection
3 ==> SPVC connection
4 ==> connection added by PAR
5 ==> connection added by PNNI
6 ==> connection added by TAGrw Enumeration .1.3.6.1.4.1.351.110.5.2.2.1.1.1.6 |
chanSvcConnIdThis connection ID is for future use
Currently not supportedrw INTEGER .1.3.6.1.4.1.351.110.5.2.2.1.1.1.7 |
ausmChanPortNumRefers to the logical port on the board to which
logical channel is associated. In AUSM (4-port card), a
logical port is same as a physical port.rw INTEGER .1.3.6.1.4.1.351.110.5.2.2.1.1.1.8 |
chanVpiThe VPI value for this channelrw INTEGER (0..'ff'h) .1.3.6.1.4.1.351.110.5.2.2.1.1.1.9 |
chanVciThe VCI value for this channelrw INTEGER (0..'ffff'h) .1.3.6.1.4.1.351.110.5.2.2.1.1.1.10 |
chanEgrQSelectSelects one out of the 16 possible queues
Each queue may have a different service algorithmrw INTEGER .1.3.6.1.4.1.351.110.5.2.2.1.1.1.11 |
ingrQDepthThis variable sets the max depth for queue, before
it starts dropping the cells. In AUSM (4-port card), the
valid range is from 1..8000.rw INTEGER .1.3.6.1.4.1.351.110.5.2.2.1.1.1.12 |
ingrQCLPThreshHighThis variable sets the higher threshold for
dropping CLP set cells in the ingress direction. In AUSM
(4-port card), the valid range is from 1..8000.This value
should be less than or equal to ingrQDepth.
Default value depends on the ingrQDepth.rw INTEGER .1.3.6.1.4.1.351.110.5.2.2.1.1.1.13 |
ingrQCLPThreshLowThis variable sets the lower threshold for dropping CLP set
cells in the ingress direction. In AUSM (4-port card), the
valid range is from 1..8000.This value should be less than
or equal to ingrQCLPThreshHigh.
Default value depends on the ingrQDepth.rw INTEGER .1.3.6.1.4.1.351.110.5.2.2.1.1.1.14 |
ingrQCLPStateThis variable indicates the CLP state for
the channelro Enumeration .1.3.6.1.4.1.351.110.5.2.2.1.1.1.15 |
ingrQEfciThreshThis variable sets the efci threshold value for setting efci bit
in the ingress direction. In AUSM (4-port card), the
valid range is from 1..8000.This value should be less than
or equal to ingrQDepth.rw INTEGER .1.3.6.1.4.1.351.110.5.2.2.1.1.1.16 |
ingrUpcEnableenables/disables UPC for Ingress cellsrw Enumeration .1.3.6.1.4.1.351.110.5.2.2.1.1.1.17 |
ingrUpcPCR01Peak Cell Rate for CLP [0+1] cells. The actual value
depends on the speed of the logical port (which can be
a T1, E1 (normal), E1 (clear), IMA T1, IMA E1 (normal) or
IMA E1 (clear) port. Note that the IMA port's speed is
variable and depends on the number of links in the port. In
AUSM (4-port), maximum value is 4830.rw INTEGER .1.3.6.1.4.1.351.110.5.2.2.1.1.1.18 |
ingrUpcCIRComplaint Information Rate. The actual value
depends on the speed of the logical port (which can be
a T1, E1 (normal), E1 (clear), IMA T1, IMA E1 (normal) or
IMA E1 (clear) port. Note that the IMA port's speed is
variable and depends on the number of links in the port. In
AUSM (4-port), maximum value is 4830.rw INTEGER .1.3.6.1.4.1.351.110.5.2.2.1.1.1.19 |
ingrUpcCCDVComplaint Cell Delay Variation for all cellsrw INTEGER .1.3.6.1.4.1.351.110.5.2.2.1.1.1.20 |
ingrUpcCBSComplaint Burst Size
The unit of this parameter is in terms of number of cells.
CBS is applicable only for VBR and ABR connections.
In MGX switches, release 3.0.0.0 and above,
the default value is 1024rw INTEGER .1.3.6.1.4.1.351.110.5.2.2.1.1.1.21 |
ingrUpcIBSInitial Burst Size.
The Burst size allowed for a connection that has been
idle for some time. The unit of this parameter is in
terms of number of cells.
IBS is applicable only for VBR and ABR connections.
IBS value should be less than CBS for VBR and ABR connections.
IBS value will be ignored for other service types.rw INTEGER .1.3.6.1.4.1.351.110.5.2.2.1.1.1.22 |
ingrUpcMFSMaximum Frame Sizerw INTEGER .1.3.6.1.4.1.351.110.5.2.2.1.1.1.23 |
ingrUpcSCRPolicingselects SCR policing for CLP = 0 or all cellsrw Enumeration .1.3.6.1.4.1.351.110.5.2.2.1.1.1.24 |
ingrUpcPCR0Peak Cell Rate for CLP=0 cells. The actual value
depends on the speed of the logical port (which can be
a T1, E1 (normal), E1 (clear), IMA T1, IMA E1 (normal) or
IMA E1 (clear) port. Note that the IMA port's speed is
variable and depends on the number of links in the port. In
AUSM (4-port), maximum value is 4830.rw INTEGER .1.3.6.1.4.1.351.110.5.2.2.1.1.1.25 |
ingrUpcCDVT0Complaint Cell Delay Variation for CLP=0 cellsrw INTEGER .1.3.6.1.4.1.351.110.5.2.2.1.1.1.26 |
ingrUpcCLPTagEnableenables/disables CLP tagging for Ingress cellsrw Enumeration .1.3.6.1.4.1.351.110.5.2.2.1.1.1.27 |
ingrUpcFGCRAEnableenables/disables Frame based GCRArw Enumeration .1.3.6.1.4.1.351.110.5.2.2.1.1.1.28 |
foresightEnableenables/disables Foresightrw Enumeration .1.3.6.1.4.1.351.110.5.2.2.1.1.1.29 |
foresightMIRMinimum Information Rate. The actual value
depends on the speed of the logical port (which can be
a T1, E1 (normal), E1 (clear), IMA T1, IMA E1 (normal) or
IMA E1 (clear) port. Note that the IMA port's speed is
variable and depends on the number of links in the port. In
AUSM (4-port), maximum value is 4830.rw INTEGER .1.3.6.1.4.1.351.110.5.2.2.1.1.1.30 |
foresightPIRPeak Information Rate. The actual value
depends on the speed of the logical port (which can be
a T1, E1 (normal), E1 (clear), IMA T1, IMA E1 (normal) or
IMA E1 (clear) port. Note that the IMA port's speed is
variable and depends on the number of links in the port. In
AUSM (4-port), maximum value is 4830.rw INTEGER .1.3.6.1.4.1.351.110.5.2.2.1.1.1.31 |
foresightQIRQuiescent Information Rate. The actual value
depends on the speed of the logical port (which can be
a T1, E1 (normal), E1 (clear), IMA T1, IMA E1 (normal) or
IMA E1 (clear) port. Note that the IMA port's speed is
variable and depends on the number of links in the port. In
AUSM (4-port), maximum value is 4830.rw INTEGER .1.3.6.1.4.1.351.110.5.2.2.1.1.1.32 |
ausmChanLocRmtLpbkStateThe default is disable.
This variable enables or disables the remote loopback for each
channel.
When you enable this option on a connection (channel) then all the
cells that are coming from the network side would be looped back
toward the network and all the frames coming from the user side
would be dropped.
This channel remote loopback has nothing to do with the chanTestType
option, each one does a different function.
For example, the channel remote loopback is used for looping the data
toward the network and if this connection is terminated on an IPX
then they can put a test equipment and measure some of the
characteristics of the network.
1 = enable
2 = disablerw Enumeration .1.3.6.1.4.1.351.110.5.2.2.1.1.1.33 |
ausmChanTestTypeThe default is notest.
The chanTestType starts testing the continuity or delay of a connection.
It sends specific cell patterns toward the network and the terminating
end of this connection has to be an AXIS or ASI of a BPX in order for
this test to be working.
The receiving node would loop back when it receives these
cells. The test should be done in about couple of seconds. The testcon
tests the continuity of the connection and testdelay uses the same
test except that it measures for delay through the network.
To test the delay follow this procedure:
a- set chanTestType to testdelay
b- read chanTestState till it is Pass or Fail
c- Read chanRTDResult for the delay if it is Pass
*Note that the chanTestType would go back to notest when the
test is completed
To test the continuity follow this procedure:
a- set chanTestType to testcon
b- read chanTestState till it is Pass or Fail
*Note that the chanTestType would go back to notest when the
test is completed
You CAN NOT select 2 tests back to back, you have selcelt one and wait
the result and then start the other one.
SYNTAX
When you select testdelay
This is the type of the test
1 = Test Continuity
2 = Test Delay
3 = No Testrw Enumeration .1.3.6.1.4.1.351.110.5.2.2.1.1.1.34 |
ausmChanTestStateThis shows the state of the test
When you add a connection then the chanTestState becomes notinprogress
and when you select any test, it would go to inprogress state and after
it completes the test, it will go to failed or passed state.
1 = Passed
2 = Failed
3 = In Progress
4 = Not In Progressro Enumeration .1.3.6.1.4.1.351.110.5.2.2.1.1.1.35 |
ausmChanRTDResultThis is round trip delay in milliseconds.
When you select testdelay option for the chanTestType, the result of
the test that is measured in milliseconds can be read in chanRTDResult.ro INTEGER .1.3.6.1.4.1.351.110.5.2.2.1.1.1.36 |
ausmChanTestTypeCPESideThe default is notest.
The chanTestType starts testing the segment continuity of a connection.
It sends OAM Segment loopback cell towards port side (CPE)
The CPE would loop back the cell
To test the continuity follow this procedure:
a- set chanTestTypeCPEside to testconseg
b- read chanTestState till it is Pass or Fail
*Note that the chanTestType would go back to notest when the
test is completed
SYNTAX
When you select testdelay
This is the type of the test
1 = Test Continuity
2 = No Testrw Enumeration .1.3.6.1.4.1.351.110.5.2.2.1.1.1.37 |
ausmChanTestStateCPESideThis shows the state of the test
When you add a connection then the chanTestState becomes notinprogress
and when you select any test, it would go to inprogress state and after
it completes the test, it will go to failed or passed state.
1 = Passed
2 = Failed
3 = In Progress
4 = Not In Progressro Enumeration .1.3.6.1.4.1.351.110.5.2.2.1.1.1.38 |
ausmChanIngrPercentUtilPercentage Utilization of the IngrService Rate. This is used
for connection admission control.rw INTEGER .1.3.6.1.4.1.351.110.5.2.2.1.1.1.39 |
ausmChanEgrPercentUtilPercentage Utilization of the EgrService Rate. This is used for
egress bandwidth calculation and connection admission control.rw INTEGER .1.3.6.1.4.1.351.110.5.2.2.1.1.1.40 |
ausmChanEgrSrvRateEgress service rate - This is used for egress bandwidth calculation
and for connection admission control. The actual value
depends on the speed of the logical port (which can be
a T1, E1 (normal), E1 (clear), IMA T1, IMA E1 (normal) or
IMA E1 (clear) port. Note that the IMA port's speed is
variable and depends on the number of links in the port. In
AUSM (4-port), maximum value is 4830.rw INTEGER .1.3.6.1.4.1.351.110.5.2.2.1.1.1.41 |
ausmChanOvrSubOvrRideThis MIB variable allows one to add a new connection on a port
even if it is over subscribed.rw Enumeration .1.3.6.1.4.1.351.110.5.2.2.1.1.1.42 |
ausmChanLocalVpIdEvery VP connection will have a unique local VpId between
1 to 340. This is sent to ASC at the time of vp connection
setup. This number along with the slot number will form a
number which is unique across the shelf. This will be set
only at the time adding the connection.
This range varies dpending on the BNM interface.
For STI 1..100
For UNI 1..20
For NNI 1..340
In case of AUSM-4P maximum localVpId can be only 1..255rw INTEGER .1.3.6.1.4.1.351.110.5.2.2.1.1.1.43 |
ausmChanRMEnableenables/disables sending Resource Mangement Cellsrw Enumeration .1.3.6.1.4.1.351.110.5.2.2.1.1.1.44 |
ausmIngrDiscardOptionThis variable specifies whether Frame based Discard is to be
enabled or CLP Threshold is to be used for determining the
criterion for dropping cells. FrameDiscard enables the EPD/PPD
featuresrw Enumeration .1.3.6.1.4.1.351.110.5.2.2.1.1.1.45 |
ausmIngrFrDiscardThresholdThis variable specifies the Ingress Frame Discard Threshold.
Valid only when Ingress Frame Discard option is selected. By
default, the value of this variable would be the peak queue
depth of the queue. The value of this variable should be less
than the peak queue depth that is configured for the queuerw INTEGER .1.3.6.1.4.1.351.110.5.2.2.1.1.1.46 |
ausmCDRNumberThis is the key to correlate cell/frame counts, start/end record.rw INTEGER .1.3.6.1.4.1.351.110.5.2.2.1.1.1.47 |
ausmLocalVpiThis VPI has different meaning with the end point VPI (CPE),
it can be same with the end point VPI but not necessary,
it represents the local end point VPI, this object is
read only, therefore, SM is responsible to assign a value
to it.ro INTEGER .1.3.6.1.4.1.351.110.5.2.2.1.1.1.48 |
ausmLocalVciThis VCI has different meaning with the end point VCI (CPE),
it can be same with the end point VPI but not necessary
it represents the local end point VCI, this object is
read only, therefore, SM is responsible to assign a value
to it.ro INTEGER .1.3.6.1.4.1.351.110.5.2.2.1.1.1.49 |
ausmLocalNSAPThis NSAP is 20 bytes binary, among these 20 bytes: 13 bytes
as prefix, 2 bytes for Cisco ID, 2 bytes rsvd, 2 bytes for
slot (5 bits) and port number (11 bits), and 1 byte for SELrw OCTET STRING .1.3.6.1.4.1.351.110.5.2.2.1.1.1.50 |
ausmRemoteVpiThis VPI has different with the remote end point VPI (CPE),
this is similar to a connection ID and it can be same
with the remote end point VPI but not necessaryrw INTEGER .1.3.6.1.4.1.351.110.5.2.2.1.1.1.51 |
ausmRemoteVciThis VCI has different with the remote end point VCI (CPE),
this is similar to a connection ID and it can be same
with the remote end point VPI but not necessaryrw INTEGER .1.3.6.1.4.1.351.110.5.2.2.1.1.1.52 |
ausmRemoteNSAPThis NSAP is 20bytes binary, among these 20 bytes: 13 bytes
as prefix, 2 bytes for Cisco ID, 2 bytes rsvd, 2 bytes for
slot (5 bits) and port number (11 bits), and 1 byte for SELrw OCTET STRING .1.3.6.1.4.1.351.110.5.2.2.1.1.1.53 |
ausmMastershipThis is used by PXM to determine if this end point is
master or slave. In AXIS shelf, unknown is always used,
but in MGX shelf, if unknown is set, PXM will fail
the set request.rw Enumeration .1.3.6.1.4.1.351.110.5.2.2.1.1.1.54 |
ausmVpcFlagThis represents the connection type, used for PXM to
identify VPC/VCCrw Enumeration .1.3.6.1.4.1.351.110.5.2.2.1.1.1.55 |
ausmConnServiceTypeThis specifies the service type
1 ==> Constant Bit Rate
2 ==> Variable Bit Rate
3 ==> Not used
4 ==> Unspecified Bit Rate
5 ==> ATM frame relay
6 ==> standard ABR
7 ==> foresight ABR
8 ==> Real-Time Variable Bit Rate
Note that this is used by PXM card, FRSM doesn't need to set it
Also to make it compatible with existing AUSM MIB definition,
value 3 is not used.
The following types are being added for PNNI support.
and are based on UNI 4.0
cbr1 (21) - CBR.1
vbr1rt (22) - Real time VBR.1
vbr2rt (23) - Real time VBR.2
vbr3rt (24) - Real time VBR.3
vbr1nrt(25) - Non Real time VBR.1
vbr2nrt(26) - Non Real time VBR.2
vbr3nrt(27) - Non Real time VBR.3
ubr1 (28) - UBR.1
ubr2 (29) - UBR.2
stdabr (30) - TM 4.0 compliant standard ABR
cbr2 (31) - CBR.2
cbr3 (32) - CBR.3rw Enumeration .1.3.6.1.4.1.351.110.5.2.2.1.1.1.56 |
ausmRoutingPriorityThis is also known as class of service, it is used by
PXM to determine how important this connection is when
selecting connections to routerw INTEGER .1.3.6.1.4.1.351.110.5.2.2.1.1.1.57 |
ausmMaxCostMaximum allowed cost. It is related to Cost Based Routing.
This is used by PXM so that it won't choose a path with
a cost greater than this configured level.
When used with PAR controller the valid range is 1..65535 and the
default value is 255.
When used with PNNI controller the valid range is 1..2147483647 and
the default value is 2147483647.rw INTEGER .1.3.6.1.4.1.351.110.5.2.2.1.1.1.58 |
ausmRestrictTrunkTypeRestricted trunk type for routing, used by PXM. It
specifies that the connection either cannot be routed over
satelite trunks, or terrestrial trunks, or it can be on
any type of trunk.rw Enumeration .1.3.6.1.4.1.351.110.5.2.2.1.1.1.59 |
ausmConnPCRPeak cell rate, if not set in MGX, will be derived
from the end point parameterrw INTEGER .1.3.6.1.4.1.351.110.5.2.2.1.1.1.60 |
ausmConnMCRMinimum cell rate, if not set in MGX, will be derived
from the end point parameterrw INTEGER .1.3.6.1.4.1.351.110.5.2.2.1.1.1.61 |
ausmConnPercentUtilThis is the expected long-term utilization of the
channel by theis end-point.rw INTEGER .1.3.6.1.4.1.351.110.5.2.2.1.1.1.62 |
ausmConnRemotePCRPeak cell rate of the other end, if not set in MGX, will be
derived from the end point parameterrw INTEGER .1.3.6.1.4.1.351.110.5.2.2.1.1.1.63 |
ausmConnRemoteMCRMinimum cell rate of the other end, if not set in MGX, will be
derived from the end point parameterrw INTEGER .1.3.6.1.4.1.351.110.5.2.2.1.1.1.64 |
ausmConnRemotePercentUtilThis is the expected long-term utilization of the
channel by the other end-point.rw INTEGER .1.3.6.1.4.1.351.110.5.2.2.1.1.1.65 |
ausmConnForeSightEnableThis object is used by the controller(PAR/PNNI/TAG) to set up
the Qbin for the connectionrw Enumeration .1.3.6.1.4.1.351.110.5.2.2.1.1.1.66 |
ausmConnFGCRAEnableenables/disables Frame based GCRA (early packet discard).rw Enumeration .1.3.6.1.4.1.351.110.5.2.2.1.1.1.67 |
ausmChanRerouteThis is used by the administrator to trigger the re-routing
of the connection. The rerouting takes effect, when this object
is set to true(1). When set to false (2), no action is taken.
A get on this object always returns false (2).
This object is not applicable to MGX Release 1.x.rw Enumeration .1.3.6.1.4.1.351.110.5.2.2.1.1.1.68 |
ausmConnSCRSustained cell rate, Used for VBR connections setup with PNNI
controller.rw INTEGER .1.3.6.1.4.1.351.110.5.2.2.1.1.1.69 |
ausmConnRemoteSCRSustained cell rate of the other end, Used for VBR connections
setup with PNNI controller.rw INTEGER .1.3.6.1.4.1.351.110.5.2.2.1.1.1.70 |
ausmConnMBSMaximum burst size, Used for VBR connections
setup with PNNI controller.
In MGX switches, release 3.0.0.0 and above,
the default value is 1024rw INTEGER .1.3.6.1.4.1.351.110.5.2.2.1.1.1.71 |
ausmConnRemoteMBSMaximum burst size at the remote end of the connection,
Used for VBR connections setup with PNNI controller.rw INTEGER .1.3.6.1.4.1.351.110.5.2.2.1.1.1.72 |
ausmConnTemplateIdThis object specifies the template identifier for the connection
template associated with this connection.
The valid range for templates is 1..16.
A value of 17 indicates no template is associated with this
connectionrw INTEGER .1.3.6.1.4.1.351.110.5.2.2.1.1.1.73 |
ausmConnAdminStatusThis object specifies channel admin status.
This object is not applicable to MGX Release 1.x.rw Enumeration .1.3.6.1.4.1.351.110.5.2.2.1.1.1.74 |
ausmChanNumNextAvailableThis variable contains the next unused channel number of the possible
1000. This number can be used in channel config table.
ChanNumNextAvailable gets updated whenever this number is used to
create a new logical channel. Value 0 for this variable indicates that
no more channels are available. In AUSM (4-port card), the maximum
number of values for this variable is 256 (i.e. 16 ..271).ro INTEGER .1.3.6.1.4.1.351.110.5.2.2.1.2 |
ausmChanVpIdNextAvailableThis variable contains the next unused local VPId of the possible
1 to 100. This number can be used in channel config table. It gets
updated if the number is used to create a new vp connection. There
can max 100 vp connections per slot. Value of 0 for this variable
indicates that no more vp connections are available.ro INTEGER .1.3.6.1.4.1.351.110.5.2.2.1.3 |
ausmStdABRCnfGrpTableThe ABR config table is for logical channel interface
there are 1000 entries for the 8 logical ports in AUSM
(8-port). SEQUENCE OF AusmStdABRCnfGrpEntry .1.3.6.1.4.1.351.110.5.2.2.1.4 |
ausmStdABRCnfGrpEntryAn entry for logical channel AusmStdABRCnfGrpEntry .1.3.6.1.4.1.351.110.5.2.2.1.4.1 |
ausmStdABRCnfChanNumRefers to the virtual connection index.ro INTEGER .1.3.6.1.4.1.351.110.5.2.2.1.4.1.1 |
ausmStdABRTypeStdabrType of value 1 indicates a TM4.0 switch behaving
connection (Transparent connection) which assumes that RM cells
will be received from a TM4.0 compliant CPE. Value 2 indicates
a TM4.0 source destination behaving connection (Terminating
connection) which generates RM cells by itself.rw Enumeration .1.3.6.1.4.1.351.110.5.2.2.1.4.1.2 |
ausmStdABRTBETransient Buffer Exposure. The unit is number of cells.rw INTEGER .1.3.6.1.4.1.351.110.5.2.2.1.4.1.3 |
ausmStdABRFRTTFixed Round-Trip Time. The unit is milliseconds. Value 0
signifies that FRTT value is not available.rw INTEGER .1.3.6.1.4.1.351.110.5.2.2.1.4.1.4 |
ausmStdABRRDFRate Decrease Factor. This unitless value has to be inversed
to arrive at the actual value. The valid values possible are
only powers of 2; i.e. 1, 2, 4, 8 ..... 32768 . The SNMP
agent has to verify this compliance.rw INTEGER .1.3.6.1.4.1.351.110.5.2.2.1.4.1.5 |
ausmStdABRRIFRate Increase Factor. This unitless value has to be inversed
to arrive at the actual value. The valid values possible are
are only powers of 2; i.e. 1, 2, 4, 8 ..... 32768 . The SNMP
agent has to verify this compliance.rw INTEGER .1.3.6.1.4.1.351.110.5.2.2.1.4.1.6 |
ausmStdABRNrmMaximum number of cells a source may send for each forward RM
cell. The valid values possible are only powers of 2 starting
from 2 ; i.e. 2, 4, 8 ..... 256. The SNMP agent has to verify
this compliance.rw INTEGER .1.3.6.1.4.1.351.110.5.2.2.1.4.1.7 |
ausmStdABRTrmUpper bound on the time between forward RM cells for an active
source. The unit is in milliseconds.rw INTEGER .1.3.6.1.4.1.351.110.5.2.2.1.4.1.8 |
ausmStdABRCDFCutoff Decrease Factor. This unitless value has to be inversed
to arrive at the actual value. The valid values possible are 0
and only powers of 2; i.e. 1, 2, 4, 8, 16, 32, 64 . The SNMP
agent has to verify this compliance.rw INTEGER .1.3.6.1.4.1.351.110.5.2.2.1.4.1.9 |
ausmStdABRADTFACR Decrease Time Factor. Unit of this value is milliseconds.
Granularity allowed is 10 milli seconds. The SNMP agent has to
verify this compliance.rw INTEGER .1.3.6.1.4.1.351.110.5.2.2.1.4.1.10 |
ausmStdABRICRInitial cell Rate. The actual value depends on the speed of the
logical port (which can be a T1, E1 (normal), E1 (clear), IMA T1,
IMA T1, IMA E1 (normal) or IMA E1 (clear) port. Note that the
IMA port's speed is variable and depends on the number of
links in the port.rw INTEGER .1.3.6.1.4.1.351.110.5.2.2.1.4.1.11 |
ausmStdABRMCRMinimum cell Rate. The actual value depends on the speed of the
logical port (which can be a T1, E1 (normal), E1 (clear), IMA T1
IMA E1 (normal) or IMA E1 (clear) port. Note that the IMA port's
speed is variable and depends on the number of links in the port.
Please note that the MCR value will include bandwidth occupied
by Data cells as well as all in-rate RM cells.rw INTEGER .1.3.6.1.4.1.351.110.5.2.2.1.4.1.12 |
ausmStdABRPCRPeak cell Rate. The actual value depends on the speed of the
logical port (which can be a T1, E1 (normal), E1 (clear), IMA T1
IMA E1 (normal) or IMA E1 (clear) port. Note that the IMA port's
speed is variable and depends on the number of links in the port.
Please note that the PCR value will include bandwidth occupied
by Data cells as well as all in-rate RM cells.rw INTEGER .1.3.6.1.4.1.351.110.5.2.2.1.4.1.13 |
ausmChanStateGrp OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.5.2.2.2 |
ausmChanStateGrpTableTable of transmit/receive states of channels. SEQUENCE OF AusmChanStateGrpEntry .1.3.6.1.4.1.351.110.5.2.2.2.1 |
ausmChanStateGrpEntryAn entry for AusmChannelStateGrpEntry. AusmChanStateGrpEntry .1.3.6.1.4.1.351.110.5.2.2.2.1.1 |
ausmStateChanNumRefers to the logical channel number. In AUSM (4-port card),
the permissible range is from 16..271.ro INTEGER .1.3.6.1.4.1.351.110.5.2.2.2.1.1.1 |
ausmChanStateThis variable indicates the state of the
VC (channel)
failed(4) is added to distinguish between alarm (when the connection
segment is not actually broken) and failed(when the segment is actually
broken). This is applicable only to the PNNI environment.ro Enumeration .1.3.6.1.4.1.351.110.5.2.2.2.1.1.2 |
chanEgrXmtStateindicates the status of port transmit(Egress)ro Enumeration .1.3.6.1.4.1.351.110.5.2.2.2.1.1.3 |
chanIngrRcvStateindicates the status of port receive(Ingress)ro Enumeration .1.3.6.1.4.1.351.110.5.2.2.2.1.1.4 |
chanIngrXmtStateThis variable indicates the transmit state of the
VC (channel) on the Cellbus side (Ingress)
1 - other
2- normal
3 - sendingAIS
4 - sendingFerfro Enumeration .1.3.6.1.4.1.351.110.5.2.2.2.1.1.5 |
chanEgrRcvStateThis variable indicates the receiving state of the
VC (channel) on the Cellbus side (Egress)
1 - other
2- normal
3 - receivingAIS
4 - receivingFERFro Enumeration .1.3.6.1.4.1.351.110.5.2.2.2.1.1.6 |
ausmChanStatusBitMapThis variable indicates the consolidated bit map of the channel alarm
state.
Individual bit positions are as defined below.
Bit position Fail/Alarm Reason
0 Alarm port side AIS/RDI Rx
1 Alarm n/w side AIS/RDI Rx
2 Fail Conditioned(A bit from n/w)
3 Alarm Reserved
4 Fail Reserved
5 Fail Reserved
6 Alarm Reserved
7 Alarm Reserved
Fail bitmap mask : 0x34
Alarm bitmap mask: 0xCB
This object is not applicable to MGX Release 1.x.ro INTEGER (0..'ff'h) .1.3.6.1.4.1.351.110.5.2.2.2.1.1.7 |
ausmChanCntGrp OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.5.2.2.3 |
ausmChanCntGrpTableThe config table is for logical channel interface
there are 1000 entries for 8 logical ports. In AUSM (4-port
card), a logical port is synonymous with a physical port and
the number of supported entries in this table is 256. SEQUENCE OF AusmChanCntGrpEntry .1.3.6.1.4.1.351.110.5.2.2.3.1 |
ausmChanCntGrpEntryAn entry for logical channel AusmChanCntGrpEntry .1.3.6.1.4.1.351.110.5.2.2.3.1.1 |
ausmCntChanNumRefers to the logical channel number. In AUSM (4-port card),
the permissible range is from 16..271.ro INTEGER .1.3.6.1.4.1.351.110.5.2.2.3.1.1.1 |
chanSecInServiceThe number of seconds channel is in servicero Counter .1.3.6.1.4.1.351.110.5.2.2.3.1.1.2 |
chanCongestMinutesThe number of minutes for which congestion was
experiencedro Counter .1.3.6.1.4.1.351.110.5.2.2.3.1.1.3 |
chanIngrPeakQDepthPeak queue depth on the ingress directionro INTEGER (0..'ffff'h) .1.3.6.1.4.1.351.110.5.2.2.3.1.1.4 |
chanIngrRcvCellsThe number of cells received in the Ingress directionro Counter .1.3.6.1.4.1.351.110.5.2.2.3.1.1.5 |
chanIngrClpSetRcvCellsThe number of CLP set cells received in Ingress directionro Counter .1.3.6.1.4.1.351.110.5.2.2.3.1.1.6 |
chanIngrEfciSetRcvCellsThe number of EFCI set cells received in Ingress directionro Counter .1.3.6.1.4.1.351.110.5.2.2.3.1.1.7 |
chanIngrQfullDiscardCellsThe number of cells discarded due to ingress Q fullro Counter .1.3.6.1.4.1.351.110.5.2.2.3.1.1.8 |
chanIngrClpSetDiscardCellsThe number of CLP set cells discarded in Ingress directionro Counter .1.3.6.1.4.1.351.110.5.2.2.3.1.1.9 |
chanIngrUpcClpSetCellsThe number of cells for which CLP was set by UPCro Counter .1.3.6.1.4.1.351.110.5.2.2.3.1.1.10 |
chanIngrXmtCellsThe number of cells transmitted to the cellbusro Counter .1.3.6.1.4.1.351.110.5.2.2.3.1.1.11 |
chanShelfAlarmDiscardCellsThe number of cells discarded due to Shelf Alarmro Counter .1.3.6.1.4.1.351.110.5.2.2.3.1.1.12 |
ausmChanClrButtonwriting a value of 2 resets all the countersrw Enumeration .1.3.6.1.4.1.351.110.5.2.2.3.1.1.13 |
chanEpdDiscCellsThe number of cells discarded due to EPD (Early Packet Discard)
conditionro Counter .1.3.6.1.4.1.351.110.5.2.2.3.1.1.14 |
chanPpdDiscCellsThe number of cells discarded due to PPD (Partial Packet Discard)
conditionro Counter .1.3.6.1.4.1.351.110.5.2.2.3.1.1.15 |
chanIngrRcvCellRateThe number of cells received per second from the port. Statistics
collected before UPC and ingress qeueing. The maximum value is
5000 because clear E1 rate is 4830.ro Gauge .1.3.6.1.4.1.351.110.5.2.2.3.1.1.16 |
chanIngrRcvUtilizationThe percentage utilization of the reserved bandwidth (PCR). Statistics
collected before UPC and ingress queueing. The maximum value is 200
because a connection can oversubcribe.ro Gauge .1.3.6.1.4.1.351.110.5.2.2.3.1.1.17 |
chanIngrXmtCellRateThe number of cells transmitted per second to the network. Statistics
collected after UPC and ingress qeueing.ro Gauge .1.3.6.1.4.1.351.110.5.2.2.3.1.1.18 |
chanIngrXmtUtilizationThe percentage utilization of the reserved bandwidth (PCR). Statistics
collected after UPC and ingress queueing.ro Gauge .1.3.6.1.4.1.351.110.5.2.2.3.1.1.19 |
chanEgrRcvCellRateThe number of cells received per second from the network. Statistics
collected before egress qeueing.ro Gauge .1.3.6.1.4.1.351.110.5.2.2.3.1.1.20 |
chanEgrRcvUtilizationThe percentage utilization of the reserved bandwidth (PCR). Statistics
collected before egress queueing.ro Gauge .1.3.6.1.4.1.351.110.5.2.2.3.1.1.21 |
chanIngrXmtAAL5FramesThis statistics provides a count of the number of AAL5 Frames that are
sent to the networkro Counter .1.3.6.1.4.1.351.110.5.2.2.3.1.1.22 |
chanIngrEfciSetXmtCellsThis statistics provides a count of the number of EFCI set cells
that are transmitted to the network. This statistis is collected
after the policing and queueing.ro Counter .1.3.6.1.4.1.351.110.5.2.2.3.1.1.23 |
chanEgrPortQfullDiscardCellsThis statistics provides a count of the number of cells discarded
because of Egress Port Queue full. This count is displayed for the
queue corresponding to port and the service type to which this channel
belongs.ro Counter .1.3.6.1.4.1.351.110.5.2.2.3.1.1.24 |
chanEgrPortQClpThresDiscardCellsThis statistics provides a count of the number of cells discarded
because of Egress Port Queue CLP Threshold exceed. This count is
displayed for the queue corresponding to port and the service type to
which this channel belongs.ro Counter .1.3.6.1.4.1.351.110.5.2.2.3.1.1.25 |
chanTxFifoFullCntThis statistics provides a count of the number of times the AUSM
card tried to send a cell, but was unable to send because the
Transmit FIFO was full. Note that this is NOT a count of the number
of cells dropped. This statistics is per card statistics.ro Counter .1.3.6.1.4.1.351.110.5.2.2.3.1.1.26 |
chanIngrCurrQDepthCurrent queue depth on the ingress directionro INTEGER (0..'ffff'h) .1.3.6.1.4.1.351.110.5.2.2.3.1.1.27 |
atmLineCnfTableThe ATM Line config table is for the physical interface.
There will an entry for each of the physical line. SEQUENCE OF AtmLineCnfEntry .1.3.6.1.4.1.351.110.5.2.5.1.1 |
atmLineCnfEntryAn entry for the physical interface. AtmLineCnfEntry .1.3.6.1.4.1.351.110.5.2.5.1.1.1 |
atmLineCnfNumRefers to the phsical line number, PXM port will have a maximum of
4 lines.ro INTEGER .1.3.6.1.4.1.351.110.5.2.5.1.1.1.1 |
atmLineInterfaceFormatThis indicates the format of the cells going out on the
physical interfacerw Enumeration .1.3.6.1.4.1.351.110.5.2.5.1.1.1.2 |
atmLineCntTableThe ATM Line count table is for the physical interface.
There will an entry for each of the physical line. SEQUENCE OF AtmLineCntEntry .1.3.6.1.4.1.351.110.5.2.5.2.1 |
atmLineCntEntryAn entry for the physical interface.
These are counts which are collected on a physical line basis. AtmLineCntEntry .1.3.6.1.4.1.351.110.5.2.5.2.1.1 |
atmLineNumRefers to the phsical line number, PXM port will have a maximum of
4 lines.ro INTEGER .1.3.6.1.4.1.351.110.5.2.5.2.1.1.1 |
atmLineTotalRcvCellsThe number of cells received in Ingress direction.ro Counter .1.3.6.1.4.1.351.110.5.2.5.2.1.1.2 |
atmLineTotalXmtCellsThe number of cells transmitted in the egress directionro Counter .1.3.6.1.4.1.351.110.5.2.5.2.1.1.3 |
atmLineRcvHecErrorCellsNumber of cells with HEC errorro Counter .1.3.6.1.4.1.351.110.5.2.5.2.1.1.4 |
atmLineCntClrButtonwriting a value of 2 resets all the countersrw Enumeration .1.3.6.1.4.1.351.110.5.2.5.2.1.1.5 |
bbIfCnfPortGrp OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.5.2.6.1.1 |
bbIfCnfPortGrpTableThe Broadband Interface config table is for logical interface.
There will an entry for each of the logical partition of the
physical line. SEQUENCE OF BbIfCnfPortGrpEntry .1.3.6.1.4.1.351.110.5.2.6.1.1.1 |
bbIfCnfPortGrpEntryAn entry for the logical interface. The interface may be further
be configured to be used as a virtual trunk OR as a UNI Port. BbIfCnfPortGrpEntry .1.3.6.1.4.1.351.110.5.2.6.1.1.1.1 |
bbIfNumThis is logical interface number within a physical line num.
In MGX PXM card, a physical port can have a maximum of 32 logical
interfaces.ro INTEGER .1.3.6.1.4.1.351.110.5.2.6.1.1.1.1.1 |
bbIfRowStatusThis variable enables or disables the logical interface.
1 - enable
2 - disable
3 - modifyrw Enumeration .1.3.6.1.4.1.351.110.5.2.6.1.1.1.1.2 |
bbIfAdminThis variable enables or disables the logical interface.
1 - up
2 - down
3 - writeOnlyrw Enumeration .1.3.6.1.4.1.351.110.5.2.6.1.1.1.1.3 |
bbIfLineNumThe line number associated with the logical interface.
For PXM, there is currently 4 physical lines.rw INTEGER .1.3.6.1.4.1.351.110.5.2.6.1.1.1.1.4 |
bbIfIngrPctBandwidthThe percentage of aggregate physical line bandwidth, available for
this broadband interface - Ingress. Default is 0 %rw INTEGER ( 0..100 ) .1.3.6.1.4.1.351.110.5.2.6.1.1.1.1.5 |
bbIfEgrPctBandwidthThe percentage of aggregate physical line bandwidth, available for
this broadband interface - Egress . Default is 0 %rw INTEGER ( 0..100 ) .1.3.6.1.4.1.351.110.5.2.6.1.1.1.1.6 |
bbIfMinVpiThe lower limit of VPI range to be reserved for this logical interface.rw INTEGER ( 0..4095 ) .1.3.6.1.4.1.351.110.5.2.6.1.1.1.1.7 |
bbIfMaxVpiThe upper limit of VPI range to be reserved for this logical interface.
For virtual trunks, bbIfMinVpi and bbIfMaxVpi should be the same.rw INTEGER ( 0..4095 ) .1.3.6.1.4.1.351.110.5.2.6.1.1.1.1.8 |
bbIfSpeedThe speed of the port in cells per secondro INTEGER .1.3.6.1.4.1.351.110.5.2.6.1.1.1.1.9 |
bbIfMaxCellRatePctThe maximum cell rate allowed for the port in terms of percentage.
Must be greater than or equal to bbIfIngrPctBandwidth.
The default is 100 percent.rw INTEGER ( 0..100 ) .1.3.6.1.4.1.351.110.5.2.6.1.1.1.1.10 |
nextBbIfNumAvailableIndicates the next logical broadband interface number that is availablero INTEGER .1.3.6.1.4.1.351.110.5.2.6.1.1.2 |
bbIfCnfSigILMIGrp OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.5.2.6.1.2 |
bbIfCnfSigILMIGrpTableThe config table is for upto 32 logical port interfaces. SEQUENCE OF BbIfCnfSigILMIGrpEntry .1.3.6.1.4.1.351.110.5.2.6.1.2.1 |
bbIfCnfSigILMIGrpEntryAn entry for a boradband interface used as a UNI port.
In MGX PXM card, a physical port can have a maximum of 32 logical
interfaces. BbIfCnfSigILMIGrpEntry .1.3.6.1.4.1.351.110.5.2.6.1.2.1.1 |
bbIfSigPortNumRefers to the logical interface index on the PXM card in MGX node.ro INTEGER .1.3.6.1.4.1.351.110.5.2.6.1.2.1.1.1 |
bbIfIlmiEnableThe logical interface is a generic entity, it can be used as either
a virtual trunk, or user port with UNI support.
This variable is provided to enable/disable ILMI.
ILMI should only be enabled on 'user ports' and not on 'virtual trunks'
1 - disable
2 - enablerw Enumeration .1.3.6.1.4.1.351.110.5.2.6.1.2.1.1.2 |
bbIfSignallingProtocolTypeThis will set the signalling protocol
1 - other
2 - noSignalling
3 - ILMIrw Enumeration .1.3.6.1.4.1.351.110.5.2.6.1.2.1.1.3 |
bbIfSignallingVpiIndicates the VPI on which signalling cells arrive.rw INTEGER (0..4095 ) .1.3.6.1.4.1.351.110.5.2.6.1.2.1.1.4 |
bbIfSignallingVciIndicates the VCI on which signalling cells arrive.rw INTEGER (0..'ffff'h ) .1.3.6.1.4.1.351.110.5.2.6.1.2.1.1.5 |
bbIfAddrPrefixNetwork Prefix for the ATM addressrw NetPrefix -- from ILMI MIB .1.3.6.1.4.1.351.110.5.2.6.1.2.1.1.6 |
bbIfCustomerIdFor the INS as a read/write variablerw INTEGER .1.3.6.1.4.1.351.110.5.2.6.1.2.1.1.7 |
bbIfProtocolRevNoFor the INS as a read/write variable.rw INTEGER .1.3.6.1.4.1.351.110.5.2.6.1.2.1.1.8 |
bbIfIlmiTrapEnableEnable/disable ILMI Trap sendingrw Enumeration .1.3.6.1.4.1.351.110.5.2.6.1.2.1.1.9 |
bbIfMinTrapIntervalNumber of seconds between traps.rw INTEGER .1.3.6.1.4.1.351.110.5.2.6.1.2.1.1.10 |
bbIfKeepAlivePollingEnableEnable/disable Keep Alive Pollingrw Enumeration .1.3.6.1.4.1.351.110.5.2.6.1.2.1.1.11 |
bbIfErrorThresholdN491Error Threshold (N491) valuerw INTEGER .1.3.6.1.4.1.351.110.5.2.6.1.2.1.1.12 |
bbIfEventThresholdN492Event Threshold (N492) valuerw INTEGER .1.3.6.1.4.1.351.110.5.2.6.1.2.1.1.13 |
bbIfPollingIntervalT491Polling Interval (T491) valuerw Enumeration .1.3.6.1.4.1.351.110.5.2.6.1.2.1.1.14 |
bbIfMinEnquiryIntervalT493Minimum Enquiry Interval (T493)rw INTEGER .1.3.6.1.4.1.351.110.5.2.6.1.2.1.1.15 |
bbIfAddrRegEnableEnable/disable ILMI Address Registrationrw Enumeration .1.3.6.1.4.1.351.110.5.2.6.1.2.1.1.16 |
bbIfCnfRscPartGrpTableThe config table is for logical port interface
There can be 32 entries for PXM card in MGX. SEQUENCE OF BbIfCnfRscPartGrpEntry .1.3.6.1.4.1.351.110.5.2.6.2.1 |
bbIfCnfRscPartGrpEntryAn entry for a logical interface BbIfCnfRscPartGrpEntry .1.3.6.1.4.1.351.110.5.2.6.2.1.1 |
bbRscPartIfNumThis is logical interface number.ro INTEGER .1.3.6.1.4.1.351.110.5.2.6.2.1.1.1 |
bbRscPartCtrlrNumThis is index for controller using the interface .
1 - PAR
2 - PNNI
3 - TAGro Enumeration .1.3.6.1.4.1.351.110.5.2.6.2.1.1.2 |
bbIfRscPrtRowStatusThis will add, delete or modify the partition.
1 ==> ADD
2 ==> DELETE
3 ==> MODIFYrw Enumeration .1.3.6.1.4.1.351.110.5.2.6.2.1.1.3 |
bbIfRscPrtInUseSetting this object to 1 indicates that the resources
(LCN/Local VPID/VCI/VPI) have been partitioned and INS,
network ctrlrs.,SV+ are currently using this information. The resource
partition information can be changed after setting this
variable to 2.
The default value is 2 (NotInUse).rw Enumeration .1.3.6.1.4.1.351.110.5.2.6.2.1.1.4 |
bbIfRscPrtIngrPctBandwidthThe percentage of logical interface bandwidth ( bbIfIngrPctBandwidth ),
available for UNI channels.rw INTEGER .1.3.6.1.4.1.351.110.5.2.6.2.1.1.5 |
bbIfRscPrtEgrPctBandwidthThe percentage of logical interface bandwidth ( bbIfIngrPctBandwidth ),
available for UNI channels.rw INTEGER .1.3.6.1.4.1.351.110.5.2.6.2.1.1.6 |
bbIfRscPrtVpiLowThe beginning of the VPI range reserved for this partition.rw INTEGER .1.3.6.1.4.1.351.110.5.2.6.2.1.1.7 |
bbIfRscPrtVpiHighThe end of the VPI range reserved for this partition.rw INTEGER .1.3.6.1.4.1.351.110.5.2.6.2.1.1.8 |
bbIfRscPrtVciLowThe beginning of the VCI range reserved for this partition.
This field is only valid for logical interfaces configured with
a single VPI.rw INTEGER (0..'ffff'h) .1.3.6.1.4.1.351.110.5.2.6.2.1.1.9 |
bbIfRscPrtVciHighThe end of the VCI range reserved for this partition.
This field is only valid for logical interfaces configured with
a single VPI.rw INTEGER (0..'ffff'h) .1.3.6.1.4.1.351.110.5.2.6.2.1.1.10 |
bbIfRscPrtVpidLowThe beginning of the VPID range reserved for partition.
Used for VP conn.srw INTEGER .1.3.6.1.4.1.351.110.5.2.6.2.1.1.11 |
bbIfRscPrtVpidHighThe end of the VPID range reserved for partition.
Used for VP conn.srw INTEGER .1.3.6.1.4.1.351.110.5.2.6.2.1.1.12 |
bbIfRscPrtMaxChansThis represents no. of channels that are available to the
controller.rw INTEGER .1.3.6.1.4.1.351.110.5.2.6.2.1.1.13 |
bbIfRscPartCtrlrIDThis is the controller identifier for resource patition.
The default value is set for PNNI controller.rw INTEGER .1.3.6.1.4.1.351.110.5.2.6.2.1.1.14 |
bbIfStateGrpTableThe state table for the logical interface
there can be 32 entries for the PXM card in MGX. SEQUENCE OF BbIfStateGrpEntry .1.3.6.1.4.1.351.110.5.2.6.3.1 |
bbIfStateGrpEntryAn entry for logical interface.
In MGX PXM card, a physical port can have a maximum of 32 logical
interfaces. BbIfStateGrpEntry .1.3.6.1.4.1.351.110.5.2.6.3.1.1 |
bbStateIfNumThis is logical interface number within a physical line num.
In MGX PXM card, a physical port can have a maximum of 32 logical
interfaces.ro INTEGER .1.3.6.1.4.1.351.110.5.2.6.3.1.1.1 |
bbIfStateThis variable indicates the status of the logical interface.
The following are not supported for the logical interface.ro Enumeration .1.3.6.1.4.1.351.110.5.2.6.3.1.1.2 |
bbIfOversubscribedThis variable indicates the whether the logical interface is
over subscribed or not.ro Enumeration .1.3.6.1.4.1.351.110.5.2.6.3.1.1.3 |
bbIfIngrPercentUtilPercentage Utilization of the interface in the Ingress direction.ro INTEGER .1.3.6.1.4.1.351.110.5.2.6.3.1.1.4 |
bbIfEgrPercentUtilPercentage Utilization of the interface in the Egress direction.ro INTEGER .1.3.6.1.4.1.351.110.5.2.6.3.1.1.5 |
bbIfCntGrp OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.5.2.6.4.1 |
bbIfCntGrpTableThe Broadband Interface Count table is for logical interface.
There will an entry for each of the logical partition of the
physical line. SEQUENCE OF BbIfCntGrpEntry .1.3.6.1.4.1.351.110.5.2.6.4.1.1 |
bbIfCntGrpEntryAn entry for logical interface. BbIfCntGrpEntry .1.3.6.1.4.1.351.110.5.2.6.4.1.1.1 |
bbCntIfNumRefers to the logical interface index on the PXM card in MGX node.ro INTEGER .1.3.6.1.4.1.351.110.5.2.6.4.1.1.1.1 |
bbIfTotalCellsTotal number of cells (VC plus Qbin) that belong to this Interface.
This maps on to the virtual interface of QE.ro Counter .1.3.6.1.4.1.351.110.5.2.6.4.1.1.1.2 |
bbIfRcvValidOAMCellsTotal number of OAM cell received.ro Counter .1.3.6.1.4.1.351.110.5.2.6.4.1.1.1.3 |
bbIfRcvRmCellsTotal number of RM cells Received.ro Counter .1.3.6.1.4.1.351.110.5.2.6.4.1.1.1.4 |
bbIfRcvClp0CellsTotal number of CLP-0 cells Received.ro Counter .1.3.6.1.4.1.351.110.5.2.6.4.1.1.1.5 |
bbIfRcvClp1CellsTotal number of CLP-1 cells Received.ro Counter .1.3.6.1.4.1.351.110.5.2.6.4.1.1.1.6 |
bbIfRcvClp0DiscCellsTotal number of CLP-0 cells discarded at Ingress.ro Counter .1.3.6.1.4.1.351.110.5.2.6.4.1.1.1.7 |
bbIfRcvClp1DiscCellsTotal number of CLP-1 cells discarded at Ingress.ro Counter .1.3.6.1.4.1.351.110.5.2.6.4.1.1.1.8 |
bbIfXmtOAMCellsTotal number of OAM cells transmitted.ro Counter .1.3.6.1.4.1.351.110.5.2.6.4.1.1.1.9 |
bbIfXmtRmCellsTotal number of RM cells transmitted.ro Counter .1.3.6.1.4.1.351.110.5.2.6.4.1.1.1.10 |
bbIfXmtClp0CellsTotal number of CLP-0 cells transmitted.ro Counter .1.3.6.1.4.1.351.110.5.2.6.4.1.1.1.11 |
bbIfXmtClp1CellsTotal number of CLP-1 cells transmitted.ro Counter .1.3.6.1.4.1.351.110.5.2.6.4.1.1.1.12 |
bbIfCntClrButtonWriting a value of 2 resets all the countersrw Enumeration .1.3.6.1.4.1.351.110.5.2.6.4.1.1.1.13 |
bbIfCntSigILMIGrp OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.5.2.6.4.2 |
bbIfCntSigILMIGrpTableThe counter table is for upto 32 logical port interfaces. SEQUENCE OF BbIfCntSigILMIGrpEntry .1.3.6.1.4.1.351.110.5.2.6.4.2.1 |
bbIfCntSigILMIGrpEntryAn entry for a boradband interface used as a UNI port.
In MGX PXM card, a physical port can have a maximum of 32 logical
interfaces. BbIfCntSigILMIGrpEntry .1.3.6.1.4.1.351.110.5.2.6.4.2.1.1 |
sigCntBbIfNumRefers to the logical interface index on the PXM card in MGX node.ro INTEGER .1.3.6.1.4.1.351.110.5.2.6.4.2.1.1.1 |
bbIfSnmpPduReceivedThe number of snmp packets received on this logical interface.ro Counter .1.3.6.1.4.1.351.110.5.2.6.4.2.1.1.2 |
bbIfGetRequestReceivedThe number of get request messages receivedro Counter .1.3.6.1.4.1.351.110.5.2.6.4.2.1.1.3 |
bbIfGetNextRequestReceivedThe number of get-next messages receivedro Counter .1.3.6.1.4.1.351.110.5.2.6.4.2.1.1.4 |
bbIfSetRequestReceivedThe number of set messages receivedro Counter .1.3.6.1.4.1.351.110.5.2.6.4.2.1.1.5 |
bbIfTrapReceivedThe number of traps receivedro Counter .1.3.6.1.4.1.351.110.5.2.6.4.2.1.1.6 |
bbIfGetResponseReceivedThe number of Keep Alive response messages receivedro Counter .1.3.6.1.4.1.351.110.5.2.6.4.2.1.1.7 |
bbIfGetResponseTransmittedThe number of response messages transmittedro Counter .1.3.6.1.4.1.351.110.5.2.6.4.2.1.1.8 |
bbIfGetRequestTransmittedThe number of Keep Alive get request messages transmittedro Counter .1.3.6.1.4.1.351.110.5.2.6.4.2.1.1.9 |
bbIfTrapTransmittedThe number of trap messages transmittedro Counter .1.3.6.1.4.1.351.110.5.2.6.4.2.1.1.10 |
bbIfInvalidPDUReceivedThe number of invalid PDUs receivedro Counter .1.3.6.1.4.1.351.110.5.2.6.4.2.1.1.11 |
bbIfAsn1ParseErrorThe number of parse errors on ASN.1ro Counter .1.3.6.1.4.1.351.110.5.2.6.4.2.1.1.12 |
bbIfNoSuchNameErrorThe number of errors for name not presentro Counter .1.3.6.1.4.1.351.110.5.2.6.4.2.1.1.13 |
bbIfTooBigErrorThe number of messages received with len > 484ro Counter .1.3.6.1.4.1.351.110.5.2.6.4.2.1.1.14 |
bbIfSigCntClrButtonWriting a value of 2 resets all the countersrw Enumeration .1.3.6.1.4.1.351.110.5.2.6.4.2.1.1.15 |
bbChanCnfGrpTableThe Broadband Channel config table is for a channel on logical
interface. There will an entry for each of the channel added on the
logical partition of the physical line. SEQUENCE OF BbChanCnfGrpEntry .1.3.6.1.4.1.351.110.5.2.7.1.1 |
bbChanCnfGrpEntryThe config table is for logical channel. BbChanCnfGrpEntry .1.3.6.1.4.1.351.110.5.2.7.1.1.1 |
bbChanCnfNumThis identifies a channel on the PXM logical interface, used as
PXM port.ro INTEGER .1.3.6.1.4.1.351.110.5.2.7.1.1.1.1 |
bbChanRowStatusThis will add, delete or modify the channel
1 ==> ADD
2 ==> DELETE
3 ==> MODIFYrw Enumeration .1.3.6.1.4.1.351.110.5.2.7.1.1.1.2 |
bbChanConnTypeThis specifies the connection type
1 ==> Virtual Path Connection
2 ==> Virtual Channel Connectionrw Enumeration .1.3.6.1.4.1.351.110.5.2.7.1.1.1.3 |
bbChanServiceTypeThis specifies the service type
1 ==> Constant Bit Rate
2 ==> Variable Bit Rate
3 ==> Available Bit Rate
4 ==> Unspecified Bit Rate
5 ==> Variable Bit Rate - Real Timerw Enumeration .1.3.6.1.4.1.351.110.5.2.7.1.1.1.4 |
bbChanConnDescA string that has been defined to give a
descriptive name to the connectionrw DisplayString .1.3.6.1.4.1.351.110.5.2.7.1.1.1.5 |
bbChanSvcFlagThis specifies the connection type
1 ==> SVC connection
2 ==> PVC connection, used by PAR
3 ==> Soft PVC connection, used by PNNIrw Enumeration .1.3.6.1.4.1.351.110.5.2.7.1.1.1.6 |
bbChanSvcConnIdThis connection ID is for future use Currently not supported.rw INTEGER .1.3.6.1.4.1.351.110.5.2.7.1.1.1.7 |
bbChanIfNumChannel's logical Interface from which traffic of the connection
will be received.rw INTEGER .1.3.6.1.4.1.351.110.5.2.7.1.1.1.8 |
bbChanVpiVPI for the connection.rw INTEGER .1.3.6.1.4.1.351.110.5.2.7.1.1.1.9 |
bbChanVciVCI for the connection.rw INTEGER (0..'ffff'h) .1.3.6.1.4.1.351.110.5.2.7.1.1.1.10 |
bbChanUpcEnableenables/disables UPC for Ingress cellsrw Enumeration .1.3.6.1.4.1.351.110.5.2.7.1.1.1.11 |
bbChanUpcPCRPCR(0+1), Peak Cell Rate, specifies an upper bound on
rate at which traffic can be submitted on an ATM
connection. This object applies to the First Leaky
Bucket for leaving cells with Cell Loss Priority of 0 or 1.
. Units: cells per second.
. Applicable connection types:
UBR, CBR, VBR, ABR
. Default: 50
. Ranges:
T3 : 50-96000
E3 : 50-80000
OC3 : 50-353208
OC12: 50-1412832rw INTEGER .1.3.6.1.4.1.351.110.5.2.7.1.1.1.12 |
bbChanUpcCDVTCompliant Cell Delay Variation. Also known as
CDVT(0+1), Cell Delay Variation Tolerance, which
specifies the maximum time period for accumulated
violations of cell-arrival time parameters. This object
applies to the First Leaky bucket for cells with Cell
Loss Priority of 0 or 1.
. Units: microseconds.
. Applicable connection types:
UBR, CBR, VBR, ABR
. Default:
CBR: 10000
Others: 250000rw INTEGER .1.3.6.1.4.1.351.110.5.2.7.1.1.1.13 |
bbChanUpcSCRSCR, Sustainable Cell Rate, is an upper bound on the
conforming average rate of an ATM connection, over
time scales which are long relative to those for which
the PCR is defined. Enforcement of this bound by the UPC
could allow the network to allocate sufficient resources,
but less than thos based on the PCR, and still ensure
that the performance objectives (e.g., Cell Loss Ratio)
can be achieved.
. Units: cell per second.
. Applicable connection types:
. VBR, ABR
. Ranges:
T3 : 50-96000
E3 : 50-80000
OC3 : 50-353208
OC12: 50-1412832
. Default: 50rw INTEGER .1.3.6.1.4.1.351.110.5.2.7.1.1.1.14 |
bbChanUpcMBSMaximum Burst Size (MBS). Also known as Compliant Burst Size (CBS).
. Units: cells
. Applicable connection types:
. VBR, ABR
. Default: 1000
. Range : 1-5000000rw INTEGER .1.3.6.1.4.1.351.110.5.2.7.1.1.1.15 |
bbChanGcra1ActionGCRA1 Action.
1 = No Action
2 = Tag Untagged cells
3 = Tag untagged cells and discard tagged cells
4 = Discard all (0+1) non-comforming cellsrw Enumeration .1.3.6.1.4.1.351.110.5.2.7.1.1.1.16 |
bbChanGcra2ActionGCRA2 Action.
1 = No Action
2 = Tag Untagged cells
3 = Tag untagged cells and discard tagged cells
4 = Discard all (0+1) non-comforming cellsrw Enumeration .1.3.6.1.4.1.351.110.5.2.7.1.1.1.17 |
bbChanUpcSCRPolicingSelects SCR policing for CLP = 0 or all cellsrw Enumeration .1.3.6.1.4.1.351.110.5.2.7.1.1.1.18 |
bbChanEfciThresholdThreshold above which EFCI bit is to be set.
Default Value is 3/4 of max cell count.rw INTEGER .1.3.6.1.4.1.351.110.5.2.7.1.1.1.19 |
bbChanDiscardOptionEnable Frame Discard or CLP Hysteresis.rw Enumeration .1.3.6.1.4.1.351.110.5.2.7.1.1.1.20 |
bbChanFrmDiscardThresholdIngress Frame Discard Threshold.
Valid only when Ingress Frame Discard option is selected.
Default Value : TBDrw INTEGER .1.3.6.1.4.1.351.110.5.2.7.1.1.1.21 |
bbChanClpHiThresholdIngress CLP High Threshold.
Default is 3/4 of max cell count.rw INTEGER .1.3.6.1.4.1.351.110.5.2.7.1.1.1.22 |
bbChanClpLoThresholdIngress CLP Low Threshold. Valid only when
Ingress CLP Hysteresis option is selected.
Default Value is 1/2 of max cell count.rw INTEGER .1.3.6.1.4.1.351.110.5.2.7.1.1.1.23 |
bbChanCongstUpdateCodeIngress Channel Congestion Update Code.
Default Value : TBDrw Enumeration .1.3.6.1.4.1.351.110.5.2.7.1.1.1.24 |
bbChanMaxCellMemThresholdMaximum number of cells of that connection in
the memory.
Assuming Total Cell Memory is 512K cells, this is defaulted to
half of total size.rw INTEGER .1.3.6.1.4.1.351.110.5.2.7.1.1.1.25 |
bbChanIngrPercentUtilPercentage Utilization of the IngrService Rate. This is used
for connection admission control.
Default Value : TBDrw INTEGER .1.3.6.1.4.1.351.110.5.2.7.1.1.1.26 |
bbChanEgrPercentUtilPercentage Utilization of the EgrService Rate.
This is used for egress bandwidth calculation and
connection admission control.
Default Value : TBDrw INTEGER .1.3.6.1.4.1.351.110.5.2.7.1.1.1.27 |
bbChanEgrSrvRateEgress service rate - This is used for egress bandwidth calculation
and for connection admission control. The actual value
depends on the speed of the logical interfacerw INTEGER .1.3.6.1.4.1.351.110.5.2.7.1.1.1.28 |
bbChanOvrSubOvrRideChannel Over Subscrive Override
This MIB variable allows one to add a new connection on a port
even if it is over subscribed.rw Enumeration .1.3.6.1.4.1.351.110.5.2.7.1.1.1.29 |
bbChanLocalVpiThe VPI value for this channelro INTEGER .1.3.6.1.4.1.351.110.5.2.7.1.1.1.30 |
bbChanLocalVciThe VCI value for this channelro INTEGER (0..'ffff'h) .1.3.6.1.4.1.351.110.5.2.7.1.1.1.31 |
bbChanLocalNsapAddrThe Near End NSAP Address value for this channel.rw IfNsapAddress .1.3.6.1.4.1.351.110.5.2.7.1.1.1.32 |
bbChanRemoteVpiThe VPI value for this channelrw INTEGER .1.3.6.1.4.1.351.110.5.2.7.1.1.1.33 |
bbChanRemoteVciThe VCI value for this channelrw INTEGER (0..'ffff'h) .1.3.6.1.4.1.351.110.5.2.7.1.1.1.34 |
bbChanRemoteNsapAddrThe Far End NSAP Address value for this channel.rw IfNsapAddress .1.3.6.1.4.1.351.110.5.2.7.1.1.1.35 |
bbChanMasterThis is used by the PXM switch platform module, to determine if this
endpoint ia master or slave.rw Enumeration .1.3.6.1.4.1.351.110.5.2.7.1.1.1.36 |
bbChanRtePriorityThis is also known as class of service, it is used by
PXM to determine how important this connection is when
selecting connections to route.rw INTEGER .1.3.6.1.4.1.351.110.5.2.7.1.1.1.37 |
bbChanMaxCostMaximum allowed cost. It is related to Cost Based Routing.
This is used by PXM so that it won't choose a path with a
cost greater than this configured level.rw INTEGER .1.3.6.1.4.1.351.110.5.2.7.1.1.1.38 |
bbChanRestrictTrkTypeRestricted trunk type for routind, used by PXM. It
specifies that the connection either cannot be routed over satellite
trunks or terrestrial trunks, or it can be on any type of trunk.rw Enumeration .1.3.6.1.4.1.351.110.5.2.7.1.1.1.39 |
bbChanTestTypeThe chanTestType starts testing the continuity or delay of a connection.
It sends specific cell patterns toward the network and the terminating
end of this connection has to be an AXIS or ASI of a BPX in order for
this test to be working.
The receiving node would loop back when it receives these
cells. The test should be done in about couple of seconds. The testcon
tests the continuity of the connection and testdelay uses the same
test except that it measures for delay through the network.
To test the delay follow this procedure:
a- set chanTestType to testdelay
b- read chanTestState till it is Pass or Fail
c- Read chanTestResult for the delay if it is Pass
*Note that the chanTestType would go back to notest when the
test is completed
To test the continuity follow this procedure:
a- set chanTestType to testcon
b- read chanTestState till it is Pass or Fail
*Note that the chanTestType would go back to notest when the
test is completed
You CAN NOT select 2 tests back to back, you have selcelt one and wait
the result and then start the other one.
SYNTAX
When you select testdelay
This is the type of the test
1 = Test Continuity
2 = Test Delay
3 = No Test
tstconseg is performed on the port side, i.e, towards the CPErw Enumeration .1.3.6.1.4.1.351.110.5.2.7.1.1.1.40 |
bbChanTestStateThis shows the state of the test
When you add a connection then the chanTestState becomes notinprogress
and when you select any test, it would go to inprogress state and after
it completes the test, it will go to failed or passed state.
1 = Passed
2 = Failed
3 = In Progress
4 = Not In Progressro Enumeration .1.3.6.1.4.1.351.110.5.2.7.1.1.1.41 |
bbChanTestResultThis is round trip delay in milliseconds.
When you select testdelay option for the chanTestType, the result of
the test that is measured in milliseconds can be read in chanTestResult.ro INTEGER .1.3.6.1.4.1.351.110.5.2.7.1.1.1.42 |
bbChanTestTypeCPESideThe default is notest.
The chanTestType starts testing the segment continuity of a connection.
It sends OAM Segment loopback cell towards port side (CPE)
The CPE would loop back the cell
To test the continuity follow this procedure:
a- set chanTestTypeCPEside to testconseg
b- read chanTestState till it is Pass or Fail
*Note that the chanTestType would go back to notest when the
test is completed
SYNTAX
When you select testdelay
This is the type of the test
1 = Test Continuity
2 = No Testrw Enumeration .1.3.6.1.4.1.351.110.5.2.7.1.1.1.43 |
bbChanTestStateCPESideThis shows the state of the test
When you add a connection then the chanTestState becomes notinprogress
and when you select any test, it would go to inprogress state and after
it completes the test, it will go to failed or passed state.
1 = Passed
2 = Failed
3 = In Progress
4 = Not In Progressro Enumeration .1.3.6.1.4.1.351.110.5.2.7.1.1.1.44 |
bbConnVpcFlagThis represents the connection type, used for PXM to
identify VPC/VCCrw Enumeration .1.3.6.1.4.1.351.110.5.2.7.1.1.1.45 |
bbConnServiceTypeThis specifies the service type
1 ==> Constant Bit Rate
2 ==> Variable Bit Rate
4 ==> Unspecified Bit Rate
6 ==> Available Bit Rate ( standard )
8 ==> Variable Bit Rate - Real-Time
Note that this is used by PXM card,
Also to make it compatible with existing AUSM MIB definition,
value 3 is not used.
foresight ABR is not supported in PXM , i.e Virtual Service Modulerw Enumeration .1.3.6.1.4.1.351.110.5.2.7.1.1.1.46 |
bbConnPCRPeak cell rate, could be derived from the end point parameterrw INTEGER .1.3.6.1.4.1.351.110.5.2.7.1.1.1.47 |
bbConnSCRSustained cell rate, could be derived from the end point parameterrw INTEGER .1.3.6.1.4.1.351.110.5.2.7.1.1.1.48 |
bbConnPercentUtilThis is the expected long-term utilization of the
channel by this end-point.rw INTEGER ( 0..100 ) .1.3.6.1.4.1.351.110.5.2.7.1.1.1.49 |
bbRemoteConnPCRPeak cell rate of the other end, if not set, will be
set to the same as local end PCR (bbChanUpcPCR). However,
note that if the PCRs for both local and remote end
are set to the different value (i.e., asymmetric conn),
then this should be set differently from local end PCR.rw INTEGER .1.3.6.1.4.1.351.110.5.2.7.1.1.1.50 |
bbRemoteConnSCRSustained cell rate of the other end, if not set, will be
set to the same as local end SCR (bbChanUpcSCR). However,
note that if the PCRs for both local and remote end
are set to the different value (i.e., asymmetric conn),
then this should be set differently from local end SCR.rw INTEGER .1.3.6.1.4.1.351.110.5.2.7.1.1.1.51 |
bbRemoteConnPercentUtilThis is the expected long-term utilization of the
channel by this end-point. If this is not specified in
the connection setup request, it'll be defaulted to
100 percentrw INTEGER ( 0..100 ) .1.3.6.1.4.1.351.110.5.2.7.1.1.1.52 |
bbChanUpcMCRSCR, Sustainable Cell Rate, is an upper bound on the
conforming average rate of an ATM connection, over
time scales which are long relative to those for which
the PCR is defined. Enforcement of this bound by the UPC
could allow the network to allocate sufficient resources,
but less than thos based on the PCR, and still ensure
that the performance objectives (e.g., Cell Loss Ratio)
can be achieved.
. Units: cell per second.
. Applicable connection types:
. ABR
. Ranges:
T3 : 50-96000
E3 : 50-80000
OC3 : 50-353208
OC12: 50-1412832
. Default: 50rw INTEGER .1.3.6.1.4.1.351.110.5.2.7.1.1.1.53 |
bbChanNumNextAvailableThis variable contains the next unused channel number of the possible
4096 . This number can be used in channel config table.
ChanNumNextAvailable gets updated whenever this number is used to
create a new logical channel. Value 0 for this variable indicates that
no more channels are available.ro INTEGER .1.3.6.1.4.1.351.110.5.2.7.1.2 |
bbChanVpIdNextAvailableThis in only valid for a Service Module, will NOT be used in PXM.
This variable contains the next unused local VPId of the possible
1 to 4095. This number can be used in channel config table. It gets
updated if the number is used to create a new vp connection.
The max. no. of VP conn.s is limited to the VPI range configured
for this logical interface.
Value of 0 for this variable indicates that no more vp connections
are availablero INTEGER .1.3.6.1.4.1.351.110.5.2.7.1.3 |
bbChanStateGrpTableThe Broadband Channel state table is for a channel on logical
interface. There will an entry for each of the channel added on the
logical partition of the physical line. SEQUENCE OF BbChanStateGrpEntry .1.3.6.1.4.1.351.110.5.2.7.2.1 |
bbChanStateGrpEntryThe state table is for logical channel.
The available number of channels on the broadband interface (user ports)
on the PXM card is restricted to 4K.
The PXM card has 2 Queue Engines ( QE0 and QE1).
Current calculations allow 31954 GLCNs on QE0, and 31748 GLCNs on QE1. BbChanStateGrpEntry .1.3.6.1.4.1.351.110.5.2.7.2.1.1 |
bbChanStateNumRefers to the logical channel numberro INTEGER .1.3.6.1.4.1.351.110.5.2.7.2.1.1.1 |
bbChanStateThis variable indicates the state of the VC (channel).ro Enumeration .1.3.6.1.4.1.351.110.5.2.7.2.1.1.2 |
bbChanEgrXmtStateIndicates the status of port transmit(Egress)ro Enumeration .1.3.6.1.4.1.351.110.5.2.7.2.1.1.3 |
bbChanIngrRcvStateindicates the status of port receive(Ingress)ro Enumeration .1.3.6.1.4.1.351.110.5.2.7.2.1.1.4 |
bbChanCntGrpTableThe Broadband Channel count table is for a channel on virtual
interface or a physical line. There will an entry for each
of the channel added on the logical partition of the physical line. SEQUENCE OF BbChanCntGrpEntry .1.3.6.1.4.1.351.110.5.2.7.3.1 |
bbChanCntGrpEntryThe count table is for logical channel.
The available number of channels on the broadband interface
on the PXM card is restricted to 4K.
The PXM card has 2 Queue Engines ( QE0 and QE1). BbChanCntGrpEntry .1.3.6.1.4.1.351.110.5.2.7.3.1.1 |
bbChanCntNumChannel number.ro INTEGER .1.3.6.1.4.1.351.110.5.2.7.3.1.1.1 |
bbChanRcvClp0CellsCLP_0 Cells Received From Port Count.ro Counter .1.3.6.1.4.1.351.110.5.2.7.3.1.1.2 |
bbChanRcvClp1CellsCLP_1 Cells Received From Port Count.ro Counter .1.3.6.1.4.1.351.110.5.2.7.3.1.1.3 |
bbChanNonConformCellsAtGcra1PolicerNon-Conforming Cells Received at Ingress GCRA1 Policer Count.ro Counter .1.3.6.1.4.1.351.110.5.2.7.3.1.1.4 |
bbChanNonConformCellsAtGcra2PolicerNon-Conforming Cells Received at Ingress GCRA2 Policer Count.ro Counter .1.3.6.1.4.1.351.110.5.2.7.3.1.1.5 |
bbChanRcvEOFCellsNumber of cells received from PXM port with EOF set.ro Counter .1.3.6.1.4.1.351.110.5.2.7.3.1.1.6 |
bbChanDscdClp0CellsNumber of discarded clp = 0 cells received from PXM port.ro Counter .1.3.6.1.4.1.351.110.5.2.7.3.1.1.7 |
bbChanDscdClp1CellsNumber of discarded clp = 1 cells received from PXM port.ro Counter .1.3.6.1.4.1.351.110.5.2.7.3.1.1.8 |
bbChanRcvCellsSentNumber of cells received from port and sent out of the Queue Engine.ro Counter .1.3.6.1.4.1.351.110.5.2.7.3.1.1.9 |
bbChanXmtClp0CellsNumber of cells with EFCI clear transmitted to PXM port.ro Counter .1.3.6.1.4.1.351.110.5.2.7.3.1.1.10 |
bbChanXmtClp1CellsNumber of cells with EFCI set transmitted to PXM port.ro Counter .1.3.6.1.4.1.351.110.5.2.7.3.1.1.11 |
bbChanDscdClpZeroCellsToPortNumber of discard CLP = 0 cells before transmitted to PXM port.ro Counter .1.3.6.1.4.1.351.110.5.2.7.3.1.1.12 |
bbChanDscdClpOneCellsToPortNumber of discard CLP = 1 cells before transmitted to PXM port.ro Counter .1.3.6.1.4.1.351.110.5.2.7.3.1.1.13 |
bbChanCntClrButtonWriting a value of 2 resets all the countersrw Enumeration .1.3.6.1.4.1.351.110.5.2.7.3.1.1.14 |
virtualInterfaceCnf OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.5.2.8.1 |
vrtlIntrConfigTableVirtual Interface Configuration Table SEQUENCE OF VrtlIntrConfigEntry .1.3.6.1.4.1.351.110.5.2.8.1.1 |
vrtlIntrConfigEntryAn entry in the Virtual Interface configuration Table VrtlIntrConfigEntry .1.3.6.1.4.1.351.110.5.2.8.1.1.1 |
configVrtlIntrNumVirtual Interface Number. There are totaly
32 Virtual Interfaces on the card (egress).ro INTEGER .1.3.6.1.4.1.351.110.5.2.8.1.1.1.1 |
vrtlIntrPortNumPort number which will be connected to the
Virtual Interface. Value zero meens that this
virtual interface is not connected to any port.rw INTEGER .1.3.6.1.4.1.351.110.5.2.8.1.1.1.2 |
vrtlIntrStateVirtual Interface State.rw Enumeration .1.3.6.1.4.1.351.110.5.2.8.1.1.1.3 |
vrtlIntrMaxQueMemVirtual Interface's Max queue memory.
1 = 4Kcells
2 = 8Kcells
3 = 16Kcells
4 = 32Kcells
5 = 64Kcells
6 = 128Kcells
7 = 256Kcells
8 = 512Kcellsrw INTEGER .1.3.6.1.4.1.351.110.5.2.8.1.1.1.4 |
vrtlIntrMinCellRateVirtual Interface's minimum cell rate.
The default value:
for OC12 port is 1412832 cells/sec
for OC3 port is 353208 cells/sec
for T3 port is 96000 cells/sec
for E3 port is 80000 cells/secrw INTEGER .1.3.6.1.4.1.351.110.5.2.8.1.1.1.5 |
vrtlIntrMaxCellRateVirtual Interface's maximum cell rate.
The default value:
for OC12 port is 1412832 cells/sec
for OC3 port is 353208 cells/sec
for T3 port is 96000 cells/sec
for E3 port is 80000 cells/secrw INTEGER .1.3.6.1.4.1.351.110.5.2.8.1.1.1.6 |
vrtlIntrCurrConfigPathsThis is not a configurable parameter.
This gives the count of paths currently configured on this VI.ro INTEGER .1.3.6.1.4.1.351.110.5.2.8.1.1.1.7 |
virtualInterfaceCnt OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.5.2.8.2 |
vrtlIntrCounterTableVirtual Interface Counters Table. SEQUENCE OF VrtlIntrCounterEntry .1.3.6.1.4.1.351.110.5.2.8.2.1 |
vrtlIntrCounterEntryAn entry in the Virtual Interface Counter Table. VrtlIntrCounterEntry .1.3.6.1.4.1.351.110.5.2.8.2.1.1 |
countVrtlIntrNumVirtual Interface Number.ro INTEGER .1.3.6.1.4.1.351.110.5.2.8.2.1.1.1 |
vrtlIntrTotalCellCntTotal number of cells (VC plus Qbin) that belong to
this Virtual Interface.ro Counter .1.3.6.1.4.1.351.110.5.2.8.2.1.1.2 |
vrtlIntrTotalQbinCellCntTotal number of cells in the Qbin belonging
to this Virtual Interface.ro Counter .1.3.6.1.4.1.351.110.5.2.8.2.1.1.3 |
vrtlIntrRxdValidOAMCellCntTotal number of OAM cell received.ro Counter .1.3.6.1.4.1.351.110.5.2.8.2.1.1.4 |
vrtlIntrRxdRmCellCntTotal number of RM cells Received.ro Counter .1.3.6.1.4.1.351.110.5.2.8.2.1.1.5 |
vrtlIntrRxdClpUntaggedCellCntTotal number of CLP-0 cells Received.ro Counter .1.3.6.1.4.1.351.110.5.2.8.2.1.1.6 |
vrtlIntrRxdClpTaggedCellCntTotal number of CLP-1 cells Received.ro Counter .1.3.6.1.4.1.351.110.5.2.8.2.1.1.7 |
vrtlIntrRxdClpUntaggedDiscardedCellCntTotal number of CLP-0 cells discarded at Ingress.ro Counter .1.3.6.1.4.1.351.110.5.2.8.2.1.1.8 |
vrtlIntrRxdClpTaggedDiscardedCellCntTotal number of CLP-1 cells discarded at Ingress.ro Counter .1.3.6.1.4.1.351.110.5.2.8.2.1.1.9 |
vrtlIntrXmtdOAMCellCntTotal number of OAM cells transmitted.ro Counter .1.3.6.1.4.1.351.110.5.2.8.2.1.1.10 |
vrtlIntrXmtdRmCellCntTotal number of RM cells transmitted.ro Counter .1.3.6.1.4.1.351.110.5.2.8.2.1.1.11 |
vrtlIntrXmtdClpUntaggedCellCntTotal number of CLP-0 cells transmitted.ro Counter .1.3.6.1.4.1.351.110.5.2.8.2.1.1.12 |
vrtlIntrXmtdClpTaggedCellCntTotal number of CLP-1 cells transmitted.ro Counter .1.3.6.1.4.1.351.110.5.2.8.2.1.1.13 |
virtualInterfaceQbinCnf OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.5.2.8.3 |
vrtlIntrQbinConfigTableVirtual Interface QBin Configuration Table. SEQUENCE OF VrtlIntrQbinConfigEntry .1.3.6.1.4.1.351.110.5.2.8.3.1 |
vrtlIntrQbinConfigEntryAn entry in the Virtual Interface Qbin Config Table. VrtlIntrQbinConfigEntry .1.3.6.1.4.1.351.110.5.2.8.3.1.1 |
queConfigVrtlIntrNumVirtual Interface Number.ro INTEGER .1.3.6.1.4.1.351.110.5.2.8.3.1.1.1 |
queConfigVrtlIntrQbinNumVirtual Interface Qbin Number. There are totaly 16 Qbin
per Virtual Interface.ro INTEGER .1.3.6.1.4.1.351.110.5.2.8.3.1.1.2 |
vrtlIntrQbinStateVirtual Interface QBIN state.rw Enumeration .1.3.6.1.4.1.351.110.5.2.8.3.1.1.3 |
vrtlIntrQbinPriThis indicates the priority of the QBIN service
within the Virtual Interface.rw INTEGER .1.3.6.1.4.1.351.110.5.2.8.3.1.1.4 |
vrtlIntrQbinRateThe rate at which cells in the QBIN are serviced.
Max Cell rate for OC3 interface is 353208 cell/sec.rw INTEGER .1.3.6.1.4.1.351.110.5.2.8.3.1.1.5 |
vrtlIntrQbinDiscardSelectionVirtual Interface QBin Congestion control option.rw Enumeration .1.3.6.1.4.1.351.110.5.2.8.3.1.1.6 |
vrtlIntrQbinMaxThresholdMax cells that can be queued in the QBIN.
The Get value will be different from the Set
value because of FW internal round up.rw INTEGER .1.3.6.1.4.1.351.110.5.2.8.3.1.1.7 |
vrtlIntrQbinClpHiThresholdThe threshold above which the tagged cells
will be dropped.
The Get value will be different from the Set
value because of FW internal round up.rw INTEGER .1.3.6.1.4.1.351.110.5.2.8.3.1.1.8 |
vrtlIntrQbinClpLoThresholdValid only if congestion control is set to
CLP hysterises. The threshold upto which the
dropping of the tagged cells should continue once
it has crossed CLP HI threshold.
The Get value will be different from the Set
value because of FW internal round up.rw INTEGER .1.3.6.1.4.1.351.110.5.2.8.3.1.1.9 |
vrtlIntrQbinFrameDiscardThresholdValid only if congestion control is set to
Frame Discard. It is the threshold after which
the QE will start discarding the entire frame
if one or more cells of the frame is discarded..
The Get value will be different from the Set
value because of FW internal round up.rw INTEGER .1.3.6.1.4.1.351.110.5.2.8.3.1.1.10 |
vrtlIntrQbinEfciThresholdThe threshold above which the EFCI bits of
the cell is set.
The Get value will be different from the Set
value because of FW internal round up.rw INTEGER .1.3.6.1.4.1.351.110.5.2.8.3.1.1.11 |
virtualInterfaceQbinCnt OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.5.2.8.4 |
vrtlIntrQbinCounterTableVirtual Interface QBin Counter Table. SEQUENCE OF VrtlIntrQbinCounterEntry .1.3.6.1.4.1.351.110.5.2.8.4.1 |
vrtlIntrQbinCounterEntryAn entry in the Virtual Interface Qbin Counter Table. VrtlIntrQbinCounterEntry .1.3.6.1.4.1.351.110.5.2.8.4.1.1 |
queConuterVrtlIntrNumVirtual Interface Number.ro INTEGER .1.3.6.1.4.1.351.110.5.2.8.4.1.1.1 |
queCounterVrtlIntrQbinNumVirtual Interface Qbin Number. There are totaly 16 Qbin
per Virtual Interface.ro INTEGER .1.3.6.1.4.1.351.110.5.2.8.4.1.1.2 |
vrtlIntrQbinCurrentCellCntTotal number of cells currently in the Qbin.ro Counter .1.3.6.1.4.1.351.110.5.2.8.4.1.1.3 |
vrtlIntrQbinRxdCellCntTotal number of cells arrived to the QBIN.ro Counter .1.3.6.1.4.1.351.110.5.2.8.4.1.1.4 |
vrtlIntrQbinTxdCellCntTotal number of cells departured from QBIN.ro Counter .1.3.6.1.4.1.351.110.5.2.8.4.1.1.5 |
vrtlIntrQbinDiscardedCellCntTotal number of arrivals to QBIN which were discarded.ro Counter .1.3.6.1.4.1.351.110.5.2.8.4.1.1.6 |
rpmPortTableList of RPM backplane sub-interfaces. SEQUENCE OF RpmPortEntry .1.3.6.1.4.1.351.110.5.2.9.1.1 |
rpmPortEntryAn entry for the RPM backplane sub interface.
Each entry contains RPM's backplane sub interface number,
its IP address and ATM address. RpmPortEntry .1.3.6.1.4.1.351.110.5.2.9.1.1.1 |
rpmPortSlotNumSpecifies the slot number of the RPM card.ro INTEGER .1.3.6.1.4.1.351.110.5.2.9.1.1.1.1 |
rpmPortInterfaceThis is the RPM's backplane interface.
Currently there is only one interface.ro INTEGER .1.3.6.1.4.1.351.110.5.2.9.1.1.1.2 |
rpmPortSubInterfaceIt identifies a sub-interface.
(SNMP doent support index value 0)
sub-interface starts from 1. The sub-interface
0 in CLI will be 1 here. So sub-interface
is incremented by 1.ro INTEGER .1.3.6.1.4.1.351.110.5.2.9.1.1.1.3 |
rpmPortRowStatusThis indicates the status of this sub-interface.
1 ==> ADD
2 ==> DELETE
3 ==> MODIFYro Enumeration .1.3.6.1.4.1.351.110.5.2.9.1.1.1.4 |
rpmPortIpAddressIP address of the sub-interface.ro IpAddress .1.3.6.1.4.1.351.110.5.2.9.1.1.1.5 |
rpmPortSubNetMaskSUB-NETMASK of the sub-interface.ro IpAddress .1.3.6.1.4.1.351.110.5.2.9.1.1.1.6 |
rpmPortStateThis indicates the state of this sub-interface.
1 ==> notConfigured
2 ==> active
3 ==> failed.
Currently 'failed' state is not supported.ro Enumeration .1.3.6.1.4.1.351.110.5.2.9.1.1.1.7 |
rpmIfCnfResPart OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.5.2.9.2 |
rpmIfCnfRscPartTableThe table is for RPM interface resource partition. SEQUENCE OF RpmIfCnfRscPartEntry .1.3.6.1.4.1.351.110.5.2.9.2.1 |
rpmIfCnfRscPartEntryAn entry for a logical interface RpmIfCnfRscPartEntry .1.3.6.1.4.1.351.110.5.2.9.2.1.1 |
rpmIfRscSlotNumSpecifies the slot number of the RPM card.ro INTEGER .1.3.6.1.4.1.351.110.5.2.9.2.1.1.1 |
rpmIfRscPartIfNumThis is backplane interface number.
Currently there is only one interface.ro INTEGER .1.3.6.1.4.1.351.110.5.2.9.2.1.1.2 |
rpmIfRscPartCtrlrNumThis is index for controller using the interface .
1 - PAR
2 - PNNI
3 - TAGro Enumeration .1.3.6.1.4.1.351.110.5.2.9.2.1.1.3 |
rpmIfRscPrtRowStatusThis will add, delete or modify the partition.
1 ==> ADD
2 ==> DELETE
3 ==> MODIFYro Enumeration .1.3.6.1.4.1.351.110.5.2.9.2.1.1.4 |
rpmIfRscPrtIngrPctBandwidthThe percentage of logical interface bandwidth.ro INTEGER .1.3.6.1.4.1.351.110.5.2.9.2.1.1.5 |
rpmIfRscPrtEgrPctBandwidthThe percentage of logical interface bandwidth.ro INTEGER .1.3.6.1.4.1.351.110.5.2.9.2.1.1.6 |
rpmIfRscPrtVpiLowThe beginning of the VPI range reserved for this partition.ro INTEGER .1.3.6.1.4.1.351.110.5.2.9.2.1.1.7 |
rpmIfRscPrtVpiHighThe end of the VPI range reserved for this partition.ro INTEGER .1.3.6.1.4.1.351.110.5.2.9.2.1.1.8 |
rpmIfRscPrtVciLowThe beginning of the VCI range reserved for this partition.
This field is only valid for logical interfaces configured with
a single VPI.ro INTEGER .1.3.6.1.4.1.351.110.5.2.9.2.1.1.9 |
rpmIfRscPrtVciHighThe end of the VCI range reserved for this partition.
This field is only valid for logical interfaces configured with
a single VPI.ro INTEGER .1.3.6.1.4.1.351.110.5.2.9.2.1.1.10 |
rpmIfRscPrtMaxChansThis represents no. of channels that are available to the
controller.ro INTEGER .1.3.6.1.4.1.351.110.5.2.9.2.1.1.11 |
rpmChanGrpTableThe RPM channel table. SEQUENCE OF RpmChanGrpEntry .1.3.6.1.4.1.351.110.5.2.10.1.1 |
rpmChanGrpEntryAn entry for logical channel. RpmChanGrpEntry .1.3.6.1.4.1.351.110.5.2.10.1.1.1 |
rpmChanSlotNumSpecifies the slot number of the RPM card.ro INTEGER .1.3.6.1.4.1.351.110.5.2.10.1.1.1.1 |
rpmChanInterfaceThis is the RPM's backplane interface.
Currently there is only one interface.ro INTEGER .1.3.6.1.4.1.351.110.5.2.10.1.1.1.2 |
rpmChanNumThis is the LCN. A unique number which identifies a
connection. LCN maps VPI and VCI.
For VCC, VCI range is 1..3825, and LCN range is 16..3840.
LCN = VCI + 16.
For VPC, VPI range is 1..255 and LCN range is 3841..4095.
LCN = VPI + 3840.ro INTEGER .1.3.6.1.4.1.351.110.5.2.10.1.1.1.3 |
rpmChanRowStatusThis indicates the status of this channel.
1 ==> ADD
2 ==> DELETE
3 ==> MODIFYro Enumeration .1.3.6.1.4.1.351.110.5.2.10.1.1.1.4 |
rpmChanVcdVirtual Circuit Descriptor. A unique number which identifies a
connection.ro INTEGER .1.3.6.1.4.1.351.110.5.2.10.1.1.1.5 |
rpmChanVpiThe VPI value for this channel.
For VPC, VPI range is 1..255 and LCN range is 3841..4095.
LCN = VPI + 3840ro INTEGER .1.3.6.1.4.1.351.110.5.2.10.1.1.1.6 |
rpmChanVciThe VCI value for this channel.
For VCC, VCI range is 1..3825, and LCN range is 16..3840.
LCN = VCI + 16.ro INTEGER .1.3.6.1.4.1.351.110.5.2.10.1.1.1.7 |
rpmChanSubInterfaceThis is the RPM's backplane sub-interface.
(SNMP doent support index value 0)
sub-interface starts from 1. The sub-interface
0 in CLI will be 1 here. So sub-interface
is incremented by 1.ro INTEGER .1.3.6.1.4.1.351.110.5.2.10.1.1.1.8 |
rpmChanLocalVpiThis VPI together with the local VCI and NSAP represents the
local end point in this connection. The VPI value is zero if it
is a VCC conn. type.ro INTEGER .1.3.6.1.4.1.351.110.5.2.10.1.1.1.9 |
rpmChanLocalVciThis VCI together with the local VPI and NSAP represents the
local end point in this connection.ro INTEGER .1.3.6.1.4.1.351.110.5.2.10.1.1.1.10 |
rpmChanLocalNsapThe Near End NSAP Address value for this channel.
This NSAP is 20 bytes binary, among these 20 bytes: 13 bytes
as node name, 2 bytes for Cisco ID, 1 byte rsvd, 3 bytes for
logical interface: slot (1 byte) and port number (2 bytes),
the last byte is for SEL
Of the 13 bytes for the node name, only the first 8 bytes are
used. If the node name is n (0 < n < 8) bytes long, the node
name must be left justified ( Bytes 1 to n contain the node name
and bytes (n+1) to 8 must be 0 ). Bytes 9-13 must be always 0.ro RpmNsapAddress .1.3.6.1.4.1.351.110.5.2.10.1.1.1.11 |
rpmChanRemoteVpiThis VPI together with the remote VCI and NSAP represents the
remote end point in this connection.ro INTEGER .1.3.6.1.4.1.351.110.5.2.10.1.1.1.12 |
rpmChanRemoteVciThis VCI together with the remote VPI and NSAP represents the
remote end point in this connection.ro INTEGER .1.3.6.1.4.1.351.110.5.2.10.1.1.1.13 |
rpmChanRemoteNsapThe Far End NSAP Address value for this channel.
This NSAP is 20 bytes binary, among these 20 bytes: 13 bytes
as prefix, 2 bytes for Cisco ID, 1 byte rsvd, 3 bytes for
logical interface: slot (1 byte) and port number (2 bytes),
the last byte is for SELro RpmNsapAddress .1.3.6.1.4.1.351.110.5.2.10.1.1.1.14 |
rpmChanTypeThis specifies the connection type
1 ==> SVC
2 ==> PVC
3 ==> Soft PVC
Currently only PVC is supported.ro Enumeration .1.3.6.1.4.1.351.110.5.2.10.1.1.1.15 |
rpmChanConnTypeThis specifies the connection type
1 ==> Virtual Path Connection
2 ==> Virtual Channel Connectionro Enumeration .1.3.6.1.4.1.351.110.5.2.10.1.1.1.16 |
rpmChanServiceTypeThis specifies the service type
1 ==> Constant Bit Rate
2 ==> Variable Bit Rate
4 ==> Unspecified Bit Rate
5 ==> ATM frame relay
6 ==> standard ABR
7 ==> foresight ABR
Only VBR,standard ABR and UBR are supported in phase I.ro Enumeration .1.3.6.1.4.1.351.110.5.2.10.1.1.1.17 |
rpmChanMastershipThis specifies which end of the connection is the master.
This is used by PXM to determine if this end point is
master or slave. Only in AXIS shelf, 'unknown' is always used.
For consistency it was added here.ro Enumeration .1.3.6.1.4.1.351.110.5.2.10.1.1.1.18 |
rpmChanRtePriorityThis is also known as class of service, it is used by
PXM to determine how important this connection is when
selecting connections to route.ro INTEGER .1.3.6.1.4.1.351.110.5.2.10.1.1.1.19 |
rpmChanMaxCostMaximum allowed cost. It is related to Cost Based Routing.
This is used by PXM so that it won't choose a path with a
cost greater than this configured level.ro INTEGER .1.3.6.1.4.1.351.110.5.2.10.1.1.1.20 |
rpmChanRestrictTrkTypeRestricted trunk type for routing, used by PXM. It
specifies that the connection either cannot be routed over satellite
trunks or terrestrial trunks, or it can be on any type of trunk.ro Enumeration .1.3.6.1.4.1.351.110.5.2.10.1.1.1.21 |
rpmChanPCRPeak cell rate.(in cells per sec.)ro INTEGER .1.3.6.1.4.1.351.110.5.2.10.1.1.1.22 |
rpmChanRemotePCRPeak cell rate of the other end, if not set, will be
set to the same as local end PCR.ro INTEGER .1.3.6.1.4.1.351.110.5.2.10.1.1.1.23 |
rpmChanMCRMinimum cell rate.(in cells per sec.)ro INTEGER .1.3.6.1.4.1.351.110.5.2.10.1.1.1.24 |
rpmChanRemoteMCRMinimum cell rate of the other end, if not set, will be
set to the same as local end MCR.ro INTEGER .1.3.6.1.4.1.351.110.5.2.10.1.1.1.25 |
rpmChanPercentUtilThis is the expected long-term utilization of the
channel by this end-point.ro INTEGER ( 0..100 ) .1.3.6.1.4.1.351.110.5.2.10.1.1.1.26 |
rpmChanRemotePercentUtilThis is the expected long-term utilization of the
channel by the other end-point. If this is not specified in
the connection setup request, it'll be set to be the same
as the local end.ro INTEGER ( 0..100 ) .1.3.6.1.4.1.351.110.5.2.10.1.1.1.27 |
rpmChanEncapTypeATM adaptation layer (AAL) and Encapsulation type.
aal5snap - LLC/SNAP precedes the protocol datagram.
aal34smds - Encapsulation for SMDS network.
aal5nlpid - Encapsulation that allows ATM interfaces to
interoperate with HSSI.
qsaal - signaling type PVC used for setting up or
tearing down SVCs.
ilmi - used to set up communication with ILMI.
aal5mux[protocol] - a MUX-type Virtual circuit.
ppp - PPP over ATM.
The Encapsulation types aal34smds, qsaal and ilmi
are not supported.ro Enumeration .1.3.6.1.4.1.351.110.5.2.10.1.1.1.28 |
rpmChanMidLowStarting Message Identifier Number for this PVC.ro INTEGER .1.3.6.1.4.1.351.110.5.2.10.1.1.1.29 |
rpmChanMidHighEnding Message Identifier Number for this PVC.ro INTEGER .1.3.6.1.4.1.351.110.5.2.10.1.1.1.30 |
rpmChanBurstSizeThe Maximum number of ATM cells the virtual circuit can
transmit.ro INTEGER .1.3.6.1.4.1.351.110.5.2.10.1.1.1.31 |
rpmChanInArpFreqSpecifies how often (in minutes) Inverse ARP datagrams
will be sent on this virtual circuit.ro INTEGER .1.3.6.1.4.1.351.110.5.2.10.1.1.1.32 |
rpmChanOAMloopbackSpecifies how often (in seconds) to generate an OAM F5
loopback cell from this virtual circuit.ro INTEGER .1.3.6.1.4.1.351.110.5.2.10.1.1.1.33 |
rpmChanStateThis indicates the status of this channel.
1 ==> notConfigured
2 ==> active
3 ==> failed.
Currently 'failed' state is not supported.
When the channel is not added, the state is
notConfigured.ro Enumeration .1.3.6.1.4.1.351.110.5.2.10.1.1.1.34 |
rpmChanVirtualTemplateSpecifies the Virtual Template used for CISCO PPP.
If it is not using Virtual Template then this value
is 0.ro INTEGER .1.3.6.1.4.1.351.110.5.2.10.1.1.1.35 |
rpmChanAbrRDFThis is valid only for ABR Service Type.
Rate Decrease Factor: Controls the rate decrease which occurs
when backward RM-cells with CI=1 are received. Larger values
lead to faster rate decrease.
Reference - ATM Forum Traffic Management Specification
Version 4.0 Section 5.10.2ro INTEGER .1.3.6.1.4.1.351.110.5.2.10.1.1.1.36 |
rpmChanAbrRIFThis is valid only for ABR Service Type.
Rate Increase Factor: Controls the rate increase which occurs
when a backward RM-cell is received with CI=0 and NI=0. Larger
values lead to faster rate increase.
Reference - ATM Forum Traffic Management Specification
Version 4.0 Section 5.10.2ro INTEGER .1.3.6.1.4.1.351.110.5.2.10.1.1.1.37 |
cesmPort OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.5.3.1 |
cesmPortCnfGrp OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.5.3.1.1 |
cesmPortCnfGrpTableThe config table is for logical port interface
there are 192 entries for 8 DS1s or 248 entries for 8 E1s SEQUENCE OF CesmPortCnfGrpEntry .1.3.6.1.4.1.351.110.5.3.1.1.1 |
cesmPortCnfGrpEntryAn entry for logical port CesmPortCnfGrpEntry .1.3.6.1.4.1.351.110.5.3.1.1.1.1 |
cesPortNumThis is logical port number.
If we have T1 card then the maximum port number is 192
and if we have E1 card the maximum port number can be 248
for T3 only one port is supported.ro INTEGER .1.3.6.1.4.1.351.110.5.3.1.1.1.1.1 |
cesPortRowStatusThis variable enables or modifies the port
1- add
2 - del
3 - modrw Enumeration .1.3.6.1.4.1.351.110.5.3.1.1.1.1.2 |
cesPortLineNumThis represents the line number to which this port is associated.
For T3 only one line is supported.rw INTEGER .1.3.6.1.4.1.351.110.5.3.1.1.1.1.3 |
cesPortTypeThis represents port type whether it is carrying subrate circuits
strau. If it is strau port then it can have only one DS0 time slot.
In case of unstructured all the time slots will be allocated to that.
Strau ports are not supported in CESM-8T1/E1 or CESM-T3E3.
framingOnVcDisconnect is similar to unstructured port
during normal operation. In case of channel failure, line data will
be looped back towards line.
CESM-T3E3 card will support only unstructured mode.rw Enumeration .1.3.6.1.4.1.351.110.5.3.1.1.1.1.4 |
cesPortDs0ConfigBitMapThis respesents bit map of DS0s for a line which
are used to form this logical port. Bit 0
represents DS0-1.rw INTEGER (0..'ffffff'h) .1.3.6.1.4.1.351.110.5.3.1.1.1.1.5 |
cesPortNumOfDs0SlotThis represents number of DS0 time slots configured to this
Port. If the port type is strau then this can not have
more than 1 DS0 time slot.rw INTEGER .1.3.6.1.4.1.351.110.5.3.1.1.1.1.6 |
cesPortNumOfSCIPerDS0This is applicable only to the Strau Port.
represents number of subcircuit in the DS0 time slot.
8 = there are 8 no .of 8kbps links (1 bit)
4 = there are 4 no .of 16kbps links (2 bit)
2 = there are 2 no .of 32kbps links (4 bit)
Currently not supported in CESM-8rw INTEGER .1.3.6.1.4.1.351.110.5.3.1.1.1.1.7 |
cesPortSpeedConfigured speed of port in kbps
Max speed for T1 = 1544
Max speed for E1 = 2038
Max speed for T3 = 44736
Max spped for E3 = 34368ro INTEGER .1.3.6.1.4.1.351.110.5.3.1.1.1.1.8 |
cesPortStateThis variable indicates the state of the
logical portro Enumeration .1.3.6.1.4.1.351.110.5.3.1.1.1.1.9 |
cesPortBERTEnableThis variable enables BERT
This object is not supported in CESM-T3E3.rw Enumeration .1.3.6.1.4.1.351.110.5.3.1.1.1.1.10 |
cesPortNextAvailableThis variable contains the next UNUSED logical port number
of the possible 32 DS0s * n ports.
This number can be used in channel config table, the
cesportNextAvailable gets updated if the number gets
used to create a logical port.
A '0' indicates that no more ports are available.ro INTEGER .1.3.6.1.4.1.351.110.5.3.1.1.2 |
cesPortsUsedLine1Each bits set represents a DS0 that is used by all the
logical ports defined so far for that DS1, the most significant
byte is invalid for DS1
This is for line 1ro INTEGER (0..'ffffff'h) .1.3.6.1.4.1.351.110.5.3.1.1.3 |
cesPortsUsedLine2Each bits set represents a DS0 that is used by all the
logical ports defined so far for that DS1, the most significant
byte is invalid for DS1
This is for line 2ro INTEGER (0..'ffffff'h) .1.3.6.1.4.1.351.110.5.3.1.1.4 |
cesPortsUsedLine3Each bits set represents a DS0 that is used by all the
logical ports defined so far for that DS1, the most significant
byte is invalid for DS1
This is for line 3ro INTEGER (0..'ffffff'h) .1.3.6.1.4.1.351.110.5.3.1.1.5 |
cesPortsUsedLine4Each bits set represents a DS0 that is used by all the
logical ports defined so far for that DS1, the most significant
byte is invalid for DS1
This is for line 4ro INTEGER (0..'ffffff'h) .1.3.6.1.4.1.351.110.5.3.1.1.6 |
cesPortsUsedLine5Each bits set represents a DS0 that is used by all the
logical ports defined so far for that DS1, the most significant
byte is invalid for DS1
This is for line 5ro INTEGER (0..'ffffff'h) .1.3.6.1.4.1.351.110.5.3.1.1.7 |
cesPortsUsedLine6Each bits set represents a DS0 that is used by all the
logical ports defined so far for that DS1, the most significant
byte is invalid for DS1
This is for line 6ro INTEGER (0..'ffffff'h) .1.3.6.1.4.1.351.110.5.3.1.1.8 |
cesPortsUsedLine7Each bits set represents a DS0 that is used by all the
logical ports defined so far for that DS1, the most significant
byte is invalid for DS1
This is for line 7ro INTEGER (0..'ffffff'h) .1.3.6.1.4.1.351.110.5.3.1.1.9 |
cesPortsUsedLine8Each bits set represents a DS0 that is used by all the
logical ports defined so far for that DS1, the most significant
byte is invalid for DS1
This is for line 8ro INTEGER (0..'ffffff'h) .1.3.6.1.4.1.351.110.5.3.1.1.10 |
cesmPortCnfResPartGrp OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.5.3.1.2 |
cesmPortCnfResPartGrpTableThis table contains the configuration of port resource
partition
This is applicable for MGX8820(formerly AXIS) Rel. 5 and MGX. SEQUENCE OF CesmPortCnfResPartGrpEntry .1.3.6.1.4.1.351.110.5.3.1.2.1 |
cesmPortCnfResPartGrpEntryAn entry for logical port CesmPortCnfResPartGrpEntry .1.3.6.1.4.1.351.110.5.3.1.2.1.1 |
cesmResPartPortNumThis is the logical port number, the index to this table.
If we have T1 card then the maximum port number is 192
and if we have E1 card the maximum port number can be 248.
CESM-T3/E3 supports only one port.ro INTEGER .1.3.6.1.4.1.351.110.5.3.1.2.1.1.1 |
cesmResPartCtrlrNumThis is index for controller using the portro Enumeration .1.3.6.1.4.1.351.110.5.3.1.2.1.1.2 |
cesmResPartRowStatusThis will add, delete or modify the partition.
1 ==> ADD
2 ==> DELETE
3 ==> MODIFYrw Enumeration .1.3.6.1.4.1.351.110.5.3.1.2.1.1.3 |
cesmResPartNumOfLcnAvailThis represents number of LCNs available for this
controller and this port.
In CESM-T3/E3 and 8-T1/E1,this value is 1.rw INTEGER .1.3.6.1.4.1.351.110.5.3.1.2.1.1.4 |
cesmResPartLcnLowThis represents low end of reserved LCN
In CESM-8T1/E1 and T3/E3, this refers to the
logical port.rw INTEGER .1.3.6.1.4.1.351.110.5.3.1.2.1.1.5 |
cesmResPartLcnHighThis represents high end of reserved LCN
In CESM-8T1/E1 and T3/E3, this refers to the
logical port.rw INTEGER .1.3.6.1.4.1.351.110.5.3.1.2.1.1.6 |
cesmResPartIngrPctBWThe percentage of total ingress bandwidth reserved.
In CESM-8T1/E1 and T3/E3, as
there is only one LCN per port and it could be
used by only one controller,this value is
100% for that controller.rw INTEGER .1.3.6.1.4.1.351.110.5.3.1.2.1.1.7 |
cesmResPartEgrPctBWThe percentage of total egress bandwidth reserved
In CESM-8T1/E1 and T3/E3, as
there is only one LCN per port and it could be
used by only one controller,this value is
100% for that controller.rw INTEGER .1.3.6.1.4.1.351.110.5.3.1.2.1.1.8 |
cesmResPartCtrlrIDThis is the controller identifier for the resource patition.
The default value is set for PNNI controller.rw INTEGER .1.3.6.1.4.1.351.110.5.3.1.2.1.1.9 |
cesmChanCnfGrp OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.5.3.2.1 |
cesmChanCnfGrpTableThe config table is for logical channel interface
there are 4 entries for 4 DS1s in case of CESM-4P
in case of CESM-8P it can have 263 entries.
For CESM-T3/E3 , this will have only one entry. SEQUENCE OF CesmChanCnfGrpEntry .1.3.6.1.4.1.351.110.5.3.2.1.1 |
cesmChanCnfGrpEntryAn entry for logical channel CesmChanCnfGrpEntry .1.3.6.1.4.1.351.110.5.3.2.1.1.1 |
cesCnfChanNumRefers to the virtual connection no. In case of
CESM-4P the range is 16..19 (only for 4 entries).
for CESM-8t1 we can have 192 and for CESM-8e1 we
can have 248 channels. For CESM-T3/E3 we can have only one
connection.
For CESM-T1/E1/T3/E3, channel number starts from 35
in Release2.2ro INTEGER .1.3.6.1.4.1.351.110.5.3.2.1.1.1.1 |
cesChanRowStatusThis indicates the channel status
1 ==> ADD
2 ==> DELETE
3 ==> MODIFY
4 ==> Setting this object to outOfService takes the channel
out of service or brings the channel 'down'. The channel
can be brought 'up' again by setting the object to mod.rw Enumeration .1.3.6.1.4.1.351.110.5.3.2.1.1.1.2 |
cesMapPortNumIn case of CESM-4P this variable specifies the port number
to which this channel is associated. Mappings are as -
Port 1 - channel 16, 2-17, 3-18, 4-19 (it can take value from 1..4)
In CESM-8 this variable gives mapping between logical channel
and physical line number.
In case of CESM-8P instead of this cesChanPortNum will be used
to have the mapping between Channel and logical Port. In case of
CESM-T3 it can be 1..1ro INTEGER .1.3.6.1.4.1.351.110.5.3.2.1.1.1.3 |
cesMapVpiThe value of this object is equal to the VPI used for the emulated
circuit represented by this connection. In MGX8220( formerly AXIS)
Implementaion slot number of the card will be used for this.ro INTEGER .1.3.6.1.4.1.351.110.5.3.2.1.1.1.4 |
cesMapVciThis specifies VCI for emulated circuit represented by this VC.
Our Implementation cesCnfChanNum will be used for this.
In case of CESM-4P valid range is 16..19.
In case of CESM-8P valid range is 32..279.
In case of CESM-T3/E3 valid value is 32.ro INTEGER .1.3.6.1.4.1.351.110.5.3.2.1.1.1.5 |
cesCBRServiceThis specifies data type supported by the CBR service
Only Unstructured mode is supported in CESM-4P
CESM-8P supports both structured and unstructured mode for
T1/E1 and supports only unstructured mode in case of T3/E3.
In CESM-T3 only unstructured is supported.ro Enumeration .1.3.6.1.4.1.351.110.5.3.2.1.1.1.6 |
cesCBRClockModeThis specifies clocking mode of the CBR service
Only synchronous mode is supported in CESM-4P
Structured mode is always synchronous. CESM -T3
will support only synchronous.rw Enumeration .1.3.6.1.4.1.351.110.5.3.2.1.1.1.7 |
cesCasSpecifies if CAS bits are carried by the service.
This also selects which AAL1 format should be used.
Only basic mode is supported for unstructured connections
Only basic mode is supported in CESM-4P and CESM-T3E3 .
If type is ccs then this particular VC is carrying
Signaling information. ccs option is not supported in CESM-8T1E1.
In CESM-8T1/E1 all channels on a line should have the same value.
basicNoPointer should be used for adding 1x64 basic connections
without an AAL1 pointer ( CES-IS 2.0 compliance ).
when cesCas = basic, for 1x64 connections, cells will be generated
with a AAL1 pointer.Similarly while receiving, pointer will be
expected in the incoming cells.
ds1SfCasMF and ds1EsfCasMF should be used when line level
multiframe sync to be enabled.rw Enumeration .1.3.6.1.4.1.351.110.5.3.2.1.1.1.8 |
cesPartialFillSpecifies the number of user octets per cell, if partial
cell fill is used. 47 means partial fill disabled.
Partial fill is not supported in CESM-4P
Ranges for partial fill are:
T1 struct 25 - 47
T1 unstruct 33 - 47
E1 struct 20 - 47
E1 unstruct 33 - 47
and
partial fill for any channel should always exceed the number
of time slots assigned to that channel.rw INTEGER .1.3.6.1.4.1.351.110.5.3.2.1.1.1.9 |
cesBufMaxSizeSpecifies the maximum size in octets of egress buffer.
CESM - 4P:
Should be at least 0.6*CDVRxT for a T1 line and
0.7 * CDVRxT for a E1 line. 0 can be specified to internally
compute the value
Defaults for CESM-8T1E1 and CESM-T3E3
-
Default value of cesBufMaxSize is 0.
Maximum value for CESM-8T1E1 and CESM-T3E3
For T1 UDT and E1 UDT : 16224 bytes
For T1 SDT : 384 * N bytes
For E1 SDT : 417 * N bytes
For T3 UDT and E3 UDT : 16224 bytes
where N is the number of timeslots assigned in Nx64
connection. For T1-UDT and E1 UDT use N = 32 .
Minimum value for CESM-8T1E1 and CESM-T3E3
In CESM-8T1/E1 and CESM-T3E3 this object ( unit in bytes ) should be at
least the greater of
(1) CDVT in frames * 2 * N
(2) ( CDVT in frames + number of frames in two cells ) * N
where N is the number of timeslots assigned in Nx64
connection. For T1-UDT and E1-UDT use N = 32.rw INTEGER .1.3.6.1.4.1.351.110.5.3.2.1.1.1.10 |
cesCDVRxTSpecifies maximum cell arrival jitter that the reassembly
process will tolerate.
In case of CESM-8P it should be in increment of 125 micro secs and
Max limit are as follows. T1 = 24 ms E1 = 26 ms T3 = 1.447 ms
and E3 = 1.884 ms.
Default values in CESM-8T1/E1 and CESM-T3/E3.:
For T1 and E1 , 1000 microsecs.
For T3 and E3 , 1000 microsecs.rw INTEGER .1.3.6.1.4.1.351.110.5.3.2.1.1.1.11 |
cesCellLossIntegrationPeriodSpecifies the cell loss integration period in millisecondsrw INTEGER .1.3.6.1.4.1.351.110.5.3.2.1.1.1.12 |
cesChanLocRmtLpbkStateLoopback on cellbus in egress direction.rw Enumeration .1.3.6.1.4.1.351.110.5.3.2.1.1.1.13 |
cesChanTestTypeThis is the type of the test
1 = Test Continuity
2 = Test Delay
3 = no test is initated
4 = test continuity with sti cell format
5 = test delay with sti cell formatrw Enumeration .1.3.6.1.4.1.351.110.5.3.2.1.1.1.14 |
cesChanTestStateThis shows the state of the test
1 = Passed
2 = Failed
3 = In Progress
4 = Not In Progressro Enumeration .1.3.6.1.4.1.351.110.5.3.2.1.1.1.15 |
cesChanRTDResultThis is round trip delay in millisecondsro INTEGER .1.3.6.1.4.1.351.110.5.3.2.1.1.1.16 |
cesChanPortNumThis indicates to which logical port this connection
belongs. Applicable on CESM-8T1/E1 or CESM-T3/E3.
1.. 248 for E1
1.. 192 for T1
1.. 1 for T3
Only applicable to CESM-8Prw INTEGER .1.3.6.1.4.1.351.110.5.3.2.1.1.1.17 |
cesChanConnTypeThis indicates the type of connection.
1 = PVC
2 = SVC
3 ==> SPVC connection
Only applicable to CESM-8P and CESM-T3/E3.rw Enumeration .1.3.6.1.4.1.351.110.5.3.2.1.1.1.18 |
cesChanStrauSciNumThis indicates the type of connection.
1 = Normal Channel (nonStrauChannel(0) )
2 = SCI 1 i.e bit 1 & 2
3 = SCI 2 i.e bit 3 & 4
4 = SCI 3 i.e bit 5 & 6
5 = SCI 4 i.e bit 7 & 8
Currently not supported in CESM-8
Not applicable for CESM-4 and CESM-T3/E3rw Enumeration .1.3.6.1.4.1.351.110.5.3.2.1.1.1.19 |
cesChanIdleDetEnableThis indicates the type of Idle detection enabled
1 = Idle code detection is disabled.
2 = This will enable Idle detection whenver it detects
Onhook in ABCD bits. Onhook code is configurable
using cesChanOnhookCode. Applicable in
structured mode.
3 = This will enable payload Idle code detection.
Idle pattern is configurable through cesChanIdleSignalCode
variable.
Only applicable to CESM-8T1/E1 and non strau channels
This will be supported in future releaserw Enumeration .1.3.6.1.4.1.351.110.5.3.2.1.1.1.20 |
cesChanIdleSignalCodeWhen cesChanIdleDetEnable = enableIdlePatternDet
3. This object will carry value 0..0xff and this will
indicate Idle pattern in DS0 time slots.
Only applicable to CESM-8P and not supported in this release.rw INTEGER .1.3.6.1.4.1.351.110.5.3.2.1.1.1.21 |
cesChanIdleCodeIntgnPeriodThis variable indicates the Integration period in seconds
whenever cesChanIdleDetEnable = enableIdlePatternDet
Only applicable to CESM-8P and not supported in this release.rw INTEGER .1.3.6.1.4.1.351.110.5.3.2.1.1.1.22 |
cesChanOnhookCodeWhen cesChanIdleDetEnable = enableOnhookDet
1. This will carry value 0..3 for framing mode SF.
2. This will carry value 0..15 for framing mode ESF/e1Cas.
Only applicable for CESM-8T1/E1rw INTEGER .1.3.6.1.4.1.351.110.5.3.2.1.1.1.23 |
cesChanConditionedDataThis byte will indicate Idle data to be sent
towards the line whenever channels goes
in to Underrun
Only applicable for CESM-8T1/E1rw INTEGER .1.3.6.1.4.1.351.110.5.3.2.1.1.1.24 |
cesmChanExtTrgIdleSuppUsing this variable we can initiate Idle suppression on the
connection. This can be set by external signalling device.
Only applicable to CESM-8T1/E1.rw Enumeration .1.3.6.1.4.1.351.110.5.3.2.1.1.1.25 |
cesmChanConditionedSigCodeThis byte will indicate Signal code to be sent
sent towards the line whenever channels goes
in to Underrun
Only applicable to CESM-8T1/E1rw INTEGER .1.3.6.1.4.1.351.110.5.3.2.1.1.1.26 |
cesLocalVpiThis VPI together with the local VCI and NSAP represents the
local end point in this connection, this object is read only,
therefore it'll be assigned by SM to 0.ro INTEGER .1.3.6.1.4.1.351.110.5.3.2.1.1.1.27 |
cesLocalVciThis VCI together with the local VPI and NSAP represents the
local end point in this connection, this object is read only,
therefore it'll be assigned by SM to 0.ro INTEGER .1.3.6.1.4.1.351.110.5.3.2.1.1.1.28 |
cesLocalNSAPThis NSAP is 20 bytes binary, among these 20 bytes: 13 bytes
as prefix, 2 bytes for Cisco ID, 1 byte rsvd, 3 bytes for
logical interface: slot (1 byte) and port number (2 bytes),
the last byte is for SELrw OCTET STRING .1.3.6.1.4.1.351.110.5.3.2.1.1.1.29 |
cesRemoteVpiThis VPI together with the remote VCI and NSAP represents the
remote end point in this connection.
The value should be 0 for a DACS connection in MGXrw INTEGER .1.3.6.1.4.1.351.110.5.3.2.1.1.1.30 |
cesRemoteVciThis VCI together with the remote VPI and NSAP represents the
remote end point in this connection.
The value should be 0 for a DACS connection in MGXrw INTEGER .1.3.6.1.4.1.351.110.5.3.2.1.1.1.31 |
cesRemoteNSAPThis NSAP is 20 bytes binary, among these 20 bytes: 13 bytes
as prefix, 2 bytes for Cisco ID, 1 byte rsvd, 3 bytes for
logical interface: slot (1 byte) and port number (2 bytes),
the last byte is for SELrw OCTET STRING .1.3.6.1.4.1.351.110.5.3.2.1.1.1.32 |
cesMastershipThis is used by PXM to determine if this end point is
master or slave, a new type unknown is added to identify
the SM in MGX8220(formerly AXIS) shelf and the SM in MGX shelf.
In MGX8220 shelf, user can still use addchan to add a channel without
specifying X/Y/P parameters. But in MGX shelf, if the
user uses addchan without X/Y/P set (based on this object
being set to type 3 unknown), SPM on PXM will reject
the request. It must be supplied in connection setup requestrw Enumeration .1.3.6.1.4.1.351.110.5.3.2.1.1.1.33 |
cesVpcFlagThis represents the connection type, used for PXM to
identify VPC/VCC but CESM card doesn't use it
always set to vcc for CESM cardrw Enumeration .1.3.6.1.4.1.351.110.5.3.2.1.1.1.34 |
cesConnServiceTypeThis specifies the service type
1 ==> Constant Bit Rate
2 ==> Variable Bit Rate
3 ==> Not used
4 ==> Unspecified Bit Rate
5 ==> ATM frame relay
6 ==> standard ABR
7 ==> foresight ABR
Note that this is used by PXM card, SV+ doesn't need to set it,
if not set in the connection setup request, it'll be defaulted
to CBR type for CESM.
Also to make it compatible with existing AUSM MIB definition,
value 3 is not used.
The following types are being added for PNNI support
and are based on UNI 4.0.
cbr1 (21) - CBR.1
vbr1rt (22) - Real time VBR.1
vbr2rt (23) - Real time VBR.2
vbr3rt (24) - Real time VBR.3
vbr1nrt(25) - Non Real time VBR.1
vbr2nrt(26) - Non Real time VBR.2
vbr3nrt(27) - Non Real time VBR.3
ubr1 (28) - UBR.1
ubr2 (29) - UBR.2
stdabr (30) - TM 4.0 compliant standard ABR
cbr2 (31) - CBR.2
cbr3 (32) - CBR.3
Note that for CESM, the only valid connection type for PNNI
support is cbr1(21). Other enumerations have been added
for the sake of consistency across Narrow-Band service
modules.rw Enumeration .1.3.6.1.4.1.351.110.5.3.2.1.1.1.35 |
cesRoutingPriorityThis is used by PXM to determine how important
this connection is when selecting connections to routerw INTEGER .1.3.6.1.4.1.351.110.5.3.2.1.1.1.36 |
cesMaxCostMaximum allowed cost. It is related to Cost Based Routing.
This is used by PXM so that it won't choose a path with
a cost greater than this configured level. This is not
necessary to be provided in the connection setup request,
if not provided, the default value 255 will be used.
When used with PAR controller the valid range is 1..65535 and
the default value is 255.
When used with PNNI controller the valid range is 1..2147483647
and the default value is 2147483647.rw INTEGER .1.3.6.1.4.1.351.110.5.3.2.1.1.1.37 |
cesRestrictTrunkTypeRestricted trunk type for routing, used by PXM. It
specifies that the connection either cannot be routed over
satelite trunks, or terrestrial trunks, or it can be on
any type of trunk. It is not necessary to be provide in
the connection setup request, the default value is
noresriction(1).rw Enumeration .1.3.6.1.4.1.351.110.5.3.2.1.1.1.38 |
cesConnPCRPeak cell rate,if not provided in the connection setup
request,it will be computed as follows,
For CESM-8T1/E1 - N * 64 Kbps , where N = Number of timeslots assigned
to this channel.
For CESM-T3, the value is 44736 Kbps
For CESM-E3, the value is 34368 Kbps.rw INTEGER .1.3.6.1.4.1.351.110.5.3.2.1.1.1.39 |
cesConnMCRMinimum cell rate,if not provided in the connection setup
request,it will be computed as follows,
For CESM-8T1/E1 - N * 64 Kbps , where N = Number of timeslots assigned
to this channel.
For CESM-T3, the value is 44736 Kbps
For CESM-E3, the value is 34368 Kbps.rw INTEGER .1.3.6.1.4.1.351.110.5.3.2.1.1.1.40 |
cesConnPercentUtilThis is the expected long-term utilization of the
channel by theis end-point.
For CESM-8T1/E1/T3/E3 , the value is 100%rw INTEGER .1.3.6.1.4.1.351.110.5.3.2.1.1.1.41 |
cesmConnRemotePCRPeak cell rate of the other end, if not set in MGX, will be
derived from the end point parameterrw INTEGER .1.3.6.1.4.1.351.110.5.3.2.1.1.1.42 |
cesmConnRemoteMCRMinimum cell rate of the other end, if not set in MGX, will be
derived from the end point parameterrw INTEGER .1.3.6.1.4.1.351.110.5.3.2.1.1.1.43 |
cesmConnRemotePercentUtilThis is the expected long-term utilization of the
channel by the other end-point.rw INTEGER .1.3.6.1.4.1.351.110.5.3.2.1.1.1.44 |
cesmConnForeSightEnableThis object is used by the controller(PAR/PNNI/TAG) to set up
the Qbin for the connection.
This is notapplicable to CESM-8T1/E1/T3/E3.rw Enumeration .1.3.6.1.4.1.351.110.5.3.2.1.1.1.45 |
cesmConnFGCRAEnableenables/disables Frame based GCRA (early packet discard).
This is not applicable to CESM-8T1/E1/T3/E3.rw Enumeration .1.3.6.1.4.1.351.110.5.3.2.1.1.1.46 |
cesmChanRerouteThis is used by the administrator to trigger the re-routing
of the connection. The rerouting takes effect, when this object
is set to true(1). When set to false (2), no action is taken.
A get on this object always returns false (2).
This object is not applicable to MGX Release 1.x.rw Enumeration .1.3.6.1.4.1.351.110.5.3.2.1.1.1.47 |
cesmConnAdminStatusThis object specifies channel admin status.
This object is not applicable to MGX Release 1.x.rw Enumeration .1.3.6.1.4.1.351.110.5.3.2.1.1.1.48 |
cesmChanNumNextAvailableThis variable contains the next unused channel number of the possible
248. This number can be used in channel config table.
cesChanNumNextAvailable gets updated whenever this number is used to
create a new logical channel. Value 0 for this variable indicates that
no more channels are available. In CESM 8-port card), the maximum
number of values for this variable is 248 (i.e. 32 ..279).
Only applicable to CESM-8T1/E1/T3/E3.ro INTEGER .1.3.6.1.4.1.351.110.5.3.2.1.2 |
cesmChanCntGrp OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.5.3.2.2 |
cesmChanCntGrpTableThe config table is for logical channel interface
there are 4 entries for 4 DS1s in case of CESM-4P
In case of CESM-8P it can have 352 entries. SEQUENCE OF CesmChanCntGrpEntry .1.3.6.1.4.1.351.110.5.3.2.2.1 |
cesmChanCntGrpEntryAn entry for logical channel CesmChanCntGrpEntry .1.3.6.1.4.1.351.110.5.3.2.2.1.1 |
cesCntChanNumRefers to the channel Number
16 - 19 for CESM-4P
32 - 279 for CESM-8t1e1
32 for CESM-T3/E3ro INTEGER .1.3.6.1.4.1.351.110.5.3.2.2.1.1.1 |
cesChanStateThis variable indicates the connection status
failed(4) is added to distinguish between alarm (when the connection
segment is not actually broken) and failed(when the segment is actually
broken). This is applicable only to the PNNI environment.ro Enumeration .1.3.6.1.4.1.351.110.5.3.2.2.1.1.2 |
cesXmtATMStateThis variable indicates the transmit state of channel
on the ATM side (towards the network).ro Enumeration .1.3.6.1.4.1.351.110.5.3.2.2.1.1.3 |
cesRcvATMStateThis variable indicates the receive state of channel
on the ATM side (from the network).ro Enumeration .1.3.6.1.4.1.351.110.5.3.2.2.1.1.4 |
cesCellLossStatusWhen cells are lost for the CellLossIntegrationPeriod the value
is set to loss ( 2). when cells are no longer lost, the value is
set to noLoss(1).ro Enumeration .1.3.6.1.4.1.351.110.5.3.2.2.1.1.5 |
cesReassCellsThe number of cells played out to T1/E1/T3E3 interface. It
excludes cells that were discarded for any reason.ro Counter .1.3.6.1.4.1.351.110.5.3.2.2.1.1.6 |
cesGenCellsThe number of cells generated from T1/E1/T3E3 interface and
sent towards network.ro Counter .1.3.6.1.4.1.351.110.5.3.2.2.1.1.7 |
cesHdrErrorsThe number of AAL-1 header errors detected and possibly
corrected. Header errors include correctable and uncor-
rectable CRC, plus bad parity.ro Counter .1.3.6.1.4.1.351.110.5.3.2.2.1.1.8 |
cesPointerReframesThe number of events in which the AAL1 reassembler found
that an SDT pointer is not where it is expected and the
and the pointer must be reacquired. Not supported in
cesm8P due limitation in AAL1 SAR.
Not applicable for CESM-4T1/E1 and CESM-T3/E3ro Counter .1.3.6.1.4.1.351.110.5.3.2.2.1.1.9 |
cesLostCellsThe number of cells lost in egress direction due to
AAL 1 header errors and missing cells.ro Counter .1.3.6.1.4.1.351.110.5.3.2.2.1.1.10 |
cesBufUnderflowsThe number of buffer underflows in Egress direction
Not supported in cesm8P due limitation in AAL1 SAR.ro Counter .1.3.6.1.4.1.351.110.5.3.2.2.1.1.11 |
cesBufOverflowsThe number of buffer overflows in Egress direction
Not supported in cesm8P due limitation in AAL1 SAR.ro Counter .1.3.6.1.4.1.351.110.5.3.2.2.1.1.12 |
cesIngrDiscardedBytesThe number of bytes discarded due to shelf alarm in ingress
direction from port data. Not supported in CESM-8P.ro Counter .1.3.6.1.4.1.351.110.5.3.2.2.1.1.13 |
cesUflowInsCellsThe Number of All 1's cells inserted in case of Egress Buffer
Underflow
Not supported in CESM-8P.ro Counter .1.3.6.1.4.1.351.110.5.3.2.2.1.1.14 |
cesOflowDropBytesThe Number of bytes discarded in Egress direction because of
Egress buffer overflow
Not supported in CESM-8P.ro Counter .1.3.6.1.4.1.351.110.5.3.2.2.1.1.15 |
cesCellSeqMismatchCntThe Number of times SAR received a valid out of sequence AAL-1
cell from CellBus.ro Counter .1.3.6.1.4.1.351.110.5.3.2.2.1.1.16 |
counterClrButtonwriting a value of 2 resets all the countersrw Enumeration .1.3.6.1.4.1.351.110.5.3.2.2.1.1.17 |
cesChanSecUptimeThe Number of seconds channel is in service
only applicable for CESM-8Pro Counter .1.3.6.1.4.1.351.110.5.3.2.2.1.1.18 |
cesChanSignalingStatusThis variable indicates the connection signalling status
Connection will be in Idle suppression mode if it in on-hook.
Not applicable for T3E3 and CESM-4P.ro Enumeration .1.3.6.1.4.1.351.110.5.3.2.2.1.1.19 |
cesChanStatusBitMapThis variable indicates the consolidated bit map of the channel alarm
state.
Individual bit positions are as defined below.
Bit position Fail/Alarm Reason
0 Alarm Reserved
1 Alarm n/w side AIS/RDI Rx
2 Fail Conditioned(A bit from n/w)
3 Alarm Reserved
4 Fail Reserved
5 Fail Reserved
6 Alarm Reserved
7 Alarm Cell loss alarm
Fail bitmap mask : 0x34
Alarm bitmap mask: 0xCB
This object is not applicable to MGX Release 1.x.ro INTEGER (0..'ff'h) .1.3.6.1.4.1.351.110.5.3.2.2.1.1.20 |
cesmEndPtMapGrp OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.5.3.3 |
cesmEndPtMapGrpTableThere are 248 entries and port num will uniquely
identify a row.
For CESM-8T1/E1 , only 248 ports are possible.
For CESM-T3/E3, only one port is possible. SEQUENCE OF CesmEndPtMapGrpEntry .1.3.6.1.4.1.351.110.5.3.3.1 |
cesmEndPtMapGrpEntryAn entry for cesmEndPtMapGrpEntry. CesmEndPtMapGrpEntry .1.3.6.1.4.1.351.110.5.3.3.1.1 |
cesEndPortNumRefers to the logical port index
CESM-8E1 supports 248 ports.
CESM-8T1 supports 192 ports.
CESM-T3/E3 supports only one port.ro INTEGER .1.3.6.1.4.1.351.110.5.3.3.1.1.1 |
cesEndChanNumLogical connection number for above cesEndPortNumro INTEGER .1.3.6.1.4.1.351.110.5.3.3.1.1.2 |
cesEndLineNumRefers to the physical line index
In case T3 only one line will be supported.ro INTEGER .1.3.6.1.4.1.351.110.5.3.3.1.1.3 |
vismPortCnfGrp OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.5.5.2.1 |
vismPortCnfGrpTablePort configuration table for the virtual port.
Only one entry is allowed in this table. SEQUENCE OF VismPortCnfGrpEntry .1.3.6.1.4.1.351.110.5.5.2.1.1 |
vismPortCnfGrpEntryAn entry for logical port. VismPortCnfGrpEntry .1.3.6.1.4.1.351.110.5.5.2.1.1.1 |
vismPortNumThis is a logical port number. If PXM1 is the PXM
used on the shelf this object should be set to 1.
For PXM1E this object should be set to 255.
.ro INTEGER .1.3.6.1.4.1.351.110.5.5.2.1.1.1.1 |
vismPortRowStatusTo add, del or modify a port.
To add the port, this object has to be set to add, values
for other objects should not be specififed (refer to Note 1).
VISM will choose default values for all other objects (Note 1).
Once added, the value mod is returned for a GET.
To delete the port, this object has to be set to del. The port
can be deleted only after deleting all the connections and the
resource partition.
Note 1: From VISM 2.x release onwards, vismPortRowStatus will be
set to mod after adding the VISM port. Also, vismPortSpeed can
be specified optionaly when VISM port is added.rw Enumeration .1.3.6.1.4.1.351.110.5.5.2.1.1.1.2 |
vismPortLineNumThis represents the line number to which this port is associated.
Since the network port is not associated with any line,
line number 0 is returned on a GET.
This object is currently not used and SET is not allowed on this
object.rw INTEGER .1.3.6.1.4.1.351.110.5.5.2.1.1.1.3 |
vismPortTypeThe value of this object is always set to voIP. It indicates that
it is the network port. The same value is used even when VISM
supports VoAAL1 or VoAAL2.
The value userPort is not applicable for VISM.
SET is not allowed on this object.rw Enumeration .1.3.6.1.4.1.351.110.5.5.2.1.1.1.4 |
vismPortDs0ConfigBitMapThis respesents the bit map of DS0s which is used to create
this port. Bit 0 represents DS0-1.
Since this object is not applicable to the network port,
value 0 is returned on a GET.
SET is not allowed on this object.rw INTEGER (0..'ffffff'h) .1.3.6.1.4.1.351.110.5.5.2.1.1.1.5 |
vismPortSpeedThe speed of the port in cells per second.
It is used by VISM card to advertise virtual port bandwidth to
the controller, SVC and PVC connection admission control and
aggregate traffic clipping.
This object can be modified only when there is no existing
resource partition on the port.
Changed from read-only to read-write from VISM2.x release.rw INTEGER .1.3.6.1.4.1.351.110.5.5.2.1.1.1.6 |
vismPortStateThis object indicates the state of the port.ro Enumeration .1.3.6.1.4.1.351.110.5.5.2.1.1.1.7 |
vismPortResPartCnfGrp OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.5.5.2.2 |
vismPortResPartCnfGrpTableThis table contains the configuration of port resource
partition.
Currently this table contains a single row. SEQUENCE OF VismPortResPartCnfGrpEntry .1.3.6.1.4.1.351.110.5.5.2.2.1 |
vismPortResPartCnfGrpEntryAn entry for port resource partition. VismPortResPartCnfGrpEntry .1.3.6.1.4.1.351.110.5.5.2.2.1.1 |
vismResPartPortNumThis is the logical port number, the index to this table.
If PXM1 is the PXM used on the shelf this object should
be set to 1. For PXM1E this object should be set to 255.ro INTEGER .1.3.6.1.4.1.351.110.5.5.2.2.1.1.1 |
vismResPartCtrlrNumThis is index for controller using the port.
In MGX release 1.0, the value par should be used.
In MGX release 2.0, the value pnni should be used.ro Enumeration .1.3.6.1.4.1.351.110.5.5.2.2.1.1.2 |
vismResPartRowStatusThis will add, delete or modify the partition.
In MGX Release1.0:
To add an entry, this object should be set to add, value
for other objects should not be specified. VISM will choose
default values for all other objects.
In MGX Release2.0:
To add an entry, this object should be set to add, value
for vismResPartCtrlrID may be specified. VISM will choose
default values for all other objects.
Currently the value mod is not supported.
To delete an entry, this object has to be set to del. The resource
partition can be deleted only after deleting all the connections
(LCNs).rw Enumeration .1.3.6.1.4.1.351.110.5.5.2.2.1.1.3 |
vismResPartNumOfLcnAvailThis represents number of LCNs available for this
controller and this port. The default value for this
object is chosen based on vismMode :
default value in voipSwitching mode - 3
default value in aal2Trunking mode - 72
Currently SET is not allowed on this object.
From vism2.0.3 release onwards as there is no
concept of modes the number of lcns will
be set to maximum of number of lcns supported.rw INTEGER .1.3.6.1.4.1.351.110.5.5.2.2.1.1.4 |
vismResPartLcnLowThis represents low end of reserved LCN.
Currently SET is not allowed on this object.rw INTEGER .1.3.6.1.4.1.351.110.5.5.2.2.1.1.5 |
vismResPartLcnHighThis represents high end of reserved LCN.
Currently SET is not allowed on this object.rw INTEGER .1.3.6.1.4.1.351.110.5.5.2.2.1.1.6 |
vismResPartIngrPctBWThe percentage of total ingress bandwidth reserved.
Since we have only one LCN for VoIP, the value is 100.
Currently SET is not allowed on this object.
From vism 2.0.3 release onwards since the mode will be
gone this object will be writable.rw INTEGER .1.3.6.1.4.1.351.110.5.5.2.2.1.1.7 |
vismResPartEgrPctBWThe percentage of total egress bandwidth reserved
Since we have only one LCN for VoIP, the value is 100.
Currently SET is not allowed on this object.
From vism 2.0.3 release onwards since the mode will be
gone this object will be writable.rw INTEGER .1.3.6.1.4.1.351.110.5.5.2.2.1.1.8 |
vismResPartCtrlrIDThis is the controller identifier of the PNNI controller.rw INTEGER .1.3.6.1.4.1.351.110.5.5.2.2.1.1.9 |
vismChanCnfGrpTableThe channel config table for voice traffic. SEQUENCE OF VismChanCnfGrpEntry .1.3.6.1.4.1.351.110.5.5.3.1.1 |
vismChanCnfGrpEntryAn entry for each voice channel. VismChanCnfGrpEntry .1.3.6.1.4.1.351.110.5.5.3.1.1.1 |
vismCnfChanNumLogical Channel Number for the PVC.ro INTEGER .1.3.6.1.4.1.351.110.5.5.3.1.1.1.1 |
vismChanRowStatusAn entry is created by setting this object to add. Once the entry
is added, the value mod is returned for successive GETs. The value
mod is used to modify an existing entry. An entry is deleted by
setting this object to del.
Setting this object to outOfService takes the channel out of service
or brings the channel 'down'. The channel can be brought 'up' again
by setting the object to mod.
If there is redundant configuration for the channel, an active
channel can be deleted only after locking the channel.rw Enumeration .1.3.6.1.4.1.351.110.5.5.3.1.1.1.2 |
vismChanPortNumThis refers to the virtual port between VISM and PXM. This number
is defaulted to the appropriate number for the shelf. (1 for PXM1
and 255 for PXM1E)rw INTEGER .1.3.6.1.4.1.351.110.5.5.3.1.1.1.3 |
vismChanLocRmtLpbkStateLoopback on cellbus in egress direction.
This variable enables or disables the remote loopback for each channel.
When you enable this option on a connection (channel) then all the
cells that are coming from the network side would be looped back
toward the network and all the frames coming from the user side
would be dropped.rw Enumeration .1.3.6.1.4.1.351.110.5.5.3.1.1.1.4 |
vismChanTestTypeThis is the type of the test.
1 = Test Continuity
2 = Test Delay
3 = No test
notest is meant for GET only.
While doing a SET on this object, the SET request should contain
only this parameter and no other MIB objects in this table.rw Enumeration .1.3.6.1.4.1.351.110.5.5.3.1.1.1.5 |
vismChanTestStateThis shows the state of the test.ro Enumeration .1.3.6.1.4.1.351.110.5.5.3.1.1.1.6 |
vismChanRTDResultThis is round trip delay in milliseconds.ro INTEGER .1.3.6.1.4.1.351.110.5.5.3.1.1.1.7 |
vismChanPvcTypePVC type. In VISM 1.0 pvc type VoIP was supported. It has been
deprecated in the current release.
This is a mandatory parameter when adding a PVC.rw Enumeration .1.3.6.1.4.1.351.110.5.5.3.1.1.1.8 |
vismChanConnTypeConnection type.rw Enumeration .1.3.6.1.4.1.351.110.5.5.3.1.1.1.9 |
vismLocalVpiThis VPI together with the local VCI and NSAP represents the
local end point in this connection.
GET on this object returns value=0.ro INTEGER .1.3.6.1.4.1.351.110.5.5.3.1.1.1.10 |
vismLocalVciThis VCI together with the local VPI and NSAP represents the
local end point in this connection.
GET on this object returns the vismCnfChanNum or LCN.ro INTEGER .1.3.6.1.4.1.351.110.5.5.3.1.1.1.11 |
vismLocalNSAPThis NSAP is 20 bytes binary, among these 20 bytes: 13 bytes
as prefix(node name), 2 bytes for Cisco ID, 1 byte rsvd, 3 bytes for
logical interface: slot (1 byte) and port number (2 bytes),
the last byte is for SEL.rw OCTET STRING .1.3.6.1.4.1.351.110.5.5.3.1.1.1.12 |
vismRemoteVpiThis VPI together with the remote VCI and NSAP represents the
remote end point in this connection.
This parameter is required only if vismMastership is set to master.rw INTEGER .1.3.6.1.4.1.351.110.5.5.3.1.1.1.13 |
vismRemoteVciThis VCI together with the remote VPI and NSAP represents the
remote end point in this connection.
This parameter is required only if vismMastership is set to master.rw INTEGER .1.3.6.1.4.1.351.110.5.5.3.1.1.1.14 |
vismRemoteNSAPThis NSAP is 20 bytes binary, among these 20 bytes: 13 bytes
as prefix, 2 bytes for Cisco ID, 1 byte rsvd, 3 bytes for
logical interface: slot (1 byte) and port number (2 bytes),
the last byte is for SEL.
This parameter is required only if vismMastership is set to master.
This object contains the NSAP address of the cross-connect (PXM/AUSM).rw OCTET STRING .1.3.6.1.4.1.351.110.5.5.3.1.1.1.15 |
vismMastershipThis is used by PXM to determine if this end point is
master or slave.
For VoIP channel, the value is master (1).rw Enumeration .1.3.6.1.4.1.351.110.5.5.3.1.1.1.16 |
vismVpcFlagThis is used by PXM to identify the connection type.rw Enumeration .1.3.6.1.4.1.351.110.5.5.3.1.1.1.17 |
vismConnServiceTypeThis specifies the class of service or service type
1 ==> Constant Bit Rate
2 ==> Variable Bit Rate 1 (Real Time)
Although, VISM does not do any kind of traffic shaping,
the PVC has to be specified as vbr-rt for PXM to treat
the connection as a VBR1 connection.
Variable Bit Rate is not currently supported.
3 ==> Variable Bit Rate 1 (non real time)
VISM has to support all these kinds of traffic rates from
Indiana release onwards
The service type of the connection cannot be modified once
the PVC is added.
4 ==> Variable Bit Rate 3 (Real Time)
Although, VISM does not do any kind of traffic shaping,
the PVC has to be specified as vbr3-rt for PXM to treat
the connection as a VBR3 connection.
Variable Bit Rate is not currently supported.
5 ==> Variable Bit Rate 2 (Real Time)
Although, VISM does not do any kind of traffic shaping,
the PVC has to be specified as vbr2-rt for PXM to treat
the connection as a VBR2 connection.
Variable Bit Rate is not currently supported.
6 ==> Variable Bit Rate 2 (non real time)
VISM has to support all these kinds of traffic rates from
Indiana release onwards
The service type of the connection cannot be modified once
the PVC is added.
7 ==> Variable Bit Rate 3 (non real time)
VISM has to support all these kinds of traffic rates from
Indiana release onwards
The service type of the connection cannot be modified once
the PVC is added.rw Enumeration .1.3.6.1.4.1.351.110.5.5.3.1.1.1.18 |
vismRoutingPriorityThis is used by PXM to determine how important
this connection is when selecting connections to route.rw INTEGER .1.3.6.1.4.1.351.110.5.5.3.1.1.1.19 |
vismMaxCostMaximum allowed cost. It is related to Cost Based Routing.
This is used by PXM so that it won't choose a path with
a cost greater than this configured level. This is not
necessary to be provided in the connection setup request,
if not provided, the default value 255 will be used.
When used with PAR controller the valid range is 1..65535 and the
default value is 255.
When used with PNNI controller the valid range is 1..2147483647 and
the default value is 2147483647.rw INTEGER .1.3.6.1.4.1.351.110.5.5.3.1.1.1.20 |
vismRestrictTrunkTypeRestricted trunk type for routing, used by PXM. It
specifies that the connection either cannot be routed over
satelite trunks, or terrestrial trunks, or it can be on
any type of trunk. It is not necessary to be provide in
the connection setup request, the default value is
noresriction(1).rw Enumeration .1.3.6.1.4.1.351.110.5.5.3.1.1.1.21 |
vismConnPCRThis indicates bandwidth(Peak Cell Rate) in cells per second
from the local end i.e in the ingress direction of the PVC.
For a VoIP bearer PVC, the max value is 75600 cps.
For a VoIP control PVC, the max value is 24400 cps.
For AAL2 PVCs, the PCR to be specified has to be computed based on:
a) The no. of channels multiplexed on an AAL2 PVC
b) The Codec (Compression Algorithm) used.
c) The VAD factor
d) Partial fill factor.
For a AAL2 bearer PVC, the max value is 60,000 cps on E1 card and
50,000 cps on T1 card.
For a signaling PVC, the max value is 400 cps.
This is a mandatory parameter when adding a PVC. Hence a default
value is not applicable. This parameter can not be changed when
there are calls active on the PVC.
From Indiana release onwards
For a VOIP bearer PVC the max allowed value is 80000
For a VOIP control PVC the max allowed value is 20000
increased as we will allow 248 endpoints.
For Aal2 the values remain the same 50000/60000.
For vbr connections the minimum value of PCR is 15.rw INTEGER .1.3.6.1.4.1.351.110.5.5.3.1.1.1.22 |
vismConnPercentUtilThis is the expected long-term utilization of the
channel by this end-point.
Currently only 100 is allowed.rw INTEGER .1.3.6.1.4.1.351.110.5.5.3.1.1.1.23 |
vismConnRemotePCRThis indicates bandwidth(Peak Cell Rate) from the other end i.e
in the egress direction of the PVC. This value is expressed in
units of cells per second.
If not set, will be set to the same as local end PCR.
From Indiana release onwards
The range of this object is 1..100000rw INTEGER .1.3.6.1.4.1.351.110.5.5.3.1.1.1.24 |
vismConnRemotePercentUtilThis is the expected long-term utilization of the
channel by the other end-point.
Currently only 100 is allowed.rw INTEGER .1.3.6.1.4.1.351.110.5.5.3.1.1.1.25 |
vismChanProtectionThis object is used to configure a PVC protection group (or redundant group)
with the PVCs protecting each other. Currently only two PVCs are supported
in a protection group. One of them is primary and the other one is secondary.
This is intended for PVCs designated to carry control traffic and needs to
be protected. (However the same PVC may also be used to carry VoIP bearer
traffic or other traffic).
Channels that are protected share the following characteristics:
1. They are monitored for their health (including emission of traps in
case of state changes)
2. An active channel is protected by another protected channel which is
standby. This means when an active channel fails, switchover to another
channel will happen if one is available.
3. It is also possible to do a forced switchover (through locking).
Even in the case of forced switchover, switchover to another
channel, which is in standby, will happen.
4. Channels may be locked to force switchover and/or to take the
channel out of service in a graceful fashion.
This object takes the default value of unprotected during the creation of the
table entry. Once the primary and secondary channels have been created as
unprotected channels, they can be protected by doing a SET on the primary
channel by specifying the vismChanProtection as protected and by specifying the
vismChanFallbackLcn as the LCN number of the secondary channel.
The sequence of operations for setting up the protection group is:
step 1: Add primary channel as unprotected
step 2: Add secondary channel as unprotected. The PCR value for the secondary
should be the same as that of the primary.
step 3: Do a SET on the primary channel with vismChanProtection set to protected
and vismChanFallbackLcn set to the LCN number of the secondary channel.
This operation sets-up the protection group. The primary channel becomes
active and the secondary channel becomes standby.
Please note that all the cac releated parameters for the both the PVCs
in the protecting group should be same. In other words the vismChanCacMaster
vismChanCarrierLossPolicy, vismChanCacRejectionPolicy, VAD tolerance etc..
should have the same value for the PVCs that are protecting each other, else
the set request to protect two channels will be rejected.
Once the protection group is setup, if the active channel fails, it automatically
switches over to the standby. The standby channel then becomes active.
The channels can be removed from the protection group by setting this object to
unprotected.
Deletion of a protected channel is not allowed. Channels have to be removed from
the protection group first before deleting. The sequence of operations for deleting
protected channels is:
step 1: Remove the channels from the protection group by setting
vismChanProtection to unprotected.
step 2: Delete secondary channel.
step 3: Delete primary channel.rw Enumeration .1.3.6.1.4.1.351.110.5.5.3.1.1.1.26 |
vismChanPreferenceThis object is used to identify a PVC as primary or secondary.
The primary PVC should be added before the secondary. Similarly
secondary should be deleted before deleting the primary.
When the protection group is setup, the primary becomes active and secondary
becomes standby. The distinction of primary and secondary is meaningful only
if the PVC is protected.
This is a mandatory parameter when adding a PVC.rw Enumeration .1.3.6.1.4.1.351.110.5.5.3.1.1.1.27 |
vismChanActivityStateIndicates whether the PVC is currently used to carry IP traffic or not,
and whether it has failed.
The possible states are:
active - Channel is healthy and is currently designated to carry IP
traffic. A channel can only be active if it is also unlocked.
standby - Channel is healthy but not designated to carry IP traffic.
Switchover to this channel is allowed.
failed - Channel is unable to carry any traffic.
unknown - Channel is unprotected and hence health of the channel is not
monitored.
The default value upon creation of the row will be standby for a
protected channel and unknown for an unprotected channel. VISM may then
transition a protected channel to active if it determines that this
channel should be the one carrying the traffic.ro Enumeration .1.3.6.1.4.1.351.110.5.5.3.1.1.1.28 |
vismChanLockingStateThis object is used to control the switchover of protected channels.
The possible values are:
unlock - Transition state to unlock. A channel which is in lock state
has to be brought to unlock state for it to be available for
switchover.
Whether a switchover to a channel is allowed or not is
dependent on both vismChanActivityState and
vismChanLockingState. A switchover is allowed if its
vismChanActivityState is standby and its vismChanLockingState
is unlock.
Changing the vismChanLockingState to unlock does not cause a
change in the vismChanActivityState.
A channel which is in unlock state may carry traffic
depending on its activity state (active or standby).
lock - Transition state to lock. If the activity state is active,
it transitions to standby and a switchover occurs to another
channel which is standby and unlocked.
When a channel is in lock state, switchover to this channel
is not allowed.
A channel which is in lock state, is always in either standby
or failed state. Hence it will not carry any traffic.
Switchover to a channel which is in lock state is not allowed.
The default value of this object is unlock. It can be set to locked to
force a switchover and/or to perform maintenance operations related to
that channel.
A channel that is unprotected will always be in unlock state. It can
not be set to lock state.rw Enumeration .1.3.6.1.4.1.351.110.5.5.3.1.1.1.29 |
vismChanScrIngressThis object defines the SCR (Sustained Cell Rate) for the PVC.
SCR is used for vbr connection types only. Although, based on the
value of SCR, any kind of traffic shaping is not done on the VISM
card, this value is useful for setting up the parameters for the
end-to-end PVC.
This value is expressed in units of cells per second.
This object defines the SCR value for the ingress direction of
the PVC.
From Indiana release onwards
For a VOIP bearer PVC the max value is 80000
For a VOIP control PVC the max value is 20000
increased as we will allow 248 endpoints.
For Aal2 the values remain the same (50000/60000).
If the user provides a value that is greater than vismConnPCR
then the SET request will be rejected.
For vbr connections the allowed range of values of SCR is from
15 - PCR.rw INTEGER .1.3.6.1.4.1.351.110.5.5.3.1.1.1.30 |
vismChanMbsIngressThis object defines the MBS (Max. Burst Size) in cells per second.
This object is meaningful for VBR connections only.
This object defines the MBS value for the ingress direction of
the PVC.
The MBS value cannot be greater than 10 times vismChanSCRIngress value.rw INTEGER .1.3.6.1.4.1.351.110.5.5.3.1.1.1.31 |
vismChanClrIngressThis object defines the CLR (Cell Loss Ratio) for the PVC.
This field is also meaningful for VBR connections only.
This object defines the CLR value for the ingress direction of
the PVC.rw INTEGER .1.3.6.1.4.1.351.110.5.5.3.1.1.1.32 |
vismChanCdvtThis object defines the CDVT (Cell Delay Variation Tolerance) for the
connection. CDVT is useful for detemining the playout buffer size in
the DSPs. This object is applicable only in AAL1 adaptation. For AAL2,
the equivalent of this parameter, known as PDVT (Packet Delay Variation
Tolerance) is internally derived.rw INTEGER .1.3.6.1.4.1.351.110.5.5.3.1.1.1.33 |
vismConnPCREgressThis object defines the PCR (Peak Cell Rate) for the PVC.
PCR is applicable to all connection service types ie. CBR, RT-VBR
and nRT-VBR.
This value is expressed in units of cells per second.
This object defines the PCR value for the egress direction of
the PVC.
This is a mandatory parameter when adding a PVC.rw INTEGER .1.3.6.1.4.1.351.110.5.5.3.1.1.1.34 |
vismChanScrEgressThis object defines the SCR (Sustained Cell Rate) for the PVC.
SCR is used for vbr connection types only. Although, based on the
value of SCR, any kind of traffic shaping is not done on the VISM
card, this value is useful for setting up the parameters for the
end-to-end PVC.
This value is expressed in units of cells per second.
This object defines the SCR value for the egress direction of
the PVC.
From Indiana release onwards the range of this
object has been increased to 100000.rw INTEGER .1.3.6.1.4.1.351.110.5.5.3.1.1.1.35 |
vismChanMbsEgressThis object defines the MBS (Max. Burst Size) in cells per second.
This object is meaningful for VBR connections only.
This object defines the MBS value for the egress direction of
the PVC.rw INTEGER .1.3.6.1.4.1.351.110.5.5.3.1.1.1.36 |
vismChanClrEgressThis object defines the CLR (Cell Loss Ratio) for the PVC.
This field is also meaningful for VBR connections only.
This object defines the MBS value for the egress direction of
the PVC.rw INTEGER .1.3.6.1.4.1.351.110.5.5.3.1.1.1.37 |
vismChanApplicationThis object defines the application that the LCN is used for.
There are 4 types of PVCs known so far:
1 - Control PVC used for carrying control traffic only (SGCP packets)
2 - bearer PVC, used for carrying voice payload traffic only
3 - signaling PVC, used for carrying the signaling protocol messages
This is a mandatory parameter when adding a PVC.rw Enumeration .1.3.6.1.4.1.351.110.5.5.3.1.1.1.38 |
vismChanFallbackLcnThis object defines the LCN to be used as a fallback mechanism,
in case the primary PVC fails. This is applicable if the PVC is
configured for redundancy. The redundancy is applicable for both
applications i.e control PVC and bearer PVC.
This object is applicable only if the vismChanProtection is set to
protected. It is mandatory if the PVC is protected.rw INTEGER .1.3.6.1.4.1.351.110.5.5.3.1.1.1.39 |
vismChanRerouteThis is used by the administrator to trigger the re-routing
of the connection. The rerouting takes effect, when this object
is set to true(1). When set to false (2), no action is taken.
A get on this object always returns false (2).rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.351.110.5.5.3.1.1.1.40 |
vismFarEndAddressTypeThe address type can be one of five types: NSAP, E164, GWID, notapplicable
or unspecified. It determines which object contains the scope for the VCCI,
i.e. whether the VCCI needs to be unique relative to NSAP, E164 address or GWID.
In case of nsap, object vismFarEndNSAPAddress contains the address. In case
of e164, object vismFarEndE164Address contains the address. In case of gwid,
object vismFarEndGWIDAddress contains the address. In case this object is
set to notapplicable, no valid addresses are required and no
validation of VCCI uniqueness for a remote address is performed.
In case this object is set to unspecified, no valid addresses are
required but VCCI needs to be unique.
While this object is writeable, it is recommended not to change the
value of this object once it has been created. However, upon
modification to any value other than notapplicable, it will be ensured
that the resulting combination of VCCI and remote address is unique.
Requests that would result in a non-unique combination will be rejected.
If the vismFarEndAddressType is one of nsap, e164 or gwid, the far end
address has to be specified.rw Enumeration .1.3.6.1.4.1.351.110.5.5.3.1.1.1.41 |
vismFarEndE164AddressThe E.164 address of the far end peer. The address is expressed
as decimal numbers with up to 15 digits. If the vismFarEndAddressType
is different from e164, this object is not applicable and it should be
ignored.
This object serves as the scope for VCCI identifiers (vismVCCI) if
vismFarEndAddressType is equal to e164. In that case, the combination
of (vismFarEndE164Address, vismVCCI) will always be unique for any given
agent. It thus constitutes a label denoting the scope for a VCCI
address space; it has no purpose otherwise.
While this object is writeable, it is recommended not to change the
value of this object once it has been created. However, upon
modification, it will be ensured that the resulting combination of
VCCI and remote E164 address is unique (as long as the remote address
type is E164). Requests that would result in a non-unique combination
will be rejected. Beyond this, there are no other integrity constraints
that will be enforced for this object. This includes network-level
consistency with the actual address of the remote peer.
The value of this object cannot be modified when there are active
calls on this PVC. The valid characters allowed are '0..9'.rw DisplayString .1.3.6.1.4.1.351.110.5.5.3.1.1.1.42 |
vismFarEndGWIDAddressThe gateway ID of the far end peer. The address is expressed as ASCII
characters. If the vismFarEndAddressType is different from gwid,
this object is not applicable and it should be ignored.
This object serves as the scope for VCCI identifiers (vismVCCI) if
vismFarEndAddressType is equal to gwid. In that case, the combination
of (vismFarEndGWIDAddress, vismVCCI) will always be unique for any given
agent. It thus constitutes a label denoting the scope for a VCCI
address space; it has no purpose otherwise.
While this object is writeable, it is recommended not to change the
value of this object once it has been created. However, upon
modification, it will be ensured that the resulting combination of
VCCI and far end GWID address is unique (as long as the vismFarEndAddress
type is GWID). Requests that would result in a non-unique combination
will be rejected. Beyond this, there are no other integrity constraints
that will be enforced for this object. This includes network-level
consistency with the actual address of the remote peer.
The value of this object cannot be modified when there are active
calls on this PVC. All ASCII characters are allowed by this object.rw DisplayString .1.3.6.1.4.1.351.110.5.5.3.1.1.1.43 |
vismFarEndNSAPAddressThis object contains the 20 byte NSAP address of the far end peer.
If the vismFarEndAddressType is different from nsap, this object
is not applicable and it should be ignored.
This object serves as the scope for VCCI identifiers (vismVCCI) if
vismFarEndAddressType is equal to nsap. In that case, the
combination of (vismFarEndNSAPAddress, vismVCCI) will always be unique
for any given agent. It thus constitutes a label denoting the scope
for a VCCI address space; it has no purpose otherwise.
While this object is writeable, it is recommended not to change the
value of this object once it has been created. However, upon
modification, it will be ensured that the resulting combination of
VCCI and far end NSAP address is unique (as long as the far end
address type is GWID). Requests that would result in a non-unique
combination will be rejected. Beyond this, there are no other integrity
constraints that will be enforced for this object. This includes
network-level consistency with the actual address of the remote peer.
The value of this object cannot be modified when there are active
calls on this PVC.
When the user adds a connection, by default the value of this object
will be set to vismRemoteNSAP, unless the user specifies a value for
this object. This object is represented as hex (0 .. 9,A .. F)rw OCTET STRING .1.3.6.1.4.1.351.110.5.5.3.1.1.1.44 |
vismVCCIThe VCCI, or Virtual Circuit Connection Identifier, is a
variable that identifies a virtual circuit connection between
two nodes. A virtual circuit connection, or VCC, consists of
one virtual circuit link or a series of concatenated virtual
circuit links. In its most common usage, the value of the VCCI
is unique between the nodes at the extremities of the virtual
circuit connection, but not on a network-wide basis. Hence, its
value needs to be qualified by the ATM addresses of these end
nodes. At one of these end nodes, its value needs to be qualified
by the ATM address of the far-end node. Some applications can
extend this definition to make the VCCI value unique on a network-
wide basis. This is specially possible when VCCIs are administered
from a management system and not locally assigned by a node.
In this MIB, the VCCI serves as a label to be assigned by an
external application. VCCIs need to be unique for a given
remote peer, however, the same VCCI can be reused for different
remote peers. Accordingly, the combination of (remote address, VCCI)
will always be unique for any given agent. This allows a controller
to refer to a VC by the VCCI and remote peer address, in contrast to
VPI/VCI and port. It thus constitutes a convenience feature,
providing an alternative identification scheme for a VC which is
managed by an outside user, such as a management system.
The remote peer address can be specified in NSAP, E.164, or GWID
format, as indicated by the address type (vismRemoteAddressType).
Depending on the address type specified, uniqueness will be relative
to NSAP, E.164 address, or GWID.
While this object is writeable, it is recommended not to change the
value of this object once it has been created. However, upon
modification, it will be ensured that the resulting combination of VCCI
and remote address is unique. Requests that would result in a non-unique
combination will be rejected. Beyond this, there are no other
integrity constraints that will be enforced for this object. This
includes network-level consistency whether the remote peer, or an
external controller, use the same VCCI designation for the VC.rw INTEGER .1.3.6.1.4.1.351.110.5.5.3.1.1.1.45 |
vismConnAdminStatusThis object specifies channel administration status.rw Enumeration .1.3.6.1.4.1.351.110.5.5.3.1.1.1.46 |
vismChanNumNextAvailableThis variable contains the next unused channel number.
When channels are available the range is 32..510.
This number can be used in channel config table.
Value 0 for this variable indicates that
no more channels are available.ro INTEGER .1.3.6.1.4.1.351.110.5.5.3.1.2 |
vismChanCacTableThis table defines the CAC success or failure statistics. CAC
functionality is applied on a per PVC basis for accepting
the new calls in a switching model (i.e when CRCX message is
received from the Call Agent) and when adding a new binding
between a CID and a PVC in the AAL2 trunking application
('addcid' command). In both switching and trunking
models, the CAC functionality is applied for upspeeding the
connections due to the detection of fax/modem tone on a
connection configured with voice compression. SEQUENCE OF VismChanCacEntry .1.3.6.1.4.1.351.110.5.5.3.1.3 |
vismChanCacEntryThis table is used for CAC functions on a PVC. Each entry in this
table corresponds to a PVC, since the CAC functionality is applied
on a per PVC basis. The bandwidth is allocated on a per PVC basis
and the connection admission control is done by comparing the
available bandwidth on a PVC with the required bandwidth as a result
of new connection setup request or upspeed request.
The entries in this table are implicitly created and deleted with
the creation and deletion of entries in vismChanCnfGrpEntry. VismChanCacEntry .1.3.6.1.4.1.351.110.5.5.3.1.3.1 |
vismChanNumThis attribute defines the index for the vismChanCac Table. The LCN
Number is the same as the LCN value used as the index for the
vismChanCnfGrpTable i.e. vismCnfChanNumro INTEGER .1.3.6.1.4.1.351.110.5.5.3.1.3.1.1 |
vismChanCacMasterThis attribute defines whether the PVC is the master end or
slave end. CAC functionality is applied only at the master
end of the PVC. It is not necessary if the PVC end is configured
as the slave end. This is to prevent the glare condition resulting
from the simulatenous allocation of the same bandwidth for different
calls from both the ends.
This parameter is applicable only in the trunking mode.rw Enumeration .1.3.6.1.4.1.351.110.5.5.3.1.3.1.2 |
vismChanCacPassedConsThis attribute defines the count of connections that
passed successfully the CAC function. CAC functionality is
applied either due to
1) The CRCX message sent to VISM from the Call Agent to set
up a new connection OR at the time of 'addcid' command in
AAL2 trunking application.
2) Upspeed request due to Fax/modem tone detection on a
connection configured for compression.
For the initial version of Alabama release, only case 2 is
valid.ro Counter .1.3.6.1.4.1.351.110.5.5.3.1.3.1.3 |
vismChanCacRejectedConsThis attribute defines the count of connections that
got rejected due to CAC function. The CAC rejection was
due to the bandwidth not being available on a given PVC.ro Counter .1.3.6.1.4.1.351.110.5.5.3.1.3.1.4 |
vismChanCacRejectionPolicyThis attribute defines the policy that needs to be applied
once the CAC function rejects the upspeeding of a connection,
due to a fax/modem switch-over request. The applicable options
are
1 - To delete the connection that got rejected by CAC for upspeed
2 - To maintain the connection with the prior compression scheme.
Note that the default value of maintaining the prior encoding
scheme is applicable in the trunking application only since the
connection is not deleted after the fax/modem switchover.
In the case of switching application, the connection is deleted
after the fax/modem switchover.
From Indiana release onwards by default the value
of this object will be unspecified.
If the value of this object is 'unspecified' then the
cac rejection policy as defined in the card
level object vismCacRejectionPolicy will be used,
else the value of this object will be used .
Configuring this object will not have any affect when
card level cac is disabled (vismCacEnable).rw Enumeration .1.3.6.1.4.1.351.110.5.5.3.1.3.1.5 |
vismChanCarrierLossPolicyThis object defines the policy that needs to be applied
when a carrier loss is detected.
This states whether to switch to the pre-upspeed codec or
to remain with the upspeed codec.
By default the value of this object will be unspecified
in that case the card level object value (vismCarrierLossPolicy)
will be used.
Configuring this object will not have any affect when
card level cac is disabled (vismCacEnable).rw Enumeration .1.3.6.1.4.1.351.110.5.5.3.1.3.1.6 |
vismChanVADToleranceThe value in this object refers to the customer accepted
drop rate for voice connections when the bandwidth usage
exceeds allowed value.
The actual range of this object is 0.0001% - 1.00 %
The unit is in percentage, since the default is 0.01 %,
and since we cannot express such fractions
in MIB , it is being multiplied by 10000 .
However, when the underlying CAC module is notified of
the change in this object, then the value
has to be divided by a factor of 10000.
Multiplication factor 10000 is picked as someone might be
interested in a tolerance as low as 0.0001%.
A value of zero indicates an invalid value. In that
case the card level object value will be used (vismVADTolerance).
Configuring this object will not have any affect when
card level cac is disabled (vismCacEnable).rw INTEGER .1.3.6.1.4.1.351.110.5.5.3.1.3.1.7 |
vismChanVADDutyCycleThis object refers to the talk-spurts duty cycle.
The unit is in percentage.
The actual range of this object is 0.01 to 0.99 %
and not 0.01 to 1.00 % as specified in the range
values above. Since a value of 100 will cause a
floating point exception, this value is disallowed.
The default value is 0.61% and since we cannot
have fractions in a MIB variable the value
is being multiplied by 100 and is expressed as
61.
When the value of this object is to be passed
to underlying CAC module in VISM this value has to
be divided by 100.
A value of zero indicates an invalid value. In that
case the card level object value will be used (vismVADDutyCycle).
Configuring this object will not have any affect when
card level cac is disabled (vismCacEnable).
only value 1 - 99 is allowed to be set.rw INTEGER .1.3.6.1.4.1.351.110.5.5.3.1.3.1.8 |
networkCacConfigStateThis attribute defines whether the originating and terminating
VISMs are configured properly or not, by default the
configuration is assumed to be ok and this object is set
to ok, if later during upspeed if we discover that both
the originating and terminating VISMs are configured as
either cac master or slave then it is considered as an
invalid configuration and this object will be set to 'notOk'
and trapNetworkCacConfigState change trap will be sent.
This parameter is applicable only in trunking applications.ro Enumeration .1.3.6.1.4.1.351.110.5.5.3.1.3.1.9 |
vismChanStateGrp OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.5.5.3.2 |
vismChanStateGrpTablevoice connection state table SEQUENCE OF VismChanStateGrpEntry .1.3.6.1.4.1.351.110.5.5.3.2.1 |
vismChanStateGrpEntryAn entry for each channel (PVC) VismChanStateGrpEntry .1.3.6.1.4.1.351.110.5.5.3.2.1.1 |
vismStateChanNumRefers to the channel Number LCN.ro INTEGER .1.3.6.1.4.1.351.110.5.5.3.2.1.1.1 |
vismChanStateChannel status.ro Enumeration .1.3.6.1.4.1.351.110.5.5.3.2.1.1.2 |
vismChanXmtATMStateThis variable indicates the transmit state of channel
on the ATM side(towards the network).ro Enumeration .1.3.6.1.4.1.351.110.5.5.3.2.1.1.3 |
vismChanRcvATMStateThis variable indicates the receive state of channel
on the ATM side(from the network).ro Enumeration .1.3.6.1.4.1.351.110.5.5.3.2.1.1.4 |
vismChanStatusBitMapThis variable indicates the consolidated bit map of
the channel alarm state.
Individual bit positions are as defined below, all reserved
bits will be set to zero.
Bit position Fail/Alarm Reason
0 Alarm Reserved
1 Alarm n/w side CC failure/AIS/RDI Rx
2 Fail Conditioned (Abit from n/w)
3 Alarm Reserved
4 Fail Reserved
5 Fail Reserved
6 Alarm Reserved
7 Alarm Reserved
Fail bitmap mask : 0x34
Alarm bitmap mask: 0xCBro INTEGER (0..'ff'h) .1.3.6.1.4.1.351.110.5.5.3.2.1.1.5 |
vismChanCntGrp OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.5.5.3.3 |
vismChanCntGrpTablevism channel counters table. This table gets implicitly created and
deleted at the time of creation and deletion of ChanCnfGrp. SEQUENCE OF VismChanCntGrpEntry .1.3.6.1.4.1.351.110.5.5.3.3.1 |
vismChanCntGrpEntryAn entry for each voice channel. VismChanCntGrpEntry .1.3.6.1.4.1.351.110.5.5.3.3.1.1 |
vismCntChanNumRefers to the logical channel Number.ro INTEGER .1.3.6.1.4.1.351.110.5.5.3.3.1.1.1 |
vismCntClrButtonwriting a value of 2 resets all the counters.ro Enumeration .1.3.6.1.4.1.351.110.5.5.3.3.1.1.10 |
vismChanAal2HecErrorsThe count of egress AAL2 CPS(Common Part Sub-layer) PDUs dropped
due to HEC (Header Error Control) error.ro Counter .1.3.6.1.4.1.351.110.5.5.3.3.1.1.11 |
vismChanAal2CrcErrorsThe count of egress AAL2 type3 CPS PDUs dropped due to
invalid CRC-10 error. CRC validation is for type 3 packets only.
Type 1 packets are not subjected to CRC-10 error validation. Also
this counter keeps track of CRC-10 errors for the type 3 packets
which are generated by the the datamover CPU only. It does not take
into account of type3 packets generated by the DSPs.ro Counter .1.3.6.1.4.1.351.110.5.5.3.3.1.1.12 |
vismChanAal2OamLpbLostCellsThe count of OAM loopback cells lost. OAM loopback cells are sent
on a periodic basis (1sec) on each PVC to monitor the health of
the PVC. This is applicable for all PVCs.ro Counter .1.3.6.1.4.1.351.110.5.5.3.3.1.1.13 |
vismChanAal2InvOsfCellsThe Number of AAL2 cells dropped due to invalid OSF (OffSet Field)
in the egress direction.ro Counter .1.3.6.1.4.1.351.110.5.5.3.3.1.1.14 |
vismChanAal2InvParCellsThe Number of AAL2 cells dropped due to invalid Parity bit field
in the egress direction.ro Counter .1.3.6.1.4.1.351.110.5.5.3.3.1.1.15 |
vismChanAal2CpsSentPktsThe count of AAL2 CPS packets sent to the network.ro Counter .1.3.6.1.4.1.351.110.5.5.3.3.1.1.16 |
vismChanAal2CpsRcvdPktsThe count of AAL2 CPS packets received from the network. This does
not include the packets which are counted as error packets.ro Counter .1.3.6.1.4.1.351.110.5.5.3.3.1.1.17 |
vismChanAal2CpsInvCidPktsThe count of AAL2 CPS packets dropped in the egress direction
due to invalid CID (Channel ID). The CID may be considered as
invalid if -
a) It is out of range.
b) It is not configuredro Counter .1.3.6.1.4.1.351.110.5.5.3.3.1.1.18 |
vismChanAal2CpsInvUuiPktsThe count of AAL2 CPS packets dropped in the egress direction
due to invalid UUI (User-to-User Info.) field.ro Counter .1.3.6.1.4.1.351.110.5.5.3.3.1.1.19 |
vismChanAal2CpsInvLenPktsThe count of AAL2 CPS packets dropped in the egress direction
due to invalid length field.ro Counter .1.3.6.1.4.1.351.110.5.5.3.3.1.1.20 |
vismChanAal5InvCpiPdusThe count of AAL5 PDUs dropped in the egress direction
due to invalid CPI (common part indicator) field in the
AAL5 PDU trailer. This is applicable only to the PVCs
configured as AAL5 PVCs (VoIP PVCs or CCS PVCs in the
case of VoAAL2 application).ro Counter .1.3.6.1.4.1.351.110.5.5.3.3.1.1.21 |
vismChanAal5OversizedSdusRcvdPdusThe count of AAL5 PDUs dropped due to the SDU size
bigger than the configured value. This is applicable
for AAL5 PVCs only.ro Counter .1.3.6.1.4.1.351.110.5.5.3.3.1.1.22 |
vismChanAal5InvLenPdusThe count of AAL5 PDUs dropped due to the length
violations. This is applicable to the CCS PVCs.
The HDLC frames should have a minimum frame size
in order for the proper interpretation by the
upper layer protocol.ro Counter .1.3.6.1.4.1.351.110.5.5.3.3.1.1.23 |
vismChanAal5Crc32ErrorPdusThe count of AAL5 PDUs dropped in the egress direction
due to CRC-32 errors detected by the SAR.ro Counter .1.3.6.1.4.1.351.110.5.5.3.3.1.1.24 |
vismChanAal5ReassemTimerExpiryPdusThe count of AAL5 PDU reassembly timer expirations.
The timers are maintained in the egress direction
for building an AAL5 PDU from the cells.ro Counter .1.3.6.1.4.1.351.110.5.5.3.3.1.1.25 |
vismAal2CidGrp OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.5.5.3.4 |
vismAal2CidCnfTableThis table is defined to establish the binding between an endpoint
and a PVC/CID pair in the case of AAL2 adaptation. This table is
created and used in trunking mode VISM application only.
The maximum number of CIDs that can be configured depends on the
current codec template being used as represented by vismAppliedTemplate
object. The signaling type of the line has to be configured before
adding any CID on that line. SEQUENCE OF VismAal2CidEntry .1.3.6.1.4.1.351.110.5.5.3.4.1 |
vismAal2CidEntryPlease see the above description. VismAal2CidEntry .1.3.6.1.4.1.351.110.5.5.3.4.1.1 |
vismAal2CidNumThis attribute defines part of the index for the cid Table.
vismAal2CidNum is the CID (or Channel ID) of a voice channel. CID has to be
the same at both endpoints for a connection. CID is unique only within
the context of a Virtual Circuit (PVC or SVC).ro INTEGER .1.3.6.1.4.1.351.110.5.5.3.4.1.1.1 |
vismAal2CidLcnThis attribute defines part of the index for the cid Table.
Since CID is unique to a PVC, a combination of LCN and CID uniquely
identifies a voice connection.
This field refers to vismChanNum defined in vismChanCnfGrp.ro INTEGER .1.3.6.1.4.1.351.110.5.5.3.4.1.1.2 |
vismAal2EndptNumThis attribute defines the endpoint number to which this
CId is associated. It is the same as mgEndpointNumber in
in mgEndpointTablerw INTEGER .1.3.6.1.4.1.351.110.5.5.3.4.1.1.3 |
vismAal2CidRowStatusThis variable allows to add or delete a CID. A CID can only be
added or deleted. Once added, mdifying an entry is not allowed.
createAndGo: Use this to add an entry in this table.
active: This values is returned, once the row is created
destroy: Use this to delete an entry from this table.
For creating a CID, a value for vismAal2EndptNum, vismAal2CidCodecType
vismAal2CidProfileType, vismAal2CidProfileNum must be provided. To all
other objects, defaults defined by the agent implementation may apply.rw Enumeration .1.3.6.1.4.1.351.110.5.5.3.4.1.1.4 |
vismAal2CidType3RedundancyThis attribute defines whether the triple redundancy is supported
for type 3 packets in AAL2 for this channel. When Triple redundancy
is enabled for a channel, the type 3 packets (CAS bits, dialled digits
and user state control packets) are transmitted in triplicates with an
interval defined as per the standards I.366.2. For channels which are
quite reliable, triple redundancy can be disabled in order to save the
bandwidth and the processing overheads.
The default value of this object is true if either
vismAal2CidCasTransport or vismAal2CidDtmfTransport is true, otherwise
the default value is false.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.351.110.5.5.3.4.1.1.5 |
vismAal2CidVadThis attribute defines whether the VAD (Voice Activity Detection)
has to be applied on this channel, upon detection of silence.
For algorithms that do not have VAD (Voice Activity Detection)
standards, Cisco-proprietary VAD can be applied and the generic
SID packet as specified in I.366.2 standards can be sent to the
other end.
When the codecType is clearChannel vad has to be off.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.351.110.5.5.3.4.1.1.6 |
vismAal2CidProfileTypeThis attribute defines the profile type. The profile type
defines which group of the profile tables the profile number
should correspond to. There are three possible groups:
itu - corresponding to the tables in ITU
format in the profile is being used.
atm - This is not supported
custom - VISM specific custom profiles
For doing a SET on this object, a value for vismAal2CidprofileNum also
has to be specified.
This is a mandatory parameter while adding a cid.rw Enumeration .1.3.6.1.4.1.351.110.5.5.3.4.1.1.7 |
vismAal2CidProfileNumThis attribute defines the profile number. A profile is a set of
entries, where each entry specifies an encoding format with a UUI range
and length. This set defines a mapping that informs the receiver of a
type 1 packet how to interpret the packet contents, i.e. which encoding
format in the profile is being used.
For doing a SET on this object, a value for vismAal2CidprofileType also
has to be specified.
This is a mandatory parameter while adding a cid.rw INTEGER .1.3.6.1.4.1.351.110.5.5.3.4.1.1.8 |
vismAal2CidCodecTypeThis attribute defines the codec Type used for the connection.
g711u represents PCMU with 64 kbps.
g711a represents PCMA with 64 kbps.
g726r32000 represents G.726 at rate 32 kbps
g726r16000 represents G.726 at rate 16 kbps
g726r24000 represents G.726 at rate 24 kbps
g726r40000 represents G.726 at rate 40 kbps
g729a represents G.729 Annex A algorithm.
g729ab represents G.729 Annex A and Annex B algorithm.
clearChannel represents CCD with 64 kbps.
g723h represents G.723.1-H at rate 6.3kbps.
g723ah represents G.723.1-H at rate 6.3kbps with Silence Supression(SID)
ON.
g723l represents G.723.1-L at rate 5.3kbps.
g723al represents G.723.1-L at rate 5.3kbps with Silence Supression(SID)
ON.
Note :
1. When codec type is clearChannel, vismAal2CidProfileType
and vismAal2CidProfileNum are not applicable and will be ignored.
2. Value 10 is RESERVED and can't be used in future.rw Enumeration .1.3.6.1.4.1.351.110.5.5.3.4.1.1.9 |
vismAal2CidDtmfTransportThis attribute defines whether the DTMF (Dual Tone Multi Frequency)
digits need to be transported to the other end-point.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.351.110.5.5.3.4.1.1.10 |
vismAal2CidCasTransportThis attribute defines whether the CAS (ABCD bits) bits need to be
transported to the other endpoint. In the case of switching application,
the CAS bits are backhauled to the Call Agent thro' xGCP-CAS protocol.
Note that if the line signaling type is CAS the default value is TRUE,
else the default value is FALSE.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.351.110.5.5.3.4.1.1.11 |
vismAal2CidEcanEnableThis attribute defines whether Echo Cancellation has to be enabled
on this connection. If it is set to True, echo cancellation is
enabled. If it is set to False, echo cancellation is disabled.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.351.110.5.5.3.4.1.1.12 |
vismAal2InitVadTimerThis attribute defines the hangover time for VAD in milliseconds.
Once the voice inactivity is detected, the gateway will wait for
this duration before activating silence suppression.rw INTEGER .1.3.6.1.4.1.351.110.5.5.3.4.1.1.13 |
vismAal2CnfPktPeriodThis object is used to configure the packetization period for
a given codec. This pkt period has to be a valid entry in the profile table.
Profile type and number identify a unique profile table and one codec
type in this table might have one or more packetization period. This
is applicable only if the vismAal2CidCodecType is G.729a.
The configurable values for G.729a are 10,20,30 & 40.
If a cid entry is configured with a codec other than G.729a then the user
cannot configure the pkt period for that codec and the pkt period is picked
from the profile table.
Hence when we do get/walk on this entry/table any one of the above values could
be returned.
The packetization periods of 20, 30 and 40 ms. are not allowable in
case of G729-a for the list of profiles that we support now. We can
only support 10ms.
For G.723 the configurable values is 30. Default value would be 30.
Please see ENG-45055 or ITU specification I.366.2 annex P for more
information.rw Enumeration .1.3.6.1.4.1.351.110.5.5.3.4.1.1.14 |
vismAal2CidICSEnableThis object is used to enable or disable the Idle Channel Suppresion for
a cid. This can be specified while adding the cid and cannot be modified.
When the Idle Channel Suppression is enabled the DSP will look for the
idle cas (ABCD bits) pattern specified in ds0IdleCode in dsx0 MIB. If
the idle pattern is present the DSP stops generating voice packets towards
ATM side. By default the ds0IdleCode will be zero unless the user has
configured it before adding the cid. If the ds0IdleCode is
changed after the cid is added it will have no affect unless the card is reset.
Idle Channel Suppression is applicable only for trunking application,
In case of switching there is no need for Idle channel Suppression as the
calls are teared down and set up dynamically.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.351.110.5.5.3.4.1.1.15 |
vismAal2CidStateIndicates the state of the cid.
active - the cid is in service and operational
failed - the cid is in service but not operational,
e.g. because the PVC that the cid belongs to
is receiving F5 level alarm
When VISM sees alarm on a CID (network side) sets
this object to cidStateFailed, trapVismCidState
trap will be sent, and an AIS will be sent
on the ds0 that this cid corresponds to.
If the whole PVC is in alarm then all the cids
on that PVC will be set to cidStateFailed,
trapVismChanFailed trap will be sent and all
the ds0's that corresponds to each of the cids
on this PVC will be in alarm. (NOTE: no trapVismCidState
will be sent).
If VISM sees an alarm on a ds0 in a line then
an RAI will be sent on the cid that corresponds
to this ds0, however the cid will not be put in
failed state.ro Enumeration .1.3.6.1.4.1.351.110.5.5.3.4.1.1.16 |
vismAal2CidFailReasonThis object is used to indicate the cid failure
reason.
self: fail because of non-PVC alarm
highLevel: fail because of PVC alarm
both: fail because of both PVC and non-PVC alarm
notFail: not failro Enumeration .1.3.6.1.4.1.351.110.5.5.3.4.1.1.17 |
bert OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.6.1 |
bertControlThis object controls all the SET operations on this MIB group.
acquireBert : Acquire BERT resources.
cnfBert : Configure the required BERT test.
startBert : The configured test has to be started.
modBert : Modify parameters for the ongoing BERT test.
delBert : Running BERT test has to be stopped.
The above list shows the sequence in which the SET operations
on this group need to be done, ideally.
Bert can be operated upon only with bertUserId and bertSlotNumber.
The default value is 0, means no action.rw Enumeration .1.3.6.1.4.1.351.110.6.1.1 |
bertResourceStatusAll of bert resources can be used by only one user at a time.
This gives the status of the resources.ro Enumeration .1.3.6.1.4.1.351.110.6.1.2 |
bertOwnerThis refers to the user who owns the BERT resources.
If the user is a CLI user, then this is username.
If it is SV+, then this would be the IP address.
For example, this value can be, 192.9.209.157 within quotes.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.351.110.6.1.3 |
bertUserIdThis identifies the user who wants to do a SET operation
on this group. This will be compared against bertOwner
and access will be given only if it matches. Hence, for
every SET request, this object should have a valid value.
If the user is a CLI user, then this is username.
If it is SV+, then this would be the IP address.
For example, this value can be, 192.9.209.157 within quotes.
Required for bert operations.rw DisplayString (SNMPv2-TC) .1.3.6.1.4.1.351.110.6.1.4 |
bertStatusThis variable provides the status of BERT in the shelf.ro Enumeration .1.3.6.1.4.1.351.110.6.1.5 |
bertSlotNumberspecifies the physical slot number of the Service Module
which is to run BERT
For MGX 8220, the range is 5-14.
For MGX 8850, the range is 1-6, 9-14, 17-22, 25-30.
Required for bert operations.rw INTEGER .1.3.6.1.4.1.351.110.6.1.6 |
bertTestMediumspecifies whether the bert is to test a port or an
entire T1/E1 line.
No default value for this, it has to be set if bert is configured.rw Enumeration .1.3.6.1.4.1.351.110.6.1.7 |
bertPortspecifies the port number for BERT.rw INTEGER .1.3.6.1.4.1.351.110.6.1.8 |
bertLinespecifies the line number for BERT. If the test medium
is port, this represents the line to which the port belongs.rw INTEGER .1.3.6.1.4.1.351.110.6.1.9 |
bertModespecifies the mode, the BERT module is to be configured for.rw Enumeration .1.3.6.1.4.1.351.110.6.1.10 |
bertDeviceToLoopThis shows the type of the end device and the type of the
loopback used (latching/nonlatching/polynomial).rw Enumeration .1.3.6.1.4.1.351.110.6.1.11 |
bertDS0DPIterationCountThe Iteration Register needs to be programmed in SRM when
DSO drop loop option is selected in bertDeviceToLoop. The
value to be programmed there is minus one of this object value,
since the register is 0 based. DSP-OP devices can be cross
connected in the centeral office. By this, the user has
capablitiy to put any of the devices in the chain in loopback
mode. This is done by repeating the latching activation
code in a specific manner. The binary number in the
iterataion register determines how many times the first portion
of a latching loop activation code needs to be repeated as per
user request and according to the Bellcore spec. A value of 0
results in no iteration and will cause the very first device in
chain to go into loop back. A value of 1 will result into one
iteration and will cause the second device to go into loopback
and so on. The range of this count is 1 to 32, and it would
translate to a range of 0 to 31 for the iteration register.rw INTEGER .1.3.6.1.4.1.351.110.6.1.12 |
bertPatternThis variable determines BERT pattern to be transmitted.rw Enumeration .1.3.6.1.4.1.351.110.6.1.13 |
bertLoopbackspecifies the type of loopback to be (d)established.rw Enumeration .1.3.6.1.4.1.351.110.6.1.14 |
bertLoopbackOperationspecifies the operation of loopback (up or down).rw Enumeration .1.3.6.1.4.1.351.110.6.1.15 |
bertDS0Speedrepresents the ds0 speed of the test running.ro Enumeration .1.3.6.1.4.1.351.110.6.1.16 |
bertTimeSlotsrepresents the number of ds0s in the test medium chosen.ro INTEGER .1.3.6.1.4.1.351.110.6.1.17 |
bertStartTimeThe syntax is hh:mm:ss
The time zone is as configured in the shelf.ro DisplayString .1.3.6.1.4.1.351.110.6.1.18 |
bertStartDateOn MGX 8220, the syntax is mm/dd/yy
On MGX 8850, the syntax is mm/dd/yyyyro DisplayString .1.3.6.1.4.1.351.110.6.1.19 |
bertBitCountThis shows the number of bits transmitted.ro INTEGER .1.3.6.1.4.1.351.110.6.1.20 |
bertBitErrorCountThis shows the number of bits received in error.ro INTEGER .1.3.6.1.4.1.351.110.6.1.21 |
bertErrorInjectCountThis shows the number of times error was injected.ro INTEGER .1.3.6.1.4.1.351.110.6.1.22 |
bertCleanupActionWhen the BERT has to be stopped or aborted (due to card state
changes), this object would give the exact action to take.
The bert related changes to the shelf, then, can be cleaned up.
When its value is a Loopdown, it implies smCleanup plus the
corresponding Loopdown.ro Enumeration .1.3.6.1.4.1.351.110.6.1.23 |
bertAbortReasonwhen the BERT is aborted, this object would give the
reason for that.ro Enumeration .1.3.6.1.4.1.351.110.6.1.24 |
bertDDSSeekResultsTableFirstIndexDenotes the index of the oldest entry in the table.
A value of zero means that there are no entries in the table.ro INTEGER .1.3.6.1.4.1.351.110.6.1.25 |
bertDDSSeekResultsTableLastIndexDenotes the index of the latest entry in the table.
A value of zero means that there are no entries in the table.ro INTEGER .1.3.6.1.4.1.351.110.6.1.26 |
bertDDSSeekResultsTableA list of detected DDS codes. SEQUENCE OF BertDDSSeekResultsTableEntry .1.3.6.1.4.1.351.110.6.1.27 |
bertDDSSeekResultsTableEntryAn entry in the detected DDS codes table. BertDDSSeekResultsTableEntry .1.3.6.1.4.1.351.110.6.1.27.1 |
bertDDSSeekResultsTableIndexDenotes the serial number of the entry in the table.ro INTEGER .1.3.6.1.4.1.351.110.6.1.27.1.1 |
bertDDSCodeDenotes the type of DDS code detected.ro Enumeration .1.3.6.1.4.1.351.110.6.1.27.1.2 |
bertSupportedTestsTableA list of supported tests for a given SM. SEQUENCE OF BertSupportedTestsTableEntry .1.3.6.1.4.1.351.110.6.1.28 |
bertSupportedTestsTableEntryA general supported tests entry. BertSupportedTestsTableEntry .1.3.6.1.4.1.351.110.6.1.28.1 |
bertSupportedTestsTableIndexThis index is the physical slot number of the Service
Module whose entry it represents in the table.
For MGX 8220, the range is 5-14.
For MGX 8850, the range is 1-6, 9-14, 17-22, 25-30.ro INTEGER .1.3.6.1.4.1.351.110.6.1.28.1.1 |
bertSupportFlag'yes' if the table entry correctly represents the supported
tests for the SM on the corresponding slot. 'no' if no tests
at all are supported.ro Enumeration .1.3.6.1.4.1.351.110.6.1.28.1.2 |
bertTestMediumMaskEvery test medium is represented by a bit of mask. Bits 0-1 are
valid in this integer. The meaning of the mask can be
understood from the example below:
TestMedium | SM
| support
port | 1
line | 1
(Table contents applicable to FRSM-4T1)
bertTestMediumMask = 11 binary
The column titles represent the variables bertTestMedium
depends on. The mask is represented in column major order.ro INTEGER .1.3.6.1.4.1.351.110.6.1.28.1.3 |
bertModeMaskEvery mode is represented by 2 bits of mask. Bits 0-5 are
valid in this integer. The meaning of the mask can be
understood from the example below:
Mode | SM support | Test Medium:
| | Multiple
| | T1 time slots
Pattern test | 1 | 1
DDS seek | 1 | 0
Loopback | 1 | 1
(Table contents applicable to FRSM-4T1)
bertModeMask = 101111 binary
The column titles represent the variables bertMode depends on.
The mask is represented in column major order.ro INTEGER .1.3.6.1.4.1.351.110.6.1.28.1.4 |
bertDeviceToLoopMaskEvery class of devices to loop is represented by 6 bits
of mask. Bits 0-29 are valid in this integer. The meaning
of the mask can be understood from the example below:
| | | Test Medium
Class of | SM | MODE |________________________________
devices |supp | Loopback|Line |multiple T1 | 64k | 56k
| | | | time slots | |
noLatch | 1 0 0 0 0 1
latch | 1 1 0 0 1 1
v54 | 1 1 0 1 1 1
inband/esf| 1 1 1 0 0 0
metallic | 1 0 1 0 0 0
(Table contents applicable to FRSM-4T1)
bertDeviceToLoopMask = 001110011000100110000111011111 binary
The column titles represent the variables bertDeviceToLoop
depends on. The mask is represented in column major order.
Due to the limitation on the length of the mask, 'noDevice'
option is not represented in this mask. But, the mask for
it, is assumed to be a row of ones except for a zero on
'MODE Loopback' column.ro INTEGER .1.3.6.1.4.1.351.110.6.1.28.1.5 |
bertPatternMaskEvery class of patterns is represented by 2 bits of mask.
Bits 0-3 are valid in this integer. The meaning of the
mask can be understood from the example below:
Class of | SM | Non latching
patterns | support |device to loop
Other patterns | 1 | 0
Patterns | 1 | 1
power 9 and 11 | |
(Table contents applicable to FRSM-4T1)
bertPatternMask = 1011 binary
The column titles represent the variables bertPattern
depends on. The mask is represented in column major order.ro INTEGER .1.3.6.1.4.1.351.110.6.1.28.1.6 |
bertLoopbackMaskEvery loopback is represented by 2 bits of mask. Bits 0-5 are
valid in this integer. The meaning of the mask can be
understood from the example below:
Loopback | SM | Test Medium
| support | Port
Far End Loopback | 1 | 1
Facility Loopback | 1 | 1
Metallic Loopback | 1 | 0
(Table contents applicable to FRSM-4T1)
bertLoopbackMask = 011111 binary
The column titles represent the variables bertLoopback
depends on. The mask is represented in column major order.ro INTEGER .1.3.6.1.4.1.351.110.6.1.28.1.7 |
bertCardT1E1TypeSpecifies whether a t1 or e1 card.ro Enumeration .1.3.6.1.4.1.351.110.6.1.28.1.8 |
onlineDiagnostics OBJECT IDENTIFIER .1.3.6.1.4.1.351.110.6.3 |
diagTypeThis is used to identify the type of diagnostics.
When a trap is sent to report diagnostics results
this is used as a varbind to indicate the type of diagnostics.ro Enumeration .1.3.6.1.4.1.351.110.6.3.1 |
diagResultThis is used to indicate the result of the diagnostics
tests in traps.ro Enumeration .1.3.6.1.4.1.351.110.6.3.2 |
diagTestIdThis is used to indicate the test number of the
diagnostics test that failed.ro INTEGER .1.3.6.1.4.1.351.110.6.3.3 |
parCmParmsMaxRoutingBundleThis object specifies the maximum number of connections that
can be routed in one routing cycle.rw INTEGER .1.3.6.1.4.1.351.130.5.2.1 |
parCmParmsRerouteTimerThis object specifies the minimum time after which a connection
is routed once it has been successfully routed.rw INTEGER .1.3.6.1.4.1.351.130.5.2.2 |
parCmParmsResetTimerThis object specifies whether the reroute timer should be reset
if the path for routed connection failed.
If the value of the object is True the timer is reset on detecting
path fail.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.351.130.5.2.3 |
parCmParmsDnUpPerPassThis object specifies the maximum number of connections that are
upped or down in one schedule of down connection state machine.rw INTEGER .1.3.6.1.4.1.351.130.5.2.4 |
parCmParmsDnUpTimerThis object specifies the minimum time interval (in milliseconds)
between two schedules of the down connection state machine.rw INTEGER .1.3.6.1.4.1.351.130.5.2.5 |
parCmParmsRrtErrsPerCycleThis object specifies the threshold for number of failures to
route a connection before it is moved into the wait group.
If the value of this object is 0 the feature is disabled.rw INTEGER .1.3.6.1.4.1.351.130.5.2.6 |
parCmParmsRrtCycleIntervalThis object specifies the time (in minutes) for which no
attempt is made to route a connection in the wait group.rw INTEGER .1.3.6.1.4.1.351.130.5.2.7 |
parCmParmsMaxRrtCyclesThis object specifies the number of times a connection is
added to the wait group before declaring it unroutable.rw INTEGER .1.3.6.1.4.1.351.130.5.2.8 |
parCmParmsRrtPauseTimeThis object specifies the time interval (in milliseconds)
between two routing cycles.rw INTEGER .1.3.6.1.4.1.351.130.5.2.9 |
parCmParmsMaxUpdatesThis object specifies the maximum number of connection
management updates that are sent by the node in schedule..rw INTEGER .1.3.6.1.4.1.351.130.5.2.10 |
parCmParmsRerouteGroupsThis object specifies the total number of reroute groups.rw INTEGER .1.3.6.1.4.1.351.130.5.2.11 |
parCmParmsMinRrGroupSizeThis object specifies the minimum size of reroute group in
Cell Load Units.rw INTEGER .1.3.6.1.4.1.351.130.5.2.12 |
parCmParmsRrGroupIncThis object specifies the increment of reroute group size
(in Cell Load Units) between adjacent groups.rw INTEGER .1.3.6.1.4.1.351.130.5.2.13 |
parCmParmsCostBasedThis object can be configured to enable or disable cost
based routing feature. If the value of this object is True
the feature is enabled else it is disabled.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.351.130.5.2.14 |
parCmParmsUseCacheThis object can be configured to enable or disable hop
based route selection from using cache of precomputed routes.
If the value of this object is True the feature is enabled
else it is disabled.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.351.130.5.2.15 |
parCmParmsUseDelayThis object can be configured to enable or disable cost
based route selection from considering end-to-end delay
associated with the routes. If the value of this object
is True the delay would be considered otherwise daley would
not be considered during routing of connection.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.351.130.5.2.16 |
parCmParmMaxViaConsThis object specifies the maximum number of via user connections
that can be routed through the node.rw INTEGER .1.3.6.1.4.1.351.130.5.2.17 |
parMnUpdtIntervalThis object specifies the timer interval (in seconds) for
the mandatory update state machine.rw INTEGER .1.3.6.1.4.1.351.130.5.3.1 |
parMnUpdtNodesPerIntThis object specifies the maximum number of nodes to which
mandatory updates can be sent per interval.rw INTEGER .1.3.6.1.4.1.351.130.5.3.2 |
parMnUpdtBatchSendThis object specifies whether mandatory updates to any node
are sent one at a time or all in one go. If the value of this
object is True, all mandatory updates are sent to the node
simultaneously. If the value of this object is False, mandatory
updates are sent one at a time.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.351.130.5.3.3 |
parSwFuncAbrVsvdThis object enables/disables the ABR standard with VSVD.
The feature is enabled if the value of the object is True.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.351.130.5.4.1 |
parSwFuncNodeTypeThis object specifies whether the node is a routing node or
a feeder node. To configure the node from a routing(1) node
to feeder(2) node the node should be part of a single node network.
To configure the node from feeder node to routing node, there
should be no feeder trunk attached to the node.rw Enumeration .1.3.6.1.4.1.351.130.5.4.2 |
parOnOffBackgroundUpdtThis object can be used to enable or disable Background updates.
If the value of the object is True Background updates are enabled;
otherwise they are disabled.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.351.130.5.5.1 |
parOnOffDynamicBwAllocThis object can be used to enable or disable Bandwidth state
machine. If the value of the object is True Bandwidth state
machine is enabled; otherwise it is disabled.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.351.130.5.5.2 |
parOnOffCmUpdtsThis object can be used to enable or disable Connection
management updates. If the value of the object is True
Connection management updates are enabled; otherwise they
are disabled.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.351.130.5.5.3 |
parOnOffRoutingThis object can be used to enable or disable connection
routing. If the value of the object is True routing is enabled;
otherwise it is disabled.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.351.130.5.5.4 |
parOnOffCommFailTestThis object can be used to enable or disable Comm Fail Test.
If the value of the object is True Comm Fail test is enabled;
otherwise it is disabled.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.351.130.5.5.5 |
parOnOffDrtDelayThis object can be used to enable or disable Deroute Delay feature.
If the value of the object is True Derote delay feature is
enabled; otherwise it is disabled.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.351.130.5.5.6 |
parOnOffRenumRecThis object can be used to enable or disable Renumber
recovery feature. If the value of the object is True renumber
recovery feature is enabled; otherwise it is disabled.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.351.130.5.5.7 |
parOnOffCommBreakThis object can be used to enable or disable Comm Break Test.
If the value of the object is True Comm Break Test feature is
enabled; otherwise it is disabled.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.351.130.5.5.8 |
parSysParmsTsPacketAgeTime Stamped packets older than this value (in milliseconds)
are discarded. This is a network wide parameter.rw INTEGER .1.3.6.1.4.1.351.130.5.6.1 |
parSysParmsConnFailThis object specifies whether the connections to a node
should be failed when comm fail is declared with the node.
If the value of this object is True the connection will be
failed. This is a network wide parameter.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.351.130.5.6.2 |
parSysParmsVcPollRateThis object specifies the rate at which VC statistics are
to be polled. This is a network wide parameter.
For Portable AutoRoute statistic collections would be done by
platform software.ro INTEGER .1.3.6.1.4.1.351.130.5.6.3 |
parSysParmsMaxVDelayThis object specifies the maximum delay for
voice connection with VAD enabled in milli-seconds. This is
a network wide parameter.ro INTEGER .1.3.6.1.4.1.351.130.5.6.4 |
parSysParmsMaxCDelayThis object specifies the maximum delay for ADPCM compressed
voice connection with VAD enabled in milli-seconds. This is
a network wide parameter.ro INTEGER .1.3.6.1.4.1.351.130.5.6.5 |
parSysParmsMaxDDelayThis object specifies the maximum delay for data connection
in milli-seconds. This is a network wide parameter.ro INTEGER .1.3.6.1.4.1.351.130.5.6.6 |
parSysParmsMaxADelayThis object specifies the maximum delay for ADPCM compressed
voice connection in milli-seconds. This is a network wide parameter.ro INTEGER .1.3.6.1.4.1.351.130.5.6.7 |
parSysParmsMaxHsdDelayThis object specifies the maximum delay for High Speed data
connection in milli-seconds. This is a network wide parameter.ro INTEGER .1.3.6.1.4.1.351.130.5.6.8 |
parSysParmsDeEnableThis object specifies whether DE bit of Frame Relay frames
can be modified. DE bit can be modified if the value of this
object is True. This is a network wide parameter.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.351.130.5.6.9 |
parSysParmsFrStandardThis object specifies whether standard Frame Relay parameters,
Be and Bc, are to be used. If the value of this object is True,
standard parameters are used. This is a network wide parameter.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.351.130.5.6.10 |
parSysParmsDrtDelayThis object specifies whether Deroute Delay feature is enabled.
If the value of this object is True, the feature is enabled.
This is a network wide parameter.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.351.130.5.6.11 |
parSysParmsInvLogAlarmThresThis object specifies the threshold for invalid login attempts
before triggering an alarm. If the value of this object is zero,
this feature is disabled. This is a network wide parameter.ro INTEGER .1.3.6.1.4.1.351.130.5.6.12 |
parSysParmsMaxCdpVDelayThis object specifies the maximum network delay for CDP to CDP
voice connection with VAD enabled in milli-seconds. This is a
network wide parameter.ro INTEGER .1.3.6.1.4.1.351.130.5.6.13 |
parSysParmsMaxCdpCDelayThis object specifies the maximum network delay for CDP to CDP
ADPCM compressed voice connection with VAD enabled in milli-seconds.
This is a network wide parameter.ro INTEGER .1.3.6.1.4.1.351.130.5.6.14 |
parSysParmsMaxCdpDDelayThis object specifies the maximum network delay for CDP to CDP
data connection in milli-seconds. This is a network wide parameter.ro INTEGER .1.3.6.1.4.1.351.130.5.6.15 |
parSysParmsMaxCdpADelayThis object specifies the maximum network delay for CDP to CDP
ADPCM compressed voice connection in milli-seconds. This is a
network wide parameter.ro INTEGER .1.3.6.1.4.1.351.130.5.6.16 |
parSysParmsMaxCdpHsdDelayThis object specifies the maximum network delay for CDP to CDP
High Speed data connection in milli-seconds. This is a network
wide parameter.ro INTEGER .1.3.6.1.4.1.351.130.5.6.17 |
parSysParmsMaxIpcdpVDelayThis object specifies the maximum local delay for CDP to CDP voice connection with VAD enabled in milli-seconds. This is a network wide parameter.ro INTEGER .1.3.6.1.4.1.351.130.5.6.18 |
parSysParmsMaxIpcdpCDelayThis object specifies the maximum local delay for CDP to CDP ADPCM compressed voice connection with VAD enabled in milli-seconds. This is a network wide parameter.ro INTEGER .1.3.6.1.4.1.351.130.5.6.19 |
parSysParmsMaxIpcdpDDelayThis object specifies the maximum local delay for CDP to CDP data connection in milli-seconds. This is a network wide parameter.ro INTEGER .1.3.6.1.4.1.351.130.5.6.20 |
parSysParmsMaxIpcdpADelayThis object specifies the maximum local delay for CDP to CDP ADPCM compressed voice connection in milli-seconds. This is a network wide parameter.ro INTEGER .1.3.6.1.4.1.351.130.5.6.21 |
parSysParmsMaxIpcdpHsdDelayThis object specifies the maximum local delay for CDP to CDP High Speed data connection in milli-seconds. This is a network wide parameter.ro INTEGER .1.3.6.1.4.1.351.130.5.6.22 |
parSysParmsMaxIphsdDelayThis object specifies the maximum local delay for High Speed data connection in milli-seconds. This is a network wide parameter.ro INTEGER .1.3.6.1.4.1.351.130.5.6.23 |
parSysParmsFpdDeJitterThis object specifies the jitter delay for Fast Pad. This is a network wide parameter.ro INTEGER .1.3.6.1.4.1.351.130.5.6.24 |
parNetParmCondInitialStgrThis object specifies the initial pause time
(in milliseconds) per new node added on addition of node(s)
in the network before initiating conditional updates.rw INTEGER .1.3.6.1.4.1.351.130.5.7.1 |
parNetParmCondPerNodeIntervalThis object specifies the minimum interval (in milliseconds)
between sending of conditional updates to any two nodes.rw INTEGER .1.3.6.1.4.1.351.130.5.7.2 |
parNetParmCbDelayThis object specifies the minimum interval (in milliseconds)
between initiating comm break tests between any two nodes.rw INTEGER .1.3.6.1.4.1.351.130.5.7.3 |
parNetParmCbOffsetTBD.rw INTEGER .1.3.6.1.4.1.351.130.5.7.4 |
parNetParmMsgTimeoutThis object specifies the timeout (in milliseconds) for
acknowledgment for control plane message sent to another node.rw INTEGER .1.3.6.1.4.1.351.130.5.7.5 |
parNetParmMsgMaxTimeoutThis object specifies the maximum number of times a network
handler timeout waiting for acknowledgment for control plane
message sent to another node reachable through all terrestrial trunks.rw INTEGER .1.3.6.1.4.1.351.130.5.7.6 |
parNetParmMsgMaxTimeoutSatThis object specifies the maximum number of times a network
handler timeout waiting for acknowledgment for control plane
message sent to another node reachable through all satellite trunks.rw INTEGER .1.3.6.1.4.1.351.130.5.7.7 |
parNetParmBlindMaxTimeoutThis object specifies the maximum number of times a network
handler timeout waiting for acknowledgment for control plane
blind message sent to another node.rw INTEGER .1.3.6.1.4.1.351.130.5.7.8 |
parNetParmCbMaxTimeoutThis object specifies the maximum number of times a network
handler timeout waiting for acknowledgment for comm break test
message sent to another node.rw INTEGER .1.3.6.1.4.1.351.130.5.7.9 |
parNetParmCfTestIntervalThis object specifies the minimum time interval between the
comm fail tests for a trunk.rw INTEGER .1.3.6.1.4.1.351.130.5.7.10 |
parNetParmCfTestMultiplierThis object specifies the multiplier for the comm fail test
interval for good trunks, that is, trunks not in comm fail.rw INTEGER .1.3.6.1.4.1.351.130.5.7.11 |
parNetParmNetwWindowSzThis object specifies the window size for the network handler
for messages to any node. That is, the number of messages that
the network handler can send simultaneous to a node without
receiving the acknowledgment for them.rw INTEGER .1.3.6.1.4.1.351.130.5.7.12 |
parNetParmNetwLetWaitThis object specifies the maximum interval (in milliseconds)
network handler waits for the letter (message) from the
processes running on its nodes before checking the received cells.rw INTEGER .1.3.6.1.4.1.351.130.5.7.13 |
parNetParmCfDelayTBD (in milliseconds).rw INTEGER .1.3.6.1.4.1.351.130.5.7.14 |
parNetParmHighTxRateThis object specifies the rate (in fast packets per second)
at which the network handler sends control plane message cells
to high performance nodes (High performance node are BPX and MGX).rw INTEGER .1.3.6.1.4.1.351.130.5.7.15 |
parNetParmLowTxRateThis object specifies the rate (in fast packets per second) at
which the network handler sends control plane message cells to
low capacity nodes (Low capacity node are IPX and IGX).rw INTEGER .1.3.6.1.4.1.351.130.5.7.16 |
parNetParmMaxNodeBlksThis object specifies the maximum number of blocks, of size
256 bytes, that should be queued up for transmission to a node.rw INTEGER .1.3.6.1.4.1.351.130.5.7.17 |
parNetParmTopoMsgSegSzThis object specifies the maximum size (in bytes) of the
segment into which the topology message, sent during network
join, is divided.rw INTEGER .1.3.6.1.4.1.351.130.5.7.18 |
frEndPtMapGrp OBJECT IDENTIFIER .1.3.6.1.4.1.635.1.2.3 |
frEndPtMapGrpTableTable of transmit/receive states of channels. SEQUENCE OF FrEndPtMapGrpEntry .1.3.6.1.4.1.635.1.2.3.1 |
frEndPtMapGrpEntryAn entry for FrEndPtMapGrpEntry. FrEndPtMapGrpEntry .1.3.6.1.4.1.635.1.2.3.1.1 |
endPortNumRefers to the logical port index
For FRSM12 card:
The ifIndex of the port's corresponding row in ifTable.
Byte 3 = Chassis Number, Byte 2 = Slot Number,
Byte 1 & 0 = Encoded unique number for Port.ro INTEGER .1.3.6.1.4.1.635.1.2.3.1.1.1 |
endDLCIRefers to the DLCI indexro INTEGER .1.3.6.1.4.1.635.1.2.3.1.1.2 |
endChanNumLogical connection number
0 if port.dlci is a multicast group
Note that the actual range of endChanNum
supported by a card depends on the type of card.
eg: FRSM-4T1/E1 supports a range from 16..271 (256 entries)
FRSM-8T1/E1 supports a range from 16..1015 (1000 entries)
FRSM-T3/E3/HS2 supports a range from 16..2015 (2000 entries)
FRSM-2CT3 supports a range from 16..4015 (4000 entries)
For FRSM12 Card:
Byte 3 = Chassis Number, Byte 2 = Slot Number,
Byte 1 & 0 = channel Number.
Lower two bytes range from 16..16015 (16000 entries)ro INTEGER .1.3.6.1.4.1.635.1.2.3.1.1.3 |
endLineNumRefers to the physical line index.
Note that the actual range of endLineNum
supported by a card depends on the type of card.
eg: FRSM-4T1/E1 supports a range from 1..4 (4 entries)
FRSM-8T1/E1 supports a range from 1..8 (8 entries)
FRSM-T3/E3/HS2 supports a range from 1..2 (2 entries)
FRSM-2CT3 supports a range from 1..56 (56 entries)
For FRSM12 Card:
The ifIndex of the physical line on which this channel
is provisioned.ro INTEGER .1.3.6.1.4.1.635.1.2.3.1.1.4 |
ausmEndPointMapGrp OBJECT IDENTIFIER .1.3.6.1.4.1.1954.3.13.3 |
ausmEndPointMapGrpTableFor Ausm-4p There are 255 entries
For Ausm-8p There are 1000 entries
For PXM (MGX) There are 4096 entries
Port Num and VpiVci will uniquely identify a row. SEQUENCE OF AusmEndPointMapGrpEntry .1.3.6.1.4.1.1954.3.13.3.1 |
ausmEndPointMapGrpEntryAn entry in the table AusmEndPointMapGrpEntry .1.3.6.1.4.1.1954.3.13.3.1.1 |
ausmEndPortNumRefers to the logical port on the board. In AUSM (4-port card),
a logical port is synonymous with a physical port.
In PXM, a port refers to the Logical Broadband Interface.
Refer bbIfCnfPortGrp.my for more information.ro INTEGER .1.3.6.1.4.1.1954.3.13.3.1.1.1 |
endVpiThe VPI value for the connectionro INTEGER .1.3.6.1.4.1.1954.3.13.3.1.1.2 |
endVciThe VCI value for the connectionro INTEGER (0..'ffff'h) .1.3.6.1.4.1.1954.3.13.3.1.1.3 |
ausmEndChanNumRefers to the logical connection for this port and VpiVci.
In AUSM (4-port card), the permissible range is 16..271
In AUSM (8-port card), the permissible range is 16..1015
In PXM (MGX ) , the permissible range is 16..4111ro INTEGER .1.3.6.1.4.1.1954.3.13.3.1.1.4 |
endChanTypeRefers to the type of the connection for this Port and VpiVciro Enumeration .1.3.6.1.4.1.1954.3.13.3.1.1.5 |
pxmAtmMIBObjects OBJECT IDENTIFIER .1.3.6.1.4.1.1954.3.13.16 |
pxmAtmVcCrossConnectIndexNextThis object contains an appropriate value to
be used for pxmAtmVcCrossConnectIndex when creating
entries in the pxmAtmVcCrossConnectTable. The value
0 indicates that no unassigned entries are
available. To obtain the pxmAtmVpCrossConnectIndex
value for a new entry, the manager issues a
management protocol retrieval operation to obtain
the current value of this object. After each
retrieval, the agent should modify the value to
the next unassigned index.ro INTEGER .1.3.6.1.4.1.1954.3.13.16.10 |
pxmAtmVcCrossConnectTableThe ATM VC Cross Connect table. A bi-
directional VC cross-connect which
cross-connects two end points (i.e., VCLs)
is modeled as one entry in this table. SEQUENCE OF PxmAtmVcCrossConnectEntry .1.3.6.1.4.1.1954.3.13.16.11 |
pxmAtmVcCrossConnectEntryAn entry in the ATM VC Cross Connect table.
This entry is used to model a bi-directional ATM
VC cross-connect cross-connecting two end points.
Step-wise Procedures to set up a VC Cross-connect
Once the entries in the pxmAtmVclTable are created,
the following procedures are used
to cross-connect the VCLs together to
form a VCC segment.
(1) The manager obtains a unique
pxmAtmVcCrossConnectIndex by reading the
pxmAtmVcCrossConnectIndexNext object.
(2) Next, the manager creates a set of one
or more rows in the ATM VC Cross Connect
Table, one for each cross-connection between
two VCLs. Each row is indexed by the ATM
interface port numbers and VPI/VCI values of
the two ends of that cross-connection.
This set of rows specifies the topology of the
VCC cross-connect and is identified by a single
value of pxmAtmVcCrossConnectIndex.
Negotiated VC Cross-Connect Establishment
(2a) The manager creates a row in this table by
setting pxmAtmVcCrossConnectRowStatus to
createAndWait(5). The agent checks the
requested topology and the mutual sanity of
the ATM traffic parameters and
QoS Classes, i.e., the row creation fails if:
- the requested topology is not supported
by the agent,
- the traffic/QoS parameter values
associated with the requested row are
incompatible with those of already existing
rows for this VC cross-connect.
[For example, for setting up
a point-to-point VC cross-connect, the
ATM traffic parameters in the receive direction
of a VCL at the low end of the cross-connect
must equal to the traffic parameters in the
transmit direction of the other VCL at the
high end of the cross-connect,
otherwise, the row creation fails.]
The agent also checks for internal errors
in building the cross-connect.
The pxmAtmVcCrossConnectIndex values in the
corresponding pxmAtmVclTable rows are filled
in by the agent at this point.
(2b) The manager promotes the row in the
pxmAtmVcCrossConnectTable by setting
pxmAtmVcCrossConnectRowStatus to active(1). If
this set is successful, the agent has reserved
the resources specified by the ATM traffic
parameter and QoS Class values
for each direction of the VC cross-connect
in an ATM switch or network.
(3) The manager sets the
pxmAtmVcCrossConnectAdminStatus to up(1)
in all rows of this VC cross-connect to
turn the traffic flow on.
One-Shot VC Cross-Connect Establishment
A VC cross-connect may also be established in
one step by a set-request with all necessary
parameter values and pxmAtmVcCrossConnectRowStatus
set to createAndGo(4).
In contrast to the negotiated VC cross-connect
establishment which allows for detailed error
checking i.e., set errors are explicitly linked to
particular resource acquisition failures), the
one-shot VC cross-connect establishment
performs the setup on one operation but does
not have the advantage of step-wise error
checking.
VC Cross-Connect Retirement
A VC cross-connect identified by a particular
value of pxmAtmVcCrossConnectIndex is released by:
(1) Setting pxmAtmVcCrossConnectRowStatus of all rows
identified by this value of
pxmAtmVcCrossConnectIndex to destroy(6).
The agent may release all
associated resources, and the
pxmAtmVcCrossConnectIndex values in the
corresponding pxmAtmVclTable row are removed.
Note that a situation when only a subset of
the associated rows are deleted corresponds
to a VC topology change.
(2) After deletion of the appropriate
pxmAtmVcCrossConnectEntries, the manager may
set pxmAtmVclRowStatus to destroy(6) the
associated VCLs. The agent releases
the resources and removes the associated
rows in the pxmAtmVclTable.
VC Cross-Connect Reconfiguration
At the discretion of the agent, a VC
cross-connect may be reconfigured by
adding and/or deleting leafs to/from
the VC topology as per the VC cross-connect
establishment/retirement procedures.
Reconfiguration of traffic/QoS parameter
values requires release of the VC cross-connect
before those parameter values may by changed
for individual VCLs. PxmAtmVcCrossConnectEntry .1.3.6.1.4.1.1954.3.13.16.11.1 |
pxmAtmVcCrossConnectIndexA unique value to identify this VC cross-connect.ro INTEGER .1.3.6.1.4.1.1954.3.13.16.11.1.1 |
pxmAtmVcCrossConnectLowIfIndexThe value of this object is equal to MIB II's
ifIndex value of the ATM interface port for this
VC cross-connect. The term low implies
that this ATM interface has the numerically lower
ifIndex value than the other ATM interface
identified in the same pxmAtmVcCrossConnectEntry.ro INTEGER .1.3.6.1.4.1.1954.3.13.16.11.1.2 |
pxmAtmVcCrossConnectLowVpiThe value of this object is equal to the VPI
value at the ATM interface
associated with the VC cross-connect that is
identified by pxmAtmVcCrossConnectLowIfIndex.
The VPI value cannot exceed the number
supported by the pxmAtmInterfaceMaxVpiBits
at the low ATM interface port.ro INTEGER .1.3.6.1.4.1.1954.3.13.16.11.1.3 |
pxmAtmVcCrossConnectLowVciThe value of this object is equal to the VCI
value at the ATM interface
associated with this VC cross-connect that is
identified by pxmAtmVcCrossConnectLowIfIndex.
The VCI value cannot exceed the number
supported by the pxmAtmInterfaceMaxVciBits
at the low ATM interface port.ro INTEGER .1.3.6.1.4.1.1954.3.13.16.11.1.4 |
pxmAtmVcCrossConnectHighIfIndexThe value of this object is equal to MIB II's
ifIndex value for the ATM interface port for
this VC cross-connect. The term high
implies that this VC cross-connect
that this ATM interface has the numerically higher
ifIndex value than the other ATM interface
identified in the same pxmAtmVcCrossConnectEntry.ro INTEGER .1.3.6.1.4.1.1954.3.13.16.11.1.5 |
pxmAtmVcCrossConnectHighVpiThe value of this object is equal to the VPI
value at the ATM interface
associated with the VC cross-connect that is
identified by pxmAtmVcCrossConnectHighIfIndex.
The VPI value cannot exceed
the number supported by the pxmAtmInterfaceMaxVpiBits
at the high ATM interface port.ro INTEGER .1.3.6.1.4.1.1954.3.13.16.11.1.6 |
pxmAtmVcCrossConnectHighVciThe value of this object is equal to the VCI
value at the ATM interface
associated with the VC cross-connect that is
identified by pxmAtmVcCrossConnectHighIfIndex.
The VCI value cannot exceed
the number supported by the pxmAtmInterfaceMaxVciBits
at the high ATM interface port.ro INTEGER .1.3.6.1.4.1.1954.3.13.16.11.1.7 |
pxmAtmVcCrossConnectAdminStatusThe value of this object identifies the desired
administrative status of this bi-directional
VC cross-connect. The up and down states
indicate that the traffic flow is enabled or
disabled respectively on this VC cross-connect.ro Enumeration .1.3.6.1.4.1.1954.3.13.16.11.1.8 |
pxmAtmVcCrossConnectL2HOperStatusThe value of this object identifies the current
operational status of the VC cross-connect
in one direction; (i.e., from the low to
high direction). The up and down states indicate
that this ATM VC cross-connect from low
to high direction is operational or not
operational respectively. The unknown state
indicates that the state of it cannot be
determined.ro Enumeration .1.3.6.1.4.1.1954.3.13.16.11.1.9 |
pxmAtmVcCrossConnectH2LOperStatusThe value of this object identifies the current
operational status of the VC cross-connect
in one direction; (i.e., from the high to
low direction). The up and down states indicate
that this ATM VC cross-connect from high
to low direction is operational or not
operational respectively. The unknown state
indicates that the state of it cannot be
determined.ro Enumeration .1.3.6.1.4.1.1954.3.13.16.11.1.10 |
pxmAtmVcCrossConnectL2HLastChangeThe value of MIB II's sysUpTime object
at the time this VC cross-connect entered
its current operational state in low to high
direction. If the current state was
entered prior to the last re-initialization of the
agent, then this object contains a zero value.ro INTEGER .1.3.6.1.4.1.1954.3.13.16.11.1.11 |
pxmAtmVcCrossConnectH2LLastChangeThe value of MIB II's sysUpTime object
at the time this VC cross-connect entered
its current operational state in high to low
direction. If the current state was
entered prior to the last re-initialization of the
agent, then this object contains a zero value.ro INTEGER .1.3.6.1.4.1.1954.3.13.16.11.1.12 |
pxmAtmVcCrossConnectRowStatusThe status of this entry in the
pxmAtmVcCrossConnectTable. This object is used to
create a new cross-connect for cross-connecting
VCLs which are created using the pxmAtmVclTable
or to change or delete existing cross-connect.
This object must be initially set to
`createAndWait' or `createAndGo'. This object
cannot be set to `active' unless the following
columnar object exists in this row:
pxmAtmVcCrossConnectAdminStatus.
To turn on a VC cross-connect,
the pxmAtmVcCrossConnectAdminStatus
is set to `up'.ro INTEGER .1.3.6.1.4.1.1954.3.13.16.11.1.13 |
pxmAtmVcCrossConnectHighAddressTypeThe value of this object identifies the address type of the
interface associated with the VC cross-connect that is
identified by pxmAtmVcCrossConnectHighIfIndex. If the address
type is pxmAtmUni, the first 4 bits of the VPI field is the
GFCI and the remaing 12 bits of the VPI field is the VPI. If
the address type is pxmAtmNni, the whole 16 bits of the VPI
is the VPI. If the address type is the frameRelay, the
combination of the VPI field and the VCI field are the DLCI.ro Enumeration .1.3.6.1.4.1.1954.3.13.16.11.1.14 |
pxmAtmVcCrossConnectLowAddressTypeThe value of this object identifies the address type of the
interface associated with the VC cross-connect that is
identified by pxmAtmVcCrossConnectLowIfIndex. If the address
type is pxmAtmUni, the first 4 bits of the VPI field is the
GFCI and the remaing 12 bits of the VPI field is the VPI. If
the address type is pxmAtmNni, the whole 16 bits of the VPI
is the VPI. If the address type is the frameRelay, the
combination of the VPI field and the VCI field are the DLCI.ro Enumeration .1.3.6.1.4.1.1954.3.13.16.11.1.15 |