SNMP Monitoring for Sunone 5.2

Hi,
I want to monitor my LDAP boxes using SMARTs and IV. for this I need to setup SNMP on LDAP boxes. can someone give me hints to do this and provide mibs ?
Regards,
-Manish

http://docs.sun.com/source/817-7607/monitor.html#wp19755
http://docs.sun.com/source/817-7616/config.html#wp26382
Do these help?

Similar Messages

Nagios SNMP Monitoring for NSS devices ?

Has anyone managed to utilise the inbuilt SNMP functions of the NSS with nagios efficiently ?
if so, what plugins are you using and how have you got them configured ?
Steve

There are some threads in this forum regarding this already. It is not as easy as monitoring a switch or router. the controllers combine the AP mac with the oid for unique lines. You can glean some snmp info off the controllers by using some of the generic OIDs and controller specific OIDs, but you will need an snmp monitoring program that you can load the WLC MIBs into and then tailor your monitoring of the controller based on that. I use Cacti, which is really awesome, but I would need to grab the complete OID off each controller based on the APs on it, which is fine as long as the AP is on that particular controller and not another one. snmpwalk is your friend in this case.
OID+mac = results

Snmp monitoring for wlc 4404

Hi,
we use a snmp monitoring software called Nagios in our LAN. Now we have two WLC 4404. Is it possible to monitor values via snmp? Is someone else doing it so?
Witch values can be monitored and for what values is it wise or practicable to monitor it?
Regards
Christian

There are some threads in this forum regarding this already. It is not as easy as monitoring a switch or router. the controllers combine the AP mac with the oid for unique lines. You can glean some snmp info off the controllers by using some of the generic OIDs and controller specific OIDs, but you will need an snmp monitoring program that you can load the WLC MIBs into and then tailor your monitoring of the controller based on that. I use Cacti, which is really awesome, but I would need to grab the complete OID off each controller based on the APs on it, which is fine as long as the AP is on that particular controller and not another one. snmpwalk is your friend in this case.
OID+mac = results

SNMP monitoring for EoMPLS virtual circuit

I am looking to implement SNMP-based monitoring of an MPLS layer-2 tunnel. The desired result would be the same as the output from the following command:
"sh mpls l2transport vc"
I have configured the router to generate SNMP traps based on LDP changes, but this is not specific to the status of the EoMPLS tunnel.
Thanks in advance.

Polling to these MIB values would have your task accomplished.
1) VC status <--> cpwVcOperStatus
2) If you need outbound staus <--> pwVcInboundOperStatus
3) Inbound status <--> cpwVcOutboundOperStatus
And here is the link for list of MIB objects for L2VPN.
http://www.cisco.com/en/US/products/ps6441/products_configuration_guide_chapter09186a00808194e1.html
HTH-Cheers,
Swaroop

Recommended product for syslogging and snmp monitoring

Hi,
    We currently use KIWI syslog but can anyone recommend a better product for syslogs from Firewalls, Routers and Switches. Our current product creates a seperate text file per day per device. Ideally I would like all these to be combined (or combinable for display purposes) into one log that shows to update realtime and have the ability to filterout "background noise" - stuff we know is acceptable, as well as being able to run simple or quick searches and reports. Ideally for asbout 200+ devices.
     Am I too hopeful or is there a product out there that can do this (that also will not break my companies bank account).
     Also, recommended products for SNMP monitoring if better than we currently use would be useful - currently using Orion and SNMPc.
Regards
Adrian

Adrian,
We use syslog-ng for RHEL. It can do what you need as far as writing to files and filtering out background noise, but it is not a search/reporting tool. If KIWI does the latter, I imagine you could tell it to read from the file that syslog-ng creates.
It is open source for writing files through version 3.1.4. Later versions require licensing to write to files or if you are using a Windows OS.
http://www.balabit.com/downloads/files/syslog-ng/open-source-edition/3.1.4
Here are some other options:
Rsyslog: http://www.rsyslog.com/
Splunk: http://www.splunk.com/
Snare: http://www.intersectalliance.com/projects/index.html
Hope this helps.
Steve Lee
Emory University

How to configure SNMP agent for Oracle 10g

Hello,
I've installed oracle 10g in a Windows 2000 SP4 and I want to monitor database using SNMP.
I've already installed Windows SNMP agent but I haven't any idea how to configure Oracle in order to grant SNMP monitoring.
What should I do?
Is Oracle database ready to be monitored via SNMP by default?
Thanks in advance for your help.
Regards,
Carles

Hello,
Thanks for your message.
In fact, I already found this doc in oracle, but it just show executables I have to install and my question can I install these executables.
I've already installed Windows SNMP agent, configured and testedwith disk space checkings, but it doesn't work fine with Oracle.
I launched Oracle Universal Installer and I checked Installed Products, but I haven't found how to install SNMP agents for oracle.
How can I add Oracle Peer Master Agent and Encapsulator to my oracle installation?
Thanks again for your help.
Regards,
Carles

Oracle VM 3.0 and HP Hardware SNMP monitoring

Has anyone successfully installed a SNMP tool to monitor Hard disk status in an HP Proliant server that has OVM 3.x server running on it? Insight Manager seems to require too many RPMs that we can not install and we are playing with ZenOss but it too does not seem to detect the hard disks. Though at the moment, I have CPU, Power Supplies and memory being monitored. Just not the internal RAID set that receives the OVM Server software.
This must be possible.

Avi Miller wrote:
If you have Oracle VM Support, you can download the net-snmp RPMs for Oracle VM 3.0 from My Oracle Support.Yes i have done that and installed them as well as all of the other rpms needed. Once that was done and configured Zenoss shows me
Network Routes
Memory Modules
Power Supplies
Interfaces
Fans
Temperature Sensors
FileSystems
IP Services
Processors
but not
Expansion Cards
Hard Disks
Logical Disks
I have these other 3 on other servers, so it must be an agent needs to be started or configured that isn't there. In this case Zenoss might not be the correct solution but I am wondering what others have done to solve this type of issue. We need hard disk monitoring as its vital to knowing if one disk goes bad in the RAID01 array so we can change it out before the other one fails.
Not comfortable of going to production without this monitoring.
Edited by: user897654321 on Feb 23, 2012 2:01 PM

Basic Network Monitoring for Cisco Operation Manager 2012

Hello,
Please bear with me as i'm new the Operations Manager 2012 world. I've just installed operations manager 2012 in our environment and i've setup a network management point. I've discovered my networking gear which is primarily cisco equipment. The devices
are appearing as CERTIFIED. It appears that they are HEALTHY however in most cases i'm getting some arbitrary monitors. I have a 6509 switch where memory and processor appear to be being monitored out of the box. I'm receiving alerts and everything.
My question is how do I turn on monitoring for other discovered components. I seem to understand I can make SNMP monitors under the authoring pane if i know the OID. That sounds like it'd be tedious work for such a simple and basic monitor. However I was
under the impression I would be able to monitor a lot of these components with a simple click of a button. Is this not the case? I'm primarily interested in monitoring the state and performance of particular interfaces as well as the state of the power supplies
in our switches. Is there a guide that explains the basic principles of this. What are my options?
Thanks!
-Brandon

Hi,
You will need to edit the discovery and broaden the range. You may use recursive discovery.
Recursive discovery will try to discover any other network devices it knows about through its Address Routing Protocol (ARP) table, its IP address table, or the topology Management Information Block (MIB) to grow the network map and present all applicable
devices to you for monitoring.
You can also filter out devices that you don't want to be discovered by using properties such as the device type, name, and object identifier (OID). This is a handy option if you wanted to quickly discover all the network devices in your network except,
a small number or some with a specific criteria.
In really large networks with a lot of network devices, keep in mind that there is a default limit of 1500 network devices that can be discovered recursively. You can of course tweak this limit to suit your environment if you wish, but for most people, this
won't be needed.
More details, please go through the article below:
http://kevingreeneitblog.blogspot.com/2012/07/scom-2012-network-monitoring-explicit.html
Regards,
Yan Li
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

