ccie and switch...

it's right here... all of it... don't tell anybody...

and you can download the whole damn pdf for your very own... the contents page is basically a blueprint map for switch on the ccie lab... shhhhhhhhhhhhh...

http://www.cisco.com/en/US/docs/switches/lan/catalyst3750e_3560e/software/release/12.2_55_se/configuration/guide/3750escg.html

virtual and hardware, l2..

i have the 3750 in place, and l2 is functioning properly...

many thanks to tyson scott at ipexpert...

http://blog.ipexpert.com/2011/02/28/gns3-and-physical-switches-breakout-switch/#more-6136

the cloud and gns3 switch plus the 3750, represent the connection to the switched network...

i'm tunneling l2 through the 3750 to get there, and it is invisible, as below...

gns3rtr1#sh cdp neigh
Capability Codes: R - Router, T - Trans Bridge, B - Source Route Bridge
                  S - Switch, H - Host, I - IGMP, r - Repeater, P - Phone,
                  D - Remote, C - CVTA, M - Two-port Mac Relay

Device ID        Local Intrfce     Holdtme    Capability  Platform  Port ID
core1.ozlan      Fas 0/0           166             R S I  WS-C3560- Fas 0/24

gns3rtr2#sh cdp neigh
Capability Codes: R - Router, T - Trans Bridge, B - Source Route Bridge
                  S - Switch, H - Host, I - IGMP, r - Repeater, P - Phone,
                  D - Remote, C - CVTA, M - Two-port Mac Relay

Device ID        Local Intrfce     Holdtme    Capability  Platform  Port ID
core1.ozlan      Fas 0/0           147             R S I  WS-C3560- Fas 0/23

core1#sh cdp neigh                                                             
Capability Codes: R - Router, T - Trans Bridge, B - Source Route Bridge        
                  S - Switch, H - Host, I - IGMP, r - Repeater, P - Phone,     
                  D - Remote, C - CVTA, M - Two-port Mac Relay                 
                                                                               
Device ID        Local Intrfce     Holdtme    Capability  Platform  Port ID    
agg1.ozlan       Fas 0/1           149             R S I  WS-C3560- Fas 0/1    
agg1.ozlan       Fas 0/2           149             R S I  WS-C3560- Fas 0/2    
agg2.ozlan       Fas 0/5           166             R S I  WS-C3560- Fas 0/5    
agg2.ozlan       Fas 0/6           166             R S I  WS-C3560- Fas 0/6    
gns3rtr1.ozlan   Fas 0/24          140               R    7206VXR   Fas 0/0    
gns3rtr2.ozlan   Fas 0/23          159               R    7206VXR   Fas 0/0    
core2.ozlan      Fas 0/4           143             R S I  WS-C3560- Fas 0/4    
core2.ozlan      Fas 0/3           143             R S I  WS-C3560- Fas 0/3

each router is in a separate vlan, the gns3 switch is access vlans to the routers, and dot1q to the cloud, vlan 1... there are two tunneled connections, one each per vlan from the 3750 to core1 on ports f0/23 and 24 respectively...

core1#sh vlan brie                                                             
                                                                               
VLAN Name                             Status    Ports                          
---- -------------------------------- --------- -------------------------------
1    default                          active    Fa0/7, Fa0/8, Fa0/9, Fa0/10    
                                                Fa0/11, Fa0/12, Fa0/13, Fa0/14 
                                                Fa0/15, Fa0/16, Fa0/17, Fa0/18 
                                                Fa0/19, Fa0/20, Fa0/21, Fa0/22 
                                                Gi0/1, Gi0/2                   
10   10                               active                                   
100  100                              active                                   
101  VLAN0101                         active    Fa0/24                         
102  VLAN0102                         active    Fa0/23                         
200  200                              active                                   
1002 fddi-default                     act/unsup                                
1003 token-ring-default               act/unsup                                
1004 fddinet-default                  act/unsup                                
1005 trnet-default                    act/unsup      

note trunked ports 1-6 to the switched network...

