- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Multinet to TCP/IP migration
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
тАО07-26-2004 01:28 AM
тАО07-26-2004 01:28 AM
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-26-2004 05:12 AM
тАО07-26-2004 05:12 AM
Re: Multinet to TCP/IP migration
Its a matter of configuring TCPIP to match after that.
Art
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-26-2004 05:20 AM
тАО07-26-2004 05:20 AM
Re: Multinet to TCP/IP migration
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-26-2004 07:34 AM
тАО07-26-2004 07:34 AM
Re: Multinet to TCP/IP migration
Never saw multinet but
1) applications may be linked with some olb/exe of it and may fail if multinet is not available. Relink them !
2) you should compare all timeout settings (e.g. keepalive) or get appl;ication hangs.
3) test test test
Wim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-26-2004 07:41 AM
тАО07-26-2004 07:41 AM
Re: Multinet to TCP/IP migration
$ MULTINET CONFIGURE /SERVERS
SERVER-CONFIG> shutdown
This stops the master process. Alternatively, comment out the startup command procedure and reboot, which might not be a bad idea...gets rid of all the Multinet logicals etc.
Why the switch away from Multinet?
Art
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-26-2004 08:31 AM
тАО07-26-2004 08:31 AM
Re: Multinet to TCP/IP migration
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-26-2004 02:30 PM
тАО07-26-2004 02:30 PM
Solutionhttp://www.process.com/tcpip/mndocs/MN%20v5.0%20Installation%20Administrator%20Guide/Ch09.htm#E55E56
has an overview of the various configuration files used by Multinet and what they contain (and how to access them). Obviously you do need to mirror this information in the new TCPIP setup. My advise would be to invoke tcpip$configure, start with the first menu and followup through all the submenus ;-). If you know IP in general and have an idea of your network this should not take more than about an hour at most (assuming a moderatly difficult network environment, if you do have 10 Ethernet interfaces in the box and do all kinds of "interesting" routing between the various networks it might take longer ;-)
Other things to consider are in-house developed applications that might use Multinet specific features, third party should be fine, they will use the UCX compatibility mode of Multinet anyhow.
As mentioned before, testing is your friend :-), especially make sure to test your environment under network load.
Greetings, Martin
P.S. Is 5.5 already out?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-28-2004 11:17 AM
тАО07-28-2004 11:17 AM
Re: Multinet to TCP/IP migration
Process Software is fully committed to supporting UCX emulation in our MultiNet product. Past versions of MultiNet were directly certified by Oracle, but currently are not - although we are working to rectify this. As a result, Process Software conducts its own 3rd party certification to ensure full UCX emulation in the MultiNet product.
We have many customers successfully using MultiNet with Oracle and will take very seriously any problems you might discover relating to UCX emulation and Oracle.
Steve Lovejoy, Technical Manager
Process Softare
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-29-2004 12:53 AM
тАО07-29-2004 12:53 AM
Re: Multinet to TCP/IP migration
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-03-2004 02:04 AM
тАО08-03-2004 02:04 AM
Re: Multinet to TCP/IP migration
As to MultiNet v4.3, please be aware that we recently released MultiNet v5.0. Since we support the current version and one back (which is MultiNet 4.4), you should consider moving forward.
Geoff Byant
Process Software