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

This entry controls the addition and deletion of mscAal1Ces components.

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

This variable is used as the basis for SNMP naming of mscAal1Ces 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 mscAal1Ces tables.

This variable represents the index for the mscAal1Ces tables.

This entry controls the addition and deletion of mscAal1CesNap components.

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

This variable is used as the basis for SNMP naming of mscAal1CesNap 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 mscAal1CesNap tables.

This variable represents the index for the mscAal1CesNap tables.

This group contains the provisioning data for the NailedUpAdaptationPoint component.

An entry in the mscAal1CesNapProvTable.

This attribute specifies the identity of the component to which the NailedUpAdaptationPoint is linked. This is an AtmIf Vcc NailedUpEndPoint or an AtmIf Vpt Vcc NailedUpEndPoint (the AAL1 cells are transported off the switch over an ATM UNI, where they are routed to the appropriate AAL1 entity at the other end by the ATM bearer service).

This entry controls the addition and deletion of mscAal1CesAep components.

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

This variable is used as the basis for SNMP naming of mscAal1CesAep 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 mscAal1CesAep tables.

This variable represents the index for the mscAal1CesAep tables.

This group contains NSAP address provisioning data for components using switched virtual circuits.

An entry in the mscAal1CesAepProvEndPointAddrTable.

This attribute specifies the expected remote address prefix for an incoming connection setup request. If expectedRemoteAddress is not empty, only matching connections will be considered for acceptance. If expectedRemoteAddress is 40 characters long, the remote address must match exactly to be accepted. If expectedRemoteAddress is less than 40 characters long, the remote address must begin with expectedRemoteAddress to be accepted. If expectedRemoteAddress is empty, the component will process connection requests from any remote address.

This attribute specifies the local NSAP address. If the switch prefix (the nodePrefix attribute of the ModuleData component) has been provisioned, a default value for localAddress based on nodePrefix will be provided. If ModuleData nodePrefix has not been provisioned and one or more alternate switch prefixes (the alternatePorsPrefixes attribute of the ModuleData component) have been provisioned, a default value for localAddress based on the first provisioned alternatePorsPrefix value will be provided. If no switch prefixes have been provisioned, localAddress will default to an empty string. To obtain a valid default localAddress in this case, either or both of the ModuleData nodePrefix and ModuleData alternatePorsPrefixes attributes must be provisioned, and this end point component must then be deleted and re-added.

This group contains the provisioning data specific to the ActiveEndPoint component.

An entry in the mscAal1CesAepProvTable.

This attribute specifies the remote NSAP address which this ActiveEndPoint will call.

This attribute specifies the type of routing to use for establishing the connection: AAL1 cards accept only porsOnly. Multi-Service Access cards accept all four options. porsOnly means that only the Path Oriented Routing System may be used in establishing a connection. atmOnly means that only the native ATM Routing may be used in establishing a connection. porsFirst means that the switch tries to establish a connection using the Path Oriented Routing System first, and, if the connection cannot be established, it tries native ATM Routing instead. atmFirst means that the switch tries to establish a connection using native ATM Routing first, and, if the connection cannot be established, it tries the Path Oriented Routing System instead. Enumeration: 'atmOnly': 1, 'atmFirst': 3, 'porsOnly': 0, 'porsFirst': 2.

This attribute specifies the PORS routing profile to use for this connection. If profile is empty, PORS will provide a default profile.

This attribute specifies the time to wait, in seconds, before attempting to establish the connection after the first failed attempt. The time to wait between subsequent call attempts will generally differ due to a backoff scheme.

retryLimit specifies the maximum number of consecutive unsuccessful connection setup attempts that may be made before further attempts are abandoned. If this limit is reached, the Restart verb may be used to restart connection attempts. If retryLimit is 0, there is no limit; attempts will continue indefinitely until a successful connection is established.

activeEndPointType specifies the type of end point: svc or softPvc. The default is svc. When activeEndPointType is svc, calledVpiVci is not relevant. When activeEndPointType is softPVC, routingOption must be atmOnly, and profile, firstRetryInterval, and retryLimit are not relevant. Enumeration: 'svc': 0, 'softPVC': 1.

calledVpiVci specifies the identity of the PVC at the remote ATM node on which the softPVC connection terminates. calledVpiVci is relevant only when activeEndPointType is set to softPVC. The default value is 0.1

This group contains general operational attributes for components using switched virtual circuits.

An entry in the mscAal1CesAepEpOperTable.

remoteAddress is the address of the remote end point. If a connection is currently established, remoteAddress will contain the address of the remote end point. If a connection is not established, remoteAddress will be Unknown.

lastTearDownCause indicates the cause of the last connection tear down. The values are as defined in the ATM Forum ATM User-Network Interface (UNI) Specification.

lastTearDownDiagnostic provides a diagnostic to supplement the lastTearDownCause attribute.

This group contains status information about the AAL1 Circuit Emulation Service ActiveEndPoint component.

An entry in the mscAal1CesAepOutTable.

svcStatus indicates the status of the incoming and outgoing connections. When this attribute has the value initialising, it indicates that the component is initialising when first created; a connection has not been established, and no incoming setup requests will be processed. When this attribute has the value connecting, it indicates that a connection has not yet been established, but that incoming setup requests will be processed. When this attribute has the value connected, it indicates that a connection has been established. When this attribute has the value retriesExhausted, it indicates that retryLimit consecutive connection setup attempts have failed, and the connection procedure has been aborted. When this attribute has the value idle, it indicates that a connection has not been established, and that no incoming setup requests will be processed. When this attribute has the value failed, it indicates that the connections is in a state other than those described above. Enumeration: 'retriesExhausted': 4, 'failed': 5, 'idle': 3, 'connected': 2, 'initialising': 0, 'connecting': 1.

lastSetupFailureCause indicates the cause of the last connection setup failure. The values are as defined in the ATM Forum ATM User- Network Interface (UNI) Specification.

lastSetupFailureDiagnostic provides a diagnostic to supplement the lastSetupFailureCause attribute.

retryTimerValue is the current value of the retry timer for this connection; it indicates the number of seconds before the next connection attempt will be made. retryTimerValue is initialized when a connection attempt fails. When retryTimerValue reaches 0, an attempt will be made to establish the connection. When the timer is not running, for example when the connection has been established, retryTimerValue will be 0.

retryFailures counts the number of consecutive failed connection attempts. retryFailures is reset to 0 whenever a connection is successfully established, or the connection is restarted using the Restart verb. The counter wraps when the maximum value is exceeded.

