No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

S12700 V200R013C00 Log Reference

This document provides the explanations, causes, and recommended actions of logs on the product.
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
L2V

L2V

L2V/5/BFD_FOR_PW_DOWN

Message

L2V/5/BFD_FOR_PW_DOWN:The status of BFD for PW turned DOWN. (VcId=[ULONG], VcType=[STRING], PeerAddress=[IPADDR])

Description

The status of BFD for PW became Down.

Parameters

Parameter Name Parameter Meaning
VcId Indicates the ID of the VC.
VcType Indicates the type of the VC.
PeerAddress Indicates the IP address of a peer.

Possible Causes

BFD detected that the link was not available and notified the L2VPN module that the link of the current PW was Down.

Procedure

  1. This log message is informational only, and no action is required.

L2V/5/BFD_FOR_PW_UP

Message

L2V/5/BFD_FOR_PW_UP:The status of BFD for PW turned UP. (VcId=[ULONG], VcType=[STRING], PeerAddress=[IPADDR])

Description

The status of BFD for PW became Up.

Parameters

Parameter Name Parameter Meaning
VcId Indicates the ID of the VC.
VcType Indicates the type of the VC.
PeerAddress Indicates the IP address of a peer.

Possible Causes

BFD detected that the link was available and notified the L2VPN module that the link of the current PW went Up.

Procedure

  1. This log message is informational only, and no action is required.

L2V/3/BGPRMTCEIDLOCIDSAME

Message

L2V/3/BGPRMTCEIDLOCIDSAME:Remote CE ID is the same with local CE ID. (CeId=[ULONG], Pe=[STRING], Rd=[STRING])

Description

The remote CE ID was the same as the local CE ID.

Parameters

Parameter Name Parameter Meaning
CeId Indicates the CE ID.
Pe Indicates the IP address of the remote PE.
Rd Indicates the remote Route Distinguisher (RD).

Possible Causes

The remote CE ID and the local CE ID were the same.

Procedure

  1. Change the ID of either the remote CE or the local CE.

L2V/5/BGPVC_DWN

Message

L2V/5/BGPVC_DWN:The status of the Kompella VC turned DOWN. (VcVpnName=[STRING], CeId=[ULONG], RemoteCeId=[ULONG], InterfaceName=[STRING], SecondaryVc=[STRING], Reason=[STRING])

Description

This log message explained why the Kompella VC went Down.

Parameters

Parameter Name Parameter Meaning
VcVpnName Indicates the name of the Virtual Private Network (VPN).
CeId Indicates the ID of the Customer Edge (CE).
RemoteCeId Indicates the ID of the remote CE.
InterfaceName Indicates the name of the interface.
SecondaryVc Indicates the secondary VC.
Reason Indicates the cause, including

1 Invalid reason type

2 VC was created

3 VC was deleted

4 LDP session was Down

5 LDP session was Up

6 Same LDP mapping was received with different label and MTU

7 Same LDP mapping was received with matching interface parameters

8 LDP mapping was received with mismatching interface parameters

9 LDP mapping was received with unpass Cbit check

10 LDP mapping was received with unpass PW loop check

11 New LDP mapping was received

12 New LDP mapping was received but remote Vc or local Vc is Down

13 LDP withdrawn message was received

14 LDP release message was received

15 LDP request message was received

16 LDP GR ended processing

17 RSVP message was received

18 Interface was Up

19 Interface was Down

20 Interface encapsulation changed

21 Refresh

22 Download again

23 Tunnel was Up

24 Tunnel was Down

25 VC state changed when New RLB was received

26 RLB was Deleted

27 VC was created or connected to another remote CE

28 Outgoing interface was unavailable

29 Outgoing interface was available

30 LDP notification message was forwarded

31 LDP notification message was not forwarded

32 PW was recreated

33 Download FTN & ILM for EthernetTrunk

34 AC OAM fault detection was disabled

35 Remote AC fault

36 Remote AC fault was resumed

37 Local AC fault

38 Local AC fault was resumed

39 Remote PSN fault

40 Remote PSN fault was resumed

41 Local PSN fault

42 Local PSN fault was resumed

43 Bfd for pw status changed toDown

44 Bfd for pw status changed to UP

45 Bfd for pw status changed to ADMIN DOWN

46 Bfd for pw was disabled

47 Manual set was enabled

48 Manual set was disabled

49 Delay timed out

50 Resume Timed Out

Possible Causes

The VC went Down.

Procedure

  1. Identify the cause of the VC status change.

L2V/5/BGPVC_P2W

Message

L2V/5/BGPVC_P2W:The status of the Kompella VC turned working from protecting. (VcVpnName=[STRING], CeId=[ULONG], RemoteCeId=[ULONG], InterfaceName=[STRING], PrimaryVcRemoteCeId=[ULONG], Reason=[STRING])

Description

This log message explained why the Kompella VC changed from a protection link to a working link.

Parameters

Parameter Name Parameter Meaning
VcVpnName Indicates the name of the Virtual Private Network (VPN).
CeId Indicates the ID of the Customer Edge (CE).
RemoteCeId Indicates the ID of the remote CE.
InterfaceName Indicates the name of the interface.

PrimaryVcRemoteCeId

Indicates the secondary VC.
Reason Indicates the cause, including

1 Invalid reason type

2 VC was created

3 VC was deleted

4 LDP session was Down

5 LDP session was Up

6 Same LDP mapping was received with different label and MTU

7 Same LDP mapping was received with matching interface parameters

8 LDP mapping was received with mismatching interface parameters

9 LDP mapping was received with unpass Cbit check

10 LDP mapping was received with unpass PW loop check

11 New LDP mapping was received

12 New LDP mapping was received but remote Vc or local Vc is Down

13 LDP withdrawn message was received

14 LDP release message was received

15 LDP request message was received

16 LDP GR ended processing

17 RSVP message was received

18 Interface was Up

19 Interface was Down

20 Interface encapsulation changed

21 Refresh

22 Download again

23 Tunnel was Up

24 Tunnel was Down

25 VC state changed when New RLB was received

26 RLB was Deleted

27 VC was created or connected to another remote CE

28 Outgoing interface was unavailable

29 Outgoing interface was available

30 LDP notification message was forwarded

31 LDP notification message was not forwarded

32 PW was recreated

33 Download FTN & ILM for EthernetTrunk

34 AC OAM fault detection was disabled

35 Remote AC fault

36 Remote AC fault was resumed

37 Local AC fault

38 Local AC fault was resumed

39 Remote PSN fault

40 Remote PSN fault was resumed

41 Local PSN fault

42 Local PSN fault was resumed

