How Fired Am I?

[dlots]

Cool
It's time to loot the storage closet and make your home lab much better :-)

[wintermute000]

If you really know as much ISE as you claim then you should have no issues finding work in that arena. Its red hot ATM and you get to drink the trustsec koolaid. Bone up on your wireless integration FTW. We have a guy here who's pretty much spent the last year doing nothing but ISE, cisco WLC and trustsec deployments.
But yeah technical security administration is usually thankless IMO, even driving firewalls (as an admin, happy to ride in on the contractor train and bail before the real problems occur lol).

[deanwebb]

I had some very good advice from my boss' boss: build up a network among my stakeholders. If I know people in different groups and have good communications with them, I can get information from them faster and when stuff hits the fan, they'll help me clean up the fan blades instead of complaining about the smell. I won't get 100% of my stakeholders to happily join in, but if I can get good numbers, that helps when things come down to a vote, like when *their* bosses make decisions in meetings based on what those engineers say.

I immediately started to build my network and found the AD issue that was causing the wireless NAC problem. Getting some attaboys now, so firing level now reduced to 1.

[icecream-guy]

I had some very good advice from my boss' boss: build up a network among my stakeholders. If I know people in different groups and have good communications with them, I can get information from them faster and when stuff hits the fan, they'll help me clean up the fan blades instead of complaining about the smell. I won't get 100% of my stakeholders to happily join in, but if I can get good numbers, that helps when things come down to a vote, like when *their* bosses make decisions in meetings based on what those engineers say.

I think that's called networking

[wintermute000]

you must have it bad. In my experiences, due to the 80/20 rule (20% of the people do 80% of the work) in most large orgs, the 20% know each other well and its always the informal back-channel network that gets the triages rolling the fastest. I always know the two or three SAN / wintel / vmware / unix guys I'd call first and know they would take me seriously and vice versa.

[icecream-guy]

one of our most recent deletions, coworker offered to help another group with something not networking related. soon found out he was in too deep and sent an email to the people, that he wasn't going to work in the project anymore. People whom he didn't understand who they were (higher-ups) were on the email distro, he and got his badge confiscated and was escorted off premises by security for failing to do his job.

lessons learned.
1. know who you are sending email to
2. do not offer to help with tasks outside your job scope.
(we had a team meeting and this was hammered into our skulls)

[deanwebb]

Wintermute: this company is very large and for some towers, 100% of the staff are in Europe, so it's very difficult to develop that collegiate, lean-over-the-cube relationship. I'm working on it, though.

[deanwebb]

Looks like I made some good headway at developing that transatlantic collegiate relationship:

"Holy shit guys, this is the best contact from the Connectivity tower I've ever gotten." <- Manager to his team, just now. Yeah, that's right. He's talking about me.

[hizzo3]

:clap: to boldly say that a corporate buzz word concept is bad for something... That takes balls. Glad it worked out for you Dean.