See The Examples For More Information: Difference between revisions
Created page with "<br>SISF-based device monitoring could be enabled manually (by utilizing gadget-tracking commands), or programmatically (which is the case when providing system tracking providers to other options). SISF-Based system monitoring is disabled by default. You may allow it by defining a device tracking coverage and attaching the policy to a selected target. The target could be an interface or a VLAN. Option 1: Apply the default device tracking coverage to a goal. Enter the sy..." |
(No difference)
|
Latest revision as of 19:07, 19 September 2025
SISF-based device monitoring could be enabled manually (by utilizing gadget-tracking commands), or programmatically (which is the case when providing system tracking providers to other options). SISF-Based system monitoring is disabled by default. You may allow it by defining a device tracking coverage and attaching the policy to a selected target. The target could be an interface or a VLAN. Option 1: Apply the default device tracking coverage to a goal. Enter the system-monitoring command iTagPro website within the interface configuration mode or within the VLAN configuration mode. The system then attaches the default coverage it to the interface or VLAN. Note The default policy is a built-in coverage with default settings; you can't change any of the attributes of the default coverage. So as to be able to configure system tracking policy attributes it's essential to create a custom coverage. See Option 2: Create a custom coverage with custom settings. Option 2: Create a custom coverage with customized settings. Enter the machine-tracking policy command in world configuration mode and enter a custom coverage identify.
The coverage that is created, and its settings, iTagPro website are system-outlined. Configurable coverage attributes can be found within the system tracking configuration mode (config-gadget-tracking) and differ from one release to another. For those who try to change an attribute that's not configurable, the configuration change is rejected and an error message is displayed. For release-particular information about programmatically created policies, see Programmatically Enabling SISF-Based Device Tracking in Cisco IOS XE within the required model of the doc. Starting with Cisco IOS XE Denali 16.1.1, the present IPv6 snooping and IP Device Tracking (IPDT) commands have corresponding SISF-based gadget-tracking commands that enable you to apply your configuration to both IPv4 and IPv6 deal with households. After you've gotten upgraded from a Cisco IOS XE 3.x.x launch to a Cisco IOS XE 16.x.x release, enter the device-monitoring upgrade-cli to transform legacy IPDT and IPv6 Snooping commands to SISF-based mostly gadget tracking commands. After you run the command, only the brand ItagPro new system-tracking commands can be found on your device and the legacy commands are not supported.
Based on the legacy configuration that exists on your system, the gadget-monitoring improve-cli command upgrades your CLI otherwise. Consider the following configuration scenarios and the corresponding migration outcomes before you migrate your existing configuration. You can not configure a mixture of the outdated IPDT and IPv6 snooping CLI with the brand new SISF-primarily based gadget-tracking CLI. In case your system has solely IPDT configuration, working the machine-monitoring upgrade-cli command converts the configuration to make use of the new SISF policy that is created and attached to the interface. You can then update this SISF policy. Should you proceed to make use of the legacy commands, this restricts you to function in a legacy mode where only the legacy IPDT and iTagPro smart device IPv6 snooping commands are available on the device. On a machine with present IPv6 snooping configuration, the old IPv6 Snooping commands are available for additional configuration. Use the system-monitoring improve-cli command to transform all of your legacy configuration to the brand new SISF-primarily based machine tracking commands. After conversion, only the new device monitoring commands will work on your device.
Use the legacy IPv6 Snooping commands in your future configuration and do not run the machine-monitoring upgrade-cli command. With this feature, only the legacy IPv6 Snooping commands can be found on your machine, and you can't use the new SISF-based mostly gadget monitoring CLI commands. On a device that has both legacy IPDT configuration and iTagPro website IPv6 snooping configuration, you may convert legacy commands to the SISF-primarily based device tracking CLI commands. However, observe that only one snooping coverage will be connected 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 should use solely the new SISF-based system tracking commands for all your future configuration. The legacy IPDT commands and IPv6 snooping commands usually are not accessible. Starting from Cisco IOS XE Denali 16.3.1, the ip dhcp snooping vlan vlan command creates a system tracking policy programmatically, to support the IEEE 802.1X, internet authentication, Cisco TrustSec and IPSG features.
The programmatically created coverage tracks both IPv4 and IPv6 clients. Be sure that this command is configured, if you're using any of the aforementioned features. Table Table 1 shows legacy IPDT after which the IPv6 snooping commands they're converted to - if the gadget-monitoring upgrade-cli command (world configuration mode) isn't executed. Table Table 2 shows legacy IPDT after which the SISF-based mostly system-tracking commands that the system converts them to, if you have executed the device-monitoring improve-cli command. Set to the default value, and cannot be modified. Set to the default worth, and cannot be changed1. Set to the default habits, and can't be modified. Set to the default value, and cannot be changed. Set to the default worth, and can't be changed3. Set to the default behaviour and iTagPro support can't be changed. Enters the global configuration mode. Specifies the interface and enters the interface configuration mode. The gadget monitoring policy can be connected to the required interface.