43 Bfd for pw status changed to Down

44 Bfd for pw status changed to UP

45 Bfd for pw status changed to ADMIN DOWN

46 Bfd for pw was disabled

47 Manual set was enabled

48 Manual set was disabled

49 Delay timed out

50 Resume Timed Out

Possible Causes

The VC changed from a protection link to a working link.

Procedure

  1. Identify the cause of the switchover between the primary VC and the secondary VC according to the recorded reason.

L2V/5/BGPVC_UP

Message

L2V/5/BGPVC_UP:The status of the Kompella VC turned UP. (VcVpnName=[STRING], CeId=[ULONG], RemoteCeId=[ULONG], InterfaceName=[STRING], SecondaryVc=[STRING], Reason=[STRING])

Description

This log message explained why the Kompella VC went Up.

Parameters

Parameter Name Parameter Meaning
VcVpnName Indicates the name of the Virtual Private Network (VPN).
CeId Indicates the ID of the Customer Edge (CE).
RemoteCeId Indicates the ID of the remote CE.
InterfaceName Indicates the name of the interface.
SecondaryVc Indicates the secondary VC.
Reason Indicates the cause, including

1 Invalid reason type

2 VC was created

3 VC was deleted

4 LDP session was Down

5 LDP session was Up

6 Same LDP mapping was received with different label and MTU

7 Same LDP mapping was received with matching interface parameters

8 LDP mapping was received with mismatching interface parameters

9 LDP mapping was received with unpass Cbit check

10 LDP mapping was received with unpass PW loop check

11 New LDP mapping was received

12 New LDP mapping was received but remote Vc or local Vc is Down

13 LDP withdrawn message was received

14 LDP release message was received

15 LDP request message was received

16 LDP GR ended processing

17 RSVP message was received

18 Interface was Up

19 Interface was Down

20 Interface encapsulation changed

21 Refresh

22 Download again

23 Tunnel was Up

24 Tunnel was Down

25 VC state changed when New RLB was received

26 RLB was Deleted

27 VC was created or connected to another remote CE

28 Outgoing interface was unavailable

29 Outgoing interface was available

30 LDP notification message was forwarded

31 LDP notification message was not forwarded

32 PW was recreated

33 Download FTN & ILM for EthernetTrunk

34 AC OAM fault detection was disabled

35 Remote AC fault

36 Remote AC fault was resumed

37 Local AC fault

38 Local AC fault was resumed

39 Remote PSN fault

40 Remote PSN fault was resumed

41 Local PSN fault

42 Local PSN fault was resumed

43 Bfd for pw status changed to Down

44 Bfd for pw status changed to UP

45 Bfd for pw status changed to ADMIN DOWN

46 Bfd for pw was disabled

47 Manual set was enabled

48 Manual set was disabled

49 Delay timed out

50 Resume Timed Out

Possible Causes

The VC went Up.

Procedure

  1. Identify the cause of the VC status change.

L2V/5/BGPVC_W2P

Message

L2V/5/BGPVC_W2P:The status of the Kompella VC turned protecting from working. (VcVpnName=[STRING], CeId=[ULONG], RemoteCeId=[ULONG], InterfaceName=[STRING], SecondaryVcRemoteCeId=[ULONG], Reason=[STRING])

Description

This log message explained why the Kompella VC changed from a working link to a protection link.

Parameters

Parameter Name Parameter Meaning
VcVpnName Indicates the name of the Virtual Private Network (VPN).
CeId Indicates the ID of the Customer Edge (CE).
RemoteCeId Indicates the ID of the remote CE.
InterfaceName Indicates the name of the interface.
SecondaryVcRemoteCeId Indicates the secondary VC.
Reason Indicates the cause, including

1 Invalid reason type

2 VC was created

3 VC was deleted

4 LDP session was Down

5 LDP session was Up

6 Same LDP mapping was received with different label and MTU

7 Same LDP mapping was received with matching interface parameters

8 LDP mapping was received with mismatching interface parameters

9 LDP mapping was received with unpass Cbit check

10 LDP mapping was received with unpass PW loop check

11 New LDP mapping was received

12 New LDP mapping was received but remote Vc or local Vc is Down

13 LDP withdrawn message was received

14 LDP release message was received

15 LDP request message was received

16 LDP GR ended processing

17 RSVP message was received

18 Interface was Up

19 Interface was Down

20 Interface encapsulation changed

21 Refresh

22 Download again

23 Tunnel was Up

24 Tunnel was Down

25 VC state changed when New RLB was received

26 RLB was Deleted

27 VC was created or connected to another remote CE

28 Outgoing interface was unavailable

29 Outgoing interface was available

30 LDP notification message was forwarded

31 LDP notification message was not forwarded

32 PW was recreated

33 Download FTN & ILM for EthernetTrunk

34 AC OAM fault detection was disabled

35 Remote AC fault

36 Remote AC fault was resumed

37 Local AC fault

38 Local AC fault was resumed

39 Remote PSN fault

40 Remote PSN fault was resumed

41 Local PSN fault

42 Local PSN fault was resumed

43 Bfd for pw status changed to Down

44 Bfd for pw status changed to UP

45 Bfd for pw status changed to ADMIN DOWN

46 Bfd for pw was disabled

47 Manual set was enabled

48 Manual set was disabled

49 Delay timed out

50 Resume Timed Out

Possible Causes

The VC changed from a working link to a protection link.

Procedure

  1. Identify the cause of the switchover between the primary VC and the secondary VC according to the recorded reason.

L2V/5/CCCVC_DOWN

Message

L2V/5/CCCVC_DOWN:The status of the CCC VC turned DOWN. (CccName=[STRING], InterfaceName=[STRING], Reason=[STRING])

Description

The CCC VC went Down.

Parameters

Parameter Name Parameter Meaning
CccName Indicates the name of the CCC.
InterfaceName Indicates the name of the interface.
Reason Indicates the cause:

1. Invalid reason type

2. VC was created

3. VC was deleted

4. LDP session was Down

5. LDP session was Up

6. Same LDP mapping was received with different label and MTU

7. Same LDP mapping was received with matching interface parameters

8. LDP mapping was received with mismatching interface parameters

9. LDP mapping was received with unpass Cbit check

10. LDP mapping was received with unpass PW loop check

11. New LDP mapping was received

12. New LDP mapping was received but remote Vc or local Vc is Down

13. LDP withdrawn message was received

14. LDP release message was received

15. LDP request message was received

16. LDP GR ended processing

17. RSVP message was received

18. Interface was Up

19. Interface was Down

20. Interface encapsulation changed

21. Refresh

