ATM-FORUM-AUTO-CONFIG: View SNMP OID List / Download MIB

The ATM Forum ILMI Auto Configuration Extension ATM Service Type Information.

An entry in the service type table describes the reference information about a service that may be associated with individual ATM connections for the purpose of auto- configuration. This information describe the name and sub- name of the service, the client layer protocol using the ATM service, the TM 4.0 service category, and the TM 4.0 conformance definition.

A number between which identifies the entry in the Service Type Table.

This string identifies the name of the service provider for the service described in this profile. The value of this attribute should not set to NULL.

This string identifies the name of the service described in this profile. The value of this attribute should not be set to NULL.

This string identifies the sub-name of the service described in this profile. A Service may have zero or more sub-names, each with its own service type profile.

This string identifies the client protocol of the service described in this profile. A Service (sub-service) may have zero or more described client, each with its own service type profile.

The TM 4.0 Service category used for this service type. Indicates CBR, rt-VBR, nrt-VBR, ABR, UBR, (or GFR) Enumeration: 'rtVbr': 3, 'ubr': 6, 'gfr': 7, 'cbr': 2, 'abr': 5, 'other': 1, 'nrtVbr': 4.

The TM 4.1 conformance definition used for this service type. Indicates CBR.1, VBR.1, VBR.2, VBR.3, UBR.1, UBR.2, ABR, GFR.1, or GFR.2. Enumeration: 'vbr2': 4, 'vbr3': 5, 'none': 0, 'vbr1': 3, 'cbr1': 2, 'abr': 8, 'other': 1, 'gfr1': 9, 'gfr2': 10, 'ubr2': 7, 'ubr1': 6.

The ATM Forum ILMI Auto Configuration Extension ATM Service Connection Information.

An entry in the service connection information table describes the ATM connection that provides a service across an ATM interface. The connection is identified by port and VPI/VCI value. Information about the connection includes the connection type (VP or VC, SVC or PVC), and the association of the connection with a service type. Specific connection information, such as traffic descriptors, should be accessed in the atmfVpc and atmfVcc tables defined in ILMI.

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

The VPI value of the ATM service connection at the local ATM interface.

The VCI value of the ATM service connection at the local ATM interface. If the atmfAtmServiceSignalId indicates that the connection is a VP connection, the value of this attribute shall be set to 0 (zero) and any meaning of this attribute ignored.

This attribute represents the characteristic information of the layer network domain. It may be set to either VC characteristic information (vcCI) or VP characteristic information (vpCI). Enumeration: 'vpCI': 1, 'vcCI': 0.

The value of this object identifies the row in the atmfAtmServiceTypeTable. This entry represents the association between an ATM service connection and an ATM service type profile that describes it.

This string identifies the name of the service connection. The value of this attribute may be set to NULL.

Describes the AAL Type of the ATM service connection. A value of none indicates that no AAL is used. The AAL types include AAL1, AAL 3/4, and AAL 5. The value other may be a user-defined AAL type. The unknown type indicates that the AAL type cannot be determined. Enumeration: 'none': 0, 'aal2': 6, 'unknown': 5, 'aal1': 1, 'aal5': 3, 'other': 4, 'aal34': 2.

The value of this object identifies the row in the atmfAAL1ProfileTable for AAL 1 connection, the atmfAAL34ProfileTable for AAL3/4 connection, and the atmfAAL5ProfileTable for AAL 5 connections. This entry represents the association between an ATM service connection and an ATM Adaptation Layer profile that describes it.

The ATM Forum ILMI Auto Configuration Extension AAL1 Profile Information.

An entry in the AAL1 Profile table provides data that describes the AAL1 processing function.

A number between which identifies the entry in the AAL1 Profile Table.

This attribute describes AAL type 1 subtype used by the CBR service application (e.g. 64 KBPS voice band signal transport, circuit transport). Enumeration: 'highQualityAuto': 4, 'voiceBand': 1, 'circuitEmulationAsynchronous': 3, 'video': 5, 'circuitEmulationSynchronous': 2, 'null': 0.

This attribute describes the rate of the CBR service supported by the AAL.

This attribute indicates whether the clock recovery type is synchronous, asynchronous-SRTS(Synchronous Residual Time Stamp), or asynchronous-Adaptive Clock Recovery. Enumeration: 'srts': 1, 'adaptive': 2, 'synchronous': 0.

