We recently experienced a Cisco network issue which prevented all
nodes in that subnet from accessing the default gateway for about a
minute.
The Solaris nodes which run probe-based IPMP reported that all
interfaces had failed because they were unable to ping the default
gateway; however, they
I would be more concerned about future failures being handled properly.
If you were able to take out all networks from all nodes at same time,
you have a SPOF. If this was a one time maintenance upgrade to your
network gear and not a normal event, setting VCS to not respond to
network events means
Some notes inline.
On Mon, Oct 20, 2008 at 7:37 AM, Paul Robertson
[EMAIL PROTECTED] wrote:
We recently experienced a Cisco network issue which prevented all
nodes in that subnet from accessing the default gateway for about a
minute.
The Solaris nodes which run probe-based IPMP reported
Buddy,
Thanks for the info.
The FaultPropagation=0 idea is a good one, but it applies at the
service group level, and cannot be set only for specified resources or
resource types. It's probably better than my ToleranceLimit approach,
since it results in a resfault and will therefore run our
If you only have 1 router (which is very common) in your subnet then the
router can possibly be a SPOF for IPMP. Here's how you can setup up more
targets for the IPMP to probe so that the router is not a SPOF.
How to Manually Specify Target Systems for Probe-Based Failure Detection
1.
Yes always have 2 interconnect switches for sure. Also if you switch
interconnect to UDP for Oracle, it will still work with a few modifications
using 2 switches.
For me having 2 switches for public solved most networking blunders. IT is
OK cluster wise if the DG goes away. Traffic just stops,
