— Exhibit –
— Exhibit —
Refer to the Exhibit.
Referring to the VPLS network shown in the exhibit, you notice that only one of the two CE sites
configured under the VPLS instance forms a connection to the remote site. The other site remains
in a forwarding and learning mode.
How does PE1 determine which CE within the VPLS instance forms the connection to the remote
site?
A.
The site that first distributes the outgoing label to the remote site will form the connection.
B.
The site with a lower interface index value will form the connection.
C.
The site with a higher interface index value will form the connection.
D.
The site with the lowest site ID will form the connection.
Explanation:
http://kb.juniper.net/InfoCenter/index?page=content&id=KB25097#LM
0
0
LM — local site ID not minimum designated
so correct answer is =D
as site CE-B is even not yet configured on PE1 for VPLS, and CE-c is in LM state…..
0
0
LM — local site ID not minimum designated ; RM — remote site ID not minimum designated
The LM or RM state is typically found in multi-homing scenarios:
RM — The remote site identifier is not the minimum designated, i.e. it is not the lowest. There is another remote site connected to the same PE router which has a lower site identifier. The PE router cannot establish a pseduowire to this remote site and the associated remote site identifier cannot be used to distribute VPLS label blocks. However, this is not an error state. Traffic can continue to be forwarded to the PE router interface connected to this remote site when the remote site is in this state.
To correct this issue:
Confirm that only one site is configured for a routing instance. If multiple sites are added to the routing-instance, enable the multi-homing knob.
0
0