Monitoring IP SLA

Someone told me it is possible to graph IP SLA statistic on Cisco Router itself, is it true? if yes, how do to that?
Moreover,I try to set "history hours-of-statistics-kept 3". How to see this history statistic via CLI?
Thanks,
CT

Hi Any one help please and also tell the troubleshoot steps for the ip sla jitter its urgent my principal is eating me.

Similar Messages

Setting monitoring and SLA Alerts via Workspace studio

Hi,
Is it possible to set monitoring and SLA Alert rules via workspace studio. If yes, could you please help me how to do it.
Thanks
James

Hi..
Operational settings such as enabled, tracing, monitoring etc are easily set within eclipse by editing with the text editor rather than the proxy editor..
The SLA Alerts are possible to modify in the same way, but they're a bit more tricky to figure out..
..Mark.

IP SLA Monitor /Tracking 2921

I am looking or IOS code for a Cisco 2921/K9 that will allow me to do IP SLA Tracking. The current code "c2900-universalk9-mz.SPA.151-4.M.bin" will only allow me to sset up IP SLA responder or IP SLA Server but NOT IP SLA Monitor or IP SLA RTR.
I have used the Cisco feature set research tool and chose what it recommended but to no avail.
Am I missing something? Will the Server or Responder perform tracking?
Thanks in advance to anyone who can assist..
~g

Dear All,
I have the same problem with C2921. I want to config IP SLA for my C2921 but it seems do not support. The below for your reference.
####### Do not have option monitor
ip sla ?
key-chain Use MD5 Authentication for IP SLAs Control Messages
responder Enable IP SLAs Responder
server     IPPM server configuration
Show version
System image file is "flash0:c2900-universalk9-mz.SPA.151-4.M1.bin"
License Info:
License UDI:
Device#   PID                   SN
*0        CISCO2921/K9          FGL153913PM
Technology Package License Information for Module:'c2900'
Technology    Technology-package           Technology-package
              Current       Type           Next reboot
ipbase        ipbasek9      Permanent      ipbasek9
security      None          None           None
uc            None          None           None
data          None          None           None
Please kindly advise what ios I can use for configuring IP SLA. there're any problem with my licence for that
Best Regards,
Binh

ALSB Monitoring statistics export to file

Hello,
I'm currently working on ALSB 3.0, en setting up monitoring and SLA-alerting. I do get the statistics on the the service-health tab (within operations). I was wondering if it is possible to export these statistics to a file.
With regards,
Wilco Meijer

Out of box-not possible at present.
We can use
http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/jmx_monitoring/introduction.html
http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/jmx_monitoring/example.html#wp1109828 is good one to start with.
Example program can be modified to write statistics to file.
Thanks
Manoj
Edited by: mneelapu on Nov 26, 2009 2:02 PM

OSB: Cannot found SLA Alert Log

Dear all,
http://docs.oracle.com/cd/E17904_01/doc.1111/e15867/alert_destinations.htm
"+Alert Logging: If you select Yes, alerts sent to this alert destination are logged to the alert log.+"
From this document, Where can I found the alert log ?
Thank you very much

As given in the documentation:
An alert destination can include one or more of the following types of destinations: console (default), Reporting Data stream, SNMP trap, e-mail, JMS queue, or JMS topic.You will need to configure the Alert destination to be able to see the messages there.
By default you should see them on the OSB Console.
{Operations > Monitoring > Dashboard > SLA ALerts}
{Operations > Monitoring > Dashboard > Pipeline ALerts}
Please refer to the section 6.2 in the same link to get more details on how to configure diff. alert destinations.
Thanks,
Patrick

Enterprise Business Services and Oracle Service Bus

Hi,
We are using AIA and we have developed a number of EBS’. These are composite applications containing a mediator and are deployed to the SOA Server.
Am I right in saying that another option is to use the Oracle Service Bus and replace the composite application ESB’s with ESB’s in the Oracle Service Bus?
Robert

Gerhard,
I was thinking the benefits would be:
-     End point Virtualisation – Single end point for services we can configure.
-     Move the job of wiring the integrations from Development to Admin
-     Single point of monitoring for SLA’s and QOS
-     Improve visibility of ESB’s by providing a single list. (At the moment they are amongst many services in enterprise manager.)
At the moment we have 3 SOA servers connected to 6 systems. (Dev, Test and Prod) I was imagining it might be possible to have a single OSB with Service routing controlled by policies. This way we would not need three OSB setup’s.
I am also charged with planning for the development of further services and we already have a long list of composites in enterprise manager. I am imagining that this will quickly become unmanageable. With OSB we could hide the downstream services and only show the EBS’.
I also imagined that when we introduced a 11.1.1.6 SOA server we could simply adjust the routing rules at the OSB to set up a dev environment. Test out the new services work, then make similar adjustments on a per EBS basis until we have migrated completely to 11.1.1.6.
I agree that there are a lot of trade off’s and I do not really have the experience to weigh up the balance between the two. Yesterday I was asked to come up with methods of monitoring performance of the current integration as well as future integrations and the OSB data sheet talks a little bit about this which is why I am thinking more about it; Although have only got as far as looking at the OSB data sheet and some manuals.
I guess another option would be to go with some EBS’s as mediators and others on OSB but I think using a consistent method for EBS’s would be preferable.
Also there is the question do we have one OSB for all systems or separate OSB’s for Dev, Test and Prod.
Robert

Dialup connection sporatically dials

