- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: ucx telnet access, i'm missing something....
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
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
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
05-01-2018 07:37 PM
05-01-2018 07:37 PM
ucx telnet access, i'm missing something....
This has got to fall into the forehead slapping zone - I'm moving a VAX (5.5, running ucx) to a new network area. But the users cannot telnet in to the vax using putty. This is a very mature system, and I'm sure I have forgotten the obvious. Bot of these "vaxes" are running in VMs using charon-vax.
From my laptop, I can ping both servers hosting the VMs, and I can ping the existing VAX, but the new vax remains unpingable. This leads to my inability to telnet to it.
Something deep inside of me says their is something I forgot to do in ucx ...
what am I missing?
appreciate the obvious
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-01-2018 11:30 PM
05-01-2018 11:30 PM
Re: ucx telnet access, i'm missing something....
> [...] VAX (5.5, running ucx) [...]
ucx show version
> [...] to a new network area. [...]
Define "new". What are the IP addresses of these systems?
> [...] users cannot telnet in to the vax using putty. [...]
"cannot" is not a useful problem description. An actual error
message might be more helpful.
> what am I missing?
Can't tell without some info on the network configuration. The VMS
system could simply have an IP address in the wrong subnet, and no route
to the right subnet.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-02-2018 08:32 AM
05-02-2018 08:32 AM
Re: ucx telnet access, i'm missing something....
Not a mind reader? i'm disappointed. lol, yeah, I didn't provide much information.
This is an old legacy system running OpenVMS 6.1, UCX 4.0 within the charon-vax emulation environment. I'm in the process of migrating to a new virtual machine running in the customer's cloud. The new installation is using the exact same disk files as the existing system.
The existing system is at 10.90.10.202. I can access the system from my laptop.
I took the existing disk files, moved them to the VM and simply used UCX$CONFIG to change the new system's ip address to 10.90.10.186. Can't ping this address, can't telnet into the machine.
The addresses are so close, I would not expect routing to pay an issue.
Forehead slap moment - Windows Server 2012 is probably doing this, not the vax.... I'll be back to close this issue out.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-02-2018 08:50 AM - edited 05-02-2018 08:51 AM
05-02-2018 08:50 AM - edited 05-02-2018 08:51 AM
Re: ucx telnet access, i'm missing something....
You need to also look at the CHARON-VAX network configuration and VMware network configuration !
Is the CHARON-VAX network interface correctly mapped to the dedicated Windows network adapter to be used by CHARON exclusively ? NDIS6 binding o.k. ?
Looking from VMS: do the counters of $ UCX SHOW INTERFACE show packets being sent and/or received ?
Does the CHARON NCC tool show packets being sent and/or received ?
Does the VAX use DECnet on the LAN interface (in addition to IP) ? If so, is the VMware LAN interface correctly configured (MAC address change enabled and promiscuous mode enabled) ?
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-02-2018 09:02 AM
05-02-2018 09:02 AM
Re: ucx telnet access, i'm missing something....
Yes to all. And good suggestions, thanks. The part I missed is that if I connect to the Server 2012 machine, I have no problem telneting or pinging the VAX. I think I'm getting hammered by a group policy out in the customer's domain.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-02-2018 03:40 PM
05-02-2018 03:40 PM
Re: ucx telnet access, i'm missing something....
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-08-2018 02:48 AM
05-08-2018 02:48 AM
Re: ucx telnet access, i'm missing something....
I agree with prior statements, this sounds like a network problem on the host. There are lots of considerations for networking CHARON in the cloud. Follow the Stromasys documentation closely.
Software Concepts International
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-08-2018 04:19 AM
05-08-2018 04:19 AM
Re: ucx telnet access, i'm missing something....
Turns out it's death by typos. I changed the IP address and missed the route entry.
The route entry was left to the old server IP address....
thanks for the suggestions