Juniper-UNI-ATM-MIB: View SNMP OID List / Download MIB

The ATM MIB for the Juniper enterprise.

Coordinate ifIndex value allocation for entries in juniAtmIfTable. A GET of this object returns the next available ifIndex value to be used to create an entry in the associated interface table; or zero, if no valid ifIndex value is available. This object also returns a value of zero when it is the lexicographic successor of a varbind presented in an SNMP GETNEXT or GETBULK request, for which circumstance it is assumed that ifIndex allocation is unintended. Successive GETs will typically return different values, thus avoiding collisions among cooperating management clients seeking to create table entries simultaneously.

This table contains entries for ATM interfaces present in the system.

Each entry describes the characteristics of an ATM interface. Creating/deleting entries in this table causes corresponding entries for be created/deleted in ifTable/ifXTable/juniIfTable.

The ifIndex of the ATM interface. When creating entries in this table, suitable values for this object are determined by reading juniAtmNextIfIndex.

Controls creation/deletion of entries in this table according to the RowStatus textual convention, constrained to support the following values only: createAndGo destroy To create an entry in this table, the following entry objects MUST be explicitly configured: juniAtmIfRowStatus juniAtmIfLowerIfIndex In addition, when creating an entry the following condition must hold: A value for juniAtmIfIndex must have been determined previously, by reading juniAtmNextIfIndex. A corresponding entry in ifTable/ifXTable/juniIfTable is created or destroyed as a result of creating/destroying an entry in this table.

The ifIndex of an interface over which this ATM interface is to be layered. A value of zero indicates no layering. An implementation may choose to require that a nonzero value be configured at entry creation.

The VPI of the ILMI of a major ATM interface.

The VCI of the ILMI of a major ATM interface.

An integer identifier for the ILMI, used in conjunction with the command-line interface. The value must be unique among VCs configured on the same ATM interface.

The amount of time in seconds between successive transmissions of ILMI messages on this interface for the purpose of detecting loss of ILMI connectivity. The distinguished value zero disables ILMI connectivity procedures on this interface.

The administrative status of ILMI in the ATM interface. Enumeration: 'disabled': 0, 'enabled': 1.

Use to specify the User Network Interface (UNI) the router should use when ILMI link auto determination is unsuccesful or ILMI is disabled. Enumeration: 'uniVersionAutoConfig': 0, 'version4Dot0': 3, 'version3Dot0': 1, 'version3Dot1': 2.

Use to specify the OAM Cell Receive Administrative state on this interface. Enumeration: 'oamCellAdminStateDisabled': 0, 'oamCellAdminStateEnabled': 1.

The total number of cells received on this major interface.

The total number of cells transmitted on this major interface.

The total number of circuits configured on this interface.

The NBMA map group this interface is associated with.

The administrative staus of CAC on this ATM major interface.

The bandwidth associated with every UBR and UBR with PCR connection configured on the ATM major interface. This value is used for CAC computation. The units are kilo-bits per second (kbps).

The subscribed bandwidth of the ATM major interface. If this value is not specified or set to 0, the effective port bandwidth is used. When a Get operation is performed the current effective bandwidth is returned. The units are kilo-bits per second (kbps).

The available bandwidth in Tx direction of the ATM major interface. As connections are added or deleted on the interface, this value is updated. The units are kilo-bits per second (kbps).

The available bandwidth in Rx direction of the ATM major interface. As connections are added or deleted on the interface, this value is updated. The units are kilo-bits per second (kbps).

The status of E164 autoconversion feature in the ATM interface. Enumeration: 'disabled': 0, 'enabled': 1.

The status of E164 gateway feature in the ATM interface. Enumeration: 'disabled': 0, 'enabled': 1.

The status of E164 one-to-one address translation feature in the ATM interface. Enumeration: 'disabled': 0, 'enabled': 1.

The type of OAM cells to discard when juniAtmIfOamCellRxAdminState is set to oamCellAdminStateDisabled. The value oamCellFilterAlarm discards received OAM AIS and RDI cells. The value oamCellFilterAll discards all received OAM cells. Note that when juniAtmIfOamCellRxAdminState is set to oamCellAdminStateEnabled, this object has no effect. Enumeration: 'oamCellFilterAll': 0, 'oamCellFilterAlarm': 1.

The most significant 32 bits of the CAC used bandwidth on the ATM major interface. The least significant 32 bits of the CAC used bandwidth are specified by juniAtmIfCacUsedBandwidthLower.

The least significant 32 bits of the CAC used bandwidth on the ATM major interface. The most significant 32 bits of the CAC used bandwidth are specified by juniAtmIfCacUsedBandwidthUpper.

The integer identifier of the ATM VC class associated with this ATM interface. A value for this identifier is determined by locating or creating an ATM VC class name in the juniAtmVcClassNameTable. A value of 0 means no VC class association exists for this interface.

This table contains statistics for PVC entries.

Each entry provides statistics on an ATM PVC.

The ifIndex of the ATM interface.

The VPI of the ATM VCC used by this ATM interface and PVC.

The VCI of the ATM VCC used by this ATM interface and PVC.

Received cells.

Received cells octets.

Received AAL PDUs.

Received AAL PDU octets.

Transmitted cells.

Transmitted cell octets.

Transmitted AAL PDUs.

Transmitted AAL PDU octets.

Received cells dropped due to errors.

Received packets dropped due to errors.

Cells not transmitted due to errors.

Packets not transmitted due to errors.

Received packets w/o errors discarded.

Received bytes w/o errors discarded.

Received packets that are discarded because the interface can not discern or is not configured to support this protocol.

This table contains entries for ATM VP Tunnels present in the system.

Each entry describes the characteristics of an ATM VP Tunnel.

The ifIndex of the ATM interface. The value of this object is the same as the juniAtmIfIndex object in the juniAtmIfTable. Entries in this table cannot be created unless the underlying ATM interface entry is created first in the juniAtmIfTable.

The VPI value for this VP tunnel entry.

The tunnel rate in kilobits per second (kbps) for this entry.

Controls creation/deletion of entries in this table according to the RowStatus textual convention, constrained to support the following values only: createAndGo destroy To create an entry in this table, the following entry objects MUST be explicitly configured: juniAtmVpTunnelRowStatus juniAtmVpTunnelKbps In addition, when creating an entry the following condition must hold: A correponding juniAtmVpTunnelIfIndex value must have been created in the juniAtmIfTable previously.

The ATM service category for the tunnel. Enumeration: 'nrtVbr': 1, 'cbr': 2.

This table contains entries for ATM interfaces present in the system.

Each entry describes the capabilities of an ATM interface. A management client can use this table to determine differences in the configurable level of support across entries in this table.

