Nortel-MsCarrier-MscPassport-AtmPnniMIB: View SNMP OID List / Download MIB

This entry controls the addition and deletion of mscAtmIfVptPnni components.

A single entry in the table represents a single mscAtmIfVptPnni component.

This variable is used as the basis for SNMP naming of mscAtmIfVptPnni components. These components can be added and deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the mscAtmIfVptPnni tables.

This variable represents the index for the mscAtmIfVptPnni tables.

This entry controls the addition and deletion of mscAtmIfVptPnniSig components.

A single entry in the table represents a single mscAtmIfVptPnniSig component.

This variable is used as the basis for SNMP naming of mscAtmIfVptPnniSig components. These components cannot be added nor deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the mscAtmIfVptPnniSig tables.

This variable represents the index for the mscAtmIfVptPnniSig tables.

This entry controls the addition and deletion of mscAtmIfVptPnniSigVcd components.

A single entry in the table represents a single mscAtmIfVptPnniSigVcd component.

This variable is used as the basis for SNMP naming of mscAtmIfVptPnniSigVcd components. These components can be added and deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the mscAtmIfVptPnniSigVcd tables.

This variable represents the index for the mscAtmIfVptPnniSigVcd tables.

This group contains the provisionable traffic attributes for a control channel.

An entry in the mscAtmIfVptPnniSigVcdProvTable.

This attribute specifies the type of traffic management which is applied to both the transmit and receive direction of this connection as defined in the ATM Forum. The trafficDescType determines the number and meaning of the parameters in the trafficDescParm attribute. Enumeration: 'n8': 8, 'n3': 3, 'n6': 6, 'n7': 7.

This attribute specifies the ATM service category for both directions of the connection. The constantBitRate service category is intended for real time applications, that is those requiring tightly constrained delay and delay variation, as would be appropriate for voice and video applications. The consistent availability of a fixed quantity of bandwidth is considered appropriate for CBR service. Cells which are delayed beyond the value specified by CellTransfer Delay are assumed to be of significantly reduce value to the application. The rtVariableBitRate service category is intended for real time applications, that is those requiring tightly constrained delay and delay variation, as would be appropriate for voice and video applications. Sources are expected to transmit at a rate which varies with time. Equivalently, the source can be described as 'bursty'. Cells which are delayed beyond the value specified by CTD are assumed to be of significantly reduced value to the application. Real time VBR service may support statistical multiplexing of real time sources. The nrtVariableBitRate service category is intended for non-real time applications which have bursty traffic characteristics and which can be characterized in terms of a PCR, SCR, and MBS. For those cells which are transferred within the traffic contract, the application expects a low cell loss ratio. For all connections, it expects a bound on the mean cell transfer delay. Non-real time VBR service may support statistical multiplexing of connections. The unspecifiedBitRate service is intended for non-real time applications; that is, those not requiring tightly constrained delay and delay variation. UBR sources are expected to be bursty. UBR service supports a high degree of statistical multiplexing among sources. UBR service does not specify traffic related service guarantees. No numerical commitments are made with respect to the cell loss ratio experienced by a UBR connection, or as to the cell transfer delay experienced by cells on the connection. Enumeration: 'constantBitRate': 1, 'unspecifiedBitRate': 0, 'rtVariableBitRate': 2, 'nrtVariableBitRate': 3.

This attribute specifies an override for the weight of this unshaped connection. This attribute is ignored for shaped connections, for ABR connections, for connections on a CQC-based ATM FP and basic VPTs. When the value is set to sameAsCa, the weight is determined by the weight policy attribute under the CA service category component for all but standard VPT VCCs. For standard VPT VCCs, the weight is determined by the VCC's service category, when the value is set to sameAsCa. When this attribute is set to a value from 1 to 4095, that value is used for the weight policy of this connection relative to other connections. For all but standard VPT VCCs, weight policy determines the proportion of transit cell opportunities which are allocated to this connection, compared to other connections in the same service category. For standard VPT VCCs, weight policy determines the proportion of transmit cell opportunities which are allocated to this connection, compared to other connections associated with the VPT. When the value is set to upToQueueLimit, the weight policy is limited only by the txQueueLimit. VALUES ( 0 = upToQueueLimit 65535 = sameAsCa )

This attribute specifies the quality of service for both the forward and backward direction for this connection. Class 1 supports a QOS that meets Service Class A performance requirements (Circuit emulation, constant bit rate video). Class 2 supports a QOS that meets Service Class B performance requirements (Variable bit rate audio and video). Class 3 supports a QOS that meets Service Class C performance requirements (Connection-Oriented Data Transfer). Class 4 supports a QOS that meets Service Class D performance requirements (Connectionless Data Transfer). Class 0 is the unspecified bit rate QOS class; no objective is specified for the performance parameters. Enumeration: 'n0': 0, 'n1': 1, 'n2': 2, 'n3': 3, 'n4': 4.

This attribute specifies whether this connection uses traffic shaping when transmitting traffic to the ATM interface. When sameAsCa is selected, traffic shaping for this connection is based on the trafficShaping attribute of the connection's service category component under the AtmIf CA. If the service category has traffic shaping enabled, then traffic shaping is enabled for the connection. Note that enabling traffic shaping may have no effect under certain cases. These cases are listed in the description of the trafficShaping operational attribute, which is under the Vcc Tm and Vpc Tm components. When disabled is selected, traffic shaping for this connection is disabled. Enumeration: 'disabled': 1, 'sameAsCa': 2.

This attribute only applies when this connection is unshaped. This attribute specifies the transmit queueing method for this connection if it is unshaped. Refer to the unshapedTransmitQueueing attribute under the AtmIf CA service category subcomponent for more details on the meaning of this attribute. When this attribute is set to sameAsCa, the transmit queueing method for the connection is based on the unshapedTransmitQueueing attribute of the connection's service category component under the ConnectionAdministrator. When this attribute is set to common, transmit traffic on this unshaped connection is destined for the common queue. The value sameAsInterface is for migration from previous software releases, but should no longer be used Enumeration: 'sameAsCa': 3, 'common': 1.

This attribute specifies whether this connection enforces usage parameter control when receiving traffic from the ATM interface. When sameAsCa is selected, UPC for the connection is based on the usageParameterControl attribute of the connection's service category component under the ConnectionAdministrator. If the service category has UPC enabled, then UPC is enabled for the connection. Note that enabling UPC may have no effect under certain cases. These cases are listed in the description of the usageParameterControl operational attribute, which is under the Vcc Tm or Vpc Tm component. When disabled is selected, UPC for this connection is disabled. The value sameAsInterface is for migration from previous software releases, but should no longer be used Enumeration: 'disabled': 1, 'sameAsCa': 2.

This attribute is a vector of five traffic parameters whose meanings are defined by the trafficDescType attribute. The values of peak cell rate (PCR), sustained cell rate (SCR) and requested shaping rate are expressed in cell/s. Maximum burst size (MBS) is expressed in cells. CDVT is expressed in microseconds. The values of PCR, SCR, MBS and CDVT are used for connection admission control (CAC). The value of CDVT is only used for connections where the atmServiceCategory is constantBitRate. For all other values of atmServiceCategory, CDVT is ignored. The values of PCR, SCR and requested shaping rate are used to determine the actual shaping rate where traffic shaping is enabled. When trafficDescType is 3, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 4 represents the CDVT; and parameter 5 represents the requested shaping rate. A non-zero value in parameter 5 overrides any value in parameter 1. This result is used as the PCR. Parameter 1 must be non-zero. Parameters 2 and 3 must be zero. When trafficDescType is 6, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 2 represents the SCR for CLP equal to 0 and 1 traffic; parameter 3 represents the MBS for CLP equal to 0 and 1 traffic; parameter 4 represents the CDVT; and parameter 5 represents the requested shaping rate. A non-zero value in parameter 5 overrides any value in parameter 1. This result is used as the PCR. Parameters 1, 2, and 3 must be non-zero. Parameter 1 must be greater than or equal to parameter 2. Parameter 5 must either be zero (unused) or greater than or equal to parameter 2. When trafficDescType is 7, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 2 represents the SCR for CLP equal to 0 with cell discard; parameter 3 represents the MBS for CLP equal to 0 traffic; parameter 4 represents the CDVT; and parameter 5 represents the requested shaping rate. A non-zero value in parameter 5 overrides any value in parameter 1. This result is used as the PCR. Parameters 1, 2, and 3 must be non-zero. Parameter 1 must be greater than or equal to parameter 2. Parameter 5 must either be zero (unused) or greater than or equal to parameter 2. When trafficDescType is 8, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 2 represents the SCR for CLP equal to 0 traffic with cell tagging; parameter 3 represents the MBS for CLP equal to 0 traffic; parameter 4 represents the CDVT; and parameter 5 represents the requested shaping rate. A non-zero value in parameter 5 overrides any value in parameter 1. This result is used as the PCR. Parameters 1, 2, and 3 must be non-zero. Parameter 1 must be greater than or equal to parameter 2. Parameter 5 must either be zero (unused) or greater than or equal to parameter 2. Whenever it is valid for PCR to be specified, parameter 5 may also be used to specify a requested shaping rate. A non-zero value in parameter 5 overrides the value in parameter 1 and is used as the peak cell rate in calculations of CAC and shaping rate. For trafficDescType 3 the traffic is shaped at the next rate less than the PCR. For trafficDescType 6, 7, and 8, the traffic is shaped at the highest available rate which is between PCR and SCR. However, if there is no available shaping rate between PCR and SCR, traffic is shaped at the next rate above the PCR.

