What i`m up to.

This Week has been a mid-load week, work have been kinda active and i try to keep up with my study habits, currently i`m working with EIGRP labs from BSCI (yes i know ROUTE is the new exam) as a review, already read once, Wendell Odom CCIE RS 4th edition EIGRP chapter, need to make a review still. After finishing BSCI labs, going to take and review CCNP ROute official course. Then Narbik Workbook practice for command and scenarios skills.

Regarding my voice studies, i started reading the official certification guide, took notes from the first chapter, will be posting them later, been having some hands on with the Call manger Web administration, and ip phones, looking forward to dive more deep into the voice world.

By the way, did some macros to test on the production network…kinda kool.

Later.

Rebirth of an Engineer.

Its a long time, i do not even think on posting something related or unrelated to networking and my quest in general, i have to say things have changed a lot, i finally have a stable work in a finance(bank) company, now i`m able to everyday grasp the behavior of ospf on a mid-size network, i`m able to see how the integration of redundant links affects a production network, how technical problems rise from nowhere , now i`m feeling the pressure of working as the IT-Networking Guy, and i must say i love it.

 

It passed a certain time, till i started to think again about my goals and the networking knowledge in general, its kinda strange i had lots of time focusing on other interesting but unrelated affairs, But now here we are, again inspired and ready to move on to new challenges and to tackle old bad behavior ( Structured cabling makes a sound  here….). Lately i`ve been reviewing ospf and the related link-state theory, i have also some agenda regarding some kind of unrelated ( not really) technology like Cisco Call manager (which is the main voice system on my work), some stuff related to wireless devices Alvarion, also planning on getting my hands on ASA Cisco sec technology and the usual IT server – technical support stuff.

 