The ifIndex of the ATM interface. The value of this object is the same as juniAtmIfIndex in the juniAtmIfTable.

Indicates whether traffic shaping is supported on this interface; true(1) indicates that it is, false(2) indicates that it is not.

Indicates whether OAM is supported on this interface; true(1) indicates that it is, false(2) indicates that it is not.

The default number of VCs per VP for this interface.

The total range of bits used for constructing VPI/VCI identifiers for this interface.

The maximum configurable value for a VCD on this interface.

The maximum configurable value for a VPI on this interface.

The maximum configurable value for a VCI on this interface.

Indicates whether OAM cell filter is supported on this interface; true(1) indicates that it is, false(2) indicates that it is not.

This table contains entries for extending the juniAtmIfTable for configuring signalling information for switched virtual connection (SVC).

Each entry provides configuration parameters for ATM signalling on the interface.

The VPI identifier of the ATM circuit used for signalling for this interface.

The VCI identifier of the ATM circuit used for signalling for this interface.

An integer identifier for the ATM circuit used for signalling on this interface.

The administrative status of signalling on the ATM interface.

This table contains entries for extending the juniAtmIfTable for configuring PNNI RCC information.

Each entry provides configuration parameters for PNNI RCC on the interface.

The VPI identifier of the ATM circuit used for PNNI RCC on this interface.

The VCI identifier of the ATM circuit used for PNNI RCC on this interface.

An integer identifier for the ATM circuit used for PNNI RCC on this interface.

The administrative status of PNNI on the ATM interface.

This table contains entries for F4 OAM end-to-end flows configured.

Each entry provides configuration parameters for one F4 OAM end-to-end flow configured for each VPI.

The ifIndex of the ATM interface to configure the F4 OAM end-to-end flow.

Select the VPI for F4 OAM end-to-end flow configuration.

Configure the timer for sending the F4 flow end-to-end loopback OAM cells. Setting this value will enable sending the F4 end cells on the circuit. It is not allowed to set the value to -1 and whenever it is read as -1 that means sending end loopback is not enabled. Setting the loopback timer, other than -1, will enable sending the end cells.

Enable/Disable F4 flow end-to-end continuity check sink end point for this VP.

Enable/Disable F4 flow end-to-end continuity check source end point for this VP.

Controls creation/deletion of entries in this table according to the RowStatus textual convention, constrained to support the following values only: createAndGo destroy To create/delete an entry in this table, the following entry objects MUST be explicitly configured: juniAtmOamF4FlowEndToEndRowStatus F4 OAM end loopback and CC tests are mutually exclusive, enabling one will disable the other automatically. So, it is not allowed either at the circuit creation time or after the circuit creation to issue a request to enable end-to-end loopback and CC tests simultaneouly. Enabling/disabling CC sink and source is one time operation. To re-enable either CC source and sink in way different to earlier, both has to be disabled from the previous.

This table contains entries for F4 OAM Segment flows configured.

Each entry provides configuration parameters for one F4 OAM Segment flow configured for each VPI.

The ifIndex of the ATM interface to configure the F4 OAM segment flow.

Select the VPI for F4 OAM segment flow configuration.

Enable/Disable F4 flow segment continuity check sink end point for this VP.

Enable/Disable F4 flow segment continuity check source end point for this VP.

Controls creation/deletion of entries in this table according to the RowStatus textual convention, constrained to support the following values only: createAndGo destroy To create/delete an entry in this table, the following entry objects MUST be explicitly configured: juniAtmOamF4FlowSegmentRowStatus Enabling/disabling CC sink and source is one time operation. To re-enable either CC source and sink in way different to earlier, both has to be disabled from the previous. F4 OAM segment loopback test is not supported.

This table contains entries for ATM VP Description present in the system. The user can configure a description of up to 32 characters for every VP in the ATM interface. A row exists for every VP on the ATM interface. These rows get created as soon as the ATM major interface created.

Each entry contains the description of the VP.

The description for this VP. The default value of this object is null string.

This table contains entries for F4 flow EndToEnd OAM circuits stats.

Each entry provides stats for one F4 OAM circuit for each VPI.

Received end-to-end OAM F4 AIS cells.

Received end-to-end OAM F4 RDI cells.

Received end-to-end OAM F4 CC cells.

Received end-to-end OAM F4 activation/de-activation cells.

Total received OAM F4 end-to-end loopback cells. Aggregate of juniAtmF4FlowEndToEndInLoopbackCmds and juniAtmF4FlowEndToEndInLoopbackRsps

Transmitted end-to-end OAM F4 RDI cells.

Transmitted end-to-end OAM F4 CC cells.

Transmitted end-to-end OAM F4 activation/de-activation cells.

Total transmitted OAM F4 end-to-end loopback cells. Aggregate of juniAtmF4FlowEndToEndOutLoopbackCmds and juniAtmF4FlowEndToEndOutLoopbackRsps

Actual end-to-end loopback Frequecy calculated for OAM cells transmission.

Last time end-to-end F4 OAM flow got changed.

Represents the F4 end-to-end OAM flow VP operation states. It can take one of the following operational state values: vcAisState - AIS cell received or underlying physical layer reporting transmission path AIS. vcRdiState - RDI cell received. vcDownRetry - OAM loopback failed, using retry frequency to verify that the VC is really down. vcUpRetry - OAM loopback successful, using retry frequency to verify that the VC is really up. vcUp - OAM loopback successful after up retry verification. vcDown - OAM loopback failed after down retry verification. vcNotManaged - No verification via loopback cells being performed. vpAisState - State when F4 AIS cell is received. vpRdiState - State when F4 RDI cell is received. vcInVpRdiState - The data vc is down as a result of VP failure thorugh F4 Rdi oam cell. vcInVpAisState - The data vc is down as a result of VP failure through F4 Ais oam cell. vcSegmentAisState - Segment AIS cell received. vcSegRdiState - Segment RDI cell received. Enumeration: 'vcDown': 5, 'vpRdiState': 8, 'vcRdiState': 1, 'vcInVpAisState': 10, 'vcUpRetry': 3, 'vcDownRetry': 2, 'vcInVpRdiState': 9, 'vcNotManaged': 6, 'vcSegmentAisState': 11, 'vcUp': 4, 'vpAisState': 7, 'vcSegRdiState': 12, 'vcAisState': 0.

End-to-end VP admin state. Enumeration: 'down': 0, 'up': 1.

Received end-to-end OAM F4 loopback cells.

Transmitted end-to-end OAM F4 loopback cells.

Received end-to-end OAM cells that were dropped.

Received OAM F4 end-to-end loopback commands.

Received OAM F4 end-to-end loopback responses.

Transmitted OAM F4 end-to-end loopback commands.

