SISF-primarily based machine tracking might be enabled manually (through the use of system-tracking commands), or programmatically (which is the case when providing machine tracking companies to other features). SISF-Based machine tracking is disabled by default. You'll be able to allow it by defining a device monitoring coverage and attaching the coverage to a particular target. The goal might be an interface or a VLAN. Option 1: Apply the default gadget tracking coverage to a goal. Enter the gadget-monitoring command in the interface configuration mode or in the VLAN configuration mode. The system then attaches the default coverage it to the interface or iTagPro smart device VLAN. Note The default policy is a built-in policy with default settings; you cannot change any of the attributes of the default coverage. So as to have the ability to configure gadget tracking policy attributes you must create a customized policy. See Option 2: Create a custom coverage with custom settings. Option 2: Create a customized policy with customized settings. Enter the machine-monitoring policy command in world configuration mode and enter a customized policy name.

The coverage that is created, and its settings, are system-defined. Configurable policy attributes are available in the gadget tracking configuration mode (config-system-tracking) and iTagPro portable fluctuate from one release to another. In case you attempt to modify an attribute that is not configurable, the configuration change is rejected and an error message is displayed. For iTagPro USA launch-particular information about programmatically created insurance policies, see Programmatically Enabling SISF-Based Device Tracking in Cisco IOS XE in the required version of the document. Starting with Cisco IOS XE Denali 16.1.1, the present IPv6 snooping and IP Device Tracking (IPDT) commands have corresponding SISF-primarily based system-monitoring commands that allow you to apply your configuration to each IPv4 and IPv6 tackle families. After you could have upgraded from a Cisco IOS XE 3.x.x launch to a Cisco IOS XE 16.x.x launch, enter the system-monitoring upgrade-cli to transform legacy IPDT and IPv6 Snooping commands to SISF-based mostly gadget monitoring commands. After you run the command, solely the new device-tracking commands can be found in your device and the legacy commands usually are not supported.

Based on the legacy configuration that exists on your device, iTagPro portable the gadget-tracking improve-cli command upgrades your CLI otherwise. Consider the next configuration eventualities and the corresponding migration results earlier than you migrate your existing configuration. You can not configure a mixture of the old IPDT and IPv6 snooping CLI with the brand new SISF-primarily based gadget-tracking CLI. In case your device has only IPDT configuration, working the system-monitoring upgrade-cli command converts the configuration to make use of the brand new SISF coverage that is created and attached to the interface. You may then update this SISF coverage. If you proceed to use the legacy commands, this restricts you to function in a legacy mode the place only the legacy IPDT and IPv6 snooping commands are available on the device. On a system with existing IPv6 snooping configuration, the previous IPv6 Snooping commands are available for further configuration. Use the machine-tracking upgrade-cli command to convert all your legacy configuration to the new SISF-based gadget monitoring commands. After conversion, only the new machine monitoring commands will work on your system.

Use the legacy IPv6 Snooping commands for iTagPro geofencing your future configuration and don't run the gadget-tracking improve-cli command. With this feature, only the legacy IPv6 Snooping commands can be found in your gadget, and you can't use the brand new SISF-based device tracking CLI commands. On a system that has both legacy IPDT configuration and iTagPro portable IPv6 snooping configuration, you'll be able to convert legacy commands to the SISF-based mostly machine tracking CLI commands. However, notice that just one snooping policy could be hooked up to an interface, and the IPv6 snooping policy parameters override the IPDT settings. In case your system has no legacy IP Device Tracking or IPv6 Snooping configurations, you need to use solely the brand new SISF-based mostly system monitoring commands for all of your future configuration. The legacy IPDT commands and IPv6 snooping commands aren't available. Starting from Cisco IOS XE Denali 16.3.1, the ip dhcp snooping vlan vlan command creates a gadget tracking policy programmatically, to help the IEEE 802.1X, web authentication, Cisco TrustSec and ItagPro IPSG features.

The programmatically created coverage tracks each IPv4 and IPv6 purchasers. Be certain that this command is configured, in case you are utilizing any of the aforementioned options. Table Table 1 displays legacy IPDT after which the IPv6 snooping commands they are transformed to - if the machine-tracking improve-cli command (international configuration mode) isn't executed. Table Table 2 shows legacy IPDT after which the SISF-based device-tracking commands that the system converts them to, ItagPro when you've got executed the machine-monitoring improve-cli command. Set to the default value, and can't be changed. Set to the default worth, and can't be changed1. Set to the default behavior, and cannot be changed. Set to the default value, and can't be changed. Set to the default worth, and cannot be changed3. Set to the default behaviour and cannot be changed. Enters the global configuration mode. Specifies the interface and enters the interface configuration mode. The device tracking coverage will probably be hooked up to the desired interface.