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

This entry controls the addition and deletion of rtgRs components.

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

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

This variable represents the index for the rtgRs tables.

This group contains operational attributes describing the last selected or manual route returned by RouteSelector. These attributes form selected route description data.

An entry in the rtgRsSelectedRouteTable.

This attribute indicates the sum of cost metrics of trunks that make up the selected route returned by RouteSelector. If the cost metrics at both ends of a trunk differ, the larger metric is used for that trunk. If a route could not be selected for whatever reason then the routeCostMetric is set to a value 999999 intended to symbolize unknown cost. For manual routes the value of routeCostMetric is also 999999. This is because RouteSelector does not verify manual routes thus routeCostMetric is unknown.

This attribute indicates the sum of delay metrics of trunks that make up the selected route returned by RouteSelector. The delay metric of a trunk is equal to half the measuredRoundTripDelay operational attribute of the trunk. If the delay metrics at both ends of a trunk differ, the larger metric is used for that trunk. If a route could not be selected for whatever reason then the routeDelayMetric is set to a value 999999 intended to symbolize unknown delay. For manual routes the value of routeDelayMetric is also 999999. This is because RouteSelector does not verify manual routes, thus routeDelayMetric is unknown.

This attribute indicates the priority at which a route has been selected, or a value of 4 for manual routes since no route selection was made. Since RouteSelector does not verify manual routes the value of 4 for routeBumpingPriority symbolizes an unknown value for manual routes. The remainder of the description is not applicable to manual routes. The bumping priority of a route specifies a priority at which a path along that route can be established. The lowest bumping priority is 4, the highest bumping priority is equal to a setup priority contained in the route request data. If a route is selected at bumping priority 4, then no paths will be bumped since there appears to be enough free bandwidth on selected trunks, and also since this bumping priority is not better than the lowest holding priority (4) of any path. If a route cannot be selected at bumping priority 4 and a setup priority is 3 or better, then a route may be selected at bumping priority 3. This means that paths at holding priority 4 may be bumped if currently there is not enough free bandwidth on selected trunks to establish the new path with setup priority 3. If a route cannot be selected at bumping priority 3 and a setup priority is 2 or better, then a route may be selected at bumping priority 2. In this case paths with holding priority 4 and 3 may be bumped if there is not enough free bandwidth on selected trunks to establish the new path with setup priority 2. If a route cannot be selected at bumping priority 2 and a setup priority is 1 or better, then a route may be selected at bumping priority 1. In this case paths with holding priority 4, 3, and 2 may be bumped if there is not enough free bandwidth on selected trunks to establish the new path with setup priority 1. If a route cannot be selected at bumping priority 1 and a setup priority is 0, then a route may be selected at bumping priority 0. In this case paths with holding priority 4, 3, 2, and 1 may be bumped if there is not enough free bandwidth on selected trunks to establish the new path with setup priority 0.

This attribute indicates the reason for which a route was not selected by RouteSelector. If the route was selected then reasonForNoRoute has a value of none. If the destination in the form of ASCII name was specified (see destination) and the name of node is too long (more than 12 characters) then reasonForNoRoute has a value of destinationNameTooLong. Check and correct node name in the destination attribute. If the destination was not specified, that is destination is blank, then reasonForNoRoute has a value of destinationNotSpecified. Destination attribute should not be blank. If the destination in the form of ASCII name was specified (see destination) and the name of node cannot be found in topological database then reasonForNoRoute has a value of unknownDestinationName. Check and correct node name in the destination attribute. If it is correct then this node does not appear in local topological database as this node may lie across the topology region or cluster boundary. If the destination cannot be found in the topological database or cannot be reached through any gateway node then reasonForNoRoute has a value of unknownDestination. Ensure the destination specified in destination attribute resides in the topology region, or can be reached through a Routing Gateway. That is, at least one reachable address provisioned under a Trunk Address component representing a gateway link can reach the destination NSAP address. If the destination was specified using an incorrect format (see destination) then reasonForNoRoute has a value of incorrectDestination. Use the correct format for destination attribute. If there is no physical connectivity to the destination or gateway node, or number of hops to such node exceeds a limit of 20 hops, or a route to such node cannot satisfy all the parameters in the route request data then reasonForNoRoute has a value of attributeNotMet. Set operationMode to manual and issue d rtg rs command and inspect attributeNotMet to determine which attribute could not be satisfied. If the route to the destination could not be selected for some internal reason then reasonForNoRoute has a value of internalReason. A Software Alarm generated in association with this situation should be reported to Nortel Networks technical support. If the route to the destination could not be selected because of profile reference problem then reasonForNoRoute has a value of attributeProfileProblem. If the route to the destination could not be selected because of manual path reference problem then reasonForNoRoute has a value of manualPathIndexProblem. The following values of reasonForNoRoute are no longer generated: routeCostTooMuch, routeDelayTooMuch, incorrectDestinationEndPoint, and sameNode. Enumeration: 'destinationNotSpecified': 2, 'attributesNotMet': 11, 'none': 0, 'attributeProfileProblem': 13, 'incorrectDestinationEndPoint': 5, 'routeDelayTooLong': 10, 'sameNode': 8, 'unknownDestination': 7, 'routeCostTooMuch': 9, 'unknownSource': 6, 'internalReason': 12, 'unknownDestinationName': 3, 'manualPathIndexProblem': 14, 'destinationNameTooLong': 1, 'incorrectDestination': 4.

This attribute indicates the name of a possible route request data parameter which prevents RouteSelector from selecting the route. This attribute always has a value of allAttributesMet for manual routes since RouteSelector does not verify manual routes. This attribute has a meaningful value if reasonForNoRoute attribute has a value of attributesNotMet. The value of attributeNotMet is only computed when RouteSelector operates in manual mode. That is, when route selection has been initiated by the operator in which case operationMode has a value of manual. RouteSelector determines which of the attributes: requiredRxBandwidth, requiredTxBandwidth, requiredTrunkModes, maximumAcceptableCost, maximumAcceptableDelay, maximumAcceptableGatewaCost, requiredTrafficType, permittedTrunkTypes, requiredSecurity, requiredCustomerParameter, and maximumTransmissionUnit prevents successful route selection by dropping the constraints associated with that attribute and reselecting the route. If that route can be successfully selected then the attribute for which the constraints were dropped is the attribute preventing successful route selection. For example, RouteSelector drops bandwidth constraints by selecting a route with requiredRxBandwidth or requiredTxBandwidth of 0. If the route can be selected then bandwidth is preventing successful route selection. A value of unknownAttributeNotMet indicates that RouteSelector cannot determine why route cannot be selected. Constraints for all attributes are dropped yet successful route cannot be computed. This usually indicates a lack physical connectivity to the destination or gateway node. Alternatively, this may indicate that destination or gateway node is more than 20 hops away where 20 hops is the maximum number of hops in the route. Enumeration: 'permittedTrunkTypes': 8, 'requiredCustomerParm': 10, 'maximumTransmissionUnit': 11, 'maximumAcceptableGatewayCost': 12, 'requiredTxBandwidth': 3, 'unknownAttributeNotMet': 0, 'allAttributesMet': 1, 'maximumAcceptableDelay': 6, 'maximumAcceptableCost': 5, 'requiredSecurity': 9, 'requiredRxBandwidth': 2, 'requiredTrafficType': 7, 'maximumGatewayHops': 13, 'requiredTrunkModes': 4.

This attribute indicates the cost metric associated with reaching the destination indirectly through a gateway node or gateway link that is part of the selected route If the selected route leads directly to the destination node then the routeGatewayCostMetric is set to a value 0. If a route could not be selected for whatever reason then the routeGatewayCostMetric is set to a value 999999 intended to symbolize unknown cost. For manual routes the value of routeGatewayCostMetric is also 999999. This is because RouteSelector does not verify manual routes thus routeGatewayCostMetric is unknown.

This attribute indicates the type of route that was selected by RouteSelector. If no route was selected then routeType has a value of noRoute. If the destination resides on the current node then routeType has a value of sameNode. If the destination resides on a different node and can be reached directly as opposed to indirectly through a gateway node then routeType has a value of destinationNode or destinationNodeLegacy with the latter only possible when legacy gateway selection algorithm was used (see gatewaySelectionAlgorithm). If the destination can be reached indirectly through a gateway node with the gateway node being different from the current node then routeType has a value of gatewayNode or gatewayLink depending on whether or not the route consists of a single gateway link. A route consists of a single gateway link only when the route requestor (see routeRequestor) is a Routing Gateway (in inbound or outbound direction) and the route leads immediately across topology region or cluster boundary. If the destination can be reached indirectly through a gateway node with the gateway node being the current node and the route requestor (see routeRequestor) is an application service as opposed to a Routing Gateway then routeType has a value of routingGateway. If selected route is a manual route then routeType has a value of manual. Note that the type of route, except for manual route, depends on who is the route requestor (application service, Routing Gateway serving as inbound or outbound gateway), where it resides (gateway or non-gateway node), how the destination can be reached (directly or indirectly through a gateway node), and what is the gateway selection algorithm (cost-based, random or legacy). Enumeration: 'destinationNode': 5, 'routingGateway': 9, 'sameNode': 4, 'gatewayLink': 8, 'noRoute': 3, 'manual': 10, 'destinationNodeLegacy': 6, 'gatewayNode': 7.

This group contains attributes used to control RouteSelector.

An entry in the rtgRsControlsTable.

This attribute acts as a 2-position switch, allowing an operator to specify whether the route selection attributes kept by the RouteSelector should be as he/she set them: routeSelectionAttributes = fromOperator, or the route selection attributes could be updated automatically to contain the route selection attributes of the last automatic route request: routeSelectionAttributes = fromLastRouteRequest. Enumeration: 'fromLastRouteRequest': 1, 'fromOperator': 0.

This attribute indicates the mode in which the RouteSelector is currently operating. The two possible modes are automatic and manual. In the automatic mode, a route request message containing the route request data is originated by a PORS VC and sent to the RouteSelector. RouteSelector then selects a route or gets a manual route and returns its description in the selected route description data in the selected route message back to the PORS VC. In the manual mode, the RouteSelector allows the operator to modify the parameters in the route request data (except for the manual path profile reference), and to initiate route selection using that data. When RouteSelector selects the route it displays its description to the operator. Note that even when operationMode is set to manual, RouteSelector handles route request messages originated by services' VCs in the same way as it does when operationMode is set to automatic. Enumeration: 'manual': 1, 'automatic': 0.

This attribute indicates the time when RouteSelector last handled a route request message.

This group contains parameters in route request data that govern the route selection. Values of these parameters are obtained either from an operator or from the last route request message from a PORS VC that contained such parameters or a reference to such parameters (parameter profile reference) as part of the route request data. Route request messages from a PORS VC that ask for a manual route do not contain such parameters or reference to such parameters. All other route request messages either explicitly contain route request data parameters or a reference to a profile containing such parameters. This group of attributes is therefore not applicable to manual routes.

An entry in the rtgRsPathAttributesTable.

This attribute indicates the node ID of the source node from which a route to the destination is to be found. It is typically the current node. The term 'source' is used in relation to the route selection process and not the node where RouteSelector resides, that is the current node. That is, the source node need not be the current node although the selected route will be based on the topological database of the current node.

This attribute is the remote end point's description. The term 'remote' means the other end point, usually distant from the source node. End points are identified using a node name and a service name. The syntax is 'EM/NodeName /'. As an example, the end point component name for the third voice service on node MoonBase is 'EM/MoonBase VS/3'.

This attribute indicates the required priority for path establishment along the selected. Zero is the highest priority and four is the lowest. This attribute is closely related to bumpingPriority attribute.

This attribute indicates the required transmit bandwidth in bits per second to send data to the destination.

This attribute indicates the required receive bandwidth in bits per second to receive data from the destination.

This attribute indicates the size of the largest packet that can be transported along the selected route. It is used by RouteSelector to select a route which avoids trunks whose maximum transmission unit is less than maximumTransmissionUnit and as a result would be unable to transport packets of this size. The default value of 0 permits all trunks to be eligible with respect to this attribute.

This attribute indicates the required minimum level of security of the trunks along the selected 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 PathAdministrator (Trk Pa) component. RouteSelector ensures that any route selected does not contain a trunk whose trunkSecurity attribute is numerically greater than the requiredSecurity.