An entry in the mscAtmIfVptPnniSigVcdTdpTable.

This variable represents the mscAtmIfVptPnniSigVcdTdpTable specific index for the mscAtmIfVptPnniSigVcdTdpTable.

This variable represents an individual value for the mscAtmIfVptPnniSigVcdTdpTable.

This attribute group contains the provisionable attributes for the Signalling component.

An entry in the mscAtmIfVptPnniSigProvTable.

This attribute specifies the signalling channel number.

This attribute specifies the address conversion on the outgoing signalling PDUs. The options are none, nativeE164, or nsap. The none option is the default and if this option is chosen then nothing is done to the address information element (IE) in the outgoing signalling message. If nativeE164 option is chosen, then only NSAP encapsulated E.164 addresses with zeros in the ESI are converted to native E.164 format in the outgoing signalling message. If the NSAP address is not encapsulated E.164 or the ESI field is not zeros and the nativeE164 option is chosen, then the call is cleared. If the nsap option is chosen, then native E.164 addresses are converted to NSAP E.164 with zeros in the ESI field; otherwise the address is in NSAP format and is not changed. Enumeration: 'none': 0, 'nativeE164': 1, 'nsap': 2.

This attribute specifies the operating mode of the signaling channel. provisionedOnly indicates that only SPVCs and SPVPs are supported on the interface and SVCs are not supported. This value is permitted only on UNI interfaces. normal indicates that SVCs, SPVCs, and SPVPs are supported on the interface. Enumeration: 'provisionedOnly': 1, 'normal': 0.

This group contains the three OSI State attributes. The descriptions generically indicate what each state attribute implies about the component. Note that not all the values and state combinations described here are supported by every component which uses this group. For component-specific information and the valid state combinations, refer to NTP 241-7001-150, Passport Operations and Maintenance Guide.

An entry in the mscAtmIfVptPnniSigStateTable.

This attribute indicates the OSI Administrative State of the component. The value locked indicates that the component is administratively prohibited from providing services for its users. A Lock or Lock - force command has been previously issued for this component. When the value is locked, the value of usageState must be idle. The value shuttingDown indicates that the component is administratively permitted to provide service to its existing users only. A Lock command was issued against the component and it is in the process of shutting down. The value unlocked indicates that the component is administratively permitted to provide services for its users. To enter this state, issue an Unlock command to this component. Enumeration: 'locked': 0, 'shuttingDown': 2, 'unlocked': 1.

This attribute indicates the OSI Operational State of the component. The value enabled indicates that the component is available for operation. Note that if adminState is locked, it would still not be providing service. The value disabled indicates that the component is not available for operation. For example, something is wrong with the component itself, or with another component on which this one depends. If the value is disabled, the usageState must be idle. Enumeration: 'disabled': 0, 'enabled': 1.

This attribute indicates the OSI Usage State of the component. The value idle indicates that the component is not currently in use. The value active indicates that the component is in use and has spare capacity to provide for additional users. The value busy indicates that the component is in use and has no spare operating capacity for additional users at this time. Enumeration: 'active': 1, 'idle': 0, 'busy': 2.

This attribute contains the operational attributes for the AtmSignalling component.

An entry in the mscAtmIfVptPnniSigOperTable.

This attribute indicates the cause code in the last transmitted signalling message that contains the CAUSE information element. The cause code is used to describe the reason for generating certain signalling messages.

This attribute contains the diagnostic code in the last transmitted signalling message. The diagnostic code is contained in the CAUSE information element and identifies an information element type or timer type. The diagnostic code is present only if a procedural error is detected by the signalling protocol. A diagnostic code is always accompanied by the cause code. If there is no failure, this attribute is set to 0.

This attribute contains the cause code in the last received signalling message that contains the CAUSE information element. The cause code is used to describe the reason for generating certain signalling messages.

This attribute contains the diagnostic code in the last received signalling message. The diagnostic code is contained in the CAUSE information element and identifies an information element type or timer type. The diagnostic code is present only if a procedural error is detected by the signalling protocol. A diagnostic code is always accompanied by the cause code. If there is no failure, this attribute is set to 0.

This attribute group contains the statistics associated with the AtmSignalling component.

An entry in the mscAtmIfVptPnniSigStatsTable.

This attribute indicates the total number of currently active connections.

This attribute indicates the high water mark of active point-to- point and point-to-multipoint connections.

This attribute counts the total number of switched point-to- point and point-to-multipoint connections that were successfully established. The counter wraps to 0 when the maximum value is exceeded.

This attribute counts the total number of switched connections that were not successfully established.The counter wraps to 0 when the maximum value is exceeded.

This attribute counts the number of transmitted signalling PDUs.The counter wraps to 0 when the maximum value is exceeded.

This attribute counts the number of received signalling PDUs.The counter wraps to 0 when the maximum value is exceeded.

This attribute indicates the number of currently active point-to- multipoint connections.

This attribute indicates the high water mark of active point-to- multipoint connections.

This attribute counts the total number of switched point-to- multipoint connections that were successfully established. The counter wraps to 0 when the maximum value is exceeded.

This attribute counts the number of switched point-to- multipoint connections that were not successfully established.The counter wraps to 0 when the maximum value is exceeded.

This attribute indicates the total number of currently active point-to- point and point-to-multipoint connections.

This entry controls the addition and deletion of mscAtmIfVptPnniRcc components.

A single entry in the table represents a single mscAtmIfVptPnniRcc component.

This variable is used as the basis for SNMP naming of mscAtmIfVptPnniRcc components. These components cannot be added nor deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the mscAtmIfVptPnniRcc tables.

This variable represents the index for the mscAtmIfVptPnniRcc tables.

This entry controls the addition and deletion of mscAtmIfVptPnniRccVcd components.

A single entry in the table represents a single mscAtmIfVptPnniRccVcd component.

This variable is used as the basis for SNMP naming of mscAtmIfVptPnniRccVcd components. These components can be added and deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the mscAtmIfVptPnniRccVcd tables.

This variable represents the index for the mscAtmIfVptPnniRccVcd tables.

This group contains the provisionable traffic attributes for a control channel.

An entry in the mscAtmIfVptPnniRccVcdProvTable.

This attribute specifies the type of traffic management which is applied to both the transmit and receive direction of this connection as defined in the ATM Forum. The trafficDescType determines the number and meaning of the parameters in the trafficDescParm attribute. Enumeration: 'n8': 8, 'n3': 3, 'n6': 6, 'n7': 7.

This attribute specifies the ATM service category for both directions of the connection. The constantBitRate service category is intended for real time applications, that is those requiring tightly constrained delay and delay variation, as would be appropriate for voice and video applications. The consistent availability of a fixed quantity of bandwidth is considered appropriate for CBR service. Cells which are delayed beyond the value specified by CellTransfer Delay are assumed to be of significantly reduce value to the application. The rtVariableBitRate service category is intended for real time applications, that is those requiring tightly constrained delay and delay variation, as would be appropriate for voice and video applications. Sources are expected to transmit at a rate which varies with time. Equivalently, the source can be described as 'bursty'. Cells which are delayed beyond the value specified by CTD are assumed to be of significantly reduced value to the application. Real time VBR service may support statistical multiplexing of real time sources. The nrtVariableBitRate service category is intended for non-real time applications which have bursty traffic characteristics and which can be characterized in terms of a PCR, SCR, and MBS. For those cells which are transferred within the traffic contract, the application expects a low cell loss ratio. For all connections, it expects a bound on the mean cell transfer delay. Non-real time VBR service may support statistical multiplexing of connections. The unspecifiedBitRate service is intended for non-real time applications; that is, those not requiring tightly constrained delay and delay variation. UBR sources are expected to be bursty. UBR service supports a high degree of statistical multiplexing among sources. UBR service does not specify traffic related service guarantees. No numerical commitments are made with respect to the cell loss ratio experienced by a UBR connection, or as to the cell transfer delay experienced by cells on the connection. Enumeration: 'constantBitRate': 1, 'unspecifiedBitRate': 0, 'rtVariableBitRate': 2, 'nrtVariableBitRate': 3.

This attribute specifies an override for the weight of this unshaped connection. This attribute is ignored for shaped connections, for ABR connections, for connections on a CQC-based ATM FP and basic VPTs. When the value is set to sameAsCa, the weight is determined by the weight policy attribute under the CA service category component for all but standard VPT VCCs. For standard VPT VCCs, the weight is determined by the VCC's service category, when the value is set to sameAsCa. When this attribute is set to a value from 1 to 4095, that value is used for the weight policy of this connection relative to other connections. For all but standard VPT VCCs, weight policy determines the proportion of transit cell opportunities which are allocated to this connection, compared to other connections in the same service category. For standard VPT VCCs, weight policy determines the proportion of transmit cell opportunities which are allocated to this connection, compared to other connections associated with the VPT. When the value is set to upToQueueLimit, the weight policy is limited only by the txQueueLimit. VALUES ( 0 = upToQueueLimit 65535 = sameAsCa )

This attribute specifies the quality of service for both the forward and backward direction for this connection. Class 1 supports a QOS that meets Service Class A performance requirements (Circuit emulation, constant bit rate video). Class 2 supports a QOS that meets Service Class B performance requirements (Variable bit rate audio and video). Class 3 supports a QOS that meets Service Class C performance requirements (Connection-Oriented Data Transfer). Class 4 supports a QOS that meets Service Class D performance requirements (Connectionless Data Transfer). Class 0 is the unspecified bit rate QOS class; no objective is specified for the performance parameters. Enumeration: 'n0': 0, 'n1': 1, 'n2': 2, 'n3': 3, 'n4': 4.

This attribute specifies whether this connection uses traffic shaping when transmitting traffic to the ATM interface. When sameAsCa is selected, traffic shaping for this connection is based on the trafficShaping attribute of the connection's service category component under the AtmIf CA. If the service category has traffic shaping enabled, then traffic shaping is enabled for the connection. Note that enabling traffic shaping may have no effect under certain cases. These cases are listed in the description of the trafficShaping operational attribute, which is under the Vcc Tm and Vpc Tm components. When disabled is selected, traffic shaping for this connection is disabled. Enumeration: 'disabled': 1, 'sameAsCa': 2.

This attribute only applies when this connection is unshaped. This attribute specifies the transmit queueing method for this connection if it is unshaped. Refer to the unshapedTransmitQueueing attribute under the AtmIf CA service category subcomponent for more details on the meaning of this attribute. When this attribute is set to sameAsCa, the transmit queueing method for the connection is based on the unshapedTransmitQueueing attribute of the connection's service category component under the ConnectionAdministrator. When this attribute is set to common, transmit traffic on this unshaped connection is destined for the common queue. The value sameAsInterface is for migration from previous software releases, but should no longer be used Enumeration: 'sameAsCa': 3, 'common': 1.

This attribute specifies whether this connection enforces usage parameter control when receiving traffic from the ATM interface. When sameAsCa is selected, UPC for the connection is based on the usageParameterControl attribute of the connection's service category component under the ConnectionAdministrator. If the service category has UPC enabled, then UPC is enabled for the connection. Note that enabling UPC may have no effect under certain cases. These cases are listed in the description of the usageParameterControl operational attribute, which is under the Vcc Tm or Vpc Tm component. When disabled is selected, UPC for this connection is disabled. The value sameAsInterface is for migration from previous software releases, but should no longer be used Enumeration: 'disabled': 1, 'sameAsCa': 2.

This attribute is a vector of five traffic parameters whose meanings are defined by the trafficDescType attribute. The values of peak cell rate (PCR), sustained cell rate (SCR) and requested shaping rate are expressed in cell/s. Maximum burst size (MBS) is expressed in cells. CDVT is expressed in microseconds. The values of PCR, SCR, MBS and CDVT are used for connection admission control (CAC). The value of CDVT is only used for connections where the atmServiceCategory is constantBitRate. For all other values of atmServiceCategory, CDVT is ignored. The values of PCR, SCR and requested shaping rate are used to determine the actual shaping rate where traffic shaping is enabled. When trafficDescType is 3, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 4 represents the CDVT; and parameter 5 represents the requested shaping rate. A non-zero value in parameter 5 overrides any value in parameter 1. This result is used as the PCR. Parameter 1 must be non-zero. Parameters 2 and 3 must be zero. When trafficDescType is 6, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 2 represents the SCR for CLP equal to 0 and 1 traffic; parameter 3 represents the MBS for CLP equal to 0 and 1 traffic; parameter 4 represents the CDVT; and parameter 5 represents the requested shaping rate. A non-zero value in parameter 5 overrides any value in parameter 1. This result is used as the PCR. Parameters 1, 2, and 3 must be non-zero. Parameter 1 must be greater than or equal to parameter 2. Parameter 5 must either be zero (unused) or greater than or equal to parameter 2. When trafficDescType is 7, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 2 represents the SCR for CLP equal to 0 with cell discard; parameter 3 represents the MBS for CLP equal to 0 traffic; parameter 4 represents the CDVT; and parameter 5 represents the requested shaping rate. A non-zero value in parameter 5 overrides any value in parameter 1. This result is used as the PCR. Parameters 1, 2, and 3 must be non-zero. Parameter 1 must be greater than or equal to parameter 2. Parameter 5 must either be zero (unused) or greater than or equal to parameter 2. When trafficDescType is 8, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 2 represents the SCR for CLP equal to 0 traffic with cell tagging; parameter 3 represents the MBS for CLP equal to 0 traffic; parameter 4 represents the CDVT; and parameter 5 represents the requested shaping rate. A non-zero value in parameter 5 overrides any value in parameter 1. This result is used as the PCR. Parameters 1, 2, and 3 must be non-zero. Parameter 1 must be greater than or equal to parameter 2. Parameter 5 must either be zero (unused) or greater than or equal to parameter 2. Whenever it is valid for PCR to be specified, parameter 5 may also be used to specify a requested shaping rate. A non-zero value in parameter 5 overrides the value in parameter 1 and is used as the peak cell rate in calculations of CAC and shaping rate. For trafficDescType 3 the traffic is shaped at the next rate less than the PCR. For trafficDescType 6, 7, and 8, the traffic is shaped at the highest available rate which is between PCR and SCR. However, if there is no available shaping rate between PCR and SCR, traffic is shaped at the next rate above the PCR.

An entry in the mscAtmIfVptPnniRccVcdTdpTable.

This variable represents the mscAtmIfVptPnniRccVcdTdpTable specific index for the mscAtmIfVptPnniRccVcdTdpTable.

This variable represents an individual value for the mscAtmIfVptPnniRccVcdTdpTable.

This group contains the generic provisionable attributes of an Rcc component.

An entry in the mscAtmIfVptPnniRccProvTable.

This attribute specifies the VCI for the Routing Control Channel (RCC). It is not recommended that the value be changed from the default of 18 unless absolutely necessary. If a different VCI is specified, ensure that the RCC at the far end is provisioned to use the same VCI, otherwise the RCC will not come up.

This group contains the provisionable Hello protocol parameters for an Rcc component.

An entry in the mscAtmIfVptPnniRccHlParmsTable.

This attribute is used to limit the rate at which this node sends out Hello packets. Specifically, it specifies the minimum time between successive Hellos. A value of 0 specifies that the value provisioned for the helloHoldDown attribute of the ARtg Pnni component should be used.

This attribute specifies the duration of the Hello Timer. Every helloInterval seconds, this node will send out a Hello packet to the neighbor node, subject to the helloHoldDown timer having expired at least once since the last Hello packet was sent. A value of 0 specifies that the value provisioned for the helloInterval attribute of the ARtg Pnni component should be used.

This attribute specifies the number of Hello intervals allowed to pass without receiving a Hello from the neighbor node, before an attempt is made to re-stage. The hello inactivity timer is enabled in the oneWayInside, twoWayInside, oneWayOutside, twoWayOutside and commonOutside hello states (see the helloState attribute on the Rcc component for a description of these states). Note that the value for the Hello interval used in the calculation is the one specified in the Hello packet from the neighbor node. A value of 0 specifies that the value provisioned for the helloInactivityFactor attribute of the ARtg Pnni component should be used. DESCRIPTION

This group contains the three OSI State attributes. The descriptions generically indicate what each state attribute implies about the component. Note that not all the values and state combinations described here are supported by every component which uses this group. For component-specific information and the valid state combinations, refer to NTP 241-7001-150, Passport Operations and Maintenance Guide.

An entry in the mscAtmIfVptPnniRccStateTable.

This attribute indicates the OSI Administrative State of the component. The value locked indicates that the component is administratively prohibited from providing services for its users. A Lock or Lock - force command has been previously issued for this component. When the value is locked, the value of usageState must be idle. The value shuttingDown indicates that the component is administratively permitted to provide service to its existing users only. A Lock command was issued against the component and it is in the process of shutting down. The value unlocked indicates that the component is administratively permitted to provide services for its users. To enter this state, issue an Unlock command to this component. Enumeration: 'locked': 0, 'shuttingDown': 2, 'unlocked': 1.

This attribute indicates the OSI Operational State of the component. The value enabled indicates that the component is available for operation. Note that if adminState is locked, it would still not be providing service. The value disabled indicates that the component is not available for operation. For example, something is wrong with the component itself, or with another component on which this one depends. If the value is disabled, the usageState must be idle. Enumeration: 'disabled': 0, 'enabled': 1.

This attribute indicates the OSI Usage State of the component. The value idle indicates that the component is not currently in use. The value active indicates that the component is in use and has spare capacity to provide for additional users. The value busy indicates that the component is in use and has no spare operating capacity for additional users at this time. Enumeration: 'active': 1, 'idle': 0, 'busy': 2.

This group contains the operational attributes for an Rcc component.

An entry in the mscAtmIfVptPnniRccOperTable.

This attribute indicates the role of this link in the PNNI hierarchy. The following values are possible: unknown: the Hello protocol has not yet determined the role of the link. lowestLevelHorizLink: the link is a horizontal link between two lowest level nodes. lowestLevelOutsideLink: the link is an outside link between two border nodes. horizontalLinkToLgn: the link is a horizontal link to a Logical Group Node (LGN). uplink: the link is a uplink to a higher level LGN. Enumeration: 'unknown': 0, 'lowestLevelHorizLink': 1, 'horizontalLinkToLGN': 3, 'uplink': 4, 'lowestLevelOutsideLink': 2.

This attribute indicates the PNNI version negotiated with the neighbor node. Enumeration: 'version1point0': 1, 'unsupported': 0.

This attribute indicates the state of the Hello protocol exchange over this link. The following are the possible values for this attribute: down: the link is down; no PNNI routing packets will be sent over or received over such a link. This is the initial state of the Hello Finite State Machine, and can also be reached when lower-level protocols have indicated that the link is not usable. attempt: no Hello packets or Hello packets, with mismatch information, have been received recently from the neighbor. Attempts are made to contact the neighbor node by sending out Hello packets every helloInterval seconds. oneWayInside: Hello packets have been recently received from the neighbor and it has been established that both nodes are members of the same peer group, but the remote node ID and remote port ID in the neighbor's Hello packets were set to zero. A Hello packet is sent to the neighbor and the Hello timer is restarted. twoWayInside: Bidirectional communication over this link between this node and the neighbor node has been achieved. oneWayOutside: Hello packets have been recently received from the neighbor and it has been established that both nodes are members of a different peer group, but the remote node ID and remote port ID in the neighbor's Hello packets were set to zero. twoWayOutside: Hellos have recently been received from the neighbor indicating that the neighbor node belongs to a different peer group. The correct remote node ID and remote port ID fields were included in the Hello packet, but the nodal hierarchy list did not include any common peer group. This state can also be reached if a hierarchy mismatch occurs while in the commonOutside state. commonOutside: A common level of the routing hierarchy has been found, in addition to achieving full bi-directional communication between the two nodes. Enumeration: 'attempt': 2, 'oneWayOutside': 5, 'twoWayInside': 4, 'down': 1, 'notApplicable': 0, 'oneWayInside': 3, 'twoWayOutside': 6, 'commonOutside': 7.

This attribute indicates the neighbor node's node id.

This attribute indicates the neighbor node's port id.

This group contains the statistical attributes for an Rcc component.

An entry in the mscAtmIfVptPnniRccStatsTable.

This attribute counts the total number of Hello packets received across this RCC, including bad and mismatched Hello packets. The counter wraps when it exceeds the maximum value.

This attribute counts the total number of Hello packets transmitted across this RCC. The counter wraps when it exceeds the maximum value.

This attribute counts the total number of mismatched Hello packets received over this RCC. The counter wraps when it exceeds the maximum value.

This attribute counts the total number of bad Hello packets received over this RCC. The counter wraps when it exceeds the maximum value.

This entry controls the addition and deletion of mscAtmIfVptPnniAddr components.

A single entry in the table represents a single mscAtmIfVptPnniAddr component.

This variable is used as the basis for SNMP naming of mscAtmIfVptPnniAddr components. These components can be added and deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the mscAtmIfVptPnniAddr tables.

This variable represents an index for the mscAtmIfVptPnniAddr tables.

This variable represents an index for the mscAtmIfVptPnniAddr tables. Enumeration: 'default': 3, 'registered': 2, 'alternate': 1, 'primary': 0.

This entry controls the addition and deletion of mscAtmIfVptPnniAddrTermSP components.

A single entry in the table represents a single mscAtmIfVptPnniAddrTermSP component.

This variable is used as the basis for SNMP naming of mscAtmIfVptPnniAddrTermSP components. These components can be added and deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the mscAtmIfVptPnniAddrTermSP tables.

This variable represents the index for the mscAtmIfVptPnniAddrTermSP tables.

This entry controls the addition and deletion of mscAtmIfVptPnniAddrPnniInfo components.

A single entry in the table represents a single mscAtmIfVptPnniAddrPnniInfo component.

This variable is used as the basis for SNMP naming of mscAtmIfVptPnniAddrPnniInfo components. These components can be added and deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the mscAtmIfVptPnniAddrPnniInfo tables.

This variable represents the index for the mscAtmIfVptPnniAddrPnniInfo tables.

This attribute group contains the provisioned attributes relating to PNNI for a PnniInfo component.

An entry in the mscAtmIfVptPnniAddrPnniInfoProvTable.

This attribute specifies the scope of the ATM address, which is the highest level up to which this address will be advertised in the PNNI hierarchy. The scope must be set to a value numerically less than or equal to the level of the lowest level peer group containing this node. Setting the scope to 0 will cause the address to be advertised globally within this PNNI routing domain.

This attribute indicates whether the address is internal or exterior. An internal reachable address is an address of a destination that is directly attached to the logical node advertising the address. An exterior reachable address is an address that can be reached through a PNNI routing domain, but which is not located in that PNNI routing domain. Enumeration: 'internal': 0, 'exterior': 1.

This attribute group contains the operational attributes for the Address component.

An entry in the mscAtmIfVptPnniAddrOperTable.

This attribute indicates the scope of the ATM address, which is the highest level to which this address will be advertised in the PNNI hierarchy. If no PnniInfo subcomponent has been provisioned, then the scope will default to the level of this node in the PNNI hierarchy. If this node does not participate in a PNNI hierarchy, then this attribute will have the value of -1.

This attribute indicates whether the address is internal or exterior. An internal reachable address is an address of a destination that is directly attached to the logical node advertising the address. An exterior reachable address is an address that can be reached through a PNNI routing domain, but which is not located in that PNNI routing domain. Enumeration: 'internal': 0, 'exterior': 1.

This group contains the provisionable attributes for the Pnni component.

An entry in the mscAtmIfVptPnniProvTable.

This attribute represents the time in seconds to wait between call setup retries. The resolution is to the nearest 10 seconds. This attribute has been obsoleted and is replaced by the softPvpAndPvcRetryPeriod attribute.

This attribute represents the time in seconds to wait between soft PVP or soft PVC call setup retries. The resolution is to the nearest 10 seconds.

This attribute specifies how long to hold off retries following a release or the connection. The resolution is to the nearest 50 ms.

This group contains the provisionable administrative weights for the Pnni component. These weights will be used by Generic Connection Admission Control (GCAC) if administrative weight is the selected optimization criterion.

An entry in the mscAtmIfVptPnniAdminWeightsTable.

This attribute specifies the administrative weight assigned for setting up switched calls with a service category of Constant Bit Rate (CBR) for this PNNI interface. The value specified will be used by Generic Connection Admission Control (GCAC) if administrative weight is the selected optimization criterion; the higher the value, the less desirable the link will be in path selection.

This attribute specifies the administrative weight assigned for setting up switched calls with a service category of Real-Time Variable Bit Rate (RT-VBR) for this PNNI interface. The value specified will be used by Generic Connection Admission Control (GCAC) if administrative weight is the selected optimization criterion; the higher the value, the less desirable the link will be in path selection.

This attribute specifies the administrative weight assigned for setting up switched calls with a service category of Non Real-Time Variable Bit Rate (NRT-VBR) for this PNNI interface. The value specified will be used by Generic Connection Admission Control (GCAC) if administrative weight is the selected optimization criterion; the higher the value, the less desirable the link will be in path selection.

This attribute specifies the administrative weight assigned for setting up switched calls with a service category of Unspecified Bit Rate (UBR) for this PNNI interface. The value specified will be used by Generic Connection Admission Control (GCAC) if administrative weight is the selected optimization criterion; the higher the value, the less desirable the link will be in path selection.

This group contains the provisionable attributes for accounting.

An entry in the mscAtmIfVptPnniAcctOptTable.

This attribute is used to turn accounting on or off for SVC and SPVC connections. It also specifies the reason(s) for which accounting data is collected: billing, test, study, audit, or force. If the set of reasons is not empty then accounting records will be generated by this interface in the following situations: - on a TODA changeover if TODA is enabled; - every 12 hours (per connection) if TODA is disabled; - on every call clear (a call record with final cell counts). If none of the reasons is present, then accounting will be suppressed. The reason for collection is recorded in the accounting record, in the attribute callingCollectReason or calledCollectReason as appropriate. Description of bits: bill(0) test(1) study(2) audit(3) force(4)

This attribute specifies whether accounting records generated by this interface should be marked as originating, terminating or intermediate. This attribute, in combination with the direction of the call, determines the value of attribute connPointType of the accounting record and may be used by downstream accounting processes to correlate the records. If the value is origTerm then records generated for incoming calls will be marked as originating and records generated for outgoing calls will be marked as terminating. If the value is intermediate then records generated for all calls will be marked as intermediate. Enumeration: 'origTerm': 0, 'intermediate': 1.

This attribute specifies the accounting class associated with the interface. Its meaning is determined by the network operator. Its value is simply recorded in the accounting records generated by this interface, in the attribute callingServiceType or calledServiceType as appropriate.

This attribute specifies the data service exchange associated with this interface. Its meaning is determined by the network operator. Its value is simply recorded in the accounting records generated by this interface, in the attribute callingDse or calledDse as appropriate.

This group contains the operational attributes for a Pnni component.

An entry in the mscAtmIfVptPnniOperationalTable.

