Sponsored Content
Operating Systems Solaris How i test the UDP port is working? Post 302255776 by vimes on Friday 7th of November 2008 05:15:52 AM
Old 11-07-2008
Try netcat.

I think you can do:

Code:
nc -zu <ip> <udpport>

 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

How to check the TCP/UDP port of a connection

Hi, Users are connecting thru a KCML Client to UNIX machine, and I want to know which TCP/UDP port that client uses? How can I check the port of a user logged in? Regards, Tayyab (2 Replies)
Discussion started by: tayyabq8
2 Replies

2. Infrastructure Monitoring

UDP Port 161

hi guys My linux server have SNMP configure port by default is 161 (UDP) now my monitor team - who are using Nagios - say the server are not being monitor so check netstat -lnu and I see all is OK and snmp service is running fine what else should I check about this port 161? to see if it is... (0 Replies)
Discussion started by: karlochacon
0 Replies

3. AIX

TCP/UDP port range for default AIX NFS?

May I know what is the TCP/UCP port range for any default AIX NFS? Based on rpcinfo -p, I got the following output: program vers proto port service 100000 4 udp 111 portmapper 100000 3 udp 111 portmapper 100000 2 udp 111 portmapper 100000 4 ... (4 Replies)
Discussion started by: famasutika
4 Replies

4. Programming

Using socket to test a TCP port

Hello, I'm trying to write a small c application to test a tcp port. This works fine for the most part but the default timeout on the connect is very long. I have been reading many posts but and it looks like I need to set the socket to be non-blocking and poll for a result. I have been totally... (2 Replies)
Discussion started by: tjones1105
2 Replies

5. IP Networking

Sending data from DELL OMSA SNMP and Custom SNMP MIB to same UDP port 161

Hi , Currently DELL OMSA SNMP sends data through default udp port 161.I want my custom SNMP MIB also to send data in the same udp port 161.Whether its possible.If yes where to configure .I tried starting my custom MIB in udp port 161,but it throws port already in use.Kindly guide. (0 Replies)
Discussion started by: prabakar4all
0 Replies

6. Red Hat

Sending data from DELL OMSA SNMP and Custom SNMP MIB to same UDP port 161

Hi , Currently DELL OMSA SNMP sends data through default udp port 161.I want my custom SNMP MIB also to send data in the same udp port 161.Whether its possible.If yes where to configure .I tried starting my custom MIB in udp port 161,but it throws port already in use.Kindly guide. (1 Reply)
Discussion started by: prabakar4all
1 Replies

7. IP Networking

telnet for port 5433 is not working while it works for port 22

Hi, I am trying to set up a dev environment and I have Ubuntu server (10.16.1.92) and a CentOS VM (10.16.3.235) on this. On the CentOS I have a program running on port 5433. Now my problem is that I am unable to telnet this port from another Windows server whereas I can telnet port 22 from... (5 Replies)
Discussion started by: rishav
5 Replies

8. Shell Programming and Scripting

How to check UDP port example = 31011?

We have open port UDP port 31011, how to verify if port were working or traffic were receive. (2 Replies)
Discussion started by: avtalan
2 Replies

9. UNIX for Dummies Questions & Answers

Test connectivity to IP/port

I want to test the connectivity to an IP with Port number = xxxx. I only know telnet can do it. For example, telnet <IP> <port>. But I don't have telnet installed (no package) on my Red Hat Linux server. I searched the Internet and realized that I will need either the installation media which... (2 Replies)
Discussion started by: learnix
2 Replies

10. Shell Programming and Scripting

Test multiple IP:Port servers

Hello, I am pretty unskilled in bash and I need some script and my skills ale limited (yet) I am learning but situation now needs some more skills. is there possibility to simply check IP address with ports from csv file? My csv has hundred of IPs in this format ... (9 Replies)
Discussion started by: Keagan
9 Replies
vrport(1M)																vrport(1M)

NAME
vrport - Veritas Volume Replicator port management utility SYNOPSIS
vrport [-a | -r] data [port | portlow-porthigh [,port...]] vrport heartbeat [port] vrport vradmind [port] vrport vxrsyncd [port] DESCRIPTION
The vrport utility manages the various UDP and TCP ports used by Veritas Volume Replicator (VVR). VVR uses the UDP and TCP transport protocols to communicate between the Primary and Secondary. VVR exchanges three types of message between the Primary and Secondary: heartbeat, data and administrative control. The heartbeat messages are transmitted using the UDP protocol on the IANA approved 4145 UDP Port number. VVR can use either the UDP trans- port protocol or the TCP transport protocol to exchange data messages. VVR uses UDP Anonymous ports for data replication between Primary and the Secondary if the network protocol is UDP. VVR uses IANA approved 4145 TCP port number for TCP listener port on the Secondary and TCP Anonymous ports on the Primary for data replication if the network protocol is TCP. VVR uses IANA approved 8199 TCP port for communication between the vradmind daemons on the Primary and the Secondary. vradmind server pro- vides administration of VVR objects in a distributed environment. VVR uses 8989 TCP port number for communication between the vxrsyncd dae- mons on the Primary and the Secondary. Use vrport to display, change or set the port numbers used by VVR. You may have to change the port numbers to resolve a port number con- flict with other applications, to configure VVR to work in a firewall environment when using UDP network protocol by restricting the number of ports to replicate data between the Primary and the Secondary. The action performed by vrport depends on the specified keyword operand(s). When invoked with no arguments, vrport displays the port number(s) used for heartbeat, data, vradmind and vxrsyncd communication between the Primary and Secondary on the standard output. KEYWORDS
data [port | portlow-porthigh [,port...]] Without any arguments, the vrport data command displays the port number(s) used by VVR for data replication between the Primary and the Secondary. This is applicable only if you have chosen UDP for network protocol. With the port number(s) or range specified, restricts VVR to use the ports or list of ports specified for data replication. If the -a flag is specified, the vrport data command appends the given port numbers(s) or range to the existing port number(s) or range to be used for data replication. If the -r flag is specified, the vrport data command removes the given port number(s) or range from the existing port number(s) for data replication. You need to execute /usr/sbin/vxnetd, and pause and resume all RLINKs for VVR to use the new port information. heartbeat [port] Without the port argument, displays the UDP port number used to exchange heartbeat messages. With the port argument specified, sets the UDP port number to exchange heartbeat messages. Use the vradmin changeip command to update the RLINKs with the new port information. To have VVR use the new port number, enter the command /usr/sbin/vxnetd stop followed by /usr/sbin/vxnetd. vradmind [port] Without the port argument, displays the TCP port number used by the vradmind daemons for communication between the Primary and the Secondary. With the port argument specified, sets the TCP port number to be used by the vradmind daemons. The new port is used when the vradmind process is restarted. vxrsyncd [port] Without the port argument, displays the port the TCP port number used by vxrsyncd daemons for communication between the Primary and the Secondary hosts. With the port argument specified, command sets the TCP port number to be used by the vxrsyncd daemons. The new port is used when the vxrsyncd process is restarted. EXAMPLES
See the Veritas Volume Replicator Configuration Notes for examples. EXIT CODES
The vrport utility exits with a non-zero status if the attempted operation fails. A non-zero exit code is not a complete indicator of the problems encountered but denotes the first condition that prevented further execution of the utility. SEE ALSO
vradmin(1M),vxrlink(1M) Veritas Volume Replicator Administrator's Guide Veritas Volume Replicator Configuration Notes VxVM 5.0.31.1 24 Mar 2008 vrport(1M)
All times are GMT -4. The time now is 12:46 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy