11-15-2004 03:33 PM
Hi
This question is with regards to naming conventions. As a service provider I am launching a global FRoMPLS service in 6 different locations, where each location will have 2 ports on the same PE: one for data traffic for all customers located at that location, and another port for voice traffic. Next to each PE is a frame-relay switch which sends me the individual customer PVCs.
The questions is specifically about the command:
connect <connection name> .....
l2transport ... <VCID>
Can I resue the same VCID that is on Paris-London for another "voice" connection between Paris-Moscow? In other words, with Paris being a hub, I would like to use VCID=78 for both the connections named "pw_paris_london" and "pw_paris_moscow"? Remember that for "voice" traffic terminating at let's say Paris I have only 1 port on the PE (with a DLCI per customer).
If the answer to the above is no, then what is a smart way to assign those VC IDs globally? And why does Cisco allow me to assign it while configuring if I already have a "connection name"?
Thanks ...
Tarek
Solved! Go to Solution.
11-15-2004 08:35 PM
Tarek,
You can certainly reuse the same VCID between different pair of routers. The only limitation is not to reuse the VCID between the same pair of router. Doing so will indeed generate an error message as follow:
r4(config-fr-pw-switching)#mpls l2transport route 2.2.2.2 10
FR_PW: VC ID is already in used
Hope this helps,
11-15-2004 08:35 PM
Tarek,
You can certainly reuse the same VCID between different pair of routers. The only limitation is not to reuse the VCID between the same pair of router. Doing so will indeed generate an error message as follow:
r4(config-fr-pw-switching)#mpls l2transport route 2.2.2.2 10
FR_PW: VC ID is already in used
Hope this helps,
11-16-2004 01:00 PM
Hi
Yes this seems to help. Thanks a lot. I could've tried it myself but I didn't have access to lab equipment.
One follow-on question:
I am at a loss as to where to find good network design information. I feel that I'm the first one desgining a FRoMPLS service. I am sure there are others who faced prior design decisions and I don't want to fall in the same mistakes. Any pointers from you for good tutorials, design notes, etc, other than the CCO documentation (which is limited to the basics)?
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide