Table Of Contents

Support for IPv6

Understanding IPv6

Viewing IPv6 Addresses Report

Interpreting IPv6 Addresses Report

Support for IPv6

---

This chapter describes the IPv6 support provided in Campus Manager 4.0. It contains the following topics:

•Understanding IPv6

•Viewing IPv6 Addresses Report

•Interpreting IPv6 Addresses Report

Understanding IPv6

Campus Manager 4.0 support for IPv6 includes support for the following network scenarios:

•Devices that may have IPv6 configured on their interfaces, but which have at least one IPv4 interface. Devices are managed using IPv4.

•Hosts running IPv6 are supported in the User Tracking application.

Campus Manager has been updated as follows for IPv6 support:

Discovery Related Changes

No new IPv6 discovery mechanism is included for IPv6 support.

Current discovery also collects IPv6 address and related information from devices, which is leveraged in User Tracking and Path Analysis.

The Discovery related changes for IPv6 support are:

•In the ANIServer.properties file set Discovery.IPv6 to ON.

•Give preference to local device database. Use /etc/inet/ipnodes for IPv6 addresses and use /etc/hosts for IPv4 addresses.

•Do not configure multiple IPv6 addresses on your Solaris server.

•Do not configure your Solaris machine as IPv6 only. Discovery supports IPv4 only or dual stack devices. Discovery does not support IPv6 only devices.

•Check your L3 connectivity from Solaris to other IPv6 enabled devices using traceroute and ping.

•Ensure that all dual stack devices in the network are covered during discovery.

•Seed devices are IPv4. You cannot specify an IPv6 address as a seed device.

•Use name lookup and configure your device for IPv6.

User Tracking Changes

IPv6 support in User Tracking is available on both Solaris and Windows servers. In User Tracking, hosts configured with IPv6 address are discovered and shown in the main table. IPv6 name lookup (reverse name lookup only) is done if IPv4 name lookup fails.

All global unicast addresses are fetched and used for User Tracking computation but link local addresses are dropped.

User Tracking end host reports have an IPv6 format. Select this format to view the IPv6 address, Prefix Length and Prefix of IPv6 enabled devices

User Tracking Ping Sweep Applicability to IPv6 Subnets

Ping Sweep functionality is currently available for Class C or smaller subnets. Since with IPv6 each of the networks can be larger than Class C networks and we cannot determine individual IPv6 addresses that can be present in a given network/sub-network, Ping Sweep is not on any of the IPv6 Subnets.

Path Analysis Changes

Path Analysis is modified to support only the IPv6 source to IPv6 destination through IPv6 network scenario. To accommodate the above requirement the following changes are done:

•Current IP trace Algorithms are reused and modified appropriately to accommodate IPv6 trace.

•Change address resolution is provided to accommodate AAAA type records

Path Related Restrictions

The following IPv6 trace scenarios are not supported:

•IPv6 trace is not supported for CiscoWorks server on Windows platforms due to unavailability of LSR traceroute on Windows platforms

•Configure one global IPv6 address on your Solaris server running ANI.

•Name lookup is done using /etc/inet/ipnodes.

•Map the device name to IPv6 addresses in DNS server or in the local device database [/etc/inet/ipnodes] for the Path traces to run.

•As part of the IPv6 network you can have a tunnel between a Solaris machine running ANI with IPv6 and an IPv6 network.

•You can have tunnels between two IPv6 networks.

•IPv6 name lookup feature is available only on Solaris, Windows 2003 and XP machines. Windows 2000 server(WinSock) does not support this feature

•Routing protocols such as BGP, RIPv6, and OSPFv3 are supported.

Subnet to VLAN Mapping

Sometimes Layer 2 traces are seen in Path Analysis when you run IPv6 Trace. Subnet to Vlan mapping does not contain enough entries to determine the layer 2 trace. IPv4 traces have a UI where you can enter subnet to vlan mapping entries.

At present, IPv6 traces do not have UI for subnet to VLAN mapping.

However, you can overcome this constraint by:

1. Creating anisubnet6.conf file with permissions (r w _ r_ _ _ _ _ )640 under NMSROOT/campus/etc/cwsi/

2. Adding subnet to vlan mapping entries

Format : subnet address|subnetmask|VTP Domain|VLAN

For example: 2001:5:a:1::|64|CMTestLab|vlan2

Topology Changes

The following changes have been made to Topology Service to provide IPv6 support:

•IPv6 filter that lets you highlight the IPv6 devices

•Find option for IPv6 devices

•Table for devices running IPv6.

Viewing IPv6 Addresses Report

You can view IPv6 addresses report for IPv6 enabled devices. To view this report:

---

Step 1 Right-click the LAN Edge View or Layer 2 View from Network Views in the Topology Services window.

Step 2 Click Display View.

The Network Topology window appears.

Step 3 Select an IPv6 enabled device.

Step 4 Right-click the device then select IPv6 Addresses, or click Reports > IPv6 Addresses.

The IPv6 Addresses report appears.

---

Interpreting IPv6 Addresses Report

See Table 11-1 for interpreting the fields in the IPv6 Addresses Report.

Table 11-1 IPv6 Address Report 

Field	Description
Interface Name	Name of the interface
IPv6 Address	IPv6 address of the device
Prefix Length	Length of the prefix
Prefix Address	Prefix portion of the IPv6 address
Address Type	Type of IPv6 address