- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- Gated and RIP Broadcasts
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
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
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- 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
тАО09-28-2004 06:26 PM
тАО09-28-2004 06:26 PM
[gated.conf]
# Enable RIP to behave as "routed -q"
# (i.e. quiet mode) -- never send RIP update even >1 interface configured.
rip yes
{
nobroadcast;
} ;
[/gated.conf]
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-28-2004 07:37 PM
тАО09-28-2004 07:37 PM
Re: Gated and RIP Broadcasts
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-28-2004 07:50 PM
тАО09-28-2004 07:50 PM
Re: Gated and RIP Broadcasts
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-28-2004 09:29 PM
тАО09-28-2004 09:29 PM
Re: Gated and RIP Broadcasts
Is 5.1B a cluster installation or not?
TruCluster 1.6 could be all sorts of V4.x Tru64 versions... so please be more specific we know nothing about your setup or what you have done and the given information is not very technical...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-28-2004 09:36 PM
тАО09-28-2004 09:36 PM
Re: Gated and RIP Broadcasts
The version we are using is:
TruCluster Server V5.1B (Rev. 1029); 06/16/04 03:56
As for what we did, nothing special. Just running a normal setup of 5.1B Unix (PK4) with TruCluster 5.1B, running gated.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-28-2004 09:45 PM
тАО09-28-2004 09:45 PM
Re: Gated and RIP Broadcasts
Why does gated send out RIP broadcast requests, even if it is configured not to do so.
Seen the network traces, proof of the network admin cannot be denied. (i tried: yes i run gated, yes it supports RIP, but it configured not to send RIP boardcasts, shows gated config file to network admin. Network admin shows nettrace. Unix admin gets burned :( )
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-28-2004 10:53 PM
тАО09-28-2004 10:53 PM
Re: Gated and RIP Broadcasts
Btw. RIP is always used within an Trucluster 5.x system. In V5.1B there were some changes documented within the cluster admin guide.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-28-2004 11:22 PM
тАО09-28-2004 11:22 PM
Re: Gated and RIP Broadcasts
RIP is indeed enabled (broadcast)in /etc/gated.conf.member1 and /etc/gated.conf.member2.
Atleast i know where it comes from, then again why is it needed?
Is it because, we are using Netrain and Niff needs it?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-29-2004 07:52 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-01-2004 03:42 AM
тАО10-01-2004 03:42 AM
Re: Gated and RIP Broadcasts
In v5.1b much of the work done by gated has been moved to aliasd.
If you do decide to prevent gated from running, check with your network people first to make sure that RIP is not providing a valid service announcement to the local hosts or routers on the network.
Gated is used to announce the presence of the cluster alias(es) to all interfaces on the cluster members.
The correct method for preventing gated from running on a v5.1b cluster is to define the following:
rcmgr set CLUAMGR_ROUTE_ARGS "nogated"
Then reboot each member. Also make sure that GATED="no" or null in the rc.config
files as you don't want gated to start and use the default /etc/gated.conf file, unless you reall know what you're doing.