wbrown

I'll buy that. Until we got a truly DPI capable firewall in-line with outbound user traffic we really didn't have an effective means of contolling something as "simple" as IM. I say "simple" because most IM products do so much more than just relay text messages.

That link is an April Fools joke, but same name was being mentioned in new TheRegister articles yesterday.

Same here. I'm thinking today's daily was yesterday's bonus question.

Yup. If the resource isn't usable then reachability doesn't really matter.

I am way too paranoid to ever trust a cloud service for my logs. There's too much recon data in there. I'm sure I'm not the only person to ever mistakenly type my password when the prompt was expecting username. Suddenly those failed login attempt logs have alot more value to a data miner or attacker. 

(Reachibility v. Availability) v. Acceptibility might be a better process. Reachability means we can get there, Availability means we can get the resources, but Acceptibility means we can access the data in a period such that the data is still useful. I hear from patient care providers at remote sites often when anything…

I've thought about doing that and using SAM to run the scripts but that would take more dev time that I have available for the forseeable future.

We've had exactly those finger-pointing conversations many times. So far our server/virtualization admins control vSphere and all components including the v-switch. All we can say from the network side is we (network operations) see no errors on the trunk that we are providing to the hosts and that the requested vlans are…

The problem I ran into is that the installer indicates my architecture must be x64. So no installation for me on my work box.

Too true. An example I use for some environments I've reviewed in the past is "Yes, critical segment ABC is isolated from the non-trusted segments by a firewall. Just ignore that 'permit ip any any' line at the top of the ACL." The existance of a firewall appliance as the only means in/out of the environment allowed for…

Wish I could say I've never done that. Lesson learned: don't make firewall changes the day before going on paternity/maternity leave.

I'd like to be able to monitor the status of the drives in the chassis. Although this may first require some software updates on the part of F5. I've tried to find OIDs to reflect drive array/ disk drive status but haven't had any success.

That gets right to the point of my opinion - experienced help desk personnel are helpful and a good source of info. Inexperienced personnel, or those that can't think outside of a script, are worse than useless.

I'd add hardware, software, and HVAC to that list. We're planning a VoIP rollout for one of our facilities where our biggest concerns are hardware/software, power, and cooling. All our phones use PoE. The first issue is we need to upgrade the switch software to handle VoIP. Upgrading the switch software requires upgrading…

"In space no one can hear you scream."

"Entrant will receive double his/her wager..."

I would really say it is the job to be done, along with the desired efficiency of doing that job, that drives both the hardware and the software. When driving a nail certain hardware is needed to drive that nail but at the same time certain software is required to use the impact-driver/hammer/big-f'n-rock/etc correctly.

I completely agree. Which is why I don't agree with todays answer.

As others have mentioned I think you really need both internal and external monitoring so that you can get a measurement from the users' perspective as well as to compare the data from the different monitoring viewpoints.

Completely agree and couldn't really have said it any better.

I've got a poller for Catalyst 4500's that may provide the budget you're looking for: Cisco Catalyst 4500 PoE pollers

It's the same video from the May 7 link. You may want to try using the link from that day.

Do respondents have to be currently working in public sector, or would working in public sector within recent months or years qualify?

The bookshelf in my cube.

Networks need 3 "eens" to keep running: Caffeine, nicotine, and codeine. _____ is happening soon? Is that soon in human terms or geologic terms? (one of my favorites taken from The Register) Total Inability To Support Usual Performance.

First time winner here too. My 18-month old is going to enjoy sitting on Daddy's lap and playing with this

IP SLA support is dependent on your firmware, and then it has to be enabled with the feature command. As to not recognizing the machine type, that is a problem with Orion in general and getting updates into the MIB DB.

As Stephen Occhiogrosso mentioned, look through the config guides. If you don't find any mention of IP SLA being available for your older Cisco gear (i.e. Catalyst 4500/Sup2 running IOS 12.2) then look for RTR. Response Time Reporter is what Cisco called the previous version of SLA.

Oh yes, been there. It's always the network's fault, and especially the firewall's fault. So being the firewall admin I show up prepared to do battle. The battle isn't really to point blame at someone else but rather to make sure the network/firewall isn't blamed without reason and that we actually get down to finding out…

I'd say a possible total of 9000 points (3000 from drawing questions, 6000 from thwack stack) is plenty for a single month.