--- title: "Sending a management request in a NAT deployment using the File Protect CLI" slug: "sending-a-management-request-in-a-nat-deployment-using-the-file-protect-cli" tags: ["File Protect (FX)", "Product Usage"] updated: 2026-10-01T20:53:15Z published: 2026-10-01T20:53:15Z canonical: "docs.trellix.com/sending-a-management-request-in-a-nat-deployment-using-the-file-protect-cli" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # Sending a management request in a NAT deployment using the File Protect CLI Use the commands in this section to send a management request from an File Protect appliance in a NAT deployment to the Central Management System appliance. The following topologies are supported: - [Central Management System and File Protect appliance behind the same NAT gateway](/network-and-platform/docs/sending-a-management-request-in-a-nat-deployment-using-the-file-protect-cli#central_management_system_and_file_protect_appliance_behind_the_same_nat_gateway) - [File Protect appliance behind NAT gateway and Central Management System in external network](/network-and-platform/docs/sending-a-management-request-in-a-nat-deployment-using-the-file-protect-cli#file_protect_appliance_behind_nat_gateway_and_central_management_system_in_external_network) - [Central Management System behind NAT gateway and File Protect appliance in external network](/network-and-platform/docs/sending-a-management-request-in-a-nat-deployment-using-the-file-protect-cli#central_management_system_behind_nat_gateway_and_file_protect_appliance_in_external_network) - [Central Management System and File Protect appliances behind different NAT gateways](/network-and-platform/docs/sending-a-management-request-in-a-nat-deployment-using-the-file-protect-cli#central_management_system_and_file_protect_appliances_behind_different_nat_gateways) ### Caution If the File Protect appliance has never sent a management request, ensure the requirements described in [Preparing a File Protect appliance to send a management request in a NAT deployment](/network-and-platform/docs/preparing-file-protect-appliance-send-management-request-nat-deployment) are in place before you attempt to send the request. ### Central Management System and File Protect appliance behind the same NAT gateway To send a management request: 1. Log in to the File Protect CLI. 2. Go to CLI configuration mode: ```plaintext appl-hostname > enable appl-hostname # configure terminal ``` 3. Specify the hostname, or IPv4 or IPv6 address of the Central Management System appliance: ```plaintext appl-hostname (config) # cmc client server address ``` 4. Specify the authentication type and admin credentials the appliance should use to log in to the Central Management System appliance to announce itself. ```plaintext appl-hostname (config) # cmc client server auth authtype appl-hostname (config) # cmc client server auth username appl-hostname (config) # cmc client server auth password  | identity ``` where `<authType>` can be `password`, `ssh-dsa2`, or `ssh-rsa2`. 5. Save your changes. ```plaintext appl-hostname (config) # write memory ``` ### File Protect appliance behind NAT gateway and Central Management System in external network To send a management request: 1. Log in to the File Protect CLI. 2. Go to CLI configuration mode: ```plaintext appl-hostname > enable appl-hostname # configure terminal ``` 3. Specify the hostname, or IPv4 or IPv6 address of the Central Management System appliance: ```plaintext appl-hostname (config) # cmc client server address ``` 4. Specify the authentication type and admin credentials the appliance should use to log in to the Central Management System appliance to announce itself. ```plaintext appl-hostname (config) # cmc client server auth appl-hostname (config) # cmc client server auth username appl-hostname (config) # cmc client server auth password | identity ``` where `<authType>` can be `password`, `ssh-dsa2`, or `ssh-rsa2`. 5. Prevent the local IP address of the appliance behind the NAT gateway from being part of the request: ```plaintext appl-hostname (config) # no cmc rendezvous client send-client-address ``` 6. Save your changes. ```plaintext appl-hostname (config) # write memory ``` ### Central Management System behind NAT gateway and File Protect appliance in external network To send a management request: 1. Log in to the File Protect CLI. 2. Go to CLI configuration mode: ```plaintext appl-hostname > enable appl-hostname # configure terminal ``` 3. Specify the virtual NAT hostname, or IPv4 or IPv6 address and port that are mapped to the Central Management System internal IP address and SSH port: ```plaintext appl-hostname (config) # cmc client server address ``` where `<IPv4 or IPv6 address>` is the mapped IPv4 or IPv6 address. 4. (Optional) Specify the virtual NAT port that is mapped to the Central Management System internal SSH port: ```plaintext appl-hostname (config) # cmc client server port ``` The port defaults to 22 if it is not specified. 5. Specify the authentication type and admin credentials the appliance should use to log in to the Central Management System platform to announce itself. ```plaintext appl-hostname (config) # cmc client server auth appl-hostname (config) # cmc client server auth username appl-hostname (config) # cmc client server auth password | identity ``` where can be `password`, `ssh-dsa2`, or `ssh-rsa2`. 6. Save your changes. ```plaintext appl-hostname (config) # write memory ``` ### Central Management System and File Protect appliances behind different NAT gateways To send a management request: 1. Log in to the File Protect CLI. 2. Go to CLI configuration mode: ```plaintext appl-hostname > enable appl-hostname # configure terminal ``` 3. Specify the virtual Central Management System NAT hostname, or IPv4 or IPv6 address that is mapped to the Central Management System internal IP address: ```plaintext appl-hostname (config) # cmc client server address ``` where` <IPv4 or IPv6 address> `is the mapped IPv4 or IPv6 address. 4. (Optional) Specify the virtual Central Management System NAT port that is mapped to the Central Management System internal SSH port: ```plaintext appl-hostname (config) # cmc client server port ``` The port defaults to 22 if it is not specified. 5. Specify the authentication type and admin credentials the appliance should use to log in to the Central Management System platform to announce itself. ```plaintext hostname (config) # cmc client server auth authtype hostname (config) # cmc client server auth username hostname (config) # cmc client server auth password |  identity ``` where` <authType> `can be `password`, `ssh-dsa2`, or `ssh-rsa2`. 6. Prevent the local IP address of the appliance behind the NAT gateway from being part of the request: ```plaintext appl-hostname (config) # no cmc rendezvous client send-client-address ``` 7. Send the request again without including the local IP address of the appliance: ```plaintext appl-hostname (config) # cmc rendezvous client force ``` 8. Save your changes. ```plaintext appl-hostname (config) # write memory ``` :