Controller-less WLANs

enet0_bridging gets enabled accidentally

Aruba Employee

Symptoms

Why is Aruba Instant not able to get IP address after reboot and works on factory reset? 
Why did enet0_bridging get enabled on reboot after CLI configuration?

Diagnosis

Any Aruba Instant running code version 6.2.1.0-3.4.0.1 or older

 

CLI configuration was being done on Access Point and on reboot; AP doesn't get IP address / doesn't come up.

Solution

Aruba Instant doesn't have an additional enable mode with enable password. When logged in with admin credentials; user can directly execute show / action commands.

Out of habit; admin user may accidentally execute "en" command. As the only match is "enet0-bridging"; it would get enabled. Since enet0-bridging is an action command; it can be enabled without entering config mode and the effect takes only on reboot.

 

6c:f3:7f:c4:0b:6a# en?
enet0-bridging


6c:f3:7f:c4:0b:6a# en
6c:f3:7f:c4:0b:6a# reload

The system is going down NOW !!

Sending SIGTERM to all processes.
Jan 1 00:02:52 udhcpc[1094]: Received SIGTERM


Sending SIGKILL to all processes.

Please stand by while rebooting the system.
Restarting system.


APBoot 1.2.6.7 (build 30025)
Built: 2011-08-30 at 17:41:16

Model: AP-13x
CPU: 88F6560 A0 (DDR3)
Clock: CPU 1600MHz, L2 533MHz, SysClock 533MHz, TClock 200MHz
DRAM: 256MB
POST1: mem 0 mem 1 mem 2 mem 3 passed
Flash: 16 MB
Power: 802.3at POE
LAN: done
PHY: ....done
PEX 0: RC, link up, x1
bus.dev fn venID devID class rev MBAR0 MBAR1 MBAR2 MBAR3
00.00 00 11ab 6560 00005 02 f1000000 00000000 00000000 00000000
00.01 00 168c 0030 00002 01 90000000 00000000 00000000 00000000
PEX 1: RC, link up, x1
bus.dev fn venID devID class rev MBAR0 MBAR1 MBAR2 MBAR3
01.00 00 11ab 6500 00005 02 f1000000 00000000 00000000 00000000
01.01 00 168c 0030 00002 01 94000000 00000000 00000000 00000000
Net: eth0, eth1
Radio: ar9390#0, ar9390#1

Hit <Enter> to stop autoboot: 2 0
apboot> print
bootdelay=2
baudrate=9600
autoload=n
boardname=Arran
servername=aruba-master
bootcmd=boot ap
autostart=yes
bootfile=armv5te.ari
ethaddr=6c:f3:7f:c4:0b:6a
os_partition=0
enet0_bridging=1
stdin=serial
stdout=serial
stderr=serial
ethact=eth0

 

To recover the following can be done ::

factory reset the AP (if there is source to get the config and there is no static config on AP)

From apboot>; execute purge (if there is no other static config)

From apboot> execute; setenv enet0_bridging

apboot> setenv enet0_bridging

apboot> save

Saving Environment to Flash...

Un-Protected 1 sectors

.done

Erased 1 sectors

Writing

 

apboot> printenv

bootdelay=2

baudrate=9600

autoload=n

boardname=Arran

servername=aruba-master

bootcmd=boot ap

autostart=yes

bootfile=armv5te.ari

ethaddr=6c:f3:7f:c4:0b:6a

os_partition=0

stdin=serial

stdout=serial

stderr=serial

ethact=eth0

To avoid this accidental enabling of enet0_bridging; a no-operation i.e. dummy enable command has been included starting from 6.2.1.0_3.4.0.2

6c:f3:7f:c4:0b:6a# en?
enable
enet0-bridging

6c:f3:7f:c4:0b:6a# en
% Incomplete command.

Version history
Revision #:
1 of 1
Last update:
‎06-01-2014 08:21 PM
Updated by:
 
Labels (1)
Contributors
Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: 
Is this a frequent problem?

Request an official Aruba knowledge base article to be written by our experts.