IP SLA Proactive xofy bug

Hi All,
Has anyone came across this weird bug that when you configure ip sla in proactive with xofy, it will generate two syslog messages?
Here is how I am using it:
ip sla reaction-configuration 3 react rtt threshold-value 100 70 threshold-type xofy 2 5 action-type triggerOnly
Mar 5 10:27:06.976: %RTT-3-IPSLATHRESHOLD: IP SLAs(3): Threshold below for rtt
Mar 5 10:27:06.980: %RTT-3-IPSLATHRESHOLD: IP SLAs(3): Threshold below for rtt
And therefore, causing EEM to act twice ..which is a memory/cpu waste.
Mar 5 10:26:47.516: %SYS-5-CONFIG_I: Configured from console by vty1
Mar 5 10:26:47.620: %SYS-5-CONFIG_I: Configured from console by vty2
Using average or immediate works just fine.
One more thing ..i'm not sure if I understood 'average' , does it mean that if you have it configured for 5 attempts , you for example get a failure today, and the other day another 4 failures then it will trigger?
Here is my IOS:
Cisco IOS Software, 2800 Software (C2800NM-ADVENTERPRISEK9-M), Version 15.0(1)M
Thanks

The same results comes from c871 and c1811 too.
Cisco IOS Software, C870 Software (C870-ADVIPSERVICESK9-M), Version 12.4(15)T10, RELEASE SOFTWARE (fc3)
Cisco IOS Software, C181X Software (C181X-ADVIPSERVICESK9-M), Version 15.0(1)M, RELEASE SOFTWARE (fc2)

Similar Messages

Post-installation RAC maintenance

DB version ==> 10.2.0.4
OS ===> Solaris SPARC 5.10
For the last 7 months , i have been working in two RAC DBs (both of them are 2 node RACs). Apart from few instance restarts, i haven't actually done anything in these DBs because they have been very stable. Wish it wasn't because i never got to learn anything.
If you were asked what are the top 3 RAC maintenance tasks (apart from restarts), what would you say?

Hi,
Tasks of a DBA.
Initial and complete study of system
Continuous monitoring of database using advanced monitoring and alert tools
Routine health checks of database and proactive maintenance.
Regular database backups and validation of backups.
User and security management
Database growth planning and management.
Performance monitoring and periodic tuning.
Regular report on the activities performed and database health
Emergency support for production outages
Guaranteed response to production outages (based on SLA)
Proactive Maintenance
- Gather optimizer statistics
- Manage the Automatic Workload Repository
- Use the Automatic Database Diagnostic Monitor (ADDM)
- SQL Tuning Advisor: helps you to find critical or improvable statements
- SQL Access Advisor: gives you suggestion about possible indexes or materialized view that can improve performance of a statement or of a set of statements.
- Memory Advisor: controls SGA usage and performance
- MTTR Advisor: this checks checkpointing attivity, sintetically estimates MTTR. Check FAST_START_MTTR_TARGET parameter
- Segment Advisor
- Undo Advisor
- Set warning and critical alert thresholds
- You can define some baselines and on those baselines are based warning and critical thresholds.
Oracle Enterprise Manager Concepts gives an overview of what can be managed.
http://download.oracle.com/docs/cd/B19306_01/em.102/b31949/database_management.htm
Oracle RAC Monitoring: Keeping your RAC under control
http://www.databasejournal.com/features/oracle/article.php/3676451/Oracle-RAC-Monitoring-Keeping-your-RAC-under-control.htm
This has a lot of work.
Regards,
Levi Pereira

SCSM 2012: Strange Queue SLA Bug

We're in the process of scoping down our User Roles and I'm coming across a strange condition which I think might be a bug.
We have multiple teams within our organisation, each team has their own Support Group and SLA. We have created separate Queues and SLA's for each team.
For example:
Support Group = "Tier 1"
Queue (Tier 1) = All Incidents where Support Group equals "Tier 1"
SLO (Tier 1) = Is targeted at "Queue (Tier 1)"
This is what I've found, if I create a new User Role based on "Incident Resolver" and grant that Role access to to everything, that is tick the "All XYZ can be accessed" in each section of the wizard, the user can see the 'SLO Description',
'Target End Date' and 'Time before SLO Breached' in the incident form.
However, if I then limit this user role to 'Queue (Tier 1)' only, keeping everything else the same this information disappears from the view.
After some more investigation I found, if you select 'All work items can be accessed' under Queues this information shows, however if you tick a couple of individual queues manually or tick all of the queues manually you get this bug. It only works
when selecting 'All work items can be accessed'.
We might have to raise a case, quite difficult to explain on the forum. But wanted to post it in case others have come across this issue.