VLAN0010                                                                       
  Spanning tree enabled protocol rstp                                          
  Root ID    Priority    4106                                                  
             Address     0016.c706.9680                                        
             This bridge is the root                                           
             Hello Time   2 sec  Max Age 20 sec  Forward Delay 15 sec          
                                                                               
  Bridge ID  Priority    4106   (priority 4096 sys-id-ext 10)                  
             Address     0016.c706.9680                                        
             Hello Time   2 sec  Max Age 20 sec  Forward Delay 15 sec          
             Aging Time  300 sec                                               
                                                                               
Interface           Role Sts Cost      Prio.Nbr Type                           
------------------- ---- --- --------- -------- --------------------------------
Fa0/1               Desg FWD 19        128.3    P2p Peer(STP)                  
Fa0/2               Desg FWD 19        128.4    P2p Peer(STP)                  
Fa0/3               Desg FWD 19        128.5    P2p                            
Fa0/4               Desg FWD 19        128.6    P2p                            
Fa0/5               Desg FWD 19        128.7    P2p                            
Fa0/6               Desg FWD 19        128.8    P2p     


behavior is expected... i haven't dicked around with mtu and difficulties that presents with ospf yet...  i'm simply happy that l2 is functioning properly... as has been stated by others, the plan is not to troubleshoot gns3, the plan is to perform labs...

3750 switch...

i have the 3750 now...  nice thing is on the so called doc cd

http://www.cisco.com/cisco/web/psa/default.html?mode=prod

there are guides that handle the 3750 and 3560 together...

http://www.cisco.com/en/US/docs/switches/lan/catalyst3750e_3560e/software/release/12.2_55_se/configuration/guide/3750escg.html

this will be available during the ccie lab...

however, the plan is to not need this availability...

the whole pdf can be downloaded at once...

what does this mean?

it means i have a complete ccie switch book, for free...

thanks cisco...

perhaps it is because of this that another switch book like the old lan switching bible was never made... it's all there...

you haven't downloaded it yet?

get your free copy now while they last...

i have 9 switches now...

1x3750 for gns3 to miniprise

4x3560

2x3550 which i will probably retire (the fearless beasts that got me through ccnp switch)...

and 2x2950 faithful layer 2's...

i have switchlash...

and 4x hardware routers, and gns3 on ubu 12.04... my pc nic supports dot1q...

i am ready for a fight...

extended system id...

a fixed switch shares it's mac address with it's ports...

Base ethernet MAC Address: 00:09:B7:52:D7:80
the mac address of port 1 on this switch is:


asw2#sh int f0/1
FastEthernet0/1 is up, line protocol is up (connected)
  Hardware is Fast Ethernet, address is 0009.b752.d781 (bia 0009.b752.d781)

if your comfortable with hex, you can easily determine the rest of the ports mac addresses by counting up...


asw2#sh int f0/10
FastEthernet0/10 is down, line protocol is down (notconnect)
  Hardware is Fast Ethernet, address is 0009.b752.d78a (bia 0009.b752.d78a) = 10 hex

you knew that...

the default switch priority is 32768...

we know that the combination of priority and mac address gives us the BID
because 1 or many ports may belong to a vlan, we need more distinction...

the extended system id makes that yet more granular...


asw2#sh spann vlan 20

VLAN0020
  Spanning tree enabled protocol ieee
  Root ID    Priority    32788
             Address     0009.b73f.ce80 (base ethernet)
             Cost        38
             Port        2 (FastEthernet0/2)
             Hello Time   2 sec  Max Age 20 sec  Forward Delay 15 sec

  Bridge ID  Priority    32788  (priority 32768 sys-id-ext 20) 32768 + 20

the extended system id allows the vlan for the switch to have a unique BID

graphic below from http://adelzalok.wordpress.com/2011/09/29/anatomy-of-a-mac-address-bpdu-bid-and-the-802-1q-ethernet-frame-tag/  great site by the way... you haven't clicked on it yet?

switchport identification...

use sh ver to find the mac address assigned to a switch...

sw2950_02#sh ver
Cisco Internetwork Operating System Software
IOS (tm) C2950 Software (C2950-I6K2L2Q4-M), Version 12.1(22)EA14, RELEASE SOFTWA

Processor board ID FHK0619X14J
Last reset from system-reset
Running Standard Image
24 FastEthernet/IEEE 802.3 interface(s)

32K bytes of flash-simulated non-volatile configuration memory.
Base ethernet MAC Address: 00:09:B7:3F:CE:80


so what is the mac of port 1?

