Posts tagged Cisco

EIGRP Lab #1

May 3rd

Posted by Colby in Labs

2 comments

This is the first EIGRP post I’ll be doing for CCIE lab preparation.

I’ve tried to include a lot in this one without making it too long. Here’s the topology:

Click here for the initial configs

Here is task one:
1. Advertise all connected loopbacks into EIGRP AS 100. Ensure that only interfaces connected to other routers will form adjacencies. Do not allow EIGRP to summarize automatically.

Simple stuff:

R1(config)#router eigrp 100
R1(config-router)#passive-interface default
R1(config-router)#no passive-interface Virtual-Template12
R1(config-router)#no passive-interface Virtual-Template13
R1(config-router)#network 1.0.0.0
R1(config-router)#network 10.0.0.0
R1(config-router)#no auto-summary
 
R1(config)#interface Virtual-Template12
R1(config-if)#ip address 10.1.12.1 255.255.255.0
R1(config-if)#
R1(config-if)#interface Virtual-Template13
R1(config-if)#ip address 10.1.13.1 255.255.255.0
R1(config-if)#
R1(config-if)#interface Serial0/0.102 point-to-point
R1(config-subif)#frame-relay interface-dlci 102 ppp Virtual-Template12
R1(config-subif)#
R1(config-fr-dlci)#interface Serial0/0.103 point-to-point
R1(config-subif)# frame-relay interface-dlci 103 ppp Virtual-Template13

This EIGRP config is basic, we’ve started the EIGRP 100 process, added our passive interface and network statements. We also disable auto-summarization. I’m only showing R1 here as the config is nearly identical across the board. We’ve also configured PPP on the FR links with Virtual Templates, this will be needed later in the config (leak maps).

Read more...

, , , , , , ,

RIP Lab #2

Apr 30th

Posted by Colby in Labs

3 comments

This is the second and last RIP post I’ll be doing to prepare for the CCIE.

I’ve tried to include a lot in this one without making it too long. Here’s the topology:


(Click image for fullsize)

Click here for the initial configs

Here is task one:
1. Configure RIPv2 on all routers and advertise their directly connected interfaces. Ensure that these routers have full NLRI to all the loopback interfaces advertised into RIP. Ensure that all routers can ping all loopbacks. Configure RIP not to advertise on any interface by default.

Let’s go through the config:

R1(config)#router rip
R1(config-router)# version 2
R1(config-router)# no auto-summary
R1(config-router)# network 1.0.0.0
R1(config-router)# network 10.0.0.0
R1(config-router)# passive-interface default
R1(config-router)# no passive-interface Serial0/0.102
R1(config-router)# no passive-interface Serial0/0.103

I’m only showing R1 here as the other routers will be nearly identical. First we enable RIP, configure the version, turn of auto-summary and configure our network statements. Then we use the “passive-interface default” command, which tells RIP that all interfaces are passive unless explicity configured otherwise. Last we configure the configure s0/0.102 and s0/0.103 NOT to be passive.

Read more...

, , , , , , ,

Guest Post On NF Blog

Apr 29th

Posted by Colby in Labs

No comments

I wrote a BGP Lab post on the Networking-Forum Blog. Here’s a preview:

Topology:

Tasks:
1. Configure the Oustside Border Router in AS 6500. Peer with ISP-1 and ISP-2. Ensure that the DMZ subnet is advertised to the internet.
2. Prevent AS 6500 from being used as a transit between ASes 1111 and 2222.
3. The link through ISP-1 is much faster than the link through ISP-2. Configure outgoing traffic to use ISP-1 as the primary, only use the link through ISP-2 if the primary link is down.
4. Configure incoming traffic to use the link through ISP-1 as the primary.
5. Ensure that NAT is setup to use both ISPs.

Check it out if you’re interested!

, , , , , , ,

RIP Lab #1

Apr 27th

Posted by Colby in Labs

5 comments

This is the first in a series of lab posts I’ll be doing to prepare for the CCIE.

Today’s lab is from Narbik’s Volume One workbook. It’s a RIPv2 lab with some tricks thrown in. Here’s the topology:


(Click image for fullsize)

Click here for the initial configs

Here is task one:

1. Configure RIPv2 on all routers and advertise their directly connected interfaces. Ensure that these routers have full NLRI to all the loopback interfaces advertised into RIP. Ensure that all routers can ping all loopbacks.

Let’s go through the config:

R1:
R1(config)#router rip
R1(config-router)#ver 2
R1(config-router)#no auto
R1(config-router)#network 10.0.0.0
R1(config-router)#network 1.0.0.0
 
R2:
R2(config)#router rip
R2(config-router)#ver 2
R2(config-router)#no auto
R2(config-router)#network 10.0.0.0
R2(config-router)#network 2.0.0.0
 
R3:
R3(config)#router rip
R3(config-router)#ver 2
R3(config-router)#no auto
R3(config-router)#network 10.0.0.0
R3(config-router)#network 3.0.0.0

Looks pretty simple, but I’m sure you guys see that this won’t work correctly. Let’s look at R2 and R3′s routing tables:

R2#sh ip route
...
R    1.0.0.0/8 [120/1] via 10.1.1.1, 00:00:15, Serial0/0
C    2.0.0.0/8 is directly connected, Loopback0
     10.0.0.0/24 is subnetted, 1 subnets
C       10.1.1.0 is directly connected, Serial0/0
 