For the benefit of others I thought I'd update this post.
The solution to this problem can be found
here and
here.
Regards

BUG: Thunderbolt display audio at 32 samples is distorted

Found a bug and submitted case for distorted audio when routing a I/O buffer size of 32 samples in Logic Pro X to a thunderbolt display. Apple engineers have reproduced but no word on how or when it will be addressed. Engineers said it has nothing to do with any 3rd party drivers.
My first experience with Apple support and was really surprised there are no SLA's for known issues. Wondering how proactive the fix will addressed.

You're also transmitting a -lot- of video information, I'm sure video has priority.
It's not like a dedicated thunderbolt audio interface designed to be low latency.

E52 bug list for advanced users

I wanted to start the compilation of a bug list for advanced users. Here is my first suggestion:
1. SMS Functionality:
When trying to send SMS to a distribution list, the phone interface will ask you to choose between number and email addresses, even though the phone does understand that this is a SMS and not an email ("Text Message" appering on top)
This happens even when the contact has one phone number only (and an email address) in the phonebook
This does not happen when you use PC Suite to do the same task
2. Mail for Exchange client:
I will not go through the many -most already reported- bugs and general instability of the client. However, I will mention two that I have not seen reported anywhere so far:
When forwarding emails, only the header (From/To/Date/Subject) is forwarded. The rest of the text, as well as possible atachments are not forwarded. This is happening -to my epxerience- every time you try to forward an email
The client doesn't provide information (like the previous, installable client for devices such as E51, E71, etc.) as to when was the last time that sync took place, while it also doesn't show a real-time progress like the previous one. These two functionalities were very useful for controlling the Mail for Exchange process and understanding proactively if there was an issue. I consider these a must for any Business user (going through the log files to understand the same thing is obviously utterly impractical)
The client doesn't synchronise the "Deleted Items" folder from the mail server but only locally (which means it includes emails that were deleted only from the device itself).
The synchronization of the folders other than "Inbox" should be happening ad-hoc whenever the user is accessing these folders and requesting a sunchronization. Otherwise, we see the phenomenon of extremely lengthy synchronizations
3. Screen/Display:
It would be nice, when using the smallest font, to also accordingly compress the menu choices, in order to be able to fit more on the screen. Otherwise, with the present implementation, the fonts get smaller, but the relevant menu icons are not, resulting in an assymetrical look
4. Ovi suite:
As a general comment, I would like to mention that -apart from totally unknown NOKIA policy with regards to Ovi vis-a-vis PC Suite- it is not appropriate for Ovi to contain less functionality than PC Suite (I am referring to SMS presentation, etc.). In general, I find Ovi much clunkier and more clumsy than PC Suite which has actually evolved well over the years as the absolute PC phone tool (and still a differentiator for Nokia). So, NOKIA, please do not screw up PC Suite for something that may be "hype" accoridng to you, but is used as a tool by many of your customers.
5. Log:
As in previous phones/firmware versions, when setting the Log to 30 days, only 7 or ten days are actually retained. Maybe related to phone memory, but in any case it is a nuissance
6. SMS/VMs/Missed calls notifications:
This is not a bug, but at least personally, I preffered the way the SMS/VMs/Missed calls notifications were displayed in the previous devices (E51, etc.), just below the active stand-by applications "ribbon", instead of at the bottom of the screen. The new implementation makes it harder to access these items than before (at least for me)
I appeal to NOKIA to consider and fix these issues in the next firmware release(s).
Timos Tsokanis

@Timos , great compilation. I hope Nokia will work to resolve these quickly.
I have been using phone since last 2-3 days and find few things in Email client really annoying.
Also I want to understand few settings in Email client (version 2.1.0). They have made settings too complicated.
1)Any folder except Inbox doesn't show unread email count in brackets next to folder names.
i.e. If i delete or move 2 emails which I have not read to any folder(Deleted etc) , then deleted folder should be like Deleted(2). But right now it doesnt show anything. Strange.
I have checked with E72 and this bug is not there.
2) I have Gmail, Hotmail and Ovi mail as part of Nokia Messaging. But only Gmail and Hotmail actually show up when I open Messaging. All 3 show up if I open Email.
3)What does "Download Notification" under Global settings do? Notification icon control?
4) Why my Name field in Mailbox setting is picked from account at email.nokia.com, also even though secure connection is Yes under server settings in email.nokia.com, for same email its No in email client.
5) Why I am not allowed to change settings in "What to sync" , e.g. Hide email older than
6) what do settings "synchronise new updates" , "timed sync" do? No explaining in help.
7) Setting ->Gmail(or any other)->Account settings->Account Info, why number is blank? Also please make this work with destinations support. Also connectivity setting should be in global settings.
Best Regards,
Suyog

IP SLA Alert

Hi,
I have configured IP SLA to monitor the remote peer ip address sucessfully with icmp. Below is the configuration :-
ip sla 1
icmp-echo 192.168.10.1 source-interface Loopback1
timeout 1000
threshold 2
frequency 3
ip sla schedule 1 life forever start-time now
track 101 ip sla 1 reachability
IP SLA works fine. Now i want configure IP SLA in such a way that the failover happens only if there are 5 to 10 timeouts on the link and in such case there should be an alert generated via logging or snmp. Can any one help on this?

Hi Maxson,
Yes, its possible to configure the failover in such a way that it will happen only if there are 5 to 10 min timeouts on the link.
For this you have to define the track command and also defined the delay up time and down time. This delay up and delay down is the settings that will wait upto specific time before making changeover happen that will provide stability to your track and it will save the failover from flapping too much if there are slightly one or 2 ip sla operations failed event will expected in network.
So for example under track 101 ip sla 1 reachability command --> you can define delay up 3 down 10
This wlll change the failover happen only when the operation keep up for 3 seconds and and also make the failover happen when the ip sla operation will remain down for 10 seconds.
For more information and options, here is the reference guide for the same :-
http://www.cisco.com/en/US/docs/ios/ipapp/configuration/guide/ipapp_eot.html#wp1055209
Now the next part is to get an alert for the failover happen, you can configure trap like this
ip sla reaction-configuration 1 react timeout threshold-type immediate action-type trapOnly
The above command will generate the trap the moment threshold had been exceeded. There had been lot more trap that you can configure as per the requirements, kindly have a look at this nice document here :-
Configuring Proactive Threshold Monitoring of IP SLAs Operations
http://www.cisco.com/en/US/docs/ios/ipsla/configuration/guide/sla_threshold_mon.html
Many Thanks,
Gaganjeet Singh

IP SLA responder on Catalyst 2960S stacked

Hi
I have a pair of switches stacked:
Switch Ports Model                          SW Version          SW Image
     1    52      WS-C2960S-48FPS-L 15.0(1)SE             C2960S-UNIVERSALK9-M
*    2    52      WS-C2960S-48FPS-L 15.0(1)SE             C2960S-UNIVERSALK9-M
When I try to enable ip sla responder on the stack I get:
%SYS-3-HARIKARI: Process IP SLAs Responder top-level routine exited
I have been able to find a bug in the toolkit. Should ip sla responder be supported on the
stack as above?
Thanks
Lee Flight

I can confirm 15.0(1)SE3 still has the bug.
I just tested 15.0(2)SE3 released yesterday in a lab environment and....... (drum roll)..... no more HARIKARI . Hardware were two WS-C2960S-48FPS-L unstacked (one of them with installed stacking module though)
Haven't tried the earlier 15.0(2) (i.e. SE, SE1 and SE2) releases - maybe they work too.

IP SLA stats - one-way latency / MOS score 4.34 not updating

I'm trying to use Cisco IP SLA to bench mark voice traffic peformance before and after I apply QoS to the network.
* I've setup IP SLA in both directions over a DSL connection between a 7600, and an 1801
* I've setup IP SLA in both directions over an Ethernet WAN link between a 7200 and another 7200
ip sla 1
udp-jitter 10.101.1.1 32770 source-ip 10.101.2.1 source-port 32770 codec g711alaw
frequency 30
ip sla schedule 1 life forever start-time now
ip sla responder
I have a problem in that I'm not getting any meaningful data from the IP SLA statistics for Voice Score Values:, or any data for Latency one-way time: for any of my tests(x 4).
After a day of testing it seems the MOS score never changes from 4.34, and the ICPIF never changes from 1
Is there something wrong with my config? Is this working properly or could this be a bug?
ADSL-R1#show ip sla statistics 1 details
Round Trip Time (RTT) for       Index 1
        Latest RTT: 48 milliseconds
Latest operation start time: *09:27:48.435 UTC Thu Jul 5 2012
Latest operation return code: OK
Over thresholds occurred: FALSE
RTT Values:
        Number Of RTT: 999              RTT Min/Avg/Max: 45/48/89 milliseconds
Latency one-way time:
        Number of Latency one-way Samples: 0
        Source to Destination Latency one way Min/Avg/Max: 0/0/0 milliseconds
        Destination to Source Latency one way Min/Avg/Max: 0/0/0 milliseconds
        Source to Destination Latency one way Sum/Sum2: 0/0
        Destination to Source Latency one way Sum/Sum2: 0/0
