Design Reference
Table Of Contents
- Contents
- Chapter 1: Introduction
- Chapter 2: New in this release
- Chapter 3: Network design fundamentals
- Chapter 4: Hardware fundamentals and guidelines
- Chapter 5: Optical routing design
- Chapter 6: Platform redundancy
- Chapter 7: Link redundancy
- Chapter 8: Layer 2 loop prevention
- Chapter 9: Spanning tree
- Chapter 10: Layer 3 network design
- Chapter 11: SPBM design guidelines
- Chapter 12: IP multicast network design
- Multicast and VRF-Lite
- Multicast and MultiLink Trunking considerations
- Multicast scalability design rules
- IP multicast address range restrictions
- Multicast MAC address mapping considerations
- Dynamic multicast configuration changes
- IGMPv3 backward compatibility
- IGMP Layer 2 Querier
- TTL in IP multicast packets
- Multicast MAC filtering
- Guidelines for multicast access policies
- Multicast for multimedia
- Chapter 13: System and network stability and security
- Chapter 14: QoS design guidelines
- Chapter 15: Layer 1, 2, and 3 design examples
- Chapter 16: Software scaling capabilities
- Chapter 17: Supported standards, RFCs, and MIBs
- Glossary
Tunneling
The switch supports manually configured IPv6-in-IPv4 tunnels per RFC4213.
A manually-configured tunnel is equivalent to a permanent link between two IPv6 domains over an
IPv4 backbone.
Use tunnels to provide stable, secure communications between two edge routers, an end system
and an edge router, or to provide a connection to remote IPv6 networks.
Configure an IPv6 address on the tunnel interface.
Configure an IPv4 address on the tunnel source and destination.
Note:
The host or router at each end of the tunnel must be a dual-stack device.
The following figure demonstrates an IPv6 over IPv4 tunnel.
Figure 31: IPv6 over IPv4 tunneling
The tunnel in the preceding figure exists only between two VSP devices.
If you add new devices, you must configure additional tunnels.
VRRP
For IPv6 hosts on a LAN to learn about one or more default routers, IPv6-enabled routers send
router advertisements using the IPv6 Neighbor Discovery (ND) protocol. The routers multicast these
router advertisements every few minutes.
The ND protocol includes a mechanism called Neighbor Unreachability Detection to detect the
failure of a neighbor node (router or host) or the failure of the forwarding path to a neighbor. Nodes
can monitor the health of a forwarding path by sending unicast ND neighbor solicitation messages to
the neighbor node. To reduce traffic, nodes only send neighbor solicitations to neighbors to which
they are actively sending traffic, and only after the node receives no positive indication that the
neighbors are up for a period of time. Using the default ND parameters, it takes a host
approximately 38 seconds to learn that a router is unreachable before it switches to another default
router. This delay is very noticeable and causes some transport protocol implementations to
timeout.
While you can decrease the ND unreachability detection period by modifying the ND parameters,
the lowest limit that can be achieved is 5 seconds, with the added downside of significantly
IPv6
January 2015 Network Design Reference for Avaya VSP 4000 Series 71
Comments? infodev@avaya.com