/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin-top:0in;
mso-para-margin-right:0in;
mso-para-margin-bottom:10.0pt;
mso-para-margin-left:0in;
line-height:115%;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:"Times New Roman";
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;}
I have two sites linked together via microwave with dialup as backup solution. I have an IP SLA monitoring the main link and activates the dialup when the link goes down.
Well, my problem is that the SLA errorously sees the main link go down and kicks in the dialup. BUT just for a few seconds and once it sees the main link up it, of course, drops the dialup.
On both ends, I have increase the timeout from 1000 to 10000 and changed the frequency to 51. Hoping that prohibit the dialup. But it hasn’t.
I have added the SLA config for your reference.
This is the far-end RTR
ip sla monitor 11
type echo protocol ipIcmpEcho 10.30.12.2
timeout 10000
threshold 4
frequency 51
ip sla monitor schedule 11 life forever start-time now
this is the central RTR
ip sla monitor 12
type echo protocol ipIcmpEcho 10.30.51.254
timeout 10000
threshold 4
frequency 51
ip sla monitor schedule 12 life forever start-time now
I think I need to change the SLA statement but I’m not sure.
Thanks, Gary

Hi Gary
Can you tell me what is the ip which you are monitoring using sla? (10.30.12.2 / 10.30.251.54).
Also can you post the output of show run/show log/show ip route here
regds

Error for osb (11g ps2) cluster

I setup a 2 nodes osb (11g ps2) cluster env in my linux laptop. Everything is OK except the below error message, it's from the managed servers log. Anybody can help me, thanks a lot.
<2010-11-23 下午05时51分00秒 CST> <Error> <ALSB Statistics Manager> <BEA-473003> <Aggregation Server Not Available. Failed to get remote aggregator
java.lang.IllegalArgumentException: Server 'null' not found
     at com.bea.alsb.platform.weblogic.WlsDomainConfigurationImpl.getServer(WlsDomainConfigurationImpl.java:98)
     at com.bea.alsb.platform.weblogic.WlsDomainConfigurationImpl.getAggregationServer(WlsDomainConfigurationImpl.java:119)
     at com.bea.wli.monitoring.statistics.ALSBStatisticsManager.getRemoteAggregator(ALSBStatisticsManager.java:291)
     at com.bea.wli.monitoring.statistics.ALSBStatisticsManager.access$000(ALSBStatisticsManager.java:38)
     at com.bea.wli.monitoring.statistics.ALSBStatisticsManager$RemoteAggregatorProxy.send(ALSBStatisticsManager.java:55)
     Truncated. see log file for complete stacktrace
>

Please test it properly.. As far as I know 'ALSB Domain Singleton Marker Application' should be targeted to only a single instance and not to a cluster. Check if your monitoring and SLA alerting is working fine.
If you have setup the cluster properly, ( by specifying the correct listen addresses for the servers and the cluster), weblogic clustering will replicate jndi in all the managed servers . So all the jndi objects binded on the targeted server by this application , will be available on the jndi tree of the other man server and applications running on other server will be able to lookup the object in its local tree.. (I think the original error you were seeing was due to a failure of this).
I think you applied a wrong fix by targeting to the cluster. Hence objects are binded to both the servers without jndi replication. This might have adverse effect on how the above singleton application works. Root cause for the problem should be with the clustering setup.

Error in importing the jar

PS: We are using ALSB 2.5
We have got the exported jar from another ALSB environment, but while trying to import, we are getting following error:
The import failed with exception: com.bea.wli.config.component.ValidationException: Validation failed with diagnostic messages. Diagnostics for BusinessService CoverageVerification_IAA/BusinessService/VerifyCoverageBusinessService
ERROR: <0> Invalid xml: Expected attribute: name in element coreEntry@http://www.bea.com/wli/sb/services Location: <ser:coreEntry isProxy="false" isEnabled="true" isAutoPublish="false" xmlns:ser="http://www.bea.com/wli/sb/services" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:tran="http://www.bea.com/wli/sb/transports" xmlns:env="http://www.bea.com/wli/config/env" xmlns:http="http://www.bea.com/wli/sb/transports/http">
<ser:description/>
<ser:binding type="SOAP" isSoap12="false" xsi:type="con:SoapBindingType" xmlns:con="http://www.bea.com/wli/sb/services/bindings/config">
<con:wsdl ref="CoverageVerification_IAA/WSDL/VerifyCoverageWSDL"/>
<con:port>
<con:name>VerifyCoveragePort</con:name>
<con:namespace>http://www.ibm.com/industries/financialservices/ValidateCoverage</con:namespace>
</con:port>
<con:WSI-compliant>false</con:WSI-compliant>
</ser:binding>
<ser:monitoring isEnabled="false">
<ser:aggregationInterval>10</ser:aggregationInterval>
</ser:monitoring>
<ser:sla-alerting isEnabled="true">
<ser:alertLevel>normal</ser:alertLevel>
</ser:sla-alerting>
</ser:coreEntry>
ERROR: <0> Invalid xml: Attribute not allowed (no wildcards allowed): isSoap12 in element binding@http://www.bea.com/wli/sb/services Location: <xml-fragment isSoap12="false" xmlns:con="http://www.bea.com/wli/sb/services/bindings/config" xmlns:ser="http://www.bea.com/wli/sb/services" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:tran="http://www.bea.com/wli/sb/transports" xmlns:env="http://www.bea.com/wli/config/env" xmlns:http="http://www.bea.com/wli/sb/transports/http"/>
ERROR: <0> Invalid xml: Expected elements 'registryName@http://www.bea.com/wli/sb/services uddiServiceKey@http://www.bea.com/wli/sb/services modifiedTimeInRegistry@http://www.bea.com/wli/sb/services timeImportedFromRegistry@http://www.bea.com/wli/sb/services' instead of 'sla-alerting@http://www.bea.com/wli/sb/services' here in element coreEntry@http://www.bea.com/wli/sb/services Location: <ser:sla-alerting isEnabled="true" xmlns:ser="http://www.bea.com/wli/sb/services" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:tran="http://www.bea.com/wli/sb/transports" xmlns:env="http://www.bea.com/wli/config/env" xmlns:http="http://www.bea.com/wli/sb/transports/http">
<ser:alertLevel>normal</ser:alertLevel>
</ser:sla-alerting>
Any help on this would be appreciated.
Rajesh

