# switch pmm clients to new pmm server

**URL:** <https://forums.percona.com/t/switch-pmm-clients-to-new-pmm-server/5602>\
**Category:** PMM 1.x\
**Created:** [May 15, 2017, 9:34am UTC](https://forums.percona.com/t/switch-pmm-clients-to-new-pmm-server/5602 "2017-05-15T09:34:22Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![jackber](https://avatars.discourse-cdn.com/v4/letter/j/898d66/32.png) [@jackber](https://forums.percona.com/u/jackber)\
**Post date:** [May 15, 2017, 9:34am UTC](https://forums.percona.com/t/switch-pmm-clients-to-new-pmm-server/5602/1 "2017-05-15T09:34:22Z")

</div>

Hi,  
i’ve been running new PMM server.

- both of pmm server has the same OS (suse SLES 12 sp2), username and password.
- i’ve changed parameters in /usr/local/percona/pmm-client/pmm.yml and restart service (pmm-admin restart)
- network check is OK:  
"# pmm-admin check-network  
PMM Network Status  
Server Address | [correct server IP]  
Client Address | [correct client IP]

- Connection: Client → Server

* * *

SERVER SERVICE STATUS

* * *

Consul API OK  
Prometheus API OK  
Query Analytics API OK  
Connection duration | 153.578µs  
Request duration | 508.65µs  
Full round trip | 662.228µs

No monitoring registered for this node identified as ‘[client name]’."

Which steps are missing to switch pmm clients to new server ?

---

<div class="post-metadata">

**Author:** ![Michael\_Coburn](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/michael_coburn/32/18_2.png) [@Michael\_Coburn](https://forums.percona.com/u/Michael_Coburn)\
**Post date:** [May 15, 2017, 2:30pm UTC](https://forums.percona.com/t/switch-pmm-clients-to-new-pmm-server/5602/2 "2017-05-15T14:30:13Z")

</div>

Hi [jackber](https://percona.vanillacommunities.com/profile/x/x/37853) ,

The best approach is to remove all local monitoring and then re-add. The example below shows how to stop, remove, and re-add - note that in your case you probably want a MySQL, MongoDB, or ProxySQL stanza instead of just linux:metrics for removal, and re-addition:

```auto
pmm-admin stop --all
pmm-admin list
pmm-admin remove linux:metrics 
pmm-admin config --server
pmm-admin add linux:metrics

```

There is no state maintained on the client, rather they are passive listeners for incoming scrape requests from Prometheus. In your case, Consul on the new PMM instance isn’t aware of the host to be newly scraped so Prometheus never attempts to collect metrics. Hope this helps,

---

<div class="post-metadata">

**Author:** ![jackber](https://avatars.discourse-cdn.com/v4/letter/j/898d66/32.png) [@jackber](https://forums.percona.com/u/jackber)\
**Post date:** [June 1, 2017, 7:24am UTC](https://forums.percona.com/t/switch-pmm-clients-to-new-pmm-server/5602/3 "2017-06-01T07:24:07Z")

</div>

It’s correct. Thanks a lot !