This attribute indicates the required type of traffic that can be transported along the selected route. There are eight possible traffic types, and only one type can be transported. The voice, data, and video traffic types are already defined, and five other traffic types can be defined by the network administrator. The supportedTrafficType attribute of the Trunk PathAdministrator (Trk Pa) component lists all the types of traffic allowed on the trunk. When selecting a route, RouteSelector only chooses trunks whose supportedTrafficType contains the requiredTrafficType. Enumeration: 'trafficType5': 7, 'trafficType4': 6, 'trafficType1': 3, 'trafficType3': 5, 'trafficType2': 4, 'video': 2, 'voice': 0, 'data': 1.

This attribute indicates a maximum of eight types of trunks that can be part of the selected route. The terrestrial and satellite trunk types have been defined already, leaving six remaining types that can be defined by the network administrator. The trunkType attribute of the Trunk PathAdministrator (Trk Pa) component specifies the type of the trunk. When selecting a route, RouteSelector only chooses trunks whose trunkType is one of the permittedTrunkTypes. Description of bits: terrestrial(0) satellite(1) trunkType1(2) trunkType2(3) trunkType3(4) trunkType4(5) trunkType5(6) trunkType6(7)

This attribute indicates the mechanism to customize the usage of trunks. Any trunk, whose customerParameter attribute under the Trunk PathAdministrator (Trk Pa) component is larger than the requiredCustomerParameter is not eligible to become part of the selected route.

This attribute indicates whether a route should be selected on the basis of minimizing the route cost or the route delay. Each trunk has a cost and a delay metric associated with it. The cost of a route is the sum of the trunk cost metrics for all trunks included in the route. The delay of a route is the sum of the trunk delay metrics for all trunks included in the route. The delay metric of a trunk is equal to half the measuredRoundTripDelay operational attribute of the trunk. Enumeration: 'delay': 1, 'cost': 0.

This attribute indicates the upper bound on the cost metric of the selected route, which is the sum of the cost metrics of all trunks on the route. RouteSelector ensures the cost metric of the selected route does not exceed the maximumAcceptableCost.

This attribute indicates the upper bound on the delay metric of the selected route, which is the sum of the delay metrics of all trunks on the route. RouteSelector ensures the delay metric of the selected route does not exceed the maximumAcceptableDelay. The delay metric of a trunk is equal to half the measuredRoundTripDelay operational attribute of the trunk.

This attribute indicates whether bumping may be considered when selecting a route. By default, bumping may be considered only when it is necessary. That is, only when no other route to the destination or gateway node can be found An indication to always bump in order to find the best route may be set. In this case an absolutely best route to the destination or gateway node is found even if other paths along that route would need bumping. Enumeration: 'bumpWhenNecessary': 0, 'bumpToObtainBestRoute': 1.

This attribute indicates which trunk modes to consider during route selection. The operational mode attribute of the Trunk PathAdministrator (Trk Pa) component specifies the mode of the trunk. When selecting a route, RouteSelector can either consider trunks with any mode, or only trunks with mode set to mapping. That is, the selected route may contain trunks with any mode, or all trunks with mode set to mapping. Enumeration: 'any': 0, 'mapping': 1.

This attribute indicates the upper bound on the cost metric associated with reaching the destination along the selected route and through a gateway node. Such cost metrics are provisioned under Trunk Address component on a gateway node specifying costs of reaching an address through the gateway node and more accurately through the gateway link represented by the Trunk component.

This attribute indicates the type of entity that makes a request for a route (route requestor). Three types of entities can make route requests: application service, Routing Gateway serving as inbound gateway at a gateway node, or Routing Gateway serving as outbound gateway at a gateway node. Enumeration: 'outboundRGty': 2, 'inboundRGty': 1, 'applicationService': 0.

This attribute indicates the type of algorithm to use when a route to the destination has to be selected indirectly through a gateway node. The following types of algorithms are available: cost based, random, and legacy. For cost based algorithm, RouteSelector selects gateway node that advertised it can reach the destination at the smallest cost. For random algorithm, RouteSelector selects randomly any gateway node that advertised it can reach the destination. For legacy algorithm, RouteSelector selects a complete route to the destination without attempting to route through gateway nodes. This is only possible during single to multi topology region migration, or cluster migration but before such migration is complete. During such migrations routing to the destination is initially attempted through gateway nodes, but if such routing fails then legacy routing is attempted. Enumeration: 'random': 2, 'legacy': 4, 'costBased': 1.

