I wanted to thank everyone on the list, particularly Clarence for the pager
help. I spent the last week creating a simple ruleset and writing some code
and now have Netview paging us whenever a router goes down and when it goes
back up. It only pages us the first time Netview see's it's down and my
script checks to see if it's pingable before paging us. Once the router is
back up, the script checks what routers we have been paged against and then
removes it and pages us to let us know it's up.
Thanks
--
Dean S.
Arizona Department of Transportation
Information Technology Group
Network Architecture Team
-----Original Message-----
From: Hart Clarence (rti1clh) [mailto:CHart@ups.com]
Sent: Wednesday, September 17, 2003 12:05 PM
To: 'DSullinger@dot.state.az.us'
Cc: 'nv-l@lists.tivoli.com'
Subject: RE: [nv-l] nvpagerd - PAGE_Q full error
D,
I create my own scripts that analyze the data from the traps... I attached
a sample ruleset that only responds to Symbol Access Points Traps (these
were loaded in manually via the mib loader). I then add the Ruleset to the
active Control Panel and leave it open. This activates the ruleset... If its
not running it the control panel it wont page you. If you want it to run
without the control panel you need to remove the "ForwardCorr" and add the
ruleset file name to the /usr/OV/conf/ESE.automation file. I use the
Control Panel so I can see the traps logging to the screen but it can bite
you in the butt if the control panel crashes and the Wireless Access Points
dies. No pages will be sent... :( It's up to you how you want to set
that part up....
Anyway, what happens is if control panel see a Wireless AP trap and it
matches one in the file it passes it along to my home made script. In the
script you can do what ever you want... Check for time, date, and cross
reference a severity level file then use the nvpage program to page your
manager to fix the problem. Or just send email. Or if you cant get the
modem to work you could send an email-to-pager message... Basically if your
good at writing shell scripts you can do whatever you want.
This is no doubt the hardest way to do paging in NetView but it works for
me because I'm a UNIX admin 1st, and a Cisco Admin 2nd... Plus I had
problems along time ago trying to get the rulesets to work in ver 5.x .
Later
C
-----Original Message-----
From: DSullinger@dot.state.az.us [mailto:DSullinger@dot.state.az.us]
Sent: Wednesday, September 17, 2003 1:39 PM
To: CHart@ups.com
Subject: RE: [nv-l] nvpagerd - PAGE_Q full error
Wow, thanks for the quick reply.
We are running Netview v7.1 on Solaris 8
I've been able to get the modem to work, my issue has always been getting
the ruleset to work. What are you doing about a ruleset that makes the
page?
-----Original Message-----
From: Hart Clarence (rti1clh) [mailto:CHart@ups.com]
Sent: Wednesday, September 17, 2003 10:02 AM
To: 'DSullinger@dot.state.az.us'
Subject: RE: [nv-l] nvpagerd - PAGE_Q full error
What version are you using? Also what platform are you using?
The hardest part is getting the modem to be recognized by Solaris... To
test use the : nvpage and nvpager commands.
On solaris you can do the following :
----------------------------------------------------------------------------
--------------------
1st configure your serial ports (if you havnt already done so): # admintool
settings - PortA [ Service Enabled, baud 9600, Initialize Only, the rest
are defaults]
----------------------------------------------------------------------------
--------------------
Then setup the /usr/OV/conf/nv.carriers file
"this is what I use... You will have to check your pager companies for phone
#'s"
Carrier: archwireless
Modem phone #: 1-800-250-6325
Numeric IDs accepted on modem line: N
DTMF phone #:
Max. message length: 230
Max. digits in alphanumeric pager #: 10
Max. blocks/transaction: 1
Max. transactions/call: 30
Baud rate: 9600
Parity: N
Data bits: 8
Stop bits: 1
Password:
Protocol: TAP
Carrier: skytel
Modem phone #: 1-800-759-6366
Numeric IDs accepted on modem line: N
DTMF phone #: 1-800-759-6366
Max. message length: 190
Max. digits in alphanumeric pager #: 18
Max. blocks/transaction: 1
Max. transactions/call: 7
Baud rate: 9600
Parity: E
Data bits: 7
Stop bits: 1
Password:
Protocol: TAP
----------------------------------------------------------------------------
--------------------
Then I setup the /usr/OV/conf/nvpager.config file
" again use your own modem settings"
#
# GSC Paging configuration file
#
# Outside Line # (p=Pause): 9p
# This is any dialing that needs to be done for the attached modem to
# get an outside dial tone. Numeric pager numbers as well as carrier
# phone number should NOT include this. This will be dialed each time
# a call is made by the modem.
# Valid characters: 0123456789p
Outside Line # (p=Pause): 9p
# Default Modem File: newhayes.modem
# This is the modem information file that describes the initialization
# needed for the attached modem and other control information specific
# to each type of modem.
Default Modem File: newhayes.modem
# Default Baud Rate (300,1200,2400,4800,9600,19200,38400): 300
# This is the baud rate between the computer and modem when direct-dial
# numeric pagers are contacted and when the carrier's direct-dial DTMF
# number is used for numeric pagers.
# Valid values: 300,1200,2400,4800,9600,19200,38400
Default Baud Rate (300,1200,2400,4800,9600,19200,38400): 19200
# Default Data Bits (7,8): 7
# This is the number of data bits between the computer and modem when
# direct-dial numeric pagers are contacted and when the carrier's direct-
# dial DTMF number is used for numeric pagers.
# Valid values: 7,8
Default Data Bits (7,8): 7
# Default Parity (N,E,O): E
# This is the parity between the computer and modem when direct-dial
numeric
# pagers are contacted and when the carrier's direct-dial DTMF number is
# used for numeric pagers.
# Valid values: N,E,O
Default Parity (N,E,O): E
# Default Stop Bits (1,2): 1
# This is the number of stop bits between the computer and modem when
# direct-dial numeric pagers are contacted and when the carrier's direct-
# dial DTMF number is used for numeric pagers.
# Valid values: 1,2
Default Stop Bits (1,2): 1
# Default Device: tty1
# This is the device that the modem is attached to. It must be in the
/dev
# directory. If your modem is attached to another tty port, this must be
# changed.
Default Device: ttya
----------------------------------------------------------------------------
--------------------
You need to turn on NetView Security and configure users and pager ids. You
can set each user to do alpha or numeric paging. This is done by the GUI
interface but each user file is found under: /usr/OV/security/C/Users
Example file
# dodobrown: Profile updated on Wed Jul 23 12:32:33 2003
LOGIN_ID = dodobrown
GROUP_LIST = SrAdmin, Oper, web
CLIENT_LIST = *
MANAGER_LIST = *
TIME_SET = 1058977953
PASSKEY =µsdfsÕøfdsf Ù-wfd
PASSKEY_TIME_CHANGED = 947606673
LOGIN_START_TIME = 00:00
LOGIN_END_TIME = 24:00
LOGIN_DAYS_OF_WEEK = SUN,MON,TUE,WED,THU,FRI,SAT
PAGER_NUMERIC_NUMBER = NONE PAGER_ALPHANUM_NUMBER = 4102830482
PAGER_CARRIER_NAME = archwireless
NOTES =Clarence Hart
----------------------------------------------------------------------------
------------
-----Original Message-----
From: DSullinger@dot.state.az.us [mailto:DSullinger@dot.state.az.us]
Sent: Wednesday, September 17, 2003 12:45 PM
To: chart@ups.com
Subject: RE: [nv-l] nvpagerd - PAGE_Q full error
Clarence,
I'm sorry to bother you, but I saw your post within the Netview list and I
was wondering how you have your Netview to setup to page you. We have been
trying to setup Netview so it would page us once a Router was down, but we
have not been successful to this point.
--
Dean Sullinger
Arizona Department of Transportation
Information Technology Group
Network Architecture Team
Phone: (602)712-8673
Email : dsullinger@dot.state.az.us
SMail : 206 S. 17th Ave MS#110G Phx Az 85007-3212
Internet: http://www.dot.state.az.us/
Intranet: http://wan.dot.state.az.us/
-----Original Message-----
From: Clarence Hart [mailto:rti1clh@ismd.ups.com]
Sent: Wednesday, September 17, 2003 7:37 AM
To: nv-l@lists.tivoli.com
Subject: [nv-l] nvpagerd - PAGE_Q full error
All,
Whenever we have an outage and some of our devices are unreachable
NetView is configured to page us. This works fine for a few devices at a
time. But sometimes we can have a several devices drop off the network
and this causes a huge surge of alerts to be pushed into nvpagerd's
queue. When this happens we se the following error and the nvpagerd
daemon freezes and we have to reboot the entire machine.
Has anybody ran into this error message? Suppose alot of devices go down
and you need this pages. Why is there a non-expandable queue?
09/15/03 19:21:18 Error: PAGE_Q full
09/15/03 19:21:19 PAGE_Q is not expandable on this platform 09/15/03
19:21:19 Error: PAGE_Q full 09/15/03 19:21:19 PAGE_Q is not expandable on
this platform 09/15/03 19:21:19 Error: PAGE_Q full
Thanks!!!
Clarence Hart
UPS
Office: 410-560-4182
Fax: 410-560-4329
chart@ups.com
---------------------------------------------------------------------
To unsubscribe, e-mail: nv-l-unsubscribe@lists.tivoli.com
For additional commands, e-mail: nv-l-help@lists.tivoli.com
*NOTE*
This is not an Offical Tivoli Support forum. If you need immediate
assistance from Tivoli please call the IBM Tivoli Software Group help line
at 1-800-TIVOLI8(848-6548)
|