This attribute indicates the FEC method: no FEC, FEC for Loss Sensitive Signal Transport, or FEC for Delay Sensitive Signal Transport. Enumeration: 'delaySensitiveSignalFEC': 2, 'noFEC': 0, 'lossSensitiveSignalFEC': 1.

This attribute indicates whether Structured Data Transfer (SDT) has been configured at the AAL. A value of TRUE means SDT has been selected. This attribute value can be set to TRUE only when the Forward Error Correction Type attribute equals noFEC. Enumeration: 'true': 1, 'false': 0.

This attribute identifies the number of leading octets in use.

This attribute represents the time in milliseconds for the cell loss integration period. If cells are lost for this period of time, the Interworking VCC Termination Point entity will generate a cell starvation alarm.

The ATM Forum ILMI Auto Configuration Extension AAL3/4 Profile Information.

An entry in the AAL34 Profile table provides data that describes the AAL3/4 processing function.

A number between which identifies the entry in the AAL3/4 Profile Table.

This attribute represents the maximum CPCS_PDU size that will be transmitted over the connection in both the incoming (forward) direction of transmission.

This attribute represents the maximum CPCS_PDU size that will be transmitted over the connection in both the outgoing (backward) direction of transmission.

This attribute represents the low value of MID supported at the AAL for the supporting VCC.

This attribute represents the high value of MID supported at the AAL for the supporting VCC.

This attribute indicates whether the AAL for the supporting VCC is operating in message mode or streaming mode, assured or unassured. Enumeration: 'streamingUnassured': 3, 'messageUnassured': 1, 'messageAssured': 0, 'streamingAssured': 2.

This attribute identifies the SSCS type for the AAL. Valid values are NULL, Data SSCS based on SSCOP (assured operation), Data SSCS based on SSCOP (non-assured operation), or Frame Relay SSCS Enumeration: 'dataNonAssured': 2, 'dataAssured': 1, 'null': 0, 'frameRelay': 3.

The ATM Forum ILMI Auto Configuration Extension AAL5 Profile Information.

An entry in the AAL5 Profile table provides data that describes the AAL5 processing function.

A number between which identifies the entry in the AAL5 Profile Table.

This attribute represents the maximum CPCS_PDU size that will be transmitted over the connection in both the incoming (forward) direction of transmission.

This attribute represents the maximum CPCS_PDU size that will be transmitted over the connection in both the outgoing (backward) direction of transmission.

This attribute indicates whether the AAL for the supporting VCC is operating in message mode or streaming mode, assured or unassured. Enumeration: 'streamingUnassured': 3, 'messageUnassured': 1, 'messageAssured': 0, 'streamingAssured': 2.

This attribute identifies the SSCS type for the AAL. Valid values are NULL, Data SSCS based on SSCOP (assured operation), Data SSCS based on SSCOP (non-assured operation), or Frame Relay SSCS Enumeration: 'dataNonAssured': 2, 'dataAssured': 1, 'null': 0, 'frameRelay': 3.

The ATM Forum ILMI Auto Configuration Extension AAL2 Profile Information. This table contains AAL2 parameters that are common to all AAL2 applications. These parameters are taken from I.363.2, I.366.1 and I.366.2

An atmfAAL2CommonProfileEntry provides AAL2 common parameters of operation that are to be used by the PVC associated with this entry.

A number which uniquely identifies the entry in the AAL2 Profile Table.

The application identifier specifies which AAL2 application is using the PVC. In addition it specifies protocol combinations to be used on AAL2 channels between IWFs, i.e. it implicitly configures the use of I.366.1 or I.366.2 for bearer and signalling AAL2 channels. The value of this object should be one of those values given in the administered list of AppIds for AAL2 Applications in section 5 of the ATM Forum document of well-known addresses and assigned codes which can be located at vhttp://www.atmforum.com/atmforum/specs/public_assigned_codes.pdf.