It seems you are trying to import a configuration generated from ALSB 2.6 into 2.5. In that particular case your configuration contains SOAP 1.2 services that were only introduced in ALSB 2.6 so you will get an error on 2.5.
ASLB guarantees configuration backward compatibility not forward compatibility :)
Gregory Haardt
ALSB Prg. Manager
[email protected]

Crazy JMS pattern

Hi,
I'm trying to implement this:
- JMS queue BS, named QUEUE, is request/response, it has a URI endpoint and a response URI endpoint
I have 3 proxy services working around this JMS queue, but for now I'm only working with two of them:
- PS 1: receives the http message and writes into the queue with transport outbound JMSMessageID = $body/messageid
- PS 3: an external entity now wants to communicate the response, and this PS routes into QUEUE response endpoint with transport outbound JMSCorrelationID = previous JMSMessageID
Is this possible to do?
I'm having an hard time implementing this, cause PS 1 just freezes and never correlates to the response.
I'm testing this using soapUI... making sure $body/messageid is common at all times.
Is there some tool to check messages (and headers) in JMS queues?
Can someone help me with this plz?

atheek1 I guess you are right.
However I still didn't manage to implement the desired correlation pattern.
I'm surely doing it wrong... but kinda running out of options.
I made two new JMS BS: requestQueue_BS and responseQueue_BS
Both are queues and text message type and requestQueue is JMSCorrelationID response pattern with response URI = responseQueue_BS
PS1 is any XML service that simply routes message to requestQueue using, inside routing, an transport header transformation of JMSCorrelationID to $body/id/text() on outbound request direction.
PS3 is any XML service that simply routes message to responseQueue using, inside routing, an transport header transformation of JMSCorrelationID to $body/id/text() on outbound request direction.
message body example is: <id>4324</id>
This doesn't work... what am I doing wrong?
PS1 just waits for the response... it doesn't matter how many times I trigger PS3 with the same JMSCorrelationID, PS1 just waits until it times out... :(
******* CONFIG FILES ************
requestQueue
<?xml version="1.0" encoding="UTF-8"?>
<xml-fragment xmlns:ser="http://www.bea.com/wli/sb/services" xmlns:tran="http://www.bea.com/wli/sb/transports" xmlns:http="http://www.bea.com/wli/sb/transports/http" xmlns:env="http://www.bea.com/wli/config/env" xmlns:jms="http://www.bea.com/wli/sb/transports/jms">
<ser:coreEntry isProxy="false" isEnabled="true">
<ser:binding type="abstract XML"/>
<ser:monitoring isEnabled="false">
<ser:aggregationInterval>10</ser:aggregationInterval>
</ser:monitoring>
<ser:sla-alerting isEnabled="true">
<ser:alertLevel>normal</ser:alertLevel>
</ser:sla-alerting>
</ser:coreEntry>
<ser:endpointConfig>
<tran:provider-id>jms</tran:provider-id>
<tran:inbound>false</tran:inbound>
<tran:URI>
<env:value>jms://localhost:7001/weblogic.jms.XAConnectionFactory/requestQueueRequest</env:value>
</tran:URI>
<tran:outbound-properties>
<tran:load-balancing-algorithm>round-robin</tran:load-balancing-algorithm>
<tran:retry-count>0</tran:retry-count>
<tran:retry-interval>30</tran:retry-interval>
<tran:retry-application-errors>true</tran:retry-application-errors>
</tran:outbound-properties>
<tran:provider-specific>
<jms:is-queue>true</jms:is-queue>
<jms:is-secure>false</jms:is-secure>
<jms:outbound-properties>
<jms:message-type>Text</jms:message-type>
<jms:expiration>0</jms:expiration>
<jms:enable-message-persistence>true</jms:enable-message-persistence>
<jms:response-required>true</jms:response-required>
<jms:response-URI>jms://localhost:7001/weblogic.jms.XAConnectionFactory/responseQueueRequest</jms:response-URI>
<jms:response-timeout>0</jms:response-timeout>
<jms:response-pattern>JMSCorrelationID</jms:response-pattern>
<jms:response-target-map>
<jms:target-pair>
<jms:target>AdminServer</jms:target>
<jms:destination/>
</jms:target-pair>
</jms:response-target-map>
<jms:pass-caller-subject>false</jms:pass-caller-subject>
</jms:outbound-properties>
<jms:request-encoding>UTF-8</jms:request-encoding>
</tran:provider-specific>
</ser:endpointConfig>
</xml-fragment>
and responseQueue
<?xml version="1.0" encoding="UTF-8"?>
<xml-fragment xmlns:ser="http://www.bea.com/wli/sb/services" xmlns:tran="http://www.bea.com/wli/sb/transports" xmlns:http="http://www.bea.com/wli/sb/transports/http" xmlns:env="http://www.bea.com/wli/config/env" xmlns:jms="http://www.bea.com/wli/sb/transports/jms">
<ser:coreEntry isProxy="false" isEnabled="true">
<ser:binding type="abstract XML"/>
<ser:monitoring isEnabled="false">
<ser:aggregationInterval>10</ser:aggregationInterval>
</ser:monitoring>
<ser:sla-alerting isEnabled="true">
<ser:alertLevel>normal</ser:alertLevel>
</ser:sla-alerting>
</ser:coreEntry>
<ser:endpointConfig>
<tran:provider-id>jms</tran:provider-id>
<tran:inbound>false</tran:inbound>
<tran:URI>
<env:value>jms://localhost:7001/weblogic.jms.XAConnectionFactory/responseQueueRequest</env:value>
</tran:URI>
<tran:outbound-properties>
<tran:load-balancing-algorithm>round-robin</tran:load-balancing-algorithm>
<tran:retry-count>0</tran:retry-count>
<tran:retry-interval>30</tran:retry-interval>
<tran:retry-application-errors>true</tran:retry-application-errors>
</tran:outbound-properties>
<tran:provider-specific>
<jms:is-queue>true</jms:is-queue>
<jms:is-secure>false</jms:is-secure>
<jms:outbound-properties>
<jms:message-type>Text</jms:message-type>
<jms:expiration>0</jms:expiration>
<jms:enable-message-persistence>true</jms:enable-message-persistence>
<jms:response-required>false</jms:response-required>
<jms:pass-caller-subject>false</jms:pass-caller-subject>
</jms:outbound-properties>
<jms:request-encoding>UTF-8</jms:request-encoding>
</tran:provider-specific>
</ser:endpointConfig>
</xml-fragment>
PS1
<?xml version="1.0" encoding="UTF-8"?>
<xml-fragment xmlns:ser="http://www.bea.com/wli/sb/services" xmlns:tran="http://www.bea.com/wli/sb/transports" xmlns:env="http://www.bea.com/wli/config/env" xmlns:http="http://www.bea.com/wli/sb/transports/http" xmlns:con="http://www.bea.com/wli/sb/stages/config">
<ser:coreEntry isProxy="true" isEnabled="true">
<ser:binding type="abstract XML"/>
<ser:monitoring isEnabled="false">
<ser:aggregationInterval>10</ser:aggregationInterval>
<ser:pipelineMonitoringLevel>Pipeline</ser:pipelineMonitoringLevel>
</ser:monitoring>
<ser:reporting>true</ser:reporting>
<ser:logging isEnabled="true">
<ser:logLevel>debug</ser:logLevel>
</ser:logging>
<ser:sla-alerting isEnabled="true">
<ser:alertLevel>normal</ser:alertLevel>
</ser:sla-alerting>
<ser:pipeline-alerting isEnabled="true">
<ser:alertLevel>normal</ser:alertLevel>
</ser:pipeline-alerting>
</ser:coreEntry>
<ser:endpointConfig>
<tran:provider-id>http</tran:provider-id>
<tran:inbound>true</tran:inbound>
<tran:URI>
<env:value>/ItevProj/proxy/test/3/ps1</env:value>
</tran:URI>
<tran:inbound-properties/>
<tran:all-headers>false</tran:all-headers>
<tran:provider-specific>
<http:inbound-properties/>
</tran:provider-specific>
</ser:endpointConfig>
<ser:router>
<con:flow xmlns:con="http://www.bea.com/wli/sb/pipeline/config">
<con:route-node name="RouteNode1">
<con:context/>
<con:actions>
<con1:route xmlns:con1="http://www.bea.com/wli/sb/stages/routing/config">
<con2:id xmlns:con2="http://www.bea.com/wli/sb/stages/config">_ActionId-9035043200913057533-78de896f.1287cc7514b.-7faf</con2:id>
<con1:service ref="ItevProj/business/common/jms/test/3/requestQueue" xsi:type="ref:BusinessServiceRef" xmlns:ref="http://www.bea.com/wli/sb/reference" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<con1:outboundTransform>
<con2:transport-headers xmlns:con2="http://www.bea.com/wli/sb/stages/transform/config">
<con3:id xmlns:con3="http://www.bea.com/wli/sb/stages/config">_ActionId-9035043200913057533-78de896f.1287cc7514b.-7da1</con3:id>
<con2:header-set>outbound-request</con2:header-set>
<con2:header name="JMSCorrelationID" value="expression">
<con3:xqueryText xmlns:con3="http://www.bea.com/wli/sb/stages/config">$body/id/text()</con3:xqueryText>
</con2:header>
</con2:transport-headers>
</con1:outboundTransform>
<con1:responseTransform/>
</con1:route>
</con:actions>
</con:route-node>
</con:flow>
</ser:router>
</xml-fragment>
PS3
<?xml version="1.0" encoding="UTF-8"?>
<xml-fragment xmlns:ser="http://www.bea.com/wli/sb/services" xmlns:tran="http://www.bea.com/wli/sb/transports" xmlns:env="http://www.bea.com/wli/config/env" xmlns:http="http://www.bea.com/wli/sb/transports/http" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:con="http://www.bea.com/wli/sb/pipeline/config" xmlns:con1="http://www.bea.com/wli/sb/stages/routing/config" xmlns:con2="http://www.bea.com/wli/sb/stages/config">
<ser:coreEntry isProxy="true" isEnabled="true">
<ser:binding type="abstract XML" xmlns:con3="http://www.bea.com/wli/sb/services/bindings/config"/>
<ser:monitoring isEnabled="false">
<ser:aggregationInterval>10</ser:aggregationInterval>
<ser:pipelineMonitoringLevel>Pipeline</ser:pipelineMonitoringLevel>
</ser:monitoring>
<ser:reporting>true</ser:reporting>
<ser:logging isEnabled="true">
<ser:logLevel>debug</ser:logLevel>
</ser:logging>
<ser:sla-alerting isEnabled="true">
<ser:alertLevel>normal</ser:alertLevel>
</ser:sla-alerting>
<ser:pipeline-alerting isEnabled="true">
<ser:alertLevel>normal</ser:alertLevel>
</ser:pipeline-alerting>
</ser:coreEntry>
<ser:endpointConfig>
<tran:provider-id>http</tran:provider-id>
<tran:inbound>true</tran:inbound>
<tran:URI>
<env:value>/ItevProj/proxy/test/3/ps3</env:value>
</tran:URI>
<tran:inbound-properties/>
<tran:all-headers>false</tran:all-headers>
<tran:provider-specific>
<http:inbound-properties/>
</tran:provider-specific>
</ser:endpointConfig>
<ser:router>
<con:flow>
<con:route-node name="RouteNode1">
<con:context>
<con2:varNsDecl namespace="http://webservice.chargingstation.itev.criticalsoftware.com" prefix="web"/>
</con:context>
<con:actions>
<con1:route>
<con2:id>_ActionId-9035043200913057533-78de896f.1287cc7514b.-7eb7</con2:id>
<con1:service ref="ItevProj/business/common/jms/test/3/responseQueue" xsi:type="ref:BusinessServiceRef" xmlns:ref="http://www.bea.com/wli/sb/reference"/>
<con1:outboundTransform>
<con3:transport-headers xmlns:con3="http://www.bea.com/wli/sb/stages/transform/config">
<con2:id>_ActionId-9035043200913057533-78de896f.1287cc7514b.-7d69</con2:id>
<con3:header-set>outbound-request</con3:header-set>
<con3:header name="JMSCorrelationID" value="expression">
<con2:xqueryText>$body/id/text()</con2:xqueryText>
</con3:header>
</con3:transport-headers>
</con1:outboundTransform>
<con1:responseTransform/>
</con1:route>
</con:actions>
</con:route-node>
</con:flow>
</ser:router>
</xml-fragment>

