tshoot cont...

as below...

dhcp is being issued to the pc...

R4#sh ip dhcp bind
Bindings from all pools not associated with VRF:
IP address      Client-ID/         Lease expiration     Type       State      Interface
        Hardware address/
        User name
10.2.1.3        01e8.9a8f.98a7.03       Jan 05 2013 02:22 PM    Automatic  Active     Unknown

hsrp is configured...

dsw1#sh stand brie                                                             
                     P indicates configured to preempt.                        
                     |                                                         
Interface   Grp  Pri P State   Active          Standby         Virtual IP      
Vl10        1    110 P Active  local           10.2.1.2        10.2.1.254  

i had an issue with the port channels...  i didn't like their numbering anyway, but l2 switches can have numbers from 1 - 6 only for port channels...  so i did it the way i like to anyway, because i wasn't about to swap the l2's out for 3560's over

that... i made them all lacp as you can see below

you can see my logic here:  http://insearchofthecert.blogspot.com/2012/04/mesh.html





dsw1#sh etherch summ | b Group                                                 
Group  Port-channel  Protocol    Ports                                         
------+-------------+-----------+-----------------------------------------------
1      Po1(SU)         LACP      Fa0/19(P)   Fa0/20(P)                         
2      Po2(SU)         LACP      Fa0/21(P)   Fa0/22(P)                         
3      Po3(SU)         LACP      Fa0/23(P)   Fa0/24(P)  

the difference in the tshoot network is there is no bottom side link between the l2's...

so i made po1 from dsw1 to als1...

po2 forms the X for both sides, and po3 is the distribution side link...

all that's left is the v6 network and gre tunnel...

i'll use a hardware router for the server client off vlan 20 on als2 for completeness, although it really doesn't matter...

i used rapid-pvst+ everywhere... 

it kind of leans to the left a little, but i don't give a shit...

it's got me thinking about the ccie lab configuration section...  i have no idea what to expect from that... i suppose building something like this should be easy enough in 6 hours if everything is pre-addressed, you don't have to screw around with cables, or deleting old configuration already present...  and of course there would be no gns3 to qinq; that eats up time...  i've read it is supposed to be about this many devices, but then there will be qos, and firewalling, maybe some client side mplsvpn, vrf, sla, monitoring, syslog, the list goes on...

this is a small, bumper to bumper enterprise network... in the real world, you'd spend weeks in the lab prepping for a weekend long deployment of something like this... preconfiguring, testing, discussions, meetings...  it's a bit unreasonable...