This entry controls the addition and deletion of mscAal1CesPep components.

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

This variable is used as the basis for SNMP naming of mscAal1CesPep 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 mscAal1CesPep tables.

This variable represents the index for the mscAal1CesPep tables.

This group contains NSAP address provisioning data for components using switched virtual circuits.

An entry in the mscAal1CesPepProvEndPointAddrTable.

This attribute specifies the expected remote address prefix for an incoming connection setup request. If expectedRemoteAddress is not empty, only matching connections will be considered for acceptance. If expectedRemoteAddress is 40 characters long, the remote address must match exactly to be accepted. If expectedRemoteAddress is less than 40 characters long, the remote address must begin with expectedRemoteAddress to be accepted. If expectedRemoteAddress is empty, the component will process connection requests from any remote address.

This attribute specifies the local NSAP address. If the switch prefix (the nodePrefix attribute of the ModuleData component) has been provisioned, a default value for localAddress based on nodePrefix will be provided. If ModuleData nodePrefix has not been provisioned and one or more alternate switch prefixes (the alternatePorsPrefixes attribute of the ModuleData component) have been provisioned, a default value for localAddress based on the first provisioned alternatePorsPrefix value will be provided. If no switch prefixes have been provisioned, localAddress will default to an empty string. To obtain a valid default localAddress in this case, either or both of the ModuleData nodePrefix and ModuleData alternatePorsPrefixes attributes must be provisioned, and this end point component must then be deleted and re-added.

This group contains general operational attributes for components using switched virtual circuits.

An entry in the mscAal1CesPepEpOperTable.

remoteAddress is the address of the remote end point. If a connection is currently established, remoteAddress will contain the address of the remote end point. If a connection is not established, remoteAddress will be Unknown.

lastTearDownCause indicates the cause of the last connection tear down. The values are as defined in the ATM Forum ATM User-Network Interface (UNI) Specification.

lastTearDownDiagnostic provides a diagnostic to supplement the lastTearDownCause attribute.

This group contains status information about the AAL1 Circuit Emulation Service PassiveEndPoint component.

An entry in the mscAal1CesPepPassiveOperTable.

svcStatus indicates the status of the incoming connection. When this attribute has the value initialising, it indicates that the component is initialising when first created; a connection has not been established, and no incoming setup requests will be processed. When this attribute has the value connecting, it indicates that a connection has not yet been establised, but that incoming setup requests will be processed. When this attribute has the value connected, it indicates that a connection has been established. When this attribute has the value idle, it indicates that a connection has not been established, and that no incoming setup requests will be processed. When this attribute has the value failed, it indicates that the connections is in a state other than those described above. Enumeration: 'initialising': 0, 'connected': 2, 'idle': 3, 'connecting': 1, 'failed': 5.

This entry controls the addition and deletion of mscAal1CesLCo components.

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

This variable is used as the basis for SNMP naming of mscAal1CesLCo 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 mscAal1CesLCo tables.

This variable represents the index for the mscAal1CesLCo tables.

This group contains all operational attributes for the path oriented LCo.

An entry in the mscAal1CesLCoPathDataTable.

This attribute reflects the current state of the connection. The pathDown state indicates a connection that has no remote end provisioned or the application has not yet signalled for a path. The selectingRoute state occurs when a request has been sent to route selector and it has not yet responded. The connectingState occurs while a path is being established. The pathUp state is the normal operational state of a path. The pathDownRetrying state indicates a path that attempted route selection but received no route and is now waiting to retry route selection again. Enumeration: 'pathUp': 3, 'pathDown': 0, 'pathDownRetrying': 4, 'connecting': 2, 'selectingRoute': 1.

If set and the current PLC remoteName is blank this remoteName will override the blank PLC remoteName. Usually you would set this attribute and then lock/unlock the service component which will result in this new overrideRemoteName being used as if it had been provisioned into the PLC remoteName. The advantage of this attribute is that the connection's remoteName can be changed immediately without having to 'activate prov' but the disadvantage is that the overrideRemoteName is not permanent and if the card or switch is reset the override will be lost.

This attribute identifies whether this is the calling or called end of the path. Enumeration: 'called': 1, 'calling': 0.

This attribute gives the route's total cost metric. It is calculated as the sum of the cost metric of all trunks in the path at the time the connection was established. The cost metric of a trunk is defined by the trunkCost attribute of the Trunk component. The costMetric for an LCo that is originated and terminated on the same module is 0.

This attribute gives the total delay of the route as the one way delay for a 512 byte packet. It is calculated as the sum of the delays of all trunks in the path stored in topology at the time the connection was established. The delay for an LCo that is originated and terminated on the same module is 0.

This attribute contains the time taken for a packet (cell) of 44 bytes to be transmitted to the remote LCo and return to this LCo. The number reported is given in milliseconds to the nearest millisecond. A value of one millisecond is reported if the time is less than 1 millisecond even though the delay may be less than 1 Millisecond when the LCo is originated and terminated on the same module.

This attribute gives the priority at which the current path is established. Zero is the highest priority and four is the lowest. The holdingPriority, a complementary attribute of this component, indicates the priority a path maintains once it is established.

This attribute gives the priority at which a path holds its current path once the path is established. Zero is the highest priority and four is the lowest. The setupPriority, a complementary attribute, indicates the priority of a path at establishment time.

This attribute gives the actual bandwidth (in bits per second) reserved by this path on each of the trunks of its route. This attribute represents the bandwidth for traffic outgoing to the remote end point. The originating end of the connection determines this value.

This attribute gives the actual bandwidth (in bits per second) reserved by this path on each of trunks of its route. This attribute represents the bandwidth for traffic incoming from the remote end point. The originating end of the connection determines this value

This operational attribute indicates the type of traffic transmitted over the path. There are eight possible traffic types, and the path can transmit only one of them. The originating end of the connection determines the type. These are arbitrary designations for traffic type. The voice, data and video traffic types are defined, and five other arbitrary traffic types can be defined by the network administration. This attribute is used in the route selection process to restrict the route to trunks that support this traffic type. The supportedTrafficType trunk attribute lists all the types of traffic allowed on the trunk. For example, if requiredTrafficType is specified as trafficType1 then only trunks that include trafficType1 in supportedTrafficType, will be candidates for this connection. Enumeration: 'trafficType5': 7, 'trafficType4': 6, 'trafficType1': 3, 'trafficType3': 5, 'trafficType2': 4, 'video': 2, 'voice': 0, 'data': 1.

