tmnxOesCfgBlocked
TIMETRA-OES-MIB ·
.1.3.6.1.4.1.6527.3.1.3.98.0.15
Object
notification
[CAUSE] This event tmnxOesCfgBlocked notification is generated when a
configuration being made in the OES is blocked.
[EFFECT] The configuration is not active in the OES.
[RECOVERY]
One possible reason for this configuration failure is if there is a card
present in the OES that is a supported card type but the router was not yet
aware of its presence. This condition should clear as soon as the router
becomes aware of the card. A second reason is when the supported card is
present and is misaligned with the configuration (e.g. card present in slot
3 and 4, yet configuration is oes-1/2 where the width of card is two slots).
This condition cannot be cleared automatically as the card has to be moved
to the correct slot (or the configuration has to be removed for card oes-1/3
via cli command ). A third reason is when there is an unsupported card type
in the OES that the router cannot manage. This condition cannot be cleared
automatically and the OES will need to be recommissioned to clear the
condition.
Note: services on cards not impacted by the unknown card type are not
affected.
Context
- MIB
- TIMETRA-OES-MIB
- OID
.1.3.6.1.4.1.6527.3.1.3.98.0.15- Type
- notification
- Status
- current
- Parent
- tmnxOesNotifications
- Siblings
- 15
Syntax
No syntax metadata recorded.
Values & Constraints
No enumerated values or constraints recorded.
Related Objects
Sibling Objects
| Object | Type | Syntax | OID |
|---|---|---|---|
| tmnxOesCtlCommsDown [CAUSE] The tmnxOesCtlCommsDown notification is generated when the
active CPM can't reach the OES master chassis.
[EFFECT] The OES can't be managed by the router.
… | notification | - | .1.3.6.1.4.1.6527.3.1.3.98.0.1 |
| tmnxOesNtpOutOfSync [CAUSE] The tmnxOesNtpOutOfSync notification is generated when NTP time
on the OES is not synchronized to the host router. The host router must
have NTP enabled and have recover… | notification | - | .1.3.6.1.4.1.6527.3.1.3.98.0.10 |
| tmnxOesNtpSync [CAUSE] The tmnxOesNtpSync notification is generated when NTP on the
OES is synchronized to the host router. The host router is serving
acceptable time toward the OES and the OE… | notification | - | .1.3.6.1.4.1.6527.3.1.3.98.0.11 |
| tmnxOesSwBelowMinRev [CAUSE] The tmnxOesSwBelowMinRev notification is generated when the
version of the running OES software image is below the minimum expected
version.
[EFFECT] The OES … | notification | - | .1.3.6.1.4.1.6527.3.1.3.98.0.12 |
| tmnxOesFirmwareCondition [CAUSE] The tmnxOesFirmwareCondition notification is generated when the
firmware on the card has a condition that needs to be notified to
network administrator. The value of tmn… | notification | - | .1.3.6.1.4.1.6527.3.1.3.98.0.13 |
| tmnxOesCfgFailNoMemory [CAUSE] The tmnxOesCfgFailNoMemory notification is generated when a
request to obtain dynamic memory to download a configuration to the
OES has failed.
[EFFECT] The… | notification | - | .1.3.6.1.4.1.6527.3.1.3.98.0.14 |
| tmnxOesSwUpgdCleanupFailed [CAUSE] This event tmnxOesSwUpgdCleanupFailed notification is
generated when the operation to clean-up a failed software upgrade
fails. The reason for the failure is specified … | notification | - | .1.3.6.1.4.1.6527.3.1.3.98.0.16 |
| tmnxOesCtlCommsUp [CAUSE] The tmnxOesCtlCommsUp notification is generated when the
active CPM can reach the OES master chassis.
[EFFECT] The OES can be managed by the router.
… | notification | - | .1.3.6.1.4.1.6527.3.1.3.98.0.2 |
| tmnxOesDbSyncFailure The active Equipment Controller is unable to synchronize its database
with the inactive Equipment Controller.
[CAUSE] The tmnxOesDbSyncFailure notification may be rai… | notification | - | .1.3.6.1.4.1.6527.3.1.3.98.0.3 |
| tmnxOesDbSyncFailureClear [CAUSE] The tmnxOesDbSyncFailureClear notification is generated when
the active Equipment Controller is able to synchronize its database
with the inactive Equipment Controller.
… | notification | - | .1.3.6.1.4.1.6527.3.1.3.98.0.4 |
| tmnxOesDbInvalid [CAUSE] The tmnxOesDbInvalid notification may be raised under the
following conditions:
1) During initial installation, if the OES is not properly
commissioned;
2) The … | notification | - | .1.3.6.1.4.1.6527.3.1.3.98.0.5 |
| tmnxOesDbInvalidClear [CAUSE] The tmnxOesDbInvalidClear notification is generated when the
active Equipment Controller previously under tmnxOesDbInvalid
condition now contains a valid database.
… | notification | - | .1.3.6.1.4.1.6527.3.1.3.98.0.6 |
| tmnxOesDbUnsync [CAUSE] The tmnxOesDbUnsync notification is generated when the active
and standby Equipment Controllers are not in sync.
[EFFECT] The OES does not have redundancy prot… | notification | - | .1.3.6.1.4.1.6527.3.1.3.98.0.7 |
| tmnxOesDbUnsyncClear [CAUSE] The tmnxOesDbUnsyncClear notification is generated when the
previously out of sync database is now synchronized between the
active and standby Equipment Controller cards.… | notification | - | .1.3.6.1.4.1.6527.3.1.3.98.0.8 |
| tmnxOesSwUpgdFailed [CAUSE] The tmnxOesSwUpgdFailed notification is generated when a
failure occurs in upgrading a component in the OES. This notification
is applicable at the NE (Network Element) … | notification | - | .1.3.6.1.4.1.6527.3.1.3.98.0.9 |
Notification Objects
| Object | Type | Syntax | OID |
|---|---|---|---|
| TIMETRA-CHASSIS-MIBtmnxHwClass The value of tmnxHwClass indicates the general hardware type of this
component. If no appropriate enumeration exists for this hardware
identify this hardware component then the … | column | TmnxHwClass | .1.3.6.1.4.1.6527.3.1.2.2.1.8.1.7 |