SNMP monitoring of Oracle 10g?

Hi there,
I'm curious about using SNMP technology to monitor Oracle 10g databases.
I've done some light reading on the subject and I'm now at the stage
where I have a few questions.
-What exactly do I need to configure in my Oracle 10g environment?
-Is Enterprise Manager the best and/or only UI available for me
to carry out configuration chores?
-I see no SNMP specific documentation for 10g; why is that?
-I do see a good document for 9i:
Oracle SNMP Support Reference Guide Release 9.2.0 Part Number A96672-01
http://download-west.oracle.com/docs/cd/B10501_01/em.920/a96672/toc.htm
Is the above document suitable for configuring SNMP monitoring of Oracle
in a 10g environment?
-moi

I'm able to set up traps via the EM website following these instructions:
http://download-west.oracle.com/docs/cd/B19306_01/em.102/b40002/notification.htm
However, what I'm really looking for is the ability to do snmp gets. I need functionality similar to how the old school DBSNMP under OMS used to work. These commands seem to be totally missing. I found the following documentation:
http://download-east.oracle.com/docs/cd/B19306_01/em.102/b16244/chap2.htm#sthref74
Which indicates there should be an snmp subfolder under $ORACLE_HOME/sysman, but that folder does not exist in my installation. I installed Oracle EE. Is there another package I need to install in order to make the subagent run like a normal snmp agent?
So far if I do a:
emctl start dbconsole
that starts up the EM Website and I can use that no probelm. If I...
emctl start agent -- I get:
Starting agent ... started.
issuing a 'emctl staus agent' gives me a normal status message. Things start to get strange when I try to start the subagent, which to my understanding is what I need running in order to to talk to net-snmp, which is the master agent running on this host. Here's what happens:
[zaro@cheetah bin]$ ./emctl start subagent
Oracle Enterprise Manager 10g Database Control Release 10.2.0.1.0
Copyright (c) 1996, 2005 Oracle Corporation. All rights reserved.
Starting sub agent .....started
[zaro@cheetah bin]$ ./emctl status subagent
Oracle Enterprise Manager 10g Database Control Release 10.2.0.1.0
Copyright (c) 1996, 2005 Oracle Corporation. All rights reserved.
Sub agent is not running..
I guess my question is how do I get to have the ability I used to have back in 8i to start up dbsnmp and then have my SNMP monitoring app "discover" the agent and use its instrumentation to get data?

SNMP Query for Byspass Status (AIP5)

I'd like to monitor the state of Bypass mode for the ASA-SSC-AIP-5 and would like to know if I can check this with SNMP and if so, which OID.
I started messing with SNMP and the SSC5 a while back and started a thread about snmpwalk causing it to crash. After that, I never really picked the project back up.
I've been known to miss the obvious every now and then, but I was dissapointed to see that there wasn't an (obvious) way for the device to alert you when it automatically goes into bypass mode. This should be a feature request.

IPS provides SNMP traps for different interface conditions like link going down or up, traffic bypass started, etc. Below is one such example
Received SNMPv2c Trap: Community: "public"
From: 10.89.149.204 mib_2.1.3.0 = 38429472
snmpModules.1.1.4.1.0 = ciscoMgmt.138.2.0.1
ciscoMgmt.138.1.3.3.1.3 = 3                      <====    index can be mapped to index obtained from snmpwalk
ciscoMgmt.138.1.3.3.1.4 = 5                      <====    Traffic bypass started
ciscoMgmt.138.1.3.3.1.5 = 4
ciscoMgmt.138.1.3.3.1.6 = 38429472
All you need to do is enable sending traps from the sensor.
qssp-8085(config)# service notification
qssp-8085(config-not)# enable-set-get true
qssp-8085(config-not)# enable-notification true
qssp-8085(config-not)# read-only-community public
qssp-8085(config-not)# read-write-community private
qssp-8085(config-not)# trap-destinations x.x.x.x           <===== trap destination
qssp-8085(config-not-tra)# exit
qssp-8085(config-not)# exit
You can configure separate community name under trap-destination. If not provided then the read-write-community will be used to send with the trap.
Hope this helps
Madhu

