AXD301-ILMI-MIB
AI MIB Summary
Standard SNMP MIB module defining data structures for AXD301-ILMI-MIB.
170
Objects
Active
Status
6
Dependencies
Imported Objects
Objects
170 total| Object Name |
|---|
atmForum OBJECT IDENTIFIER .1.3.6.1.4.1.353 |
IMPORTS Unknown .1.3.6.1.4.1.353 |
atmfVpcChangeAn atmfVpcChange trap indicates that a permanent VPC has been
added or deleted at this ATM Interface or that the attributes
of an existing VPC have been modified. The variables
included in the trap identify the VPI value of the
reconfigured VPC at this ATM Interface. TRAP-TYPE .1.3.6.1.4.1.353.0.1 |
atmfVccChangeAn atmfVccChange trap indicates that a permanent VCC has been
added or deleted at this ATM Interface or that the attributes
of an existing VCC have been modified.. The variables
included in the trap identify the VCI and VPI values
of the reconfigured VCC at this ATM
Interface. TRAP-TYPE .1.3.6.1.4.1.353.0.2 |
atmForumAdmin OBJECT IDENTIFIER .1.3.6.1.4.1.353.1 |
atmfTransmissionTypes OBJECT IDENTIFIER .1.3.6.1.4.1.353.1.2 |
atmfUnknownType OBJECT IDENTIFIER .1.3.6.1.4.1.353.1.2.1 |
atmfSonetSTS3c OBJECT IDENTIFIER .1.3.6.1.4.1.353.1.2.2 |
atmfDs3 OBJECT IDENTIFIER .1.3.6.1.4.1.353.1.2.3 |
atmf4B5B OBJECT IDENTIFIER .1.3.6.1.4.1.353.1.2.4 |
atmf8B10B OBJECT IDENTIFIER .1.3.6.1.4.1.353.1.2.5 |
atmfSonetSTS12c OBJECT IDENTIFIER .1.3.6.1.4.1.353.1.2.6 |
atmfE3 OBJECT IDENTIFIER .1.3.6.1.4.1.353.1.2.7 |
atmfT1 OBJECT IDENTIFIER .1.3.6.1.4.1.353.1.2.8 |
atmfE1 OBJECT IDENTIFIER .1.3.6.1.4.1.353.1.2.9 |
atmfMediaTypes OBJECT IDENTIFIER .1.3.6.1.4.1.353.1.3 |
atmfMediaUnknownType OBJECT IDENTIFIER .1.3.6.1.4.1.353.1.3.1 |
atmfMediaCoaxCable OBJECT IDENTIFIER .1.3.6.1.4.1.353.1.3.2 |
atmfMediaSingleMode OBJECT IDENTIFIER .1.3.6.1.4.1.353.1.3.3 |
atmfMediaMultiMode OBJECT IDENTIFIER .1.3.6.1.4.1.353.1.3.4 |
atmfMediaStp OBJECT IDENTIFIER .1.3.6.1.4.1.353.1.3.5 |
atmfMediaUtp OBJECT IDENTIFIER .1.3.6.1.4.1.353.1.3.6 |
atmfTrafficDescrTypes OBJECT IDENTIFIER .1.3.6.1.4.1.353.1.4 |
atmfNoDescriptor OBJECT IDENTIFIER .1.3.6.1.4.1.353.1.4.1 |
atmfPeakRate OBJECT IDENTIFIER .1.3.6.1.4.1.353.1.4.2 |
atmfNoClpNoScr OBJECT IDENTIFIER .1.3.6.1.4.1.353.1.4.3 |
atmfClpNoTaggingNoScr OBJECT IDENTIFIER .1.3.6.1.4.1.353.1.4.4 |
atmfClpTaggingNoScr OBJECT IDENTIFIER .1.3.6.1.4.1.353.1.4.5 |
atmfNoClpScr OBJECT IDENTIFIER .1.3.6.1.4.1.353.1.4.6 |
atmfClpNoTaggingScr OBJECT IDENTIFIER .1.3.6.1.4.1.353.1.4.7 |
atmfClpTaggingScr OBJECT IDENTIFIER .1.3.6.1.4.1.353.1.4.8 |
atmfClpNoTaggingMcr OBJECT IDENTIFIER .1.3.6.1.4.1.353.1.4.9 |
atmfSrvcRegTypes OBJECT IDENTIFIER .1.3.6.1.4.1.353.1.5 |
atmForumUni OBJECT IDENTIFIER .1.3.6.1.4.1.353.2 |
atmfPhysicalGroup OBJECT IDENTIFIER .1.3.6.1.4.1.353.2.1 |
atmfPortTableA table of physical layer status and parameter
information for the ATM Interface's physical interface. Unknown .1.3.6.1.4.1.353.2.1.1 |
atmfPortEntryAn entry in the table, containing information about
the physical layer of an ATM Interface. AtmfPortEntry .1.3.6.1.4.1.353.2.1.1.1 |
atmfPortIndexThe value of 0 which has the special meaning of
identifying the ATM Interface over which this message
was received.ro INTEGER .1.3.6.1.4.1.353.2.1.1.1.1 |
atmfPortAddressThis object should not be implemented except as
required for backward compatibility with version 2.0
of the UNI specification. The Address Group, defined
in theAddress Registration MIB should be used instead.roobsolete AtmAddress .1.3.6.1.4.1.353.2.1.1.1.2 |
atmfPortTransmissionTypeThis object should not be implemented except as
required for backward compatibility with version 3.1
of the UNI specification. Appropriate Network Management
MIBs should be used instead.roobsolete OBJECT IDENTIFIER .1.3.6.1.4.1.353.2.1.1.1.3 |
atmfPortMediaTypeThis object should not be implemented except as
required for backward compatibility with version 3.1
of the UNI specification. Appropriate Network Management
MIBs should be used instead.roobsolete OBJECT IDENTIFIER .1.3.6.1.4.1.353.2.1.1.1.4 |
atmfPortOperStatusThis object should not be implemented except as
required for backward compatibility with version 3.1
of the UNI specification. Appropriate Network Management
MIBs should be used instead.roobsolete Enumeration .1.3.6.1.4.1.353.2.1.1.1.5 |
atmfPortSpecificThis object should not be implemented except as
required for backward compatibility with version 3.1
of the UNI specification. Appropriate Network Management
MIBs should be used instead.roobsolete OBJECT IDENTIFIER .1.3.6.1.4.1.353.2.1.1.1.6 |
atmfPortMyIfNameA textual name of this interface. If this system is
manageable through SNMP, and supports the object
ifName, the value of this object must be identical
with that of ifName for the ifEntry of the lowest
level physical interface for this port. This interface
must be uniquely named on this system to distinguish
parallel links with a neighboring system. If this
interface does not have a textual name, the value of
this object is a zero length string.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.353.2.1.1.1.7 |
atmfPortMyIfIdentifierA unique value for each ATM interface. The scheme used to
number the ATM interfaces on an ATM device is
implementation specific. One way to generate this value is
to use the ifIndex that an SNMP manager would use to
identify the port. This interface must be uniquely numbered
on this system to distinguish parallel links with a
neighboring system.ro INTEGER .1.3.6.1.4.1.353.2.1.1.1.8 |
atmfMyIpNmAddressAn IP Address to which a Network Management Station
can send Network Management protocol messages, e.g. SNMP
messages to UDP port 161, in order to access network
management information concerning the operation of the
ATM device local to this IME. If this object is supported,
but the Network Management Agent has not been configured with
an IP Address, the IME should return 0.0.0.0.ro IpAddress .1.3.6.1.4.1.353.2.1.2 |
atmfMyOsiNmNsapAddressAn NSAP Address to which a Network Management Station
can send Network Management protocol messages in order
to access network management information concerning
the operation of the ATM device local to this IME.
If this object is supported,
but the Network Management Agent has not been configured with
an NSAP Address, the IME should return 0.0.0.0ro ClnpAddress .1.3.6.1.4.1.353.2.1.3 |
atmfMySystemIdentifierA 48 bit identifier, taken from the IEEE universally
administered MAC address space, which uniquely
identifies the ATM device local to this IME.ro OCTET STRING .1.3.6.1.4.1.353.2.1.4 |
atmfAtmLayerGroup OBJECT IDENTIFIER .1.3.6.1.4.1.353.2.2 |
atmfAtmLayerTableA table of ATM layer status and parameter information
for the ATM Interface. SEQUENCE OF AtmfAtmLayerEntry .1.3.6.1.4.1.353.2.2.1 |
atmfAtmLayerEntryAn entry in the table, containing information about
the ATM layer of an ATM Interface. AtmfAtmLayerEntry .1.3.6.1.4.1.353.2.2.1.1 |
atmfAtmLayerIndexThe value of 0 which has the special meaning of
identifying the ATM Interface over which this message
was received.ro INTEGER .1.3.6.1.4.1.353.2.2.1.1.1 |
atmfAtmLayerMaxVPCsThe maximum number of switched and permanent VPCs
supported on this ATM Interface. For virtual interfaces
(i.e. Virtual Path Connections), the maximum number of VPCs
PNNI may communicate over is set to zero.ro INTEGER .1.3.6.1.4.1.353.2.2.1.1.2 |
atmfAtmLayerMaxVCCsThe maximum number of switched and permanent VCCs
supported on this ATM Interface.ro INTEGER .1.3.6.1.4.1.353.2.2.1.1.3 |
atmfAtmLayerConfiguredVPCsThe number of permanent VPCs configured for use on
this ATM Interface. For virtual interfaces (i.e. Virtual Path
Connections used by PNNI), the maximum number of VPCs
is set to zero.ro INTEGER .1.3.6.1.4.1.353.2.2.1.1.4 |
atmfAtmLayerConfiguredVCCsThe number of permanent VCCs configured for use on
this ATM Interface.ro INTEGER (0.. 268435456) .1.3.6.1.4.1.353.2.2.1.1.5 |
atmfAtmLayerMaxVpiBitsThe maximum number of active VPI bits on this ATM Interface.
For virtual interfaces (i.e. Virtual Path Connections used by PNNI),
this value has no meaning and is set to zero.ro INTEGER .1.3.6.1.4.1.353.2.2.1.1.6 |
atmfAtmLayerMaxVciBitsThe maximum number of active VCI bits on this ATM Interface.ro INTEGER .1.3.6.1.4.1.353.2.2.1.1.7 |
atmfAtmLayerUniTypeThe type of the ATM device, either public or private.ro Enumeration .1.3.6.1.4.1.353.2.2.1.1.8 |
atmfAtmLayerUniVersionAn indication of the latest version of the ATM Forum UNI
Signalling Specification that is supported on this ATM
Interface. If this value is not present, a version of the UNI
earlier than 3.1 is supported.
If the peer IME's value of this object is the same as,
or later than the local IME's value, then the version
corresponding to the local IME's value should be
attempted. Otherwise, if the peer IME's value of this
object is earlier, and supported locally, then the
local IME should attempt the version corresponding to
the peer IME's value. Otherwise, compatibility of the
two IMEs cannot be assumed.ro Enumeration .1.3.6.1.4.1.353.2.2.1.1.9 |
atmfAtmLayerDeviceTypeThis object determines the type of the ATM device. This
object is used in automatic ATM Interface-Type determination
procedure such that a correct operational ATM
Interface-type can be determined. An ATM End System
shall take the value of user(1), and an ATM network
node shall take the value of node(2).ro Enumeration .1.3.6.1.4.1.353.2.2.1.1.10 |
atmfAtmLayerIlmiVersionAn indication of the latest version of the ATM Forum
ILMI Specification that is supported on this ATM Interface.
If the peer IME's value of this object is the same as,
or later than the local IME's value, then the version
corresponding to the local IME's value should be
attempted. Otherwise, if the peer IME's value of this
object is earlier, and supported locally, then the
local IME should attempt the version corresponding to
the peer IME's value. Otherwise, compatibility of the
two IMEs cannot be assumed.
If this object is not present, a version of the ILMI earlier
than 4.0 is supported.ro Enumeration .1.3.6.1.4.1.353.2.2.1.1.11 |
atmfAtmLayerNniSigVersionAn indication of the latest version of the ATM Forum
PNNI Signalling Specification that is supported on this
ATM Interface. Note that the PNNI routing version is not
determined through ILMI.
If the peer IME's value of this object is the same as,
or later than the local IME's value, then the version
corresponding to the local IME's value should be
attempted. Otherwise, if the peer IME's value of this
object is earlier, and supported locally, then the
local IME should attempt the version corresponding to
the peer IME's value. Otherwise, compatibility of the
two IMEs cannot be assumed.ro Enumeration .1.3.6.1.4.1.353.2.2.1.1.12 |
atmfAtmLayerMaxSvpcVpiThe maximum VPI that the signalling stack on the ATM
interface is configured to support for allocation to
switched virtual path connections.ro INTEGER .1.3.6.1.4.1.353.2.2.1.1.13 |
atmfAtmLayerMaxSvccVpiThe maximum VPI that the signalling stack on the ATM
interface is configured to support for allocation to
switched virtual channel connections.ro INTEGER .1.3.6.1.4.1.353.2.2.1.1.14 |
atmfAtmLayerMinSvccVciThis is the minimum VCI value that the
signalling stack is configured to support for
allocation to switched virtual channel connections. The same
value applies to all SVCC VPI values for which the
signalling stack is configured.ro INTEGER .1.3.6.1.4.1.353.2.2.1.1.15 |
atmfAtmStatsGroup OBJECT IDENTIFIER .1.3.6.1.4.1.353.2.3 |
atmfVpcGroup OBJECT IDENTIFIER .1.3.6.1.4.1.353.2.4 |
atmfVpcTableA table of status and parameter information on the
virtual path connections which cross this ATM
Interface. There is one entry in this table for each
permanent virtual path connection. SEQUENCE OF AtmfVpcEntry .1.3.6.1.4.1.353.2.4.1 |
atmfVpcEntryAn entry in the table, containing information about a
particular virtual path connection. AtmfVpcEntry .1.3.6.1.4.1.353.2.4.1.1 |
atmfVpcPortIndexThe value of 0 which has the special meaning of
identifying the ATM Interface over which this message
was received.ro INTEGER .1.3.6.1.4.1.353.2.4.1.1.1 |
atmfVpcVpiThe VPI value of this Virtual Path Connection at the
local ATM Interface.ro INTEGER .1.3.6.1.4.1.353.2.4.1.1.2 |
atmfVpcOperStatusThe present actual operational status of the VPC.
A value of end2endUp(2) or end2endDown(3) would be
used if the end-to-end status is known. If only local
status information is available, a value of
localUpEnd2endUnknown(4) or localDown(5) would be
used.ro Enumeration .1.3.6.1.4.1.353.2.4.1.1.3 |
atmfVpcTransmitTrafficDescriptorTypeThe type of traffic management, applicable to the
transmit direction of this VPC. The type may indicate
none, or a type with one or more parameters. These
parameters are specified as a parameter vector, in the
corresponding instances of the objects:
atmfVpcTransmitTrafficDescriptorParam1,
atmfVpcTransmitTrafficDescriptorParam2,
atmfVpcTransmitTrafficDescriptorParam3,
atmfVpcTransmitTrafficDescriptorParam4, and
atmfVpcTransmitTrafficDescriptorParam5.ro OBJECT IDENTIFIER .1.3.6.1.4.1.353.2.4.1.1.4 |
atmfVpcTransmitTrafficDescriptorParam1The first parameter of the transmit parameter vector
for this VPC, used according to the value of
atmfVpcTransmitTrafficDescriptorType.ro INTEGER .1.3.6.1.4.1.353.2.4.1.1.5 |
atmfVpcTransmitTrafficDescriptorParam2The second parameter of the transmit parameter vector
for this VPC, used according to the value of
atmfVpcTransmitTrafficDescriptorType.ro INTEGER .1.3.6.1.4.1.353.2.4.1.1.6 |
atmfVpcTransmitTrafficDescriptorParam3The third parameter of the transmit parameter vector
for this VPC, used according to the value of
atmfVpcTransmitTrafficDescriptorType.ro INTEGER .1.3.6.1.4.1.353.2.4.1.1.7 |
atmfVpcTransmitTrafficDescriptorParam4The fourth parameter of the transmit parameter vector
for this VPC, used according to the value of
atmfVpcTransmitTrafficDescriptorType.ro INTEGER .1.3.6.1.4.1.353.2.4.1.1.8 |
atmfVpcTransmitTrafficDescriptorParam5The fifth parameter of the transmit parameter vector
for this VPC, used according to the value of
atmfVpcTransmitTrafficDescriptorType.ro INTEGER .1.3.6.1.4.1.353.2.4.1.1.9 |
atmfVpcReceiveTrafficDescriptorTypeThe type of traffic management, applicable to the
traffic in the receive direction of this VPC. The type
may indicate none, or a type with one or more
parameters. These parameters are specified as a
parameter vector, in the corresponding instances of
the objects:
atmfVpcReceiveTrafficDescriptorParam1,
atmfVpcReceiveTrafficDescriptorParam2,
atmfVpcReceiveTrafficDescriptorParam3,
atmfVpcReceiveTrafficDescriptorParam4, and
atmfVpcReceiveTrafficDescriptorParam5.ro OBJECT IDENTIFIER .1.3.6.1.4.1.353.2.4.1.1.10 |
atmfVpcReceiveTrafficDescriptorParam1The first parameter of the receive parameter vector
for this VPC, used according to the value of
atmfVpcReceiveTrafficDescriptorType.ro INTEGER .1.3.6.1.4.1.353.2.4.1.1.11 |
atmfVpcReceiveTrafficDescriptorParam2The second parameter of the receive parameter vector
for this VPC, used according to the value of
atmfVpcReceiveTrafficDescriptorType.ro INTEGER .1.3.6.1.4.1.353.2.4.1.1.12 |
atmfVpcReceiveTrafficDescriptorParam3The third parameter of the receive parameter vector
for this VPC, used according to the value of
atmfVpcReceiveTrafficDescriptorType.ro INTEGER .1.3.6.1.4.1.353.2.4.1.1.13 |
atmfVpcReceiveTrafficDescriptorParam4The fourth parameter of the receive parameter vector
for this VPC, used according to the value of
atmfVpcReceiveTrafficDescriptorType.ro INTEGER .1.3.6.1.4.1.353.2.4.1.1.14 |
atmfVpcReceiveTrafficDescriptorParam5The fifth parameter of the receive parameter vector
for this VPC, used according to the value of
atmfVpcReceiveTrafficDescriptorType.ro INTEGER .1.3.6.1.4.1.353.2.4.1.1.15 |
atmfVpcQoSCategoryThis object should not be implemented except as
required for backward compatibility with version 2.0
of the UNI specification.roobsolete Enumeration .1.3.6.1.4.1.353.2.4.1.1.16 |
atmfVpcTransmitQoSClassThis object should not be implemented except as
required for backward compatibility with version 3.1
of the UNI specification.roobsolete INTEGER .1.3.6.1.4.1.353.2.4.1.1.17 |
atmfVpcReceiveQoSClassThis object should not be implemented except as
required for backward compatibility with version 3.1
of the UNI specification.roobsolete INTEGER .1.3.6.1.4.1.353.2.4.1.1.18 |
atmfVpcBestEffortIndicatorThe object is examined when
atmfVpcTransmitTrafficDescriptorType or
atmfVpcReceiveTrafficDescriptorType for the associated
connection is equal to atmfNoClpNoScr.
If this object is set to false(2), the network is requested
to apply the CBR.1 conformance definition. If this object
is set to true(1), the network is requested to apply the
UBR.1 conformance definition.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.353.2.4.1.1.19 |
atmfVpcServiceCategoryThe service category of this virtual path connection.ro AtmServiceCategory (ATM-TC-MIB) .1.3.6.1.4.1.353.2.4.1.1.20 |
atmfVccGroup OBJECT IDENTIFIER .1.3.6.1.4.1.353.2.5 |
atmfVccTableA table of status and parameter information on the
virtual channel connections which are visible at this
ATM Interface. There is one entry in this table for
each permanent virtual channel connection, including
reserved VCCs that are supported; e.g., signalling,
OAM flows, and ILMI, but not unassigned cells. SEQUENCE OF AtmfVccEntry .1.3.6.1.4.1.353.2.5.1 |
atmfVccEntryAn entry in the table, containing information about a
particular virtual channel connection. AtmfVccEntry .1.3.6.1.4.1.353.2.5.1.1 |
atmfVccPortIndexThe value of 0 which has the special meaning of
identifying the ATM Interface over which this message
was received.ro INTEGER .1.3.6.1.4.1.353.2.5.1.1.1 |
atmfVccVpiThe VPI value of this Virtual Channel Connection at
the local ATM Interface. For virtual interfaces (i.e.
Virtual Path Connections), this value has no meaning
and is set to zeroro INTEGER .1.3.6.1.4.1.353.2.5.1.1.2 |
atmfVccVciThe VCI value of this Virtual Channel Connection at
the local ATM Interface.ro INTEGER .1.3.6.1.4.1.353.2.5.1.1.3 |
atmfVccOperStatusThe present actual operational status of the VCC. A
value of end2endUp(2) or end2endUp(3) is used if the
end to end status is known.
If only local status is known a value of
localUpEnd2endUnknown(4) or localDown(5) is used.ro Enumeration .1.3.6.1.4.1.353.2.5.1.1.4 |
atmfVccTransmitTrafficDescriptorTypeThe type of traffic management, applicable to the
transmit direction of this VCC. The type may indicate
none, or a type with one or more parameters. These
parameters are specified as a parameter vector, in the
corresponding instances of the objects:
atmfVccTransmitTrafficDescriptorParam1,
atmfVccTransmitTrafficDescriptorParam2,
atmfVccTransmitTrafficDescriptorParam3,
atmfVccTransmitTrafficDescriptorParam4, and
atmfVccTransmitTrafficDescriptorParam5.ro OBJECT IDENTIFIER .1.3.6.1.4.1.353.2.5.1.1.5 |
atmfVccTransmitTrafficDescriptorParam1The first parameter of the transmit parameter vector
for this VCC, used according to the value of
atmfVccTransmitTrafficDescriptorType.ro INTEGER .1.3.6.1.4.1.353.2.5.1.1.6 |
atmfVccTransmitTrafficDescriptorParam2The second parameter of the transmit parameter vector
for this VCC, used according to the value of
atmfVccTransmitTrafficDescriptorType.ro INTEGER .1.3.6.1.4.1.353.2.5.1.1.7 |
atmfVccTransmitTrafficDescriptorParam3The third parameter of the transmit parameter vector
for this VCC, used according to the value of
atmfVccTransmitTrafficDescriptorType.ro INTEGER .1.3.6.1.4.1.353.2.5.1.1.8 |
atmfVccTransmitTrafficDescriptorParam4The fourth parameter of the transmit parameter vector
for this VCC, used according to the value of
atmfVccTransmitTrafficDescriptorType.ro INTEGER .1.3.6.1.4.1.353.2.5.1.1.9 |
atmfVccTransmitTrafficDescriptorParam5The fifth parameter of the transmit parameter vector
for this VCC, used according to the value of
atmfVccTransmitTrafficDescriptorType.ro INTEGER .1.3.6.1.4.1.353.2.5.1.1.10 |
atmfVccReceiveTrafficDescriptorTypeThe type of traffic management, applicable to the
traffic in the receive direction of this VCC. The type
may indicate none, or a type with one or more
parameters. These parameters are specified as a
parameter vector, in the corresponding instances of
the objects:
atmfVccReceiveTrafficDescriptorParam1,
atmfVccReceiveTrafficDescriptorParam2,
atmfVccReceiveTrafficDescriptorParam3,
atmfVccReceiveTrafficDescriptorParam4, and
atmfVccReceiveTrafficDescriptorParam5.ro OBJECT IDENTIFIER .1.3.6.1.4.1.353.2.5.1.1.11 |
atmfVccReceiveTrafficDescriptorParam1The first parameter of the receive parameter vector
for this VCC, used according to the value of
atmfVccReceiveTrafficDescriptorType.ro INTEGER .1.3.6.1.4.1.353.2.5.1.1.12 |
atmfVccReceiveTrafficDescriptorParam2The second parameter of the receive parameter vector
for this VCC, used according to the value of
atmfVccReceiveTrafficDescriptorType.ro INTEGER .1.3.6.1.4.1.353.2.5.1.1.13 |
atmfVccReceiveTrafficDescriptorParam3The third parameter of the receive parameter vector
for this VCC, used according to the value of
atmfVccReceiveTrafficDescriptorType.ro INTEGER .1.3.6.1.4.1.353.2.5.1.1.14 |
atmfVccReceiveTrafficDescriptorParam4The fourth parameter of the receive parameter vector
for this VCC, used according to the value of
atmfVccReceiveTrafficDescriptorType.ro INTEGER .1.3.6.1.4.1.353.2.5.1.1.15 |
atmfVccReceiveTrafficDescriptorParam5The fifth parameter of the receive parameter vector
for this VCC, used according to the value of
atmfVccReceiveTrafficDescriptorType.ro INTEGER .1.3.6.1.4.1.353.2.5.1.1.16 |
atmfVccQoSCategoryThis object should not be implemented except as
required for backward compatibility with version 2.0
of the UNI specification.roobsolete Enumeration .1.3.6.1.4.1.353.2.5.1.1.17 |
atmfVccTransmitQoSClassThis object should not be implemented except as
required for backward compatibility with version 3.1
of the UNI specification.roobsolete INTEGER .1.3.6.1.4.1.353.2.5.1.1.18 |
atmfVccReceiveQoSClassThis object should not be implemented except as
required for backward compatibility with version 3.1
of the UNI specification.roobsolete INTEGER .1.3.6.1.4.1.353.2.5.1.1.19 |
atmfVccBestEffortIndicatorThe object is examined when
atmfVccTransmitTrafficDescriptorType or
atmfVccReceiveTrafficDescriptorType for the associated
connection is equal to atmfNoClpNoScr.
If this object is set to false(2), the network is requested
to apply the CBR.1 conformance definition. If this object
is set to true(1), the network is requested to apply the
UBR.1 conformance definition.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.353.2.5.1.1.20 |
atmfVccTransmitFrameDiscardIf set to true(1), this object indicates that the network
is requested to treat data for this connection (in the
transmit direction) as frames (e.g. AAL5 CPCS-PDU's) rather
than as individual cells. While the precise
implementation is network-specific, this treatment may
for example involve discarding entire frames during
congestion, rather than a few cells from many frames.
The default value is false(2).ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.353.2.5.1.1.21 |
atmfVccReceiveFrameDiscardIf set to true(1), this object indicates that the network
is requested to treat data for this connection (in the
receive direction) as frames (e.g. AAL5 CPCS-PDU's) rather
than as individual cells. While the precise
implementation is network-specific, this treatment may
for example involve discarding entire frames during
congestion, rather than a few cells from many frames.
The default value is false(2).ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.353.2.5.1.1.22 |
atmfVccServiceCategoryThe service category of this virtual channel connection.ro AtmServiceCategory (ATM-TC-MIB) .1.3.6.1.4.1.353.2.5.1.1.23 |
atmfAddressGroup OBJECT IDENTIFIER .1.3.6.1.4.1.353.2.6 |
atmfAddressTableA table implemented by the network-side IME, containing the
ATM-layer addresses in effect on the user side of the UNI. SEQUENCE OF AtmfAddressEntry .1.3.6.1.4.1.353.2.6.1 |
atmfAddressEntryInformation about a single ATM-layer address in effect
on the user-side IME. Note that the index variable
atmAddressAtmAddress is a variable-length string, and as
such the rule for variable-length strings in section
4.1.6 of RFC 1212 applies. AtmfAddressEntry .1.3.6.1.4.1.353.2.6.1.1 |
atmfAddressPortA unique value which identifies the UNI port for
which the ATM address is in effect. The value of 0
has the special meaning of identifying the local UNI. INTEGER .1.3.6.1.4.1.353.2.6.1.1.1 |
atmfAddressAtmAddressThe ATM address which is in effect on the user side
of the ATM UNI port. AtmAddress .1.3.6.1.4.1.353.2.6.1.1.2 |
atmfAddressStatusAn indication of the validity of the ATM address at
the user side of the UNI port. To configure a new
address in this table, the user-side IME must set the
appropriate instance of this object to the value
valid(1). To delete an existing address in this table,
the user-side IME must set the appropriate instance of
this object to the value invalid(2).
If circumstances occur on the network-side IME which cause
an address to become invalid, the network-side IME
modifies the value of the appropriate instance of this
object to invalid(2).
Whenever the value of this object for a particular
address becomes invalid(2), the conceptual row for
that address may be removed from the table at any
time, either immediately or subsequently.rw Enumeration .1.3.6.1.4.1.353.2.6.1.1.3 |
atmfAddressOrgScopeThis object indicates the organizational
scope for the referenced address. The information of
the referenced address shall not be distributed
outside the indicated scope. If the user-side IME does
not specify a value for the atmfAddressOrgScope object,
the network shall set the value of this object to
localNetwork(1), if the registered address is an ATM group
address, or to global(15), if the registered address is
an individual address. Refer to Annex 6.0
of ATM Forum UNI Signalling 4.0 for guidelines regarding
the use of organizational scopes.
This organization hierarchy may be mapped to ATM network's
routing hierarchy such as PNNI's routing level and
the mapping shall be configurable in
nodes. Use of this object in a public network is for
further study.
The default values for organizational scope are
localNetwork(1) for ATM group addresses, and global(15)
for individual addresses.rw Enumeration .1.3.6.1.4.1.353.2.6.1.1.4 |
atmfNetPrefixGroup OBJECT IDENTIFIER .1.3.6.1.4.1.353.2.7 |
atmfNetPrefixTableA table implemented by the user-side IME, containing the
network-prefix(es) for ATM-layer addresses in effect on
the user side of the UNI. Unknown .1.3.6.1.4.1.353.2.7.1 |
atmfNetPrefixEntryInformation about a single network-prefix for
ATM-layer addresses in effect on the user-side IME.
Note that the index variable atmNetPrefixPrefix is a
variable-length string, and as such the rule for
variable-length strings in section 4.1.6 of RFC 1212
applies. AtmfNetPrefixEntry .1.3.6.1.4.1.353.2.7.1.1 |
atmfNetPrefixPortA unique value which identifies the UNI port for
which the network prefix for ATM addresses is in
effect. The value of 0 has the special meaning of
identifying the local UNI. INTEGER .1.3.6.1.4.1.353.2.7.1.1.1 |
atmfNetPrefixPrefixThe network prefix for ATM addresses which is in
effect on the user side of the ATM UNI port. NetPrefix .1.3.6.1.4.1.353.2.7.1.1.2 |
atmfNetPrefixStatusAn indication of the validity of the network prefix
for ATM addresses on the user side of the UNI port.
To configure a new network prefix in this table, the
network-side IME must set the appropriate instance of this
object to the value valid(1). To delete an existing
network prefix in this table, the network-side IME must
set the appropriate instance of this object to the
value invalid(2).
If circumstances occur on the user-side IME which cause a
prefix to become invalid, the user-side IME modifies the
value of the appropriate instance of this object to invalid(2).
Whenever the value of this object for a particular
prefix becomes invalid(2), the conceptual row for that
prefix may be removed from the table at any time,
either immediately or subsequently.rw Enumeration .1.3.6.1.4.1.353.2.7.1.1.3 |
atmfSrvcRegistryGroup OBJECT IDENTIFIER .1.3.6.1.4.1.353.2.8 |
atmfVpcAbrGroup OBJECT IDENTIFIER .1.3.6.1.4.1.353.2.9 |
atmfVpcAbrTableA table of operational parameters related to the ABR
virtual path connections which cross this ATM
Interface. There is one entry in this table for each
ABR virtual path connection.
Each virtual path connection represented
in this table must also be represented by
an entry in the atmfVpcTable. SEQUENCE OF AtmfVpcAbrEntry .1.3.6.1.4.1.353.2.9.1 |
atmfVpcAbrEntryAn entry in the table, containing information about a
particular ABR virtual path connection. AtmfVpcAbrEntry .1.3.6.1.4.1.353.2.9.1.1 |
atmfVpcAbrPortIndexThe value of 0 which has the special meaning of identifying
the ATM Interface over which this message was received.ro INTEGER .1.3.6.1.4.1.353.2.9.1.1.1 |
atmfVpcAbrVpiThe VPI value of this ABR Virtual Path Connection at the
local ATM Interface.ro INTEGER .1.3.6.1.4.1.353.2.9.1.1.2 |
atmfVpcAbrTransmitIcrInitial Cell Rate: This is the rate at which the
source starts, both initially and after an idle period.
The unit is cells per second. The value must not be
larger than PCR, and is usually lower.ro INTEGER .1.3.6.1.4.1.353.2.9.1.1.3 |
atmfVpcAbrTransmitNrmThe maximum number of data cells a source may send
for each forward RM-cell. The default value is nrm32(5).ro Enumeration .1.3.6.1.4.1.353.2.9.1.1.4 |
atmfVpcAbrTransmitTrmUpper bound on the time between forward RM-cells for
an active source (in milliseconds). The default value
is trm100(8).ro Enumeration .1.3.6.1.4.1.353.2.9.1.1.5 |
atmfVpcAbrTransmitCdfCutoff Decrease Factor: This field controls the rate
decrease associated with lost or delayed backward RM
cells. Larger values result in faster rate decrease.
The default value is cdfOneOver16(4).ro Enumeration .1.3.6.1.4.1.353.2.9.1.1.6 |
atmfVpcAbrTransmitRifRate Increment Factor: Controls the rate at which the rate
increases, when a backward RM-cell is received with CI=0 and
NI=0. Larger values lead to faster rate increase. The default
value is rifOneOver16(12).ro Enumeration .1.3.6.1.4.1.353.2.9.1.1.7 |
atmfVpcAbrTransmitRdfRate Decrease Factor: Controls the rate decrease
which occurs when backward RM-cells with CI=1, are
received. Larger values lead to faster rate
decrease. The default value is rdfOneOver16(12).ro Enumeration .1.3.6.1.4.1.353.2.9.1.1.8 |
atmfVpcAbrTransmitAdtfACR Decrease Time Factor: Time permitted between
sending RM-cells, before the allowed rate (ACR) is
decreased to ICR. Range is 10 ms to 10.23 seconds.
The unit is 10 milliseconds. For example, the default
value of 50 corresponds to a time factor of 500 ms.
Larger values allow a source to retain its current
rate longer, during periods of relative inactivity.
The default is 50 (0.5 seconds).ro INTEGER .1.3.6.1.4.1.353.2.9.1.1.9 |
atmfVpcAbrTransmitCrmRM Cells Before Cutoff: Limits the number of forward
RM-cells which may be sent in the absence of received
backward RM-cells.ro INTEGER .1.3.6.1.4.1.353.2.9.1.1.10 |
atmfVccAbrGroup OBJECT IDENTIFIER .1.3.6.1.4.1.353.2.10 |
atmfVccAbrTableA table of operational parameters related to the ABR
virtual channel connections which cross this ATM
Interface. There is one entry in this table for each
ABR virtual channel connection.
Each virtual channel connection represented
in this table must also be represented by
an entry in the atmfVccTable. SEQUENCE OF AtmfVccAbrEntry .1.3.6.1.4.1.353.2.10.1 |
atmfVccAbrEntryAn entry in the table, containing information about a
particular ABR virtual channel connection. AtmfVccAbrEntry .1.3.6.1.4.1.353.2.10.1.1 |
atmfVccAbrPortIndexThe value of 0 which has the special meaning of identifying
the ATM Interface over which this message was received.ro INTEGER .1.3.6.1.4.1.353.2.10.1.1.1 |
atmfVccAbrVpiThe VPI value of this ABR Virtual Channel Connection at the
local ATM Interface. For virtual interfaces (i.e. Virtual Path
Connections), this value has no meaning and is set to zeroro INTEGER .1.3.6.1.4.1.353.2.10.1.1.2 |
atmfVccAbrVciThe VCI value of this ABR Virtual Channel Connection at the
local ATM Interface.ro INTEGER .1.3.6.1.4.1.353.2.10.1.1.3 |
atmfVccAbrTransmitIcrInitial Cell Rate: This is the rate at which the
source starts, both initially and after an idle period.
The unit is cells per second. The value must not be
larger than PCR, and is usually lower.ro INTEGER .1.3.6.1.4.1.353.2.10.1.1.4 |
atmfVccAbrTransmitNrmThe maximum number of data cells a source may send
for each forward RM-cell. The default value is nrm32(5).ro Enumeration .1.3.6.1.4.1.353.2.10.1.1.5 |
atmfVccAbrTransmitTrmUpper bound on the time between forward RM-cells for
an active source (in milliseconds). The default value
is trm100(8).ro Enumeration .1.3.6.1.4.1.353.2.10.1.1.6 |
atmfVccAbrTransmitCdfCutoff Decrease Factor: This field controls the rate
decrease associated with lost or delayed backward RM
cells. Larger values result in faster rate decrease.
The default value is cdfOneOver16(4).ro Enumeration .1.3.6.1.4.1.353.2.10.1.1.7 |
atmfVccAbrTransmitRifRate Increment Factor: Controls the rate at which the rate
increases, when a backward RM-cell is received with CI=0 and
NI=0. Larger values lead to faster rate increase. The default
value is rifOneOver16(12).ro Enumeration .1.3.6.1.4.1.353.2.10.1.1.8 |
atmfVccAbrTransmitRdfRate Decrease Factor: Controls the rate decrease
which occurs when backward RM-cells with CI=1, are
received. Larger values lead to faster rate
decrease. The default value is rdfOneOver16(12).ro Enumeration .1.3.6.1.4.1.353.2.10.1.1.9 |
atmfVccAbrTransmitAdtfACR Decrease Time Factor: Time permitted between
sending RM-cells, before the allowed rate (ACR) is
decreased to ICR. Range is 10 ms to 10.23 seconds.
The unit is 10 milliseconds. For example, the default
value of 50 corresponds to a time factor of 500 ms.
Larger values allow a source to retain its current
rate longer, during periods of relative inactivity.
The default is 50 (0.5 seconds).ro INTEGER .1.3.6.1.4.1.353.2.10.1.1.10 |
atmfVccAbrTransmitCrmRM Cells Before Cutoff: Limits the number of forward
RM-cells which may be sent in the absence of received
backward RM-cells.ro INTEGER .1.3.6.1.4.1.353.2.10.1.1.11 |
atmfAddressRegistrationAdminGroup OBJECT IDENTIFIER .1.3.6.1.4.1.353.2.11 |
atmfAddressRegistrationAdminTableA table of Address Registration administrative
information for the ATM Interface. SEQUENCE OF AtmfAddressRegistrationAdminEntry .1.3.6.1.4.1.353.2.11.1 |
atmfAddressRegistrationAdminEntryAn entry in the table, containing Address
Registration administrative information for the ATM
Interface. AtmfAddressRegistrationAdminEntry .1.3.6.1.4.1.353.2.11.1.1 |
atmfAddressRegistrationAdminIndexThe value of 0 which has the special meaning of
identifying the ATM Interface over which this message
was received.ro INTEGER .1.3.6.1.4.1.353.2.11.1.1.1 |
atmfAddressRegistrationAdminStatusAn indication of whether or not Address Registration
is supported on this ATM Interface. Supported(1)
indicates that this ATM Interface supports address
registration. Unsupported(2) indicates that this ATM
Interface does not support address registration.ro Enumeration .1.3.6.1.4.1.353.2.11.1.1.2 |
system OBJECT IDENTIFIER .1.3.6.1.4.1.727.7.2.1.1 |
sysDescrA textual description of the entity. This value
should include the full name and version
identification of the system's hardware type,
software operating-system, and networking
software. It is mandatory that this only contain
printable ASCII characters.ro DisplayString .1.3.6.1.4.1.727.7.2.1.1.1 |
sysObjectIDThe vendor's authoritative identification of the
network management subsystem contained in the
entity. This value is allocated within the SMI
enterprises subtree (1.3.6.1.4.1) and provides an
easy and unambiguous means for determining `what
kind of box' is being managed. For example, if
vendor `Flintstones, Inc.' was assigned the
subtree 1.3.6.1.4.1.4242, it could assign the
identifier 1.3.6.1.4.1.4242.1.1 to its `Fred
Router'.ro OBJECT IDENTIFIER .1.3.6.1.4.1.727.7.2.1.1.2 |
sysUpTimeThe time (in hundredths of a second) since the
network management portion of the system was last
re-initialized.ro TimeTicks (SNMPv2-SMI) .1.3.6.1.4.1.727.7.2.1.1.3 |
sysContactThe textual identification of the contact person
for this managed node, together with information
on how to contact this person.ro DisplayString .1.3.6.1.4.1.727.7.2.1.1.4 |
sysNameAn administratively-assigned name for this
managed node. By convention, this is the node's
fully-qualified domain name.ro DisplayString .1.3.6.1.4.1.727.7.2.1.1.5 |
sysLocationThe physical location of this node (e.g.,
`telephone closet, 3rd floor').ro DisplayString .1.3.6.1.4.1.727.7.2.1.1.6 |
sysServicesA value which indicates the set of services that
this entity primarily offers.
The value is a sum. This sum initially takes the
value zero, Then, for each layer, L, in the range
1 through 7, that this node performs transactions
for, 2 raised to (L - 1) is added to the sum. For
example, a node which performs primarily routing
functions would have a value of 4 (2^(3-1)). In
contrast, a node which is a host offering
application services would have a value of 72
(2^(4-1) + 2^(7-1)). Note that in the context of
the Internet suite of protocols, values should be
calculated accordingly:
layer functionality
1 physical (e.g., repeaters)
2 datalink/subnetwork (e.g., bridges)
3 internet (e.g., IP gateways)
4 end-to-end (e.g., IP hosts)
7 applications (e.g., mail relays)
For systems including OSI protocols, layers 5 and
6 may also be counted.ro INTEGER .1.3.6.1.4.1.727.7.2.1.1.7 |