Nortel-Magellan-Passport-DprsMcsEpMIB: View SNMP OID List / Download MIB

This entry controls the addition and deletion of mcsMgrDprsMcsEpG components.

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

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

This variable represents the index for the mcsMgrDprsMcsEpG tables.

This entry controls the addition and deletion of mcsMgrDprsMcsEpGAddr components.

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

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

This variable represents the index for the mcsMgrDprsMcsEpGAddr tables.

This group contains the provisionable attributes of the Address component.

An entry in the mcsMgrDprsMcsEpGAddrProvTable.

This attribute specifies the NSAP address of the McsMgr at the destination module. This address is used by the EndPoints provisioned under this DprsMcsEpG to establish a Dprs MCS Switched Path.

This attribute specifies additional textual information to be added by the network operator. Typical use of this attribute is to specify the destination module name.

This entry controls the addition and deletion of mcsMgrDprsMcsEpGEp components.

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

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

This variable represents the index for the mcsMgrDprsMcsEpGEp tables.

This entry controls the addition and deletion of mcsMgrDprsMcsEpGEpEpD components.

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

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

This variable represents the index for the mcsMgrDprsMcsEpGEpEpD tables.

This group contains the parameters used to establish the transport connection for this Ep.

An entry in the mcsMgrDprsMcsEpGEpEpDProvTable.

This attribute specifies the bandwidth at which the transport connection agrees to transfer information. A conservative value would be the sum of the committed information rates (CIRs) of all individual Frame Relay DLCIs multiplexed on the transport connection. For ATM connections, the value is converted to an equivalent Peak Cell Rate (PCR01) for all cells with Cell Loss Priority (CLP), CLP = 0 and CLP = 1. Note that the conversion to an equivalent cell rate for ATM connections may result in some wasted bandwidth depending on the average frame size to cell ratio.

This attribute specifies the transfer priority used to establish the transport connection. It references the ModuleData Frs AtmNet Tpm to determine the ATM service category to be used by the transport connection. This attribute is used by the Ep solely for the purpose of determining the service category that should be used to establish the transport connection.

This attribute specifies the preference of routing system to be used to set up the transport connection. If a value of atmOnly is specified, attempts to set up the transport connection will be made using only the ATM routing system's network facilities. If a value of porsOnly is specified, attempts to set up the transport connection will be made using only PORS network facilities. Enumeration: 'atmOnly': 1, 'porsOnly': 3.

This attribute specifies the PORS profile to be used for the transport connection when it is set up using PORS. This attribute is ignored if the transportConnectionPreference is atmOnly.

This attribute specifies the PORS manual path to be used for the transport connection when it is set up using PORS. The manual path that this attribute is linked to specifies the sequence of Trunks that will be used when PORS chooses and instantiates the route. This attribute is ignored if the transportConnectionPreference is atmOnly.

This attribute specifies the Frame Relay transfer priorities that are supported through the transport connection. It is used to determine which EndPoint within a DprsMcsEndPointGroup is to multiplex a particular Frame Relay DLCI. A particular transfer priority can be specified on at most one EndPoint within a DprsMcsEndPointGroup. Description of bits: n0(0) n1(1) n2(2) n3(3) n4(4) n5(5) n6(6) n7(7) n8(8) n9(9) n10(10) n11(11) n12(12) n13(13) n14(14) n15(15)

This entry controls the addition and deletion of mcsMgrDprsMcsEpGEpAtmCon components.

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

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

This variable represents the index for the mcsMgrDprsMcsEpGEpAtmCon tables.

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

An entry in the mcsMgrDprsMcsEpGEpAtmConOperTable.

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

This entry controls the addition and deletion of mcsMgrDprsMcsEpGEpLCo components.

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

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

This variable represents the index for the mcsMgrDprsMcsEpGEpLCo tables.

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

An entry in the mcsMgrDprsMcsEpGEpLCoPathDataTable.

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

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

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

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

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 the operational attributes of the EndPoint component.

An entry in the mcsMgrDprsMcsEpGEpOperTable.

This attribute indicates the most recent clear cause for the transport connection. This indicates the causes provided by the network. A value of zero indicates that the transport connection has never been cleared. A value of 1000 indicates that the network has not provided a clear cause for the transport connection clearing. Section 5.4.5.15 of the ATMF UNI 3.1 specification lists the clear causes provided by the network.

This attribute indicates the type of the end point. If the value is originating, this Ep is provisioned and is responsible for initiating the SPVC call to set up the PORS or ATM connection. If the value is terminating, this Ep is created dynamically by the McsMgr at the destination node when it receives a call setup request. Enumeration: 'originating': 0, 'terminating': 1.

This attribute indicates the Frame Relay transfer priorities supported by the transport connection. Description of bits: n0(0) n1(1) n2(2) n3(3) n4(4) n5(5) n6(6) n7(7) n8(8) n9(9) n10(10) n11(11) n12(12) n13(13) n14(14) n15(15)

