--- title: "Exporting an existing token from a Central Management System peer using the CLI" slug: "exporting-an-existing-token-from-a-central-management-system-peer-using-the-cli-2" updated: 2026-08-25T21:17:42Z published: 2026-08-25T21:17:42Z canonical: "docs.trellix.com/exporting-an-existing-token-from-a-central-management-system-peer-using-the-cli-2" --- > ## 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. # Exporting an existing token from a Central Management System peer using the CLI Use the CLI commands to export an existing authentication token from a Central Management System peer. Use this procedure when you want to use an existing token with another Central Management System peer but do not want to generate a new token. When a token is exported, it is displayed. You can copy the existing token and send it to the administrator of a Central Management System peer. To export an existing authentication token with a Central Management System peer: 1. Go to CLI configuration mode. ``` CMS1 > enable CMS1 # configure terminal ``` 2. Export an existing token. Partial output of the existing token is displayed. ``` CMS1 (config) # cms peer-service auth-token export AUTH-TOKEN = "PD94bWwg.........." AUTH-TOKEN CHECKSUM = "234b19a369887ef5b0bbfd269c477704" . . . ``` 3. Copy all the characters of the existing token within the quotes, but do not copy the quotes, from the exported auth-token. 4. Paste the exported token to an out-of-band mechanism (for example, a signed email). 5. Send the exported token to the administrator of the CM peer. :