Snmp configuration for SG300

Hi,
Am trying to configure SNMP functionality for the first time on an SG300-28 switch so I can use mrtg to monitor it. I've defined no users, 2 groups (mrtg and mrtg2 for SNMPv1 and SNMPv2 respectively), both with No authentication required. Default View of Read. I also defined a Basic Community type and called it sg300, with the View Name of Default. Under Views I changed nothing; the Default has 1 Object ID subtree included.
The mrtg CFGMaker in cannot retrieve any information from the switch. I've used it before with routers, Windows servers, etc. with no problem so I have to be overlooking something specific to this switch.
Much appreciated.
--Ben

Agreed Jonathan was correct, that was the part I missed the first time through. I walked through again to make sure there wasn't anything else and have attached the notes I took, mostly so I'll have them next time I have to do it :)
Steps to configure SNMP for MRTG on SG200-26
***Note*** These are minimum steps only for a lab environment additional security settings may be required for production use.
Switch is starting at factory reset configuration state
Login to the switch
Default ip 192.168.1.254
Username: cisco
Password: cisco
Change Password
Expand SNMP Section on bottom of left navigation
Highlight communities on the expanded SNMP section
Click the Add button
Enter the IP address of the system that will be making SNMP requests to your switch
Community string: mrtg (or whatever you want to use)
Ensure Read Only is selected for your access mode
Click Apply
Click Close
Expand the Security Section on the left navigation bar
Highlight TCP/UDP Services
Click the Checkbox to enable SNMP Service at the top of the screen
Click Apply
In the top right hand corner you should see a flashing save button, make sure to save your config if your happy with it.
“Snmpwalk –c mrtg 192.168.1.254” Should now run and return
***Note*** If your looking for port numbers in the output they start with .49 for port 1 and go to .74 for port 26.
IF-MIB::ifHCOutOctets.49 = Counter64: 0
IF-MIB::ifHCOutOctets.50 = Counter64: 0
IF-MIB::ifHCOutOctets.51 = Counter64: 0
IF-MIB::ifHCOutOctets.52 = Counter64: 0
IF-MIB::ifHCOutOctets.53 = Counter64: 0
IF-MIB::ifHCOutOctets.54 = Counter64: 0
IF-MIB::ifHCOutOctets.55 = Counter64: 0
IF-MIB::ifHCOutOctets.56 = Counter64: 0
IF-MIB::ifHCOutOctets.57 = Counter64: 0
IF-MIB::ifHCOutOctets.58 = Counter64: 0
IF-MIB::ifHCOutOctets.59 = Counter64: 2849723
IF-MIB::ifHCOutOctets.60 = Counter64: 0
IF-MIB::ifHCOutOctets.61 = Counter64: 0
IF-MIB::ifHCOutOctets.62 = Counter64: 0
IF-MIB::ifHCOutOctets.63 = Counter64: 0
IF-MIB::ifHCOutOctets.64 = Counter64: 0
IF-MIB::ifHCOutOctets.65 = Counter64: 0
IF-MIB::ifHCOutOctets.66 = Counter64: 0
IF-MIB::ifHCOutOctets.67 = Counter64: 0
IF-MIB::ifHCOutOctets.68 = Counter64: 0
IF-MIB::ifHCOutOctets.69 = Counter64: 0
IF-MIB::ifHCOutOctets.70 = Counter64: 0
IF-MIB::ifHCOutOctets.71 = Counter64: 0
IF-MIB::ifHCOutOctets.72 = Counter64: 0
IF-MIB::ifHCOutOctets.73 = Counter64: 0
IF-MIB::ifHCOutOctets.74 = Counter64: 0

Snmp alerts for CPU utilization

Hi,
I want to enable snmp alerts on l2 and l3 switches to monitor CPU utilization.
I have Opmanager which is acting as SNMP server.
I have switches L2 and L3 which are running IOS 12.0, 12.1, 12.2
Do all these IOS versions support SNMP alerts?
And also I want to know the commands to be configured on switches for this.
Regards
skrao

