TCP/UDP Listener Management

Last updated: 2021-04-12 11:20:18

    Creating a TCP/UDP Listener

    1. Log in to the GAAP console, click Access Management on the left sidebar, and then click the ID/Connection Name of a connection.
    2. Open the TCP/UDP Listener Management tab and click Create to add a new TCP or UDP listener.
      1. Configure the listener information to set the mapping between the protocol and port.

        Origin Server Type: It can be an IP address or a domain name, but the same listener only supports one type.
        Source Port: Access port of the acceleration connection VIP. Valid range: 1–65535 (port 21 is currently unavailable). A single port or a range of consecutive ports is supported. The port must be unique. A maximum of 20 consecutive ports can be added at a time, such as 8000–8019.
      2. Configure the origin server processing policy, that is, if a listener is bound with multiple origin servers, you need to select a scheduling policy for origin servers.

        RR: Round Robin scheduling policy
        Weighted RR: You can set the weight of each origin server when binding a listener.
        Least Connections: Origin server with the least number of connections is scheduled first.

        Note:

        Listeners whose origin server type is domain name only support RR scheduling policy. If the domain name is resolved to multiple IPs, each resolved IP is scheduled according to the RR policy.

      3. Health check is required for using TCP.

    Response Timeout: The timeout period for a response.
    Health Check Interval: It refers to the interval between two consecutive health checks. If an origin server is checked as abnormal, the origin server will stop forwarding packets until it recovers to a normal status upon another health check.

    Setting a TCP/UDP Listener

    Open the TCP/UDP Listener Management tab and click Set in the operation column of a listener to modify its name, scheduling policy, and health check parameters.

    Binding an Origin Server

    Open the TCP/UDP Listener Management tab and click Bind Origin Servers in the operation column of a listener to bind or unbind one or multiple origin servers. If no origin server information is found, the origin server type may be invalid or the origin server is not added to Origin Server Management.

    If the listener policy is Weighted RR, you can set the weight (1–100) of an origin server while binding it. The origin server is scheduled based on the ratio of its weight to the total weight. For example, if the weight of origin server A is 60 and that of origin server B is 80, the scheduling ratio will be 60/(60 + 80) = 42.8% for origin server A or 57.2% for origin server B.

    If enabled, health check will start when the origin server is bound. You can determine whether the origin server is normal by checking the listener status. An acceleration connection will only forward packets to origin servers in normal status. Packets will not be forwarded to abnormal origin servers until they return to normal status during health check.

    For UDP listeners or the ones without health checks, packets are always forwarded regardless of the status of the origin server.

    Deleting a TCP/UDP Listener

    Open the TCP/UDP Listener Management tab and click Delete to delete a listener. If the listener is bound with an origin server, you need to tick Allow force deletion of listeners bound with origin server first. After deletion, the acceleration service for the listener's port stops.

    Was this page helpful?

    Was this page helpful?

    • Not at all
    • Not very helpful
    • Somewhat helpful
    • Very helpful
    • Extremely helpful
    Send Feedback
    Help