12-22-2009
i've done probe based ipmp. same adapters for me. e1000g0-3. and i use a "internal only" network for public and clusterinterconnect. so no traffic to the outside world.
what instructions do you mean?
10 More Discussions You Might Find Interesting
1. HP-UX
Hi,
Please advise me whereas I have two node cluster server configured with MC/SG. Application and DB are running on Node 1, while Node 2 is standby.
All the volume group devices are part of cluster environment. There is only one package running at node 1.
Node 2 is having the problem to... (1 Reply)
Discussion started by: rauphelhunter
1 Replies
2. AIX
This post just as a follow-up for thread https://www.unix.com/aix/115548-hacmp-5-4-aix-5300-10-not-working.html: there was a bug in the clcomdES that would cause the Two-Node-Cluster-Configuration-Assistant to fail even with a correct TCP/IP adapter setup. That affected HACMP 5.4.1 in combinatin... (0 Replies)
Discussion started by: shockneck
0 Replies
3. Solaris
Hello
I have problem with scinstall. I found information that i should`t configure public network before using scinstall.
Each node configuration:
4 node, 3 network adapter on each node. 1 for public adapter and 2 for cluster interconnect. Two switches.
After scinstall first node is... (1 Reply)
Discussion started by: time0ut
1 Replies
4. Solaris
Need some one to explain "In cluster configuration ora* VGs are not controlled by VCS". Actually, I am not aware of this.
Thanks,
Rama (0 Replies)
Discussion started by: ramareddi16
0 Replies
5. Solaris
I am using VMware Workstation-7 on Windows-XP host .
I am trying to configure Solaris 10-X86 guest os based 2 nodes Sun Cluster .
I have added one extra Virtual Lan adapter on my VMware with another subnet (that I would like to put for SUN Cluster private communication).
I have... (0 Replies)
Discussion started by: sanjee
0 Replies
6. UNIX for Advanced & Expert Users
Hi - Please help me to understand the Veritas Cluster fail-over capability.
We configured oracle database file system on veritas cluster file system and it is automatically failing-over from node 1 to node 2.
Does Veritas cluster softward have any option to fail-back from node 2 to node 1... (6 Replies)
Discussion started by: Mansoor8810
6 Replies
7. Red Hat
Hi Everybody,
I would like to know meaning of following parameters in cluster.conf file in linux
<device name="blade_fence" blade="2" option="off"
<clusternode name="Blade1-int" votes="1" nodeid="1">
what do you mean by "option=off" and "votes=1"
Thanks (1 Reply)
Discussion started by: mastansaheb
1 Replies
8. UNIX and Linux Applications
Hi Experts,
I have question regarding linux cluster managment on Red Hat 5.x server. When I try to install 'luci' or 'ricci' in one of our linux servers it is giving me below error:-
yum install luci
Loaded plugins: katello, product-id, rhnplugin, security, subscription-manager
Updating... (0 Replies)
Discussion started by: Amey Joshi
0 Replies
9. Emergency UNIX and Linux Support
Hello HP-UX experts,
Server = rx8640 Node partition
OS = HP-UX 11.23
arch = IA64
Network switch = Foundry 16 port switch (1Gbps)
Existing configuration: Tough to explain as it is very messy (see below for the link of zip of network related fles). 2 x 2Gbps aggregates configured some time... (1 Reply)
Discussion started by: prvnrk
1 Replies
10. Red Hat
why does my cluster form but fail after a few minutes, or why do my multicast communications stop working after a short amount of time? (1 Reply)
Discussion started by: gema.utama
1 Replies
LEARN ABOUT CENTOS
tapset::ioscheduler
tapset::ioscheduler(3stap) tapset::ioscheduler(3stap)
NAME
tapset::ioscheduler - systemtap ioscheduler tapset
DESCRIPTION
This family of probe points is used to probe IO scheduler activities.
ioscheduler.elv_next_request
Fires when a request is retrieved from the request queue
See probe::ioscheduler.elv_next_request(3stap)
for details.
ioscheduler.elv_next_request.return
Fires when a request retrieval issues a return signal
See probe::ioscheduler.elv_next_request.return(3stap)
for details.
ioscheduler.elv_completed_request
Fires when a request is completed
See probe::ioscheduler.elv_completed_request(3stap)
for details.
ioscheduler.elv_add_request.kp
kprobe based probe to indicate that a request was added to the request queue
See probe::ioscheduler.elv_add_request.kp(3stap)
for details.
ioscheduler.elv_add_request.tp
tracepoint based probe to indicate a request is added to the request queue.
See probe::ioscheduler.elv_add_request.tp(3stap)
for details.
ioscheduler.elv_add_request
probe to indicate request is added to the request queue.
See probe::ioscheduler.elv_add_request(3stap)
for details.
ioscheduler_trace.elv_completed_request
Fires when a request is
See probe::ioscheduler_trace.elv_completed_request(3stap)
for details.
ioscheduler_trace.elv_issue_request
Fires when a request is
See probe::ioscheduler_trace.elv_issue_request(3stap)
for details.
ioscheduler_trace.elv_requeue_request
Fires when a request is
See probe::ioscheduler_trace.elv_requeue_request(3stap)
for details.
ioscheduler_trace.elv_abort_request
Fires when a request is aborted.
See probe::ioscheduler_trace.elv_abort_request(3stap)
for details.
ioscheduler_trace.plug
Fires when a request queue is plugged;
See probe::ioscheduler_trace.plug(3stap)
for details.
ioscheduler_trace.unplug_io
Fires when a request queue is unplugged;
See probe::ioscheduler_trace.unplug_io(3stap)
for details.
ioscheduler_trace.unplug_timer
Fires when unplug timer associated
See probe::ioscheduler_trace.unplug_timer(3stap)
for details.
SEE ALSO
probe::ioscheduler.elv_next_request(3stap), probe::ioscheduler.elv_next_request.return(3stap),
probe::ioscheduler.elv_completed_request(3stap), probe::ioscheduler.elv_add_request.kp(3stap),
probe::ioscheduler.elv_add_request.tp(3stap), probe::ioscheduler.elv_add_request(3stap),
probe::ioscheduler_trace.elv_completed_request(3stap), probe::ioscheduler_trace.elv_issue_request(3stap),
probe::ioscheduler_trace.elv_requeue_request(3stap), probe::ioscheduler_trace.elv_abort_request(3stap),
probe::ioscheduler_trace.plug(3stap), probe::ioscheduler_trace.unplug_io(3stap), probe::ioscheduler_trace.unplug_timer(3stap), stap(1),
stapprobes(3stap)
IBM
--- tapset::ioscheduler(3stap)