SSI or not??

 
Thread Tools Search this Thread
Special Forums UNIX and Linux Applications High Performance Computing SSI or not??
Prev   Next
# 1  
Old 07-02-2012
SSI or not??

I'm new to HPC so forgive me if this question is extremely simple.

I have a cluster and each node has multiple NICs. I need the master to be able to see the nodes NICs as if they were it's own. The vision is being able to run ifconfig and see a bunch of ethX entries on the master when in fact say eth1 - eth15 are located on other nodes.

While researching a solution I came across OpenSSI and thought this would provide the correct functionality, but the only thing I can do is list the local interfaces on nodes with the 'node X ifconfig' command.

Is SSI even the technology that'll make node interfaces look local to the master or am I barking up the wrong tree? Does anyone have experience with a system as described?

Thanks!
 
Login or Register to Ask a Question

Previous Thread | Next Thread

2 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

SSI related Unix In (link) support needed

I have multiple web sites and have SSI all working fine! but I want a script that allows me to place a SSI script (or .html) on any web site within my server - One problem, SSI is limited to files located within the file structure - I want to access a file outside, (but still on my server) I found... (1 Reply)
Discussion started by: johnzule
1 Replies

2. UNIX for Dummies Questions & Answers

the unix answer to SSI?

On websites I build one thing I like to use is SSI to make it easier for the owner of the site to update parts of it him/herself. So the text of a page is keep in a simple .txt file, which the main page calls. Unix does not support this (I'm told), is there a similar system I can use with UNIX?... (1 Reply)
Discussion started by: garrettcarr
1 Replies
Login or Register to Ask a Question
cmhaltnode(1m)															    cmhaltnode(1m)

NAME
cmhaltnode - halt a node in a high availability cluster SYNOPSIS
cmhaltnode [-f] [-v] [-t] [node_name...] DESCRIPTION
cmhaltnode causes a node to halt its cluster daemon and remove itself from the existing cluster. To halt cluster on the node, a user must either be superuser(UID=0), or have an access policy of FULL_ADMIN allowed in the cluster configu- ration file. See access policy in cmquerycl. When cmhaltnode is run on a node, the cluster daemon is halted and, optionally, all packages that were running on that node are moved to other nodes if possible. If node_name is not specified, the cluster daemon running on the local node will be halted and removed from the existing cluster. If you issue this command while a cluster is still in the process of forming, the command will fail with the message "Unable to connect to daemon." If this happens, wait for the cluster to form successfully, then issue the command again. Options cmhaltnode supports the following options: -f Force the node to halt even if there are packages or group members running on it. The group members on the node will be terminated. The halt scripts for all packages running on the node will be run; based on priority or dependency relation- ships, this may affect packages on other nodes. In other words, packages on other nodes may either start or halt based on this package halting. If the package configuration and current cluster membership permit, and if the package halt script succeeds, the packages will be started on other nodes. Without this option, if packages are running on the given node, the command will fail. If a package fails to halt, the node halt will also fail. -v Verbose output will be displayed. -t Test only. Provide an assessment of the package placement without affecting the current state of the nodes or packages. This option validates the node's eligibility with respect to the package dependencies as well as the external dependencies such as EMS resources, package subnets, and storage before predicting any package placement decisions. If there is a pack- age in maintenance mode running on the nodes being halted, the package will always be halted and not failover to another node; the report will not display an assessment for that package. node_name... The name of the node(s) to halt. RETURN VALUE
cmhaltnode returns the following value: 0 Successful completion. 1 Command failed. EXAMPLES
Halt the cluster daemon on two other nodes: cmhaltnode node2 node3 AUTHOR
cmhaltnode was developed by HP. SEE ALSO
cmquerycl(1m), cmhaltcl(1m), cmruncl(1m), cmrunnode(1m), cmviewcl(1m), cmeval(1m). Requires Optional Serviceguard Software cmhaltnode(1m)