Sponsored Content
Top Forums Shell Programming and Scripting Failure rate of a node / Data center Post 303020079 by chercheur111 on Thursday 12th of July 2018 05:37:42 PM
Old 07-12-2018
What operating system are you using?


Linux OS (Ubuntu distribution)


What shell are you using?

shell bash

How do you expect to deduce a failure rate from a single point in time? Are you instead maybe looking for a percentage of network node failures at this point in time?


This is only a simple example. I will generate an history of some days.


What output are you hoping to produce from the sample input you have provided?

The MTBF (mean-time-between-failures) of each node.


What have you tried on your own to get the output you want?
 

6 More Discussions You Might Find Interesting

1. Virtualization and Cloud Computing

Cloud Enabling Computing for the Next Generation Data Center

Hear how the changing needs of massive scale-out computing is driving a transfomation in technology and learn how HP is supporting this new evolution of the web. More... (1 Reply)
Discussion started by: Linux Bot
1 Replies

2. HP-UX

Need to set up a HP cluster system in a data center

What are the server requirements, Software requirements, Network requirements etc, Please help me.. as 'm new 'm unable to get things done @ my end alone. Please refrain from typing subjects completely in upper case letters to get more attention, ty. (5 Replies)
Discussion started by: Sounddappan
5 Replies

3. Red Hat

Problem in RedHat Cluster Node while network Failure or in Hang mode

Hi, We are having many RedHat linux Server with Cluster facility for availability of service like HTTPD / MySQL. We face some issue while some issue related to power disturbance / fluctuation or Network failure. There is two Cluster Node configured in... (0 Replies)
Discussion started by: hirenkmistry
0 Replies

4. What is on Your Mind?

Cut Over to New Data Center and Upgraded OS Done. :)

Three days ago we received an expected notice from our long time data center that they were going dark on Sept 12th. About one and a half hours ago, after three days of marathon work, I just cut over the unix.com to a new data center with a completely new OS and Ubuntu distribution. (22 Replies)
Discussion started by: Neo
22 Replies

5. What is on Your Mind?

Resolved: Issue in Server Data Center

Dear All, There was a problem in the data center data, which caused the server to be unreachable for about an hour. Server logs show the server did not crash or go down. Hence, I assume there was a networking issue at the data center. Still waiting for final word on what happened. ... (4 Replies)
Discussion started by: Neo
4 Replies

6. What is on Your Mind?

OUTAGE: Data Center Problem Resolved.

There was a problem with our data center today, creating a site outage (server unreachable). That problem has been resolved. Basically, it seems to have been a socially engineered denial-of-service attack against UNIX.com; which I stopped as soon as I found out what the problem was. Total... (2 Replies)
Discussion started by: Neo
2 Replies
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)
All times are GMT -4. The time now is 02:40 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy