MigratingfromLegacyIPDTandIPv6SnoopingtoSISF-BasedDeviceTracking Based on the legacy configuration that exists on your device, the device-tracking upgrade-cli command upgrades your CLI differently. Consider the following configuration scenarios and the corresponding migration results before you migrate your existing configuration. You cannot configure a mix of the old IPDT and IPv6 snooping CLI with the SISF-based device tracking CLI. Note Only IPDT Configuration Exists If your device has only IPDT configuration, running the device-tracking upgrade-cli command converts the configuration to use the new SISF policy that is created and attached to the interface.
You can then update this SISF policy. If you continue to use the legacy commands, this restricts you to operate in a legacy mode where only the legacy IPDT and IPv6 snooping commands are available on the device. Only IPv6 Snooping Configuration Exists On a device with existing IPv6 snooping configuration, the old IPv6 Snooping commands are available for further configuration. The following options are available: • (Recommended) Use the device-tracking upgrade-cli command to convert all your legacy configuration to the new SISF-based device tracking commands. After conversion, only the new device tracking commands will work on your device.
Configuring Switch Integrated Security Features Migrating from Legacy IPDT and IPv6 Snooping to SISF-Based Device Tracking Command or Action Purpose Step 8 end Example: Device(config-if)# end Exits the interface configuration mode and enters the privileged EXEC mode. Step 9 show running-config interface type number Example: Device# show running-config interface gigabitethernet 1/1/4 Building configuration... Current configuration : 71 bytes ! interface GigabitEthernet1/1/14 source template template w sisf _ _ end Displays the contents of the running configuration. Configuring Switch Integrated Security Features 29