This attribute indicates the port id of the PNNI interface, which is the parent AtmIf's instance number.

This group contains the provisionable attributes for the Pnni component which are specific to virtual PNNI interfaces.

An entry in the mscAtmIfVptPnniVProvTable.

This attribute specifies the Virtual Path Connection Identifier (VPCI) to be used between this signalling entity and its peer. The VPCI of the peer virtual PNNI must have the same value for switched connections to be set up across the interface.

This entry controls the addition and deletion of mscAtmIfPnni components.

A single entry in the table represents a single mscAtmIfPnni component.

This variable is used as the basis for SNMP naming of mscAtmIfPnni components. These components can be added and deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the mscAtmIfPnni tables.

This variable represents the index for the mscAtmIfPnni tables.

This entry controls the addition and deletion of mscAtmIfPnniSig components.

A single entry in the table represents a single mscAtmIfPnniSig component.

This variable is used as the basis for SNMP naming of mscAtmIfPnniSig components. These components cannot be added nor deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the mscAtmIfPnniSig tables.

This variable represents the index for the mscAtmIfPnniSig tables.

This entry controls the addition and deletion of mscAtmIfPnniSigVcd components.

A single entry in the table represents a single mscAtmIfPnniSigVcd component.

This variable is used as the basis for SNMP naming of mscAtmIfPnniSigVcd components. These components can be added and deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the mscAtmIfPnniSigVcd tables.

This variable represents the index for the mscAtmIfPnniSigVcd tables.

This group contains the provisionable traffic attributes for a control channel.

An entry in the mscAtmIfPnniSigVcdProvTable.

This attribute specifies the type of traffic management which is applied to both the transmit and receive direction of this connection as defined in the ATM Forum. The trafficDescType determines the number and meaning of the parameters in the trafficDescParm attribute. Enumeration: 'n8': 8, 'n3': 3, 'n6': 6, 'n7': 7.

This attribute specifies the ATM service category for both directions of the connection. The constantBitRate service category is intended for real time applications, that is those requiring tightly constrained delay and delay variation, as would be appropriate for voice and video applications. The consistent availability of a fixed quantity of bandwidth is considered appropriate for CBR service. Cells which are delayed beyond the value specified by CellTransfer Delay are assumed to be of significantly reduce value to the application. The rtVariableBitRate service category is intended for real time applications, that is those requiring tightly constrained delay and delay variation, as would be appropriate for voice and video applications. Sources are expected to transmit at a rate which varies with time. Equivalently, the source can be described as 'bursty'. Cells which are delayed beyond the value specified by CTD are assumed to be of significantly reduced value to the application. Real time VBR service may support statistical multiplexing of real time sources. The nrtVariableBitRate service category is intended for non-real time applications which have bursty traffic characteristics and which can be characterized in terms of a PCR, SCR, and MBS. For those cells which are transferred within the traffic contract, the application expects a low cell loss ratio. For all connections, it expects a bound on the mean cell transfer delay. Non-real time VBR service may support statistical multiplexing of connections. The unspecifiedBitRate service is intended for non-real time applications; that is, those not requiring tightly constrained delay and delay variation. UBR sources are expected to be bursty. UBR service supports a high degree of statistical multiplexing among sources. UBR service does not specify traffic related service guarantees. No numerical commitments are made with respect to the cell loss ratio experienced by a UBR connection, or as to the cell transfer delay experienced by cells on the connection. Enumeration: 'constantBitRate': 1, 'unspecifiedBitRate': 0, 'rtVariableBitRate': 2, 'nrtVariableBitRate': 3.

This attribute specifies an override for the weight of this unshaped connection. This attribute is ignored for shaped connections, for ABR connections, for connections on a CQC-based ATM FP and basic VPTs. When the value is set to sameAsCa, the weight is determined by the weight policy attribute under the CA service category component for all but standard VPT VCCs. For standard VPT VCCs, the weight is determined by the VCC's service category, when the value is set to sameAsCa. When this attribute is set to a value from 1 to 4095, that value is used for the weight policy of this connection relative to other connections. For all but standard VPT VCCs, weight policy determines the proportion of transit cell opportunities which are allocated to this connection, compared to other connections in the same service category. For standard VPT VCCs, weight policy determines the proportion of transmit cell opportunities which are allocated to this connection, compared to other connections associated with the VPT. When the value is set to upToQueueLimit, the weight policy is limited only by the txQueueLimit. VALUES ( 0 = upToQueueLimit 65535 = sameAsCa )

This attribute specifies the quality of service for both the forward and backward direction for this connection. Class 1 supports a QOS that meets Service Class A performance requirements (Circuit emulation, constant bit rate video). Class 2 supports a QOS that meets Service Class B performance requirements (Variable bit rate audio and video). Class 3 supports a QOS that meets Service Class C performance requirements (Connection-Oriented Data Transfer). Class 4 supports a QOS that meets Service Class D performance requirements (Connectionless Data Transfer). Class 0 is the unspecified bit rate QOS class; no objective is specified for the performance parameters. Enumeration: 'n0': 0, 'n1': 1, 'n2': 2, 'n3': 3, 'n4': 4.

This attribute specifies whether this connection uses traffic shaping when transmitting traffic to the ATM interface. When sameAsCa is selected, traffic shaping for this connection is based on the trafficShaping attribute of the connection's service category component under the AtmIf CA. If the service category has traffic shaping enabled, then traffic shaping is enabled for the connection. Note that enabling traffic shaping may have no effect under certain cases. These cases are listed in the description of the trafficShaping operational attribute, which is under the Vcc Tm and Vpc Tm components. When disabled is selected, traffic shaping for this connection is disabled. Enumeration: 'disabled': 1, 'sameAsCa': 2.

This attribute only applies when this connection is unshaped. This attribute specifies the transmit queueing method for this connection if it is unshaped. Refer to the unshapedTransmitQueueing attribute under the AtmIf CA service category subcomponent for more details on the meaning of this attribute. When this attribute is set to sameAsCa, the transmit queueing method for the connection is based on the unshapedTransmitQueueing attribute of the connection's service category component under the ConnectionAdministrator. When this attribute is set to common, transmit traffic on this unshaped connection is destined for the common queue. The value sameAsInterface is for migration from previous software releases, but should no longer be used Enumeration: 'sameAsCa': 3, 'common': 1.

This attribute specifies whether this connection enforces usage parameter control when receiving traffic from the ATM interface. When sameAsCa is selected, UPC for the connection is based on the usageParameterControl attribute of the connection's service category component under the ConnectionAdministrator. If the service category has UPC enabled, then UPC is enabled for the connection. Note that enabling UPC may have no effect under certain cases. These cases are listed in the description of the usageParameterControl operational attribute, which is under the Vcc Tm or Vpc Tm component. When disabled is selected, UPC for this connection is disabled. The value sameAsInterface is for migration from previous software releases, but should no longer be used Enumeration: 'disabled': 1, 'sameAsCa': 2.

This attribute is a vector of five traffic parameters whose meanings are defined by the trafficDescType attribute. The values of peak cell rate (PCR), sustained cell rate (SCR) and requested shaping rate are expressed in cell/s. Maximum burst size (MBS) is expressed in cells. CDVT is expressed in microseconds. The values of PCR, SCR, MBS and CDVT are used for connection admission control (CAC). The value of CDVT is only used for connections where the atmServiceCategory is constantBitRate. For all other values of atmServiceCategory, CDVT is ignored. The values of PCR, SCR and requested shaping rate are used to determine the actual shaping rate where traffic shaping is enabled. When trafficDescType is 3, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 4 represents the CDVT; and parameter 5 represents the requested shaping rate. A non-zero value in parameter 5 overrides any value in parameter 1. This result is used as the PCR. Parameter 1 must be non-zero. Parameters 2 and 3 must be zero. When trafficDescType is 6, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 2 represents the SCR for CLP equal to 0 and 1 traffic; parameter 3 represents the MBS for CLP equal to 0 and 1 traffic; parameter 4 represents the CDVT; and parameter 5 represents the requested shaping rate. A non-zero value in parameter 5 overrides any value in parameter 1. This result is used as the PCR. Parameters 1, 2, and 3 must be non-zero. Parameter 1 must be greater than or equal to parameter 2. Parameter 5 must either be zero (unused) or greater than or equal to parameter 2. When trafficDescType is 7, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 2 represents the SCR for CLP equal to 0 with cell discard; parameter 3 represents the MBS for CLP equal to 0 traffic; parameter 4 represents the CDVT; and parameter 5 represents the requested shaping rate. A non-zero value in parameter 5 overrides any value in parameter 1. This result is used as the PCR. Parameters 1, 2, and 3 must be non-zero. Parameter 1 must be greater than or equal to parameter 2. Parameter 5 must either be zero (unused) or greater than or equal to parameter 2. When trafficDescType is 8, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 2 represents the SCR for CLP equal to 0 traffic with cell tagging; parameter 3 represents the MBS for CLP equal to 0 traffic; parameter 4 represents the CDVT; and parameter 5 represents the requested shaping rate. A non-zero value in parameter 5 overrides any value in parameter 1. This result is used as the PCR. Parameters 1, 2, and 3 must be non-zero. Parameter 1 must be greater than or equal to parameter 2. Parameter 5 must either be zero (unused) or greater than or equal to parameter 2. Whenever it is valid for PCR to be specified, parameter 5 may also be used to specify a requested shaping rate. A non-zero value in parameter 5 overrides the value in parameter 1 and is used as the peak cell rate in calculations of CAC and shaping rate. For trafficDescType 3 the traffic is shaped at the next rate less than the PCR. For trafficDescType 6, 7, and 8, the traffic is shaped at the highest available rate which is between PCR and SCR. However, if there is no available shaping rate between PCR and SCR, traffic is shaped at the next rate above the PCR.

An entry in the mscAtmIfPnniSigVcdTdpTable.

This variable represents the mscAtmIfPnniSigVcdTdpTable specific index for the mscAtmIfPnniSigVcdTdpTable.

This variable represents an individual value for the mscAtmIfPnniSigVcdTdpTable.

This attribute group contains the provisionable attributes for the Signalling component.

An entry in the mscAtmIfPnniSigProvTable.

This attribute specifies the signalling channel number.

This attribute specifies the address conversion on the outgoing signalling PDUs. The options are none, nativeE164, or nsap. The none option is the default and if this option is chosen then nothing is done to the address information element (IE) in the outgoing signalling message. If nativeE164 option is chosen, then only NSAP encapsulated E.164 addresses with zeros in the ESI are converted to native E.164 format in the outgoing signalling message. If the NSAP address is not encapsulated E.164 or the ESI field is not zeros and the nativeE164 option is chosen, then the call is cleared. If the nsap option is chosen, then native E.164 addresses are converted to NSAP E.164 with zeros in the ESI field; otherwise the address is in NSAP format and is not changed. Enumeration: 'none': 0, 'nativeE164': 1, 'nsap': 2.

This attribute specifies the operating mode of the signaling channel. provisionedOnly indicates that only SPVCs and SPVPs are supported on the interface and SVCs are not supported. This value is permitted only on UNI interfaces. normal indicates that SVCs, SPVCs, and SPVPs are supported on the interface. Enumeration: 'provisionedOnly': 1, 'normal': 0.

This group contains the three OSI State attributes. The descriptions generically indicate what each state attribute implies about the component. Note that not all the values and state combinations described here are supported by every component which uses this group. For component-specific information and the valid state combinations, refer to NTP 241-7001-150, Passport Operations and Maintenance Guide.

An entry in the mscAtmIfPnniSigStateTable.

This attribute indicates the OSI Administrative State of the component. The value locked indicates that the component is administratively prohibited from providing services for its users. A Lock or Lock - force command has been previously issued for this component. When the value is locked, the value of usageState must be idle. The value shuttingDown indicates that the component is administratively permitted to provide service to its existing users only. A Lock command was issued against the component and it is in the process of shutting down. The value unlocked indicates that the component is administratively permitted to provide services for its users. To enter this state, issue an Unlock command to this component. Enumeration: 'locked': 0, 'shuttingDown': 2, 'unlocked': 1.

This attribute indicates the OSI Operational State of the component. The value enabled indicates that the component is available for operation. Note that if adminState is locked, it would still not be providing service. The value disabled indicates that the component is not available for operation. For example, something is wrong with the component itself, or with another component on which this one depends. If the value is disabled, the usageState must be idle. Enumeration: 'disabled': 0, 'enabled': 1.

This attribute indicates the OSI Usage State of the component. The value idle indicates that the component is not currently in use. The value active indicates that the component is in use and has spare capacity to provide for additional users. The value busy indicates that the component is in use and has no spare operating capacity for additional users at this time. Enumeration: 'active': 1, 'idle': 0, 'busy': 2.

This attribute contains the operational attributes for the AtmSignalling component.

An entry in the mscAtmIfPnniSigOperTable.

This attribute indicates the cause code in the last transmitted signalling message that contains the CAUSE information element. The cause code is used to describe the reason for generating certain signalling messages.

This attribute contains the diagnostic code in the last transmitted signalling message. The diagnostic code is contained in the CAUSE information element and identifies an information element type or timer type. The diagnostic code is present only if a procedural error is detected by the signalling protocol. A diagnostic code is always accompanied by the cause code. If there is no failure, this attribute is set to 0.

This attribute contains the cause code in the last received signalling message that contains the CAUSE information element. The cause code is used to describe the reason for generating certain signalling messages.

This attribute contains the diagnostic code in the last received signalling message. The diagnostic code is contained in the CAUSE information element and identifies an information element type or timer type. The diagnostic code is present only if a procedural error is detected by the signalling protocol. A diagnostic code is always accompanied by the cause code. If there is no failure, this attribute is set to 0.

This attribute group contains the statistics associated with the AtmSignalling component.

An entry in the mscAtmIfPnniSigStatsTable.

This attribute indicates the total number of currently active connections.

This attribute indicates the high water mark of active point-to- point and point-to-multipoint connections.

This attribute counts the total number of switched point-to- point and point-to-multipoint connections that were successfully established. The counter wraps to 0 when the maximum value is exceeded.

This attribute counts the total number of switched connections that were not successfully established.The counter wraps to 0 when the maximum value is exceeded.

This attribute counts the number of transmitted signalling PDUs.The counter wraps to 0 when the maximum value is exceeded.

This attribute counts the number of received signalling PDUs.The counter wraps to 0 when the maximum value is exceeded.

This attribute indicates the number of currently active point-to- multipoint connections.

This attribute indicates the high water mark of active point-to- multipoint connections.

This attribute counts the total number of switched point-to- multipoint connections that were successfully established. The counter wraps to 0 when the maximum value is exceeded.

This attribute counts the number of switched point-to- multipoint connections that were not successfully established.The counter wraps to 0 when the maximum value is exceeded.

This attribute indicates the total number of currently active point-to- point and point-to-multipoint connections.

This entry controls the addition and deletion of mscAtmIfPnniRcc components.

A single entry in the table represents a single mscAtmIfPnniRcc component.

This variable is used as the basis for SNMP naming of mscAtmIfPnniRcc components. These components cannot be added nor deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the mscAtmIfPnniRcc tables.

This variable represents the index for the mscAtmIfPnniRcc tables.

This entry controls the addition and deletion of mscAtmIfPnniRccVcd components.

A single entry in the table represents a single mscAtmIfPnniRccVcd component.

This variable is used as the basis for SNMP naming of mscAtmIfPnniRccVcd components. These components can be added and deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the mscAtmIfPnniRccVcd tables.

This variable represents the index for the mscAtmIfPnniRccVcd tables.

This group contains the provisionable traffic attributes for a control channel.

An entry in the mscAtmIfPnniRccVcdProvTable.

This attribute specifies the type of traffic management which is applied to both the transmit and receive direction of this connection as defined in the ATM Forum. The trafficDescType determines the number and meaning of the parameters in the trafficDescParm attribute. Enumeration: 'n8': 8, 'n3': 3, 'n6': 6, 'n7': 7.

This attribute specifies the ATM service category for both directions of the connection. The constantBitRate service category is intended for real time applications, that is those requiring tightly constrained delay and delay variation, as would be appropriate for voice and video applications. The consistent availability of a fixed quantity of bandwidth is considered appropriate for CBR service. Cells which are delayed beyond the value specified by CellTransfer Delay are assumed to be of significantly reduce value to the application. The rtVariableBitRate service category is intended for real time applications, that is those requiring tightly constrained delay and delay variation, as would be appropriate for voice and video applications. Sources are expected to transmit at a rate which varies with time. Equivalently, the source can be described as 'bursty'. Cells which are delayed beyond the value specified by CTD are assumed to be of significantly reduced value to the application. Real time VBR service may support statistical multiplexing of real time sources. The nrtVariableBitRate service category is intended for non-real time applications which have bursty traffic characteristics and which can be characterized in terms of a PCR, SCR, and MBS. For those cells which are transferred within the traffic contract, the application expects a low cell loss ratio. For all connections, it expects a bound on the mean cell transfer delay. Non-real time VBR service may support statistical multiplexing of connections. The unspecifiedBitRate service is intended for non-real time applications; that is, those not requiring tightly constrained delay and delay variation. UBR sources are expected to be bursty. UBR service supports a high degree of statistical multiplexing among sources. UBR service does not specify traffic related service guarantees. No numerical commitments are made with respect to the cell loss ratio experienced by a UBR connection, or as to the cell transfer delay experienced by cells on the connection. Enumeration: 'constantBitRate': 1, 'unspecifiedBitRate': 0, 'rtVariableBitRate': 2, 'nrtVariableBitRate': 3.

This attribute specifies an override for the weight of this unshaped connection. This attribute is ignored for shaped connections, for ABR connections, for connections on a CQC-based ATM FP and basic VPTs. When the value is set to sameAsCa, the weight is determined by the weight policy attribute under the CA service category component for all but standard VPT VCCs. For standard VPT VCCs, the weight is determined by the VCC's service category, when the value is set to sameAsCa. When this attribute is set to a value from 1 to 4095, that value is used for the weight policy of this connection relative to other connections. For all but standard VPT VCCs, weight policy determines the proportion of transit cell opportunities which are allocated to this connection, compared to other connections in the same service category. For standard VPT VCCs, weight policy determines the proportion of transmit cell opportunities which are allocated to this connection, compared to other connections associated with the VPT. When the value is set to upToQueueLimit, the weight policy is limited only by the txQueueLimit. VALUES ( 0 = upToQueueLimit 65535 = sameAsCa )