This operational attribute lists up to eight types of trunk that can be used on the route. The originating end of the connection determines the types. The terrestrial and satellite trunk types have been defined, leaving six remaining arbitrary types that can be defined by the network administration. The trunk's type is indicated in the trunkType attribute of the Trunk component. When selecting a route, PORS only chooses trunks whose trunkType are in the permittedTrunkTypes for the path. Description of bits: terrestrial(0) satellite(1) trunkType1(2) trunkType2(3) trunkType3(4) trunkType4(5) trunkType5(6) trunkType6(7)

This attribute indicates the required minimum level of security of the trunks on the route. Zero represents the most secure and seven represents the least secure. The trunk's security is indicated by the trunkSecurity attribute of the Trunk component, and has values identical in range and meaning to the requiredSecurity attribute. PORS ensures that any route selected does not contain a trunk whose trunkSecurity attribute is numerically greater than the requiredSecurity.

This attribute indicates the allowed customer defined parameter of the trunks on the route.The originating end of the connection determines the customer defined parameter. Its value, a number from zero to seven, is chosen by a network administration to have a meaning specific to their network, thus allowing them to customize the use of their trunks. A complementary trunk attribute, customerParameter, also has a value from zero to seven. The route selection process does not consider trunks whose customerParameter is greater than the requiredCustomerParameter of the path.

This attribute indicates the urgency with which packets on the path are emitted by the trunks on the route. The originating end of the connection selects the emissionPriority. EmissionPriority of zero indicates the highest emission priority, while two indicates the lowest emission priority. Packets with a higher emissionPriority (or numerically less) are serviced and sent out before the packets of lower emissionPriority (or numerically higher).

This attribute indicates the importance of the packets on the path.The originating end of the connection sets discardPriority. One is used for paths carrying the most important traffic, and three is used for paths carrying the least important traffic. Packets with lower discardPriority(numerically lower) are discarded after packets with a higher discardPriority(numerically higher).

This attribute indicates whether the path for this PLC was determined automatically or by static provisioning. Normal pathTypes are selected automatically by Route Selector.The other pathTypes are both manual pathTypes where the operator must specify, through provisioning, a static route termed the manualPath. A manual pathType connection is nearly identical to a normal path type connection with the exception that the route is pre-provisioned. For a manual pathType, bandwidth reservations are respected along the path exactly as in a normal path. The last type, the forced pathType, is also a manual path but regardless of the bandwidth available the route is granted provided the trunks are operational and there are sufficient Logical Channels (LChs). The forced pathType could result in over committing the reserved bandwidth allowed on a trunk. A better way to achieve the effects of a forced pathType is to use a manual pathType with setupPriority = 0 and holdingPriority = 0. In this manner the path will reserve correct bandwidth and it will bump other paths if required while not being bumped itself. Enumeration: 'forced': 2, 'manual': 1, 'normal': 0.

This attribute is the count of the number of times the path chosen during route selection could not be instantiated. This count should be three or below if the network is performing adequately. A high value indicates that the route selection is often performed using an out-of-date view of available network bandwidth and/or topology. This attribute will only increase at the calling end of the connection. This attribute is reset each time a path reconnects and stops counting when it reaches its maximum value.

This attribute is the count of the number of times the path has successfully connected. It is set to zero the first time the path is up. If a path fails anytime after connecting this count will be incremented when the path is up again. Failed route requests do not count in this statistic. See retryCount above. This attribute stops counting at its maximum value.

This attribute is the route selection's reasonForNoRoute and provides a brief reason for which a route was not selected. The reasons are essentially self-explanatory. Perhaps two reasons for no route require some explanation. The reason unknownRemoteNodeName is issued when the remote node name is not in the topological database. The reason plcAttributesNotMet is issued when there is no network connectivity at a level specified by the PLC attributes. This reason is also issued when there is no physical connectivity between two end nodes. Enumeration: 'destinationNotSpecified': 2, 'attributesNotMet': 11, 'none': 0, 'attributeProfileProblem': 13, 'incorrectDestinationEndPoint': 5, 'sameNode': 8, 'unknownDestination': 7, 'routeCostTooMuch': 9, 'unknownSource': 6, 'manualPathIndexProblem': 14, 'unknownDestinationName': 3, 'destinationNameTooLong': 1, 'anError': 12, 'routesDelayTooLong': 10, 'incorrectDestination': 4.

This attribute reflects the last tear down reason for a connection (LCo). In many cases this displays the reason for a momentary service interruption. This attribute applies to the last path failure only. If a path is no longer up, this may give an indication to the reason that the path has failed. In many cases an alarm will also be generated with more specific information. The following is a brief description of the reasons: none - This path has no information for the teardown this is typical of a path provisioned with no remoteName that has not been up. normalShutDown - This path has gone down due to normal call termination. insufficientTxLcOrBandwidth - At present there is either no available bandwidth or logical channel numbers available on one or more of the trunks for this path in the transmit direction. insufficientRxLcOrBandwidth - At present there is either no available bandwidth or logical channel numbers available on one or more of the trunks for this path in the receive direction. trunkFailure- A trunk on the path has failed or has gone down due to a provisioning change of a critical attribute. trunkCardFailure- A trunk FP card has failed along the path. accessCardFailure- The FP on which the peer access service was running has failed. operatorForced- The path has terminated due to the operator locking a trunk along the path. lostLcnClash- The path has terminated because the PA's at both ends of an intermediate trunk have allocated the same LC to different calls. When this happens both calls must go down and then try to come up again a fraction of a second later (effectively ensuring that they will now be assigned different LC's). It is normal to get the odd clash especially when the PA's usedLC is approaching the PA's maxLC. networkCongestion - The path has failed due to control information being lost and not recoverable. trunkNotFound - Occurs on a manual path usually. Check for trunks not up or names provisioned incorrectly. farEndNotFound - The far end is not provisioned or is not up. Check remote Name. wrongModuleReached - This may occur on a manual path. Check provisioning for correct trunk and service names. For a normal path, the network Topology may be changing check remoteName. farEndBusy - The far end has been reached but it is busy. Check remoteName and remote end provisioning. callLoopedBack - This LCo is provisioned to call itself. Re- provision since this is invalid. unknownReason - The failure was not resolved. farEndNotReady - The remote end was reached but the connection was refused due to the remote end not being enabled. remoteNameMismatch - The remote end has alarmed and rejected this setup due to remoteName provisioning. serviceTypeMismatch - The remote Service Type does not match this service type. Check provisioning. reconnectFromFarEnd - The remote end re-established this connection. Check the remote end lastTearDownReason to determine the real reason. bumped - Another call bumped this path from a trunk to get bandwidth (or an LC) which it required to come up. This other path had a higher setupPriority than this path's holdingPriority hence it was allowed to steal the bandwidth (or LC) from this path. optimized - This call has been rerouted due to the optimization feature. The call is still active this just indicates why the path changed. trunkOrFarEndDidNotSupportMode - This call was unable to complete because a mode required by the service was not supported by one of the trunks the route went through or by the far end service it connected to. Currently the only mode that this applies to is the map/mux mode on TRUNK PA ATM component. Map mode was required by the application (CES/FrAtm etc.) but was not available on the TRUNK PA ATM component through which the call was routed or the far end CES/FrAtm component did not specify the same mode. Enumeration: 'insufficientRxLcOrBandwidth': 3, 'lostLcnClash': 7, 'accessCardFailure': 20, 'networkCongestion': 8, 'farEndBusy': 12, 'farEndNotReady': 15, 'callLoopedBack': 13, 'unknownReason': 14, 'trunkCardFailure': 5, 'insufficientTxLcOrBandwidth': 2, 'overrideRemoteName': 22, 'serviceTypeMismatch': 17, 'remoteNameMismatch': 16, 'wrongModuleReached': 11, 'trunkNotFound': 9, 'trunkOrFarEndDidNotSupportMode': 23, 'reconnectFromFarEnd': 18, 'farEndNotFound': 10, 'optimized': 21, 'operatorForced': 6, 'bumped': 19, 'none': 0, 'trunkFailure': 4, 'normalShutDown': 1.

