In order to discover a device, it must have an IP address belonging to the discovery range and a username and password
pre-populated in the Default Users tab. The device must be a type supported by the appliance as listed in the firmware
release notes.
Whether performing a discovery, importing or manually adding a device, the appliance will always perform a capabilities
discovery to determine the licensed feature set of each device in order to display session buttons or control capabilities
appropriate for what the device will support. For example, an HP iLO without an advanced license does not support vKVM.
When added to the appliance, the capability discovery will recognize the license in the iLO and will disable the
vKVM session button.
CAUTION: The appliance requires most SP types to have IPMI enabled in order to be discovered or managed.
Some SPs will have IPMI disabled by default, for example, iDRAC7. If the SP is physically connected behind
the appliance and cannot be discovered or added due to an IPMI problem, you may manually add the
SP using the generic profile. Then launch an SP Access browser session to the SP and correct the
IPMI problem. Then delete the generic SP and add it using the appropriate SP profile.
Physical discovery
The appliance has a DHCP service active by default running on the priv virtual interface.
SPs physically connected to the appliance and configured as DHCP clients will be issued an IP and then queried for
discovery. A DHCP scope is, by default, assigned only to the priv virtual interface and associated physical ports. The spm
and kvm virtual interfaces do not have addresses assigned to them by default. To assign DHCP ranges to the spm and kvm
virtual interfaces to discover and manage certain classes of devices independently, the virtual interface must first be
assigned an IP. The priv virtual interface is by default: 192.168.10.1/24.
To assign virtual interfaces IP addresses:
1.
Browse to the Network Settings page located at
Administration - Targets - Port Configuration - Network
Settings
.
2.
Use the drop-down menu under state to enable the interface.
3.
Enter the IP address/mask and broadcast address.
4. Click
Apply
.
The IP address (CIDR format) is sometimes referred to as prefix notation for an IP/mask combo. The IP/mask information
required is the number of bits occupying the network portion of a subnet mask when displayed in binary notation. The
following table is an example.
DECIMAL
BINARY
PREFIX/CIDR
EXAMPLE
255.0.0.0
11111111.00000000.00000000.00000000
/8
10.1.2.3/8
255.255.0.0
11111111.11111111.00000000.00000000
/16
172.18.1.4/16
255.255.255.0
11111111.11111111.11111111.00000000
/24
192.168.1.10/24
255.255.255.252
11111111.11111111.11111111.11111100
/30
176.23.8.1/30
Table 5.8 CIDR Format Example
After assigning the virtual interface IP addresses, new DHCP ranges can be created. It is important to ensure that the DHCP
range is appropriate for the IP assigned to the virtual interface but that the range does not contain that IP (avoid potential
for IP conflict). The virtual IP should be assigned as the gateway for the new range.
To create dynamic DHCP ranges:
1.
Browse to
Targets - Port Configuration - DHCP Settings.
2.
Under Dynamic Ranges, click
Add
.
3.
Enter the Subnet address, the start and end range, the subnet mask and the gateway.
4. Click
Apply
.
Vertiv
| Avocent® Universal Management Gateway Appliance Installer/User Guide |
39