Jitter Time:
        Number of Jitter Samples: 997
        Source to Destination Jitter Min/Avg/Max: 1/2/26 milliseconds
        Destination to Source Jitter Min/Avg/Max: 1/1/18 milliseconds
        Source to destination positive jitter Min/Avg/Max: 1/2/26 milliseconds
        Source to destination positive jitter Number/Sum/Sum2: 348/793/4295
        Source to destination negative jitter Min/Avg/Max: 1/2/16 milliseconds
        Source to destination negative jitter Number/Sum/Sum2: 346/802/3742
        Destination to Source positive jitter Min/Avg/Max: 1/1/18 milliseconds
        Destination to Source positive jitter Number/Sum/Sum2: 330/611/2051
        Destination to Source negative jitter Min/Avg/Max: 1/1/18 milliseconds
        Destination to Source negative jitter Number/Sum/Sum2: 318/606/1992
        Interarrival jitterout: 0       Interarrival jitterin: 0
Packet Loss Values:
        Loss Source to Destination: 0           Loss Destination to Source: 1
        Out Of Sequence: 0      Tail Drop: 0    Packet Late Arrival: 0
Voice Score Values:
        Calculated Planning Impairment Factor (ICPIF): 1
MOS score: 4.34
Number of successes: 72
Number of failures: 0
Operation time to live: Forever
Operational state of entry: Active
Last time this entry was reset: Never
7200-R2#show ip sla statistics details
Round Trip Time (RTT) for       Index 1
Type of operation: jitter
        Latest RTT: 6 ms
Latest operation start time: 08:08:31.349 UTC Thu Jul 5 2012
Latest operation return code: OK
RTT Values
        Number Of RTT: 1000
        RTT Min/Avg/Max: 2/6/199 ms
Latency one-way time milliseconds
        Number of Latency one-way Samples: 0
        Source to Destination Latency one way Min/Avg/Max: 0/0/0 ms
        Destination to Source Latency one way Min/Avg/Max: 0/0/0 ms
        Source to Destination Latency one way Sum/Sum2: 0/0
        Destination to Source Latency one way Sum/Sum2: 0/0
Jitter time milliseconds
        Number of SD Jitter Samples: 999
        Number of DS Jitter Samples: 999
        Source to Destination Jitter Min/Avg/Max: 0/2/13 ms
        Destination to Source Jitter Min/Avg/Max: 0/1/195 ms
        Source to destination positive jitter Min/Avg/Max: 1/1/13 ms
        Source to destination positive jitter Number/Sum/Sum2: 342/638/2142
        Source to destination negative jitter Min/Avg/Max: 1/1/11 ms
        Source to destination negative jitter Number/Sum/Sum2: 335/638/1886
        Destination to Source positive jitter Min/Avg/Max: 1/2/195 ms
        Destination to Source positive jitter Number/Sum/Sum2: 198/408/38510
        Destination to Source negative jitter Min/Avg/Max: 1/2/128 ms
        Destination to Source negative jitter Number/Sum/Sum2: 203/408/20720
        Interarrival jitterout: 0       Interarrival jitterin: 0
        Over thresholds occurred: FALSE
Packet Loss Values
        Loss Source to Destination: 0           Loss Destination to Source: 0
        Out Of Sequence: 0      Tail Drop: 0    Packet Late Arrival: 0
        Packet Skipped: 0
Voice Score Values
        Calculated Planning Impairment Factor (ICPIF): 1
MOS score: 4.34
Number of successes: 19
Number of failures: 0
Operation time to live: Forever
Operational state of entry: Active
Last time this entry was reset: 15:59:31.345 UTC Wed Jul 4 2012

Update (RESOVLED)
The MOS and ICPIF scores do change. I saturated the WAN link with FTP down/upload traffic inducing packet loss,increased jitter and delay. The scores degraded accordingling show ip sla statistics 10 details
R#show ip sla statistics 10
Round Trip Time (RTT) for       Index 10
Type of operation: jitter
        Latest RTT: 292 ms
Latest operation start time: 19:07:12.358 UTC Tue Jul 17 2012
Latest operation return code: OK
RTT Values
        Number Of RTT: 979
        RTT Min/Avg/Max: 58/292/487 ms
Latency one-way time milliseconds
        Number of Latency one-way Samples: 1
        Source to Destination Latency one way Min/Avg/Max: 1/1/1 ms
        Destination to Source Latency one way Min/Avg/Max: 112/112/112 ms
Jitter time milliseconds
        Number of SD Jitter Samples: 958
        Number of DS Jitter Samples: 958
        Source to Destination Jitter Min/Avg/Max: 0/1/6 ms
        Destination to Source Jitter Min/Avg/Max: 0/11/151 ms
Packet Loss Values
        Loss Source to Destination: 0           Loss Destination to Source: 21
        Out Of Sequence: 0      Tail Drop: 0
        Packet Late Arrival: 0 Packet Skipped: 0