This attribute indicates the transfer priority used to establish the transport connection.

This attribute indicates the ATM service category of the transport connection. Enumeration: 'cbr': 1, 'rtVbr': 2, 'nrtVbr': 3, 'ubr': 0.

This attribute indicates the bandwidth at which the transport connection agrees to transfer information.

This attribute indicates the component name of the remote Ep, learned from the remote end. For example: 'EM/NODEY2D0 McsMgr DprsMcsEpG/1 Ep/1'. The value will be a null string if the transport connection is down.

This attribute indicates the routing identifier (RID) associated with the Passport node on which the remote Ep resides. The remote RID is learned from the remote Ep. The value is valid when the transport connection is up and zero otherwise.

This attribute indicates the module identifier (MID) associated with the Passport node on which the remote Ep resides. The remote MID is learned from the remote Ep. The value is valid when the transport connection is up and zero otherwise.

This attribute indicates the diagnostic code of the most recently cleared transport connection. This indicates the diagnostic code (associated with the lastTransportConnectionClearCause) provided by the network. A string containing only a 0 or 00 (zero) indicates that the network has not provided a diagnostic code for the most recently cleared transport connection. Section 5.4.5.15 of the ATMF UNI 3.1 specification lists the diagnostic codes that can be provided by the network.

This group contains statistics of traffic received on the Dprs MCS Switched Path.

An entry in the mcsMgrDprsMcsEpGEpStatsTable.

This attribute counts the number of attempts made to set up the transport connection. The counter wraps around to zero when the maximum value is reached.

This attribute counts errored packets received on the Dprs MCS Switched Path that have been discarded. The counter wraps around to zero when the maximum value is reached.

This attribute counts the packets received on the Dprs MCS Switched Path for each discard priority. This attribute is a vector with four entries. Each vector entry is a counter indexed by one of four discard priorities, namely, discard priority 0(dp0), discard priority 1(dp1), discard priority 2(dp2) or discard priority 3(dp3). Each entry (counter) wraps around to zero when the maximum value is reached.

An entry in the mcsMgrDprsMcsEpGEpPktFromMcsTable.

This variable represents the mcsMgrDprsMcsEpGEpPktFromMcsTable specific index for the mcsMgrDprsMcsEpGEpPktFromMcsTable. Enumeration: 'discardPriority2': 2, 'discardPriority3': 3, 'discardPriority0': 0, 'discardPriority1': 1.

This variable represents an individual value for the mcsMgrDprsMcsEpGEpPktFromMcsTable.

This attribute counts the octets received on the Dprs MCS Switched Path for each discard priority. This attribute is a vector with four entries. Each vector entry is a counter indexed by one of four discard priorities, namely, discard priority 0(dp0), discard priority 1(dp1), discard priority 2(dp2) or discard priority 3(dp3). Each entry (counter) wraps around to zero when the maximum value is reached.

An entry in the mcsMgrDprsMcsEpGEpOctetsFromMcsTable.

This variable represents the mcsMgrDprsMcsEpGEpOctetsFromMcsTable specific index for the mcsMgrDprsMcsEpGEpOctetsFromMcsTable. Enumeration: 'discardPriority2': 2, 'discardPriority3': 3, 'discardPriority0': 0, 'discardPriority1': 1.

This variable represents an individual value for the mcsMgrDprsMcsEpGEpOctetsFromMcsTable.

This attribute counts packets received on the Dprs MCS Switched Path for each discard priority that have been discarded at the transport card due to free list congestion at the access card. This attribute is a vector with four entries. Each vector entry is a counter indexed by one of four discard priorities, namely, discard priority 0(dp0), discard priority 1(dp1), discard priority 2(dp2) or discard priority 3(dp3). Each entry (counter) wraps around to zero when the maximum value is reached.

An entry in the mcsMgrDprsMcsEpGEpPktDiscCongestedFromMcsTable.

This variable represents the mcsMgrDprsMcsEpGEpPktDiscCongestedFromMcsTable specific index for the mcsMgrDprsMcsEpGEpPktDiscCongestedFromMcsTable. Enumeration: 'discardPriority2': 2, 'discardPriority3': 3, 'discardPriority0': 0, 'discardPriority1': 1.

This variable represents an individual value for the mcsMgrDprsMcsEpGEpPktDiscCongestedFromMcsTable.

This group contains the operational attributes of the DprsMcsEpG component.

An entry in the mcsMgrDprsMcsEpGOperTable.

This attribute indicates the NSAP address of the McsMgr at the destination module to which all EndPoints of this group are connected.

For a provisioned DprsMcsEpG, this attribute indicates the name of the DprsMcsEpG that contains the dynamic Eps to the same destination. For a dynamic DprsMcsEpG, this attribute indicates the name of the DprsMcsEpG that contains the provisioned Eps to the same destination. A null component name indicates that there is no DprsMcsEpG associated with this group.