02-26-2020
Here is the reply from the data center just now:
Quote:
I hear you. As a part of our global upgrade of site routers in all our data centers, today there was a scheduled update of the STL routers. Connectivity loss was not expected, thus you have not been informed. Unfortunately, during the process, connectivity problems arose and our Network Technicians had to revert to the router's original settings. The duration of the outage is being estimated to about 2h 30 min.
I am not arguing with you, not at all. Let us know how do you wish to proceed.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi
I faced a problem while booting linux which is as follows;-
*************************************************
Inode 146180 has illegal block(s)
xauth:error in locking authority file /home/root/.Xauthority
Fatal Server Error:
Could not create lock file in /tmp/tXo-lock
... (1 Reply)
Discussion started by: Abhishek
1 Replies
2. UNIX for Dummies Questions & Answers
Our SUn Solaris Server has crashed second time in 2 days, reason is not known , we are trying to determine what could have gone wrong, any ideas, the power supply seems to be fine, there is no response from keyboard,monitor etc and we had to do a hot boot yesterday..
Any suggestions what could be... (9 Replies)
Discussion started by: knarayan
9 Replies
3. UNIX for Advanced & Expert Users
We have had a server (Solaris 2.6) hardisk crash. When booting the server we get:
ok> boot -S
Boot Device: /sbus/espdmc@e, 8400000/esp@e,8800000/sd@0,0
short read 0x2000 chars read
disk read error
The only way we can get into the console is to
ok> boot cdrom
whereby everything (e.g.... (3 Replies)
Discussion started by: Breen
3 Replies
4. UNIX for Dummies Questions & Answers
Is it possible for a group of servers to monitor each other and then send an alert if one of them is no longer 'alive'?
Or if its easier have one server that monitors the other five and then sends an alert.
If so how would this be done?
Thanks (3 Replies)
Discussion started by: Sepia
3 Replies
5. Linux
Is it true that you can't have the crash dump server/client on the same server?
I know I've installed Nagios open source before, I though it's only for that kind of thing. I never though that Red hat ent 4 would be like client/server on the crash dump.
if someone is having problem with high... (0 Replies)
Discussion started by: itik
0 Replies
6. Programming
Problem
- Linux Client/Server Socket Application: Preventing Client from quitting on server crash
Hi,
I am writing a Linux socket Server and Client using TCP protocol on Ubuntu 9.04 x64.
I am having problem trying to implement a scenario where the client should keep running even when the... (2 Replies)
Discussion started by: varun.nagpaal
2 Replies
7. SCO
Hi there.
Well i have a really bad problem with my server:
UnixWare Version 5 Release 7
The system crash :wall: and show the error:
Panic: Kernel-mode address fault on user address 0x00000004 :eek:
If anyone knows about the reason of this error please give me a help
Sorry by my english.... (3 Replies)
Discussion started by: danilosevilla
3 Replies
8. Programming
The steps to test the problem
1. Open TCP Server
2. Open TCP Client
3. TCP Client sends data to Server.
4. Close TCP Server and the client also crash without any notification
Second wonderful test:
1. Comment the following statement in Client.c (at line 168) and compile it
Writen(... (1 Reply)
Discussion started by: sehang
1 Replies
9. Red Hat
hi,
i would like to configure netdump, but saving the var/crash in the server itself, not in another server.
could anybody tell me if this is possible?
thanks (4 Replies)
Discussion started by: pabloli150
4 Replies
10. AIX
Hi there
I've bought a used System p 9115-505. When I attach the LAN cable to my router the HMC receives an IP address from my router, but the HMC is unreachable. There are no open ports.
Does anybody know that problem?
Any help greatly appreciated. Greetings from Italy! (2 Replies)
Discussion started by: mediaset23
2 Replies
RDISC(8) System Manager's Manual: iputils RDISC(8)
NAME
rdisc - network router discovery daemon
SYNOPSIS
rdisc [ -abdfstvV] [ send_address] [ receive_address]
DESCRIPTION
rdisc implements client side of the ICMP router discover protocol. rdisc is invoked at boot time to populate the network routing tables
with default routes.
rdisc listens on the ALL_HOSTS (224.0.0.1) multicast address (or receive_address provided it is given) for ROUTER_ADVERTISE messages from
routers. The received messages are handled by first ignoring those listed router addresses with which the host does not share a network.
Among the remaining addresses the ones with the highest preference are selected as default routers and a default route is entered in the
kernel routing table for each one of them.
Optionally, rdisc can avoid waiting for routers to announce themselves by sending out a few ROUTER_SOLICITATION messages to the ALL_ROUTERS
(224.0.0.2) multicast address (or send_address provided it is given) when it is started.
A timer is associated with each router address and the address will no longer be considered for inclusion in the the routing tables if the
timer expires before a new advertise message is received from the router. The address will also be excluded from consideration if the host
receives an advertise message with the preference being maximally negative.
Server side of router discovery protocol is supported by Cisco IOS and by any more or less complete UNIX routing daemon, f.e gated.
OPTIONS
-a Accept all routers independently of the preference they have in their advertise messages. Normally rdisc only accepts (and enters
in the kernel routing tables) the router or routers with the highest preference.
-b Opposite to -a, i.e. install only router with the best preference value. It is default behaviour.
-d Send debugging messages to syslog.
-f Run rdisc forever even if no routers are found. Normally rdisc gives up if it has not received any advertise message after after
soliciting three times, in which case it exits with a non-zero exit code. If -f is not specified in the first form then -s must be
specified.
-s Send three solicitation messages initially to quickly discover the routers when the system is booted. When -s is specified rdisc
exits with a non-zero exit code if it can not find any routers. This can be overridden with the -f option.
-t Test mode. Do not go to background.
-v Be verbose i.e. send lots of debugging messages to syslog.
-V Print version and exit.
HISTORY
This program was developed by Sun Microsystems (see copyright notice in source file). It was ported to Linux by Alexey Kuznetsov
<kuznet@ms2.inr.ac.ru>.
SEE ALSO
icmp(7), inet(7), ping(8).
REFERENCES
Deering, S.E.,ed "ICMP Router Discovery Messages", RFC1256, Network Information Center, SRI International, Menlo Park, Calif., September
1991.
SECURITY
rdisc requires CAP_NET_RAWIO to listen and send ICMP messages and capability CAP_NET_ADMIN to update routing tables.
AVAILABILITY
rdisc is part of iputils package and the latest versions are available in source form for anonymous ftp ftp://ftp.inr.ac.ru/ip-rout-
ing/iputils-current.tar.gz.
iputils-021109 09 iINAON 2002 RDISC(8)