RFC 3728
Definitions of Managed Objects for Very High Speed Digital Subscriber Lines (VDSL)
vdslLineConfDownPsdTemplate OBJECT-TYPE
SYNTAX INTEGER
{
templateMask1(1),
templateMask2(2)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The downstream PSD template to be used for the line.
Here, templateMask1(1) refers to a notched mask that
limits the transmitted PSD within the internationally
standardized HAM (Handheld Amateur Radio) radio bands,
while templateMask2(2) refers to an unnotched mask.
The masks themselves depend upon the applicable
standard being used (vdslLineConfApplicableStandard)."
REFERENCE "DSL TR-057"
DEFVAL { templateMask1 }
::= { vdslLineConfProfileEntry 35 }
vdslLineConfHamBandMask OBJECT-TYPE
SYNTAX BITS
{
customNotch1(0), -- custom (region-specific) notch
customNotch2(1), -- custom (region-specific) notch
amateurBand30m(2), -- amateur radio band notch
amateurBand40m(3), -- amateur radio band notch
amateurBand80m(4), -- amateur radio band notch
amateurBand160m(5) -- amateur radio band notch
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The transmit power spectral density mask code, used
to avoid interference with HAM (Handheld Amateur Radio)
radio bands by introducing power control (notching) in one
or more of these bands.
Amateur radio band notching is defined in the VDSL
spectrum as follows:
Band Start Frequency Stop Frequency
---- ------------------ --------------------------------
30m 1810 kHz 2000 kHz
40m 3500 kHz 3800 kHz (ETSI); 4000 kHz (ANSI)
80m 7000 kHz 7100 kHz (ETSI); 7300 kHz (ANSI)
160m 10100 kHz 10150 kHz
Notching for each standard band can be enabled or disabled
via the bit mask.
Two custom notches may be specified. If either of these
are enabled via the bit mask, then the following objects
MUST be specified:
If customNotch1 is enabled, then both
vdslLineConfCustomNotch1Start
vdslLineConfCustomNotch1Stop
MUST be specified.
If customNotch2 is enabled, then both
vdslLineConfCustomNotch2Start
vdslLineConfCustomNotch2Stop
MUST be specified."
REFERENCE "DSLF TR-057, section 2.6"
DEFVAL { { } }
::= { vdslLineConfProfileEntry 36 }
vdslLineConfCustomNotch1Start OBJECT-TYPE
SYNTAX Unsigned32
UNITS "kHz"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Specifies the start frequency of custom HAM (Handheld
Amateur Radio) notch 1. vdslLineConfCustomNotch1Start MUST
be less than or equal to vdslLineConfCustomNotch1Stop."
DEFVAL { 0 }
::= { vdslLineConfProfileEntry 37 }
vdslLineConfCustomNotch1Stop OBJECT-TYPE
SYNTAX Unsigned32
UNITS "kHz"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Specifies the stop frequency of custom HAM (Handheld
Amateur Radio) notch 1. vdslLineConfCustomNotch1Stop MUST
be greater than or equal to vdslLineConfCustomNotch1Start."
DEFVAL { 0 }
::= { vdslLineConfProfileEntry 38 }
vdslLineConfCustomNotch2Start OBJECT-TYPE
SYNTAX Unsigned32
UNITS "kHz"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Specifies the start frequency of custom HAM (Handheld
Amateur Radio) notch 2. vdslLineConfCustomNotch2Start MUST
be less than or equal to vdslLineConfCustomNotch2Stop."
DEFVAL { 0 }
::= { vdslLineConfProfileEntry 39 }
vdslLineConfCustomNotch2Stop OBJECT-TYPE
SYNTAX Unsigned32
UNITS "kHz"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Specifies the stop frequency of custom HAM (Handheld
Amateur Radio) notch 2. vdslLineConfCustomNotch2Stop MUST
be greater than or equal to vdslLineConfCustomNotch2Start."
DEFVAL { 0 }
::= { vdslLineConfProfileEntry 40 }
vdslLineConfDownTargetSlowBurst OBJECT-TYPE
SYNTAX Unsigned32 (0..1275)
UNITS "microseconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Specifies the target level of impulse noise (burst)
protection for an interleaved (slow) channel."
REFERENCE "ITU-T G.997.1, section 7.3.2.3"
DEFVAL { 0 }
::= { vdslLineConfProfileEntry 41 }
vdslLineConfUpTargetSlowBurst OBJECT-TYPE
SYNTAX Unsigned32 (0..1275)
UNITS "microseconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Specifies the target level of impulse noise (burst)
protection for an interleaved (slow) channel."
REFERENCE "ITU-T G.997.1, section 7.3.2.3"
DEFVAL { 0 }
::= { vdslLineConfProfileEntry 42 }
vdslLineConfDownMaxFastFec OBJECT-TYPE
SYNTAX Unsigned32 (0..50)
UNITS "%"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This parameter provisions the maximum level of Forward
Error Correction (FEC) redundancy related overhead to
be maintained for a fast channel."
DEFVAL { 0 }
::= { vdslLineConfProfileEntry 43 }
vdslLineConfUpMaxFastFec OBJECT-TYPE
SYNTAX Unsigned32 (0..50)
UNITS "%"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This parameter provisions the maximum level of Forward
Error Correction (FEC) redundancy related overhead to
be maintained for a fast channel."
DEFVAL { 0 }
::= { vdslLineConfProfileEntry 44 }
vdslLineConfLineType OBJECT-TYPE
SYNTAX INTEGER
{
noChannel(1), -- no channels exist
fastOnly(2), -- only fast channel exists
interleavedOnly(3), -- only interleaved channel exists
fastOrInterleaved(4), -- either fast or interleaved channel
-- exist, but only one at a time
fastAndInterleaved(5) -- both fast and interleaved channels
-- exist
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This parameter provisions the VDSL physical entity at
start-up by defining whether and how the line will be
channelized, i.e., which channel type(s) are supported.
If the line is to be channelized, the value will be other
than noChannel(1).
This configuration can be activated only during start-up.
Afterwards, the value of vdslLineType coincides with the
value of vdslLineConfLineType. Depending on this value,
the corresponding entries in the ifTable for the
interleaved and the fast channels are enabled or disabled
according to the value of their ifOperStatus.
Defined values are:
noChannel(1) -- no channels exist
fastOnly(2) -- only fast channel exists
interleavedOnly(3) -- only interleaved channel exists
fastOrInterleaved(4) -- either fast or interleaved channel
-- exists, but only one at a time
fastAndInterleaved(5) -- both fast and interleaved channels
-- exist
Note that 'slow' and 'interleaved' refer to the same
channel."
REFERENCE "T1E1.4/2000-009R3, Part 1, common spec"
DEFVAL { noChannel }
::= { vdslLineConfProfileEntry 45 }
vdslLineConfProfRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object is used to create a new row or modify or
delete an existing row in this table.
A profile activated by setting this object to 'active'.
When 'active' is set, the system will validate the profile.
Before a profile can be deleted or taken out of service
(by setting this object to 'destroy' or 'outOfService'),
it must be first unreferenced from all associated lines.
An 'active' profile may be modified at any time. Note
that some changes may require that any referenced lines be
restarted (e.g., vdslLineConfLineType)."
::= { vdslLineConfProfileEntry 46 }
--
-- Alarm configuration profile table
--
vdslLineAlarmConfProfileTable OBJECT-TYPE
SYNTAX SEQUENCE OF VdslLineAlarmConfProfileEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains information on the VDSL line alarm
configuration. One entry in this table reflects a profile
defined by a manager which can be used to configure the
VDSL line alarm thresholds.
Entries in this table MUST be maintained in a
persistent manner."
::= { vdslMibObjects 20 }
vdslLineAlarmConfProfileEntry OBJECT-TYPE
SYNTAX VdslLineAlarmConfProfileEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Each entry consists of a list of parameters that
represents the configuration of a VDSL line alarm
profile.
A default profile with an index of 'DEFVAL', will
always exist and its parameters will be set to vendor
specific values, unless otherwise specified in this
document."
INDEX { vdslLineAlarmConfProfileName }
::= { vdslLineAlarmConfProfileTable 1 }
VdslLineAlarmConfProfileEntry ::=
SEQUENCE
{
vdslLineAlarmConfProfileName SnmpAdminString,
vdslLineAlarmConfThresh15MinLofs HCPerfIntervalThreshold,
vdslLineAlarmConfThresh15MinLoss HCPerfIntervalThreshold,
vdslLineAlarmConfThresh15MinLprs HCPerfIntervalThreshold,
vdslLineAlarmConfThresh15MinLols HCPerfIntervalThreshold,
vdslLineAlarmConfThresh15MinESs HCPerfIntervalThreshold,
vdslLineAlarmConfThresh15MinSESs HCPerfIntervalThreshold,
vdslLineAlarmConfThresh15MinUASs HCPerfIntervalThreshold,
vdslLineAlarmConfInitFailure TruthValue,
vdslLineAlarmConfProfRowStatus RowStatus
}
vdslLineAlarmConfProfileName OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (1..32))
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The name for this profile as specified by an
administrator."
::= { vdslLineAlarmConfProfileEntry 1 }
vdslLineAlarmConfThresh15MinLofs OBJECT-TYPE
SYNTAX HCPerfIntervalThreshold
UNITS "seconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object configures the threshold for the number of
loss of frame seconds (lofs) within any given 15-minute
performance data collection interval. If the value of
loss of frame seconds in a particular 15-minute collection
interval reaches/exceeds this value, a
vdslPerfLofsThreshNotification notification will be
generated. No more than one notification will be sent
per interval."
DEFVAL { 0 }
::= { vdslLineAlarmConfProfileEntry 2 }
vdslLineAlarmConfThresh15MinLoss OBJECT-TYPE
SYNTAX HCPerfIntervalThreshold
UNITS "seconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object configures the threshold for the number of
loss of signal seconds (loss) within any given 15-minute
performance data collection interval. If the value of
loss of signal seconds in a particular 15-minute
collection interval reaches/exceeds this value, a
vdslPerfLossThreshNotification notification will be
generated. One notification will be sent per interval
per endpoint."
DEFVAL { 0 }
::= { vdslLineAlarmConfProfileEntry 3 }
vdslLineAlarmConfThresh15MinLprs OBJECT-TYPE
SYNTAX HCPerfIntervalThreshold
UNITS "seconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object configures the threshold for the number of
loss of power seconds (lprs) within any given 15-minute
performance data collection interval. If the value of
loss of power seconds in a particular 15-minute collection
interval reaches/exceeds this value, a
vdslPerfLprsThreshNotification notification will be
generated. No more than one notification will be sent
per interval."
DEFVAL { 0 }
::= { vdslLineAlarmConfProfileEntry 4 }
vdslLineAlarmConfThresh15MinLols OBJECT-TYPE
SYNTAX HCPerfIntervalThreshold
UNITS "seconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object configures the threshold for the number of
loss of link seconds (lols) within any given 15-minute
performance data collection interval. If the value of
loss of power seconds in a particular 15-minute collection
interval reaches/exceeds this value, a
vdslPerfLolsThreshNotification notification will be
generated. No more than one notification will be sent
per interval."
DEFVAL { 0 }
::= { vdslLineAlarmConfProfileEntry 5 }
vdslLineAlarmConfThresh15MinESs OBJECT-TYPE
SYNTAX HCPerfIntervalThreshold
UNITS "seconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object configures the threshold for the number of
errored seconds (ESs) within any given 15-minute
performance data collection interval. If the value of
errored seconds in a particular 15-minute collection
interval reaches/exceeds this value, a
vdslPerfESsThreshNotification notification will be
generated. No more than one notification will be sent
per interval."
DEFVAL { 0 }
::= { vdslLineAlarmConfProfileEntry 6 }
vdslLineAlarmConfThresh15MinSESs OBJECT-TYPE
SYNTAX HCPerfIntervalThreshold
UNITS "seconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object configures the threshold for the number of
severely errored seconds (SESs) within any given 15-minute
performance data collection interval. If the value of
severely errored seconds in a particular 15-minute
collection interval reaches/exceeds this value, a
vdslPerfSESsThreshNotification notification will be
generated. No more than one notification will be sent
per interval."
DEFVAL { 0 }
::= { vdslLineAlarmConfProfileEntry 7 }
vdslLineAlarmConfThresh15MinUASs OBJECT-TYPE
SYNTAX HCPerfIntervalThreshold
UNITS "seconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object configures the threshold for the number of
unavailable seconds (UASs) within any given 15-minute
performance data collection interval. If the value of
unavailable seconds in a particular 15-minute collection
interval reaches/exceeds this value, a
vdslPerfUASsThreshNotification notification will be
generated. No more than one notification will be sent
per interval."
DEFVAL { 0 }
::= { vdslLineAlarmConfProfileEntry 8 }
vdslLineAlarmConfInitFailure OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object specifies if a vdslInitFailureNotification
notification will be generated if an initialization
failure occurs."
DEFVAL { false }
::= { vdslLineAlarmConfProfileEntry 9 }
vdslLineAlarmConfProfRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object is used to create a new row or modify or
delete an existing row in this table.
A profile activated by setting this object to 'active'.
When 'active' is set, the system will validate the profile.
Before a profile can be deleted or taken out of service,
(by setting this object to 'destroy' or 'outOfService') it
must be first unreferenced from all associated lines.
An 'active' profile may be modified at any time."
::= { vdslLineAlarmConfProfileEntry 10 }
-- Notification definitions
vdslNotifications OBJECT IDENTIFIER ::= { vdslLineMib 0 }
vdslPerfLofsThreshNotification NOTIFICATION-TYPE
OBJECTS {
vdslPerfDataCurr15MinLofs
}
STATUS current
DESCRIPTION
"Loss of Framing 15-minute interval threshold
(vdslLineAlarmConfThresh15MinLofs) reached."
::= { vdslNotifications 1 }
vdslPerfLossThreshNotification NOTIFICATION-TYPE
OBJECTS {
vdslPerfDataCurr15MinLoss
}
STATUS current
DESCRIPTION
"Loss of Signal 15-minute interval threshold
(vdslLineAlarmConfThresh15MinLoss) reached."
::= { vdslNotifications 2 }
vdslPerfLprsThreshNotification NOTIFICATION-TYPE
OBJECTS {
vdslPerfDataCurr15MinLprs
}
STATUS current
DESCRIPTION
"Loss of Power 15-minute interval threshold
(vdslLineAlarmConfThresh15MinLprs) reached."
::= { vdslNotifications 3 }
vdslPerfLolsThreshNotification NOTIFICATION-TYPE
OBJECTS {
vdslPerfDataCurr15MinLols
}
STATUS current
DESCRIPTION
"Loss of Link 15-minute interval threshold
(vdslLineAlarmConfThresh15MinLols) reached."
::= { vdslNotifications 4 }
vdslPerfESsThreshNotification NOTIFICATION-TYPE
OBJECTS {
vdslPerfDataCurr15MinESs
}
STATUS current
DESCRIPTION
"Errored Seconds 15-minute interval threshold
(vdslLineAlarmConfThresh15MinESs) reached."
::= { vdslNotifications 5 }
vdslPerfSESsThreshNotification NOTIFICATION-TYPE
OBJECTS {
vdslPerfDataCurr15MinSESs
}
STATUS current
DESCRIPTION
"Severely Errored Seconds 15-minute interval threshold
(vdslLineAlarmConfThresh15MinSESs) reached."
::= { vdslNotifications 6 }
vdslPerfUASsThreshNotification NOTIFICATION-TYPE
OBJECTS {
vdslPerfDataCurr15MinUASs
}
STATUS current
DESCRIPTION
"Unavailable Seconds 15-minute interval threshold
(vdslLineAlarmConfThresh15MinUASs) reached."
::= { vdslNotifications 7 }
vdslDownMaxSnrMgnNotification NOTIFICATION-TYPE
OBJECTS {
vdslPhysCurrSnrMgn
}
STATUS current
DESCRIPTION
"The downstream Signal to Noise Margin exceeded
vdslLineConfDownMaxSnrMgn. The object
vdslPhysCurrSnrMgn will contain the Signal to Noise
margin as measured by the VTU-R."
::= { vdslNotifications 8 }
vdslDownMinSnrMgnNotification NOTIFICATION-TYPE
OBJECTS {
vdslPhysCurrSnrMgn
}
STATUS current
DESCRIPTION
"The downstream Signal to Noise Margin fell below
vdslLineConfDownMinSnrMgn. The object vdslPhysCurrSnrMgn
will contain the Signal to Noise margin as measured by
the VTU-R."
::= { vdslNotifications 9 }
vdslUpMaxSnrMgnNotification NOTIFICATION-TYPE
OBJECTS {
vdslPhysCurrSnrMgn
}
STATUS current
DESCRIPTION
"The upstream Signal to Noise Margin exceeded
vdslLineConfUpMaxSnrMgn. The object vdslPhysCurrSnrMgn
will contain the Signal to Noise margin as measured
by the VTU-C."
::= { vdslNotifications 10 }
vdslUpMinSnrMgnNotification NOTIFICATION-TYPE
OBJECTS {
vdslPhysCurrSnrMgn
}
STATUS current
DESCRIPTION
"The upstream Signal to Noise Margin fell below
vdslLineConfUpMinSnrMgn. The object vdslPhysCurrSnrMgn
will contain the Signal to Noise margin as measured
by the VTU-C."
::= { vdslNotifications 11 }
vdslInitFailureNotification NOTIFICATION-TYPE
OBJECTS {
vdslPhysCurrStatus
}
STATUS current
DESCRIPTION
"Vtu initialization failed. See vdslPhysCurrStatus for
potential reasons."
::= { vdslNotifications 12 }
-- conformance information
vdslConformance OBJECT IDENTIFIER ::= { vdslLineMib 3 }
vdslGroups OBJECT IDENTIFIER ::= { vdslConformance 1 }
vdslCompliances OBJECT IDENTIFIER ::= { vdslConformance 2 }
vdslLineMibCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SNMP entities which
manage VDSL interfaces."
MODULE -- this module
MANDATORY-GROUPS
{
vdslGroup,
vdslNotificationGroup
}
::= { vdslCompliances 1 }
-- units of conformance
vdslGroup OBJECT-GROUP
OBJECTS
{
vdslLineCoding,
vdslLineType,
vdslLineConfProfile,
vdslLineAlarmConfProfile,
vdslPhysInvSerialNumber,
vdslPhysInvVendorID,
vdslPhysInvVersionNumber,
vdslPhysCurrSnrMgn,
vdslPhysCurrAtn,
vdslPhysCurrStatus,
vdslPhysCurrOutputPwr,
vdslPhysCurrAttainableRate,
vdslPhysCurrLineRate,
vdslChanInterleaveDelay,
vdslChanCrcBlockLength,
vdslChanCurrTxRate,
vdslChanCurrTxSlowBurstProtect,
vdslChanCurrTxFastFec,
vdslPerfDataValidIntervals,
vdslPerfDataInvalidIntervals,
vdslPerfDataLofs,
vdslPerfDataLoss,
vdslPerfDataLprs,
vdslPerfDataLols,
vdslPerfDataESs,
vdslPerfDataSESs,
vdslPerfDataUASs,
vdslPerfDataInits,
vdslPerfDataCurr15MinTimeElapsed,
vdslPerfDataCurr15MinLofs,
vdslPerfDataCurr15MinLoss,
vdslPerfDataCurr15MinLprs,
vdslPerfDataCurr15MinLols,
vdslPerfDataCurr15MinESs,
vdslPerfDataCurr15MinSESs,
vdslPerfDataCurr15MinUASs,
vdslPerfDataCurr15MinInits,
vdslPerfData1DayValidIntervals,
vdslPerfData1DayInvalidIntervals,
vdslPerfDataCurr1DayTimeElapsed,
vdslPerfDataCurr1DayLofs,
vdslPerfDataCurr1DayLoss,
vdslPerfDataCurr1DayLprs,
vdslPerfDataCurr1DayLols,
vdslPerfDataCurr1DayESs,
vdslPerfDataCurr1DaySESs,
vdslPerfDataCurr1DayUASs,
vdslPerfDataCurr1DayInits,
vdslPerfIntervalLofs,
vdslPerfIntervalLoss,
vdslPerfIntervalLprs,
vdslPerfIntervalLols,
vdslPerfIntervalESs,
vdslPerfIntervalSESs,
vdslPerfIntervalUASs,
vdslPerfIntervalInits,
vdslPerf1DayIntervalMoniSecs,
vdslPerf1DayIntervalLofs,
vdslPerf1DayIntervalLoss,
vdslPerf1DayIntervalLprs,
vdslPerf1DayIntervalLols,
vdslPerf1DayIntervalESs,
vdslPerf1DayIntervalSESs,
vdslPerf1DayIntervalUASs,
vdslPerf1DayIntervalInits,
vdslChanValidIntervals,
vdslChanInvalidIntervals,
vdslChanFixedOctets,
vdslChanBadBlks,
vdslChanCurr15MinTimeElapsed,
vdslChanCurr15MinFixedOctets,
vdslChanCurr15MinBadBlks,
vdslChan1DayValidIntervals,
vdslChan1DayInvalidIntervals,
vdslChanCurr1DayTimeElapsed,
vdslChanCurr1DayFixedOctets,
vdslChanCurr1DayBadBlks,
vdslChanIntervalFixedOctets,
vdslChanIntervalBadBlks,
vdslChan1DayIntervalMoniSecs,
vdslChan1DayIntervalFixedOctets,
vdslChan1DayIntervalBadBlks,
vdslLineConfDownRateMode,
vdslLineConfUpRateMode,
vdslLineConfDownMaxPwr,
vdslLineConfUpMaxPwr,
vdslLineConfDownMaxSnrMgn,
vdslLineConfDownMinSnrMgn,
vdslLineConfDownTargetSnrMgn,
vdslLineConfUpMaxSnrMgn,
vdslLineConfUpMinSnrMgn,
vdslLineConfUpTargetSnrMgn,
vdslLineConfDownFastMaxDataRate,
vdslLineConfDownFastMinDataRate,
vdslLineConfDownSlowMaxDataRate,
vdslLineConfDownSlowMinDataRate,
vdslLineConfUpFastMaxDataRate,
vdslLineConfUpFastMinDataRate,
vdslLineConfUpSlowMaxDataRate,
vdslLineConfUpSlowMinDataRate,
vdslLineConfDownRateRatio,
vdslLineConfUpRateRatio,
vdslLineConfDownMaxInterDelay,
vdslLineConfUpMaxInterDelay,
vdslLineConfDownPboControl,
vdslLineConfUpPboControl,
vdslLineConfDownPboLevel,
vdslLineConfUpPboLevel,
vdslLineConfDeploymentScenario,
vdslLineConfAdslPresence,
vdslLineConfApplicableStandard,
vdslLineConfBandPlan,
vdslLineConfBandPlanFx,
vdslLineConfBandOptUsage,
vdslLineConfUpPsdTemplate,
vdslLineConfDownPsdTemplate,
vdslLineConfHamBandMask,
vdslLineConfCustomNotch1Start,
vdslLineConfCustomNotch1Stop,
vdslLineConfCustomNotch2Start,
vdslLineConfCustomNotch2Stop,
vdslLineConfDownTargetSlowBurst,
vdslLineConfUpTargetSlowBurst,
vdslLineConfDownMaxFastFec,
vdslLineConfUpMaxFastFec,
vdslLineConfLineType,
vdslLineConfProfRowStatus,
vdslLineAlarmConfThresh15MinLofs,
vdslLineAlarmConfThresh15MinLoss,
vdslLineAlarmConfThresh15MinLprs,
vdslLineAlarmConfThresh15MinLols,
vdslLineAlarmConfThresh15MinESs,
vdslLineAlarmConfThresh15MinSESs,
vdslLineAlarmConfThresh15MinUASs,
vdslLineAlarmConfInitFailure,
vdslLineAlarmConfProfRowStatus
}
STATUS current
DESCRIPTION
"A collection of objects providing information about
a VDSL Line."
::= { vdslGroups 1 }
vdslNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS
{
vdslPerfLofsThreshNotification,
vdslPerfLossThreshNotification,
vdslPerfLprsThreshNotification,
vdslPerfLolsThreshNotification,
vdslPerfESsThreshNotification,
vdslPerfSESsThreshNotification,
vdslPerfUASsThreshNotification,
vdslDownMaxSnrMgnNotification,
vdslDownMinSnrMgnNotification,
vdslUpMaxSnrMgnNotification,
vdslUpMinSnrMgnNotification,
vdslInitFailureNotification
}
STATUS current
DESCRIPTION
"This group supports notifications of significant
conditions associated with VDSL Lines."
::= { vdslGroups 2 }
END
5. Security Considerations
There are a number of management objects defined in this MIB module with a MAX-ACCESS clause of read-write and/or read-create. Such objects may be considered sensitive or vulnerable in some network environments. The support for SET operations in a non-secure environment without proper protection can have a negative effect on network operations. Some of the readable objects in this MIB module (i.e., objects with a MAX-ACCESS other than not-accessible) may be considered sensitive or vulnerable in some network environments. It is thus important to control even GET and/or NOTIFY access to these objects and possibly to even encrypt the values of these objects when sending them over the network via SNMP. VDSL layer connectivity from the Vtur will permit the subscriber to manipulate both the VDSL link directly and the VDSL embedded operations channel (EOC) for their own loop. For example, unchecked or unfiltered fluctuations initiated by the subscriber could generate sufficient notifications to potentially overwhelm either the management interface to the network or the element manager. Additionally, allowing write access to configuration data may allow an end-user to increase their service levels or affect other end- users in either a positive or negative manner. For this reason, the following tables should be considered to contain sensitive information: - vdslLineTable - vdslLineConfProfileTable - vdslLineAlarmConfProfileTable Individual line utilization information, available via the performance tables, may be considered sensitive. For example, if an end-user has a far lower line utilization during certain periods of the day, it may indicate an empty office or residence. For these reasons, the following tables should be considered to contain sensitive information: - vdslPerfDataTable - vdslPerfIntervalTable - vdslPerf1DayIntervalTable Further, notifications generated by agents implementing this MIB will contain threshold and performance information.
It is thus important to control even GET access to the objects within these tables and possibly to even encrypt the values of these objects when sending them over the network via SNMP. Not all versions of SNMP provide features for such a secure environment. SNMP versions prior to SNMPv3 did not include adequate security. Even if the network itself is secure (for example by using IPSec), even then, there is no control as to who on the secure network is allowed to access and GET/SET (read/change/create/delete) the objects in this MIB module. It is RECOMMENDED that implementers consider the security features as provided by the SNMPv3 framework (see [RFC3410], section 8), including full support for the SNMPv3 cryptographic mechanisms (for authentication and privacy). Further, deployment of SNMP versions prior to SNMPv3 is NOT RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to enable cryptographic security. It is then a customer/operator responsibility to ensure that the SNMP entity giving access to an instance of this MIB module is properly configured to give access to the objects only to those principals (users) that have legitimate rights to indeed GET or SET (change/create/delete) them.6. References
6.1. Normative References
[DSLFTR057] DSL Forum TR-057, "VDSL Network Element Management", February 2003. [ETSI2701] ETSI TS 101 270-1 V1.2.1 "Transmission and Multiplexing (TM); Access transmission systems on metallic access cables; Very high speed Digital Subscriber Line (VDSL); Part 1: Functional requirements", October 1999. [ETSI2702] ETSI TS 101 270-2 V1.1.1 "Transmission and Multiplexing (TM); Access transmission systems on metallic access cables; Very high speed Digital Subscriber Line (VDSL); Part 1: Transceiver specification", February 2001. [ITU9931] ITU-T G.993.1 "Very-high-speed digital subscriber line foundation", November 2001. [ITU9971] ITU-T G.997.1 "Physical layer management for Digital Subscriber Line (DSL) Transceivers", July 1999.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999. [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999. [RFC2856] Bierman, A., McCloghrie, K. and R. Presuhn, "Textual Conventions for Additional High Capacity Data Types", RFC 2856, June 2000. [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB", RFC 2863, June 2000. [RFC3411] Harrington, D., Presuhn, R. and B. Wijnen, "An Architecture for Describing Simple Network Management Protocol (SNMP) Management Frameworks", RFC 3411, December 2002. [RFC3418] Presuhn, R., "Management Information Base (MIB) for the Simple Network Management Protocol (SNMP)", STD 62, RFC 3418, December 2002. [RFC3593] Tesink, K., "Textual Conventions for MIB Modules Using Performance History Based on 15 Minute Intervals", RFC 3593, September 2003. [RFC3705] Ray, B. and R. Abbi, "High Capacity Textual Conventions for MIB Modules Using Performance History Based on 15 Minute Intervals", RFC 3705, February 2004. [T1E1311] ANSI T1E1.4/2001-311, "Very-high-bit-rate Digital Subscriber Line (VDSL) Metallic Interface, Part 1: Functional Requirements and Common Specification", February 2001. [T1E1011] ANSI T1E1.4/2001-011R3, "VDSL Metallic Interface, Part 2: Technical Specification for a Single-Carrier Modulation (SCM) Transceiver", November 2001.
[T1E1013] ANSI T1E1.4/2001-013R4, "VDSL Metallic Interface, Part 3: Technical Specification for a Multi-Carrier Modulation (MCM) Transceiver", November 2000.6.2. Informative References
[RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, "Introduction and Applicability Statements for Internet- Standard Management Framework", RFC 3410, December 2002. [RFC3415] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)", STD 62, RFC 3415, December 2002.7. Acknowledgements
Greg Bathrick (Texas Instruments) Umberto Bonollo (NEC) Andrew Cheers (NEC) Felix Flemisch (Siemens) David Horton (CiTR) Travis Levin (Paradyne) Moti Morgenstern (Inovia) Randy Presuhn (BMC) Say Sabit (NLC) Bert Wijnen (Lucent)
8. Authors' Addresses
Bob Ray PESA Switching Systems, Inc. 330-A Wynn Drive Huntsville, AL 35805 USA Phone: +1 256 726 9200 ext. 142 Fax: +1 256 726 9271 EMail: rray@pesa.com Rajesh Abbi Alcatel USA 2301 Sugar Bush Road Raleigh, NC 27612-3339 USA Phone: +1 919 850 6194 EMail: Rajesh.Abbi@alcatel.com
9. Full Copyright Statement
Copyright (C) The Internet Society (2004). This document is subject to the rights, licenses and restrictions contained in BCP 78 and except as set forth therein, the authors retain all their rights. This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Intellectual Property The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79. Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf- ipr@ietf.org. Acknowledgement Funding for the RFC Editor function is currently provided by the Internet Society.