Thanks. I thought I had to set it under traps, but found what I needed to do
under security. It's started now.
Thanks!
From: [email protected]
[mailto:[email protected]] On Behalf Of Jonathan Barker
Sent: Wednesday, March 23, 2011 3:00 PM
To: A list for BES Admin's to discuss issues, etc.
Subject: Re: [Bes-admins] Trying to figure out BES Monitoring Service
I'm guessing it's a security issue. You may need to go into the SNMP service on
BES and set your BES monitor server as a trap receiver or as an allowed IP.
From: [email protected]
[mailto:[email protected]] On Behalf Of Peterson David
Sent: Wednesday, March 23, 2011 11:55 AM
To: A list for BES Admin's to discuss issues, etc.
Subject: [Bes-admins] Trying to figure out BES Monitoring Service
I need to get the BES Monitoring Service installed on a server to connect to
our 5.0.2 MR3 Exchange BES.
Not sure what I've been doing wrong (even though I updated it immediately to
MR3 I had to do the date change to Sep 1 and run the keygen just to login.)
Now, I'm getting SNMP errors. My knowledge of SNMP is pretty limited, but the
BES does have the service started.
This is in the logs (server names and IP's redacted):
(03/23 14:19:30:240):{PeerRecvQueue:1} [machine_tester:completeCheck:133]
[INFO] Run completeCheck against FQDN BES Name:161 (platform X). Host IP:
Internal IP Address
(03/23 14:19:30:460):{PeerRecvQueue:1} [machine_tester:completeCheck:160]
[INFO] START -- host= FQDN BES Name port=161 snmpread=public socketTimeout=5
platform=X, snmpTimeout=5
(03/23 14:19:36:460):{PeerRecvQueue:1} [machine_tester:_checkOID:84] [INFO]
Error indication 'requestTimedOut' for oid (1, 3, 6, 1, 2, 1, 1, 1, 0)
(03/23 14:19:36:460):{PeerRecvQueue:1} [machine_tester:completeCheck:201]
[INFO] END -- host= FQDN BES Name, result={'errstr':
'ERR_SNMP_NO_RESPONSE_STR', 'errcode': 101, 'ts': 1300904376.461}
NOTICE: This electronic mail transmission from the law firm of Dinsmore & Shohl
may constitute an attorney-client communication that is privileged at law. It
is not intended for transmission to, or receipt by, any unauthorized persons.
If you have received this electronic mail transmission in error, please delete
it from your system without copying it, and notify the sender by reply e-mail,
so that our address record can be corrected._______________________________________________
Bes-Admins mailing list
[email protected]
http://www.dataoutages.com/mailman/listinfo/bes-admins
http://www.dataoutages.com
http://www.dataoutagenews.com
RSS Feed: http://feeds.feedburner.com/Bes-admins
---------------------------------
Bes-Admins mailing list is sponsored by Dataoutagenews.com.
http://www.dataoutagenews.com
