Sponsored Content
Operating Systems AIX HEA configuration on managed node. Post 302932360 by bakunin on Wednesday 21st of January 2015 05:29:10 AM
Old 01-21-2015
Quote:
Originally Posted by thisissouvik
what does "Flow Control Enabled" checkbox help us with if opted for?
You need to enable it, not only here but also on the switch and every other network component involved. Enabling it enhances throughput considerably by eliminating retransmissions.

See a detailed description here.

I hope this helps.

bakunin
 

9 More Discussions You Might Find Interesting

1. Web Development

managed service reccomendations

Dunno If its ok to post this, but I am looking for a company to manage our linux server. If the company is a specialist in security issues then that would be ideal Thanks Ed (5 Replies)
Discussion started by: edzillion
5 Replies

2. AIX

hacmp in a 7 node configuration ?

Hi Guys, I have to design a multinode hacmp cluster and am not sure if the design I am thinking of makes any sense. I have to make an environment that currently resides on 5 nodes more resilient but I have the constrain of only having 4 frames. In addition the business doesnt want to pay for... (7 Replies)
Discussion started by: zxmaus
7 Replies

3. AIX

Hea software error

I´m having the problem listed below. The server is a Blade JS22 in a BladeCenter S chassis. My system is up to date with AIX 5.3 TL11 (5300-11-01-0944) and i have already updated my microcode to the recommended version by the vendor. If you want we can use spanish for this post. In... (3 Replies)
Discussion started by: diesan
3 Replies

4. AIX

HACMP 5.4.1 Two-Node-Cluster-Configuration-Assistant fails

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

5. Solaris

SVM metaset on 2 node Solaris cluster storage replicated to non-clustered Solaris node

Hi, Is it possible to have a Solaris cluster of 2 nodes at SITE-A using SVM and creating metaset using say 2 LUNs (on SAN). Then replicating these 2 LUNs to remote site SITE-B via storage based replication and then using these LUNs by importing them as a metaset on a server at SITE-B which is... (0 Replies)
Discussion started by: dn2011
0 Replies

6. AIX

P770 HEA lose conectivity while while its very active

Dears we have p770 running in AIX 5.3 TL11 , oracle installed in the server , some times the HEA will lose the connection for some reason we try with our local support to fix the issue but there is no luck , we change the HEA hardware but the problem still , it was running with firmware... (1 Reply)
Discussion started by: thecobra151
1 Replies

7. Homework & Coursework Questions

Accessing one UNIX node from another node of the same server

Hi Experts, I am in need of running a script from one node say node 1 via node 2. My scheduling tool dont have access to node2 , so i need to invoke the list file from node1 but the script needs to run from node2. because the server to which i am hitting, is having access only for the node... (5 Replies)
Discussion started by: arun1377
5 Replies

8. HP-UX

Mount FIle systems from node-1 onto node-2

Hi, We have HP UX service guard cluster on OS 11.23. Recently 40+ LUNs presented to both nodes by SAN team but I was asked to mount them on only one node. I created required VGs/LVs, created VxFS and mounted all of them and they are working fine. Now client requested those FS on 2nd node as... (4 Replies)
Discussion started by: prvnrk
4 Replies

9. AIX

Command to see the status of managed node from CLI of HMC?

Folks, Asking a silly question - is there a way to know the status(Power Off/Running) of a managed node from CLI of HMC, alike the way we see it for the LPARs running on the node from 'vtmenu'? Most of us use the UI to see the status of the LPARs/Managed node - but just inquisitive to know if... (4 Replies)
Discussion started by: thisissouvik
4 Replies
scconf_quorum_dev_scsi(1M)				  System Administration Commands				scconf_quorum_dev_scsi(1M)

NAME
scconf_quorum_dev_scsi - Add and remove shared SCSI quorum devices and change various SCSI cluster quorum configuration properties or states. SYNOPSIS
scconf {-a|-c|-r} -q globaldev=devicename otheroptions scconf {-a|-c|-r} -q name=devicename otheroptions DESCRIPTION
Note - Beginning with the Sun Cluster 3.2 release, Sun Cluster software includes an object-oriented command set. Although Sun Cluster software still supports the original command set, Sun Cluster procedural documentation uses only the object-oriented command set. For more infor- mation about the object-oriented command set, see the Intro(1CL) man page. A SCSI quorum device is considered to be any Sun Cluster supported, attached storage that is connected to two or more nodes of the cluster. The device must be managed by DID, and the device name that is provided must be a DID device name. The SCSI quorum device has no other properties that can be specified. OPTIONS
The following options are specific to shared disk quorum devices. See scconf(1M) for the list of supported generic options. See scconf_quo- rum_dev_netapp_nas(1M) for options that are specific to NAS quorum devices. The add and remove forms of the command are used to add and remove shared quorum devices to or from the configuration. The change form of the command is used for changing various properties of cluster quorum configuration. The -q quorum-options available for each of the three forms of the command can be used to change the cluster quorum configuration are as follows: Add a shared quorum device: -q -a globaldev=devicename[, node=node,node=node[, ...]] or -q -a name= devicename,type=scsi or -q -a autoconfig[,noop] Change a property or state of quorum configuration: -q -c globaldev=devicename,{maintstate | reset} or -q -c autoconfig[,noop] Remove a shared quorum device: -q -r globaldev=devicename or -q -r name=devicename autoconfig When used with the add form of the command, automatically chooses and assigns one quorum device in the two-node cluster. The quorum device is chosen from the available devices. If a quorum device is already configured, the command aborts. When used with the change form of the command, automatically chooses and assigns one device that replaces all existing quorum devices in the two-node cluster. The quorum device is chosen from the available devices. All available devices in the cluster must be qualified to be a quorum device. The autoconfig suboption does not assess whether an available device is qualified to be a quorum device. If the cluster contains more than two nodes, the autoconfig suboption makes no changes to the quorum configuration. Do not use the autoconfig suboption if you intend to configure a NAS device as quorum. [,noop] Is valid with the autoconfig suboption. The command prints to standard output the list of quorum devices that the autoconfig suboption would add or change. The autoconfig,noop suboption makes no changes to the quorum configuration. When scconf is interrupted or fails while performing quorum-related operations, quorum configuration information can become inconsistent in the cluster configuration database. If an inconsistency occurs, either run the same scconf command again or run it with the reset option to reset the quorum information. With the add form of the command, if a name is specified without a node list, the quorum device is added with a port defined for every node to which the device is attached. But, if a node list is given, at least two nodes must be provided, and each node in the list must be ported to the device. EXAMPLES
Example 1 Adding SCSI Quorum Devices The following scconf commands adds a SCSI quorum device. -a -q globaldev=/dev/did/rdsk/d4s2 or -a -q name=/dev/did/rdsk/d4s2,type=scsi Example 2 Changing SCSI Quorum Devices The following scconf command changes a SCSI quorum device configuration. -c -q globaldev=/dev/did/rdsk/d4s2,reset or -c -q name=/dev/did/rdsk/d4s2,reset Example 3 Removing SCSI Quorum Devices The following scconf command removes the SCSI quorum device. qd1. -r -q globaldev=qd1 ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWsczu | +-----------------------------+-----------------------------+ |Interface Stability |Evolving | +-----------------------------+-----------------------------+ SEE ALSO
Intro(1CL), clquorum(1CL), cluster(1CL), scconf(1M), scconf_quorum_dev_netapp_nas(1M) Sun Cluster 3.2 10 Apr 2006 scconf_quorum_dev_scsi(1M)
All times are GMT -4. The time now is 11:06 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy