See The Examples For More Information

De Transcription | Bibliothèque patrimoniale numérique Mines ParisTech
Révision datée du 21 octobre 2025 à 09:52 par BrigetteW58 (discussion | contributions) (Page créée avec « <br>SISF-based mostly device tracking may be enabled manually (by using system-monitoring commands), or programmatically (which is the case when offering gadget monitoring... »)
(diff) ← Version précédente | Voir la version actuelle (diff) | Version suivante → (diff)
Aller à : navigation, rechercher


SISF-based mostly device tracking may be enabled manually (by using system-monitoring commands), or programmatically (which is the case when offering gadget monitoring companies to other options). SISF-Based machine monitoring is disabled by default. You may allow it by defining a device monitoring coverage and attaching the policy to a selected goal. The goal may very well be an interface or a VLAN. Option 1: Apply the default device monitoring policy to a target. Enter the system-tracking command in the interface configuration mode or iTagPro portable in the VLAN configuration mode. The system then attaches the default policy it to the interface or VLAN. Note The default policy is a constructed-in coverage with default settings; you can not change any of the attributes of the default coverage. So as to have the ability to configure machine tracking coverage attributes it's essential to create a custom coverage. See Option 2: Create a custom policy with customized settings. Option 2: Create a customized coverage with custom settings. Enter the gadget-tracking coverage command iTagPro shop in world configuration mode and enter a custom coverage identify.



The policy that's created, and its settings, are system-outlined. Configurable coverage attributes are available in the gadget tracking configuration mode (config-machine-tracking) and differ from one release to another. If you try to modify an attribute that isn't configurable, the configuration change is rejected and an error message is displayed. For launch-particular information about programmatically created policies, see Programmatically Enabling SISF-Based Device Tracking in Cisco IOS XE within the required model of the document. Starting with Cisco IOS XE Denali 16.1.1, the prevailing IPv6 snooping and IP Device Tracking (IPDT) commands have corresponding SISF-based mostly system-monitoring commands that permit you to use your configuration to each IPv4 and smart item locator IPv6 tackle households. After you will have upgraded from a Cisco IOS XE 3.x.x release to a Cisco IOS XE 16.x.x launch, enter the gadget-tracking upgrade-cli to transform legacy IPDT and IPv6 Snooping commands to SISF-primarily based gadget monitoring commands. After you run the command, solely the brand new device-tracking commands can be found on your machine and the legacy commands usually are not supported.



Based on the legacy configuration that exists in your gadget, the gadget-monitoring upgrade-cli command upgrades your CLI differently. Consider the following configuration scenarios and iTagPro official the corresponding migration outcomes earlier than you migrate your existing configuration. You can't configure a mix of the outdated IPDT and IPv6 snooping CLI with the brand new SISF-primarily based machine-monitoring CLI. In case your machine has solely IPDT configuration, working the machine-monitoring improve-cli command converts the configuration to use the new SISF coverage that's created and attached to the interface. You possibly can then replace this SISF coverage. In the event you continue to make use of 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 system. On a system with present IPv6 snooping configuration, the old IPv6 Snooping commands can be found for additional configuration. Use the device-monitoring improve-cli command to convert all your legacy configuration to the brand new SISF-based gadget monitoring commands. After conversion, solely the brand new device tracking commands will work in your system.



Use the legacy IPv6 Snooping commands in your future configuration and don't run the device-tracking improve-cli command. With this option, only the legacy IPv6 Snooping commands are available in your system, and you cannot use the brand new SISF-primarily based gadget tracking CLI commands. On a system that has both legacy IPDT configuration and IPv6 snooping configuration, you'll be able to convert legacy commands to the SISF-based mostly system monitoring CLI commands. However, note that only one snooping coverage will be connected to an interface, and the IPv6 snooping coverage parameters override the IPDT settings. If your machine has no legacy IP Device Tracking or IPv6 Snooping configurations, you need to use solely the new SISF-based device tracking commands for all of your future configuration. The legacy IPDT commands and IPv6 snooping commands should not available. Starting from Cisco IOS XE Denali 16.3.1, the ip dhcp snooping vlan vlan command creates a gadget monitoring policy programmatically, to support the IEEE 802.1X, net authentication, Cisco TrustSec and IPSG options.



The programmatically created policy tracks each IPv4 and IPv6 purchasers. Make sure that this command iTagPro product is configured, if you are utilizing any of the aforementioned options. Table Table 1 shows legacy IPDT after which the IPv6 snooping commands they're converted to - if the gadget-tracking improve-cli command (international configuration mode) isn't executed. Table Table 2 displays legacy IPDT after which the SISF-primarily based gadget-monitoring commands that the system converts them to, when you've got executed the machine-tracking upgrade-cli command. Set to the default worth, and can't be changed. Set to the default worth, ItagPro 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 worth, and can't be changed3. Set to the default behaviour and smart item locator can't be modified. Enters the global configuration mode. Specifies the interface and enters the interface configuration mode. The machine tracking coverage shall be hooked up to the desired interface.