This switch is shipping with an unsupported BVS1.0 firmware that will be changed, and it does not operate as the Guide says. This is the reason a corrected guide is not provided.
ADTRAN apologizes for this current issue.
To access the device with firmware versions earlier then the supported R13.2.3, you have two options.
Option 1. The console port will allow you access to the switch with a serial Cisco cable to the unit.
From the console interface, you can set the IP address of the switch, to allow you web access later. Defaults -
Username: admin
Password: password
Example:
1550-24>
1550-24>en
1550-24#con t
1550-24(config)#int vlan 1
1550-24(config-intf-vlan 1)#ip address 10.19.221.50 /24 <------- Whatever IP address you like
1550-24(config-intf-vlan 1)#no shut
1550-24(config-intf-vlan 1)#exit
1550-24(config)#exit
Appropriate commands must be issued to preserve configuration.
1550-24#wr
Building configuration...
- Success!
1550-24#
Now using a PC connected to an Ethernet port ( with IP address 10 .19.221.51 ) you should be able to access the switch web interface. http://10.19.221.50
Option 2. If you connect the switch to a network with a DHCP server, you should be able to hit the Web interface at the 10.10.10.1 ( or the DHCP assigned IP address) as the Quick Start Guide documents. The IP address assigned, will bring up the VLAN interface and then the secondary IP 10.10.10.1 will also be responsive.
As far as all Adtran switches, it is recommended to upgrade them to the current EMR release ( currently R13.2.3 ). This is especially true of the 1550 series switches since they can become completely un-responsive with BVS1.0 firmware.
The firmware is available on our website www.ADTRAN.com under Home»Support»Product Downloads»Software Releases
The upgrade instructions are also linked in the Release Notes of the Firmware release. It will point to https://supportforums.adtran.com/docs/DOC-1672 for Upgrading Firmware in AOS.
The web interface firmware upgrade is usually the easiest method.
- P.S. Upgrades can be done during working hours and the required reboot will not happen till administrator requests the reboot with the CLI command or web interface. So firmware can be loaded and waiting till the maintenance window allowed reboot.
