SISF-based machine tracking may be enabled manually (by utilizing gadget-tracking commands), or programmatically (which is the case when offering device tracking services to different features). SISF-Based device monitoring is disabled by default. You possibly can allow it by defining a gadget monitoring policy and attaching the policy to a particular goal. The goal may very well be an interface or a VLAN. Option 1: Apply the default system monitoring coverage to a target. Enter the device-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 VLAN. Note The default coverage is a built-in policy with default settings; you cannot change any of the attributes of the default coverage. In order to have the ability to configure system monitoring coverage attributes you should create a custom coverage. See Option 2: Create a custom coverage with customized settings. Option 2: anti-loss gadget Create a custom coverage with custom settings. Enter the device-monitoring policy command in international configuration mode and anti-loss gadget enter a custom policy identify.

The policy that is created, and its settings, are system-outlined. Configurable policy attributes are available in the device tracking configuration mode (config-device-tracking) and fluctuate from one launch to a different. For those who strive to switch an attribute that is not configurable, the configuration change is rejected and an error message is displayed. For launch-specific 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 existing IPv6 snooping and IP Device Tracking (IPDT) commands have corresponding SISF-based anti-loss gadget-tracking commands that allow you to apply your configuration to both IPv4 and IPv6 tackle families. After you have got upgraded from a Cisco IOS XE 3.x.x release to a Cisco IOS XE 16.x.x launch, enter the machine-monitoring improve-cli to convert legacy IPDT and IPv6 Snooping commands to SISF-based mostly machine monitoring commands. After you run the command, only the new gadget-tracking commands are available on your system and the legacy commands should not supported.

Based on the legacy configuration that exists in your system, the gadget-monitoring improve-cli command upgrades your CLI in another way. Consider the following configuration situations and the corresponding migration results before you migrate your existing configuration. You cannot configure a mix of the previous IPDT and IPv6 snooping CLI with the new SISF-based device-tracking CLI. If your device has only IPDT configuration, working the system-monitoring improve-cli command converts the configuration to use the brand new SISF policy that's created and iTagPro features connected to the interface. You may then replace this SISF policy. For iTagPro support those who continue to make use of the legacy commands, anti-loss gadget this restricts you to function in a legacy mode where solely the legacy IPDT and IPv6 snooping commands are available on the machine. On a device with present IPv6 snooping configuration, the outdated IPv6 Snooping commands are available for further configuration. Use the gadget-tracking improve-cli command to convert all your legacy configuration to the new SISF-based device monitoring commands. After conversion, iTagPro smart device only the new machine monitoring commands will work on your system.

Use the legacy IPv6 Snooping commands on your future configuration and anti-loss gadget do not run the machine-tracking improve-cli command. With this option, solely the legacy IPv6 Snooping commands can be found in your system, anti-loss gadget and you cannot use the brand new SISF-based system tracking CLI commands. On a system that has each legacy IPDT configuration and IPv6 snooping configuration, you can convert legacy commands to the SISF-based device monitoring CLI commands. However, be aware 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 gadget has no legacy IP Device Tracking or IPv6 Snooping configurations, you need to use only the brand new SISF-based mostly machine monitoring commands for all your future configuration. The legacy IPDT commands and iTagPro device IPv6 snooping commands are usually not accessible. Starting from Cisco IOS XE Denali 16.3.1, the ip dhcp snooping vlan vlan command creates a machine tracking coverage programmatically, to support the IEEE 802.1X, web authentication, ItagPro Cisco TrustSec and IPSG features.

The programmatically created coverage tracks each IPv4 and IPv6 purchasers. Ensure that this command is configured, in case you are using any of the aforementioned options. Table Table 1 shows legacy IPDT after which the IPv6 snooping commands they're transformed to - if the machine-tracking improve-cli command (world configuration mode) just isn't executed. Table Table 2 displays legacy IPDT after which the SISF-based machine-tracking commands that the system converts them to, if in case you have executed the system-monitoring improve-cli command. Set to the default value, and can't be modified. Set to the default worth, and cannot be changed1. Set to the default conduct, and can't be modified. Set to the default value, and cannot be modified. Set to the default value, and can't be changed3. Set to the default behaviour and can't be modified. Enters the global configuration mode. Specifies the interface and enters the interface configuration mode. The machine monitoring policy will be connected to the required interface.