Transmitted OAM F4 end-to-end loopback responses.

This table contains entries for F4 flow Segment OAM circuits stats.

Each entry provides stats for one F4 OAM circuit for each VPI.

Received end-to-end OAM F4 AIS cells.

Received end-to-end OAM F4 RDI cells.

Received end-to-end OAM F4 CC cells.

Received end-to-end OAM F4 activation/de-activation cells.

Total received OAM F4 segment loopback cells. Aggregate of juniAtmF4FlowSegmentInLoopbackCmds and juniAtmF4FlowSegmentInLoopbackRsps

Transmitted end-to-end OAM F4 RDI cells.

Transmitted end-to-end OAM F4 CC cells.

Transmitted end-to-end OAM F4 activation/de-activation cells.

Total transmitted OAM F4 segment loopback cells. Aggregate of juniAtmF4FlowSegmentOutLoopbackCmds and juniAtmF4FlowSegmentOutLoopbackRsps

Last time end-to-end F4 OAM flow got changed.

Represents the F4 end-to-end OAM flow VP operation states. It can take one of the following operational state values: vcAisState - AIS cell received or underlying physical layer reporting transmission path AIS. vcRdiState - RDI cell received. vcDownRetry - OAM loopback failed, using retry frequency to verify that the VC is really down. vcUpRetry - OAM loopback successful, using retry frequency to verify that the VC is really up. vcUp - OAM loopback successful after up retry verification. vcDown - OAM loopback failed after down retry verification. vcNotManaged - No verification via loopback cells being performed. vpAisState - State when F4 AIS cell is received. vpRdiState - State when F4 RDI cell is received. vcInVpRdiState - The data vc is down as a result of VP failure thorugh F4 Rdi oam cell. vcInVpAisState - The data vc is down as a result of VP failure through F4 Ais oam cell. vcSegmentAisState - Segment AIS cell received. vcSegRdiState - Segment RDI cell received. Enumeration: 'vcDown': 5, 'vpRdiState': 8, 'vcRdiState': 1, 'vcInVpAisState': 10, 'vcUpRetry': 3, 'vcDownRetry': 2, 'vcInVpRdiState': 9, 'vcNotManaged': 6, 'vcSegmentAisState': 11, 'vcUp': 4, 'vpAisState': 7, 'vcSegRdiState': 12, 'vcAisState': 0.

Segment VP admin state. Enumeration: 'down': 0, 'up': 1.

Received end-to-end OAM F4 loopback cells.

Transmitted end-to-end OAM F4 loopback cells.

Received end-to-end OAM cells that were dropped.

Received OAM F4 segment loopback commands.

Received OAM F4 segment loopback responses.

Transmitted OAM F4 segment loopback commands.

Transmitted OAM F4 segment loopback responses.

This table contains entries for ATM Martini cell aggregation timeout detection. The user can configure timeout values for three timers. A row exists for every separate timer supported. These rows get created as soon as the ERX system comes up.

Each entry contains the timeout value of ATM Martini cell aggregation timer.

The ATM Martini cell aggregation timeout timer identifier. Enumeration: 'timer3': 3, 'timer2': 2, 'timer1': 1.

The ATM Martini cell aggregation timeout timer value in microseconds.

This table contains entries for ATM VP statistics present in the system. A row exists for every VP on the ATM interface. These rows get created as soon as the ATM major interface created.

Each entry contain the VP statistics.

The ifIndex of the ATM interface.

The VPI value of the virtual path for which statistics are retrieved.

Received cells.

Received AAL5 PDUs.

Received AAL5 PDU octets.

Transmitted cells.

Transmitted AAL5 PDUs

Transmitted AAL5 PDU octets.

Received packets dropped due to errors.

Packets not transmitted due to errors.

Received packets without errors discarded.

Received bytes without errors discarded.

Received packets that are discarded because the interface can not discern or is not configured to support this protocol.

Received packets that are discarded because of check sum erros

Received packets that are discarded because of SAR timeout

Over sized packets that are received on this VP.

Coordinate ifIndex value allocation for entries in juniAtmAal5IfTable. A GET of this object returns the next available ifIndex value to be used to create an entry in the associated interface table; or zero, if no valid ifIndex value is available. This object also returns a value of zero when it is the lexicographic successor of a varbind presented in an SNMP GETNEXT or GETBULK request, for which circumstance it is assumed that ifIndex allocation is unintended. Successive GETs will typically return different values, thus avoiding collisions among cooperating management clients seeking to create table entries simultaneously.

This table contains entries for ATM AAL5 interfaces present in the system.

Each entry describes the characteristics of an ATM AAL5 interface. Creating/deleting entries in this table causes corresponding entries for be created/deleted in ifTable/ifXTable/juniIfTable.

The ifIndex of the ATM AAL5 interface. When creating entries in this table, suitable values for this object are determined by reading juniAtmAal5NextIfIndex.

Controls creation/deletion of entries in this table according to the RowStatus textual convention, constrained to support the following values only: createAndGo destroy To create an entry in this table, the following entry objects MUST be explicitly configured: juniAtmAal5IfRowStatus juniAtmAal5IfLowerIfIndex In addition, when creating an entry the following condition must hold: A value for juniAtmAal5IfIndex must have been determined previously, by reading juniAtmAal5NextIfIndex. A corresponding entry in ifTable/ifXTable/juniIfTable is created or destroyed as a result of creating/destroying an entry in this table.

The ifIndex of an ATM interface over which this ATM AAL5 interface is to be layered. A value of zero indicates no layering. An implementation may choose to require that a nonzero value be configured at entry creation.

The entries in this table provide mappings of ATM bulk virtual circuit range names to local integer identifiers for those profiles. These integers are used as indexes into other MIB tables containing profile configuration parameters associated with the same profile name.

A mapping of a ATM bulk virtual circuit range name to an integer identifier for that name.

The ifIndex of the ATM AAL5 interface.

The ATM bulk virtual circuit range name uniquely identifying this entry.

Controls creation/deletion of entries in this table. Only the values 'createAndGo' and 'destroy' may be SET. Creating an entry in this table creates corresponding entry in juniAtmBulkCircuitsIdTable. Deleting an entry in this table deletes corresponding entries in juniAtmBulkCircuitsIdTable, juniAtmBulkCircuitsTable and juniAtmProfileOverrideAssignIfCircuitTable.

The integer identifier associated with this ATM bulk virtual circuit range name. This value of this identifier is assigned by the device when an entry in this table is created.

Provides inverse mapping of ATM bulk virtual circuit IDs to ATM bulk virtual circuit names.

A mapping of an integer identifier to a ATM bulk virtual circuit name.

The ifIndex of the ATM AAL5 interface.