You can configure SNMP traps for CPU Thresholding Notification.
http://www.cisco.com/en/US/products/ps6350/products_configuration_guide_chapter09186a0080455772.html
You should be ok with the versions you list but check exact IOS version supports it at http://www.cisco.com/go/fn
If you do not want to use traps then there are specific oids that can be polled for 1minute average (1.3.6.1.4.1.9.2.1.57) and also 5 minute average (1.3.6.1.4.1.9.2.1.58). I've used these in the past with no problems. These oids may have been superceeded so check for latest. You can always snmpwalk a device to check oids.
The cisco SNMP navigator is helpful when it comes to oids.
http://tools.cisco.com/Support/SNMP/do/BrowseOID.do?local=en
If you haven't got any SNMP configured yet on the switch check out http://forum.cisco.com/eforum/servlet/NetProf?page=netprof&forum=Network%20Infrastructure&topic=Network%20Management&CommCmd=MB%3Fcmd%3Ddisplay_location%26location%3D.1ddb4e54
HTH
--Phil

Is there anyway to monitor network traffic on the newer Time Capsules, similar to the SNMP monitoring previously?

Is there anyway to monitor network traffic on the newer Time Capsules, similar to the SNMP monitoring previously?

Can I use a real router and still have the Time Capsule for backups etc?
Yes, that is what Bridge Mode is for. Just connect the Time Capsule to a LAN <--> Ethernet port on your "main" router.

Guidelines for Health Monitoring for TimesTen