This attribute displays whether the application is set to tolerate momentary interruption of a path while a new path is selected. If disconnectConnection is displayed, the application is informed as soon as possible about a failure by disconnection. If the attribute displays reRoutePath, the path may attempt an immediate reroute, provided the failure is a recoverable failure. If rerouting fails the application is informed of the failure. With this option set to reRoutePath the LCo may wait up to 30 seconds before informing the service of complete disconnection in order to allow both ends to attempt to reconnect. Note that if PLC components are different at both ends only the calling end is allowed to reconnect. All pathTypes respect this attribute. Also on a manualPath with both ends provisioned with independent paths (at least with respect to the failure) this option will have the desired effect that the path is rerouted without complete disconnection at both ends Enumeration: 'reRoutePath': 1, 'disconnectConnection': 0.

This attribute specifies when bumping will occur during route selection process. Bumping may occur when necessary or always. It will be necessary for a connection to bump if there is not enough resources for the connection to be established and these resources are occupied by a connection whose setupPriority is lower (numerically higher) than the connection's setupPriority. A connection may also always bump in order to obtain the best route. Enumeration: 'bumpWhenNecessary': 0, 'bumpToObtainBestRoute': 1.

This attribute is used to specify whether this connection should attempt to optimize its path when requested by the routing PORS component. Every path is as optimal as it can be when it is established, but as network traffic patterns and configurations change this path may no longer be as optimal as it could be. The PORS connection manager on a module requests circuits to optimize at the optimization interval. Enumeration: 'disabled': 0, 'enabled': 1.

This is the time stamp when the current path was established or reestablished.

This group contains the operational statistics attributes for the path oriented LCo.

An entry in the mscAal1CesLCoStatsTable.

This attribute counts the number of packets transmitted to the network over this Logical Connection.

This attribute counts the number of bytes sent to the network over this Logical Connection.

This attribute counts the number of packets received from the remote LCo via the network.

This attribute counts the number of bytes received from the remote LCo via the network.

This attribute contains the trunk component names over which the path has been instantiated and the remote end point name terminating the path.

An entry in the mscAal1CesLCoPathTable.

This variable represents both the value and the index for the mscAal1CesLCoPathTable.

This entry controls the addition and deletion of mscAal1CesAtmCon components.

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

This variable is used as the basis for SNMP naming of mscAal1CesAtmCon 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 mscAal1CesAtmCon tables.

This variable represents the index for the mscAal1CesAtmCon tables.

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

An entry in the mscAal1CesAtmConOperTable.

This attribute shows the component name of the AtmIf Vcc Ep or AtmCon component to which this switched connection is established.

This group contains the attribute for a component's Customer Identifier (CID). Refer to the attribute description for a detailed explanation of CIDs.

An entry in the mscAal1CesCidDataTable.

This attribute holds the Customer Identifier (CID). Every component has a CID. If a component has a cid attribute, the component's CID is the provisioned value of that attribute; otherwise the component inherits the CID of its parent. The top- level component has a CID of 0. Every operator session also has a CID, which is the CID provisioned for the operator's user ID. An operator will see only the stream data for components having a matching CID. Also, the operator will be allowed to issue commands for only those components which have a matching CID. An operator CID of 0 is used to identify the Network Manager (referred to as 'NetMan' in DPN). This CID matches the CID of any component. Values 1 to 8191 inclusive (equivalent to 'basic CIDs' in DPN) may be assigned to specific customers.

This group contains basic provisioning data for the AAL1 Circuit Emulation Service.

An entry in the mscAal1CesProvTable.

This attribute specifies the service type for the CES. In an unstructured service, the entire data stream at the service interface (including any framing bits which may be present) is passed across the network transparently. The unstructured service uses the Unstructured Data Transfer (UDT) mode of AAL1. In a structured service, an Nx64kbit/s fraction of the data stream at the service interface is passed across the network. Two modes of structured service are supported: basicStructured and casStructured. In a casStructured service, the Channel Associated Signalling (CAS) bits are carried in a separate data structure from the Nx64 payload; in a basicStructured service they are not. The structured service uses the Structured Data Transfer (SDT) mode as defined in ITU-T Recommendation I.363.1. The serviceType attributes at both ends of a connection must be the same. Enumeration: 'unstructured': 0, 'casStructured': 2, 'basicStructured': 1.

