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

This entry controls the addition and deletion of btds components.

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

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

This variable represents the index for the btds tables.

This entry controls the addition and deletion of btdsFramer components.

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

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

This variable represents the index for the btdsFramer tables.

This group contains the base provisioning data for the Framer component. Application or hardware interface specific provisioning data is contained in other provisionable Framer groups.

An entry in the btdsFramerProvTable.

This attribute contains a hardware component name. The attribute associates the application with a specific link. This defines the module processor on which Framer's parent component (as well as Framer itself) will run.

This group contains attributes defining the framing of data on the link interface or n*64kbps channel.

An entry in the btdsFramerChannelTable.

This attribute specifies the ingress frames suppressed by this Btds. If protocol is none, this Btds does not suppress any ingress frames. If protocol is hdlc, this Btds suppresses ingress frames where each byte is an identical non-inverted hdlc idle pattern, but only after two or more consecutive frames meet this description. If protocol is nrziHdlc, this Btds suppresses ingress frames where each byte is an identical NRZI encoded hdlc idle pattern, but only after two or more consecutive frames meet this description. If protocol is universal, this Btds suppresses ingress frames where each 16-bit word is identical, but only after a provisionable number of consecutive frames meet this description. The number of consecutive frames is determined by numOfIdleBytesToMonitor. Note that the number of idle bytes suppressed at the ingress side does not necessarily equal the number of idle bytes generated at the egress side. Enumeration: 'none': 0, 'nrziHdlc': 2, 'universal': 3, 'hdlc': 1.

This attribute specifies the number of consecutive repeated ingress 16-bit words this Btds must encounter before suppressing universal ingress idle frames. This attribute is only used if protocol is universal. numOfIdleBytesToMonitor should be larger than the largest frame size that can be sent into this Btds.

This attribute specifies how to fill a local egress frame when the remote Btds suppressed an ingress frame.

This attribute specifies the time slot alignment of this Btds. With time slot alignment, data sent out on a particular time slot to a link is received on the same time slot. A value of unaligned specifies the regular Btds application. A value of frameAligned enables frame aligned Btds. When framed aligned Btds is specified, only one channel may be provisioned since only one fraction of N x 64 kbit/s is presently available. timeSlotAlignment can not be set to frameAligned unless this Btds is running on a DS1V, E1V, 1pDS1V or 1pE1V card timeSlotAlignment must have the same value at both ends of a Btds. If timeSlotAlignment does not have the same value at both ends of a Btds, the Btds will be out of service. In this case, Btds serviceFailureReason is mismatchedTimeSlotAlignment. Enumeration: 'frameAligned': 1, 'unaligned': 0.

This attribute defines the amount of added output delay to compensate for cross network delay variations. Cross network delay variations is a function of the network topology. Setting this attribute will allow the Btds service to deal with cross network delay variations. This attribute provides for delay in addition to the elastic buffer. Total egress delay is approximately the insertedOutputDelay plus the elastic buffer. The elastic buffer is the packetization timex5 cells in the buffer. Packetization time per cell is calculated by taking the inverse of [linespeed (kbits/sec) x (byte/8bits) x (1/cellsize (bytes))]. This value is msec.The value for insertedOutputDelay should be increased if the frmUnderRuns is increasing and frmLostInNetwork is not increasing.

This attribute allows selection of larger BTDS cell sizes. Larger BTDS cell sizes improve efficiency but increase the minimum egress queue delay. If the associated channel is using less than 5 timeslots (320 kbits/sec), the default btdsCellSize will be used. Setting btdsCellSize to 84 is only allowed on DS1 and E1 FPs. Enumeration: 'n84': 1, 'n44': 0.

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

An entry in the btdsFramerStateTable.

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

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

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

This group contains the operational statistics data for a Framer component.

An entry in the btdsFramerStatsTable.

This attribute counts the number of frames received from the link interface by Framer. This count wraps to zero after reaching its maximum value.

This attribute counts the number of frames dropped at the interface due to the idle pattern being detected. This count wraps to zero after reaching its maximum value.

This attribute counts the number of frames transmitted to the link interface by Framer. This count wraps to zero after reaching its maximum value.

This attribute counts the number of frames received from the network with LRC errors. This count wraps to zero after reaching its maximum value.

This attribute counts the number of frames which the service knows it did not receive from the network although they were sent in to the network from the far end. This count wraps to zero after reaching its maximum value.

