Alternately, you can also use the SNMP Collector GUI / Mib Browser to do this:  0- Logon to the SNMP Collector configuration GUI, through the frontend administration section, or directly: (ie: [URL] ) 1- Create a collector entry in the Collectors list that match the location of the collector you want to rename. ( correct address and communication port number ) 2- Open that collector node in the action tree (left pane), then select the synchronization node under it. 3- In the Synchronization page, you'll see a "Retrieve" the "running" configuration from the collector. Click the "Retrieve" button. 4- Go back to the Collectors list, then rename that collector; do not forget to click "Save". 5- Go to the Synchronization page for the collector, then push this configuration. A message will confirm that the collector is now using this configuration (with the new name).  Once those steps are done, logon the device-discovery application then import the collector as you've tried before.  These steps will rename the collector and ensure that the collector configuration (polling groups, agents, masks) are preserved. They will work if you have the rights to use the SNMP Collector GUI (I assume you are using the admin user) and have the required licenses to run it.  Regards, Patrick
I have installed single VM SRM Suite that includes Frontend and Backend Services on a single VM and then deployed collectors in 3 additional sites. I am trying to configure SNMP collectors on each of these sites to monitor SAN switches locally to each collector and when I create the first Collector it is automatically named Watch4NetSnmpCollector-1 if then try and add another collector from another site it then fails The SNMP Collector running on 10.8.20.56, port 2008, is named Watch4NetSnmpCollector-1. This SNMP Collector already has a registered Collector. Please delete it before creating it again..  How can I define the name of the SNMP collector on each of the collectors deployed...
Adding multiple SNMP Collectors