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

This entry controls the addition and deletion of appn components.

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

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

This variable represents the index for the appn tables.

This entry controls the addition and deletion of appnDna components.

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

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

This variable represents the index for the appnDna tables.

This entry controls the addition and deletion of appnDnaHgM components.

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

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

This variable represents the index for the appnDnaHgM tables.

This entry controls the addition and deletion of appnDnaHgMHgAddr components.

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

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

This variable represents the index for the appnDnaHgMHgAddr tables.

This group contains attributes common to all DNAs. Every DNA used in the network is defined with this group of 2 attributes.

An entry in the appnDnaHgMHgAddrAddrTable.

This attribute specifies the Numbering Plan Indicator (NPI) of the Dna that is entered. The address may belong to the X.121 or E.164 numbering plans. Enumeration: 'e164': 1, 'x121': 0.

This attribute specifies the digits that form the unique identifier of the customer interface. It can be compared (approximation only) to a telephone number where phone number identifies unique telephone set. Dna digits are selected and assigned by network operators.

This group contains the interface parameters between the HuntGroupMember and the Hunt Group server.

An entry in the appnDnaHgMIfTable.

This attribute indicates the number of channels that have to be freed or occupied before the Availability Message Packet (AMP) is sent to the Hunt Group Server informing it of the status of this interface.

This group contains the operational attributes of the HuntGroupMember component.

An entry in the appnDnaHgMOpTable.

This attribute indicates the maximum number of available channels for this HuntGroupMember.

This attribute indicates the number of available channels reported to the hunt group in the Availability Message Packet (AMP). It is incremented by the application when a channel is freed and decremented when a channel is occupied.

This attribute indicates the net change in the available channels since the last Availability Message Packet (AMP) was sent to the Hunt Group. Once the absolute value of this attribute reaches the availabilityUpdateThreshold an AMP is sent to the host and the availabilityDelta is reset to 0. If this attribute is positive it means an increase of the number of available channels. If it is negative it means a decrease in the number of available channels.

This entry controls the addition and deletion of appnDnaCug components.

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

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

This variable represents the index for the appnDnaCug tables.

Attributes in this group defines ClosedUserGroup options associated with interlockCode. Dnas with the same Cug (interlockCode) make calls within this group. Various combinations which permit or prevent calls in the same Cug group are defined here.

An entry in the appnDnaCugCugOptionsTable.

This attribute specifies the Cug type - the Cug is either a national Cug, or an international Cug. International closed user groups are usually established between DTEs for which there is an X.75 Gateway between; whereas national closed user groups are usually established between DTEs for which there is no X.75 Gateway between. (National Cugs cannot normally traverse an X.75 Gateway). If this attribute is set to national, then the Cug is a national Cug, in which case, the dnic should be left at its default value since it is not part of a national Cug. If this attribute is set to international, then the Cug is an international Cug, in which case, the dnic should be set appropriately as part of the Cug interlockCode. Enumeration: 'international': 1, 'national': 0.

This attribute specifies the dnic (Data Network ID Code) the Cug by which packet networks are identified. This attribute is not applicable if the Cug is a national Cug, as specified by the Cug type attribute. There are usually 1 or 2 dnics assigned per country, for public networks. The U.S. is an exception where each BOC has a dnic. Also, a group of private networks can have its own dnic. dnic value is not an arbitrary number. It is assigned by international agreement and controlled by CCITT.

This attribute specifies the Cug identifier of a national or international Cug call. It is an arbitrary number and it also can be called Cug in some descriptions. Interfaces (Dnas) with this number can make calls to Dnas with the same interlockCode.

This attribute, if set to yes indicates that this Cug is the preferential Cug, in which case it will be used during the call establishment phase if the DTE has not explicitly specified a Cug index in the call request packet. If set to no, then this Cug is not the preferential Cug. Only one of the Cugs associated with a particular Dna can be the preferential Cug - only one Cug can have this attribute set to yes. Enumeration: 'yes': 1, 'no': 0.

This attribute, if set to allowed indicates that outgoing calls (from the DTE into the network) be made using this particular Cug. If set to a value of disallowed, then outgoing calls cannot be made using this Cug - such calls will be cleared by the local DCE. This attribute corresponds to the CCITT 'Outgoing Calls Barred' feature for Cugs in that outgoing calls are barred if this attribute is set to a value of disallowed. Enumeration: 'disallowed': 0, 'allowed': 1.

This attribute, if set to allowed indicates that incoming calls (from the network to the DTE) be made using this particular Cug. If set to disallowed, then incoming calls cannot be made using this Cug - such calls will be cleared by the local DCE. This attribute corresponds to the CCITT 'Incoming Calls Barred' feature for Cugs in that incoming calls are barred if this attribute is set to a value of disallowed. Enumeration: 'disallowed': 0, 'allowed': 1.

This attribute, if set to yes indicates that this Cug is a privileged Cug. In DPN, at least one side of a call setup within a Cug must have the Cug as a privileged Cug. If set to no, then the Cug is not privileged. If both the local DTE and the remote DTE subscribe to the Cug, but it is not privileged, then the call will be cleared. This attribute is typically used for a host DTE which must accept calls from many other DTEs in which case the other DTEs cannot call one another, but can call the host. In this example, the host would have the privileged Cug, and the other DTEs would belong to the same Cug, but it would not be privileged. Enumeration: 'yes': 1, 'no': 0.

Address group contains attributes common to all Dna's. Every Dna used in the network is defined with this group of 2 attributes. String of address digits is complemented by type of address and Npi. These attributes are used to interpret format of the address digits.

An entry in the appnDnaAddressTable.

This attribute indicates the Numbering Plan Indicator (NPI) of the Dna that is entered. Address may belong to X.121 or E.164 plans. X.121 is used in packet switched data networks. Enumeration: 'e164': 1, 'x121': 0.

Dna attribute contains digits which form unique identifier of the customer interface. It can be compared (approximation only) to telephone number where phone number identifies unique telephone set. Dna digits are selected and assigned by network operators.

OutgoingOptions group defines call options of a Dna for calls which are made out of the interface represented by Dna. All these options are not used for calls arriving to the interface represented by Dna.

An entry in the appnDnaOutgoingOptionsTable.

This attribute, if set to normal indicates that the default priority for outgoing calls (from the DTE to the network) using this particular Dna is normal priority - if the priority is not specified by the DTE. If this attribute is set to high then the default priority for outgoing calls using this particular Dna is high priority. This option can be also included in X.25 signalling, in such case it will be overruled. Enumeration: 'high': 1, 'normal': 0.

This attribute specifies the default class of routing for delay/ throughput sensitive routing for all outgoing calls (from the DTE to the network) using this particular Dna. The chosen default class of routing applies to all outgoing calls established using this Dna, and applies to the packets travelling in both directions on all outgoing calls (local to remote, and remote to local). For incoming calls, the default class of routing is chosen by the calling party (as opposed to DPN, where either end of the call can choose the default routing class). This attribute, if set to a value of throughput, indicates that the default class of routing is throughput sensitive routing. If set to a value of delay, then the default class of routing is delay sensitive routing. In the future, the class of routing sensitivity may be overridden at the calling end of the call as follows: The default class of routing sensitivity can be overridden by the DTE in the call request packet through the TDS&I (Transit Delay Selection & Indication) facility if the DTE supports this facility. Whether or not the DTE is permitted to signal the TDS&I facility will depend on the DTE (i.e.: TDS&I is supported in X.25 only), and will depend on whether the port is configured to permit the TDS&I facility. In Passport, the treatment of DTE facilities (for example, NUI, RPOA, and TDS&I) is not fully defined yet since it is not required. At the point in time when it is required, the parameter to control whether or not the DTE is permitted to signal the TDS&I will be in a Facility Treatment component. Currently, the default is to disallow the TDS&I facility from the DTE. Enumeration: 'delay': 1, 'throughput': 0.

If this attribute is set to yes in the call request, the called end will use the calling end provisioning data on sensitivity to override its provisioning data, Enumeration: 'yes': 1, 'no': 0.

This attribute specifies the default class of routing for reliability routing for all outgoing calls (from the DTE to the network) using this particular Dna. The chosen default class of routing applies to all outgoing calls established using this Dna, and applies to the packets travelling in both directions on all outgoing calls (local to remote, and remote to local). For incoming calls, the default class of routing is chosen by the calling party (as opposed to DPN, where either end of the call can choose the default routing class). This attribute, if set to a value of normal, indicates that the default class of routing is normal reliability routing. If set to a value of high, then the default class of routing is high reliability routing. High reliability is the standard choice for most DPN and Passport services. It usually indicates that packets are overflowed or retransmitted at various routing levels. Typically high reliability results in duplication and disordering of packets in the network when errors are detected or during link congestion. However, the Vc handles the duplication and disordering to ensure that packets are delivered to the DTE properly. For the Frame Relay service, duplication of packets is not desired, in which case, normal reliability may be chosen as the preferred class of routing. Enumeration: 'high': 0, 'normal': 1.

This attribute is an extension of the Closed User Group (CUG) facility, as follows: This attribute, if set to a value of allowed indicates that outgoing calls (from the DTE to the network) to the open (non-CUG) part of the network are permitted. It also permits outgoing calls to DTEs that have Incoming Access capabilities. If set to a value of disallowed, then such calls cannot be made using this Dna - such calls will be cleared by the local DCE. This attribute corresponds to the CCITT 'Closed User Group with Outgoing Access' feature for Dna's in that outgoing access is granted if this attribute is set to a value of allowed. Enumeration: 'disallowed': 0, 'allowed': 1.

This attribute specifies the default transfer priority to network for all outgoing calls using this particular Dna. It is overRidden by the transferPriority provisioned in the DLCI Direct Call sub- component. The transfer priority is a preference specified by an application according to its delay-sensitivity requirement. Frames with high transfer priority are served by the network before the frames with normal priority. Each transfer priority contains a predetermined setting for trunk queue (interrupting, delay or throughput), and routing metric (delay or throughput). When the transfer priority is set at high, the trunk queue is set to high, the routing metric is set to delay. When the transfer priority is set at normal, the trunk queue is set to normal, the routing metric is set to throughput. The default of defaultTransferPriority is normal. Enumeration: 'high': 9, 'normal': 0.

When this attribute is set to yes in the call request, the called end will use the calling end provisioning data on transfer priority to override its own provisioning data. If it is set no, the called end will use its own provisioning data on transfer priority. The default of outTransferPriorityOverRide is yes. Enumeration: 'yes': 1, 'no': 0.

IncomingOptions defines set of options for incoming calls. These options are used for calls arriving to the interface represented by Dna. For calls originated from the interface, IncomingOptions attributes are not used.

An entry in the appnDnaIncomingOptionsTable.

This attribute is an extension of the Closed User Group (CUG) facility, as follows: This attribute, if set to a value of allowed indicates that incoming calls (from the network to the DTE) from the open (non-CUG) part of the network are permitted. It also permits incoming calls from DTEs that have Outgoing Access capabilities. If set to a value of disallowed, then such calls cannot be made to this Dna - such calls will be cleared by the local DCE. This attribute corresponds to the CCITT 'Closed User Group with Incoming Access' feature for Dnas in that incoming access is granted if this attribute is set to a value of allowed. Enumeration: 'disallowed': 0, 'allowed': 1.

CallOptions group defines additional options for calls not related directly to direction of a call.

An entry in the appnDnaCallOptionsTable.

This attribute indicates the default receive throughput class for all calls using this particular Dna.

This attribute indicates the default send throughput class for all calls using this particular Dna.

This attribute indicates the default number of data packets that can be received by the DTE from the DCE before more packets can be received. This view is oriented with respect to the DTE.

This attribute indicates the number of data packets that can be transmitted from the DTE to the DCE and must be acknowledged before more packets can be transmitted.

This attribute specifies the accounting class which is reserved for network operations usage. Its value is returned in the accounting record in the local and remote service type attributes. Use of this attribute is decided by network operator and it is an arbitrary number.

This attribute indicates that accounting records are to be collected by the network for the various reasons: billing, test, study, auditing. The last of the parameters, force, indicates that accounting records are to be collected irrespective of other collection reasons. If none of these reasons are set, then accounting will be suppressed. Description of bits: bill(0) test(1) study(2) audit(3) force(4)

This attribute is an arbitrary number, entered by the network operator. It is included in the accounting record created by Vc.

This entry controls the addition and deletion of appnDlci components.

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

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

This variable represents the index for the appnDlci tables.

This entry controls the addition and deletion of appnDlciDc components.

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

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

This variable represents the index for the appnDlciDc tables.

The Options group defines attributes associated with a direct call. It defines a complete connection in terms of path and call options. This connection can be permanent (PVC) or switched (SVC). It can have facilities. The total number of bytes of facilities including the facility codes, and all of the facility data from all of the four classes of facilities: CCITT_Facilities DTE_Facilities National_Facilities International_Facilities must not exceed 512.

An entry in the appnDlciDcOptionsTable.

This attribute specifies the numbering plan used for remoteDna. Enumeration: 'e164': 1, 'x121': 0.

This attribute specifies the Data Network Address (Dna) of the remote. This is the called (destination) DTE address (Dna) to which this direct call will be sent. Initially, the called DTE address attribute must be present, that is, there must be a valid destination address. However, it may be possible in the future to configure the direct call with a mnemonic address, in which case, this attribute will contain a zero-length Dna, and the mnemonic address will be carried as one of the facilities.

This attribute provides the remote DLCI (Logical Channel Number) - it is used only for PVCs, where attribute type is set to permanentMaster or permanentSlave or permanentBackupSlave. In switched case, value of remoteDlci is not known when call request is made.

This attribute specifies the type of Vc call: permanentMaster, permanentSlave, permanentSlaveWithBackup, permanentBackupSlave. If the value is set to permanentMaster, then a permanent connection will be established between two ends. The remote end must be defined as a permanentSlave, permanentBackupSlave or permanentSlaveWithBackup. The connection cannot be established if the remote end is defined as anything else. The end defined as permanentMaster always initiates the calls. It will attempt to call once per minute. If the value is set to permanentSlave then a permanent connection will be established between 2 ends. The remote end must be defined as a permanentMaster. The connection cannot be established if the remote end is defined as anything else. The permanentSlave end will attempt to call once per minute. If the value is set to permanentSlaveWithBackup then a permanent connection will be established between the 2 ends . The remote end must be defined as a permanentMaster. The Connection cannot be established if the remote end is defined as anything else. The permanentSlaveWithBackup end will attempt to call once per minute. If the value is set to permanentBackupSlave then a permanent connection will be established between the 2 ends only if the permanentMaster end is disconnected from the permanentSlaveWithBackup end and a backup call is established by the redirection system. If the permanentSlaveWithBackup interface becomes visible again, the permanentBackupSlave end is disconnected and the permanentSlaveWithBackup end is reconnected to the permanentMaster end. The permanentBackupSlave end does not try to establish PVC call. Enumeration: 'permanentSlave': 2, 'permanentMaster': 1, 'permanentBackupSlave': 3, 'permanentSlaveWithBackup': 4.

This attribute specifies the transfer priority to network for the outgoing calls using this particular DLCI. It overRides the defaultTransferPriority provisioned in its associated Dna component. The transfer priority is a preference specified by an application according to its delay-sensitivity requirement. Frames with high transfer priority are served by the network before the frames with normal priority. Each transfer priority contains a predetermined setting for trunk queue (interrupting, delay or throughput), and routing metric (delay or throughput). When the transfer priority is set at high, the trunk queue is set to high, the routing metric is set to delay. When the transfer priority is set at normal, the trunk queue is set to normal, the routing metric is set to throughput. The default of transferPriority is useDnaDefTP. It means using the provisioning value under defaultTransferPriority of its associated Dna for this DLCI. Enumeration: 'high': 9, 'useDnaDefTP': 255, 'normal': 0.

This attribute specifies the discard priority for outgoing call using this DLCI. The discard priority has three provisioning values: normal, high, and useDnaDefPriority. Traffic with normal priority are discarded first than the traffic with high priority. The Dna default value (provisioned by outDefaultPriority) is taken if this attribute is set to the value useDnaDefPriority. The default of discardPriority is useDnaDefPriority. Enumeration: 'high': 1, 'useDnaDefPriority': 3, 'normal': 0.

Two explicit attributes discardPriority and transferPriority are created to replace H.01 and H.30 in the group VcsDirectCallOptionsProv of this file. The migrate escape here (DcComponent::migrateFaxEscape) propagates the old provisioning data under H.01 and H.30 into discardPriority and transferPriority. The rule of the above propagation are: 0 in H.01 is equivalent to discardPriority 0; 1 in H.01 is equivalent to discardPriority 1. And 0 in H.30 is equivalent to transferPriority normal; 1 in H.30 is equivalent to transferPriority high. Please refer to discardPriority and transferPriority for more information on how to use them.

An entry in the appnDlciDcNfaTable.

This variable represents the index for the appnDlciDcNfaTable.

This variable represents an individual value for the appnDlciDcNfaTable.

This variable is used to control the addition and deletion of individual values of the appnDlciDcNfaTable.

This entry controls the addition and deletion of appnDlciVc components.

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

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

This variable represents the index for the appnDlciVc tables.

This group represents operational call data related to Frame Relay Vc. It can be displayed only for Frame Relay Vc which is created by application.

An entry in the appnDlciVcCadTable.

This attribute displays the type of call, pvc,svc or spvc. Enumeration: 'spvc': 2, 'pvc': 1, 'svc': 0.

This attribute displays the state of call control. P5 state is not supported but is listed for completness. Transitions from one state to another take very short time. state most often displayed is dataTransferP4. Enumeration: 'readyP1': 1, 'creating': 0, 'dteWaitingP2': 2, 'dceWaitingP3': 3, 'termination': 8, 'dataTransferP4': 4, 'dteClearRequestP6': 6, 'dceClearIndicationP7': 7, 'unsupportedP5': 5.

This attribute displays the previous state of call control. This is a valuable field to determine how the processing is progressing. Enumeration: 'readyP1': 1, 'creating': 0, 'dteWaitingP2': 2, 'dceWaitingP3': 3, 'termination': 8, 'dataTransferP4': 4, 'dteClearRequestP6': 6, 'dceClearIndicationP7': 7, 'unsupportedP5': 5.

This attribute displays the internal substate of call control. It is used to further refine state of call processing.

This attribute displays the internal substate of call control. It is used to further refine state of call processing.

This attribute displays the Numbering Plan Indicator (NPI) of the called end. Enumeration: 'e164': 1, 'x121': 0.

This attribute displays the Data Network Address (Dna) of the called (destination) DTE to which this call is sent. This address if defined at recieving end will complete Vc connection.

This attribute displays the Logical Channel Number of the called end. It is valid only after both ends of Vc exchanged relevant information.

This attribute displays the Numbering Plan Indicator (NPI) of the calling end. Enumeration: 'e164': 1, 'x121': 0.

This attribute displays the Data Network Address (Dna) of the calling end.

This attribute displays the Logical Channel Number of the calling end.

This attribute indicates that this optional section of accounting record is suppressed or permitted. If accountingEnabled is yes, conditions for generation of accounting record were met. These conditions include billing options, vc recovery conditions and Module wide accounting data options. Enumeration: 'yes': 0, 'no': 1.

This attribute displays that this is a fast select call. Enumeration: 'yes': 1, 'no': 0.

This attribute displays the path reliability. Enumeration: 'high': 0, 'normal': 1.

This attribute indicates if this end should generate an accounting record. Normally, callingEnd is the end to generate an accounting record. Enumeration: 'calledEnd': 1, 'callingEnd': 0.

This attribute displays whether the call is a normal or a high priority call. Enumeration: 'high': 1, 'normal': 0.

This attribute displays the segment size (in bytes) used on the call. It is used to calculate the number of segments transmitted and received.

This attribute indicates the maximum packet size allowed on the Vc.

This attribute indicates the routing metric routing class of service to the network. Enumeration: 'delay': 1, 'multimedia': 2, 'throughput': 0.

This attribute displays the routing metric Routing Class of Service from the Network. Enumeration: 'delay': 1, 'multimedia': 2, 'throughput': 0.

This attribute displays the network internal emission priotity to the network. Enumeration: 'high': 1, 'interrupting': 2, 'normal': 0.

This attribute displays the network internal emission priotity from the network. Enumeration: 'high': 1, 'interrupting': 2, 'normal': 0.

This attribute indicates the data path used by the connection. The data path is provisioned in Dna and DirectCall components. The displayed value of this attribute can be different from the provisioned value. If the connection is using dprsOnly data path, the string dprsOnly is displayed. (dynamic packet routing system) If the connection is using dprsMcsOnly data path, the string dprsMcsOnly is displayed. If the connection is using dprsMcsFirst data path, the string dprsMcsFirst is displayed.

This group defines display of interval data collected by Vc. Data in this group is variable and may depend on time when this display command is issued.

An entry in the appnDlciVcIntdTable.

This attribute displays the call reference number which is a unique number generated by the switch.The same Call Reference Number is stored in the interval data (accounting record) at both ends of the call. It can be used as one of the attributes in matching duplicate records generated at each end of the call.

This attribute displays the elapsed time representing the period of this interval data. It is elapsed time in 0.1 second increments since Vc started.

This attribute displays the number of segments received at the time command was issued. This is the segment received count maintained by accounting at each end of the Vc. This counter is updated only when the packet cannot be successfully delivered out of the sink Vc and to the sink AP Conditions in which packets may be discarded by the sink Vc include: missing packets due to subnet discards, segmentation protocol violations due to subnet discard, duplicated and out-of-ranged packets and packets that arrive while Vc is in path recovery state.

This attribute displays the number of segments sent at the time command was issued. This is the segment sent count maintained by accounting at the source Vc. Vc only counts packets that Vc thinks can be delivered successfully into the subnet. In reality, these packets may be dropped by trunking, for instance. This counter is not updated when splitting fails, when Vc is in a path recovery state, when packet forwarding fails to forward this packet and when subsequent packets have to be discarded as we want to minimize the chance of out-of-sequence and do not intentionally send out-of- sequenced packets into the subnet.

This attribute displays the start time of this interval period. If Vc spans 12 hour time or time of day change startTime reflects new time as recorded at 12 hour periods or time of day changes.

This group defines Frame Relay attributes collected by Frame Relay Vc. The purpose of Vc attributes is to aid end users and verification people to understand the Vc internal behavior. This is particularly useful when the network has experienced abnormality and we want to isolate problems and pinpoint trouble spots. Attributes are collected on a per Vc basis. Until a need is identified, statistics are not collected at a processor level. Each attribute is stored in a 32 bit field and is initialized to zero when a Vc enters into the data transfer state. When a PVC is disconnected and then connected again, the attributes will be reset. Attributes cannot be reset through other methods. Frame Relay Vc uses a best effort data packet delivery protocol and a different packet segmentation and combination methods from the General Vc. The Frame Relay Vc uses the same call setup and control mechanism (e.g. the support of non-flow control data packets) as in a General Vc. Most General Vc statistics and internal variables are used in a Frame Relay Vc and are displayed by software developers

An entry in the appnDlciVcFrdTable.

This attribute displays the number of frames from link discarded due to lack of resources. It keeps track of the number of frames from link that have to be discarded. The discard reasons include insufficient memory for splitting the frame into smaller subnet packet size.

This attribute displays the number of discarded packets that can not be forwarded into the subnet because of subnet congestion. Number of frames from link discarded due to failure in forwarding a packet from Vc into the subnet.- This attribute is increased when packet forwarding fails to forward a packet into the subnet. If a frame is split into multiple subnet packets and a partial packet has to be discarded, all subsequent partial packets that have not yet been delivered to the subnet will be discarded as well.

This attribute records the number of frames from link discarded when the Vc tries to recover from internal path failure.

This attribute displays the number of frames from subnet discarded due to out of sequence range for arriving too late.

This attribute records the number of subnet packets discarded at the sink Vc due to the Vc segmentation and combination protocol error. Usually, this occurs when the subnet discards packets and thus this statistics can be used to guest the number of subnet packets that are not delivered to the Vc. It cannot be used as an actual measure because some subnet packets may have been delivered to Vc but have to be discarded because these are partial packets to a frame in which some other partial packets have not been properly delivered to Vc

This attribute displays the number of subnet packets discarded due to duplication. Although packets are not retransmitted by the Frame Relay Vc, it is possible for the subnet to retransmit packets. When packets are out-of-sequenced and copies of the same packets arrive, then this attribute is increased.

This attribute displays the number of subnet packets discarded when data transfer is suspended in Vc recovery.

This attribute displays the number of lost frame timer expiries. When this count is excessive, the network is very congested and packets have been discarded in the subnet.

This attribute displays the number times that the out of sequence byte threshold is exceeded. When the threshold is exceeded, this condition is treated as if the loss frame timer has expired and all frames queued at the sink Vc are delivered to the AP. We need to keep this count to examine if the threshold is engineered properly. This should be used in conjunction with the peak value of out-of- sequenced queue and the number of times the loss frame timer has expired. This count should be relatively small when compared with loss frame timer expiry count.

This attribute displays the frame relay peak packet count of the out of sequence queue. This attribute records the maximum queue length of the out-of-sequenced queue. The counter can be used to deduce the message buffer requirement on a Vc.

This attribute displays the frame relay peak size of the sequence packet queue. The subnet may deliver packets out-of- sequenced. These packets are then queued in an out-of-sequenced queue, waiting for a packet with the expected sequence number to come. When that packet arrives, this attribute records the maximum number of packets that were out-of-sequenced, but now have become in-sequenced. The statistics is used to measure expected queue size due to normal subnet packet disorder (not due to subnet packet discard). Current implementation also uses this statistics to set a maximum size for the out-of-sequenced queue.

This attribute displays the Vc internal packet's send sequence number. Note that a 'packet' in this context, may be either a user data packet, or an OAM frame.

This attribute displays the number of packets which have retransmission time-outs. When this count is excessive, the network is very congested and packets have been discarded in the subnet.

This attribute displays the peak size of retransmission queue. This attribute is used as an indicator of the acknowledgment behavior across the subnet. Records the largest body of unacknowledged packets.

This attribute displays the number of successful Vc recovery attempts.

This attribute displays the number times that the out of sequence packet threshold is exceeded. When the threshold is exceeded, this condition is treated as if the loss frame timer has expired and all frames queued at the sink Vc are delivered to the AP. We need to keep this count to examine if the threshold is engineered properly. This should be used in conjunction with the peak value of out-of- sequenced queue and the number of times the loss frame timer has expired. This count should be relatively small when compared with loss frame timer expiry count.

This attribute displays the frame relay peak byte count of the out of sequence queue. This attribute records the maximum queue length of the out-of-sequenced queue. The counter can be used to deduce the message buffer requirement on a Vc.

This attribute displays the data path used by the connection. Data path is provisioned in Dna and DirectCall components. If the connection is using dprsOnly data path, this attribute is empty. If the connection is using dprsMcsOnly or dprsMcsFirst data path, this attribute displays component name of the dprsMcsEndPoint.

An entry in the appnDlciVcDmepTable.

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

This entry controls the addition and deletion of appnDlciBnnLsDef components.

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

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

This variable represents the index for the appnDlciBnnLsDef tables.

This group contains the provisioning data for a Link Station on a frame relay DLCI.

An entry in the appnDlciBnnLsDefProvTable.

This attribute specifies which down stream physical unit service is supported on this Link Station. Enumeration: 'dlur': 2, 'none': 0.

This attribute specifies the fully qualified control point (FQCP) name of the adjacent node. This attribute is ignored if the adjacent node is not an APPN node. If this attribute is not empty it is checked against the name received from the adjacent node during the XID exchange, unless adjacentCpType is set to backLevelLenNode (in which case it is used to identify the adjacent node). The first portion of this name, up to the period, is the network identifier for the network to which the adjacent node belongs. An APPN network is a portion of a virtual private network which has a separately administered name space. This network identifier is the implicit qualifier of all resources which do not have an explicit network identifier.

This attribute specifies the adjacent control point (CP) type: networkNode - Specifies that the adjacent device is an APPN network node. endNode - Specifies that the adjacent device is an APPN end node. appnNode - Specifies that the adjacent device is an APPN node or an up-level LEN node, and the node type will be dynamically determined during XID exchange. backLevelLenNode - Specifies that the adjacent device is a back- level LEN node. hostXID3 - Specifies that the adjacent device is a host and that this APPN node should respond to a polling XID from the node with a format 3 XID. hostXID0 - Specifies that the adjacent device is a host and that this APPN node should respond to a polling XID from the node with a format 0 XID. dlurXID - Specifies that the adjacent device is a downstream PU requiring DLUR services and XID exchange in link activation dlurNoXID - Specifies that the adjacent device is a downstream PU requiring DLUR services and no XID exchange in link activation Enumeration: 'backLevelLenNode': 5, 'hostXID3': 6, 'hostXID0': 7, 'networkNode': 2, 'dlurNoXID': 9, 'endNode': 3, 'appnNode': 0, 'dlurXID': 8.

This attribute specifies the TG number to be used for this link. It is only relevant if the adjacent device is an APPN node and is ignored otherwise. If adjacentCpType is set to backLevelLenNode this attribute is ignored and the TG number is assumed to be 1. If this attribute is set to zero (0), the TG number is dynamically assigned and can be determined from the tgNum attribute of the related LinkStation component. If this attribute is non-zero, the adjacentCpType must be set to appnNode, networkNode, endNode or backLevelLenNode, and the TG number on the adjacent device must also be set to the same value.

This attribute specifies the fully qualified control point (FQCP) name of the primary DLUS for this link station. This attribute is ignored if the adjacent device does not request DLUR services. This attribute overrides the primaryDefDlusName and secondaryDefDlusName specified in the DLUR component. If this attribute is empty, the primaryDefDlusName (specified in the DLUR component), or secondaryDefDlusName (specified in the DLUR component) will be used. The first portion of this name, up to the period, is the network identifier for the network to which the DLUS node belongs. An APPN network is a portion of a virtual private network which has a separately administered name space. This network identifier is the implicit qualifier of all resources which do not have an explicit network identifier.

This attribute specifies the fully qualified control point (FQCP) name of the backup DLUS for this link station. This attribute is ignored if the adjacent device does not request DLUR services. This attribute overrides the primaryDefDlusName and secondaryDefDlusName specified in the DLUR component. If this attribute is empty and the dlusName attribute is empty, the primaryDefDlusName (specified in the DLUR component), or secondaryDefDlusName (specified in the DLUR component) will be used. If this attribute is specified, the dlusName attribute must also contain a non-empty string. The first portion of this name, up to the period, is the network identifier for the network to which the DLUS node belongs. An APPN network is a portion of a virtual private network which has a separately administered name space. This network identifier is the implicit qualifier of all resources which do not have an explicit network identifier.

This attribute specifies whether high performance routing (HPR) is supported on this link station. If this attribute is set to sameAsNode, and the hprSupport attribute in the APPN component is set to either rtp or anr, HPR will be negotiated with the remote node, if the hprSupport attrbute in the APPN component is set to no HPR will not be negotiated with the remote node. If this attribute is set to no, HPR will not be negotiated on this link station. The results of this negotiation are visible in the hprSupport attribute of the related LinkStation component Enumeration: 'sameAsNode': 1, 'no': 0.

This attribute specifies the node id of the adjacent device. This attribute, if non-zero, is used to check the identity of the adjacent device. If this attribute is zero, the identity is not checked. If adjacentCpType is set to dlurNoXID, this attribute is used to identify the downstream PU to the DLUS.

This attribute specifies whether this link station supports CP-CP sessions. This attribute is ignored if the adjacent device is not an APPN node. Enumeration: 'yes': 1, 'no': 0.

This attribute specifies the maximum basic transmission unit (BTU) size that can be sent on this link station. This attribute is used to negotiate the maximum BTU size that can be transmitted between a link station pair. If the link and node are HPR-capable, then this attribute must be set to a value greater than or equal to 768.

This attribute specifies the role for this link station. This attribute will be ignored if adjacentCpType is set to hostXID0 or hostXID3 (the link station will always be secondary), or if adjacentCpType is set to dlurXID or dlurNoXID (the link station will always be primary). Enumeration: 'primary': 1, 'negotiable': 0, 'secondary': 2.

This entry controls the addition and deletion of appnDlciSp components.

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

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

This variable represents the index for the appnDlciSp tables.

This group contains the provisionable attributes for the Data Link Connection Identifier. These attributes reflect the service parameters specific to this instance of Dlci.

An entry in the appnDlciSpParmsTable.

This attribute specifies whether rate enforcement is to be used on this DLCI. Turning on rate enforcement means that the data sent from the service to the virtual circuit is subjected to rate control. Enumeration: 'on': 1, 'off': 0.

This attribute specifies the committed information rate (cir) in bits per second (bit/s). When rateEnforcement is set to on, cir is the rate at which the network agrees to transfer information under normal conditions. This rate is measured over a measurement interval (t) that is determined internally based on cir and the committed burst size (bc). An exception to this occurs when cir is provisioned to be zero, in which case the measurement interval (t) must be provisioned explicitly. This attribute is ignored when rateEnforcement is off. If rateEnforcement is on and this attribute is 0, bc must also be 0.

This attribute specifies the committed burst size (bc) in bits. bc is the amount of data that a network agrees to transfer under normal conditions over a measurement interval (t). Data marked DE=1 is not accounted for in bc. This attribute is ignored when rateEnforcement is off. If rateEnforcement is on and this attribute is 0, cir must also be 0.

This attribute specifies the excess burst size (be) in bits. be is the amount of uncommitted data that the network will attempt to deliver over measurement interval (t). Data marked DE=1 by the user or by the network is accounted for here. cir, bc, and be cannot all be 0 when rateEnforcement is on.

This attribute specifies the time interval (in milliseconds) over which rates and burst sizes are measured. When cir and bc are 0 and rateEnforcement is on, this attribute must be provisioned. When cir and bc are non-zero, the time interval is internally calculated. In that situation, this attribute is ignored, and is not representative of the time interval. This attribute is also ignored when rateEnforcement is off. If rateEnforcement is on and both cir and bc are 0, this field must be non-zero.

This entry controls the addition and deletion of appnDlciBanLsDef components.

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

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

This variable represents an index for the appnDlciBanLsDef tables.

This variable represents an index for the appnDlciBanLsDef tables.

This group contains the provisioning data for a Link Station on a frame relay DLCI.

An entry in the appnDlciBanLsDefProvTable.

This attribute specifies which down stream physical unit service is supported on this Link Station. Enumeration: 'dlur': 2, 'none': 0.

This attribute specifies the fully qualified control point (FQCP) name of the adjacent node. This attribute is ignored if the adjacent node is not an APPN node. If this attribute is not empty it is checked against the name received from the adjacent node during the XID exchange, unless adjacentCpType is set to backLevelLenNode (in which case it is used to identify the adjacent node). The first portion of this name, up to the period, is the network identifier for the network to which the adjacent node belongs. An APPN network is a portion of a virtual private network which has a separately administered name space. This network identifier is the implicit qualifier of all resources which do not have an explicit network identifier.

This attribute specifies the adjacent control point (CP) type: networkNode - Specifies that the adjacent device is an APPN network node. endNode - Specifies that the adjacent device is an APPN end node. appnNode - Specifies that the adjacent device is an APPN node or an up-level LEN node, and the node type will be dynamically determined during XID exchange. backLevelLenNode - Specifies that the adjacent device is a back- level LEN node. hostXID3 - Specifies that the adjacent device is a host and that this APPN node should respond to a polling XID from the node with a format 3 XID. hostXID0 - Specifies that the adjacent device is a host and that this APPN node should respond to a polling XID from the node with a format 0 XID. dlurXID - Specifies that the adjacent device is a downstream PU requiring DLUR services and XID exchange in link activation dlurNoXID - Specifies that the adjacent device is a downstream PU requiring DLUR services and no XID exchange in link activation Enumeration: 'backLevelLenNode': 5, 'hostXID3': 6, 'hostXID0': 7, 'networkNode': 2, 'dlurNoXID': 9, 'endNode': 3, 'appnNode': 0, 'dlurXID': 8.

This attribute specifies the TG number to be used for this link. It is only relevant if the adjacent device is an APPN node and is ignored otherwise. If adjacentCpType is set to backLevelLenNode this attribute is ignored and the TG number is assumed to be 1. If this attribute is set to zero (0), the TG number is dynamically assigned and can be determined from the tgNum attribute of the related LinkStation component. If this attribute is non-zero, the adjacentCpType must be set to appnNode, networkNode, endNode or backLevelLenNode, and the TG number on the adjacent device must also be set to the same value.

This attribute specifies the fully qualified control point (FQCP) name of the primary DLUS for this link station. This attribute is ignored if the adjacent device does not request DLUR services. This attribute overrides the primaryDefDlusName and secondaryDefDlusName specified in the DLUR component. If this attribute is empty, the primaryDefDlusName (specified in the DLUR component), or secondaryDefDlusName (specified in the DLUR component) will be used. The first portion of this name, up to the period, is the network identifier for the network to which the DLUS node belongs. An APPN network is a portion of a virtual private network which has a separately administered name space. This network identifier is the implicit qualifier of all resources which do not have an explicit network identifier.

This attribute specifies the fully qualified control point (FQCP) name of the backup DLUS for this link station. This attribute is ignored if the adjacent device does not request DLUR services. This attribute overrides the primaryDefDlusName and secondaryDefDlusName specified in the DLUR component. If this attribute is empty and the dlusName attribute is empty, the primaryDefDlusName (specified in the DLUR component), or secondaryDefDlusName (specified in the DLUR component) will be used. If this attribute is specified, the dlusName attribute must also contain a non-empty string. The first portion of this name, up to the period, is the network identifier for the network to which the DLUS node belongs. An APPN network is a portion of a virtual private network which has a separately administered name space. This network identifier is the implicit qualifier of all resources which do not have an explicit network identifier.