This document provides some guidance on monitoring the health of a TimesTen
datastore. Information is provided on monitoring the health of the
datastore itself, and on monitoring the health of replication.
There are two basic mechanisms for monitoring TimesTen:
1. Reactive - monitor for alerts either via SNMP traps (preferred) or
by scanning the Timesten daemon log (very difficult) and reacting
to problms as they occur.
2. Proactive - probe TimesTen periodically and react if problems, or
potential problems, are detected.
This document focusses on the second (proactive) approach.
First, some basic recommendations and guidelines relating to monitoring
TimesTen:
1. Monitoring should be implemented as a separate process which maintains
a persistent connection to TimesTen. Monitoring schemes (typically based
on scripts) that open a connection each time they check TimesTen impose
an unnecessary and undesireable loading on the system and are discouraged.
2. Many aspects of monitoring are 'stateful'. They require periodic
sampling of some metric maintained by TimesTen and comparing its
value with the previous sample. This is another reason why a separate
process with a persistent connection is desireable.
3. A good monitoring implementation will be configurable since the values
used for some of the chcks may depend on e.g. the TimesTen configuration
in use or the workload being handled.
MONITORING THE HEALTH OF A DATASTORE
====================================
At the simples level, this can be achieved by performing a simple SELECT
against one of the system tables. The recommended table to use is the
SYS.MONITOR table. If this SELECT returns within a short time then the
datastore can be considered basically healthy.
If the SELECT does not return within a short time then the datastroe is
stuck in a low level hang situation (incredibly unlikely and very serious).
More likely, the SELECT may return an error such as 994 or 846 indicating
that the datastore has crashed (again very unlikely, but possible).
A slightly more sophisticated version would also include an update to a
row in a dummy table. This would ensure that the datastore is also capable
of performing updates. This is important since if the filesystem holding
the trsnaction logs becomes full the datastore may start to refuse write
operations while still allowing reads.
Now, the SYS.MONITOR table contains many useful operational metrics. A more
sphisticated monitoring scheme could sample some of these metrics and
compute the delta between subsequent samples, raising an alert if the
delta exceeds some (configurable) threshold.
Some examples of metrics that could be handled in this way are:
PERM_IN_USE_SIZE and PERM_IN_USE_HIGH_WATER compared to PERM_ALLOCATED_SIZE
(to detect if datastore is in danger of becoming full).
TEMP_IN_USE_SIZE and TEMP_IN_USE_HIGH_WATER compared to TEMP_ALLOCATED_SIZE
(ditto for temp area).
XACT_ROLLBACKS - excessive rollbacks are a sign of excessive database
contention or application logic problems.
DEADLOCKS - as for XACT_ROLLBACKS.
LOCK_TIMEOUTS - excessive lock timeouts usually indicate high levels of
contention and/or application logic problems.
CMD_PREPARES & CMD_REPREPARES - it is very important for performance that
applications use parameterised SQL statements that they prepare just once
and then execute many times. If these metrics are continuously increasing
then this points to bad application programming which will be hurting
performance.
CMD_TEMP_INDEXES - if this value is increasing then the optimiser is
comntinually creating temporary indices to process certain queries. This
is usually a serious performance problem and indicates a missing index.
LOG_BUFFER_WAITS - of this value is increasing over timne this indicates
inadequate logging capacity. Yiou may need to increase the size of the
datastore log buffer (LogBuffSize) and log file size (LogFileSize). If that
does not alleviate the problem you may need to change your disk layout or
even obtain a higher performance storage subsystem.
LOG_FS_READS - this indicates an inefficieny in 'log snoop' processing as
performed by replication and the XLA/JMS API. To alleviate this you should
try increasing LogBuffSize and LogFileSize.
Checking these metrics is of course optional and not necessary for a basic
healthy/failed decision but if you do check them then you will detect more
subtle problems in advance and be able to take remedial action.
MONITORING THE HEALTH OF REPLICATION
====================================
This is a little more complex but is vital to achieve a robust and reliable
system. ideally, monitorting should be implemented at both datstores, the
active and the standby. There are many more failure modes possible for
a replicated system than for a standalone datastore and it is not possible
to ennumerate them all here. However the information provided here should
be sufficient to form the basis of a robist monitoring scheme.
Monitoring replication at the ACTIVE datastore
1.     CALL ttDataStoreStatus() and check result set;
If no connections with type 'replication' exists, conclude that
replication agents are stopped, restart the agents and skip
next steps.
It is assumed here that the replication start policy is 'norestart'.
An alarm about unstable replication agents should be raised
if this is Nth restart in M seconds (N and M are configuration parameters).
The alarm can later be cleared when the agents stayed alive K
seconds (K is configuration parameter).
2.     CALL ttReplicationStatus() and check result set;
This returns a row for every replication peer for this datastore.
If the pState is not 'start' for any peer, raise an alarm about paused or
stopped replication and skip rest of the steps.
It is assumed that master cannot help the fact that state is not
'start'. An operator may have stopped/paused the replication or
TimesTen stopped the replication because of fail threshold
strategy. In former case the operator hopefully starts the replication
sooner or later (of course, after that TimesTen may stop it again
because of the fail threshold strategy). In latter case the standby
side monitor process should recognise the fact and duplicate the data
store with setMasterRepStart-option which sets state back to 'start'.
If for any peer, lastMsg > MAX (MAX is a configuration parameter), raise
an alarm for potential communication problems.
Note that if replication is idle (nothing to replicate), or there is
very little replication traffic, the value for lastMsg may become as
high as 60 seconds without indicating any problem. The test logic
should cater for this (i.e. MAX must be > 60 seconds).
3.     CALL ttBookmark();
Compute the holdLSN delta between the values from this call and the
previous call and if the delta is greater than maximum allowed
(configuration parameter), raise an alarm about standby
that is too far behind. Continue to next step.
Notice that maximum delta should be less than FAILTHRESHOLD * logSize.
4.     CALL ttRepSyncSubscriberStatus(datastore, host);
This step is only needed if you are using RETURN RECEIPT or RETURN TWOSAFE
with the optional DISABLE RETURN feature.
If disabled is 1, raise an alarm for disabled return service.
Continue to next step. If RESUME RETURN policy is not enabled we could,
of course, try to enable return service again (especially when DURABLE
COMMIT is OFF).
There should be no reason to reject TimesTen own mechanisms that
control return service. Thus, no other actions for disabled return
service.
Monitoring replication at the STANDBY datastore
1.     CALL ttDataStoreStatus();
If no connections with type 'replication' exists, conclude that
replication agents are stopped, restart the agents and skip
next steps.
It is assumed that replication start policy is 'norestart'.
An alarm about unstable replication agents should be raised
if this is Nth restart in M seconds (N and M are configuration parameters).
The alarm can later be cleared when the agents stayed alive K
seconds (K is configuration parameter).
2.     Call SQLGetInfo(...,TT_REPLICATION_INVALID,...);
If the status is 1, this indicates that the active store has marked this store
as failed due to it being too far out of sync due to log FAILTHRESHOLD.
Start recovery actions by destroying the datastore and recreating via a
'duplicate' operation from the active.
3.     Check 'timerecv' value for relevant row in TTREP.REPPEERS
If (timerecv - previous timerecv) > MAX (MAX is a configuration parameter),
raise an alarm for potential communication problems.
You can determine the correct row in TTREP.REPPEERS by first getting the
correct TT_STORE_ID value from TTREP.TTSTORES based on the values in
HOST_NAME and TT_STORE_NAME (you want the id corresponding to the active
store) and then using that to query TTREP.REPPEERS (you can use a join if
you like).
The recovery actions that should be taken in the event of a problem with
replication depend on several factors:
1. The application requirements
2. The type of replication configuration
3. The replication mode (asynchronous, return receipt or return twosafe)
that is in use
Consult the Timesten replication guide for information on detailed recovery
procedures for each combination.
================================ END ==================================

