Archive for March, 2004
Posted in March 29th, 2004
In a pretty naked marketing attempt, the following objective appears on the outline:
Describe the features and operation of network analysis modules on Catalyst switches to improve network traffic management
Most of what I found on this is from the Network Analysis Module (NAM-1/NAM-2) page. The NAM 1/2 data sheets provide more information on what this [...]
continue reading.....
Posted in March 28th, 2004
After more research, and talking with a couple of people, I’ve found out that R1 and R2 will never see each other’s routes over an L2 adjacency, only over an L1 (which they can’t have, since they’re in separate areas)
The only way around this appears to give them connectivity, either by a GRE tunnel, or [...]
continue reading.....
Posted in March 27th, 2004
If you’re following along with my IS-IS example, it seems it’s a bit more complex than I thought. I brought up R2 and R1 stopped working.
So far, I’ve set the priority on R3 to 99 so it becomes the DIS which lets R1 and R2 see all routes except each other’s. Going to [...]
continue reading.....
Posted in March 26th, 2004
If you look at the previous entry, I didn’t set up R2 because it didn’t have IS-IS loaded. Well, I find myself with a bit of free time, and a desire to see what happens between R1 and R2, who are on the same subnet but don’t have direct access.
So, I figure I’ll load [...]
continue reading.....
Posted in March 26th, 2004
To finish up with IS-IS for now, I’m going to go through the set up of a four router, three area IS-IS network that uses a hub and spoke frame relay network. Here is a drawing of the network:
The goal is to simply have all the addresses, including the loopbacks, appear in the routing [...]
continue reading.....
Posted in March 25th, 2004
I don’t want to spend much more time on IS-IS so that I can get to other things. From what I can tell, the level of knowledge required is not as deep as it is for OSPF, EIGRP, and BGP.
As mentioned earlier, a router configured as L1-L2 will form an adjacency twice, once for [...]
continue reading.....
Posted in March 23rd, 2004
Since I’ve been having so much fun with IS-IS recently, I thought I’d look closer at the hello process whereby neighbours form an adjacency. I took two routers, connected over an Ethernet interface, and turned on IS-IS.
r0:
interface Loopback99
ip address 1.1.1.1 255.255.255.255
ip router isis
interface Ethernet0
ip address 10.50.0.1 255.255.255.0
ip router isis
router isis
[...]
continue reading.....
Posted in March 22nd, 2004
I’ve been going over some of the basics behind the OSI protocols, it’s finally time to look at the operation of IS-IS, and compare it to OSPF
The IS-IS protocol uses four types of packets:
Link State Packets (LSP) - distributes the link state information
Hello PDUs - For adjacencies
Partial Sequence Number (PSNP) - acknowledges and requests link [...]
continue reading.....
Posted in March 19th, 2004
In the IS-IS Intro I presented a few links for the IS-IS protocol. Before I can proceed to the configuration/verification of IS-IS (ie the good stuff), I have to go over the underlying OSI protocols.
IS-IS started life out as the routing protocol for CLNP, or the Connectionless Network Protocol. Integrated IS-IS was later [...]
continue reading.....
Posted in March 18th, 2004
IS-IS, or Intermediate System to Intermediate System is a new addition to the CCNP path. It is therefore likely that most people looking at the recertification will not have dealt with it.
The objectives associated with IS-IS are:
Explain basic OSI terminology and network layer protocols used in OSI
Identify similarities and differences between Integrated IS-IS and [...]
continue reading.....