Voice Score Values
        Calculated Planning Impairment Factor (ICPIF): 10
MOS score: 4.09
Number of successes: 32
Number of failures: 0
Operation time to live: Forever
        Source to Destination Latency one way Sum/Sum2: 9591/94681
        Destination to Source Latency one way Sum/Sum2: 346227/125286895
Jitter time milliseconds
        Number of SD Jitter Samples: 999
        Number of DS Jitter Samples: 999
        Source to Destination Jitter Min/Avg/Max: 0/2/11 ms
        Destination to Source Jitter Min/Avg/Max: 0/10/48 ms
        Source to destination positive jitter Min/Avg/Max: 1/2/11 ms
        Source to destination positive jitter Number/Sum/Sum2: 231/513/2789
        Source to destination negative jitter Min/Avg/Max: 1/2/10 ms
        Source to destination negative jitter Number/Sum/Sum2: 232/512/2724
        Destination to Source positive jitter Min/Avg/Max: 1/15/48 ms
        Destination to Source positive jitter Number/Sum/Sum2: 305/4762/93106
        Destination to Source negative jitter Min/Avg/Max: 1/6/42 ms
        Destination to Source negative jitter Number/Sum/Sum2: 682/4717/43395
        Interarrival jitterout: 0       Interarrival jitterin: 0
        Over thresholds occurred: FALSE
Packet Loss Values
        Loss Source to Destination: 0           Loss Destination to Source: 0
        Out Of Sequence: 0      Tail Drop: 0    Packet Late Arrival: 0
        Packet Skipped: 0
Voice Score Values
        Calculated Planning Impairment Factor (ICPIF): 5
MOS score: 4.24
Number of successes: 43
Number of failures: 0
Operation time to live: Forever
Operational state of entry: Active
Last time this entry was reset: 17:51:41.945 BST Fri Jul 20 2012

Jdeveloper 11g r2 bug

Hi i upgrade our project from jdev 11g r1 to r2, and we got this bug.
i create a view object, using sql:
select count(*) as pp from TABLE1
this sql is ok
when I click next, it popup this information:
cannot complete query to determin the view attributes.
Either the query is invalid or timeout occurs. Please
revise the query or create the view attributes manually.
Cursor 'jconnect_implicit_19' was declaed with a FOR UPDATE cluase. This cursor was found to be read only.
The sql is absolutely correct, it's very simple.
And our Database server is sybase ASE 12.5, we are now engaging in converting system from UNIFACE to web.
We're using SQL92 Builder/Generic selection.
There're many bugs there. can Jdeveloper support team make a dialect and Sybase SQL Builder Impl next service patch???
yes we know Oracle database is the best for choose, but the old system is using sybase, and there're lots of store procedure,
so we can not change DB very easily right now. forgive us, we just want a sybase sql builder implement from official, and thank you all again.

Hi Frank,
I have to say that posting the issues into support.oracle.com is not a guarantee that the problem is finally solved, at least on time. Currenty, I've 2 problems sent to support with two testcases (with the minimal code to repoduce the problem), both for Jdev 11.1.1.2.0 (SR# 3-1081284061 and 3-1074529551).
One of them is on "Support bug screening" state for 6 days, and the other has been completely ignored, we don't have even a confirmation from them about the testcase (now, for 13 days).
Just as a suggestion, I think it is worth for support to check the OTN to track possible bugs and improve the product in a proactive way, no just in a reactive way responding to our communications to support.
Best Regards,
Juanjo

Azure SQL DB Basic Edition Preview: "Session Request Limit Reached" Stuck and Doesn't Clear - SQL DB Bug?

