Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Catalyst 6500 IOS RPR+ Bootvar sync

I have a 6500 running 12.1-22 and it is configured with RPR+. The configuration is set to sync bootvar with the auto-sync bootvar command however the second MSFC isn't showing the correct bootvar when I issue the SHOW BOOTVAR command. I thought this was supposed to sync automatically. How can I manually sync this?

  • Other Network Infrastructure Subjects
2 REPLIES
VIP Purple

Re: Catalyst 6500 IOS RPR+ Bootvar sync

Hello Jeff,

how do you have the auto-sync configured ?

Can you have a look at this document ?

Configuring RPR and RPR+ Supervisor Engine Redundancy

http://www.cisco.com.ru/univercd/cc/td/doc/product/lan/cat6000/12_1e/swconfig/redund.htm#wp1089808

Regards,

GP

New Member

Re: Catalyst 6500 IOS RPR+ Bootvar sync

Thanks GP, I have read that document. Here's the configuration for my RPR+:

redundancy

mode rpr-plus

main-cpu

auto-sync running-config

auto-sync bootvar

auto-sync standard

As you can see I do have the auto-sync bootvar setting but the bootvar settings are different:

sh bootvar

BOOT variable = sup-bootflash:c6sup22-jsv-mz.121-22.E2.bin,1;slot0:c6sup22-jsv-mz.121-22.E2.bin,1;slot0:c6sup22-jsv-mz.121-19.E1a,1

CONFIG_FILE variable =

BOOTLDR variable =

Configuration register is 0x2102

Standby is up

Standby has 458752K/65536K bytes of memory.

Standby BOOT variable = bootflash:c6sup22-jsv-mz.121-22.E2.bin,1;slot0:c6sup22-jsv-mz.121-22.E2.bin,1;slot0:c6sup22-jsv-mz.121-19.E1a,1

Standby CONFIG_FILE variable =

Standby BOOTLDR variable =

Standby Configuration register is 0x2102

Do you think issuing the copy running-config startup-config will sync the bootvar information?

Thanks,

-Jeff

210
Views
0
Helpful
2
Replies
This widget could not be displayed.