3 added 6 characters in body
source | link

When an application establishes a TCP connection, it specifies a port for the inbound (receive) port, and uses a (somewhat) randomly selected port for outbound (source, or send). The inbound port for AG replication is 5022 by default, so all replication traffic is sent TO port 5022. Accordingly, you see the network reads occurring on port 5022, as SQL Server is listening on port 5022 and reading packets that are sent to itthat port.

The outbound port, which is selected randomly (more or less), is the port it is sent FROM. Accordingly, so that is why you see the writes associated with the random port (63420 in your example), as SQL Server is writing data to this port to be sent on the connection.

See How are source ports determined... for more

When an application establishes a TCP connection, it specifies a port for the inbound (receive) port, and uses a (somewhat) randomly selected port for outbound (source, or send). The inbound port for AG replication is 5022 by default, so all replication traffic is sent TO port 5022. Accordingly, you see the network reads occurring on port 5022, as SQL Server is listening on port 5022 and reading packets that are sent to it.

The outbound port, which is selected randomly (more or less), is the port it is sent FROM, so that is why you see the writes associated with the random port (63420 in your example), as SQL Server is writing data to this port to be sent on the connection.

See How are source ports determined... for more

When an application establishes a TCP connection, it specifies a port for the inbound (receive) port, and uses a (somewhat) randomly selected port for outbound (source, or send). The inbound port for AG replication is 5022 by default, so all replication traffic is sent TO port 5022. Accordingly, you see the network reads occurring on port 5022, as SQL Server is listening on port 5022 and reading packets that are sent to that port.

The outbound port, which is selected randomly (more or less), is the port it is sent FROM. Accordingly, you see the writes associated with the random port (63420 in your example), as SQL Server is writing data to this port to be sent on the connection.

See How are source ports determined... for more

2 added 205 characters in body
source | link

When an application establishes a TCP connection, it specifies a port for the inbound (receive) port, and uses a (somewhat) randomly selected port for outbound (sendsource, or send). The inbound port for AG replication is 5022 by default, so all replication traffic is sent TO port 5022. Accordingly, you see the network reads on occurring on port 5022, as SQL Server is listening on port 5022 and reading packets that are sent to it.

The outbound port, which is selected randomly (more or less), is the port it is sent FROM, so that is why you see the writes associated with the random port (63420 in your example), as SQL Server is writing data to this port to be sent on the connection.

See How are source ports determined... for more

When an application establishes a TCP connection, it specifies a port for the inbound (receive) port, and uses a randomly selected port for outbound (send). The inbound port for AG replication is 5022 by default, so all replication traffic is sent TO port 5022. Accordingly, you see the network reads on occurring on port 5022.

The outbound port, which is selected randomly (more or less), is the port it is sent FROM, so that is why you see the writes associated with the random port (63420 in your example).

When an application establishes a TCP connection, it specifies a port for the inbound (receive) port, and uses a (somewhat) randomly selected port for outbound (source, or send). The inbound port for AG replication is 5022 by default, so all replication traffic is sent TO port 5022. Accordingly, you see the network reads occurring on port 5022, as SQL Server is listening on port 5022 and reading packets that are sent to it.

The outbound port, which is selected randomly (more or less), is the port it is sent FROM, so that is why you see the writes associated with the random port (63420 in your example), as SQL Server is writing data to this port to be sent on the connection.

See How are source ports determined... for more

1
source | link

When an application establishes a TCP connection, it specifies a port for the inbound (receive) port, and uses a randomly selected port for outbound (send). The inbound port for AG replication is 5022 by default, so all replication traffic is sent TO port 5022. Accordingly, you see the network reads on occurring on port 5022.

The outbound port, which is selected randomly (more or less), is the port it is sent FROM, so that is why you see the writes associated with the random port (63420 in your example).