interface
Click on the red underlined text to get to the source
...
These objects are used when the particular media being used to
realize an interface is a DS1/J1/E1 ...
... J1/E1/DS2/E2 interface. At present,
this applies to the following value of the ifType variable in the
...
... J1 but in
both examples, there is definition in both related lines. Therefore,
interface types e1(19) and g703at2mb(67) have been obsoleted and
there is also no need for special type for J1.
...
... ===================================================================
ifIndex Interface index.
ifDescr ...
... proxy case to represent the
association between pairs of interfaces, i.e., this T1 is attached to
that T1 ...
... ifStackTable to
show the association between various sub-layers of an interface. In
both cases, entire PDUs are exchanged between the interface ...
... interface. In
both cases, entire PDUs are exchanged between the interface pairs --
in the case of a T1, entire T1 ...
... connections in general.
External and Internal interface scenario: the SNMP agent resides on a
host ...
... ifStackTable is then used to show the relationships between the
various DS1 interfaces.
ifStackTable ...
... SNMP agent, the
situation would be identical, except the Ethernet and the four router
interfaces are deleted. Interfaces would also be numbered from 1 to
...
... Ethernet and the four router
interfaces are deleted. Interfaces would also be numbered from 1 to
8.
...
... interfaces are stacked on DS2/E2
interfaces. It is not necessary nor is it always desirable to
represent DS2 interfaces ...
... interfaces. It is not necessary nor is it always desirable to
represent DS2 interfaces. If this is required, the following
stacking should be used. All ifTypes are ds1. The DS2 is determined
...
... dsx1LoopbackConfig represents the desired state of
loopbacks on this interface. Using this object, a manager can
request
...
... To model the current state of loopbacks on a DS1 interface, the
object dsx1LoopbackStatus defines which loopback is currently applied
...
... object dsx1LoopbackStatus defines which loopback is currently applied
to an interface. This object, which is a bitmap, will have bits
turned on that reflect the currently active ...
... turned on that reflect the currently active loopbacks on the
interface as well as the source of those loopbacks.
The following restrictions/rules apply to loopbacks:
...
... E1, DS2, or E2
interfaces. As such, a design decision was made up front to very
closely align the MIB ...
... read from these types of devices that are currently deployed.
J2 interfaces are not supported by this MIB.
...
... error conditions on
a DS1 interface as monitored by a DS1 device are based on the latest
ANSI ...
... links, the 'all ones' condition is detected at a
DS1 line interface upon observing an unframed signal with a one's
density of at least 99.9% present for a time equal to or greater
than T, where 3 ms <= T <= 75 ms. The AIS ...
... E1 links, the 'all-ones' condition is detected at the line
interface as a string of 512 bits containing fewer than three zero
bits ...
... performance parameter. Performance parameters
continue to be collected when the interface is down.
There is no requirement ...
... Unavailable Seconds (UASs) are calculated by counting the number
of seconds that the interface is unavailable. The DS1 interface ...
... interface is unavailable. The DS1 interface
is said to be unavailable from the onset of 10 contiguous SESs, or
...
... States). If the condition leading to the failure was immediately
preceded by one or more contiguous SESs, then the DS1 interface
unavailability starts from the onset of these SESs. Once
...
... unavailable, and if no failure is present, the DS1 interface
becomes available at the onset of 10 contiguous seconds with no
SESs. Once unavailable ...
... unavailable, and if a failure is present, the DS1
interface becomes available at the onset of 10 contiguous seconds
with no SESs, if the failure clearing time is less than or equal
to 10 seconds. If the failure clearing time is more than 10
...
... to 10 seconds. If the failure clearing time is more than 10
seconds, the DS1 interface becomes available at the onset of 10
contiguous seconds with no SESs, or the onset period leading to
the successful clearing condition, whichever occurs later. With
...
... counters are incremented
while the DS1 interface is deemed available. While the interface
is deemed unavailable ...
... while the DS1 interface is deemed available. While the interface
is deemed unavailable, the only count that is incremented is UASs.
...
... starts with the first of the 10 contiguous SESs. Also, while an
interface is deemed unavailable all counters for that interface ...
... interface is deemed unavailable all counters for that interface are
frozen except for the UAS count. It follows that an implementation
...
... The following failure states are received, or detected failures, that
are reported in the dsx1LineStatus object. When a DS1 interface
would, if ever, produce the conditions leading to the failure state
...
... An AIS defect at a 6312-kbit/s (G.704) interface is detected when
the incoming signal has two or less zeroes in a sequence of 3156
bits ...
...
A LOS defect at 6312kbit/s interfaces is detected when the
incoming signal has "no transitions", i.e., when the signal level
is less than or equal to a signal level of 35dB below nominal, for
...
... SNMP messages and replies to them on
behalf of the devices that implement the actual DS1/E1 interfaces.
The proxy may have already collected the information about the
...
... DS1/J1/E1 interfaces into its local database and may not
necessarily forward the requests to the actual DS1 ...
... J1/E1
interface. It is expected in such an application that there are
periods of time where the proxy is not communicating with the
...
... DS1/J1/E1 interfaces. In these instances, the proxy will not
necessarily have up-to-date configuration information ...
... introduced to reflect the loopbacks established
on a DS1 interface and the source to the requests.
dsx1LoopbackConfig continues to be the desired
...
... identifier of a DS1
interface on a managed device. If there is an
ifEntry that is directly associated with this and
only this DS1 ...
... ifEntry that is directly associated with this and
only this DS1 interface, it should have the same
value as ifIndex. Otherwise, number the
...
... following the rules of choosing a number that is
greater than ifNumber and numbering the inside
interfaces (e.g., equipment side) with even
numbers and outside interfaces (e.g., network
side ...
... interfaces (e.g., equipment side) with even
numbers and outside interfaces (e.g., network
side) with odd numbers."
::= { dsx1ConfigEntry 1 }
...
... "The number of previous near-end intervals for
which data was collected. The value will be 96
unless the interface was brought online within the
last 24 hours, in which case the value will be the
number of complete 15-minute near-end intervals
...
... last 24 hours, in which case the value will be the
number of complete 15-minute near-end intervals
since the interface has been online. In the case
where the agent is a proxy ...
... Physical/Electrical Characteristics
of Hierarchical Digital Interfaces, November
2001.
ITU-T ...
... CRC) Procedures.
JT-I431. ISDN Primary Rate User-Network Interface,
Layer 1 Specifications, 2002 "
...
... DESCRIPTION
"This variable describes the variety of Zero Code
Suppression used on this interface, which in turn
affects a number of its characteristics.
...
... "This variable indicates what type of code is
being sent across the DS1 interface by the device.
Setting this variable causes the interface to send
...
... DS1 interface by the device.
Setting this variable causes the interface to send
the code requested. The values mean the following:
...
... loopback
configuration of the DS1 interface. Agents
supporting read/write access should return
...
... state. A device that is not
capable of performing a loopback on the interface
shall always return this as its value.
...
... dsx1PayloadLoop
the received signal at this interface is looped
through the device. Typically, the received signal
is looped back for retransmission ...
...
dsx1LineLoop
the received signal at this interface does not go
through the device (minimum penetration) but is
looped back out.
...
...
dsx1InwardLoop
the transmitted signal at this interface is
looped back and received by the same interface.
...
... the transmitted signal at this interface is
looped back and received by the same interface.
What is transmitted onto the line is product
dependent.
...
... DESCRIPTION
"This variable indicates the line status of the
interface. It contains loopback, failure,
received alarm ...
... 'localTiming' indicates that a local clock
source is used or when an external clock is
attached to the box containing the interface.
'throughTiming' indicates that recovered
...
...
'throughTiming' indicates that recovered
receive clock from another interface is used as
the transmit clock.
...
... object provides information for line build-out
circuitry. This object is only useful if the
interface has configurable line build-out
circuitry."
::= { dsx1ConfigEntry 15 }
...
... "Indicates whether dsx1LineStatusChange traps
should be generated for this interface."
DEFVAL { disabled }
::= { dsx1ConfigEntry 17 }
...
... loopback on the DS1 interface. It contains
information about loopbacks established by a
manager and remotely from the far end.
...
... index value that uniquely identifies the DS1
interface to which this entry is applicable. The
interface identified by a particular value of this
...
... interface to which this entry is applicable. The
interface identified by a particular value of this
index is the same interface as identified by the
...
... interface identified by a particular value of this
index is the same interface as identified by the
same value as a dsx1LineIndex object instance."
...
... DS1 Interval table contains various
statistics collected by each DS1 interface over
the previous 24 hours of operation. The past 24
hours are broken into 96 completed 15-minute
...
... index value that uniquely identifies the DS1
interface to which this entry is applicable. The
interface identified by a particular value of this
...
... interface to which this entry is applicable. The
interface identified by a particular value of this
index is the same interface as identified by the
...
... interface identified by a particular value of this
index is the same interface as identified by the
same value as a dsx1LineIndex object instance."
...
... index value that uniquely identifies the DS1
interface to which this entry is applicable. The
interface identified by a particular value of this
...
... interface to which this entry is applicable. The
interface identified by a particular value of this
index is the same interface as identified by the
...
... interface identified by a particular value of this
index is the same interface as identified by the
same value as a dsx1LineIndex object instance."
...
... Errored Seconds encountered by a DS1
interface in the previous 24-hour interval.
Invalid 15-minute intervals count as 0."
::= { dsx1TotalEntry 2 }
...
... Severely Errored Seconds
encountered by a DS1 interface in the previous
24-hour interval. Invalid 15-minute intervals
count as 0."
...
... Severely Errored Framing Seconds
encountered by a DS1 interface in the previous
24-hour interval. Invalid 15-minute intervals
count as 0."
...
... Unavailable Seconds encountered by
a DS1 interface in the previous 24-hour interval.
Invalid 15-minute intervals count as 0."
::= { dsx1TotalEntry 5 }
...
... Controlled Slip Seconds encountered
by a DS1 interface in the previous 24-hour
interval. Invalid 15-minute intervals count as
0."
...
... "The number of Path Coding Violations encountered
by a DS1 interface in the previous 24-hour
interval. Invalid 15-minute intervals count as
0."
...
... Line Errored Seconds encountered by
a DS1 interface in the previous 24-hour interval.
Invalid 15-minute intervals count as 0."
::= { dsx1TotalEntry 8 }
...
...
encountered by a DS1 interface in the previous
24-hour interval. Invalid 15-minute intervals count
as 0."
...
... Degraded Minutes (DMs) encountered
by a DS1 interface in the previous 24-hour
interval. Invalid 15-minute intervals count as
0."
...
... "The number of Line Coding Violations (LCVs)
encountered by a DS1 interface in the current
15-minute interval. Invalid 15-minute intervals
count as 0."
...
... is an entry in this table corresponding to each
DS1 ifEntry within any interface that is
channelized to the individual DS1 ifEntry level.
...
...
This table is intended to facilitate mapping from
channelized interface / channel number to DS1
...
... element
dsx1Ds1ChannelNumber) of the given channelized
interface (specified by INDEX element ifIndex)."
...
... index value that uniquely identifies the DS1
interface to which this entry is applicable. The
interface identified by a particular value of this
...
... interface to which this entry is applicable. The
interface identified by a particular value of this
index is identical to the interface identified by
...
... interface identified by a particular value of this
index is identical to the interface identified by
the same value of dsx1LineIndex."
...
... far-end intervals for
which data was collected. The value will be 96
unless the interface was brought online within the
last 24 hours, in which case the value will be the
number of complete 15-minute far-end ...
... number of complete 15-minute far-end intervals
since the interface has been online. In the case
where the agent is a proxy ...
... DS1 Far End Interval table contains various
statistics collected by each DS1 interface over
the previous 24 hours of operation. The past 24
hours are broken into 96 completed 15-minute
...
... index value that uniquely identifies the DS1
interface to which this entry is applicable. The
interface identified by a particular value of this
...
... interface to which this entry is applicable. The
interface identified by a particular value of this
index is identical to the interface identified by
...
... interface identified by a particular value of this
index is identical to the interface identified by
the same value of dsx1LineIndex."
...
... index value that uniquely identifies the DS1
interface to which this entry is applicable. The
interface identified by a particular value of this
...
... interface to which this entry is applicable. The
interface identified by a particular value of this
index is identical to the interface identified by
...
... interface identified by a particular value of this
index is identical to the interface identified by
the same value of dsx1LineIndex."
...
... Errored Seconds encountered
by a DS1 interface in the previous 24-hour
interval. Invalid 15-minute intervals count as
0."
...
... Severely Errored Seconds
encountered by a DS1 interface in the previous
24-hour interval. Invalid 15-minute intervals
count as 0."
...
... "The number of Far End Severely Errored Framing
Seconds encountered by a DS1 interface in the
previous 24-hour interval. Invalid 15-minute
intervals count as 0."
...
... Unavailable Seconds encountered by
a DS1 interface in the previous 24-hour interval.
Invalid 15-minute intervals count as 0."
::= { dsx1FarEndTotalEntry 5 }
...
... Controlled Slip Seconds
encountered by a DS1 interface in the previous
24-hour interval. Invalid 15 minute intervals
count as 0."
...
... Line Errored Seconds
encountered by a DS1 interface in the previous
24-hour interval. Invalid 15-minute intervals
count as 0."
...
... reported via the far end block error count
encountered by a DS1 interface in the previous
24-hour interval. Invalid 15-minute intervals
count as 0."
...
... Bursty Errored Seconds (BESs)
encountered by a DS1 interface in the previous
24-hour interval. Invalid 15-minute intervals
count as 0."
...
... Degraded Minutes (DMs) encountered
by a DS1 interface in the previous 24-hour
interval. Invalid 15-minute intervals count as
0."
...
... channels associated with a CSU are being used to
support a logical interface, i.e., an entry in the
interfaces table from the Internet-standard ...
... support a logical interface, i.e., an entry in the
interfaces table from the Internet-standard MIB.
...
... DS1 and refers to the DS1 interface and that the
interfaces layered onto it are numbered 3..16.
...
... DS1 interface and that the
interfaces layered onto it are numbered 3..16.
We might describe the allocation of channels ...
... index value that uniquely identifies the
DS1 interface to which this entry is applicable.
The interface identified by a particular
...
... DS1 interface to which this entry is applicable.
The interface identified by a particular
value of this index is the same interface as
...
... The interface identified by a particular
value of this index is the same interface as
identified by the same value as a dsx1LineIndex
...
... "An index value that uniquely identifies an
interface. The interface identified by a particular
value of this index is the same interface ...
... index value that uniquely identifies an
interface. The interface identified by a particular
value of this index is the same interface
...
... interface. The interface identified by a particular
value of this index is the same interface
as identified by the same value as an ifIndex
...
... as identified by the same value as an ifIndex
object instance. If no interface is currently using
a channel, the value should be zero. If a
...
... a channel, the value should be zero. If a
single interface occupies more than one time-slot,
that ifIndex value will be found in multiple
...
... group is the set of statistics appropriate
for all systems that attach to a DS1 interface
running transparent or unFramed lineType."
...
... T1 ISDN
Primary Rate interfaces.
Note: Eventually, dsx1Att-54016(4) is to be
used here since the line type is ESF ...
... "The transmit clock is derived from received
clock on ISDN Primary Rate interfaces."
OBJECT dsx1Fdl ...
... group is optional for all
systems that attach to a DS1 interface. If it is
implemented, then ds1NearEndOptionalConfigGroup
should also be implemented."
...
... group is recommended for
all systems that attach to a DS1 interface and
implement ds1NearEndOptionalTrapGroup."
...
... group is the set of statistics appropriate
for all systems that attach to a DS1 interface
running transparent or unFramed lineType."
...
... T1 ISDN
Primary Rate interfaces.
Note: Eventually, dsx1Att-54016(4) is to be
used here since the line type is ESF ...
... "The transmit clock is derived from received
clock on ISDN Primary Rate interfaces."
OBJECT dsx1Fdl ...
... group is optional for all
systems that attach to a DS1 interface. If it is
implemented, then ds1NearEndOptionalConfigGroup
...
... group is recommended for
all systems that attach to a DS1 interface and
implement ds1NearEndOptionalTrapGroup."
...
... group is the set of statistics appropriate
for all systems that attach to a DS1 interface
running transparent or unFramed lineType."
...
... T1 ISDN
Primary Rate interfaces.
Note: Eventually, dsx1Att-54016(4) is to be
used here since the line type is ESF ...
... "The transmit clock is derived from received
clock on ISDN Primary Rate interfaces."
OBJECT dsx1Fdl ...
... "A collection of objects providing configuration
information applicable to all DS1 interfaces."
::= { ds1Groups 1 }
...
... "A collection of objects providing statistics
information applicable to all DS1 interfaces."
::= { ds1Groups 2 }
...
... statistics that can be collected from a DS1
interface that is running transparent or unframed
lineType. Statistics not in this list should
return noSuchInstance."
...
... "A collection of objects providing configuration
information applicable to all DS1 interfaces."
::= { ds1Groups 10 }
...
... "A collection of objects providing configuration
information applicable to all DS1 interfaces."
::= { ds1Groups 11 }
...
... "A collection of objects providing statistics
information applicable to all DS1 interfaces."
::= { ds1Groups 12 }
...
... some environments since, collectively, they provide extensive
information about the performance of interfaces in DS1/J1/E1 ...
... McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB", RFC 2863draft, June 2000. ...
... Telecommunications -- Carrier-to-Customer Installation - DS1 Metallic Interface, T1.403, February 1989. ...
... ITU-T G.703, Physical/Electrical Characteristics of Hierarchical Digital Interfaces, November 2001. ...
... AT&T Technical Reference, Technical Reference 62411, ACCUNET T1.5 Service Description And Interface Specification, December 1990. ...
... Definitions of Managed Objects for the DS1 and E1 Interface Types", RFC 1406(-> 2495(-> 3895prop(-> 4805prop))), January 1993. ...
... Nicklass, O., "Definitions of Managed Objects for the DS3/E3 Interface Type", RFC 3896prop, September 2004. ...
... Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Interface Type", RFC 3592draft, September 2003. ...
... Fowler, D., "Definitions of Managed Objects for the DS0 and DS0 Bundle Interface Type", RFC 2494prop, January 1999. ...
... American National Standard for Telecommunications -- Digital Hierarchy - Electrical Interfaces, T1.102, December 1993. ...
... [Old Definition]: "This object is the identifier of a DS1 Interface
on a managed device. If there is an ifEntry that is directly
associated with this and only this DS1 ...
... on a managed device. If there is an ifEntry that is directly
associated with this and only this DS1 interface, it should have the
same value as ifIndex. Otherwise, number the dsx1LineIndices with an
...
... unique identifier following the rules of choosing a number that is
greater than ifNumber and numbering the inside interfaces (e.g.,
equipment side) with even numbers and outside interfaces (e.g.,
...
... greater than ifNumber and numbering the inside interfaces (e.g.,
equipment side) with even numbers and outside interfaces (e.g.,
network side) with odd numbers."
...
... equipment exist. To accommodate these scenarios, two different
indices for DS1 interfaces are introduced in this MIB. These
indices are dsx1IfIndex ...
... SNMP Agent represents all managed
DS1 lines as external interfaces (for example, an Agent residing
on the device supporting DS1 ...
... Agent residing
on the device supporting DS1 interfaces directly):
For this scenario, all interfaces ...
... interfaces directly):
For this scenario, all interfaces are assigned an integer value
equal to ifIndex ...
... DS1 Configuration table relates each
DS1 interface to its corresponding interface (ifIndex) in the
...
... dsx1LineIndex is used to not only represent the DS1
interfaces external from the host/DS1-device combination, but also
...
... DS1-device combination, but also
the DS1 interfaces connecting the host and the DS1 device. The
...
... dsx1LineIndex identifies a DS1
Interface on a managed device. If there is an ifEntry that is
directly associated with this and only this DS1 interface ...
... Interface on a managed device. If there is an ifEntry that is
directly associated with this and only this DS1 interface, it
should have the same value as ifIndex. Otherwise, number the
...
... unique identifier following the rules of
choosing a number greater than ifNumber and numbering inside
interfaces (e.g., equipment side) with even numbers and outside
interfaces (e.g., network side ...
... interfaces (e.g., equipment side) with even numbers and outside
interfaces (e.g., network side) with odd numbers.
...
... This procedure is illustrated below for a DS1 ESF interface. Similar
rules would apply for other DS1, DS2 ...
... DS1, DS2, and E1 interface variants. The
procedure guarantees that the statistical counters are correctly
...
... (16) A new object, dsx1LoopbackStatus, has been introduced to
reflect the loopbacks established on a DS1 interface and the
source to the requests. dsx1LoopbackConfig continues to be
...