22. Download again

23. Tunnel was Up

24. Tunnel was Down

25. VC state changed when New RLB was received

26. RLB was Deleted

27. VC was created or connected to another remote CE

28. Outgoing interface was unavailable

29. Outgoing interface was available

30. LDP notification message was forwarded

31. LDP notification message was not forwarded

32. PW was recreated

33. Download FTN & ILM for Eth-Trunk

34. AC OAM fault detection was disabled

35. Remote AC fault

36. Remote AC fault was resumed

37. Local AC fault

38. Local AC fault was resumed

39. Remote PSN fault

40. Remote PSN fault was resumed

41. Local PSN fault

42. Local PSN fault was resumed

43. BFD for PW status changed to Down

44. BFD for PW status changed to Up

45. BFD for PW status changed to ADMIN DOWN

46. BFD for PW was disabled

47. Manual set was enabled

48. Manual set was disabled

49. Delay timed out

50. Resume timed out

Possible Causes

The VC went Down.

Procedure

  1. Identify the cause of the VC status change.

L2V/5/CCCVC_UP

Message

L2V/5/CCCVC_UP:The status of the CCC VC turned UP. (CccName=[STRING], InterfaceName=[STRING], Reason=[STRING])

Description

The CCC VC went Up.

Parameters

Parameter Name Parameter Meaning
CccName Indicates the name of the CCC.
InterfaceName Indicates the name of the interface.
Reason Indicates the cause:

1. Invalid reason type

2. VC was created

3. VC was deleted

4. LDP session was Down

5. LDP session was Up

6. Same LDP mapping was received with different label and MTU

7. Same LDP mapping was received with matching interface parameters

8. LDP mapping was received with mismatching interface parameters

9. LDP mapping was received with unpass Cbit check

10. LDP mapping was received with unpass PW loop check

11. New LDP mapping was received

12. New LDP mapping was received but remote Vc or local Vc is Down

13. LDP withdrawn message was received

14. LDP release message was received

15. LDP request message was received

16. LDP GR ended processing

17. RSVP message was received

18. Interface was Up

19. Interface was Down

20. Interface encapsulation changed

21. Refresh

22. Download again

23. Tunnel was Up

24. Tunnel was Down

25. VC state changed when New RLB was received

26. RLB was Deleted

27. VC was created or connected to another remote CE

28. Outgoing interface was unavailable

29. Outgoing interface was available

30. LDP notification message was forwarded

31. LDP notification message was not forwarded

32. PW was recreated

33. Download FTN & ILM for Eth-Trunk

34. AC OAM fault detection was disabled

35. Remote AC fault

36. Remote AC fault was resumed

37. Local AC fault

38. Local AC fault was resumed

39. Remote PSN fault

40. Remote PSN fault was resumed

41. Local PSN fault

42. Local PSN fault was resumed

43. BFD for PW status changed to Down

44. BFD for PW status changed to Up

45. BFD for PW status changed to ADMIN DOWN

46. BFD for PW was disabled

47. Manual set was enabled

48. Manual set was disabled

49. Delay timed out

50. Resume timed out

Possible Causes

The VC went Up.

Procedure

  1. Identify the cause of the VC status change.

L2V/3/CEOUTOFRANGE

Message

L2V/3/CEOUTOFRANGE: The local CE cannot communicate with the remote CE because the CE ID exceeds the range. (Local: CeId=[ULONG], VpnRd=[STRING]; Remote: CeId=[ULONG], Pe=[STRING], VpnRd=[STRING])

Description

The local CE cannot communicate with the remote CE because the CE ID exceeds the range.

Parameters

Parameter Name Parameter Meaning
Local: Indicates the local device.
CeId Indicates the local CE ID.
VpnRd Indicates the local VPN Route Distinguisher (RD).
Remote: Indicates the remote device.
CeId Indicates the remote CE ID.
Pe Indicates the IP address of the remote PE.
VpnRd Indicates the remote VPN RD.

Possible Causes

When the Kompella VLL is configured, the ID of the local CE was beyond the range on the remote CE.

Procedure

  1. Change the ID of the local CE to be smaller one or extend the range on the remote CE.

L2V/3/CONFLICTCONN

Message

L2V/3/CONFLICTCONN:There are conflicting connections which have the same VC ID and VC type!

Description

The same VC ID and VC type led to connection conflict.

Parameters

Parameter Name Parameter Meaning
None None

Possible Causes

Conflicted connections with the same VC ID and VC type existed.

Procedure

  1. Check the configurations and ensure each connection is configured with a unique VC ID and VC type.

L2V/4/ISSU_CHK_FL

Message

L2V/4/ISSU_CHK_FL:ISSU Check failed. (Reason=[STRING])

Description

The ISSU check on the L2VPN module failed because of problems in compatibility, specifications, and configurations.

Parameters

Parameter Name Parameter Meaning
Reason

Indicates possible causes:

  • starting the ISSU check failed: indicates that the ISSU check cannot be performed.
  • compatibility failed: indicates that the compatibility check failed.
  • getting spec data failed: indicates that specification data cannot be obtained.
  • data did not contain specs: indicates that there were no specifications in the data.
  • specs were inconsistent: indicates that specifications in earlier and later versions were inconsistent.
  • config was greater than the new spec: indicates that the configured value was greater than the value specified in the new specification.
  • new spec did not exist: indicates that the new specification did not exist.

Possible Causes

After the ISSU check was performed to check the version, specifications, and configurations of the L2VPN module, lossless ISSU cannot be performed on the L2VPN module.

Procedure

  • Perform lossy ISSU on the L2VPN module.

L2V/3/LDP_MSG_ERR

Message

L2V/3/LDP_MSG_ERR:Received an error or unknown signal message. (MessageType=[STRING], PeerIpAddress=[STRING], ErrorReason=[STRING])

Description

Received an error or unknown signal message.

Parameters

Parameter Name Parameter Meaning
MessageType Indicates the type of message.
PeerIpAddress Indicates the remote ip address.
ErrorReason Indicates the reason of the error.

Possible Causes

The received L2VPN LDP signaling packets had an error or unknown field. The remote device might be a non-Huawei device.

Procedure

  1. Check whether the signaling packet sent from the remote device complies with the RFC.

L2V/3/OTHERCEIDSAME

Message

L2V/3/OTHERCEIDSAME:When inserting RLB into VPN, found the same remote CE ID RLB already existed. (CeId=[ULONG], Old Rlb: Pe=[STRING], Rd=[STRING]; New Rlb: Pe=[STRING], Rd=[STRING])

Description

An RLB with the same remote CE ID already existed when the RLB was inserted into VPN.

Parameters

Parameter Name Parameter Meaning
CeId Indicates the ID of the CE.
Old Rlb: Pe Indicates the IP address of the PE in the original RLB.
Rd Indicates the route distinguisher of the original label block.
New Rlb: Pe Indicates the IP address of the PE in the new RLB.
Rd Indicates the route distinguisher of the new label block.

Possible Causes

The local site ID was the same as the remote site ID.

Procedure

  1. Re-configure the two site IDs.

L2V/3/PAFLCSERR

Message

L2V/3/PAFLCSERR:PAF LCS inconsistency: avail value exceeded max! (Item=[STRING], AvailValue=[ULONG], MaxValue=[ULONG])

Description

The actual value exceeded the maximum value defined in the PAF license file.

Parameters

Parameter Name Parameter Meaning
Item

Name of the item

AvailValue

Default value in the PAF license

MaxValue

Maximum value supported by the system

Possible Causes

The value read from the PAF license exceeded the maximum value supported by the system.

Procedure

  1. Change the value in the PAF license to the maximum value supported by the system.

L2V/5/PWE3VC_BACKUP

Message

L2V/5/PWE3VC_BACKUP:The status of the PWE3 VC turned BACKUP. (VcId=[ULONG], VcType=[string], InterfaceName=[string], SecondaryPw=[string], Reason=[string], SysUpTime=[TIMETICK], PeerAddress=[IPADDR])

Description

The PWE3 VC turned to the backup state.

Parameters

Parameter Name Parameter Meaning
VcId Indicates the ID of the VC.
VcType Indicates the type of the VC.
InterfaceName Indicates the name of the interface.
SecondaryPw Indicates the secondary PW.
Reason Indicates the cause of VC status change:

The bound VRRP backup group entered the non-master state.

The bound VRRP backup group entered the backup state.

The interface board bound to the VRRP backup group was pulled out.

SysUpTime Indicates the startup time of the system.
PeerAddress Indicates the IP address of a peer.

Possible Causes

The cause of a VC status change can be one of the following: the bound VRRP backup group entered the non-master state; the bound VRRP backup group entered the backup state; the interface board bound to the VRRP backup group was pulled out.

Procedure

  1. This log message is informational only, and no action is required.

L2V/5/PWE3VC_DWN_ME

Message

L2V/5/PWE3VC_DWN_ME:The status of the PWE3 VC turned DOWN. (VcId=[ULONG], VcType=[STRING], InterfaceName=[STRING], SecondaryPw=[STRING], Reason=[STRING], SysUpTime=[TIMETICK], PeerAddress=[IPADDR])

Description

This log message explained why the PWE3 VC went Down.

Parameters

Parameter Name Parameter Meaning
VcId Indicates the VC ID.
VcType Indicates the VC type:

0. unsupport

2. atm aal5 adu

3. atm trans cell

4. vlan

5. ethernet

6. hdlc

7. ppp

8. cem

9. atm nto1 vcc

10. atm nto1 vpc

11. ip layer2

12. atm 1to1 vcc

13. atm 1to1 vpc

14. atm aal5 pdu

15. mpls

16. vpls

17. interworking

18. vlan if

19. unsuppprt

InterfaceName Indicates the interface name.
SecondaryPw Indicates the secondary PW.
Reason Indicates the cause:

1. Invalid reason type

2. VC was created

3. VC was deleted

4. LDP session was Down

5. LDP session was Up

6. Same LDP mapping was received with different label and MTU

7. Same LDP mapping was received with matching interface parameters

8. LDP mapping was received with mismatching interface parameters

9. LDP mapping was received with unpass Cbit check

10. LDP mapping was received with unpass PW loop check

11. New LDP mapping was received

12. New LDP mapping was received but remote Vc or local Vc is Down

13. LDP withdrawn message was received

14. LDP release message was received

15. LDP request message was received

16. LDP GR ended processing

17. RSVP message was received

18. Interface was Up

19. Interface was Down

20. Interface encapsulation changed

21. Refresh

22. Download again

23. Tunnel was Up

24. Tunnel was Down

25. VC state changed when New RLB was received

26. RLB was Deleted

27. VC was created or connected to another remote CE

28. Outgoing interface was unavailable

29. Outgoing interface was available

30. LDP notification message was forwarded

31. LDP notification message was not forwarded

32. PW was recreated

33. Download FTN & ILM for Eth-Trunk

34. AC OAM fault detection was disabled

35. Remote AC fault

36. Remote AC fault was resumed

37. Local AC fault

38. Local AC fault was resumed

39. Remote PSN fault

40. Remote PSN fault was resumed

41. Local PSN fault

42. Local PSN fault was resumed

43. BFD for PW status changed to Down

44. BFD for PW status changed to UP

45. BFD for PW status changed to ADMIN DOWN

46. BFD for PW was disabled

47. Manual set was enabled

48. Manual set was disabled

49. Delay timed out

50. Resume timed out

SysUpTime Indicates the Tick time for the system being Up.
PeerAddress Indicates the IP address of a peer.

Possible Causes

The VC went Down.

Procedure

  1. Identify the cause of the VC status change.

L2V/5/PWE3VC_P2W

Message

L2V/5/PWE3VC_P2W:The status of the PWE3 VC turned working from protecting. (VcId=[ULONG], VcType=[STRING], PrimaryPwId=[ULONG], Reason=[STRING])

Description

This log message explained why the PWE3 VC changed from a protection link to a working link.

Parameters

Parameter Name Parameter Meaning
VcId Indicates the VC ID.
VcType Indicates the VC type:

0. unsupport

2. atm aal5 adu

3. atm trans cell

4. vlan

5. ethernet

6. hdlc

7. ppp

8. cem

9. atm nto1 vcc

10. atm nto1 vpc

11. ip layer2

12. atm 1to1 vcc

13. atm 1to1 vpc

14. atm aal5 pdu

15. mpls

16. vpls

17. interworking

18. vlan if

19. unsuppprt

PrimaryPwId Indicates the VC ID of the primary PW.
Reason Indicates the cause:

1. Invalid reason type

2. VC was created

3. VC was deleted

4. LDP session was Down

5. LDP session was Up

6. Same LDP mapping was received with different label and MTU

7. Same LDP mapping was received with matching interface parameters

8. LDP mapping was received with mismatching interface parameters

9. LDP mapping was received with unpass Cbit check

10. LDP mapping was received with unpass PW loop check

11. New LDP mapping was received

12. New LDP mapping was received but remote Vc or local Vc is Down

13. LDP withdrawn message was received

14. LDP release message was received