OSB 10g Offline Endpoint URI is not working

We are facing an issue with marking Endpoint URI to offline on unavailability.
Have tried all possible ways to check this issue in environments by making all necessary configurations but somehow the URI's are not being marked out offline.
Please confirm if this is know issue or we missing anything out configurations?
Thanks.

Hi,
There is no issue that I know of...
In my configuration I have state and Offline Endpoint URIs enabled and also monitoring and SLA alerts enabled...
I created an SLA alert that sends me email if an URI gets offline -- Any URI offline on all servers = true
It works for me...
How are you testing? What makes you believe the URI is not being marked as offline?
Cheers,
Vlad
It is considered good etiquette to reward answerers with points (as "helpful" - 5 pts - or "correct" - 10pts)
https://forums.oracle.com/forums/ann.jspa?annID=893

OEG/Oracle API gateway vs OSB

I see most of the capabilities which an enterprise bus offers can also be implemented in OEG or Oracle API gateway. I understand that OEG is a gateway and is meant to be used as first layer of defense for security. However, in terms of features and capabilities OEG has almost all the features that a enterprise bus like OSB provides.
OEG provides Monitoring capabilities -> SLA alerts, logging of payloads for auditing
Routing, transformations, and protocol conversions like accepting Rest messages and converting to SOAP and call soap services.
expect the features like dynamic routing, split join I see almost all features including throttling and caching are available in OEG.
Can some one tell me if it is a correct decision to use OEG instead of using service bus for implementing the interfaces.