sw2950_02#sh int fa0/1
FastEthernet0/1 is up, line protocol is up (connected)
  Hardware is Fast Ethernet, address is 0009.b73f.ce81 (bia 0009.b73f.ce81)

how about fa0/10? better know hex...

sw2950_02#sh int fa0/10
FastEthernet0/10 is down, line protocol is down (notconnect)
  Hardware is Fast Ethernet, address is 0009.b73f.ce8a (bia 0009.b73f.ce8a)

15 is easy...

sw2950_02#sh int fa0/15
FastEthernet0/15 is down, line protocol is down (notconnect)
  Hardware is Fast Ethernet, address is 0009.b73f.ce8f (bia 0009.b73f.ce8f)

16 is not...

sw2950_02#sh int fa0/16
FastEthernet0/16 is down, line protocol is down (notconnect)
  Hardware is Fast Ethernet, address is 0009.b73f.ce90 (bia 0009.b73f.ce90)

the ten's position incremented by one remainder zero is fa0/16...


which makes fa0/24 easy... what is 16 plus 8...

sw2950_02#sh int fa0/24
FastEthernet0/24 is down, line protocol is down (notconnect)
  Hardware is Fast Ethernet, address is 0009.b73f.ce98 (bia 0009.b73f.ce98)

switch 03...

transparent bridge
a transparent bridge is the idea of a layer 2 device which segments a network and passes frames between    
these segments to nodes by learning  information about the nodes addresses, and without the nodes
knowledge of their existence (hence, the bridges are seemingly transparent to the nodes)

bridging loop
a bridging loop is a condition which can occur if more than one layer 2 path exists in a network between
two endpoints.  layer 2 is helpless to stop such occurrences for lack of a mechanism such as ttl

Spanning Tree Protocol
spanning tree is such a mechanism, designed solely to shut down a redundant path that might cause a
loop

BPDU
the unit of communication between switches to establish the rules for the effective topology of the tree, sent
every 2 seconds

root bridge
a root bridge is determined after a topology election in the tree; this is effectively the hub of the layer 2    
network. the ports of the root bridge are always designated

root port
every switch in the network determines a root port; the port with the least cost path to the root switch

root path cost
the cost determined by bandwidth to the root switch.  this cost is often cumulative

designated port
a non-root port on the switch that is the least cost path to the root connecting to another segment

Hello Time
the time between each transmission of a bpdu; default 2 seconds

Forward Delay
the cumulative time for a port to transition to the forwarding state

Max Age time
the time for the prior information learned from a bpdu to expire because a new bpdu has not been received

TCN
a topology change notification bpdu will be initiated by a switch upon port transitioning

Common Spanning Tree
a single instance (common) tree for the network

PVST
a tree instance for every vlan

PVST+
the same as pvst but ieee open standard (without isl)

again with errdisable...

it is safe to say that the errdisable state that a switchport may go through is inconvenient at best and a pain in the ass mostly...
make a mistake with channel groups or port security and you'll find the ports you're working on go belly up with this silliness, and the default recovery time interval is 300 seconds... damn...

this is the link that explains the reasoning and recovery procedures for errdisable...
you have to reset the timer, then enable the timer, and still wait a minimum of 30 seconds for recovery...

http://www.cisco.com/en/US/tech/tk389/tk621/technologies_tech_note09186a00806cd87b.shtml

a simple no shut will not do... the procedures in the link outline recovery, but there is an easier way... once the port is errdisabled, go to the interface, issue shut, then no shut and the interface will come back... who'd a thought...

download this pdf now to your local drive... you don't want to get all twisted up with something like this, especially under pressure...

router on a tip...

it doesn't get easier than this...

get a router a switch and 2 pc's...
connect a straight through cable from the router to a port on a switch... remove the ip address from the fa0/0 first and always, when making subinterfaces (frame and ppp too)... make two subinterfaces on the router
encap dot1q 21 means what it says; encapsulation dot1q for vlan 21...
give each sub ip's on different subnets (intervlan routing; now i got a network boner)


r2620_02#config t
Enter configuration commands, one per line.  End with CNTL/Z.
r2620_02(config)#int fa0/0.21
r2620_02(config-subif)#encap dot1q 21
r2620_02(config-subif)#ip add 192.168.21.1 255.255.255.0
r2620_02(config-subif)#no shut
r2620_02(config-subif)#int fa0/0.22
r2620_02(config-subif)#encap dot1q 22
r2620_02(config-subif)#ip add 192.168.22.1 255.255.255.0
r2620_02(config-subif)#no shut
r2620_02(config-subif)#

swich time..
make two vlans, make a trunk (assigning vlans to the trunk is optional, why, because they forward all vlan traffic by default unless otherwise slapped around), put an interface into each vlan and you got...

s2(config)#vlan 21
s2(config-vlan)#name 21
s2(config-vlan)#vlan 22
s2(config-vlan)#name 22
s2(config-vlan)#exit
s2(config)#int fa0/17
s2(config-if)#sw mode trunk
s2(config-if)#sw trunk allow vlan 21,22
s2(config-if)#exit
s2(config)#int fa0/15
s2(config-if)#sw mode acc
s2(config-if)#sw acc vlan 21
s2(config-if)#int fa0/16
s2(config-if)#sw mode acc
s2(config-if)#sw acc vlan 22
s2(config-if)#do sh vlan

VLAN Name                             Status    Ports
---- -------------------------------- --------- -------------------------------
1    default                          active    Fa0/5
10   fac/staff                        active    Fa0/11, Fa0/12, Fa0/13, Fa0/14
20   students                         active    Fa0/18, Fa0/19, Fa0/20, Fa0/21
                                                Fa0/22, Fa0/23, Fa0/24
21   21                               active    Fa0/15
22   22                               active    Fa0/16

connect a pc to each switch port and set ip's and gateways...

and then ping the damn things... don't forget to debug ip icmp on the router, see after pc pings...

C:\Users\bosgood>ping 192.168.21.1

Pinging 192.168.21.1 with 32 bytes of data:
Reply from 192.168.21.1: bytes=32 time=2ms TTL=255
Reply from 192.168.21.1: bytes=32 time=1ms TTL=255
Reply from 192.168.21.1: bytes=32 time=1ms TTL=255
Reply from 192.168.21.1: bytes=32 time=2ms TTL=255

Ping statistics for 192.168.21.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 2ms, Average = 1ms


C:\Users\bosgood>ping 192.168.22.1

Pinging 192.168.22.1 with 32 bytes of data:
Reply from 192.168.22.1: bytes=32 time=2ms TTL=255
Reply from 192.168.22.1: bytes=32 time=2ms TTL=255
Reply from 192.168.22.1: bytes=32 time=1ms TTL=255
Reply from 192.168.22.1: bytes=32 time=1ms TTL=255

Ping statistics for 192.168.22.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 2ms, Average = 1ms

r2620_02#debug ip icmp
ICMP packet debugging is on
r2620_02#
Dec 22 18:47:13.575: ICMP: echo reply sent, src 192.168.21.1, dst 192.168.21.2
r2620_02#
Dec 22 18:47:14.575: ICMP: echo reply sent, src 192.168.21.1, dst 192.168.21.2
r2620_02#
Dec 22 18:47:15.579: ICMP: echo reply sent, src 192.168.21.1, dst 192.168.21.2
r2620_02#
Dec 22 18:47:16.583: ICMP: echo reply sent, src 192.168.21.1, dst 192.168.21.2

r2620_02#
Dec 22 18:49:39.983: ICMP: echo reply sent, src 192.168.22.1, dst 192.168.22.2
r2620_02#
Dec 22 18:49:40.987: ICMP: echo reply sent, src 192.168.22.1, dst 192.168.22.2
r2620_02#
Dec 22 18:49:41.987: ICMP: echo reply sent, src 192.168.22.1, dst 192.168.22.2
r2620_02#
Dec 22 18:49:42.991: ICMP: echo reply sent, src 192.168.22.1, dst 192.168.22.2
r2620_02#

that's a router on my...

spanning tree very pretty...

STP summary

1.  all bridge (switch ports) stabilize at forwarding or blocking.  Forwarding ports are considered part of the spanning tree.

2.  one switch is elected root, and its ports will all move to forwarding state.

3.  each switch receives hellos from the root, directly or through another switch. The port that receives the least cost BPDU is placed in forwarding and becomes that switch’s root port

4.  for each segment one switch forwards the BPDU with the lowest cost.  That switch becomes that segment’s designated bridge.

