Security Router Pod - Quick Reference Page

This quick reference page provides a summary of the specifications of this topology. For a complete reference including installation details, please refer to the Security Router Pod Planning and Installation Guide

Topology	Supports	Documentation
	FNSR 1.x	Planning and Installation Guide

Lab Topology

Lab Device Requirements

Lab devices are part of the topology and users can interact with them either directly through the console or network.

Hardware compatibility with NETLAB+ does not guarantee the compatibility of labs. Please check the Academy curriculum, NDG pod guides, and lab support pages for specific hardware and IOS requirements.

Other equipment may work if it is supported by NETLAB+ and can meet the minimum requirements for feature sets, interfaces, IOS, RAM, and Flash.

ROUTER1 and ROUTER2

VPN Router bundles ship by default with 12.3(4)T or later. Do not go above the 12.3(7)T image, as the IOS Intrusion Detection commands have changed significantly in version 12.3(8)T. If the router has 12.3(8)T or later, the image must be downgraded.

Security Device Manager (SDM) version 1.2 or later will be required for labs in Modules 2 through 7. VPN router bundles ship by default with SDM.

¹The 2621 model router will work for all labs excluding SDM labs once they have been upgraded from 16F/32DRAM to 16F/64DRAM.

Router Backbone (RBB)

RBB is a static router. It is not accessible or configurable by users. However, it is part of the topology so users can indirectly interact with it (i.e. ping, trace, RIP, etc.).

You can implement RBB in one of two ways:

1. A separate standalone RBB router for each Security Router Pod
2. Simulating RBB for two or more security pods by utilizing multi-VRF on one physical router.

Configuration of each option is covered in detail in section 8 of the Planning and Installation Guide.

Backbone Server / VPN Client PC

The Backbone Server (BB) provides services that are typically provided by Internet servers.

The FNS curriculum provides two options for the backbone server (BB):

• Option 1 - a dedicated BB server.
• Option 2 - one SuperServer with Intel Pro Server NIC with VLAN support, serving as several PCs in the pod.

NETLAB+ currently does not support the SuperServer (option 2). You should use VMware GSX (or other virtualization) products to simulate several machines. Virtual machines have their own routing tables, which avoids asymmetric routing problems in the pod.

FNSR refers to a Client-to-IOS Firewall configuration. NETLAB+ does not have a pod type for this topology. However, you may also configure the Backbone Server (BB) for direct access, which means that users can login and interact with the Windows interface.

By loading the Cisco VPN client software on BB, users can use the NETLAB+ Security Router Pod for client-to-IOS firewall labs. Direct access also allows BB to be used as an external PC for labs that require testing from an outside network (i.e. simulating the Internet).

Router Interfaces

The NETLAB+ interface name translation feature is supported on this pod type. This may influence the selection of modular interface cards and slot placement within the router. Please review the expected interface names for each router.

Virtual PC Support

Remote PCs are implemented by integrating with 3rd party virtualization products. The NETLAB+ documentation library includes several guides with extensive detail on the implementation of virtualization with your NETLAB+ system.

The following operating system choices are typical based on the curriculum. These choices are not mandatory; you can make substitutions provided that:

1. Your choice of NETLAB+ supported virtualization product supports the operating system (as a guest).
2. Your choices are compatible with the curriculum.

The Security Router Pod includes placeholders for 5 remote PCs.

Control Device Requirements

Control devices provide internal connectivity, console access, and managed power. Control devices are dynamically managed by NETLAB+ and are not accessible or configurable by end users.

• Control switches provide connectivity between devices in the pod.
• Access server lines provide console connections to lab equipment.
• Switched outlets provide managed electrical power, allowing NETLAB+ and users to turn lab equipment on and off.

Control Device Requirements for the Security Router Pod

The Security Router Pod requires 10 Consecutive Ports + up to 5 Reserved Ports on a control switch.

The Security Router Pod requires 2 async ports on an access server.

The Security Router Pod requires 2 outlets on a switched outlet device.

For More Information

Please refer to the Security Router Pod Plan ning and Installation Guide