This attribute counts the number of times that a frame was needed but was not available because it had been delayed too long in the network. This error may occur repeatedly if the interface clocks at the two access points to the network are operating at different rates. This count wraps to zero after reaching its maximum value.

This attribute counts the number of frames which have been dumped because the local interface output queue grew too large. This can occur if the clock rate on the local interface is faster than the clock rate on the remote interface and there are no silence periods to absorb the difference. This count wraps to zero after reaching its maximum value.

This entry controls the addition and deletion of btdsPlc components.

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

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

This variable represents the index for the btdsPlc tables.

This group contains all provisionable attributes for a permanent logical connection. Note that all of the attributes are valid and provisionable on both ends of a connection. However with the exception of remoteName, all operational attributes are derived from the originating end provisioning, which may be either end unless remoteName is not provisioned on one end.

An entry in the btdsPlcProvTable.

This attribute is the PLC's remote end point's address in the format of a Passport component name The syntax of a component is: 'em/node type/instance'. End points are identified using a node name and a service name. As an example, the end point component name for the third voice service on node MoonBase is: 'EM/MoonBase VS/3'. If the remoteName is provisioned it must match the remote name of the other end or the connection will not be established even if the remote end is provisioned correctly. If no remoteName is provisioned then this LC will accept connections from any other remote LC and it will not originate calls. Connections establish faster and are unique if both ends are provisioned with the remoteName. These strings are case insensitive but the complete component name must be input.

This attribute gives the priority at which a path is established. Zero is the highest priority and four is the lowest. When PORS establishes a path through the network, it uses the setupPriority attribute to determine its potential for bumping established paths to acquire their bandwidth. The holdingPriority, a complementary attribute of this attribute, indicates the priority a path maintains once it is established. A new path can bump an existing path if the new path's setupPriority is higher (numerically less) than the existing path's holdingPriority.

This attribute gives the priority that a path holds once it is established. Zero(0) is the highest priority and four(4) is the lowest. A path's holdingPriority determines its likelihood of being bumped by a new path to acquire its bandwidth. The setupPriority, a complementary attribute, indicates the priority of a path at establishment time. A new path can bump an existing path if the new path's setupPriority is higher (numerically less) than the existing path's holdingPriority.

This attribute gives the bandwidth (in bits per second) reserved by a path on each of the trunks of its route. This attribute represents the bandwidth for traffic outgoing to the remote end point. This value should be chosen to achieve the amount of statistical bandwidth sharing that is desired by the network administration. This reservation is not enforced and is used to determine how many paths can be supported on a trunk. Both ends should be provisioned with the correct values allowing for the fact that Transmit at this end represents Receive at the remote end. Note that when the values do not correspond the originating end of the connection determines the value.

This attribute gives the bandwidth (in bits per second) reserved by a path on each of trunks of its route. This attribute represents the bandwidth for traffic incoming from the remote end point. This value should be chosen to achieve the amount of statistical bandwidth sharing that is desired by the network administration. This reservation is not enforced and is used to determine how many paths can be supported on a trunk. Both ends should be provisioned with the correct values allowing for the fact that transmit at this end represents receive at the remote end. Note that when the values do not correspond, the originating end of the connection determines the value.

This attribute indicates the type of traffic transmitted over the path. There are eight(8) 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(5) 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 attribute lists up to eight(8) types of trunk that can be used on the route. The terrestrial and satellite trunk types have been defined, leaving six(6) 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. Its value, a number from zero to seven, is chosen by 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 whether a route is selected on the basis of minimizing the cost or the delay. Each trunk has a cost and a delay metric associated with it. The cost of a selected route is the sum of the trunk cost metrics for all trunks included in the route. The delay of a selected route is the sum of the trunk delay metric for all trunks included in the route. Enumeration: 'delay': 1, 'cost': 0.

This attribute indicates an upper bound on the cost metric of a route, which is the sum of the cost metrics of all trunks on the route. The cost metric is the trunkCost attribute of the Trunk component. If for any trunk the trunkCost is larger than the maximumAcceptableCost, then that trunk is not considered during the route selection. While a shortest route is being selected, the route cost is being compared with the maximumAcceptableCost attribute, and this is done for any minimization criterion. No route is selected if the cost metric of the shortest route is larger than the maximumAcceptableCost.

