Might need to purge down elements. This can be done by logging into Fabric Manager and select Server -> Purge Down Elements.

Another thing you could try is to completely remove a config from Fabric Manager and discover the whole fabric from the beginning. I've noticed that the local database of FM sometimes keeps showing ghosts of switches that have been long gone.

I cannot purge down element because this is not Fabric Manager GUI but "Fabric Manager web client" that is used for monitoring health, inventory, performance(if licnse is installed on the switch),....

I deleted the Fabric and rediscover and it is ok but old stats lost.

Thanks,

Dominique

Do you use fabric manager gui as well? The GUI on the server and web client share the same information.

Yes, I use Fabric Manager gui, but it runs as standalone version.

I restarted FMS and now it is ok with historic performance values.

Dominique

The data are collected with Cisco Perfomance Manager of Fabric Manager that runs on a server.

Local Perfromance Manager is only the standalone version with GUI to make configuration change (zoning,...). Performance data are not collected by the local Performance Manager but on the server running licensed FMS.

Dominique

I was glad to help, but indeed.... if you collected data locally, that's lost, including passwords to logon to that particular fabric.

So when you start up your local fabric manager it is logging into localhost? Something you might want to consider is logging into the server's fabric manager via your standalone client. This way any changes not saved to the switch's configuration is seen by all the users since you are all working off the same local databases.

Do I have that correct RRR?

There is no possible link between local FM and FMS running on the server because local FMS has its client/server running locally and it cannot point somewhere else.

The performance data are stored on the FMS server continuously.

When I do some changes on a switch (zoning) from the local FM, I have to distribute the change to the other switches with the "distribute" command (or gui) and if I don't want someone else to do a change in the same time I have to work with enhanced zone mode for that vsan. But it is not possible to share a common logging place for all standalone FM.

Dominique

newwdomi1 is correct. You can't use a central logging server from decentral FM GUI's. Use logging on 1 FM only: the central one.