This attribute indicates either the ASCII name, node ID, or NSAP address of the destination node to which a route needs to be found. The format for destination is either 1. 'EM/nodeName serviceName/instance', for ASCII name, for example 'EM/MoonBase VS/3', or 2. 'NID/nodeId', for node ID, for example 'NID/1226', or 3. 'NSAP/nsapAddress', for NSAP address, for example 'NSAP/12234001'. For NSAP address formats a full ATM End System Address, node summary, or reachable address can be specified, as well as a node prefix.

This attribute indicates a vector of strings describing the selected or manual route returned by RouteSelector. Each entry in the vector describes one hop of the route. The hops are identified using a node name and either - a TRM allocated trunk identification or exit number (TRM uses a component 'link', or 'Lk' in short form, to refer to trunks), or - a trunk name, which is local to that node. TRM allocated exit number is used for routes selected by RouteSelector. Trunk name is used for manual routes. For example, a hop out of node StarBase using exit number 99 is described as 'EM/STARBASE Trm Lk/99' for the selected route. A hop out of node StarBase using trunk name 123 is described as 'EM/STARBASE TRK/123' for the manual route. A command display Trm Lk/99 on node StarBase can be used to find out the trunk name corresponding to exit number 99.

An entry in the rtgRsSrdTable.

This variable represents the rtgRsSrdTable specific index for the rtgRsSrdTable.

This variable represents an individual value for the rtgRsSrdTable.

This attribute indicates a table (or an array) of the number of route requests and the number of routes selected. There are six rows and five columns in the table. The first row contains a number of route requests in a column. Each column corresponds to a value of setupPriority (= 0,1,2,3,4). An element in the first row gives a number of route request per given setupPriority. The five subsequent rows provide numbers of routes selected at bumpingPriority 0,1,2,3,4. The second row provides numbers of route selections at bumpingPriority 0. Only route requests of setupPriority 0 could be given routes of the bumpingPriority 0. By virtue of the property of bumpingPriority that it cannot be better than the setupPriority the rows two to six form a lower triangular matrix. Route selections performed upon operator request (manual route requests) are not counted.

An entry in the rtgRsRouteStatisticsTable.

This variable represents the next to last index for the rtgRsRouteStatisticsTable. Enumeration: 'routesSelectedAtBp4': 5, 'routesSelectedAtBp3': 4, 'routesSelectedAtBp2': 3, 'routesSelectedAtBp1': 2, 'routesSelectedAtBp0': 1, 'routesRequested': 0.

This variable represents the final index for the rtgRsRouteStatisticsTable.

This variable represents an individual value for the rtgRsRouteStatisticsTable.

This attribute indicates a set of node IDs of destination or gateway nodes which directly or indirectly support the destination and to which RouteSelector attempted to find a route. Node to which the RouteSelector selected the route is also included in destinationOrGatewayNodes.

An entry in the rtgRsDgnTable.

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

This entry controls the addition and deletion of rtgPors components.

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

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

This variable represents the index for the rtgPors tables.

This entry controls the addition and deletion of rtgPorsProf components.

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

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

This variable represents the index for the rtgPorsProf tables.

This group contains all provisionable attributes for a PORS profile..

An entry in the rtgPorsProfProvTable.

This attribute specifies 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, specifies 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 specifies the priority that a path holds once it is established. Zero is the highest priority and four is the lowest. A path's holdingPriority determines this path's 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 specifies 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 but 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. A value of 0 (the default) means that the bandwidth will be the Peak Cell Rate for CLP0+1 as chosen by the user. A non zero value overrides this reservation.

This attribute specifies 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 but 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. A value of 0 (the default) means that the bandwidth will be the Peak Cell Rate for CLP0+1 as chosen by the user. A non zero value overrides this reservation.

This attribute specifies 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. 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 attribute specifies up to eight types of trunk that can be used on the route. 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 specifies the required minimum level of security of the trunks on the route. A value of zero represents the most secure while 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 specifies 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 specifies 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 specifies 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 regardless ofthe value of pathAttributeToMinimize. No route is selected if the cost metric of the shortest route is larger than the maximumAcceptableCost.