15. LDP request message was received

16. LDP GR ended processing

17. RSVP message was received

18. Interface was Up

19. Interface was Down

20. Interface encapsulation changed

21. Refresh

22. Download again

23. Tunnel was Up

24. Tunnel was Down

25. VC state changed when New RLB was received

26. RLB was Deleted

27. VC was created or connected to another remote CE

28. Outgoing interface was unavailable

29. Outgoing interface was available

30. LDP notification message was forwarded

31. LDP notification message was not forwarded

32. PW was recreated

33. Download FTN & ILM for Eth-Trunk

34. AC OAM fault detection was disabled

35. Remote AC fault

36. Remote AC fault was resumed

37. Local AC fault

38. Local AC fault was resumed

39. Remote PSN fault

40. Remote PSN fault was resumed

41. Local PSN fault

42. Local PSN fault was resumed

43. BFD for PW status changed to Down

44. BFD for PW status changed to UP

45. BFD for PW status changed to ADMIN DOWN

46. BFD for PW was disabled

47. Manual set was enabled

48. Manual set was disabled

49. Delay timed out

50. Resume timed out

Possible Causes

The service was switched from the secondary PW to the primary PW.

Procedure

  1. Identify the cause of the VC status change.

L2V/5/PWE3VC_UP_ME

Message

L2V/5/PWE3VC_UP_ME:The status of the PWE3 VC turned UP. (VcId=[ULONG], VcType=[STRING], InterfaceName=[STRING], SecondaryPw=[STRING], Reason=[STRING], SysUpTime=[TIMETICK], PeerAddress=[IPADDR])

Description

The PWE3 VC goes Up.

Parameters

Parameter Name Parameter Meaning
VcId Indicates the VC ID.
VcType Indicates the type of a VC, which can be any of the following:

0. unsupport

2. atm aal5 adu

3. atm trans cell

4. vlan

5. ethernet

6. hdlc

7. ppp

8. cem

9. atm nto1 vcc

10. atm nto1 vpc

11. ip layer2

12. atm 1to1 vcc

13. atm 1to1 vpc

14. atm aal5 pdu

15. mpls

16. vpls

17. interworking

18. vlan if

19. unsuppport

InterfaceName Indicates the name of an interface.
SecondaryPw Indicates the secondary PW.
Reason Indicates the reason why the log is generated, which can be any of the following:

1 Invalid reason type

2 VC was created

3 VC was deleted

4 LDP session was Down

5 LDP session was Up

6 Same LDP mapping was received with different label and MTU

7 Same LDP mapping was received with matching interface parameters

8 LDP mapping was received with mismatching interface parameters

9 LDP mapping was received with unpass Cbit check

10 LDP mapping was received with unpass PW loop check

11 New LDP mapping was received

12 New LDP mapping was received but remote Vc or local Vc is Down

13 LDP withdrawn message was received

14 LDP release message was received

15 LDP request message was received

16 LDP GR ended processing

17 RSVP message was received

18 Interface was Up

19 Interface was Down

20 Interface encapsulation changed

21 Refresh

22 Download again

23 Tunnel was Up

24 Tunnel was Down

25 VC state changed when New RLB was received

26 RLB was Deleted

27 VC was created or connected to another remote CE

28 Outgoing interface was unavailable

29 Outgoing interface was available

30 LDP notification message was forwarded

31 LDP notification message was not forwarded

32 PW was recreated

33 Download FTN & ILM for EthernetTrunk

34 AC OAM fault detection was disabled

35 Remote AC fault

36 Remote AC fault was resumed

37 Local AC fault

38 Local AC fault was resumed

39 Remote PSN fault

40 Remote PSN fault was resumed

41 Local PSN fault

42 Local PSN fault was resumed

43 Bfd for pw status changed to Down

44 Bfd for pw status changed to UP

45 Bfd for pw status changed to ADMIN DOWN

46 Bfd for pw was disabled

47 Manual set was enabled

48 Manual set was disabled

49 Delay timed out

50 Resume Timed Out

SysUpTime Indicates the Tick time for the system being Up.
PeerAddress Indicates the IP address of a peer.

Possible Causes

The VC went Up.

Procedure

  1. Identify the reason for the VC status change.

L2V/5/PWE3VC_W2P

Message

L2V/5/PWE3VC_W2P:The status of the PWE3 VC turned protecting from working. (VcId=[ULONG], VcType=[STRING], SecondaryPwId=[ULONG], Reason=[STRING])

Description

This log message explained why the PWE3 VC changed from a working link to a protection link.

Parameters

Parameter Name Parameter Meaning
VcId Indicates the VC ID.
VcType Indicates the VC type:

0. unsupport

2. atm aal5 adu

3. atm trans cell

4. vlan

5. ethernet

6. hdlc

7. ppp

8. cem

9. atm nto1 vcc

10. atm nto1 vpc

11. ip layer2

12. atm 1to1 vcc

13. atm 1to1 vpc

14. atm aal5 pdu

15. mpls

16. vpls

17. interworking

18. vlan if

19. unsuppprt

SecondaryPwId Indicates the remote VC ID of the secondary PW.
Reason Indicates the cause:

1. Invalid reason type

2. VC was created

3. VC was deleted

4. LDP session was Down

5. LDP session was Up

6. Same LDP mapping was received with different label and MTU

7. Same LDP mapping was received with matching interface parameters

8. LDP mapping was received with mismatching interface parameters

9. LDP mapping was received with unpass Cbit check

10. LDP mapping was received with unpass PW loop check

11. New LDP mapping was received

12. New LDP mapping was received but remote Vc or local Vc is Down

13. LDP withdrawn message was received

14. LDP release message was received

15. LDP request message was received

16. LDP GR ended processing

17. RSVP message was received

18. Interface was Up

19. Interface was Down

20. Interface encapsulation changed

21. Refresh

22. Download again

23. Tunnel was Up

24. Tunnel was Down

25. VC state changed when New RLB was received

26. RLB was Deleted

27. VC was created or connected to another remote CE

28. Outgoing interface was unavailable

29. Outgoing interface was available

30. LDP notification message was forwarded

31. LDP notification message was not forwarded

32. PW was recreated

33. Download FTN & ILM for EthernetTrunk

34. AC OAM fault detection was disabled

35. Remote AC fault

36. Remote AC fault was resumed

37. Local AC fault

38. Local AC fault was resumed

39. Remote PSN fault

40. Remote PSN fault was resumed

41. Local PSN fault

42. Local PSN fault was resumed

43. BFD for PW status changed to Down

44. BFD for PW status changed to Up

45. BFD for PW status changed to ADMIN DOWN

46. BFD for PW was disabled

47. Manual set was enabled

48. Manual set was disabled

49. Delay timed out

50. Resume timed out

Possible Causes

Services were switched from the primary PW to the secondary PW.

Procedure

  1. Identify the cause of the VC status change.

L2V/3/PWLOOPDETECT

Message

L2V/3/PWLOOPDETECT:A PW loop is detected. (VcId=[ULONG], VcType=[STRING], LoopIpAddress=[STRING])

Description

A PW loop was detected.

Parameters

Parameter Name Parameter Meaning
VcId VC ID
VcType VC type
LoopIpAddress IP address that causes the loop

Possible Causes

PW links formed a loop.

Procedure

  1. Adjust the configuration on the device based on VcId, VcType, and LoopIpAddress to prevent loops.

L2V/5/SVC_DWN

Message

L2V/5/SVC_DWN:The status of the SVC turned DOWN. (InterfaceName=[STRING], Reason=[STRING], SvcId=[GAUGE], SVcType=[INTEGER], PeerAddress=[IPADDR])

Description

This log message explained why the Static Virtual Circuit (SVC) went Down.

Parameters

Parameter Name Parameter Meaning
InterfaceName Indicates the name of the interface.
Reason Indicates the cause, including

1 Invalid reason type

2 VC was created

3 VC was deleted

4 LDP session was Down

5 LDP session was Up

6 Same LDP mapping was received with different label and MTU

7 Same LDP mapping was received with matching interface parameters

8 LDP mapping was received with mismatching interface parameters

9 LDP mapping was received with unpass Cbit check

10 LDP mapping was received with unpass PW loop check

11 New LDP mapping was received

12 New LDP mapping was received but remote Vc or local Vc is Down

13 LDP withdrawn message was received

14 LDP release message was received

15 LDP request message was received

16 LDP GR ended processing

17 RSVP message was received

18 Interface was Up

19 Interface was Down

20 Interface encapsulation changed

21 Refresh

22 Download again

23 Tunnel was Up

24 Tunnel was Down

25 VC state changed when New RLB was received

26 RLB was Deleted

27 VC was created or connected to another remote CE

28 Outgoing interface was unavailable

29 Outgoing interface was available

30 LDP notification message was forwarded

31 LDP notification message was not forwarded

32 PW was recreated

33 Download FTN & ILM for EthernetTrunk

34 AC OAM fault detection was disabled

35 Remote AC fault

36 Remote AC fault was resumed

37 Local AC fault

38 Local AC fault was resumed

39 Remote PSN fault

40 Remote PSN fault was resumed

41 Local PSN fault

42 Local PSN fault was resumed

43 Bfd for pw status changed to Down

44 Bfd for pw status changed to UP

45 Bfd for pw status changed to ADMIN DOWN

46 Bfd for pw was disabled

47 Manual set was enabled

48 Manual set was disabled

49 Delay timed out

50 Resume Timed Out

SvcId

Indicates the ID of an SVC.

SVcType
Indicates the type of a VC, which can be any of the following:
  • 0 unsupport
  • 1 frame relay
  • 2 atm aal5 adu
  • 3 atm trans cell
  • 4 vlan
  • 5 ethernet
  • 6 hdlc
  • 7 ppp
  • 8 cem
  • 9 atm nto1 vcc
  • 10 atm nto1 vpc
  • 11 ip layer2
  • 12 atm 1to1 vcc
  • 13 atm 1to1 vpc
  • 14 atm aal5 pdu
  • 15 mpls
  • 16 vpls
  • 17 interworking
  • 18 vlan if
  • 19 unsuppprt
PeerAddress Indicates the IP address of a peer.

Possible Causes

The SVC went Down.

Procedure

  1. Identify the cause of the SVC status change.

L2V/5/SVC_UP

Message

L2V/5/SVC_UP:The status of the SVC turned UP. (InterfaceName=[STRING], Reason=[STRING], SvcId=[GAUGE], SVcType=[INTEGER], PeerAddress=[IPADDR])

Description

This log message explained why the SVC went Up.

Parameters

Parameter Name Parameter Meaning
InterfaceName Indicates the name of the interface.
Reason Indicates the cause, including

1 Invalid reason type

2 VC was created

3 VC was deleted

4 LDP session was Down

5 LDP session was Up

6 Same LDP mapping was received with different label and MTU

7 Same LDP mapping was received with matching interface parameters

8 LDP mapping was received with mismatching interface parameters

9 LDP mapping was received with unpass Cbit check

10 LDP mapping was received with unpass PW loop check

11 New LDP mapping was received

12 New LDP mapping was received but remote Vc or local Vc is Down

13 LDP withdrawn message was received

14 LDP release message was received

15 LDP request message was received

16 LDP GR ended processing

17 RSVP message was received

18 Interface was Up

19 Interface was Down

20 Interface encapsulation changed

21 Refresh

22 Download again

23 Tunnel was Up

24 Tunnel was Down

25 VC state changed when New RLB was received

26 RLB was Deleted

27 VC was created or connected to another remote CE

28 Outgoing interface was unavailable

29 Outgoing interface was available

30 LDP notification message was forwarded

31 LDP notification message was not forwarded

32 PW was recreated

33 Download FTN & ILM for EthernetTrunk

34 AC OAM fault detection was disabled

35 Remote AC fault

36 Remote AC fault was resumed

37 Local AC fault

38 Local AC fault was resumed

39 Remote PSN fault

40 Remote PSN fault was resumed

41 Local PSN fault

42 Local PSN fault was resumed

43 Bfd for pw status changed to Down

44 Bfd for pw status changed to UP

45 Bfd for pw status changed to ADMIN DOWN

46 Bfd for pw was disabled

47 Manual set was enabled

48 Manual set was disabled

49 Delay timed out

50 Resume Timed Out

SvcId

Indicates the ID of an SVC.

SVcType
Indicates the type of a VC, which can be any of the following:
  • 0 unsupport
  • 1 frame relay
  • 2 atm aal5 adu
  • 3 atm trans cell
  • 4 vlan
  • 5 ethernet
  • 6 hdlc
  • 7 ppp
  • 8 cem
  • 9 atm nto1 vcc
  • 10 atm nto1 vpc
  • 11 ip layer2
  • 12 atm 1to1 vcc
  • 13 atm 1to1 vpc
  • 14 atm aal5 pdu
  • 15 mpls
  • 16 vpls
  • 17 interworking
  • 18 vlan if
  • 19 unsuppprt
PeerAddress Indicates the IP address of a peer.

Possible Causes

The SVC went Up.