Edit: I have updated the below to reflect that it took four hours for the database to unblock. This looks like a bug to me. SQL Server seemed to believe there were 30 running sessions with open requests nearly four hours after the client
side connections were terminated (and thus in the process blocking SQL Server from accepting new connections).
Problem
I am running a preview "Basic" edition SQL DB and have hit a problem with Azure SQL DB blocking database access for an extended time period.
I was running a test, which was running normally for several hours (loading small batches of data), then suddenly lots of connection timeouts (error type 1 below). My workload was constant over the whole test - but if the server was suddenly under
pressure, I accept this might happen - no problem with me so far.
Upon retrying, the errors then changed to request limit exceeded (error type 2 below).
I am surprised I hit the limit in the first place, since the test code closes the SQL Connection on a timeout error and reopens. (In C#, the code is wrapped in a using{} to ensure prompt connection closure). Still, perhaps the amount of concurrent
work on the server did momentarily hit this limit. Perhaps fair enough on this point too.
BUT: Surprisingly, nearly four hours later, I was still unable to connect to the database - it was refusing new connections. Either from my worker role or from the Azure Management Website. The Management Window, upon trying to connect,
failed with exactly the same text as error type 2 below.
Further, sys.resource_stats (from the master db, which is still accessible) is reporting that there were 30 active sessions, 30 active workers (see extract below) for four afters after the test ended. Even though during this time period the Azure Cloud
Service that was generating the SQL requests was stopped too (so the client side of any open requests were long since dead). Also,
the CPU, Log Write and Phys Data Read columns in sys.resource_stats are all showing 0 for the four hours after the test ended. This to me suggests a fault condition that isn't clearing server-side.
Why was the database unavailable for four hours? Why did Azure believe that there were 30 open requests? (each request was an insert of 1000 rows, each of 400 bytes, i.e. pretty small so no way should they take this long to process).
PS. To be clear, none of the above is a complaint. I completely accept that the service in in preview, different SLA, etc. I am writing to a) check that I haven't missed anything and b) if this is a bug, to report it.
Appendix
Error Type 1
System.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
Error Type 2
SqlException: Resource ID : 1. The request limit for the database is 30 and has been reached. See 'http://go.microsoft.com/fwlink/?LinkId=267637' for assistance.
Metrics
The following is an extract from sys.resource_stats for the affected time period. SQL Server seems to wrongly believe/report that there are 30 pending requests between 6:20 and 10:45. It thus blocks any further requests during this time. There
were NO client connections during this time, either new or previously opened.
start time
end time
sku
session count
worker count
avg cpu
avg phys data read
avg log write
07 Jun 11:15
07 Jun 11:20
Basic
0
0
0
0
0
07 Jun 10:50
07 Jun 10:55
Basic
0
0
0.5
0
0
07 Jun 10:40
07 Jun 10:45
Basic
30
30
0.01
0
0
07 Jun 09:35
07 Jun 09:40
Basic
30
30
0.02
0
0
07 Jun 09:20
07 Jun 09:25
Basic
30
30
0
0
0
07 Jun 09:10
07 Jun 09:15
Basic
30
30
0.01
0
0
07 Jun 08:40
07 Jun 08:45
Basic
30
30
0
0
0
07 Jun 08:20
07 Jun 08:25
Basic
30
30
0.01
0
0
07 Jun 08:10
07 Jun 08:15
Basic
30
30
0.01
0
0
07 Jun 07:55
07 Jun 08:00
Basic
30
30
0
0
0
07 Jun 07:25
07 Jun 07:30
Basic
30
30
0.01
0
0
07 Jun 07:15
07 Jun 07:20
Basic
30
30
0
0
0
07 Jun 07:05
07 Jun 07:10
Basic
30
30
0.01
0
0
07 Jun 06:55
07 Jun 07:00
Basic
30
30
0
0
0
07 Jun 06:45
07 Jun 06:50
Basic
30
30
0.15
0
0
07 Jun 06:20
07 Jun 06:25
Basic
30
30
0.01
0
0
07 Jun 06:15
07 Jun 06:20
Basic
30
30
0.22
0
0
07 Jun 06:10
07 Jun 06:15
Basic
26
26
0.13
0
0
07 Jun 06:05
07 Jun 06:10
Basic
20
20
0.14
0
0
07 Jun 06:00
07 Jun 06:05
Basic
13
13
0.12
0
0
07 Jun 05:55
07 Jun 06:00
Basic
7
7
0.12
0
0
07 Jun 05:50
07 Jun 05:55
Basic
1
1
54.04
0
93.47
07 Jun 05:45
07 Jun 05:50
Basic
1
0
1.4
0
2.06
07 Jun 05:40
07 Jun 05:45
Basic
1
1
55.17
0
88.35
07 Jun 05:35
07 Jun 05:40
Basic
1
0
52.05
0
90.01
07 Jun 05:30
07 Jun 05:35
Basic
1
1
54.95
0
90.1
07 Jun 05:25
07 Jun 05:30
Basic
1
1
56.38
0
89.82
07 Jun 05:20
07 Jun 05:25
Basic
1
0
52.15
0
90.19
07 Jun 05:15
07 Jun 05:20
Basic
1
0
52.76
0
87.86

Hi Chris,
Thanks for testing the new Basic edition and for reporting this issue. Without some more investigation it is hard to tell what exactly has happened here.
To be able to take a closer look I would need some more information from you. Could you please reach out to me via email (firstname DOT lastname AT microsoft DOT com)? I will then let you know what additional information we and will kick-off
the investigation.
Thanks,
Jan

Availability "SLA" report - wrong "Planned Maintance" for some servers

Just wondering if anybody knows of any bugs or perhaps what I am doing “wrong” here when I have created an availability “SLA” report
The report is the generic, availability and tagets a large group (1000) of SCOM health service watchers . Under downtime I am checking the options for “Planned Maintenance” and “Unplanned Maitenance”. When I run the report most seem correct – I spot
servers I know have been down and small amount of planned downtime for patching. However I
have bunch of servers (mabe 20) that all show pretty much 100% planned maintenance and all with the same odd uptime of say 4 hours exactly. I cant find anything common with these servers. I even removed the SCOM agent from one server, left
a litte while and re-installed and this still shows up in this fashion. Any ideas?
I am running SCOM2012 SP1 CU4
Many thanks

Hi,
It seems like that there are cache data for the agent, what is the result when we use report tasks under monitoring console for that specific server?
If the issue still there, then I would like to suggest you refer to the below blog, and follow the article to re-install the agent:
http://blogs.technet.com/b/kevinholman/archive/2009/10/01/fixing-troubled-agents.aspx
Regards,
Yan Li
Regards, Yan Li

Regarding " SLA "

Hello Guyz,
           What is SLA ?
           Where and Why is this concept used specifically.?
           Can anyone give me, the navigational steps how to follow this.
   Thanks adn Regards,
   Hawkin.

Hi ,
SLA are Service Level Agreements to resolve the tickets by the market.
SLA means Service Level agreement. It is the service agreement between a Company and a service provider. For example an IT Organization providing support of SAP / other software / hardware has a agreement. This can be for example categorized based on criticality of the incident. High priority incident has to be resolved on 10 hours. Medium priority incident has a 3 days time to resolve etc
Tickets:
Handling tickets is called Issue Tracking system. The errors or bugs forwarded by the end user to the support team are prioritized under three seviority High, Medium and Low. Each and every seviority as got its time limits before that we have to fix the error.
The main job of the supporting consultant is to provide assistance on line to the customer or the organisation where SAP is already implemented for which the person should be very strong in the subject and the process which are implemented in SAP at the client side to understand,to analyse,to actuate and to give the right solution in right time.This is the job of the support consultant.
The issues or the tickets(problems) which are arised is taken care of on priority basis by the support team consultants.
The work process in support projects are given below for your reference.
1. The customer or the end user logs a call through any tool or by mail (RADIX).
2. Each one of the support team is a part of support group.
3. Whenever a customer logs a call he /she has to mention to which work group (by name).
4. Once the calls came to the work group the support consultant or the team need to send an IR (Initial Response) to the user depending upon the priority of the calls. (Top,High,Med,Low,None)
5. Then the error is fixed, debugged by the support consultant or the team. Then after testing properly by generating TR(Transport Request through the basis admin)
6. Then it is informed to the end user/customer/super user about the changes which have moved to the production server by CTS process.
These are the process. In summary, what I understand is that if any configuration or customization is required to solve the issue, then the consultant have to work on DEV Client, then the end user will test it in the QA client and after approval the BASIS consultant has to transport it to the PRODUCTION client.
An example:
Tickets in SD can be considered as the problems which the end user or the employee in the company face while working on R/3. Tickets usually occur during the implementation or after theimplementation of the project. There can be numerous problem which can occur in the production support and a person who is working in the support has to resolve those tickets in the limited duration, every ticket has the particular deadline alert so your responsibility is to finish it before that deadline.
To begin with , we should give "TICKET" to you for not knowing it.
Here is an eg of a ticket raise:
End user is not able to
1. Create Sales order for a customer from a New plant , since shipping point determination is not happened . ( Without Shipping point the document becomes INCOMPLETE and he will not be able to proceed further like DELIVERY, BILLING).
He raises a ticket and the priority is set in one of the below:
1. Low 2. Medium 3. High.
Now you need to solve this ticket. You would analyze the problem and identify that the SP configuration has to be done for the new plant.
You would request a transport for DEV CLIENT to BASIS. You do the change and Request one more Transport to BASIS for QA client. The End user will test the same by creating a sales order for the new plant and approve it.
Finally, you request a transport to move the changes to PRODUCTION. Once the change is deployed in production the TICKET is closed. What I have given is a small example. You would get some real issues with severity HIGH in your day-day support.
assign pts if helpful..

CSCtg82170: ip sla target port changes to 1967

