WRT150N router crashing

Hello my router has been working fine up until this point and ive had no complaints however as of recently ive been working on hosting a SRCDS dedicated server on one of my PC's and after running the server for awhile (anywhere from 10-30 minutes) the router will lock up all internet connections wired and wireless and i have no connection. When this happens the linksys advisor tells me that a new router has been connected and wants to walk me through setup again but obviously its the same router. The only way to fix this is to unplug the router for about 5 seconds and plug it back in. Im wondering if their is a way to prevent the router from crashing like this as it would be impossible to host a server with router crashes every 30 minutes.
Thank you

Let me know who is your Internet Service Provider so that i can tell you few manual steps .....

Similar Messages

Connecting WCG200 or WRT150N Router w/ a Macbook Pro & iMac

I plan to buy either the WCG200 or WRT150N router (recommendations welcomed!) for use with Macbook Pro & iMac computers. Could someone please direct me to a set-up & configure guide? I assume this info is not included with the router. Thank you for your help.

Both routers come with a CD which contains the manual which explains the configuration interface of the router. You can also download the manual from the linksys support website. On the support website you'll also find articles how to setup the router in various scenarios.

Linksys WRT150N router

I have a Linksys WRT150N router. My OS is win XP pro. The Easy Link Advisor keeps telling me during setup that I am not connected to the Internet on my desk top computer. However my desktop is connected to the Internet as well as my wireless laptop both through the WRT150N router. I unstalled the Easy Link Advisor, cleaned the register of all Linksys keys and reinstalled the Easy Link Advisor. The installation is complete. The Easy Link Advisor is ready for the setup on my desk top computer. When I go through the setup process with my fire wall turned off the end result is that I am not connected to the internet. I know that I am and using the internet right now. Help!!!!!!
Solved!
Go to Solution.

Do not use the EasyLink Advisor to setup the router...Open the router setup page by typing 192.168.1.1 in the address bar.Now,configure the router.

My router crashes at the sight of my macbook.!! I have to keep them well separated

Hi
I live in France and have a Orange router for wifi with 2 laptops, my MacBook and a Sony Vaio.
The router crashes whenever I approach it with my Ipad Or Mac. It works fine. It hates Apple? I am constantly resetting. Both laptops state that there is an IP conflict. My mac is designed to adapt to that...?
Can you suggest action please? Merci

You may have to see if it is fairly easy to set up wireless by hardware identification number, commonly referred to as 'mac address' in DHCP in router server; which has nothing to do with Apple, as all hardware can use their ID to connect. Including printers so equipped. This is usually done by ethernet or wireless, and imparts a greater degree of security at your home base for those items you have. Is there something there that is repeating or re-sending the wireless signal, perhaps on the same frequency as the router? Channel numbers can be changed, for example, if there are two. But there are more complex things to consider if the matter is worse, and so far there is no explanation for this conflict. The MacBook and Sony should be able to use the same wireless router base station.
How is file sharing and internet sharing set up on these competing devices? This can be a place to look.
•Cascading router and DHCP conflicts?
http://www.tomshardware.com/forum/44038-42-cascading-router-dhcp-conflict
In an area a bit more complex, the matter of IP Conflict, this one when moving between wi-fi router and repeater, is among the more difficult: http://www.tomshardware.com/forum/38238-43-conflict-moving-wifi-router-wifi-repe ater This may not be what is happening with your competing wi-fi products, but that matter of settings, since you can share files, and also web connections through the Apple products. As an option.
Other router conflicts are noted, from a larger volume of search results:
http://www.tomshardware.com/forum/27902-43-router-conflict
Also, it may be a matter of choosing how the MacBook connects to the available wireless, and what those wireless settings are in the router, and if the MacBook shares an internet connect to another product, that could be a source of conflict if not set up correctly. Something may be seeing a third product as a competing source of a potential wi-fi connection to the internet, and it isn't.
Some of these things have a dynamic IP address (changes) and another could be using fixed IP addresses. The router 's should be fixed. All of mine are and I can use four Macs, or more PCs via an Apple branded wireless router.
There are several possibilities, and most difficult to guess at a distance. But the settings in each brand and item have to be looked into, as they all have the ability to be customized to fit certain working parameters.
Not sure if this helps any... at 2AM.
Good luck & happy computing!
edited.

Need Help w Collobos Fingerprint through a WRT150N Router

