lpImaIndex |
.1.3.6.1.4.1.562.2.4.1.12.22.1.1.10 |
This variable represents the index for the lpIma tables.
|
lpImaRowStatus |
.1.3.6.1.4.1.562.2.4.1.12.22.1.1.1 |
This variable is used as the basis for SNMP naming of
lpIma components.
These components can be added and deleted.
|
lpImaComponentName |
.1.3.6.1.4.1.562.2.4.1.12.22.1.1.2 |
This variable provides the component's string name for
use with the ASCII Console Interface
|
lpImaStorageType |
.1.3.6.1.4.1.562.2.4.1.12.22.1.1.4 |
This variable represents the storage type value for the
lpIma tables.
|
lpImaLinkSelectionCriterion |
.1.3.6.1.4.1.562.2.4.1.12.22.10.1.1 |
This attribute specifies the method to be used by the IMA group
when selecting links to be activated. This comes into effect only
when the configured links do not respect the maximum differential
delay (otherwise all links are accepted).
If leastDelay is chosen, first the link having the smallest delay is
selected as the reference link. The IMA group will then include all
links which respect the maximum differential delay relative to the
reference link.
If maxBandwidth is chosen, the IMA group will select the
maximum possible number of links, with each selected link
respecting the maximum differential delay relative to every other
selected link. When more than one possibility exists, the
combination which offers the least delay will be selected.
|
lpImaMaxDiffDelay |
.1.3.6.1.4.1.562.2.4.1.12.22.10.1.2 |
This attribute specifies the maximum differential delay (in
milliseconds) between links acceptable in the IMA group. If a link
violates that maximum differential delay, it will not be active in the
IMA group and an alarm will be generated.
|
lpImaLinkRetryTimeout |
.1.3.6.1.4.1.562.2.4.1.12.22.10.1.3 |
This attribute specifies the amount of time (in seconds) before
reactivation of a link is attempted after it recovers from a failure
condition.
|
lpImaApplicationFramerName |
.1.3.6.1.4.1.562.2.4.1.12.22.10.1.4 |
This attribute defines the link to the AtmIf component using the Ima.
An example is AtmIf/31.
|
lpImaTransmitClockMode |
.1.3.6.1.4.1.562.2.4.1.12.22.10.1.5 |
This attribute specifies the transmit clocking mode.
If itc (Independent Transmit Clock) is chosen, the physical ports
used by the IMA group may have different clocking sources.
If ctc (Common Transmit Clock) is chosen, it is recommended that
the physical ports used by the IMA group have the same clocking
source. However, if the physical ports have different clocking
sources, the operator should ensure that all the clocking sources
have the same rate.
|
lpImaProtocol |
.1.3.6.1.4.1.562.2.4.1.12.22.10.1.6 |
This attribute specifies what protocol the component should run.
If atmForum10 is chosen, the ATM Forum's IMA protocol (version
1.0) will be used and signalled in outgoing IMA Control Protocol
(ICP) cells. This protocol is specified in version 1.1 of the ATM
Forum IMA specification. The IMA group will come up only if the
far end IMA also uses the ATM Forum's IMA protocol.
If proprietary is chosen, Nortel's proprietary IMA protocol will be
used. The IMA group will come up only if the far end IMA also
uses Nortel's proprietary IMA protocol. This IMA group will not
inter-operate with IMA implementations from other vendors.
Feature ima must be provisioned on the LP for this protocol to be
used.
|
lpImaFailureCause |
.1.3.6.1.4.1.562.2.4.1.12.22.11.1.1 |
This attribute indicates the cause of the current local end failure
experienced by the IMA group. The failure may have occurred
during a start-up procedure or during normal operation. Possible
values are:
noFailure: no local end failure.
noGoodLinksInStartup: no good links were available during IMA
start-up.
badGidInStartup: during start-up, different group identifiers (GIDs)
were received on the links.
badLidInStartup: during start-up, duplicate link identifiers (LIDs)
were received on the links.
unsupportedFrameLengthInStartup: during start-up, an
unsupported frame length was received.
timeoutInStartup: a time-out has occurred during start-up.
noGoodLinks: no good links are available in the IMA group.
remoteFailure: the far end is down.
unsupportedSymmetryInStartup: the symmetry proposed by the far
end is not supported on the near-end. This value will occur when
the IMA group is running the ATM Forum protocol and the far end
is proposing a group symmetry other than 'symmetric configuration
and operation'.
|
lpImaRemoteDefect |
.1.3.6.1.4.1.562.2.4.1.12.22.11.1.2 |
This attribute indicates the cause of the current far end defect
experienced by the IMA group.
For the ATM Forum IMA protocol, possible values are:
noDefect: no defect.
unsupportedFrameLengthInStartup: during the far end's start-up,
an unsupported frame length was received.
unsupportedSymmetryInStartup: during the far end's start-up, an
unsupported symmetry configuration was received.
otherAbortStartup: the far end has aborted its start-up for another
reason. This could be because different Gids were received on the
links or if duplicate link identifiers (LIDs) were received.
insufficientLinks: the far end does not have sufficient links active.
This value will be displayed if the far end IMA group is locked.
blocked: the far end IMA group is blocked.
For the proprietary IMA protocol, possible values are:
noDefect: no defect.
noGoodLinksInStartup: no good links were available during the far
end's start-up.
badGidInStartup: during the far end's start-up, different GIDs were
received on the links.
badLidInStartup: during the far end's start-up, duplicate link
identifiers (LIDs) were received on the links.
unsupportedFrameLengthInStartup: during the far end's start-up,
an unsupported frame length was received.
timeoutInStartup: a time out has occurred during the far end's start-
up.
noGoodLinks: no good links are available in the far end IMA
group.
locked: the far end IMA group is locked.
|
lpImaRemoteLidsConfig |
.1.3.6.1.4.1.562.2.4.1.12.22.11.1.3 |
This attribute indicates all the links which have been configured in
the remote IMA group. For example, if links 1, 3 and 5 have been
configured in the remote IMA group, this attribute would contain 1
3 5.
Description of bits:
n0(0)
n1(1)
n2(2)
n3(3)
n4(4)
n5(5)
n6(6)
n7(7)
n8(8)
n9(9)
n10(10)
n11(11)
n12(12)
n13(13)
n14(14)
n15(15)
n16(16)
n17(17)
n18(18)
n19(19)
n20(20)
n21(21)
n22(22)
n23(23)
n24(24)
n25(25)
n26(26)
n27(27)
n28(28)
n29(29)
n30(30)
n31(31)
|
lpImaRemoteLidsActive |
.1.3.6.1.4.1.562.2.4.1.12.22.11.1.4 |
This attribute indicates all the links which are active in the remote
IMA group. For example, if links 1 and 5 are active in the remote
IMA, this attribute would contain 1 5.
Description of bits:
n0(0)
n1(1)
n2(2)
n3(3)
n4(4)
n5(5)
n6(6)
n7(7)
n8(8)
n9(9)
n10(10)
n11(11)
n12(12)
n13(13)
n14(14)
n15(15)
n16(16)
n17(17)
n18(18)
n19(19)
n20(20)
n21(21)
n22(22)
n23(23)
n24(24)
n25(25)
n26(26)
n27(27)
n28(28)
n29(29)
n30(30)
n31(31)
|
lpImaCellCapacity |
.1.3.6.1.4.1.562.2.4.1.12.22.11.1.5 |
This attribute indicates the total cell capacity (in cells per second)
which is provided to the ATM layer. This cell capacity takes into
account the physical and IMA level overheads.
|
lpImaRemoteGid |
.1.3.6.1.4.1.562.2.4.1.12.22.11.1.6 |
This attribute indicates the IMA group identifier (GID) used by the
remote IMA. A value of 0 will be displayed if the group is not
receiving IMA Control Protocol (ICP) cells.
This attribute will always have a value of 0 if the protocol for the
IMA group is proprietary.
|
lpImaClockingModeMismatch |
.1.3.6.1.4.1.562.2.4.1.12.22.11.1.7 |
This attribute indicates whether or not both ends of the IMA group
are using the same transmit clocking mode (itc/ctc). Its value will be
yes if both ends are not using the same transmit clocking mode. A
clocking mode mismatch does not prevent an IMA group from
coming up and can be corrected by using the same clocking mode at
both ends.
This attribute will always have a value of no if the protocol for the
IMA group is proprietary.
|
lpImaRunningTime |
.1.3.6.1.4.1.562.2.4.1.12.22.12.1.1 |
This attribute indicates the length of time (in seconds) for which the
Ima component has been in the unlocked state or has been used for
operational testing.
|
lpImaUnavailSecs |
.1.3.6.1.4.1.562.2.4.1.12.22.12.1.2 |
This attribute indicates the number of one second intervals during
which the Ima component has been unlocked and out of service.
|
lpImaFailures |
.1.3.6.1.4.1.562.2.4.1.12.22.12.1.3 |
This attribute indicates the number of complete failures, during
start-up or normal operation, that the Ima component has
experienced since being added. It must be noted that a service
degradation, such as 1 of the 3 links in an IMA group being down,
is not counted as a failure. If an Ima component is in a failure loop
and does not come up, this count will only increase by 1.
|
lpImaReceiveCellUtilization |
.1.3.6.1.4.1.562.2.4.1.12.22.12.1.4 |
This attribute indicates the ratio of the number of valid, assigned
user cells received on the IMA group to the IMA cell capacity
(based on the number of active links). The utilization is calculated
over a one minute period.
This attribute will always have a value of 0 if the protocol for the
IMA group is proprietary.
|
lpImaTransmitCellUtilization |
.1.3.6.1.4.1.562.2.4.1.12.22.12.1.5 |
This attribute indicates the ratio of the number of user cells
transmitted on the IMA group to the IMA cell capacity (based on
the number of active links). The utilization is calculated over a one
minute period.
This attribute will always have a value of 0 if the protocol for the
IMA group is proprietary.
|
lpImaCustomerIdentifier |
.1.3.6.1.4.1.562.2.4.1.12.22.13.1.1 |
This attribute holds the Customer Identifier (CID).
Every component has a CID. If a component has a cid attribute, the
component's CID is the provisioned value of that attribute;
otherwise the component inherits the CID of its parent. The top-
level component has a CID of 0.
Every operator session also has a CID, which is the CID
provisioned for the operator's user ID. An operator will see only the
stream data for components having a matching CID. Also, the
operator will be allowed to issue commands for only those
components which have a matching CID.
An operator CID of 0 is used to identify the Network Manager
(referred to as 'NetMan' in DPN). This CID matches the CID of
any component. Values 1 to 8191 inclusive (equivalent to 'basic
CIDs' in DPN) may be assigned to specific customers.
|
lpImaAdminState |
.1.3.6.1.4.1.562.2.4.1.12.22.14.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.
The OSI Status attributes, if supported by the component, may
provide more details, qualifying the state of the component.
|
lpImaOperationalState |
.1.3.6.1.4.1.562.2.4.1.12.22.14.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.
The OSI Status attributes, if supported by the component, may
provide more details, qualifying the state of the component.
|
lpImaUsageState |
.1.3.6.1.4.1.562.2.4.1.12.22.14.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.
The OSI Status attributes, if supported by the component, may
provide more details, qualifying the state of the component.
|
lpImaAvailabilityStatus |
.1.3.6.1.4.1.562.2.4.1.12.22.14.1.4 |
If supported by the component, this attribute indicates the OSI
Availability status of the component. Note that, even though it is
defined as a multi-valued set, at most one value is shown to the user.
When no values are in the set, this indicates that either the attribute
is not supported or that none of the status conditions described
below are present.
The value inTest indicates that the resource is undergoing a test
procedure. If adminState is locked or shuttingDown, the normal
users are precluded from using the resource and controlStatus is
reservedForTest. Tests that do not exclude additional users can be
present in any operational or administrative state but the
reservedForTest condition should not be present.
The value failed indicates that the component has an internal fault
that prevents it from operating. The operationalState is disabled.
The value dependency indicates that the component cannot operate
because some other resource on which it depends is unavailable.
The operationalState is disabled.
The value powerOff indicates the resource requires power to be
applied and it is not powered on. The operationalState is disabled.
The value offLine indicates the resource requires a routine
operation (either manual, automatic, or both) to be performed to
place it on-line and make it available for use. The operationalState
is disabled.
The value offDuty indicates the resource is inactive in accordance
with a predetermined time schedule. In the absence of other
disabling conditions, the operationalState is enabled or disabled.
The value degraded indicates the service provided by the
component is degraded in some way, such as in speed or operating
capacity. However, the resource remains available for service. The
operationalState is enabled.
The value notInstalled indicates the resource is not present. The
operationalState is disabled.
The value logFull is not used.
Description of bits:
inTest(0)
failed(1)
powerOff(2)
offLine(3)
offDuty(4)
dependency(5)
degraded(6)
notInstalled(7)
logFull(8)
|
lpImaProceduralStatus |
.1.3.6.1.4.1.562.2.4.1.12.22.14.1.5 |
If supported by the component, this attribute indicates the OSI
Procedural status of the component. Note that, even though it is
defined as a multi-valued set, at most one value is shown to the user.
When no values are in the set, this indicates that either the attribute
is not supported or that none of the status conditions described
below are present.
The value initializationRequired indicates (for a resource which
doesn't initialize autonomously) that initialization is required before
it can perform its normal functions, and this procedure has not been
initiated. The operationalState is disabled.
The value notInitialized indicates (for a resource which does
initialize autonomously) that initialization is required before it can
perform its normal functions, and this procedure has not been
initiated. The operationalState may be enabled or disabled.
The value initializing indicates that initialization has been initiated
but is not yet complete. The operationalState may be enabled or
disabled.
The value reporting indicates the resource has completed some
processing operation and is notifying the results. The
operationalState is enabled.
The value terminating indicates the component is in a termination
phase. If the resource doesn't reinitialize autonomously,
operationalState is disabled; otherwise it is enabled or disabled.
Description of bits:
initializationRequired(0)
notInitialized(1)
initializing(2)
reporting(3)
terminating(4)
|
lpImaControlStatus |
.1.3.6.1.4.1.562.2.4.1.12.22.14.1.6 |
If supported by the component, this attribute indicates the OSI
Control status of the component. Note that, even though it is defined
as a multi-valued set, at most one value is shown to the user.
When no values are in the set, this indicates that either the attribute
is not supported or that none of the status conditions described
below are present.
The value subjectToTest indicates the resource is available but tests
may be conducted simultaneously at unpredictable times, which
may cause it to exhibit unusual characteristics.
The value partOfServicesLocked indicates that part of the service is
restricted from users of a resource. The adminState is unlocked.
The value reservedForTest indicates that the component is
administratively unavailable because it is undergoing a test
procedure. The adminState is locked.
The value suspended indicates that the service has been
administratively suspended.
Description of bits:
subjectToTest(0)
partOfServicesLocked(1)
reservedForTest(2)
suspended(3)
|
lpImaAlarmStatus |
.1.3.6.1.4.1.562.2.4.1.12.22.14.1.7 |
If supported by the component, this attribute indicates the OSI
Alarm status of the component. Note that, even though it is defined
as a multi-valued set, at most one value is shown to the user.
When no values are in the set, this indicates that either the attribute
is not supported or that none of the status conditions described
below are present.
The value underRepair indicates the component is currently being
repaired. The operationalState is enabled or disabled.
The value critical indicates one or more critical alarms are
outstanding against the component. Other, less severe, alarms may
also be outstanding. The operationalState is enabled or disabled.
The value major indicates one or more major alarms are
outstanding against the component. Other, less severe, alarms may
also be outstanding. The operationalState is enabled or disabled.
The value minor indicates one or more minor alarms are
outstanding against the component. Other, less severe, alarms may
also be outstanding. The operationalState is enabled or disabled.
The value alarmOutstanding generically indicates that an alarm of
some severity is outstanding against the component.
Description of bits:
underRepair(0)
critical(1)
major(2)
minor(3)
alarmOutstanding(4)
|
lpImaStandbyStatus |
.1.3.6.1.4.1.562.2.4.1.12.22.14.1.8 |
If supported by the component, this attribute indicates the OSI
Standby status of the component.
The value notSet indicates that either the attribute is not supported
or that none of the status conditions described below are present.
Note that this is a non-standard value, used because the original
specification indicated this attribute was set-valued and thus, did not
provide a value to indicate that none of the other three are
applicable.
The value hotStandby indicates that the resource is not providing
service but will be immediately able to take over the role of the
resource to be backed up, without initialization activity, and
containing the same information as the resource to be backed up.
The value coldStandby indicates the resource is a backup for
another resource but will not be immediately able to take over the
role of the backed up resource and will require some initialization
activity.
The value providingService indicates that this component, as a
backup resource, is currently backing up another resource.
|
lpImaUnknownStatus |
.1.3.6.1.4.1.562.2.4.1.12.22.14.1.9 |
This attribute indicates the OSI Unknown status of the component.
The value false indicates that all of the other OSI State and Status
attribute values can be considered accurate.
The value true indicates that the actual state of the component is not
known for sure.
|
lpImaTestIndex |
.1.3.6.1.4.1.562.2.4.1.12.22.2.1.1.10 |
This variable represents the index for the lpImaTest tables.
|
lpImaTestRowStatus |
.1.3.6.1.4.1.562.2.4.1.12.22.2.1.1.1 |
This variable is used as the basis for SNMP naming of
lpImaTest components.
These components cannot be added nor deleted.
|
lpImaTestComponentName |
.1.3.6.1.4.1.562.2.4.1.12.22.2.1.1.2 |
This variable provides the component's string name for
use with the ASCII Console Interface
|
lpImaTestStorageType |
.1.3.6.1.4.1.562.2.4.1.12.22.2.1.1.4 |
This variable represents the storage type value for the
lpImaTest tables.
|
lpImaTestAdminState |
.1.3.6.1.4.1.562.2.4.1.12.22.2.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.
|
lpImaTestOperationalState |
.1.3.6.1.4.1.562.2.4.1.12.22.2.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.
|
lpImaTestUsageState |
.1.3.6.1.4.1.562.2.4.1.12.22.2.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.
|
lpImaTestPurpose |
.1.3.6.1.4.1.562.2.4.1.12.22.2.11.1.1 |
This attribute records the purpose of the test so that the test results
can be associated and properly analyzed.
|
lpImaTestType |
.1.3.6.1.4.1.562.2.4.1.12.22.2.11.1.2 |
This attribute is the type of test to be run. The available test types
include the following:
card test sets up an internal loop on the board and runs a bit error
rate test.
manual test assumes the line is looped back externally and a bit
error rate test is performed.
localLoop test loops back the local modem and performs a bit error
rate test.
remoteLoop test loops back the remote modem (or CSU) and
performs a bit error rate test.
externalLoop test loops back the line to the far end.
payloadLoop test only loops back the payload data received from
the incoming line.
remoteLoopThisTrib loops this particular tributary back at the far
end, using services provided by the parent.
v54RemoteLoop initiates a V.54 Remote Loopback test.
pn127RemoteLoop initiates a PN127 Remote Loopback test.
Note that not all test types are not supported by all function
processors.
|
lpImaTestFrmSize |
.1.3.6.1.4.1.562.2.4.1.12.22.2.11.1.3 |
This attribute defines the size of the test data frames in number of
bytes.
|
lpImaTestFrmPatternType |
.1.3.6.1.4.1.562.2.4.1.12.22.2.11.1.4 |
This attribute defines the type of data pattern generation to use. The
following lists the available pattern types:
ccitt32kBitPattern is a pseudo-random sequence of 32 kbit.
ccitt8MBitPattern is a pseudo-random sequence of 8Mbit.
customizedPattern is the pattern defined in the customizedPattern
attribute.
|
lpImaTestCustomizedPattern |
.1.3.6.1.4.1.562.2.4.1.12.22.2.11.1.5 |
This attribute allows a customized 32 bit pattern to be defined for
use in the test data frames. This attribute is used when the attribute
frmPatternType is set to CustomizedPattern. Note that a 55 hex
pattern is an alternating 1 and 0 pattern.
|
lpImaTestDataStartDelay |
.1.3.6.1.4.1.562.2.4.1.12.22.2.11.1.6 |
This attribute specifies the time delay (in seconds) between when
the test expects the loop to have been set up, to when the test data
actually starts to be transmitted. This attribute is to accommodate
some non-standard equipment that requires extra time for setting up
a requested loop.
This attribute is ignored when the test type is set to externalLoop.
|
lpImaTestDisplayInterval |
.1.3.6.1.4.1.562.2.4.1.12.22.2.11.1.7 |
This attribute defines the interval (in minutes) between which
interim test results are to be displayed. Results are displayed at the
operator console at which the test was started. When the test type is
set to externalLoop, this attribute is ignored. There will be no
display of results if displayInterval is set to 0. This attribute can be
changed anytime.
|
lpImaTestDuration |
.1.3.6.1.4.1.562.2.4.1.12.22.2.11.1.8 |
This attribute is the duration (in minutes) that test data will be
transmitted. In the case of an externalLoop, this is the time that the
loop is in effect. Note that dataStartDelay does not apply to the
externalLoop.
|
lpImaTestElapsedTime |
.1.3.6.1.4.1.562.2.4.1.12.22.2.12.1.1 |
This attribute is the number of minutes elapsed since the test started
for an externalLoop test. For a data test, this is the time since test
data was first transmitted.
|
lpImaTestTimeRemaining |
.1.3.6.1.4.1.562.2.4.1.12.22.2.12.1.2 |
This attribute is the number of minutes remaining before the test is
to be stopped according to the duration attribute.
|
lpImaTestCauseOfTermination |
.1.3.6.1.4.1.562.2.4.1.12.22.2.12.1.3 |
This attribute records the reason the test is terminated.
|
lpImaTestBitsTx |
.1.3.6.1.4.1.562.2.4.1.12.22.2.12.1.4 |
This attribute is the total number of bits sent during the test period.
As long as the line speed of the hardware interface is less than
70 Mbit/s, this counter is not expected to reach the maximum value.
|
lpImaTestBytesTx |
.1.3.6.1.4.1.562.2.4.1.12.22.2.12.1.5 |
This attribute is the total number of bytes sent during the test
period. This counter is not expected to reach its maximum value.
|
lpImaTestFrmTx |
.1.3.6.1.4.1.562.2.4.1.12.22.2.12.1.6 |
This attribute is the total number of frames sent during the test
period. This counter is not expected to reach its maximum value.
|
lpImaTestBitsRx |
.1.3.6.1.4.1.562.2.4.1.12.22.2.12.1.7 |
This attribute is the total number of bits received during the test
period. This counter is not expected to reach its maximum value.
The counter will wrap around to 0 if it does reach the maximum
value.
|
lpImaTestBytesRx |
.1.3.6.1.4.1.562.2.4.1.12.22.2.12.1.8 |
This attribute is the total number of bytes received during the test
period. This counter is not expected to reach its maximum value.
The counter will wrap around to 0 if it does reach its maximum
value.
|
lpImaTestFrmRx |
.1.3.6.1.4.1.562.2.4.1.12.22.2.12.1.9 |
This attribute is the total number of frames received during the test
period. This counter is not expected to reach its maximum value.
The counter will wrap around to 0 if it does reach its maximum
value.
|
lpImaTestErroredFrmRx |
.1.3.6.1.4.1.562.2.4.1.12.22.2.12.1.10 |
This attribute counts the errored frames received during the test
period. This counter is not expected to reach its maximum value.
The counter wraps to 0 if it exceeds its maximum value.
This attribute is not displayed for ATM cards because the physical
layer drops all errored frames at the controller interface.
|
lpImaTestBitErrorRate |
.1.3.6.1.4.1.562.2.4.1.12.22.2.12.1.11 |
This attribute indicates the calculated bit error rate on the link. Test
data are generated and sent in frames of a preset size (frameSize).
The Test component tries to estimate the number of bit errors in any
errored frame which is identifiable. The statistics are updated
accordingly. A lost frame (possibly due to an error on the flag
sequence) is not used for the bit error rate calculation. The result is
presented in the form of xEsyy, where x is the mantissa; and syy is
the exponent, for example 0E+00, 2E-09.
Note that the bitErrorRate is an estimate only. For more reliable test
results, the test should be done over a long period. Multiple tests
would also improve the confidence level of the test results.
This attribute is not displayed for ATM cards because the physical
layer drops all errored frames at the controller interface.
|
lpImaLkIndex |
.1.3.6.1.4.1.562.2.4.1.12.22.3.1.1.10 |
This variable represents the index for the lpImaLk tables.
|
lpImaLkRowStatus |
.1.3.6.1.4.1.562.2.4.1.12.22.3.1.1.1 |
This variable is used as the basis for SNMP naming of
lpImaLk components.
These components can be added and deleted.
|
lpImaLkComponentName |
.1.3.6.1.4.1.562.2.4.1.12.22.3.1.1.2 |
This variable provides the component's string name for
use with the ASCII Console Interface
|
lpImaLkStorageType |
.1.3.6.1.4.1.562.2.4.1.12.22.3.1.1.4 |
This variable represents the storage type value for the
lpImaLk tables.
|
lpImaLkInterfaceName |
.1.3.6.1.4.1.562.2.4.1.12.22.3.10.1.1 |
This attribute associates the Link subcomponent with a specific
interface on a function processor, for example Lp/5 E1/3 Chan/0.
If IMA groups and independent links coexist on a card running
IMA and per-Vc queueing is enabled, plan the selection of DS1/E1
ports to be used by the IMA group carefully.
|
lpImaLkFailureCause |
.1.3.6.1.4.1.562.2.4.1.12.22.3.11.1.1 |
This attribute indicates the failure cause on this link. Possible values
are:
noFailure: there is no failure on this link.
interfaceDown: the physical port used by the link is down.
lif: the link is in loss of IMA frame (LIF) state.
lods: the link is in loss of delay synchronization (LODS) state; that
is, it has exhibited a differential delay which is greater than the
maximum differential delay tolerated by the IMA group. It must be
noted that hysteresis is used for the LODS condition.
protocolError: the link is down because of a time-out or because
bad values are being received in IMA Control Protocol (ICP) cells.
remoteFailure: the far end link is down.
misconnected: the link is down because the IMA group has
declared, after using its transmit test pattern procedure, that this link
is not properly connected. This value can occur only if the protocol
for the IMA group is atmForum10.
unsupportedFrameLength: the link is down because it is receiving
from the far end a frame length which is not supported by the local
IMA group. This value can occur only if the protocol for the IMA
group is atmForum10.
unsupportedSymmetry: the link is down because it is receiving
from the far end a group symmetry which is not supported by the
local IMA group. This value can occur only if the protocol for the
IMA group is atmForum10.
noIcp: the link is down because it is not receiving IMA Control
Protocol (ICP) cells. This value can occur only if the protocol for
the IMA group is atmForum10.
|
lpImaLkRemoteDefect |
.1.3.6.1.4.1.562.2.4.1.12.22.3.11.1.2 |
This attribute indicates the IMA remote defect indicator (RDI)
currently being received on this link. Possible values are:
noDefect: no defect.
physicalLayerDefect: the interface used by the remote link has a
physical layer defect. This value can occur only if the protocol for
the IMA group is atmForum10.
interfaceDown: the physical interface used by the remote link is
down.This value can occur only if the protocol for the IMA group is
proprietary.
lif: the remote link has a loss of IMA frame (LIF) defect.
lods: the remote link has a loss of delay synchronization (LODS)
defect; that is, it has exhibited a differential delay which is greater
than the maximum differential delay tolerated by the IMA group.
|
lpImaLkRemoteLid |
.1.3.6.1.4.1.562.2.4.1.12.22.3.11.1.3 |
This attribute indicates the link identifier (LID) used by the remote
IMA group on the physical link. A value of 0 will be displayed if
the link is not receiving IMA Control Protocol (ICP) cells or if the
physical layer is down.
|
lpImaLkRelativeDelay |
.1.3.6.1.4.1.562.2.4.1.12.22.3.11.1.4 |
This attribute indicates the latest measured differential delay
(rounded up in milliseconds) between this link and the link, in the
same IMA group, having the least delay. A value of 4294967295
indicates that the relative delay could not be measured. This can be
due to physical layer problems or to no IMA Control Protocol (ICP)
cells being received on the link.
|
lpImaLkLastOifCause |
.1.3.6.1.4.1.562.2.4.1.12.22.3.11.1.5 |
This attribute indicates the cause of the last out of IMA frame (OIF)
anomaly on the link. It will always have a value of noOif if the
protocol for the IMA group is proprietary.
Possible values are:
noOif: no OIF was detected.
badFrameLength: an IMA Control Protocol (ICP) cell with an
unexpected frame length was received.
badGid: an ICP cell with an unexpected group identifier (GID) was
received.
badLid: an ICP cell with an unexpected link identifier (LID) was
received.
badOffset: an ICP cell with an unexpected cell offset was received.
badSequenceNumber: an ICP cell with an unexpected frame
sequence number was received.
stuffError: an illegal stuffing sequence was received.
missingIcp: an expected ICP cell was not received.
unexpectedIcp: an unexpected ICP cell was received.
erroredIcp: two consecutive errored ICP cells were received.
noCells: no cells are being received on the link.
idleCell: an idle cell was received on the link.
|
lpImaLkRunningTime |
.1.3.6.1.4.1.562.2.4.1.12.22.3.12.1.1 |
This attribute counts the length of time (in seconds) for which the
Link component has been running.
|
lpImaLkUnavailSecs |
.1.3.6.1.4.1.562.2.4.1.12.22.3.12.1.2 |
For an IMA group whose protocol is atmForum10, this attribute
counts the number of unavailable seconds. Unavailability begins at
the start of 10 contiguous severely errored seconds (SES) and ends
at the start of 10 contiguous seconds with no SES.
For an IMA group whose protocol is proprietary, this attribute
counts the number of one second intervals during which the Link
component has been out of service.
|
lpImaLkFailures |
.1.3.6.1.4.1.562.2.4.1.12.22.3.12.1.3 |
This attribute counts the number of failures, during link addition or
normal operation, that the link has experienced.
|
lpImaLkUnusableSec |
.1.3.6.1.4.1.562.2.4.1.12.22.3.12.1.4 |
This attribute counts the number of one second intervals during
which the near end has been in an unusable state.
This attribute will always have a value of 0 if the protocol for the
IMA group is proprietary.
|
lpImaLkSevErroredSec |
.1.3.6.1.4.1.562.2.4.1.12.22.3.12.1.5 |
This attribute counts the number of one second intervals in which at
least 30 percent of the IMA Control Protocol (ICP) cells were
counted as ICP violations or at least one link defect (physical layer,
LIF and LODS defects) was detected. This attribute will not
increment during UAS (Unavailable Second) conditions.
This attribute will always have a value of 0 if the protocol for the
IMA group is proprietary.
|
lpImaLkFarEndUnusableSec |
.1.3.6.1.4.1.562.2.4.1.12.22.3.12.1.6 |
This attribute counts the number of one second intervals during
which the 'Tx/Rx Unusable' condition has been received from the
far end.
This attribute will always have a value of 0 if the protocol for the
IMA group is proprietary.
|
lpImaLkFarEndSevErroredSec |
.1.3.6.1.4.1.562.2.4.1.12.22.3.12.1.7 |
This attribute counts the number of one second intervals containing
one or more RDI defects. This attribute will not increment during
FEUAS (Far-End Unavailable Second) conditions.
This attribute will always have a value of 0 if the protocol for the
IMA group is proprietary.
|
lpImaLkFarEndUnavailSec |
.1.3.6.1.4.1.562.2.4.1.12.22.3.12.1.8 |
This attribute counts the number of unavailable seconds at the far
end. Unavailability begins at the start of 10 contiguous severely
errored seconds (SES) at the far end and ends at the start of 10
contiguous seconds at the far end with no SES.
This attribute will always have a value of 0 if the protocol for the
IMA group is proprietary.
|
lpImaLkIcpViolations |
.1.3.6.1.4.1.562.2.4.1.12.22.3.12.1.9 |
This attribute counts the number of errored, invalid or missing IMA
Control Protocol (ICP) cells during non-SES (Severely Errored
Second) and non-UAS (Unavailable Seconds) conditions.
This attribute will always have a value of 0 if the protocol for the
IMA group is proprietary.
|
lpImaLkTxStuffEvents |
.1.3.6.1.4.1.562.2.4.1.12.22.3.12.1.10 |
This attribute counts the number of Stuff events transmitted during
non-SES (Severely Errored Second) and non-UAS (Unavailable
Seconds) conditions.
This attribute will always have a value of 0 if the protocol for the
IMA group is proprietary.
|
lpImaLkRxStuffEvents |
.1.3.6.1.4.1.562.2.4.1.12.22.3.12.1.11 |
This attribute counts the number of Stuff events received during
non-SES (Severely Errored Second) and non-UAS (Unavailable
Seconds) conditions.
This attribute will always have a value of 0 if the protocol for the
IMA group is proprietary.
|
lpImaLkIdleCellSec |
.1.3.6.1.4.1.562.2.4.1.12.22.3.12.1.12 |
This attributes counts the number of one second intervals during
which one or more idle cells was received. The reception of idle
cells is an abnormal condition which could be caused by the remote
IMA using the Common Transmit Clock mode with ports whose
clock sources are not synchronized.
This attribute will always have a value of 0 if the protocol for the
IMA group is proprietary.
|
lpImaLkAdminState |
.1.3.6.1.4.1.562.2.4.1.12.22.3.13.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.
The OSI Status attributes, if supported by the component, may
provide more details, qualifying the state of the component.
|
lpImaLkOperationalState |
.1.3.6.1.4.1.562.2.4.1.12.22.3.13.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.
The OSI Status attributes, if supported by the component, may
provide more details, qualifying the state of the component.
|
lpImaLkUsageState |
.1.3.6.1.4.1.562.2.4.1.12.22.3.13.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.
The OSI Status attributes, if supported by the component, may
provide more details, qualifying the state of the component.
|
lpImaLkAvailabilityStatus |
.1.3.6.1.4.1.562.2.4.1.12.22.3.13.1.4 |
If supported by the component, this attribute indicates the OSI
Availability status of the component. Note that, even though it is
defined as a multi-valued set, at most one value is shown to the user.
When no values are in the set, this indicates that either the attribute
is not supported or that none of the status conditions described
below are present.
The value inTest indicates that the resource is undergoing a test
procedure. If adminState is locked or shuttingDown, the normal
users are precluded from using the resource and controlStatus is
reservedForTest. Tests that do not exclude additional users can be
present in any operational or administrative state but the
reservedForTest condition should not be present.
The value failed indicates that the component has an internal fault
that prevents it from operating. The operationalState is disabled.
The value dependency indicates that the component cannot operate
because some other resource on which it depends is unavailable.
The operationalState is disabled.
The value powerOff indicates the resource requires power to be
applied and it is not powered on. The operationalState is disabled.
The value offLine indicates the resource requires a routine
operation (either manual, automatic, or both) to be performed to
place it on-line and make it available for use. The operationalState
is disabled.
The value offDuty indicates the resource is inactive in accordance
with a predetermined time schedule. In the absence of other
disabling conditions, the operationalState is enabled or disabled.
The value degraded indicates the service provided by the
component is degraded in some way, such as in speed or operating
capacity. However, the resource remains available for service. The
operationalState is enabled.
The value notInstalled indicates the resource is not present. The
operationalState is disabled.
The value logFull is not used.
Description of bits:
inTest(0)
failed(1)
powerOff(2)
offLine(3)
offDuty(4)
dependency(5)
degraded(6)
notInstalled(7)
logFull(8)
|
lpImaLkProceduralStatus |
.1.3.6.1.4.1.562.2.4.1.12.22.3.13.1.5 |
If supported by the component, this attribute indicates the OSI
Procedural status of the component. Note that, even though it is
defined as a multi-valued set, at most one value is shown to the user.
When no values are in the set, this indicates that either the attribute
is not supported or that none of the status conditions described
below are present.
The value initializationRequired indicates (for a resource which
doesn't initialize autonomously) that initialization is required before
it can perform its normal functions, and this procedure has not been
initiated. The operationalState is disabled.
The value notInitialized indicates (for a resource which does
initialize autonomously) that initialization is required before it can
perform its normal functions, and this procedure has not been
initiated. The operationalState may be enabled or disabled.
The value initializing indicates that initialization has been initiated
but is not yet complete. The operationalState may be enabled or
disabled.
The value reporting indicates the resource has completed some
processing operation and is notifying the results. The
operationalState is enabled.
The value terminating indicates the component is in a termination
phase. If the resource doesn't reinitialize autonomously,
operationalState is disabled; otherwise it is enabled or disabled.
Description of bits:
initializationRequired(0)
notInitialized(1)
initializing(2)
reporting(3)
terminating(4)
|
lpImaLkControlStatus |
.1.3.6.1.4.1.562.2.4.1.12.22.3.13.1.6 |
If supported by the component, this attribute indicates the OSI
Control status of the component. Note that, even though it is defined
as a multi-valued set, at most one value is shown to the user.
When no values are in the set, this indicates that either the attribute
is not supported or that none of the status conditions described
below are present.
The value subjectToTest indicates the resource is available but tests
may be conducted simultaneously at unpredictable times, which
may cause it to exhibit unusual characteristics.
The value partOfServicesLocked indicates that part of the service is
restricted from users of a resource. The adminState is unlocked.
The value reservedForTest indicates that the component is
administratively unavailable because it is undergoing a test
procedure. The adminState is locked.
The value suspended indicates that the service has been
administratively suspended.
Description of bits:
subjectToTest(0)
partOfServicesLocked(1)
reservedForTest(2)
suspended(3)
|
lpImaLkAlarmStatus |
.1.3.6.1.4.1.562.2.4.1.12.22.3.13.1.7 |
If supported by the component, this attribute indicates the OSI
Alarm status of the component. Note that, even though it is defined
as a multi-valued set, at most one value is shown to the user.
When no values are in the set, this indicates that either the attribute
is not supported or that none of the status conditions described
below are present.
The value underRepair indicates the component is currently being
repaired. The operationalState is enabled or disabled.
The value critical indicates one or more critical alarms are
outstanding against the component. Other, less severe, alarms may
also be outstanding. The operationalState is enabled or disabled.
The value major indicates one or more major alarms are
outstanding against the component. Other, less severe, alarms may
also be outstanding. The operationalState is enabled or disabled.
The value minor indicates one or more minor alarms are
outstanding against the component. Other, less severe, alarms may
also be outstanding. The operationalState is enabled or disabled.
The value alarmOutstanding generically indicates that an alarm of
some severity is outstanding against the component.
Description of bits:
underRepair(0)
critical(1)
major(2)
minor(3)
alarmOutstanding(4)
|
lpImaLkStandbyStatus |
.1.3.6.1.4.1.562.2.4.1.12.22.3.13.1.8 |
If supported by the component, this attribute indicates the OSI
Standby status of the component.
The value notSet indicates that either the attribute is not supported
or that none of the status conditions described below are present.
Note that this is a non-standard value, used because the original
specification indicated this attribute was set-valued and thus, did not
provide a value to indicate that none of the other three are
applicable.
The value hotStandby indicates that the resource is not providing
service but will be immediately able to take over the role of the
resource to be backed up, without initialization activity, and
containing the same information as the resource to be backed up.
The value coldStandby indicates the resource is a backup for
another resource but will not be immediately able to take over the
role of the backed up resource and will require some initialization
activity.
The value providingService indicates that this component, as a
backup resource, is currently backing up another resource.
|
lpImaLkUnknownStatus |
.1.3.6.1.4.1.562.2.4.1.12.22.3.13.1.9 |
This attribute indicates the OSI Unknown status of the component.
The value false indicates that all of the other OSI State and Status
attribute values can be considered accurate.
The value true indicates that the actual state of the component is not
known for sure.
|