On 4pDS1Aal1 and 4pE1Aal1 cards, this attribute specifies the size of the AAL1 receive segment reassembly buffer in bytes. On initialization the buffer is filled to a level determined by cellDelayVariationTolerance. Thereafter the buffer is emptied as TDM frames are transmitted, and is filled as ATM cells are received. If the buffer overflows, sufficient data is discarded to bring the level down to that set after initialization. The cause of a buffer overflow may be one or a combination of any of the following: cell- arrival-jitter, initialization with delayed ATM cells, or TDM clock difference or wander. On 4pDS1Aal1 and 4pE1Aal1 cards, if this attribute is autoConfigure, the buffer size applied is equivalent to two times cellDelayVariationTolerance. A provisioned numeric value of bufferSize must be higher than the equivalent cellDelayVariationTolerance, plus an allowance of one ATM Cell for the quantization of data in cells, and an allowance, if applicable, for the ATM overheads of structured CES. On MSA cards this attribute's value must be autoConfigure, to acknowledge that maximumBufferDelay is provisioned instead of this attribute. Setting this attribute too low allows traffic with normal CDV to cause unnecessary loss of data on the service interface. Setting this attribute too high permits the buffer to introduce an unnecessarily high propagation delay. VALUES ( 0 = autoConfigure )

This attribute specifies the cell loss integration period. This period defines the interval of time (in milliseconds) for which a loss of cells condition must persist before a buffer underflow alarm is raised. A loss of cells condition occurs when the flow of cells to the AAL1 reassembly buffer stops, causing a buffer underflow or starvation condition. The operational attribute cellLossStatus will be set to loss when the buffer underflow alarm is raised, and noLoss when it is cleared.

This attribute identifies the instance of Chan to which an instance of Aal1Ces is linked.

A significant source of delay in a structured service is the amount of time it takes to collect enough data to fill a cell. This period of time can be reduced by sending cells that are only partially filled with data (idlePattern octets are added to the ATM payload beyond the partial fill level). This attribute specifies the number of payload octets to fill with data. It is applicable to structured services only, and must be set to 47 for unstructured services. On a given AAL1 Function Processor, the maximum cell rate that can be sustained is dependent upon the combined bandwidths of the provisioned services, and (for structured services) the levels of partialFill. The smaller the partialFill level, the greater the cell rate and hence the fewer the services that can be sustained at that fill level.

This attribute controls the suppression of idle cells. An idle cell is one in which the bytes of the ATM payload (up to the partialFill level) match the idlePattern. If idleSuppression is off, idle cells are not suppressed. If idleSuppression is on, at least 75% of cells are suppressed under idle conditions. The strategy is as follows: the first idle cell after a sequence of non- idle cells is always sent; those that follow are suppressed. Note, however, that at least one cell in eight is always sent (to allow the receive end to regenerate the suppressed cells) and more often than not, two cells are sent (the cell containing the AAL1 pointer, which will almost always fail to match, and the one after that). Enumeration: 'on': 1, 'off': 0.

This attribute specifies the pattern which the bytes of an ATM payload, up to the partialFill level, must match in order for the cell to be classified as idle. Payload bytes beyond the partialFill level are not checked. The suppression of idle cells is controlled by the attribute idleSuppression. If idleSuppression is on, at least 75% of cells are suppressed under idle conditions.

This attribute specifies the cell loss recovery period. This period defines the interval of time (in seconds) for which a loss of cells condition must desist before the buffer underflow alarm is cleared. The operational attribute cellLossStatus will be set to noLoss when the buffer underflow alarm is cleared.

This attribute specifies the pattern which is played out onto the service interface to maintain bit integrity when data is unavailable from the ATM network. For an unstructured service (serviceType is set to unstructured), dummyDataByte must be set to FF.

This attribute specifies the maximum delay that a Cell Delay Variation buffer is permitted to add to the egress stream. The delay in the buffer is modified in response to variation in the egress cell stream. At the point that the delay would be modified in excess of the maximum, sufficient data is discarded that the delay returns to cellDelayVariationTolerance. Setting this attribute too low allows traffic with normal CDV to cause unnecessary loss of data on the service interface. Setting this attribute too high permits the buffer to introduce an unnecessarily high propagation delay. If this attribute is autoConfigure, the maximum delay tolerated in the buffer is two times cellDelayVariationTolerance. On MSA cards, 'best-effort' applies on a channel with high cellDelayVariationTolerance and low ATM bandwidth. The value applied is the same as the range limit on provisioned maximumBufferDelay on that channel. On MSA cards this attribute's value is rounded up to the nearest multiple of 0.125ms when applied to the buffer. The range is nominally 0.12..63.62ms, but the upper limit may be reduced by up to 6ms one a channel with high cellDelayVariationTolerance and low ATM bandwidth. On 4pDS1Aal1 and 4pE1Aal1 cards this attribute's value is rounded up to the nearest multiple of 1ms when applied to the buffer. The upper limit is roughly inverse- proportional to the ATM bandwidth of the channel. VALUES ( 0 = autoConfigure )

This attribute specifies the maximum time that a cell may arrive late, compared to a nominal time established at buffer initialization, without producing errors on the service interface. The nominal time of a cell's arrival is predicted according to the time interval required to transmit a cell's worth of data on the service interface. This attribute's value is the delay that the Cell Delay Variation Tolerance buffer adds to the egress stream immediately after the buffer initializes. The buffer absorbs variation in the arrival time of cells from the network, so that a steady stream of data appears on the service interface. If the buffer underflows, due to a late cell, fill- in data is output on the service interface while the buffer re- initializes. When the buffer has re-initialized, normal data is output on the service interface and the delay in the buffer is restored to the value of this attribute. This attribute must have a value lower than a numeric value of maximumBufferDelay. The relationship between this attribute and bufferSize is described under that attribute. Setting this attribute too low allows traffic with normal CDV to cause unnecessary loss of data on the service interface. Setting this attribute too high imposes an unnecessarily high propagation delay on the egress stream. On MSA cards this attribute's provisionable range is 0.01..32ms and the value applied is rounded up to the nearest multiple of 0.125ms. On 4pDS1Aal1 and 4pE1Aal1 cards, this attribute's provisionable range is strongly dependent on the bandwidth of the channel, and the value applied is rounded up to the nearest whole number of milliseconds, then rounded down to the equivalent number of cells.

This group contains the three OSI State attributes and the six OSI Status attributes. The descriptions generically indicate what each 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 mscAal1CesStateTable.

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. The OSI Status attributes, if supported by the component, may provide more details, qualifying the state of the 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. The OSI Status attributes, if supported by the component, may provide more details, qualifying the state of the component. 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. The OSI Status attributes, if supported by the component, may provide more details, qualifying the state of the component. Enumeration: 'active': 1, 'idle': 0, 'busy': 2.

