PCEP session state change. (PcepEntityIndex=[EntityIndex], PcepPeerAddrType=[AddrType], PcepPeerAddr=[PeerAddr], PcepSessInitiator=[SessionInitiator], PcepSessState=[SessionState], PcepSessStateLastChange=[StateChangeTime], Reason=[Reason])
The PCEP session status changed.
| Trap Attribute | Description |
|---|---|
Alarm or Event |
Alarm |
Trap Severity |
Critical |
Mnemonic Code |
pcePcepSessDown |
Trap OID |
1.3.6.1.2.1.227.0.2 |
MIB |
PCE-PCEP-MIB |
Alarm ID |
0x09de2000 |
Alarm Name |
pcePcepSessDown |
Alarm Type |
communicationsAlarm |
Raise or Clear |
Raise |
Match trap |
| Parameter | Description |
|---|---|
EntityIndex |
PCEP index |
AddrType |
Type of a peer PCEP IP address |
PeerAddr |
IP address of a peer PCEP device |
SessionInitiator |
Initial PCEP session status |
SessionState |
PCEP session status |
StateChangeTime |
Last changed PCEP session status |
Reason |
Cause for the alarm |
| VB OID | VB Name | VB Index |
|---|---|---|
1.3.6.1.2.1.227.1.3.1.3 |
pcePcepSessState |
pcePcepEntityIndex pcePcepPeerAddrType pcePcepPeerAddr pcePcepSessInitiator |
1.3.6.1.2.1.227.1.3.1.2 |
pcePcepSessStateLastChange |
pcePcepEntityIndex pcePcepPeerAddrType pcePcepPeerAddr pcePcepSessInitiator |
1. Run the display current-configuration command to check whether the source IP address configured on the PCE server is consistent with the IP address of the candidate server configured on the PCE client. - If yes, go to step 2. - If no, run the source-address command on the PCE server or the connect-server command on the forwarder to modify the configuration, so that the source IP address configured on the PCE server is consistent with the IP address of the candidate server configured on the PCC client. Then, check whether the fault is resolved. If the fault persists, proceed with the subsequent operations. 2. Run the display current-configuration command to check whether the keychain configuration on the PCE server is consistent with that on the PCE client, such as the authentication algorithm and Key-id. If the configuration is consistent, it is recommended that the key-string command be run to set a password to ensure that the keychain configuration is consistent at both ends. Then, check whether the fault is resolved. If the fault persists, proceed with the subsequent operations. 3. Run the display ip routing-table command on the forwarder to check whether the forwarder has received the routing from the server. - If yes, go to step 4. - If no, check whether the IS-IS configuration is consistent at both ends. Such configuration include the system ID, IS-IS level, and regional address. If the IS-IS configuration is inconsistent, modify the configuration by referring to section IS-IS Configuration, ensuring that the forwarder can receive the routing from the server. Then, check whether the fault is resolved. If the fault persists, go to step 4. 4. Check whether the physical connection between the PCE server and PCE client is normal. - If yes, go to step 5. - If no, disconnect and then reconnect the forwarder and controller, or replace the physical connection between the forwarder and controller for the link to be normal. Then, check whether the fault is resolved. If the fault persists, go to step 5. 5. Collect alarm information and configuration information, and then contact technical support personnel.
The same as Cause 1 Recovery Suggestion.
The same as Cause 1 Recovery Suggestion.
The same as Cause 1 Recovery Suggestion.
The same as Cause 1 Recovery Suggestion.
The same as Cause 1 Recovery Suggestion.
The same as Cause 1 Recovery Suggestion.
The same as Cause 1 Recovery Suggestion.
The same as Cause 1 Recovery Suggestion.
The same as Cause 1 Recovery Suggestion.
The same as Cause 1 Recovery Suggestion.
The same as Cause 1 Recovery Suggestion.
The same as Cause 1 Recovery Suggestion.
The same as Cause 1 Recovery Suggestion.