This attribute specifies 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 during its staging, the trunk 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 data packet is used to perform the measurement. If for any trunk, 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 specifies the urgency with which packets on the path are emitted by the trunks on the route. An 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). The default value for this attribute (sameAsApplication) will cause the connection's emissionPriority to be inherited from the user of the profile. In other words, setting this attribute to anything other than the default acts as an override to the priority normally used by the application linked to this profile. Enumeration: 'sameAsApplication': 3, 'ep2': 2, 'ep0': 0, 'ep1': 1.

This attribute specifies 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). The default value for this attribute (sameAsApplication) will cause the connection's discardPriority to be inherited from the user of the profile. In other words, setting this attribute to anything other than the default acts as an override to the priority normally used by the application linked to this profile. Enumeration: 'sameAsApplication': 0, 'dp3': 3, 'dp2': 2, 'dp1': 1.

This attribute specifies 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. Enumeration: 'reRoutePath': 1, 'disconnectConnection': 0.

This attribute specifies when bumping may be triggered as a result of this call being routed/rerouted or optimized. There are two possibilities: bumpWhenNecessary: means that this call will only trigger the bumping of another call (subject to setup/holding priority restrictions) when there is no other way to establish a route for this call. bumpToObtainBestRoute: means that this call may trigger the bumping of other calls (subject to setup/holding priority restrictions) if doing so would result in this call obtaining a better (lower cost/delay) route. Since bumping to obtain the best route can be somewhat intrusive the default is only to bump when there is no other way to route the call. Enumeration: 'bumpWhenNecessary': 0, 'bumpToObtainBestRoute': 1.

If this attribute is enabled, this connection will be optimized periodically as specified by the Rtg Pors attribute optimizationInterval. If this attribute is disabled, the connection will use the route it was given for the life of the connection or until a failure or lock results in the call being rerouted. Enumeration: 'disabled': 0, 'enabled': 1.

This attribute specifies all of the components which are associated with this Profile. Users of this profile will select and instantiate routes based on the attributes of this profile when PORS is used to choose and instantiate the route. If IISP or PNNI are used to choose and instantiate the route these attributes are ignored since they have no counterparts in IISP or PNNI routing.

An entry in the rtgPorsProfUsrTable.

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

This entry controls the addition and deletion of rtgPorsMpath components.

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

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

This variable represents the index for the rtgPorsMpath tables.

This group contains operational information for the Rtg Pors ManualPath/n component.

An entry in the rtgPorsMpathOperTable.

This attribute indicates the reason for the most recent failure for an attempted connection using this ManualPath's route. The following is a brief description of the reasons: none - This path has no information for the teardown. 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. If a trunk in the route attribute was previously locked, or has a Trk PA subcomponent that is not in the up state , that Trunk is considered as having no available bandwidth. If the Trunk PA is in mapped mode, the inability to allocate an Atmif Vcc also results in this failure reason. 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. If a trunk in the route attribute was previously locked, or has a Trk PA subcomponent that is not in the up state , that Trunk is considered as having no available bandwidth. trunkFailure- A Trunk on the path has failed or has gone down, due to a provisioning change of a critical attribute, as the path was being established. trunkCardFailure- A Trunk FP card has failed along the path as the path was being established. accessCardFailure- The FP on which the peer access service was running has failed as the path was being established. operatorForced- The path has terminated due to the operator locking a Trunk along the path as the path was being established. lostLcnClash- The path has terminated because the Trk PA's at both ends of an intermediate trunk have allocated the same Trk 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 Trk LC's). It is normal to get the odd clash especially when the Trk PA usedLC is approaching the Trk PA maxLC. An LCN clash results in the path failing to instantiate only if the application disabled rerouting. By default rerouting is enabled for all applications. Applications can disable rerouting by using a Rtg Pors Prof/n component with pathFailureAction set to disconnectConnection. networkCongestion - The path has failed to establish due to control information being lost and not being recoverable. trunkNotFound - Check for Trunks not up or names provisioned incorrectly in route attribute . farEndNotFound - The far end is not provisioned or is not up. The called NSAP address cannot be reached through the last node in the Rtg Pors ManualPath path. farEndBusy - The far end has been reached but it is busy. Check remote end provisioning. 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. serviceTypeMismatch - The remote service type does not match this service type. Check provisioning. bumped - Another call bumped this path, as it was being established, 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. A manual path that is bumped fails to instantiate if it cannot bump another path along the same route, or if it has pathFailureAction set to disconnectConnection. 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 Trk Pa Atm component. Enumeration: 'farEndNotReady': 15, 'bumped': 19, 'none': 0, 'trunkOrFarEndDidNotSupportMode': 23, 'insufficientRxLcOrBandwidth': 3, 'unknownReason': 14, 'trunkFailure': 4, 'farEndNotFound': 10, 'trunkCardFailure': 5, 'insufficientTxLcOrBandwidth': 2, 'lostLcnClash': 7, 'accessCardFailure': 20, 'serviceTypeMismatch': 17, 'operatorForced': 6, 'networkCongestion': 8, 'farEndBusy': 12, 'trunkNotFound': 9.