The information in the forum article is the abridged text of a whitepaper I wrote recommending best practice for building a monitoring infrastructure for TimesTen. i.e. you write an 'application' in C, C++ or Java that performs these monitoring activities and run it continually in production against your datastores. Various aspects of the behaviour of the application could be controlled by configurable parameters; these are not TimesTen parameters but parameters defined and used by the monitoring application.
In the specific case you mentioned, the 'lastMsg' value returned by ttReplicationStatus is the number of seconds since the last message was received from that peer. The monitoring application would compare this against some meaningful threshold (maybe 30 seconds) and if lastMsg is > that value, raise an alarm. To allow flexibility, the value compared against )MAX) should be configurable.
Does that make sense?
Chris

SNMP Monitor PIX throught VPN tunnel

I have two Cisco PIX 515e firewalls configured in fail-over. The primary PIX has private address 192.168.1.5 and the secondary PIX (standby) has a private address 192.168.1.6. The PIX firewalls are running IOS 6.3.3. I'm connecting to the PIX firewalls through a VPN tunnel (PIXes terminate VPN tunnel) and my monitoring system uses SNMP to monitor devices behind the PIX firewalls and the primary PIX private IP address. I would also like to monitor the standby IP address 192.168.1.6 from the tunnel and have been unsuccessful thus far. I can do this from behind the PIX, but not through the tunnel (only the primary PIX).
Is there a way I can SNMP monitor (and PING) the IP address of the standby PIX through the VPN tunnel?
Please send email to [email protected]
Thank you,
frank

Paul,
Thank you for your email. Yes, we currently use this command to monitor the active private IP of the active PIX firewall through the VPN tunnel. What I would like to be able to monitor is the private IP address of the standby PIX firewall (has a different IP address while in standby mode) would like to make sure that it too is up and running (I can do this today for other PIX firewalls from the inside, but not through the tunnel.
Best regards,
Frank Pikelner
Hi Frank,
Dont think you are going to get that to work due to the routing issues. Sending syslog messages to the snmp server is the only way Ive done it in the past. Have you given this a try?
http://cisco.com/en/US/products/sw/secursw/ps2120/products_configuration_guide_chapter09186a008017278a.html#wp1052111
http://cisco.com/en/US/products/sw/secursw/ps2120/products_system_message_guide09186a00800896ac.html
I hope this is of some help.
Cheers,
Paul.

SNMP Monitoring for Sunone 5.2

Similar Messages

Maybe you are looking for