It wouldn't be a violation to share information about each topic. But it 
would be an awful lot of work. It's exactly what sites like 
www.certificationzone.com are doing. But note that each topic, for 
example,  OSPF, is one or more 25-page papers, 30 study questions and 
answers, and one or more lab scenarios. And that's what it takes to learn 
this stuff. (Actually certificationzone teaches you a bit more than you 
need to know, but even if they didn't, it would be lot of information.)

Priscilla

At 04:30 PM 6/28/01, Allen May wrote:
>Prepare to be blasted for NDA violations ;)
>
>----- Original Message -----
>From:
>To:
>Sent: Thursday, June 28, 2001 3:05 PM
>Subject: CCIE written blueprints. Lets pass this blueprint around tell
>[7:10310]
>
>
> > I was studying the Blueprints for the 350-001 CCIE written test and a =
> > thought popped into my head. If everyone who was trying to pass this =
> > exam would pull together and answer the Blueprint objectives it would =
> > really benefit everyone.=20
> >
> > I have answered a couple of the objectives. Lets pass this blueprint =
> > around tell we get all of the objectives answered.
> >
> > =20
> >   1.. Cisco Device Operation=20
> >     1.. Commands: show, debug Infrastructure: NVRAM, Flash, Memory & =
> > CPU, file system, config reg
> >     2.. Operations: file transfers, password recovery,=20
> >     3.. Simple Network Management Protocol (SNMP), accessing devices, =
> > security (passwords)=20
> >
> >   1.. General Networking Theory=20
> >     1.. OSI model: Layer comparisons, functions
> >     2.. General Routing Concepts: Split horizon, difference between =
> > switching and routing, summarization, Link State vs. Distance Vector, =
> > loops, tunneling
> >     3.. Protocol comparisons: Internet Protocol (IP) vs. Internetwork =
> > Packet Exchange (IPX), Transmission Control Protocol (TCP), User =
> > Datagram Protocol (UDP), etc.
> >     4.. Standards: 802.x, protocol limitations
> >     5.. Protocol Mechanics: Windowing/Acknowledgements (ACK), =
> > fragmentation, maximum transmission unit (MTU), handshaking, termination
> >
> >   1.. Bridging & LAN Switching=20
> >     1.. Transparent Bridging: IEEE/DEC spanning tree, translational, =
> > Configuration Bridging Protocol Data Unit (BPDU), Integrated Routed and =
> > Bridging (IRB), Concurrent Routing and Bridging (CRB), access lists
> >     2.. Source Route Bridging: Source-route translational bridging =
> > (SR/TLB), source-route transparent bridging (SRT), data-link switching =
> > (DLSw), remote source-route bridging (RSRB), access lists
> >     3.. LAN Switching: Trunking, VLAN Trunk Protocol (VTP), inter-switch
=
> > link (ISL), Virtual LANs (VLANS),
> >     4.. Fast Ether Channel (FEC) =
> >
http://www.cisco.com/warp/public/cc/techno/media/lan/ether/channel/tech/f=
> > etec_wp.htm
> >     5.. Cisco Discovery Protocol (CDP)
> >     6.. Cisco Group Management Protocol (CGMP) When the CGMP-capable =
> > router receives an IGMP control packet, it creates a CGMP packet that =
> > contains the request type (either join or leave), the multicast group =
> > address, and the Media Access Control (MAC) address of the host. The =
> > router sends the CGMP packet to a well-known address to which all =
> > Catalyst 5000 series switches listen. When a switch receives the CGMP =
> > packet, the supervisor engine module interprets the packet and modifies =
> > the forwarding table automatically CGMP requires Catalyst  5000 series =
> > software release  2.2 or later and a network connection from the =
> > Catalyst  5000 series switch to a router running CGMP. By default, CGMP =
> > is disabled, and no multicast routers are configured.  Before you enable
=
> > CGMP on a Catalyst  5000 series switch, you must disable IGMP snooping =
> > if it is enabled, by entering the set igmp disable command. If you try =
> > to enable CGMP without first disabling IGMP snooping, an error message =
> > is generated.
> >     7.. LANE: LAN Emulation Client (LEC) LAN emulation client (LEC)-End =
> > systems that support    LANE, such as network interface =
> > card(NIC)-connected workstations, LAN switches with ATM uplinks (for =
> > example, the Catalyst family of switches), and Cisco 7500, 7000, 4500, =
> > and 4000 series routers that support ATM attachment, all require the =
> > implementation of a LEC. The LEC emulates an interface to a legacy LAN =
> > to the higher-level protocols. It performs data forwarding, address =
> > resolution, and registration of MAC addresses with the LANE server and =
> > communicates with other LECs via ATM virtual channel connections (VCCs).
=
> >
> >     8.. LAN Emulation Server (LES) LAN emulation configuration server =
> > (LECS)-The LECS maintains a   database of ELANs and the ATM addresses of
=
> > the LESs that control the ELANs. It accepts queries from LECs and =
> > responds with the ATM address of the LES that serves the appropriate =
> > ELAN/VLAN. This database is defined and maintained by the network =
> > administrator.
> >     9.. Broadcast and Unknown  Server (BUS) Broadcast and unknown server
=
> > (BUS)-The BUS acts as a   central point for distributing broadcasts and =
> > multicasts. ATM is essentially a point-to-point technology without =
> > "any-to-any"or "broadcast" support. LANE solves this problem by =
> > centralizing the broadcast support in theBUS. Each LEC must set up a =
> > Multicast Send VCC to the BUS. The BUS then adds the LEC as a leaf to =
> > its point-to-multipoint VCC (known as the Multicast Forward VCC). The =
> > BUS also acts as a multicast server. LANE is defined on ATM adaptation =
> > layer 5 (AAL5), which specifies a simple trailer to be appended to a =
> > frame before it is broken into ATMcells. The problem is that there is no
=
> > way to differentiate between ATM cells from different senders when =
> > multiplexed on a virtual channel. It is assumed that cells received will
=
> > be in sequence, and whe the End of Message (EOM) cell arrives, you =
> > should just have to reassemble all of the cells that have already =
> > arrived. The BUS takes the sequence of cells on each Multicast Send VCC =
> > and reassembles them into frames. When a full frame is received, it is =
> > queued for sending to all of the LECs on the Multicast Forward VCC. This
=
> > way, all the cells from a particular data frame can be guaranteed to be =
> > sent in order and not interleaved with cells from any other data frames =
> > on the point-to-multipoint VCC.
> >     10.. LAN Emulation Configuration Server (LECS) LAN emulation server =
> > (LES)-The LES provides a  central control point for all LECs. LECs =
> > maintain a Control Direct VCC to the LES to forward registration and =
> > control information. The LES maintains a point-to-multipoint VCC, known =
> > as the Control Distribute VCC, to all LECs. The Control Distribute VDD =
> > is used only to forward control information. As new LECs join the ATM =
> > ELAN, each LEC is added as a leaf to the control distribute tree.
> > 12. Simple Server Replication Protocol (SSRP) =
> > http://www.cisco.com/warp/public/121/ssrpconfig.html
> >
> >
> >   1.. Internet Protocol (IP)=20
> >     1.. Addressing: Classless Interdomain Routing (CIDR), subnetting, =
> > Address Resolution Protocol (ARP), Network Address Translation (NAT), =
> > Hot Standby Router Protocol (HSRP)
> >     2.. Services: Domain Name System (DNS), Bootstrap Protocol (BOOTP), =
> > Dynamic Host Configuration Protocol (DHCP), Internet Control Message =
> > Protocol (ICMP)
> >     3.. Applications: Telnet, File Transfer Protocol (FTP), Trivial File
=
> > Transfer Protocol (TFTP)
> >     4.. Transport: IP fragmentation, sockets, ports=20
> >     5.. Access Lists=20
> >
> >   1.. IP Routing Protocols=20
> >     1.. Open Shortest Path First (OSPF):=20
> >                                                                i.      =
> > Design: areas, virtual links, stub, not so stubby areas (NSSA), area =
> > border router (ABR) / autonomous system boundary router (ASBR) =
> > redistributions, media dependencies, external vs. internal, =
> > summarization=20
> >
> >                                                               ii.      =
> > Operation: Designated Router (DR), Backup Designated Router (BDR), =
> > adjacencies, link-state advertisement (LSA) types, link-state database, =
> > shortest path first (SPF) algorithm, authentication=20
> >
> >     1.. Border Gateway Protocol (BGP):=20
> >                                                                i.      =
> > Design: Peer Groups, Route Reflectors, Confederations, Clusters, =
> > Attributes, Autonomous Systems (AS)=20
> >
> >                                                               ii.      =
> > Operation: Route Maps, Filters, Neighbors, decision algorithm, Interior =
> > Border Gateway Protocol (IBGP), Exterior Border Gateway Protocol
(EBGP)=20
> >
> >     1.. Enhanced Interior Gateway Routing Protocol (EIGRP): Metrics, =
> > mechanics, & design=20
> >     2.. Intermediate System to Intermediate System (IS-IS): Metrics, =
> > mechanics, & design=20
> >     3.. Routing Information Protocol
> >     (RIP) & RIP v2: : Metrics, mechanics, & design=20
> >     4.. Multicast: Design, Protocol Independent Multicast (PIM - both =
> > sparse and dense), Distance Vector Multicast Routing Protocol (DVMRP), =
> > Internet Group Management Protocol (IGMP)
> >     5.. Access lists: distribute lists, route maps, policy routing, =
> > redistribution, route tagging=20
> >
> >   1.. Desktop Protocols=20
> >     1.. Internetwork Packet Exchange (IPX): NetWare Link Services =
> > Protocol. (NLSP), IPX-RIP, IPX-Service Advertising Protocol (SAP), =
> > IPX-EIGRP, Sequenced Packet Exchange (SPX), Network Control Protocol =
> > (NCP), IPXWAN, IPX addressing, Get Nearest Server (GNS), Novell =
> > Directory Services (routing & mechanisms), access lists=20
> >     2.. AppleTalk: Routing Table Maintenance Protocol (RTMP), AppleTalk =
> > Update-Based Routing Protocol (AURP), Appletalk-EIGRP, Datagram Delivery
=
> > Protocol (DDP), Zone Information Protocol (ZIP), Name Binding Protocol =
> > (NBP), addressing (phase 1 & 2), access lists=20
> >     3.. DECnet/OSI: Addressing, access lists=20
> >     4.. Windows NT: NetBIOS, browsing, domain controller (e.g. WINS), =
> > access lists=20
> >
> >   1.. Performance Management=20
> >     1.. Traffic Management: Queuing, Weighted Fair Queuing (WFQ), =
> > Resource Reservation Protocol (RSVP), traffic shaping, load balancing=20
> >
> >   1.. WAN (addressing, signaling, framing)=20
> >     1.. ISDN: Link Access Procedure on the D channel (LAPD), Basic Rate =
> > Interface (BRI) / Primary Rate Interface (PRI) framing, signaling, =
> > mapping, dialer map, interface types, B/D channels, PPP Multilink=20
> >     2.. Frame relay: Local Management Interface (LMI), Data Link =
> > Connection Identifier (DLCI), Permanent Virtual Circuit (PVC), framing, =
> > traffic shaping, forward explicit congestion notification (FECN), =
> > backward explicit congestion notification (BECN), CIR, discard eligible =
> > (DE), mapping, compression=20
> >     3.. X.25: addressing, routing, Link Access Procedure Balanced =
> > (LAPB), error control/recovery, windowing, signaling, mapping, Switched =
> > Virtual Circuit (SVC) / Permanent Virtual Circuit (PVC), Protocol =
> > Translation=20
> >     4.. ATM: Switched Virtual Connection (SVC) / Permanent Virtual =
> > Connection (PVC), ATM Adaptation Layer (AAL), Service Specific =
> > Connection Oriented Protocol (SSCOP), User-Network Interface (UNI) / =
> > Network-Network Interface (NNI), Interim Local Management Interface =
> > (ILMI), Cell format, Quality of Service (QoS), RFC 1483 &1577, Private =
> > Network-Network Interface (PNNI), Interim-Interswitch Signaling Protocol
=
> > (IISP), mapping=20
> >     5.. Physical Layer: Synchronization, Synchronous Optical Network =
> > (SONET), T1, E1, encoding=20
> >     6.. Leased Line Protocols: High-Level Data Link Control (HDLC), =
> > Point to Point Protocol (PPP), async & modems, compression=20
> >     7.. Dial on Demand Routing (DDR): dial backup=20
> >
> >   1.. LAN=20
> >     1.. Datalink Layer: addressing, 802.2=20
> >     2.. Ethernet/Fast Ethernet/Gigabit Ethernet: encapsulation, carrier =
> > sense multiple access collision detect (CSMA/CD), topology, speed, =
> > controller errors, limitations, 802.3=20
> >     3.. Token Ring: token passing, beaconing, Active Monitor, ring =
> > insertion, soft & hard errors, encapsulation, topology, maximum =
> > transmission unit (MTU), speed, limitations=20
> >     4.. FDDI/CDDI: dual ring, encapsulation, class, redundancy, dual =
> > homing, medium (copper, fiber), claims, Station Management (SMT), =
> > limitations=20
> >
> >   1.. Security=20
> >     1.. Authentication, Authorization, and Accounting (AAA),=20
> >     2.. Terminal Access Controller Access Control System (TACACS)  =
> > RADIUS: general concepts, usage, comparisons=20
> >     3.. Firewalls: PIX, access lists, demilitarized zones (DMZ)=20
> >     4.. Encryption: public/private key, Data Encryption Standard (DES)=20
> >
> >   1.. Multiservice=20
> >     1.. Voice/Video:=20
> >     2.. H.323,
> >     3..  codecs,
> >     4..  Signaling System 7 (SS7),
> >     5..  Real-Time Transport Protocol (RTP),=20
> >     6.. RTP Control Protocol (RTCP),
> >     7..  Quality of Service (QoS)=20
> >     =20
> >      =20
> > =20
> >
> > [GroupStudy.com removed an attachment of type image/gif which had a name
>of
> > clip_image001.gif]
> >
> > [GroupStudy.com removed an attachment of type image/jpeg which had a name
>of
> > clip_image003.jpg]
________________________

Priscilla Oppenheimer
http://www.priscilla.com




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=10392&t=10392
--------------------------------------------------
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