This attribute specifies the quality of service for both the forward and backward direction for this connection. Class 1 supports a QOS that meets Service Class A performance requirements (Circuit emulation, constant bit rate video). Class 2 supports a QOS that meets Service Class B performance requirements (Variable bit rate audio and video). Class 3 supports a QOS that meets Service Class C performance requirements (Connection-Oriented Data Transfer). Class 4 supports a QOS that meets Service Class D performance requirements (Connectionless Data Transfer). Class 0 is the unspecified bit rate QOS class; no objective is specified for the performance parameters. Enumeration: 'n0': 0, 'n1': 1, 'n2': 2, 'n3': 3, 'n4': 4.

This attribute specifies whether this connection uses traffic shaping when transmitting traffic to the ATM interface. When sameAsCa is selected, traffic shaping for this connection is based on the trafficShaping attribute of the connection's service category component under the AtmIf CA. If the service category has traffic shaping enabled, then traffic shaping is enabled for the connection. Note that enabling traffic shaping may have no effect under certain cases. These cases are listed in the description of the trafficShaping operational attribute, which is under the Vcc Tm and Vpc Tm components. When disabled is selected, traffic shaping for this connection is disabled. Enumeration: 'disabled': 1, 'sameAsCa': 2.

This attribute only applies when this connection is unshaped. This attribute specifies the transmit queueing method for this connection if it is unshaped. Refer to the unshapedTransmitQueueing attribute under the AtmIf CA service category subcomponent for more details on the meaning of this attribute. When this attribute is set to sameAsCa, the transmit queueing method for the connection is based on the unshapedTransmitQueueing attribute of the connection's service category component under the ConnectionAdministrator. When this attribute is set to common, transmit traffic on this unshaped connection is destined for the common queue. The value sameAsInterface is for migration from previous software releases, but should no longer be used Enumeration: 'sameAsCa': 3, 'common': 1.

This attribute specifies whether this connection enforces usage parameter control when receiving traffic from the ATM interface. When sameAsCa is selected, UPC for the connection is based on the usageParameterControl attribute of the connection's service category component under the ConnectionAdministrator. If the service category has UPC enabled, then UPC is enabled for the connection. Note that enabling UPC may have no effect under certain cases. These cases are listed in the description of the usageParameterControl operational attribute, which is under the Vcc Tm or Vpc Tm component. When disabled is selected, UPC for this connection is disabled. The value sameAsInterface is for migration from previous software releases, but should no longer be used Enumeration: 'disabled': 1, 'sameAsCa': 2.

This attribute is a vector of five traffic parameters whose meanings are defined by the trafficDescType attribute. The values of peak cell rate (PCR), sustained cell rate (SCR) and requested shaping rate are expressed in cell/s. Maximum burst size (MBS) is expressed in cells. CDVT is expressed in microseconds. The values of PCR, SCR, MBS and CDVT are used for connection admission control (CAC). The value of CDVT is only used for connections where the atmServiceCategory is constantBitRate. For all other values of atmServiceCategory, CDVT is ignored. The values of PCR, SCR and requested shaping rate are used to determine the actual shaping rate where traffic shaping is enabled. When trafficDescType is 3, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 4 represents the CDVT; and parameter 5 represents the requested shaping rate. A non-zero value in parameter 5 overrides any value in parameter 1. This result is used as the PCR. Parameter 1 must be non-zero. Parameters 2 and 3 must be zero. When trafficDescType is 6, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 2 represents the SCR for CLP equal to 0 and 1 traffic; parameter 3 represents the MBS for CLP equal to 0 and 1 traffic; parameter 4 represents the CDVT; and parameter 5 represents the requested shaping rate. A non-zero value in parameter 5 overrides any value in parameter 1. This result is used as the PCR. Parameters 1, 2, and 3 must be non-zero. Parameter 1 must be greater than or equal to parameter 2. Parameter 5 must either be zero (unused) or greater than or equal to parameter 2. When trafficDescType is 7, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 2 represents the SCR for CLP equal to 0 with cell discard; parameter 3 represents the MBS for CLP equal to 0 traffic; parameter 4 represents the CDVT; and parameter 5 represents the requested shaping rate. A non-zero value in parameter 5 overrides any value in parameter 1. This result is used as the PCR. Parameters 1, 2, and 3 must be non-zero. Parameter 1 must be greater than or equal to parameter 2. Parameter 5 must either be zero (unused) or greater than or equal to parameter 2. When trafficDescType is 8, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 2 represents the SCR for CLP equal to 0 traffic with cell tagging; parameter 3 represents the MBS for CLP equal to 0 traffic; parameter 4 represents the CDVT; and parameter 5 represents the requested shaping rate. A non-zero value in parameter 5 overrides any value in parameter 1. This result is used as the PCR. Parameters 1, 2, and 3 must be non-zero. Parameter 1 must be greater than or equal to parameter 2. Parameter 5 must either be zero (unused) or greater than or equal to parameter 2. Whenever it is valid for PCR to be specified, parameter 5 may also be used to specify a requested shaping rate. A non-zero value in parameter 5 overrides the value in parameter 1 and is used as the peak cell rate in calculations of CAC and shaping rate. For trafficDescType 3 the traffic is shaped at the next rate less than the PCR. For trafficDescType 6, 7, and 8, the traffic is shaped at the highest available rate which is between PCR and SCR. However, if there is no available shaping rate between PCR and SCR, traffic is shaped at the next rate above the PCR.

An entry in the mscAtmIfPnniRccVcdTdpTable.

This variable represents the mscAtmIfPnniRccVcdTdpTable specific index for the mscAtmIfPnniRccVcdTdpTable.

This variable represents an individual value for the mscAtmIfPnniRccVcdTdpTable.

This group contains the generic provisionable attributes of an Rcc component.

An entry in the mscAtmIfPnniRccProvTable.

This attribute specifies the VCI for the Routing Control Channel (RCC). It is not recommended that the value be changed from the default of 18 unless absolutely necessary. If a different VCI is specified, ensure that the RCC at the far end is provisioned to use the same VCI, otherwise the RCC will not come up.

This group contains the provisionable Hello protocol parameters for an Rcc component.

An entry in the mscAtmIfPnniRccHlParmsTable.

This attribute is used to limit the rate at which this node sends out Hello packets. Specifically, it specifies the minimum time between successive Hellos. A value of 0 specifies that the value provisioned for the helloHoldDown attribute of the ARtg Pnni component should be used.

This attribute specifies the duration of the Hello Timer. Every helloInterval seconds, this node will send out a Hello packet to the neighbor node, subject to the helloHoldDown timer having expired at least once since the last Hello packet was sent. A value of 0 specifies that the value provisioned for the helloInterval attribute of the ARtg Pnni component should be used.

This attribute specifies the number of Hello intervals allowed to pass without receiving a Hello from the neighbor node, before an attempt is made to re-stage. The hello inactivity timer is enabled in the oneWayInside, twoWayInside, oneWayOutside, twoWayOutside and commonOutside hello states (see the helloState attribute on the Rcc component for a description of these states). Note that the value for the Hello interval used in the calculation is the one specified in the Hello packet from the neighbor node. A value of 0 specifies that the value provisioned for the helloInactivityFactor attribute of the ARtg Pnni component should be used. DESCRIPTION

This group contains the three OSI State attributes. The descriptions generically indicate what each state attribute implies about the component. Note that not all the values and state combinations described here are supported by every component which uses this group. For component-specific information and the valid state combinations, refer to NTP 241-7001-150, Passport Operations and Maintenance Guide.

An entry in the mscAtmIfPnniRccStateTable.

This attribute indicates the OSI Administrative State of the component. The value locked indicates that the component is administratively prohibited from providing services for its users. A Lock or Lock - force command has been previously issued for this component. When the value is locked, the value of usageState must be idle. The value shuttingDown indicates that the component is administratively permitted to provide service to its existing users only. A Lock command was issued against the component and it is in the process of shutting down. The value unlocked indicates that the component is administratively permitted to provide services for its users. To enter this state, issue an Unlock command to this component. Enumeration: 'locked': 0, 'shuttingDown': 2, 'unlocked': 1.

This attribute indicates the OSI Operational State of the component. The value enabled indicates that the component is available for operation. Note that if adminState is locked, it would still not be providing service. The value disabled indicates that the component is not available for operation. For example, something is wrong with the component itself, or with another component on which this one depends. If the value is disabled, the usageState must be idle. Enumeration: 'disabled': 0, 'enabled': 1.

This attribute indicates the OSI Usage State of the component. The value idle indicates that the component is not currently in use. The value active indicates that the component is in use and has spare capacity to provide for additional users. The value busy indicates that the component is in use and has no spare operating capacity for additional users at this time. Enumeration: 'active': 1, 'idle': 0, 'busy': 2.

This group contains the operational attributes for an Rcc component.

An entry in the mscAtmIfPnniRccOperTable.

