Got an eval, configured all sorts of things and then got to a point where the config didn't update on the 9004 any more. From 9004 I was able to ping 22.214.171.124 etc but show switches showed something like "update successful, master unreachable".
At this point would've there been some way to diagnose what went wrong and why the new configs didn't get pushed to the controller?
I rebooted the gateway, but at the boot it got stuck at "Waiting for Controller IP" message. Where it has been the last 24 hours. I only have remote console but can't reboot the gateway for now. Might have to drive down to our lab to do some sort of full reset for the box. Hopefully this is something that doesn't happen all the time in the production?
Anyone had similar issues? I have 126.96.36.199_73853 installed.
This 9004 controller is managed from Central? Do you have system-IP configured?
Yes it was Central managed and it was working previously. Not sure which config changes broke it so bad it didn't get the updates. I had also system IP configured previously.
I think system IP was removed / not pushed for some reason... You might want to go in debug / disaster-recovery mode to check that..
System IP was available just before I booted, check with 'show ip int brief' (as I was wondering why it says master unreachable and was wondering if I've lost the IP addresses for some reason). I could also ping the system IP from my computer just fine. Now it's stuck at the System IP boot message so it's not possible to go to any mode. I'll hope to get to the site tomorrow or so and do a full reset for the box, though this is not really convincing.
If possible, open a case with TAC to find the root cause.. Update the thread accordingly afterwards..
Would there be any update on this issue?
Didn't find any real solution with TAC either. Just had to reset the gateway. Hopefully it doesn't happen often in the future.
Yes, it would be nice to have more debugging options in this case. I've also managed to get the BGW up again. I've set the cfgfile to the value 'dummy' in cpboot (setting it to default.cfg didn't help). Then the initial provisioning menu came up and the GW also appeared (once) in Central. After upgrading the BGW and reboot it lost connection to Central for some reason. It was not pingeable either. I had to reboot again and remove the dummy cfgfile entry. At that point the BGW booted fine and was connecting to Central.
So, it is working now, but without debugging it's difficult to know why.
At Aruba, we believe that the most dynamic customer experiences happen at the Edge. Our mission is to deliver innovative solutions that harness data at the Edge to drive powerful business outcomes.
© Copyright 2021 Hewlett Packard Enterprise Development LPAll Rights Reserved.