[c-nsp] 12000 & EoMPLS

[Nikos Leontsinis]

Thank you Oliver this is what I meant I cannot find any documentation 
For this specific platform in terms of the Ethernet over Mpls Service on the
cco

#-----Original Message-----
#From: Oliver Boehmer (oboehmer) [mailto:oboehmer at cisco.com]
#Sent: Wednesday, March 09, 2005 4:43 PM
#To: nikos at oteglobe.net
#Cc: cisco-nsp at puck.nether.net
#Subject: RE: [c-nsp] 12000 & EoMPLS
#
#Nikos Leontsinis <mailto:nikos at oteglobe.net> wrote on Wednesday, March
#09, 2005 3:07 PM:
#
#> Imagine 2 cisco 12000 directly connected via a STM4 interface, you
#> want on each end to connect a CE in such a way as to create an
#Ethernet
#> Pseudowire and carry Ethernet/802.3 Protocol Data Units over the MPLS
#network.
#> In this  scenario the 12000 is both a PE and P (using engine 3). Is
#that
#> possible or  you need to have other routers on the edge and have the
#12000 act as P
#> routers?
#
#No, this will work just fine. So you have
#
#CE1 -- GSR1 -- GSR2 -- CE2
#
#right? no problem w/ Engine3.
#
#	oli
#
#>
#>
#> #-----Original Message-----
#> #From: Oliver Boehmer (oboehmer) [mailto:oboehmer at cisco.com]
#> #Sent: Wednesday, March 09, 2005 3:28 PM
#> #To: nikos at oteglobe.net
#> #Cc: cisco-nsp at puck.nether.net
#> #Subject: RE: [c-nsp] 12000 & EoMPLS
#> #
#> #
#> #> Anyone knows if the 12000 series support PE & P FUNCTIONALITY (on
#> the #> same box) on the EoMPLS service?
#> #> As far as I know, in the 7600 services you cannot have a layer 2
#> #> connection between PEs with Ethernet over MPLS. In other words the
#> #> 7600 can only act as PE. Does the same hold for the 12000?
#> #
#> #Don't really understand your question. What do you want to achieve?
#> Can #you describe the topology in more detail?
#> #
#> #	oli
#> #
#> #--
#> #This message has been scanned for viruses and
#> #dangerous content by MailScanner, and is
#> #believed to be clean.
#>
#>
#>
#> --
#> This message has been scanned for viruses and
#> dangerous content by MailScanner, and is
#> believed to be clean.
#
#--
#This message has been scanned for viruses and
#dangerous content by MailScanner, and is
#believed to be clean.



-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.