Campus Networking
This area deals with the campus network itself with the routers and switches as its basic building block. Requirements both to layer 2 and layer 3 are covered. Recommendations for a redundant design are given. There is a particular emphasis on guidelines for implementing IPv6 on campus. Light paths on campus are also dealt with.

Recommendations for a Redundant Campus Network     
For a campus core network, a structure consisting of two equipment rooms with completely separate electrical and cooling systems is recommended. The fibre-optic structure should be redundant. The core network should consist of at least two core switches, configured with redundant BGP connection to the NREN. There should also be redundant connections to distribution and/or edge switches. In the distribution network, the use of Rapid Spanning Tree (IEEE 802.1w) is recommended. Servers should be connected redundantly to the network using two different switches.

Recommended Resilient Campus Network Design     
This document describes how to set up a fully resilient network within a campus. The recommendation for standards and proprietary technologies are discussed. Descriptions of resilient network parts, including the core network, distribution switches and resilient server connections are described in this document. A testbed setup, using HP equipment is also provided.

Requirements for EDGE Devices in a Campus Network     
This document presents a compilation of issues that should be taken into consideration when purchasing an EDGE device for a campus network and connecting it to the country or regional network. Pros and cons of topology alternatives are discussed.

Recommended Configuration of Switches in Campus Networks    
This document presents a recommendation regarding the configuration of switches in campus networks. Layer 2 and Layer 2+ functions are covered, but not Layer 3 (routing). The recommendation is generic. A number of configurations intended for supplier-specific implementations will support the recommendation. Note that this document does not deal with the design of campus networks, but focuses on the individual components and their configuration.

Configuration of HP ProCurve Devices in a Campus Environment   
This document describes the basic configuration of HP switches in a campus environment. Switches have a large number of configuration options, of which only a subset is used for an ordinary configuration. This document attempts to summarise the most common settings of the ProCurve switches, as they are used in campus networks. The individual configuration examples are arranged for cutting and pasting while configuring a real switch.

Evaluating the Progress Towards IPv6 Implementation    
This document establishes a means of evaluating the level of readiness for IPv6 traffic that is demonstrated by a campus network. The implementation of IPv6 can be evaluated by a number of approaches, none of which are fully objective. The chosen method is based on a classification of used services and the complexity of the subnets.  Several levels of IPv6 readiness are defined. This method is used by CESNET as a means of ranking the various Czech campus networks. Other NRENs should also consider adopting the same methodology.

IPv6 Address Space
The initial motivation to create the IPv6 protocol was the need to extend the IP address space. The hierarchisation of addresses has the potential to enable much more effective management of routing information at a global level, which has been disrupted by the concept of provider-independent address allocation. At the end-user network level, IPv6 offers completely new possibilities for creating addresses in end-user systems. The document describes network structure, the ways of creating IPv6 addresses in end-user networks, and the methods used to connect home, corporate and campus networks.

IPv6 Autoconfiguration         
IPv6 autoconfiguration represents perhaps the most difficult story in the whole IPv6 standardisation process. Ambiguities and delays in the inclusion of recursive DNS servers into mechanisms of stateless configuration have led to many alternative solutions.  It is not clear what type of autoconfiguration will eventually dominate. This creates complications for hardware and software manufacturers, who do not know what standard to implement in their products. The document details the options for autoconfiguration in current operating systems and gives an overview of deployment of these options in IPv6 networks.

IPv6 Configuration on HP ProCurve Switches    
This document presents a detailed look at the implementation of IPv6 support in HP ProCurve switches. In November 2010, HP introduced IPv6 support for their ProCurve switches. IPv6 routing is carried out in hardware, and the OSPVv3 routing protocol is supported. The document also gives examples of IPv6 configuration, which is not a very complicated process.

IPv6 Migration Guide
This  document  contains  a  high-level  description  of  procedures that  enable  a  controlled migration to IPv6 in an organisation currently using IPv4. The working order suggested in this  document  can  be  used,  for  example,  as  a  framework  for  an  IPv6  project plan,  or otherwise as support in the planning of IPv6 migration. The starting point of this document was that the IPv4 protocol will be eventually phased out completely.

Support for the operation of IPv6 multicast and anycast
Multicast  support  under  the  IPv6  protocol  is, in  many  ways, similar  to  multicast  under  IPv4.  However, the additional address length has enabled the integration of some improvements. This document examines IPv6 multicasting in detail.

Use of Lightpaths in Campus Networks
One of the most common and popular applications for lightpaths is to connect remote offices to the main campus network. As the lightpath is a secure end-to-end connection, the remote office can be connected to be part of the main campus intranet. This document provides a description of lightpaths, and a checklist for lightpath implementation is also included.

Light Path Deployment, Guide for IT Support
The purpose of this document is to support IT personnel who are implementing a light path connection in the Funet network. This document contains a step-by-step description on what should be taken into consideration in the deployment of a light path. A light path is a dedicated data transfer channel between two endpoints. Light paths are separately priced additional services provided by Funet

Virtualisation of critical network services
This document describes a way to virtualise network servers that are required for the operation of a large campus network. This includes DHCP, DNS, VPN, email, network monitoring, and radius. The document is focused on the requirements to be considered when choosing the appropriate hardware for the job, with emphasis on the price/performance ratio, while maintaining all the benefits of the Vmware vSphere virtualisation platform. Configuration of network devices, iSCSI storage, and VMware vSphere hypervisors is covered. Practical experience and pitfalls are discussed. The benefits of virtualisation are emphasized.
CBP Documents
Campus Best Practice documents available to download

Physical infrastructure
Campus networking
Network monitoring
Real-time communications