This attribute indicates the point in the route at which the path failed to establish. A failure at either end of a trunk will result in the display of the name of the trunk nearer the calling end.

This attribute indicates the component in the users attribute that last failed to instantiate a path based on the route.

This attribute specifies the sequence of trunks used as the route for a path. If any trunk in the sequence does not meet the requirements (bandwidth, permittedTrunkType, security, customerParm, etc.) for a component listed in users, path validation fails and no path is instantiated for that user. Changing this attribute will cause active connections of users of this ManualPath to move to the new route only if the users have optimization enabled and Rtg Pors optimizationInterval > 0. Otherwise, changing this attribute will cause the users' current connections to stay on the old route with all new calls instantiating their paths with the new route. Optimization can be disabled by having the application use a Rtg Pors Prof/n component with optimization disabled or by setting Rtg Pors optimizationInterval 0. As an example, the trunk component name for the trunk instance 10 on node MoonBase is EM/MoonBase Trk/10. These strings are case insensitive but the complete component name must be input. Note 1: the trunk designation must be in the 3-letter form 'trk'. Note 2: only the outbound trunk component names are used to provision the route.

An entry in the rtgPorsMpathRouteTable.

This variable represents the rtgPorsMpathRouteTable specific index for the rtgPorsMpathRouteTable.

This variable represents an individual value for the rtgPorsMpathRouteTable.

This attribute specifies all of the components that will use this ManualPath to instantiate a path. Users of this component have paths that follow the sequence of Trunks specified in the route attribute of this component when PORS is used to choose and instantiate the route.

An entry in the rtgPorsMpathUsrTable.

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

This group contains all provisionable attributes for the Routing PathOrientedRoutingSystem component.

An entry in the rtgPorsProvTable.

This attribute defines the interval at which the optimization process will be triggered. The time is defined from the end of one optimization pass until the start of another optimization pass. If an interval of zero is specified periodic optimization is disabled on this module.

This group contains operational information for the PathOrientedRoutingSystem component.

An entry in the rtgPorsInfoTable.

This attribute is the current number of active PORS connections on this module. Active connections are connections that are in the Logical Connection component pathUp state. This value is updated when requested and represents the current number of active PORS connections. During PORS optimization this number represents all the connections that receive optimization requests.

This attribute is the current state of the PORS optimization. The disabled state means that the optimizationInterval has been set to zero. The scheduled state means that the optimization will be started at the nextOptimizationTime. The optimizing state means that PORS is currently attempting to optimize all connections on the module. Enumeration: 'disabled': 0, 'scheduled': 1, 'optimizing': 2.

This attribute specifies the time that the last optimization started.

This attribute specifies the time the next optimization process will begin. In the event that optimizationInterval is set to zero this value is also set to 0.

This is the number of optimization passes for the PORS connection manager. An optimization pass consists of a notification to each active PORS connection to attempt to optimize. All types of optimization passes are included in this statistic.

This attribute is the percentage of active connections that have been sent an optimization request. A message is sent to each PORS component LC requesting it to optimize its route. This value is cleared at the beginning of each optimization pass.

This attribute is the number of successfully optimized paths for the latest optimization pass. Successfully optimized paths are paths that switched to a better route. This value is cleared at the beginning of each optimization pass.

This attribute is the number of successfully optimized paths on this module since the CP became active.