- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- RIP with TCP/IP Services v5.1
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
Forums
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
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
тАО07-26-2004 12:18 AM
тАО07-26-2004 12:18 AM
RIP with TCP/IP Services v5.1
I have been informed from my networking group that the Alpha with OpenVMS is running the RIP protocol. They see this when from their PC they do a "route print". The effect that this has is that it updates a workstation routes when "RIP Listner" is installed.
I have not got dynamic routing enabled, i.e. GATED etc. Does OpenVMS automatically enable RIP ?
With regards
Andrew
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-26-2004 12:52 AM
тАО07-26-2004 12:52 AM
Re: RIP with TCP/IP Services v5.1
To my knowledge, ROUTED nor GATED are automatically enabled, when starting TCP/IP.
What does TCPIP SHOW CONFIG START ROUTING tell you?
Kris.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-26-2004 12:55 AM
тАО07-26-2004 12:55 AM
Re: RIP with TCP/IP Services v5.1
$ ucx start routing
Disabled by
$ ucx stop routing
Permanently disable :
$ ucx set config start norouting
Wim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-26-2004 01:03 AM
тАО07-26-2004 01:03 AM
Re: RIP with TCP/IP Services v5.1
Just to clarify it a bit further. This system is in an OpenVMS cluster, and I do have a cluster IP address configured. Does RIP get enabled to handle the cluster aliasing ?
With regards
Andrew
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-26-2004 02:51 AM
тАО07-26-2004 02:51 AM
Re: RIP with TCP/IP Services v5.1
Not to my knowledge. RIP simply means that routers are populating your routing database. If you do "ucx sho rout" and compare it with "ucx sho rout/perm" you can see what it added (some like the 127 rout are added without rip). To disable RIP, you might need to add manual routing info with "ucx add rout". Otherwise, you might not be able to contact nodes on other subnets.
Wim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-26-2004 02:43 PM
тАО07-26-2004 02:43 PM
Re: RIP with TCP/IP Services v5.1
RIP is the Routing Information Protocol (see e.g. http://www.cisco.com/univercd/cc/td/doc/cisintwk/ito_doc/rip.htm
for some basic information). You should only see an OpenVMS box participate in RIP if either
ROUTED or GATED are enabled. Some further information about this can be found e.g. if you invoke tcpip$config and select core-> routing information. Also other protocols are supported. Most of the time networkers are opposed to non-Network equipment doing routing nowadays ;-)
Greetings, Martin