The integer identifier associated with this ATM bulk virtual circuit name.

The ATM bulk virtual circuit name having the associated identifier.

The next available instance value for juniAtmBulkCircuitsEntry.

This table contains bulk virtual circuit range parameters.

Each entry describes the characteristics of VC range.

The ifIndex of the ATM AAL5 interface on which this bulk virtual circuit sub-range is created.

The integer identifier associated with this ATM bulk virtual circuit name.

The unique identifier of the ATM bulk virtual circuit sub-range.

Controls creation/deletion of entries in this table. Only the values 'createAndGo' and 'destroy' may be SET. Since none of the VPI/VCI minimum and maximum values have default values, all these values must be specified before setting RowStatus to 'createAndGo'. The VPI/VCI minimum and maximum values can only be configured upon creation. Deleting an entry in this table deletes corresponding entries in juniAtmProfileOverrideAssignIfCircuitTable.

The minimum value of VPI for this circuit sub-range. This value must be less than or equal to the value of juniAtmBulkCircuitsMaxVpi.

The maximum value of VPI for this cicuit sub-range. This value must be equal to or greater than the value of juniAtmBulkCircuitsMinVpi.

The minimum value of VCI for this circuit sub-range. This value must be less than or equal to the value of juniAtmBulkCircuitsMaxVci.

The maximum value of VCI for this circuit sub-range. This value must be equal to or greater than the value of juniAtmBulkCircuitsMinVci.

The administrative status of this circuit sub-range.

Table providing overriding profile assignment to a circuit configured as part of bulk-configuration. Circuit is identified by interface index and vpi, vci. The entries in this table specify which profile to use when creating and configuring a dynamic interface above a circuit specified by vpi and vci. This entry is effective when the circuit specified by juniAtmProfileOverrideAssignIfCircuitAal5Index, juniAtmProfileOverrideAssignIfCircuitRangeId, juniAtmProfileOverrideAssignIfCircuitVpi, juniAtmProfileOverrideAssignIfCircuitVci is part of bulk-configuration.

An assignment of a profile to a circuit configured as part of bulk-configuration on an AAL5 interface.

The ifIndex of the AAL5 interface to which the profile is assigned.

The integer identifier associated with the ATM bulk circuit configuration.

The VPI value of the circuit to which the profile is assigned.

The VCI value of the circuit to which the profile is assigned.

Controls creation/deletion of entries in this table. Only the values 'createAndGo' and 'destroy' may be SET. Since the VPI, VCI and profileId values do not have any default values, all these values must be specified before setting RowStatus to 'createAndGo'. The VPI, VCI and profileId values can only be configured upon creation. None of these values can be modified except by deleting the entry.

The ID of the profile assigned to the circuit configured as part of bulk-configuration. Circuit is identified by interface index and vpi, vci.

The operational status of the profile override assignment identified by this entry. It returns inactive(0), if a static ATM circuit with identical VPI/VCI values is present on the same ATM interface. In this case, this profile override will not be used to configure upper dynamic interfaces. It returns active(1), if no static ATM circuit with identical VPI/VCI values is present on the same ATM interface. In this case, this profile override will be used to configure upper dynamic interfaces. Enumeration: 'active': 1, 'inactive': 0.

Coordinate ifIndex value allocation for entries in juniAtmSubIfTable. A GET of this object returns the next available ifIndex value to be used to create an entry in the associated interface table; or zero, if no valid ifIndex value is available. This object also returns a value of zero when it is the lexicographic successor of a varbind presented in an SNMP GETNEXT or GETBULK request, for which circumstance it is assumed that ifIndex allocation is unintended. Successive GETs will typically return different values, thus avoiding collisions among cooperating management clients seeking to create table entries simultaneously.

This table contains entries for ATM Subinterfaces present in the system.

Each entry describes the characteristics of an ATM Subinterface. Creating/deleting entries in this table causes corresponding entries for be created/deleted in ifTable/ifXTable/juniIfTable.

The ifIndex of the ATM Subinterface. When creating entries in this table, suitable values for this object are determined by reading juniAtmSubNextIfIndex.

Controls creation/deletion of entries in this table according to the RowStatus textual convention, constrained to support the following values only: createAndGo destroy To create an entry in this table, the following entry objects MUST be explicitly configured: juniAtmSubIfRowStatus juniAtmSubIfLowerIndex In addition, when creating an entry the following condition must hold: A value for juniAtmSubIfIndex must have been determined previously, by reading juniAtmSubIfNextIfIndex. A corresponding entry in ifTable/ifXTable/juniIfTable is created or destroyed as a result of creating/destroying an entry in this table.

An integer identifier for the subinterface, used in conjunction with the command-line interface. It is provided here for cross-reference purposes only. The value must be unique among subinterfaces configured on the same underlying ATM adaptation layer. The upper bound for the value is further constrained to be identical with the maximum number of subinterfaces supported by the lower interface. If this object is not configured, a value will be allocated internally and can be queried after table entry creation has succeeded.

The ifIndex of an ATM AAL5 interface over which this ATM subinterface is to be layered. A value of zero indicates no layering. An implementation may choose to require that a nonzero value be configured at entry creation.

The NBMA administrative setting. Setting this value of this object to true(1) will enable multipoint access on this interface. Setting the value to false(2), will enable point to point access on this interface.

Specifies the local ATM NSAP address of the circuit. A GET operation returns a full 20-octet NSAP. A SET operation only requires 7 octets, since the prefix can be implied.

The size of the largest packet which can be sent/received on the interface, specified in octets.

Advisory receive speed, in kilobits per second (kbps), of this subinterface. This object has no impact on forwarding performance but may be used as a hint for underlying circuit receive speed.

The number of cells that can be aggregated in a single ATM Martini packet in cell-relay mode.

The timer identifier used to abandon cell aggregation when no cells are supplied for transmission in ATM Martini cell-relay mode.

The integer identifier of the ATM VC class associated with this ATM sub interface. A value for this identifier is determined by locating or creating an ATM VC class name in the juniAtmVcClassNameTable. A value of 0 means no VC class association exists for this interface.

This table contains entries for ATM VCCs configured on ATM subinterfaces present in the system. An implementation may constrain the number of VCCs permitted to be configured per ATM Subinterface; in particular, an implementation may restrict each ATM Subinterface to have a single VCC. Attributes in this entry can only be configured at entry creation, and remain fixed for the lifetime of the entry.

Each entry describes the characteristics of an ATM subinterface VCC.

The VPI of the ATM VCC used by this subinterface.

The VCI of the ATM VCC used by this subinterface.

Controls creation/deletion of entries in this table according to the RowStatus textual convention, constrained to support the following values only: createAndGo destroy To create an entry in this table, the following entry objects MUST be explicitly configured: juniAtmSubIfVccRowStatus In addition, when creating an entry the following conditions must hold: The ATM Subinterface identified by juniAtmSubIfIndex must exist. A positive value configured for juniAtmSubIfVccVcd must not already be assigned to an existing VCC. For each value of juniAtmSubIfVccServiceCategory, additional dependent objects in the entry require configuration as identified here: juniAtmSubIfVccServiceCategory Requires configuration of: ------------------------------------------------------------ ubr ubrPcr juniAtmSubIfVccPcr nrtVbr juniAtmSubIfVccPcr juniAtmSubIfVccScr juniAtmSubIfVccMbs cbr juniAtmSubIfVccPcr rtVbr juniAtmSubIfVccPcr juniAtmSubIfVccScr juniAtmSubIfVccMbs ------------------------------------------------------------ Attributes in this entry can only be configured at entry creation, and remain fixed for the lifetime of the entry.

An integer identifier for the circuit, used in conjunction with the command-line interface. It is provided here for cross-reference purposes only. The value must be unique among VCCs configured on the same underlying ATM interface. If this object is not configured, or is configured with a value of zero, a value will be allocated internally and can be queried after table entry creation has succeeded.

Specifies the encapsulation used by the circuit to carry IP datagrams. Encapsulations are as specified in RFC1483 Multiprotocol Interconnect over ATM. The 'autoconfig' value will recognize both VcMux and LLC formats. The 'aal5' and 'aal0' values are used for encapsulation methods for transport of ATM frames and cells over IP and MPLS networks when no encapsulation method is specified. Enumeration: 'rfc1483VcMux': 0, 'aal0': 4, 'rfc1483Llc': 1, 'autoconfig': 2, 'aal5': 3.

Service category for this circuit: ubr Unspecified Bit Rate (best effort). ubrPcr Unspecified Bit Rate with Peak Cell Rate limit. nrtVbr Non-RealTime Variable Bit Rate. cbr Constant Bit Rate. rtVbr Realtime Variable Bit Rate. Enumeration: 'nrtVbr': 2, 'cbr': 3, 'ubrPcr': 1, 'ubr': 0, 'rtVbr': 4.

Peak Cell Rate, in kilobits per second (kbps), of this circuit. This parameter is only required when juniAtmSubIfVccServiceCategory is configured to have one of the following values: ubrPcr nrtVbr cbr rtVbr

Sustained Cell Rate, in kilobits per second (kbps), of this circuit. This parameter is only required when juniAtmSubIfVccServiceCategory is configured to have the following value: nrtVbr rtVbr

Maximum Burst Size, in cells, of this circuit. This parameter is only required when juniAtmSubIfVccServiceCategory is configured to have the following value: nrtVbr rtVbr

Enables the inverse ARP protocol on this VCC; true(1) enables the protocol, false(2) disables it.

The refresh rate in minutes between inverse ARP protocol messages.

The integer identifier of the ATM VC class associated with this ATM sub interface. A value for this identifier is determined by locating or creating an ATM VC class name in the juniAtmVcClassNameTable. A value of 0 means no VC class association exists for this VC.

This table contains circuit OAM data for a PVC.

Each entry provides OAM data on an ATM PVC.

The ifIndex of the ATM subinterface.

The VPI of the ATM VCC used by this ATM interface and PVC.

The VCI of the ATM VCC used by this ATM interface and PVC.

The administrative state of OAM for the interface identified by this entry. Enumeration: 'oamAdminStateDisabled': 1, 'oamAdminStateEnabled': 2.

The operational status of OAM for the interface identified by this entry. oamOperStatusNotSupported(0) - OAM not supported on this interface oamOperStatusDisabled(1) - VC integrity disabled oamOperStatusSent(2) - Loopback sent, awaiting response oamOperStatusReceived(3) - Loopback response received, awaiting frequency oamOperStatusFailed(4) - Loopback response not received, or invalid response received Enumeration: 'oamOperStatusNotSupported': 0, 'oamOperStatusDisabled': 1, 'oamOperStatusReceived': 3, 'oamOperStatusSent': 2, 'oamOperStatusFailed': 4.

The OAM VC operational status of this entry. oamVcOperStateAisState(0) - AIS cell received or underlying physical layer reporting transmission path AIS oamVcOperStateRdiState(1) - RDI cell received oamVcOperStateDownRetry(2) - OAM loopback failed, using retry frequency to verify that the VC is really down oamVcOperStateUpRetry(3) - OAM loopback successful, using retry frequency to verify that the VC is really up oamVcOperStateUp(4) - OAM loopback successful after up retry verification oamVcOperStateDown(5) - OAM loopback failed after down retry verification oamVcOperStateNotManaged(6)- No verification via loopback cells being performed oamVcOperStateVpAis(7) - F4 AIS cell received oamVcOperStateVpRdi(8) - F4 RDI cell received oamVcOperStateVcInVpRdi(9) - F4 RDI cell received; path failure oamVcOperStateVcInVpAis(10)- F4 AIS cell received; path failure oamVcOperStateSegAis(11) - Segment AIS cell received oamVcOperStateSegRdi(12) - Segment RDI cell received oamVcOperStateGenAis(13) - Connection failure; generating AIS cells. Enumeration: 'oamVcOperStateSegAis': 11, 'oamVcOperStateGenAis': 13, 'oamVcOperStateVpRdi': 8, 'oamVcOperStateVcInVpRdi': 9, 'oamVcOperStateSegRdi': 12, 'oamVcOperStateDownRetry': 2, 'oamVcOperStateDown': 5, 'oamVcOperStateNotManaged': 6, 'oamVcoperStateVcInVpAis': 10, 'oamVcOperStateVpAis': 7, 'oamVcOperStateUp': 4, 'oamVcOperStateUpRetry': 3, 'oamVcOperStateAisState': 0, 'oamVcOperStateRdiState': 1.

The OAM loopback frequency in seconds.

Received OAM F5 cells.

Received OAM cells that were dropped.

Transmitted OAM F5 cells.

Total received OAM F5 end-to-end loopback cells. Aggregate of juniAtmCircuitInOamF5EndToEndLoopbackCmds and juniAtmCircuitInOamF5EndToEndLoopbackRsps

Total received OAM F5 segment loopback cells. Aggregate of juniAtmCircuitInOamF5SegmentLoopbackCmds and juniAtmCircuitInOamF5SegmentLoopbackRsps

Received OAM F5 AIS cells.

Received OAM F5 RDI cells.

Total transmitted OAM F5 end-to-end loopback cells. Aggregate of juniAtmCircuitOutOamF5EndToEndLoopbackCmds and juniAtmCircuitOutOamF5EndToEndLoopbackRsps