I was having the same same knowledge the one that you supplied. We have set-up the API gateway with bundled server.
But I was working with Oracle support on one of the other issue and Support engineer informed me when you deploy the services you can select the WebLogic server instance like Gateway server instance. This was confusing so I open the Oracle ticket and post the question in forum.
I know we can integrate the OAG with WebLogic but installing the Gateway product on WeblOgic JVM process was my doubt.

ASA5510 sla monitor does not fail back

I've been down this path before and never got a resolution to this issue.
ASA5510 Security Plus
Primary ISP conn is Comcast cable
Secondary ISP conn is fract T1
I duplicated the SLA code from http://www.cisco.com/en/US/partner/products/hw/vpndevc/ps2030/products_configuration_example09186a00806e880b.shtml
When I pull the conn from primary ISP the default route to the secondary comes up
When I reconnect the primary the default route to the secondary does not go away.
I must either reload the ASA or remove/readd the two default outside routes.
Anyone have this same experience and could lend a hand?
Are there any commands I might have in my config that break SLA?
If so I would have hoped either the Configuration Guide or Command Reference for 8.2 would say so, but I don't see any mentioned.
I'm working remotely with my customer so I can't play with this except on off-hours.
ASA running 8.2(2) so as to use AnyConnect Essentials.
Thx,
Phil

