K2000 Boot Actions not always working
From time to time we are seeing an issue when we set a boot action on a machine, usually to install a scripted install. The machine PXE boots, lists the boot action it was set to perform (the scripted install with the default KBE for that architecture) and starts downloading the KBE. Once the KBE loads, it just goes to the Recovery Console menu and does not start the scripted install. The boot action is still listed in the K2000. Reboot from PXE and try again and usually it works fine. Any ideas?
Physical K2200 v3.4.54256, although we saw it occasionally with 3.3 and on a VM K2000.
Answers (3)
Probably Network Communication Issues
I ran into that on some machines and it came down to the network causing communcation problems. I also ran into a driver not negotiating speed properly and the switch would reset and drop the connection, try to renegotiate the speed and cause a timeout.
Interesting, as if it connects to the k2, I would think it checks in as you don't get a valid deployment menu screen until we check the mac address with the K2 to verify it has a license.
Corey
Lead L3 Enterprise Solutions Engineer, K2000
If my response was helpful, please rate it!
When I've run into this issue (which happens periodically), I've deleted the machine from Systems>Boot Actions screen and then added it back via the Deploy this Scripted Installation to a System link (on the Scripted Installation Detail page). Typically the second attempt works fine.
In a couple of instances the issue kept occurring, in which case deleting and rebuilding the scripted install from scratch resolved the issue. What I have found to work the best is to create a "baseline" scripted install (with just the OS and basic tasks), verify that works consistently, then Duplicate it and add other postinstall tasks.
John