This attribute specifies whether high performance routing (HPR) is supported on this link station. If this attribute is set to sameAsNode, and the hprSupport attribute in the APPN component is set to either rtp or anr, HPR will be negotiated with the remote node, if the hprSupport attrbute in the APPN component is set to no HPR will not be negotiated with the remote node. If this attribute is set to no, HPR will not be negotiated on this link station. The results of this negotiation are visible in the hprSupport attribute of the related LinkStation component Enumeration: 'sameAsNode': 1, 'no': 0.

This attribute specifies the node id of the adjacent device. This attribute, if non-zero, is used to check the identity of the adjacent device. If this attribute is zero, the identity is not checked. If adjacentCpType is set to dlurNoXID, this attribute is used to identify the downstream PU to the DLUS.

This attribute specifies whether this link station supports CP-CP sessions. This attribute is ignored if the adjacent device is not an APPN node. Enumeration: 'yes': 1, 'no': 0.

This attribute specifies the maximum basic transmission unit (BTU) size that can be sent on this link station. This attribute is used to negotiate the maximum BTU size that can be transmitted between a link station pair. If the link and node are HPR-capable, then this attribute must be set to a value greater than or equal to 768.

This attribute specifies the role for this link station. This attribute will be ignored if adjacentCpType is set to hostXID0 or hostXID3 (the link station will always be secondary), or if adjacentCpType is set to dlurXID or dlurNoXID (the link station will always be primary). Enumeration: 'primary': 1, 'negotiable': 0, 'secondary': 2.

This entry controls the addition and deletion of appnDlciBan components.

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

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

This variable represents the index for the appnDlciBan tables.

This group contains the provisioning data for the local link address (MAP,SAP pair) to be used for a Frame Relay connection with BAN encapsulation.

An entry in the appnDlciBanProvTable.

This attribute specifies the MAC address to be used for a Frame Relay connection with BAN encapsulation.

This attribute specifies the local SAP number to be used for a Frame Relay connection with BAN encapsulation.

This entry controls the addition and deletion of appnDlciCn components.

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

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

This variable represents the index for the appnDlciCn tables.

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

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 actual service parameters in use for this instance of Dlci.

An entry in the appnDlciSpOpTable.

This attribute indicates whether rate enforcement is in use for this Dlci. Enumeration: 'on': 1, 'off': 0.

This attribute indicates the current effective committed information rate (cir) in bits per second (bit/s). cir is the rate at which the network agrees to transfer data with Discard Eligiblity indication DE=0 under normal conditions. This attribute should be ignored when rateEnforcement is off.

This attribute indicates the committed burst size (bc) in bits. bc is the amount of data that the network agrees to transfer under normal conditions over a measurement interval (t). bc is used for data with Discard Eligibility indication DE=0. DE=1 data does not use bc at all, excessBurstSize if is used instead. This attribute should be ignored when rateEnforcement is off.

This attribute indicates the current effective excess information rate (eir) in bits per second (bit/s). eir is the rate at which the network agrees to transfer data with Discard Eligibility indication DE=1 under normal conditions. DE can be set by the user or the network. DE indication of a data frame is set to 1 by the network after cir has been exceeded while eir is still available for data transfer.

This attribute indicates the excess burst size (be) in bits. be is the amount of uncommitted data that the network will attempt to deliver over measurement interval (t). Data marked DE=1 by the user or by the network is accounted for here. This attribute should be ignored when rateEnforcement is off.

This attribute indicates the time interval (in milliseconds) over which rates and burst sizes are measured. This attribute should be ignored when rateEnforcement is off.

This entry controls the addition and deletion of appnLcn components.

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

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

This variable represents the index for the appnLcn tables.

This entry controls the addition and deletion of appnLcnDc components.

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

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

This variable represents the index for the appnLcnDc tables.

Options group defines attributes associated with direct call. It defines complete connection in terms of path and call options. This connection can be permanent (pvc) or switched (svc). It can have facilities. The total number of bytes of facilities including the facility codes, and all of the facility data from all of the four classes of facilities: CCITT_Facilities DTE_Facilities National_Facilities International_Facilities must not exceed 512 bytes.

An entry in the appnLcnDcOptionsTable.

RemoteNumbering Plan Indicator (Npi) indicates the numbering plan used in the remoteDna. Enumeration: 'e164': 1, 'x121': 0.

This attribute specifies the Data Network Address (Dna) of the remote. This is the called (destination) DTE address (Dna) to which this direct call will be sent. Initially, the called DTE address attribute must be present, that is, there must be a valid destination address. However, it may be possible in the future to configure the direct call with a mnemonic address, in which case, this attribute will contain a zero-length Dna, and the mnemonic address will be carried as one of the facilities.

This attribute specifies the transfer priority to network for the outgoing calls using this particular LCN. It overRides the defaultTransferPriority provisioned in its associated Dna component. The transfer priority is a preference specified by an application according to its delay-sensitivity requirement. Frames with high transfer priority are served by the network before the frames with normal priority. Each transfer priority contains a predetermined setting for trunk queue (interrupting, delay or throughput), and routing metric (delay or throughput). When the transfer priority is set at high, the trunk queue is set to high, the routing metric is set to delay. When the transfer priority is set at normal, the trunk queue is set to normal, the routing metric is set to throughput. The default of transferPriority is useDnaDefTP. It means using the provisioning value under defaultTransferPriority of its associated Dna for this DLCI. Enumeration: 'high': 9, 'useDnaDefTP': 255, 'normal': 0.

This attribute specifies the discard priority for outgoing call using this LCN. The discard priority has three provisioning values: normal, high, and useDnaDefPriority. Traffic with normal priority are discarded first than the traffic with high priority. The Dna default value (provisioned by outDefaultPriority) is taken if this attribute is set to the value useDnaDefPriority. The default of discardPriority is useDnaDefPriority. Enumeration: 'high': 1, 'useDnaDefPriority': 3, 'normal': 0.

This entry controls the addition and deletion of appnLcnVc components.

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

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

This variable represents the index for the appnLcnVc tables.

This group represents operational call data related to General Vc. It can be displayed only for General Vc which is created by application.

An entry in the appnLcnVcCadTable.

This attribute displays the type of call, pvc or svc. type is provided at provisioning time. Enumeration: 'pvc': 1, 'svc': 0.

This attribute displays the state of call control. P5 state is not supported but is listed for completness. Transitions from one state to another take very short time. state most often displayed is dataTransferP4. Enumeration: 'readyP1': 1, 'creating': 0, 'dteWaitingP2': 2, 'dceWaitingP3': 3, 'termination': 8, 'dataTransferP4': 4, 'dteClearRequestP6': 6, 'dceClearIndicationP7': 7, 'unsupportedP5': 5.

This attribute displays the previous state of call control. This is a valuable field to determine how the processing is progressing. Enumeration: 'readyP1': 1, 'creating': 0, 'dteWaitingP2': 2, 'dceWaitingP3': 3, 'termination': 8, 'dataTransferP4': 4, 'dteClearRequestP6': 6, 'dceClearIndicationP7': 7, 'unsupportedP5': 5.

This attribute displays the internal substate of call control. It is used to further refine state of call processing.

This attribute displays the internal substate of call control. It is used to further refine state of call processing.

This attribute displays the Numbering Plan Indicator (NPI) of the called end. Enumeration: 'e164': 1, 'x121': 0.

This attribute displays the Data Network Address (Dna) of the called (destination) DTE to which this call is sent. This address if defined at recieving end will complete Vc connection.

This attribute displays the Logical Channel Number of the called end. It is valid only after both ends of Vc exchanged relevant information.

This attribute displays the Numbering Plan Indicator (NPI) of the calling end. Enumeration: 'e164': 1, 'x121': 0.

This attribute displays the Data Network Address (Dna) of the calling end.

This attribute displays the Logical Channel Number of the calling end.

This attribute indicates that this optional section of accounting record is suppressed or permitted. If accountingEnabled is yes, conditions for generation of accounting record were met. These conditions include billing options, vc recovery conditions and Module wide accounting data options. Enumeration: 'yes': 0, 'no': 1.

This attribute displays that this is a fast select call. Enumeration: 'yes': 1, 'no': 0.

This attribute displays the locally negotiated size of send packets. Enumeration: 'n1024': 10, 'n64': 6, 'n16': 4, 'n256': 8, 'n4096': 12, 'unknown': 0, 'n512': 9, 'n128': 7, 'n2048': 11, 'n32': 5.

This attribute displays the locally negotiated size of send packets. Enumeration: 'n1024': 10, 'n64': 6, 'n16': 4, 'n256': 8, 'n4096': 12, 'unknown': 0, 'n512': 9, 'n128': 7, 'n2048': 11, 'n32': 5.

This attribute displays the send window size provided on incoming call packets or the default when a call request packet does not explicitly provide the window size.

This attribute displays the receive window size provided on incoming call packets or the default when a call request does not explicitly provide the window sizes.

This attribute displays the path reliability. Enumeration: 'high': 0, 'normal': 1.

This attribute indicates if this end should generate an accounting record. Normally, callingEnd is the end to generate an accounting record. Enumeration: 'calledEnd': 1, 'callingEnd': 0.

This attribute displays whether the call is a normal or a high priority call. Enumeration: 'high': 1, 'normal': 0.

This attribute displays the segment size (in bytes) used on the call. It is used to calculate the number of segments transmitted and received.

This attribute displays the locally negotiated size of the data packets on this Vc. Enumeration: 'n1024': 10, 'n64': 6, 'n16': 4, 'n256': 8, 'n4096': 12, 'unknown': 0, 'n512': 9, 'n128': 7, 'n2048': 11, 'n32': 5.

This attribute displays the current send window size of Vc.

This attribute displays the locally negotiated size of receive packets. Enumeration: 'n1024': 10, 'n64': 6, 'n16': 4, 'n256': 8, 'n4096': 12, 'unknown': 0, 'n512': 9, 'n128': 7, 'n2048': 11, 'n32': 5.

This attribute displays the receive window size provided on incoming call packets and to the default when a call request does not explicitly provide the window sizes.

This attribute displays the maximum packet size allowed on Vc.

This attribute displays the priority in which data is transferred to the network. The transfer priority is a preference specified by an application according to its delay-sensitivity requirement. Frames with high transfer priority are served by the network before the frames with normal priority. Each transfer priority contains a predetermined setting for trunk queue (interrupting, delay or throughput), and routing metric (delay or throughput). When the transfer priority is set at high, the trunk queue is set to high, the routing metric is set to delay. When the transfer priority is set at normal, the trunk queue is set to normal, the routing metric is set to throughput. Enumeration: 'high': 9, 'normal': 0.

This attribute displays the priority in which data is transferred from the network. The transfer priority is a preference specified by an application according to its delay-sensitivity requirement. Frames with high transfer priority are served by the network before the frames with normal priority. Each transfer priority contains a predetermined setting for trunk queue (interrupting, delay or throughput), and routing metric (delay or throughput). When the transfer priority is set at high, and the trunk queue is set to high, the routing metric is set to delay. When the transfer priority is set at normal, the trunk queue is set to normal, and the routing metric is set to throughput. Enumeration: 'high': 9, 'normal': 0.

This group defines display of interval data collected by Vc. Data in this group is variable and may depend on time when this display command is issued.

An entry in the appnLcnVcIntdTable.

This attribute displays the call reference number which is a unique number generated by the switch.The same Call Reference Number is stored in the interval data (accounting record) at both ends of the call. It can be used as one of the attributes in matching duplicate records generated at each end of the call.

This attribute displays the elapsed time representing the period of this interval data. It is elapsed time in 0.1 second increments since Vc started.

This attribute displays the number of segments received at the time command was issued. This is the segment received count maintained by accounting at each end of the Vc. This counter is updated only when the packet cannot be successfully delivered out of the sink Vc and to the sink AP Conditions in which packets may be discarded by the sink Vc include: missing packets due to subnet discards, segmentation protocol violations due to subnet discard, duplicated and out-of-ranged packets and packets that arrive while Vc is in path recovery state.

This attribute displays the number of segments sent at the time command was issued. This is the segment sent count maintained by accounting at the source Vc. Vc only counts packets that Vc thinks can be delivered successfully into the subnet. In reality, these packets may be dropped by trunking, for instance. This counter is not updated when splitting fails, when Vc is in a path recovery state, when packet forwarding fails to forward this packet and when subsequent packets have to be discarded as we want to minimize the chance of out-of-sequence and do not intentionally send out-of- sequenced packets into the subnet.

This attribute displays the start time of this interval period. If Vc spans 12 hour time or time of day change startTime reflects new time as recorded at 12 hour periods or time of day changes.

... Statistics(Stats) This group defines general attributes collected by general Vc. The purpose of Vc attributes is to aid end users and verification people to understand the Vc internal behavior. This is particularly useful when the network has experienced abnormality and we want to isolate problems and pinpoint trouble spots. Attributes are collected on a per Vc basis. Until a need is identified, statistics are not collected at a processor level. Each attribute is stored in a 32 bit field and is initialized to zero when a Vc enters into the data transfer state. When a PVC is disconnected and then connected again, the attributes will be reset. Attributes cannot be reset through other methods.

An entry in the appnLcnVcStatsTable.

This attribute counts the number of ack stacking timer expiries. It is used as an indicator of the acknowledgment behavior across the subnet when ack stacking is in effect. If it expires often, usually this means end users will experience longer delay. The ack stacking timer specifies how long the Vc will wait before finally sending the subnet acknowledgment. if this attribute is set to a value of 0, then the Vc will automatically return acknowledgment packets without delay. If this attribute is set to a value other than zero, then the Vc will wait for this amount of time in an attempt to piggyback the acknowledgment packet on another credit or data packet. If the Vc cannot piggyback the acknowledgment packet within this time, then the packet is returned without piggybacking.

This attribute counts the number of subnet frames discarded due to the sequence number being out of range. Two Categories apply for the General Vc 1) lost Acks (previous Range) 2) unexpected Packets (next Range) Vc internally maintains its own sequence number of packet order and sequencing. Due to packet retransmission, Vc may receive duplicate packets that have the same Vc internal sequence number. Only 1 copy is accepted by the Vc and other copies of the same packets are detected through this count. This attribute can be used to record the frequency of packet retransmission due to Vc and other part of the subnet.

This attribute counts the number of subnet packets discarded due to duplication. It is used to detect software error fault or duplication caused by retransmitting.

This attribute counts the number of frames which have retransmission time-out. If packets from Vc into the subnet are discarded by the subnet, the source Vc will not receive any acknowledgment. The retransmission timer then expires and packets will be retransmitted again. Note that the Vc idle probe may be retransmitted and is included in this count. This statistics does not show the distribution of how many times packets are retransmitted (e.g. first retransmission results in successful packet forwarding).

This attribute indicates the peak size of the retransmission queue. This attribute is used as an indicator of the acknowledgment behavior across the subnet. It records the largest body of unacknowledged packets.

This attribute indicates the peak size of the out of sequence queue. This attribute is used as an indicator of the sequencing behavior across the subnet. It records the largest body of out of sequence packets.

This attribute indicates the peak size of the sequence packet queue. This attribute is used as an indicator of the sequencing behavior across the subnet. It records the largest body of out of sequence packets, which by the receipt of an expected packet have been transformed to expected packets. The number of times this peak is reached is not recorded as it is traffic dependent.

This attribute indicates the peak size of wait acks. This attribute is used as an indicator of the acknowledgment behavior across the subnet. It records the largest collective acknowledgment.

This attribute counts the number of successful Vc recovery attempts. This attribute is used as an indicator of how many times the Vc path is broken but can be recovered. This attribute is useful to record the number of network path failures.

This attribute counts the number of window closures to subnet. A packet may have been sent into the subnet but its acknowledgment from the remote Vc has not yet been received. This is a 8 bit sequence number.This number is useful in detecting whether the Vc is sending any packet into the subnet.

This attribute counts the number of window closures from subnet. This attribute is useful in detecting whether the Vc is receiving any packet from the subnet.

This attribute displays the number of times the Vc stays within the W-R region. The W-R region is a value used to determined the timing of credit transmission. Should the current window size be beneath this value, the credits will be transmitted immediately. Otherwise, they will be transmitted later with actual data. The wrTriggers statistic is therefore used to analyze the flow control and credit mechanism.

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

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 TABLE CURRENTLY NOT IMPLEMENTED *** This entry controls the addition and deletion of appnPort components.

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

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

This variable represents the index for the appnPort tables.

*** THIS TABLE CURRENTLY NOT IMPLEMENTED *** Learned attributes of a SNA Port.

An entry in the appnPortConfigTable.

This attribute specifies the type of line used by the port. The possible values are: nonSwitched - switched - sharedAccessFacilities - Enumeration: 'sharedAccessFacilities': 3, 'nonSwitched': 1, 'switched': 2.

This is the maximum basic transmission unit (BTU) size that can be received. The BTU is the unit of data and control information passed between path control components.

This is the maximum basic transmission unit (BTU) size that can be sent. The BTU is the unit of data and control information passed between path control components.

This is the total link activation limit. This is the maximum number of active adjacent link stations the port will support. This value limits the number of adjacent link stations that can be concurrently connected to the local node through this port. The limit includes adjacent link stations connected by both inbound and outbound link activations. The distinction of inbound or outbound for link activations is used to indicate which node initiated the connection. For inbound link activations, the adjacent link station initiates the connection with the local link station. For outbound link activations, the local node initiates the connection with the adjacent link station. totLinkActLim must be greater than either inbLinkActLim or outLinkActLim, but it should not greater than the sum of inbLinkActLim and outLinkActLim.

This is the inbound link activation limit. This is the maximum number of link stations which can be simultaneously active as a result of connection initiations from adjacent nodes.

This is the outbound link activation limit. This is the maximum number of link stations which can be simultaneously active as a result of connection initiations by the local node.

This is the initial role of the port's local link station when communicating with an adjacent link station. The possible options are negotiable, primary and secondary. Enumeration: 'primary': 1, 'negotiable': 3, 'secondary': 2.

This is the exchange limit for activation XIDs.

This is the exchange limit for non-activation XIDs.

This is Link Station transmit/receive capability. This is either tws (two-way simultaneous (full-duplex)) or twa (two-way alternate (half-duplex)). Enumeration: 'tws': 1, 'twa': 0.

This is the maximum number of I-frames that can be received by the local link stations before an acknowledgment is sent.

This is the desired pacing window size for BINDs on this transmission group. The number is significant only when fixed BIND pacing is being performed.

*** THIS TABLE CURRENTLY NOT IMPLEMENTED *** Operational attributes of a SNA Port.

An entry in the appnPortOperTable.

The attribute represents the current operational state of the port. The value can be any of the following: inactive - pendingActive - active - pendingInactive - Enumeration: 'active': 3, 'pendingInactive': 4, 'pendingActive': 2, 'inactive': 1.

Type of the DLC interface used by this port. Possible values are: sdlc - synchronous data link control x25 - QLLC logical link control tokenRing - IEEE 802.2 logical link control frameRelay - RFC1490 and IEEE 802.2 logical link control other - dlc type other than those listed above. Enumeration: 'tokenRing': 6, 'x25': 31, 'other': 1, 'frameRelay': 30, 'sdlc': 2.