5.  the other interfaces are placed in blocking

6.  the root sends BPDU’s every 2 seconds. This time interval can be modified and will be noted in the BPDU.

7.  if max-age elapses (20 seconds, default) and no BPDU, panic ensues and the spanning tree changes.

8.  forward delay (default 15 seconds) is the time it takes for a port to transition through the dumbass states to forwarding. (listening, 15 seconds, learning 15 seconds)

9.  when a switch goes into listening, it sends a TCN BPDU (topology change notification) through the new path to the root. Other switches will refresh their tables with the new entry.

10. spanning tree creates these delays to prevent transitional loops because…

spanning tree, very pretty and the bpdu’s are sweet,

but the root of the poor spanning, is impossible to eat…

spanning-tree song...

spanning-tree very pretty and the bpdu's are sweet,
but the root of the poor spanning, is impossible to eat,

Michael the network cat likes that song... reow
 

STP elects a root bridge (switch) and puts all root bridge interfaces into forwarding state

Each non root bridge (switch) determines which of its ports has the least administrative cost (best) to the root bridge and STP makes that port that switch’s root port.

The switch with the lowest (best) cost  to the root is put in forwarding state.

The lowest cost switch on each segment is the designated bridge (switch) and the interface on that switch is called the designated port.

            The root bridge’s (switch) ports are always in forwarding state and the root switch (bridge) is always the designated bridge on all connected segments.

            The non root bridge root port is always forwarding. This port receives the lowest cost BPDU from the root.

            Each LAN’s designated port is always forwarding and the bridge forwarding the lowest cost BPDU is the segment’s designated bridge (switch)

             All other ports are blocking. No forwarding frames, no receiving frames.

         At first each switch claims to be root by sending BPDU’s that contain:

                 The root bridge ID- a combination switch priority and MAC address, lower number, higher priority

             The cost to reach the root- again the lower, the better

             And it’s own bridge ID

can't we just call a root bridge a root switch instead...

Stinky Toilet Paper...

this is gonna hurt you more than me...
spanning-tree port states... arrrrrrrrrrrrrrgh

after initializing, a switchport always enters the blocking state

blocking:
the port dumps the frames received
dumps frames switched for forwarding from another switch
doesn't learn shit
receives bpdu's

listening:

the port dumps the frames received
dumps frames switched for forwarding from another switch
doesn't learn shit
receives bpdu's

learning:
the port dumps the frames received
dumps frames switched for forwarding from another switch
finally gets off its dead ass and learns addresses
receives bpdu's

forwarding:
receives and forwards frames
forwards frames switched from another port
learns addresses
receives bpdu's

disabled:
doesn't do shit

spanning-treed...

i asked michael the network cat exactly what it is that spanning-tree does...
he replied, it prevents switching loops...
precisely...

so in case you don't have a meshed network, what then michael?

it causes a lot of traffic, slows down your ports, doesn't block any ports because there are no redundant links, but gives you nice output and bridge and port status information, lots of debugging stuff if you want to see it, and many other features that will be tested by cisco...

ok then... the right answer is the cisco answer...

saran wrap...

when you receive a cisco switch it is by default set to server mode out of the box...  be sure to set it to transparent mode before deployment...

Server
 can create, add, delete  and/or change vlan information.  these changes are added throughout the VTP domain

Client
  listen for advertisements and modify their own configurations as a result.  a server is required by the client    for vlan changes. a client cannot create, add or delete vlans

Transparent
  can forward or receive vlan advertisements but otherwise do not participate in the domain...

you can see right through them... so there...

rip and eigrp together...

follow the bouncing prompts...

r2620_01#sh ip route
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
       D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
       E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
       i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area
       * - candidate default, U - per-user static route, o - ODR
       P - periodic downloaded static route

Gateway of last resort is not set

     1.0.0.0/24 is subnetted, 1 subnets
C       1.1.1.0 is directly connected, Loopback0
R    2.0.0.0/8 [120/1] via 10.0.0.2, 00:00:10, Serial0/1
R    100.0.0.0/8 [120/1] via 192.168.1.100, 00:00:20, FastEthernet0/0
R    3.0.0.0/8 [120/1] via 11.0.0.3, 00:00:12, Serial0/0
     10.0.0.0/30 is subnetted, 1 subnets
