AppNeta - Trying to deploy a new V35, and the device does not seem to be configured.
Article ID: 254185
Updated On:
Products
Issue/Introduction
I'm having trouble configuring my V35, the configuration file didn't take correctly, or the json wasn't loaded. My IP address seems to be different.
Cause
If your V35 started but appears to be missing your configuration, you may notice:
- The hostname is incorrect - for example, the image below shows an example: vv35-kSJin
- The device is defaulted to using DHCP
- The device is using the default password
- The device is not configured for my organization (missing nis.config).
How do I resolve these issues?
These settings can easily be remedied by logging into the V35, configuring the IP (if needed) and then accessing the device over the WebUI.
If you open the console settings of your appliance, you may see the similar bootup, and a prompt to log in:
As previously mentioned, If the V35 is not configured correctly - it will default to using DHCP and the default password.
In 13.11.0 and earlier - the default password is: appneta.admin
In 13.12.0 and later, the password is the MAC address in upper case and no colons (for example, 525400E09F76)
Resolution
1. Log into the monitoring point.
Type in the username:
admin
For a password, please try any password you configured on the appliance. If it still continues to fail, the default password for a monitoring point is:
appneta.admin
or
For firmware 13.12.0 and newer, please use the MAC address on the monitoring point.
For VMware V35's, see these instructions.
For KVM V35'S, see these instructions.
2. Once logged in issue
sudo -i
3. The appliance defaults to use DHCP. Check for an IP address;
ifconfig eth0
If you need to configure a Static IP, please complete step 4.
4. Configure a Static IP using curl commands. In my example below we've used 10.0.0.100/24 - please replace the IPs below with the correct static IP address if needed.
curl -ku admin -X POST "https://localhost/api/v1/interface/" -H "accept: application/json" -H "Content-Type: application/json" -d "{ \"name\": \"eth0\", \"family\": \"inet\", \"method\": \"static\", \"address\": \"10.0.0.100\", \"netmask\": \"255.255.255.0\", \"gateway\": \"10.0.0.1\"}"
When you hit enter, you will be prompted for your password to begin.
5. Restart networking for the change to take effect.
sudo systemctl restart networking
6. The appliance should now be online, you can now test for IP connectivity using ping. Once confirmed working, from a computer in the local network, please attempt to log into the appliance's webui. In my example:
http://10.0.0.100/
Log in with username:
admin
and the previous password used.
7. You may now continue configuring the appliance through the Webui:
8. Check for the Monitoring Points NIS.configuration, consisting of NIS address and Site Key, ect.
9. If this information is missing, additional steps will need to be made to ensure the V35 is able to connect online. Please see this following information to configure apply NIS.config:
How to get a copy of your nis.config file:
https://knowledge.broadcom.com/external/article/240444
Provisioning an AppNeta monitoring point with a NIS.CONFIG file:
https://knowledge.broadcom.com/external/article/242839
Feedback
