[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Testbed-admins] Node mapping

The 'no possible mapping message' is fairly specific in this case - it's complaining the emulab-ops/FBSD62-STD image doesn't run on your node type. This means you either are asking for an incorrect image in your NS file, or your database needs to be updated to indicate that this image can really run on the type of nodes you have. 

On 6/15/10 12:17 PM, Chris Benninger wrote:

Hi again,

So I am trying to create a simple dumbbell experiment as an example. I
have 14 nodes "free" and 2 of them are reserved for the testbed project.

The experiment swap-in log give me a "No possible mapping" message and
fails. Also each node is in the "Boot wait mode", I assume that is where
they need to be? Any Ideas? Thanks!

Here is the swap-in log:

    Running'tbswap in  testbed dumbell'


    Beginning swap-in for testbed/dumbell (20). 06/15/2010 18:10:32
    TIMESTAMP: 18:10:32:626024 tbswap in started
    Checking with Admission Control ...
    Mapping to physical reality ...
    TIMESTAMP: 18:10:32:634689 assign_wrapper started


    assign_wrapper improved started
    TIMESTAMP: 18:10:33:19330 assign_wrapper started
    TIMESTAMP: 18:10:33:23063 TOP started
    Resetting DB before updating.
    opened topfile
    Minimum nodes   = 2
    Maximum nodes   = 2


    TIMESTAMP: 18:10:33:52347 TOP finished
    TIMESTAMP: 18:10:33:53113 assign_loop started
    Assign Run 1
    TIMESTAMP: 18:10:33:54555 ptopgen started
    ptopargs -p testbed -e dumbell
    TIMESTAMP: 18:10:33:876991 ptopgen finished


    TIMESTAMP: 18:10:33:879341 assign started
    assign -P testbed-dumbell-2322.ptop testbed-dumbell-2322.top
    ASSIGN FAILED:
    Type precheck passed.
       *** No possible mapping for node0
            OS'emulab-ops/FBSD62-STD'  (OS-10003) does not run on this hardware type!


       *** No possible mapping for node1
            OS'emulab-ops/FBSD62-STD'  (OS-10003) does not run on this hardware type!
    *** Node mapping precheck failed!


    Trying assign on an empty testbed.
    TIMESTAMP: 18:10:35:953404 ptopgen started
    ptopargs -p testbed -e dumbell -a
    TIMESTAMP: 18:10:36:775456 ptopgen finished
    TIMESTAMP: 18:10:36:777663 assign started
    assign -n -P testbed-dumbell-2322-empty.ptop testbed-dumbell-2322.top


    ASSIGN FAILED:
    Type precheck passed.
       *** No possible mapping for node0
            OS'emulab-ops/FBSD62-STD'  (OS-10003) does not run on this hardware type!


       *** No possible mapping for node1
            OS'emulab-ops/FBSD62-STD'  (OS-10003) does not run on this hardware type!
    *** Node mapping precheck failed!


    *** ERROR: assign_wrapper:
    ***   This experiment cannot be instantiated on this testbed. You have most
    ***   likely asked for hardware this testbed does not have, such as nodes


    ***   of a type it does not contain, or nodes with too many network
    ***   interfaces.  You will need to modify this experiment before it can be
    ***   swapped in - re-submitting the experiment as-is will always result in


    ***   failure.
    *** ERROR: tbswap: Failed (65) to map to reality.
    Cleaning up after errors.
    Stopping the event system
    TIMESTAMP: 18:10:40:977371 snmpit started


    Removing VLANs.
    snmpit: testbed/dumbell has no VLANs to remove, skipping
    TIMESTAMP: 18:10:41:856165 snmpit finished
    Tearing down virtual nodes.
    TIMESTAMP: 18:10:41:859579 vnode_setup -k started
    *** /usr/testbed/sbin/vnode_setup:


         No allocated nodes in experiment testbed/dumbell!
    TIMESTAMP: 18:10:42:604939 vnode_setup finished
    Freeing nodes.
    TIMESTAMP: 18:10:42:608341 nfree started
    Releasing all nodes from experiment [Experiment: testbed/dumbell].


    TIMESTAMP: 18:10:43:348916 nfree finished
    Resetting named maps.
    TIMESTAMP: 18:10:43:353147 named started
    TIMESTAMP: 18:10:44:382893 named finished
    Resetting email lists.
    TIMESTAMP: 18:10:44:385739 genelists started


    TIMESTAMP: 18:10:45:169411 genelists finished
    Resetting DB.
    Failingly finished swap-in for testbed/dumbell. 18:10:45:176600
    TIMESTAMP: 18:10:45:177719 tbswap in finished (failed)
    *** ERROR: swapexp: tbswap in failed!


    Cleaning up and exiting with status 1 ...
    **** Experimental information, please ignore ****
    Session ID = 6986
    Likely Cause of the Problem:
       This experiment cannot be instantiated on this testbed. You have most


       likely asked for hardware this testbed does not have, such as nodes of
       a type it does not contain, or nodes with too many network interfaces.
       You will need to modify this experiment before it can be swapped in -


       re-submitting the experiment as-is will always result in failure.

       No possible mapping for node0
       OS'emulab-ops/FBSD62-STD'  (OS-10003) does not run on this hardware type!

       No possible mapping for node1


       OS'emulab-ops/FBSD62-STD'  (OS-10003) does not run on this hardware type!
    Cause: user
    Confidence: 0.9
    Script: assign_wrapper
    **** End experimental information ****


Here is my NS file:

    set ns [new Simulator]
    source tb_compat.tcl

    # Nodes


    set node0 [$ns node]
    tb-set-node-os $node0 FBSD62-STD
    set node1 [$ns node]
    tb-set-node-os $node1 FBSD62-STD

    # Lans
    set lan0 [$ns make-lan"$node0 $node1"  100000.0kb 0.0ms]

    $ns rtproto Static


    $ns run




--
Chris Benninger
University of Victoria, Computer Science
cbenning@cs.uvic.ca <mailto:cbenning@cs.uvic.ca>
http://syfor.com

--
This message has been scanned for viruses and
dangerous content by *MailScanner* <http://www.mailscanner.info/>, and is
believed to be clean.



_______________________________________________
Testbed-admins mailing list
Testbed-admins@flux.utah.edu
http://www.flux.utah.edu/mailman/listinfo/testbed-admins