This attribute indicates an upper bound on the delay of a route, which is the sum of the delay of all trunks on the route. It should be provisioned with a reasonable maximum acceptable delay for the end to end one way delay of a 512-byte packet. Remember, that the trunk during its staging measures a measuredRoundTripDelay. This delay is divided by two and truncated to an integer number of milliseconds to provide a one way delay which is used to populate the delay in this trunk object in the topological database. The value includes emission, propagation, and queuing delays. A 512-byte packet is used to perform the measurement. If for any trunk the half of the trunk's measuredRoundTripDelay is larger than the maximumAcceptableDelay, then that trunk is not considered during the route selection. While a shortest route is being selected, the route delay is being compared with the maximumAcceptableDelay attribute, and this is done for any minimization criterion. No route is selected if the delay metric of the shortest route is larger than the maximumAcceptableDelay.

This attribute indicates the urgency with which packets on the path are emitted by the trunks on the route. EmissionPriority of Zero(0) indicates the highest emission priority, while two (2) 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. 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 specifies if the path for this PLC is determined automatically or by static provisioning. The default (normal) is to automatically choose a route with Route Selection. Normal pathTypes require less provisioning and can dynamically handle path failures. 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 used to specify whether the application can tolerate momentary interruption of a path while a new path is selected. If disconnectConnection is chosen, the application is informed as soon as possible about a failure by disconnection. If the attribute is set to 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 controls when bumping occurs in the route selection process. A connection with higher (numerically less) setupPriority may bump a connection with lower (numerically higher) holdingPriority in order to acquire its bandwidth and be established. By default, bumping occurs only when it is necessary. That is, a connection will bump another connection only if there is no other way for the connection to be established. A connection may be set to always bump in order to find the best route it may have. 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 attribute is optional and specifies the sequence of trunks to be used as the route for the path, thus bypassing PORS' automatic route selection. If the path fails the validation, no other path can be selected1. This attribute should only be used in special cases since the route selection algorithm is able to find and maintain the best routes. A related path attribute, the pathType, determines if this route will be used as a manual or forced path type. As an example, the trunk component name for the third trunk on node MoonBase is 'EM/MoonBase Trk/3'. Note that only the first end of the trunk that the packet would encounter is provisioned. These strings are case insensitive but the complete component name must be input. Note 1: the trunk designation must be a 3-letter form, e.g., 'trk'. Note 2: only the outbound trunks component names are used to provision the manualPath. Note 3: It is recommended to have two independent routes specified for a manual path by specifying a different manualPath (non-symmetric) for each end. In this case, there is no way to select which route will be used (first up wins) but if one path is torn down due to a failure then the other manualPath may be used to reroute the path.

An entry in the btdsPlcMpathTable.

This variable represents the btdsPlcMpathTable specific index for the btdsPlcMpathTable.

This variable represents an individual value for the btdsPlcMpathTable.

This entry controls the addition and deletion of btdsLCo components.

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

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

This variable represents the index for the btdsLCo tables.

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

An entry in the btdsLCoPathDataTable.

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

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

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

This entry controls the addition and deletion of btdsDpnss1 components.

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

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

This variable represents the index for the btdsDpnss1 tables.

This group contains the provisionable attribute for the Dpnss1 component to handle DPNSS 1 messages.

An entry in the btdsDpnss1ProvTable.

This attribute contains the list of timeslots that are provisioned X for call collision resolution. A timeslot not provisioned as X is assumed to be Y. Description of bits: notused0(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) n16(16) n17(17) n18(18) n19(19) n20(20) n21(21) n22(22) n23(23) n24(24) n25(25) n26(26) n27(27) n28(28) n29(29) n30(30) n31(31)

This group contains attributes which count the protocol messages indicating changes to operational modes of VoiceServices.

An entry in the btdsDpnss1VdcdTable.

This attribute counts the number of messages indicating beginning of establishment of a voice call. This count wraps to zero after reaching its maximum value.

This attribute counts the number of messages indicating beginning of establishment of a data call. This count wraps to zero after reaching its maximum value.

This attribute counts the number of messages indicating a change of a call operational mode from voice transmission to data transmission. This count wraps to zero after reaching its maximum value.

This attribute counts the number of messages indicating a change of a call operational mode from data transmission to voice transmission. This count wraps to zero after reaching its maximum value.

This attribute counts the number of CCS messages indicating the end of a call. This count wraps to zero after reaching its maximum value.