This attribute indicates whether Set Initialization Mode (SIM) and Receive Initialization Mode (RIM) are supported. Enumeration: 'yes': 1, 'no': 2.

This is the total number of successful XIDs that have been received on all of the defined link stations on this port since the last time this port was started.

This attributes contains the total number of unsuccessful XIDs that have been received on all of the defined link stations on this port since the last time this port was started.

This is the total number of successful XIDs that have been received on all of the dynamic link stations on this port since the last time this port was started.

This is the total number of unsuccessful XIDs that have been received on all of the dynamic link stations on this port since the last time this port was started.

*** THIS TABLE CURRENTLY NOT IMPLEMENTED *** These attributes of the link station are in a group using a common structure. This set provides the TG characteristics of the link through this link station for route selection.

An entry in the appnPortTgCharTable.

The effective capacity is an integer value that indicates the capacity in kilo bits per second. It is derived from the link bandwidth and the maximum load factor with the range of 0 thru 603,979,776. Enumeration: 'n940Mbps': 180, 'n2500Mbps': 192, 'n64Mbps': 149, 'n88Mbps': 153, 'n1900Mbps': 188, 'n45Gbps': 225, 'n510Mbps': 173, 'n19Gbps': 215, 'n6000bps': 42, 'n141Gbps': 238, 'n310Mbps': 168, 'n190kbps': 82, 'n280Gbps': 246, 'n70Gbps': 230, 'n29kbps': 60, 'n240Gbps': 244, 'n28Gbps': 219, 'n18kbps': 55, 'n34Mbps': 142, 'n1000kbps': 101, 'n44Mbps': 145, 'n230bps': 4, 'n550Mbps': 174, 'n920kbps': 100, 'n128Mbps': 157, 'n62kbps': 69, 'n560Gbps': 254, 'n2500kbps': 112, 'n260Gbps': 245, 'n410bps': 11, 'n8400bps': 46, 'n1080kbps': 102, 'n18Mbps': 135, 'n320Gbps': 248, 'n13800Mbps': 211, 'n9800kbps': 128, 'n380kbps': 90, 'n190bps': 2, 'n630Mbps': 176, 'n2000bps': 29, 'n690kbps': 97, 'n32Mbps': 141, 'n134kbps': 78, 'n540kbps': 94, 'n69Mbps': 150, 'n2200Mbps': 190, 'n74Mbps': 151, 'n180Gbps': 241, 'n6100kbps': 122, 'n16Mbps': 133, 'n770kbps': 98, 'n36kbps': 63, 'n12000bps': 50, 'n25Gbps': 218, 'n210bps': 3, 'n81Gbps': 232, 'n8600kbps': 126, 'n250kbps': 85, 'n480Gbps': 252, 'n35Gbps': 222, 'n118Mbps': 156, 'n77kbps': 72, 'n170bps': 1, 'n18Gbps': 214, 'n170kbps': 81, 'n840kbps': 99, 'n1700bps': 27, 'n12300kbps': 130, 'n53kbps': 67, 'n3900bps': 37, 'n10100Mbps': 208, 'n3300bps': 35, 'n1230kbps': 104, 'n138Mbps': 158, 'n1260Mbps': 184, 'n980bps': 21, 'n49Mbps': 146, 'n1380kbps': 105, 'n4000kbps': 117, 'n26kbps': 59, 'n900bps': 20, 'n4200bps': 38, 'n500kbps': 93, 'n380bps': 10, 'n25Mbps': 138, 'n340bps': 9, 'n440Gbps': 251, 'n3100kbps': 114, 'n4300kbps': 118, 'n310kbps': 88, 'n91Gbps': 233, 'n96kbps': 74, 'n2300kbps': 111, 'n280bps': 7, 'n260Mbps': 165, 'n67kbps': 70, 'n160Gbps': 240, 'n2100bps': 30, 'n1700kbps': 107, 'n43kbps': 65, 'n2800kbps': 113, 'n1540kbps': 106, 'n15100Mbps': 212, 'n1800bps': 28, 'n2700bps': 33, 'n1500bps': 26, 'n15600bps': 53, 'n2400Mbps': 191, 'n1150kbps': 103, 'n106kbps': 75, 'n1420Mbps': 185, 'n600bps': 16, 'n750bps': 18, 'n210kbps': 83, 'n520Gbps': 253, 'n2200kbps': 110, 'n98Mbps': 154, 'n300bps': 8, 'n790Mbps': 178, 'n200Mbps': 162, 'n2800Mbps': 193, 'n131Gbps': 237, 'n14400bps': 52, 'n240bps': 5, 'n560bps': 15, 'n290Mbps': 167, 'n1200bps': 24, 'n30Gbps': 220, 'n7200bps': 44, 'n5700Mbps': 201, 'n59Mbps': 148, 'n157Mbps': 160, 'n7400kbps': 124, 'n55Gbps': 227, 'n4100Mbps': 197, 'n37Mbps': 143, 'n3000bps': 34, 'n3800Mbps': 196, 'n3600bps': 36, 'n4800bps': 40, 'n230kbps': 84, 'n8200Mbps': 205, 'n4500bps': 39, 'n280Mbps': 166, 'n40Gbps': 224, 'n530bps': 14, 'n8000kbps': 125, 'n1700Mbps': 187, 'n9200kbps': 127, 'n710Mbps': 177, 'n4400Mbps': 198, 'n1020Mbps': 181, 'n490bps': 13, 'n600Gbps': 255, 'n5500kbps': 121, 'n86kbps': 73, 'n300Gbps': 247, 'n2000Mbps': 189, 'n580kbps': 95, 'n54Mbps': 147, 'n111Gbps': 235, 'n4900kbps': 120, 'n108Mbps': 155, 'n121Gbps': 236, 'n1130bps': 23, 'n610kbps': 96, 'n16Gbps': 213, 'n20Mbps': 136, 'n33Gbps': 221, 'n220Gbps': 243, 'n420kbps': 91, 'n7800bps': 45, 'n290kbps': 87, 'n125kbps': 77, 'n180Mbps': 161, 'n6900Mbps': 203, 'n3500Mbps': 195, 'n470Mbps': 172, 'n240Mbps': 164, 'n60Gbps': 228, 'n22Mbps': 137, 'n154kbps': 80, 'n14700kbps': 132, 'n4600kbps': 119, 'n39Mbps': 144, 'n22kbps': 57, 'n9000bps': 47, 'n17Mbps': 134, 'n8800Mbps': 206, 'n350Mbps': 169, 'n220Mbps': 163, 'n72kbps': 71, 'n11300Mbps': 209, 'n79Mbps': 152, 'n9600bps': 48, 'n50Gbps': 226, 'n400Gbps': 250, 'n151Gbps': 239, 'n680bps': 17, 'n6800kbps': 123, 'n830bps': 19, 'n75Gbps': 231, 'n101Gbps': 234, 'n260bps': 6, 'n3100Mbps': 194, 'n11100kbps': 129, 'n38Gbps': 223, 'n65Gbps': 229, 'n6600bps': 43, 'n12600Mbps': 210, 'n34kbps': 62, 'min': 0, 'n6300Mbps': 202, 'n390Mbps': 170, 'n1180Mbps': 183, 'n430Mbps': 171, 'n31kbps': 61, 'n24kbps': 58, 'n460kbps': 92, 'n13500kbps': 131, 'n5000Mbps': 200, 'n1050bps': 22, 'n147Mbps': 159, 'n360Gbps': 249, 'n3400kbps': 115, 'n23Gbps': 217, 'n2000kbps': 109, 'n1350bps': 25, 'n19kbps': 56, 'n200Gbps': 242, 'n2400bps': 32, 'n38kbps': 64, 'n5400bps': 41, 'n20Gbps': 216, 'n350kbps': 89, 'n450bps': 12, 'n2300bps': 31, 'n29Mbps': 140, 'n590Mbps': 175, 'n4700Mbps': 199, 'n870Mbps': 179, 'n7500Mbps': 204, 'n1570Mbps': 186, 'n13200bps': 51, 'n115kbps': 76, 'n27Mbps': 139, 'n144kbps': 79, 'n1100Mbps': 182, 'n3700kbps': 116, 'n1800kbps': 108, 'n17kbps': 54, 'n48kbps': 66, 'n10800bps': 49, 'n58kbps': 68, 'n270kbps': 86, 'n9400Mbps': 207.

