Hi Adu,

I’m not quite sure myself… I would suggest you post your question in the discussion forums where I’m sure someone will respond.

http://forums.networkinfrastructure.info/nortel-ethernet-switching/

Good Luck!

Could you please tell me. What is command line using for see HA syncing.

Thanks.

Hi Prince,

I don’t believe ‘d’ is for the day, although I’m not 100% sure what it’s for.

tz dst-end M11.1.0/0200
tz dst-start M3.2.0/0200

M11 – November
1 – First Sunday
0 – ?? delay perhaps
0200 – 2:00AM

M3 – March
2 – 2nd Sunday
0 – ??
0200 – 2:00AM

Cheers!

I’m having problems with the following command:
config bootconfig tz dst-start [Mm.n.d/hhmm | MMddhhmm]

What is ‘n’ given that ‘d’ is presumably day?
M3.?.14/0200

Thanks.

I’m running 4.1.8.2 version. I found this no Release Notes 4.1.0 “The following protocols, features and modules are not available with High
Availability mode:
…
Multicast dynamic routing protocols (DVMRP, PIM-SM, PIM-SSM, PGM)
• VRRP Fast Advertisement Interval
…”

And I found this on Release Notes 7.0 “For Release 7.0, HA-CPU supports the following in Hot Standby mode:
• platform configuration
• Layer 2 protocols: IGMP, STP, MLT, SMLT, ARP, LACP, VLACP
• Layer 3 protocols: RIP, OSPF, VRRP, RSMLT, VRF Lite
HA-CPU supports the following in Warm Standby mode. After failover,
these protocols are restarted:
• DVMRP, PIM-SM, PIM-SSM”

Now I have HA-CPU enabled (hot standby), I think it is the reaseon beacuse of I saw multicast protocols disabled. I´ll be disabling HA-CPU (warm standby) and I´ll see the effect.

I´m understanding multicast L3 protocols are not supported in hot standby mode enabled (config bootconfig flags ha-cpu true).

Thanks for your comments!

Hi Alex,

What version of software are you running? I believe the latest software release (v7.0) now supports all protocols including IPv6 in an HA configuration. In older versions the protocol will still work but it’s not HA, meaning the protocol will need to restart if there is a CPU/SF switchover.

Good Luck!

I have a full-mesh network and I need to configure DVMRP or PIM protocols. Multicast, DVMRP, PIM and PGM protocols are not available on my full-msh devices.

All my ERS 8600’s are in HA (config bootconfig flags ha-cpu true). I’m not really sure if I need to disable ha-cpu.

Tanks in advance.

Hi David,

You need don’t necessarily need to run in an HA mode. It’s a design and operational consideration. You should examine the pros and cons of running in “standby” mode against running in “HA” mode.

You want “savetostandby” enabled no matter what mode you are running. Anytime you save the configuration, the configuration will be saved to both the primary and standby CPU.

If you want HA mode you need to enable HA mode on each CPU and then reboot the CPU.

Good Luck!

If I have 2 CPUs, it’s recommended to activate the flags “ha-cpu” to have high availability and the “savetostandby” to save config both CPUs.

Now my configuration is:

ha-cpu false (failover not working?)
savetostandby false

Thanks!

The command “config bootconfig flags savetostandby true” just instructs the switch to save the switch configuration to both the primary CPU and the standby CPU whenever you save the configuration file. If that option isn’t enabled you need to manually save the configuration file to the standby CPU every time you save it to the primary CPU.

There are a few protocols which aren’t supported in HA mode but for the most part it’s a hitless event (less than 50ms fail over).

Good Luck!

The command you referred to, “config bootconfig flags telnetd true” will allow you to telnet into the 869xSF (CPU). With two 869xSFs in an ERS 8610 chassis they will operate in cold standby mode with a brief reset of the switch during fail over. If you are interested in the high-availability mode then you need to issue the following command, “config bootconfig flags ha-cpu true” and reset both CPUs.

There are links to the Tek-Tips forums on the right hand side of this page.

Thanks for the comment!