I've been impacted by this bug significantly. The sla's are used for gathering stats that populate a customer portal. The bug basically causes the sla to fail when the event occurs and there's no indication that it's occurred.
For no reason the target port changes to 1967 which is reserved for IP SLA control packets.
example:
ip sla 778482511
udp-jitter 10.197.197.253 15426 source-ip 192.168.15.254 num-packets 20 interval 300
vrf xxxxxx
owner xxx
tag AutoGenerated
frequency 300
ip sla schedule 778482511 life forever start-time now
becomes
ip sla 778482511
udp-jitter 10.197.197.253 1967 source-ip 192.168.15.254 num-packets 20 interval 300
vrf xxxxxx
owner xxx
tag AutoGenerated
frequency 300
ip sla schedule 778482511 life forever start-time now
It took quite some time to work out what was actually happening and some time on a Tac service request before it was acknowledge as a bug.
Below is a table indicating device counts for various platforms and images with the affected count at the bottom.
h/w           image            count
1841      12.4(15)T8                98
1841      12.4(7a)                     41
1941      15.1(1)T                1944
1941      15.1(1)T2                     3
1941      15.1(3)T3                   48
1941      15.1(4)M4                349
1941      15.2(1)T1                     3
1941      15.2(2)T                       2
2821      12.4(15)T9                   1
2821      12.4(2)T1                   21
2821      12.4(24)T2                 79
2951      15.2(1)T                     24
3845      12.4(24)T2                   6
2921/K9 15.1(2)T1                     2
2921/K9 15.2(1)T                     48
3750ME 12.1(14)AX2               2
3750ME 12.2(52)SE               59
Total 2730
Devices currently displaying the issue
1941      15.1(1)T           324
1941      15.1(3)T3             3
1941      15.1(4)M4           10
If you've been struck by this bug I know you'll be relieved that it's actually a bug and your not going insane :-)
We currently have extra monitoring/checking in order to get on top of the issue but a fix would be really great.

We're having a similar issue with icmp-echo in that our source-ip address changes quite frequently in the running config (7201 rtr). The destination ip also appears to change when viewing sh ip sla configuration but not in the running config. We're currently running 12.4(24)T1. Looks like we'll be doing an IOS upgrade in the near future...

Need to find all Bugs and QF created for 8.0.0.13

Hi all,
I kneed to know how to find all bugs and possibly patches/QF created on top of 8.0.0.13 for bugs found in 8.0.0.13 after its release on Jan 2012. This is for my Customer that needs to know if they have to plan some QF in proactive way.
I can access to Internal Support Portal, so if there is any place where Support people can go I can access.
Thank you in advance
Chiara Scarafiotti
ACS TAM

Hi radhika,,
This the the way to go..just modify the col according to your table col names...
You can do a CONNECT BY query without a START WITH clause to link every node with each of its ancestors.
Getting the total is just a matter of GROUP BY.
SELECT emp_id, employee_name, manager_id
, CASE
          WHEN COUNT (*) = 1
          THEN 0
          ELSE COUNT (*)
     END               AS cnt0
,     COUNT (*)      AS cnt1
FROM employee
CONNECT BY emp_id     = PRIOR          manager_id
GROUP BY emp_id, employee_name, manager_id
ORDER BY emp_id;
output:
Output:
. EMP_ID EMPLOYEE_N MANAGER_ID CNT0 CNT1
1 Mark 0 5 5
2 John 1 3 3
3 Stella 1 0 1
4 Karen 2 0 1
5 Andrea 2 0 1
I made this a bottom-up query (going from each node to its ancestors) rather that a top_down query (node to descendants) because you can't GROUP BY CONNECT_BY_ROOT.
In your description you implied that each node would be counted among its own descendants, but in the sample output you had 0, not 1, as the count for all the leaves, that is, managers counted as their own descendants, but non-managers did not. The column called count0 in the query above does that; the column count1 counts each node as its own descendant, leaves included.
Regards
Onenessboy

How to proactively get information on OIM/OIA latest patches

Is there a way for a customer to proactively get information on the latest patches (BP) available? Is there a document on MOS that maintains this information?
Thanks.
Edited by: user730871 on 9-Mar-2012 2:49 PM
Edited by: user730871 on 9-Mar-2012 2:49 PM

When you install/configure OIM you have the option of checking for updates automatically. I think that can automatically check for updates from the product itself. Although for that to work, you will have to allow access to oracle.com from your server. Another option would be to check the metalink notes periodically to see what's been out. There are specific notes which track for OIM9.x, OIM11.1.1.3x and then one for OIM11.1.1.5.x . I am not sure about OIA but there should be one as well.
Information And Bug Listing of Oracle Identity Manager Bundle Patches: 11.1.1.5.x (PS1) Version [ID 1360009.1]
Information And Bug Listing of Oracle Identity Manager Bundle Patches: 11.1.1.3.x (DW) Version [ID 1247564.1]
Information And Bug Listing of Oracle Identity Manager Bundle Patches: 9.1.0.2 [ID 881954.1]
-Bikash

IP SLA Proactive xofy bug

Similar Messages

Maybe you are looking for