I would very much appreciate any expert advise I can get regarding using the Collobos Fingerprint software through my WRT150N router. I'm using Windows XP SP3 and immediatly after installing (which went extreamy well) it immediatly found and listed all of my home network printers. All of the wired and wireless windows based systems in my house can see and print to the printers without any problem. However, getting ANY of my apple devices (iPad, iPhone etc ) to print will not even show them as listed on the device when I select print on the devices. Collobos says that I have to make sure that Ports UDP 5353 doe Bonjour and TCP 6361 for FingerPrint need to be open both ways for it to work (http://collobos.uservoice.com/knowledgebase/articles/66995-required-ports).
I have no problem getting into the router settings and have set them up as stated above in Port Range Triggering and enabled. Also made sure Filter Multicast was not check marked in Security. Unfortunatly, that doesn't seem to work as I had hoped.
If anyone has this software up and printing through a LInksys router, I sure wouold appreciate knowing how you did it! Or any other ideas you experts may have.
Thank You all for reading and trying to help!
Mac

I want to thank the kind people that replied and spent a moment to try and help. I thought I might get more from this large forum full of so many experts.
I have been troubleshooting the problem with the very limited help files provided by the Program Collobos Fingerprint. The most important factor they failed to mention was that it is necessary to have a wired connection to the router. As soon as I connected the computer, (old laptop) that had their software installed, printing began immediately since I had already put in the settings they recommended.
FYI, the works very well even though the prints are large. Even if a photo is lets say 3"x5", it will print full page. I can print anything that the idevice application will prompt printing for. Have printed from our iPod, iPads, iPhone. Anyone else I have let into my home network which have iDevices can print also. My printers are not wifi nor Airprint capable. They are connected via an old HP Print Direct Parallel box with ethernet to the router. Never thought anything would work, but now am able to print everything.
I again want to thank the people that replied!
Forum Administrator, you can close and clear this thread since it will more than likely not be of any help to others.
Mac

Airport Express, Linksys WRT150N Router, Windows Vista - Scene Two

I hate to post again, but I am hoping someone can clue me in on what's going on with my Airport Express. This is my second post, as I thought it started working on its own the last time I posted, which was just three days ago.
I have read all over this dicussion group,and I think I've tried everything mentioned here, and under the sun. I have mine set up to JOIN my existing network only to let me play iTunes over my stereo.
Sunday I finally got my Airport Express to communicate with my computer. After an hour, I shut down my computer and went to bed.
Monday, I had to reset the Express to get it to start communicating again. Changed my Router to Channel 11
Tuesday, I had to reset the Express to get to start communicating again. But, it would cut in and out continuously. I changed my router settings again, and it started working.
Tonight, I turned on my computer, and the AE showed up as still being connected. I started to play iTunes over my stereo, and about 5 minutes later, it all stopped. I unplugged the AE to reset it, and it once again started working, and has been for about 15 minutes while I am typing this out.
Why does this small device cause so much trouble, and am I setting this up wrong? Here is how things are configured right now, and I am hoping someone can tell me what I've done, am doing, wrong.
Computer Details:
I have a Gateway FX530 running Windows Vista. I have set up a wireless network using a LinkSys WRT150N router which also shares my DSL connection. Using my laptop, the wireless system works great.
Linksys Wireless settings:
Wireless mode - bgn
Connection Type - dhcp
Radio Band - Wide 40 MHz channel ( I had to set it here for my laptop to work)
Wide Channel - 3
Standard Channel - 1 - 2.412 GHz.
(Monday it was working on Wide Channel 9, Std Channel 11)
Security Mode - WPA2
Encryption - TKIP or AES
Key Renewal 3600 Seconds
Beacon Interval - 100ms
DTIM Interval 1
Fragmentaion Threshold - 2346
RTS Threshold - 2347
Airport Express Settings:
IP Manually set to 192.168.0.104
Running version 7.3.1
Set to JOIN a Wireless Netowrk
Security WPA2 Personal
Channel: 1(Automatic)
Allow Ethernet clients is NOT checked.

