appnIndex |
.1.3.6.1.4.1.562.2.4.1.110.1.1.10 |
This variable represents the index for the appn tables.
|
appnRowStatus |
.1.3.6.1.4.1.562.2.4.1.110.1.1.1 |
This variable is used as the basis for SNMP naming of
appn components.
These components can be added and deleted.
|
appnComponentName |
.1.3.6.1.4.1.562.2.4.1.110.1.1.2 |
This variable provides the component's string name for
use with the ASCII Console Interface
|
appnStorageType |
.1.3.6.1.4.1.562.2.4.1.110.1.1.4 |
This variable represents the storage type value for the
appn tables.
|
appnLogicalProcessor |
.1.3.6.1.4.1.562.2.4.1.110.100.1.1 |
This attribute specifies the logical processor on which the Appn
component will utilize memory and CPU resources.
|
appnMaximumSvcs |
.1.3.6.1.4.1.562.2.4.1.110.100.1.22 |
This attribute specifies the total number of general switched virtual
circuits (GSVC) that can be active on this Appn node. Once this
number is reached no GSVC calls will be accepted by the service.
This attribute does not include the Frame Relay switched virtual
circuits.
|
appnMaximumLinkStations |
.1.3.6.1.4.1.562.2.4.1.110.100.1.23 |
This attribute specifies the total number of link stations for GSVCs,
Frame Relay PVCs and SVCs that can be active on this Appn node.
Once the value of activeLinkStations reaches or exceeds the value
of maximumLinkStations, no new incoming SVC calls (GSVCs
and Frame Relay SVCs) will be accepted by the service until the
value of activeLinkStations is again below the value of
maximumLinkStations. Outgoing GSVCs and Frame Relay PVCs
(incoming or outgoing) are provisioned and their call setups at this
end are not affected when the value of activeLinkStations reaches
or exceeds the value of maximumLinkStations.
Link stations are dynamically created for the end user applications
as required. Therefore the value of activeLinkStations may exceed
the value of maximumLinkStations.
|
appnFqCpName |
.1.3.6.1.4.1.562.2.4.1.110.101.1.1 |
The network qualified control point (CP) name. This is the name by
which the node is identified within the APPN network. It is
signalled on the XID 3 exchange and is the end-point of CP-CP
sessions established with this node.
The first portion of this name, up to the period, is the network
identifier for the network to which this 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.
|
appnBlockNumber |
.1.3.6.1.4.1.562.2.4.1.110.101.1.3 |
The block number identifies the product of the node. It is the first
three hexadecimal digits of the SNA node id.
|
appnIdNumber |
.1.3.6.1.4.1.562.2.4.1.110.101.1.4 |
The idNumber is used to identify the local SNA node. It is the last
five hexadecimal digits of the SNA node id and is administratively
defined. The idNumber will be combined with the three
hexadecimal digit block number to form the SNA node id. The SNA
node id is included in APPN alerts and in XIDs. A unique value is
required for connections to SNA.
|
appnRouteAdditionResistance |
.1.3.6.1.4.1.562.2.4.1.110.101.1.5 |
Route addition resistance is a value that indicates the relative
desirability of using this node for intermediate session traffic.The
value, which can be any integer 0-255, is used in route computation.
The lower the value, the more desirable the node is for intermediate
routing.
|
appnFeatures |
.1.3.6.1.4.1.562.2.4.1.110.101.1.6 |
This attribute supports several YES/NO flags which are defined in
the create parameters:
multipleDomainSupport
If present, specifies that Management Services (MS) supports
Multiple Domain Support (MDS) and MS capabilities exchange.
registerWithCDS
If present, for a network node this specifies whether local and
domain resources may be registered with a central directory server.
storeEndptRscvs
If present, specifies that route selection control vectors (RSCV)
should be stored for diagnostic purposes on sessions which
terminate in this node. Note that selecting this value means that an
RSCV will be stored for each ISR session. This extra storage can be
up to 256 bytes per session.
storeIsrRscvs
If present, specifies that route selection control vectors (RSCV)
should be stored for diagnostic purposes on intermediate session
routing (ISR) sessions. Note that selecting this value means that an
RSCV will be stored for each ISR session. This extra storage can be
up to 256 bytes per session.
Description of bits:
multipleDomainSupport(0)
registerWithCDS(1)
storeEndptRscvs(2)
storeIsrRscvs(3)
|
appnMaximumLocates |
.1.3.6.1.4.1.562.2.4.1.110.101.1.7 |
This attribute represents the maximum number of locate requests
the node can handle simultaneously. Attribute locateTimeout should
be set to ensure that locate requests can timeout, thereby freeing up
node resources.
|
appnMaximumDirectorySize |
.1.3.6.1.4.1.562.2.4.1.110.101.1.8 |
This attribute contains the maximum number of SnaDirectoryEntry
components that can be defined or learned by this node. A value of
zero means unlimited.
|
appnMdsTxAlertQueueSize |
.1.3.6.1.4.1.562.2.4.1.110.101.1.9 |
This is the size of Multiple Domain Support send alert queue. When
the limit is reached, the MDS component deletes the oldest entry in
the queue.
|
appnTreeCacheSize |
.1.3.6.1.4.1.562.2.4.1.110.101.1.10 |
This is the topology database routing tree cache size.
|
appnTreeCacheUseLimit |
.1.3.6.1.4.1.562.2.4.1.110.101.1.11 |
This is the number of times a cached tree can be reused. Once this
number is exceeded, the tree is discarded and recomputed. This
allows the node to balance sessions among equal weight routes. A
low value provides better load balancing at the expense of increased
activation latency. The minimum is 1.
|
appnMaximumTopologyNodes |
.1.3.6.1.4.1.562.2.4.1.110.101.1.12 |
This is the maximum number of Appn network nodes that can be
stored in the Topology Database (zero means unlimited).
|
appnMaximumTopologyTgs |
.1.3.6.1.4.1.562.2.4.1.110.101.1.13 |
This is the maximum number of Transmission Groups that can be
stored in the Topology Database (zero means unlimited).
|
appnMaximumIsrSessions |
.1.3.6.1.4.1.562.2.4.1.110.101.1.14 |
This attribute represents the maximum number of ISR sessions this
node can participate in at once. The minimum value is 100.
|
appnIsrUpperCongestionThreshold |
.1.3.6.1.4.1.562.2.4.1.110.101.1.15 |
This is the upper threshold for ISR sessions. This attribute and the
following one control the node's ISR congestion status. The node
state changes from uncongested to congested if the number of ISR
sessions exceeds the upper threshold. The node state changes back
to uncongested once the number of ISR sessions dips below the
lower threshold. To prevent thrashing, the lower threshold should be
less than the upper threshold. The upper threshold should be lower
than maximumIsrSessions.
|
appnIsrLowerCongestionThreshold |
.1.3.6.1.4.1.562.2.4.1.110.101.1.16 |
This is the lower threshold for the ISR session congestion
algorithm. This value should be less than
isrUpperCongestionThreshold.
|
appnIsrMaxRuSize |
.1.3.6.1.4.1.562.2.4.1.110.101.1.17 |
Maximum request unit (RU) size supported for intermediate routing
(ISR) sessions.
|
appnIsrRxPacingWindow |
.1.3.6.1.4.1.562.2.4.1.110.101.1.18 |
This is the suggested receive pacing window size for intermediate
sessions. This value is only used on the secondary hop of
intermediate sessions if the adjacent node does not support adaptive
pacing. A value of zero means that no pacing will occur.
|
appnLocateTimeout |
.1.3.6.1.4.1.562.2.4.1.110.101.1.19 |
This attribute specifies the time in seconds before a network search
will time-out. A value of zero indicates that the search has no time
limit.
|
appnHprSupport |
.1.3.6.1.4.1.562.2.4.1.110.101.1.20 |
This attribute specifies the type of High Performance Routing
(HPR) that is to be used on this node. The options are: none - the
node does not support HPR, anrOnly - the node only supports
Automatic Network Routing (ANR), or rtp - the node supports
Rapid Transport Protocol as an end point.
The default value of rtp ensures that the node can Aping other nodes
via a HPR pipe, this option is also required to allow dependent LU
sessions teminating on this node to use HPR and for the node to act
as a boundary node between ISR only nodes and the HPR capable
portion of the network. With this option, the node can work with
non-HPR capable nodes.
|
appnDlurSupport |
.1.3.6.1.4.1.562.2.4.1.110.101.1.21 |
This attribute specifies whether or not this node supports dependent
logical unit requestor (DLUR). By default, DLUR is not supported.
If this attribute is set to yes, ensure that the Dlur subcomponent is
provisioned with appropriate values, if this attribute is set to no, the
Dlur subcomponent is not used and is ignored if present.
|
appnAdminState |
.1.3.6.1.4.1.562.2.4.1.110.102.1.1 |
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.
|
appnOperationalState |
.1.3.6.1.4.1.562.2.4.1.110.102.1.2 |
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.
|
appnUsageState |
.1.3.6.1.4.1.562.2.4.1.110.102.1.3 |
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.
|
appnUpTime |
.1.3.6.1.4.1.562.2.4.1.110.103.1.1 |
This attribute represents the time in hundredths of a second since
the node was started or restarted.
|
appnHeapSpaceLimit |
.1.3.6.1.4.1.562.2.4.1.110.103.1.2 |
This attribute represents the size of the heap in bytes, as obtained by
storage management from the underlying operating system.
|
appnHeapSpaceCurrent |
.1.3.6.1.4.1.562.2.4.1.110.103.1.3 |
This attribute contains the number of bytes in the memory segment
that are currently allocated to the processes associated with the
Appn component.
SNMP APPN MIB = ibmappnMemoryUsed
|
appnMemWarningThreshold |
.1.3.6.1.4.1.562.2.4.1.110.103.1.4 |
This attribute contains the memory allocation threshold beyond
which storage management considers the storage resources to be
constrained. This is calculated as a fraction of heapSpaceLimit.
The value returned now is always zero until the functionality is
supported in future release.
SNMP APPN MIB = ibmappnMemoryWarnThresh
|
appnMemCriticalThreshold |
.1.3.6.1.4.1.562.2.4.1.110.103.1.5 |
This attribute represents the memory allocation threshold beyond
which storage management considers the storage resources to be
critically constrained. The value is calculated as a fraction of
heapSpaceLimit.
The value returned now is always zero until the functionality is
supported in future release.
|
appnNnFunctionsSupported |
.1.3.6.1.4.1.562.2.4.1.110.103.1.6 |
The network node functions supported may include any of the
following:
receiveRegistration - If present, indicates that this node supports
receiving registered characteristics on a GDS frame. This function
is not supported in the current release.
gateway - If present, indicates that this is a gateway node.
centralDirectoryServer - If present, indicates that this node
supports central directory server cache.
treeCaching -If present, indicates that this node supports route tree
cache.
treeUpdates - If present, indicates that this node supports
incremental tree update, which is only supported when tree caching
is supported.
intermediateSessionRouting - Indicates that the node supports
intermediate session routing.
Description of bits:
receiveRegistration(0)
gateway(1)
centralDirectoryServer(2)
treeCaching(3)
treeUpdates(4)
intermediateSessionRouting(5)
|
appnGeneralFunctionsSupported |
.1.3.6.1.4.1.562.2.4.1.110.103.1.7 |
The general functions supported may include any of the following:
negotiableLs -If present, indicates that this node supports
negotiable link stations.
segmentReassembly -If present, indicates whether this node
supports segment reassembly. This is only supported when segment
generation is also supported.
bindReassembly -If present, indicates whether this node supports
Bind segment reassembly. This will only be supported when Bind
segment generation is also supported.
parallelTgs -If present, indicates whether this node supports parallel
TGs.
callIn - If present, indicates whether this node allows call-in from
nodes not defined locally.
adaptivePacing - If present, indicates whether this node supports
adaptive bind pacing.
Description of bits:
negotiableLs(0)
segmentReassembly(1)
bindReassembly(2)
parallelTgs(3)
callIn(4)
adaptivePacing(5)
|
appnStatus |
.1.3.6.1.4.1.562.2.4.1.110.103.1.8 |
This attribute contains the status of the node. This may be
nodeUncongested or one or more of the following:
isrCongested
The number of ISR sessions is greater than specified by the
isrSessionsUpperThreshold attribute. This node is not be included
in route selection by other nodes when this congestion exists.
endPtDepleted
The number of end-point sessions has reached the maximum
specified.
isrDepleted
The number of ISR sessions has reached the maximum specified by
the maximumIsrSessions attribute. This node is not included in
intermediate route selection by other nodes when resources are
depleted.
quiescing
Indicates whether the node is quiescing. This node is not included
in route selection by other nodes when the node is quiescing.
Description of bits:
nodeUncongested(0)
notused1(1)
quiescing(2)
notused3(3)
notused4(4)
endPtDepleted(5)
isrDepleted(6)
isrCongested(7)
|
appnFlowReductionSequenceNumber |
.1.3.6.1.4.1.562.2.4.1.110.103.1.9 |
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 object is the last FRSN sent in a topology
update the adjacent network nodes.
SNMP APPN MIB = ibmappnNodeNnFrsn
|
appnResourceSequenceNumber |
.1.3.6.1.4.1.562.2.4.1.110.103.1.10 |
Resource sequence number of this Appn network node.
|
appnDefinedLsGoodXids |
.1.3.6.1.4.1.562.2.4.1.110.103.1.11 |
This attribute represents the total number of successful XIDs that
have been received on all defined link stations since the last time
this node was initialized. When the upper limit is reached, the
number wraps around to 0.
|
appnDefinedLsBadXids |
.1.3.6.1.4.1.562.2.4.1.110.103.1.12 |
This attribute represents the total number of unsuccessful XIDs that
have been received on all defined link stations since the last time
this node was initialized. When the upper limit is reached, the
number wraps around to 0.
|
appnDynamicLsGoodXids |
.1.3.6.1.4.1.562.2.4.1.110.103.1.13 |
This attribute represents the total number of successful XIDs that
have been received on all dynamic link stations since the last time
this node was initialized. When the upper limit is reached, the
number wraps around to 0.
|
appnDynamicLsBadXids |
.1.3.6.1.4.1.562.2.4.1.110.103.1.14 |
This attribute represents the total number of unsuccessful XIDs that
have been received on all dynamic link stations since the last time
this node was initialized. When the upper limit is reached, the
number wraps around to 0.
|
appnActiveSvcs |
.1.3.6.1.4.1.562.2.4.1.110.103.1.15 |
This attribute indicates the number of general switched virtual
circuits (GSVC) on this Appn node at the time of the query. This
attribute does not include the Frame Relay switched virtual circuits.
|
appnActiveLinkStations |
.1.3.6.1.4.1.562.2.4.1.110.103.1.16 |
This attribute indicates the number of link stations (for GSVCs,
Frame Relay PVCs and SVCs) on the Appn node at the time of the
query.
|
appnDnaIndex |
.1.3.6.1.4.1.562.2.4.1.110.2.1.1.10 |
This variable represents the index for the appnDna tables.
|
appnDnaRowStatus |
.1.3.6.1.4.1.562.2.4.1.110.2.1.1.1 |
This variable is used as the basis for SNMP naming of
appnDna components.
These components cannot be added nor deleted.
|
appnDnaComponentName |
.1.3.6.1.4.1.562.2.4.1.110.2.1.1.2 |
This variable provides the component's string name for
use with the ASCII Console Interface
|
appnDnaStorageType |
.1.3.6.1.4.1.562.2.4.1.110.2.1.1.4 |
This variable represents the storage type value for the
appnDna tables.
|
appnDnaNumberingPlanIndicator |
.1.3.6.1.4.1.562.2.4.1.110.2.10.1.1 |
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.
|
appnDnaDataNetworkAddress |
.1.3.6.1.4.1.562.2.4.1.110.2.10.1.2 |
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.
|
appnDnaOutDefaultPriority |
.1.3.6.1.4.1.562.2.4.1.110.2.12.1.7 |
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.
|
appnDnaOutDefaultPathSensitivity |
.1.3.6.1.4.1.562.2.4.1.110.2.12.1.11 |
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.
|
appnDnaOutPathSensitivityOverRide |
.1.3.6.1.4.1.562.2.4.1.110.2.12.1.12 |
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,
|
appnDnaOutDefaultPathReliability |
.1.3.6.1.4.1.562.2.4.1.110.2.12.1.14 |
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.
|
appnDnaOutAccess |
.1.3.6.1.4.1.562.2.4.1.110.2.12.1.17 |
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.
|
appnDnaDefaultTransferPriority |
.1.3.6.1.4.1.562.2.4.1.110.2.12.1.18 |
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.
|
appnDnaTransferPriorityOverRide |
.1.3.6.1.4.1.562.2.4.1.110.2.12.1.19 |
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.
|
appnDnaIncAccess |
.1.3.6.1.4.1.562.2.4.1.110.2.13.1.9 |
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.
|
appnDnaDefaultRecvFrmNetworkThruputClass |
.1.3.6.1.4.1.562.2.4.1.110.2.14.1.5 |
This attribute indicates the default receive throughput class for all
calls using this particular Dna.
|
appnDnaDefaultSendToNetworkThruputClass |
.1.3.6.1.4.1.562.2.4.1.110.2.14.1.6 |
This attribute indicates the default send throughput class for all calls
using this particular Dna.
|
appnDnaDefaultRecvFrmNetworkWindowSize |
.1.3.6.1.4.1.562.2.4.1.110.2.14.1.7 |
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.
|
appnDnaDefaultSendToNetworkWindowSize |
.1.3.6.1.4.1.562.2.4.1.110.2.14.1.8 |
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.
|
appnDnaAccountClass |
.1.3.6.1.4.1.562.2.4.1.110.2.14.1.10 |
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.
|
appnDnaAccountCollection |
.1.3.6.1.4.1.562.2.4.1.110.2.14.1.11 |
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)
|
appnDnaServiceExchange |
.1.3.6.1.4.1.562.2.4.1.110.2.14.1.12 |
This attribute is an arbitrary number, entered by the network
operator. It is included in the accounting record created by Vc.
|
appnDnaHgMIndex |
.1.3.6.1.4.1.562.2.4.1.110.2.2.1.1.10 |
This variable represents the index for the appnDnaHgM tables.
|
appnDnaHgMRowStatus |
.1.3.6.1.4.1.562.2.4.1.110.2.2.1.1.1 |
This variable is used as the basis for SNMP naming of
appnDnaHgM components.
These components can be added and deleted.
|
appnDnaHgMComponentName |
.1.3.6.1.4.1.562.2.4.1.110.2.2.1.1.2 |
This variable provides the component's string name for
use with the ASCII Console Interface
|
appnDnaHgMStorageType |
.1.3.6.1.4.1.562.2.4.1.110.2.2.1.1.4 |
This variable represents the storage type value for the
appnDnaHgM tables.
|
appnDnaHgMAvailabilityUpdateThreshold |
.1.3.6.1.4.1.562.2.4.1.110.2.2.10.1.1 |
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.
|
appnDnaHgMMaxAvailableChannels |
.1.3.6.1.4.1.562.2.4.1.110.2.2.11.1.1 |
This attribute indicates the maximum number of available channels
for this HuntGroupMember.
|
appnDnaHgMAvailableChannels |
.1.3.6.1.4.1.562.2.4.1.110.2.2.11.1.2 |
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.
|
appnDnaHgMAvailabilityDelta |
.1.3.6.1.4.1.562.2.4.1.110.2.2.11.1.3 |
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.
|
appnDnaHgMHgAddrIndex |
.1.3.6.1.4.1.562.2.4.1.110.2.2.2.1.1.10 |
This variable represents the index for the appnDnaHgMHgAddr tables.
|
appnDnaHgMHgAddrRowStatus |
.1.3.6.1.4.1.562.2.4.1.110.2.2.2.1.1.1 |
This variable is used as the basis for SNMP naming of
appnDnaHgMHgAddr components.
These components can be added and deleted.
|
appnDnaHgMHgAddrComponentName |
.1.3.6.1.4.1.562.2.4.1.110.2.2.2.1.1.2 |
This variable provides the component's string name for
use with the ASCII Console Interface
|
appnDnaHgMHgAddrStorageType |
.1.3.6.1.4.1.562.2.4.1.110.2.2.2.1.1.4 |
This variable represents the storage type value for the
appnDnaHgMHgAddr tables.
|
appnDnaHgMHgAddrNumberingPlanIndicator |
.1.3.6.1.4.1.562.2.4.1.110.2.2.2.10.1.1 |
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.
|
appnDnaHgMHgAddrDataNetworkAddress |
.1.3.6.1.4.1.562.2.4.1.110.2.2.2.10.1.2 |
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.
|
appnDnaCugIndex |
.1.3.6.1.4.1.562.2.4.1.110.2.3.1.1.10 |
This variable represents the index for the appnDnaCug tables.
|
appnDnaCugRowStatus |
.1.3.6.1.4.1.562.2.4.1.110.2.3.1.1.1 |
This variable is used as the basis for SNMP naming of
appnDnaCug components.
These components can be added and deleted.
|
appnDnaCugComponentName |
.1.3.6.1.4.1.562.2.4.1.110.2.3.1.1.2 |
This variable provides the component's string name for
use with the ASCII Console Interface
|
appnDnaCugStorageType |
.1.3.6.1.4.1.562.2.4.1.110.2.3.1.1.4 |
This variable represents the storage type value for the
appnDnaCug tables.
|
appnDnaCugType |
.1.3.6.1.4.1.562.2.4.1.110.2.3.10.1.1 |
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.
|
appnDnaCugDnic |
.1.3.6.1.4.1.562.2.4.1.110.2.3.10.1.2 |
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.
|
appnDnaCugInterlockCode |
.1.3.6.1.4.1.562.2.4.1.110.2.3.10.1.3 |
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.
|
appnDnaCugPreferential |
.1.3.6.1.4.1.562.2.4.1.110.2.3.10.1.4 |
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.
|
appnDnaCugOutCalls |
.1.3.6.1.4.1.562.2.4.1.110.2.3.10.1.5 |
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.
|
appnDnaCugIncCalls |
.1.3.6.1.4.1.562.2.4.1.110.2.3.10.1.6 |
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.
|
appnDnaCugPrivileged |
.1.3.6.1.4.1.562.2.4.1.110.2.3.10.1.7 |
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.
|
appnDlciIndex |
.1.3.6.1.4.1.562.2.4.1.110.3.1.1.10 |
This variable represents the index for the appnDlci tables.
|
appnDlciRowStatus |
.1.3.6.1.4.1.562.2.4.1.110.3.1.1.1 |
This variable is used as the basis for SNMP naming of
appnDlci components.
These components can be added and deleted.
|
appnDlciComponentName |
.1.3.6.1.4.1.562.2.4.1.110.3.1.1.2 |
This variable provides the component's string name for
use with the ASCII Console Interface
|
appnDlciStorageType |
.1.3.6.1.4.1.562.2.4.1.110.3.1.1.4 |
This variable represents the storage type value for the
appnDlci tables.
|
appnDlciAdminState |
.1.3.6.1.4.1.562.2.4.1.110.3.10.1.1 |
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.
|
appnDlciOperationalState |
.1.3.6.1.4.1.562.2.4.1.110.3.10.1.2 |
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.
|
appnDlciUsageState |
.1.3.6.1.4.1.562.2.4.1.110.3.10.1.3 |
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.
|
appnDlciRateEnforcement |
.1.3.6.1.4.1.562.2.4.1.110.3.12.1.1 |
This attribute indicates whether rate enforcement is in use
for this Dlci.
|
appnDlciCommittedInformationRate |
.1.3.6.1.4.1.562.2.4.1.110.3.12.1.2 |
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.
|
appnDlciCommittedBurstSize |
.1.3.6.1.4.1.562.2.4.1.110.3.12.1.3 |
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.
|
appnDlciExcessInformationRate |
.1.3.6.1.4.1.562.2.4.1.110.3.12.1.4 |
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.
|
appnDlciExcessBurstSize |
.1.3.6.1.4.1.562.2.4.1.110.3.12.1.5 |
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.
|
appnDlciMeasurementInterval |
.1.3.6.1.4.1.562.2.4.1.110.3.12.1.6 |
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.
|
appnDlciDcIndex |
.1.3.6.1.4.1.562.2.4.1.110.3.2.1.1.10 |
This variable represents the index for the appnDlciDc tables.
|
appnDlciDcRowStatus |
.1.3.6.1.4.1.562.2.4.1.110.3.2.1.1.1 |
This variable is used as the basis for SNMP naming of
appnDlciDc components.
These components cannot be added nor deleted.
|
appnDlciDcComponentName |
.1.3.6.1.4.1.562.2.4.1.110.3.2.1.1.2 |
This variable provides the component's string name for
use with the ASCII Console Interface
|
appnDlciDcStorageType |
.1.3.6.1.4.1.562.2.4.1.110.3.2.1.1.4 |
This variable represents the storage type value for the
appnDlciDc tables.
|
appnDlciDcRemoteNpi |
.1.3.6.1.4.1.562.2.4.1.110.3.2.10.1.3 |
This attribute specifies the numbering plan used for remoteDna.
|
appnDlciDcRemoteDna |
.1.3.6.1.4.1.562.2.4.1.110.3.2.10.1.4 |
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.
|
appnDlciDcRemoteDlci |
.1.3.6.1.4.1.562.2.4.1.110.3.2.10.1.5 |
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.
|
appnDlciDcType |
.1.3.6.1.4.1.562.2.4.1.110.3.2.10.1.6 |
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.
|
appnDlciDcTransferPriority |
.1.3.6.1.4.1.562.2.4.1.110.3.2.10.1.9 |
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.
|
appnDlciDcDiscardPriority |
.1.3.6.1.4.1.562.2.4.1.110.3.2.10.1.10 |
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.
|
appnDlciDcNfaIndex |
.1.3.6.1.4.1.562.2.4.1.110.3.2.283.1.1 |
This variable represents the index for the appnDlciDcNfaTable.
|
appnDlciDcNfaValue |
.1.3.6.1.4.1.562.2.4.1.110.3.2.283.1.2 |
This variable represents an individual value for the
appnDlciDcNfaTable.
|
appnDlciDcNfaRowStatus |
.1.3.6.1.4.1.562.2.4.1.110.3.2.283.1.3 |
This variable is used to control the addition and deletion
of individual values of the appnDlciDcNfaTable.
|
appnDlciVcIndex |
.1.3.6.1.4.1.562.2.4.1.110.3.3.1.1.10 |
This variable represents the index for the appnDlciVc tables.
|
appnDlciVcRowStatus |
.1.3.6.1.4.1.562.2.4.1.110.3.3.1.1.1 |
This variable is used as the basis for SNMP naming of
appnDlciVc components.
These components cannot be added nor deleted.
|
appnDlciVcComponentName |
.1.3.6.1.4.1.562.2.4.1.110.3.3.1.1.2 |
This variable provides the component's string name for
use with the ASCII Console Interface
|
appnDlciVcStorageType |
.1.3.6.1.4.1.562.2.4.1.110.3.3.1.1.4 |
This variable represents the storage type value for the
appnDlciVc tables.
|
appnDlciVcType |
.1.3.6.1.4.1.562.2.4.1.110.3.3.10.1.1 |
This attribute displays the type of call, pvc,svc or spvc.
|
appnDlciVcState |
.1.3.6.1.4.1.562.2.4.1.110.3.3.10.1.2 |
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.
|
appnDlciVcPreviousState |
.1.3.6.1.4.1.562.2.4.1.110.3.3.10.1.3 |
This attribute displays the previous state of call control. This is a
valuable field to determine how the processing is progressing.
|
appnDlciVcDiagnosticCode |
.1.3.6.1.4.1.562.2.4.1.110.3.3.10.1.4 |
This attribute displays the internal substate of call control. It is used
to further refine state of call processing.
|
appnDlciVcPreviousDiagnosticCode |
.1.3.6.1.4.1.562.2.4.1.110.3.3.10.1.5 |
This attribute displays the internal substate of call control. It is used
to further refine state of call processing.
|
appnDlciVcCalledNpi |
.1.3.6.1.4.1.562.2.4.1.110.3.3.10.1.6 |
This attribute displays the Numbering Plan Indicator (NPI) of the
called end.
|
appnDlciVcCalledDna |
.1.3.6.1.4.1.562.2.4.1.110.3.3.10.1.7 |
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.
|
appnDlciVcCalledLcn |
.1.3.6.1.4.1.562.2.4.1.110.3.3.10.1.8 |
This attribute displays the Logical Channel Number of the called
end. It is valid only after both ends of Vc exchanged relevant
information.
|
appnDlciVcCallingNpi |
.1.3.6.1.4.1.562.2.4.1.110.3.3.10.1.9 |
This attribute displays the Numbering Plan Indicator (NPI) of the
calling end.
|
appnDlciVcCallingDna |
.1.3.6.1.4.1.562.2.4.1.110.3.3.10.1.10 |
This attribute displays the Data Network Address (Dna) of the
calling end.
|
appnDlciVcCallingLcn |
.1.3.6.1.4.1.562.2.4.1.110.3.3.10.1.11 |
This attribute displays the Logical Channel Number of the calling
end.
|
appnDlciVcAccountingEnabled |
.1.3.6.1.4.1.562.2.4.1.110.3.3.10.1.12 |
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.
|
appnDlciVcFastSelectCall |
.1.3.6.1.4.1.562.2.4.1.110.3.3.10.1.13 |
This attribute displays that this is a fast select call.
|
appnDlciVcPathReliability |
.1.3.6.1.4.1.562.2.4.1.110.3.3.10.1.19 |
This attribute displays the path reliability.
|
appnDlciVcAccountingEnd |
.1.3.6.1.4.1.562.2.4.1.110.3.3.10.1.20 |
This attribute indicates if this end should generate an accounting
record. Normally, callingEnd is the end to generate an accounting
record.
|
appnDlciVcPriority |
.1.3.6.1.4.1.562.2.4.1.110.3.3.10.1.21 |
This attribute displays whether the call is a normal or a high
priority call.
|
appnDlciVcSegmentSize |
.1.3.6.1.4.1.562.2.4.1.110.3.3.10.1.22 |
This attribute displays the segment size (in bytes) used on the call.
It is used to calculate the number of segments transmitted and
received.
|
appnDlciVcMaxSubnetPktSize |
.1.3.6.1.4.1.562.2.4.1.110.3.3.10.1.27 |
This attribute indicates the maximum packet size allowed on the Vc.
|
appnDlciVcRcosToNetwork |
.1.3.6.1.4.1.562.2.4.1.110.3.3.10.1.28 |
This attribute indicates the routing metric routing class of service to
the network.
|
appnDlciVcRcosFromNetwork |
.1.3.6.1.4.1.562.2.4.1.110.3.3.10.1.29 |
This attribute displays the routing metric Routing Class of Service
from the Network.
|
appnDlciVcEmissionPriorityToNetwork |
.1.3.6.1.4.1.562.2.4.1.110.3.3.10.1.30 |
This attribute displays the network internal emission priotity to the
network.
|
appnDlciVcEmissionPriorityFromNetwork |
.1.3.6.1.4.1.562.2.4.1.110.3.3.10.1.31 |
This attribute displays the network internal emission priotity from
the network.
|
appnDlciVcDataPath |
.1.3.6.1.4.1.562.2.4.1.110.3.3.10.1.32 |
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.
|
appnDlciVcCallReferenceNumber |
.1.3.6.1.4.1.562.2.4.1.110.3.3.11.1.1 |
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.
|
appnDlciVcElapsedTimeTillNow |
.1.3.6.1.4.1.562.2.4.1.110.3.3.11.1.2 |
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.
|
appnDlciVcSegmentsRx |
.1.3.6.1.4.1.562.2.4.1.110.3.3.11.1.3 |
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.
|
appnDlciVcSegmentsSent |
.1.3.6.1.4.1.562.2.4.1.110.3.3.11.1.4 |
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.
|
appnDlciVcStartTime |
.1.3.6.1.4.1.562.2.4.1.110.3.3.11.1.5 |
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.
|
appnDlciVcFrmCongestedToSubnet |
.1.3.6.1.4.1.562.2.4.1.110.3.3.12.1.2 |
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.
|
appnDlciVcCannotForwardToSubnet |
.1.3.6.1.4.1.562.2.4.1.110.3.3.12.1.3 |
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.
|
appnDlciVcNotDataXferToSubnet |
.1.3.6.1.4.1.562.2.4.1.110.3.3.12.1.4 |
This attribute records the number of frames from link discarded
when the Vc tries to recover from internal path failure.
|
appnDlciVcOutOfRangeFrmFromSubnet |
.1.3.6.1.4.1.562.2.4.1.110.3.3.12.1.5 |
This attribute displays the number of frames from subnet discarded
due to out of sequence range for arriving too late.
|
appnDlciVcCombErrorsFromSubnet |
.1.3.6.1.4.1.562.2.4.1.110.3.3.12.1.6 |
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
|
appnDlciVcDuplicatesFromSubnet |
.1.3.6.1.4.1.562.2.4.1.110.3.3.12.1.7 |
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.
|
appnDlciVcNotDataXferFromSubnet |
.1.3.6.1.4.1.562.2.4.1.110.3.3.12.1.8 |
This attribute displays the number of subnet packets discarded when
data transfer is suspended in Vc recovery.
|
appnDlciVcFrmLossTimeouts |
.1.3.6.1.4.1.562.2.4.1.110.3.3.12.1.9 |
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.
|
appnDlciVcOoSeqByteCntExceeded |
.1.3.6.1.4.1.562.2.4.1.110.3.3.12.1.10 |
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.
|
appnDlciVcPeakOoSeqPktCount |
.1.3.6.1.4.1.562.2.4.1.110.3.3.12.1.11 |
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.
|
appnDlciVcPeakOoSeqFrmForwarded |
.1.3.6.1.4.1.562.2.4.1.110.3.3.12.1.12 |
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.
|
appnDlciVcSendSequenceNumber |
.1.3.6.1.4.1.562.2.4.1.110.3.3.12.1.13 |
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.
|
appnDlciVcPktRetryTimeouts |
.1.3.6.1.4.1.562.2.4.1.110.3.3.12.1.15 |
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.
|
appnDlciVcPeakRetryQueueSize |
.1.3.6.1.4.1.562.2.4.1.110.3.3.12.1.16 |
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.
|
appnDlciVcSubnetRecoveries |
.1.3.6.1.4.1.562.2.4.1.110.3.3.12.1.17 |
This attribute displays the number of successful Vc recovery
attempts.
|
appnDlciVcOoSeqPktCntExceeded |
.1.3.6.1.4.1.562.2.4.1.110.3.3.12.1.19 |
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.
|
appnDlciVcPeakOoSeqByteCount |
.1.3.6.1.4.1.562.2.4.1.110.3.3.12.1.20 |
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.
|
appnDlciVcDmepValue |
.1.3.6.1.4.1.562.2.4.1.110.3.3.417.1.1 |
This variable represents both the value and the index for the
appnDlciVcDmepTable.
|
appnDlciBnnLsDefIndex |
.1.3.6.1.4.1.562.2.4.1.110.3.4.1.1.10 |
This variable represents the index for the appnDlciBnnLsDef tables.
|
appnDlciBnnLsDefRowStatus |
.1.3.6.1.4.1.562.2.4.1.110.3.4.1.1.1 |
This variable is used as the basis for SNMP naming of
appnDlciBnnLsDef components.
These components can be added and deleted.
|
appnDlciBnnLsDefComponentName |
.1.3.6.1.4.1.562.2.4.1.110.3.4.1.1.2 |
This variable provides the component's string name for
use with the ASCII Console Interface
|
appnDlciBnnLsDefStorageType |
.1.3.6.1.4.1.562.2.4.1.110.3.4.1.1.4 |
This variable represents the storage type value for the
appnDlciBnnLsDef tables.
|
appnDlciBnnLsDefDspuService |
.1.3.6.1.4.1.562.2.4.1.110.3.4.2.1.1 |
This attribute specifies which down stream physical unit service is
supported on this Link Station.
|
appnDlciBnnLsDefAdjacentCpName |
.1.3.6.1.4.1.562.2.4.1.110.3.4.2.1.2 |
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.
|
appnDlciBnnLsDefAdjacentCpType |
.1.3.6.1.4.1.562.2.4.1.110.3.4.2.1.3 |
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
|
appnDlciBnnLsDefTgNum |
.1.3.6.1.4.1.562.2.4.1.110.3.4.2.1.5 |
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.
|
appnDlciBnnLsDefDlusName |
.1.3.6.1.4.1.562.2.4.1.110.3.4.2.1.6 |
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.
|
appnDlciBnnLsDefBackupDlusName |
.1.3.6.1.4.1.562.2.4.1.110.3.4.2.1.7 |
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.
|
appnDlciBnnLsDefHprSupported |
.1.3.6.1.4.1.562.2.4.1.110.3.4.2.1.8 |
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
|
appnDlciBnnLsDefAdjacentNodeID |
.1.3.6.1.4.1.562.2.4.1.110.3.4.2.1.9 |
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.
|
appnDlciBnnLsDefCpCpSessionSupport |
.1.3.6.1.4.1.562.2.4.1.110.3.4.2.1.10 |
This attribute specifies whether this link station supports CP-CP
sessions. This attribute is ignored if the adjacent device is not an
APPN node.
|
appnDlciBnnLsDefMaxTxBtuSize |
.1.3.6.1.4.1.562.2.4.1.110.3.4.2.1.11 |
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.
|
appnDlciBnnLsDefLsRole |
.1.3.6.1.4.1.562.2.4.1.110.3.4.2.1.12 |
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).
|
appnDlciSpIndex |
.1.3.6.1.4.1.562.2.4.1.110.3.5.1.1.10 |
This variable represents the index for the appnDlciSp tables.
|
appnDlciSpRowStatus |
.1.3.6.1.4.1.562.2.4.1.110.3.5.1.1.1 |
This variable is used as the basis for SNMP naming of
appnDlciSp components.
These components cannot be added nor deleted.
|
appnDlciSpComponentName |
.1.3.6.1.4.1.562.2.4.1.110.3.5.1.1.2 |
This variable provides the component's string name for
use with the ASCII Console Interface
|
appnDlciSpStorageType |
.1.3.6.1.4.1.562.2.4.1.110.3.5.1.1.4 |
This variable represents the storage type value for the
appnDlciSp tables.
|
appnDlciSpRateEnforcement |
.1.3.6.1.4.1.562.2.4.1.110.3.5.11.1.1 |
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.
|
appnDlciSpCommittedInformationRate |
.1.3.6.1.4.1.562.2.4.1.110.3.5.11.1.2 |
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.
|
appnDlciSpCommittedBurstSize |
.1.3.6.1.4.1.562.2.4.1.110.3.5.11.1.3 |
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.
|
appnDlciSpExcessBurstSize |
.1.3.6.1.4.1.562.2.4.1.110.3.5.11.1.4 |
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.
|
appnDlciSpMeasurementInterval |
.1.3.6.1.4.1.562.2.4.1.110.3.5.11.1.5 |
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.
|
appnDlciBanLsDefMacIndex |
.1.3.6.1.4.1.562.2.4.1.110.3.6.1.1.10 |
This variable represents an index for the appnDlciBanLsDef tables.
|
appnDlciBanLsDefSapIndex |
.1.3.6.1.4.1.562.2.4.1.110.3.6.1.1.11 |
This variable represents an index for the appnDlciBanLsDef tables.
|
appnDlciBanLsDefRowStatus |
.1.3.6.1.4.1.562.2.4.1.110.3.6.1.1.1 |
This variable is used as the basis for SNMP naming of
appnDlciBanLsDef components.
These components can be added and deleted.
|
appnDlciBanLsDefComponentName |
.1.3.6.1.4.1.562.2.4.1.110.3.6.1.1.2 |
This variable provides the component's string name for
use with the ASCII Console Interface
|
appnDlciBanLsDefStorageType |
.1.3.6.1.4.1.562.2.4.1.110.3.6.1.1.4 |
This variable represents the storage type value for the
appnDlciBanLsDef tables.
|
appnDlciBanLsDefDspuService |
.1.3.6.1.4.1.562.2.4.1.110.3.6.2.1.1 |
This attribute specifies which down stream physical unit service is
supported on this Link Station.
|
appnDlciBanLsDefAdjacentCpName |
.1.3.6.1.4.1.562.2.4.1.110.3.6.2.1.2 |
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.
|
appnDlciBanLsDefAdjacentCpType |
.1.3.6.1.4.1.562.2.4.1.110.3.6.2.1.3 |
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
|
appnDlciBanLsDefTgNum |
.1.3.6.1.4.1.562.2.4.1.110.3.6.2.1.5 |
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.
|
appnDlciBanLsDefDlusName |
.1.3.6.1.4.1.562.2.4.1.110.3.6.2.1.6 |
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.
|
appnDlciBanLsDefBackupDlusName |
.1.3.6.1.4.1.562.2.4.1.110.3.6.2.1.7 |
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.
|
appnDlciBanLsDefHprSupported |
.1.3.6.1.4.1.562.2.4.1.110.3.6.2.1.8 |
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
|
appnDlciBanLsDefAdjacentNodeID |
.1.3.6.1.4.1.562.2.4.1.110.3.6.2.1.9 |
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.
|
appnDlciBanLsDefCpCpSessionSupport |
.1.3.6.1.4.1.562.2.4.1.110.3.6.2.1.10 |
This attribute specifies whether this link station supports CP-CP
sessions. This attribute is ignored if the adjacent device is not an
APPN node.
|
appnDlciBanLsDefMaxTxBtuSize |
.1.3.6.1.4.1.562.2.4.1.110.3.6.2.1.11 |
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.
|
appnDlciBanLsDefLsRole |
.1.3.6.1.4.1.562.2.4.1.110.3.6.2.1.12 |
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).
|
appnDlciBanIndex |
.1.3.6.1.4.1.562.2.4.1.110.3.7.1.1.10 |
This variable represents the index for the appnDlciBan tables.
|
appnDlciBanRowStatus |
.1.3.6.1.4.1.562.2.4.1.110.3.7.1.1.1 |
This variable is used as the basis for SNMP naming of
appnDlciBan components.
These components can be added and deleted.
|
appnDlciBanComponentName |
.1.3.6.1.4.1.562.2.4.1.110.3.7.1.1.2 |
This variable provides the component's string name for
use with the ASCII Console Interface
|
appnDlciBanStorageType |
.1.3.6.1.4.1.562.2.4.1.110.3.7.1.1.4 |
This variable represents the storage type value for the
appnDlciBan tables.
|
appnDlciBanLocalMac |
.1.3.6.1.4.1.562.2.4.1.110.3.7.2.1.1 |
This attribute specifies the MAC address to be used for a Frame
Relay connection with BAN encapsulation.
|
appnDlciBanLocalSap |
.1.3.6.1.4.1.562.2.4.1.110.3.7.2.1.2 |
This attribute specifies the local SAP number to be used for a
Frame Relay connection with BAN encapsulation.
|
appnDlciCnIndex |
.1.3.6.1.4.1.562.2.4.1.110.3.8.1.1.10 |
This variable represents the index for the appnDlciCn tables.
|
appnDlciCnRowStatus |
.1.3.6.1.4.1.562.2.4.1.110.3.8.1.1.1 |
This variable is used as the basis for SNMP naming of
appnDlciCn components.
These components can be added and deleted.
|
appnDlciCnComponentName |
.1.3.6.1.4.1.562.2.4.1.110.3.8.1.1.2 |
This variable provides the component's string name for
use with the ASCII Console Interface
|
appnDlciCnStorageType |
.1.3.6.1.4.1.562.2.4.1.110.3.8.1.1.4 |
This variable represents the storage type value for the
appnDlciCn tables.
|
appnLcnIndex |
.1.3.6.1.4.1.562.2.4.1.110.4.1.1.10 |
This variable represents the index for the appnLcn tables.
|
appnLcnRowStatus |
.1.3.6.1.4.1.562.2.4.1.110.4.1.1.1 |
This variable is used as the basis for SNMP naming of
appnLcn components.
These components can be added and deleted.
|
appnLcnComponentName |
.1.3.6.1.4.1.562.2.4.1.110.4.1.1.2 |
This variable provides the component's string name for
use with the ASCII Console Interface
|
appnLcnStorageType |
.1.3.6.1.4.1.562.2.4.1.110.4.1.1.4 |
This variable represents the storage type value for the
appnLcn tables.
|
appnLcnAdminState |
.1.3.6.1.4.1.562.2.4.1.110.4.10.1.1 |
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.
|
appnLcnOperationalState |
.1.3.6.1.4.1.562.2.4.1.110.4.10.1.2 |
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.
|
appnLcnUsageState |
.1.3.6.1.4.1.562.2.4.1.110.4.10.1.3 |
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.
|
appnLcnDcIndex |
.1.3.6.1.4.1.562.2.4.1.110.4.2.1.1.10 |
This variable represents the index for the appnLcnDc tables.
|
appnLcnDcRowStatus |
.1.3.6.1.4.1.562.2.4.1.110.4.2.1.1.1 |
This variable is used as the basis for SNMP naming of
appnLcnDc components.
These components cannot be added nor deleted.
|
appnLcnDcComponentName |
.1.3.6.1.4.1.562.2.4.1.110.4.2.1.1.2 |
This variable provides the component's string name for
use with the ASCII Console Interface
|
appnLcnDcStorageType |
.1.3.6.1.4.1.562.2.4.1.110.4.2.1.1.4 |
This variable represents the storage type value for the
appnLcnDc tables.
|
appnLcnDcRemoteNpi |
.1.3.6.1.4.1.562.2.4.1.110.4.2.10.1.3 |
RemoteNumbering Plan Indicator (Npi) indicates the numbering
plan used in the remoteDna.
|
appnLcnDcRemoteDna |
.1.3.6.1.4.1.562.2.4.1.110.4.2.10.1.4 |
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.
|
appnLcnDcTransferPriority |
.1.3.6.1.4.1.562.2.4.1.110.4.2.10.1.9 |
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.
|
appnLcnDcDiscardPriority |
.1.3.6.1.4.1.562.2.4.1.110.4.2.10.1.10 |
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.
|
appnLcnVcIndex |
.1.3.6.1.4.1.562.2.4.1.110.4.3.1.1.10 |
This variable represents the index for the appnLcnVc tables.
|
appnLcnVcRowStatus |
.1.3.6.1.4.1.562.2.4.1.110.4.3.1.1.1 |
This variable is used as the basis for SNMP naming of
appnLcnVc components.
These components cannot be added nor deleted.
|
appnLcnVcComponentName |
.1.3.6.1.4.1.562.2.4.1.110.4.3.1.1.2 |
This variable provides the component's string name for
use with the ASCII Console Interface
|
appnLcnVcStorageType |
.1.3.6.1.4.1.562.2.4.1.110.4.3.1.1.4 |
This variable represents the storage type value for the
appnLcnVc tables.
|
appnLcnVcType |
.1.3.6.1.4.1.562.2.4.1.110.4.3.10.1.1 |
This attribute displays the type of call, pvc or svc. type is provided
at provisioning time.
|
appnLcnVcState |
.1.3.6.1.4.1.562.2.4.1.110.4.3.10.1.2 |
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.
|
appnLcnVcPreviousState |
.1.3.6.1.4.1.562.2.4.1.110.4.3.10.1.3 |
This attribute displays the previous state of call control. This is a
valuable field to determine how the processing is progressing.
|
appnLcnVcDiagnosticCode |
.1.3.6.1.4.1.562.2.4.1.110.4.3.10.1.4 |
This attribute displays the internal substate of call control. It is used
to further refine state of call processing.
|
appnLcnVcPreviousDiagnosticCode |
.1.3.6.1.4.1.562.2.4.1.110.4.3.10.1.5 |
This attribute displays the internal substate of call control. It is used
to further refine state of call processing.
|
appnLcnVcCalledNpi |
.1.3.6.1.4.1.562.2.4.1.110.4.3.10.1.6 |
This attribute displays the Numbering Plan Indicator (NPI) of the
called end.
|
appnLcnVcCalledDna |
.1.3.6.1.4.1.562.2.4.1.110.4.3.10.1.7 |
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.
|
appnLcnVcCalledLcn |
.1.3.6.1.4.1.562.2.4.1.110.4.3.10.1.8 |
This attribute displays the Logical Channel Number of the called
end. It is valid only after both ends of Vc exchanged relevant
information.
|
appnLcnVcCallingNpi |
.1.3.6.1.4.1.562.2.4.1.110.4.3.10.1.9 |
This attribute displays the Numbering Plan Indicator (NPI) of the
calling end.
|
appnLcnVcCallingDna |
.1.3.6.1.4.1.562.2.4.1.110.4.3.10.1.10 |
This attribute displays the Data Network Address (Dna) of the
calling end.
|
appnLcnVcCallingLcn |
.1.3.6.1.4.1.562.2.4.1.110.4.3.10.1.11 |
This attribute displays the Logical Channel Number of the calling
end.
|
appnLcnVcAccountingEnabled |
.1.3.6.1.4.1.562.2.4.1.110.4.3.10.1.12 |
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.
|
appnLcnVcFastSelectCall |
.1.3.6.1.4.1.562.2.4.1.110.4.3.10.1.13 |
This attribute displays that this is a fast select call.
|
appnLcnVcLocalRxPktSize |
.1.3.6.1.4.1.562.2.4.1.110.4.3.10.1.14 |
This attribute displays the locally negotiated size of send packets.
|
appnLcnVcLocalTxPktSize |
.1.3.6.1.4.1.562.2.4.1.110.4.3.10.1.15 |
This attribute displays the locally negotiated size of send packets.
|
appnLcnVcLocalTxWindowSize |
.1.3.6.1.4.1.562.2.4.1.110.4.3.10.1.16 |
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.
|
appnLcnVcLocalRxWindowSize |
.1.3.6.1.4.1.562.2.4.1.110.4.3.10.1.17 |
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.
|
appnLcnVcPathReliability |
.1.3.6.1.4.1.562.2.4.1.110.4.3.10.1.19 |
This attribute displays the path reliability.
|
appnLcnVcAccountingEnd |
.1.3.6.1.4.1.562.2.4.1.110.4.3.10.1.20 |
This attribute indicates if this end should generate an accounting
record. Normally, callingEnd is the end to generate an accounting
record.
|
appnLcnVcPriority |
.1.3.6.1.4.1.562.2.4.1.110.4.3.10.1.21 |
This attribute displays whether the call is a normal or a high
priority call.
|
appnLcnVcSegmentSize |
.1.3.6.1.4.1.562.2.4.1.110.4.3.10.1.22 |
This attribute displays the segment size (in bytes) used on the call.
It is used to calculate the number of segments transmitted and
received.
|
appnLcnVcSubnetTxPktSize |
.1.3.6.1.4.1.562.2.4.1.110.4.3.10.1.23 |
This attribute displays the locally negotiated size of the data packets
on this Vc.
|
appnLcnVcSubnetTxWindowSize |
.1.3.6.1.4.1.562.2.4.1.110.4.3.10.1.24 |
This attribute displays the current send window size of Vc.
|
appnLcnVcSubnetRxPktSize |
.1.3.6.1.4.1.562.2.4.1.110.4.3.10.1.25 |
This attribute displays the locally negotiated size of receive packets.
|
appnLcnVcSubnetRxWindowSize |
.1.3.6.1.4.1.562.2.4.1.110.4.3.10.1.26 |
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.
|
appnLcnVcMaxSubnetPktSize |
.1.3.6.1.4.1.562.2.4.1.110.4.3.10.1.27 |
This attribute displays the maximum packet size allowed on Vc.
|
appnLcnVcTransferPriorityToNetwork |
.1.3.6.1.4.1.562.2.4.1.110.4.3.10.1.28 |
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.
|
appnLcnVcTransferPriorityFromNetwork |
.1.3.6.1.4.1.562.2.4.1.110.4.3.10.1.29 |
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.
|
appnLcnVcCallReferenceNumber |
.1.3.6.1.4.1.562.2.4.1.110.4.3.11.1.1 |
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.
|
appnLcnVcElapsedTimeTillNow |
.1.3.6.1.4.1.562.2.4.1.110.4.3.11.1.2 |
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.
|
appnLcnVcSegmentsRx |
.1.3.6.1.4.1.562.2.4.1.110.4.3.11.1.3 |
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.
|
appnLcnVcSegmentsSent |
.1.3.6.1.4.1.562.2.4.1.110.4.3.11.1.4 |
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.
|
appnLcnVcStartTime |
.1.3.6.1.4.1.562.2.4.1.110.4.3.11.1.5 |
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.
|
appnLcnVcAckStackingTimeouts |
.1.3.6.1.4.1.562.2.4.1.110.4.3.12.1.1 |
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.
|
appnLcnVcOutOfRangeFrmFromSubnet |
.1.3.6.1.4.1.562.2.4.1.110.4.3.12.1.2 |
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.
|
appnLcnVcDuplicatesFromSubnet |
.1.3.6.1.4.1.562.2.4.1.110.4.3.12.1.3 |
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.
|
appnLcnVcFrmRetryTimeouts |
.1.3.6.1.4.1.562.2.4.1.110.4.3.12.1.4 |
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).
|
appnLcnVcPeakRetryQueueSize |
.1.3.6.1.4.1.562.2.4.1.110.4.3.12.1.5 |
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.
|
appnLcnVcPeakOoSeqQueueSize |
.1.3.6.1.4.1.562.2.4.1.110.4.3.12.1.6 |
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.
|
appnLcnVcPeakOoSeqFrmForwarded |
.1.3.6.1.4.1.562.2.4.1.110.4.3.12.1.7 |
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.
|
appnLcnVcPeakStackedAcksRx |
.1.3.6.1.4.1.562.2.4.1.110.4.3.12.1.8 |
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.
|
appnLcnVcSubnetRecoveries |
.1.3.6.1.4.1.562.2.4.1.110.4.3.12.1.9 |
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.
|
appnLcnVcWindowClosuresToSubnet |
.1.3.6.1.4.1.562.2.4.1.110.4.3.12.1.10 |
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.
|
appnLcnVcWindowClosuresFromSubnet |
.1.3.6.1.4.1.562.2.4.1.110.4.3.12.1.11 |
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.
|
appnLcnVcWrTriggers |
.1.3.6.1.4.1.562.2.4.1.110.4.3.12.1.12 |
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.
|
appnPortIndex |
.1.3.6.1.4.1.562.2.4.1.110.5.1.1.10 |
This variable represents the index for the appnPort tables.
|
appnPortRowStatus |
.1.3.6.1.4.1.562.2.4.1.110.5.1.1.1 |
This variable is used as the basis for SNMP naming of
appnPort components.
These components cannot be added nor deleted.
|
appnPortComponentName |
.1.3.6.1.4.1.562.2.4.1.110.5.1.1.2 |
This variable provides the component's string name for
use with the ASCII Console Interface
|
appnPortStorageType |
.1.3.6.1.4.1.562.2.4.1.110.5.1.1.4 |
This variable represents the storage type value for the
appnPort tables.
|
appnPortType |
.1.3.6.1.4.1.562.2.4.1.110.5.10.1.1 |
This attribute specifies the type of line used by the port. The
possible values are:
nonSwitched -
switched -
sharedAccessFacilities -
|
appnPortMaxRxBtuSize |
.1.3.6.1.4.1.562.2.4.1.110.5.10.1.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.
|
appnPortMaxTxBtuSize |
.1.3.6.1.4.1.562.2.4.1.110.5.10.1.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.
|
appnPortTotLinkActLim |
.1.3.6.1.4.1.562.2.4.1.110.5.10.1.4 |
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.
|
appnPortInbLinkActLim |
.1.3.6.1.4.1.562.2.4.1.110.5.10.1.5 |
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.
|
appnPortOutLinkActLim |
.1.3.6.1.4.1.562.2.4.1.110.5.10.1.6 |
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.
|
appnPortLsRole |
.1.3.6.1.4.1.562.2.4.1.110.5.10.1.7 |
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.
|
appnPortActXidExchLim |
.1.3.6.1.4.1.562.2.4.1.110.5.10.1.8 |
This is the exchange limit for activation XIDs.
|
appnPortNonactXidExchLim |
.1.3.6.1.4.1.562.2.4.1.110.5.10.1.9 |
This is the exchange limit for non-activation XIDs.
|
appnPortLsXmitRxCap |
.1.3.6.1.4.1.562.2.4.1.110.5.10.1.10 |
This is Link Station transmit/receive capability. This is either tws
(two-way simultaneous (full-duplex)) or twa (two-way alternate
(half-duplex)).
|
appnPortMaxIfrmRxWindow |
.1.3.6.1.4.1.562.2.4.1.110.5.10.1.11 |
This is the maximum number of I-frames that can be received by
the local link stations before an acknowledgment is sent.
|
appnPortTargetPacingCount |
.1.3.6.1.4.1.562.2.4.1.110.5.10.1.12 |
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.
|
appnPortState |
.1.3.6.1.4.1.562.2.4.1.110.5.11.1.1 |
The attribute represents the current operational state of the port. The
value can be any of the following:
inactive -
pendingActive -
active -
pendingInactive -
|
appnPortDlcType |
.1.3.6.1.4.1.562.2.4.1.110.5.11.1.2 |
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.
|
appnPortSimRim |
.1.3.6.1.4.1.562.2.4.1.110.5.11.1.3 |
This attribute indicates whether Set Initialization Mode (SIM) and
Receive Initialization Mode (RIM) are supported.
|
appnPortDefinedLsGoodXids |
.1.3.6.1.4.1.562.2.4.1.110.5.11.1.4 |
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.
|
appnPortDefinedLsBadXids |
.1.3.6.1.4.1.562.2.4.1.110.5.11.1.5 |
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.
|
appnPortDynLsGoodXids |
.1.3.6.1.4.1.562.2.4.1.110.5.11.1.6 |
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.
|
appnPortDynLsBadXids |
.1.3.6.1.4.1.562.2.4.1.110.5.11.1.7 |
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.
|
appnPortEffectiveCap |
.1.3.6.1.4.1.562.2.4.1.110.5.12.1.1 |
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.
|
appnPortConnectCost |
.1.3.6.1.4.1.562.2.4.1.110.5.12.1.2 |
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.
|
appnPortByteCost |
.1.3.6.1.4.1.562.2.4.1.110.5.12.1.3 |
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.
|
appnPortSecurity |
.1.3.6.1.4.1.562.2.4.1.110.5.12.1.4 |
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.
|
appnPortPropagationDelay |
.1.3.6.1.4.1.562.2.4.1.110.5.12.1.5 |
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
|
appnPortUserDefinedParm1 |
.1.3.6.1.4.1.562.2.4.1.110.5.12.1.7 |
This is the user defined routing parameter in range 0-255.
|
appnPortUserDefinedParm2 |
.1.3.6.1.4.1.562.2.4.1.110.5.12.1.8 |
This is the user defined routing parameter in range 0-255.
|
appnPortUserDefinedParm3 |
.1.3.6.1.4.1.562.2.4.1.110.5.12.1.9 |
This is the user defined routing parameter in range 0-255.
|
appnLsIndex |
.1.3.6.1.4.1.562.2.4.1.110.6.1.1.10 |
This variable represents the index for the appnLs tables.
|
appnLsRowStatus |
.1.3.6.1.4.1.562.2.4.1.110.6.1.1.1 |
This variable is used as the basis for SNMP naming of
appnLs components.
These components cannot be added nor deleted.
|
appnLsComponentName |
.1.3.6.1.4.1.562.2.4.1.110.6.1.1.2 |
This variable provides the component's string name for
use with the ASCII Console Interface
|
appnLsStorageType |
.1.3.6.1.4.1.562.2.4.1.110.6.1.1.4 |
This variable represents the storage type value for the
appnLs tables.
|
appnLsName |
.1.3.6.1.4.1.562.2.4.1.110.6.10.1.1 |
This string identifies which physical interface the link station is
associated with.
|
appnLsSap |
.1.3.6.1.4.1.562.2.4.1.110.6.10.1.2 |
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.
|
appnLsPortName |
.1.3.6.1.4.1.562.2.4.1.110.6.11.1.1 |
This attribute contains the name of the port associated with this link
station.
|
appnLsFeatures |
.1.3.6.1.4.1.562.2.4.1.110.6.11.1.4 |
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)
|
appnLsMaxTxBtuSize |
.1.3.6.1.4.1.562.2.4.1.110.6.11.1.6 |
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.
|
appnLsDlcType |
.1.3.6.1.4.1.562.2.4.1.110.6.12.1.1 |
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.
|
appnLsLinkStationState |
.1.3.6.1.4.1.562.2.4.1.110.6.12.1.2 |
This the current state of the link station. The possible values are:
inactive -
active -
pendingActive -
pendingInactive -
|
appnLsLinkStationSubState |
.1.3.6.1.4.1.562.2.4.1.110.6.12.1.3 |
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
|
appnLsActSessCount |
.1.3.6.1.4.1.562.2.4.1.110.6.12.1.4 |
This is the total number of active sessions (both endpoint and
intermediate) using this link.
|
appnLsActualCpName |
.1.3.6.1.4.1.562.2.4.1.110.6.12.1.5 |
This is the actual network qualified adjacent control point (CP)
name as determined from the XID 3 exchange.
|
appnLsActualCpType |
.1.3.6.1.4.1.562.2.4.1.110.6.12.1.6 |
This is the actual type of adjacent node type as determined during
contact negotiation. The possible types are:
endNode
lowEntryNode
networkNode
toBeDetermine
|
appnLsDlcName |
.1.3.6.1.4.1.562.2.4.1.110.6.12.1.7 |
This is the name of the port group associated with the port through
which this link station is attached.
|
appnLsDynamicOrDefined |
.1.3.6.1.4.1.562.2.4.1.110.6.12.1.8 |
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.
|
appnLsMigration |
.1.3.6.1.4.1.562.2.4.1.110.6.12.1.9 |
This attribute specifies whether the adjacent node is a
migration level node, such as a low entry networking or LEN
node.
|
appnLsTgNum |
.1.3.6.1.4.1.562.2.4.1.110.6.12.1.10 |
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.
|
appnLsHprSupport |
.1.3.6.1.4.1.562.2.4.1.110.6.12.1.11 |
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.
|
appnLsAnrLabel |
.1.3.6.1.4.1.562.2.4.1.110.6.12.1.12 |
This is the HPR ANR label associated with this link station.
|
appnLsEffectiveCap |
.1.3.6.1.4.1.562.2.4.1.110.6.13.1.1 |
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.
|
appnLsConnectCost |
.1.3.6.1.4.1.562.2.4.1.110.6.13.1.2 |
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.
|
appnLsByteCost |
.1.3.6.1.4.1.562.2.4.1.110.6.13.1.3 |
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.
|
appnLsSecurity |
.1.3.6.1.4.1.562.2.4.1.110.6.13.1.4 |
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.
|
appnLsPropagationDelay |
.1.3.6.1.4.1.562.2.4.1.110.6.13.1.5 |
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
|
appnLsUserDefinedParm1 |
.1.3.6.1.4.1.562.2.4.1.110.6.13.1.7 |
This is the user defined routing parameter in range 0-255.
|
appnLsUserDefinedParm2 |
.1.3.6.1.4.1.562.2.4.1.110.6.13.1.8 |
This is the user defined routing parameter in range 0-255.
|
appnLsUserDefinedParm3 |
.1.3.6.1.4.1.562.2.4.1.110.6.13.1.9 |
This is the user defined routing parameter in range 0-255.
|
appnLsInXidBytes |
.1.3.6.1.4.1.562.2.4.1.110.6.14.1.1 |
This attribute counts the total number of XID bytes received on this
link station.
|
appnLsInMsgBytes |
.1.3.6.1.4.1.562.2.4.1.110.6.14.1.2 |
This attribute counts the total number of message (I-frame) bytes
received on this link station.
|
appnLsInXidFrames |
.1.3.6.1.4.1.562.2.4.1.110.6.14.1.3 |
This attribute counts the total number of XID frames received on
this link station.
|
appnLsInMsgFrames |
.1.3.6.1.4.1.562.2.4.1.110.6.14.1.4 |
This attribute counts the total number of message (I-frame) frames
received on this link station.
|
appnLsOutXidBytes |
.1.3.6.1.4.1.562.2.4.1.110.6.14.1.5 |
This attribute counts the total number of XID bytes sent on this link
station.
|
appnLsOutMsgBytes |
.1.3.6.1.4.1.562.2.4.1.110.6.14.1.6 |
This attribute counts the total number of message (I-frame) bytes
sent on this link station.
|
appnLsOutXidFrames |
.1.3.6.1.4.1.562.2.4.1.110.6.14.1.7 |
This attribute counts the total number of XID frames sent on this
link station.
|
appnLsOutMsgFrames |
.1.3.6.1.4.1.562.2.4.1.110.6.14.1.8 |
This attribute counts the total number of message (I-frame) frames
sent on this link station.
|
appnLsInInvalidSnaFrames |
.1.3.6.1.4.1.562.2.4.1.110.6.14.1.9 |
This attribute counts the total number of invalid SNA frames
received on this link station.
|
appnLsInSessionControlFrames |
.1.3.6.1.4.1.562.2.4.1.110.6.14.1.10 |
This attribute counts the total number of session control frames
received on this link station.
|
appnLsOutSessionControlFrames |
.1.3.6.1.4.1.562.2.4.1.110.6.14.1.11 |
This attribute counts the total number of session control frames sent
on this link station.
|
appnLsEchoResponse |
.1.3.6.1.4.1.562.2.4.1.110.6.14.1.12 |
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.
|
appnLsCurrentDelay |
.1.3.6.1.4.1.562.2.4.1.110.6.14.1.13 |
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.
|
appnLsMaxDelay |
.1.3.6.1.4.1.562.2.4.1.110.6.14.1.14 |
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.
|
appnLsMinDelay |
.1.3.6.1.4.1.562.2.4.1.110.6.14.1.15 |
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.
|
appnLsGoodXids |
.1.3.6.1.4.1.562.2.4.1.110.6.14.1.17 |
This attribute contains the total number of successful XIDs that
have been received on this link station since it was started.
|
appnLsBadXids |
.1.3.6.1.4.1.562.2.4.1.110.6.14.1.18 |
This attribute contains the total number of unsuccessful XIDs that
have been received on this link station since it was started.
|
appnDirEntIndex |
.1.3.6.1.4.1.562.2.4.1.110.7.1.1.10 |
This variable represents the index for the appnDirEnt tables.
|
appnDirEntRowStatus |
.1.3.6.1.4.1.562.2.4.1.110.7.1.1.1 |
This variable is used as the basis for SNMP naming of
appnDirEnt components.
These components cannot be added nor deleted.
|
appnDirEntComponentName |
.1.3.6.1.4.1.562.2.4.1.110.7.1.1.2 |
This variable provides the component's string name for
use with the ASCII Console Interface
|
appnDirEntStorageType |
.1.3.6.1.4.1.562.2.4.1.110.7.1.1.4 |
This variable represents the storage type value for the
appnDirEnt tables.
|
appnDirEntServerName |
.1.3.6.1.4.1.562.2.4.1.110.7.10.1.1 |
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.
|
appnDirEntLuOwnerName |
.1.3.6.1.4.1.562.2.4.1.110.7.10.1.2 |
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.
|
appnDirEntLocation |
.1.3.6.1.4.1.562.2.4.1.110.7.10.1.3 |
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.
|
appnDirEntEntryType |
.1.3.6.1.4.1.562.2.4.1.110.7.10.1.4 |
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.
|
appnDirEntWildCard |
.1.3.6.1.4.1.562.2.4.1.110.7.10.1.5 |
It indicates the type of wildcard used for the resources used for
LEN node.
|
appnAdjNnIndex |
.1.3.6.1.4.1.562.2.4.1.110.8.1.1.10 |
This variable represents the index for the appnAdjNn tables.
|
appnAdjNnRowStatus |
.1.3.6.1.4.1.562.2.4.1.110.8.1.1.1 |
This variable is used as the basis for SNMP naming of
appnAdjNn components.
These components cannot be added nor deleted.
|
appnAdjNnComponentName |
.1.3.6.1.4.1.562.2.4.1.110.8.1.1.2 |
This variable provides the component's string name for
use with the ASCII Console Interface
|
appnAdjNnStorageType |
.1.3.6.1.4.1.562.2.4.1.110.8.1.1.4 |
This variable represents the storage type value for the
appnAdjNn tables.
|
appnAdjNnCpCpSessStatus |
.1.3.6.1.4.1.562.2.4.1.110.8.10.1.1 |
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.
|
appnAdjNnOutOfSeqTdus |
.1.3.6.1.4.1.562.2.4.1.110.8.10.1.2 |
Number of out of sequence topology database updates (TDU)
received from this node.
|
appnAdjNnLastFrsnSent |
.1.3.6.1.4.1.562.2.4.1.110.8.10.1.3 |
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.
|
appnAdjNnLastFrsnReceived |
.1.3.6.1.4.1.562.2.4.1.110.8.10.1.4 |
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.
|
appnNnIndex |
.1.3.6.1.4.1.562.2.4.1.110.9.1.1.10 |
This variable represents the index for the appnNn tables.
|
appnNnRowStatus |
.1.3.6.1.4.1.562.2.4.1.110.9.1.1.1 |
This variable is used as the basis for SNMP naming of
appnNn components.
These components cannot be added nor deleted.
|
appnNnComponentName |
.1.3.6.1.4.1.562.2.4.1.110.9.1.1.2 |
This variable provides the component's string name for
use with the ASCII Console Interface
|
appnNnStorageType |
.1.3.6.1.4.1.562.2.4.1.110.9.1.1.4 |
This variable represents the storage type value for the
appnNn tables.
|
appnNnDaysLeft |
.1.3.6.1.4.1.562.2.4.1.110.9.10.1.2 |
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.
|
appnNnNodeType |
.1.3.6.1.4.1.562.2.4.1.110.9.10.1.3 |
Type of the APPN node. Possible values are networkNode (nn) and
virtualRoutingNode (vrn).
|
appnNnResourceSequenceNumber |
.1.3.6.1.4.1.562.2.4.1.110.9.10.1.4 |
Resource sequence number. This is assigned by the network node
that owns this resource.
|
appnNnRouteAdditionResistance |
.1.3.6.1.4.1.562.2.4.1.110.9.10.1.5 |
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.
|
appnNnStatus |
.1.3.6.1.4.1.562.2.4.1.110.9.10.1.6 |
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)
|
appnNnFunctionSupported |
.1.3.6.1.4.1.562.2.4.1.110.9.10.1.7 |
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)
|
appnLocTgDestFqcpNameIndex |
.1.3.6.1.4.1.562.2.4.1.110.10.1.1.10 |
This variable represents an index for the appnLocTg tables.
|
appnLocTgTransmissionGroupIndex |
.1.3.6.1.4.1.562.2.4.1.110.10.1.1.11 |
This variable represents an index for the appnLocTg tables.
|
appnLocTgRowStatus |
.1.3.6.1.4.1.562.2.4.1.110.10.1.1.1 |
This variable is used as the basis for SNMP naming of
appnLocTg components.
These components cannot be added nor deleted.
|
appnLocTgComponentName |
.1.3.6.1.4.1.562.2.4.1.110.10.1.1.2 |
This variable provides the component's string name for
use with the ASCII Console Interface
|
appnLocTgStorageType |
.1.3.6.1.4.1.562.2.4.1.110.10.1.1.4 |
This variable represents the storage type value for the
appnLocTg tables.
|
appnLocTgStatus |
.1.3.6.1.4.1.562.2.4.1.110.10.10.1.1 |
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)
|
appnLocTgResourceSequenceNumber |
.1.3.6.1.4.1.562.2.4.1.110.10.10.1.2 |
This attribute contains the resource sequence number.
|
appnLocTgDlcData |
.1.3.6.1.4.1.562.2.4.1.110.10.11.1.1 |
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.
|
appnLocTgEffectiveCap |
.1.3.6.1.4.1.562.2.4.1.110.10.12.1.1 |
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.
|
appnLocTgConnectCost |
.1.3.6.1.4.1.562.2.4.1.110.10.12.1.2 |
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.
|
appnLocTgByteCost |
.1.3.6.1.4.1.562.2.4.1.110.10.12.1.3 |
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.
|
appnLocTgSecurity |
.1.3.6.1.4.1.562.2.4.1.110.10.12.1.4 |
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.
|
appnLocTgPropagationDelay |
.1.3.6.1.4.1.562.2.4.1.110.10.12.1.5 |
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
|
appnLocTgUserDefinedParm1 |
.1.3.6.1.4.1.562.2.4.1.110.10.12.1.7 |
This is the user defined routing parameter in range 0-255.
|
appnLocTgUserDefinedParm2 |
.1.3.6.1.4.1.562.2.4.1.110.10.12.1.8 |
This is the user defined routing parameter in range 0-255.
|
appnLocTgUserDefinedParm3 |
.1.3.6.1.4.1.562.2.4.1.110.10.12.1.9 |
This is the user defined routing parameter in range 0-255.
|
appnIsrSessFqcpNameIndex |
.1.3.6.1.4.1.562.2.4.1.110.11.1.1.10 |
This variable represents an index for the appnIsrSess tables.
|
appnIsrSessProcedureCorrelationIdIndex |
.1.3.6.1.4.1.562.2.4.1.110.11.1.1.11 |
This variable represents an index for the appnIsrSess tables.
|
appnIsrSessRowStatus |
.1.3.6.1.4.1.562.2.4.1.110.11.1.1.1 |
This variable is used as the basis for SNMP naming of
appnIsrSess components.
These components cannot be added nor deleted.
|
appnIsrSessComponentName |
.1.3.6.1.4.1.562.2.4.1.110.11.1.1.2 |
This variable provides the component's string name for
use with the ASCII Console Interface
|
appnIsrSessStorageType |
.1.3.6.1.4.1.562.2.4.1.110.11.1.1.4 |
This variable represents the storage type value for the
appnIsrSess tables.
|
appnIsrSessTransmissionPriority |
.1.3.6.1.4.1.562.2.4.1.110.11.10.1.1 |
This attribute contains the transmission priority. This is one of low,
medium, high or network.
|
appnIsrSessCosName |
.1.3.6.1.4.1.562.2.4.1.110.11.10.1.2 |
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.
|
appnIsrSessLimitedResource |
.1.3.6.1.4.1.562.2.4.1.110.11.10.1.3 |
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.
|
appnIsrSessPriStatsIndex |
.1.3.6.1.4.1.562.2.4.1.110.11.100.1.1.10 |
This variable represents the index for the appnIsrSessPriStats tables.
|
appnIsrSessPriStatsRowStatus |
.1.3.6.1.4.1.562.2.4.1.110.11.100.1.1.1 |
This variable is used as the basis for SNMP naming of
appnIsrSessPriStats components.
These components cannot be added nor deleted.
|
appnIsrSessPriStatsComponentName |
.1.3.6.1.4.1.562.2.4.1.110.11.100.1.1.2 |
This variable provides the component's string name for
use with the ASCII Console Interface
|
appnIsrSessPriStatsStorageType |
.1.3.6.1.4.1.562.2.4.1.110.11.100.1.1.4 |
This variable represents the storage type value for the
appnIsrSessPriStats tables.
|
appnIsrSessPriStatsRxRuSize |
.1.3.6.1.4.1.562.2.4.1.110.11.100.10.1.1 |
This is the maximum request unit (RU) size that can be used on the
session.
|
appnIsrSessPriStatsMaxTxBtuSize |
.1.3.6.1.4.1.562.2.4.1.110.11.100.10.1.2 |
This is the maximum BTU size (length of the information field in a
frame) that can be sent on the session.
|
appnIsrSessPriStatsMaxRxBtuSize |
.1.3.6.1.4.1.562.2.4.1.110.11.100.10.1.3 |
This is the maximum BTU size (length of the information field in a
frame) that can be received on the session.
|
appnIsrSessPriStatsMaxTxPacWin |
.1.3.6.1.4.1.562.2.4.1.110.11.100.10.1.4 |
This is the maximum size of the send pacing window on the
session.
|
appnIsrSessPriStatsCurTxPacWin |
.1.3.6.1.4.1.562.2.4.1.110.11.100.10.1.5 |
This is the current size of the send pacing window on the session.
|
appnIsrSessPriStatsMaxRxPacWin |
.1.3.6.1.4.1.562.2.4.1.110.11.100.10.1.6 |
This is the maximum size of the receive pacing window on the
session.
|
appnIsrSessPriStatsCurRxPacWin |
.1.3.6.1.4.1.562.2.4.1.110.11.100.10.1.7 |
This is the current size of the receive pacing window on the
session.
|
appnIsrSessPriStatsTxDataframes |
.1.3.6.1.4.1.562.2.4.1.110.11.100.10.1.8 |
This attribute counts the number of normal flow data frames sent
on the session, the counter wraps to zero.
|
appnIsrSessPriStatsTxFmdFrames |
.1.3.6.1.4.1.562.2.4.1.110.11.100.10.1.9 |
This attribute counts the number of FMD data frames sent on the
session, the counter wraps to zero.
|
appnIsrSessPriStatsTxDataBytes |
.1.3.6.1.4.1.562.2.4.1.110.11.100.10.1.10 |
This is the number of normal flow data bytes sent on the session,
the counter wraps to zero.
|
appnIsrSessPriStatsRxDataFrames |
.1.3.6.1.4.1.562.2.4.1.110.11.100.10.1.11 |
This is the number of normal flow data frames received on the
session, the counter wraps to zero.
|
appnIsrSessPriStatsRxFmdFrames |
.1.3.6.1.4.1.562.2.4.1.110.11.100.10.1.12 |
This attribute counts the number of FMD data frames received on
the session, the counter wraps to zero.
|
appnIsrSessPriStatsRxDataBytes |
.1.3.6.1.4.1.562.2.4.1.110.11.100.10.1.13 |
This is the number of normal flow data bytes received on the
session, the counter wraps to zero.
|
appnIsrSessPriStatsSidh |
.1.3.6.1.4.1.562.2.4.1.110.11.100.10.1.14 |
This attribute contains the session identifier high byte on the
session.
|
appnIsrSessPriStatsSidl |
.1.3.6.1.4.1.562.2.4.1.110.11.100.10.1.15 |
This attribute contains the session ID low byte on the SSCP session.
|
appnIsrSessPriStatsOdai |
.1.3.6.1.4.1.562.2.4.1.110.11.100.10.1.16 |
This is the origin destination assignor indicator (ODAI) on the
session.
|
appnIsrSessPriStatsLsName |
.1.3.6.1.4.1.562.2.4.1.110.11.100.10.1.17 |
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.
|
appnIsrSessSecStatsIndex |
.1.3.6.1.4.1.562.2.4.1.110.11.101.1.1.10 |
This variable represents the index for the appnIsrSessSecStats tables.
|
appnIsrSessSecStatsRowStatus |
.1.3.6.1.4.1.562.2.4.1.110.11.101.1.1.1 |
This variable is used as the basis for SNMP naming of
appnIsrSessSecStats components.
These components cannot be added nor deleted.
|
appnIsrSessSecStatsComponentName |
.1.3.6.1.4.1.562.2.4.1.110.11.101.1.1.2 |
This variable provides the component's string name for
use with the ASCII Console Interface
|
appnIsrSessSecStatsStorageType |
.1.3.6.1.4.1.562.2.4.1.110.11.101.1.1.4 |
This variable represents the storage type value for the
appnIsrSessSecStats tables.
|
appnIsrSessSecStatsRxRuSize |
.1.3.6.1.4.1.562.2.4.1.110.11.101.10.1.1 |
This is the maximum request unit (RU) size that can be used on the
session.
|
appnIsrSessSecStatsMaxTxBtuSize |
.1.3.6.1.4.1.562.2.4.1.110.11.101.10.1.2 |
This is the maximum BTU size (length of the information field in a
frame) that can be sent on the session.
|
appnIsrSessSecStatsMaxRxBtuSize |
.1.3.6.1.4.1.562.2.4.1.110.11.101.10.1.3 |
This is the maximum BTU size (length of the information field in a
frame) that can be received on the session.
|
appnIsrSessSecStatsMaxTxPacWin |
.1.3.6.1.4.1.562.2.4.1.110.11.101.10.1.4 |
This is the maximum size of the send pacing window on the
session.
|
appnIsrSessSecStatsCurTxPacWin |
.1.3.6.1.4.1.562.2.4.1.110.11.101.10.1.5 |
This is the current size of the send pacing window on the session.
|
appnIsrSessSecStatsMaxRxPacWin |
.1.3.6.1.4.1.562.2.4.1.110.11.101.10.1.6 |
This is the maximum size of the receive pacing window on the
session.
|
appnIsrSessSecStatsCurRxPacWin |
.1.3.6.1.4.1.562.2.4.1.110.11.101.10.1.7 |
This is the current size of the receive pacing window on the
session.
|
appnIsrSessSecStatsTxDataframes |
.1.3.6.1.4.1.562.2.4.1.110.11.101.10.1.8 |
This attribute counts the number of normal flow data frames sent
on the session, the counter wraps to zero.
|
appnIsrSessSecStatsTxFmdFrames |
.1.3.6.1.4.1.562.2.4.1.110.11.101.10.1.9 |
This attribute counts the number of FMD data frames sent on the
session, the counter wraps to zero.
|
appnIsrSessSecStatsTxDataBytes |
.1.3.6.1.4.1.562.2.4.1.110.11.101.10.1.10 |
This is the number of normal flow data bytes sent on the session,
the counter wraps to zero.
|
appnIsrSessSecStatsRxDataFrames |
.1.3.6.1.4.1.562.2.4.1.110.11.101.10.1.11 |
This is the number of normal flow data frames received on the
session, the counter wraps to zero.
|
appnIsrSessSecStatsRxFmdFrames |
.1.3.6.1.4.1.562.2.4.1.110.11.101.10.1.12 |
This attribute counts the number of FMD data frames received on
the session, the counter wraps to zero.
|
appnIsrSessSecStatsRxDataBytes |
.1.3.6.1.4.1.562.2.4.1.110.11.101.10.1.13 |
This is the number of normal flow data bytes received on the
session, the counter wraps to zero.
|
appnIsrSessSecStatsSidh |
.1.3.6.1.4.1.562.2.4.1.110.11.101.10.1.14 |
This attribute contains the session identifier high byte on the
session.
|
appnIsrSessSecStatsSidl |
.1.3.6.1.4.1.562.2.4.1.110.11.101.10.1.15 |
This attribute contains the session ID low byte on the SSCP session.
|
appnIsrSessSecStatsOdai |
.1.3.6.1.4.1.562.2.4.1.110.11.101.10.1.16 |
This is the origin destination assignor indicator (ODAI) on the
session.
|
appnIsrSessSecStatsLsName |
.1.3.6.1.4.1.562.2.4.1.110.11.101.10.1.17 |
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.
|
appnNnTgOwnerFqcpNameIndex |
.1.3.6.1.4.1.562.2.4.1.110.12.1.1.10 |
This variable represents an index for the appnNnTg tables.
|
appnNnTgDestFqcpNameIndex |
.1.3.6.1.4.1.562.2.4.1.110.12.1.1.11 |
This variable represents an index for the appnNnTg tables.
|
appnNnTgTransmissionGroupIndex |
.1.3.6.1.4.1.562.2.4.1.110.12.1.1.12 |
This variable represents an index for the appnNnTg tables.
|
appnNnTgRowStatus |
.1.3.6.1.4.1.562.2.4.1.110.12.1.1.1 |
This variable is used as the basis for SNMP naming of
appnNnTg components.
These components cannot be added nor deleted.
|
appnNnTgComponentName |
.1.3.6.1.4.1.562.2.4.1.110.12.1.1.2 |
This variable provides the component's string name for
use with the ASCII Console Interface
|
appnNnTgStorageType |
.1.3.6.1.4.1.562.2.4.1.110.12.1.1.4 |
This variable represents the storage type value for the
appnNnTg tables.
|
appnNnTgFlowReductionSequenceNumber |
.1.3.6.1.4.1.562.2.4.1.110.12.10.1.1 |
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
|
appnNnTgDaysLeft |
.1.3.6.1.4.1.562.2.4.1.110.12.10.1.2 |
Number of days left until entry purged.
|
appnNnTgResourceSequenceNumber |
.1.3.6.1.4.1.562.2.4.1.110.12.10.1.3 |
Resource sequence number.
|
appnNnTgStatus |
.1.3.6.1.4.1.562.2.4.1.110.12.10.1.4 |
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)
|
appnNnTgDlcData |
.1.3.6.1.4.1.562.2.4.1.110.12.11.1.1 |
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.
|
appnNnTgEffectiveCap |
.1.3.6.1.4.1.562.2.4.1.110.12.12.1.1 |
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.
|
appnNnTgConnectCost |
.1.3.6.1.4.1.562.2.4.1.110.12.12.1.2 |
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.
|
appnNnTgByteCost |
.1.3.6.1.4.1.562.2.4.1.110.12.12.1.3 |
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.
|
appnNnTgSecurity |
.1.3.6.1.4.1.562.2.4.1.110.12.12.1.4 |
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.
|
appnNnTgPropagationDelay |
.1.3.6.1.4.1.562.2.4.1.110.12.12.1.5 |
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
|
appnNnTgUserDefinedParm1 |
.1.3.6.1.4.1.562.2.4.1.110.12.12.1.7 |
This is the user defined routing parameter in range 0-255.
|
appnNnTgUserDefinedParm2 |
.1.3.6.1.4.1.562.2.4.1.110.12.12.1.8 |
This is the user defined routing parameter in range 0-255.
|
appnNnTgUserDefinedParm3 |
.1.3.6.1.4.1.562.2.4.1.110.12.12.1.9 |
This is the user defined routing parameter in range 0-255.
|
appnRtpIndex |
.1.3.6.1.4.1.562.2.4.1.110.13.1.1.10 |
This variable represents the index for the appnRtp tables.
|
appnRtpRowStatus |
.1.3.6.1.4.1.562.2.4.1.110.13.1.1.1 |
This variable is used as the basis for SNMP naming of
appnRtp components.
These components cannot be added nor deleted.
|
appnRtpComponentName |
.1.3.6.1.4.1.562.2.4.1.110.13.1.1.2 |
This variable provides the component's string name for
use with the ASCII Console Interface
|
appnRtpStorageType |
.1.3.6.1.4.1.562.2.4.1.110.13.1.1.4 |
This variable represents the storage type value for the
appnRtp tables.
|
appnRtpLocalLsName |
.1.3.6.1.4.1.562.2.4.1.110.13.10.1.1 |
This is the name of the local link station associated with this High
Performance Routing-Rapid Transport Protocol pipe
|
appnRtpRemoteCpName |
.1.3.6.1.4.1.562.2.4.1.110.13.10.1.2 |
This is the CP name of the node at the other end of the High
Performance Routing-Rapid Transport Protocol pipe
|
appnRtpCosName |
.1.3.6.1.4.1.562.2.4.1.110.13.10.1.3 |
This is the name of the Class of Service associated with this High
Performance Routing-Rapid Transport Protocol pipe
|
appnRtpActiveSessions |
.1.3.6.1.4.1.562.2.4.1.110.13.10.1.4 |
The number of active sessions using this High Performance
Routing-Rapid Transport Protocol pipe
|
appnRtpLocalTcid |
.1.3.6.1.4.1.562.2.4.1.110.13.10.1.5 |
The Transport Connection Identifier (TCID) assigned to this HPR
RTP pipe by the local node
|
appnRtpRemoteTcid |
.1.3.6.1.4.1.562.2.4.1.110.13.10.1.6 |
The Transport Connection Identifier (TCID) assigned to this HPR
RTP pipe by the remote node.
|
appnRtpIdleTimer |
.1.3.6.1.4.1.562.2.4.1.110.13.10.1.7 |
The idle timer of this High Performance Routing-Rapid Transport
Protocol pipe (in seconds)
|
appnRtpMaxBtuSize |
.1.3.6.1.4.1.562.2.4.1.110.13.10.1.8 |
The maximum BTU size (the length of the information field in a
frame) of the High Performance Routing-Rapid Transport Protocol
pipe.
|
appnRtpTxBytes |
.1.3.6.1.4.1.562.2.4.1.110.13.11.1.1 |
This attribute is the total number of bytes sent on this High
Performance Routing-Rapid Transport Protocol pipe. This counter
wraps to zero.
|
appnRtpRxBytes |
.1.3.6.1.4.1.562.2.4.1.110.13.11.1.2 |
This attribute is the total number of bytes received on this High
Performance Routing-Rapid Transport Protocol pipe. This counter
wraps to zero.
|
appnRtpBytesResent |
.1.3.6.1.4.1.562.2.4.1.110.13.11.1.3 |
This attribute counts the total number of bytes resent on this High
Performance Routing-Rapid Transport Protocol pipe. This counter
wraps to zero.
|
appnRtpBytesDiscarded |
.1.3.6.1.4.1.562.2.4.1.110.13.11.1.4 |
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.
|
appnRtpPktTx |
.1.3.6.1.4.1.562.2.4.1.110.13.11.1.5 |
This attribute counts the total number of packets sent on this High
Performance Routing-Rapid Transport Protocol pipe. This counter
wraps to zero.
|
appnRtpPktRx |
.1.3.6.1.4.1.562.2.4.1.110.13.11.1.6 |
This attribute counts the total number of packets received on this
High Performance Routing-Rapid Transport Protocol pipe. This
counter wraps to zero.
|
appnRtpPktResent |
.1.3.6.1.4.1.562.2.4.1.110.13.11.1.7 |
This attribute counts the total number of packets resent on this High
Performance Routing-Rapid Transport Protocol pipe. This counter
wraps to zero.
|
appnRtpPktDiscard |
.1.3.6.1.4.1.562.2.4.1.110.13.11.1.8 |
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.
|
appnRtpLostFrames |
.1.3.6.1.4.1.562.2.4.1.110.13.11.1.9 |
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.
|
appnRtpCurTxRate |
.1.3.6.1.4.1.562.2.4.1.110.13.11.1.10 |
This attribute gives the current send rate on this pipe.
|
appnRtpMaxTxRate |
.1.3.6.1.4.1.562.2.4.1.110.13.11.1.11 |
This attribute give the maximum send rate on this pipe.
|
appnRtpMinTxRate |
.1.3.6.1.4.1.562.2.4.1.110.13.11.1.12 |
This attribute gives the minimum send rate on this pipe.
|
appnRtpCurRxRate |
.1.3.6.1.4.1.562.2.4.1.110.13.11.1.13 |
This attribute gives the current receive rate on this pipe.
|
appnRtpMaxRxRate |
.1.3.6.1.4.1.562.2.4.1.110.13.11.1.14 |
This attribute gives the maximum receive rate on this pipe.
|
appnRtpMinRxRate |
.1.3.6.1.4.1.562.2.4.1.110.13.11.1.15 |
This attribute gives the minimum receive rate on this pipe.
|
appnRtpBurstSize |
.1.3.6.1.4.1.562.2.4.1.110.13.11.1.16 |
This attribute gives the current burst size on this pipe.
|
appnRtpUptime |
.1.3.6.1.4.1.562.2.4.1.110.13.11.1.17 |
This attribute gives the total uptime of this High Performance
Routing-Rapid Transport Protocol pipe.
|
appnRtpSmoothRoundTripTime |
.1.3.6.1.4.1.562.2.4.1.110.13.11.1.18 |
This attribute gives the smoothed round-trip time on this pipe.
|
appnRtpLastRoundTripTime |
.1.3.6.1.4.1.562.2.4.1.110.13.11.1.19 |
This attribute gives the last round-trip time on this pipe.
|
appnRtpShortReqTimer |
.1.3.6.1.4.1.562.2.4.1.110.13.11.1.20 |
This attribute gives the short request timer duration on this pipe.
|
appnRtpShortReqTimeouts |
.1.3.6.1.4.1.562.2.4.1.110.13.11.1.21 |
This attribute counts the number of short request timer timeouts on
this pipe.
|
appnRtpIdleTimeouts |
.1.3.6.1.4.1.562.2.4.1.110.13.11.1.22 |
This attribute count the number of idle timer timeouts on this pipe.
|
appnRtpRxInvalidSnaFrames |
.1.3.6.1.4.1.562.2.4.1.110.13.11.1.23 |
This attribute counts the number of invalid SNA frames received on
this pipe.
|
appnRtpInSessionControlFrames |
.1.3.6.1.4.1.562.2.4.1.110.13.11.1.24 |
This attribute counts the number of Session Control frames received
on this pipe.
|
appnRtpOutSessionControlFrames |
.1.3.6.1.4.1.562.2.4.1.110.13.11.1.25 |
This attribute counts the number of Session Control frames sent on
this pipe.
|
appnDluIndex |
.1.3.6.1.4.1.562.2.4.1.110.14.1.1.10 |
This variable represents the index for the appnDlu tables.
|
appnDluRowStatus |
.1.3.6.1.4.1.562.2.4.1.110.14.1.1.1 |
This variable is used as the basis for SNMP naming of
appnDlu components.
These components cannot be added nor deleted.
|
appnDluComponentName |
.1.3.6.1.4.1.562.2.4.1.110.14.1.1.2 |
This variable provides the component's string name for
use with the ASCII Console Interface
|
appnDluStorageType |
.1.3.6.1.4.1.562.2.4.1.110.14.1.1.4 |
This variable represents the storage type value for the
appnDlu tables.
|
appnDluSscpSessActive |
.1.3.6.1.4.1.562.2.4.1.110.14.10.1.1 |
This attribute tells whether the SSCP-LU session is active
|
appnDluPluSessActive |
.1.3.6.1.4.1.562.2.4.1.110.14.10.1.2 |
This attribute tells whether the dependent LU session is active.
|
appnDluDlusName |
.1.3.6.1.4.1.562.2.4.1.110.14.10.1.3 |
This attribute tells the name of the dependent LU server name that
this dependent LU is connected to.
|
appnDluPluName |
.1.3.6.1.4.1.562.2.4.1.110.14.10.1.4 |
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.
|
appnDluNauAddress |
.1.3.6.1.4.1.562.2.4.1.110.14.10.1.5 |
This attribute gives the NAU address of the dependent LU.
|
appnDluSscpIndex |
.1.3.6.1.4.1.562.2.4.1.110.14.100.1.1.10 |
This variable represents the index for the appnDluSscp tables.
|
appnDluSscpRowStatus |
.1.3.6.1.4.1.562.2.4.1.110.14.100.1.1.1 |
This variable is used as the basis for SNMP naming of
appnDluSscp components.
These components cannot be added nor deleted.
|
appnDluSscpComponentName |
.1.3.6.1.4.1.562.2.4.1.110.14.100.1.1.2 |
This variable provides the component's string name for
use with the ASCII Console Interface
|
appnDluSscpStorageType |
.1.3.6.1.4.1.562.2.4.1.110.14.100.1.1.4 |
This variable represents the storage type value for the
appnDluSscp tables.
|
appnDluSscpRxRuSize |
.1.3.6.1.4.1.562.2.4.1.110.14.100.10.1.1 |
This is the maximum request unit (RU) size that can be used on the
session.
|
appnDluSscpMaxTxBtuSize |
.1.3.6.1.4.1.562.2.4.1.110.14.100.10.1.2 |
This is the maximum BTU size (length of the information field in a
frame) that can be sent on the session.
|
appnDluSscpMaxRxBtuSize |
.1.3.6.1.4.1.562.2.4.1.110.14.100.10.1.3 |
This is the maximum BTU size (length of the information field in a
frame) that can be received on the session.
|
appnDluSscpMaxTxPacWin |
.1.3.6.1.4.1.562.2.4.1.110.14.100.10.1.4 |
This is the maximum size of the send pacing window on the
session.
|
appnDluSscpCurTxPacWin |
.1.3.6.1.4.1.562.2.4.1.110.14.100.10.1.5 |
This is the current size of the send pacing window on the session.
|
appnDluSscpMaxRxPacWin |
.1.3.6.1.4.1.562.2.4.1.110.14.100.10.1.6 |
This is the maximum size of the receive pacing window on the
session.
|
appnDluSscpCurRxPacWin |
.1.3.6.1.4.1.562.2.4.1.110.14.100.10.1.7 |
This is the current size of the receive pacing window on the
session.
|
appnDluSscpTxDataframes |
.1.3.6.1.4.1.562.2.4.1.110.14.100.10.1.8 |
This attribute counts the number of normal flow data frames sent
on the session, the counter wraps to zero.
|
appnDluSscpTxFmdFrames |
.1.3.6.1.4.1.562.2.4.1.110.14.100.10.1.9 |
This attribute counts the number of FMD data frames sent on the
session, the counter wraps to zero.
|
appnDluSscpTxDataBytes |
.1.3.6.1.4.1.562.2.4.1.110.14.100.10.1.10 |
This is the number of normal flow data bytes sent on the session,
the counter wraps to zero.
|
appnDluSscpRxDataFrames |
.1.3.6.1.4.1.562.2.4.1.110.14.100.10.1.11 |
This is the number of normal flow data frames received on the
session, the counter wraps to zero.
|
appnDluSscpRxFmdFrames |
.1.3.6.1.4.1.562.2.4.1.110.14.100.10.1.12 |
This attribute counts the number of FMD data frames received on
the session, the counter wraps to zero.
|
appnDluSscpRxDataBytes |
.1.3.6.1.4.1.562.2.4.1.110.14.100.10.1.13 |
This is the number of normal flow data bytes received on the
session, the counter wraps to zero.
|
appnDluSscpSidh |
.1.3.6.1.4.1.562.2.4.1.110.14.100.10.1.14 |
This attribute contains the session identifier high byte on the
session.
|
appnDluSscpSidl |
.1.3.6.1.4.1.562.2.4.1.110.14.100.10.1.15 |
This attribute contains the session ID low byte on the SSCP session.
|
appnDluSscpOdai |
.1.3.6.1.4.1.562.2.4.1.110.14.100.10.1.16 |
This is the origin destination assignor indicator (ODAI) on the
session.
|
appnDluSscpLsName |
.1.3.6.1.4.1.562.2.4.1.110.14.100.10.1.17 |
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.
|
appnDluUsStatIndex |
.1.3.6.1.4.1.562.2.4.1.110.14.101.1.1.10 |
This variable represents the index for the appnDluUsStat tables.
|
appnDluUsStatRowStatus |
.1.3.6.1.4.1.562.2.4.1.110.14.101.1.1.1 |
This variable is used as the basis for SNMP naming of
appnDluUsStat components.
These components cannot be added nor deleted.
|
appnDluUsStatComponentName |
.1.3.6.1.4.1.562.2.4.1.110.14.101.1.1.2 |
This variable provides the component's string name for
use with the ASCII Console Interface
|
appnDluUsStatStorageType |
.1.3.6.1.4.1.562.2.4.1.110.14.101.1.1.4 |
This variable represents the storage type value for the
appnDluUsStat tables.
|
appnDluUsStatRxRuSize |
.1.3.6.1.4.1.562.2.4.1.110.14.101.10.1.1 |
This is the maximum request unit (RU) size that can be used on the
session.
|
appnDluUsStatMaxTxBtuSize |
.1.3.6.1.4.1.562.2.4.1.110.14.101.10.1.2 |
This is the maximum BTU size (length of the information field in a
frame) that can be sent on the session.
|
appnDluUsStatMaxRxBtuSize |
.1.3.6.1.4.1.562.2.4.1.110.14.101.10.1.3 |
This is the maximum BTU size (length of the information field in a
frame) that can be received on the session.
|
appnDluUsStatMaxTxPacWin |
.1.3.6.1.4.1.562.2.4.1.110.14.101.10.1.4 |
This is the maximum size of the send pacing window on the
session.
|
appnDluUsStatCurTxPacWin |
.1.3.6.1.4.1.562.2.4.1.110.14.101.10.1.5 |
This is the current size of the send pacing window on the session.
|
appnDluUsStatMaxRxPacWin |
.1.3.6.1.4.1.562.2.4.1.110.14.101.10.1.6 |
This is the maximum size of the receive pacing window on the
session.
|
appnDluUsStatCurRxPacWin |
.1.3.6.1.4.1.562.2.4.1.110.14.101.10.1.7 |
This is the current size of the receive pacing window on the
session.
|
appnDluUsStatTxDataframes |
.1.3.6.1.4.1.562.2.4.1.110.14.101.10.1.8 |
This attribute counts the number of normal flow data frames sent
on the session, the counter wraps to zero.
|
appnDluUsStatTxFmdFrames |
.1.3.6.1.4.1.562.2.4.1.110.14.101.10.1.9 |
This attribute counts the number of FMD data frames sent on the
session, the counter wraps to zero.
|
appnDluUsStatTxDataBytes |
.1.3.6.1.4.1.562.2.4.1.110.14.101.10.1.10 |
This is the number of normal flow data bytes sent on the session,
the counter wraps to zero.
|
appnDluUsStatRxDataFrames |
.1.3.6.1.4.1.562.2.4.1.110.14.101.10.1.11 |
This is the number of normal flow data frames received on the
session, the counter wraps to zero.
|
appnDluUsStatRxFmdFrames |
.1.3.6.1.4.1.562.2.4.1.110.14.101.10.1.12 |
This attribute counts the number of FMD data frames received on
the session, the counter wraps to zero.
|
appnDluUsStatRxDataBytes |
.1.3.6.1.4.1.562.2.4.1.110.14.101.10.1.13 |
This is the number of normal flow data bytes received on the
session, the counter wraps to zero.
|
appnDluUsStatSidh |
.1.3.6.1.4.1.562.2.4.1.110.14.101.10.1.14 |
This attribute contains the session identifier high byte on the
session.
|
appnDluUsStatSidl |
.1.3.6.1.4.1.562.2.4.1.110.14.101.10.1.15 |
This attribute contains the session ID low byte on the SSCP session.
|
appnDluUsStatOdai |
.1.3.6.1.4.1.562.2.4.1.110.14.101.10.1.16 |
This is the origin destination assignor indicator (ODAI) on the
session.
|
appnDluUsStatLsName |
.1.3.6.1.4.1.562.2.4.1.110.14.101.10.1.17 |
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.
|
appnDluDsStatIndex |
.1.3.6.1.4.1.562.2.4.1.110.14.102.1.1.10 |
This variable represents the index for the appnDluDsStat tables.
|
appnDluDsStatRowStatus |
.1.3.6.1.4.1.562.2.4.1.110.14.102.1.1.1 |
This variable is used as the basis for SNMP naming of
appnDluDsStat components.
These components cannot be added nor deleted.
|
appnDluDsStatComponentName |
.1.3.6.1.4.1.562.2.4.1.110.14.102.1.1.2 |
This variable provides the component's string name for
use with the ASCII Console Interface
|
appnDluDsStatStorageType |
.1.3.6.1.4.1.562.2.4.1.110.14.102.1.1.4 |
This variable represents the storage type value for the
appnDluDsStat tables.
|
appnDluDsStatRxRuSize |
.1.3.6.1.4.1.562.2.4.1.110.14.102.10.1.1 |
This is the maximum request unit (RU) size that can be used on the
session.
|
appnDluDsStatMaxTxBtuSize |
.1.3.6.1.4.1.562.2.4.1.110.14.102.10.1.2 |
This is the maximum BTU size (length of the information field in a
frame) that can be sent on the session.
|
appnDluDsStatMaxRxBtuSize |
.1.3.6.1.4.1.562.2.4.1.110.14.102.10.1.3 |
This is the maximum BTU size (length of the information field in a
frame) that can be received on the session.
|
appnDluDsStatMaxTxPacWin |
.1.3.6.1.4.1.562.2.4.1.110.14.102.10.1.4 |
This is the maximum size of the send pacing window on the
session.
|
appnDluDsStatCurTxPacWin |
.1.3.6.1.4.1.562.2.4.1.110.14.102.10.1.5 |
This is the current size of the send pacing window on the session.
|
appnDluDsStatMaxRxPacWin |
.1.3.6.1.4.1.562.2.4.1.110.14.102.10.1.6 |
This is the maximum size of the receive pacing window on the
session.
|
appnDluDsStatCurRxPacWin |
.1.3.6.1.4.1.562.2.4.1.110.14.102.10.1.7 |
This is the current size of the receive pacing window on the
session.
|
appnDluDsStatTxDataframes |
.1.3.6.1.4.1.562.2.4.1.110.14.102.10.1.8 |
This attribute counts the number of normal flow data frames sent
on the session, the counter wraps to zero.
|
appnDluDsStatTxFmdFrames |
.1.3.6.1.4.1.562.2.4.1.110.14.102.10.1.9 |
This attribute counts the number of FMD data frames sent on the
session, the counter wraps to zero.
|
appnDluDsStatTxDataBytes |
.1.3.6.1.4.1.562.2.4.1.110.14.102.10.1.10 |
This is the number of normal flow data bytes sent on the session,
the counter wraps to zero.
|
appnDluDsStatRxDataFrames |
.1.3.6.1.4.1.562.2.4.1.110.14.102.10.1.11 |
This is the number of normal flow data frames received on the
session, the counter wraps to zero.
|
appnDluDsStatRxFmdFrames |
.1.3.6.1.4.1.562.2.4.1.110.14.102.10.1.12 |
This attribute counts the number of FMD data frames received on
the session, the counter wraps to zero.
|
appnDluDsStatRxDataBytes |
.1.3.6.1.4.1.562.2.4.1.110.14.102.10.1.13 |
This is the number of normal flow data bytes received on the
session, the counter wraps to zero.
|
appnDluDsStatSidh |
.1.3.6.1.4.1.562.2.4.1.110.14.102.10.1.14 |
This attribute contains the session identifier high byte on the
session.
|
appnDluDsStatSidl |
.1.3.6.1.4.1.562.2.4.1.110.14.102.10.1.15 |
This attribute contains the session ID low byte on the SSCP session.
|
appnDluDsStatOdai |
.1.3.6.1.4.1.562.2.4.1.110.14.102.10.1.16 |
This is the origin destination assignor indicator (ODAI) on the
session.
|
appnDluDsStatLsName |
.1.3.6.1.4.1.562.2.4.1.110.14.102.10.1.17 |
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.
|
appnDlusIndex |
.1.3.6.1.4.1.562.2.4.1.110.15.1.1.10 |
This variable represents the index for the appnDlus tables.
|
appnDlusRowStatus |
.1.3.6.1.4.1.562.2.4.1.110.15.1.1.1 |
This variable is used as the basis for SNMP naming of
appnDlus components.
These components cannot be added nor deleted.
|
appnDlusComponentName |
.1.3.6.1.4.1.562.2.4.1.110.15.1.1.2 |
This variable provides the component's string name for
use with the ASCII Console Interface
|
appnDlusStorageType |
.1.3.6.1.4.1.562.2.4.1.110.15.1.1.4 |
This variable represents the storage type value for the
appnDlus tables.
|
appnDlusPrimaryDlus |
.1.3.6.1.4.1.562.2.4.1.110.15.10.1.1 |
This attribute indicates if this is the pipe to the primary default
dependent LU server.
|
appnDlusPipeState |
.1.3.6.1.4.1.562.2.4.1.110.15.10.1.2 |
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.
|
appnDlusActivePUs |
.1.3.6.1.4.1.562.2.4.1.110.15.10.1.3 |
This attribute indicates the number of active physical units using the
pipe.
|
appnDlusReqActPuTx |
.1.3.6.1.4.1.562.2.4.1.110.15.11.1.1 |
This attribute counts the number of REQACTPUs sent to the
DLUS. The counter wraps to zero.
|
appnDlusReqActPuRspRx |
.1.3.6.1.4.1.562.2.4.1.110.15.11.1.2 |
This attribute counts the number of REQACTPU responses received
from the DLUS. The counter wraps to zero.
|
appnDlusActPuRx |
.1.3.6.1.4.1.562.2.4.1.110.15.11.1.3 |
This attributes counts the number of ACTPUs received from the
DLUS. The counter wraps to zero.
|
appnDlusActPuRspTx |
.1.3.6.1.4.1.562.2.4.1.110.15.11.1.4 |
This attribute counts the number of ACTPU responses sent to the
DLUS. The counter wraps to zero.
|
appnDlusReqDactPuTx |
.1.3.6.1.4.1.562.2.4.1.110.15.11.1.5 |
This attribute counts the number of REQDACTPUs sent to the
DLUS. The counter wraps to zero.
|
appnDlusReqDactPuRspRx |
.1.3.6.1.4.1.562.2.4.1.110.15.11.1.6 |
This attribute counts the number of REQDACTPU responses
received from the DLUS. The counter wraps to zero.
|
appnDlusDactPuRx |
.1.3.6.1.4.1.562.2.4.1.110.15.11.1.7 |
This attribute counts the number of DACTPUs received from the
DLUS. The counter wraps to zero.
|
appnDlusDactPuRspTx |
.1.3.6.1.4.1.562.2.4.1.110.15.11.1.8 |
This attribute counts the number of DACTPU responses received
from the DLUS. The counter wraps to zero.
|
appnDlusActLuRx |
.1.3.6.1.4.1.562.2.4.1.110.15.11.1.9 |
This attribute counts the number of ACTLUs received from the
DLUS. The counter wraps to zero.
|
appnDlusActLuRspTx |
.1.3.6.1.4.1.562.2.4.1.110.15.11.1.10 |
This attribute counts the number of ACTLU responses sent to the
DLUS. The counter wraps to zero.
|
appnDlusDactLuRx |
.1.3.6.1.4.1.562.2.4.1.110.15.11.1.11 |
This attribute counts the number of DACTLUs received from the
DLUS. The counter wraps to zero.
|
appnDlusDactLuRspTx |
.1.3.6.1.4.1.562.2.4.1.110.15.11.1.12 |
This attribute counts the number of DACTLU responses sent to the
DLUS. The counter wraps to zero.
|
appnDlusSscpPuMuRx |
.1.3.6.1.4.1.562.2.4.1.110.15.11.1.13 |
This attribute counts the number of SSCP-PU MUs received. The
counter wraps to zero.
|
appnDlusSscpPuMuTx |
.1.3.6.1.4.1.562.2.4.1.110.15.11.1.14 |
This attribute counts the number of SSCP-PU MUs sent. The
counter wraps to zero.
|
appnDlusSscpLuMuRx |
.1.3.6.1.4.1.562.2.4.1.110.15.11.1.15 |
This attributes counts the number of SSCP-LU MUs received. The
counter wraps to zero.
|
appnDlusSscpLuMuTx |
.1.3.6.1.4.1.562.2.4.1.110.15.11.1.16 |
This attributes counts the number of SSCP-LU MUs sent. The
counter wraps to zero.
|
appnDLURIndex |
.1.3.6.1.4.1.562.2.4.1.110.16.1.1.10 |
This variable represents the index for the appnDLUR tables.
|
appnDLURRowStatus |
.1.3.6.1.4.1.562.2.4.1.110.16.1.1.1 |
This variable is used as the basis for SNMP naming of
appnDLUR components.
These components can be added and deleted.
|
appnDLURComponentName |
.1.3.6.1.4.1.562.2.4.1.110.16.1.1.2 |
This variable provides the component's string name for
use with the ASCII Console Interface
|
appnDLURStorageType |
.1.3.6.1.4.1.562.2.4.1.110.16.1.1.4 |
This variable represents the storage type value for the
appnDLUR tables.
|
appnDLURPrimaryDefDlusName |
.1.3.6.1.4.1.562.2.4.1.110.16.2.1.2 |
The fully qualified CP name of the node that will serve as the
primary dependent LU server (DLUS).
|
appnDLURSecondaryDefDlusName |
.1.3.6.1.4.1.562.2.4.1.110.16.2.1.3 |
The fully qualified CP name of the node that will serve as the
backup or secondary dependent LU server (DLUS).
|
appnDLURDlusRetryTimeout |
.1.3.6.1.4.1.562.2.4.1.110.16.2.1.4 |
This attribute specifies the time in seconds before a network search
to locate a DLUS times out.
|
appnDLURDlusRetryLimit |
.1.3.6.1.4.1.562.2.4.1.110.16.2.1.5 |
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.
|
appnCosIndex |
.1.3.6.1.4.1.562.2.4.1.110.17.1.1.10 |
This variable represents the index for the appnCos tables.
|
appnCosRowStatus |
.1.3.6.1.4.1.562.2.4.1.110.17.1.1.1 |
This variable is used as the basis for SNMP naming of
appnCos components.
These components can be added and deleted.
|
appnCosComponentName |
.1.3.6.1.4.1.562.2.4.1.110.17.1.1.2 |
This variable provides the component's string name for
use with the ASCII Console Interface
|
appnCosStorageType |
.1.3.6.1.4.1.562.2.4.1.110.17.1.1.4 |
This variable represents the storage type value for the
appnCos tables.
|
appnCosTransmissionPriority |
.1.3.6.1.4.1.562.2.4.1.110.17.104.1.1 |
This attribute specifies the transmission priority of session traffic
using this class of service.
|
appnCosTgIndex |
.1.3.6.1.4.1.562.2.4.1.110.17.10.1.1.10 |
This variable represents the index for the appnCosTg tables.
|
appnCosTgRowStatus |
.1.3.6.1.4.1.562.2.4.1.110.17.10.1.1.1 |
This variable is used as the basis for SNMP naming of
appnCosTg components.
These components can be added and deleted.
|
appnCosTgComponentName |
.1.3.6.1.4.1.562.2.4.1.110.17.10.1.1.2 |
This variable provides the component's string name for
use with the ASCII Console Interface
|
appnCosTgStorageType |
.1.3.6.1.4.1.562.2.4.1.110.17.10.1.1.4 |
This variable represents the storage type value for the
appnCosTg tables.
|
appnCosTgMinEffectiveCapacity |
.1.3.6.1.4.1.562.2.4.1.110.17.10.10.1.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
acceptable speed for a TG using this Class of Service.
|
appnCosTgMaxEffectiveCapacity |
.1.3.6.1.4.1.562.2.4.1.110.17.10.10.1.2 |
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.
|
appnCosTgMinConnectCost |
.1.3.6.1.4.1.562.2.4.1.110.17.10.10.1.3 |
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).
|
appnCosTgMaxConnectCost |
.1.3.6.1.4.1.562.2.4.1.110.17.10.10.1.4 |
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).
|
appnCosTgMinByteCost |
.1.3.6.1.4.1.562.2.4.1.110.17.10.10.1.5 |
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.
|
appnCosTgMaxByteCost |
.1.3.6.1.4.1.562.2.4.1.110.17.10.10.1.6 |
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.
|
appnCosTgMinSecurity |
.1.3.6.1.4.1.562.2.4.1.110.17.10.10.1.7 |
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.
|
appnCosTgMaxSecurity |
.1.3.6.1.4.1.562.2.4.1.110.17.10.10.1.8 |
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.
|
appnCosTgMinPropDelay |
.1.3.6.1.4.1.562.2.4.1.110.17.10.10.1.9 |
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
|
appnCosTgMaxPropDelay |
.1.3.6.1.4.1.562.2.4.1.110.17.10.10.1.10 |
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
|
appnCosTgMinModemClass |
.1.3.6.1.4.1.562.2.4.1.110.17.10.10.1.11 |
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.
|
appnCosTgMaxModemClass |
.1.3.6.1.4.1.562.2.4.1.110.17.10.10.1.12 |
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
modem class allowed for a TG to carry session traffic.
|
appnCosTgMinUserDefParm1 |
.1.3.6.1.4.1.562.2.4.1.110.17.10.10.1.13 |
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 value for user defined routing parameter number 1.
|
appnCosTgMaxUserDefParm1 |
.1.3.6.1.4.1.562.2.4.1.110.17.10.10.1.14 |
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 value for user defined routing parameter number 1.
|
appnCosTgMinUserDefParm2 |
.1.3.6.1.4.1.562.2.4.1.110.17.10.10.1.15 |
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 value for user defined routing parameter number 2.
|
appnCosTgMaxUserDefParm2 |
.1.3.6.1.4.1.562.2.4.1.110.17.10.10.1.16 |
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 value for user defined routing parameter number 2.
|
appnCosTgMinUserDefParm3 |
.1.3.6.1.4.1.562.2.4.1.110.17.10.10.1.17 |
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 value for user defined routing parameter number 3.
|
appnCosTgMaxUserDefParm3 |
.1.3.6.1.4.1.562.2.4.1.110.17.10.10.1.18 |
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 contains the maximum
acceptable value for user defined routing parameter number 3.
|
appnCosNodeIndex |
.1.3.6.1.4.1.562.2.4.1.110.17.11.1.1.10 |
This variable represents the index for the appnCosNode tables.
|
appnCosNodeRowStatus |
.1.3.6.1.4.1.562.2.4.1.110.17.11.1.1.1 |
This variable is used as the basis for SNMP naming of
appnCosNode components.
These components can be added and deleted.
|
appnCosNodeComponentName |
.1.3.6.1.4.1.562.2.4.1.110.17.11.1.1.2 |
This variable provides the component's string name for
use with the ASCII Console Interface
|
appnCosNodeStorageType |
.1.3.6.1.4.1.562.2.4.1.110.17.11.1.1.4 |
This variable represents the storage type value for the
appnCosNode tables.
|
appnCosNodeMinRouteAddResistance |
.1.3.6.1.4.1.562.2.4.1.110.17.11.10.1.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
route addition resistance value allowed for a node to route session
traffic. Route addition resistance defines the desirability for a
network node to perform additional intermediate session routing.
The higher the value, the less desirable the node is for session
routing purposes.
|
appnCosNodeMaxRouteAddResistance |
.1.3.6.1.4.1.562.2.4.1.110.17.11.10.1.2 |
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
route addition resistance value allowed for a node to route session
traffic. Route addition resistance defines the desirability for a
network node to perform additional intermediate session routing.
The higher the value, the less desirable the node is for session
routing purposes.
|
appnCosNodeMinStatus |
.1.3.6.1.4.1.562.2.4.1.110.17.11.10.1.3 |
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
congestion value that will be allowed for a node to carry session
traffic.
|
appnCosNodeMaxStatus |
.1.3.6.1.4.1.562.2.4.1.110.17.11.10.1.4 |
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
congestion value that will be allowed for a node to carry session
traffic.
|
appnFrSvcIndex |
.1.3.6.1.4.1.562.2.4.1.110.18.1.1.10 |
This variable represents the index for the appnFrSvc tables.
|
appnFrSvcRowStatus |
.1.3.6.1.4.1.562.2.4.1.110.18.1.1.1 |
This variable is used as the basis for SNMP naming of
appnFrSvc components.
These components can be added and deleted.
|
appnFrSvcComponentName |
.1.3.6.1.4.1.562.2.4.1.110.18.1.1.2 |
This variable provides the component's string name for
use with the ASCII Console Interface
|
appnFrSvcStorageType |
.1.3.6.1.4.1.562.2.4.1.110.18.1.1.4 |
This variable represents the storage type value for the
appnFrSvc tables.
|
appnFrSvcBanLocalMac |
.1.3.6.1.4.1.562.2.4.1.110.18.10.1.1 |
This attribute specifies the MAC address to be used for Frame Relay
SVCs with BAN encapsulation.
|
appnFrSvcBanLocalSap |
.1.3.6.1.4.1.562.2.4.1.110.18.10.1.2 |
This attribute specifies the local SAP number to be used for Frame
Relay SVCs with BAN encapsulation.
|
appnFrSvcMaximumFrameRelaySvcs |
.1.3.6.1.4.1.562.2.4.1.110.18.11.1.1 |
This attribute specifies the maximum number of concurrently active
Frame Relay SVC calls that are allowed for this service. This
attribute does not include the general switched virtual circuits
(GSVC).
|
appnFrSvcRateEnforcement |
.1.3.6.1.4.1.562.2.4.1.110.18.11.1.2 |
This attribute specifies whether rate enforcement is to be used for
new Frame Relay SVCs on this service. When rate enforcement is
on the rate of data sent by the service to individual Frame Relay
SVCs is controlled.
|
appnFrSvcMaximumCir |
.1.3.6.1.4.1.562.2.4.1.110.18.11.1.4 |
This attribute specifies the maximum rate enforcement CIR
(Committed Information Rate) that is allowed for use with the
Frame Relay SVCs on this service. During call setup negotiation, if
the caller to this service requests a higher CIR value be used, the
CIR used is reduced to the value of maximumCir.
|
appnFrSvcCurrentNumberOfSvcCalls |
.1.3.6.1.4.1.562.2.4.1.110.18.12.1.1 |
This attribute indicates the number of Frame Relay SVCs currently
existing on this service. This attribute does not include the general
switched virtual circuits (GSVC).
|
appnCnIndex |
.1.3.6.1.4.1.562.2.4.1.110.19.1.1.10 |
This variable represents the index for the appnCn tables.
|
appnCnRowStatus |
.1.3.6.1.4.1.562.2.4.1.110.19.1.1.1 |
This variable is used as the basis for SNMP naming of
appnCn components.
These components cannot be added nor deleted.
|
appnCnComponentName |
.1.3.6.1.4.1.562.2.4.1.110.19.1.1.2 |
This variable provides the component's string name for
use with the ASCII Console Interface
|
appnCnStorageType |
.1.3.6.1.4.1.562.2.4.1.110.19.1.1.4 |
This variable represents the storage type value for the
appnCn tables.
|
appnCnNumberActivePorts |
.1.3.6.1.4.1.562.2.4.1.110.19.5.1.219 |
This attribute specifies the number of active ports under this
ConnectionNetwork.
|