Total transmitted OAM F5 segment loopback cells. Aggregate of juniAtmCircuitOutOamF5SegmentLoopbackCmds and juniAtmCircuitOutOamF5SegmentLoopbackRsps

Transmitted OAM F5 RDI cells.

Received OAM F5 end-to-end loopback commands.

Received OAM F5 end-to-end loopback responses.

Received OAM F5 segment loopback commands.

Received OAM F5 segment loopback responses.

Transmitted OAM F5 end-to-end loopback commands.

Transmitted OAM F5 end-to-end loopback responses.

Transmitted OAM F5 segment loopback commands.

Transmitted OAM F5 segment loopback responses.

Specifies the number of successive loopback cell responses to receive before a PVC is up for connectivity verification.

Specifies the number of successive loopback cell responses not received before declaring a PVC down for connectivity verification.

Specifies the frequency (in seconds) to transmit loopback cells when verifying PVC state (up or down) for connectivity verification.

Specifies the number of successive alarm (AIS or RDI) cells to receive before declaring a PVC down.

Specifies how long to wait (in seconds) before declaring a PVC up after it has stopped receiving alarm cells.

This table contains entries for traffic shaping of ATM VCCs configured on ATM subinterfaces present in the system. This table augments the juniAtmSubIfVccTable only for VCCs that support traffic shapping. Attributes in this entry can only be configured at entry creation, and remain fixed for the lifetime of the entry.

Each entry describes the traffic shping characteristics of an ATM subinterface VCC.

The network cell delay variation tolerance (CDVT) in tenths of a microsecond.

Specifies whether or not only CLP0 cells are to be policed according to the traffic contract. CLP1 cells are forwarded on a best-effort basis CLP-significant model for (VBR.2, VBR.3 conformance). Applicable only for VBR circuits.

Specifies whether or not CLP0 cells should be tagged for SCR policing (VBR.3 conformance). Applicable only for VBR circuits.

Specifies whether of not no policing action is to be taken (note the double negative; if true(1) then no policing action will be taken; if false(2) then policing action will be taken). Regardless of the state of this object, all counters will be incremented.

Specifies whether of not to shape output traffic on a packet boundary.

This table contains entries for extending the juniAtmSubIfTable to configure switched virtual connection (SVC) on the subinterfaces.

Each entry provides configuration parameters for an ATM SVC on the subinterface.

Controls creation/deletion of entries in this table according to the RowStatus textual convention, constrained to support the following values only: createAndGo destroy

Specifies the destination ATM NSAP address of the circuit.

Specifies the encapsulation used by the circuit to carry IP datagrams. Encapsulations are as specified in RFC1483 Multiprotocol Interconnect over ATM. Enumeration: 'rfc1483VcMux': 0, 'rfc1483Llc': 1.

Service category for this circuit: ubr Unspecified Bit Rate (best effort). ubrPcr Unspecified Bit Rate with Peak Cell Rate limit. nrtVbr Non-RealTime Variable Bit Rate. cbr Constant Bit Rate. rtVbr Realtime Variable Bit Rate. Enumeration: 'nrtVbr': 2, 'cbr': 3, 'ubrPcr': 1, 'ubr': 0, 'rtVbr': 4.

Peak Cell Rate, in kilo-bits per second (kbps), of this circuit.

Sustained Cell Rate, in kilo-bits per second (kbps), of this circuit.

Maximum Burst Size, in cells, of this circuit.

Specify the network Cell Delay Variation Tolerance.

Specify that only CLP0 cells are to be policed according to the traffic contract. CLP1 cells are forwarded on a best-effort basis CLP-significant model for (VBR.2, VBR.3 conformance).

Specify that CLP0 cells should be tagged for SCR policing (VBR.3 conformance).

Specify that no policing action is to be taken; only counters are incremented.

Enable early packet Discard for this circuit.

Specifies the destination ATM E164 address of the circuit.

Enabling of this object will program the subinterface description down to the applicable line card. Note, the subinterface description sent down to the line card is a truncated version (32 bytes) of the ifAlias.

This table contains entries for ATM NBMA maps.

Each entry describes the characteristics of an ATM NBMA map.

The NBMA map name.

An integer identifier for the ATM circuit, used in conjunction with the command-line interface. The value must be unique among VCs configured on the same ATM interface.

The IP address associated with this entry.

The VPI identifier of the ATM circuit.

The VCI identifier of the ATM circuit.

The ifIndex of the ATM major interface associated with this entry. The value of this object will be zero when the map is not applied to an interface.

The broadcast enable/disable setting for this entry. The value true(1) enable broadcast support; disable(2) disabled broadcast support for this entry.

Controls creation/deletion of entries in this table according to the RowStatus textual convention, constrained to support the following values only: createAndGo destroy Additional notes to aid the network manager: - NBMA maps are not supported on dynamic interface. - NBMA maps can only be applied to a single major ATM interface at a time. - NBMA maps cannot be deleted unless the map is removed from the ATM interface (juniAtmNbmaMapIfIndex = 0). - The values of juniAtmNbmaMapVpi, juniAtmNbmaMapVci and juniAtmNbmaMapIfIndex are zero until the map is applied to a major ATM interface. - To create an entry in this table, the following objects must be present in the set PDU: juniAtmNbmaMapIpAddress juniAtmNbmaMapBroadcast juniAtmNbmaMapRowStatus - Once created, only the following objects can be modified: juniAtmNbmaMapBroadcast

This table contains entries for ATM NBMA map lists.

Each entry describes the characteristics of an ATM NBMA map.

The NBMA Map List name.

Controls creation/deletion of entries in this table according to the RowStatus textual convention, constrained to support the following values only: createAndGo destroy

This identifies an OAM Ping (multiple loopbacks) Test on a VPL, VPC, VCL, or VCC termination point, using segment OAM cells. The test type must have appended to it a code that uniquely identifies an intermediate point responsible for looping back each cell. If this is absent, the loopbacks are performed at the end of the segment or connection. E.g., the OID { juniAtmPingTestOamSeg 5 } identifies that the loopbacks should be performed at the intermediate point labeled 5.

This identifies an OAM Ping (multiple loopbacks) Test on a VPL, VPC, VCL, or VCC termination point, using end-to-end OAM cells.

This table contains entries for extending the ATM-FORUM-SNMP-M4-MIB atmM4VpTestTable to do ping (multiple loopback) type testing.

Each entry describes the characteristics, status and results of the most recent ATM ping test.

The number of ping probes (OAM cells) to be sent to complete the test.

Specifies the time-out value, in seconds, for a remote ping operation.

The value of this object determines when and if to generate a notification for this entry: testCompletion(0) - Generate a juniPingTestCompleted notification. The value of this object defaults to zero, indicating that no notification has been selected. Bits: 'testCompletion': 0.

