- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- HPE 9000 and HPE e3000 Servers
- >
- remote command
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
тАО04-23-2002 11:18 AM
тАО04-23-2002 11:18 AM
remote command
This message is received on a dsline from sys A to sys B.
I do not receive this message doing a DSLINE the opposite direction (from B to A)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-23-2002 11:26 AM
тАО04-23-2002 11:26 AM
Re: remote command
Does this post help? http://groups.google.com/groups?q=%22REMOTE+NOT+RESPONDING,+DATA+SEND+FAILED%22&hl=en&selm=0003HY%40PICARD.3K.COM&rnum=4
Ciao,
Greg
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-24-2002 04:21 AM
тАО04-24-2002 04:21 AM
Re: remote command
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-24-2002 04:57 AM
тАО04-24-2002 04:57 AM
Re: remote command
Do you have NS3000 software on System B? Is the IP address setup in NSDIR for System A on System B?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-24-2002 05:10 AM
тАО04-24-2002 05:10 AM
Re: remote command
Sorry, My last question should have asked... is the IP for system B in the NSDIR on system A? You could check this by going in to NMMGR, F2 to open directory, then F1 to update dir. The node name for system B should be listed. Type this NODE name in, then F6 to modify, if you want to check the IP that is asigned to this entry.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-24-2002 01:29 PM
тАО04-24-2002 01:29 PM
Re: remote command
RUN NETTOOL.NET.SYS
PING
PING
Name or address of destination
If the PING fails then you could be having problems resolving the node name for SYSTEM B from SYSTEM A. Maybe an entry got deleted from the Network Directory on SYSTEM A that points to SYSTEM B. If the PING succeeds then check the IP address that is returned to make sure it is the correct IP address of SYSTEM B. If you do have an entry in the NETWORK Directory for SYSTEM B make sure the Transport Service Flags are set to Y-N-Y. If you don't have an entry in the Network Directory for SYSTEM B on SYSTEM A try adding one and see if this solves the problem.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-25-2002 08:40 AM
тАО04-25-2002 08:40 AM
Re: remote command
System A is our Production and System B(connected thru fiber at a seperate location)is used as our Development system.
Encountered a power failure. System A was gracefully shutdown prior to the UPS running out of power. System B did not shutdown because it has dual power on the UPS, therefore was never shutdown.
Although when System A was rebooted (by Operator)it appears that sysstart did not execute therefore netcontrol and nscontrol commands were executed manually afterstartup
Since this occurence, I can remote from system B to A but cannot remote from A to B. A ping through NETTOOL is fine executed from both systems. It returns the proper address. These 2 systems are both managed through DTC Manager and Openview.
In addition the switch between the two systems also did loose power. Since the power failure,I restarted the NETWORK SERVICES on System A but not System B.
No configurations changes have been made from the previous 6 months or so.