R3#sh ip route
...
R    1.0.0.0/8 [120/1] via 10.1.1.1, 00:00:06, Serial0/0
C    3.0.0.0/8 is directly connected, Loopback0
     10.0.0.0/24 is subnetted, 1 subnets
C       10.1.1.0 is directly connected, Serial0/0
Read more...

, , , , , , , ,

Weekly Open Ended Question #11

Apr 26th

Posted by Colby in Open Ended Questions

4 comments

The answer to the tenth question has been added to the post.

Eleventh question:

What is PIM, what are its modes and how do they differ?


Please post answers in the comments (without Googling)!

Highlight for answer:

PIM is “Protocol Independent Multicast”. Its two modes are Dense and Sparse. Dense mode is a pudh model, while Sparse Mode is a pull model.

Source

, , ,

Simple IPv6 Tutorial

Apr 20th

Posted by Colby in Tutorials

9 comments

Today we’ll configure a basic IPv6 network. I’m not a big fan of IPv6. I’ve never used it in the real world, so it’s hard for me to keep it in my head, but I’ve been studying the hell out of it for the Written, so here goes.

We have a simple topology, only three routers. We will be running OSFPv3 on our serial links and loopbacks. Here’s our topology:


(Click image for fullsize)

First we’ll configure our IPv6 addresses:

R1:
R1(config)#ipv6 unicast-routing
R1(config)#int s0/0
R1(config-if)#ip add 10.1.12.1 255.255.255.0
R1(config-if)#ipv6 add 10:1:1:12::1/64
R1(config-if)#no shut
 
R2:
R2(config)#ipv6 unicast-routing
R2(config)# int s0/0
R2(config-if)#ip add 10.1.12.2 255.255.255.0
R2(config-if)#ipv6 add 10:1:1:12::2/64
R2(config-if)#no shut
R2(config-if)#exit
R2(config)#int s0/1
R2(config-if)#ip add 10.1.23.2 255.255.255.0
R2(config-if)#ipv6 add 10:1:1:23::2/64
R2(config-if)#no shut
 
R3:
R3(config)#ipv6 unicast-routing
R3(config-if)#int s0/1
R3(config-if)#ip add 10.1.23.3 255.255.255.0
R3(config-if)#ipv6 add 10:1:1:23::3/64

The first thing we do on each router is enable IPv6 routing. Then we give the interface an IPv4 address and finally an IPv6 address.

Let’s verify connectivity from R2:

Serial0/0 is up, line protocol is up
  IPv6 is enabled, link-local address is FE80::C001:71FF:FE12:0
  Global unicast address(es):
    10:1:1:12::2, subnet is 10:1:1:12::/64
  Joined group address(es):
    FF02::1
    FF02::2
    FF02::1:FF00:2
    FF02::1:FF12:0
  MTU is 1500 bytes
  ICMP error messages limited to one every 100 milliseconds
  ICMP redirects are enabled
  ND DAD is enabled, number of DAD attempts: 1
  ND reachable time is 30000 milliseconds
  Hosts use stateless autoconfig for addresses.
Serial0/1 is administratively down, line protocol is down
  IPv6 is enabled, link-local address is FE80::C001:71FF:FE12:0 [TEN]
  Global unicast address(es):
    10:1:1:23::2, subnet is 10:1:1:23::/64 [TEN]
  Joined group address(es):
    FF02::1
    FF02::2
    FF02::1:FF00:2
    FF02::1:FF12:0
  MTU is 1500 bytes
  ICMP error messages limited to one every 100 milliseconds
  ICMP redirects are enabled
  ND DAD is enabled, number of DAD attempts: 1
  ND reachable time is 30000 milliseconds
  Hosts use stateless autoconfig for addresses.
 
R2#sh ipv int b
Serial0/0                  [up/up]
    FE80::C001:71FF:FE12:0
    10:1:1:12::2
Serial0/1                  [up/up]
    FE80::C001:71FF:FE12:0
    10:1:1:23::2
 
R2#ping  10:1:1:12::1
Sending 5, 100-byte ICMP Echos to 10:1:1:12::1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 0/2/4 ms
 
R2#ping  10:1:1:23::3
Sending 5, 100-byte ICMP Echos to 10:1:1:23::3, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 0/3/12 ms

We have connectivity between interfaces on the same subnet.

Now we’ll configure our loopbacks and OSPFv3:

R1:
R1(config-if)#int lo0
R1(config-if)#ipv6 add 1:1:1::1/64
R1(config-if)#ipv6 ospf 20 area 0
R1(config-if)#int s0/0
R1(config-if)#ipv6 ospf 20 area 0
 
R2:
R2(config)#int lo0
R2(config-if)#ipv6 add 2:2:2::2/64
R2(config-if)#ipv6 ospf 20 area 0
R2(config-if)#int s0/0
R2(config-if)#ipv6 ospf 20 area 0
R2(config-if)#int s0/1
R2(config-if)#ipv6 ospf 20 area 0
 
R3:
R3(config)#int lo0
R3(config-if)#ipv6 add 3:3:3::3/64
R3(config-if)#ipv6 ospf 20 area 0
R3(config-if)#int s0/1
R3(config-if)#ipv6 ospf 20 area 0

With v6 we enable OSPF directly under the interface on which it runs.

Read more...

, , , , , , , , , ,
« First...«23456»10...Last »