Here is the absolute guaranteed way (that probably won't work for anyone else) to solve how to connect the Airport Express to a non Apple router to a non Apple computer. I will probably jinx myself upon hitting the Post Message button, but here goes.
Step 1: Spend countless hours trying to use the Utility to configure the device. This must be done over a course of 5 days. If you have small children, I would suggest doing this behind a closed door where all the swearing can go unheard.
Step 2: Read every possible thread here on the Discussions group trying every possible suggestion known to mankind.
Step 3: Post at least two threads yourself asking why nothing works. Mark the first thread as 'Answered' within 90 minutes of posting when the AE decides to work for longer than 5 minutes.
Step 4: On the 6th day, take the device back to the Apple store and have them verify the device actually works and that you are not going absolutely insane. Know that they will be testing this device from an Apple Computer thru an Apple router.
Step 5: Wait for the call, which you know is coming, that the device works perfectly for them, and that they can not find anything wrong at all.
Step 6: Feeling like all is lost, you retrieve the device from the Apple store and have the Tech person tell you 'Good Luck'. Yeah, that helps.
Step 7: Connect the device back to your system, program as required and connect to your stereo.
Step 8: Start up iTunes and enjoy endless hours of music.
Step 9: Now this is the crucial part. You sit and wonder WHY it all of a sudden starts working after you bring it in to 'be looked at'. You do exactly the same thing programming it as you did from the first 'out of box' scenerio, having changed nothing to the router settings that didn't work the last time before you brought it back to Apple Store.
Step 10: And in the spirt of the Apple Tech..... "Good Luck"

Can't find Network using a Linksys WUSB54G Wireless-G USB Adapter with a linksys WRT150N router????

Hello.....I just recently bought a linksys WRT150N router and am having problems connecting a computer that uses a Linksys WUSB54G Wireless-G USB Adapter. This computer's operating system is windows 2000 and it cannot find the network I setup.....Even when I double checked that the router was in mixed mode.....Can anybody help?

I am having a similar problem with my WUSB54GC adapter connecting to my WRT54G router 100 feet away with only a single stud wall in between. Sometimes the computer connects automatically and sometimes I have to restart windows or use the repair connection wizard to get the computer to connect. Using Windows XP and Mixed infrastructure network with SSID broadcasting disabled.
Message Edited by HOOfan_1 on 05-29-200709:03 PM

EA6500 Router crashes every Saturday during the night

Systematically the router crashes every Saturday night. Can it be the auto update "feature"?
When I wake up on Sunday I have to power cycle it to regain connectivity.
Solved!
Go to Solution.

Here you go, read through this post:
http://www.dd-wrt.com/phpBB2/viewtopic.php?t=162802
Start with Fractals build on page 5 then update to Brainslayer's latest build which you can find here:
http://www.dd-wrt.com/dd-wrtv2/down.php?path=downloads%2Fothers%2Feko%2FBrainSlayer-V24-preSP2%2F201...
The router database is outdated...
Good luck!

Router Crashing when ATM Interface under Heavier Load

Hi all,
Looking for a little guidance before I engage TAC (AKA, waiting for maintenance contract purchase approval). I have a 3945 router running IOS 15.1.2T5 with an ATM interface card and adapter. It is currently configured with a 30Mbps PVC. As it reaches about 20 to 21Mbps and 14000 packets per second, I start to see output drops on the interface, which I had previously attributed to a combination of ATM overhead + volume of traffic being pushed through it. About half of the traffic that passes through is VoIP, so it is a lot of smaller packets, which hurts on ATM overhead, if I recall correctly. Starting yesterday, though, the circuit peaked at 23Mbps and 17000 packets per second. About 5 minutes, later, the router crashed and rebooted itself. Crash info reports the following:
PCIe Interrupt - Root Complex 0
Last PCIe Read CFG Data = 0x81000030
Last PCIe Write CFG Data = 0x81000034
Last PCIe CFG Op: Write
PCIe Interrupt: Error Detect Reg = 0x80100000
PCIe Err Enable = 0xBC8000 PCIe Err Cap Status = 0x5
PCIe Err Cap R0 = 0xC000040 PCIe Err Cap R1 = 0xFF000004
PCIe Err Cap R2 = 0x20000000 PCIe Err Cap R3 = 0xAAAA0300
Fatal PCIe error - Multiple Errors Detected
Fatal PCIe error - Inbound transaction was not mapped to any inbound window
%Software-forced reload
12:24:26 CST Mon Dec 29 2014: Unexpected exception to CPU: vector 1500, PC = 0x4A3A114 , LR = 0x4A3A0AC
-Traceback= 0x4A3A114z 0x4A3A0ACz 0x4A3DF54z 0x4124D00z 0x4124D00z 0x4A3E010z 0x6644898z 0x664480Cz 0x6644B04z 0x6621B94z 0x8F86324z 0x8DBCF4Cz 0x8DD0420z 0x8DD0A60z 0x8DAE54Cz 0x8DAEE84z
Plus the various memory dumps.
This has happened 3 times now and in all cases, traffic levels have been the same just before the crash.
Any help in understanding why this is happening would be appreciated and thanks in advance.
-Gary

Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
Unless you really need your particular IOS version, like Leo, I too would recommend moving to a mainline recommended release that suites your needs.
PS:
It's likely you're correct that you're seeing drops before you hit your ATM "bandwidth" cap. The ATM cell "tax" is a 5 byte header in each 53 byte cell and, if doing IP, there's cell padding (packets will sized up to the next multiple of 48).
For example, a 97 byte payload would consume 159 bytes (about 39% overhead).

My router crashes everyday.

I need turn off power and turn on. Every day the router crashed. model is MI424WR.

I wonder if that has something to deal with the DNS Client/Server in the router.
I point to https://www.grc.com/dns/dns.htm
and try the Standard DNS Test and the Router Crash Test
If you are the original poster (OP) and your issue is solved, please remember to click the "Solution?" button so that others can more easily find it. If anyone has been helpful to you, please show your appreciation by clicking the "Kudos" button.

Router crashes after starting app

Hello,
Can anyone help me with the following problem:
I have an app (Ruzzle) on my iPad. It's a simple game, nothing fancy. But when I'm at home connected true WIFI and I start this app, my router crashes. Everytime after approx 5 seconds when I start this app my connection is lost on every device which is connected to this router (iPad/iPhone/Computers). When I play this game in an different environment (which has an different router) I do not have this problem. When I use other apps which require internet connections there is also no problem.
This app originally is an iPhone app which I also have installed on my iPhone. However when I play it on my iPhone there is no problem.
Anyone has any idea what the problem is?

i made some changes, but nothing that would or could cause this. And besides according to my collegues its not a recent problem (before i joined the company), it goes back at least a year or more...but ofc. since router is working fine untill you try to show the config noone bothered to resolve the issue they just kept their hands off it -.-

How to expand the signal of a WRT150N router

Hello,
In a recent trip to USA, I bought a WRT150N router and a WMP300N Wireless-N PCI Adapter, but due to the distance and walls I am not being able to receive the signal. I would like to know if Linksys has any kind of antenna or other product compatible with those two products that I can use to expand the signal and solve my problem.
Thanks and best regards,
Gustavo

well...the N-series router itself should give u a good range..however , if u want to go for a expand the signal , u can try out WRE54G v3...it works with WRT300N and WRT350N..so i guess it should work fine with WRT150N as well..

Router crashes

Hi All,
I hope someone can help me. I am trying to capture traffic in our router which is a Cisco 892. I need to submit a ticket to our ISP and provide them the info as we think that the connection is dropping packets.
I follow the steps from this link: https://learningnetwork.cisco.com/blogs/vip-perspectives/2014/04/15/capturing-traffic-on-cisco-routers-rite-and-epc-features
When I try to add the profile to the interface. the router crash and restarted itself. Below is message from console when it crashed.
router(config-if)#ip traffic-export ?
apply Apply a configured profile to this interface
router(config-if)#ip traffic-export apply cisco-test
router(config-if)#
16:41:07 GMT Thu Mar 5 2015: Unexpected exception to CPU: vector 1200, PC = 0x8002CDCC, LR = 0x8392ED18
-Traceback= 0x8002CDCCz 0x8392ED18z 0x8392F164z 0x8005830Cz 0x80058F10z 0x8005830Cz 0x800587E4z 0x835E494Cz 0x835E3614z 0x81420E60z 0x81423108z 0x8003A9B4z 0x8003CEA0z 0x81661770z 0x8002DB98z 0x8166743Cz
CPU Register Context:
MSR = 0x40019030 CR = 0x44028048 CTR = 0x8002CD40 XER   = 0x20000000
R0 = 0x00000000 R1 = 0x894A8E08 R2 = 0xFFF950B0 R3    = 0x00001200
R4 = 0x00000039 R5 = 0x0000001D R6 = 0x00000000 R7    = 0xFF400000
R8 = 0x6DFFFFFF R9 = 0x00000001 R10 = 0x897656FF R11   = 0x8002CD40
R12 = 0x44028044 R13 = 0xFFC00000 R14 = 0x89751038 R15   = 0x894A8FF8
R16 = 0x86FE0000 R17 = 0x894A9068 R18 = 0x00000000 R19   = 0x89750AC4
R20 = 0x894A8EB0 R21 = 0x8B2098BC R22 = 0x86FE0000 R23   = 0x894A8EB4
R24 = 0x00000000 R25 = 0x8C24B01D R26 = 0x8B1B00B4 R27   = 0x896B5334
R28 = 0x89C36458 R29 = 0x00000000 R30 = 0x0000003A R31   = 0x89765700
TEXT_START : 0x800200E8
DATA_START : 0x851444DC
Writing crashinfo to flash:crashinfo_20150305-164107-GMT
=== Flushing messages (16:41:07 GMT Thu Mar 5 2015) ===
Buffered messages:
*Mar 5 08:22:13.591: %LINK-3-UPDOWN: Interface FastEthernet8, changed state to up
*Mar 5 08:22:13.591: %LINK-3-UPDOWN: Interface GigabitEthernet0, changed state to up
*Mar 5 08:22:33.679: %LINK-3-UPDOWN: Interface Virtual-Access1, changed state to up
*Mar 5 08:22:35.091: %LINK-3-UPDOWN: Interface FastEthernet0, changed state to up
*Mar 5 08:22:35.103: %LINK-3-UPDOWN: Interface FastEthernet1, changed state to up
*Mar 5 08:22:35.115: %LINK-3-UPDOWN: Interface FastEthernet2, changed state to up
*Mar 5 08:22:35.163: %LINK-3-UPDOWN: Interface FastEthernet7, changed state to up
*Mar 5 08:22:35.767: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to up
*Mar 5 08:22:37.343: %LINK-3-UPDOWN: Interface FastEthernet0, changed state to down
*Mar 5 08:22:39.419: %LINK-3-UPDOWN: Interface FastEthernet0, changed state to up
Queued messages:
No warm reboot Storage
*** System received a SIGTRAP exception ***
signal= 0x5, code= 0x1200, context= 0x870dd260
Stack trace:
PC = 0x8002cdcc, SP = 0x894a8e28
Frame 00: SP = 0x894a8ea8    PC = 0x8392f164
Frame 01: SP = 0x894a8ef8    PC = 0x8005830c
Frame 02: SP = 0x894a8f28    PC = 0x80058f10
Frame 03: SP = 0x894a8f78    PC = 0x8005830c
Frame 04: SP = 0x894a8f80    PC = 0x800587e4
Frame 05: SP = 0x894a8fd8    PC = 0x835e494c
Frame 06: SP = 0x894a8fe0    PC = 0x835e3614
Frame 07: SP = 0x894a9058    PC = 0x81420e60
Frame 08: SP = 0x894a90b8    PC = 0x81423108
Frame 09: SP = 0x894a9120    PC = 0x8003a9b4
Frame 10: SP = 0x894a9140    PC = 0x8003cea0
Frame 11: SP = 0x894a9158    PC = 0x81661770
Frame 12: SP = 0x875ce224    PC = 0x8002db98
Frame 13: SP = 0x875ce234    PC = 0x8166743c
Frame 14: SP = 0x875ce27c    PC = 0x8166743c
Frame 15: SP = 0x8885f0f4    PC = 0x8002dc58
Frame 16: SP = 0x8885f100    PC = 0x81855640
Frame 17: SP = 0x8885f160    PC = 0x8185563c
Frame 18: SP = 0xffffffff    PC = 0x8185bf44
CPU Register Context:
PC = 0x8002cdcc MSR = 0x40019030 CR = 0x44028048 LR    = 0x8392ed18
CTR = 0x8002cd40 XER = 0x20000000 DAR = 0x00000000 DSISR = 0x00000000
DEC = 0xc1438ef5 TBU = 0x00000016 TBL = 0x3ebc3f41 PVR   = 0x80830031
R0 = 0x00000000 R1 = 0x894a8e08 R2 = 0xfff950b0 R3    = 0x00001200
R4 = 0x00000039 R5 = 0x0000001d R6 = 0x00000000 R7    = 0xff400000
R8 = 0x6dffffff R9 = 0x00000001 R10 = 0x897656ff R11   = 0x8002cd40
R12 = 0x44028044 R13 = 0xffc00000 R14 = 0x89751038 R15   = 0x894a8ff8
R16 = 0x86fe0000 R17 = 0x894a9068 R18 = 0x00000000 R19   = 0x89750ac4
R20 = 0x894a8eb0 R21 = 0x8b2098bc R22 = 0x86fe0000 R23   = 0x894a8eb4
R24 = 0x00000000 R25 = 0x8c24b01d R26 = 0x8b1b00b4 R27   = 0x896b5334
R28 = 0x89c36458 R29 = 0x00000000 R30 = 0x0000003a R31   = 0x89765700
I hope someone can help take a look. Now getting traffic logs is more important. Please Help!

I'd recommend upgrading the IOS.

Router Crashs when using EEM(TCL script)

I wrote a TCL script to deal with my dual-link router, but the script running for some time will case the router crash.Could you help me for this?
Is there some problem with my script ?Thank you!
Routers :CISCO2821
IOS vesion:12.4(15)T8

This looks like CSCsv52332. This bug is fixed in 12.4(15)T10.

Router Crashes after entering "show run" or similar commands

Hello,
Im having a problem with my Company router C3845-ADVSECURITYK9-M, software Version 15.1(4)M. After i issue "show run" it tends to crash in middle of output, router restarts itself to be precise....same thing happened when i tried "show stack" afterwards, it happened several times when trying to show running config, so im guessing it has some problem when trying to display large outputs...i have never heard of such thing though so im asking for advice,
These are some informations i gathered:
show version:....
System returned to ROM by error - a Software forced crash, PC 0x60AD4710 at 14:10:56 CET-SUM Wed Aug 13 2014
xxxx#sh env
SYS PS1 is present.
Fan status: Normal
Input Voltage status: Normal
DC Output Voltage status: Normal
Type: AC
Thermal status: Normal
SYS PS2 is absent.
AUX(-48V) PS1 is absent.
AUX(-48V) PS2 is absent.
Fan 1 OK
Fan 2 OK
Fan 3 OK
Fan Speed Setting: Normal
Alert settings:
Intake temperature warning: Enabled, Threshold: 55
Core temperature warning: Enabled, Threshold: 70 (CPU: 90)
Board Temperature: Normal
Internal-ambient temperature = 38, Normal
CPU temperature = 50, Normal
Intake temperature = 32, Normal
Backplane temperature = 29, Normal
Voltage 1(3300) is Normal, Current voltage = 3284 mV
Voltage 2(5150) is Normal, Current voltage = 5153 mV
Voltage 3(2500) is Normal, Current voltage = 2525 mV
Voltage 4(1200) is Normal, Current voltage = 1203 mV
xxxx#sh logg
Syslog logging: enabled (0 messages dropped, 120 messages rate-limited, 0 flushes, 0 overruns, xml disabled, filtering disabled)
No Active Message Discriminator.
No Inactive Message Discriminator.
Console logging: level debugging, 62 messages logged, xml disabled,
filtering disabled
Monitor logging: level debugging, 0 messages logged, xml disabled,
filtering disabled
Buffer logging: level debugging, 178 messages logged, xml disabled,
filtering disabled
Exception Logging: size (4096 bytes)
Count and timestamp logging messages: disabled
Persistent logging: disabled
No active filter modules.
Trap logging: level informational, 181 message lines logged
Logging to 10.254.0.49 (udp port 514, audit disabled,
link up),
181 message lines logged,
0 message lines rate-limited,
0 message lines dropped-by-MD,
xml disabled, sequence number disabled
filtering disabled
Logging to 10.254.8.44 (udp port 514, audit disabled,
link up),
181 message lines logged,
0 message lines rate-limited,
0 message lines dropped-by-MD,
xml disabled, sequence number disabled
filtering disabled
Log Buffer (1000000 bytes):
*Aug 13 12:33:24.867: %VPN_HW-6-INFO_LOC: Crypto engine: onboard 0 State changed to: Initialized
*Aug 13 12:33:24.871: %VPN_HW-6-INFO_LOC: Crypto engine: onboard 0 State changed to: Enabled
*Aug 13 12:33:25.635: %LINK-5-CHANGED: Interface GigabitEthernet0/0, changed state to reset
*Aug 13 12:33:25.635: %LINK-5-CHANGED: Interface GigabitEthernet0/1, changed state to reset
*Aug 13 12:33:25.927: %LINEPROTO-5-UPDOWN: Line protocol on Interface Onboard VPN, changed state to up
*Aug 13 12:33:26.635: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/0, changed state to up
*Aug 13 12:33:26.635: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed state to up
*Aug 13 12:33:27.787: %LINK-3-UPDOWN: Interface GigabitEthernet0/0, changed state to up
*Aug 13 12:33:27.787: %LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed state to up
*Aug 13 13:33:29.023: %SYS-6-CLOCKUPDATE: System clock has been updated from 12:33:29 UTC Wed Aug 13 2014 to 13:33:29 MET Wed Aug 13 2014, configured from console by console.
*Aug 13 14:33:29.023: %SYS-6-CLOCKUPDATE: System clock has been updated from 13:33:29 MET Wed Aug 13 2014 to 14:33:29 CET-SUM Wed Aug 13 2014, configured from console by console.
*Aug 13 14:33:30.471: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:0, changed state to down
*Aug 13 14:33:30.471: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:1, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:2, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:3, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:4, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:5, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:6, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:7, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:8, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:9, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:10, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:11, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:12, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:13, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:14, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:16, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:17, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:18, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:19, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:20, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:21, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:22, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:23, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:24, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:25, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:26, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:27, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:28, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:29, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:30, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:15, changed state to down
*Aug 13 14:33:30.499: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:0, changed state to down
*Aug 13 14:33:30.499: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:1, changed state to down
*Aug 13 14:33:30.499: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:2, changed state to down
*Aug 13 14:33:30.499: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:3, changed state to down
*Aug 13 14:33:30.499: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:4, changed state to down
*Aug 13 14:33:30.499: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:5, changed state to down
*Aug 13 14:33:30.503: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:6, changed state to down
*Aug 13 14:33:30.503: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:7, changed state to down
*Aug 13 14:33:30.503: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:8, changed state to down
*Aug 13 14:33:30.503: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:9, changed state to down
*Aug 13 14:33:30.503: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:10, changed state to down
*Aug 13 14:33:30.503: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:11, changed state to down
*Aug 13 14:33:30.503: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:12, changed state to down
*Aug 13 14:33:30.503: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:13, changed state to down
*Aug 13 14:33:30.503: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:14, changed state to down
*Aug 13 14:33:30.507: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:16, changed state to down
*Aug 13 14:33:30.507: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:17, changed state to down
*Aug 13 14:33:30.507: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:18, changed state to down
*Aug 13 14:33:30.507: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:19, changed state to down
*Aug 13 14:33:30.507: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:20, changed state to down
*Aug 13 14:33:30.507: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:21, changed state to down
*Aug 13 14:33:30.507: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:22, changed state to down
*Aug 13 14:33:30.507: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:23, changed state to down
*Aug 13 14:33:30.507: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:24, changed state to down
*Aug 13 14:33:30.511: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:25, changed state to down
*Aug 13 14:33:30.511: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:26, changed state to down
*Aug 13 14:33:30.511: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:27, changed state to down
*Aug 13 14:33:30.511: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:28, changed state to down
*Aug 13 14:33:30.511: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:29, changed state to down
*Aug 13 14:33:30.511: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:30, changed state to down
*Aug 13 14:33:30.511: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:15, changed state to down
*Aug 13 14:33:30.575: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:0, changed state to down
*Aug 13 14:33:30.575: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:1, changed state to down
*Aug 13 14:33:30.575: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:2, changed state to down
*Aug 13 14:33:30.575: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:3, changed state to down
*Aug 13 14:33:30.575: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:4, changed state to down
*Aug 13 14:33:30.575: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:5, changed state to down
*Aug 13 14:33:30.575: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:6, changed state to down
*Aug 13 14:33:30.575: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:7, changed state to down
*Aug 13 14:33:30.575: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:8, changed state to down
*Aug 13 14:33:30.575: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:9, changed state to down
*Aug 13 14:33:30.575: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:10, changed state to down
*Aug 13 14:33:30.579: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:11, changed state to down
*Aug 13 14:33:30.579: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:12, changed state to down
*Aug 13 14:33:30.579: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:13, changed state to down
*Aug 13 14:33:30.579: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:14, changed state to down
*Aug 13 14:33:30.579: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:16, changed state to down
*Aug 13 14:33:30.579: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:17, changed state to down
*Aug 13 14:33:30.579: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:18, changed state to down
*Aug 13 14:33:30.579: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:19, changed state to down
*Aug 13 14:33:30.579: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:20, changed state to down
*Aug 13 14:33:30.579: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:21, changed state to down
*Aug 13 14:33:30.579: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:22, changed state to down
*Aug 13 14:33:30.579: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:23, changed state to down
*Aug 13 14:33:30.579: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:24, changed state to down
*Aug 13 14:33:30.579: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:25, changed state to down
*Aug 13 14:33:30.579: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:26, changed state to down
*Aug 13 14:33:30.579: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:27, changed state to down
*Aug 13 14:33:30.579: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:28, changed state to down
*Aug 13 14:33:30.579: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:29, changed state to down
*Aug 13 14:33:30.579: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:30, changed state to down
*Aug 13 14:33:30.579: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:15, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:0, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:1, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:2, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:3, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:4, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:5, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:6, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:7, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:8, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:9, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:10, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:11, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:12, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:13, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:14, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:16, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:17, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:18, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:19, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:20, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:21, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:22, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:23, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:24, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:25, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:26, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:27, changed state to down
*Aug 13 14:33:30.687: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:28, changed state to down
*Aug 13 14:33:30.687: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:29, changed state to down
*Aug 13 14:33:30.687: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:30, changed state to down
*Aug 13 14:33:30.687: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:15, changed state to down
*Aug 13 14:33:30.731: %LINEPROTO-5-UPDOWN: Line protocol on Interface Loopback0, changed state to up
*Aug 13 14:33:31.535: %LINK-3-UPDOWN: Interface Serial0/1/0:1, changed state to down
*Aug 13 14:33:31.795: %LINK-5-CHANGED: Interface GigabitEthernet0/0, changed state to reset
*Aug 13 14:33:31.999: %LINK-5-CHANGED: Interface GigabitEthernet0/1, changed state to reset
*Aug 13 14:33:32.599: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/0:1, changed state to down
*Aug 13 14:33:32.799: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/0, changed state to down
*Aug 13 14:33:32.999: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed state to down
*Aug 13 14:33:34.811: %QOS_CLI_DEPRECATE-4-MAX_RESERVED_BW: max-reserved-bandwidth on interface has been deprecated. For further information, please consult Product Bulletin 580832, Legacy QoS CLI Commands Deprecation
*Aug 13 14:33:34.815: Interface Serial0/1/0:1 max_reserved_bandwidth config will not
take effect on the queueing features configured via service-policy
*Aug 13 14:33:35.795: %LINK-3-UPDOWN: Interface GigabitEthernet0/0, changed state to up
*Aug 13 14:33:35.795: %LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed state to up
*Aug 13 14:33:36.811: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/0, changed state to up
*Aug 13 14:33:36.811: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed state to up
*Aug 13 14:33:36.811: %LINK-5-CHANGED: Interface Serial0/1/0:1, changed state to administratively down
*Aug 13 14:33:37.419: %LINK-5-CHANGED: Interface Dialer1, changed state to administratively down
*Aug 13 14:33:38.055: %SYS-5-CONFIG_I: Configured from memory by console
*Aug 13 14:33:38.491: %SYS-5-RESTART: System restarted --
Cisco IOS Software, 3800 Software (C3845-ADVSECURITYK9-M), Version 15.1(4)M, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2011 by Cisco Systems, Inc.
Compiled Thu 24-Mar-11 17:29 by prod_rel_team
*Aug 13 14:33:38.495: %SNMP-5-COLDSTART: SNMP agent on host xxxx is undergoing a cold start
*Aug 13 14:33:38.519: %SSH-5-ENABLED: SSH 2.0 has been enabled
*Aug 13 14:33:38.699: %SYS-6-BOOTTIME: Time taken to reboot after reload = 158 seconds
*Aug 13 14:33:38.859: %CONTROLLER-5-UPDOWN: Controller E1 0/0/0, changed state to up
*Aug 13 14:33:38.867: %CONTROLLER-5-UPDOWN: Controller E1 0/0/1, changed state to up
*Aug 13 14:33:38.875: %CRYPTO-6-ISAKMP_ON_OFF: ISAKMP is OFF
*Aug 13 14:33:38.875: %CRYPTO-6-ISAKMP_ON_OFF: ISAKMP is OFF
*Aug 13 14:33:38.879: %CRYPTO-6-ISAKMP_ON_OFF: ISAKMP is OFF
*Aug 13 14:33:38.879: %CRYPTO-6-GDOI_ON_OFF: GDOI is OFF
*Aug 13 14:33:38.879: %CRYPTO-6-ISAKMP_ON_OFF: ISAKMP is ON
*Aug 13 14:33:38.896: %CONTROLLER-5-UPDOWN: Controller E1 1/0, changed state to up
*Aug 13 14:33:39.140: %SYS-6-LOGGINGHOST_STARTSTOP: Logging to host 10.254.0.49 port 514 started - CLI initiated
*Aug 13 14:33:39.140: %SYS-6-LOGGINGHOST_STARTSTOP: Logging to host 10.254.8.44 port 514 started - CLI initiated
*Aug 13 14:33:40.860: %LINK-3-UPDOWN: Interface Serial0/0/0:15, changed state to up
*Aug 13 14:33:40.868: %LINK-3-UPDOWN: Interface Serial0/0/1:15, changed state to up
*Aug 13 14:33:40.884: %LINK-3-UPDOWN: Interface Serial1/0:15, changed state to up
*Aug 13 14:33:41.684: %CSM-5-PRI: add PRI at 0/0/1:15 (index 0)
*Aug 13 14:33:41.688: %CSM-5-PRI: add PRI at 0/0/0:15 (index 1)
*Aug 13 14:33:51.648: %CSM-5-PRI: add PRI at 1/0:15 (index 2)
*Aug 13 14:34:14.956: %HSRP-5-STATECHANGE: GigabitEthernet0/0.400 Grp 0 state Standby -> Active
*Aug 13 14:34:15.164: %HSRP-5-STATECHANGE: GigabitEthernet0/0.400 Grp 2 state Standby -> Active
*Aug 13 14:34:15.484: %HSRP-5-STATECHANGE: GigabitEthernet0/0.400 Grp 3 state Standby -> Active
*Aug 13 14:34:21.600: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.85.212 on GigabitEthernet0/1.86 from LOADING to FULL, Loading Done
*Aug 13 14:34:27.728: %HSRP-5-STATECHANGE: GigabitEthernet0/0.400 Grp 4 state Standby -> Active
*Aug 13 14:20:02.780: %SYS-5-PRIV_AUTH_FAIL: Authentication to privilege level 15 failed by xxxx on vty0 (xxxx)
*Aug 13 14:21:50.405: %SYS-5-CONFIG_I: Configured from console by av-vilenko on vty0 (xxxx)

i made some changes, but nothing that would or could cause this. And besides according to my collegues its not a recent problem (before i joined the company), it goes back at least a year or more...but ofc. since router is working fine untill you try to show the config noone bothered to resolve the issue they just kept their hands off it -.-

WRT150N router crashing

Similar Messages

Maybe you are looking for