Mike, I'd characterize it as a very bad idea if your network isn't down and you call in to make your case a P1/P2.
If your TAC engineer isn't responding you can call in and requeue the SR, but raising severity would only hurt you (the customers), if TAC is busy with fake P1/P2's and an actual network down event happens. Regards, Faisal On Jan 9, 2008 7:33 AM, Mike King <[EMAIL PROTECTED]> wrote: > Nevermind, Just saw that your engineer was clueless. > > If your TAC is on vacation, and will not forward, ask to speak to the Duty > Manager. > > Repeat the words > "This has become a network down emergency" > > Because if nobody is getting on thru CCA, my network is down. > > You should have a new TAC engineer speaking to you in about 3-5 minutes. > > On Jan 9, 2008 7:30 AM, Mike King < [EMAIL PROTECTED]> wrote: > > > You have a TAC case open? > > > > > > On Jan 8, 2008 2:23 PM, Stanclift, Michael < > > [EMAIL PROTECTED]> wrote: > > > > > As soon as we upgraded every check we had (virus defs, windows > > > updates, etc) all started causing this error. > > > > > > > > > > > > *Michael Stanclift* > > > > > > *Network Analyst* > > > > > > *Rockhurst University* > > > > > > > > > > > > Conway Hall, Office 415 > > > > > > 1100 Rockhurst Road > > > > > > Kansas City, Missouri 64110 > > > > > > (816) 501-4231 > > > > > > > > > > > > *From:* Cisco Clean Access Users and Administrators [mailto: > > > [EMAIL PROTECTED] *On Behalf Of *Caines, Max > > > *Sent:* Tuesday, January 08, 2008 11:25 AM > > > *To:* [email protected] > > > *Subject:* Re: 4.1.3 Agent Issues > > > > > > > > > > > > Interesting. Are you using WSUS checks (as we are)? If so, do you have > > > "Show UI" checking on the requirement definition? I turned it on because I > > > understood 4.1.3 fixed the bug which previously made it unwise to use > > > it, but I'm wondering if that was a bad idea > > > > > > > > > > > > Regards > > > > > > > > > > > > Max > > > > > > > > > ------------------------------ > > > > > > *From:* Cisco Clean Access Users and Administrators [mailto: > > > [EMAIL PROTECTED] *On Behalf Of *Stanclift, Michael > > > *Sent:* 08 January 2008 14:45 > > > *To:* [email protected] > > > *Subject:* Re: [CLEANACCESS] 4.1.3 Agent Issues > > > > > > This is the same problem I'm having and our TAC engineer was clueless > > > (and is on vacation this week and refused to forward my TAC to another > > > engineer.) The problem is we ONLY allow McAfee AntiVirus Enterprise to get > > > on our network. > > > > > > > > > > > > *Michael Stanclift* > > > > > > *Network Analyst* > > > > > > *Rockhurst University* > > > > > > > > > > > > > > >
