LMS 3.2.1 IPM collector
HI,
I have LMS 3.2.1 installed in my server. When I am try to create a new collector the expected source device is not appearing in list of devices source device list. However the device is added under IPM devices and reflecting under destination devices while trying to create teh collector. The device was appearing earlier but I deleted the device from common services and re added it. The device is also managed by other module like, DFM and RME.
Please help me.
Regards,
Satya
Thanks Afroj,
I have created the collectors in IPM. I had tried with all possible setting with device credentials in common services. Finally I found if the RW credential is left blank in common service device credential, the device does not appears as a source in IPM collector configuration. In initial condition we need to add a RW string in device and mention the same in common service device credential. Latter after creation of the collector if we remove the RW string then also it will continue to collect latency information from IP SLA and display it in graph.
Thanks for your kind support.
Similar Messages
-
IPM Collector - Scheduled Status -
I'm running LMS 3.2 w/ IPM 4.2.0 (10k license). I have been attempting to create various collectors, with some being fully successful, while others remain in a status of scheduled. They have been in this status for >24 hours. Any thoughts?
There might have been a problem configuring them on the source device in question. Alternatively, it may have been that they were schedule to run in the distant future. Delete one of these collectors, and try recreating it filtering on all SNMP traffic between the IPM server and the device. Post the capture file.
-
Facing problems in LMS 3.0.1 ( IPM not making graphs / visuals )
Yes. I think i am doing some mistake.
1. i have two switches. both are 6509.
2. i have configured snmp properly and can see them in rme and can do ssh also to them from cisco works
3. in ipm i try to pull reports i says "no data to poll "
4. i have tried configuring collector from source ip of loopback switch A and destination ip of loopback switch B. but when i try to take reports not coming,
5. Is there any document to refer to exact steps to generate reports, i think i am missing some step.
ALSO what configuration shall i do ( on switches to make this IPM generate graphs ).
i tried doing some configs on both switches as below (same on both) :
ip sla monitor 1
frequency 60
ip sla monitor schedule forever start now
and above snippet is same on both the boxes ????? what mistake have i done ? how to fix it and how to see the beautiful LATENCY graphs in IPM ????Thanks for the reply clarke...
\\herewith attached the screenshot of the error..unfortunately i left the site now...so other details I will be able to send it tomorrow only.. -
CiscoWorks IPM - collectors stuck in pending state
I have IPM 2.6 running on ciscoworks, the first collector i created as a test worked perfectly and started running immediately. Now when i've come to start the project proper to configure 400 collectors only 4 collectors show up. Cisco's recommended collectors per ipm server is 1000 so i'm well within the figure.
I even left it overnight thinking it might be database synching issues. Still can't find all the collectors, worst of all when i try to create new collectors it sees them as duplicates.
The source device is reachable and the ipm process is running, any pointers please?Hi
I also facing the same issues as you, User Entitlement Attestation process don't work.
Did you able to fix it now ?
Thanks in advanced
Thanks
John -
LMS 2.6 with IPM 2.6 integration ACS 4.1, problem with IPM
Hi
Recently I integrated ACS 4.1 with LMS 2.6 follow this document:
http://www.cisco.com/en/US/prod/collateral/netmgtsw/ps6504/ps6528/ps2425/prod_white_paper0900aecd80613f62.html
The integration was a partial success, because after the integration I cannot run IPM client and Reports. Just I don't have the icon to run this features.
Some of you know why is happen, and if there is a solution?
In accord with the document above, I check the integration and was everything how this doc says. But IPM give me this problem.
Thank you really much.
Best Regards Antonello.Thank you a lot Joe.
I wrongly thought that System Administrator has totally access.
Thank you really much, I rate you post.
Best Regards Antonello -
IPM and dynamic user tracking not running properly.
Hello, I've got two problems after a reinstallation of CiscoWorks LMS 3.2.
Versions of software components:
LMS-3.2
Campus Manager-5.2.1
CiscoView-6.1.9
CiscoWorks Assistant-1.2.0
CiscoWorks Common Services-3.3.0
Device Fault Manager-3.2.0
Integration Utility-1.9.0
Internetwork Performance Monitor-4.2.0
LMS Portal-1.2.0
Resource Manager Essentials-4.3.0
First probelm I have sounds pretty much like this thread:
https://supportforums.cisco.com/message/3064784#3064784
Source device is a WS-C3560-8PC - 12.2(55)SE1 - C3560-IPSERVICESK9-M
I configured a IPM collector, if I have a look at the "Collector Management" the collector is running and I can also monitor the running collector.
But if I have a look at the running config of the switch, there is no ip sla collector configuration but I can see the ip sla statistics via the show command.
#sh ip sla configuration 135123
IP SLAs, Infrastructure Engine-II.
Entry number: 135123
Owner: ipm|XXXS1077
Tag: QA-Site1-Site2
Type of operation to perform: udp-jitter
Target address/Source address: target ip address/source ip address
Target port/Source port: 2000/0
Type Of Service parameter: 0xB8
Operation timeout (milliseconds): 5000
Codec Type: g729a
Codec Number Of Packets: 1000
Codec Packet Size: 32
Codec Interval (milliseconds): 20
Advantage Factor: 12
Verify data: No
Vrf Name:
Control Packets: enabled
Schedule:
Operation frequency (seconds): 60
Next Scheduled Start Time: Start Time already passed
Group Scheduled : FALSE
Randomly Scheduled : FALSE
Life (seconds): Forever
Entry Ageout (seconds): 3600
Recurring (Starting Everyday): FALSE
Status of entry (SNMP RowStatus): Active
Threshold (milliseconds): 5000
Distribution Statistics:
Number of statistic hours kept: 2
Number of statistic distribution buckets kept: 1
Statistic distribution interval (milliseconds): 20
Enhanced History:
#sh ip sla statistics
Round Trip Time (RTT) for Index 135123
Type of operation: jitter
Latest RTT: 45 ms
Latest operation start time: 14:36:31.759 MET Wed Mar 16 2011
Latest operation return code: OK
RTT Values
Number Of RTT: 1000
RTT Min/Avg/Max: 21/45/60 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
Jitter time milliseconds
Number of SD Jitter Samples: 999
Number of DS Jitter Samples: 999
Source to Destination Jitter Min/Avg/Max: 0/3/15 ms
Destination to Source Jitter Min/Avg/Max: 0/1/9 ms
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): 11
MOS score: 4.06
Number of successes: 18
Number of failures: 0
Operation time to live: Forever
#sh run all | include 135123
Any suggestions? Am I right?
The second problem is about the dynamic user tracking like these theads https://supportforums.cisco.com/message/3135881#3135881 or
https://supportforums.cisco.com/message/3195492#3195492
Access switches are configured properly, the configuration ran without any problems with the previous installation.
No changes done at the configuration, using the default trap listener port etc.
In the macuhic.log file I get entries like in the attached txt.
When I try to run a full Campus Manager Data Collection I get the following errormessage:
Failed to start acquisition: Construction of XML data required for UT is in progress.Please try after some time
Also any suggestions? Am I right, too?By default IP SLA collectors installed by IPM do not appear in the running configuration. If you want to install the collectors into the running configuration, then set the "Copy IPSLA Configuration to running-config" property under IPM > Admin > Application Settings, then delete and recreate the collector.
Your Campus problem could be CSCtd49439 (a patch is available by contacting TAC). However, you should start a new thread for your Campus problem. -
IPM 4.2.0 and icmp-echo 0.0.0.0 problem
Hi,
I'm having a problem with IPM.
We are running LMS 3.2 with IPM 4.2.0.
I used IPM to configure a device to perform a ping to an ad-hoc target, the source router was configured as:
ip sla 182611
icmp-echo 0.0.0.0
request-data-size 64
owner ipm|<name>
tag <tag>
ip sla schedule 182611life forever start-time now ageout 3600
The target device is an ad-hoc with an ip-address but the IP SLA job ends up as 0.0.0.0.
When I'm running 'show ip sla statistics' it shows that the ping are timed out (as they are being sent to 0.0.0.0 instead of the real IP address).
The source router is running:
Cisco IOS Software, 3800 Software (C3825-ADVSECURITYK9-M), Version 12.4(22)T, RELEASE SOFTWARE (fc1)
Anyone had familiar problems?
Thanks,
Amitjclarke wrote:I haven't seen this before. Can you redo the configuration, and collect a sniffer trace of SNMP traffic between the IPM server and the device? This will help determine if the problem is with IPM or IOS.
Hi,
My IPM is running on Solaris 10.
Can you advise what/how I can sniff the SNMP traffic between the server and the IOS device?
Here is more information from the device:
#show version
Cisco IOS Software, C3550
Software (C3550-IPSERVICESK9-M), Version 12.2(46)SE, RELEASE SOFTWARE
(fc2)
#show running-config | inc 154366
ip sla 154366
ip sla schedule 154366 life forever start-time now ageout 3600ip sla reaction-configuration 154366 react timeout threshold-type immediate action-type trapOnly
ip sla reaction-configuration 154366 react rtt threshold-value 4000 3000 threshold-type consecutive 2 action-type trapOnly
35PROB#show ip sla configuration 154366
IP SLAs, Infrastructure Engine-II.
Entry number: 154366Owner: ipm|unix107776a44Tag: 35PROB_AMIT
Type of operation to perform: echoTarget address: 0.0.0.0
Source address: 0.0.0.0Request size (ARR data portion): 64
Operation timeout (milliseconds): 5000Type Of Service parameters: 0x0
Verify data: NoVrf Name:
Schedule: Operation frequency (seconds): 60
Next Scheduled Start Time: Start Time already passed Group Scheduled : FALSE
Randomly Scheduled : FALSE Life (seconds): Forever
Entry Ageout (seconds): 3600 Recurring (Starting Everyday): FALSE
Status of entry (SNMP RowStatus): ActiveThreshold (milliseconds): 4000
Distribution Statistics:
Number of statistic hours kept: 2 Number of statistic distribution buckets kept: 1
Statistic distribution interval (milliseconds): 20
History Statistics: Number of history Lives kept: 0
Number of history Buckets kept: 15 History Filter Type: None
Enhanced History:
Thanks -
Monitoring Cisco ASR 1002 with IOS-XE in IPM 4.2
We are running LMS 3.2 with IPM 4.2 installed....and we are looking to do IPSLA monitoring on a couple of our Cisco ASR's with IOS-XE code installed.
I looked at the IPSLA feature mapping and it only talks about supported IOS code....do we need to upgrade our current IPM module to a current version?Hi Konstantin,
Regarding "It is strange that these commands cleaned from sh run view.": this is normal for many default configuration commands.
Mine is a lab device so I cannot really comment on stability or provide you a recommendation based on that. However, I see that the download section from Cisco.com mentiones the following release as the recommended based on quality, stability and longevity:
asr1002x-universal.03.07.04a.S.152-4.S4a.SPA.bin
The best would be for you to check this with yor cisco Account Team or Advanced Services Team as normally they are the proper point of contacts for SW advisory.
Regards. -
LMS4.0/IPM: can't configure a dns collector
Hi,
Customer has lms 4.0 on windows.
He can't create a dns collector on IPM :
When we look at config device, device supports dns collector:
device_name #sho ip sla mon app
IP Service Level Agreement Monitor
Version: Round Trip Time MIB 2.2.0, Infrastructure Engine-II
Time of last change in whole IP SLA Monitor: 10:50:17.069 METDST Wed Apr 20 2011
Estimated system max number of entries: 30321
Estimated number of configurable operations: 30320
Number of Entries configured : 1
Number of active Entries : 0
Number of pending Entries : 0
Number of inactive Entries : 1
Supported Operation Types
Type of Operation to Perform: dhcp
Type of Operation to Perform: dns
Type of Operation to Perform: echo
Type of Operation to Perform: frameRelay
Type of Operation to Perform: ftp
Type of Operation to Perform: http
Type of Operation to Perform: jitter
Type of Operation to Perform: pathEcho
Type of Operation to Perform: pathJitter
Type of Operation to Perform: slm atm interface
Type of Operation to Perform: slm atm pvc
Type of Operation to Perform: slm controller
Type of Operation to Perform: slm frame-relay interface
Type of Operation to Perform: slm frame-relay pvc
Type of Operation to Perform: slm interface
Type of Operation to Perform: tcpConnect
Type of Operation to Perform: udpEcho
Type of Operation to Perform: voip
IP SLA Monitor low memory water mark: 41392015
Many thanks for your help,
ElisabethThere is no default DNS operation because a DNS operation requires one to specify the DNS server. Before DNS will show up in the create collectors interface, you must create a new DNS operation under Monitor > Performance Settings > IPSLA > Operations.
-
Traps from IPM in LMS 4.0
Hi, in LMS 4.0, is it possible to send traps from IPM? I remember that this was impossible from LMS 3.x.
Thanks.Yes.
Create it under the "operation" section. Monitor -> Performance Settings -> IP SLA -> operation, then apply to a collector. -
IPSLA/Perfromance/IPM: syslog message on collector down/failed
Dears,
Customer is upgrading from ciscoworks SNMS and they feel they loose a lot of valuable info.
They now have a few maps that give an at a glace state of the network. There is little I can do in LMS 4.1 to cover that.
The main problem for now is alerting on a host that runs a service like smtp, dns, etc and some hosts that should be pingable.
I'm trying to configure a collector on "IPM/ IPSLA/Performance" to run tests like echo, smtp and dns from a few central devices.
I think a IPSLA device it is capable to send syslog messages when the collector action 'fails' right?
Does anyone know what these messages look like?
I'd like to generate an alert using the syslog automated actions so I need to know what I can expect, provided my asumptions are correct.
Cheers,
MichelI am amazed.
When I use LMS to configure the devices to send IPSLA SYSLOG it configures ..... traps!
"IP SLA jobs for syslog configuration"
rtr logging traps
ip sla logging traps
ip sla monitor logging traps
I found this other thread https://supportforums.cisco.com/thread/176841
It seems what is being said in LMS help and on cisco.com is perhaps somewhat misleading.
It can send traps not syslogs.
Now looking at the helpfile I get the impression someone is confused about syslog and traps
"IPSLA Syslog Configuration
Syslog is a trap message that is sent from the device if any changes occur to the device. You can either enable or disable the IPSLA Syslog. However the IPSLA Syslog can be configured only by a Network Administrator or System Administrator.
The Device Selector will display only the Source devices that are IPSLA enabled. It does not display any Target devices.
To enable or disable IPSLA Syslog: "
A SYSLOG message is not a trap message!.
Can someone shed some light on this?
Can I get LMS to act upon a failing collector? -
Icmp Jitter collector configuration with Cisco LMS
Hi,
I am trying to collect jitter information of cisco Routers which are added in Cisco LMS
I have configured collector icmp jitter for them but somehow no stats are visible in lms and its says in IPM that u have no jitter collectors configured.
Do i need to enable anything on the Router as well to export stats to LMS ?
ThanksHi,
show ip sla application
IP Service Level Agreements
Version: Round Trip Time MIB 2.2.0, Infrastructure Engine-II
Time of last change in whole IP SLAs: *07:35:21.730 UTC Thu Mar 13 2014
Estimated system max number of entries: 27977
Estimated number of configurable operations: 27976
Number of Entries configured : 1
Number of active Entries : 1
Number of pending Entries : 0
Number of inactive Entries : 0
Supported Operation Types
Type of Operation to Perform: dhcp
Type of Operation to Perform: dns
Type of Operation to Perform: echo
Type of Operation to Perform: frameRelay
Type of Operation to Perform: ftp
Type of Operation to Perform: http
Type of Operation to Perform: icmpJitter
Type of Operation to Perform: jitter
Type of Operation to Perform: pathEcho
Type of Operation to Perform: pathJitter
Type of Operation to Perform: slm controller
Type of Operation to Perform: slm frame-relay interface
Type of Operation to Perform: slm frame-relay pvc
Type of Operation to Perform: slm interface
Type of Operation to Perform: tcpConnect
Type of Operation to Perform: udpEcho
Type of Operation to Perform: voip
IP SLAs low memory water mark: 38288719
The device is a Cisco 1841 -
LMS 4.2 Syslog Collector doesn't work
Hi fellas,
I need a few help for my LMS 4.2, syslog collector on LMS doesnt working even service syslog collector running normaly and also i saw in syslog_info is working to collect syslog from all router but not show up in dashboard monitoring.
I have setting on every router to logging (ip address LMS) but on LMS no any syslog from router can collect.
if you was face problem same with me or know how to solved this issue please share to me
i did a selftest from LMS there are all PASS except nslookup fail, it is has relation with syslog not show up on dashboard??Hi ngoldwat,
thanks for concern my issue.
there are packet capture syslog_info that i get :
May 2 19:07:29 10.29.246.47 62893: 161406: May 2 12:01:57.134 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Speak -> Standby
May 2 19:08:23 10.29.246.47 62894: 161407: May 2 12:02:51.170 UTC: %TRACKING-5-STATE: 10 ip sla 10 reachability Down->Up
May 2 19:08:23 10.29.246.47 62895: 161408: May 2 12:02:51.174 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Standby -> Active
May 3 16:42:28 10.29.246.47 62897: 161410: May 3 09:36:54.806 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Active -> Speak
May 3 16:42:28 10.29.246.47 62896: 161409: May 3 09:36:54.774 UTC: %TRACKING-5-STATE: 10 ip sla 10 reachability Up->Down
May 3 16:42:28 10.29.246.47 62898: 161411: May 3 09:36:55.750 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Speak -> Standby
May 3 16:43:23 10.29.246.47 62899: 161412: May 3 09:37:49.846 UTC: %TRACKING-5-STATE: 10 ip sla 10 reachability Down->Up
May 3 16:43:23 10.29.246.47 62900: 161413: May 3 09:37:50.018 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Standby -> Active
May 3 16:54:59 10.29.246.47 62902: 161415: May 3 09:49:27.031 UTC: %BGP-3-NOTIFICATION: sent to neighbor 10.29.252.85 4/0 (hold time expired) 0 bytes
May 3 16:54:59 10.29.246.47 62901: 161414: May 3 09:49:27.031 UTC: %BGP-5-ADJCHANGE: neighbor 10.29.252.85 Down BGP Notification sent
May 3 16:55:29 10.29.246.47 62904: 161417: May 3 09:49:55.731 UTC: %TRACKING-5-STATE: 10 ip sla 10 reachability Up->Down
May 3 16:55:29 10.29.246.47 62905: 161418: May 3 09:49:55.923 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Active -> Speak
May 3 16:55:30 10.29.246.47 62906: 161419: May 3 09:49:56.803 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Speak -> Standby
May 3 16:57:12 10.29.246.47 62907: 161420: May 3 09:51:38.859 UTC: %BGP-5-ADJCHANGE: neighbor 10.29.252.85 Up
May 3 16:57:24 10.29.246.47 62908: 161421: May 3 09:51:50.875 UTC: %TRACKING-5-STATE: 10 ip sla 10 reachability Down->Up
May 3 16:57:24 10.29.246.47 62909: 161422: May 3 09:51:50.891 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Standby -> Active
May 6 07:57:31 10.29.246.47 62910: 161423: May 6 00:51:53.214 UTC: %TRACKING-5-STATE: 10 ip sla 10 reachability Up->Down
May 6 07:57:31 10.29.246.47 62911: 161424: May 6 00:51:53.274 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Active -> Speak
May 6 07:57:31 10.29.246.47 62912: 161425: May 6 00:51:54.122 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Speak -> Standby
May 6 07:58:26 10.29.246.47 62913: 161426: May 6 00:52:48.291 UTC: %TRACKING-5-STATE: 10 ip sla 10 reachability Down->Up
May 6 07:58:26 10.29.246.47 62914: 161427: May 6 00:52:48.319 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Standby -> Active
May 6 08:04:32 10.29.246.47 62915: 161428: May 6 00:58:53.743 UTC: %TRACKING-5-STATE: 10 ip sla 10 reachability Up->Down
May 6 08:04:32 10.29.246.47 62916: 161429: May 6 00:58:53.867 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Active -> Speak
May 6 08:04:33 10.29.246.47 62917: 161430: May 6 00:58:54.747 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Speak -> Standby
May 6 08:05:27 10.29.246.47 62919: 161432: May 6 00:59:49.043 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Standby -> Active
May 6 08:05:27 10.29.246.47 62918: 161431: May 6 00:59:48.819 UTC: %TRACKING-5-STATE: 10 ip sla 10 reachability Down->Up
May 6 10:59:36 10.29.246.47 62921: 161434: May 6 03:53:56.510 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Active -> Speak
May 6 10:59:36 10.29.246.47 62920: 161433: May 6 03:53:56.466 UTC: %TRACKING-5-STATE: 10 ip sla 10 reachability Up->Down
May 6 10:59:36 10.29.246.47 62922: 161435: May 6 03:53:57.422 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Speak -> Standby
May 6 11:00:30 10.29.246.47 62923: 161436: May 6 03:54:51.542 UTC: %TRACKING-5-STATE: 10 ip sla 10 reachability Down->Up
May 6 11:00:30 10.29.246.47 62924: 161437: May 6 03:54:51.562 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Standby -> Active
May 6 19:10:31 10.29.246.47 62925: 161438: May 6 12:04:52.034 UTC: %TRACKING-5-STATE: 10 ip sla 10 reachability Up->Down
May 6 19:10:31 10.29.246.47 62926: 161439: May 6 12:04:52.142 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Active -> Speak
May 6 19:10:32 10.29.246.47 62927: 161440: May 6 12:04:53.038 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Speak -> Standby
May 6 19:11:26 10.29.246.47 62928: 161441: May 6 12:05:47.110 UTC: %TRACKING-5-STATE: 10 ip sla 10 reachability Down->Up
May 6 19:11:26 10.29.246.47 62929: 161442: May 6 12:05:47.346 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Standby -> Active
May 6 19:21:32 10.29.246.47 62930: 161443: May 6 12:15:52.870 UTC: %TRACKING-5-STATE: 10 ip sla 10 reachability Up->Down
May 6 19:21:32 10.29.246.47 62931: 161444: May 6 12:15:52.970 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Active -> Speak
May 6 19:21:32 10.29.246.47 62932: 161445: May 6 12:15:53.818 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Speak -> Standby
May 6 19:22:27 10.29.246.47 62934: 161447: May 6 12:16:47.974 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Standby -> Active
May 6 19:22:27 10.29.246.47 62933: 161446: May 6 12:16:47.946 UTC: %TRACKING-5-STATE: 10 ip sla 10 reachability Down->Up
May 6 19:27:32 10.29.246.47 62935: 161448: May 6 12:21:53.326 UTC: %TRACKING-5-STATE: 10 ip sla 10 reachability Up->Down
May 6 19:27:32 10.29.246.47 62936: 161449: May 6 12:21:53.518 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Active -> Speak
May 6 19:27:33 10.29.246.47 62937: 161450: May 6 12:21:54.462 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Speak -> Standby
May 6 19:28:27 10.29.246.47 62938: 161451: May 6 12:22:48.402 UTC: %TRACKING-5-STATE: 10 ip sla 10 reachability Down->Up
May 6 19:28:27 10.29.246.47 62939: 161452: May 6 12:22:48.442 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Standby -> Active
May 7 15:46:37 10.29.246.47 62940: 161453: May 7 08:40:56.647 UTC: %TRACKING-5-STATE: 10 ip sla 10 reachability Up->Down
May 7 15:46:37 10.29.246.47 62941: 161454: May 7 08:40:56.679 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Active -> Speak
May 7 15:46:37 10.29.246.47 62942: 161455: May 7 08:40:57.575 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Speak -> Standby
May 7 15:47:32 10.29.246.47 62943: 161456: May 7 08:41:51.647 UTC: %TRACKING-5-STATE: 10 ip sla 10 reachability Down->Up
May 7 15:47:32 10.29.246.47 62944: 161457: May 7 08:41:51.659 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Standby -> Active
May 7 19:13:37 10.29.246.47 62945: 161458: May 7 12:07:56.576 UTC: %TRACKING-5-STATE: 10 ip sla 10 reachability Up->Down
May 7 19:13:37 10.29.246.47 62946: 161459: May 7 12:07:56.776 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Active -> Speak
May 7 19:13:38 10.29.246.47 62947: 161460: May 7 12:07:57.688 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Speak -> Standby
May 7 19:14:32 10.29.246.47 62948: 161461: May 7 12:08:51.652 UTC: %TRACKING-5-STATE: 10 ip sla 10 reachability Down->Up
May 7 19:14:32 10.29.246.47 62949: 161462: May 7 12:08:51.776 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Standby -> Active
May 8 12:23:38 10.29.246.47 62950: 161463: May 8 05:17:56.001 UTC: %TRACKING-5-STATE: 10 ip sla 10 reachability Up->Down
May 8 12:23:38 10.29.246.47 62952: 161465: May 8 05:17:56.877 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Speak -> Standby
May 8 12:23:38 10.29.246.47 62951: 161464: May 8 05:17:56.029 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Active -> Speak
May 8 12:24:33 10.29.246.47 62953: 161466: May 8 05:18:51.074 UTC: %TRACKING-5-STATE: 10 ip sla 10 reachability Down->Up
May 8 12:24:33 10.29.246.47 62954: 161467: May 8 05:18:51.126 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Standby -> Active
May 11 00:39:10 10.29.246.47 62955: 161468: May 10 17:33:23.758 UTC: %SYS-5-CONFIG_I: Configured from console by 1445000 on vty0 (10.132.17.17)
May 11 00:50:32 10.29.246.32 144502: 6296699: May 10 17:44:45.413 UTC: %SYS-5-CONFIG_I: Configured from console by 1445000 on vty0 (10.132.17.17)
May 11 00:52:24 10.29.246.21 305: 000307: May 10 17:46:36.954 UTC: %SYS-5-CONFIG_I: Configured from console by 1445000 on vty0 (10.132.17.17)
May 11 19:28:22 10.29.246.47 62956: 161469: May 11 12:22:34.195 UTC: %SYS-5-CONFIG_I: Configured from console by srte@m on vty0 (10.132.17.186)
May 11 19:28:27 10.29.246.32 144503: 6305725: May 11 12:22:39.494 UTC: %SYS-5-CONFIG_I: Configured from console by srte@m on vty0 (10.132.17.186)
May 11 19:28:56 10.29.246.21 306: 000308: May 11 12:23:08.019 UTC: %SYS-5-CONFIG_I: Configured from console by srte@m on vty0 (10.132.17.186)
May 11 19:38:21 10.29.246.47 62957: 161470: May 11 12:32:32.744 UTC: %SYS-5-CONFIG_I: Configured from console by 1445000 on vty0 (10.132.17.186)
May 11 19:38:25 10.29.246.32 144504: 6305806: May 11 12:32:37.346 UTC: %SYS-5-CONFIG_I: Configured from console by 1445000 on vty0 (10.132.17.186)
May 11 19:38:26 10.29.246.21 307: 000309: May 11 12:32:37.666 UTC: %SYS-5-CONFIG_I: Configured from console by 1445000 on vty0 (10.132.17.186)
May 11 19:51:41 10.29.246.47 62958: 161471: May 11 12:45:52.641 UTC: %SYS-5-CONFIG_I: Configured from console by 1445000 on vty0 (10.132.17.186)
May 11 19:51:54 10.29.246.32 144505: 6305911: May 11 12:46:06.395 UTC: %SYS-5-CONFIG_I: Configured from console by 1445000 on vty0 (10.132.17.186)
May 11 20:01:45 10.29.246.21 308: 000310: May 11 12:55:57.175 UTC: %SYS-5-CONFIG_I: Configured from console by 1445000 on vty0 (10.132.17.186)
May 13 09:17:48 10.29.246.47 62959: 161472: May 13 02:11:56.894 UTC: %TRACKING-5-STATE: 10 ip sla 10 reachability Up->Down
May 13 09:17:48 10.29.246.47 62960: 161473: May 13 02:11:57.034 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Active -> Speak
May 13 09:17:49 10.29.246.47 62961: 161474: May 13 02:11:57.962 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Speak -> Standby
May 13 09:18:43 10.29.246.47 62962: 161475: May 13 02:12:51.966 UTC: %TRACKING-5-STATE: 10 ip sla 10 reachability Down->Up
May 13 09:18:43 10.29.246.47 62963: 161476: May 13 02:12:52.046 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Standby -> Active
May 13 10:23:48 10.29.246.47 62966: 161479: May 13 03:17:57.681 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Speak -> Standby
May 13 10:23:48 10.29.246.47 62964: 161477: May 13 03:17:56.689 UTC: %TRACKING-5-STATE: 10 ip sla 10 reachability Up->Down
May 13 10:23:48 10.29.246.47 62965: 161478: May 13 03:17:56.801 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Active -> Speak
May 13 10:24:43 10.29.246.47 62967: 161480: May 13 03:18:51.689 UTC: %TRACKING-5-STATE: 10 ip sla 10 reachability Down->Up
May 13 10:24:43 10.29.246.47 62968: 161481: May 13 03:18:51.801 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Standby -> Active
May 13 16:23:00 10.29.246.32 144506: 6327510: May 13 09:17:08.851 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Standby -> Active
May 2 19:07:29 10.29.246.47 62893: 161406: May 2 12:01:57.134 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Speak -> Standby
May 2 19:08:23 10.29.246.47 62894: 161407: May 2 12:02:51.170 UTC: %TRACKING-5-STATE: 10 ip sla 10 reachability Down->Up
May 2 19:08:23 10.29.246.47 62895: 161408: May 2 12:02:51.174 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Standby -> Active
May 3 16:42:28 10.29.246.47 62897: 161410: May 3 09:36:54.806 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Active -> Speak
May 3 16:42:28 10.29.246.47 62896: 161409: May 3 09:36:54.774 UTC: %TRACKING-5-STATE: 10 ip sla 10 reachability Up->Down
May 3 16:42:28 10.29.246.47 62898: 161411: May 3 09:36:55.750 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Speak -> Standby
May 3 16:43:23 10.29.246.47 62899: 161412: May 3 09:37:49.846 UTC: %TRACKING-5-STATE: 10 ip sla 10 reachability Down->Up
May 3 16:43:23 10.29.246.47 62900: 161413: May 3 09:37:50.018 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Standby -> Active
May 3 16:54:59 10.29.246.47 62902: 161415: May 3 09:49:27.031 UTC: %BGP-3-NOTIFICATION: sent to neighbor 10.29.252.85 4/0 (hold time expired) 0 bytes
May 3 16:54:59 10.29.246.47 62901: 161414: May 3 09:49:27.031 UTC: %BGP-5-ADJCHANGE: neighbor 10.29.252.85 Down BGP Notification sent
May 3 16:55:29 10.29.246.47 62904: 161417: May 3 09:49:55.731 UTC: %TRACKING-5-STATE: 10 ip sla 10 reachability Up->Down
May 3 16:55:29 10.29.246.47 62905: 161418: May 3 09:49:55.923 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Active -> Speak
May 3 16:55:30 10.29.246.47 62906: 161419: May 3 09:49:56.803 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Speak -> Standby
May 3 16:57:12 10.29.246.47 62907: 161420: May 3 09:51:38.859 UTC: %BGP-5-ADJCHANGE: neighbor 10.29.252.85 Up
May 3 16:57:24 10.29.246.47 62908: 161421: May 3 09:51:50.875 UTC: %TRACKING-5-STATE: 10 ip sla 10 reachability Down->Up
May 3 16:57:24 10.29.246.47 62909: 161422: May 3 09:51:50.891 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Standby -> Active
May 6 07:57:31 10.29.246.47 62910: 161423: May 6 00:51:53.214 UTC: %TRACKING-5-STATE: 10 ip sla 10 reachability Up->Down
May 6 07:57:31 10.29.246.47 62911: 161424: May 6 00:51:53.274 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Active -> Speak
May 6 07:57:31 10.29.246.47 62912: 161425: May 6 00:51:54.122 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Speak -> Standby
May 6 07:58:26 10.29.246.47 62913: 161426: May 6 00:52:48.291 UTC: %TRACKING-5-STATE: 10 ip sla 10 reachability Down->Up
May 6 07:58:26 10.29.246.47 62914: 161427: May 6 00:52:48.319 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Standby -> Active
May 6 08:04:32 10.29.246.47 62915: 161428: May 6 00:58:53.743 UTC: %TRACKING-5-STATE: 10 ip sla 10 reachability Up->Down
May 6 08:04:32 10.29.246.47 62916: 161429: May 6 00:58:53.867 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Active -> Speak
May 6 08:04:33 10.29.246.47 62917: 161430: May 6 00:58:54.747 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Speak -> Standby
May 6 08:05:27 10.29.246.47 62919: 161432: May 6 00:59:49.043 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Standby -> Active
May 6 08:05:27 10.29.246.47 62918: 161431: May 6 00:59:48.819 UTC: %TRACKING-5-STATE: 10 ip sla 10 reachability Down->Up
May 6 10:59:36 10.29.246.47 62921: 161434: May 6 03:53:56.510 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Active -> Speak
May 6 10:59:36 10.29.246.47 62920: 161433: May 6 03:53:56.466 UTC: %TRACKING-5-STATE: 10 ip sla 10 reachability Up->Down
May 6 10:59:36 10.29.246.47 62922: 161435: May 6 03:53:57.422 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Speak -> Standby
May 6 11:00:30 10.29.246.47 62923: 161436: May 6 03:54:51.542 UTC: %TRACKING-5-STATE: 10 ip sla 10 reachability Down->Up
May 6 11:00:30 10.29.246.47 62924: 161437: May 6 03:54:51.562 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Standby -> Active
May 6 19:10:31 10.29.246.47 62925: 161438: May 6 12:04:52.034 UTC: %TRACKING-5-STATE: 10 ip sla 10 reachability Up->Down
May 6 19:10:31 10.29.246.47 62926: 161439: May 6 12:04:52.142 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Active -> Speak
May 6 19:10:32 10.29.246.47 62927: 161440: May 6 12:04:53.038 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Speak -> Standby
May 6 19:11:26 10.29.246.47 62928: 161441: May 6 12:05:47.110 UTC: %TRACKING-5-STATE: 10 ip sla 10 reachability Down->Up
May 6 19:11:26 10.29.246.47 62929: 161442: May 6 12:05:47.346 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Standby -> Active
May 6 19:21:32 10.29.246.47 62930: 161443: May 6 12:15:52.870 UTC: %TRACKING-5-STATE: 10 ip sla 10 reachability Up->Down
May 6 19:21:32 10.29.246.47 62931: 161444: May 6 12:15:52.970 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Active -> Speak
May 6 19:21:32 10.29.246.47 62932: 161445: May 6 12:15:53.818 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Speak -> Standby
May 6 19:22:27 10.29.246.47 62934: 161447: May 6 12:16:47.974 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Standby -> Active
May 6 19:22:27 10.29.246.47 62933: 161446: May 6 12:16:47.946 UTC: %TRACKING-5-STATE: 10 ip sla 10 reachability Down->Up
May 6 19:27:32 10.29.246.47 62935: 161448: May 6 12:21:53.326 UTC: %TRACKING-5-STATE: 10 ip sla 10 reachability Up->Down
May 6 19:27:32 10.29.246.47 62936: 161449: May 6 12:21:53.518 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Active -> Speak
May 6 19:27:33 10.29.246.47 62937: 161450: May 6 12:21:54.462 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Speak -> Standby
May 6 19:28:27 10.29.246.47 62938: 161451: May 6 12:22:48.402 UTC: %TRACKING-5-STATE: 10 ip sla 10 reachability Down->Up
May 6 19:28:27 10.29.246.47 62939: 161452: May 6 12:22:48.442 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Standby -> Active
May 7 15:46:37 10.29.246.47 62940: 161453: May 7 08:40:56.647 UTC: %TRACKING-5-STATE: 10 ip sla 10 reachability Up->Down
May 7 15:46:37 10.29.246.47 62941: 161454: May 7 08:40:56.679 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Active -> Speak
May 7 15:46:37 10.29.246.47 62942: 161455: May 7 08:40:57.575 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Speak -> Standby
May 7 15:47:32 10.29.246.47 62943: 161456: May 7 08:41:51.647 UTC: %TRACKING-5-STATE: 10 ip sla 10 reachability Down->Up
May 7 15:47:32 10.29.246.47 62944: 161457: May 7 08:41:51.659 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Standby -> Active
May 7 19:13:37 10.29.246.47 62945: 161458: May 7 12:07:56.576 UTC: %TRACKING-5-STATE: 10 ip sla 10 reachability Up->Down
May 7 19:13:37 10.29.246.47 62946: 161459: May 7 12:07:56.776 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Active -> Speak
May 7 19:13:38 10.29.246.47 62947: 161460: May 7 12:07:57.688 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Speak -> Standby
May 7 19:14:32 10.29.246.47 62948: 161461: May 7 12:08:51.652 UTC: %TRACKING-5-STATE: 10 ip sla 10 reachability Down->Up
May 7 19:14:32 10.29.246.47 62949: 161462: May 7 12:08:51.776 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Standby -> Active
May 8 12:23:38 10.29.246.47 62950: 161463: May 8 05:17:56.001 UTC: %TRACKING-5-STATE: 10 ip sla 10 reachability Up->Down
May 8 12:23:38 10.29.246.47 62952: 161465: May 8 05:17:56.877 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Speak -> Standby
May 8 12:23:38 10.29.246.47 62951: 161464: May 8 05:17:56.029 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Active -> Speak
May 8 12:24:33 10.29.246.47 62953: 161466: May 8 05:18:51.074 UTC: %TRACKING-5-STATE: 10 ip sla 10 reachability Down->Up
May 8 12:24:33 10.29.246.47 62954: 161467: May 8 05:18:51.126 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Standby -> Active
May 11 00:39:10 10.29.246.47 62955: 161468: May 10 17:33:23.758 UTC: %SYS-5-CONFIG_I: Configured from console by 1445000 on vty0 (10.132.17.17)
May 11 00:50:32 10.29.246.32 144502: 6296699: May 10 17:44:45.413 UTC: %SYS-5-CONFIG_I: Configured from console by 1445000 on vty0 (10.132.17.17)
May 11 00:52:24 10.29.246.21 305: 000307: May 10 17:46:36.954 UTC: %SYS-5-CONFIG_I: Configured from console by 1445000 on vty0 (10.132.17.17)
May 11 19:28:22 10.29.246.47 62956: 161469: May 11 12:22:34.195 UTC: %SYS-5-CONFIG_I: Configured from console by srte@m on vty0 (10.132.17.186)
May 11 19:28:27 10.29.246.32 144503: 6305725: May 11 12:22:39.494 UTC: %SYS-5-CONFIG_I: Configured from console by srte@m on vty0 (10.132.17.186)
May 11 19:28:56 10.29.246.21 306: 000308: May 11 12:23:08.019 UTC: %SYS-5-CONFIG_I: Configured from console by srte@m on vty0 (10.132.17.186)
May 11 19:38:21 10.29.246.47 62957: 161470: May 11 12:32:32.744 UTC: %SYS-5-CONFIG_I: Configured from console by 1445000 on vty0 (10.132.17.186)
May 11 19:38:25 10.29.246.32 144504: 6305806: May 11 12:32:37.346 UTC: %SYS-5-CONFIG_I: Configured from console by 1445000 on vty0 (10.132.17.186)
May 11 19:38:26 10.29.246.21 307: 000309: May 11 12:32:37.666 UTC: %SYS-5-CONFIG_I: Configured from console by 1445000 on vty0 (10.132.17.186)
May 11 19:51:41 10.29.246.47 62958: 161471: May 11 12:45:52.641 UTC: %SYS-5-CONFIG_I: Configured from console by 1445000 on vty0 (10.132.17.186)
May 11 19:51:54 10.29.246.32 144505: 6305911: May 11 12:46:06.395 UTC: %SYS-5-CONFIG_I: Configured from console by 1445000 on vty0 (10.132.17.186)
May 11 20:01:45 10.29.246.21 308: 000310: May 11 12:55:57.175 UTC: %SYS-5-CONFIG_I: Configured from console by 1445000 on vty0 (10.132.17.186)
May 13 09:17:48 10.29.246.47 62959: 161472: May 13 02:11:56.894 UTC: %TRACKING-5-STATE: 10 ip sla 10 reachability Up->Down
May 13 09:17:48 10.29.246.47 62960: 161473: May 13 02:11:57.034 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Active -> Speak
May 13 09:17:49 10.29.246.47 62961: 161474: May 13 02:11:57.962 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Speak -> Standby
May 13 09:18:43 10.29.246.47 62962: 161475: May 13 02:12:51.966 UTC: %TRACKING-5-STATE: 10 ip sla 10 reachability Down->Up
May 13 09:18:43 10.29.246.47 62963: 161476: May 13 02:12:52.046 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Standby -> Active
May 13 10:23:48 10.29.246.47 62966: 161479: May 13 03:17:57.681 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Speak -> Standby
May 13 10:23:48 10.29.246.47 62964: 161477: May 13 03:17:56.689 UTC: %TRACKING-5-STATE: 10 ip sla 10 reachability Up->Down
May 13 10:23:48 10.29.246.47 62965: 161478: May 13 03:17:56.801 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Active -> Speak
May 13 10:24:43 10.29.246.47 62967: 161480: May 13 03:18:51.689 UTC: %TRACKING-5-STATE: 10 ip sla 10 reachability Down->Up
May 13 10:24:43 10.29.246.47 62968: 161481: May 13 03:18:51.801 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Standby -> Active
May 13 16:23:00 10.29.246.32 144506: 6327510: May 13 09:17:08.851 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Standby -> Active
May 13 16:23:55 10.29.246.32 144507: 6327524: May 13 09:18:03.847 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Active -> Speak
May 13 16:23:55 10.29.246.32 144508: 6327525: May 13 09:18:04.695 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Speak -> Standby
May 13 16:23:55 10.29.246.32 144507: 6327524: May 13 09:18:03.847 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Active -> Speak
May 13 16:23:55 10.29.246.32 144508: 6327525: May 13 09:18:04.695 UTC: %HSRP-5-STATECHANGE: GigabitEthernet0/2 Grp 10 state Speak -> Standby
i have Subscribed the service correct, you can see ss in my new upload
apparently the last captured syslog 13 May 2013 and not collecting again.
i will appreciate all suggest for this issue. -
LMS 4.2 – Missing messages in Remote Syslog Collector
Remote syslog Collector are dropping syslog messages - randomly. During analyzing we found out that syslog messages are stored in RSAC in file: /var/log/syslog_info
According to information from /etc/rsyslog.conf are the same syslog messages stored again in other files: /var/log/messages, /var/log/boot.log
In every file are missing the same messages. Load of RSAC and physical server is very low. When we send messages to more syslog servers (for example to other debian server in the same or different vlan) in the same physical server in vmware, we always receive every message.
We are using LMS 4.2.3 (Soft appliance) and for syslog messages RSAC 5.2 (linux in vmware). We receive approximately 200-300k syslog messages per day and RSAC drop approximately 100k.
Please what we have to change to receive all messages?
Why RSAC store the same messages more times?
Thanks
MilosI think this should change what you want - if not, revert it to the default:
for security, make a backup of the following file and open it in a text editor:
NMSROOT\MDC\tomcat\webapps\rme\WEB-INF\classes\com\cisco\nm\rmeng\csc\data\Collector.properties
change the following to a value that might fit your needs but be careful this can affect system performance:
QUEUE_CAPACITY=100000
save the file and restart the following syslog processes:
in a DOS box check the status of the following processes (they should be started) and restart them:
pdshow SyslogAnalyzer SyslogCollector
pdterm SyslogAnalyzer SyslogCollector
pdexec SyslogAnalyzer SyslogCollector
pdshow SyslogAnalyzer SyslogCollector
now, try to re-run your report. -
1. I configured ICMP jitter but its not working. Is there any specific ios requirement for icmp jitter. i have given ip sla responder
2. Is path jitter same as ICMP jitter.Hello,
perhaps your problem is related to my. With IPM (LMS 3.2) I have defined an operation of type http (IP of www.google.de). I have configured rtr thresholds to be send as SNMP traps to my network management system (HP NNMi 9.0). Setting up the collection ends up in Config Failed, but looking on the device (show rtr conf and show rtr oper) the probe is running and operations are successful. But looking at rtr reaction-configuration there are no entries. The configuration contains the "snmp-server host" and "snmp-server enable traps rtr" statements, but no SNMP trap is sent to NNMi (the output of "show snmp" shows, that the counter for SNMP traps sent is the same - even when the measurement is over threshold or the timeout value). When I change the operation in IPM to not use thresholding the collection ends up in Running (and I can use Monitor to see the operation results online). After searching the web I found this thread here:
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Normale Tabelle";
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:0cm 5.4pt 0cm 5.4pt;
mso-para-margin:0cm;
mso-para-margin-bottom:.0001pt;
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;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
https://supportforums.cisco.com/thread/173422?tstart=0&viewcondensed
Joe, could this be our problem?
Kind regards
Allessandro
Maybe you are looking for
-
Password no longer works after installing 4.0.3 !
Brand new Mac mini running 10.10.2. I downloaded the new OS X Server v 4.0.3 app and all installed fine.. I even created a share and transferred some test data okay... But my main login password on longer worked when I went to go access something in
-
How can i get the name of form object
hi can anybody tell me how we retrive the name of form on our webpage i try it document.form[0].name (i define a function in javascript for matching purpose and i want to get the form name in this function)
-
Anyone Buy the New 8 Core Machine? and Why Over Previous 8 Core ?
i know right now it's probably best to get a older 8 core, but what will it be that logic implements in their software that would make it worth spending the extra money for a new 8 core? 64 bit ? multi threading? and what specifically will the new ma
-
Ok, im still new to Mac's, and I cant figure out why I cant get Skype to download on my Macbook Pro. I go to te Skype website, click on the download option for Mac OS and it goes to another screen saying "download should begin shortly, if not click t
-
Transfering a file through Socket programming
Hi all, I want to return a file from server to client through a socket. I tried using ObjectOutput Stream where in I returned a java.io.File from server. But at client side when I say file.getLeangth() it comes as 0 and if I try to assign FileInputSt