- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: RTR problem...
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-19-2008 03:43 AM
тАО04-19-2008 03:43 AM
RTR problem...
we have four alpha nodes in cluster.
when i put the DCL command RTR MON CONNECT it shows the connection b/w the node is down.But the MONCLUS command and SHOW clus command are showing all the nodes are in the member state.
can any one tell me what is the problem with that?
NOTE: These two nodes are the front end servers.
Node ->Link State Arch T'port Fail-reason
xxxx->yyyy down ? TCP connect timeout
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-19-2008 06:31 AM
тАО04-19-2008 06:31 AM
Re: RTR problem...
CONNECT" is trying to talk to the RTR
software on the other node. Is _that_
running (properly)?
> But the MONCLUS command [...]
alp $ MONCLUS
%DCL-W-IVVERB, unrecognized command verb - check validity and spelling
\MONCLUS\
MONITOR CLUSTER or SHOW CLUSTER doesn't
really care if the RTR software is running
anywhere.
Can you talk to the other node using any
other TCP/IP stuff (Telnet, ping, ...)?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-19-2008 10:42 PM
тАО04-19-2008 10:42 PM
Re: RTR problem...
But when i try to telnet the x node to y node using following command.
telnet xx.xx.xx.xx/port=46000
%TELNET-I-TRYING, Trying ... xx.xx.xx.xx
%TELNET-I-SESSION, Session 01, host xx.xx.xx.xx, port 46000
-TELNET-I-ESCAPE, Escape character is ^]
After this line there is no response.. what could be the reason can anyone help me?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-20-2008 06:38 AM
тАО04-20-2008 06:38 AM
Re: RTR problem...
> other TCP/IP stuff (Telnet, ping, ...)?
I meant normal Telnet, not Telnet to what I
assume must be an RTR port.
> After this line there is no response.. [...]
Apparently, the RTR software is not running
properly on that system, although I don't
know how properly running RTR software
behaves when you use Telnet to connect to
that port.
Have you tried restarting the RTR software on
the problem node?
The RTR manual I found:
http://h71000.www7.hp.com/doc/82final/rtr/rtrsmm.pdf
suggests:
http://
So I would use a Web browser, not Telnet, to
talk to port 46000.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-20-2008 02:38 PM
тАО04-20-2008 02:38 PM
Re: RTR problem...
Check all nodes in your cluster for TCPIP connections on ports 46000, 46001 and 46002. You should see listeners on 46000 and 46001, and connections established in both directions on 46002.
Also check RTR SHOW NODE on each node.
Your telnet test shows that something has responded to port 46000, which is positive. That you can't type RTR protocol is no surprise.
Each node should have processes RTRACP, RTRD and RTR_
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-20-2008 08:38 PM
тАО04-20-2008 08:38 PM
Re: RTR problem...
whenever i am using telnet and ping commands its working and the commands completed successfully. but when i mentioning the port 46000 in my offline server, there is no response after some lines what i mentioned earlier.but from our other nodes, it displays
tel xx.xx.xx.xx/port=46000
%TELNET-I-TRYING, Trying ... xx.xx.xx.xx
%TELNET-E-CONNFAIL, Failed to connect to remote host
-SYSTEM-F-REJECT, connect to network object rejected.
RTR application also be restarted. now also the rtr mon connect shows the x node to y node link is down and i cant telnet via 46000.
CAN U TELL ME WHAT IS THE PROBLEM?
WHAT ARE THE COMMANDS I WANT TO CHECK?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-20-2008 08:57 PM
тАО04-20-2008 08:57 PM
Re: RTR problem...
can u tell me how to check the tcpip connections.when i check here it shows error.
so will u please tell me what are the commands to check the tcpip?
and also i can't connect rtr with web browser
http://xx.xx.xx.xx:46000/rtr_main.html but all nodes has the required RTR processes what u mentioned earlier.....
All nodes having same values when I check with RTR SHOW NODE command.
so plese tell me what are the values i want to check with and also tell what are the commands to check?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-20-2008 09:19 PM
тАО04-20-2008 09:19 PM
Re: RTR problem...
> %TELNET-I-TRYING, Trying ... xx.xx.xx.xx
> %TELNET-E-CONNFAIL, Failed to connect to remote host
> -SYSTEM-F-REJECT, connect to network object rejected.
This looks like what a UNIX system would call
"connection refused" (ECONNREFUSED), that is
you can reach the other system, but there's
no program listening at port 46000. In other
words, your RTR Web server is not running on
that system.
> [...] and i cant telnet via 46000.
And I don't know what that means. Please
show actual commands with actual output.
Don't provide only your interpretation of
what happened.
> whenever i am using telnet and ping
> commands its working and the commands
> completed successfully.
Ok. It sounds as if the basic TCP/IP
networking is good, and all your problems are
in the RTR software. [...]
CAN U TELL ME WHAT IS THE PROBLEM?
All I know about RTR is whare to find the
manual. (And how to spell "you" the way
grown-ups do.)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-20-2008 10:43 PM
тАО04-20-2008 10:43 PM
Re: RTR problem...
$ mc sysman set env/clu
do ucx sh dev /port=46000/fu
and post it ?
It may help.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-21-2008 05:42 PM
тАО04-21-2008 05:42 PM
Re: RTR problem...
here is the output for what you mentioned above...
ucx sh dev/port=46000/ful
Device_socket: bg268 Type: STREAM
LOCAL REMOTE
Port: 46000 0
Host: * *
Service:
RECEIVE SEND
Queued I/O 0 0
Q0LEN 0 Socket buffer bytes 0 0
QLEN 0 Socket buffer quota 61440 61440
QLIMIT 769 Total buffer alloc 0 0
TIMEO 0 Total buffer limit 491520 491520
ERROR 0 Buffer or I/O waits 517 0
OOBMARK 0 Buffer or I/O drops 0 0
I/O completed 519 0
Bytes transferred 0 0
Options: ACCEPT REUSEADR KEEP
State: PRIV
RCV Buff: WAIT
SND Buff: None