Description 1
The operational state for this port:
- unknown: the status of this port is unknown (this can
be the result of a module in error)
- disabled-nosignal: no activity is detected at the physical
layer while the port is disabled.
If the port is a SSI port, the
bandwidth configuration is valid.
- disabled-idle:: activity from the remote device
attached to this port has been
detected by the physical layer.
The port is disabled.
If the port is a SSI port, the bandwidth
configuration is valid.
- failing: an internal hard error has been detected on
this port while the port is enabled
- no signal: no activity is detected at the physical
layer while the port is enabled
- idle: activity from the remote device attached to this
port has been detected by the physical layer.
The port is enabled.
- in-service: the remote device successfully acknowledges
ILMI polling requests and SVC registration
- in-service-no-address-registration:
the remote device succesfully acknowledges
ILMI polling requests but it rejects the ATM
prefix registration. Only PVCs are supported.
- misConfigured:
This value is only reported by 8260 agents
before v3.0 (8285 agents before v2.0).
In that case, misConfigured is returned when
a privateNetwork port is attached to a
privateUni or to a publicUni port.
- wrongNetworkPrefix:
This value is only reported by 8260 agents
before v3.0 (8285 agents before v2.0).
In that case, wrongNetworkPrefix is returned
when
the switches on each end of a privateNetwork
link have incompatible network prefixes (the
12 first bytes have different values)
- wrongNodeNumber:
This value is only reported by 8260 agents
before v3.0 (8285 agents before v2.0).
In that case, wrongNodeNumber is returned
when
the switches on each end of an privateNetwork
link have the same ATM node Numbers.
- failing-line: the port is enabled and a invalid
signal is detected on the line
- disabled-failing: the port is disabled and an
anomaly is detected, either internal
or external.
- wrap-no-signal: the port is internally wrapped so that
all the traffic received on the attached line is
returned unchanged on the line.
No activity is detected at the physical
layer.
- wrap-idle: the port is internally wrapped so that
all the traffic received on the attached line is
returned unchanged on the line and
a valid signal is detected on the line.
- wrap-failing-internal: an internal failure has been
detected when the port has been
turned into the wrap-reply state.
The actual state of the port is
undefined.
- wrap-failing-line: the port is internally wrapped so that
all the traffic received on the attached
line is returned unchanged on the line
and an invalid signal is detected
on the line.
- idle-no-bandwidth: the port is enabled and activity
from the remote device is detected but
there is no enough bandwidth to operate
the port with its current configuration.
This state applies for privateNetwork.
- idle-internal-error: The port is enabled and activity
from the remote device is detected but
an internal error has occurred during
the checking of the port configuration.
- disabled-no-bandwidth:
This value is only reported by 8260 agents
before v3.0 (8285 agents before v2.0).
the enabling of the port is not
possible because
there is not enough bandwidth to operate
the port with its current configuration.
This state applies for privateNetwork.
- wrap-far-end-no-signal:
the port is in wrap-far-end
mode, ie the remote end of the line is
wrapped, and no signal is detected on the
line.
- wrap-far-end-idle:
the port is in wrap-far-end
mode, ie the remote end of the line is
wrapped, and a valid signal is detected
on the line.
- wrap-far-end-failing:
the port is in wrap-far-end
mode, ie the remote end of the line is
wrapped, and an internal error is detected.
- wrap-far-end-failing-line:
the port is in wrap-far-end
mode, ie the remote end of the line is
wrapped, and an invalid signal is detected
on the line.
- insufficient-connection-handles
For 8260 agents v3.0 (8285 v2.0) and higher.
The port is enabled and activity is
detected on the line but too many
connections are active on the module
and the control connections for this port
cannot be set.
- invalid-remote-vpi-vci-range
For 8260 agents v3.0 (8285 v2.0) and higher.
The port is enabled and activity is
detected on the line but the number of bits
for the vpi or the vci reported by the
attached device is not supported in the atm
subsystem.
- control-vpi-already-used
For 8260 agents v3.0 (8285 v2.0) and higher.
The port is enabled and activity is
detected on the line but the vpi value
assigned for the ilmi, signalling and
routing channels is already used by a
VP tunnel.
- missing-signalling-version:
For 8260 agents v3.0 (8285 v2.0) and higher.
The port is enabled and activity is
detected on the line but the ilmi is
disabled and the signalling version is set
to autoConfig.
When disabled, the port may be in only one of the following
states:
- unknown, disabled-failing, disabled-nosignal or
disabled-idle, disabled-no-bandwidth.
- unknown: the status of this port is unknown (this can
be the result of a module in error)
- disabled-nosignal: no activity is detected at the physical
layer while the port is disabled.
If the port is a SSI port, the
bandwidth configuration is valid.
- disabled-idle:: activity from the remote device
attached to this port has been
detected by the physical layer.
The port is disabled.
If the port is a SSI port, the bandwidth
configuration is valid.
- failing: an internal hard error has been detected on
this port while the port is enabled
- no signal: no activity is detected at the physical
layer while the port is enabled
- idle: activity from the remote device attached to this
port has been detected by the physical layer.
The port is enabled.
- in-service: the remote device successfully acknowledges
ILMI polling requests and SVC registration
- in-service-no-address-registration:
the remote device succesfully acknowledges
ILMI polling requests but it rejects the ATM
prefix registration. Only PVCs are supported.
- misConfigured:
This value is only reported by 8260 agents
before v3.0 (8285 agents before v2.0).
In that case, misConfigured is returned when
a privateNetwork port is attached to a
privateUni or to a publicUni port.
- wrongNetworkPrefix:
This value is only reported by 8260 agents
before v3.0 (8285 agents before v2.0).
In that case, wrongNetworkPrefix is returned
when
the switches on each end of a privateNetwork
link have incompatible network prefixes (the
12 first bytes have different values)
- wrongNodeNumber:
This value is only reported by 8260 agents
before v3.0 (8285 agents before v2.0).
In that case, wrongNodeNumber is returned
when
the switches on each end of an privateNetwork
link have the same ATM node Numbers.
- failing-line: the port is enabled and a invalid
signal is detected on the line
- disabled-failing: the port is disabled and an
anomaly is detected, either internal
or external.
- wrap-no-signal: the port is internally wrapped so that
all the traffic received on the attached line is
returned unchanged on the line.
No activity is detected at the physical
layer.
- wrap-idle: the port is internally wrapped so that
all the traffic received on the attached line is
returned unchanged on the line and
a valid signal is detected on the line.
- wrap-failing-internal: an internal failure has been
detected when the port has been
turned into the wrap-reply state.
The actual state of the port is
undefined.
- wrap-failing-line: the port is internally wrapped so that
all the traffic received on the attached
line is returned unchanged on the line
and an invalid signal is detected
on the line.
- idle-no-bandwidth: the port is enabled and activity
from the remote device is detected but
there is no enough bandwidth to operate
the port with its current configuration.
This state applies for privateNetwork.
- idle-internal-error: The port is enabled and activity
from the remote device is detected but
an internal error has occurred during
the checking of the port configuration.
- disabled-no-bandwidth:
This value is only reported by 8260 agents
before v3.0 (8285 agents before v2.0).
the enabling of the port is not
possible because
there is not enough bandwidth to operate
the port with its current configuration.
This state applies for privateNetwork.
- wrap-far-end-no-signal:
the port is in wrap-far-end
mode, ie the remote end of the line is
wrapped, and no signal is detected on the
line.
- wrap-far-end-idle:
the port is in wrap-far-end
mode, ie the remote end of the line is
wrapped, and a valid signal is detected
on the line.
- wrap-far-end-failing:
the port is in wrap-far-end
mode, ie the remote end of the line is
wrapped, and an internal error is detected.
- wrap-far-end-failing-line:
the port is in wrap-far-end
mode, ie the remote end of the line is
wrapped, and an invalid signal is detected
on the line.
- insufficient-connection-handles
For 8260 agents v3.0 (8285 v2.0) and higher.
The port is enabled and activity is
detected on the line but too many
connections are active on the module
and the control connections for this port
cannot be set.
- invalid-remote-vpi-vci-range
For 8260 agents v3.0 (8285 v2.0) and higher.
The port is enabled and activity is
detected on the line but the number of bits
for the vpi or the vci reported by the
attached device is not supported in the atm
subsystem.
- control-vpi-already-used
For 8260 agents v3.0 (8285 v2.0) and higher.
The port is enabled and activity is
detected on the line but the vpi value
assigned for the ilmi, signalling and
routing channels is already used by a
VP tunnel.
- missing-signalling-version:
For 8260 agents v3.0 (8285 v2.0) and higher.
The port is enabled and activity is
detected on the line but the ilmi is
disabled and the signalling version is set
to autoConfig.
When disabled, the port may be in only one of the following
states:
- unknown, disabled-failing, disabled-nosignal or
disabled-idle, disabled-no-bandwidth.
Sources for this description
MIBdepot
Parsed from atmmib21.mib.txt · ibm · ATM-SWITCHING-NODE-MIB
Source file: Download atmmib21.mib.txt
Source file: Download 65mibv412.mib.txt