C       10.0.0.0 is directly connected, Serial0/1
     11.0.0.0/24 is subnetted, 1 subnets
C       11.0.0.0 is directly connected, Serial0/0
C    192.168.1.0/24 is directly connected, FastEthernet0/0
r2620_01#

sw3550#sh ip route
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
       D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
       E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
       i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area
       * - candidate default, U - per-user static route, o - ODR
       P - periodic downloaded static route

Gateway of last resort is not set

R    1.0.0.0/8 [120/1] via 192.168.1.50, 00:00:13, Vlan1
R    2.0.0.0/8 [120/2] via 192.168.1.50, 00:00:13, Vlan1
     100.0.0.0/24 is subnetted, 1 subnets
C       100.0.0.0 is directly connected, Loopback0
R    3.0.0.0/8 [120/2] via 192.168.1.50, 00:00:13, Vlan1
R    10.0.0.0/8 [120/1] via 192.168.1.50, 00:00:13, Vlan1
R    11.0.0.0/8 [120/1] via 192.168.1.50, 00:00:13, Vlan1
C    192.168.1.0/24 is directly connected, Vlan1
sw3550#

then eigrp comes into the mix...

r2620_01#config t
Enter configuration commands, one per line.  End with CNTL/Z.
r2620_01(config)#router eigrp 1
r2620_01(config-router)#network 1.0.0.0
r2620_01(config-router)# network 10.0.0.0
r2620_01(config-router)# network 11.0.0.0
r2620_01(config-router)# network 192.168.1.0
r2620_01(config-router)#no auto-summ
r2620_01(config-router)#end
r2620_01#

after the other 2 routers have been updated with eigrp here is the new routing table...

r2620_01#sh ip route
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
       D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
       E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
       i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area
       * - candidate default, U - per-user static route, o - ODR
       P - periodic downloaded static route

Gateway of last resort is not set

     1.0.0.0/24 is subnetted, 1 subnets
C       1.1.1.0 is directly connected, Loopback0
     2.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
R       2.0.0.0/8 [120/1] via 10.0.0.2, 00:00:19, Serial0/1
D       2.2.2.0/24 [90/2297856] via 10.0.0.2, 00:05:26, Serial0/1
R    100.0.0.0/8 [120/1] via 192.168.1.100, 00:00:21, FastEthernet0/0
     3.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
R       3.0.0.0/8 [120/1] via 11.0.0.3, 00:00:05, Serial0/0
D       3.3.3.0/24 [90/2297856] via 11.0.0.3, 00:01:20, Serial0/0
     10.0.0.0/30 is subnetted, 1 subnets
C       10.0.0.0 is directly connected, Serial0/1
     11.0.0.0/24 is subnetted, 1 subnets
C       11.0.0.0 is directly connected, Serial0/0
C    192.168.1.0/24 is directly connected, FastEthernet0/0
r2620_01#


r2620_02#sh ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
       D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
       E1 - OSPF external type 1, E2 - OSPF external type 2
       i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
       ia - IS-IS inter area, * - candidate default, U - per-user static route
       o - ODR, P - periodic downloaded static route

Gateway of last resort is not set

     1.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
D       1.1.1.0/24 [90/2297856] via 10.0.0.1, 00:24:20, Serial0/0
R       1.0.0.0/8 [120/1] via 10.0.0.1, 00:00:00, Serial0/0
     2.0.0.0/24 is subnetted, 1 subnets
C       2.2.2.0 is directly connected, Loopback0
R    100.0.0.0/8 [120/2] via 10.0.0.1, 00:00:00, Serial0/0
     3.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
D       3.3.3.0/24 [90/2809856] via 10.0.0.1, 00:20:14, Serial0/0
R       3.0.0.0/8 [120/2] via 10.0.0.1, 00:00:00, Serial0/0
     10.0.0.0/30 is subnetted, 1 subnets
C       10.0.0.0 is directly connected, Serial0/0
     11.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
D       11.0.0.0/24 [90/2681856] via 10.0.0.1, 00:24:20, Serial0/0
R       11.0.0.0/8 [120/1] via 10.0.0.1, 00:00:04, Serial0/0
D    192.168.1.0/24 [90/2172416] via 10.0.0.1, 00:24:24, Serial0/0
r2620_02#


