path_grouping_policy multibus
rr_min_io 100
rr_weight uniform
failbackimmediate
}
}
blacklist {
devnode ^(dasd)[a-f]*
}
Sollenberger, Justin W Mr CIV US DISA CDB24
justin.sollenber...@csd.disa.mil 6/11/2009 12
in my private message earlier.
Deric
Sollenberger, Justin W Mr CIV US DISA CDB24
justin.sollenber...@csd.disa.mil 6/16/2009 9:36 AM
Deric,
Thanks for the response. I believe that is the issue, but I am unsure
how to correct the mess that I'm in.
I tried adjusting the lvm.conf, but because my
We have several SLES 10 SP2 guests that are using FCP LUNS. The OS is
installed on 3390's and the LUNS are used to store the customer's data.
Early this morning we lost one of the paths. Some of our systems
reacted as I would have expected but others did not. The ones that
reacted oddly would
We are currently running a SLES 10 SP2 guest (hostx) with access to
three networks (eth0, eth1, eth2). The issue we are having is that the
default route is not correct after an ipl. If I delete the incorrect
route (using: route del) and add the correct route (using: route add)
everything works
Thanks to all who replied. I was able to get it working properly by
removing all of the default routes except for one. I also replaced
those default routes (in the ifroute files) with the other more specific
routes.
Now my route table look like this:
Kernel IP routing table
Destination
