| 1 | [wiki:WikiStart Orbit] > [wiki:NodeHandler NodeHandler] > [wiki:NodeHandler/FAQ FAQ] > Program Node ID Box |
| 2 | |
| 3 | = Details of how to program a node-id box = |
| 4 | |
| 5 | You will need a computer, a cross over cable and a test ORBIT node. This setup is currently in place in the ORBIT lab room |
| 6 | |
| 7 | * Step 1: Connect the computer to the node's CM interface using cross-over cable and configure the node's IP address to 10.0.0.200 netmask 255.0.0.0 |
| 8 | |
| 9 | * Step 2: Connect the node ID that you want to program to the node ID connector socket on the front of the node |
| 10 | |
| 11 | * Step 3: Connect power to the node and wait for the node ID box to start blinking |
| 12 | |
| 13 | * Step 4: Telnet to 10.1.222.222, this is the default CM IP for a new node ID box |
| 14 | {{{ |
| 15 | telnet 10.1.222.222 |
| 16 | }}} |
| 17 | |
| 18 | * You will see a CM prompt like this |
| 19 | {{{ |
| 20 | *** WINLAB ORBIT CHASSIS MANAGER CONSOLE *** |
| 21 | |
| 22 | type ? for help |
| 23 | |
| 24 | }}} |
| 25 | |
| 26 | * At the prompt, type eprom and hit enter, you should get the following screen |
| 27 | {{{ |
| 28 | Usage: eprom NodeType p1 p2 HostBaud |
| 29 | where NodeType: 1=GridNode, 2=SupportNode, 3=SandboxNode |
| 30 | p1 p2: p1=x, p2=y GridNode coord (x,y) |
| 31 | p1 p2: p1=100, p2=SupportNode ID |
| 32 | p1 p2: p1=101...199 Sandbox ID, p2: XXXXYYYY SandboxNode coord (X,Y) |
| 33 | HostBaud: Host Console Baud Rate (1...5): |
| 34 | 1=9600, 2=19200, 3=38400, 4=57600, 5=115200 |
| 35 | Example: eprom 1 5 6 4 (all numbers decimal) |
| 36 | |
| 37 | }}} |
| 38 | |
| 39 | * Step 5: As an example to program node1-1 belonging to sandbox 5, you will use the convention |
| 40 | 3 - for sandbox domain, 105 for IP subnet of sandbox5, 17 - for first node of sandbox and 1 for baud rate |
| 41 | {{{ |
| 42 | |
| 43 | eprom 3 105 17 1 |
| 44 | |
| 45 | }}} |
| 46 | |
| 47 | * Step 6: This should give you an OK message, with a request to ''reboot'' the node ID box |
| 48 | |
| 49 | * Step 7: Type ''reboot'' at the node ID console |
| 50 | |
| 51 | * Step 8: You can kill the telnet session and now log in using the new node ID's IP which is 10.1.105.17 (for the above example) |
| 52 | }}} |