bob55

Hi Jesper, Did you set right VRF name for your operation? Robert

1) On the picture upper I can see f0/0 192.168.1.1 on R1, in config there is that IP used for f0/2. Could you check, which interface is used for connection from R1 to R2? 2) Routing on R2 is probably not set correctly, all traffic is directed to 192.168.1.1, I suggest to remove routing rule from this device by running no…

Could you display running configuration of these three devices by running sh run cli command? Thanks, Robert

Hi netlogix, let me summarize it to ensure that I understood your configuration well: For URL like https://FQDN/App1 your reverse proxy server calls WSDL Cluster1 identified by VIP1 compound e.g. from Node1 and Node2, for URL like https://FQDN/App2 your reverse proxy server calls WSDL Cluster2 identified by VIP2 compound…

It's probably a typo, not SNMP but SMTP.

So, it's reporting Operation Timeout in IP SLA Manager and router console as well, right? This can be caused by missing time synchronization between the device and operation target device. Could you check if the difference between working operations and operation with timeout issue isn't in missing NTR/SNTR…

To clear the data from database you need remove all applications referencing that database (all mailbox servers from the same DAG hosting this database) and then run DB maintenance. If it doesn't help, please open support ticket as aLTeReGo suggests. Robert

Hi seniorza​, Database File size, Transaction Log File size and Total size are saved per database/transaction log file, so available as statistics of database file. In a chart you can group them by database, so it's the way how to get to the result. If you want to see Size for database file or transacrion log file size…

Hi netlogix, is your cluster node directly accessible from browser, using dedicated IP from NLB properties? If not, do you have both IP addresses set as identities for your cluster node website? If cluster node is accessible from browser, please, try to use use url in form https://${IP}/App1with Ignore CN Errors option set…

Probably it's as some routing issue in your network. ICMP Path Jitter operation uses traceroute to get list of hops, could you check if traceroute returns the same hop list? Robert

Yes, you're right. Time tolerance for this is by default one day. Time difference could be caused by wrong time set on the device as you mentioned, moreover several times we have seen completely wrong timestamps received by SNMP from the device even if time was set correctly there. This was caused by some IOS bug.

Hi bilel, IPSLA writes standard IOS commands for setting up Path Echo/Path Jitter operations. For more details, follow these links, please: Cisco IOS IP SLAs Configuration Guide, Release 12.4 - IP SLAs--Analyzing IP Service Levels Using the ICMP Path Echo Operation [Cisco IOS Software Releases 12.4 Mainline] - Cisco…

Hi @humejo, As you're probably have SAM 6.2 RC2 installed, you can use custom SWQL Alert on Orion.APM.SqlDatabase entity using query like following (just customize the WHERE condition): SELECT SqlDatabase.Uri, SqlDatabase.DisplayName FROM Orion.APM.SqlDatabase AS SqlDatabase INNER JOIN Orion.APM.SqlDatabaseMirroring as…

Then it could be caused by disabled generating of call quality metrics on Call Manager (it's disabled by default). Check this on CUCM admin console: System -> Service Parameters, scroll to Cluserwide parameters, check Call diagnostics enabled

What's the frequency of incoming emails? Can you try temporarily stop alerting service? If the service is down but emails still coming, I would search for an issue on SMTP server. If it doesn't help I suggest you to open support ticket. Robert

1) Is it ICMP Path Jitter operation we're talking about? It's important to know for me to determine possible cause. Results of Path operations are polled by CLI and results of other operation types are polled by SNMP. 2) What's the status message of operations with Down status? Robert

Try to use following: SELECT GroupID, TemplateID, AgentWmiCredentialsID, SnmpIcmpCredentialsID, AutoAssign, AutoDelete, ServersOnly, CreationTime FROM Orion.APM.TemplateGroupAssignment WHERE GroupID = <your group ID> Robert

This can have multiple reasons and could be really dependent on operation type. For Path Jitter and Path Echo operation types this could be caused by timezone parsing issue. For other operation types this could be caused by completely wrong time received by SNMP. Some devices are having issue like that and in such case…

As I can see, you're using script monitor, which can produce up to 10 numeric results. Thresholds for these values are not available through ComponentAlertThresholds relation neither any other way using Orion SDK, SWIS or alerting variables. So I'm affraid there is no solution for this right now. I recommend you to open…

Is the search page working from different browser without issue or can you see any error on page? I suggest you to open support ticket for this issue. Thanks, Robert

I suggest to create multiple monitors for each of your cluster nodes. Is this suitable for you?

Hi liufisky, could you provide us with cli command "sh ip sla sta <operation number> det" result using operation number of path jitter operation "R1 -> 192.168.2.2"? Thanks, Robert

There is no possibility to change built in ssh client. From your description it seems, that operation wasn't configured on the device, however you can ensure on operation details resource. If the ssh/telnet protocol and port are set properly for the source node but IPSLAM cannot connect to the device, I suggest you to open…

Account limitation for node should work also with these versions.

Joe, The WinRM Connection Limitations issue can be related to the original issue with unknown mailbox count. How does it look like after you changed the session limit? Thanks for update, Robert

Hi, The question was about additional poller (additional polling engine), not about custom poller. If operations are polled by additional polling engine, it has to be upgraded to VNQM 4.0 as well to make it working properly. Robert

You can apply account limitations for each user and define set of nodes visible to him. It will be also applied for IPSLA operation resources. Robert

SAM doesn't pre-calculate "Last 7 Days" and "Last 30 Days" for "Received" statistics, it does so only for "Sent" statistics. If you need something like this for "Received", you have to summarize APM_ExBB_MailboxAccount_Detail.MessagesReceivedInternal and APM_ExBB_MailboxAccount_Detail.MessagesReceivedExternal for last 7/30…

Hi bilel, Most of operations are set up by SNMP. Path Echo and Path Jitter operations are set up by CLI (Telnet/SSH) using ip sla/ip sla monitor/rtr configuration mode command in dependance on command syntax, supported by device IOS version. Is this what you're asking for? Robert

Hi Bilel, for ICMP Echo operation setup we're writing to CISCO-RTTMON-MIB:rttMonCtrlAdminTable OID 1.3.6.1.4.1.9.9.42.1.2.1 CISCO-RTTMON-MIB:rttMonEchoAdminTable OID 1.3.6.1.4.1.9.9.42.1.2.2 Regards, Robert