12-15-2011 05:30 AM
Hello Everyone
This is my first post on the Support Community, so please allow me some room for not following etiquette. I have recently taken delivery of a replacement 4710 as one half of a pair. The unit that has been replaced was the primary in the pair. The current active 4710 was the secondary in the pair. I am looking for an installation guide that specifically deals with reconnecting peers, with reference to:
1) OS differences
2) Config sync
3) Failover timings
The working 4710 is on:- c4710ace-t1k9-mz.A4_1_1.bin
Replacement:- c4710ace-mz.A4_2_0.bin
Working
FT Group : 1
Configured Status : in-service
Maintenance mode : MAINT_MODE_OFF
My State : FSM_FT_STATE_ACTIVE
My Config Priority : 50
My Net Priority : 50
My Preempt : Disabled
Peer State : FSM_FT_STATE_UNKNOWN
Peer Config Priority : Unknown
Peer Net Priority : Unknown
Peer Preempt : Unknown
Peer Id : 1
No. of Contexts : 1
ft interface vlan 1111
ip address 192.168.254.2 255.255.255.252
peer ip address 192.168.254.1 255.255.255.252
no shutdown
ft peer 1
heartbeat interval 300
heartbeat count 10
ft-interface vlan 1111
ft group 1
peer 1
no preempt
priority 50
peer priority 99
associate-context Admin
inservice
My concern is the mismatch in OS, yet the USB ports seem to be unsupported. I could configure the replacement with a lower priority, but would like to find some information on if this OS mismatch will cause issues and how best to copy from one device to another.
And yes, as you can probably gather, these devices are not my strongpoint, they were a legacy left by someone else with no documentation or explanations.
Thanks for your time
12-15-2011 08:57 AM
A penny dropped in the back of my mind, I brought up the management interface and set up a TFTP server locally, so, I have coped the image across. From here, I am going to reapply the config but lower the FT priority so that failover does not take place
Fingers crossed.
12-15-2011 01:17 PM
put the same OS.
Then just configure basic connectivity, basic HA parameter and ft group for admin context only. Everything else will be synchronized.
usually I use the following file by copy/paste and I plug the box. Notice the "no preempt" in the ft group.
interface gigabitEthernet 1/1
channel-group 1
no shutdown
interface gigabitEthernet 1/2
channel-group 1
no shutdown
interface gigabitEthernet 1/3
channel-group 1
no shutdown
interface gigabitEthernet 1/4
channel-group 1
no shutdown
interface port-channel 1
ft-port vlan 98
port-channel load-balance src-dst-port
no shutdown
ft interface vlan 98
ip address 10.123.98.251 255.255.255.0
peer ip address 10.123.98.250 255.255.255.0
no shutdown
exit
ft peer 1
heartbeat interval 100
heartbeat count 10
ft-interface vlan 30
exit
ft group 1
peer 1
no preempt
priority 110
peer priority 120
associate-context Admin
inservice
exit
12-16-2011 02:35 AM
Hi Surya
Thanks for the reply, good to know about only creating the Admin context. I have set the priority lower on the replacement device and will just have that as standby now. Both have the 1gig license.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide