BACKGROUND:
I have my own rack with mixed hardware and it seemed logical to upgrade my code to resemble the CCIE v5 spec with 15.0 and 15.3T. However not all my gear can support the upgrade so I went as high a version of code as possible per platform.
MY HARDWARE:
3x2811 / 3x1841 / 3x1941 / 3x2651XM / 2x3560 / 1x3750 / 1x3750V2
C2800 Software (C2800NM-ADVENTERPRISEK9-M), Version 15.1(4)M7
C1841 Software (C1841-ADVENTERPRISEK9-M), Version 15.1(4)M7
C1900-UNIVERSALK9-M), Version 15.3(3)M2
C3750 Software (C3750-IPSERVICESK9-M), Version 12.2(55)SE8
C3750 Software (C3750-IPSERVICESK9-M), Version 15.0(2)SE5
C3560 Software (C3560-IPSERVICESK9-M), Version 12.2(55)SE8
STATEMENT:
While working on Vol 1 Multicast 8.2 I was trying to set #ip multicast rpf interval per the workbook requirement but my hardware gave me mixed results because I'm running on mixed code (non 12.4T).
EXAMPLE:
Rack1R6(config)#ip multicast rpf ?
multitopology Enable Multicast-Specific RPF Topology
proxy PIM proxy options
select Select table for RPF check
R7(config)#ip multicast rpf ?
mofrr Enable MoFRR
multitopology Enable Multicast-Specific RPF Topology
proxy PIM proxy options
select Select table for RPF check
Rack1SW4(config)#ip multicast rpf ?
multitopology Enable Multicast-Specific RPF Topology
proxy PIM proxy options
select Select table for RPF check
Rack1SW3(config)#ip multicast rpf ?
backoff Backoff delay after unicast routing change
default-distance Distance for the default RPF interface
> interval Periodic RPF check interval
proxy PIM proxy options
QUESTION(s):
1.) Will this become a running theme while trying to study v5 lab on v4 hardware?
I feel like pushing my rack out the window because I spent hours trying not to peak at the solutions guide and review doccd instead but now I know the real cause of my digital pain.
2.) Brian - Will my rack work for the new ine v5 workbooks or will I continue to bump into inconsistencies like this between the books and my gear/code?
3.) Should I roll back my code to 12.4T?
4.) Should I stop labbing for now and read from the ccie book lists and wait for the new ine workbooks to comeout and then readdress this hardware issue then? I'm having a difficult time fusing labbing with reading books together anyway...