No Passport is Gigabit Ethernet.

Actually, Passport is all of those things.  Passport is a generic term that
Nortel renamed all of their switches/routers to.  The Passport 8600 for
instance, which is the only one I'm really familiar with as I don't do
ISP/carrier stuff (yet?), is a Gigabit Ethernet switch.  It is NOT at its
core ATM, nor FR.

You have to use a model number to be sure what "Passport" you are talking
about...

Fred Reimer - CCNA


Eclipsys Corporation, 200 Ashford Center North, Atlanta, GA 30338
Phone: 404-847-5177  Cell: 770-490-3071  Pager: 888-260-2050


NOTICE; This email contains confidential or proprietary information which
may be legally privileged. It is intended only for the named recipient(s).
If an addressing or transmission error has misdirected the email, please
notify the author by replying to this message. If you are not the named
recipient, you are not authorized to use, disclose, distribute, copy, print
or rely on this email, and should immediately delete it from your computer.


-----Original Message-----
From: Nakul Malik [mailto:[EMAIL PROTECTED] 
Sent: Saturday, July 26, 2003 10:23 AM
To: [EMAIL PROTECTED]
Subject: Re: RFC 2547 vs. RFC 2764 VPNs [7:73048]

passport at heart an ATM switch????????/

Passport is FR.

-Nakul



""annlee""  wrote in message
news:[EMAIL PROTECTED]
> John Neiberger wrote:
>
> > I'm just now digging deeper into current VPN technologies since I'm
> > researching Qwest's PRN service. I'm awaiting a definitive answer from
them
> > but it appears that their PRN service is 2764-based, which apparently
means
> > it does not use MPLS like 2547-based VPNs. I'm curious about the
> > implications of choosing one model over the other.
> >
> > I thought the market trend was toward MPLS-based VPNs but 2764 seems to
> > argue against that. What are the implications of choosing one model over
> the
> > other? Are there any major drawbacks to either one that the other
> > addresses?
> >
> > I'm also a little concerned about vendor choices. Nortel seems to be
> pushing
> > 2764, while Cisco and possibly Juniper are pushing 2547 and MPLS. Is
that
> > correct? If so, is that really that important to the customer?
> >
> > Forgive me if these questions seem pretty vague. I'm still learning
about
> > the technologies involved and I'm not very familiar with the specifics
and
> > the terminology.
> >
> > I'll put in a plug here for Howard's book _Building Service Provider
> > Networks_. Among a number of things it discusses some of these VPN
> > technologies and has been very helpful the last couple of days during my
> > research.
> >
> > John
> Also worth looking at is the hardware component: what will run on
> the hardware you've already got (if anything)? IF you already
> have most or all of the hardware pieces to implement Cisco's
> version, then Cisco's probably makes sense. IF you already have
> the requisite Nortel gear (Passports?), you're probably only
> looking at upgrading to a new PCR (software version).
>
> And there's the training and management aspect -- which suite do
> you know better? Where is the rest of your network going--will
> money spent learning Passport command line be transferable to
> other devices, offering a savings there? My guess is no, but it
> could be possible. Finally, what's the underlying architecture -- 
> Passport at its heart is an ATM switch, and Nortel's VPNs using
> virtual routers still looks an awful lot like IP over ATM, with
> all the overhead in play there. If it's Passport they're pitching
> at you, have a good look at the layer 2 technology on switch
> egress. What I saw was:
>
>   [data+(local IP hdr)+(carrier IP hdr)+layer2 formatting]
>
> as it went through the cloud. Potentially, that's a lot of
> overhead. If that's not a problem, fine.
>
> Annlee




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=73064&t=73048
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Reply via email to