Procedure

  1. Identify the cause of the SVC status change.

L2V/5/VPLSVC_BACKUP

Message

L2V/5/VPLSVC_BACKUP:The status of the VPLS VC turned BACKUP. (VsiName=[string], RemoteIp=[IPADDR], PwId=[ULONG], Reason=[string], SysUpTime=[TIMETICK])

Description

The VPLS VC turned to the backup state.

Parameters

Parameter Name Parameter Meaning
VsiName Indicates the name of the VSI.
RemoteIp Indicates the IP address of the remote end.
PwId Indicates the ID of the PW.
Reason Indicates the cause of VC status change:
  • The bound VRRP turned to a non-master state, such as the backup state.
  • The interface board bound to VRRP was pulled out.
SysUpTime Indicates the startup time of the system.

Possible Causes

The bound VRRP turned to a non-master state, such as the backup state or the interface board bound to VRRP was pulled out.

Procedure

  1. This log message is informational only, and no action is required.

L2V/5/VPLSVC_DWN_ME

Message

L2V/5/VPLSVC_DWN_ME:The status of the VPLS VC turned DOWN. (VsiName=[STRING], RemoteIp=[IPADDR], PwId=[ULONG], Reason=[STRING], SysUpTime=[TIMETICK])

Description

This log message explained why the Virtual Private LAN Service (VPLS) VC interface went Down.

Parameters

Parameter Name Parameter Meaning
VsiName Indicates the name of the Virtual Switching Instance (VSI).
RemoteIp Indicates the IP address of the remote end.
PwId Indicates the ID of the pseudo wire (PW).
Reason Indicates the cause:

1. Invalid reason type

2. VC was created

3. VC was deleted

4. LDP session was Down

5. LDP session was Up

6. Same LDP mapping was received with different label and MTU

7. Same LDP mapping was received with matching interface parameters

8. LDP mapping was received with mismatching interface parameters

9. LDP mapping was received with unpass Cbit check

10. LDP mapping was received with unpass PW loop check

11. New LDP mapping was received

12. New LDP mapping was received but remote Vc or local Vc is Down

13. LDP withdrawn message was received

14. LDP release message was received

15. LDP request message was received

16. LDP GR ended processing

17. RSVP message was received

18. Interface was Up

19. Interface was Down

20. Interface encapsulation changed

21. Refresh

22. Download again

23. Tunnel was Up

24. Tunnel was Down

25. VC state changed when New RLB was received

26. RLB was Deleted

27. VC was created or connected to another remote CE

28. Outgoing interface was unavailable

29. Outgoing interface was available

30. LDP notification message was forwarded

31. LDP notification message was not forwarded

32. PW was recreated

33. Download FTN & ILM for Eth-Trunk

34. AC OAM fault detection was disabled

35. Remote AC fault

36. Remote AC fault was resumed

37. Local AC fault

38. Local AC fault was resumed

39. Remote PSN fault

40. Remote PSN fault was resumed

41. Local PSN fault

42. Local PSN fault was resumed

43. BFD for PW status changed to Down

44. BFD for PW status changed to Up

45. BFD for PW status changed to ADMIN DOWN

46. BFD for PW was disabled

47. Manual set was enabled

48. Manual set was disabled

49. Delay timed out

50. Resume timed out

SysUpTime Indicates the Tick time for the system being Up.

Possible Causes

The VC went Down.

Procedure

  1. Identify the cause of the VC status change.

L2V/5/VPLSVC_UP_ME

Message

L2V/5/VPLSVC_UP_ME:The status of the VPLS VC turned UP. (VsiName=[STRING], RemoteIp=[IPADDR], PwId=[ULONG], Reason=[STRING], SysUpTime=[TIMETICK])

Description

This log message explained why the VPLS VC interface went Up.

Parameters

Parameter Name Parameter Meaning
VsiName Indicates the name of the Virtual Switching Instance (VSI).
RemoteIp Indicates the IP address of the remote end.
PwId Indicates the ID of the pseudo wire (PW).
Reason Indicates the cause:

1. Invalid reason type

2. VC was created

3. VC was deleted

4. LDP session was Down

5. LDP session was Up

6. Same LDP mapping was received with different label and MTU

7. Same LDP mapping was received with matching interface parameters

8. LDP mapping was received with mismatching interface parameters

9. LDP mapping was received with unpass Cbit check

10. LDP mapping was received with unpass PW loop check

11. New LDP mapping was received

12. New LDP mapping was received but remote Vc or local Vc is Down

13. LDP withdrawn message was received

14. LDP release message was received

15. LDP request message was received

16. LDP GR ended processing

17. RSVP message was received

18. Interface was Up

19. Interface was Down

20. Interface encapsulation changed

21. Refresh

22. Download again

23. Tunnel was Up

24. Tunnel was Down

25. VC state changed when New RLB was received

26. RLB was Deleted

27. VC was created or connected to another remote CE

28. Outgoing interface was unavailable

29. Outgoing interface was available

30. LDP notification message was forwarded

31. LDP notification message was not forwarded

32. PW was recreated

33. Download FTN & ILM for Eth-Trunk

34. AC OAM fault detection was disabled

35. Remote AC fault

36. Remote AC fault was resumed

37. Local AC fault

38. Local AC fault was resumed

39. Remote PSN fault

40. Remote PSN fault was resumed

41. Local PSN fault

42. Local PSN fault was resumed

43. BFD for PW status changed to Down

44. BFD for PW status changed to Up

45. BFD for PW status changed to ADMIN DOWN

46. BFD for PW was disabled

47. Manual set was enabled

48. Manual set was disabled

49. Delay timed out

50. Resume timed out

SysUpTime Indicates the Tick time for the system being Up.

Possible Causes

The VC went Up.

Procedure

  1. Identify the cause of the VC status change.

L2V/5/VPLSVSI_DWN

Message

L2V/5/VPLSVSI_DWN:The status of the VPLS VSI turned DOWN. (VsiName=[STRING], Reason=[STRING])

Description

This log message explained why the VPLS VSI went Down.

Parameters

Parameter Name Parameter Meaning
VsiName Indicates the name of the VSI.
Reason Indicates the cause, including

1 Invalid reason type

2 VC was created

3 VC was deleted

4 LDP session was Down

5 LDP session was Up

6 Same LDP mapping was received with different label and MTU

7 Same LDP mapping was received with matching interface parameters

8 LDP mapping was received with mismatching interface parameters

9 LDP mapping was received with unpass Cbit check

10 LDP mapping was received with unpass PW loop check

11 New LDP mapping was received

12 New LDP mapping was received but remote Vc or local Vc is Down