This group contains attributes which count layer 2 frames potentially significant for voice/data call discrimination. See also the description of HdlcStatistics group.

An entry in the btdsDpnss1FramesTable.

This attribute counts the number of valid layer 2 frames containing an Information Field with a protocol message. Changes to operational mode of a VoiceService are triggered only by a subset of processed frames. Many frames refer to the call progress and are ignored from the standpoint of voice/data call discrimination. This count wraps to zero after reaching its maximum value.

This attribute counts the number of invalid layer 2 frames For DPNSS 1, a frames is counted as invalid if - it is shorter than 3 octets or longer than 48 octets (excluding two octets of Cyclic Redundancy Check), or - it has an invalid bit combination in the Address Field, or - the Control Field is inconsistent with the Address Field, or - the type of data is invalid, or - it relates to time slot 0. For MCDN, a frame is counted as invalid if - it is shorter than 4 or longer than 264 octets (excluding two octets of Cyclic Redundancy Check), or - it has an invalid bit combination in the Address Field, or - it has missing or incorrect mandatory information elements. This count wraps to zero after reaching its maximum value.

This group contains attributes which count the signalling frame events.

An entry in the btdsDpnss1HdlcTable.

This attribute counts the number of all hdlc frames, correct or not, received from the PRI. This count wraps to zero after reaching its maximum value.

This attribute counts the number of frame receptions aborted before completion, due to incoming frame format errors. This count wraps to zero after reaching its maximum value.

This attribute counts the number of frames received with CRC errors. This count wraps to zero after reaching its maximum value.

This attribute counts the number of frames received that were non octet aligned. This count wraps to zero after reaching its maximum value.

This attribute counts the number of frames received for which overruns occurred. This count wraps to zero after reaching its maximum value.

This attribute counts the number of received frames which were longer than 1024 octets. This count wraps to zero after reaching its maximum value.

This attribute displays the operational mode of every time slot which is serviced by a voice service. The value idle means that the time slot is not used to service a call, hence the concerned voice service's bandwidth in the Passport subnet is available for other uses. The value voice means that a phone call is in progress. All provisioned voice service's value added features have been activated (features such as voice compression, silence suppression, echo cancellation). The value data means that a data call is in progress. All provisioned voice service's value added features have been de-activated, so that a clear 64 kbit/sec data connection is provided accross the Passport subnet.

An entry in the btdsDpnss1TSlotTable.

This variable represents the index for the btdsDpnss1TSlotTable.

This variable represents an individual value for the btdsDpnss1TSlotTable. Enumeration: 'idle': 0, 'voice': 1, 'data': 2.

This entry controls the addition and deletion of btdsMcdn components.

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

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

This variable represents the index for the btdsMcdn tables.

This group contains the provisionable attribute for the Mcdn component.

An entry in the btdsMcdnProvTable.

This attribute holds the provisioning related to call collision resolution. Its value must be that same as in the adjacent PBX, at the other end of the PRI. To provision the call collision resolution in Nortel's SL1 and Meridian 1 PBXs, the network operator responds to the prompt SIDE by entering either MAS or SLAV. So if the SLAV was entered, then the adjPbxSide has to be provisioned slave. Enumeration: 'master': 1, 'slave': 0.

This group contains attributes which count the protocol messages indicating changes to operational modes of VoiceServices.

An entry in the btdsMcdnVdcdTable.

This attribute counts the number of messages indicating beginning of establishment of a voice call. This count wraps to zero after reaching its maximum value.

This attribute counts the number of messages indicating beginning of establishment of a data call. This count wraps to zero after reaching its maximum value.

This attribute counts the number of messages indicating a change of a call operational mode from voice transmission to data transmission. This count wraps to zero after reaching its maximum value.

This attribute counts the number of messages indicating a change of a call operational mode from data transmission to voice transmission. This count wraps to zero after reaching its maximum value.

This attribute counts the number of CCS messages indicating the end of a call. This count wraps to zero after reaching its maximum value.

This group contains attributes which count layer 2 frames potentially significant for voice/data call discrimination. See also the description of HdlcStatistics group.

An entry in the btdsMcdnFramesTable.

This attribute counts the number of valid layer 2 frames containing an Information Field with a protocol message. Changes to operational mode of a VoiceService are triggered only by a subset of processed frames. Many frames refer to the call progress and are ignored from the standpoint of voice/data call discrimination. This count wraps to zero after reaching its maximum value.

