mac table...

one of my mini-projects over the next year is to read through the pdf for 3560/3750 that is available on the doc cd, here...

you can download the whole thing... that is almost 1500 pages of yummy goodness and it covers the waterfront...  it's called a configuration guide but it is packed with everything switch... and it will be available during the ccie lab exam... hello... anybody out there? you gotta love yourself some doc cd, baby...

those damn 17 addresses...

IEEE 802.1D specifies 17 multicast addresses, ranging from 0x00180C2000000 to 0x0180C2000010, to be used by different bridge protocols. These addresses are static addresses that cannot be removed.

Regardless of the spanning-tree state, each switch in the stack receives but does not forward packets destined for addresses between 0x0180C2000000 and 0x0180C200000F.

If spanning tree is enabled, the CPU on the switch or on each switch in the stack receives packets destined for 0x0180C2000000 and 0x0180C2000010. If spanning tree is disabled, the switch or each switch in the stack forwards those packets as unknown multicast addresses.

you can count em if you want to...

dlsw1#sh mac add | inc CPU                                                     
 All    0100.0ccc.cccc    STATIC      CPU                                      
 All    0100.0ccc.cccd    STATIC      CPU                                      
 All    0180.c200.0000    STATIC      CPU                                      
 All    0180.c200.0001    STATIC      CPU                                      
 All    0180.c200.0002    STATIC      CPU                                      
 All    0180.c200.0003    STATIC      CPU                                      
 All    0180.c200.0004    STATIC      CPU                                      
 All    0180.c200.0005    STATIC      CPU                                      
 All    0180.c200.0006    STATIC      CPU                                      
 All    0180.c200.0007    STATIC      CPU                                      
 All    0180.c200.0008    STATIC      CPU                                      
 All    0180.c200.0009    STATIC      CPU                                      
 All    0180.c200.000a    STATIC      CPU                                      
 All    0180.c200.000b    STATIC      CPU                                      
 All    0180.c200.000c    STATIC      CPU                                      
 All    0180.c200.000d    STATIC      CPU                                      
 All    0180.c200.000e    STATIC      CPU                                      
 All    0180.c200.000f    STATIC      CPU                                      
 All    0180.c200.0010    STATIC      CPU                                      
 All    ffff.ffff.ffff    STATIC      CPU     

v6l3 plus tunnel...

adjusted the topology...

R1#sh ipv6 route ospf

OE2 2002::1:1/128 [110/20]
     via FE80::C802:14FF:FE99:8, Serial1/0
OE2 2002::1:3/128 [110/20]
     via FE80::C802:14FF:FE99:8, Serial1/0
OI  2026::1:0/122 [110/192]
     via FE80::C802:14FF:FE99:8, Serial1/0
OE2 2026::2:0/122 [110/20]
     via FE80::C802:14FF:FE99:8, Serial1/0
OE2 2026::3:0/122 [110/20]
     via FE80::C802:14FF:FE99:8, Serial1/0
OI  2026::34:0/122 [110/2128]
     via FE80::C802:14FF:FE99:8, Serial1/0

the connected statement is essential...

R4#sh run | sec router
router ospf 6
 network 4.4.4.0 0.0.0.255 area 34
 network 10.1.1.8 0.0.0.3 area 34
ipv6 router ospf 6
 router-id 0.0.0.4
 redistribute rip ripzone include-connected
ipv6 router rip ripzone
 redistribute ospf 6 metric 5 include-connected

but now it's back to the drawing board on ipv6 tunneling...  one thing labs will surely do is identify a weakness... and there you have it...

and below is everything you hoped you would never have to know about tunneling ipv6...

http://www.cisco.com/en/US/docs/ios-xml/ios/ipv6/configuration/12-4t/ip6-tunnel.html#GUID-1E4B9CE5-E384-4AF3-B371-3DFF35034349

this reference is from what is called the doc cd... from here on i will only refer to it as the doc cd...

go here for information on the doc cd...

http://insearchofthecert.blogspot.com/2012/11/doc-cd-ccie-lab.html

once there you will begin to get comfortable with the idea of eternity...

trust that this will never end...

can you guess what i'll be doing this week?

doc cd... ccie lab...

for the ccie lab, you might say it's an open book exam because the doc cd http://www.cisco.com/cisco/web/psa/reference.html is available for use... however, according to brian mcgahan over at INE, the technology section, which includes design guides, configuration examples, white papers, et al, is not available during the lab... he points it out as a great study aid in the beginning of the video http://www.ine.com/all-access-pass/training/playlist/ccie-routing-switching-advanced-technologies-class/using-the-cisco-documentation-2.html but it can't be used...

here's the challenge... if you are like me you rely heavily on search for expedient answers to stupid questions... search is off limits for the lab... searching on a page, however is not... anyway, i need to get used to using the resources that will be available during the lab...  i'm going to start forcing myself to use the so called doc cd as much as possible from now on...

i'm certain it won't be long befor i yank all my hair out... but i'm gonna try... happy doc cd'ing...