Pls. read and try the workaround.
CSCtc16148 SLA monitor fails to fail back when ip verify reverse is applied
Symptom:
Route Tracking may fail to fail back to the primary link/route when restored.
Conditions:
SLA monitor must configured along with ip verify reverse path on the tracked interface.
Workaround:
1. Remove ip verify reverse path off of the tracked interface
or
2. add a static route to the SLA target out the primary tracked interface.
[Wrap text] [Edit this enclosure]
Release-note: Added 09/23/2009 20:28:24 by kusankar
[Unwrap text] [Edit this enclosure]
Release-note: Added 09/23/2009 20:28:24 by kusankar
[Uwrap text] [Edit this enclosure]
fixed-in-broadview-8.3.1.1_interim-by-cl104097: Added 03/23/2010 11:54:08 by perforce
fixed-in-broadview-8.3.1.1_interim-by-cl104097: Added 03/23/2010 11:54:08 by perforceCan not view this . file attachment inline, please click on the following link to view the attachment.
http://cdetsweb-prd.cisco.com/apps/dumpcr_att?identifier=CSCtc16148&title=fixed-in-broadview-8.3.1.1_interim-by-cl104097&ext=&type=FILE
fixed-in-broadview-8.3.1.1_interim-by-cl104097: Added 03/23/2010 11:54:08 by perforceCan not view this . file attachment inline, please click on the following link to view the attachment.
http://
[UnWrap text] [Edit this enclosure]
fixed-in-broadview-8.3.1.1_interim-by-cl104097: Added 03/23/2010 11:54:08 by perforce
[Wrap Text] [Edit this enclosure]
fixed-in-broadview-8.3.1.1_interim-by-cl104097: Added 03/23/2010 11:54:08 by perforce
[Uwrap text] [Edit this enclosure]
fixed-in-broadview-8.3.1_fcs_throttle-by-cl103850: Added 03/22/2010 15:48:05 by perforce
fixed-in-broadview-8.3.1_fcs_throttle-by-cl103850: Added 03/22/2010 15:48:05 by perforceCan not view this . file attachment inline, please click on the following link to view the attachment.
http://cdetsweb-prd.cisco.com/apps/dumpcr_att?identifier=CSCtc16148&title=fixed-in-broadview-8.3.1_fcs_throttle-by-cl103850&ext=&type=FILE
fixed-in-broadview-8.3.1_fcs_throttle-by-cl103850: Added 03/22/2010 15:48:05 by perforceCan not view this . file attachment inline, please click on the following link to view the attachment.
http://
[UnWrap text] [Edit this enclosure]
fixed-in-broadview-8.3.1_fcs_throttle-by-cl103850: Added 03/22/2010 15:48:05 by perforce
[Wrap Text] [Edit this enclosure]
fixed-in-broadview-8.3.1_fcs_throttle-by-cl103850: Added 03/22/2010 15:48:05 by perforce
[Uwrap text] [Edit this enclosure]
fixed-in-broadview-bennu-by-cl101314: Added 02/18/2010 19:06:08 by perforce
fixed-in-broadview-bennu-by-cl101314: Added 02/18/2010 19:06:08 by perforceCan not view this . file attachment inline, please click on the following link to view the attachment.
http://cdetsweb-prd.cisco.com/apps/dumpcr_att?identifier=CSCtc16148&title=fixed-in-broadview-bennu-by-cl101314&ext=&type=FILE
fixed-in-broadview-bennu-by-cl101314: Added 02/18/2010 19:06:08 by perforceCan not view this . file attachment inline, please click on the following link to view the attachment.
http://
[UnWrap text] [Edit this enclosure]
fixed-in-broadview-bennu-by-cl101314: Added 02/18/2010 19:06:08 by perforce
[Wrap Text] [Edit this enclosure]
fixed-in-broadview-bennu-by-cl101314: Added 02/18/2010 19:06:08 by perforce
[Uwrap text] [Edit this enclosure]
fixed-in-broadview-idfw-by-cl101317: Added 02/18/2010 19:09:07 by perforce
fixed-in-broadview-idfw-by-cl101317: Added 02/18/2010 19:09:07 by perforceCan not view this . file attachment inline, please click on the following link to view the attachment.
http://cdetsweb-prd.cisco.com/apps/dumpcr_att?identifier=CSCtc16148&title=fixed-in-broadview-idfw-by-cl101317&ext=&type=FILE
fixed-in-broadview-idfw-by-cl101317: Added 02/18/2010 19:09:07 by perforceCan not view this . file attachment inline, please click on the following link to view the attachment.
http://
[UnWrap text] [Edit this enclosure]
fixed-in-broadview-idfw-by-cl101317: Added 02/18/2010 19:09:07 by perforce
[Wrap Text] [Edit this enclosure]
fixed-in-broadview-idfw-by-cl101317: Added 02/18/2010 19:09:07 by perforce
[Uwrap text] [Edit this enclosure]
fixed-in-broadview-logging-ng-by-cl101311: Added 02/18/2010 19:03:08 by perforce
fixed-in-broadview-logging-ng-by-cl101311: Added 02/18/2010 19:03:08 by perforceCan not view this . file attachment inline, please click on the following link to view the attachment.
http://cdetsweb-prd.cisco.com/apps/dumpcr_att?identifier=CSCtc16148&title=fixed-in-broadview-logging-ng-by-cl101311&ext=&type=FILE
fixed-in-broadview-logging-ng-by-cl101311: Added 02/18/2010 19:03:08 by perforceCan not view this . file attachment inline, please click on the following link to view the attachment.
http://
[UnWrap text] [Edit this enclosure]
fixed-in-broadview-logging-ng-by-cl101311: Added 02/18/2010 19:03:08 by perforce
[Wrap Text] [Edit this enclosure]
fixed-in-broadview-logging-ng-by-cl101311: Added 02/18/2010 19:03:08 by perforce
[Uwrap text] [Edit this enclosure]
fixed-in-broadview-main-by-cl101300: Added 02/18/2010 18:27:07 by perforce
fixed-in-broadview-main-by-cl101300: Added 02/18/2010 18:27:07 by perforceCan not view this . file attachment inline, please click on the following link to view the attachment.
http://cdetsweb-prd.cisco.com/apps/dumpcr_att?identifier=CSCtc16148&title=fixed-in-broadview-main-by-cl101300&ext=&type=FILE
fixed-in-broadview-main-by-cl101300: Added 02/18/2010 18:27:07 by perforceCan not view this . file attachment inline, please click on the following link to view the attachment.
http://
[UnWrap text] [Edit this enclosure]
fixed-in-broadview-main-by-cl101300: Added 02/18/2010 18:27:07 by perforce
[Wrap Text] [Edit this enclosure]
fixed-in-broadview-main-by-cl101300: Added 02/18/2010 18:27:07 by perforce
[Uwrap text] [Edit this enclosure]
fixed-in-sedona-64bit-by-cl101362: Added 02/19/2010 04:52:24 by perforce
fixed-in-sedona-64bit-by-cl101362: Added 02/19/2010 04:52:24 by perforceCan not view this . file attachment inline, please click on the following link to view the attachment.
http://cdetsweb-prd.cisco.com/apps/dumpcr_att?identifier=CSCtc16148&title=fixed-in-sedona-64bit-by-cl101362&ext=&type=FILE
fixed-in-sedona-64bit-by-cl101362: Added 02/19/2010 04:52:24 by perforceCan not view this . file attachment inline, please click on the following link to view the attachment.
http://
[UnWrap text] [Edit this enclosure]
fixed-in-sedona-64bit-by-cl101362: Added 02/19/2010 04:52:24 by perforce
[Wrap Text] [Edit this enclosure]
fixed-in-sedona-64bit-by-cl101362: Added 02/19/2010 04:52:24 by perforce
[Uwrap text] [Edit this enclosure]
fixed-in-sedona-bv64-by-cl101426: Added 02/19/2010 11:42:41 by perforce
fixed-in-sedona-bv64-by-cl101426: Added 02/19/2010 11:42:41 by perforceCan not view this . file attachment inline, please click on the following link to view the attachment.
http://cdetsweb-prd.cisco.com/apps/dumpcr_att?identifier=CSCtc16148&title=fixed-in-sedona-bv64-by-cl101426&ext=&type=FILE
fixed-in-sedona-bv64-by-cl101426: Added 02/19/2010 11:42:41 by perforceCan not view this . file attachment inline, please click on the following link to view the attachment.
http://
[UnWrap text] [Edit this enclosure]
fixed-in-sedona-bv64-by-cl101426: Added 02/19/2010 11:42:41 by perforce
[Wrap Text] [Edit this enclosure]
fixed-in-sedona-bv64-by-cl101426: Added 02/19/2010 11:42:41 by perforce
[Uwrap text] [Edit this enclosure]
fixed-in-sedona-main-by-cl101297: Added 02/18/2010 18:24:15 by perforce
fixed-in-sedona-main-by-cl101297: Added 02/18/2010 18:24:15 by perforceCan not view this . file attachment inline, please click on the following link to view the attachment.
http://cdetsweb-prd.cisco.com/apps/dumpcr_att?identifier=CSCtc16148&title=fixed-in-sedona-main-by-cl101297&ext=&type=FILE
fixed-in-sedona-main-by-cl101297: Added 02/18/2010 18:24:15 by perforceCan not view this . file attachment inline, please click on the following link to view the attachment.
http://
[UnWrap text] [Edit this enclosure]
fixed-in-sedona-main-by-cl101297: Added 02/18/2010 18:24:15 by perforce
[Wrap Text] [Edit this enclosure]
fixed-in-sedona-main-by-cl101297: Added 02/18/2010 18:24:15 by perforce
[Uwrap text] [Edit this enclosure]
fixed-in-titan-8.2.2_fcs_throttle-by-cl101307: Added 02/18/2010 18:57:08 by perforce
fixed-in-titan-8.2.2_fcs_throttle-by-cl101307: Added 02/18/2010 18:57:08 by perforceCan not view this . file attachment inline, please click on the following link to view the attachment.
http://cdetsweb-prd.cisco.com/apps/dumpcr_att?identifier=CSCtc16148&title=fixed-in-titan-8.2.2_fcs_throttle-by-cl101307&ext=&type=FILE
fixed-in-titan-8.2.2_fcs_throttle-by-cl101307: Added 02/18/2010 18:57:08 by perforceCan not view this . file attachment inline, please click on the following link to view the attachment.
http://
[UnWrap text] [Edit this enclosure]
fixed-in-titan-8.2.2_fcs_throttle-by-cl101307: Added 02/18/2010 18:57:08 by perforce
[Wrap Text] [Edit this enclosure]
fixed-in-titan-8.2.2_fcs_throttle-by-cl101307: Added 02/18/2010 18:57:08 by perforce
[Uwrap text] [Edit this enclosure]
fixed-in-titan-bennu-by-cl101294: Added 02/18/2010 18:24:08 by perforce
fixed-in-titan-bennu-by-cl101294: Added 02/18/2010 18:24:08 by perforceCan not view this . file attachment inline, please click on the following link to view the attachment.
http://cdetsweb-prd.cisco.com/apps/dumpcr_att?identifier=CSCtc16148&title=fixed-in-titan-bennu-by-cl101294&ext=&type=FILE
fixed-in-titan-bennu-by-cl101294: Added 02/18/2010 18:24:08 by perforceCan not view this . file attachment inline, please click on the following link to view the attachment.
http://
[UnWrap text] [Edit this enclosure]
fixed-in-titan-bennu-by-cl101294: Added 02/18/2010 18:24:08 by perforce
[Wrap Text] [Edit this enclosure]
fixed-in-titan-bennu-by-cl101294: Added 02/18/2010 18:24:08 by perforce
[Uwrap text] [Edit this enclosure]
fixed-in-titan-main-by-cl101282: Added 02/18/2010 16:48:04 by perforce
fixed-in-titan-main-by-cl101282: Added 02/18/2010 16:48:04 by perforceCan not view this . file attachment inline, please click on the following link to view the attachment.
http://cdetsweb-prd.cisco.com/apps/dumpcr_att?identifier=CSCtc16148&title=fixed-in-titan-main-by-cl101282&ext=&type=FILE
fixed-in-titan-main-by-cl101282: Added 02/18/2010 16:48:04 by perforceCan not view this . file attachment inline, please click on the following link to view the attachment.
http://
[UnWrap text] [Edit this enclosure]
fixed-in-titan-main-by-cl101282: Added 02/18/2010 16:48:04 by perforce
[Wrap Text] [Edit this enclosure]
fixed-in-titan-main-by-cl101282: Added 02/18/2010 16:48:04 by perforce
[Uwrap text] [Edit this enclosure]
sla-mon-sh-tech: Added 09/23/2009 20:43:52 by kusankar
sla-mon-sh-tech: Added 09/23/2009 20:43:52 by kusankarCan not view this .log file attachment inline, please click on the following link to view the attachment.
http://cdetsweb-prd.cisco.com/apps/dumpcr_att?identifier=CSCtc16148&title=sla-mon-sh-tech&ext=log&type=FILE
sla-mon-sh-tech: Added 09/23/2009 20:43:52 by kusankarCan not view this .log file attachment inline, please click on the following link to view the attachment.
http://
[UnWrap text] [Edit this enclosure]
sla-mon-sh-tech: Added 09/23/2009 20:43:52 by kusankar
[Wrap Text] [Edit this enclosure]
sla-mon-sh-tech: Added 09/23/2009 20:43:52 by kusankar
[Uwrap text] [Edit this enclosure]
static-analysis-titan-main: Added 02/18/2010 16:48:07 by perforce
static-analysis-titan-main: Added 02/18/2010 16:48:07 by perforceCan not view this . file attachment inline, please click on the following link to view the attachment.
http://cdetsweb-prd.cisco.com/apps/dumpcr_att?identifier=CSCtc16148&title=static-analysis-titan-main&ext=&type=FILE
static-analysis-titan-main: Added 02/18/2010 16:48:07 by perforceCan not view this . file attachment inline, please click on the following link to view the attachment.
http://
[UnWrap text] [Edit this enclosure]
static-analysis-titan-main: Added 02/18/2010 16:48:07 by perforce
[Wrap Text] [Edit this enclosure]
static-analysis-titan-main: Added 02/18/2010 16:48:07 by perforce
-KS

