Now that our lab is equipped with the bare minimum (3 switches) let's go ahead and start with the configuration *rubs hands*
Keep in mind that a lot of this is going to be revision from the CCNA so I won't be going in too much detail regarding the base config, regardless I'll document all the commands here and try to cover as much explanation as possible.
Following is what I plan to configure on our Cisco switches:
Step 1 - Base Configuration - Naming and Enhancements
(1) hostname
(2) banner motd
(3) enable password (not required)
(4) enable secret (definitely req)
(5) service password-encryption (Encrypts enable password)
(6) login and password on line Con0 and VTY ports
(7) logging-synchronous (Synchronous logging)
(8) no ip domain-lookup (No domain lookup for every incorrect sentence entred)
(9) no exec-timeout (Auto timeout disabled)
Configuration:
R1>enable
R1#configure terminal
R1(config)#hostname S1
S1(config)#enable password cisco-enable
S1(config)#enable secret cisco
S1(config)#service password-encryption
S1(config)#banner motd @
******************************************
S1 - UNAUTHORIZED ACCESS PROHIBITED
******************************************
@
S1(config)#line con 0
S1(config-line)#login
S1(config-line)#password cisco
S1(config-line)#logging synchronous
S1(config-line)#no exec-timeout
S1(config-line)#line vty 0 4
S1(config-line)#login
S1(config-line)#password cisco
S1(config-line)#logging synchronous
S1(config-line)#no exec-timeout
S1(config-line)#exit
S1(config)#no ip domain-lookup
S1(config)#^z
S1#copy running-config startup-config
S1#show running-config
[Copy all text starting from the words 'version' to 'end' and paste it in notepad. Make the necessary changes, i.e: replacing 'S1' with 'S2' in one file and 'S1' with 'S3' in the other notepad, to replicate the configuration onto the other two switches in our LAN. Paste it in global config mode. This makes it a hell-lot more faster as the base config always takes a long time and is highly repetitive. Once complete, copy the running-config to the NVRAM and we'll move onto the next step...
Saturday, January 16, 2010
BCMSN Lab - Building the BCMSN lab
Step 1 - Building the BCMSN lab in GNS3
Note that if you try connecting two switches in GNS3, you are instantly prompted with an error stating 'can't connect these devices'.
You are receiving this error because GNS3 cannot emulate a Cisco switch. *Gasp* *Horror* *Shock*! Heh, it's true. GNS3 uses the dynamips/dynagen engine as mentioned earlier and therefore the same functions won't work here. A workaround to this is to use an NM-16ESW network module in a 3640 router to emulate a switching environment.
Basically the NM-16ESW module is a Cisco EtherSwitch Module designed for Integrated Services Routers. So what exactly is an EtherSwitch model you ask ehy... ? Well "Cisco EtherSwitch modules for Cisco Integrated Services Routers offer branch office customers the option to integrate switching and routing in one platform. Combining robust Layer 3 flexible WAN routing with low-density line-rate Layer 2 switching, the EtherSwitch modules provide straightforward configuration, easy deployment and integrated management in a single platform." quotes the Cisco site. Sounds something awfully close to a layer 3 switch, except the latter is designed towards inter-vlan routing at wire speed (not WAN) . Also a Layer 3 switch is a switch with a router inside whereas this effectively adds an Etherswitch module to a router.
Anyhow, if you are interested in knowing more about the NM-16ESW module, please visit the following link: http://www.cisco.com/en/US/prod/collateral/routers/ps259/product_data_sheet09186a00801aca3e.html
Having said that let's now move on to step two which is knowing how exactly do we do this in our virtual lab?
Step 2 - Adding the NM-16 EtherSwitch Module to a Cisco router
-Let's add three c3600 routers that shall eventually be converted to a 'switch' for the purpose of setting up the BCMSN lab in GNS3.
Note you can use any router you want. The c3600 is designed for small-to-medium scale businesses and therefore is one that isn't too strong on the RAM.
-After adding them in GNS3, Right-click on the router and change the hostname from 'R1' to 'S1' in-order to differentiate the switches from the routers in your lab. Do the same for R2 and R3.
-Before connecting all the 3 'switches' using crossover links, right-click S1 and select 'configure', select the specific switch 'S1' on the left column and then choose the 'slots' tab to add the 'NM-16ESW' module to the 'slot0:' adapter. Click OK. You'll receive a prompt stating: You mist use manual mode when adding a link in NM-16ESW modules. Meaning, upon connecting to other switches/routers you want to manually choose the 0/0 interface as we added the module to the same slot. (Just to be on the safe side it's best to right-click the switch and do so using the 'manual' option whilst connecting links. It's possible that GNS3 recognises the aforementioned slot automatically, but that's a chance we don't wanna take).
-Repeat the same on S2 and S3 except that S2 will have NM-16ESW modules on two slots (one for getting connected to S1 and the other to connect to S3). I think each slot-number co-relates to it's interface, e.g: slot0 = f0/0, slot6 = f0/6.
-Now connect the three switches manually using the crossover cable (would have to be 'CAT 5' or 'CAT 5e' IRL) to the appropriate interface on each switch (i.e: fa0/0).
(Do not connect the 3rd switch back to the 1st switch as we don't want to mess around STP just yet, even though Cisco switches might be programmed to enable STP by default upon receiving a BPDU. I believe it is only the low-end Alcatel switches and so forth that do not have it on by default. Enterprise switching eqiuipment such as that like Cisco probably don't have that problem.)
-Right-click each switch and choose 'start'. Green light pops up on each switch confirming POST successful and connectivity established.
In the next chapter, we start the basic switching configuration, including configuring VLAN's and setting up VTP. A lot of it, if not all will be revision from CCNA.
Note that if you try connecting two switches in GNS3, you are instantly prompted with an error stating 'can't connect these devices'.
You are receiving this error because GNS3 cannot emulate a Cisco switch. *Gasp* *Horror* *Shock*! Heh, it's true. GNS3 uses the dynamips/dynagen engine as mentioned earlier and therefore the same functions won't work here. A workaround to this is to use an NM-16ESW network module in a 3640 router to emulate a switching environment.
Basically the NM-16ESW module is a Cisco EtherSwitch Module designed for Integrated Services Routers. So what exactly is an EtherSwitch model you ask ehy... ? Well "Cisco EtherSwitch modules for Cisco Integrated Services Routers offer branch office customers the option to integrate switching and routing in one platform. Combining robust Layer 3 flexible WAN routing with low-density line-rate Layer 2 switching, the EtherSwitch modules provide straightforward configuration, easy deployment and integrated management in a single platform." quotes the Cisco site. Sounds something awfully close to a layer 3 switch, except the latter is designed towards inter-vlan routing at wire speed (not WAN) . Also a Layer 3 switch is a switch with a router inside whereas this effectively adds an Etherswitch module to a router.
Anyhow, if you are interested in knowing more about the NM-16ESW module, please visit the following link: http://www.cisco.com/en/US/prod/collateral/routers/ps259/product_data_sheet09186a00801aca3e.html
Having said that let's now move on to step two which is knowing how exactly do we do this in our virtual lab?
Step 2 - Adding the NM-16 EtherSwitch Module to a Cisco router
-Let's add three c3600 routers that shall eventually be converted to a 'switch' for the purpose of setting up the BCMSN lab in GNS3.
Note you can use any router you want. The c3600 is designed for small-to-medium scale businesses and therefore is one that isn't too strong on the RAM.
-After adding them in GNS3, Right-click on the router and change the hostname from 'R1' to 'S1' in-order to differentiate the switches from the routers in your lab. Do the same for R2 and R3.
-Before connecting all the 3 'switches' using crossover links, right-click S1 and select 'configure', select the specific switch 'S1' on the left column and then choose the 'slots' tab to add the 'NM-16ESW' module to the 'slot0:' adapter. Click OK. You'll receive a prompt stating: You mist use manual mode when adding a link in NM-16ESW modules. Meaning, upon connecting to other switches/routers you want to manually choose the 0/0 interface as we added the module to the same slot. (Just to be on the safe side it's best to right-click the switch and do so using the 'manual' option whilst connecting links. It's possible that GNS3 recognises the aforementioned slot automatically, but that's a chance we don't wanna take).
-Repeat the same on S2 and S3 except that S2 will have NM-16ESW modules on two slots (one for getting connected to S1 and the other to connect to S3). I think each slot-number co-relates to it's interface, e.g: slot0 = f0/0, slot6 = f0/6.
-Now connect the three switches manually using the crossover cable (would have to be 'CAT 5' or 'CAT 5e' IRL) to the appropriate interface on each switch (i.e: fa0/0).
(Do not connect the 3rd switch back to the 1st switch as we don't want to mess around STP just yet, even though Cisco switches might be programmed to enable STP by default upon receiving a BPDU. I believe it is only the low-end Alcatel switches and so forth that do not have it on by default. Enterprise switching eqiuipment such as that like Cisco probably don't have that problem.)
-Right-click each switch and choose 'start'. Green light pops up on each switch confirming POST successful and connectivity established.
In the next chapter, we start the basic switching configuration, including configuring VLAN's and setting up VTP. A lot of it, if not all will be revision from CCNA.
Onto teh basics
Step 1 - Creating a new Lab.
- Launch GNS3
- Hit File -> New project
Give a name to the project file and save it in a folder. Tick the two options 'Save NVRAM and other disk files' and 'Export router configuration files'. As you progress and make changes to the simulation. Click File -> Save to keep updating the changes. I learnt this the hard way. The first time I used GNS, I created this massive WAN topology with all kinds of routing. Different OSPF areas, (area 0, stubby, nssa, etc) eigrp routes, I had BGP routes, even route redistribution taking place. I saved the file through the menu option [File-> Save As -> Filename) and would periodically keep saving thing the file by hitting the 'save' option. After a week or so I shut the application (as I had to turn off my pc) and launched it the next day only to come upon the painful realisation that it wouldn't open and that 'save method' apparently wasn't the way it worked! There was a flaw in that particular version of GNS3 (0.5) where I had to create the project first and then save it.
I vividly remember expressing my sheer frustration to the developers of GNS3 at the time because so much was lost. I told them how bad their documentation was considering there was absolutely no mention of this. The result of hours of work had gone into nothingness. I later came to know that they fixed it in the next version and as you'll notice now in the current version (0.7 at the time of writing) that whenever you launch GNS3 you will prompted with the 'New Project' box. This is that particular one.
Step 2 - Enhancing GNS3
Now we need a console manager to of-course use the IOS on our switches and routers. Initially when GNS3 came out, the documentation for it was so piss poor, guys like me had to literally try out all options to figure out how it all worked. Luckily, now with it getting more popular and everything it's a lot more easily available (thanks to documentation such as this... heh.. jokes. Just makin' my self feel better in-case this goes nowhere.)
- Download the latest version of TeraTerm from http://en.sourceforge.jp/projects/ttssh2/ (Latest version at the time of writing = Tera Term Pro 2.3)
- Do a full installation in your home drive. Eg: C:\Program Files (x86)\15 - Cisco\teraterm
- In GNS3, click on 'Edit' under the menu bar and choose 'Preferences'. The 'General' window shows up where you notice the option for 'Terminal command:' underneath which lies the path to the putty exe file. Replace the default path to the putty.exe with 'C:\Program Files (x86)\15 - Cisco\teraterm\ttermpro.exe' (using above example) keeping the '-telnet %h %p' after it as it is.
- Press 'OK' or 'apply' for the changes to take effect.
This replaces putty with the much better performing, sleeker looking Terra Term.
Step 3 - Tweaking the Terra Term GUI; MATRIX Style. [Optional]
- To illustrate this with an example, we'll need to add two routers or two switches, basically any device requiring the use of Tera Term to telnet across. Add them into the GNS3 simulation and connect them with the appropriate links (i.e: crossover cable if they're both same and straight-through if they're different. Should be knowing that else I'd suggest pulling that ICND 1 book from the shelf and going back to revising the CCENT)
-In this example I have chosen two routers. Right click on the router/s/switch/es, choose 'start'. This turns the router on. The green light depicts the POST process to be successful and the router successfully establishing layer 1 connectivity. Right click again on a router and choose 'Console'. This opens up Tera Term.
- Click 'Setup' -> 'Window'. Here we want the normal text to be green in color and URL-text to be white in color, both on a black background. To do this, choose the 'Background' option and click 'Reverse'. This inverts the current default font/background color selection and makes the latter black.
- Click back on the 'Text' bullet and move the 'R' and 'B' bars to 0, to the extreme left to make the text green in color as it currently is set for the URL option. Now, choose 'URL' for the 'Attribute' option and make the background color black by moving all 3 bars to ‘0’ and text color white by moving the 'R' and 'G' bars to the extreme right to a value of ‘255’ and moving 'B' to a value of ‘240’. This sets the URL-text to a font color of white, which was by default set as the font color for normal text.
- Press 'OK' for the changes to take effect.
- Click ‘Setup’ -> ‘Save Setup’ and save by overwriting the existing TERATERM .ini file located in the installation folder.
Now we're all set to go. This establishes the base-ground work needed to set your lab up. From here you can start building your project on. Since I've already given my BSCI exam, in the next chapter we'll start off the basic switching configuration and adding VLAN's, configuring trunk links, establishing VTP, etc. Basically a good revision of the CCNA (v5).
Depending on how this 'Blog project' of mine works out and whether it does help keep me updated with my skills or enhance them through further gain in troubleshooting techniques, or help any other CCNA's out there, I will then decide if it's best to continue a similar trend for the BSCI.
Till then, I hope this helps any Cisco candidates that are studying for their certification out there, or anyone else interested in its technology.
- Launch GNS3
- Hit File -> New project
Give a name to the project file and save it in a folder. Tick the two options 'Save NVRAM and other disk files' and 'Export router configuration files'. As you progress and make changes to the simulation. Click File -> Save to keep updating the changes. I learnt this the hard way. The first time I used GNS, I created this massive WAN topology with all kinds of routing. Different OSPF areas, (area 0, stubby, nssa, etc) eigrp routes, I had BGP routes, even route redistribution taking place. I saved the file through the menu option [File-> Save As -> Filename) and would periodically keep saving thing the file by hitting the 'save' option. After a week or so I shut the application (as I had to turn off my pc) and launched it the next day only to come upon the painful realisation that it wouldn't open and that 'save method' apparently wasn't the way it worked! There was a flaw in that particular version of GNS3 (0.5) where I had to create the project first and then save it.
I vividly remember expressing my sheer frustration to the developers of GNS3 at the time because so much was lost. I told them how bad their documentation was considering there was absolutely no mention of this. The result of hours of work had gone into nothingness. I later came to know that they fixed it in the next version and as you'll notice now in the current version (0.7 at the time of writing) that whenever you launch GNS3 you will prompted with the 'New Project' box. This is that particular one.
Step 2 - Enhancing GNS3
Now we need a console manager to of-course use the IOS on our switches and routers. Initially when GNS3 came out, the documentation for it was so piss poor, guys like me had to literally try out all options to figure out how it all worked. Luckily, now with it getting more popular and everything it's a lot more easily available (thanks to documentation such as this... heh.. jokes. Just makin' my self feel better in-case this goes nowhere.)
- Download the latest version of TeraTerm from http://en.sourceforge.jp/projects/ttssh2/ (Latest version at the time of writing = Tera Term Pro 2.3)
- Do a full installation in your home drive. Eg: C:\Program Files (x86)\15 - Cisco\teraterm
- In GNS3, click on 'Edit' under the menu bar and choose 'Preferences'. The 'General' window shows up where you notice the option for 'Terminal command:' underneath which lies the path to the putty exe file. Replace the default path to the putty.exe with 'C:\Program Files (x86)\15 - Cisco\teraterm\ttermpro.exe' (using above example) keeping the '-telnet %h %p' after it as it is.
- Press 'OK' or 'apply' for the changes to take effect.
This replaces putty with the much better performing, sleeker looking Terra Term.
Step 3 - Tweaking the Terra Term GUI; MATRIX Style. [Optional]
- To illustrate this with an example, we'll need to add two routers or two switches, basically any device requiring the use of Tera Term to telnet across. Add them into the GNS3 simulation and connect them with the appropriate links (i.e: crossover cable if they're both same and straight-through if they're different. Should be knowing that else I'd suggest pulling that ICND 1 book from the shelf and going back to revising the CCENT)
-In this example I have chosen two routers. Right click on the router/s/switch/es, choose 'start'. This turns the router on. The green light depicts the POST process to be successful and the router successfully establishing layer 1 connectivity. Right click again on a router and choose 'Console'. This opens up Tera Term.
- Click 'Setup' -> 'Window'. Here we want the normal text to be green in color and URL-text to be white in color, both on a black background. To do this, choose the 'Background' option and click 'Reverse'. This inverts the current default font/background color selection and makes the latter black.
- Click back on the 'Text' bullet and move the 'R' and 'B' bars to 0, to the extreme left to make the text green in color as it currently is set for the URL option. Now, choose 'URL' for the 'Attribute' option and make the background color black by moving all 3 bars to ‘0’ and text color white by moving the 'R' and 'G' bars to the extreme right to a value of ‘255’ and moving 'B' to a value of ‘240’. This sets the URL-text to a font color of white, which was by default set as the font color for normal text.
- Press 'OK' for the changes to take effect.
- Click ‘Setup’ -> ‘Save Setup’ and save by overwriting the existing TERATERM .ini file located in the installation folder.
Now we're all set to go. This establishes the base-ground work needed to set your lab up. From here you can start building your project on. Since I've already given my BSCI exam, in the next chapter we'll start off the basic switching configuration and adding VLAN's, configuring trunk links, establishing VTP, etc. Basically a good revision of the CCNA (v5).Depending on how this 'Blog project' of mine works out and whether it does help keep me updated with my skills or enhance them through further gain in troubleshooting techniques, or help any other CCNA's out there, I will then decide if it's best to continue a similar trend for the BSCI.
Till then, I hope this helps any Cisco candidates that are studying for their certification out there, or anyone else interested in its technology.
Getting started via GNS 3
I gave my CCNP - BSCI exam (in October 2009) way before I created this blog. I also finished studying most of the BCMSN curriculum for the exam so I realise I have really covered a lot before I had this random *idea* of creating a blog.
Anyway, so I've decided that even though this might take a bit longer than expected (building labs, covering practical and theoretical concepts again for BCMSN) it will be sort of a good revision for me and thus worth it. I originally intended to sit for the BCMSN at the end of this month but now it's likely that it'll be prolonged by quite a bit... well, unless I really start to get good at my time management skills... heh either way, I definitely am time-bound here as the BCMSN is only available till 31st July 2010! (I think) so I have to sit the exam well before that else it's alternative would be to give new exam '642-813 Switch' (which is something I don't really wanna risk doing). I think that's the case anyway, after-all it's always better to be safe than sorry.
So... onto the basics.
Firstly, for building virtual labs, there's no better software than GNS3 for CCNP. Trust me, I tried packet tracer for so many simulations in BSCI and you can just forget about it. It's *HORRIBLE*. Kiss PT goodbye as you give your CCNA (if you successfully pass of-course). With CCNP come the big guns and that means you will also need the Cisco IOS (meaning it is 'assumed' you have a Cisco router/switch at home), most IOS versions are supported on GNS3 so really GNS3 serves to be perfectly ideal when it comes to building virtual-labs.
A bit about the software. It stands for 'Graphical Network Simulator', it's constantly under development and you are likely to download an RC version most of the time. It's free and can be downloaded from its official site located at http://www.gns3.net/download It uses the dynamips engine which is what the old-skool CCNP candidates had to rely on using before this good ole' software came in place (consider yourself lucky, that shi.. is horrible). There's also a forum there for troubleshooting where you can discuss *stuff* on the DB. Anyway enough about the software, that's all you need to know about it anyway.
- Download the GNS3 all-in-one package (includes Dynamips, Qemuwrapper, Pemu and WinPCAP v. X.X.X)
- Install the program/s.
- Launch GNS3. You'll be prompted with two options. One asking you to confirm the link to Dynamips and second prompting you to load the IOS. Choose the 1st one, click on the Dynamips tab, default options are usually correct especially if you installed the all-in-one package like I told you to and installed the whole pack in the same dir. Press Ok.
- Choose the second option now of adding one or more IOS images. Add all the ones you got from your 'Cisco equipment' and hit 'Save' to close the box and 'OK' to the prompt.
Now that we have downloaded and installed GNS3, in the next post I'll talk about some of its basic features that you need to know in-order to start setting up your CCNP virtual-lab.
Anyway, so I've decided that even though this might take a bit longer than expected (building labs, covering practical and theoretical concepts again for BCMSN) it will be sort of a good revision for me and thus worth it. I originally intended to sit for the BCMSN at the end of this month but now it's likely that it'll be prolonged by quite a bit... well, unless I really start to get good at my time management skills... heh either way, I definitely am time-bound here as the BCMSN is only available till 31st July 2010! (I think) so I have to sit the exam well before that else it's alternative would be to give new exam '642-813 Switch' (which is something I don't really wanna risk doing). I think that's the case anyway, after-all it's always better to be safe than sorry.
So... onto the basics.
Firstly, for building virtual labs, there's no better software than GNS3 for CCNP. Trust me, I tried packet tracer for so many simulations in BSCI and you can just forget about it. It's *HORRIBLE*. Kiss PT goodbye as you give your CCNA (if you successfully pass of-course). With CCNP come the big guns and that means you will also need the Cisco IOS (meaning it is 'assumed' you have a Cisco router/switch at home), most IOS versions are supported on GNS3 so really GNS3 serves to be perfectly ideal when it comes to building virtual-labs.
A bit about the software. It stands for 'Graphical Network Simulator', it's constantly under development and you are likely to download an RC version most of the time. It's free and can be downloaded from its official site located at http://www.gns3.net/download It uses the dynamips engine which is what the old-skool CCNP candidates had to rely on using before this good ole' software came in place (consider yourself lucky, that shi.. is horrible). There's also a forum there for troubleshooting where you can discuss *stuff* on the DB. Anyway enough about the software, that's all you need to know about it anyway.
- Download the GNS3 all-in-one package (includes Dynamips, Qemuwrapper, Pemu and WinPCAP v. X.X.X)
- Install the program/s.
- Launch GNS3. You'll be prompted with two options. One asking you to confirm the link to Dynamips and second prompting you to load the IOS. Choose the 1st one, click on the Dynamips tab, default options are usually correct especially if you installed the all-in-one package like I told you to and installed the whole pack in the same dir. Press Ok.
- Choose the second option now of adding one or more IOS images. Add all the ones you got from your 'Cisco equipment' and hit 'Save' to close the box and 'OK' to the prompt.
Now that we have downloaded and installed GNS3, in the next post I'll talk about some of its basic features that you need to know in-order to start setting up your CCNP virtual-lab.
Wednesday, January 13, 2010
Revised CCNP Certification
Right I was. BSCI + BCMSN + TSHOOT is there. Should be sweet...
http://ciscocert.custhelp.com/app/answers/detail/a_id/5793/related/1/session/L2F2LzEvc2lkL19fbHd6RVJq
Good thing I grabbed all the screenshots off the Cisco Learning Network Community. As of today, 22nd Jan, all info regarding the new CCNP curriculum has been removed from there.
Guess, this should really help those who missed reading it...
(1) Counting previous exams for Certification
(2) Changes to CCNP certification
(3)Changes to CCNP curriculum
(4) Valid period for previous CCNP exams
(5) CCNP TSHOOT beta exam
(6) Routing requirements for CCNP certification
(7) Switching requirements for CCNP certification
(8) Recommended order for CCNP exams
(9) Valid period for previous CCNP exams
(10) Who should take the ISCW and ONT exams?
I've uploaded the 10 most relevant of those screenshots. Those pretty much explain everything you need to know about the new CCNPv6 curriculum.
http://ciscocert.custhelp.com/app/answers/detail/a_id/5793/related/1/session/L2F2LzEvc2lkL19fbHd6RVJq
Good thing I grabbed all the screenshots off the Cisco Learning Network Community. As of today, 22nd Jan, all info regarding the new CCNP curriculum has been removed from there.
Guess, this should really help those who missed reading it...
(1) Counting previous exams for Certification
(2) Changes to CCNP certification
(3)Changes to CCNP curriculum
(4) Valid period for previous CCNP exams
(5) CCNP TSHOOT beta exam
(6) Routing requirements for CCNP certification
(7) Switching requirements for CCNP certification
(8) Recommended order for CCNP exams
(9) Valid period for previous CCNP exams
(10) Who should take the ISCW and ONT exams?
I've uploaded the 10 most relevant of those screenshots. Those pretty much explain everything you need to know about the new CCNPv6 curriculum.
Wednesday, January 6, 2010
New 2010 CCNP Curriculum.
https://learningnetwork.cisco.com/thread/8498?tstart=0
Seems like the current CCNP certification curriculum (CCNPv5) is getting updated to CCNPv6.
Apparently, the new version involves passing 3 exams as opposed to the current version that involves passing the following 4 papers (in the recommended order):
1. BSCI (Routing),
2. BCMSN (Switching),
3. ISCW (Security & Wireless) &
4. ONT (QoS & Voice).
New curriculum:
1. 642-902 ROUTE
2. 642-813 SWITCH
3. 642-832 TSHOOT
According to the following source: http://content.ll-0.com/cisco_netacademy/CCNP-FAQ-23Sep09.pdf?i=100109125824
•642-901 BSCI: replaced by •642-902 ROUTE
•642-812 BCMSN: replaced by •642-813 SWITCH
No exam replaces •642-832 TSHOOT
•642-825 ISCW: no replacement
•642-845 ONT: no replacement
•642-892 Composite (BSCI + BCMSN): no replacement
This is good. I never really saw the need for ONT and ISCW to be included in the CCNP curriculum. Security is pretty well covered as it is and a lot of those concepts from ISCW and ONT are overly repeated in the SP and VP tracks, which is where most of these concepts apply anyway.
Looks like the official announcement from Cisco is to be made at the end of this month. I suspect those who gave the ONT and ISCW exams before the BSCI and BCMSN will be given time until June 2011 to sit the latter two and complete their certification. Those who've given the BSCI and BCMSN should likely have the choice to sit the 'TShoot' and get their certification or give ONT/ISCW (should they have started study on that) by March 2011 and get the same.
Going by Cisco's track record they always leave parallel tracks for a while before removing the old curriculum, meaning one can choose whichever path they feel more confident at. If someone already gave the BSCI and BCMSN, with the availability of the new curriculum exams they could write either ONT + ISCW or Troubleshoot to complete their CCNP. It's usually how Cisco handles certification changes.
Anyhow, best to have it through an official announcement.
Sources:
Official statement from Cisco - https://learningnetwork.cisco.com/thread/8498?tstart=0
CCNP v6.0 - http://content.ll-0.com/cisco_netacademy/CCNP-FAQ-23Sep09.pdf?i=100109125824
Opening Post/Intro
What should I say about myself?
I'm a graduate of computer science with a keen interest in networking/security. I started my quest in IT in early 2005 and have ever since actively pursued it in the hope of turning it into a successful career.
I completed the CCENT, the CCNA and one of four exams required to gain the CCNP (BSCI) in 2009. I have almost completed studying the BCMSN curriculum (3 months of blood, sweat and tears) and now out of sheer boredom decided to blog some of my notes/troubleshooting-experiences here (hopefully when I manage to spare me some extra time).
In closing, I hope that anyone who comes across this blog finds it helpful.
I'm a graduate of computer science with a keen interest in networking/security. I started my quest in IT in early 2005 and have ever since actively pursued it in the hope of turning it into a successful career.
I completed the CCENT, the CCNA and one of four exams required to gain the CCNP (BSCI) in 2009. I have almost completed studying the BCMSN curriculum (3 months of blood, sweat and tears) and now out of sheer boredom decided to blog some of my notes/troubleshooting-experiences here (hopefully when I manage to spare me some extra time).
In closing, I hope that anyone who comes across this blog finds it helpful.
Subscribe to:
Posts (Atom)