Test Lab Standards & Best Practices

Addressing

IP segment addresses

The test lab uses 20-bit block RFC 1597 addresses (ie. 172.16.0.0 -- 172.31.255.255)

    172.N.T.X

where N=OSPF area (for area 0, N=16)

   where T=0 or 12 for point-to-point networks

   where T=4 for token ring networks

   where T=8 for frame relay networks

   where T>=16 for ethernet LAN networks

      where X=1 for router LAN interface

      where X=2 for concentrator or switch management module

      where X=3 for HP LANprobes

      where X=4 for DNS or DHCP servers

      where X=5 for Avalanche interface

      where X=6-10 for other reserved, "well known", addresses

      where X=11-50 for addresses dynamically assigned by the lab DHCP server

      where X=51-End of Range for open static addresses

 

IPX network addresses

AAxxyyAA for WAN networks

where xx=lower numbered router ID number (ie. 05 for test5 and 14 for test14)

where yy=higher numbered router ID number

 

999Annsx for LAN networks

where nn=router number

where s=0 for 10MB or F for 100MB

where x=router interface sequence number (ie. 999A02F0 for the first fast ethernet on test2 and 999A02F1 for the second fast ethernet on test2)


Best Practices

With the increasing amounts of equipment that we have to fit into the comms cabinets in the test lab, and with so many groups doing testing projects at the same time; it is important that we keep the cabinets in some semblance of order. The following guidelines, if adhered to, will enable us to best utilize the space in our cabinets; as well as helping to keep intra-project interference down. Also, many of these guidelines are mandatory in the production environment. Thus if you get into the habit of following these guidelines in the lab; it will not be a problem having to do the same things if you have to do stuff in production.

In no particular order:

1. Don't run cables horizontally through intervening cabinets -- use the patch panels.

2. Don't run cables vertically down the middle of cabinets -- run them down the sides.

3. Move the line drivers so that they are equidistant between the routers, don't set them on top of one of the routers so that one of the serial cables must be snaked through three cabinets to just barely reach the other router.

4. Run router serial cables under the floor, not through the cabinets.

5. There is a shelf in the bottom third of most of the cabinets, use those for line drivers, modems, etc.

6. Line drivers can be wired with an RJ45 terminated cable so that each line driver can be close to one of the routers and connected through the patch panels (ask me if you need help with this).

7. Completely remove unneeded cables when you remove a piece of equipment, don't leave them hanging there.

8. Install light equipment towards the tops of the cabinets, thus leaving the lower spaces available in case someone needs to install a big box.

9. Use green cables (the comms color), if we need more of a certain size -- request them.

10. If you put project specific labels on stuff, remove them when your project is over.

11. If you put funky, test, configs on stuff -- then put them back to "normal" (i.e. save the original config and then put it back, or make a new config following ANet and comms standards) when you are done with them, unless it is going into production and we want to keep an example in the lab.

12. If you plug the line from one of the terminal servers into a different device's console port -- change the config on the terminal server to reflect the change.

13. Update the map (projects/testlab/testlab.ppt)!