This brief guide applies to vSpace Management Center 3.6 and later versions. vSpace Management Center 3.3.1 for Window is no longer supported and it is highly recommend that you migrate to the most current version vSpace Management Center Appliance.
In previous versions of vSpace Management Center devices within the same subnet could autodiscovery the VMC, join and add their configuration to the database. The functionality has been deprecated in current versions of VMC as it lead to inconsistent and sometimes catastrophic configuration database corruptions.
N Series devices can still be automatically added to vSpace Management Center, by using DHCP scope options.
If you are unaware of how to create a custom DHCP scope option, here are some resouces:
- For DHCP on Server 2008R2/Server 2012: https://technet.microsoft.com/en-us/library/dd183679(WS.10).aspx
- For other DHCP solutions you will need to research how to create custom DHCP scope options
Requirements for the Custom Scope Option:
- Name: vSpace Management Center or VMC
- Data Type: String
- Code: #171
- Description: vSpace Management Center for N Series Management
- String value: (IP address or Fully Qualified Domain Name of VMC):1284 notice the port number is attached.
Requirement on N Series device:
Be sure the Autodiscovery box is unchecked and the N-Series device receives a DHCP assigned IP address.
Article: 1014