The cost-per-connect time is a characteristic represented by a single-byte value in the range 0 to 255 that expresses a relative cost of using a transmission group. The units for cost-per-connect time are installation-defined and are typically based on the applicable tariffs of the transmission facility being used by the transmission group. The cost-per-connect time values that a network administrator assigns to the transmission groups in a network should reflect the relative expense of each transmission group as compared to all other transmission groups in the network. A value of 0 means that the cost of connecting over the transmission group is at no additional cost (as in the case of a non-switched facility.

Cost-per-byte is a single byte value in the range 0 to 255 that expresses a relative cost of transmitting a byte over the associated transmission group. The units for cost-per-byte are user-defined. Like cost-per-connect-time, cost-per-byte is network specific and will not be uniform across networks unless assignments are coordinated.

This static characteristic indicates the level of security protection. The security values are architecturally defined to provide continuity across all networks. Currently, security is encoded as one of the following seven values: guardedRadiation - guarded conduit containing the transmission medium; protected against physical and radiation tapping. encrypted - link level encryption is provided unknown - has not been determined guardedConduit - guarded conduit; protected against physical tapping secureConduit - secure conduit, not guarded; e.g. pressurized pipe undergroundCable - underground cable located in a secure country publicSwitchedNetwork - public switched network; secure in the sense that there is no predetermined route that traffic will take nonSecure - all else, e.g. satellite-connected, located in a nonsecure country. Enumeration: 'guardedRadiation': 192, 'guardedConduit': 128, 'unKnown': 0, 'undergroundCable': 64, 'encrypted': 160, 'publicSwitchedNetwork': 32, 'secureConduit': 96, 'nonSecure': 1.

The propagation delay is the length of time that it takes for a signal to propagate from one end of the transmission group to the other. Typical values are: minimum - minimum negligible - 400 microsec terrestrial - 10 msec packetSwitched - 150 msec long - 300 msec Enumeration: 'terrestrial': 113, 'packetSwitched': 145, 'minimum': 0, 'negligible': 76, 'long': 153.

This is the user defined routing parameter in range 0-255.

This is the user defined routing parameter in range 0-255.

This is the user defined routing parameter in range 0-255.

*** THIS TABLE CURRENTLY NOT IMPLEMENTED *** This entry controls the addition and deletion of appnLs components.

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

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

This variable represents the index for the appnLs tables.

*** THIS TABLE CURRENTLY NOT IMPLEMENTED *** This identifies which physical interface is associated with this link station.

An entry in the appnLsLsVcReferenceTable.

This string identifies which physical interface the link station is associated with.

This attribute indicates the SAP number of the device assigned to this link station. This field is only valid for dlcType of llc2. If the dlcType is not llc2, this field will be 0.

*** THIS TABLE CURRENTLY NOT IMPLEMENTED *** This group contains the attributes that define the behavior of a SNA link station.

An entry in the appnLsConfigTable.

This attribute contains the name of the port associated with this link station.

Various optional features of a link station. autoActSupp If present specifies that the link can be activated automatically when required by a session. A link cannot be automatically activated from an independent LU session unless it has been started previously. The link cannot be defined to support CP-CP sessions and to be auto-activatable because this might cause inconsistent network behavior. limitedResource If present, specifies that this link station is to be deactivated when there are no sessions using the link. Note that link stations on a non- switched port cannot be configured as limited resource. backLvlLenEn If present, specifies that this link is to a back level LEN End Node. cpCpSessSupport If present, specifies that CP-CP sessions are supported by this link station. Description of bits: autoActSupp(0) limitedResource(1) backLvlLenEn(2) cpCpSessSupport(3)

This is the maximum basic transmission unit (BTU) size that can be sent. The BTU is the unit of data and control information passed between path control components.

*** THIS TABLE CURRENTLY NOT IMPLEMENTED *** Operational data of the link station.

An entry in the appnLsOperTable.

This attribute indicates the type of data link control that this LS is associated. Possible types are: sdlc - synchronous data link control x25 - QLLC logical link control tokenRing - IEEE 802.2 logical link control llc2 - RFC1490 and IEEE 802.2 logical link control. other - dlc type other than those listed above. Enumeration: 'tokenRing': 6, 'x25': 31, 'other': 1, 'sdlc': 2, 'llc2': 30.

This the current state of the link station. The possible values are: inactive - active - pendingActive - pendingInactive - Enumeration: 'active': 3, 'pendingInactive': 4, 'pendingActive': 2, 'inactive': 1.

This is the current sub-state of the link station. The possible values are: inactive, sentReqOpnstn, pendXidExch, sentActAs, sendSetMode, active, sentDeactAsOrd, sentDiscOrd, sentDestroyTg, sentCreateTg, sentConnReq,pendRcvConnInd, pendSendConnRsp, sentConnRsp, pendDeact. These are described in the APPN Architecture reference Enumeration: 'pendRcvConnInd': 12, 'sentConnRsp': 14, 'sentDestroyTg': 9, 'pendXidExch': 3, 'sentDeactAsOrd': 7, 'sentReqOpnstn': 2, 'sentActAs': 4, 'sentDiscOrd': 8, 'sentConnReq': 11, 'sentSentMode': 5, 'inactive': 1, 'pendSendConnRsp': 13, 'active': 6, 'sentCreateTg': 10, 'pendDeact': 15.

This is the total number of active sessions (both endpoint and intermediate) using this link.

This is the actual network qualified adjacent control point (CP) name as determined from the XID 3 exchange.

This is the actual type of adjacent node type as determined during contact negotiation. The possible types are: endNode lowEntryNode networkNode toBeDetermine Enumeration: 'endNode': 2, 'toBeDetermined': 0, 'networkNode': 1, 'lowEntryNode': 4.

This is the name of the port group associated with the port through which this link station is attached.

This attribute reflects whether the link was created explicitly or dynamically (either in response to a connection request from the adjacent node, or to connect dynamically to another node across a connection network). The possible values are dynamic or defined. Enumeration: 'defined': 2, 'dynamic': 1.

This attribute specifies whether the adjacent node is a migration level node, such as a low entry networking or LEN node. Enumeration: 'unknown': 3, 'yes': 1, 'no': 2.

This is the number associated with the transmission group using this link station. It can be used to distinguish it from other transmission groups to the same adjacent node.

This is the type of High Performance Routing (HPR) being used on this link station. It is one of anr, rtp or none. The value in this attribute are bounded by the values provisioned on this node and the attached node. Enumeration: 'none': 0, 'rtp': 2, 'anr': 1.

This is the HPR ANR label associated with this link station.

*** THIS TABLE CURRENTLY NOT IMPLEMENTED *** These attributes of the link station are in a group using a common structure. This set provides the TG characteristics of the link through this link station for route selection.

An entry in the appnLsTgCharTable.

The effective capacity is an integer value that indicates the capacity in kilo bits per second. It is derived from the link bandwidth and the maximum load factor with the range of 0 thru 603,979,776. Enumeration: 'n940Mbps': 180, 'n2500Mbps': 192, 'n64Mbps': 149, 'n88Mbps': 153, 'n1900Mbps': 188, 'n45Gbps': 225, 'n510Mbps': 173, 'n19Gbps': 215, 'n6000bps': 42, 'n141Gbps': 238, 'n310Mbps': 168, 'n190kbps': 82, 'n280Gbps': 246, 'n70Gbps': 230, 'n29kbps': 60, 'n240Gbps': 244, 'n28Gbps': 219, 'n18kbps': 55, 'n34Mbps': 142, 'n1000kbps': 101, 'n44Mbps': 145, 'n230bps': 4, 'n550Mbps': 174, 'n920kbps': 100, 'n128Mbps': 157, 'n62kbps': 69, 'n560Gbps': 254, 'n2500kbps': 112, 'n260Gbps': 245, 'n410bps': 11, 'n8400bps': 46, 'n1080kbps': 102, 'n18Mbps': 135, 'n320Gbps': 248, 'n13800Mbps': 211, 'n9800kbps': 128, 'n380kbps': 90, 'n190bps': 2, 'n630Mbps': 176, 'n2000bps': 29, 'n690kbps': 97, 'n32Mbps': 141, 'n134kbps': 78, 'n540kbps': 94, 'n69Mbps': 150, 'n2200Mbps': 190, 'n74Mbps': 151, 'n180Gbps': 241, 'n6100kbps': 122, 'n16Mbps': 133, 'n770kbps': 98, 'n36kbps': 63, 'n12000bps': 50, 'n25Gbps': 218, 'n210bps': 3, 'n81Gbps': 232, 'n8600kbps': 126, 'n250kbps': 85, 'n480Gbps': 252, 'n35Gbps': 222, 'n118Mbps': 156, 'n77kbps': 72, 'n170bps': 1, 'n18Gbps': 214, 'n170kbps': 81, 'n840kbps': 99, 'n1700bps': 27, 'n12300kbps': 130, 'n53kbps': 67, 'n3900bps': 37, 'n10100Mbps': 208, 'n3300bps': 35, 'n1230kbps': 104, 'n138Mbps': 158, 'n1260Mbps': 184, 'n980bps': 21, 'n49Mbps': 146, 'n1380kbps': 105, 'n4000kbps': 117, 'n26kbps': 59, 'n900bps': 20, 'n4200bps': 38, 'n500kbps': 93, 'n380bps': 10, 'n25Mbps': 138, 'n340bps': 9, 'n440Gbps': 251, 'n3100kbps': 114, 'n4300kbps': 118, 'n310kbps': 88, 'n91Gbps': 233, 'n96kbps': 74, 'n2300kbps': 111, 'n280bps': 7, 'n260Mbps': 165, 'n67kbps': 70, 'n160Gbps': 240, 'n2100bps': 30, 'n1700kbps': 107, 'n43kbps': 65, 'n2800kbps': 113, 'n1540kbps': 106, 'n15100Mbps': 212, 'n1800bps': 28, 'n2700bps': 33, 'n1500bps': 26, 'n15600bps': 53, 'n2400Mbps': 191, 'n1150kbps': 103, 'n106kbps': 75, 'n1420Mbps': 185, 'n600bps': 16, 'n750bps': 18, 'n210kbps': 83, 'n520Gbps': 253, 'n2200kbps': 110, 'n98Mbps': 154, 'n300bps': 8, 'n790Mbps': 178, 'n200Mbps': 162, 'n2800Mbps': 193, 'n131Gbps': 237, 'n14400bps': 52, 'n240bps': 5, 'n560bps': 15, 'n290Mbps': 167, 'n1200bps': 24, 'n30Gbps': 220, 'n7200bps': 44, 'n5700Mbps': 201, 'n59Mbps': 148, 'n157Mbps': 160, 'n7400kbps': 124, 'n55Gbps': 227, 'n4100Mbps': 197, 'n37Mbps': 143, 'n3000bps': 34, 'n3800Mbps': 196, 'n3600bps': 36, 'n4800bps': 40, 'n230kbps': 84, 'n8200Mbps': 205, 'n4500bps': 39, 'n280Mbps': 166, 'n40Gbps': 224, 'n530bps': 14, 'n8000kbps': 125, 'n1700Mbps': 187, 'n9200kbps': 127, 'n710Mbps': 177, 'n4400Mbps': 198, 'n1020Mbps': 181, 'n490bps': 13, 'n600Gbps': 255, 'n5500kbps': 121, 'n86kbps': 73, 'n300Gbps': 247, 'n2000Mbps': 189, 'n580kbps': 95, 'n54Mbps': 147, 'n111Gbps': 235, 'n4900kbps': 120, 'n108Mbps': 155, 'n121Gbps': 236, 'n1130bps': 23, 'n610kbps': 96, 'n16Gbps': 213, 'n20Mbps': 136, 'n33Gbps': 221, 'n220Gbps': 243, 'n420kbps': 91, 'n7800bps': 45, 'n290kbps': 87, 'n125kbps': 77, 'n180Mbps': 161, 'n6900Mbps': 203, 'n3500Mbps': 195, 'n470Mbps': 172, 'n240Mbps': 164, 'n60Gbps': 228, 'n22Mbps': 137, 'n154kbps': 80, 'n14700kbps': 132, 'n4600kbps': 119, 'n39Mbps': 144, 'n22kbps': 57, 'n9000bps': 47, 'n17Mbps': 134, 'n8800Mbps': 206, 'n350Mbps': 169, 'n220Mbps': 163, 'n72kbps': 71, 'n11300Mbps': 209, 'n79Mbps': 152, 'n9600bps': 48, 'n50Gbps': 226, 'n400Gbps': 250, 'n151Gbps': 239, 'n680bps': 17, 'n6800kbps': 123, 'n830bps': 19, 'n75Gbps': 231, 'n101Gbps': 234, 'n260bps': 6, 'n3100Mbps': 194, 'n11100kbps': 129, 'n38Gbps': 223, 'n65Gbps': 229, 'n6600bps': 43, 'n12600Mbps': 210, 'n34kbps': 62, 'min': 0, 'n6300Mbps': 202, 'n390Mbps': 170, 'n1180Mbps': 183, 'n430Mbps': 171, 'n31kbps': 61, 'n24kbps': 58, 'n460kbps': 92, 'n13500kbps': 131, 'n5000Mbps': 200, 'n1050bps': 22, 'n147Mbps': 159, 'n360Gbps': 249, 'n3400kbps': 115, 'n23Gbps': 217, 'n2000kbps': 109, 'n1350bps': 25, 'n19kbps': 56, 'n200Gbps': 242, 'n2400bps': 32, 'n38kbps': 64, 'n5400bps': 41, 'n20Gbps': 216, 'n350kbps': 89, 'n450bps': 12, 'n2300bps': 31, 'n29Mbps': 140, 'n590Mbps': 175, 'n4700Mbps': 199, 'n870Mbps': 179, 'n7500Mbps': 204, 'n1570Mbps': 186, 'n13200bps': 51, 'n115kbps': 76, 'n27Mbps': 139, 'n144kbps': 79, 'n1100Mbps': 182, 'n3700kbps': 116, 'n1800kbps': 108, 'n17kbps': 54, 'n48kbps': 66, 'n10800bps': 49, 'n58kbps': 68, 'n270kbps': 86, 'n9400Mbps': 207.

The cost-per-connect time is a characteristic represented by a single-byte value in the range 0 to 255 that expresses a relative cost of using a transmission group. The units for cost-per-connect time are installation-defined and are typically based on the applicable tariffs of the transmission facility being used by the transmission group. The cost-per-connect time values that a network administrator assigns to the transmission groups in a network should reflect the relative expense of each transmission group as compared to all other transmission groups in the network. A value of 0 means that the cost of connecting over the transmission group is at no additional cost (as in the case of a non-switched facility.

Cost-per-byte is a single byte value in the range 0 to 255 that expresses a relative cost of transmitting a byte over the associated transmission group. The units for cost-per-byte are user-defined. Like cost-per-connect-time, cost-per-byte is network specific and will not be uniform across networks unless assignments are coordinated.

This static characteristic indicates the level of security protection. The security values are architecturally defined to provide continuity across all networks. Currently, security is encoded as one of the following seven values: guardedRadiation - guarded conduit containing the transmission medium; protected against physical and radiation tapping. encrypted - link level encryption is provided unknown - has not been determined guardedConduit - guarded conduit; protected against physical tapping secureConduit - secure conduit, not guarded; e.g. pressurized pipe undergroundCable - underground cable located in a secure country publicSwitchedNetwork - public switched network; secure in the sense that there is no predetermined route that traffic will take nonSecure - all else, e.g. satellite-connected, located in a nonsecure country. Enumeration: 'guardedRadiation': 192, 'guardedConduit': 128, 'unKnown': 0, 'undergroundCable': 64, 'encrypted': 160, 'publicSwitchedNetwork': 32, 'secureConduit': 96, 'nonSecure': 1.

The propagation delay is the length of time that it takes for a signal to propagate from one end of the transmission group to the other. Typical values are: minimum - minimum negligible - 400 microsec terrestrial - 10 msec packetSwitched - 150 msec long - 300 msec Enumeration: 'terrestrial': 113, 'packetSwitched': 145, 'minimum': 0, 'negligible': 76, 'long': 153.

This is the user defined routing parameter in range 0-255.

This is the user defined routing parameter in range 0-255.

This is the user defined routing parameter in range 0-255.

*** THIS TABLE CURRENTLY NOT IMPLEMENTED *** This group contains the operational statistics of the link station.

An entry in the appnLsStatsTable.

This attribute counts the total number of XID bytes received on this link station.

This attribute counts the total number of message (I-frame) bytes received on this link station.

This attribute counts the total number of XID frames received on this link station.

This attribute counts the total number of message (I-frame) frames received on this link station.

This attribute counts the total number of XID bytes sent on this link station.

This attribute counts the total number of message (I-frame) bytes sent on this link station.

This attribute counts the total number of XID frames sent on this link station.

This attribute counts the total number of message (I-frame) frames sent on this link station.

This attribute counts the total number of invalid SNA frames received on this link station.

This attribute counts the total number of session control frames received on this link station.

This attribute counts the total number of session control frames sent on this link station.

This attribute counts the total number of echo responses returned from the adjacent node. A response should be returned for each test frame sent by this node. Echo requests are sent periodically to gauge the propagation delay to the adjacent node.

This attribute counts the time (in milliseconds) that it took for the last test signal to be sent and returned from this link station to the adjacent link station.

This is the longest time taken (in milliseconds) for a test signal to be sent and returned from this link station to the adjacent link station.

This is the shortest time taken (in milliseconds) for a test signal to be sent and returned from this link station to the adjacent link station.

This attribute contains the total number of successful XIDs that have been received on this link station since it was started.

This attribute contains the total number of unsuccessful XIDs that have been received on this link station since it was started.

*** THIS TABLE CURRENTLY NOT IMPLEMENTED *** This entry controls the addition and deletion of appnDirEnt components.

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

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

This variable represents the index for the appnDirEnt tables.

*** THIS TABLE CURRENTLY NOT IMPLEMENTED *** This group defines the attributes of the Directory Entry server.

An entry in the appnDirEntOperTable.

The fully-qualified control point (CP) name of the network node server. For unassociated end node entries, the end node fully- qualified name is returned.

It is the fully-qualified CP name of the node at which the LU is located. This name is the same as the serving NN name when the LU is located at a network node or an unassociated end node. It is also the same as the fully-qualified LU name when this is the control point LU for this node.

Specifies the location of the resource. This may be one of the following: The resource is at the local node. The resource belongs to an attached end node. The resource is not within the domain of the local node. Enumeration: 'domain': 1, 'xdomain': 2, 'local': 0.

Specifies whether the type of the directory entry is: cache - The LU has previously been located by a broadcast search and the location information has been saved. home - The LU is in the domain of the local network node and the LU information has been configured at the local node. register - The LU is at an end node that is in the domain of the local network node. Registered entries are registered by the served end node. Enumeration: 'home': 3, 'cache': 0, 'register': 2.

It indicates the type of wildcard used for the resources used for LEN node. Enumeration: 'fullWildcard': 4, 'other': 1, 'explicit': 2, 'partialWildcard': 3.

*** THIS TABLE CURRENTLY NOT IMPLEMENTED *** This entry controls the addition and deletion of appnAdjNn components.

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

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

This variable represents the index for the appnAdjNn tables.

*** THIS TABLE CURRENTLY NOT IMPLEMENTED *** These operational attributes are only available for network nodes which are directly attached to the current node. They are in a separate group.

An entry in the appnAdjNnOperTable.

Indicates the state of CP-CP sessions between this node and adjacent network and end nodes. Inactive indicates no CP-CP sessions exists between this node and the adjacent node. Active indicates CP-CP sessions are active using both the ConWinner and ConLoser sessions. The session initiated by this node is referred to as the ConWinner session and is used by this node to send to the adjacent node. The ConLoser session is initiated by the adjacent node and is used by this node to receive from the adjacent node. Enumeration: 'active': 1, 'conWinnerActive': 3, 'conLoserActive': 2, 'inactive': 4.

Number of out of sequence topology database updates (TDU) received from this node.

Flow reduction sequence numbers (FRSNs) are associated with Topology Database Updates (TDUs) and are unique only within each APPN network node. A TDU can be associated with multiple APPN resources. This FRSN indicates the last TDU sent to this adjacent node.

Flow reduction sequence numbers (FRSNs) are associated with Topology Database Updates (TDUs) and are unique only within each APPN network node. A TDU can be associated with multiple APPN resources. This FRSN indicates the last TDU received from this adjacent node.

*** THIS TABLE CURRENTLY NOT IMPLEMENTED *** This entry controls the addition and deletion of appnNn components.

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

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

This variable represents the index for the appnNn tables.

*** THIS TABLE CURRENTLY NOT IMPLEMENTED *** Operational attributes of a network node in the topology database.

An entry in the appnNnOperTable.

The number of days before deletion of this node entry from the Topology Database. This is set to zero for the local node entry, which always exists.

Type of the APPN node. Possible values are networkNode (nn) and virtualRoutingNode (vrn). Enumeration: 'virtualRoutingNode': 3, 'toBeDetermined': 0, 'networkNode': 1.

Resource sequence number. This is assigned by the network node that owns this resource.

Route addition resistance indicates the relative desirability of using this node for intermediate session traffic. This value is used for route computation. The lower the value, the more desirable the node is for intermediate routing.

This attribute specifies the status of the node. This may be one or more of the following: congested - If present, indicates that this node is congested. This node is not be included in route selection by other nodes when this congestion exists. irrDepleted - If present, indicates that intermediate session routing resources are depleted. This node is not included in intermediate route selection by other nodes when resources are depleted. SNMP APPN MIB = ibmappnNnNodeIsrDepleted errDepleted - If present, indicates that session endpoint resources are depleted. quiescing - If present, indicates that the node is quiescing. This node is not included in route selection by other nodes when the node is quiescing. Description of bits: congested(0) irrDepleted(1) errDepleted(2) quiescing(3)

This attribute specifies which functions are supported. This may be one or more of the following: borderNode - If present, indicates that border node functionality is supported. centralDirectoryServer -If present, indicates that the node is a central directory. gateway - If present, indicates that the node provides gateway functions. isr - If present, indicates that the node supports intermediate session routing. Description of bits: notused0(0) gateway(1) centralDirectoryServer(2) hpr(3) rtp(4) isr(5) borderNode(6)

*** THIS TABLE CURRENTLY NOT IMPLEMENTED *** This entry controls the addition and deletion of appnLocTg components.

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

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

This variable represents an index for the appnLocTg tables.

This variable represents an index for the appnLocTg tables.

*** THIS TABLE CURRENTLY NOT IMPLEMENTED *** Gives the operational status of the local node transmission group.

An entry in the appnLocTgOperTable.

Status of the transmission group can be one of operational, CpCpSession or quiescing. Description of bits: notused0(0) notused1(1) notused2(2) notused3(3) cpCpSession(4) quiescing(5) notused6(6) operational(7)

This attribute contains the resource sequence number.

*** THIS TABLE CURRENTLY NOT IMPLEMENTED *** Contains the attribute for destination address.

An entry in the appnLocTgLinkAddressTable.

This attribute contains specific data related to the link connection. Token-Ring - contains MAC/SAP X.25 Switched - contains dial digits X.21 Switched - contains dial digits Circuit Switched - contains dial digits Frame-Relay - contains DLCI and SAP The value will be set to zero if the destination node type is not a virtual routing node.

*** THIS TABLE CURRENTLY NOT IMPLEMENTED *** These attributes of the link station are in a group using a common structure. This set provides the TG characteristics of the link through this link station for route selection.

An entry in the appnLocTgTgCharTable.

The effective capacity is an integer value that indicates the capacity in kilo bits per second. It is derived from the link bandwidth and the maximum load factor with the range of 0 thru 603,979,776. Enumeration: 'n940Mbps': 180, 'n2500Mbps': 192, 'n64Mbps': 149, 'n88Mbps': 153, 'n1900Mbps': 188, 'n45Gbps': 225, 'n510Mbps': 173, 'n19Gbps': 215, 'n6000bps': 42, 'n141Gbps': 238, 'n310Mbps': 168, 'n190kbps': 82, 'n280Gbps': 246, 'n70Gbps': 230, 'n29kbps': 60, 'n240Gbps': 244, 'n28Gbps': 219, 'n18kbps': 55, 'n34Mbps': 142, 'n1000kbps': 101, 'n44Mbps': 145, 'n230bps': 4, 'n550Mbps': 174, 'n920kbps': 100, 'n128Mbps': 157, 'n62kbps': 69, 'n560Gbps': 254, 'n2500kbps': 112, 'n260Gbps': 245, 'n410bps': 11, 'n8400bps': 46, 'n1080kbps': 102, 'n18Mbps': 135, 'n320Gbps': 248, 'n13800Mbps': 211, 'n9800kbps': 128, 'n380kbps': 90, 'n190bps': 2, 'n630Mbps': 176, 'n2000bps': 29, 'n690kbps': 97, 'n32Mbps': 141, 'n134kbps': 78, 'n540kbps': 94, 'n69Mbps': 150, 'n2200Mbps': 190, 'n74Mbps': 151, 'n180Gbps': 241, 'n6100kbps': 122, 'n16Mbps': 133, 'n770kbps': 98, 'n36kbps': 63, 'n12000bps': 50, 'n25Gbps': 218, 'n210bps': 3, 'n81Gbps': 232, 'n8600kbps': 126, 'n250kbps': 85, 'n480Gbps': 252, 'n35Gbps': 222, 'n118Mbps': 156, 'n77kbps': 72, 'n170bps': 1, 'n18Gbps': 214, 'n170kbps': 81, 'n840kbps': 99, 'n1700bps': 27, 'n12300kbps': 130, 'n53kbps': 67, 'n3900bps': 37, 'n10100Mbps': 208, 'n3300bps': 35, 'n1230kbps': 104, 'n138Mbps': 158, 'n1260Mbps': 184, 'n980bps': 21, 'n49Mbps': 146, 'n1380kbps': 105, 'n4000kbps': 117, 'n26kbps': 59, 'n900bps': 20, 'n4200bps': 38, 'n500kbps': 93, 'n380bps': 10, 'n25Mbps': 138, 'n340bps': 9, 'n440Gbps': 251, 'n3100kbps': 114, 'n4300kbps': 118, 'n310kbps': 88, 'n91Gbps': 233, 'n96kbps': 74, 'n2300kbps': 111, 'n280bps': 7, 'n260Mbps': 165, 'n67kbps': 70, 'n160Gbps': 240, 'n2100bps': 30, 'n1700kbps': 107, 'n43kbps': 65, 'n2800kbps': 113, 'n1540kbps': 106, 'n15100Mbps': 212, 'n1800bps': 28, 'n2700bps': 33, 'n1500bps': 26, 'n15600bps': 53, 'n2400Mbps': 191, 'n1150kbps': 103, 'n106kbps': 75, 'n1420Mbps': 185, 'n600bps': 16, 'n750bps': 18, 'n210kbps': 83, 'n520Gbps': 253, 'n2200kbps': 110, 'n98Mbps': 154, 'n300bps': 8, 'n790Mbps': 178, 'n200Mbps': 162, 'n2800Mbps': 193, 'n131Gbps': 237, 'n14400bps': 52, 'n240bps': 5, 'n560bps': 15, 'n290Mbps': 167, 'n1200bps': 24, 'n30Gbps': 220, 'n7200bps': 44, 'n5700Mbps': 201, 'n59Mbps': 148, 'n157Mbps': 160, 'n7400kbps': 124, 'n55Gbps': 227, 'n4100Mbps': 197, 'n37Mbps': 143, 'n3000bps': 34, 'n3800Mbps': 196, 'n3600bps': 36, 'n4800bps': 40, 'n230kbps': 84, 'n8200Mbps': 205, 'n4500bps': 39, 'n280Mbps': 166, 'n40Gbps': 224, 'n530bps': 14, 'n8000kbps': 125, 'n1700Mbps': 187, 'n9200kbps': 127, 'n710Mbps': 177, 'n4400Mbps': 198, 'n1020Mbps': 181, 'n490bps': 13, 'n600Gbps': 255, 'n5500kbps': 121, 'n86kbps': 73, 'n300Gbps': 247, 'n2000Mbps': 189, 'n580kbps': 95, 'n54Mbps': 147, 'n111Gbps': 235, 'n4900kbps': 120, 'n108Mbps': 155, 'n121Gbps': 236, 'n1130bps': 23, 'n610kbps': 96, 'n16Gbps': 213, 'n20Mbps': 136, 'n33Gbps': 221, 'n220Gbps': 243, 'n420kbps': 91, 'n7800bps': 45, 'n290kbps': 87, 'n125kbps': 77, 'n180Mbps': 161, 'n6900Mbps': 203, 'n3500Mbps': 195, 'n470Mbps': 172, 'n240Mbps': 164, 'n60Gbps': 228, 'n22Mbps': 137, 'n154kbps': 80, 'n14700kbps': 132, 'n4600kbps': 119, 'n39Mbps': 144, 'n22kbps': 57, 'n9000bps': 47, 'n17Mbps': 134, 'n8800Mbps': 206, 'n350Mbps': 169, 'n220Mbps': 163, 'n72kbps': 71, 'n11300Mbps': 209, 'n79Mbps': 152, 'n9600bps': 48, 'n50Gbps': 226, 'n400Gbps': 250, 'n151Gbps': 239, 'n680bps': 17, 'n6800kbps': 123, 'n830bps': 19, 'n75Gbps': 231, 'n101Gbps': 234, 'n260bps': 6, 'n3100Mbps': 194, 'n11100kbps': 129, 'n38Gbps': 223, 'n65Gbps': 229, 'n6600bps': 43, 'n12600Mbps': 210, 'n34kbps': 62, 'min': 0, 'n6300Mbps': 202, 'n390Mbps': 170, 'n1180Mbps': 183, 'n430Mbps': 171, 'n31kbps': 61, 'n24kbps': 58, 'n460kbps': 92, 'n13500kbps': 131, 'n5000Mbps': 200, 'n1050bps': 22, 'n147Mbps': 159, 'n360Gbps': 249, 'n3400kbps': 115, 'n23Gbps': 217, 'n2000kbps': 109, 'n1350bps': 25, 'n19kbps': 56, 'n200Gbps': 242, 'n2400bps': 32, 'n38kbps': 64, 'n5400bps': 41, 'n20Gbps': 216, 'n350kbps': 89, 'n450bps': 12, 'n2300bps': 31, 'n29Mbps': 140, 'n590Mbps': 175, 'n4700Mbps': 199, 'n870Mbps': 179, 'n7500Mbps': 204, 'n1570Mbps': 186, 'n13200bps': 51, 'n115kbps': 76, 'n27Mbps': 139, 'n144kbps': 79, 'n1100Mbps': 182, 'n3700kbps': 116, 'n1800kbps': 108, 'n17kbps': 54, 'n48kbps': 66, 'n10800bps': 49, 'n58kbps': 68, 'n270kbps': 86, 'n9400Mbps': 207.

The cost-per-connect time is a characteristic represented by a single-byte value in the range 0 to 255 that expresses a relative cost of using a transmission group. The units for cost-per-connect time are installation-defined and are typically based on the applicable tariffs of the transmission facility being used by the transmission group. The cost-per-connect time values that a network administrator assigns to the transmission groups in a network should reflect the relative expense of each transmission group as compared to all other transmission groups in the network. A value of 0 means that the cost of connecting over the transmission group is at no additional cost (as in the case of a non-switched facility.

Cost-per-byte is a single byte value in the range 0 to 255 that expresses a relative cost of transmitting a byte over the associated transmission group. The units for cost-per-byte are user-defined. Like cost-per-connect-time, cost-per-byte is network specific and will not be uniform across networks unless assignments are coordinated.

This static characteristic indicates the level of security protection. The security values are architecturally defined to provide continuity across all networks. Currently, security is encoded as one of the following seven values: guardedRadiation - guarded conduit containing the transmission medium; protected against physical and radiation tapping. encrypted - link level encryption is provided unknown - has not been determined guardedConduit - guarded conduit; protected against physical tapping secureConduit - secure conduit, not guarded; e.g. pressurized pipe undergroundCable - underground cable located in a secure country publicSwitchedNetwork - public switched network; secure in the sense that there is no predetermined route that traffic will take nonSecure - all else, e.g. satellite-connected, located in a nonsecure country. Enumeration: 'guardedRadiation': 192, 'guardedConduit': 128, 'unKnown': 0, 'undergroundCable': 64, 'encrypted': 160, 'publicSwitchedNetwork': 32, 'secureConduit': 96, 'nonSecure': 1.

The propagation delay is the length of time that it takes for a signal to propagate from one end of the transmission group to the other. Typical values are: minimum - minimum negligible - 400 microsec terrestrial - 10 msec packetSwitched - 150 msec long - 300 msec Enumeration: 'terrestrial': 113, 'packetSwitched': 145, 'minimum': 0, 'negligible': 76, 'long': 153.

This is the user defined routing parameter in range 0-255.

This is the user defined routing parameter in range 0-255.

This is the user defined routing parameter in range 0-255.

*** THIS TABLE CURRENTLY NOT IMPLEMENTED *** This entry controls the addition and deletion of appnIsrSess components.

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

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

This variable represents an index for the appnIsrSess tables.

This variable represents an index for the appnIsrSess tables.

*** THIS TABLE CURRENTLY NOT IMPLEMENTED *** This component contains dynamic information about an intermediate session for which the network node is providing transit routing.

An entry in the appnIsrSessOperTable.

This attribute contains the transmission priority. This is one of low, medium, high or network. Enumeration: 'high': 3, 'medium': 2, 'low': 1, 'network': 4.

This is the class of service used to select the route. Class of service (COS) is a designation of the transport network characteristics, such as route security, transmission priority, and bandwidth, needed for a particular session. The class of service is derived from the mode name specified by the initiator of the session.

This attribute specifies whether the session uses a limited resource link. A limited resource link remains active only when being used and is deactivated when session traffic ceases. Enumeration: 'yes': 1, 'no': 2.

*** THIS TABLE CURRENTLY NOT IMPLEMENTED *** This entry controls the addition and deletion of appnIsrSessPriStats components.

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

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

This variable represents the index for the appnIsrSessPriStats tables.

*** THIS TABLE CURRENTLY NOT IMPLEMENTED *** This component contains counters and statistics for a session.

An entry in the appnIsrSessPriStatsStatsTable.

This is the maximum request unit (RU) size that can be used on the session.

This is the maximum BTU size (length of the information field in a frame) that can be sent on the session.

This is the maximum BTU size (length of the information field in a frame) that can be received on the session.

This is the maximum size of the send pacing window on the session.

This is the current size of the send pacing window on the session.

This is the maximum size of the receive pacing window on the session.

This is the current size of the receive pacing window on the session.

This attribute counts the number of normal flow data frames sent on the session, the counter wraps to zero.

This attribute counts the number of FMD data frames sent on the session, the counter wraps to zero.

This is the number of normal flow data bytes sent on the session, the counter wraps to zero.

This is the number of normal flow data frames received on the session, the counter wraps to zero.

This attribute counts the number of FMD data frames received on the session, the counter wraps to zero.

This is the number of normal flow data bytes received on the session, the counter wraps to zero.

This attribute contains the session identifier high byte on the session.

This attribute contains the session ID low byte on the SSCP session.

This is the origin destination assignor indicator (ODAI) on the session. Enumeration: 'primary': 0, 'secondary': 1.

This is the link station name associated with these counters and statistics. This is an 8 character name of the link station over which the data flowed. This field can be used to correlate the session statistics with the link over which session data flows.

*** THIS TABLE CURRENTLY NOT IMPLEMENTED *** This entry controls the addition and deletion of appnIsrSessSecStats components.

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

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

This variable represents the index for the appnIsrSessSecStats tables.

*** THIS TABLE CURRENTLY NOT IMPLEMENTED *** This component contains counters and statistics for a session.

An entry in the appnIsrSessSecStatsStatsTable.

This is the maximum request unit (RU) size that can be used on the session.

This is the maximum BTU size (length of the information field in a frame) that can be sent on the session.

This is the maximum BTU size (length of the information field in a frame) that can be received on the session.

This is the maximum size of the send pacing window on the session.

This is the current size of the send pacing window on the session.

This is the maximum size of the receive pacing window on the session.

This is the current size of the receive pacing window on the session.

This attribute counts the number of normal flow data frames sent on the session, the counter wraps to zero.

This attribute counts the number of FMD data frames sent on the session, the counter wraps to zero.

This is the number of normal flow data bytes sent on the session, the counter wraps to zero.

This is the number of normal flow data frames received on the session, the counter wraps to zero.

This attribute counts the number of FMD data frames received on the session, the counter wraps to zero.

This is the number of normal flow data bytes received on the session, the counter wraps to zero.

This attribute contains the session identifier high byte on the session.

This attribute contains the session ID low byte on the SSCP session.

This is the origin destination assignor indicator (ODAI) on the session. Enumeration: 'primary': 0, 'secondary': 1.

This is the link station name associated with these counters and statistics. This is an 8 character name of the link station over which the data flowed. This field can be used to correlate the session statistics with the link over which session data flows.

*** THIS TABLE CURRENTLY NOT IMPLEMENTED *** This entry controls the addition and deletion of appnNnTg components.

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

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

This variable represents an index for the appnNnTg tables.

This variable represents an index for the appnNnTg tables.

This variable represents an index for the appnNnTg tables.

*** THIS TABLE CURRENTLY NOT IMPLEMENTED *** This group contains the operational status of the transmission group entry in the topology database.

An entry in the appnNnTgOperTable.

Flow reduction sequence numbers (FRSNs) are associated with Topology Database Updates (TDUs) and are unique only within each APPN network node. A TDU can be associated with multiple APPN resources. This FRSN indicates the last time this resource was updated at this node. SNMP APPN MIB = ibmappnNnTgFrsn

Number of days left until entry purged.

Resource sequence number.

This attribute contains status information about the transmission group from the topology database. It can be any combination of the following: operational If present indicates that the transmission group is operational. CpCpSessions If present, indicates that CP-CP sessions are supported on this transmission group. quiescing If present, indicates that the transmission group is quiescing. Description of bits: notused0(0) notused1(1) notused2(2) notused3(3) cpCpSessions(4) quiescing(5) notused6(6) operational(7)

*** THIS TABLE CURRENTLY NOT IMPLEMENTED *** Contains the attribute for destination address.

An entry in the appnNnTgLinkAddressTable.

This attribute contains specific data related to the link connection. Token-Ring - contains MAC/SAP X.25 Switched - contains dial digits X.21 Switched - contains dial digits Circuit Switched - contains dial digits Frame-Relay - contains DLCI and SAP The value will be set to zero if the destination node type is not a virtual routing node.

*** THIS TABLE CURRENTLY NOT IMPLEMENTED *** These attributes of the link station are in a group using a common structure. This set provides the TG characteristics of the link through this link station for route selection.

An entry in the appnNnTgTgCharTable.

The effective capacity is an integer value that indicates the capacity in kilo bits per second. It is derived from the link bandwidth and the maximum load factor with the range of 0 thru 603,979,776. Enumeration: 'n940Mbps': 180, 'n2500Mbps': 192, 'n64Mbps': 149, 'n88Mbps': 153, 'n1900Mbps': 188, 'n45Gbps': 225, 'n510Mbps': 173, 'n19Gbps': 215, 'n6000bps': 42, 'n141Gbps': 238, 'n310Mbps': 168, 'n190kbps': 82, 'n280Gbps': 246, 'n70Gbps': 230, 'n29kbps': 60, 'n240Gbps': 244, 'n28Gbps': 219, 'n18kbps': 55, 'n34Mbps': 142, 'n1000kbps': 101, 'n44Mbps': 145, 'n230bps': 4, 'n550Mbps': 174, 'n920kbps': 100, 'n128Mbps': 157, 'n62kbps': 69, 'n560Gbps': 254, 'n2500kbps': 112, 'n260Gbps': 245, 'n410bps': 11, 'n8400bps': 46, 'n1080kbps': 102, 'n18Mbps': 135, 'n320Gbps': 248, 'n13800Mbps': 211, 'n9800kbps': 128, 'n380kbps': 90, 'n190bps': 2, 'n630Mbps': 176, 'n2000bps': 29, 'n690kbps': 97, 'n32Mbps': 141, 'n134kbps': 78, 'n540kbps': 94, 'n69Mbps': 150, 'n2200Mbps': 190, 'n74Mbps': 151, 'n180Gbps': 241, 'n6100kbps': 122, 'n16Mbps': 133, 'n770kbps': 98, 'n36kbps': 63, 'n12000bps': 50, 'n25Gbps': 218, 'n210bps': 3, 'n81Gbps': 232, 'n8600kbps': 126, 'n250kbps': 85, 'n480Gbps': 252, 'n35Gbps': 222, 'n118Mbps': 156, 'n77kbps': 72, 'n170bps': 1, 'n18Gbps': 214, 'n170kbps': 81, 'n840kbps': 99, 'n1700bps': 27, 'n12300kbps': 130, 'n53kbps': 67, 'n3900bps': 37, 'n10100Mbps': 208, 'n3300bps': 35, 'n1230kbps': 104, 'n138Mbps': 158, 'n1260Mbps': 184, 'n980bps': 21, 'n49Mbps': 146, 'n1380kbps': 105, 'n4000kbps': 117, 'n26kbps': 59, 'n900bps': 20, 'n4200bps': 38, 'n500kbps': 93, 'n380bps': 10, 'n25Mbps': 138, 'n340bps': 9, 'n440Gbps': 251, 'n3100kbps': 114, 'n4300kbps': 118, 'n310kbps': 88, 'n91Gbps': 233, 'n96kbps': 74, 'n2300kbps': 111, 'n280bps': 7, 'n260Mbps': 165, 'n67kbps': 70, 'n160Gbps': 240, 'n2100bps': 30, 'n1700kbps': 107, 'n43kbps': 65, 'n2800kbps': 113, 'n1540kbps': 106, 'n15100Mbps': 212, 'n1800bps': 28, 'n2700bps': 33, 'n1500bps': 26, 'n15600bps': 53, 'n2400Mbps': 191, 'n1150kbps': 103, 'n106kbps': 75, 'n1420Mbps': 185, 'n600bps': 16, 'n750bps': 18, 'n210kbps': 83, 'n520Gbps': 253, 'n2200kbps': 110, 'n98Mbps': 154, 'n300bps': 8, 'n790Mbps': 178, 'n200Mbps': 162, 'n2800Mbps': 193, 'n131Gbps': 237, 'n14400bps': 52, 'n240bps': 5, 'n560bps': 15, 'n290Mbps': 167, 'n1200bps': 24, 'n30Gbps': 220, 'n7200bps': 44, 'n5700Mbps': 201, 'n59Mbps': 148, 'n157Mbps': 160, 'n7400kbps': 124, 'n55Gbps': 227, 'n4100Mbps': 197, 'n37Mbps': 143, 'n3000bps': 34, 'n3800Mbps': 196, 'n3600bps': 36, 'n4800bps': 40, 'n230kbps': 84, 'n8200Mbps': 205, 'n4500bps': 39, 'n280Mbps': 166, 'n40Gbps': 224, 'n530bps': 14, 'n8000kbps': 125, 'n1700Mbps': 187, 'n9200kbps': 127, 'n710Mbps': 177, 'n4400Mbps': 198, 'n1020Mbps': 181, 'n490bps': 13, 'n600Gbps': 255, 'n5500kbps': 121, 'n86kbps': 73, 'n300Gbps': 247, 'n2000Mbps': 189, 'n580kbps': 95, 'n54Mbps': 147, 'n111Gbps': 235, 'n4900kbps': 120, 'n108Mbps': 155, 'n121Gbps': 236, 'n1130bps': 23, 'n610kbps': 96, 'n16Gbps': 213, 'n20Mbps': 136, 'n33Gbps': 221, 'n220Gbps': 243, 'n420kbps': 91, 'n7800bps': 45, 'n290kbps': 87, 'n125kbps': 77, 'n180Mbps': 161, 'n6900Mbps': 203, 'n3500Mbps': 195, 'n470Mbps': 172, 'n240Mbps': 164, 'n60Gbps': 228, 'n22Mbps': 137, 'n154kbps': 80, 'n14700kbps': 132, 'n4600kbps': 119, 'n39Mbps': 144, 'n22kbps': 57, 'n9000bps': 47, 'n17Mbps': 134, 'n8800Mbps': 206, 'n350Mbps': 169, 'n220Mbps': 163, 'n72kbps': 71, 'n11300Mbps': 209, 'n79Mbps': 152, 'n9600bps': 48, 'n50Gbps': 226, 'n400Gbps': 250, 'n151Gbps': 239, 'n680bps': 17, 'n6800kbps': 123, 'n830bps': 19, 'n75Gbps': 231, 'n101Gbps': 234, 'n260bps': 6, 'n3100Mbps': 194, 'n11100kbps': 129, 'n38Gbps': 223, 'n65Gbps': 229, 'n6600bps': 43, 'n12600Mbps': 210, 'n34kbps': 62, 'min': 0, 'n6300Mbps': 202, 'n390Mbps': 170, 'n1180Mbps': 183, 'n430Mbps': 171, 'n31kbps': 61, 'n24kbps': 58, 'n460kbps': 92, 'n13500kbps': 131, 'n5000Mbps': 200, 'n1050bps': 22, 'n147Mbps': 159, 'n360Gbps': 249, 'n3400kbps': 115, 'n23Gbps': 217, 'n2000kbps': 109, 'n1350bps': 25, 'n19kbps': 56, 'n200Gbps': 242, 'n2400bps': 32, 'n38kbps': 64, 'n5400bps': 41, 'n20Gbps': 216, 'n350kbps': 89, 'n450bps': 12, 'n2300bps': 31, 'n29Mbps': 140, 'n590Mbps': 175, 'n4700Mbps': 199, 'n870Mbps': 179, 'n7500Mbps': 204, 'n1570Mbps': 186, 'n13200bps': 51, 'n115kbps': 76, 'n27Mbps': 139, 'n144kbps': 79, 'n1100Mbps': 182, 'n3700kbps': 116, 'n1800kbps': 108, 'n17kbps': 54, 'n48kbps': 66, 'n10800bps': 49, 'n58kbps': 68, 'n270kbps': 86, 'n9400Mbps': 207.

The cost-per-connect time is a characteristic represented by a single-byte value in the range 0 to 255 that expresses a relative cost of using a transmission group. The units for cost-per-connect time are installation-defined and are typically based on the applicable tariffs of the transmission facility being used by the transmission group. The cost-per-connect time values that a network administrator assigns to the transmission groups in a network should reflect the relative expense of each transmission group as compared to all other transmission groups in the network. A value of 0 means that the cost of connecting over the transmission group is at no additional cost (as in the case of a non-switched facility.

Cost-per-byte is a single byte value in the range 0 to 255 that expresses a relative cost of transmitting a byte over the associated transmission group. The units for cost-per-byte are user-defined. Like cost-per-connect-time, cost-per-byte is network specific and will not be uniform across networks unless assignments are coordinated.

This static characteristic indicates the level of security protection. The security values are architecturally defined to provide continuity across all networks. Currently, security is encoded as one of the following seven values: guardedRadiation - guarded conduit containing the transmission medium; protected against physical and radiation tapping. encrypted - link level encryption is provided unknown - has not been determined guardedConduit - guarded conduit; protected against physical tapping secureConduit - secure conduit, not guarded; e.g. pressurized pipe undergroundCable - underground cable located in a secure country publicSwitchedNetwork - public switched network; secure in the sense that there is no predetermined route that traffic will take nonSecure - all else, e.g. satellite-connected, located in a nonsecure country. Enumeration: 'guardedRadiation': 192, 'guardedConduit': 128, 'unKnown': 0, 'undergroundCable': 64, 'encrypted': 160, 'publicSwitchedNetwork': 32, 'secureConduit': 96, 'nonSecure': 1.

The propagation delay is the length of time that it takes for a signal to propagate from one end of the transmission group to the other. Typical values are: minimum - minimum negligible - 400 microsec terrestrial - 10 msec packetSwitched - 150 msec long - 300 msec Enumeration: 'terrestrial': 113, 'packetSwitched': 145, 'minimum': 0, 'negligible': 76, 'long': 153.

This is the user defined routing parameter in range 0-255.

This is the user defined routing parameter in range 0-255.

This is the user defined routing parameter in range 0-255.

*** THIS TABLE CURRENTLY NOT IMPLEMENTED *** This entry controls the addition and deletion of appnRtp components.

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

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

This variable represents the index for the appnRtp tables.

*** THIS TABLE CURRENTLY NOT IMPLEMENTED *** This group contains the operational data for the High Performance Routing-Rapid Transport Protocol pipe

An entry in the appnRtpOperTable.

This is the name of the local link station associated with this High Performance Routing-Rapid Transport Protocol pipe

This is the CP name of the node at the other end of the High Performance Routing-Rapid Transport Protocol pipe

This is the name of the Class of Service associated with this High Performance Routing-Rapid Transport Protocol pipe

The number of active sessions using this High Performance Routing-Rapid Transport Protocol pipe

The Transport Connection Identifier (TCID) assigned to this HPR RTP pipe by the local node

The Transport Connection Identifier (TCID) assigned to this HPR RTP pipe by the remote node.

The idle timer of this High Performance Routing-Rapid Transport Protocol pipe (in seconds)

The maximum BTU size (the length of the information field in a frame) of the High Performance Routing-Rapid Transport Protocol pipe.

*** THIS TABLE CURRENTLY NOT IMPLEMENTED *** This group contains the statistics and counters for the High Performance Routing-Rapid Transport Protocol pipe.

An entry in the appnRtpStatsTable.

This attribute is the total number of bytes sent on this High Performance Routing-Rapid Transport Protocol pipe. This counter wraps to zero.

This attribute is the total number of bytes received on this High Performance Routing-Rapid Transport Protocol pipe. This counter wraps to zero.

This attribute counts the total number of bytes resent on this High Performance Routing-Rapid Transport Protocol pipe. This counter wraps to zero.

This attribute counts the total number of bytes discarded on this High Performance Routing-Rapid Transport Protocol pipe. High numbers of discarded bytes may indicate a problem in the APPN network. This counter wraps to zero.

This attribute counts the total number of packets sent on this High Performance Routing-Rapid Transport Protocol pipe. This counter wraps to zero.

This attribute counts the total number of packets received on this High Performance Routing-Rapid Transport Protocol pipe. This counter wraps to zero.

This attribute counts the total number of packets resent on this High Performance Routing-Rapid Transport Protocol pipe. This counter wraps to zero.

This attribute counts the total number of packets discarded on this High Performance Routing-Rapid Transport Protocol pipe. Large numbers of discarded packets may indicate a problem in the APPN network. This counter wraps to zero.

This attribute counts the number of lost frames detected on this pipe. Excessive numbers of lost frames may indicate a problem in the APPN network. This counter wraps to zero.

This attribute gives the current send rate on this pipe.

This attribute give the maximum send rate on this pipe.

This attribute gives the minimum send rate on this pipe.

This attribute gives the current receive rate on this pipe.

This attribute gives the maximum receive rate on this pipe.

This attribute gives the minimum receive rate on this pipe.

This attribute gives the current burst size on this pipe.

This attribute gives the total uptime of this High Performance Routing-Rapid Transport Protocol pipe.

This attribute gives the smoothed round-trip time on this pipe.

This attribute gives the last round-trip time on this pipe.

This attribute gives the short request timer duration on this pipe.

This attribute counts the number of short request timer timeouts on this pipe.

This attribute count the number of idle timer timeouts on this pipe.

This attribute counts the number of invalid SNA frames received on this pipe.

This attribute counts the number of Session Control frames received on this pipe.

This attribute counts the number of Session Control frames sent on this pipe.

*** THIS TABLE CURRENTLY NOT IMPLEMENTED *** This entry controls the addition and deletion of appnDlu components.

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

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

This variable represents the index for the appnDlu tables.

*** THIS TABLE CURRENTLY NOT IMPLEMENTED *** The group contains the operational data for a dependent LU session.

An entry in the appnDluOperTable.

This attribute tells whether the SSCP-LU session is active Enumeration: 'active': 1, 'inactive': 0.

This attribute tells whether the dependent LU session is active. Enumeration: 'active': 1, 'inactive': 0.

This attribute tells the name of the dependent LU server name that this dependent LU is connected to.

This attribute tells the partner LU name of this dependent LU if the LU is connected, it is a NULL string if the dependent LU does not have an active session with a partner LU.

This attribute gives the NAU address of the dependent LU.

*** THIS TABLE CURRENTLY NOT IMPLEMENTED *** This entry controls the addition and deletion of appnDluSscp components.

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

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

This variable represents the index for the appnDluSscp tables.

*** THIS TABLE CURRENTLY NOT IMPLEMENTED *** This component contains counters and statistics for a session.

An entry in the appnDluSscpStatsTable.

This is the maximum request unit (RU) size that can be used on the session.

This is the maximum BTU size (length of the information field in a frame) that can be sent on the session.

This is the maximum BTU size (length of the information field in a frame) that can be received on the session.

This is the maximum size of the send pacing window on the session.

This is the current size of the send pacing window on the session.

This is the maximum size of the receive pacing window on the session.

This is the current size of the receive pacing window on the session.

This attribute counts the number of normal flow data frames sent on the session, the counter wraps to zero.

This attribute counts the number of FMD data frames sent on the session, the counter wraps to zero.

This is the number of normal flow data bytes sent on the session, the counter wraps to zero.

This is the number of normal flow data frames received on the session, the counter wraps to zero.

This attribute counts the number of FMD data frames received on the session, the counter wraps to zero.

This is the number of normal flow data bytes received on the session, the counter wraps to zero.

This attribute contains the session identifier high byte on the session.

This attribute contains the session ID low byte on the SSCP session.

This is the origin destination assignor indicator (ODAI) on the session. Enumeration: 'primary': 0, 'secondary': 1.

This is the link station name associated with these counters and statistics. This is an 8 character name of the link station over which the data flowed. This field can be used to correlate the session statistics with the link over which session data flows.

*** THIS TABLE CURRENTLY NOT IMPLEMENTED *** This entry controls the addition and deletion of appnDluUsStat components.

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

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

This variable represents the index for the appnDluUsStat tables.

*** THIS TABLE CURRENTLY NOT IMPLEMENTED *** This component contains counters and statistics for a session.

An entry in the appnDluUsStatStatsTable.

This is the maximum request unit (RU) size that can be used on the session.

This is the maximum BTU size (length of the information field in a frame) that can be sent on the session.

This is the maximum BTU size (length of the information field in a frame) that can be received on the session.

This is the maximum size of the send pacing window on the session.

This is the current size of the send pacing window on the session.

This is the maximum size of the receive pacing window on the session.

This is the current size of the receive pacing window on the session.

This attribute counts the number of normal flow data frames sent on the session, the counter wraps to zero.

This attribute counts the number of FMD data frames sent on the session, the counter wraps to zero.

This is the number of normal flow data bytes sent on the session, the counter wraps to zero.

This is the number of normal flow data frames received on the session, the counter wraps to zero.

This attribute counts the number of FMD data frames received on the session, the counter wraps to zero.

This is the number of normal flow data bytes received on the session, the counter wraps to zero.

This attribute contains the session identifier high byte on the session.

This attribute contains the session ID low byte on the SSCP session.

This is the origin destination assignor indicator (ODAI) on the session. Enumeration: 'primary': 0, 'secondary': 1.

This is the link station name associated with these counters and statistics. This is an 8 character name of the link station over which the data flowed. This field can be used to correlate the session statistics with the link over which session data flows.

*** THIS TABLE CURRENTLY NOT IMPLEMENTED *** This entry controls the addition and deletion of appnDluDsStat components.

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

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

This variable represents the index for the appnDluDsStat tables.

*** THIS TABLE CURRENTLY NOT IMPLEMENTED *** This component contains counters and statistics for a session.

An entry in the appnDluDsStatStatsTable.

This is the maximum request unit (RU) size that can be used on the session.

This is the maximum BTU size (length of the information field in a frame) that can be sent on the session.

This is the maximum BTU size (length of the information field in a frame) that can be received on the session.

This is the maximum size of the send pacing window on the session.

This is the current size of the send pacing window on the session.

This is the maximum size of the receive pacing window on the session.

This is the current size of the receive pacing window on the session.

This attribute counts the number of normal flow data frames sent on the session, the counter wraps to zero.

This attribute counts the number of FMD data frames sent on the session, the counter wraps to zero.

This is the number of normal flow data bytes sent on the session, the counter wraps to zero.

This is the number of normal flow data frames received on the session, the counter wraps to zero.

This attribute counts the number of FMD data frames received on the session, the counter wraps to zero.

This is the number of normal flow data bytes received on the session, the counter wraps to zero.

This attribute contains the session identifier high byte on the session.

This attribute contains the session ID low byte on the SSCP session.

This is the origin destination assignor indicator (ODAI) on the session. Enumeration: 'primary': 0, 'secondary': 1.

This is the link station name associated with these counters and statistics. This is an 8 character name of the link station over which the data flowed. This field can be used to correlate the session statistics with the link over which session data flows.

*** THIS TABLE CURRENTLY NOT IMPLEMENTED *** This entry controls the addition and deletion of appnDlus components.

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

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

This variable represents the index for the appnDlus tables.

*** THIS TABLE CURRENTLY NOT IMPLEMENTED *** Information on the DLUR-DLUS pipe.

An entry in the appnDlusOperTable.

This attribute indicates if this is the pipe to the primary default dependent LU server. Enumeration: 'yes': 1, 'no': 0.

This attribute indicates the current state of the DLUR-DLUS pipe. inactive indicates the pipe is not connected (the session has likely failed), pendingActive indicates the pipe is connecting, active indicates the pipe is currently connected and data is flowing, and pendingInactive indicates the pipe is being disconnected. Enumeration: 'active': 2, 'pendingInactive': 3, 'pendingActive': 1, 'inactive': 0.

This attribute indicates the number of active physical units using the pipe.

*** THIS TABLE CURRENTLY NOT IMPLEMENTED *** This group contains the counters and statistics for the DLUR-DLUS pipe

An entry in the appnDlusDlusStatTable.

This attribute counts the number of REQACTPUs sent to the DLUS. The counter wraps to zero.

This attribute counts the number of REQACTPU responses received from the DLUS. The counter wraps to zero.

This attributes counts the number of ACTPUs received from the DLUS. The counter wraps to zero.

This attribute counts the number of ACTPU responses sent to the DLUS. The counter wraps to zero.

This attribute counts the number of REQDACTPUs sent to the DLUS. The counter wraps to zero.

This attribute counts the number of REQDACTPU responses received from the DLUS. The counter wraps to zero.

This attribute counts the number of DACTPUs received from the DLUS. The counter wraps to zero.

This attribute counts the number of DACTPU responses received from the DLUS. The counter wraps to zero.

This attribute counts the number of ACTLUs received from the DLUS. The counter wraps to zero.

This attribute counts the number of ACTLU responses sent to the DLUS. The counter wraps to zero.

This attribute counts the number of DACTLUs received from the DLUS. The counter wraps to zero.

This attribute counts the number of DACTLU responses sent to the DLUS. The counter wraps to zero.

This attribute counts the number of SSCP-PU MUs received. The counter wraps to zero.

This attribute counts the number of SSCP-PU MUs sent. The counter wraps to zero.

This attributes counts the number of SSCP-LU MUs received. The counter wraps to zero.

This attributes counts the number of SSCP-LU MUs sent. The counter wraps to zero.

This entry controls the addition and deletion of appnDLUR components.

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

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

This variable represents the index for the appnDLUR tables.

These parameters define the dependent LU requester options.

An entry in the appnDLURDlurParmsTable.

The fully qualified CP name of the node that will serve as the primary dependent LU server (DLUS).

The fully qualified CP name of the node that will serve as the backup or secondary dependent LU server (DLUS).

This attribute specifies the time in seconds before a network search to locate a DLUS times out.

This attribute specifies the maximum number of retry attempts that will be made after an initial failure to contact a DLUS. If zero is specifed, APPN will retry indefinitely. When this limit has been reached, downstream PUs that are connected to APPN will be sent a QDISC frame.

This entry controls the addition and deletion of appnCos components.

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

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

This variable represents the index for the appnCos tables.

This entry controls the addition and deletion of appnCosTg components.

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

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

This variable represents the index for the appnCosTg tables.

This group specifies a range of TG characteristics for a class of service and is used in route selection for session traffic. During route computation, APPN determines the optimum route through a network in the following steps: - obtains the required route characteristics from the COS database using the mode name specified in the session request - determines all possible combinations of transmission groups and nodes that form a route to the destination database - the actual characteristics of the Nodes and TGs in these routes are compared against the COS tables that contain the required characteristics of the session. A weight is assigned based on how well the actual characteristics meet the required characteristics. Where there is no match between actual and required characteristics, the route containing the node or TG is excluded from further computation. - Each possible route is quantified by adding the weights assigned to the node and TGs in the route. The route with the lowest weight is the one used for the session.

An entry in the appnCosTgProvTable.

During route computation, APPN determines the optimum route through a network in the following steps: - obtains the required route characteristics from the COS database using the mode name specified in the session request - determines all possible combinations of transmission groups and nodes that form a route to the destination database - the actual characteristics of the Nodes and TGs in these routes are compared against the COS tables that contain the required characteristics of the session. A weight is assigned based on how well the actual characteristics meet the required characteristics. Where there is no match between actual and required characteristics, the route containing the node or TG is excluded from further computation. - Each possible route is quantified by adding the weights assigned to the node and TGs in the route. The route with the lowest weight is the one used for the session. This attribute is part of the COS tables and specifies the minimum acceptable speed for a TG using this Class of Service. Enumeration: 'n940Mbps': 180, 'n2500Mbps': 192, 'n64Mbps': 149, 'n88Mbps': 153, 'n1900Mbps': 188, 'n45Gbps': 225, 'n510Mbps': 173, 'n19Gbps': 215, 'n6000bps': 42, 'n141Gbps': 238, 'n310Mbps': 168, 'n190kbps': 82, 'n280Gbps': 246, 'n70Gbps': 230, 'n29kbps': 60, 'n240Gbps': 244, 'n28Gbps': 219, 'n18kbps': 55, 'n34Mbps': 142, 'n1000kbps': 101, 'n44Mbps': 145, 'n230bps': 4, 'n550Mbps': 174, 'n920kbps': 100, 'n128Mbps': 157, 'n62kbps': 69, 'n560Gbps': 254, 'n2500kbps': 112, 'n260Gbps': 245, 'n410bps': 11, 'n8400bps': 46, 'n1080kbps': 102, 'n18Mbps': 135, 'n320Gbps': 248, 'n13800Mbps': 211, 'n9800kbps': 128, 'n380kbps': 90, 'n190bps': 2, 'n630Mbps': 176, 'n2000bps': 29, 'n690kbps': 97, 'n32Mbps': 141, 'n134kbps': 78, 'n540kbps': 94, 'n69Mbps': 150, 'n2200Mbps': 190, 'n74Mbps': 151, 'n180Gbps': 241, 'n6100kbps': 122, 'n16Mbps': 133, 'n770kbps': 98, 'n36kbps': 63, 'n12000bps': 50, 'n25Gbps': 218, 'n210bps': 3, 'n81Gbps': 232, 'n8600kbps': 126, 'n250kbps': 85, 'n480Gbps': 252, 'n35Gbps': 222, 'n118Mbps': 156, 'n77kbps': 72, 'n170bps': 1, 'n18Gbps': 214, 'n170kbps': 81, 'n840kbps': 99, 'n1700bps': 27, 'n12300kbps': 130, 'n53kbps': 67, 'n3900bps': 37, 'n10100Mbps': 208, 'n3300bps': 35, 'n1230kbps': 104, 'n138Mbps': 158, 'n1260Mbps': 184, 'n980bps': 21, 'n49Mbps': 146, 'n1380kbps': 105, 'n4000kbps': 117, 'n26kbps': 59, 'n900bps': 20, 'n4200bps': 38, 'n500kbps': 93, 'n380bps': 10, 'n25Mbps': 138, 'n340bps': 9, 'n440Gbps': 251, 'n3100kbps': 114, 'n4300kbps': 118, 'n310kbps': 88, 'n91Gbps': 233, 'n96kbps': 74, 'n2300kbps': 111, 'n280bps': 7, 'max': 255, 'n260Mbps': 165, 'n67kbps': 70, 'n160Gbps': 240, 'n2100bps': 30, 'n1700kbps': 107, 'n43kbps': 65, 'n2800kbps': 113, 'n1540kbps': 106, 'n15100Mbps': 212, 'n1800bps': 28, 'n2700bps': 33, 'n1500bps': 26, 'n15600bps': 53, 'n2400Mbps': 191, 'n1150kbps': 103, 'n106kbps': 75, 'n1420Mbps': 185, 'n600bps': 16, 'n750bps': 18, 'n210kbps': 83, 'n520Gbps': 253, 'n2200kbps': 110, 'n98Mbps': 154, 'n300bps': 8, 'n790Mbps': 178, 'n200Mbps': 162, 'n2800Mbps': 193, 'n131Gbps': 237, 'n14400bps': 52, 'n240bps': 5, 'n560bps': 15, 'n290Mbps': 167, 'n1200bps': 24, 'n30Gbps': 220, 'n7200bps': 44, 'n5700Mbps': 201, 'n59Mbps': 148, 'n157Mbps': 160, 'n7400kbps': 124, 'n55Gbps': 227, 'n4100Mbps': 197, 'n37Mbps': 143, 'n3000bps': 34, 'n3800Mbps': 196, 'n3600bps': 36, 'n4800bps': 40, 'n230kbps': 84, 'n8200Mbps': 205, 'n4500bps': 39, 'n280Mbps': 166, 'n40Gbps': 224, 'n530bps': 14, 'n8000kbps': 125, 'n1700Mbps': 187, 'n9200kbps': 127, 'n710Mbps': 177, 'n4400Mbps': 198, 'n1020Mbps': 181, 'n490bps': 13, 'n5500kbps': 121, 'n86kbps': 73, 'n300Gbps': 247, 'n2000Mbps': 189, 'n580kbps': 95, 'n54Mbps': 147, 'n111Gbps': 235, 'n4900kbps': 120, 'n108Mbps': 155, 'n121Gbps': 236, 'n1130bps': 23, 'n610kbps': 96, 'n16Gbps': 213, 'n20Mbps': 136, 'n33Gbps': 221, 'n220Gbps': 243, 'n420kbps': 91, 'n7800bps': 45, 'n290kbps': 87, 'n125kbps': 77, 'n180Mbps': 161, 'n6900Mbps': 203, 'n3500Mbps': 195, 'n470Mbps': 172, 'n240Mbps': 164, 'n60Gbps': 228, 'n22Mbps': 137, 'n154kbps': 80, 'n14700kbps': 132, 'n4600kbps': 119, 'n39Mbps': 144, 'n22kbps': 57, 'n9000bps': 47, 'n17Mbps': 134, 'n8800Mbps': 206, 'n350Mbps': 169, 'n220Mbps': 163, 'n72kbps': 71, 'n11300Mbps': 209, 'n79Mbps': 152, 'n9600bps': 48, 'n50Gbps': 226, 'n400Gbps': 250, 'n151Gbps': 239, 'n680bps': 17, 'n6800kbps': 123, 'n830bps': 19, 'n75Gbps': 231, 'n101Gbps': 234, 'n260bps': 6, 'n3100Mbps': 194, 'n11100kbps': 129, 'n38Gbps': 223, 'n65Gbps': 229, 'n6600bps': 43, 'n12600Mbps': 210, 'n34kbps': 62, 'min': 0, 'n6300Mbps': 202, 'n390Mbps': 170, 'n1180Mbps': 183, 'n430Mbps': 171, 'n31kbps': 61, 'n24kbps': 58, 'n460kbps': 92, 'n13500kbps': 131, 'n5000Mbps': 200, 'n1050bps': 22, 'n147Mbps': 159, 'n360Gbps': 249, 'n3400kbps': 115, 'n23Gbps': 217, 'n2000kbps': 109, 'n1350bps': 25, 'n19kbps': 56, 'n200Gbps': 242, 'n2400bps': 32, 'n38kbps': 64, 'n5400bps': 41, 'n20Gbps': 216, 'n350kbps': 89, 'n450bps': 12, 'n2300bps': 31, 'n29Mbps': 140, 'n590Mbps': 175, 'n4700Mbps': 199, 'n870Mbps': 179, 'n7500Mbps': 204, 'n1570Mbps': 186, 'n13200bps': 51, 'n115kbps': 76, 'n27Mbps': 139, 'n144kbps': 79, 'n1100Mbps': 182, 'n3700kbps': 116, 'n1800kbps': 108, 'n17kbps': 54, 'n48kbps': 66, 'n10800bps': 49, 'n58kbps': 68, 'n270kbps': 86, 'n9400Mbps': 207.

During route computation, APPN determines the optimum route through a network in the following steps: - obtains the required route characteristics from the COS database using the mode name specified in the session request - determines all possible combinations of transmission groups and nodes that form a route to the destination database - the actual characteristics of the Nodes and TGs in these routes are compared against the COS tables that contain the required characteristics of the session. A weight is assigned based on how well the actual characteristics meet the required characteristics. Where there is no match between actual and required characteristics, the route containing the node or TG is excluded from further computation. - Each possible route is quantified by adding the weights assigned to the node and TGs in the route. The route with the lowest weight is the one used for the session. This attribute is part of the COS tables and specifies the maximum acceptable speed for a TG using this Class of Service. Enumeration: 'n940Mbps': 180, 'n2500Mbps': 192, 'n64Mbps': 149, 'n88Mbps': 153, 'n1900Mbps': 188, 'n45Gbps': 225, 'n510Mbps': 173, 'n19Gbps': 215, 'n6000bps': 42, 'n141Gbps': 238, 'n310Mbps': 168, 'n190kbps': 82, 'n280Gbps': 246, 'n70Gbps': 230, 'n29kbps': 60, 'n240Gbps': 244, 'n28Gbps': 219, 'n18kbps': 55, 'n34Mbps': 142, 'n1000kbps': 101, 'n44Mbps': 145, 'n230bps': 4, 'n550Mbps': 174, 'n920kbps': 100, 'n128Mbps': 157, 'n62kbps': 69, 'n560Gbps': 254, 'n2500kbps': 112, 'n260Gbps': 245, 'n410bps': 11, 'n8400bps': 46, 'n1080kbps': 102, 'n18Mbps': 135, 'n320Gbps': 248, 'n13800Mbps': 211, 'n9800kbps': 128, 'n380kbps': 90, 'n190bps': 2, 'n630Mbps': 176, 'n2000bps': 29, 'n690kbps': 97, 'n32Mbps': 141, 'n134kbps': 78, 'n540kbps': 94, 'n69Mbps': 150, 'n2200Mbps': 190, 'n74Mbps': 151, 'n180Gbps': 241, 'n6100kbps': 122, 'n16Mbps': 133, 'n770kbps': 98, 'n36kbps': 63, 'n12000bps': 50, 'n25Gbps': 218, 'n210bps': 3, 'n81Gbps': 232, 'n8600kbps': 126, 'n250kbps': 85, 'n480Gbps': 252, 'n35Gbps': 222, 'n118Mbps': 156, 'n77kbps': 72, 'n170bps': 1, 'n18Gbps': 214, 'n170kbps': 81, 'n840kbps': 99, 'n1700bps': 27, 'n12300kbps': 130, 'n53kbps': 67, 'n3900bps': 37, 'n10100Mbps': 208, 'n3300bps': 35, 'n1230kbps': 104, 'n138Mbps': 158, 'n1260Mbps': 184, 'n980bps': 21, 'n49Mbps': 146, 'n1380kbps': 105, 'n4000kbps': 117, 'n26kbps': 59, 'n900bps': 20, 'n4200bps': 38, 'n500kbps': 93, 'n380bps': 10, 'n25Mbps': 138, 'n340bps': 9, 'n440Gbps': 251, 'n3100kbps': 114, 'n4300kbps': 118, 'n310kbps': 88, 'n91Gbps': 233, 'n96kbps': 74, 'n2300kbps': 111, 'n280bps': 7, 'max': 255, 'n260Mbps': 165, 'n67kbps': 70, 'n160Gbps': 240, 'n2100bps': 30, 'n1700kbps': 107, 'n43kbps': 65, 'n2800kbps': 113, 'n1540kbps': 106, 'n15100Mbps': 212, 'n1800bps': 28, 'n2700bps': 33, 'n1500bps': 26, 'n15600bps': 53, 'n2400Mbps': 191, 'n1150kbps': 103, 'n106kbps': 75, 'n1420Mbps': 185, 'n600bps': 16, 'n750bps': 18, 'n210kbps': 83, 'n520Gbps': 253, 'n2200kbps': 110, 'n98Mbps': 154, 'n300bps': 8, 'n790Mbps': 178, 'n200Mbps': 162, 'n2800Mbps': 193, 'n131Gbps': 237, 'n14400bps': 52, 'n240bps': 5, 'n560bps': 15, 'n290Mbps': 167, 'n1200bps': 24, 'n30Gbps': 220, 'n7200bps': 44, 'n5700Mbps': 201, 'n59Mbps': 148, 'n157Mbps': 160, 'n7400kbps': 124, 'n55Gbps': 227, 'n4100Mbps': 197, 'n37Mbps': 143, 'n3000bps': 34, 'n3800Mbps': 196, 'n3600bps': 36, 'n4800bps': 40, 'n230kbps': 84, 'n8200Mbps': 205, 'n4500bps': 39, 'n280Mbps': 166, 'n40Gbps': 224, 'n530bps': 14, 'n8000kbps': 125, 'n1700Mbps': 187, 'n9200kbps': 127, 'n710Mbps': 177, 'n4400Mbps': 198, 'n1020Mbps': 181, 'n490bps': 13, 'n5500kbps': 121, 'n86kbps': 73, 'n300Gbps': 247, 'n2000Mbps': 189, 'n580kbps': 95, 'n54Mbps': 147, 'n111Gbps': 235, 'n4900kbps': 120, 'n108Mbps': 155, 'n121Gbps': 236, 'n1130bps': 23, 'n610kbps': 96, 'n16Gbps': 213, 'n20Mbps': 136, 'n33Gbps': 221, 'n220Gbps': 243, 'n420kbps': 91, 'n7800bps': 45, 'n290kbps': 87, 'n125kbps': 77, 'n180Mbps': 161, 'n6900Mbps': 203, 'n3500Mbps': 195, 'n470Mbps': 172, 'n240Mbps': 164, 'n60Gbps': 228, 'n22Mbps': 137, 'n154kbps': 80, 'n14700kbps': 132, 'n4600kbps': 119, 'n39Mbps': 144, 'n22kbps': 57, 'n9000bps': 47, 'n17Mbps': 134, 'n8800Mbps': 206, 'n350Mbps': 169, 'n220Mbps': 163, 'n72kbps': 71, 'n11300Mbps': 209, 'n79Mbps': 152, 'n9600bps': 48, 'n50Gbps': 226, 'n400Gbps': 250, 'n151Gbps': 239, 'n680bps': 17, 'n6800kbps': 123, 'n830bps': 19, 'n75Gbps': 231, 'n101Gbps': 234, 'n260bps': 6, 'n3100Mbps': 194, 'n11100kbps': 129, 'n38Gbps': 223, 'n65Gbps': 229, 'n6600bps': 43, 'n12600Mbps': 210, 'n34kbps': 62, 'min': 0, 'n6300Mbps': 202, 'n390Mbps': 170, 'n1180Mbps': 183, 'n430Mbps': 171, 'n31kbps': 61, 'n24kbps': 58, 'n460kbps': 92, 'n13500kbps': 131, 'n5000Mbps': 200, 'n1050bps': 22, 'n147Mbps': 159, 'n360Gbps': 249, 'n3400kbps': 115, 'n23Gbps': 217, 'n2000kbps': 109, 'n1350bps': 25, 'n19kbps': 56, 'n200Gbps': 242, 'n2400bps': 32, 'n38kbps': 64, 'n5400bps': 41, 'n20Gbps': 216, 'n350kbps': 89, 'n450bps': 12, 'n2300bps': 31, 'n29Mbps': 140, 'n590Mbps': 175, 'n4700Mbps': 199, 'n870Mbps': 179, 'n7500Mbps': 204, 'n1570Mbps': 186, 'n13200bps': 51, 'n115kbps': 76, 'n27Mbps': 139, 'n144kbps': 79, 'n1100Mbps': 182, 'n3700kbps': 116, 'n1800kbps': 108, 'n17kbps': 54, 'n48kbps': 66, 'n10800bps': 49, 'n58kbps': 68, 'n270kbps': 86, 'n9400Mbps': 207.

During route computation, APPN determines the optimum route through a network in the following steps: - obtains the required route characteristics from the COS database using the mode name specified in the session request - determines all possible combinations of transmission groups and nodes that form a route to the destination database - the actual characteristics of the Nodes and TGs in these routes are compared against the COS tables that contain the required characteristics of the session. A weight is assigned based on how well the actual characteristics meet the required characteristics. Where there is no match between actual and required characteristics, the route containing the node or TG is excluded from further computation. - Each possible route is quantified by adding the weights assigned to the node and TGs in the route. The route with the lowest weight is the one used for the session. This attribute is part of the COS tables and specifies the minimum cost per connect time for a TG. It is represented by a number between 0 and 255 and is the relative cost of using a TG. The units for cost-per-connect time are installation-defined and are typically based on the applicable tariffs of the transmission facility being used by the TG. The cost-per-connect time values that a network administrator assigns to the TGs in a network should reflect the relative expense of each TG as compared to all other TGs in the network. A value of 0 means that there is no additional cost in connecting over the TG(as in the case of a non-switched facility).

During route computation, APPN determines the optimum route through a network in the following steps: - obtains the required route characteristics from the COS database using the mode name specified in the session request - determines all possible combinations of transmission groups and nodes that form a route to the destination database - the actual characteristics of the Nodes and TGs in these routes are compared against the COS tables that contain the required characteristics of the session. A weight is assigned based on how well the actual characteristics meet the required characteristics. Where there is no match between actual and required characteristics, the route containing the node or TG is excluded from further computation. - Each possible route is quantified by adding the weights assigned to the node and TGs in the route. The route with the lowest weight is the one used for the session. This attribute is part of the COS tables and specifies the maximum cost per connect time for a TG. It is represented by a number between 0 and 255 and is the relative cost of using a TG. The units for cost-per-connect time are installation-defined and are typically based on the applicable tariffs of the transmission facility being used by the TG. The cost per connect time values that a network administrator assigns to the TGs in a network should reflect the relative expense of each TG as compared to all other TGs in the network. A value of 0 means that there is no additional cost in connecting over the TG (as in the case of a non-switched facility).

During route computation, APPN determines the optimum route through a network in the following steps: - obtains the required route characteristics from the COS database using the mode name specified in the session request - determines all possible combinations of transmission groups and nodes that form a route to the destination database - the actual characteristics of the Nodes and TGs in these routes are compared against the COS tables that contain the required characteristics of the session. A weight is assigned based on how well the actual characteristics meet the required characteristics. Where there is no match between actual and required characteristics, the route containing the node or TG is excluded from further computation. - Each possible route is quantified by adding the weights assigned to the node and TGs in the route. The route with the lowest weight is the one used for the session. This attribute is part of the COS tables and specifies the minimum cost per byte allowed for a TG to be used for a session. It is a single byte value in the range 0 to 255 that expresses a relative cost of transmitting a byte over the associated TG. The units for cost per byte are user defined. Like cost per connect time, cost per byte is network specific and will not be uniform across networks unless assignments are coordinated.

During route computation, APPN determines the optimum route through a network in the following steps: - obtains the required route characteristics from the COS database using the mode name specified in the session request - determines all possible combinations of transmission groups and nodes that form a route to the destination database - the actual characteristics of the Nodes and TGs in these routes are compared against the COS tables that contain the required characteristics of the session. A weight is assigned based on how well the actual characteristics meet the required characteristics. Where there is no match between actual and required characteristics, the route containing the node or TG is excluded from further computation. - Each possible route is quantified by adding the weights assigned to the node and TGs in the route. The route with the lowest weight is the one used for the session. This attribute is part of the COS tables and specifies the maximum cost per byte allowed for a TG to be used for a session. It is a single byte value in the range 0 to 255 that expresses a relative cost of transmitting a byte over the associated TG. The units for cost per byte are user defined. Like cost per connect time, cost per byte is network specific and will not be uniform across networks unless assignments are coordinated.

During route computation, APPN determines the optimum route through a network in the following steps: - obtains the required route characteristics from the COS database using the mode name specified in the session request - determines all possible combinations of transmission groups and nodes that form a route to the destination database - the actual characteristics of the Nodes and TGs in these routes are compared against the COS tables that contain the required characteristics of the session. A weight is assigned based on how well the actual characteristics meet the required characteristics. Where there is no match between actual and required characteristics, the route containing the node or TG is excluded from further computation. - Each possible route is quantified by adding the weights assigned to the node and TGs in the route. The route with the lowest weight is the one used for the session. This attribute is part of the COS tables and specifies the minimum level of security protection required for a TG to be allowed to route session traffic. The security values are architecturally defined to provide continuity across all networks. Currently, security is encoded as one of the following seven values: guardedRadiation - guarded conduit containing the transmission medium; protected against physical and radiation tapping. encrypted - link level encryption is provided guardedConduit - guarded conduit; protected against physical tapping secureConduit- secure conduit, not guarded; e.g. pressurized pipe undergroundCable - underground cable located in a secure country publicSwitchedNetwork - public switched network; secure in the sense that there is no predetermined route that traffic will take nonSecure - all else, for example satellite-connected, located in a nonsecure country. Enumeration: 'guardedRadiation': 192, 'guardedConduit': 128, 'encrypted': 160, 'undergroundCable': 64, 'publicSwitchedNetwork': 32, 'secureConduit': 96, 'nonSecure': 1.

During route computation, APPN determines the optimum route through a network in the following steps: - obtains the required route characteristics from the COS database using the mode name specified in the session request - determines all possible combinations of transmission groups and nodes that form a route to the destination database - the actual characteristics of the Nodes and TGs in these routes are compared against the COS tables that contain the required characteristics of the session. A weight is assigned based on how well the actual characteristics meet the required characteristics. Where there is no match between actual and required characteristics, the route containing the node or TG is excluded from further computation. - Each possible route is quantified by adding the weights assigned to the node and TGs in the route. The route with the lowest weight is the one used for the session. This attribute is part of the COS tables and specifies the maximum level of security protection required for a TG to be allowed to route session traffic. The security values are architecturally defined to provide continuity across all networks. Currently, security is encoded as one of the following seven values: guardedRadiation - guarded conduit containing the transmission medium; protected against physical and radiation tapping. encrypted - link level encryption is provided guardedConduit - guarded conduit; protected against physical tapping secureConduit- secure conduit, not guarded; e.g. pressurized pipe undergroundCable - underground cable located in a secure country publicSwitchedNetwork - public switched network; secure in the sense that there is no predetermined route that traffic will take nonSecure - all else, for example. satellite-connected, located in a nonsecure country. Enumeration: 'guardedRadiation': 192, 'guardedConduit': 128, 'encrypted': 160, 'undergroundCable': 64, 'publicSwitchedNetwork': 32, 'secureConduit': 96, 'nonSecure': 1.

During route computation, APPN determines the optimum route through a network in the following steps: - obtains the required route characteristics from the COS database using the mode name specified in the session request - determines all possible combinations of transmission groups and nodes that form a route to the destination database - the actual characteristics of the Nodes and TGs in these routes are compared against the COS tables that contain the required characteristics of the session. A weight is assigned based on how well the actual characteristics meet the required characteristics. Where there is no match between actual and required characteristics, the route containing the node or TG is excluded from further computation. - Each possible route is quantified by adding the weights assigned to the node and TGs in the route. The route with the lowest weight is the one used for the session. This attribute is part of the COS tables and specifies the minimum propagation delay for this Class of Service. Propogation delay is the length of time that it takes for a signal to propagate from one end of the TG to the other. Possible values are: minimum - minimum negligible - 400 microsec terrestrial - 10 msec packetSwitched - 150 msec long - 300 msec Enumeration: 'terrestrial': 113, 'maximum': 255, 'long': 153, 'minimum': 0, 'negligible': 76, 'packetSwitched': 145.

During route computation, APPN determines the optimum route through a network in the following steps: - obtains the required route characteristics from the COS database using the mode name specified in the session request - determines all possible combinations of transmission groups and nodes that form a route to the destination database - the actual characteristics of the Nodes and TGs in these routes are compared against the COS tables that contain the required characteristics of the session. A weight is assigned based on how well the actual characteristics meet the required characteristics. Where there is no match between actual and required characteristics, the route containing the node or TG is excluded from further computation. - Each possible route is quantified by adding the weights assigned to the node and TGs in the route. The route with the lowest weight is the one used for the session. This attribute is part of the COS tables and specifies the maximum propagation delay for this Class of Service. Propagation delay is the length of time that it takes for a signal to propagate from one end of the TG to the other. Possible values are: minimum - minimum negligible - 400 microsec terrestrial - 10 msec packetSwitched - 150 msec long - 300 msec Enumeration: 'terrestrial': 113, 'maximum': 255, 'long': 153, 'minimum': 0, 'negligible': 76, 'packetSwitched': 145.

During route computation, APPN determines the optimum route through a network in the following steps: - obtains the required route characteristics from the COS database using the mode name specified in the session request - determines all possible combinations of transmission groups and nodes that form a route to the destination database - the actual characteristics of the Nodes and TGs in these routes are compared against the COS tables that contain the required characteristics of the session. A weight is assigned based on how well the actual characteristics meet the required characteristics. Where there is no match between actual and required characteristics, the route containing the node or TG is excluded from further computation. - Each possible route is quantified by adding the weights assigned to the node and TGs in the route. The route with the lowest weight is the one used for the session. This attribute is part of the COS tables and specifies the minimum modem class allowed for a TG to carry session traffic.