This attribute indicates the role of this link in the PNNI hierarchy. The following values are possible: unknown: the Hello protocol has not yet determined the role of the link. lowestLevelHorizLink: the link is a horizontal link between two lowest level nodes. lowestLevelOutsideLink: the link is an outside link between two border nodes. horizontalLinkToLgn: the link is a horizontal link to a Logical Group Node (LGN). uplink: the link is a uplink to a higher level LGN. Enumeration: 'unknown': 0, 'lowestLevelHorizLink': 1, 'horizontalLinkToLGN': 3, 'uplink': 4, 'lowestLevelOutsideLink': 2.

This attribute indicates the PNNI version negotiated with the neighbor node. Enumeration: 'version1point0': 1, 'unsupported': 0.

This attribute indicates the state of the Hello protocol exchange over this link. The following are the possible values for this attribute: down: the link is down; no PNNI routing packets will be sent over or received over such a link. This is the initial state of the Hello Finite State Machine, and can also be reached when lower-level protocols have indicated that the link is not usable. attempt: no Hello packets or Hello packets, with mismatch information, have been received recently from the neighbor. Attempts are made to contact the neighbor node by sending out Hello packets every helloInterval seconds. oneWayInside: Hello packets have been recently received from the neighbor and it has been established that both nodes are members of the same peer group, but the remote node ID and remote port ID in the neighbor's Hello packets were set to zero. A Hello packet is sent to the neighbor and the Hello timer is restarted. twoWayInside: Bidirectional communication over this link between this node and the neighbor node has been achieved. oneWayOutside: Hello packets have been recently received from the neighbor and it has been established that both nodes are members of a different peer group, but the remote node ID and remote port ID in the neighbor's Hello packets were set to zero. twoWayOutside: Hellos have recently been received from the neighbor indicating that the neighbor node belongs to a different peer group. The correct remote node ID and remote port ID fields were included in the Hello packet, but the nodal hierarchy list did not include any common peer group. This state can also be reached if a hierarchy mismatch occurs while in the commonOutside state. commonOutside: A common level of the routing hierarchy has been found, in addition to achieving full bi-directional communication between the two nodes. Enumeration: 'attempt': 2, 'oneWayOutside': 5, 'twoWayInside': 4, 'down': 1, 'notApplicable': 0, 'oneWayInside': 3, 'twoWayOutside': 6, 'commonOutside': 7.

This attribute indicates the neighbor node's node id.

This attribute indicates the neighbor node's port id.

This group contains the statistical attributes for an Rcc component.

An entry in the mscAtmIfPnniRccStatsTable.

This attribute counts the total number of Hello packets received across this RCC, including bad and mismatched Hello packets. The counter wraps when it exceeds the maximum value.

This attribute counts the total number of Hello packets transmitted across this RCC. The counter wraps when it exceeds the maximum value.

This attribute counts the total number of mismatched Hello packets received over this RCC. The counter wraps when it exceeds the maximum value.

This attribute counts the total number of bad Hello packets received over this RCC. The counter wraps when it exceeds the maximum value.

This entry controls the addition and deletion of mscAtmIfPnniAddr components.

A single entry in the table represents a single mscAtmIfPnniAddr component.

This variable is used as the basis for SNMP naming of mscAtmIfPnniAddr components. These components can be added and deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the mscAtmIfPnniAddr tables.

This variable represents an index for the mscAtmIfPnniAddr tables.

This variable represents an index for the mscAtmIfPnniAddr tables. Enumeration: 'default': 3, 'registered': 2, 'alternate': 1, 'primary': 0.

This entry controls the addition and deletion of mscAtmIfPnniAddrTermSP components.

A single entry in the table represents a single mscAtmIfPnniAddrTermSP component.

This variable is used as the basis for SNMP naming of mscAtmIfPnniAddrTermSP components. These components can be added and deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the mscAtmIfPnniAddrTermSP tables.

This variable represents the index for the mscAtmIfPnniAddrTermSP tables.

This entry controls the addition and deletion of mscAtmIfPnniAddrPnniInfo components.

A single entry in the table represents a single mscAtmIfPnniAddrPnniInfo component.

This variable is used as the basis for SNMP naming of mscAtmIfPnniAddrPnniInfo components. These components can be added and deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the mscAtmIfPnniAddrPnniInfo tables.

This variable represents the index for the mscAtmIfPnniAddrPnniInfo tables.

This attribute group contains the provisioned attributes relating to PNNI for a PnniInfo component.

An entry in the mscAtmIfPnniAddrPnniInfoProvTable.

This attribute specifies the scope of the ATM address, which is the highest level up to which this address will be advertised in the PNNI hierarchy. The scope must be set to a value numerically less than or equal to the level of the lowest level peer group containing this node. Setting the scope to 0 will cause the address to be advertised globally within this PNNI routing domain.

This attribute indicates whether the address is internal or exterior. An internal reachable address is an address of a destination that is directly attached to the logical node advertising the address. An exterior reachable address is an address that can be reached through a PNNI routing domain, but which is not located in that PNNI routing domain. Enumeration: 'internal': 0, 'exterior': 1.

This attribute group contains the operational attributes for the Address component.

An entry in the mscAtmIfPnniAddrOperTable.

This attribute indicates the scope of the ATM address, which is the highest level to which this address will be advertised in the PNNI hierarchy. If no PnniInfo subcomponent has been provisioned, then the scope will default to the level of this node in the PNNI hierarchy. If this node does not participate in a PNNI hierarchy, then this attribute will have the value of -1.

This attribute indicates whether the address is internal or exterior. An internal reachable address is an address of a destination that is directly attached to the logical node advertising the address. An exterior reachable address is an address that can be reached through a PNNI routing domain, but which is not located in that PNNI routing domain. Enumeration: 'internal': 0, 'exterior': 1.

This group contains the provisionable attributes for the Pnni component.

An entry in the mscAtmIfPnniProvTable.

This attribute represents the time in seconds to wait between call setup retries. The resolution is to the nearest 10 seconds. This attribute has been obsoleted and is replaced by the softPvpAndPvcRetryPeriod attribute.

This attribute represents the time in seconds to wait between soft PVP or soft PVC call setup retries. The resolution is to the nearest 10 seconds.

This attribute specifies how long to hold off retries following a release or the connection. The resolution is to the nearest 50 ms.

This group contains the provisionable administrative weights for the Pnni component. These weights will be used by Generic Connection Admission Control (GCAC) if administrative weight is the selected optimization criterion.

An entry in the mscAtmIfPnniAdminWeightsTable.

This attribute specifies the administrative weight assigned for setting up switched calls with a service category of Constant Bit Rate (CBR) for this PNNI interface. The value specified will be used by Generic Connection Admission Control (GCAC) if administrative weight is the selected optimization criterion; the higher the value, the less desirable the link will be in path selection.

This attribute specifies the administrative weight assigned for setting up switched calls with a service category of Real-Time Variable Bit Rate (RT-VBR) for this PNNI interface. The value specified will be used by Generic Connection Admission Control (GCAC) if administrative weight is the selected optimization criterion; the higher the value, the less desirable the link will be in path selection.

This attribute specifies the administrative weight assigned for setting up switched calls with a service category of Non Real-Time Variable Bit Rate (NRT-VBR) for this PNNI interface. The value specified will be used by Generic Connection Admission Control (GCAC) if administrative weight is the selected optimization criterion; the higher the value, the less desirable the link will be in path selection.

This attribute specifies the administrative weight assigned for setting up switched calls with a service category of Unspecified Bit Rate (UBR) for this PNNI interface. The value specified will be used by Generic Connection Admission Control (GCAC) if administrative weight is the selected optimization criterion; the higher the value, the less desirable the link will be in path selection.

This group contains the provisionable attributes for accounting.

An entry in the mscAtmIfPnniAcctOptTable.

This attribute is used to turn accounting on or off for SVC and SPVC connections. It also specifies the reason(s) for which accounting data is collected: billing, test, study, audit, or force. If the set of reasons is not empty then accounting records will be generated by this interface in the following situations: - on a TODA changeover if TODA is enabled; - every 12 hours (per connection) if TODA is disabled; - on every call clear (a call record with final cell counts). If none of the reasons is present, then accounting will be suppressed. The reason for collection is recorded in the accounting record, in the attribute callingCollectReason or calledCollectReason as appropriate. Description of bits: bill(0) test(1) study(2) audit(3) force(4)

This attribute specifies whether accounting records generated by this interface should be marked as originating, terminating or intermediate. This attribute, in combination with the direction of the call, determines the value of attribute connPointType of the accounting record and may be used by downstream accounting processes to correlate the records. If the value is origTerm then records generated for incoming calls will be marked as originating and records generated for outgoing calls will be marked as terminating. If the value is intermediate then records generated for all calls will be marked as intermediate. Enumeration: 'origTerm': 0, 'intermediate': 1.

This attribute specifies the accounting class associated with the interface. Its meaning is determined by the network operator. Its value is simply recorded in the accounting records generated by this interface, in the attribute callingServiceType or calledServiceType as appropriate.

This attribute specifies the data service exchange associated with this interface. Its meaning is determined by the network operator. Its value is simply recorded in the accounting records generated by this interface, in the attribute callingDse or calledDse as appropriate.

This group contains the operational attributes for a Pnni component.

An entry in the mscAtmIfPnniOperationalTable.

This attribute indicates the port id of the PNNI interface, which is the parent AtmIf's instance number.