SYNOPSISrds-info [-v ] -words [-cknrstIT ]
DESCRIPTIONThe rds-info utility presents various sources of information that the RDS kernel module maintains. When run without any optional arguments rds-info will output all the information it knows of. When options are specified then only the information associated with those options is displayed.
The options are as follows:
Requests verbose output. When this option is given, some classes of information
will display additional data.
Display global counters. Each counter increments as its event
occurs. The counters may not be reset. The set of supported counters
may change over time.
- The name of the counter. These names come from the kernel and can change depending on the capability of the kernel module.
- The number of times that the counter has been incremented since the kernel module was loaded.
Display all the RDS sockets in the system. There will always be one socket
listed that is neither bound to nor connected to any addresses because
itself uses an unbound socket to collect information.
- BoundAddr, BPort
- The IP address and port that the socket is bound to. 0.0.0.0 0 indicates that the socket has not been bound.
- ConnAddr, CPort
- The IP address and port that the socket is connected to. 0.0.0.0 0 indicates that the socket has not been connected.
- SndBuf, RcvBuf
- The number of bytes of message payload which can be queued for sending or receiving on the socket, respectively.
- The number of the inode object associated with the socket. Can be used to locate the process owning a given socket by searching /proc/*/fd for open files referencing a socket with this inode number.
Display all RDS connections. RDS connections are maintained between
nodes by transports.
- The IP address of this node. For connections that originate and terminate on the same node the local address indicates which address initiated the connection establishment.
- The IP address of the remote end of the connection.
- The sequence number that will be given to the next message that is sent over the connection.
- The sequence number that is expected from the next message to arrive over the connection. Any incoming messages with sequence numbers less than this will be dropped.
Flags which indicate the state of the connection.
- A process is currently sending a message down the connection.
- The transport is attempting to connect to the remote address.
- The connection to the remote host is connected and active.
- -r, -s, -t
Display the messages in the receive, send, or retransmit queues respectively.
- LocalAddr, LPort
- The local IP address and port on this node associated with the message. For sent messages this is the source address, for receive messages it is the destination address.
- RemoteAddr, RPort
- The remote IP address and port associated with the message. For sent messages this is the destination address, for receive messages it is the source address.
- The sequence number of the message.
- The number of bytes in the message payload.
The following information sources are dependent on specific transports which may not always be available.
Display the IB connections which the IB transport is using to provide
- The local IP address of this connection.
- The remote IP address of this connection.
- The local IB Global Identifier, printed in IPv6 address syntax.
- The remote IB Global Identifier, printed in IPv6 address syntax.
If verbose output is requested, per-connection settings such as the maximum number of send and receive work requests will be displayed in addition.
Display the TCP sockets which the TCP transport is using to provide
- LocalAddr, LPort
- The local IP address and port of this socket.
- RemoteAddr, RPort
- The remote IP address and port that this socket is connected to.
- The number of bytes that must be read off the socket to complete the next full RDS header.
- The number of bytes that must be read off the socket to complete the data payload of the message which is being received.
- The TCP sequence number of the first byte of the last message that we sent down the connection.
- The TCP sequence number of the byte past the last byte of the last message that we sent down the connection. When we see that the remote side has acked up to this byte then we know that the remote side has received all our RDS messages.
- The TCP sequence number of the byte past the last byte which has been acked by the remote host.