This object identifies which management channel is responsible for AAL2 provisioning and auto-configuration. The user-side IME must check the value of this parameter first before configuring the AAL2 for the PVC to determine whether or not this responsibility lies with ILMI. ilmi - if this is selected then the user-side IME must use the AAL2 Profile defined in this entry and associated AAL2 Profile extension table entry to auto-configure the AAL2 for the PVC. lesEoc - if this is selected then the user-side IME must not auto-configure the AAL2 using ILMI. The AAL2 Profile parameters do not need to be provisioned by the network- side IME and with the exception of this object the AAL2 profile parameters in the ILMI MIB are not applicable. The Loop Emulation Service Embedded Operations Channel (LES EOC) shall be used to provision the AAL2 for the PVC. The start-up AAL2 parameters for this PVC must assume the default values specified in the af-vmoa-0145.000 MIB such that the LES EOC is operational. other - if this is selected then the user-side IME must not auto-configure the AAL2 using ILMI. The AAL2 Profile parameters do not need to be provisioned by the network- side IME and with the exception of this object the AAL2 profile parameters in the ILMI MIB are not applicable. Another mechanism will be used to provision the AAL2 at the ATU-R for the PVC. Enumeration: 'other': 3, 'ilmi': 1, 'lesEoc': 2.

Maximum number of multiplexed channels.

Maximum CPS-SDU size given in octets. This parameter is bidirectional, i.e. its value applies to both directions of the AAL2 connection.

This is the maximum size and SSSAR-SDU can take as defined in I.366.1. This parameter only applies to those AAL2 channels using I.366.1 SSSAR. This parameter is bidirectional, i.e its value applies to both directions of the AAL2 connection. Note that if the appID indicates Loop Emulation Service as the AAL2 application then the minimum allowable value of this parameter is 493.

This specifies whether the SSTED service is used or not. If the value of this object is 'selected' then I.366.1 SSSAR must be supported by the AAL2. This parameter only applies to those AAL2 channels using I.366.1 SSSAR. Enumeration: 'notSelected': 2, 'selected': 1.

This specifies whether SSADT service is used or not. Note that if the value of this object is 'selected' then I.366.1 SSSAR must be supported and by implication the SSTED service must also be 'selected'. This parameter only applies to those AAL2 channels using I.366.1 SSSAR. Enumeration: 'notSelected': 2, 'selected': 1.

This object describes the type of service category supported by this AAL2 PVC. Enumeration: 'audioAndMultiRate': 3, 'audio': 1, 'multirate': 2.

This object describes whether the Audio Service that is used for transporting voice and voiceband data is enabled or disabled. Enumeration: 'disabled': 1, 'enabled': 2.

This attribute describes the source of the profile. Enumeration: 'itut': 1, 'other': 2.

This attribute contains the IEEE Organizationally Unique Identifier (OUI) of the organisation that specified the profile being used, if other than ITU-T. For example, if the source is the ATM Forum, the value of this object is 00A03E. This attribute is only meaningful if atmfAAL2SccsProfileSource has the value 'other'.

This object describes the predefined profile identifier.

This object describes the type of PCM encoding used. Enumeration: 'ulaw': 2, 'aLaw': 1.

This object describes whether transport of demodulated facsimile data is enabled or disabled. Enumeration: 'disabled': 1, 'enabled': 2.

This attribute describes whether transport of CAS signaling bits is enabled or disabled. Enumeration: 'disabled': 1, 'enabled': 2.

This attribute describes whether transport of DTMF dialled digits is enabled or disabled. Enumeration: 'disabled': 1, 'enabled': 2.

This object describes whether transport of MF-R1 dialled digits is enabled or disabled. Enumeration: 'disabled': 1, 'enabled': 2.

This object describes whether transport of MF-R2 dialled digits is enabled or disabled. Enumeration: 'disabled': 1, 'enabled': 2.

This object describes whether transport of circuit mode data is enabled or disabled. Enumeration: 'disabled': 1, 'enabled': 2.

This object describes the multiplier N in N*64kbit/s circuit mode data. It is only applicable if the value of atmfAAL2SscsCircuitModeDataTransport is 'enabled'.

This object describes whether the I.366.2 frame mode data service is enabled or disabled. Enumeration: 'disabled': 1, 'enabled': 2.

This object specifies the maximum length of I.366.2 frame mode data. It is only applicable if the value of atmfAAL2FrameModeDataTransport is 'enabled'.

The Maximum SSCOP-SDU length. This object is only required is the value of atmfAAL2SscsSsadtStatus is selected else it is not applicable.

The Maximum SSCOP-UU field length. This object is only required is the value of atmfAAL2SscsSsadtStatus is selected else it is not applicable.

