SISF-based gadget monitoring might be enabled manually (by using device-tracking commands), or programmatically (which is the case when offering device monitoring companies to different options). SISF-Based machine monitoring is disabled by default. You possibly can allow it by defining a device monitoring policy and attaching the coverage to a selected target. The target may very well be an interface or a VLAN. Option 1: Apply the default device tracking policy to a goal. Enter the machine-tracking command in the interface configuration mode or in the VLAN configuration mode. The system then attaches the default policy it to the interface or VLAN. Note The default coverage is a constructed-in coverage with default settings; you can't change any of the attributes of the default policy. In order to be able to configure gadget tracking coverage attributes you could create a customized policy. See Option 2: Create a custom coverage with custom settings. Option 2: Create a customized coverage with custom settings. Enter the system-monitoring coverage command in global configuration mode and enter a customized coverage title.

The coverage that is created, and its settings, are system-outlined. Configurable policy attributes can be found in the system monitoring configuration mode (config-system-monitoring) and vary from one release to another. For those who try to change an attribute that isn't configurable, the configuration change is rejected and an error message is displayed. For release-particular details about programmatically created policies, see Programmatically Enabling SISF-Based Device Tracking in Cisco IOS XE in the required model of the doc. Starting with Cisco IOS XE Denali 16.1.1, iTagPro smart device the present IPv6 snooping and IP Device Tracking (IPDT) commands have corresponding SISF-based machine-tracking commands that permit you to use your configuration to both IPv4 and IPv6 deal with households. After you may have upgraded from a Cisco IOS XE 3.x.x launch to a Cisco IOS XE 16.x.x release, enter the machine-tracking improve-cli to convert legacy IPDT and IPv6 Snooping commands to SISF-based gadget tracking commands. After you run the command, solely the brand new machine-monitoring commands are available in your device and the legacy commands are not supported.

Based on the legacy configuration that exists on your system, the system-tracking improve-cli command upgrades your CLI in a different way. Consider the next configuration scenarios and the corresponding migration results before you migrate your present configuration. You can not configure a mixture of the previous IPDT and IPv6 snooping CLI with the new SISF-primarily based system-monitoring CLI. In case your system has solely IPDT configuration, running the iTagPro smart device-monitoring improve-cli command converts the configuration to use the brand new SISF policy that is created and attached to the interface. You possibly can then update this SISF policy. Should you continue to use the legacy commands, this restricts you to operate in a legacy mode the place only the legacy IPDT and IPv6 snooping commands are available on the gadget. On a machine with existing IPv6 snooping configuration, the outdated IPv6 Snooping commands can be found for further configuration. Use the machine-tracking upgrade-cli command to transform all your legacy configuration to the brand new SISF-based machine tracking commands. After conversion, only the brand new system monitoring commands will work on your machine.

Use the legacy IPv6 Snooping commands for your future configuration and don't run the gadget-monitoring upgrade-cli command. With this selection, solely the legacy IPv6 Snooping commands can be found on your system, and you cannot use the brand new SISF-primarily based machine tracking CLI commands. On a gadget that has each legacy IPDT configuration and IPv6 snooping configuration, you may convert legacy commands to the SISF-primarily based gadget tracking CLI commands. However, note that only one snooping policy will be hooked up to an interface, and the IPv6 snooping policy parameters override the IPDT settings. In case your machine has no legacy IP Device Tracking or IPv6 Snooping configurations, you should utilize only the brand new SISF-based system monitoring commands for all 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 machine monitoring policy programmatically, to help the IEEE 802.1X, net authentication, Cisco TrustSec and IPSG options.

The programmatically created coverage tracks both IPv4 and IPv6 shoppers. Ensure 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 converted to - if the gadget-tracking improve-cli command (global configuration mode) shouldn't be executed. Table Table 2 displays legacy IPDT and then the SISF-primarily based system-monitoring commands that the system converts them to, if in case you have executed the gadget-monitoring upgrade-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 behavior, and cannot be changed. Set to the default worth, 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 system monitoring coverage will probably be hooked up to the desired interface.

• 글쓰기

• 수정
• 삭제
• 목록