reset necessary after updating MGC list?

[HossBoss]

I'm adding an ESS into the environment and wondering if I need to reset the chassis after?

current: PE, LSP

future: PE, ESS, LSP

clear mgc list
set mgc list PE, ESS, LSP
copy run start

Is a reset absolutely necessary? I'd like to avoid the down time if at all possible.

thanks!

 

[HossBoss]

Forgot to add that they are G430/450s

 

[ZeroZeroOne]

No reset required since you are changing the running (active) config.
Don't forget to check your recovery options:

# show recovery
RECOVERY TIMES
--------------------------------
Primary Search : 5
Total Search : 10
Transition Point: 1

Set the recovery search times and the transition point of what is used first (PE) and the ESS and LSPs.
(Your times will probably be different)
# set reset primary 5
# set reset total 10
# set reset transition 1

# show mgc list

PRIMARY MGC HOST, Primary Search Time : 5 min(s)
IPv4 Address IPv6 Address
-------------------- ----------------------------------------------
<PE IP Address> -- Not Available --

SECONDARY MGC HOST
IPv4 Address IPv6 Address
-------------------- ----------------------------------------------
<ESS IP Address> -- Not Available --
<LSP IP Address> -- Not Available --
-- Not Available -- -- Not Available --


Should be good to go!

 

[kyle555]

Possibly/probably. Its always been a best practice to clear mgc list, then set the mgc list again. I've seen times where it wouldn't.

Also, unless something changed in CM6, I've always done a reset 4 on the main when adding the 1st ESS. I can't find that in documentation right now, but unless that ESS is up and happy already, it might be something to think about!

 

[montyzummer]

As long as you get file sync you can then do the reset in the maintenace window if required.

You can stop and start the filesyncd process on LSP/ESS by using command
stop –s filesyncd
start -s filesyncd

also check
Verify that the IP address customer LAN interface of both S8xx0 servers are listed in the file
/etc/ecs.conf next to the entries SRAYPA1 and SRAYPA2 in ESS/LSP ( this confirms they see each other)



But hang on are you talking about resetting the gateway or the cm/ess , if the gateway no , if cm ess , if they are all registered and synced , it doesn't matter and is an excellent opportunity to test fail over of ESS and no down time will happen anyway , if i understand correctly and its set up correctly

APSS (SME)
ACSS (SME)
ACIS (UC)

 

[HossBoss]

Thanks for the responses...consensus is that a reboot of the gateway is not necessary when updating the MGC list.

 

[kyle555]

I meant to indicate that I thought you needed to reset 4 on the core active CM to make it play nice with your first ESS and remember reading something about it as late as 5.2 that it was part of the "official" process for getting it up.

Restarting filesyncd makes sense too though!