The ATM Forum ILMI Auto Configuration Extension AAL2 Profile Information. This table contains AAL2 parameters that are specific to the ATM Trunking AAL 2 application. These parameters are taken from af-vtoa-0113.000

An atmfAAL2TrunkingProfileEntry provides AAL2 parameters of operation for ATM Trunking applications to be used in addition to those provided in the Common AAL2 Profile Table. These together provide complete configuration of AAL2 for PVCs that support ATM Trunking using AAl2 as defined in af-vtoa-0113.000.

This object uniquely identifies a PVC between IWFs.

This object specifies the VCCI of the PVC that is used to carry the CCS for this PVC.

The ATM Forum ILMI Auto Configuration Extension AAL2 Profile Information. This table contains AAL2 parameters that are specific to the ATM LES AAL 2 application. These parameters are taken from af-vmna-0145.000

An atmfAAL2LESProfileEntry provides AAL2 parameters of operation for LES applications to be used in addition to those provided in the Common AAL2 Profile Table. These together provide complete configuration of AAL2 for PVCs that support LES using AAl2 as defined in af-vmoa-0145.000.

The minimum value the CID can take for AAL2 bearer channels and ISDN-D channels.

The maximum value the CID can take for AAL2 bearer channels and ISDN-D channels.

This object refers to the mode of operation of the CPS on the CP-IWF The value of this object imposes a restriction on the CPS-SDU length and hence must override the value of atmfAAl2CpsMaxSDULength. singleCpsPacketPerCpsPduNoOverlap -A single CPS Packet is contained within a CPS-PDU and no overlap can occur into the next CPS-PDU. If this option is selected, then Timer_CU is not applicable. Also Max CPS-SDU size must be less than or equal to 44. multipleCpsPacketsPerCpsPduWithOverlap - Multiple CPS Packets are contained within a CPS-PDU and overlap can occur into the next CPS-PDU. If this option is selected, then Timer_CU is applicable. Also Max CPS-SDU size must be less than or equal to 64. Enumeration: 'multipleCpsPacketsPerCpsPduWithOverlap': 2, 'singleCpsPacketPerCpsPduNoOverlap': 1.

The ATM Forum ILMI Auto Configuration Extension ATM Service Connection Information.

An entry in the service connection information extension table provides additional elements that help describe the ATM connection that provides a service across an ATM interface. The connection is identified by port and VPI/VCI value.

When the physical and/or MAC layer has more than one PHY-connection or MAC-connection, this object is used to select the PHY- or MAC-connection to be bound to the PVC. The semantics of the value of this object is PHY and/or MAC specific. This semantics generally shall be specified with the PHY or MAC. However, the semantics for the two PHY/MAC specifications which have been identified as having multiple connections is provided here for convenience: When the physical layer is dual latency ADSL, the PhyMacIdentifier selects the latency path to be bound to each direction of transmission for the PVC. The value of the PhyMacIdentifier shall be as follows: default = 0 upstream and downstream both interleaved path = 1 upstream and downstream both fast path = 2 upstream interleaved path, downstream fast path = 3 upstream fast path, downstream interleaved path = 4 The 'default' value shall be used for single latency ADSL PHYs. When the physical and MAC layers are IEEE 802.14, the PhyMacIdentifier specifies the 802.14 Local Identifier for the PVC

The ATM Forum ILMI Auto Configuration Extension ATM Service Type Extension Information.

An entry in the service type extension table describes additional information about a service that may be associated with individual ATM connections for the purpose of auto-configuration. This information describes the Client Protocol ID's associated with a particular service.

This object shall be used to select the user plane layer 2 protocol (if any) to be used above the AAL. The first octet of this object shall be encoded as follows. Bits 5-7 (i.e. the three most significant bits) shall be set to 0; any other values shall be ignored. Bits 0-4 (i.e. the five least significant bits) shall be encoded as shown in the entry for 'User information layer 2 protocol (octet 6)' in Table 4-10/Q.2931. However, if no user plane layer 2 protocol is present above the AAL, then the first (and only) octet shall be encoded as '0b00000000'. If the encoding of the first octet requires subsequent octets, then bit 7 (i.e., the most significant bit) of each of these octets shall be set to 0; however, if it is set to 1, it shall be ignored. Bits 0-6 shall be encoded according to table 4-10/Q.2931. If more than one subsequent octet is needed, then octets shall appear in the order shown in figure 4-16/Q.2931.

