Sponsored Content
Top Forums Shell Programming and Scripting Failure rate of a node / Data center Post 303020498 by chercheur111 on Saturday 21st of July 2018 07:12:13 AM
Old 07-21-2018
Please, can you explain me why we have this value:


127.0.0.1 = 0

?
 

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
MRINFO(8)						      System Manager's Manual							 MRINFO(8)

NAME
mrinfo - Displays configuration info from a multicast router SYNOPSIS
/usr/sbin/mrinfo [ -d debug_level ] [ -r retry_count ] [ -t timeout_count ] multicast_router DESCRIPTION
mrinfo attempts to display the configuration information from the multicast router multicast_router. mrinfo uses the ASK_NEIGHBORS IGMP message to the specified multicast router. If this multicast router responds, the version number and a list of their neighboring multicast router addresses is part of that response. If the responding router has a recent multicast version num- ber, then mrinfo requests additional information such as metrics, thresholds, and flags from the multicast router. Once the specified mul- ticast router responds, the configuration is displayed to the standard output. INVOCATION
"-d" option sets the debug level. When the debug level is greater than the default value of 0, addition debugging messages are printed. Regardless of the debug level, an error condition, will always write an error message and will cause mrinfo to terminate. Non-zero debug levels have the following effects: level 1 packet warnings are printed to stderr. level 2 all level 1 messages plus notifications down networks are printed to stderr. level 3 all level 2 messages plus notifications of all packet timeouts are printed to stderr. "-r retry_count" sets the neighbor query retry limit. Default is 3 retry. "-t timeout_count" sets the number of seconds to wait for a neighbor query reply. Default timeout is 4 seconds. SAMPLE OUTPUT
mrinfo mbone.phony.dom.net 127.148.176.10 (mbone.phony.dom.net) [version 3.3]: 127.148.176.10 - 0.0.0.0 (?) [1/1/querier] 127.148.176.10 - 127.0.8.4 (mbone2.phony.dom.net) [1/45/tunnel] 127.148.176.10 - 105.1.41.9 (momoney.com) [1/32/tunnel/down] 127.148.176.10 - 143.192.152.119 (mbone.dipu.edu) [1/32/tunnel] For each neighbor of the queried multicast router, the IP of the queried router is displayed, followed by the IP and name of the neighbor. In square brackets the metric (cost of connection), the threshold (multicast ttl) is displayed. If the queried multicast router has a newer version number, the type (tunnel, srcrt) and status (disabled, down) of the connection is displayed. IMPORTANT NOTE
mrinfo must be run as root. SEE ALSO
mrouted(8), map-mbone(8), mtrace(8) AUTHOR
Van Jacobson 4.2 Berkeley Distribution MRINFO(8)
All times are GMT -4. The time now is 10:48 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy