From: Groupstudy (groupstudy@ipexpert.net)
Date: Mon Aug 09 2004 - 13:39:47 GMT-3
Richard,
The SP track is a whole new beast! Here's a portion of our SP WB content - Most of which is not necessarily seen or covered in the R&S track. - Wayne
MPLS TLVS (IS-IS)
MBGP Syntax
MBGP Address Families
MBGP Neighbor Activation
MBGP Route Reflectors
MBGP Route Maps
MBGP Graded Flap Dampening
MPLS
Tag Switching Interface Configuration
Tag Switching IP / MPLS IP
MPLS Label Protocol Configuration
Frame Mode MPLS
Tag Switching Neighbors
Tag Ranges
MPLS over ATM
EBGP for MPLS
RIP Version 2 for MPLS
OSPF for MPLS
Traffic Engineering
OSPF TE Extension
TE Interface Commands
TE Tunnel Priority
TE Bandwidth Using RSVP
TE Dynamic Path
TE Explicit Path
Anti-spoofing Techniques
Black hole routes as packet filters
CEF and ip unicast verify reverse-path
Core Dump
Using QOS tools for flood protection
VRF Configuration
VRF IGPs (RIP, OSPF, BGP)
Static VPN Routes
Token Bucket
Diff-Serv
BGP PE-CE routing
ATM CoS
ATM OAM
TDP Ranges
TDP ID
Cell Mode MPLS
Intranet VPN
VRF Using Global Routing Table
OSPF PE-CE Routing
Explicit Path
-----Original message-----
From: "Scott Morris" swm@emanon.com
Date: Mon, 9 Aug 2004 12:22:23 -0400
To: "'Richard Dumoulin'" richard.dumoulin@vanco.es
Subject: RE: SP track
> There is a bit more in the MPLS VPNs that isn't explored by the workbook
> (exam evolved, workbook didn't yet). There's extra stuff in the routing
> protocols dealing with the nuances of MPLS. There's different stuff in L2
> technologies (ATM in particular) dealing with this as well that all added
> together make things complicated...
>
> But the R&S is a good starting place for all this! :)
>
> HTH,
>
>
> Scott Morris, CCIE4 (R&S/ISP-Dial/Security/Service Provider) #4713, CISSP,
> JNCIP, et al.
> IPExpert CCIE Program Manager
> IPExpert Sr. Technical Instructor
> swm@emanon.com/smorris@ipexpert.net
> http://www.ipexpert.net <http://www.ipexpert.net/>
>
>
> _____
>
> From: Richard Dumoulin [mailto:richard.dumoulin@vanco.es]
> Sent: Monday, August 09, 2004 9:45 AM
> To: swm@emanon.com
> Cc: 'ccielab'
> Subject: SP track
>
>
>
> What are the main differences between R&S and SP apart the MPLS section ? I
> have had a look at IPExpert SP book and I have not found a significant
> difference. Maybe some topics are to be studied more deeply. What most
> attracts me from SP is that the material needed to practice is the same as
> R&S...
>
> Do you think that the R&S background is enough for going and practicing the
> workbook directly ?
>
> --Richard
>
> -----Original Message-----
> From: Scott Morris [mailto:swm@emanon.com]
> Sent: lunes, 09 de agosto de 2004 14:26
> To: Richard Dumoulin; 'Carlos G Mendioroz'
> Cc: 'ccielab'
> Subject: RE: what's the difference between DN and line of Cisco IP phone
>
>
> The whole "ephone" concept is unique to IOS-related implementations of SRST
> and CME. It exists noplace else.
>
> However, the concept of "DN" is around in all sorts of telephony areas and
> PBX implementations as Carlos has mentioned.
>
> There are many 'gray' areas when dealing with terms in the telephony side of
> things and how they get implemented in the world of soft switches. Data
> guys tend to blur the lines a bit and (in tradition) not document it! :)
>
> A DN or directory number is exactly that. Some phone number that is known
> to your phone switch (be it a hybrid key system, a pbx, a CCM or whatever).
> What you do with that phone number is a different story.
>
> Telephones have buttons. Buttons can be assigned features or line
> appearances. A line appearance is the termination of a DN to a physical
> phone device. You can also terminate DNs in non-physical things like ACD
> groups, IVR setups, remote call forwarding, phantom voice mail boxes, etc.
>
> So in very generic terms, a DN is a phone number while a line is the
> assigning of a phone number to a particular button on a telephone.
>
> Telephony is an exciting area to get into, but it can also be a very
> confusing one with all of the terminology and cross-use of terms (wait until
> you start talking CoS to a phone guy!). But that's what keeps life
> entertaining!
>
> HTH,
>
>
> Scott Morris, CCIE4 (R&S/ISP-Dial/Security/Service Provider) #4713, CISSP,
> JNCIP, et al. IPExpert CCIE Program Manager IPExpert Sr. Technical
> Instructor swm@emanon.com/smorris@ipexpert.net
>
> http://www.ipexpert.net
>
>
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
> Richard Dumoulin
> Sent: Sunday, August 08, 2004 7:32 PM
> To: Carlos G Mendioroz
> Cc: ccielab
> Subject: RE: what's the difference between DN and line of Cisco IP phone
>
> Good, but I don't see from your explanation the difference between ephone-dn
> in CME and CCM. All you have talked about can be applied to CME too. So
> what's the difference ?
>
> --Richard
>
> -----Original Message-----
> From: Carlos G Mendioroz [mailto:tron@huapi.ba.ar]
> Sent: lunes, 09 de agosto de 2004 0:20
> To: Richard Dumoulin
> Cc: Xue Fei; ccielab
> Subject: Re: what's the difference between DN and line of Cisco IP phone
>
>
> Richard,
> that terminology applies to CME (Call MAnager Express, i.e. the Call
> Manager that "runs" in IOS boxen).
>
> CCM is usually a reference to Cisco Call Manager, or the full blown Call
> Manager. Even though terms are simmilar, they are not the same all over
> the place.
>
> A DN (directory number) is just that. A number that is part of your
> dialplan, and that you can dial to reach some extension/phone. A line
> usually refers to the ability to carry one call at one time. So lines are
> mapped to phone buttons, and ... lots of fun stuff. But if
>
> you have two lines, you may have two calls at once (usually all but one
> holded)
> DNs are in turn mapped to lines. Usually on a 1-1 way, but not
> necesarilly. You can map many DNs to one line, or many lines to one DN.
>
>
> Richard Dumoulin wrote:
>
> > An ephone-dn is basically an extension number which provides a voice
> > channel to connect to the physical e-phone. When the ephone-dn command
> > is entered in the config, a dial-peer pots is created, and when under
> > this ephone-dn you enter "number XXX" a virtual FXS voice port is
> > created. This is how the extension number is associated to the
> > physical ethernet phone. For the line, I am not sure but it might
> > refer to the voice-channel mentioned above or the virtual FXS port.
> > Take into account that there are no physical phone lines as everything
> > is IP here,
> >
> > --Richard
> >
> > -----Original Message-----
> > From: Xue Fei [mailto:xuefei@bgctv.com.cn]
> > Sent: domingo, 08 de agosto de 2004 20:12
> > To: ccielab
> > Subject: OT: what's the difference between DN and line of Cisco IP
> > phone
> >
> >
> > Hi guys,
> >
> > I'm reading CCM document and would like make clear what the difference
> > between "DN(Directory Number)" and "line" of Cisco IP phone. I really
> > got confused with them but have no cisco Ip phone to practise.
> >
> > Thanks in advance!
> >
> > Xue Fei
> > xuefei@bgctv.com.cn
> > 2004-08-08
> >
> > ______________________________________________________________________
> > _
> > Please help support GroupStudy by purchasing your study materials
> > from: http://shop.groupstudy.com
> >
> > Subscription information may be found at:
> > http://www.groupstudy.com/list/CCIELab.html
> >
> >
> > **********************************************************************
> > Any opinions expressed in the email are those of the individual and
> > not necessarily the company. This email and any files transmitted with
> > it are confidential and solely for the use of the intended recipient.
> > If you are not the intended recipient or the person responsible for
> > delivering it to the intended recipient, be advised that you have
> > received this email in error and that any dissemination, distribution,
> > copying or use is strictly prohibited.
> >
> > If you have received this email in error, or if you are concerned with
> > the content of this email please e-mail to:
> > e-security.support@vanco.info
> >
> > The contents of an attachment to this e-mail may contain software
> > viruses which could damage your own computer system. While the sender has
> taken every reasonable precaution to minimise this risk, we cannot accept
> liability for any damage which you sustain as a result of software viruses.
> You should carry out your own virus checks before opening any attachments to
> this e-mail.
>
> > **********************************************************************
> >
> > ______________________________________________________________________
> > _
> > Please help support GroupStudy by purchasing your study materials
> > from: http://shop.groupstudy.com
> >
> > Subscription information may be found at:
> > http://www.groupstudy.com/list/CCIELab.html
> >
>
> --
> Carlos G Mendioroz <tron@huapi.ba.ar> LW7 EQI Argentina
>
> _______________________________________________________________________
> Please help support GroupStudy by purchasing your study materials from:
> http://shop.groupstudy.com
>
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
> _______________________________________________________________________
> Please help support GroupStudy by purchasing your study materials from:
> http://shop.groupstudy.com
>
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
> _______________________________________________________________________
> Please help support GroupStudy by purchasing your study materials from:
> http://shop.groupstudy.com
>
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Fri Sep 03 2004 - 07:02:35 GMT-3