MGCP Gateways failing over every 5 hours and 1 minute
I am having an issue with all of my MGCP gateways failing over every 5 hours and 1 minute. Every 5 hours and 1 minute interval, I see that my last mgcp traffic elapsed time goes to 31 seconds and then they fail over. This happens on both gateways that are local (on the same switch) as the CCMs and at remote sites.
I have this field notice describing a bug in the SATA RAID controller driver for the DL320 G3. This sounds suspciously like what is happening here:
However, we are running OS 2000.4.2SR3 which includeds the 22.214.171.124 driver which is supposedly the fix for this bug. Also, when I watch the %DiskTime, %DiskWrite Time, and PageFaults/sec as described in the symptoms section, I do not see any spike on the %DiskTime and %DiskWrite Time. I do see constant spikes in the PageFaults/sec all day long and they went espcially high (over 3000) at time of failover.
Is anyone else experiencing this issue? Any idea what it might be? Would downloading the driver directly from HP and installing it rather than using the version included with the OS help?
Re: MGCP Gateways failing over every 5 hours and 1 minute
The publisher was fine. However, I found that although the subscriber had been upgraded to 4000-4.2 sr3, it still had the 126.96.36.199 version of the driver. We attempted to install the driver patch from HP-SATADriver-6.0.82.exe, but it caused the Subscriber to blue screen. We could not boot it in safe mode or from the last know good config. TAC had us change a BIOS setting on the subscriber; it was then able to boot. He then had us re-install the driver upgrade and it took. We have now been almost 8 hours without a failover. Thanks.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.