RHEL 5 Fiber Chanel Multipath Configuration with Sun StoreEdge 6000 arrays.
A step by step guide on how to attach a Sun StorEdge 6000 series array to a Red Hat Enterprise Linux Server (Sun Hardware or not). Note that Red Hat RDAC drivers can be found at http://www.lsi.com/rdac/ds4000.html
In a RHEL 5 box, I have just added new multipath configurations in /etc/multipath.conf :
wwid... (0 Replies)
I'm wondering if anyone knows whether Solaris IPMP can be configured such that the IPs of the physical NICs are not available to applications when using IP4 or if the group address and the underlying physical address are always present?
Thanks. (3 Replies)
I am running "Red Hat Enterprise Linux Server release 6.4 (Santiago)"
The root Filesystem is currently part of the Multipath configuration and I need to remove it without rebooting the production Server.
The wwid I want to remove from Multipathing is the last one i the list of... (3 Replies)
Can someone please help me configuring RIP (Routing Information Protocol v2 ). I have tried few manuals and posts from networking sites and i didnt get a clear picture.
This is what i have done:
1. Installed routed package and started routed service.
however, Dynamic routes are... (1 Reply)
I have installed RHEL 6.0 on my lappy in a separate partion with windows 7 on the hardware(not using VMWARE).Now kindly help me to active network configuration in that?????Is it require to have LINUX wireless drivers???? (1 Reply)
I am looking at the specific configuration settings for multipath.conf on RHEL5.5.
In particular i was looking at the max_fds setting. Can anyone tell me the max number of open file descriptors that the RHEL5.5 system can have?
It has been set previously to 8192, and i was... (4 Replies)
I'm trying to configure NTP client, however it failes to sync correctly.
Even after I manually set the time, once it connects with the NTP server, it pushes the time ahead by 4 hours.
We have set an AIX host as NTP server. It works fine for other AIX hosts, however fails on RHEL 5.4
... (4 Replies)
Discussion started by: max_min
LEARN ABOUT CENTOS
KSC(1) User Commands KSC(1)NAME
ksc - Linux kernel module source checker
ksc [ -d | --directory ] DIRECTORY
ksc [ -k | --ko ] FILE
KSC accepts command-line arguments, and has both a long and short form usage. You can use either style or combine them to specify
options. When the tool is run with kernel module sources it checks for all four architectures, and when run with binary kernel modules, it
checks for the specific architecture for which the binary was built.
Valid RHEL whitelist releases are rhel6.0, rhel6.1, rhel6.2, rhel6.3, rhel6.4
show this help message and exit
-c CONFIG, --config=CONFIG
path to the local ksc.conf file. If not specified the tool tries to read from ~/ksc.conf and if that is also not found then from
-d DIRECTORY, --directory=DIRECTORY
path to the directory
to create text files to be used internally.
-k KO, --ko=KO
path to the ko file. You should either use -d or -k to run the KSC tool, but not both. If both -d and -k option is used at the
same time then only -d is used and the -k option is discarded.
-n RELEASENAME, --name=RELEASENAME
Red Hat release against which the bug is to be filed. Default value is 6.5
-p PREVIOUS, --previous=PREVIOUS
path to the previous resultset file and submit it as a bug to Red Hat Bugzilla.
-r RELEASE, --release=RELEASE
RHEL whitelist release used for comparison
Submits the report to the Red Hat bugzilla (https://bugzilla.redhat.com). The credentials need to be in the /etc/ksc.conf file. The
tool will prompt for bugzilla password.
The configuration file looks like below:
Prints KSC version number
ksc - Version 0.9.11 Feb 2014 KSC(1)