Damn you. Damn you to hell.

I'm a big time Cisco kool-aid drinker. All my certs are Cisco, I have worked on primarily Cisco gear my whole career.

I'm not a programmer, can't stand it, but I do understand that no code is 100% perfect. There will always be bugs, I get it.

But holy SHIT, can we please by this point in your release train (version 8.2.151!!!!) just get a version that does the following three simple things:

1.) Fixes a couple of major, catastrophic, service interrupting bugs

2.) Is compatible with all of your various wireless hardware (APs and controllers)

3.) Doesn't introduce MORE catastrophic bugs

How hard is that?! The bug we're running into now, has apparently been around since release 8.0.100, a LONG FUCKING TIME!

To boot, we were promised this code to fix the other issues we're trying to get rid of, and had the publish date pushed back on us for a month and a half due to 'extended testing requirements'. Yeah, lot of good all that damn testing did, considering this one bombs out too!

So here I sit, half past midnight, trying to implement your janky workaround just so I can stop the users in my Melbourne, AU office from complaining about the fact that they can't get work done on the wi-fi, which they primarily use for Facebook, Instagram, and YouTube (AVC is a mo-fo if you're trying to hide this stuff, guys).

What a wonderful night.

This message has been edited. Last edited by: jcat,

Don't forget to ISE your NADs

Or some shit like that. I'm not a network nerd, but I know we have at least one Cisco SE on here..

quote:

Originally posted by exx1976:
Don't forget to ISE your NADs

Or some shit like that. I'm not a network nerd, but I know we have at least one Cisco SE on here..

Don't even get me started on ISE. Haven't had many software bug type issues but the PS time we paid for was utterly useless.

Officially: No comment and the opinions expressed in this post are my own views and not those of Cisco.

Make sure your account team knows your issues, they can let the right people know.

One of my customers has caused some heartburn with uncovering 3 bugs in the same train of code in less than 2 weeks.

So I can sympathize with your frustrations.

quote:

Originally posted by mkueffer:
Officially: No comment and the opinions expressed in this post are my own views and not those of Cisco.

Make sure your account team knows your issues, they can let the right people know.

One of my customers has caused some heartburn with uncovering 3 bugs in the same train of code in less than 2 weeks.

So I can sympathize with your frustrations.

No worries, account team is well aware as is HTOM (yep, we're one of those customers)

I've upgraded code no less than half a dozen times in as many months, all for defect corrections. I don't mind upgrading if it's gonna fix stuff, but when you delay your release by a month and a half for supposed 'testing', I expect it to be pretty tight by the time I finally get it!

It could be worse...the software you tied your wagon to could've been bought by Oracle. Hyperion Essbase used to be developed in CT and San Fran. Now it's all done in India. Pure shit.

One word: Aerohive

quote:

Originally posted by SPWAMike0317:
One word: Aerohive

Yeah, I've got experience with most of the major players (ruckus, aerohive, etc). I like aerohive but trying to convince an enterprise with over 600 access points in 60 offices around the world to forklift from Cisco to anything else isn't easy.


I actually worked with Keith Parsons at a previous company when he was consulting for ruckus before joining aerohive. Talk about a dude who knows his stuff.