02-09-2012 11:47 AM
After using and commissioning Aruba boxes for some time now I have today encountered a new problem for the first time. A quick search of these forums and the Internet reveals no instant answer.
The scenario is that I unbox a new controller, complete the setup wizard then apply IP settings so I can access the device through SSH over our staging network. This works fine, as expected. The problem comes in the next step of the commissioning process where I add the license - once the PEFNG license is installed, I can no longer SSH to the box. Indeed, the GUI is broken too.
This is on 3400 controllers with OS 188.8.131.52.
I expect it is a trivial aspect of the config we are using the new PEFNG licenses and 184.108.40.206 for the first time.
Has anyone else come across this or know how to resolve the issue?
02-09-2012 11:56 AM
Hi - yes, the device has been rebooted several time - as it took a while to work out it was the PEFNG lisence causing the issue.
All vlans are trusted on all ports, to be on the (not) safe side.
I've also tried data path in as VLAN 1, not vlan 1, untagged and tagged... this seems to make no difference. I have a bunch of these devices all manifesting the same behaviour.
Surely it's something frustratingly simple? (yes, I've raised a TAC - #1279848)
Thanks for your help
02-09-2012 12:16 PM
yep - console works fine, so I can ping:
from controler to default gateway
from laptop to controller
from core switches to controller and back
There have been no changes ot this network for some time.
02-10-2012 05:55 AM
I don't believe so, - I haven't configured any. What's a good command to check?
If you have not configured any, you don't have any. Please continue to work with support, since a reboot didn't fix it.
02-22-2012 10:12 AM
can you try the following commands,
show user | in <ip address of device from where you are trying to SSH>
show datapath session table <ip address of device from where you are trying to SSH>