If supported by the component, this attribute indicates the OSI Availability status of the component. Note that, even though it is defined as a multi-valued set, at most one value is shown to the user. When no values are in the set, this indicates that either the attribute is not supported or that none of the status conditions described below are present. The value inTest indicates that the resource is undergoing a test procedure. If adminState is locked or shuttingDown, the normal users are precluded from using the resource and controlStatus is reservedForTest. Tests that do not exclude additional users can be present in any operational or administrative state but the reservedForTest condition should not be present. The value failed indicates that the component has an internal fault that prevents it from operating. The operationalState is disabled. The value dependency indicates that the component cannot operate because some other resource on which it depends is unavailable. The operationalState is disabled. The value powerOff indicates the resource requires power to be applied and it is not powered on. The operationalState is disabled. The value offLine indicates the resource requires a routine operation (either manual, automatic, or both) to be performed to place it on-line and make it available for use. The operationalState is disabled. The value offDuty indicates the resource is inactive in accordance with a predetermined time schedule. In the absence of other disabling conditions, the operationalState is enabled or disabled. The value degraded indicates the service provided by the component is degraded in some way, such as in speed or operating capacity. However, the resource remains available for service. The operationalState is enabled. The value notInstalled indicates the resource is not present. The operationalState is disabled. The value logFull is not used. Description of bits: inTest(0) failed(1) powerOff(2) offLine(3) offDuty(4) dependency(5) degraded(6) notInstalled(7) logFull(8)

