- OSPF supports 50 routers per area
- IS-IS can support up to 1000 routers per area
- OSPF includes more features, including route tags, stub/nssa configuration, on demand circuits
- OSPF requires many LSA's to advertise and withdraw routes.
- IS-IS only requires one LSP per IS-IS router in a given area.
- IS-IS doesn't support a Backup designated router (BDR).i.e. you only have the primary Designated Intermediate System (DIS).
- IS-IS repeats the DIS election process every time a new router is added to an area.
- If the new router has the same of higher priority it will become the new DIS.
- IS-IS is designed to be deterministic so that the same set of IS-IS routers always produce the same DIS.
- Every time a DIS changes a new set of LSP's are flooded to the neighbours.
- IS-IS form adjacencies with all routers in the area not just the DIS.
- OSPF uses a scaled metric by default where as IS-IS uses a default metric of 10 for all links.
Monday, 19 April 2010
BSCI - IS-IS - Differences between IS-IS and OSPF
BSCI - IS-IS - High level operations
Routers using IS-IS issue Hello packets out of all interfaces enabled for IS-IS to discover neighbours and establish adjacencies.
Routers will become IS-IS neighbours if their Hello packets contain certin information for the creation of an adjacency.
Routers then build Link-State Packets (LSP's) based on the adjacencies present and then flodd the LSP's to their neighbours.
All routers then build a Link-State Database (LSDB) using the information in the received LSP.
The router then runs the SPF algorithm, the shortest path to each dsestination is then calcultated and added to the Routing Information Base (RIB or OSI routing table).
Next, the Partial Route Calcultion is performed using the IP information contained within one of the Time, Length, Value (TLV) fields in the LSP. This generates shortest paths for IP traffic and in turn is entered in to the IP routing table.
Routers will become IS-IS neighbours if their Hello packets contain certin information for the creation of an adjacency.
Routers then build Link-State Packets (LSP's) based on the adjacencies present and then flodd the LSP's to their neighbours.
All routers then build a Link-State Database (LSDB) using the information in the received LSP.
The router then runs the SPF algorithm, the shortest path to each dsestination is then calcultated and added to the Routing Information Base (RIB or OSI routing table).
Next, the Partial Route Calcultion is performed using the IP information contained within one of the Time, Length, Value (TLV) fields in the LSP. This generates shortest paths for IP traffic and in turn is entered in to the IP routing table.
Wednesday, 24 March 2010
BSCI - OSPF - Default Route propagation
By default OSPF does not propagate a default route, and so you need to manually tell OSPF to distribute one from your Autonomous System Border Router (ASBR).
Depending on the type of Area you have employed in your network the way you propagate a default to all your routers will differ slightly.
In Normal Areas (OSPF areas all connected to Area 0) you can do the following:
1) On your ASBR apply a default route:
R1(config)#ip route 0.0.0.0 0.0.0.0 10.1.1.1
2) Inject the default route in to OSPF:
R1(config)#router ospf 1
R1(config-router)#default-information originate [always]
- The [always] option allows you to advertise a default route from the ASBR even when one doesn't actually exist. This can potentially result in better stability for your network. For example, if a default route is learned from a different routing protocol such as RIP and this route for what ever reason starts to flap then every time the route changes type 5 LSA's will be sent into the OSPF domain from the ASBR.
- The [always] option helps prevent actions outside of the OSPF domain from affecting the routers/routes within the OSPF domain.
For Stub and Totally Stub areas the situation is different.
On an ABR you configure an area to be a stub. This in turn prevents type 5 LSA's (external route information) from being sent in to the stub area and in return a default summary route is propagated.
In a Totally Stubby area, this goes a step further. By configuring an area as a Totally Stubby area on the ABR you prevent Type 5 LSA's (for external routes) plus Type 4 and Type 3 LSA's (for inter-area summary routes) from being propogated. A default summary route replaces these types of routes.
In both cases, as a default route is automatically generated at the ABR, you do not require the default-information originate command.
Finally you have Not-So-Stubby-Area's (NSSA)
There are 2 ways to advertise a default route. NSSA ABR can generate a default route with or without a default route in its own routing table.
1) On the ABR connecting Area 0 to the NSSA area you force the ABR to generate a default route:
R3(config)#router ospf 1
R3(config-router)#area 8 nssa default-information originate
-With this example the ABR generates Type 7 LSA's with a link state ID of 0.0.0.0 this is then advertised within the NSSA area
- NOTE - NSSA ASBR can generate a default only when it has a default route in its routing table
- The default route via the ASBR must be known through non-OSPF protocol
2) You can also use the 'no-summary' option when defining your NSSA area and create 'NSSA Totally Stub area':
R3(config)#router ospf 1
R3(config-router)#area 8 nssa no-summary
-In this example you are replacing the Type 3,4,(inter-area summary routes) and Type 5 LSA's(external summary routes) with a default summary route.This is just as you do for a Totally Stubby area.
Depending on the type of Area you have employed in your network the way you propagate a default to all your routers will differ slightly.
In Normal Areas (OSPF areas all connected to Area 0) you can do the following:
1) On your ASBR apply a default route:
R1(config)#ip route 0.0.0.0 0.0.0.0 10.1.1.1
2) Inject the default route in to OSPF:
R1(config)#router ospf 1
R1(config-router)#default-information originate [always]
- The [always] option allows you to advertise a default route from the ASBR even when one doesn't actually exist. This can potentially result in better stability for your network. For example, if a default route is learned from a different routing protocol such as RIP and this route for what ever reason starts to flap then every time the route changes type 5 LSA's will be sent into the OSPF domain from the ASBR.
- The [always] option helps prevent actions outside of the OSPF domain from affecting the routers/routes within the OSPF domain.
For Stub and Totally Stub areas the situation is different.
On an ABR you configure an area to be a stub. This in turn prevents type 5 LSA's (external route information) from being sent in to the stub area and in return a default summary route is propagated.
In a Totally Stubby area, this goes a step further. By configuring an area as a Totally Stubby area on the ABR you prevent Type 5 LSA's (for external routes) plus Type 4 and Type 3 LSA's (for inter-area summary routes) from being propogated. A default summary route replaces these types of routes.
In both cases, as a default route is automatically generated at the ABR, you do not require the default-information originate command.
Finally you have Not-So-Stubby-Area's (NSSA)
There are 2 ways to advertise a default route. NSSA ABR can generate a default route with or without a default route in its own routing table.
1) On the ABR connecting Area 0 to the NSSA area you force the ABR to generate a default route:
R3(config)#router ospf 1
R3(config-router)#area 8 nssa default-information originate
-With this example the ABR generates Type 7 LSA's with a link state ID of 0.0.0.0 this is then advertised within the NSSA area
- NOTE - NSSA ASBR can generate a default only when it has a default route in its routing table
- The default route via the ASBR must be known through non-OSPF protocol
2) You can also use the 'no-summary' option when defining your NSSA area and create 'NSSA Totally Stub area':
R3(config)#router ospf 1
R3(config-router)#area 8 nssa no-summary
-In this example you are replacing the Type 3,4,(inter-area summary routes) and Type 5 LSA's(external summary routes) with a default summary route.This is just as you do for a Totally Stubby area.
Tuesday, 9 March 2010
EIGRP Summarisation and NULL0
EIGRP Summarisation allows you to stream line the routing table making it more efficient. Fewer Routes listed results in less EIGRP updates being sent out and there fore less resources are consumed (Bandwidth, CPU ultilisation, load etc).
By default EIGRP performs auto-summarisation, that is to say that EIGRP will automatically summarise at a major class boundary during redistribution from EIGRP into a classful routing protocol (eg RIP).
EIGRP will also summarise at the major classful boundary when a route is advertised out of an interface that is on a different major class boundary.
In order to prevent a routing loop when summarisation is in effect (whether manual or automatic) a summary is automatically assigned to the NULL0 interface to prevent routing loops. If the router with a summary route received a packet for an unknown subnet that is part of a summarised range then the longest match ends up being the summary route itself (not a subnet of it) and so this is forwarded to the NULL0 interface and is dropped.
The idea is that the router is then prevented from forwarding the packet on to a default route and potentially creating a loop.
Benefits of summarising in this way include a smaller routing table leading to faster look ups, more specific routes will be hidden so if that specific route goes down the whole network does not need to recalculate the DUAL alogrithm, routing updates will be smaller and so limit the number of EGIRP Queries.
The down side of auto summarisation is that it won't factor in discontiguous networks. As a result you could have networks behind the same 172.16.0.0/16 network advertised out of 2 different interfaces to 2 different networks resulting in 50% of traffic arriving in the wrong place.
To address this issue you can disable automatic summarisation and use manual summarisation.
Disabling automatic summarisation is as simple as this:
R1(config)#router eigrp 1
R1(config-router)#no auto-summary
Now the router will not perform summarisation and all available subnets will be advertised.
Manual summarisation is configured on a per-interface basis, when a summary route is applied a NULL0 summary route entry is immediately created in the routing table to help prevent loops.
To configure a manual summary route you do the following:
R1(config)#router eigrp 1
R1(config-router)#no auto-summary
R1(config)#int s0/0/0
R1(config-if)#ip summary-address eigrp [AS] [IP] [Subnet Mask]
e.g) R1(config)#int s0/0/0
R1(config-if)#ip summary-address eigrp 1 172.16.0.0 255.255.224.0
With a manual summary route, the summary route is advertised only if a more specific entry of the summary is present in the routing table. Otherwise it won't appear in the routing table.
By default EIGRP performs auto-summarisation, that is to say that EIGRP will automatically summarise at a major class boundary during redistribution from EIGRP into a classful routing protocol (eg RIP).
EIGRP will also summarise at the major classful boundary when a route is advertised out of an interface that is on a different major class boundary.
In order to prevent a routing loop when summarisation is in effect (whether manual or automatic) a summary is automatically assigned to the NULL0 interface to prevent routing loops. If the router with a summary route received a packet for an unknown subnet that is part of a summarised range then the longest match ends up being the summary route itself (not a subnet of it) and so this is forwarded to the NULL0 interface and is dropped.
The idea is that the router is then prevented from forwarding the packet on to a default route and potentially creating a loop.
Benefits of summarising in this way include a smaller routing table leading to faster look ups, more specific routes will be hidden so if that specific route goes down the whole network does not need to recalculate the DUAL alogrithm, routing updates will be smaller and so limit the number of EGIRP Queries.
The down side of auto summarisation is that it won't factor in discontiguous networks. As a result you could have networks behind the same 172.16.0.0/16 network advertised out of 2 different interfaces to 2 different networks resulting in 50% of traffic arriving in the wrong place.
To address this issue you can disable automatic summarisation and use manual summarisation.
Disabling automatic summarisation is as simple as this:
R1(config)#router eigrp 1
R1(config-router)#no auto-summary
Now the router will not perform summarisation and all available subnets will be advertised.
Manual summarisation is configured on a per-interface basis, when a summary route is applied a NULL0 summary route entry is immediately created in the routing table to help prevent loops.
To configure a manual summary route you do the following:
R1(config)#router eigrp 1
R1(config-router)#no auto-summary
R1(config)#int s0/0/0
R1(config-if)#ip summary-address eigrp [AS] [IP] [Subnet Mask]
e.g) R1(config)#int s0/0/0
R1(config-if)#ip summary-address eigrp 1 172.16.0.0 255.255.224.0
With a manual summary route, the summary route is advertised only if a more specific entry of the summary is present in the routing table. Otherwise it won't appear in the routing table.
CCNP ROUTE Cert Kit Giveaway
Rofi Neron over at ITDualism.wordpress.com has a Cisco CCNP Route Cert Kit to giveaway.
To enter check out his competition here: http://itdualism.wordpress.com/2010/03/03/giveaway-route-cert-kit/
Well worth the time and an excellent opportunity to bag some Cisco Press material.
Good Luck!!
To enter check out his competition here: http://itdualism.wordpress.com/2010/03/03/giveaway-route-cert-kit/
Well worth the time and an excellent opportunity to bag some Cisco Press material.
Good Luck!!
Wednesday, 3 March 2010
CCNP and Networking Academy students
Since Cisco announced their plans to move to the new 3 exam path back in January there's been much discussion at my local Networking Academy about what that actually means for those who have already passed some of the exams but won't finish the Academy programme until after July31st.
Cisco have posted the following information;
CCNP Exam Combinations:
BSCI+BCMSN+ISCW+ONT = Last day is July 31st 2011
COMP+ISCW+ONT = Last day is July 31st 2011
BSCI+SWITCH+ISCW+ONT = Last day is July 31st 2011
ROUTE+BCMSN+ISCW+ONT = Last day is July 31st 2011
ROUTE+SWITCH+ISCW+ONT = Last day is July 31st 2011
BSCI+BCMSN+TSHOOT = Ongoing
COMP+TSHOOT = Ongoing
BSCI+TSHOOT+SWITCH = Ongoing
ROUTE+BCMSN+TSHOOT = Ongoing
ROUTE+SWITCH+TSHOOT = Ongoing
Cisco have posted the following information;
on the last page it says
Q. Until when will Networking Academy students be able to take the current CCNP certification exams?
A. The four current CCNP certification exams will be available to the general public through July 31, 2010 and to Networking Academy students using a special voucher through July 31, 2011. More information about how to obtain a special, non-discount voucher to enable students to continue to take the retiring exams will be communicated as soon as it is available.
CCNP Exam Combinations:
BSCI+BCMSN+ISCW+ONT = Last day is July 31st 2011
COMP+ISCW+ONT = Last day is July 31st 2011
BSCI+SWITCH+ISCW+ONT = Last day is July 31st 2011
ROUTE+BCMSN+ISCW+ONT = Last day is July 31st 2011
ROUTE+SWITCH+ISCW+ONT = Last day is July 31st 2011
BSCI+BCMSN+TSHOOT = Ongoing
COMP+TSHOOT = Ongoing
BSCI+TSHOOT+SWITCH = Ongoing
ROUTE+BCMSN+TSHOOT = Ongoing
ROUTE+SWITCH+TSHOOT = Ongoing
This should be a weight off anyone's mind who is doing their CCNP through a Networking Academy (including me!)
Monday, 22 February 2010
BSCI - EIGRP - #sh ip eigrp neigbors cmd
A common question when reviewing the output of the #sh ip eigrp neighbors cmd is 'What on earth does 'H' stand for??'
Well, here it is......
H (handle): A number used internally by the Cisco IOS software to track a neighbor. It records the order in which the neighbors were learned.
So there you have it...still no clearer why the word Handle was used but at least you now know what it means :o)
Starting the BSCI
Today sees me start the BSCI course at my local Cisco Networking Academy.
I'll be doing more lab work in GNS3, I've already made a good start with my notes covering off EIGRP, and I'll be going over both Jeremy Cioara's CBT Nuggets videos and Chris Bryant's Train Signal videos.
Fingers crossed, here we go...
I'll be doing more lab work in GNS3, I've already made a good start with my notes covering off EIGRP, and I'll be going over both Jeremy Cioara's CBT Nuggets videos and Chris Bryant's Train Signal videos.
Fingers crossed, here we go...
Friday, 19 February 2010
Upgrade your Cisco PIX 525 firewall
Following on from the Cisco Advisory posted here on the 18th feb I thought it would be a good time to cover off exactly how you went about performing the upgrade. This article relates to upgrading a Cisco PIX 525 firewall however the process is similar for Cisco ASA devices too.
Install Notes:
Install Notes:
- If you have a pair, one with 'Fail over License' and the other with unrestricted license (in #sh ver) apply the upgrade to the FailOver node first. If you loose the node then you still have your unrestricted node for use. Otherwise if it goes wrong for what ever reason your Fail Over License' device will reboot every 24 hours
- The article states to connect to the Outside interface. You can infact connect to any available interface you choose not just the Outside if thats easier.
- If you are conducting a minor release upgrade you can perform the procedure on both firewalls at the same time. TFTP transfer the image file then reboot the firewalls together. Conduct your post install checks and you should be good to go.
- Cisco DTE adapter
- Console cable
- Ethernet cable (crossover ideally)
- A tftp sever application such as SolarWinds TFTP Server
- Passwords for your device
- Pix724-30.bin file (or which ever file it is you are upgrading to)
- Connect the console cable to the Primary F/W via the Cisco DTE adapter
- Open HyperTerminal - COM1;9600;8;none;1;none
- Log on the 1st F/W using your password details
- Do #sh fail - to check which is the active node
- Do #sh ver - copy the Serial Number/Running Active Key to a file and save for future reference should things go bad
- Do #sh run and copy your running in to notepad as a precaution
- Power down the Secondary node - this is because you can't have a fail over pair with differing OS versions when performing an upgrade to a major release e.g 6.3 to 7.2.4
- Next do #sh ip - and check for the 'Outside' IP address
- Pick a suitable IP from the same scope and apply it to the LAN connection on the laptop - eg 203.92.26.1
- Connect the Laptop to the 'Outside' port on the F/W - DON'T forget to reconnect the 'Outside' cable once done!
- Back to HyperTerminal do #ping 203.92.26.1 - to check the F/W can communicate with the laptop (if it doesn't, check the arp - #sh arp and #clear arp and try again)
- Start tftp32 on the laptop
- Change the 'Current Directory' in the TFTP server or make a note of the path to the folder with your pix724-30.bin file in it
- Back to HyperTerminal, do #copy tftp://203.92.26.1/pix724-30.bin flash - This will copy the upgrade OS to flash memory
- Do #write mem - to commit the changes
- Once done do #reload
- Once back up log back in and check that it is the active node (#sh fail), check the OS version (#sh ver), check to see active connections (#sh conn), check the vpn settings (#sh crypto - if applicable)
- Once you are satisfied its complete power down the primary F/W and power up the secondary F/W
- Run through the steps again
- Once complete power up the Primary F/W and reload the secondary F/W at the same time
- Log in to the Primary F/W and do #sh fail - check that it’s the active node, if it isn't restart the secondary F/W again
- Log in to the secondary F/W and check it is the secondary node - you should get a synching message whilst you log on.
- Finally go through the checks again and make sure you are happy
- If you run any VPN's through the firewall test these as applicable
- Advise any other teams/engineers your upgrade has been successful
- Enjoy a well earned cup of your favourite brew :o)
Monday, 15 February 2010
Using Cisco SDM in GNS3
One of the great things about GNS3 is that you can practice your labs using real IOS images. The same goes for Cisco SDM. Tasks such as configuring GRE over IPSec tunnels or applying IOS Firewall can be made so much easier via the Cisco SDM.
In this entry I'm going to show you how I configured my laptop to access the Cisco SDM within my GNS3 lab.
This lab assumes you are using a Windows XP system, you use IE, and your Java version is jre-1_5_0_09-windows-i586-p.exe (other versions of JRE may be fine but this is what works for me).
1) Configure a loopback interface on your laptop.
The first task is to configure a loopback interface. To do this go to:
Build your lab and make sure that you install an FE-TX interface on the router/firewall you'd like the laptop to connect to. Save the lab and close it.
3) Make a note of the Loopback hardware address
Go to the directory for GNS e.g.) C:\Program Files\GNS3 and locate the file 'Network device list.cmd'
Run this and make a note of the output for the new loopback address you set up in point 1 e.g)
NIO_gen_eth:\Device\NPF_{19DB09AF-0DC2-43C6-B9B7-69A0E722FA45}
Name : Local Area Connection 2
Desciption: Microsoft Loopback driver
N.B - copy the equivilent output that I've marked in Bold
4) Insert the output for your Loopback interface in to your lab
Now you have a functioning connection into your lab you can do many things. For example download and install Cisco SDM launcher for PC and then enter the internal IP address for the router in your lab you'd like to connect to.
You can also set up a syslog server. Install Kiwi Syslog Server and then configure your network devices to send logging information to the IP address assigned to your loopback interface.
You might want to install a RADIUS server on your XP system and then foward all RADIUS authentication requests to your loop back adapter.
These are just some examples of what you can do once you have your Loopback configure. Enjoy!
In this entry I'm going to show you how I configured my laptop to access the Cisco SDM within my GNS3 lab.
This lab assumes you are using a Windows XP system, you use IE, and your Java version is jre-1_5_0_09-windows-i586-p.exe (other versions of JRE may be fine but this is what works for me).
1) Configure a loopback interface on your laptop.
The first task is to configure a loopback interface. To do this go to:
- Start - Settings - Control Panel - Add Hardware
- Select Next when the wizard starts and then 'Yes, I have already connected the hardware', select Next
- You are presented with a list of currently installed devices, scroll to the bottom and choose 'Add a new hardware device', select Next
- Check the button for 'Intsall the hardware that I manually select from a list' and select Next
- Select 'Network Adapters' and then select Next
- On the next screen choose 'Microsoft' from the left column and then 'Microsoft Loopback Adapter' from the right column, select Next and then Next again to install.
Build your lab and make sure that you install an FE-TX interface on the router/firewall you'd like the laptop to connect to. Save the lab and close it.
3) Make a note of the Loopback hardware address
Go to the directory for GNS e.g.) C:\Program Files\GNS3 and locate the file 'Network device list.cmd'
Run this and make a note of the output for the new loopback address you set up in point 1 e.g)
NIO_gen_eth:\Device\NPF_{19DB09AF-0DC2-43C6-B9B7-69A0E722FA45}
Name : Local Area Connection 2
Desciption: Microsoft Loopback driver
N.B - copy the equivilent output that I've marked in Bold
4) Insert the output for your Loopback interface in to your lab
- Navigate to the saved location for your lab and and right click on the file e.g) mylab.net then select edit network file (if prompted for an application choose Notepad).
- Locate the device you wish to add your Loopback connection to and insert the interface address like the example below: [[ROUTER R3]]
model = 3620
console = 2003
slot0 = NM-4T
s0/0 = R2 s0/1
slot1 = NM-1FE-TX
f1/0 = NIO_gen_eth:\Device\NPF_{19DB09AF-0DC2-43C6-B9B7-69A0E722FA45}
x = 108.0
y = 19.0 - Save this.
- If correctly configured you should now see a cloud marked something like C0 or C1 connecting to your FE interface on the router you choose to assign the connection to.
- Assign IP addresses on the same subnet to both the loopback interface on your windows XP system and the FE-TX interface on your network device.
- Ping the IP addresses from either side and you should have connectivity. If you don't, trouble shoot accordingly
Now you have a functioning connection into your lab you can do many things. For example download and install Cisco SDM launcher for PC and then enter the internal IP address for the router in your lab you'd like to connect to.
You can also set up a syslog server. Install Kiwi Syslog Server and then configure your network devices to send logging information to the IP address assigned to your loopback interface.
You might want to install a RADIUS server on your XP system and then foward all RADIUS authentication requests to your loop back adapter.
These are just some examples of what you can do once you have your Loopback configure. Enjoy!
Subscribe to:
Posts (Atom)