A number of Cisco Bloggers have talked about making labs available for others to use. However, part of what will be needed is some conventions to make these labs work for the largest number of people.
Following Ivan Pepelnjak posting on Private Domain Names, and an earlier posting that I made on Reserved IP Address for Testing I believe we have perfect combination for DNS and IP addresses for building live test environments, that will work for Open Source lab scenarios.
Reserved Domain Names
From RFC2606 on Reserved Domain Names:
To safely satisfy these needs, four domain names are reserved as listed and described below.
“.test” is recommended for use in testing of current or new DNS related code.
“.example” is recommended for use in documentation or as examples.
IP Range Allocated for Testing
198.18.0.0/15 – This block has been allocated for use in benchmark tests of network interconnect devices. Its use is documented in [RFC 2544].
Use in LAB networks
When I build a test network in a Corporate Networks, I am looking for an Address range that will never have an impact on the live system. And if some sort of configuration accident occurs where traffic is introduced into the corporate system, I need to be able to clearly identify where this traffic is coming from. Unique IP addresses is a solution to this.
The use of a DNS naming convention that clearly identifies test traffic, and also the use of clearly defined range for test IP addresses. The use of .test extensions would allow for the creation of the a DNS range that is unique to a test environment, and be readily identified.
So here is a request to everyone, if you plan to write a lab or develop a testing plan or publish a configuration, consider using these DNS names and IP addresses. This could produce some consistency in our lab scenarios, and make them portable into our corporate test environments, if you like, a first step to an open source look at network labs.
Please leave comments below to show support either for or against. If there is sufficient interest, I have a forum prepared for better discussion. I look forward to hearing from you.
Other Posts in This Series
- Cisco IOS CLI Regex: sh ip bgp in (2nd May 2012)
- IOS CLI Tip: More accurate pipe commands (1st May 2012)
- Cisco Nexus NXOS and Fixing broken “switchto” syntax with alias (18th December 2011)
- show ip eigrp topology all (22nd May 2011)
- Cisco IOS CLI Shortcuts (6th February 2011)
- The poor man's IOS Traffic Generator (19th September 2009)
- IOS: "terminal monitor" on, off - logging to your terminal (17th September 2009)
- IOS: Console, Terminal, Monitor, VTY - what is what ? (16th September 2009)
- IOS: Clearing an interface configuration (13th September 2009)
- IOS: Setting Terminal Window Length (10th September 2009)
- IOS CLI: show run linenum (9th September 2009)
- IOS: Setting the TCP timeout on IOS (14th August 2008)
- IOS: enable and .... disable ? (20th July 2008)
- IOS: Reverse SSH console access - Part 2 (25th June 2008)
- IOS:Open Source Lab DNS and IP addressing (2nd June 2008)
- IOS: Reverse SSH console access (29th May 2008)
- ip tcp timestamp (14th April 2008)
- Cisco ASA and IOS command tip - test aaa-server (18th February 2008)