This object shall be used to select a user plane layer 3 protocol (or user plane layer 2 bridging). The first octet of this object shall be encoded as follows. Bits 5-7 (i.e., the three most significant bits) shall be set to 0; any other values shall be ignored. Bits 0-4 (i.e., the five least significant bits) shall be encoded as shown in the entry for 'User information layer 3 protocol (octet 7)' in Table 4-10/Q.2931. However, if no user plane layer 3 protocol is specified, then the first (and only) octet shall be encoded as '0b00000000'. a) If ISO TR9577 network layer protocol identification is to be used, then the first octet shall be encoded to indicate 'ISO/IEC TR9577'. In this case, either: i) the user plane layer 3 protocol is to be selected in the management plane. The second octet of this object shall contain the ISO/IEC TR9577 Initial Protocol Identifier (IPI). - For layer 3 protocols for which ISO/IEC has assigned a Network Layer Protocol Identifier (NLPID), then this NLPID shall be used as the IPI, and the length of the octet string shall be 2. - For layer 3 protocols for which ISO/IEC has not assigned an NLPID, the IPI shall be encoded to indicate 'IEEE 802.1a SNAP identifier' (see Annex D of ISO/IEC 9577). The following five octets (octets 3 through 7) of this object shall then contain a SNAP identifier, which consists of a 3-octet organization unique identifier (OUI) and a 2-octet protocol identifier (PID). This SNAP coding shall be used only if ISO/IEC has not assigned a Network Layer Protocol Identifier for the layer 3 or layer 2 protocol. The octet string shall thus be 7 octets long. - If an IME wishes to indicate that bridged LAN frames are to be carried in the user plane then the IPI shall be encoded to indicate 'IEEE 802.1a SNAP identifier'. The following five octets of this object shall contain a SNAP identifier, which indicates the bridged protocol. For consistency with SIG 4.0, use of the ISO/IEC subsequent protocol identifier (SPI) is not recommended but not explicitly prohibited as one can envision scenarios where it has utility. or ii) the user plane layer 3 protocol is to be selected using network layer protocol identification in the user plane. The octet-string shall be one octet long. The first octet(s) of each layer 3 protocol data unit shall contain layer 3 protocol identification according to ISO/IEC TR9577. b)If bits 0-4 of the first octet of the octet string are set to any value other than 'ISO/IEC TR9577', then any subsequent octets shall be encoded as follows. Bit 7 (i.e., the most significant bit) of each of these octets shall be set to 0; however, if it is set to 1, it shall be ignored. Bits 0-6 shall be encoded according to the codings for octet 7a, octet 7b and octet 7c specified in table 4- 10/Q.2931. If more than one subsequent octet is needed, then octets shall appear in the order shown in figure 4-16/Q.2931.

Additional parameters for the AAL5 Profile are stored in this table.

An entry in this table augments an entry in the atmfAAL5ProfileTable

This object's value is only applicable if the AAL5 VCC is carrying CCS for AAL2 narrowband calls.

The reason for the failure to configure the PVC at the ATU-R Enumeration: 'tooManyPVCs': 5, 'unsupportedAAL': 3, 'unsupportedClientProtocol': 1, 'incompleteConfigurationInformation': 6, 'unsupportedServiceCategory': 2, 'inconsistentConfigurationInformation': 7, 'invalidVPIVCIValue': 4.

This object holds a pointer to a row in the appropriate table depending on the value of the atmfAtmServiceFailReason object. This will allow the network side to determine MIB information that caused the auto-configuration failure. The value of this object should be as follows: If atmfAtmServiceConfFailReason = 1 or 2, then this object's value points to the row in the atmfAtmServiceTypeTable that is the cause of the problem. If atmfAtmServiceConfFailReason = 3, then this object's value points to the row in the atmfAALxProfileTable, where x is 1, 2, 34, or 5 depending on the AAL that can't be supported. If atmfAtmServiceConfFailReason = 4, then this object's value points to the row in the atmfAtmServiceConnInfoTable that is the cause of the problem. For any other value of atmfAtmServiceConfFailReason, this object's value should be ignored.

The user-side IME will send this trap whenever it is unable to configure itself based on the information provided in the ILMI auto-configuration MIB. The variables included in the trap identify the reason for the failure and the row in the MIB table that caused the failure.