The number of ping probes (OAM cells) that have been sent thus far for this test. The value of this object MUST be set to zero when the atmfM4VpTestStatus object transitions from notInUse(0) to inUse(1).

The number of ping responses that have been received thus far for this test. The value of this object MUST be set to zero when the atmfM4VpTestStatus object transitions from notInUse(0) to inUse(1).

The time (sysUpTime) when the test started.

The shortest round-trip-time (RTT) for the pings that have received responses. The value of this object MUST be set to zero when the atmfM4VpTestStatus object transitions from notInUse(0) to inUse(1). A value of zero for this object implies that no ping responses have been received for the current test.

The longest round-trip-time (RTT) for the pings that have received responses. The value of this object MUST be set to zero when the atmfM4VpTestStatus object transitions from notInUse(0) to inUse(1). A value of zero for this object implies that no ping responses have been received for the current test.

The average round-trip-time (RTT) for all the pings that have received responses. The value of this object MUST be set to zero when the atmfM4VpTestStatus object transitions from notInUse(0) to inUse(1). A value of zero for this object implies that no ping responses have been received for the current test.

This table contains entries for extending the ATM-FORUM-SNMP-M4-MIB atmM4VcTestTable to do ping (multiple loopback) type testing.

Each entry describes the characteristics, status and results of the most recent ATM ping test.

The number of ping probes (OAM cells) to be sent to complete the test.

Specifies the time-out value, in seconds, for a remote ping operation.

The value of this object determines when and if to generate a notification for this entry: testCompletion(0) - Generate a juniPingTestCompleted notification. The value of this object defaults to zero, indicating that no notification has been selected. Bits: 'testCompletion': 0.

The number of ping probes (OAM cells) that have been sent thus far for this test. The value of this object MUST be set to zero when the atmfM4VcTestStatus object transitions from notInUse(0) to inUse(1).

The number of ping responses that have been received thus far for this test. The value of this object MUST be set to zero when the atmfM4VcTestStatus object transitions from notInUse(0) to inUse(1).

The time (sysUpTime) when the test started.

The shortest round-trip-time (RTT) for the pings that have received responses. The value of this object MUST be set to zero when the atmfM4VcTestStatus object transitions from notInUse(0) to inUse(1). A value of zero for this object implies that no ping responses have been received for the current test.

The longest round-trip-time (RTT) for the pings that have received responses. The value of this object MUST be set to zero when the atmfM4VcTestStatus object transitions from notInUse(0) to inUse(1). A value of zero for this object implies that no ping responses have been received for the current test.

The average round-trip-time (RTT) for all the pings that have received responses. The value of this object MUST be set to zero when the atmfM4VcTestStatus object transitions from notInUse(0) to inUse(1). A value of zero for this object implies that no ping responses have been received for the current test.

This test code indicates that the ATM ping operation cannot be initiated or is aborted because the juniAtmIfOamCellRxAdminState is set to disabled.

This test code indicates that the ATM ping operation cannot be initiated or is aborted because the operational status of the ATM circuit is down.

This test code indicates that the ATM ping operation is administratively stopped by an External Management.

This test code indicates that the ATM ping operation cannot be initiated or is aborted because the circuit is down because of a OAM fault condition. This is possible if juniAtmCircuitVcOamOperStatus is one of the following: oamVcOperStateAisState(0) - AIS cell received or underlying physical layer reporting transmission path AIS. oamVcOperStateRdiState(1) - RDI cell received.

This test code indicates that the ping operation cannot be initiated as the maximum number of ping possible on this interfaces exceeds the allowable limit.

This Test Code identities the Ping operation cannot be initiated as one or more of the Ping Parameters is Invalid.

Describes the interpretation of JuniInterfaceLocationValue object values into platform-dependent interface location components, e.g., 'slot.port' on an ERX.

The entries in this table report the ifIndex of ATM Subinterfaces by location.

A specification of ATM subinterfaces by location.

The value of a platform interface location.

The ifIndex value of this subinterface.

The entries in this table provide mappings of ATM VC class names to local integer identifiers. These integers are used as indexes into other MIB tables containing ATM VC attributes associated with the same VC class name.

A mapping of ATM VC class name to an integer identifier for the ATM VC class.

The ATM VC class name uniquely identifying this entry.

Controls creation/deletion of entries in this table. Only the values 'createAndGo' ,'destroy', 'active' and 'notInService' may be SET. The SNMP manager would set the row status to notInService before making any VC class attribute changes explained in juniAtmVcClassTable. Once the VC class attribute changes are complete, the SNMP manager would set the row status to active, upon which the VC class attribute changes would be committed. Any ATM VC class attribute changes that are made when the row status is 'active' are committed right away.

The integer identifier associated with this VC class name. The value of this identifier is assigned by the device when an entry in this table is created.

Provides inverse mapping of ATM VC class IDs to ATM VC class names.

A mapping of an integer identifier to an ATM VC class name.

The integer identifier associated with this ATM VC class name.

The ATM VC class name having the associated identifier.

This table contains Juniper ATM VC Class entries which can be used to specify the ATM PVC attributes either at creation or modification time. A row in this table with default values is created when an entry in juniAtmVcClassNameTable is created.

Each entry contains the attributes of the ATM VC which would be applied to the VC either at creation or modification time when this ATM VC class is associated to it.

The integer identifier associated with this ATM VC class. A value for this identifier is determined by locating or creating an ATM VC class name in the juniAtmVcClassNameTable.

Specifies the encapsulation used by the circuit to carry IP datagrams. Encapsulations are as specified in RFC1483 Multiprotocol Interconnect over ATM. The 'autoconfig' value will recognize both VC Mux and LLC formats. The 'aal5' and 'aal0' values are used for encapsulation methods for transport of ATM frames and cells over IP and MPLS networks when no encapsulation method is specified. Enumeration: 'rfc1483VcMux': 0, 'aal0': 4, 'rfc1483Llc': 1, 'autoconfig': 2, 'aal5': 3.

Service category for this circuit: ubr Unspecified Bit Rate (best effort). ubrPcr Unspecified Bit Rate with Peak Cell Rate limit. nrtVbr Non-RealTime Variable Bit Rate. cbr Constant Bit Rate. rtVbr Realtime Variable Bit Rate. Enumeration: 'nrtVbr': 2, 'cbr': 3, 'ubrPcr': 1, 'ubr': 0, 'rtVbr': 4.

Peak Cell Rate, in kilobits per second (kbps), of this circuit. This parameter is only required when juniAtmVcClassVccServiceCategory is configured to have one of the following values: ubrPcr nrtVbr cbr rtVbr

Sustained Cell Rate, in kilobits per second (kbps), of this circuit. This parameter is only required when juniAtmVcClassVccServiceCategory is configured to have the following value: nrtVbr rtVbr

Maximum Burst Size, in cells, of this circuit. This parameter is only required when juniAtmVcClassVccServiceCategory is configured to have the following value: nrtVbr rtVbr

The OAM VC integrity administrative state of the ATM VC associated with this class. Enumeration: 'oamAdminStateDisabled': 1, 'oamAdminStateEnabled': 2.

The OAM loopback frequency in seconds.

Specifies the number of successive loopback cell responses to receive before the ATM VC associated with this class is declared up for connectivity verification.

Specifies the number of successive loopback cell responses not received before declaring the ATM VC associated with this class as down for connectivity verification.

Specifies the frequency (in seconds) to transmit loopback cells when verifying the ATM VC operational state associated with this class (up or down) for connectivity verification.

Specifies the number of successive alarm (AIS or RDI) cells to receive before declaring the ATM VC associated with class as down.

Specifies how long to wait (in seconds) before declaring the ATM VC associated with class as up after it has stopped receiving alarm cells.

Enables the inverse ARP protocol on the ATM VC associated with this class; true(1) enables the protocol, false(2) disables it.

The refresh rate in minutes between inverse ARP protocol messages.

Generated at the completion of a AtmfM4VpTest when the corresponding juniAtmVpPingCtlTrapGeneration object has the testCompletion(0) bit set.

Generated at the completion of a AtmfM4VcTest when the corresponding juniAtmVcPingCtlTrapGeneration object has the testCompletion(0) bit set.

Obsolete compliance statement for entities which implement the Juniper ATM MIB. This statement became obsolete when support was added for NBMA map lists and ATM ping.

Obsolete compliance statement for entities which implement the Juniper ATM MIB. This statement became obsolete when support was added for traffic shapping on VCC subinterfaces.

Obsolete compliance statement for entities which implement the Juniper ATM MIB. This statement became obsolete when support was added for connection admission control (CAC).

Obsolete compliance statement for entities which implement the Juniper ATM MIB. This statement became obsolete when ATM SVC, CAC used bandwidth and sub-interface address objects were added.

Obsolete compliance statement for entities which implement the Juniper ATM MIB. This statement became obsolete when CAC recieve bandwith and E164 public addressing support was added.

Obsolete compliance statement for entities which implement the Juniper ATM MIB. This statement became obsolete when F4 flow OAM circuit config and stats tables were added to the Juniper ATM MIB.

Obsolete compliance statement for entities which implement the Juniper ATM MIB. This statement became obsolete when the juniAtmLocationGroup was added.

Obsolete compliance statement for entities which implement the Juniper ATM MIB. This statement became obsolete when support was added to export the subinterface description to the line cards.

Obsolete compliance statement for entities which implement the Juniper ATM MIB. This statement was obsoleted when the juniAtmMartiniGroup was added.

Obsolete compliance statement for entities which implement the Juniper ATM MIB. This statement became obsolete when juniAtmIfCacAvailableBandwidthRx, juniAtmIfE164Autoconversion, juniAtmIfE164Gateway, and juniAtmIfE164OneToOneAddrTrans were deprecated.

Obsolete compliance statement for entities which implement the Juniper ATM MIB. This statement became obsolete when juniAtmGroup8 was added.

The compliance statement for entities which implement the Juniper ATM MIB. This statement became obsolete when juniAtmVpStatsGroup was added.

The compliance statement for entities which implement the Juniper ATM MIB. This statement became obsolete when SVC support was removed.

The compliance statement for entities which implement the Juniper ATM MIB.

Obsolete collection of objects providing management of ATM interfaces in a Juniper product. This group became obsolete when the juniAtmIfMapGroup object was added.

A collection of objects providing management of AAL5 interfaces in a Juniper product.

Obsolete collection of objects providing management of ATM subinterfaces in a Juniper product. This group became obsolete when juniAtmSubIfNbma, juniAtmSubIfInverseArp, and juniAtmSubIfInverseArpRefresh were added.

A collection of objects providing management of VP tunnels in a Juniper product.

A collection of object providing management of NBMA in a Juniper product.

Obsolete collection of objects providing management of ATM subinterfaces in a Juniper product. This group became obsolete when juniAtmSubIfAddress was added.

A collection of object providing management of ATM VPL Ping testing in a Juniper product.

A collection of object providing management of ATM VCL Ping testing in a Juniper product.

A collection of notifications supporting ATM Ping testing in a Juniper product.

Obsolete collection of objects providing management of ATM interfaces in a Juniper product. This group became obsolete when support was added for connection admission control (CAC).

A collection of objects providing management of ATM traffic shaping in a Juniper product.

Obsolete collection of objects providing management of ATM interfaces in a Juniper product. This group became obsolete when support was added for connection admission control (CAC) used bandwidth.

Obsolete collection of objects providing management of ATM interfaces in a Juniper product. This group became obsolete when CAC recieve bandwith and E164 public addressing objects were added.

Obsolete collection of objects providing management of ATM SVC interfaces in a Juniper product. This group became obsolete when E164 public addressing support was added.

Obsolete collection of objects providing management of ATM subinterfaces in a Juniper product. This group became obsolete when juniAtmSubIfMtu was added.

Obsolete collection of objects providing management of ATM interfaces in a Juniper product. This group became obsolete when ATM VP description support was added.

A collection of objects providing management of ATM SVC interfaces in a Juniper product.

A collection of objects providing management of PNNI Routing Control Channels in a Juniper product.

Obsolete collection of objects providing management of ATM subinterfaces in a Juniper product. This group became obsolete when support was added to export the subinterface description to the line cards.

Obsolete collection of objects providing management of ATM F4 flow OAM circuits in a Juniper product.

Obsolete collection of objects providing management of ATM interfaces in a Juniper product. This group became obsolete when bulk-configuration profile override support was added.

A collection of objects providing interface location information in a Juniper product.

Obsolete collection of objects providing management of ATM subinterfaces in a Juniper product.

A collection of objects providing ATM Martini cell aggregation configuration.

Obsolete collection of objects providing management of ATM interfaces in a Juniper product.

A collection of objects providing management of ATM interfaces in a Juniper product.

A collection of objects providing ATM VP level statistics.

Obsolete collection of objects providing management of ATM subinterfaces in a Juniper product. This group became obsolete when ATM SVC support was removed.

A collection of objects providing management of ATM F4 flow OAM circuits in a Juniper product.

A collection of objects providing management of ATM interfaces in a Juniper product.

A collection of objects providing management of ATM subinterfaces in a Juniper product.

A collection of objects providing management of ATM VC class in a Juniper product.