The ever-popular 2600 issue.
So I'm trying to run a 2621XM. I get the image extracted, run dynagen, start R1, and when I try to telnet to it I get:
Connected to Dynamips VM "R1" (ID 0, type c2600) - Console port
And I cant do anything more. I've searched Google, found quite a few hits, but nothing has actually solved the issue.
Just to clarify, I -have- uncompressed the image.
Here is my .net file, for good measure:
autostart = False
[localhost:7550]
udp = 12345
workingdir = /home/cjones/dynamips/labs/2600test/working
[[2621XM]]
image = /home/cjones/dynamips/images/c2600.bin
ram = 128
[[Router R1]]
model = 2621XM
console = 7551
wic0/1 = WIC-2T
slot1 = NM-4E
Thanks!
** Edit: BOO @ removing my <style> tags in my post HTML! My code blocks were all pretty! ... but apparently inline styles work...
0
Comments
just a question -
isn't udp = 12345 means you need to telnet the router on that port ?
also are you sure the path you have written here in the .net file is actually to the extracted image "image = /home/cjones/dynamips/images/c2600.bin" ???
No.
Positive. I had it longer, but I shortened it to c2600.bin to make it easier to type.
Try these things:
1. I found a thread with a guy having the same problem. It was an issue with his terminal program (Teraterm). Try using telnet from a command prompt and see if that works better.
2. Try increasing the memory to 256 MB on the router.
3. Do you need that "udp = 12345" command? Try and remove it and see if that helps.
4. The first time when you don't have an idlepc value the router will be very slow. Try detecting an idlepc value and save that and then restart the lab and see if that helps.
If these things won't solve the problem for you head over to http://7200emu.hacki.at. That is the best support forum for Dynamips questions in my opinion.
It's a UNIX system, the command prompt is all there is.
I will try this.
*EDIT*
Tried it, and got the following:
Yes. It's strange that people keep pointing this out. Perhaps they aren't familiar with how Dynamips works?
Quite aware of idlepc. Your lab will only be slow without an idlepc value if it maxes out your CPU, which in my case it doesn't even come close. Not to mention, the lack of an idlepc value makes Dynamips -slow-, it doesn't just make the console connection suddenly stop working.
Actually I'm good friends with Chris.. I'm very familiar with how Dynamips works. I just say this so people don't see this thread and assume that I'm a newbie, because that isn't the case.
Sorry if I mistook you for a newbie of Dynamips I was simply trying to help out.
I guess if everything is set up correctly and you have this issue you need to troubleshoot where the issue comes from. I see three mainly three different components that could be at fault here.
- IOS
- Dynamips
- Your setup or operating system
By changing to a completely different version av IOS for 2600 you should be able to test if it’s something wrong with your IOS or if it works well in Dynamips or not.
I guess you have run many other routers in Dynamips on your computer and they all work well?
By testing your .net file and IOS on another computer and even another platform it should be interesting to see if you will have the same problem. If it works on another system you could draw some conclusions from that.
I would be happy to try your .net file and IOS out. Send me a PM with a link for me to download it and I will test it for you.
This is my .net file:
The IOS is c2600-adventerprisek9-mz.124-11.XJ4.bin
Thanks.
Your net file and IOS worked well for me but only after changing ram = 128. Got Traceback messages when using 256 ram just like you did.
Verify the checksum of your IOS file against the one I used to see if it's damaged somehow.
I'm using:
- Debian 4.0 running pre-compiled 64 bit kernel on two Quad Xeon processors.
- Pre-compiled binary of Dynamips (0.2.8-RC2-amd64)
- Pre-compiled binary of Dynagen (0.11.0)
I know that you know about idlepc but have you actually set an idlepc value and saved it in your config/database for this specific IOS? It is a long shot but sometimes it can take up to a minute before I get past the “Connected to Dynamips…” message when I don’t have an idlepc value set (especially on my laptop). On a slower machine mixed with some bad luck I don’t see it as completely impossible that it could take 2-4 min to get past that text. It’s worth a try at least.
Wow... weird. I re-downloaded the IOS, checked md5 (it matched), unzipped, checked md5 on the unzipped file (it matched also), changed my .net back to using 128MB, used the newly unzipped file, and it started fine.
I thought "okay, maybe the original image was bad", so I checked md5 of the image I had been using... it matched too.
Now I'm -very- confused why it's working now.... but oh well, I guess. I'll take it.
Thanks for the troubleshooting help...
I'm glad it started to work for you [:)].
Here’s the mail I got
Hi,
The attached DMP file is of the BAD_POOL_HEADER (19) bug check.
This indicates that a pool header is corrupt.
1. Uninstall Malwarebytes
Pro as it may be causing corruption.
2. If the above fails,
enable Driver Verifier:
Driver Verifier:
What is Driver Verifier?
Driver Verifier is included in Windows 8/8.1, 7, Windows Server 2008 R2,
Windows Vista, Windows Server 2008, Windows 2000, Windows XP, and Windows
Server 2003 to promote stability and reliability; you can use this tool to
troubleshoot driver issues. Windows kernel-mode components can cause system
corruption or system failures as a result of an improperly written driver, such
as an earlier version of a Windows Driver Model (WDM) driver.
Essentially, if there's a 3rd party driver believed to be at issue, enabling
Driver Verifier will help flush out the rogue driver if it detects a violation.
Before enabling Driver Verifier, it is recommended to create a
System Restore Point:
Vista - START | type rstrui - create a restore point
Windows 7 - START | type create | select "Create a Restore
Point"
How to enable Driver Verifier:
Start > type "verifier" without the quotes > Select the
following options -
1. Select - "Create custom settings (for code
developers)"
2. Select - "Select individual settings from
a full list"
3. Check the following boxes -
- Special Pool
- Pool Tracking
- Force IRQL Checking
- Deadlock Detection
- Security Checks (Windows 7 & 8)
- DDI compliance checking (Windows 8)
- Miscellaneous Checks
4. Select - "Select driver names from a
list"
5. Click on the "Provider" tab. This
will sort all of the drivers by the provider.
6. Check EVERY box that is NOT provided by Microsoft / Microsoft Corporation.
7. Click on Finish.
8. Restart.
Important information regarding
Driver Verifier:
- If Driver Verifier finds a violation, the system will BSOD. To expand on this
a bit more for the interested, specifically what Driver Verifier actually does
is it looks for any driver making illegal function calls, causing memory leaks,
etc. When and/if this happens, system corruption occurs if allowed to continue.
When Driver Verifier is enabled, it is monitoring all 3rd party drivers (as we have it set that
way) and when it catches a driver attempting to do this, it will quickly flag
that driver as being a troublemaker, and bring down the system safely before any
corruption can occur.
- After enabling Driver Verifier and restarting the system, depending on the
culprit, if for example the driver is on start-up, you may not be able to get
back into normal Windows because Driver Verifier will detect it in violation
almost straight away, and as stated above, that will cause / force a BSOD.
If this happens, do not panic, do
the following:
- Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.
- Once in Safe Mode - Start > Search > type "cmd" without the
quotes.
- To turn off Driver Verifier, type in cmd "verifier /reset" without
the quotes.
·
Restart and boot into normal Windows.
If your OS became corrupt or you cannot boot into Windows after disabling
verifier via Safe Mode:
- Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.
- Once in Safe Mode - Start > type "system restore" without the
quotes.
- Choose the restore point you created earlier.
-- Note that Safe Mode for Windows 8/8.1 is a bit different, and you may need to
try different methods
How long should I keep Driver Verifier enabled for?
I recommend keeping it enabled for at least 24 hours. If you don't BSOD by
then, disable Driver Verifier. I will usually say whether or not I'd like for
you to keep it enabled any longer.
My system BSOD'd with Driver Verifier enabled, where can I find
the crash dumps?
They will be located in %systemroot%Minidump
Any other questions can most likely be answered by this article:
How To Fix “BAD POOL HEADER” BSOD?
Some newbies have issues while using windows and cannot upgrade the system. Well, this is not easy to activate windows, but now you can use windows 10 activator Kmspico tool and enjoy the full features of windows.
Microsoft toolkit 2.6.6 windows 10 and office activator, is also tool for windows 10 activation for free, you still can use it.
Hi , very good article.
thanks for sharing, keep up the good work
well this post is superb, but for the most of the time i used Microsoft toolkit 2.6.7 for activate windows 10 , 8 and office 2013, 2016. Ez mode and KMS activation method worked like a cham!!. somehow new comers to windows 10. they just getting their pc messed up by using unwanted activaters. im suggesting for all of them just use microsoft toolkit 2.6.7 for any windows versions. doesnt mind its up to date or not. tool will do the job.
thanks!!
That's great article thanks for solving the issue have a look also, Express VPN with Crack