HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- HP Tru64 5.1B -Ignoring RIP request
Operating System - Tru64 Unix
1829905
Members
1570
Online
109993
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-05-2005 11:01 PM
12-05-2005 11:01 PM
we are having Tru64 5.1B with PK4 installed & running for almost a year now, recently we started getting below messages & some clinets are not able to connect to this system.
please advice appropriate action.
Please find attched complte file.
rip_recv: ignoring RIP Request packet from 10.1.0.76+520 - not supplying RIP
Dec 6 09:16:50+0.517652
please advice appropriate action.
Please find attched complte file.
rip_recv: ignoring RIP Request packet from 10.1.0.76+520 - not supplying RIP
Dec 6 09:16:50+0.517652
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-06-2005 01:57 AM
12-06-2005 01:57 AM
Solution
Is this a cluster or a stand alone system ?
Obviously you're running gated and unless you've configured it to run on your own, it's usually automatically configured in a cluster, but not required in 5.1b.
It would appear from the message that an outside system send a RIP query, but your system did not answer as it is configured to broadcast only and not respond.
Might want to examine all statements in your gated.conf file either in /etc or if this is a cluster, in /etc/gated.conf.memberX.
Do you know what host 10.1.0.76 is ?
Is it a host or a router ?
Was it always on the network or is it a new system and if not new, what has changed ?
I don't imagine this is a very serious issue, but more of one of interest.
When you say "some clients are not able to connect to this system", can you give more details ?
Are those clients in the same subnet ?
Anything these clients have in common that might differ from other clients that can connect ?
Can those clients that can't connect ping your system ?
Obviously you're running gated and unless you've configured it to run on your own, it's usually automatically configured in a cluster, but not required in 5.1b.
It would appear from the message that an outside system send a RIP query, but your system did not answer as it is configured to broadcast only and not respond.
Might want to examine all statements in your gated.conf file either in /etc or if this is a cluster, in /etc/gated.conf.memberX.
Do you know what host 10.1.0.76 is ?
Is it a host or a router ?
Was it always on the network or is it a new system and if not new, what has changed ?
I don't imagine this is a very serious issue, but more of one of interest.
When you say "some clients are not able to connect to this system", can you give more details ?
Are those clients in the same subnet ?
Anything these clients have in common that might differ from other clients that can connect ?
Can those clients that can't connect ping your system ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-06-2005 02:08 AM
12-06-2005 02:08 AM
Re: HP Tru64 5.1B -Ignoring RIP request
Thanks tones
This is not cluster.its standalone machine.
the IP addresses which is getting ignored is branch servers.
this configuration was working for last 1 year almost.
some clients means the Ip addresses which is mentioned in the file.
everybody is able to ping to the server.
please advice what should i do so everybody can access this server.
thanks lots again.
regards
S.
This is not cluster.its standalone machine.
the IP addresses which is getting ignored is branch servers.
this configuration was working for last 1 year almost.
some clients means the Ip addresses which is mentioned in the file.
everybody is able to ping to the server.
please advice what should i do so everybody can access this server.
thanks lots again.
regards
S.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-07-2005 12:56 AM
12-07-2005 12:56 AM
Re: HP Tru64 5.1B -Ignoring RIP request
>> This is not cluster.its standalone machine.
Then why run gated ? If it is causing problems, don't run it.
>>the IP addresses which is getting ignored is branch servers.
Is this address an ip alias or a primary address on one of the interfaces ?
You might want to list the output of netstat -rn ( the routing table ) on the system in question.
>>this configuration was working for last 1 year almost.
Which means something changed. If nothing changed on this host, then you might want to inquire about changes on other hosts or routers. Or if changes did take place on this host, see if any of them may have
had an affect on the problem.
>>some clients means the Ip addresses which is mentioned in the file.
So only client cannot reach the host ?
>>everybody is able to ping to the server.
Please describe in more detail what you can't reach....i.e. a specific application on a specific address, telnet, ssh, ftp, any other services.
Gated messages are often rather cryptic and in themselves don't tell the entire story. So the more information you can provide the easier it will be to provide help.
Then why run gated ? If it is causing problems, don't run it.
>>the IP addresses which is getting ignored is branch servers.
Is this address an ip alias or a primary address on one of the interfaces ?
You might want to list the output of netstat -rn ( the routing table ) on the system in question.
>>this configuration was working for last 1 year almost.
Which means something changed. If nothing changed on this host, then you might want to inquire about changes on other hosts or routers. Or if changes did take place on this host, see if any of them may have
had an affect on the problem.
>>some clients means the Ip addresses which is mentioned in the file.
So only client cannot reach the host ?
>>everybody is able to ping to the server.
Please describe in more detail what you can't reach....i.e. a specific application on a specific address, telnet, ssh, ftp, any other services.
Gated messages are often rather cryptic and in themselves don't tell the entire story. So the more information you can provide the easier it will be to provide help.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP