[c-nsp] mpls hub & spoke.

Thu Feb 7 11:37:03 EST 2008

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Oliver Boehmer (oboehmer) wrote:
> virendra rode // <> wrote on Wednesday, February 06, 2008 8:53 PM:
> 
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Hi,
>>
>> Is there a way to find out whether a CE router (non-mpls) connection
>> point between customer network and provider's PE router (mpls enabled)
>> is configured as a hub router vs spoke?
>>
>> Unfortunately 12.4-10c doesn't have MPLS ping / traceroute integrated
>> for me to correctly identified the path. 
> 
> it wouldn't help you as the CE doesn't run MPLS.
- ----------------
true enough but I was thinking of running it anyway since the CE
connects into provider's PE thinking it would present me different result.

> 
>> Traceroute doesn't give me a
>> whole lot of information to identify this.
> 
> well, if the MPLS core doesn't show in traceroute, a full-mesh VPN would
> show PE1 -- PE2 -- CE2, while, in a hub-VPN, you might see PE1 -- PE3 --
> CE3 -- PE3 -- PE2 -- CE2 (with CE3/PE3 being the hub). So you would see
> a difference here, but you (the SP customer) should know which VPN
> topology you asked to implement? ;-)
> 
> 	oli
- --------------------------
Agreed and that's exactly what we are trying to do is validate what our
provider is saying but from what we are seeing are different results in
terms of path being traversed.

<head scratching>.

regards,
/virendra

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHqzOupbZvCIJx1bcRAqnwAKDt5aW7Y2n71DZdPfFz2j6e2XvAugCfR+8U
WJhyAfNPzAmMVkn8sZtbVuQ=
=Pu9u
-----END PGP SIGNATURE-----