IP SLA Monitor

Hi all!
We are using IP SLA to monitor the WAN IP from a client:
ip sla monitor 1
type echo protocol ipIcmpEcho 192.168.251.206 source-interface GigabitEthernet0/1
request-data-size 10
timeout 2000
threshold 4000
frequency 5
ip sla monitor schedule 1 life forever start-time now
track 104 rtr 1 reachability
delay down 8 up 30
When the link is down, traffic is switched to another link. The problem is that when we are doing maintenance with the problem link, any oscillation (up/down) causes the link to be switched back to the link with problem. The only solution we found for this case is to give a shutdown on the interface that is being repaired.
Does anyone know what I can do to prevent traffic is switched to the link that is being repaired?
Appreciate any help

Hi Sachin!
I think it would be interesting to increase the monitoring time, if the main link becomes down. You know I can how do this without using load balancing (HSRP, VRRP, GLBP ...)? Because we are monitoring the wan interface of the client, ie, on the other end of the cloud.
Thanks.

Configuring and using SLA alerts and Monitoring in OSB.

Hi,
I am having a business service which logically represents composite endpoint URI. Now I want to enable Monitoring and generate an SLA alert if the composite URI that the business service is representing is DOWN for some reason and the proxy routing to the BS is not able to invoke it.
How do I do that? Pls suggest!

Hi Deb,
Please refer section "46.5 How to Generate Alerts Based on Endpoint URI Status" at below link -
http://download.oracle.com/docs/cd/E14571_01/doc.1111/e15867/endpointurimgmt.htm#i1080465
Also refer -
http://download.oracle.com/docs/cd/E14571_01/doc.1111/e15867/monitoring_ops.htm#i1108778
Please post OSB related questions in Oracle SOA Suite forum only -
SOA Suite
Regards,
Anuj

Monitoring IP SLA

Similar Messages

Maybe you are looking for