13 LDP withdrawn message was received

14 LDP release message was received

15 LDP request message was received

16 LDP GR ended processing

17 RSVP message was received

18 Interface was Up

19 Interface was Down

20 Interface encapsulation changed

21 Refresh

22 Download again

23 Tunnel was Up

24 Tunnel was Down

25 VC state changed when New RLB was received

26 RLB was Deleted

27 VC was created or connected to another remote CE

28 Outgoing interface was unavailable

29 Outgoing interface was available

30 LDP notification message was forwarded

31 LDP notification message was not forwarded

32 PW was recreated

33 Download FTN & ILM for EthernetTrunk

34 AC OAM fault detection was disabled

35 Remote AC fault

36 Remote AC fault was resumed

37 Local AC fault

38 Local AC fault was resumed

39 Remote PSN fault

40 Remote PSN fault was resumed

41 Local PSN fault

42 Local PSN fault was resumed

43 Bfd for pw status changed to Down

44 Bfd for pw status changed to UP

45 Bfd for pw status changed to ADMIN DOWN

46 Bfd for pw was disabled

47 Manual set was enabled

48 Manual set was disabled

49 Delay timed out

50 Resume Timed Out

Possible Causes

The VSI went Down.

Procedure

  1. Identify the cause of the VC status change.

L2V/5/VPLSVSI_UP

Message

L2V/5/VPLSVSI_UP:The status of the VPLS VSI turned UP. (VsiName=[STRING], Reason=[STRING])

Description

This log message explained why the VPLS VSI went Up.

Parameters

Parameter Name Parameter Meaning
VsiName Indicates the name of the VSI.
Reason Indicates the cause, including

1 Invalid reason type

2 VC was created

3 VC was deleted

4 LDP session was Down

5 LDP session was Up

6 Same LDP mapping was received with different label and MTU

7 Same LDP mapping was received with matching interface parameters

8 LDP mapping was received with mismatching interface parameters

9 LDP mapping was received with unpass Cbit check

10 LDP mapping was received with unpass PW loop check

11 New LDP mapping was received

12 New LDP mapping was received but remote Vc or local Vc is Down

13 LDP withdrawn message was received

14 LDP release message was received

15 LDP request message was received

16 LDP GR ended processing

17 RSVP message was received

18 Interface was Up

19 Interface was Down

20 Interface encapsulation changed

21 Refresh

22 Download again

23 Tunnel was Up

24 Tunnel was Down

25 VC state changed when New RLB was received

26 RLB was Deleted

27 VC was created or connected to another remote CE

28 Outgoing interface was unavailable

29 Outgoing interface was available

30 LDP notification message was forwarded

31 LDP notification message was not forwarded

32 PW was recreated

33 Download FTN & ILM for EthernetTrunk

34 AC OAM fault detection was disabled

35 Remote AC fault

36 Remote AC fault was resumed

37 Local AC fault

38 Local AC fault was resumed

39 Remote PSN fault

40 Remote PSN fault was resumed

41 Local PSN fault

42 Local PSN fault was resumed

43 Bfd for pw status changed to Down

44 Bfd for pw status changed to UP

45 Bfd for pw status changed to ADMIN DOWN

46 Bfd for pw was disabled

47 Manual set was enabled

48 Manual set was disabled

49 Delay timed out

50 Resume Timed Out

Possible Causes

The VSI went Up.

Procedure

  1. Identify the cause of the VC status change.

L2V/5/VSICALINLBLERR

Message

L2V/5/VSICALINLBLERR:The remote site ID exceeded local label block range. (SiteId=[ULONG])

Description

The remote site ID exceeded the local label block range.

Parameters

Parameter Name Parameter Meaning
SiteId Indicates the ID of the remote site.

Possible Causes

The remote site ID exceeded the local label block range.

Procedure

  1. Enlarge the local label block range.

L2V/5/VSIMHMPREFSAME

Message

L2V/5/VSIMHMPREFSAME:In the CE dual-homing scenario, the multi-homing preference of the local PE is the same as that of the remote PE, and thus the connection may not be established. (VsiName=[STRING], Rlb: Preference=[ULONG], Pe=[STRING], Rd=[STRING])

Description

In the CE dual-homing scenario, the multi-homing preference of the local PE is the same as that of the remote PE, and thus the connection may not be established.

Parameters

Parameter Name Parameter Meaning
VsiName Indicates the name of VSI.
Rlb Indicates the remote label block.
Preference Indicates the preference of the RLB.
PE Indicates the IP address of the PE in the RLB.
Rd Indicates the route distinguisher of the RLB.

Possible Causes

In the CE dual-homing scenario of Kompella mode VPLS, the multi-homing preference of the local PE is the same as that of the remote PE.

Procedure

  1. Lower the multi-homing preference of one end.

L2V/5/VSIRMTLCLIDSAME

Message

L2V/5/VSIRMTLCLIDSAME:The remote site ID is the same as the local site ID, and the connection may not be established. (VsiName=[STRING], Rlb: SiteId=[ULONG], Pe=[STRING], Rd=[STRING])

Description

The remote site ID is the same as the local site ID, and the connection may not be established.

Parameters

Parameter Name Parameter Meaning
VsiName Indicates the name of VSI.
Rlb Indicates the remote label block.
SiteId Indicates the site ID of the RLB.
Pe Indicates the IP address of the PE in the RLB.
Rd Indicates the route distinguisher of the RLB.

Possible Causes

The site IDs on the two PEs connected through Komeplla VPLS were the same.

Procedure

  1. Change any one of the two site IDs.

L2V/5/VSISITEOUTOFRANGE

Message

L2V/5/VSISITEOUTOFRANGE:The local site cannot communicate with remote site because site ID exceeded the range. (Local: SiteId=[ULONG], VsiRd=[STRING]; Remote: SiteId=[ULONG], Pe=[STRING], VsiRd=[STRING])

Description

The local site cannot communicate with the remote site because the local site ID exceeds the range.

Parameters

Parameter Name Parameter Meaning
Local: SiteId Indicates the ID of the local site.
VsiRd Indicates the route distinguisher of the local VSI.
Remote: SiteId Indicates the ID of the remote site.
Pe Indicates the IP address of the remote PE.
VsiRd Indicates the route distinguisher of the remote VSI.

Possible Causes

The local site ID exceeded the remote ID range. Therefore, no remote label was allocated for the local site.

Procedure

  1. Modify the configuration to enlarge the ID range of the remote site or to decrease the local site ID.
Translation
Download
Updated: 2019-04-09

Document ID: EDOC1100065665

Views: 6243

Downloads: 15

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next