Contents
1 Event Description
The eVIP, Configuration Fault event is reported when Transport Management detects a faulty configuration. This occurs in the following situations:
- A faulty configuration is entered.
- Transport Management starts, or restarts, with a faulty configuration.
- An Abstract Load Balancer (ALB) or a Front-End Element (FEE) is activated with a faulty configuration.
Transport Management issues a stateless alarm (an event) when a faulty configuration is detected. All alarm listeners receive this event, even those who did not enter the faulty configuration, or are unaware that a reconfiguration attempt has occurred.
The configuration faults are divided into the following two types:
- Syntax faults, for example, a malformed IP address is used. This type of fault can be detected immediately when the configuration is entered.
- Semantic faults. The configuration is syntactically correct but cannot be processed by Transport Management. The fault is detected later when Transport Management is notified to read the new configuration.
|
Attribute Name |
Attribute Value |
|---|---|
|
Major Type |
193 |
|
Minor Type |
2129526884 |
|
Managed Object Class |
<Managed Object (MO) where the fault was detected> |
|
Managed Object Instance |
<Distinguished Name of the MO where the fault was detected> |
|
Event Type |
communicationsAlarm (2) |
|
Probable Cause |
x736UnspecifiedReason (418) |
|
Specific Problem |
eVIP, Configuration Fault |
|
Additional Text |
Fault in eVIP Configuration |
|
Perceived Severity |
critical (3) |
2 Handle eVIP, Configuration Fault
Steps
- Delete the MO where the fault was detected.
- Note:
- This is only necessary if it was a semantic fault.
- Recreate the MO with correct configuration.
- Activate the MO (ALB or FEE) if necessary.
- Is the problem solved?
- Note:
- If the problem is not solved, the alarm comes back when the MO is recreated.
Yes: Proceed with Step 7.
No: Continue with the next step.
- Perform data collection, refer to Data Collection Guideline.
- Consult the next level of maintenance support. Further actions are outside the scope of this document.
- Job is completed.
3 Configuration
Not Applicable.
4 Subscription
Not Applicable.