How to implement BVI on a WAAS device to support the virtual machine features. This is what I came up with for a remote device that is in production. This limits the impact to operations.
WARNING: This is not an inline configuration – I am using WCCP. Do not use this config on an inline configuration.
- Log into the device using telnet –
- Run the following command (Put the device name in place of Nameofdevice) –
copy startup-config ftp SERVER-IP Nameofdevice
- Browse to the directory of the FTP server
- Open the file and replace the following code –
primary-interface GigabitEthernet 1/0
!
interface GigabitEthernet 1/0
ip address ##IP Address of copied device## ##Subnet Address##
exit
!
- Put in place (Make Sure to copy the IP Address over!!!)–
- NOTE: If you are using radius, make sure to copy the radius password into the config. Otherwise you will notice that when you upload the new change, it will not be applied.
primary-interface BVI 1
!
bridge 1 protocol ieee
!
interface BVI 1
ip address ##IP address of copied device## ##Subnet Address##
exit
!
interface GigabitEthernet 1/0
bridge-group 1
exit
!
- Go back to the telnet session –
copy ftp disk SERVER-IP / Nameofdevice Nameofdevice
Some notes on this command – The “/” stands for the root directory
The first name stands for the remote file name
The second name is what you want it called on the upload
copy disk startup-config Nameofdevice
- Reboot the device –
reload
Proceed with reload?[confirm]
Proceed with clean WCCP shutdown?[confirm]
Existing connections = 72 Press ^C to skip waiting for clean WCCP shutdown
Note – Let the system reboot on its own, if it asks you to save configuration changes, don’t.
System configuration has been modified. Save?[yes]:no
I rebooted one of my WAE-274 devices; clean reboot of course. It took approximately 6 Minutes 52 Seconds for a full reload – mileage will vary.