Model Features
The model implements the following protocol features.
Table 122: IPv6 Model Features
| Feature | Description | Supported In: Flow Analysis | Supported In: DES |
|---|---|---|---|
| IPv6 address specification | IPv6 link-local addresses and global addresses can be specified for individual IP interfaces. You can manually specify IPv6 addresses or you can use the Protocols > IP > IPv6 > Auto Assign IPv6 Addresses menu operation to automatically assign addresses before running a simulation. You can view the configured addresses in a network by creating a user defined report (UDR). Stateless address auto-configuration is also supported for host nodes running IPv6. |
Yes | Yes |
| Static routing table | Static routes to IPv6 destinations can be configured on router nodes (in the IP > IPv6 Configuration > Static Routing Table attribute). | Yes | Yes |
| Access control lists | Access control lists can be configured on router nodes (in the IP > IPv6 Configuration > ACL Configuration attribute). | Yes | No |
| Prefix lists | Prefix lists can be configured on router nodes (in the IP > IPv6 Configuration > Prefix List Configuration attribute). | Yes | No |
| Route maps | Access control lists can be configured on router nodes (in the IP > IPv6 Configuration > Local Policy attribute). | Yes | No |
| Neighbor discovery | Neighbor discovery is configurable on a per-interface basis on all router and host nodes. | No | Yes |
| IPv6 tunnels | The following types of IPv6 tunnels are supported. - Manual - Automatic - Automatic 6to4 - 6PE - 6VPE |
Yes | Yes |
| Routing protocols | The model supports the following routing protocols within an IPv6 network: - RIPng - OSPFv3 - IS-IS - BGP - AODV, DSR, and OLSR (MANET routing protocols) |
Yes for OSPFv3, IS-IS, and BGP No for other routing protocols |
Yes |
| Application support | All of the application models (standard network applications and the custom application) also work with the IPv6 model. | No | Yes |
| Demand support | You can configure traffic demands between IPv6 interfaces, including mobile IPv6 interfaces, using the standard ip_traffic_flow demand. Both endpoints must be configured as IPv6 interfaces (or IPv4 interfaces) but you cannot configure a demand between an IPv6 interface and an IPv4 interface. | Yes | Yes |
| IPv6 ping | Ping packets can be sent to IPv6 destinations. The model also includes an option to record the route chosen by the ping packet. | No | Yes |
| IPv6 Path MTU Discovery | IPv6 Path MTU Discovery is supported per RFC-1981. See IPv6 Path MTU Discovery for more information. |
No | Yes |
| Layer-2 support | The model supports IPv6 on all standard layer-2 protocols (such as Ethernet, Token Ring, ATM, WLAN, and Frame Relay). | Yes | Yes |
| QoS support | All of the IP QoS features supported for IPv4 are also modeled for IPv6. For more information about the IP QoS model, see Chapter 16 "IP QoS" on page 1. |
No | Yes |
| Mobile IPv6 | Mobile nodes can connect within and across IPv6 networks. | No | Yes |
| IPv6 address assignment utility for sub-interfaces | This utility is launched from Protocols > IP > IPv6 > Assign IPv6 Addresses to Sub-interfaces on Selected Nodes. The utility uses the existing IPv4 address and mask to select the IPv6 addresses. The IPv6 prefix is constructed from the IPv4 prefix, and the IPv6 host bits are constructed from the IPv4 host bits. The standard IP auto-address assignment feature does not work on sub-interfaces. So this utility can be used in situations where there is a v4 baseline with sub-interface configuration |
||
| IPv6 6to4 tunnel configuration utility | This utility is launched from Protocols > IP > IPv6 > Create 6to4 Tunnels on Selected Nodes. For more information, see 6to4 Tunnels. |
Table 123: Summary of IPv6 Support in Riverbed Modeler
| Technology | Supports IPv6 | Special Requirements |
|---|---|---|
| Device Configuration Import | Yes | None |
| Import from NetCollector | Yes | None |
| NetDoctor | No | None |
| Flow Analysis | Yes | License for IPv6 Planning and Operations |
| Discrete event simulation | Yes | License for IPv6 for R&D |