See the Examples for Extra Information > 자유게시판

SISF-primarily based system monitoring can be enabled manually (through the use of gadget-monitoring commands), or programmatically (which is the case when offering machine tracking services to other features). SISF-Based device monitoring is disabled by default. You possibly can allow it by defining a system monitoring policy and iTagPro geofencing attaching the coverage to a particular target. The goal could possibly be an interface or a VLAN. Option 1: Apply the default device monitoring coverage to a goal. 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 policy is a constructed-in policy with default settings; you can not change any of the attributes of the default coverage. In order to be able to configure device monitoring policy attributes you will need to create a custom coverage. See Option 2: Create a customized policy with custom settings. Option 2: Create a customized policy with custom settings. Enter the system-monitoring policy command in world configuration mode and enter a custom policy name.

The coverage that's created, and its settings, are system-outlined. Configurable coverage attributes are available in the device tracking configuration mode (config-machine-monitoring) and range from one release to a different. Should you try to change an attribute that's 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 within 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-based machine-tracking commands that allow you to use your configuration to each IPv4 and IPv6 address households. After you've upgraded from a Cisco IOS XE 3.x.x launch to a Cisco IOS XE 16.x.x launch, enter the device-monitoring upgrade-cli to convert legacy IPDT and IPv6 Snooping commands to SISF-primarily based gadget tracking commands. After you run the command, only the new machine-tracking commands are available in your system and the legacy commands will not be supported.

Based on the legacy configuration that exists on your gadget, the system-monitoring upgrade-cli command upgrades your CLI otherwise. Consider the next configuration situations and the corresponding migration results before you migrate your present configuration. You cannot configure a mixture of the previous IPDT and IPv6 snooping CLI with the brand new SISF-primarily based system-tracking CLI. If your system has only IPDT configuration, running the gadget-tracking upgrade-cli command converts the configuration to make use of the new SISF policy that's created and attached to the interface. You'll be able to then update this SISF policy. For iTagPro geofencing those who continue to make use of the legacy commands, this restricts you to operate in a legacy mode the place solely the legacy IPDT and IPv6 snooping commands can be found on the gadget. On a device with existing IPv6 snooping configuration, the outdated IPv6 Snooping commands can be found for iTagPro tracker additional configuration. Use the machine-tracking improve-cli command to convert all of your legacy configuration to the new SISF-based mostly system monitoring commands. After conversion, only the new machine tracking commands will work on your machine.

Use the legacy IPv6 Snooping commands in your future configuration and don't run the device-monitoring upgrade-cli command. With this selection, solely the legacy IPv6 Snooping commands can be found in your device, and you can't use the new SISF-primarily based system tracking CLI commands. On a gadget that has both legacy IPDT configuration and IPv6 snooping configuration, ItagPro you can convert legacy commands to the SISF-based gadget tracking CLI commands. However, note that only one snooping coverage may 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 can use solely the brand new SISF-primarily based machine tracking commands for all of your future configuration. The legacy IPDT commands and IPv6 snooping commands are not available. Starting from Cisco IOS XE Denali 16.3.1, the ip dhcp snooping vlan vlan command creates a system monitoring policy programmatically, to assist the IEEE 802.1X, internet authentication, Cisco TrustSec and IPSG features.

The programmatically created policy tracks each IPv4 and IPv6 purchasers. Be sure that this command is configured, in case you are using any of the aforementioned options. Table Table 1 displays legacy IPDT after which the IPv6 snooping commands they're converted to - if the device-monitoring improve-cli command (global configuration mode) will not be executed. Table Table 2 displays legacy IPDT and iTagPro tracker then the SISF-primarily based gadget-monitoring commands that the system converts them to, if in case you have executed the machine-monitoring upgrade-cli command. Set to the default value, and can't be modified. Set to the default value, and cannot be changed1. Set to the default behavior, and cannot 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 cannot be modified. Enters the worldwide configuration mode. Specifies the interface and enters the interface configuration mode. The machine tracking policy will probably be connected to the required interface.