vThunder Initial Configuration

This section describes how to configure the device.

The following topics are covered:

•     Configuration Mode

•     Management Interface Configuration

•     Password Management

•     Saving Changes

Configuration Mode

To display commands in CLI, enter a question mark ( ? ) and press Enter. The command list is displayed for each level. For syntax help, enter a command or keyword followed by a space, followed by pressing Enter. This works for commands with sub-commands also.

1.     Log into vThunder with the default username admin and password a10.

login as: admin

Welcome to vThunder

Using keyboard-interactive authentication.

Password:***

[type ? for help]

 

2.    Enable the Privileged EXEC level by typing enable and Enter.
There is no default password to enter Privileged EXEC mode.

vThunder>enable

Password:(just press Enter on a new system)

vThunder#

 

3.    Enable the configuration mode by typing config and press Enter.

vThunder#config

vThunder(config)#

 

NOTE:                            It is strongly recommended that a Privileged EXEC enable pass­word is set up as: vThunder(config)#enable-password [newpass­word]

Management Interface Configuration

Assign an IP to the management interface of the vThunder:

1.     Configure the management interface IP address and default gateway. ACOS will obtain an IP for the management interface in the following order:

a.    If there is a management port IP configuration (either a static IP address or DHCP) in the active startup-config file, then ACOS will either assign the static IP to the vThunder
management interface or will attempt to get the IP address from the DHCP server.

b.    If there is no management port IP configuration (neither a static IP address nor DHCP), then vThunder will attempt to get an IP address from an accessible DHCP server.

c.    If vThunder cannot obtain an IP address from a DHCP server, then the default static IP address of “172.31.31.31/24” will be used.

NOTE:                            The management interface is an out-of-band interface and should not be on the same subnet as any of the data interfaces. If the
management interface and the data interfaces are not kept in
separate IP subnets, some operations such as pinging may not
work as expected.

In the example below, the IP address for the management interface is 192.168.2.228. None of the data interfaces should have an IP address of 192.168.2.x.

vThunder(config)#interface management

vThunder(config-if:management)#ip address 192.168.2.228 /24

vThunder(config-if:management)#ip default-gateway 192.168.2.1

Verify the interface IP address change:

vThunder(config-if:management)#show interface management

GigabitEthernet 0 is up, line protocol is up.

Hardware is GigabitEthernet, Address is xxxx.yyyy.zzzz

Internet address is 192.168.2.228, Subnet mask is 255.255.255.0

 

2.    Optionally, configure the ACOS device to use the management interface as the source
interface for automated management traffic generated by the ACOS device:

ACOS(config-if:management)#ip control-apps-use-mgmt-port

 

vThunder(config-if:management)#exit

vThunder(config)#

Password Management

A10 recommends changing the administrator password immediately for security.

vThunder(config)#admin admin password newpassword

vThunder(config-admin:admin)#

The vThunder is now network accessible for configuration under the new IP address and admin
password.

NOTE:                            By default, Telnet access is disabled on all interfaces, including the
management interface. SSH, HTTP, HTTPS, and SNMP access are enabled by default on the management interface only and disabled by default on all data interfaces.

Saving Changes

Configuration changes must be saved to system memory to take effect the next time the vThunder device is powered on. Otherwise, the changes are lost when    the vThunder virtual machine or its host machine is powered down.

To write the current configuration to system memory:

vThunder(config)#write memory

Building configuration...

[OK]

NOTE:                            For more information, see Command Line Interface Reference for SLB and SSL guides.