If supported by the component, this attribute indicates the OSI Procedural status of the component. Note that, even though it is defined as a multi-valued set, at most one value is shown to the user. When no values are in the set, this indicates that either the attribute is not supported or that none of the status conditions described below are present. The value initializationRequired indicates (for a resource which doesn't initialize autonomously) that initialization is required before it can perform its normal functions, and this procedure has not been initiated. The operationalState is disabled. The value notInitialized indicates (for a resource which does initialize autonomously) that initialization is required before it can perform its normal functions, and this procedure has not been initiated. The operationalState may be enabled or disabled. The value initializing indicates that initialization has been initiated but is not yet complete. The operationalState may be enabled or disabled. The value reporting indicates the resource has completed some processing operation and is notifying the results. The operationalState is enabled. The value terminating indicates the component is in a termination phase. If the resource doesn't reinitialize autonomously, operationalState is disabled; otherwise it is enabled or disabled. Description of bits: initializationRequired(0) notInitialized(1) initializing(2) reporting(3) terminating(4)

If supported by the component, this attribute indicates the OSI Control status of the component. Note that, even though it is defined as a multi-valued set, at most one value is shown to the user. When no values are in the set, this indicates that either the attribute is not supported or that none of the status conditions described below are present. The value subjectToTest indicates the resource is available but tests may be conducted simultaneously at unpredictable times, which may cause it to exhibit unusual characteristics. The value partOfServicesLocked indicates that part of the service is restricted from users of a resource. The adminState is unlocked. The value reservedForTest indicates that the component is administratively unavailable because it is undergoing a test procedure. The adminState is locked. The value suspended indicates that the service has been administratively suspended. Description of bits: subjectToTest(0) partOfServicesLocked(1) reservedForTest(2) suspended(3)

If supported by the component, this attribute indicates the OSI Alarm status of the component. Note that, even though it is defined as a multi-valued set, at most one value is shown to the user. When no values are in the set, this indicates that either the attribute is not supported or that none of the status conditions described below are present. The value underRepair indicates the component is currently being repaired. The operationalState is enabled or disabled. The value critical indicates one or more critical alarms are outstanding against the component. Other, less severe, alarms may also be outstanding. The operationalState is enabled or disabled. The value major indicates one or more major alarms are outstanding against the component. Other, less severe, alarms may also be outstanding. The operationalState is enabled or disabled. The value minor indicates one or more minor alarms are outstanding against the component. Other, less severe, alarms may also be outstanding. The operationalState is enabled or disabled. The value alarmOutstanding generically indicates that an alarm of some severity is outstanding against the component. Description of bits: underRepair(0) critical(1) major(2) minor(3) alarmOutstanding(4)

If supported by the component, this attribute indicates the OSI Standby status of the component. The value notSet indicates that either the attribute is not supported or that none of the status conditions described below are present. Note that this is a non-standard value, used because the original specification indicated this attribute was set-valued and thus, did not provide a value to indicate that none of the other three are applicable. The value hotStandby indicates that the resource is not providing service but will be immediately able to take over the role of the resource to be backed up, without initialization activity, and containing the same information as the resource to be backed up. The value coldStandby indicates the resource is a backup for another resource but will not be immediately able to take over the role of the backed up resource and will require some initialization activity. The value providingService indicates that this component, as a backup resource, is currently backing up another resource. Enumeration: 'notSet': 15, 'coldStandby': 1, 'hotStandby': 0, 'providingService': 2.

This attribute indicates the OSI Unknown status of the component. The value false indicates that all of the other OSI State and Status attribute values can be considered accurate. The value true indicates that the actual state of the component is not known for sure. Enumeration: 'true': 1, 'false': 0.

This group contains status information about the AAL1 Circuit Emulation Service.

An entry in the mscAal1CesOperTable.

This attribute is set to loss when a buffer underflow alarm is raised (see cellLossIntegrationPeriod), and noLoss when it is clear. Enumeration: 'loss': 1, 'noLoss': 0.

This attribute is set to loss when an AAL1 layer alarm is raised, and noLoss when it is clear. Enumeration: 'loss': 1, 'noLoss': 0.

This attribute indicates whether a service is non-operational because of a problem with the service interface side of the service (in which case, it is set to channelNotReady) or because of a problem with the ATM side of the service (in which case, it is set to atmNotConfigured or atmNotReady). When this attribute is set to channelNotReady, it is an indication that the corresponding Chan component (as defined by the attribute interfaceName) or the Chan component's parent port component (Lp/n Ds1/m or Lp/n E1/m) is locked. When this attribute is set to atmNotConfigured, it is an indication that no sub-component has been provisioned, and thus no ATM connection has been configured for the service. When this attribute is set to atmNotReady, it is an indication that the ATM connection with which the service is associated (as defined by a sub-component) has been lost or that it is currently unable to carry CES data. This attribute is set to connected when a service is operational (that is, the OSI attribute operationalState is enabled.) Enumeration: 'atmNotReady': 2, 'connected': 0, 'atmNotConfigured': 3, 'channelNotReady': 1.

This group contains statistical data for an AAL1 Circuit Emulation Service.

An entry in the mscAal1CesStatsTable.

This attribute counts the total number of cells transmitted to the backplane (ingress direction). This includes cells containing CBR data, trunk conditioning cells (structured services), and unframed AIS cells (unstructured services). The counter wraps when the maximum value is exceeded.

This attribute counts the total number of cells received from the backplane (egress direction). This includes CBR user data cells, cells with AAL1 header errors (correctable and non-correctable) and cells with AAL1 sequencing errors. The counter wraps when the maximum value is exceeded.

This attribute counts the number of cells declared as never received by the AAL1 protocol layer. The counter wraps when the maximum value is exceeded.

This attribute counts the number of times the AAL1 reassembly buffer underflows. In the case of a continuous buffer starvation, a single buffer underflow event will be counted. The counter wraps when the maximum value is exceeded.

This attribute counts the number of times the AAL1 reassembly buffer overflows. Buffer overflows occur when AAL1 cells arrive at a rate above that which is expected. Occurrences of this condition may be reduced by increasing the value of the attribute bufferSize or maximumBufferDelay. The buffer overflow counter wraps when the maximum value is exceeded.

This attribute counts the number of received cells whose payload has been played out to the service interface. The counter wraps when the maximum value is exceeded.

This attribute counts the number of cells received with AAL1 header errors. The counter wraps when the maximum value is exceeded.

This attribute counts the number of times that the AAL1 reassembly unit found an SDT pointer where it was not expected to be, and as a result had to reacquire it. Errors of this kind can occur because of problems at the far end. This attribute is meaningful for structured services only, and will be 0 for unstructured services. This counter wraps when the maximum value is exceeded.

This attribute counts the number of times that the AAL1 reassembly unit detects a parity check failure at the point where an SDT pointer is expected. Errors of this kind can occur because of problems at the far end. This attribute is meaningful for structured services only, and will be 0 for unstructured services. This counter wraps when the maximum value is exceeded.

This attribute counts the number of times that the sequence number of an incoming AAL1 Type 1 SAR-PDU gets out of synchronisation, as defined by ITU-T Recommendation I.363.1. This counter wraps when the maximum value is exceeded.

This attribute counts the number of AAL1 sequence violations which the AAL convergence sublayer interprets as misinserted cells, as defined by ITU-T I.363.1. This counter wraps when the maximum value is exceeded.

This entry controls the addition and deletion of mscMmTx components.

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

This variable is used as the basis for SNMP naming of mscMmTx 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 mscMmTx tables.

This variable represents the index for the mscMmTx tables.

This entry controls the addition and deletion of mscMmTxNap components.

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

This variable is used as the basis for SNMP naming of mscMmTxNap 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 mscMmTxNap tables.

This variable represents the index for the mscMmTxNap tables.

This group contains the provisioning data for the NailedUpAdaptationPoint component.

An entry in the mscMmTxNapProvTable.

This attribute specifies the identity of the component to which the NailedUpAdaptationPoint is linked. This is an AtmIf Vcc NailedUpEndPoint or an AtmIf Vpt Vcc NailedUpEndPoint (the AAL1 cells are transported off the switch over an ATM UNI, where they are routed to the appropriate AAL1 entity at the other end by the ATM bearer service).

This entry controls the addition and deletion of mscMmTxAtmCon components.

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

This variable is used as the basis for SNMP naming of mscMmTxAtmCon 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 mscMmTxAtmCon tables.

This variable represents the index for the mscMmTxAtmCon tables.

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

An entry in the mscMmTxAtmConOperTable.

This attribute shows the component name of the AtmIf Vcc Ep or AtmCon component to which this switched connection is established.

This group contains the attribute for a component's Customer Identifier (CID). Refer to the attribute description for a detailed explanation of CIDs.

An entry in the mscMmTxCidDataTable.

This attribute holds the Customer Identifier (CID). Every component has a CID. If a component has a cid attribute, the component's CID is the provisioned value of that attribute; otherwise the component inherits the CID of its parent. The top- level component has a CID of 0. Every operator session also has a CID, which is the CID provisioned for the operator's user ID. An operator will see only the stream data for components having a matching CID. Also, the operator will be allowed to issue commands for only those components which have a matching CID. An operator CID of 0 is used to identify the Network Manager (referred to as 'NetMan' in DPN). This CID matches the CID of any component. Values 1 to 8191 inclusive (equivalent to 'basic CIDs' in DPN) may be assigned to specific customers.

This group contains basic provisioning data for the Maintenance Monitor Transmitter (MmTx). A MmTx represents a mono- directional AAL1 Circuit Emulation Service. AAL1 CES attributes in this group are essential information to the operator about the AAL1 CES service that must be matched in the Aal1Ces component that receives the monitored stream. The check escape checks that only one instance of a MaintenanceMonitorTx is linked to any one Lp.

An entry in the mscMmTxProvTable.

This attribute specifies the instance of a hardware component to which an instance of this component is linked. Only Lp components may be linked

monitoredDirection specifies the direction of the monitored traffic. The default and only value is ingress. Enumeration: 'ingress': 0.

serviceType specifies the service type of the CES. The serviceType attribute in the receiving Aal1Ces component must have the same value as this attribute. The default and only value is basicStructured. Enumeration: 'basicStructured': 1.

partialFill specifies the number of octets that are carried in an ATM cell by the AAL1 CES service. A full cell contains 47 octets. The partialFill attribute in the receiving Aal1Ces component must have the same value as this attribute. The default and only value is 47. DESCRIPTION

idleSuppression controls the suppression of idle cells. An idle cell is one in which the bytes of the ATM payload (up to the partialFill level) match the idlePattern. If idleSuppression is off, idle cells are not suppressed. If idleSuppression is on, at least 75% of cells are suppressed under idle conditions. The idleSuppression attribute in the receiving Aal1Ces component must have the same value as this attribute The default and only value is off. Enumeration: 'off': 0.

This group contains the three OSI State attributes and the six OSI Status attributes. The descriptions generically indicate what each 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 mscMmTxStateTable.

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. The OSI Status attributes, if supported by the component, may provide more details, qualifying the state of the 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. The OSI Status attributes, if supported by the component, may provide more details, qualifying the state of the component. 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. The OSI Status attributes, if supported by the component, may provide more details, qualifying the state of the component. Enumeration: 'active': 1, 'idle': 0, 'busy': 2.

If supported by the component, this attribute indicates the OSI Availability status of the component. Note that, even though it is defined as a multi-valued set, at most one value is shown to the user. When no values are in the set, this indicates that either the attribute is not supported or that none of the status conditions described below are present. The value inTest indicates that the resource is undergoing a test procedure. If adminState is locked or shuttingDown, the normal users are precluded from using the resource and controlStatus is reservedForTest. Tests that do not exclude additional users can be present in any operational or administrative state but the reservedForTest condition should not be present. The value failed indicates that the component has an internal fault that prevents it from operating. The operationalState is disabled. The value dependency indicates that the component cannot operate because some other resource on which it depends is unavailable. The operationalState is disabled. The value powerOff indicates the resource requires power to be applied and it is not powered on. The operationalState is disabled. The value offLine indicates the resource requires a routine operation (either manual, automatic, or both) to be performed to place it on-line and make it available for use. The operationalState is disabled. The value offDuty indicates the resource is inactive in accordance with a predetermined time schedule. In the absence of other disabling conditions, the operationalState is enabled or disabled. The value degraded indicates the service provided by the component is degraded in some way, such as in speed or operating capacity. However, the resource remains available for service. The operationalState is enabled. The value notInstalled indicates the resource is not present. The operationalState is disabled. The value logFull is not used. Description of bits: inTest(0) failed(1) powerOff(2) offLine(3) offDuty(4) dependency(5) degraded(6) notInstalled(7) logFull(8)

If supported by the component, this attribute indicates the OSI Procedural status of the component. Note that, even though it is defined as a multi-valued set, at most one value is shown to the user. When no values are in the set, this indicates that either the attribute is not supported or that none of the status conditions described below are present. The value initializationRequired indicates (for a resource which doesn't initialize autonomously) that initialization is required before it can perform its normal functions, and this procedure has not been initiated. The operationalState is disabled. The value notInitialized indicates (for a resource which does initialize autonomously) that initialization is required before it can perform its normal functions, and this procedure has not been initiated. The operationalState may be enabled or disabled. The value initializing indicates that initialization has been initiated but is not yet complete. The operationalState may be enabled or disabled. The value reporting indicates the resource has completed some processing operation and is notifying the results. The operationalState is enabled. The value terminating indicates the component is in a termination phase. If the resource doesn't reinitialize autonomously, operationalState is disabled; otherwise it is enabled or disabled. Description of bits: initializationRequired(0) notInitialized(1) initializing(2) reporting(3) terminating(4)

If supported by the component, this attribute indicates the OSI Control status of the component. Note that, even though it is defined as a multi-valued set, at most one value is shown to the user. When no values are in the set, this indicates that either the attribute is not supported or that none of the status conditions described below are present. The value subjectToTest indicates the resource is available but tests may be conducted simultaneously at unpredictable times, which may cause it to exhibit unusual characteristics. The value partOfServicesLocked indicates that part of the service is restricted from users of a resource. The adminState is unlocked. The value reservedForTest indicates that the component is administratively unavailable because it is undergoing a test procedure. The adminState is locked. The value suspended indicates that the service has been administratively suspended. Description of bits: subjectToTest(0) partOfServicesLocked(1) reservedForTest(2) suspended(3)

If supported by the component, this attribute indicates the OSI Alarm status of the component. Note that, even though it is defined as a multi-valued set, at most one value is shown to the user. When no values are in the set, this indicates that either the attribute is not supported or that none of the status conditions described below are present. The value underRepair indicates the component is currently being repaired. The operationalState is enabled or disabled. The value critical indicates one or more critical alarms are outstanding against the component. Other, less severe, alarms may also be outstanding. The operationalState is enabled or disabled. The value major indicates one or more major alarms are outstanding against the component. Other, less severe, alarms may also be outstanding. The operationalState is enabled or disabled. The value minor indicates one or more minor alarms are outstanding against the component. Other, less severe, alarms may also be outstanding. The operationalState is enabled or disabled. The value alarmOutstanding generically indicates that an alarm of some severity is outstanding against the component. Description of bits: underRepair(0) critical(1) major(2) minor(3) alarmOutstanding(4)

If supported by the component, this attribute indicates the OSI Standby status of the component. The value notSet indicates that either the attribute is not supported or that none of the status conditions described below are present. Note that this is a non-standard value, used because the original specification indicated this attribute was set-valued and thus, did not provide a value to indicate that none of the other three are applicable. The value hotStandby indicates that the resource is not providing service but will be immediately able to take over the role of the resource to be backed up, without initialization activity, and containing the same information as the resource to be backed up. The value coldStandby indicates the resource is a backup for another resource but will not be immediately able to take over the role of the backed up resource and will require some initialization activity. The value providingService indicates that this component, as a backup resource, is currently backing up another resource. Enumeration: 'notSet': 15, 'coldStandby': 1, 'hotStandby': 0, 'providingService': 2.

This attribute indicates the OSI Unknown status of the component. The value false indicates that all of the other OSI State and Status attribute values can be considered accurate. The value true indicates that the actual state of the component is not known for sure. Enumeration: 'true': 1, 'false': 0.

This group contains status information about the AAL1 Circuit Emulation Service and the related ATM service, and the means to specify the Channel to be monitor.

An entry in the mscMmTxOperTable.

This attribute indicates whether a service is non-operational because of a problem with the service interface side of the service (in which case, it is set to channelNotReady) or because of a problem with the ATM side of the service (in which case, it is set to atmNotConfigured or atmNotReady). When this attribute is set to channelNotReady, it is an indication that the corresponding Chan component (as defined by the attribute interfaceName) or the Chan component's parent port component (Lp/n Ds1/m or Lp/n E1/m) is locked. When this attribute is set to atmNotConfigured, it is an indication that no sub-component has been provisioned, and thus no ATM connection has been configured for the service. When this attribute is set to atmNotReady, it is an indication that the ATM connection with which the service is associated (as defined by a sub-component) has been lost or that it is currently unable to carry CES data. When this attribute is set to channelNotSpecified, it is an indication that the chanToMonitor attribute is not set to a valid channel. This attribute is set to connected when a service is operational (that is, the OSI attribute operationalState is enabled.) Enumeration: 'channelNotSpecified': 4, 'atmNotReady': 2, 'connected': 0, 'atmNotConfigured': 3, 'channelNotReady': 1.

chanToMonitor specifies the LP, port (E1 or DS1), and channel to monitor. The LP must be the same LP specified in the provisionable attribute linkToLogicalProcessor. This attribute's value is of the form Lp/x E1/y Chan/z or Lp/x DS1/y Chan/z.