TN-Y1564-MIB
File:
TN-Y1564-MIB.mib (23813 bytes)
Imported modules
Imported symbols
Defined Types
TnY1564ProfileEntry |
|
SEQUENCE |
|
|
|
|
tnY1564ProfileName |
SnmpAdminString |
|
|
tnY1564ProfileDescription |
DisplayString |
|
|
tnY1564DuelEnded |
TruthValue |
|
|
tnY1564DstOamAware |
TruthValue |
|
|
tnY1564TrafficType |
INTEGER |
|
|
tnY1564MegLevel |
INTEGER |
|
|
tnY1564FrameSize |
INTEGER |
|
|
tnY1564UserFrameSize |
INTEGER |
|
|
tnY1564DwellTime |
INTEGER |
|
|
tnY1564SacFLR |
INTEGER |
|
|
tnY1564SacFTD |
INTEGER |
|
|
tnY1564SacFDV |
INTEGER |
|
|
tnY1564CirEnable |
TruthValue |
|
|
tnY1564CirStepDuration |
INTEGER |
|
|
tnY1564CirDmInterval |
INTEGER |
|
|
tnY1564CirStepCount |
INTEGER |
|
|
tnY1564EirEnable |
TruthValue |
|
|
tnY1564EirDuration |
INTEGER |
|
|
tnY1564EirDmInterval |
INTEGER |
|
|
tnY1564TrafficPolicingEnable |
TruthValue |
|
|
tnY1564TrafficPolicingDuration |
INTEGER |
|
|
tnY1564TrafficPolicingDmInterval |
INTEGER |
|
|
tnY1564PerfTestEnable |
TruthValue |
|
|
tnY1564PerfTestDuration |
INTEGER |
|
|
tnY1564PerfTestUserDuration |
INTEGER |
|
|
tnY1564PerfTestDmInterval |
INTEGER |
|
|
tnY1564ProfileStatus |
RowStatus |
|
TnY1564ReportEntry |
|
SEQUENCE |
|
|
|
|
tnY1564ReportName |
SnmpAdminString |
|
|
tnY1564ReportDscr |
DisplayString |
|
|
tnY1564ReportTime |
DisplayString |
|
|
tnY1564ReportTftpAddrType |
InetAddressType |
|
|
tnY1564ReportTftpAddr |
InetAddress |
|
|
tnY1564ReportTestStatus |
INTEGER |
|
|
tnY1564ReportAction |
INTEGER |
|
Defined Values
tnY1564MIB |
1.3.6.1.4.1.868.2.5.154 |
The MIB provides functionalities for system user management in TN modules. |
MODULE-IDENTITY |
|
|
|
tnY1564ProfileTable |
1.3.6.1.4.1.868.2.5.154.2.1.1 |
This table provides configuration of SOAM Maintenance Point.
|
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
SEQUENCE OF |
|
|
|
|
TnY1564ProfileEntry |
|
tnY1564ProfileEntry |
1.3.6.1.4.1.868.2.5.154.2.1.1.1 |
A entry in the table represents a configuration for local SOAM. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
TnY1564ProfileEntry |
|
|
tnY1564DstOamAware |
1.3.6.1.4.1.868.2.5.154.2.1.1.1.4 |
When set, switch transmits Y.1731 DMM frames for delay measurements
and Y.1731 1DM frames when this is cleared. When Traffic Type is 'Y.1731 OAM',
switch transmits Y.1731 LBM frames as background traffic when DST is
configured as OAM-aware, and Y.1731 TST frames when not. |
Status: current |
Access: read-create |
OBJECT-TYPE |
|
|
|
|
TruthValue |
|
|
tnY1564TrafficType |
1.3.6.1.4.1.868.2.5.154.2.1.1.1.5 |
When set to 'Y.1731 OAM', this switch transmits Y.1731
OAM PDUs as background traffic, and DST is OAM-aware
determines the PDU type. In the current version of the
software, only one ECE can be tested at a time in this mode.
When set to 'Simulated Customer', the software will generate
a traffic-pattern per ECE that will hit the ECE, and use
the ECE's counters to determine PASS/FAIL criteria.Besides
supporting simultaneous test of multiple ECEs,
'Simulated Customer' has the advantage that the tester can
see directly from the report if she has configured ECEs wrongly,
since the report will show per-ECE counters and fail if an ECE
under test is not hit as expected by the traffic pattern. |
Status: current |
Access: read-create |
OBJECT-TYPE |
|
|
|
|
INTEGER |
y1731Oam(1), simCustomer(2) |
|
tnY1564MegLevel |
1.3.6.1.4.1.868.2.5.154.2.1.1.1.6 |
The MEG level used in generated Y.1731 OAM frames (both LBM/TST and DMM/1DM). |
Status: current |
Access: read-create |
OBJECT-TYPE |
|
|
|
|
INTEGER |
one(1), two(2), three(3), four(4), five(5), six(6), seven(7) |
|
tnY1564FrameSize |
1.3.6.1.4.1.868.2.5.154.2.1.1.1.7 |
Selects the frame size of the background traffic. The frame size
does not include possible C-tag(s) added to match the ECE. Besides
standard frame sizes there are two custom selections:
MTU - The UNI's MTU will be used for the background traffic.
User-defined - custom specification of a frame size of the background traffic.
Valid range is 64 to 10236 bytes.
|
Status: current |
Access: read-create |
OBJECT-TYPE |
|
|
|
|
INTEGER |
bytes64(1), bytes128(2), bytes256(3), bytes512(4), bytes1024(5), bytes1280(6), bytes1518(7), mtu(8), userDefined(9) |
|
tnY1564UserFrameSize |
1.3.6.1.4.1.868.2.5.154.2.1.1.1.8 |
User defined frame size of the background traffic.
Valid range is 64 to 10236 bytes.
|
Status: current |
Access: read-create |
OBJECT-TYPE |
|
|
|
|
INTEGER |
64..10236 |
|
tnY1564DwellTime |
1.3.6.1.4.1.868.2.5.154.2.1.1.1.9 |
When a trial (a single step of a subtest) is executed, background
traffic is transmitted for a certain period of time. When that
period has elapsed, the Dwell Time determines how long to wait
before reading hardware counters and status in order to assess
the status of the trial. The required dwell time must be at least
the worst-case roundtrip time, and therefore a.o. depends on the
physical distance between the near and far ends.
Valid range is from 100 to 10000 in steps of 100 milliseconds
with a default of 500 milliseconds.
|
Status: current |
Access: read-create |
OBJECT-TYPE |
|
|
|
|
INTEGER |
|
|
tnY1564SacFLR |
1.3.6.1.4.1.868.2.5.154.2.1.1.1.10 |
Defines the acceptable Frame Loss Ratio.
The Acceptable FLR is measured in permille. Setting this to
1000 effectively disables this check.The number is used in all
enabled subtests. Only delay measurement PDUs and green
background traffic undergoes FLR check. If the number of looped
green frames differs from the number of transmitted green frames
by more than the 'Acceptable FLR', the test is considered failing,
otherwise passing.If the EVC contains multiple ECEs that matches
on the same VLAN ID (UNI ingress) and the EVC uses 'Tx Lookup' equal
to 'VID-PCP', the NNI ingress rules count looped traffic per NNI
outer tag's PCP, and therefore provide more detailed information about
which ECE is failing, than if the EVC uses 'Tx Lookup' equal to 'VID',
where all looped traffic arriving on NNI is counted on the same ECE.
The disadvantage of the 'VID-PCP' method is that it uses more chip
resources than does the 'VID' method.
Valid range is from 0 to 1000 with a default of 0.
|
Status: current |
Access: read-create |
OBJECT-TYPE |
|
|
|
|
INTEGER |
0..1000 |
|
tnY1564SacFTD |
1.3.6.1.4.1.868.2.5.154.2.1.1.1.11 |
Defines the acceptable Frame Transfer Delay, measured in
milliseconds. If the highest observed frame transfer delay
exceeds this, the test fails.
Valid range is from 0 to 10000 with a default of 0 milliseconds.
A value of 0 disables this check.
|
Status: current |
Access: read-create |
OBJECT-TYPE |
|
|
|
|
INTEGER |
0..10000 |
|
tnY1564SacFDV |
1.3.6.1.4.1.868.2.5.154.2.1.1.1.12 |
Defines the acceptable Frame Delay Variation, measured in milliseconds.
If the highest observed frame delay variation exceeds this, the test fails.
Valid range is from 0 to 10000 with a default of 0 milliseconds.
A value of 0 disables this check.
|
Status: current |
Access: read-create |
OBJECT-TYPE |
|
|
|
|
INTEGER |
0..10000 |
|
tnY1564CirEnable |
1.3.6.1.4.1.868.2.5.154.2.1.1.1.13 |
Set, to enable the CIR test. |
Status: current |
Access: read-create |
OBJECT-TYPE |
|
|
|
|
TruthValue |
|
|
tnY1564CirStepDuration |
1.3.6.1.4.1.868.2.5.154.2.1.1.1.14 |
Each step in the CIR configuration test applies background
traffic for this number of seconds.
Valid range is from 1 to 3600 with a default of 10 seconds.
|
Status: current |
Access: read-create |
OBJECT-TYPE |
|
|
|
|
INTEGER |
1..3600 |
|
tnY1564CirDmInterval |
1.3.6.1.4.1.868.2.5.154.2.1.1.1.15 |
A Y.1731 1DM or DMM frame (depending on type of test) is
transmitted every so many milliseconds, in order to perform
delay measurements (DM). The number should be selected so
that at least three DM frames are transmitted during a trial
in order to obtain delay variation results. After each trial
the measured FTD and FDV is compared against the SAC's Acceptable FLR, FTD, and FDV.
Valid range is from 100 to 10000 in steps of 100 milliseconds
with a default of 500 milliseconds.
A value of 0 effectively disables transmission of DM frames,
which thereby indirectly disables the check against the SAC.
|
Status: current |
Access: read-create |
OBJECT-TYPE |
|
|
|
|
INTEGER |
100..10000 |
|
tnY1564CirStepCount |
1.3.6.1.4.1.868.2.5.154.2.1.1.1.16 |
The number of steps (trials) used to reach CIR. If, for example,
Step Count is set to 4, four trials are executed. The first runs
at 25% of this ECEs share of CIR, the second at 50%, then 75%,
and finally 100%. A step count of 1 corresponds to executing
Y.1564's A.1 test (Simple CIR Validation Test). A step count
greater than 1 corresponds to executing Y.1564's A.2 test (Step Load CIR Test).
Valid range is from 1 to 1000 with a default of 4 steps.
|
Status: current |
Access: read-create |
OBJECT-TYPE |
|
|
|
|
INTEGER |
1..1000 |
|
tnY1564EirEnable |
1.3.6.1.4.1.868.2.5.154.2.1.1.1.17 |
Set, to enable the EIR test. |
Status: current |
Access: read-create |
OBJECT-TYPE |
|
|
|
|
TruthValue |
|
|
tnY1564EirDuration |
1.3.6.1.4.1.868.2.5.154.2.1.1.1.18 |
The EIR configuration test is executed in one single trial,
whose duration is configured with this parameter.
Valid range is from 1 to 3600 with a default of 10 seconds.
|
Status: current |
Access: read-create |
OBJECT-TYPE |
|
|
|
|
INTEGER |
1..3600 |
|
tnY1564EirDmInterval |
1.3.6.1.4.1.868.2.5.154.2.1.1.1.19 |
A Y.1731 1DM or DMM frame (depending on type of test) is
transmitted every so many milliseconds, in order to perform
delay measurements (DM). The number should be selected so
that at least three DM frames are transmitted during a trial
in order to obtain delay variation results. After each trial
the measured FTD and FDV is compared against the SAC's Acceptable FLR, FTD, and FDV.
Valid range is from 100 to 10000 in steps of 100 milliseconds
with a default of 500 milliseconds.
A value of 0 effectively disables transmission of DM frames,
which thereby indirectly disables the check against the SAC.
|
Status: current |
Access: read-create |
OBJECT-TYPE |
|
|
|
|
INTEGER |
100..10000 |
|
tnY1564TrafficPolicingDuration |
1.3.6.1.4.1.868.2.5.154.2.1.1.1.21 |
The Traffic Policing test is executed in one single trial,
whose duration is configured with this parameter.
Valid range is from 1 to 3600 with a default of 10 seconds.
|
Status: current |
Access: read-create |
OBJECT-TYPE |
|
|
|
|
INTEGER |
1..3600 |
|
tnY1564TrafficPolicingDmInterval |
1.3.6.1.4.1.868.2.5.154.2.1.1.1.22 |
A Y.1731 1DM or DMM frame (depending on type of test) is
transmitted every so many milliseconds, in order to perform
delay measurements (DM). The number should be selected so
that at least three DM frames are transmitted during a trial
in order to obtain delay variation results. After each trial
the measured FTD and FDV is compared against the SAC's Acceptable FLR, FTD, and FDV.
Valid range is from 100 to 10000 in steps of 100 milliseconds
with a default of 500 milliseconds.
A value of 0 effectively disables transmission of DM frames,
which thereby indirectly disables the check against the SAC.
|
Status: current |
Access: read-create |
OBJECT-TYPE |
|
|
|
|
INTEGER |
100..10000 |
|
tnY1564PerfTestDuration |
1.3.6.1.4.1.868.2.5.154.2.1.1.1.24 |
The performance test is executed in one single trial, whose
duration is configured with this parameter. There are
Y.1564-specified standard durations and a custom duration can be
specified by selecting User-defined Duration option.
|
Status: current |
Access: read-create |
OBJECT-TYPE |
|
|
|
|
INTEGER |
mins15(1), hours2(2), hours24(3), userDefined(4) |
|
tnY1564PerfTestUserDuration |
1.3.6.1.4.1.868.2.5.154.2.1.1.1.25 |
User defined duration. Valid range is from 1 to 86400 with a default of 900 seconds
|
Status: current |
Access: read-create |
OBJECT-TYPE |
|
|
|
|
INTEGER |
1..86400 |
|
tnY1564PerfTestDmInterval |
1.3.6.1.4.1.868.2.5.154.2.1.1.1.26 |
A Y.1731 1DM or DMM frame (depending on type of test) is
transmitted every so many milliseconds, in order to perform
delay measurements (DM). The number should be selected so
that at least three DM frames are transmitted during a trial
in order to obtain delay variation results. After each trial
the measured FTD and FDV is compared against the SAC's Acceptable FLR, FTD, and FDV.
Valid range is from 100 to 10000 in steps of 100 milliseconds
with a default of 500 milliseconds.
A value of 0 effectively disables transmission of DM frames,
which thereby indirectly disables the check against the SAC.
|
Status: current |
Access: read-create |
OBJECT-TYPE |
|
|
|
|
INTEGER |
100..10000 |
|
tnY1564ProfileStatus |
1.3.6.1.4.1.868.2.5.154.2.1.1.1.27 |
The status of the row.
The writable columns in a row can not be changed if the row
is active. All columns must have a valid value before a row
can be activated.
|
Status: current |
Access: read-create |
OBJECT-TYPE |
|
|
|
|
RowStatus |
|
|
tnY1564ReportTable |
1.3.6.1.4.1.868.2.5.154.2.2.1 |
This table provides configuration of SOAM Maintenance Point.
|
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
SEQUENCE OF |
|
|
|
|
TnY1564ReportEntry |
|
tnY1564ReportEntry |
1.3.6.1.4.1.868.2.5.154.2.2.1.1 |
A entry in the table represents a configuration for local SOAM. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
TnY1564ReportEntry |
|
|
tnY1564ReportName |
1.3.6.1.4.1.868.2.5.154.2.2.1.1.1 |
The name, ASCII range 33-126, of this table. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
SnmpAdminString |
|
|
tnY1564ReportDscr |
1.3.6.1.4.1.868.2.5.154.2.2.1.1.2 |
The description of this table. |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
DisplayString |
Size(0..127) |
|
tnY1564ReportTime |
1.3.6.1.4.1.868.2.5.154.2.2.1.1.3 |
The description of this table. |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
DisplayString |
Size(26) |
|
tnY1564ReportTestStatus |
1.3.6.1.4.1.868.2.5.154.2.2.1.1.6 |
|
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
INTEGER |
inactive(1), executing(2), cancelling(3), cancelled(4), passed(5), failed(6) |
|
tnY1564ReportAction |
1.3.6.1.4.1.868.2.5.154.2.2.1.1.7 |
|
Status: current |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
INTEGER |
noAction(1), cancelTest(2), saveReport(3), deleteReport(4) |
|