r2620_02#sh ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
       D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
       E1 - OSPF external type 1, E2 - OSPF external type 2
       i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
       ia - IS-IS inter area, * - candidate default, U - per-user static route
       o - ODR, P - periodic downloaded static route

Gateway of last resort is not set

     1.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
D       1.1.1.0/24 [90/2297856] via 10.0.0.1, 00:24:20, Serial0/0
R       1.0.0.0/8 [120/1] via 10.0.0.1, 00:00:00, Serial0/0
     2.0.0.0/24 is subnetted, 1 subnets
C       2.2.2.0 is directly connected, Loopback0
R    100.0.0.0/8 [120/2] via 10.0.0.1, 00:00:00, Serial0/0
     3.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
D       3.3.3.0/24 [90/2809856] via 10.0.0.1, 00:20:14, Serial0/0
R       3.0.0.0/8 [120/2] via 10.0.0.1, 00:00:00, Serial0/0
     10.0.0.0/30 is subnetted, 1 subnets
C       10.0.0.0 is directly connected, Serial0/0
     11.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
D       11.0.0.0/24 [90/2681856] via 10.0.0.1, 00:24:20, Serial0/0
R       11.0.0.0/8 [120/1] via 10.0.0.1, 00:00:04, Serial0/0
D    192.168.1.0/24 [90/2172416] via 10.0.0.1, 00:24:24, Serial0/0
r2620_02#



look at those friggin d's up in there...

and the 3550 wants in too...
only the 3550 is still stuck with rip version 2...

sw3550#sh ip route
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
       D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
       E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
       i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area
       * - candidate default, U - per-user static route, o - ODR
       P - periodic downloaded static route

Gateway of last resort is not set

R    1.0.0.0/8 [120/1] via 192.168.1.50, 00:00:25, Vlan1
R    2.0.0.0/8 [120/2] via 192.168.1.50, 00:00:25, Vlan1
     100.0.0.0/24 is subnetted, 1 subnets
C       100.0.0.0 is directly connected, Loopback0
R    3.0.0.0/8 [120/2] via 192.168.1.50, 00:00:25, Vlan1
R    10.0.0.0/8 [120/1] via 192.168.1.50, 00:00:25, Vlan1
R    11.0.0.0/8 [120/1] via 192.168.1.50, 00:00:25, Vlan1
C    192.168.1.0/24 is directly connected, Vlan1
sw3550#

and the 2950's have a say in the matter as well on the other side of the 3550...

sw2950_02#ping 3.3.3.3

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 3.3.3.3, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 32/34/44 ms
sw2950_02#

rip still hangs in the background but rips' administrative distance just got hammered by eigrp...
(output from r2601_01's sh run)


router eigrp 1
 network 1.0.0.0
 network 10.0.0.0
 network 11.0.0.0
 network 192.168.1.0
 no auto-summary
!
router rip
 version 2
 network 1.0.0.0
 network 10.0.0.0
 network 11.0.0.0
 network 192.168.1.0


eigrp and rip; like peas and carrots...

a new beginning...

my first shipment arrived today, the 3550, i expect the rest of the gear tomorrow... it's kind of weird having the shit in my apartment... it'll be a constant reminder; configure me, connect me, make me go to porn sites... i'll do pictures tomorrow once i have them racked...

so i take the switch out of the box, set it on a stand for now, grab the console cable and i'm ready to connect it to my laptop...  no serial port... not a problem... i break out the old desktop, monitor, etc, power it up and i'm all set...  no serial port on that either and that's got to be five years old by now... damn... off to office max, nice that it's just up the road, and i look around a bit... over ten bucks for a power cable, nearly thirty for a long rj-45... i turn a corner and there is the section i'm looking for...  37 dollars for a serial to usb adapter... i have these visions that i'm about to nickel and dime myself into the poor house with this project... all right, buy it, return it before 14 days are up, and get a cheaper one on line... not a chance, 30 bucks on line not including shipping... good God...

had to install software for it also...  connect it up, run putty, select serial, com1, defaults to 8, none, and 1
and i get errors; serial port not found...  go to control-panel, system, hardware, (xp machine) and there it is... on com3...

works great... connected it up through the wireless router to the cable modem and i'm pinging the time warner gateway within moments... routers and more switches tomorrow...