This attribute counts the number of invalid layer 2 frames For DPNSS 1, a frames is counted as invalid if - it is shorter than 3 octets or longer than 48 octets (excluding two octets of Cyclic Redundancy Check), or - it has an invalid bit combination in the Address Field, or - the Control Field is inconsistent with the Address Field, or - the type of data is invalid, or - it relates to time slot 0. For MCDN, a frame is counted as invalid if - it is shorter than 4 or longer than 264 octets (excluding two octets of Cyclic Redundancy Check), or - it has an invalid bit combination in the Address Field, or - it has missing or incorrect mandatory information elements. This count wraps to zero after reaching its maximum value.

This group contains attributes which count the signalling frame events.

An entry in the btdsMcdnHdlcTable.

This attribute counts the number of all hdlc frames, correct or not, received from the PRI. This count wraps to zero after reaching its maximum value.

This attribute counts the number of frame receptions aborted before completion, due to incoming frame format errors. This count wraps to zero after reaching its maximum value.

This attribute counts the number of frames received with CRC errors. This count wraps to zero after reaching its maximum value.

This attribute counts the number of frames received that were non octet aligned. This count wraps to zero after reaching its maximum value.

This attribute counts the number of frames received for which overruns occurred. This count wraps to zero after reaching its maximum value.

This attribute counts the number of received frames which were longer than 1024 octets. This count wraps to zero after reaching its maximum value.

This attribute displays the operational mode of every time slot which is serviced by a voice service. The value idle means that the time slot is not used to service a call, hence the concerned voice service's bandwidth in the Passport subnet is available for other uses. The value voice means that a phone call is in progress. All provisioned voice service's value added features have been activated (features such as voice compression, silence suppression, echo cancellation). The value data means that a data call is in progress. All provisioned voice service's value added features have been de-activated, so that a clear 64 kbit/sec data connection is provided accross the Passport subnet.

An entry in the btdsMcdnTSlotTable.

This variable represents the index for the btdsMcdnTSlotTable.

This variable represents an individual value for the btdsMcdnTSlotTable. Enumeration: 'idle': 0, 'voice': 1, 'data': 2.

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

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 the provisionable attributes for the ifEntry.

An entry in the btdsIfEntryTable.

The desired state of the interface. The up state indicates the interface is operational. The down state indicates the interface is not operational. The testing state indicates that no operational packets can be passed. Enumeration: 'down': 2, 'testing': 3, 'up': 1.

This is the index for the IfEntry. Its value is automatically initialized during the provisioning process.

This group includes the Operational Status attribute. This attribute defines the current operational state of this component.

An entry in the btdsOperStatusTable.

The current state of the interface. The up state indicates the interface is operational and capable of forwarding packets. The down state indicates the interface is not operational, thus unable to forward packets. testing state indicates that no operational packets can be passed. Enumeration: 'down': 2, 'testing': 3, 'up': 1.

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

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 operational attributes related to a Btds.

An entry in the btdsOperationalTable.

This attribute indicates the result of end to end negotiation with the remote end across the subnet. If serviceFailureReason is undetermined, this Btds has not performed end to end negotiation with the remote end, and may or may not be up. serviceFailureReason is undetermined if this Btds just became enabled, if there is not enough available bandwidth to perform negotiation or if the remote end cannot perform negotiation with this Btds. If serviceFailureReason is none, end to end negotiation passed. If serviceFailureReason is mismatchedService, end to end negotiation failed because the remote end service is not a Btds. If serviceFailureReason is mismatchedTimeSlotAlignment, end to end negotiation failed because the local Btds Framer timeSlotAlignment does not match the remote Btds Framer timeSlotAlignment. If serviceFailureReason is mismatchedCallDiscriminator, the local Btds call discrimination subcomponents (Btds Mcdn and Btds Dpnss1) do not match the remote Btds call discrimination subcomponents. If serviceFailureReason is compDecodeFailed, end to end negotiation failed because the information received from the remote end was not recognized as valid data. Description of bits: none(0) undetermined(1) logicalConnection(2) mismatchedService(3) mismatchedTimeSlotAlignment(4) mismatchedCallDiscriminator(5) notused6(6) notused7(7) notused8(8) notused9(9) notused10(10) notused11(11) notused12(12) notused13(13) compDecodeFailed(14)