in
IEOC CCIE Forums

IEOC - INE's Online Community

Welcome to INE's Online Community - IEOC - a place for CCIE and CCENT candidates to connect, share, and learn. Our Online Community features CCIE forums and discussions for all tracks including Routing & Switching, Voice, Security, Service Provider, Wireless,, and Storage. Through these online communities you can discuss your questions with thousands of your peers, hundreds of CCIE's and INE's own team of world renowned CCIE instructors and authors, Brian Dennis - Quintuple CCIE #2210, Brian McGahan – Triple CCIE #8593, Petr Lapukhov - Quad CCIE #16379, and Mark Snow - Dual CCIE #14073.
Latest post 12-06-2016 11:46 PM by kinjo. 10 replies.
Page 1 of 1 (11 items)
Sort Posts: Previous Next
  • 08-16-2008 9:32 PM

    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...

    Chris Jones, CCIE# 25655 (R&S)

    Filed under: , , ,
    • Post Points: 65
  • 08-16-2008 10:54 PM In reply to

    Re: The ever-popular 2600 issue.

    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" ???

     

     

    • Post Points: 20
  • 08-16-2008 10:56 PM In reply to

    Re: The ever-popular 2600 issue.

    shai-l:

    isn't   udp = 12345  means you need to telnet the router on that port ?

    No.

    shai-l:

    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" ???

    Positive. I had it longer, but I shortened it to c2600.bin to make it easier to type.

    Chris Jones, CCIE# 25655 (R&S)

    • Post Points: 5
  • 08-17-2008 7:10 AM In reply to

    Re: The ever-popular 2600 issue.

    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.

    • Post Points: 20
  • 08-17-2008 10:48 AM In reply to

    Re: The ever-popular 2600 issue.

    Anders Nilsson:

    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.

    It's a UNIX system, the command prompt is all there is.

    Anders Nilsson:

    2. Try increasing the memory to 256 MB on the router.

    I will try this.

    *EDIT*

    Tried it, and got the following:

     00:00:04 UTC Fri Mar 1 2002: Unexpected exception to CPU: vector 700, PC = 0x80293DA8, LR = 0x80293CE8
    
    -Traceback= 0x80293DA8 0x80293CE8 0x80082D5C 0x8007A5F4 0x803F9810 0x803DE490 0x802DFB34 0x813C8DB4 0x813C8FF0 0x80295CC0 0x80299480
    
    CPU Register Context:
    MSR = 0x00029032  CR  = 0x28004084  CTR = 0x827CDDF8  XER   = 0x00000000
    R0  = 0x00000000  R1  = 0x85905A48  R2  = 0x85100000  R3    = 0x00000003
    R4  = 0xFFFFFFFE  R5  = 0x00000000  R6  = 0x85100000  R7    = 0x00009032
    R8  = 0x85100000  R9  = 0x84BB0000  R10 = 0x8528938C  R11   = 0x00000000
    R12 = 0x00000019  R13 = 0x00000000  R14 = 0x813C8FAC  R15   = 0x00000000
    R16 = 0x00000000  R17 = 0x00000000  R18 = 0x803F980C  R19   = 0x00000000
    R20 = 0x00000000  R21 = 0x85142794  R22 = 0x85905AD0  R23   = 0x00000000
    R24 = 0x000001D8  R25 = 0x062B4CD0  R26 = 0x85142884  R27   = 0x00000000
    R28 = 0x8514366C  R29 = 0x8338FFAC  R30 = 0x00000000  R31   = 0x062B4CD0
    

    Anders Nilsson:

    3. Do you need that "udp = 12345" command? Try and remove it and see if that helps.

    Yes. It's strange that people keep pointing this out. Perhaps they aren't familiar with how Dynamips works?

    Anders Nilsson:

    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.

    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.

    Anders Nilsson:

    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.

    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.

    Chris Jones, CCIE# 25655 (R&S)

    • Post Points: 5
  • 08-17-2008 12:45 PM In reply to

    Re: The ever-popular 2600 issue.

    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.

    • Post Points: 20
  • 08-17-2008 2:08 PM In reply to

    Re: The ever-popular 2600 issue.

    This is my .net file:

    autostart = False
    [localhost:7550]
        udp = 12345
        workingdir = /home/cjones/dynamips/labs/2600test/working
    
        [[2621XM]]
            image = /home/cjones/dynamips/images/c2600.bin
            ram = 256
    
        [[Router R1]]
            model = 2621XM
            console = 7551
            wic0/1 = WIC-2T
            slot1 = NM-4E
    

    The IOS is c2600-adventerprisek9-mz.124-11.XJ4.bin

    Thanks.

    Chris Jones, CCIE# 25655 (R&S)

    • Post Points: 20
  • 08-17-2008 11:57 PM In reply to

    Re: The ever-popular 2600 issue.

    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.

    netlab:/home/dynagen/images# md5sum c2600-adventerprisek9-mz.124-11.XJ4.bin
    a38b6452f3d26580ed9aafd6c83881d9  c2600-adventerprisek9-mz.124-11.XJ4.bin
    netlab:/home/dynagen/images# unzip c2600-adventerprisek9-mz.124-11.XJ4.bin
    Archive:  c2600-adventerprisek9-mz.124-11.XJ4.bin
    warning [c2600-adventerprisek9-mz.124-11.XJ4.bin]:  17940 extra bytes at beginning or within zipfile
      (attempting to process anyway)
      inflating: C2600-AD.BIN           
    netlab:/home/dynagen/images# md5sum C2600-AD.BIN
    79e496d9c3979b9d12b09bb01a58532a  C2600-AD.BIN


    netlab:/home/dynagen# cat labs/2600test/lab.net
    autostart = False
    [localhost:7550]
        udp = 12345
        workingdir = /home/dynagen/labs/2600test/working

        [[2621XM]]
            image = /home/dynagen/images/C2600-AD.BIN
            ram = 256

        [[Router R1]]
            model = 2621XM
            console = 7551
            wic0/1 = WIC-2T
            slot1 = NM-4E

    netlab:/home/dynagen# ./dynamips -H 7550 &
    [1] 23328
    netlab:/home/dynagen# Cisco Router Simulation Platform (version 0.2.8-RC2-amd64)
    Copyright (c) 2005-2007 Christophe Fillot.
    Build date: Oct 14 2007 10:46:52

    ILT: loaded table "mips64j" from cache.
    ILT: loaded table "mips64e" from cache.
    ILT: loaded table "ppc32j" from cache.
    ILT: loaded table "ppc32e" from cache.
    Hypervisor TCP control server started (port 7550).

    netlab:/home/dynagen# ./dynagen labs/2600test/lab.net
    Reading configuration file...

    Network successfully loaded

    Dynagen management console for Dynamips and Pemuwrapper 0.11.0
    Copyright (c) 2005-2007 Greg Anuzelli, contributions Pavel Skovajsa

    => start R1
    Warning: Starting R1 with no idle-pc value
    100-VM 'R1' started
    =>


    netlab:~# telnet localhost 7551
    Trying 127.0.0.1...
    Connected to localhost.
    Escape character is '^]'.
    Connected to Dynamips VM "R1" (ID 0, type c2600) - Console port

    Cisco 2621XM (MPC860P) processor (revision 2.2) with 118784K/12288K bytes of memory.
    Processor board ID 00000000000
    M860 processor: part number 0, mask 0
    4 Ethernet interfaces
    2 FastEthernet interfaces
    2 Serial(sync/async) interfaces
    32K bytes of NVRAM.
    16384K bytes of processor board System flash (Read/Write)


             --- System Configuration Dialog ---

    Would you like to enter the initial configuration dialog? [yes/no]: no


    Press RETURN to get started!


    *Mar  1 00:00:06.077: %LINEPROTO-5-UPDOWN: Line protocol on Interface VoIP-Null0, changed state to up
    *Mar  1 00:00:06.081: %LINK-3-UPDOWN: Interface FastEthernet0/0, changed state to up
    *Mar  1 00:00:06.089: %LINK-3-UPDOWN: Interface FastEthernet0/1, changed state to up
    *Mar  1 00:00:06.097: %LINK-3-UPDOWN: Interface Serial0/0, changed state to up
    *Mar  1 00:00:06.106: %LINK-3-UPDOWN: Interface Serial0/1, changed state to up
    *Mar  1 00:00:06.114: %LINK-3-UPDOWN: Interface Ethernet1/0, changed state to up
    *Mar  1 00:00:06.118: %LINK-3-UPDOWN: Interface Ethernet1/1, changed state to up
    *Mar  1 00:00:06.126: %LINK-3-UPDOWN: Interface Ethernet1/2, changed state to up
    *Mar  1 00:00:06.134: %LINK-3-UPDOWN: Interface Ethernet1/3, changed state to up
    *Mar  1 00:00:07.083: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/0, changed state to up
    *Mar  1 00:00:07.091: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/1, changed state to up
    *Mar  1 00:00:07.0
    Router>99: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0, changed state to up
    *Mar  1 00:00:07.107: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1, changed state to up
    *Mar  1 00:00:07.115: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet1/0, changed state to up
    *Mar  1 00:00:07.119: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet1/1, changed state to up
    *Mar  1 00:00:07.127: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet1/2, changed state to up
    *Mar  1 00:00:07.135: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet1/3, changed state to up
    *Mar  1 00:00:09.992: %SYS-5-RESTART: System restarted --
    Cisco IOS Software, C2600 Software (C2600-ADVENTERPRISEK9-M), Version 12.4(11)XJ4, RELEASE SOFTWARE (fc2)
    Technical Support: http://www.cisco.com/techsupport
    Copyright (c) 1986-2007 by Cisco Systems, Inc.
    Compiled Fri 13-Jul-07 21:49 by prod_rel_team
    *Mar  1 00:00:09.992: %SNMP-5-COLDSTART: SNMP agent on host Router is undergoing a cold start
    *Mar  1 00:00:10.236: %CRYPTO-6-ISAKMP_ON_OFF: ISAKMP is OFF
    *Mar  1 00:00:11.550: %LINK-5-CHANGED: Interface FastEthernet0/0, changed state to administratively down
    *Mar  1 00:00:11.558: %LINK-5-CHANGED: Interface Serial0/0, changed state to administratively down
    *Mar  1 00:00:11.566: %LINK-5-CHANGED: Interface FastEthernet0/1, changed state to administratively down
    *Mar  1 00:00:11.570: %LINK-5-CHANGED: Interface Serial0/1, changed state to administratively down
    *Mar  1 00:00:11.574: %LINK-5-CHANGED: Interface Ethernet1/0, changed state to administratively down
    *Mar  1 00:00:11.582: %LINK-5-CHANGED: Interface Ethernet1/1, changed state to administratively down
    *Mar  1 00:00:11.586: %LINK-5-CHANGED: Interface Ethernet1/2, changed state to administratively down
    *Mar  1 00:00:11.586: %LINK-5-CHANGED: Interface Ethernet1/3, changed state to administratively down
    *Mar  1 00:00:12.552: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/0, changed state to down
    *Mar  1 00:00:12.560: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0, changed state to down
    *Mar  1 00:00:12.564: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/1, changed state to down
    *Mar  1 00:00:12.572: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1, changed state to down
    *Mar  1 00:00:12.576: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet1/0, changed state to down
    *Mar  1 00:00:12.584: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet1/1, changed state to down
    *Mar  1 00:00:12.588: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet1/2, changed state to down
    *Mar  1 00:00:12.592: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet1/3, changed state to down
    Router>

    • Post Points: 20
  • 08-18-2008 6:11 AM In reply to

    Re: The ever-popular 2600 issue.

    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...

    Chris Jones, CCIE# 25655 (R&S)

    • Post Points: 20
  • 08-18-2008 9:46 AM In reply to

    Re: The ever-popular 2600 issue.

    I'm glad it started to work for you Smile.

    • Post Points: 5
  • 12-06-2016 11:46 PM In reply to

    Re: The ever-popular 2600 issue.

    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?

     

     

     

    • Post Points: 5
Page 1 of 1 (11 items)
IEOC CCIE Forums Internetwork Expert CCIE Training
About IEOC | Terms of Use | RSS | Privacy Policy
© 2010 Internetwork Expert, Inc. All Rights Reserved