[c-nsp] EoMPLS (6500/3750M) Network Validation/Question

[Tantsura, Jeff]

I think if the EoMPLS encapsulation will find place on 3750 you could
definitely use 7600 as a P router.

Jeff


With kind regards/ met vriendelijke groeten,
--------------------------------------------------------
Jeff Tantsura
CCIE #11416
Senior Consultant
Capgemini Nederland BV
Tel: +31(0)30 689 2866
Mob:+31(0)6 4588 6858
Fax: +31(0)30 689 6565
--------------------------------------------------------


-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net
[mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Anthony D
Cennami
Sent: Monday, August 23, 2004 5:36 PM
To: cisco-nsp at puck.nether.net
Subject: [c-nsp] EoMPLS (6500/3750M) Network Validation/Question

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

I am in the preliminary stages of setting up a small EoMPLS network, and
would like to solicit feedback from the community regarding the
equipment/topology, ideally from those who have or continue to deploy
similar applications.

The trans[it,port] portion of this network is very simple, and consists
of the following:

GE-->[6500/SUP720-PFC3A]-->OSM-OC48-->[6500/SUP720-PFC3A]-->GE

For simplicity, what I would like to be able to do is hang a couple of
3750 Metro's off each end of the 6500 (via GE/ES uplink on the 3750
side) to actually push/pop the EoMPLS stuff, and then forward it over
the 6500's.  (This would be from 3750 GE/ES to 6500 GBIC GE on the OSM
OC48)

The question lies here:  I have heard conflicting reports that the PFC3A
will not even be capable of routing this EoMPLS traffic.  While I know
the non-3BXL is not capable of acting as EoMPLS push/popping PE, my
understanding is that it should be capable of serving as a MPLS (P)
router.

Any comments would be appreciated.

Regards,

Anthony

- --
: Anthony D Cennami
: Managing Partner
: NeuPATH, LLC
: acennami at neupath.com
: [PGP KeyID] 0x51cdd6bd

CONFIDENTIALITY NOTICE:  The information contained herein, including
Message Body, Attachment(s) and Recipients, is confidential in nature
and intended only for the delivery to and Authorized Use by
aforementioned and included Recipients, Addressee(s), Entities and
Authorized Delivery Agents effecting the confidential dissemination of
the information contained herein to said parties.
If you are not an intended recipient of this communication please take
notice that any redistribution or copying of this message, or any data
or attachments included, is UNAUTHORIZED and may be unlawful.  If you
believe you received this communication in error please immediately
destroy all copies and/or reference related hereto and immediately
notify the sender.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (MingW32)
Comment: Using GnuPG with Netscape - http://enigmail.mozdev.org

iD8DBQFBKg787cvhxFHN1r0RAh+OAKCy2PwDqEEr8nlaCH8OAntvoAczsQCbBGUX
+5ZDczLyUkquV7XbV/+novE=
=OOlH
-----END PGP SIGNATURE-----


_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/


Our name has changed.  Please update your address book to the following format: "recipient at capgemini.com".

This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient,  you are not authorized to read, print, retain, copy, disseminate,  distribute, or use this message or any part thereof. If you receive this  message in error, please notify the sender immediately and delete all  copies of this message.