AXD301-ILMI-MIB: View SNMP OID List / Download MIB

A 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.

The 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'.

The time (in hundredths of a second) since the network management portion of the system was last re-initialized.

The textual identification of the contact person for this managed node, together with information on how to contact this person.

An administratively-assigned name for this managed node. By convention, this is the node's fully-qualified domain name.

The physical location of this node (e.g., `telephone closet, 3rd floor').

A 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.

A table of physical layer status and parameter information for the ATM Interface's physical interface.

An entry in the table, containing information about the physical layer of an ATM Interface.

The value of 0 which has the special meaning of identifying the ATM Interface over which this message was received.

This 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.

This 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.

This 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.

This 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. Enumeration: 'outOfService': 3, 'loopBack': 4, 'other': 1, 'inService': 2.

This 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.

A 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.

A 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.

An 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.

An 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.0

A 48 bit identifier, taken from the IEEE universally administered MAC address space, which uniquely identifies the ATM device local to this IME.

A table of ATM layer status and parameter information for the ATM Interface.

An entry in the table, containing information about the ATM layer of an ATM Interface.

The value of 0 which has the special meaning of identifying the ATM Interface over which this message was received.

The 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.

The maximum number of switched and permanent VCCs supported on this ATM Interface.

The 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.

The number of permanent VCCs configured for use on this ATM Interface.

The 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.

The maximum number of active VCI bits on this ATM Interface.

The type of the ATM device, either public or private. Enumeration: 'public': 1, 'private': 2.

An 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. Enumeration: 'version4point0': 4, 'version2point0': 1, 'unsupported': 5, 'version3point1': 3, 'version3point0': 2.

This 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). Enumeration: 'node': 2, 'user': 1.

An 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. Enumeration: 'version4point0': 2, 'unsupported': 1.

An 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. Enumeration: 'iisp': 2, 'pnniVersion1point0': 3, 'unsupported': 1.

The maximum VPI that the signalling stack on the ATM interface is configured to support for allocation to switched virtual path connections.

The maximum VPI that the signalling stack on the ATM interface is configured to support for allocation to switched virtual channel connections.

This 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.

A 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.

An entry in the table, containing information about a particular virtual path connection.

The value of 0 which has the special meaning of identifying the ATM Interface over which this message was received.

The VPI value of this Virtual Path Connection at the local ATM Interface.

The 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. Enumeration: 'unknown': 1, 'localUpEnd2endUnknown': 4, 'end2endUp': 2, 'end2endDown': 3, 'localDown': 5.

The 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.

The first parameter of the transmit parameter vector for this VPC, used according to the value of atmfVpcTransmitTrafficDescriptorType.

The second parameter of the transmit parameter vector for this VPC, used according to the value of atmfVpcTransmitTrafficDescriptorType.

The third parameter of the transmit parameter vector for this VPC, used according to the value of atmfVpcTransmitTrafficDescriptorType.

The fourth parameter of the transmit parameter vector for this VPC, used according to the value of atmfVpcTransmitTrafficDescriptorType.

The fifth parameter of the transmit parameter vector for this VPC, used according to the value of atmfVpcTransmitTrafficDescriptorType.

The 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.

The first parameter of the receive parameter vector for this VPC, used according to the value of atmfVpcReceiveTrafficDescriptorType.

The second parameter of the receive parameter vector for this VPC, used according to the value of atmfVpcReceiveTrafficDescriptorType.

The third parameter of the receive parameter vector for this VPC, used according to the value of atmfVpcReceiveTrafficDescriptorType.

The fourth parameter of the receive parameter vector for this VPC, used according to the value of atmfVpcReceiveTrafficDescriptorType.

The fifth parameter of the receive parameter vector for this VPC, used according to the value of atmfVpcReceiveTrafficDescriptorType.

This object should not be implemented except as required for backward compatibility with version 2.0 of the UNI specification. Enumeration: 'deterministic': 2, 'other': 1, 'unspecified': 4, 'statistical': 3.

This object should not be implemented except as required for backward compatibility with version 3.1 of the UNI specification.

This object should not be implemented except as required for backward compatibility with version 3.1 of the UNI specification.

The 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.

The service category of this virtual path connection.

A 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.

An entry in the table, containing information about a particular virtual channel connection.

The value of 0 which has the special meaning of identifying the ATM Interface over which this message was received.

The 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 zero

The VCI value of this Virtual Channel Connection at the local ATM Interface.

The 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. Enumeration: 'unknown': 1, 'localUpEnd2endUnknown': 4, 'end2endUp': 2, 'end2endDown': 3, 'localDown': 5.

The 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.

The first parameter of the transmit parameter vector for this VCC, used according to the value of atmfVccTransmitTrafficDescriptorType.

The second parameter of the transmit parameter vector for this VCC, used according to the value of atmfVccTransmitTrafficDescriptorType.

The third parameter of the transmit parameter vector for this VCC, used according to the value of atmfVccTransmitTrafficDescriptorType.

The fourth parameter of the transmit parameter vector for this VCC, used according to the value of atmfVccTransmitTrafficDescriptorType.

The fifth parameter of the transmit parameter vector for this VCC, used according to the value of atmfVccTransmitTrafficDescriptorType.

The 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.

The first parameter of the receive parameter vector for this VCC, used according to the value of atmfVccReceiveTrafficDescriptorType.

The second parameter of the receive parameter vector for this VCC, used according to the value of atmfVccReceiveTrafficDescriptorType.

The third parameter of the receive parameter vector for this VCC, used according to the value of atmfVccReceiveTrafficDescriptorType.

The fourth parameter of the receive parameter vector for this VCC, used according to the value of atmfVccReceiveTrafficDescriptorType.

The fifth parameter of the receive parameter vector for this VCC, used according to the value of atmfVccReceiveTrafficDescriptorType.

This object should not be implemented except as required for backward compatibility with version 2.0 of the UNI specification. Enumeration: 'deterministic': 2, 'other': 1, 'unspecified': 4, 'statistical': 3.

This object should not be implemented except as required for backward compatibility with version 3.1 of the UNI specification.

This object should not be implemented except as required for backward compatibility with version 3.1 of the UNI specification.

The 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.

If 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).

If 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).

The service category of this virtual channel connection.

A table implemented by the network-side IME, containing the ATM-layer addresses in effect on the user side of the UNI.

Information 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.

A 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.

The ATM address which is in effect on the user side of the ATM UNI port.

An 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. Enumeration: 'valid': 1, 'invalid': 2.

This 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. Enumeration: 'organizationMinusOne': 7, 'global': 15, 'sitePlusOne': 6, 'intraCommunity': 11, 'regional': 13, 'intraOrganization': 8, 'localNetwork': 1, 'organizationPlusOne': 9, 'localNetworkPlusOne': 2, 'siteMinusOne': 4, 'localNetworkPlusTwo': 3, 'intraSite': 5, 'interRegional': 14, 'communityMinusOne': 10, 'communityPlusOne': 12.

A 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.

Information 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.

A 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.

The network prefix for ATM addresses which is in effect on the user side of the ATM UNI port.

An 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. Enumeration: 'valid': 1, 'invalid': 2.

A 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.

An entry in the table, containing information about a particular ABR virtual path connection.

The value of 0 which has the special meaning of identifying the ATM Interface over which this message was received.

The VPI value of this ABR Virtual Path Connection at the local ATM Interface.

Initial 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.

The maximum number of data cells a source may send for each forward RM-cell. The default value is nrm32(5). Enumeration: 'nrm32': 5, 'nrm128': 7, 'nrm16': 4, 'nrm8': 3, 'nrm256': 8, 'nrm2': 1, 'nrm64': 6, 'nrm4': 2.

Upper bound on the time between forward RM-cells for an active source (in milliseconds). The default value is trm100(8). Enumeration: 'trm0point78125': 1, 'trm12point5': 5, 'trm25': 6, 'trm1point5625': 2, 'trm100': 8, 'trm3point125': 3, 'trm50': 7, 'trm6point25': 4.

Cutoff 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). Enumeration: 'cdfOneOver8': 5, 'cdfOneOver2': 7, 'cdf0': 1, 'cdfOneOver4': 6, 'cdfOneOver64': 2, 'cdfOneOver16': 4, 'cdfOne': 8, 'cdfOneOver32': 3.

Rate 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). Enumeration: 'rifOneOver512': 7, 'rifOneOver32': 11, 'rifOneOver16384': 2, 'rifOneOver2048': 5, 'rifOneOver1024': 6, 'rifOneOver4': 14, 'rifOneOver256': 8, 'rifOneOver2': 15, 'rifOneOver8': 13, 'rifOneOver128': 9, 'rifOneOver4096': 4, 'rifOneOver16': 12, 'rifOneOver8192': 3, 'rifOneOver64': 10, 'rifOneOver32768': 1, 'rifOne': 16.

Rate 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). Enumeration: 'rdfOneOver256': 8, 'rdfOneOver32': 11, 'rdfOneOver32768': 1, 'rdfOneOver2048': 5, 'rdfOneOver512': 7, 'rdfOneOver64': 10, 'rdfOneOver16384': 2, 'rdfOneOver128': 9, 'rdfOneOver8192': 3, 'rdfOneOver8': 13, 'rdfOneOver4': 14, 'rdfOneOver4096': 4, 'rdfOne': 16, 'rdfOneOver2': 15, 'rdfOneOver1024': 6, 'rdfOneOver16': 12.

ACR 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).

RM Cells Before Cutoff: Limits the number of forward RM-cells which may be sent in the absence of received backward RM-cells.

A 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.

An entry in the table, containing information about a particular ABR virtual channel connection.

The value of 0 which has the special meaning of identifying the ATM Interface over which this message was received.

The 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 zero

The VCI value of this ABR Virtual Channel Connection at the local ATM Interface.

Initial 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.

The maximum number of data cells a source may send for each forward RM-cell. The default value is nrm32(5). Enumeration: 'nrm32': 5, 'nrm128': 7, 'nrm16': 4, 'nrm8': 3, 'nrm256': 8, 'nrm2': 1, 'nrm64': 6, 'nrm4': 2.

Upper bound on the time between forward RM-cells for an active source (in milliseconds). The default value is trm100(8). Enumeration: 'trm0point78125': 1, 'trm12point5': 5, 'trm25': 6, 'trm1point5625': 2, 'trm100': 8, 'trm3point125': 3, 'trm50': 7, 'trm6point25': 4.

Cutoff 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). Enumeration: 'cdfOneOver8': 5, 'cdfOneOver2': 7, 'cdf0': 1, 'cdfOneOver4': 6, 'cdfOneOver64': 2, 'cdfOneOver16': 4, 'cdfOne': 8, 'cdfOneOver32': 3.

Rate 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). Enumeration: 'rifOneOver512': 7, 'rifOneOver32': 11, 'rifOneOver16384': 2, 'rifOneOver2048': 5, 'rifOneOver1024': 6, 'rifOneOver4': 14, 'rifOneOver256': 8, 'rifOneOver2': 15, 'rifOneOver8': 13, 'rifOneOver128': 9, 'rifOneOver4096': 4, 'rifOneOver16': 12, 'rifOneOver8192': 3, 'rifOneOver64': 10, 'rifOneOver32768': 1, 'rifOne': 16.

Rate 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). Enumeration: 'rdfOneOver256': 8, 'rdfOneOver32': 11, 'rdfOneOver32768': 1, 'rdfOneOver2048': 5, 'rdfOneOver512': 7, 'rdfOneOver64': 10, 'rdfOneOver16384': 2, 'rdfOneOver128': 9, 'rdfOneOver8192': 3, 'rdfOneOver8': 13, 'rdfOneOver4': 14, 'rdfOneOver4096': 4, 'rdfOne': 16, 'rdfOneOver2': 15, 'rdfOneOver1024': 6, 'rdfOneOver16': 12.

ACR 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).

RM Cells Before Cutoff: Limits the number of forward RM-cells which may be sent in the absence of received backward RM-cells.

A table of Address Registration administrative information for the ATM Interface.

An entry in the table, containing Address Registration administrative information for the ATM Interface.

The value of 0 which has the special meaning of identifying the ATM Interface over which this message was received.

An 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. Enumeration: 'supported': 1, 'unsupported': 2.

An 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.

An 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.