Intuitive? No.
Wild and Wacky? Yes!
After my upgrade and hand rebuild last night, I was compiling a list of stuff to report on, but the other thread seems to have covered most of it. This was my first pet peeve, as my only record of what goes on is my splunk server receiving syslogs. Thanks for the info, I wonder what the user manual would look like with this update?
Other observations:
- Some mispellings fixed in the saved config file, like the Pirmary DNS becoming Primary DNS. Still many other bad spellings. I must assume this makes using config files from different firmware revs would cause funny stuff?
- GUI does look nice, but omygawd dija have to use frames? And having to expand each category each time is a pain. At least before all was laid out to see. What's funny is that it looks just like the DLink firmware upgrade of a couple of years ago.
- Hasn't crashed yet, but it's only been 16 hours.
- As I mentioned in other thread, Cisco does not acknowledge any of the stated issues in the release notes for 2.0.0.5. And there is a 2.0.0.6 in evidence in the powerpoint explaining how to make an exported config actually restorable. (Which, btw, is yet another Wild and Wacky thing to have to do...)
So, ONCE AGAIN, I ask Cisco to make a forward looking statement on the future of these devices. Is it bad hardware? Can the firmware be fixed, not just gussied up so it's all perty? I saw from the other thread that units being delivered with 2.0.0.5 are still hardware rev.12, so that's not an option yet.