Finally this post even though it has a epic title, the real reason its to let you know i`m still alive, and CCIE Written its the next goal….so stay in touch…

 

 

IINS Chapter Review Q&A.

Chapter I : http://www.megaupload.com/?d=R0W9ME08

Chapter II: http://www.megaupload.com/?d=VTHI4GVP

Chapter III: http://www.megaupload.com/?d=GPEAMTE5

Chapter IV: Waiting for Edition.

Chapter V: http://www.megaupload.com/?d=BVF4IEXA

This post will be update, until the final chapter is covered. All files are on PDF format. This files are just for quick review, not exhaustive study.

Cisco CRS-1 VS Juniper T1600

Cisco Elite Core Router CRS-1, will be having a Mayor Upgrade with the  MSC120 which will take the Route to 120Gbps per slot, in the midst of that News!, Cisco Rival Juniper Networks announce they have a new generation of silicon to take the T1600 to 250Gbps!!! per slot!!, This is getting better and better !

http://www.networkworld.com/news/2010/020110-cisco-core-router-upgrade.html?hpg1=bn

http://www.networkworld.com/community/node/57157

http://www.networkworld.com/news/2007/061107-juniper-product-side.html

http://www.networkworld.com/news/2009/020209-juniper-router-switch.html

New CCNP exams Topics.

Everyone already knows that Cisco is updating CCNP this year, with a new 3 exam based squeme, ROUTE (642-902), SWITCH(642-813) and TSHOOT(642-832). The exam are going to get available later this year but here are the exam topics for each track.

https://learningnetwork.cisco.com/community/certifications/ccnp/route

https://learningnetwork.cisco.com/community/certifications/ccnp/switch

https://learningnetwork.cisco.com/community/certifications/ccnp/tshoot

http://www.megaupload.com/?d=JNF14W4O (Route Exam Topics).

http://www.megaupload.com/?d=THEBYJ4D (Switch Exam Topics).

http://www.megaupload.com/?d=KKLUAL0W (Tshoot Exam Topics).

New Cisco Track: Service Provider Operations.

Well today searching on the net, as usual i found something very interesting, Cisco is updating its service provider track, with a new one called Service Provider operation, it will update every level of the piramid, meaning CCNA SPO, CCNP SP0 and the great CCIE SP0. i`m putting a link to the CCIE-SPO blueprint at the end. I`m looking forward for study material regarding this new track .

http://blog.ipexpert.com/2010/01/25/new-ccie-track-in-town-service-provider-operations/

https://learningnetwork.cisco.com/docs/DOC-6490

https://learningnetwork.cisco.com/docs/DOC-6395

http://www.megaupload.com/?d=YVI5PXKJ (blueprint).

Changes

Well its been a long time since i post something, ill try to explain in this post what have been happening lately. Well after the holidays my resolution regarding my studies changed a lot, the goal still the same, but the way to achieve them has changed a lotttt, i will not get on details about it in this post, this post is mainly yo make everyone who reads this aware that i`ll continue to post interesting stuff and my usual posts!, it is just that things have changed and i need to reestructure and change some things , so the blog is updated and not in my old resolution. In the mean time , you can entertain yourself with the following info ( some not related to networking at all, but interesting lolz). I`ll be back soon!, more sooner than you think .

Cisco IOU and Pagent tools ( Very interesting!!! believe me :D  ).

http://blog.i-1.nl/?p=474

http://blog.i-1.nl/?p=481

PS3 hacked! ( i told you ! lolz).

http://geohotps3.blogspot.com/2010/01/hello-hypervisor-im-geohot.html

Redsnow 0.9 (Iphone OS firmware 3.1.2) )

http://www.iphonedownloadblog.com/2010/01/21/jailbreak-iphone-3-1-2-redsn0w-0-9-tutorial/

Some cool article on EEM (embedded event manager)

http://blog.internetworkexpert.com/2010/01/18/eem-demystified-part-1/

Cisco Certified Arquitect Blueprint Released.

Finally the Cisco Certified Arquitect Blueprint released.

https://learningnetwork.cisco.com/docs/DOC-6356.

Exam Sections and Sub-task Objectives	√
1. Gather, clarify, and analyze requirements
a.      Gather,   clarify, and analyze business requirements
i. Recognize critical requirements (stated and implied)
ii. Recognize noncritical requirements (stated and implied)
iii. Identify and gather missing information
iv. Identify and clarify ambiguous information
v. Identify and resolve conflicting information and requirements
vi. Demonstrate knowledge of the business
vii. Decompose requirements and problems into component parts
viii. Recognize and/or clarify CAPEX parameters (e.g., equipment costs, capital software costs, capital facility expenditures)
ix. Recognize and/or clarify OPEX parameters (e.g., software tooling changes, leases, retraining, staffing, support contracts, utilities, licensing and hosting)
x. Recognize,   challenge, and resolve unrealistic requirements   (e.g., common-case vs. worst-case scenario)
b.      Gather,   clarify, and analyze technical requirements
i. Recognize   critical requirements (stated and implied)
ii. Recognize  noncritical requirements (stated and implied)
iii. Identify and gather missing information
iv. Identify and clarify ambiguous information
v. Identify and resolve conflicting information and requirements
vi. Leverage   existing network documentation to gain understanding of the current network   and how it supports the business
vii. Decompose   requirements and problems into component parts
viii. Recognize,   challenge, and resolve unrealistic requirements   (e.g., common-case vs. worst-case scenario)
c.      Align   business and technical goals and direction
i. Map technical solution to business impact
ii. Map business needs and requirements to technology
iii. Recognize the relationship between technical and business requirements
iv. Map business continuity requirements to the network architecture
v. Establish a vision and strategy for the network with clarity and completeness
vi. Analyze and estimate various impacts on the network from a change in business   structure or process
vii. Analyze and estimate the SLAs required by the business and evaluate the impact of   outages
viii. Recognize,   challenge, and resolve unrealistic requirements   (e.g., common-case vs. worst-case scenario)
d.            d.      Perform   cursory rough estimations for new or changing requirements and/or informal   what-ifs and requests
i. Recognize   the impact on the existing network and how it currently supports the business
ii. Estimate   the general implementation cost and time frame
iii. Estimate   project feasibility and practicality (including assumptions of parameters and   constraints that impact the two)
iv. Provide   an opinion of how the request does or does not align with network and   business goals (both current and future)
v. Recognize   and/or clarify CAPEX parameters (e.g., equipment costs, capital software   costs, capital facility expenditures)
vi. Recognize   and/or clarify OPEX parameters (e.g., software tooling changes, leases,   retraining, staffing, support contracts, utilities, licensing and hosting)
2. Develop a functional specification for the network
a.      Devise   a solution
i. The complexity of the network is appropriate for the business requirements
ii. The survivability of the network is appropriate for the business requirements
iii. The scalability of the network is appropriate for the business requirements
iv. The manageability of the network is appropriate for the business requirements
v. The security of the network is appropriate for the business requirements
vi. The performance of the network is appropriate for the business requirements
vii. The cost of the network is appropriate for the business requirements
b.      Perform   risk analysis
i. Technologies
ii. Security
iii. Legal
iv. Dependencies   (e.g., outsourcing to third parties, training, tools, provisioning)
3. Create a road map
a. Create   a migration and transition strategy
i. Account   for long-term requirements
ii. Perform   and account for risk analysis
iii. Minimize   the negative impact on existing services
iv. Identify   parties responsible for design, implementation, and operation tasks
v. Strive   for ease of implementation
4. Convey decisions and rationale   (written and verbal)
a.      Communicate   to a business audience
i. Articulate   business problems, requirements, and constraints
ii. Articulate   technical problems, requirements, interdependencies, and constraints
iii. Communicate   the business strategy and direction
iv. Communicate   the risks and benefits
v. Communicate   with specificity rather than generality (e.g., “does not scale because…”   rather than simply “does not scale”)
vi. Communicate   the rationale for decisions clearly and confidently
vii. Accept,   think about, and respond to changing requirements, criticisms, questions, and   challenges in a timely and positive (not arrogant or defensive) manner
viii. Influence   others
b.      Communicate   to a technical audience
i. Articulate   business problems, requirements, and constraints
ii. Articulate   technical problems, requirements, interdependencies, and constraints
iii. Communicate   business strategy and direction
iv. Communicate   risks and benefits
v. Communicate   with specificity rather than generality (e.g., “does not scale because…”   rather than simply “does not scale”)
vi. Communicate   the rationale for decisions clearly and confidently
vii. Accept,  think about,  and respond to changing requirements,   criticisms, questions, and challenges in a timely and positive (not   defensive) manner
viii. Influence   others
5. Demonstrate technical expertise
a.      Technical   expertise
i. Demonstrate   conceptual knowledge of a wide array of network technologies (e.g., Layer 3   routing, tunneling, security, network management)
ii. Demonstrate   conceptual knowledge of places in the network (e.g., data center, WAN,   campus)
iii. Demonstrate   conceptual knowledge of a wide array of applications on the network (e.g.,   voice, video)
iv. Demonstrate   conceptual knowledge of interactions between components and technologies
v. Demonstrate   knowledge of current and future directions of technologies, places in the   network, and applications
vi. Demonstrate   detailed knowledge of a range of network technologies applicable toinfrastructure   design (e.g., Layer 3 routing, tunneling, security, network management)

INE Student Passes CCIE 4.0

Flavio Provedel passes CCIE 4.0 !!! finally. Here is the link

http://blog.internetworkexpert.com/2009/12/17/ine-self-paced-student-passes-version-4-rs/

Static Routing

This is something very Basic, but have lots of applications to some scenarios, and it is in the CCNA topics, so i will review it here. Is good to note i will be going through things like static routing, static routing using exit interface, static routing using next hop, and using default static routes to get to other networks. Things like floating static routes, ill cover them on another post(when Dynamic routing is involved).

Ok first of all what is static routing??? well static routing could be called, the procces of manually mapping networks to the routing table( what a concept!! ). The point of this?? well pretty much obvious so the router can know how to get to other networks, it does not know how to get. If a friend tells you , come by! to my home, and you do not know , his address, your lost!, so that means you need to know exactly how to get to his/her house. It is pretty much the same with ROuters, if a router does not know how to get to a network, it will discard the packets destined to those networks he do not know.That said we can move on.

Scenario

3 Routers connected in a Hub and spoke fashion. Serial links between them, and 6 loopbacks in every location for Lans simulation.

Static Routing using Exit interface/next hop address.

R0(config)# ip route 192.168.200.0 255.255.255.252 s0/0

Ok this is pretty simple. the ip route command is the one used to create static mappings. the syntax is ip route <destination network> <destination network subnet mask> <exit interface/nexthop> so what we are basically doing, is instructing R0 to when it receives a packet destined to network 192.168.200.0/30(p2p link between R1-R2) forward it through interface serial 0/0(Which is the interface pointing to R1).

When the packet arrives R1, R1 recognizes the address as part of network 192.168.200.0/30 and forward it to the interface belonging to this network(in this case pings will be succeful, when packets are sourced from R0 Serial link, and destined to R1 Serial link….Good to note…).

Now lets say we need connectivity to the whole LAN on R1(10.2.0.0/24) from R0.

on R0

R0(config)# ip route 10.2.0.0 255.255.255.0 s0/0

R0(config)# ip route 10.2.1.0 255.255.255.0 s0/0

R0(config)# ip route 10.2.2.0 255.255.255.0 s0/0

R0(config)# ip route 10.2.3.0 255.255.255.0 s0/0

R0(config)# ip route 10.2.4.0 255.255.255.0 s0/0

R0(config)# ip route 10.2.5.0 255.255.255.0 s0/0

We specified R0 how to get to the whole Lan on R1. But there is a problem, if packet where to transit between them(with a source addres of any host of the lan), they will get to R1 but they will not return, given to the fact that R0 knows how to get to R1 , but R1 does not know how to get to R0. So we need to specified R1 how to get to the Whole lan of R0.

on R1

R1(config)# ip route 10.1.0.0 255.255.255.0 192.168.100.1

R1(config)# ip route 10.1.1.0 255.255.255.0 192.168.100.1

R1(config)# ip route 10.1.2.0 255.255.255.0 192.168.100.1

R1(config)# ip route 10.1.3.0 255.255.255.0 192.168.100.1

R1(config)# ip route 10.1.4.0 255.255.255.0 192.168.100.1

R1(config)# ip route 10.1.5.0 255.255.255.0 192.168.100.1

Ok we now have specified R1 how to get to Whole lan of R0, but here we used a different approach, we used the next hop address in spite of the exit interface. You may ask what is the difference??? Well is very straighforward , Static routes pointing exit interface have a administrative distance of 0, cause the IOS sees them as directly connected. and Next-hop pointing static routes, have a AD value of 1.

Now Host from any R0 lan, can reach host on any R1 Lan and vice-versa. Now what happens if i try to ping the host on R2 lan, well ping will fail cause neither of them knows how to reach each other lan.

Static Routing using Default route.

Well on R2, we can have static mapping for all the addresses of R0-R1 lans or we can create a default route. This is called stub network, when a router only have one interface to the outside, every non local traffic only have one way out. this is a stub network. and it is even more easy to configure

R2(config)# ip route 0.0.0.0 0.0.0.0 s0/0

Every traffic destined to a any network(0.0.0.0….non local aka not known), with any subnet mask(0.0.0.0), forward it trhough Serial 0/0 interface.That means that when any host on any of the R2 lans, generates packets to any of the other networks it will forward them trhough interface s0/0.

REMEMBER: You need to specify on R0-R1 how to get to R2 Networks or it would be meaningless, and pings will not be succesful when sourced from R2 Lans, and R0 cannont reach R2 if R1 does not either know hot to get to R2, so keep that in mind. this means R1 need to have mappings to R2 networks.

On R0

R0(config)# ip route 10.3.0.0 255.255.255.0 s0/0

R0(config)# ip route 10.3.1.0 255.255.255.0 s0/0

R0(config)# ip route 10.3.2.0 255.255.255.0 s0/0

R0(config)# ip route 10.3.3.0 255.255.255.0 s0/0

R0(config)# ip route 10.3.4.0 255.255.255.0 s0/0

R0(config)# ip route 10.3.5.0 255.255.255.0 s0/0

on R1

R1(config)# ip route 10.3.0.0 255.255.255.0 s0/1

R1(config)# ip route 10.3.1.0 255.255.255.0 s0/1

R1(config)# ip route 10.3.2.0 255.255.255.0 s0/1

R1(config)# ip route 10.3.3.0 255.255.255.0 s0/1

R1(config)# ip route 10.3.4.0 255.255.255.0 s0/1

R1(config)# ip route 10.3.5.0 255.255.255.0 s0/1

Here we are seen what we have been doing til now, the only thing that has changed is the exit interface on R1.

This will leave us with total connectivy between all routers. This can be a lot more simplify by considering that R0-R2 are stub routers, and summarization on R1. This would look like this

on R0

R0(config)# ip route 0.0.0.0 0.0.0.0 s0/0

on R2

R2(config)# ip route 0.0.0.0 0.0.0.0 s0/0

on R1

R1(config)# ip route 10.1.0.0 255.255.0.0 s0/0

R1(config)# ip route 10.3.0.0 255.255.0.0 s0/1

With this Configurations, there should be Full connectivity between all routers(You can use a script…that i put at the bottom of this post ).

It is a good pratice to have debug ip routing on, while you configure static routes, and any other routing protocol,so you can see, in real time how are routes added to the routing table and lots of cool stuf(sorry morris! ).

This post is not the best post on static routing, but it is pretty much a good reminder for me of this simple task, so i hope you benefit from it somehow, feel free to give some feedback, i have tested this configuration , but feel free to to post if there is some error, or any thing that needs to be reminded.

Links:

http://www.cisco.com/en/US/tech/tk365/technologies_tech_note09186a0080094195.shtml

http://en.wikipedia.org/wiki/Stub_network

http://www.cisco.com/en/US/docs/ios/iproute/configuration/guide/irp_ip_prot_indep_ps6350_TSD_Products_Configuration_Guide_Chapter.html#wp1056183

Script.

To use this script, issue the following commands

R0#tclsh

When you get this prompt “R0(tcl)#” copy the text below and hit enter.R0(tcl)#

foreach address {

192.168.100.1
192.168.100.2
192.168.200.1
192.168.200.2
10.1.0.1
10.1.1.1
10.1.2.1
10.1.3.1
10.1.4.1
10.1.5.1
10.2.0.1
10.2.1.1
10.2.2.1
10.2.3.1
10.2.4.1
10.2.5.1
10.3.0.1
10.3.1.1
10.3.2.1
10.3.3.1
10.3.4.1
10.3.5.1
} { ping $address }