BB Unix Network Monitor - Message
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: {bb} More paging rules questions
Barbara, et. al.,
bb-warnconfig2.pl actually shows the rules as correct, which I had expected
it to. However, people aren't getting paged for things that they should be
getting paged on. I had a router down hard for well over an hour yesterday,
and no page to the oncall engineer. This rule:
hg-group1 hg-group2 hg-group3;;test1 test2 test3 test4;;0
6;*;oncall-pager@domain.com
...should have done caused that to go through, however the engineer never
received a page.
I'm fully aware that this could have been a problem with the pager, or a
typo in another area (that pager address actually is an email forward that
gets updated whenever the oncall engineer changes, however it was working
for other things, or so I hear.
That aside (and I will investigate that possibility), another possible
problem is that the bbgen info page is not reporting correctly. I failed to
find any notifications for that host in the catchall email box.
Is there any other way to verify the paging rules without waiting for
something to fail, or purposely causing an alarm event (can't do that, and I
have no sandbox)?
Regards,
Ben Pitzer
---------------------------------------------
"Those that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
--Ben Franklin--
> -----Original Message-----
> From: owner-bb@bb4.com [mailto:owner-bb@bb4.com]On Behalf Of Hale,
> Barbara S - CNF
> Sent: Monday, June 21, 2004 11:46 AM
> To: bb@bb4.com
> Subject: RE: {bb} More paging rules questions
>
>
> Ben -
>
> You might try installing bb-warnconfig2.pl from deadcat. It will show
> you a different view of the your bbwarnsetup.cfg and bbwarnrules.cfg
> files than what bbgen does. Maybe there is some odd spacing/typo
> problem that it might show easier.
>
> Do you know if the notifications are following the bbgen info column
> -or- could it be the notifications are correct and just the bbgen info
> display is wrong? For example, if test1 on prefixabc-rtr1.mydomain.com
> goes yellow does the catchall-email actually get notified as well as the
> pager-email?
>
> If you want to send me your actual bbwarnsetup.cfg and bbwarnrules.cfg
> files, I would be wiling to take a look.
>
> Barbara
>
> ----
> Barbara Hale
> Unix Systems Administrator/CNF
> 2055 NW Savier Street
> Portland, OR 97209
> hale.barbara@cnf.com
>
> -----Original Message-----
> From: owner-bb@bb4.com [mailto:owner-bb@bb4.com] On Behalf Of Ben Pitzer
> Sent: Monday, June 21, 2004 8:05 AM
> To: bb@bb4.com
> Subject: RE: {bb} More paging rules questions
>
>
> Brothers and Sisters,
>
> I'm still having trouble with this particular issue. Here is my config,
> edited from my mistaken post of last week:
>
> hg-devices: prefix*rtr* prefix*ubr* prefix*swt* prefix*tsv*
> prefix*ups*
> pg-devmgrs: pager-email@mydomain.com pager2-email@mydomain.com
>
> Now, here's what's in bbwarnrules.cfg. The plan is to have paging from
> 8am to 5pm, then hit the oncall pager from 5pm to 8am the next morning,
> and all day on weekends (I don't think that pg-devices2 and pg-devices3
> are of interest here, except that they are the same as pg-devices, but
> with a different prefix, thus meaning a different set of hosts entirely,
> yet with the same problems):
>
> hg-devices;;test1 test2 test3 test4;;1-5;0800-1659;pg-devmgrs
> hg-devices pg-devices2 pg-devices3;;test1 test2 test3
> test4;;1-5;0000-0759 1700-2359;oncall-pager@mydomain.com
> hg-devices hg-devices2 hg-devices3;;test1 test2 test3 test4;;0
> 6;*;oncall-pager@mydomain.com
> *;hg-devices hg-devices2
> hg-devices3;*;;*;*;catchall-email@mydomain.com
>
> Now, that seems to work for most hosts in the hg-devices group. However
> a couple of the hosts in hg-devices group don't seem to work like that.
> I have bbgen installed, and I am using the info column, which tells me
> that all the hosts that should match prefix*rtr* (example is prefixabc-
> rtr1.mydomain.com) match like this (pardon the poor representation of
> the table that bbgen's info column puts out):
>
> Services Ex. Services Weekdays
> Time Recipients
> All All days
> 0000-2359 catchall-email@mydomain.com
> test1 test2 test3 test4 Mon-Fri
> 0800-1659 pager-email@mydomain.com
> pager2-email@mydomain.com
>
> Now, why would this be the case, if hg-devices is in the excluded list,
> and is included in the first three paging rules, why is it not being
> included in the after hours rules, and why is it being included in the
> catchall? I'm a bit baffled. I'm also baffled by the prefix*ups*
> devices, which have this in the info column:
>
> Services Ex. Services Weekdays
> Time Recipients
> All All days
> 000-2359 catchall-email@mydomain.com
> test1 test2 test3 test4 Sun,Sat
> 0000-2359 oncall-pager@mydomain.com
> test1 test2 test3 test4 Mon-Fri
> 0000-0759 1700-2359
> oncall-pager@mydomain.com
> test1 test2 test3 test4 Mon-Fri
> 0800-1659 pager-email@mydomain.com
> pager2-email@mydomain.com
>
> So, this one catches all of the first three rules, but also hits on the
> catchall, from which it is supposed to be excluded. Can anyone shed
> some light here? Thanks.
>
> Regards,
> Ben Pitzer
>
> ---------------------------------------------
>
> "Those that can give up essential liberty to obtain a little temporary
> safety deserve neither liberty nor safety." --Ben Franklin--
>
>
>
>
> > -----Original Message-----
> > From: owner-bb@bb4.com [mailto:owner-bb@bb4.com]On Behalf Of Ben
> > Pitzer
> > Sent: Thursday, June 17, 2004 10:58 PM
> > To: bb@bb4.com
> > Subject: RE: {bb} More paging rules questions
> >
> >
> > Barbara,
> >
> > Thank you for pointing out my error. This was the end of a long day
> > trying to figure out the problem. In the email, I mixed up the hg-
> > and pg- prefixes. They are right in the bbwarn*.cfg files, but
> > incorrect in my email. So just swap the pg- and hg- prefixes in my
> > email. As I said, they
> > are correct in the files, so all is correct in my actual files in that
> > sense.
> >
> > Still looking for some suggestions, though. Thanks.
> >
> > Regards,
> > Ben Pitzer
> >
> > ---------------------------------------------
> >
> > "Those that can give up essential liberty to obtain a little temporary
>
> > safety deserve neither liberty nor safety." --Ben Franklin--
> >
> >
> >
> >
> > > -----Original Message-----
> > > From: owner-bb@bb4.com [mailto:owner-bb@bb4.com]On Behalf Of Hale,
> > > Barbara S - CNF
> > > Sent: Thursday, June 17, 2004 5:17 PM
> > > To: bb@bb4.com
> > > Subject: RE: {bb} More paging rules questions
> > >
> > >
> > >
> > > Ben --
> > >
> > > I don't know whether you have typos in your memo or whether your
> > > bbwarn*cfg really match what you have in your memo.
> > >
> > > You should check your prefixes... hg- and pg-. My understanding
> is
> > > that hg- stands for Host Group and should be lists of servers while
> pg-
> > > are Paging Groups and should be email addresses. Your examples
> look
> > > backwards... Plus your bbwarnrules.cfg only have pg- types, no hg-.
> > >
> > > Barbara
> > >
> > > ----
> > > Barbara Hale
> > > Unix Systems Administrator/CNF
> > > 2055 NW Savier Street
> > > Portland, OR 97209
> > >
> > >
> > >
> > > -----Original Message-----
> > > From: owner-bb@bb4.com [mailto:owner-bb@bb4.com] On Behalf Of Ben
> > > Pitzer
> > > Sent: Thursday, June 17, 2004 1:25 PM
> > > To: bb@bb4.com
> > > Subject: {bb} More paging rules questions
> > >
> > >
> > > Brothers and Sisters,
> > >
> > > Okay, I've got the following paging and host groups set up in
> > > bbwarnsetup.cfg:
> > >
> > > pg-devices: prefix*rtr* prefix*ubr* prefix*swt* prefix*tsv*
> > > prefix*ups*
> > > hg-devmgrs: pager-email@mydomain.com pager2-email@mydomain.com
> > >
> > > Now, here's what's in bbwarnrules.cfg. The plan is to have paging
> > > from 8am to 5pm, then hit the oncall pager from 5pm to 8am the next
> > > morning, and all day on weekends (I don't think that pg-devices2 and
>
> > > pg-devices3 are of interest here, except that they are the same as
> > > pg-devices, but with a different prefix, thus meaning a different
> > > set of hosts entirely, yet with the same problems):
> > >
> > > pg-devices;;test1 test2 test3 test4;;1-5;0800-1659;pg-devmgrs
> > > pg-devices pg-devices2 pg-devices3;;test1 test2 test3
> > > test4;;1-5;0000-0759 1700-2359;oncall-pager@mydomain.com
> > > pg-devices pg-devices2 pg-devices3;;test1 test2 test3 test4;;0
> > > 6;*;oncall-pager@mydomain.com
> > >
> > > *;pg-devices pg-devices2
> > > pg-devices3;*;;*;*;catchall-email@mydomain.com
> > >
> > > Now, that seems to work for most hosts in the pg-devices group.
> > > However a couple of the hosts in pg-devices group don't seem to work
>
> > > like that. I have bbgen installed, and I am using the info column,
> > > which tells me that all the hosts that should match prefix*rtr*
> > > (example is
> > > prefixabc-rtr1.mydomain.com) match like this (pardon the poor
> > > representation of the table that bbgen's info column puts out):
> > >
> > > Services Ex. Services Weekdays
> > > Time Recipients
> > > All All days
> > > 0000-2359 catchall-email@mydomain.com
> > > test1 test2 test3 test4 Mon-Fri
> > > 0800-1659 pager-email@mydomain.com
> > > pager2-email@mydomain.com
> > >
> > > Now, why would this be the case, if pg-devices is in the excluded
> > > list, and is included in the first three paging rules, why is it not
>
> > > being included in the after hours rules, and why is it being
> > > included in the catchall? I'm a bit baffled. I'm also baffled by
> > > the prefix*ups* devices, which have this in the info column:
> > >
> > > Services Ex. Services Weekdays
> > > Time Recipients
> > > All All days
> > > 0000-2359 catchall-email@mydomain.com
> > > test1 test2 test3 test4 Sun,Sat
> > > 0000-2359 oncall-pager@mydomain.com
> > > test1 test2 test3 test4 Mon-Fri
> > > 0000-0759 1700-2359
> > > oncall-pager@mydomain.com
> > > test1 test2 test3 test4 Mon-Fri
> > > 0800-1659 pager-email@mydomain.com
> > > pager2-email@mydomain.com
> > >
> > > So, this one catches all of the first three rules, but also hits on
> > > the catchall, from which it is supposed to be excluded. Can anyone
> > > shed some light here? Thanks.
> > >
> > > Regards,
> > > Ben Pitzer
> > >
> > > ---------------------------------------------
> > >
> > > "Those that can give up essential liberty to obtain a little
> > > temporary safety deserve neither liberty nor safety." --Ben
> > > Franklin--
> > >
> > >
> > >
> > > --
> > > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=
> > > -=
> > > To unsubscribe from this list, or to subscribe to the bb-digest list
> > > send e-mail to mailto:majordomo@bb4.com with unsubscribe bb -and/or-
> > > subscribe bb-digest in the BODY of the message.
> > >
> > > --
> > > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=
> > > -=
> > > To unsubscribe from this list, or to subscribe to the bb-digest list
> > > send e-mail to mailto:majordomo@bb4.com with unsubscribe bb -and/or-
> > > subscribe bb-digest in the BODY of the message.
> >
> > --
> > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
> > To unsubscribe from this list, or to subscribe to the bb-digest list
> > send e-mail to mailto:majordomo@bb4.com with unsubscribe bb -and/or-
> > subscribe bb-digest in the BODY of the message.
>
> --
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
> To unsubscribe from this list, or to subscribe to the bb-digest list
> send e-mail to mailto:majordomo@bb4.com with unsubscribe bb -and/or-
> subscribe bb-digest in the BODY of the message.
>
> --
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
> To unsubscribe from this list, or to subscribe to the bb-digest list
> send e-mail to mailto:majordomo@bb4.com with unsubscribe bb -and/or-
> subscribe bb-digest in the BODY of the message.
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
To unsubscribe from this list, or to subscribe to the bb-digest list
send e-mail to mailto:majordomo@bb4.com with unsubscribe bb -and/or-
subscribe bb-digest in the BODY of the message.
Home |
Main Index |
Thread Index