This list contains the additional AAL5 VCC
performance parameters and is indexed
by ifIndex values of AAL5 interfaces
and the associated VPI/VCI values.
The counter associated with the number of frames that were
discarded due to unsupported protocol encapsulation,
encountered by the AAL5 interface in the current 15 minute
interval.
The counter associated with the number of AAL5 CPCS PDUs
received with CRC-32 errors, encountered by the AAL5
interface in the current 15 minute interval.
The counter associated with the number of
dropped frames due to congestion, encountered by
the AAL5 interface on the Receive direction
in the current 15 minute interval.
The counter associated with the number of
dropped frames due to congestion, encountered by
the AAL5 interface on the Transmit direction
in the current 15 minute interval.
A number between 1 and 96, where 1 is the most
recently completed 15 minute interval and 96 is
the least recently completed 15 minutes interval
(assuming that all 96 intervals exist).
The counter associated with the number of received frames,
encountered by the AAL5 interface in one of the previous
96, individual 15 minute, intervals.
The counter associated with the number of transmitted frames,
encountered by the AAL5 interface in in one of the previous
96, individual 15 minute, intervals.
The counter associated with the number of frames that were
discarded due to unsupported protocol encapsulation,
encountered by the AAL5 interface in one of the previous
96, individual 15 minute, intervals.
The counter associated with the number of AAL5 CPCS PDUs
received with CRC-32 errors, encountered by the AAL5
interface in one of the previous 96, individual 15 minute,
intervals.
The counter associated with the number of received frames
with length error, encountered by the AAL5 interface in one
of the previous 96, individual 15 minute, intervals.
The counter associated with the number of dropped frames
due to a congestion, encountered by the AAL5 interface on
the Receive direction in one of the previous 96, individual
15 minute, intervals
The counter associated with the number of dropped frames
due to a congestion, encountered by the AAL5 interface on
the Transmit direction in one of the previous 96, individual
15 minute, intervals
The counter associated with the number of Discarded
cells due to wrong sequence number, encountered
by an AAL1 interface in the current 15 minute interval.
The counter associated with the number of Discarded
cells due to bad AAL1 header error (including correctable
and uncorrectable CRC, and bad parity), encountered
by an AAL1 interface in the current 15 minute interval.
The counter associated with the number of events in
which a SDT pointer isn't where it is expected to be,
and must be reacquired, encountered by an AAL1 interface
in the current 15 minute interval.
A number between 1 and 96, where 1 is the most
recently completed 15 minute interval and 96 is
the least recently completed 15 minutes interval
(assuming that all 96 intervals exist).
The counter associated with the number of Discarded
cells due to wrong sequence number, encountered
by an AAL1 interface in one of the previous 96,
individual 15 minute, intervals.
The counter associated with the number of Discarded
cells due to bad AAL1 header error (including correctable
and uncorrectable CRC, plus bad parity), encountered
by an AAL1 interface in one of the previous 96,
individual 15 minute, intervals.
The counter associated with the number of events in
which a SDT pointer isn't where it is expected to be,
and must be reacquired, encountered by an AAL1 interface
in one of the previous 96, individual 15 minute,
intervals.
The counter associated with the number of buffer
underflow events, encountered by an AAL1 interface
in one of the previous 96, individual 15 minute,
intervals.
The counter associated with the number of buffer
overflow events, encountered by an AAL1 interface
in one of the previous 96, individual 15 minute,
intervals.
This parameter defines if to use Spaced or Normal CBR.
Normal - TD will be allocated from the policing range (described
in ACE2002 NMS SRS). The PCR is expanded with a constant
value of 30 cell/sec.
Spaced - TD will be allocated from the spacing range (described
in ACE2002 NMS SRS). The PCR and CDVT will be expanded
as described for Normal, and the CES traffic including
the OAM will be spaced out at the TD's PCR.
This mode is used to prevent CDVT violation due to OAM
cell insertion with the CES traffic.
This object indicates the Idx of the Config being accessed.
Idx of 255 relates to the Temporary (Scratch) Config.
For products that support several configurations,
Set can be performed only to the Temporary Config (=255).
This parameter controls transmision mode:
Echo Cancellation is required when both ATU-C an ATU-R use
the same frequency.
Frequency Division (different frequency ranges for ATU-C
and ATU-R) may limit data rate.
This parameter controls Transmit Start Bin number.
For ADSL Annex A - range of values is 6 to 31.
For ADSL Annex B - range of values is 33 to 63.
Frequency (in khz unit) is calculated by multiplying this
parameter value by bin bandwidth (4Khz)
This parameter controls Transmit End Bin number.
For ADSL Annex A - range of values is 6 to 31.
For ADSL Annex B - range of values is 33 to 63.
requency (in khz unit) is calculated by multiplying this
value by bin bandwidth (4Khz)
This parameter controls Receive Start Bin number.
Range of values for this parameter depends on ADSL Annex supported,
and transmisson mode (adslTransmissionMode) selected:
ADSL Annex A and Echo Cancellation (EC) : 6 to 255
ADSL Annex A and Frequency Division (FDM) : 32 to 255
ADSL Annex B and Echo Cancellation (EC) : 33 to 255
ADSL Annex B and Frequency Division (FDM) : 64 to 255
Frequency (in khz unit) is calculated by multiplying this
value by bin bandwidth (4Khz)
This parameter controls Receive End Bin number.
Range of values for this parameter depends on ADSL Annex supported,
and transmisson mode (adslTransmissionMode) selected:
ADSL Annex A and Echo Cancellation (EC) : 6 to 255
ADSL Annex A and Frequency Division (FDM) : 32 to 255
ADSL Annex B and Echo Cancellation (EC) : 33 to 255
ADSL Annex B and Frequency Division (FDM) : 64 to 255
Frequency (in khz unit) is calculated by multiplying this
value by bin bandwidth (4Khz)
This object indicates the Idx of the Config being accessed.
Idx of 255 relates to the Temporary (Scratch) Config.
For products that support several configurations, Set can be performed
only to the Temporary Config (=255).
This table is an extension of hdsl2ShdslEndpointCurrTable of rfc3276
It contains current status and performance information
for segment endpoints in HDSL2/SHDSL Lines. As with other
tables in this MIB indexed by ifIndex, entries in this table
MUST be maintained in a persistent manner.
An entry in the shdslEndpointCurrTable. Each entry
contains status and performance information relating to a
single segment endpoint. It is indexed by the ifIndex of the
HDSL2/SHDSL line, the UnitId of the associated unit, the side
of the unit, and the wire-pair of the associated modem.
The time (in hundredths of a second) since the
accumulated counters were last re-initialized:
Accumulated counters are hdsl2ShdslEndpointES,
hdsl2ShdslEndpointSES, hdsl2ShdslEndpointCRCanomalies
hdsl2ShdslEndpointLOSWS, and hdsl2ShdslEndpointUAS.
This table supports maintenance operations (eg. loopbacks)
to be performed on HDSL2/SHDSL segment endpoints. This table
contains live data from equipment. As such, it is NOT
persistent.
An entry in the hdsl2ShdslEndpointMaintTable. Each entry
corresponds to a single segment endpoint, and is indexed by the
ifIndex of the HDSL2/SHDSL line, the UnitId of the associated
unit and the side of the unit.
This object configures the receiver at the associated
segment endpoint to operate in default or enhanced power
backoff mode.
powerbackoff may also be disabled
This table supports definitions of span configuration
profiles for SHDSL lines. HDSL2 does not support these
configuration options. This table MUST be maintained
in a persistent manner.
Each entry corresponds to a single span configuration
profile. Each profile contains a set of span configuration
parameters. The configuration parameters in a profile are
applied to those lines referencing that profile (see the
hdsl2ShdslSpanConfProfile object). Profiles may be
created/deleted using the row creation/deletion mechanism
via hdsl2ShdslSpanConfProfileRowStatus. If an active
entry is referenced in hdsl2ShdslSpanConfProfile, the
entry MUST remain active until all references are removed.
This object indicates line rate when
rfc3276.hdsl2ShdslSpanConfPSD value is asymmetric(2).
Seleceted rate depends on transmission mode -
specified in Annex A or B of G.991.2.
For Annex A;
R1 selects the 776 or 784 kbit/s
R2 selects the 1544 or 1552 kbit/s
For Annex B ;
R1 selects the 2312 kbit/s
R2 selects the 2056 kbit/s
This table enables configuration of HDSL2/SHDSL interfaces
per configuration index.
Write operation for products supporting Active+Temp configurations,
is possible only on the Temp configuration(255).
This object indicates the Idx of the Config being accessed.
Idx of 255 relates to the Temporary (Scratch) Config.
Write operation for products supporting Active+Temp configurations,
is allowed to Temporary configuration only.
Maximum BW (Bandwidth) of the Shdsl Line, in Kbps units.
Respective Max No. of TSs = Max. Rate/64
This object can be Set only for a Central (xtuC) unit.
This object configures the receiver at the associated
segment endpoint to enable/disable power backoff mode.
This object is similar to hdsl2ShdslMaintPowerBackOff, but per
configuration. Therefore, the order of the enum values is the same.
This object configures the way TS0 will be treated over the SHDSL Line.
looped - looped inside
transparent - sent transparently over the DSL Line.
This object can be Set only for a Central (xtuC) unit.
This object configures how TSs will be compacted over the SHDSL Line.
In both mapping cases (2),(3), only the TSs connected on the E1 line will be
transferred over the SHDSL Line
noCompaction - the whole E1 BW is reserved on the SHDSL Line,
even if only part of the TSs are actually connected.
noMapping - there is no mapping between the E1 TSs and the SHDSL frame TSs.
Therefore, E1 connected TSs are ordered in ascending order (e.g
E1 TSs 2, 16, 20 will occupy places 1, 2, 3 in SHDSL Line).
In this case, if user wants to add connection for
a TS that is lower than the existing ones on SHDSL,
the TSs that are higher will have to move.
That causes breaks in service for the moved TSs.
(e.g if E1 TS8 is added in the above case,
TSs 16 and 20 will move, so that by the
end of this process, the E1 TSs 2, 8, 16, 20 will
be ordered in SHDSL frame as 1, 2, 3, 4).
withMapping - there is a mapping between the E1 TSs and the SHDSL frame TSs.
Therefore, if some TSs were connected and then user wants to add
additional E1 TSs, there is no need to move the existing TSs of the
SHDSL frame. The additional TSs will be added AFTER the existing ones,
or in gaps created by E1 TSs removed by user. The main thing is that
the existing TSs will NOT be moved and so, their service will not be
damaged by the addition or removal of E1 TS connections.
lowTsMapping - the first 2 TSs are used for Signaling (TS16) and Dedicated TS
if relevant. The payload starts afterwards, unmapped (according to
E1 connected TSs order). This will ensure that Signaling and
Dedicated TS will continue to function also when new TSs are
connected. User will still get service breaks when TSs are moved.
spareMapping - applicable only for MP-2100/2104 cards. It should be selected only
when working vs. a MP-2100.2104. It resembles the noMapping option,
but it contains Spare TSs for unconnected TSs. These Spare TSs
will prevent service breaks upon added connections, because these
will be selected from the Spare existing TSs.
This table allows user to define several
WFQ tables per output port.
WFQ supports flows with different bandwidth requirements
by giving each queue a weight that assigns it
a different percentage of output port bandwidth.
When Weighted Fair Queuing is used,
it is possible to precisely attribute bandwidth
partitioning among the queues.
When there is congestion, each class (queue)
is not allowed to use more bandwidth than the amount
allocated to it.
This object indicates the Idx of the Agent Cnfg the following
objects refer.
255=Temporary Cnfg (when relevant,
Set is done only to this configuration).
For Agents that support only one configuration,
this object will be constant=1.
This object indicates a unique port or interface number,
for which Weighted Fair Queueing table is applicable .
For numbering, see product's spec.
For some products, the numbering can equal ifIndex.
Value of 255 (not applicable) refer to system level queue
This object indicates which Weighted Fair Queueing (WFQ)
Table is being used. There can be several tables.
For FCD-155 User will select which one will be used
for a virtual concatenation group.Valid values are 1,2
This object indicates a queue index.
For FCD-155, valid queues are 1..3.
The 4th queue is not in MIB.
Its weight will be RO, Calculated according to
the sum of the 3 first queues.
This object indicates a relative weight value.
User should make sure that the sum of
values for all queues will not exceed 100%
(sum should be BELOW 100% in order
to leave some BW percentage for last queue)
This object indicates the Idx of the Agent Cnfg the following
objects refer to.
255=Temporary Cnfg (when relevant, Set is done only
to this configuration).
For Agents that support only one configuration,
this object will be constant=1.
This object can be used to carry additional indexing
(e.g port index) when needed.
The time (in seconds) that passes until an
entry is deleted, unless this entry
was previously updated by a new inATMARP
request or response.
This variable value should be greater than
the value of radAtmRtrInAtmArpInterval,
so that the entry won't be deleted before
an InATMARP request was sent.
Voice port ringing cadence configuration table.
Each ringing cycle, indexed by voiceIfCadenceIdx,
consists of a number of ring ON-Period/ring OFF-Period
pairs. Pairs are indexed sequentially, according to
voiceIfCadencePeriodIdx: 1,2,...number of pairs
This object indicates the Idx of the
Agent Cnfg the following objects refer to.
255=Temporary Cnfg (when relevant,
Set is done only to this configuration).
For Agents that support only one configuration,
this object will be constant=1.
Periods index (pair number) in a ringing cycle Cadence.
This index must be sequential, start from 1. Its maximum
value is the number of pairs of certain ringing type.
For Vmux-110, one or two period pairs may be defined.
This attribute allows to create/delete
ringing cadence entry in this table.
For Vmux-110, only a single cadance can be defined.
Delete action of a period entry can be performed only
if it is the last existing period of the cadance.
This object indicates the Idx of the
Agent Cnfg the following objects refer to.
255=Temporary Cnfg (when relevant,
Set is done only to this configuration).
For Agents that support only one configuration,
this object will be constant=1.
Octet String.
Nibble No. 1 represents ON Hook (same for Rx and Tx).
Nibble No. 2 represents OFF Hook (same for Rx and Tx).
Nibble No. 3 represents Reverse Polarity.
Nibble No. 4 represents Ring pattern 1.
Nibble No. 5 represents Ring pattern 2.
Nibble No. 6 is not used.
The bits will be as following:
Bit 1 = Bit A - ON Hook (LSB)
Bit 2 = Bit B - ON Hook
Bit 3 = Bit C - ON Hook
Bit 4 = Bit D - ON Hook
Bit 5 = Bit A - OFF Hook
Bit 6 = Bit B - OFF Hook
Bit 7 = Bit C - OFF Hook
Bit 8 = Bit D - OFF Hook
Bit 9 = Bit A - Reverse Polarity
Bit 10 = Bit B - Reverse Polarity
Bit 11 = Bit C - Reverse Polarity
Bit 12 = Bit D - Reverse Polarity
Bit 13 = Bit A - Ring 1
Bit 14 = Bit B - Ring 1
Bit 15 = Bit C - Ring 1
Bit 16 = Bit D - Ring 1
Bit 17 = Bit A - Ring 2
Bit 18 = Bit B - Ring 2
Bit 19 = Bit C - Ring 2
Bit 20 = Bit D - Ring 2
Bits 21...24 = 0 (not used). (Bit 24 is MSB).
For Vmux-110:
Ring 1 and Ring 2 are used. The default is 3 octets.
(MSB) 0000 1011 1011 1001 1011 1010 (LSB)