Description

This article addresses a known issue where VPLS SNMP can successfully perform an SNMP MIB walk when there are only 2 Provider Edge (PE) devices in a VPLS setup. However, when the VPLS configuration includes more than 2 PEs, SNMP MIB walk operations may fail.

Symptoms

1. Successful SNMP MIB Walk with 2 PEs:

When the VPLS configuration includes exactly 2 PEs, the SNMP MIB walk can be executed successfully.

Example commands and outputs:

labroot@e04-36> show snmp mib walk jnxVplsPwBindTable
jnxVplsPwBindConfigType.2.666 = 1
Request failed: OID not increasing: jnxVplsPwBindConfigType.2.666 >= jnxVplsPwBindConfigType.2.665


labroot@e04-36> show vpls connections |match "rmt up" 
    194.145.188.159(vpls-id 755) rmt Up    Oct 10 11:25:33 2023           1
               
labroot@e04-36> show snmp mib walk jnxVplsPwBindTable 
jnxVplsPwBindConfigType.2.665 = 1
jnxVplsPwBindType.2.665 = 1
jnxVplsPwBindRowStatus.2.665 = 1
jnxVplsPwBindStorageType.2.665 = 5
jnxVplsPwBindIndex.2.665 = 665

2. SNMP MIB Walk Failure with More Than 2 PEs:
When adding an additional PE to the VPLS configuration, the SNMP MIB walk fails, resulting in errors. 

Example commands and outputs:
labroot@e04-36# activate routing-instances vpls-VLAN755 protocols vpls neighbor 194.145.188.158 
labroot@e04-36# commit 
 
labroot@e04-36> show vpls connections |match "rmt up" 
    194.145.188.158(vpls-id 755) rmt Up    Oct 11 07:04:13 2023           1
    194.145.188.159(vpls-id 755) rmt Up    Oct 10 11:25:33 2023           1
 
labroot@e04-36> show snmp mib walk jnxVplsPwBindTable    
jnxVplsPwBindConfigType.2.666 = 1
Request failed: OID not increasing: jnxVplsPwBindConfigType.2.666 >= jnxVplsPwBindConfigType.2.665

Solution

This issue has been resolved via following PR:

https://prsearch.juniper.net/PR1767779

 

Modification History

2024-02-13 : Article Created