The Promise Vtrak requires 3 IP addresses. There are two controllers and each has an IP for maintenance. There’s also a 3rd, virtual IP. When you initially setup the devices, they pull a DHCP or APIPA address and then you typically use Bonjour to log into the WebPAM for the first time. Once in, you configure the addresses and then viola, you’re good.
However, what if something happens? What if you configure the virtual IPs and something happens before you get the maintenance IPs configured. Or what if you never set the maintenance IPs in the first place and always relied on the virtual? Well, the Vtrak used to come with those configured to a default 10.0.0.2 and 10.0.0.3 IP address. You could simply give your laptop 10.0.0.4 and use one of those to tap in. Or put the device in maintenance mode, then tap in that way. However, the devices now ship with the maintenance IPs set to DCHP. For some reason, they don’t always grab an IP properly.
Therefore, you have to log in using a serial adapter, as I described yesterday. Once logged in, you can configure the virtual IP using the command line, using the net command, along with information about the settings to use, using 10.0.0.10 in this example:
administrator@cli> net -a mod -t mgmt -s "primaryip=10.0.0.10, primaryipmask=255.255.255.0, gateway=10.0.0.1"
To set the management ports, use -m and -c followed by the controller number you’ll be configuring (let’s say we’re gonna’ use 10.0.0.2 as used to be the default):
net -a mod -t mgmt -m -c 1 -s "primaryip=10.0.0.2, primaryipmask=255.255.255.0, gateway=10.0.0.1"
To then do the second controller, use -c 2 (let’s say we’re gonna’ use 10.0.0.3 as used to be the default):
net -a mod -t mgmt -m -c 1 -s "primaryip=10.0.0.3, primaryipmask=255.255.255.0, gateway=10.0.0.1"
Once set the IPs should be immediately accessible. View information that’s configured using the net command with no options:
net
