Cisco Prime Nerk 43 User Guide
Have a look at the manual Cisco Prime Nerk 43 User Guide online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 53 Cisco manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.
8-29 Cisco Prime Network 4.3.2 User Guide Chapter 8 Drilling Down into an NE’s Physical and Logical Inventories and Changing Basic NE Properties Changing Device Interface Properties and Disabling Interfaces Step 3Select the port and click Poll Now to synchronize the map information with the new device information. NoteBe sure you perform the poll from the right location in the inventory or your changes may not be reflected correctly in Prime Network. See Updating the Inventory (Poll Now), page 8-26. Changing Device Interface Properties and Disabling Interfaces The following commands change the interface properties of the real device. Whether you can run these commands depends on your permissions. See Appendix B, “Permissions Required to Perform Tasks Using the Prime Network Clients”. You can verify whether a device supports these commands by checking the information in the Addendum: Additional VNE Support for Cisco Prime Network 4.3.2. Step 1Locate the interface in the logical inventory. Step 2Change the interface configuration using the commands in this table. In some cases, a command will affect the interface and its parent port. When you launch the command, click Preview to see the actual commands that will be sent to the device. To make the following change on a port: Right-click: Disable or enable an interface and port (for example, disabling faulty interface so it will not continue to generate errors)Logical Inventory> Routing Entities> Routing Entity> interface> Commands > Configuration > System > Enable Interface Logical Inventory> Routing Entities> Routing Entity> interface> Commands > Configuration > System > Disable Interface Change or remove descriptive information that is displayed in Prime Network clients (for example, customer information or business details) when the interface or port is selected. (You can also label interfaces and ports using business tags; see Labelling NEs to Associate Them with Customers (Business Tags), page 4-9.)Logical Inventory> Routing Entities> Routing Entity> interface> Commands > Configuration > Update Interface Configuration Logical Inventory> Routing Entities> Routing Entity> interface> Commands > Configuration > Remove Interface Configuration
8-30 Cisco Prime Network 4.3.2 User Guide Chapter 8 Drilling Down into an NE’s Physical and Logical Inventories and Changing Basic NE Properties Changing Server Settings for DNS, NTP, RADIUS, and TACACs Step 3Right-click the appropriate logical inventory routing entity and choose Poll Now to synchronize the map information with the new device information. NoteBe sure you perform the poll from the right location in the inventory or your changes may not be reflected correctly in Prime Network. See Updating the Inventory (Poll Now), page 8-26. Changing Server Settings for DNS, NTP, RADIUS, and TACACs The following commands change the server settings on the real device. Whether you can run this command depends on your permissions. See Appendix B, “Permissions Required to Perform Tasks Using the Prime Network Clients”. You can verify whether a device supports these commands by checking the information in the Addendum: Additional VNE Support for Cisco Prime Network 4.3.2. Configure DNS Configure a Device NTP Server Configure a software-only interface that emulates an interface. If the virtual interface receives traffic, it immediately reroutes it back to the device.Logical Inventory> Routing Entities> Routing Entity> Commands> Configuration> Add Loopback Interface Configure descriptive information that is displayed in Prime Network clients (for example, customer information or business details) when the interface or port is selected. (You can also label ports using business tags; see Labelling NEs to Associate Them with Customers (Business Tags), page 4-9.)Physical Inventory> interface> Commands> Configuration> Add Interface Configuration To make the following change on a port: Right-click: Command Description DNS>Add DNS Server DNS>Remove DNS ServerAssigns the device to a Domain Name System (DNS) server to manage translating the host name to and from the device IP address. Command Description NTP> Add NTP Server NTP> Remove NTP ServerAssigns the device to a Network Time Protocol (NTP) server to manage clock synchronization.
8-31 Cisco Prime Network 4.3.2 User Guide Chapter 8 Drilling Down into an NE’s Physical and Logical Inventories and Changing Basic NE Properties Suppressing Service Alarms on Virtual Interfaces Configure RADIUS or TACACS Server on Device Suppressing Service Alarms on Virtual Interfaces In Prime Network Vision, you can suppress or unsuppress virtual interfaces related service alarms by using the Runregtool commands. You can suppress or unsuppress ipv4/ipv6 virtual interface service alarms on a Device series or VNE levels.Command Description TACACS> Add Tacacs Server TACACS> Remove Tacacs ServerAssigns the device to a Terminal Access Controller Access-Control System (TACACS) server to manage authentication (uses TCP or UDP). TACACS+> Add Tacacs+ Server TACACS+> Remove Tacacs+ ServerAssigns the device to a TACACS+ server to manage authentication (uses TCP). RADIUS> Add Radius Server RADIUS> Remove Radius ServerAssigns the device to a Remote Authentication Dial In User Service (RADIUS) server to manage centralized authentication, authorization, and accounting (uses UDP) . Table 8-5 Suppress or Unsupress Service Alarms on Device Series Level Suppress Service Alarms on Devices Series Service Alarm Name Command Dual Stack IP removed on Virtual InterfacerunRegTool.sh -gs 127.0.0.1 set 0.0.0.0 site/ciscorouter2//i pcore/software versions/default version/eventmanager/types/Dual stack IP removed on Virtual Interface/default eventmanager/templates/sub-event/ignore-tem plate Dual Stack IP added on Virtual InterfacerunRegTool.sh -gs 127.0.0.1 set 0.0.0.0 site/ciscorouter2//i pcore/software versions/default version/eventmanager/types/Dual stack IP added on Virtual Interface/default eventmanager/templates/sub-event/ignore-tem plate Dual Stack IP removed on Virtual InterfacerunRegTool.sh -gs 127.0.0.1 set 0.0.0.0 site/ciscorouter2//i pcore-evne/software versions/default version/eventmanager/types//Dual stack IP removed on Virtual Interface/default eventmanager/templates/sub-event/ignore-tem plate
8-32 Cisco Prime Network 4.3.2 User Guide Chapter 8 Drilling Down into an NE’s Physical and Logical Inventories and Changing Basic NE Properties Suppressing Service Alarms on Virtual Interfaces Dual Stack IP Added on Virtual InterfacerunRegTool.sh -gs 127.0.0.1 set 0.0.0.0 site/ciscorouter2//i pcore-evne/software versions/default version/eventmanager/types/Dual stack IP added on Virtual Interface/default eventmanager/templates/sub-event/ignore-tem plate Unsuppress Service Alarms on Device Series Service Alarms Name Command Dual Stack IP removed on Virtual InterfacerunRegTool.sh -gs 127.0.0.1 set 0.0.0.0 site/ciscorouter2//i pcore/software versions/default version/eventmanager/types/Dual stack IP removed on Virtual Interface/default eventmanager/templates/sub-event/persistent -template Dual Stack IP Added on Virtual InterfacerunRegTool.sh -gs 127.0.0.1 set 0.0.0.0 site/ciscorouter2//i pcore/software versions/default version/eventmanager/types/Dual stack IP added on Virtual Interface/default eventmanager/templates/sub-event/persistent -template Dual Stack IP removed on Virtual InterfacerunRegTool.sh -gs 127.0.0.1 set 0.0.0.0 site/ciscorouter2//i pcore-evne/software versions/default version/eventmanager/types/Dual stack IP removed on Virtual Interface/default eventmanager/templates/sub-event/persistent -template Dual Stack IP Added on Virtual InterfacerunRegTool.sh -gs 127.0.0.1 set 0.0.0.0 site/ciscorouter2//i pcore-evne/software versions/default version/eventmanager/types/Dual stack IP Changed/Dual stack IP added on Virtual Interface/default eventmanager/templates/sub-event/persistent -template Table 8-5 Suppress or Unsupress Service Alarms on Device Series Level Suppress Service Alarms on Devices Series
8-33 Cisco Prime Network 4.3.2 User Guide Chapter 8 Drilling Down into an NE’s Physical and Logical Inventories and Changing Basic NE Properties Suppressing Service Alarms on Virtual Interfaces You can also suppress or unsupress virtual interface IPs of false alarms in Tickets on a Device series or VNE. Use the following commands to suppress or unsuppress Virtual Interface IPs. Table 8-6 Suppress or Unsuppress Service Alarms on VNE Level Suppress Service Alarms Service Alarms Name Command Dual Stack IP Removed on Virtual InterfacerunRegTool.sh 127.0.0.1 set avm/agents/da//eventmanager/types/Dual stack IP removed on Virtual Interface/default eventmanager/templates/sub-event/ignore-tem plate Dual Stack IP Added on Virtual InterfacerunRegTool.sh 127.0.0.1 set avm/agents/da//eventmanager/types/Dual stack IP added on Virtual Interface/default eventmanager/templates/sub-event/ignore-tem plate Unsuppress Service Alarms Service Alarms Name Command Dual Stack IP Removed on Virtual InterfacerunRegTool.sh 127.0.0.1 set avm/agents/da//eventmanager/types/Dual stack IP removed on Virtual Interface/default eventmanager/templates/sub-event/persistent -template Dual Stack IP Added on Virtual InterfacerunRegTool.sh 127.0.0.1 set “avm/agents/da//eventmanager/types/Dual stack IP added on Virtual Interface/default eventmanager/templates/sub-event/persistent -template
8-34 Cisco Prime Network 4.3.2 User Guide Chapter 8 Drilling Down into an NE’s Physical and Logical Inventories and Changing Basic NE Properties Suppressing Service Alarms on Virtual Interfaces Table 8-7 Suppress or Unsuppress Service Alarms on the Tickets Tab Suppress Service Alarms Name Command Dual Stack IP Removed on Virtual Interface runRegTool.sh -gs 127.0.0.1 set 0.0.0.0 site/ciscorouter2//i pcore/software versions/default version/eventmanager/applications/event-cor relation/application-data/sub-applications/ com.sheer.metrocentral.framework.eventappli cation.eventcorrelation.SendAlarmMessageUti l/types/Dual stack IP removed on Virtual Interface/is-ticketable false Dual Stack IP Added on Virtual InterfacerunRegTool.sh -gs 127.0.0.1 set 0.0.0.0 site/ciscorouter2//i pcore-evne/software versions/default version/eventmanager/applications/event-cor relation/application-data/sub-applications/ com.sheer.metrocentral.framework.eventappli cation.eventcorrelation.SendAlarmMessageUti l/types/Dual stack IP added on Virtual Interface/is-ticketable false Unsuppress Service Alarms Name Command Dual Stack IP Removed on Virtual Interface runRegTool.sh -gs 127.0.0.1 set 0.0.0.0 site/ciscorouter2//ip core/software versions/default version/eventmanager/applications/event-correlat ion/application-data/sub-applications/com.sheer. metrocentral.framework.eventapplication.eventc orrelation.SendAlarmMessageUtil/types/Dual stack IP Changed/Dual stack IP removed on Virtual Interface/is-ticketable true Dual Stack IP Added on Virtual InterfacerunRegTool.sh -gs 127.0.0.1 set 0.0.0.0 site/ciscorouter2//ipco re-evne/software versions/default version/eventmanager/applications/event-correlatio n/application-data/sub-applications/com.sheer.metr ocentral.framework.eventapplication.eventcorrelati on.SendAlarmMessageUtil/types/Dual stack IP Changed/Dual stack IP added on Virtual Interface /is-ticketable true
8-35 Cisco Prime Network 4.3.2 User Guide Chapter 8 Drilling Down into an NE’s Physical and Logical Inventories and Changing Basic NE Properties Suppressing Service Alarms on Virtual Interfaces After configuring commands to the device, you can assign the loopback of ipv4 or ipv6 in the Virtual template, change the assignation of loopback of ipv4 or ipv6 in the Virtual template or remove or add the ipv6 or ipv4 address from the loopback. Changing Assignation of Loopback for both ipv4 and ipv6 in the Virtual Template To change the assignation of loopback for both ipv4 and ipv6, follow the below steps: Step 1Log in to a device. For example, asr1k. Step 2Change the assigned Loopback with ipv4 and ipv6. Table 8-8 Suppress or Unsuppress in the Tickets Tab on VNE Level Suppress Service Alarms Name Command Dual Stack IP Removed on Virtual InterfacerunRegTool.sh 127.0.0.1 set avm/agents/da//eventmanager/applications/event-corr elation/application-data/sub-applications/c om.sheer.metrocentral.framework.eventapplic ation.eventcorrelation.SendAlarmMessageUtil /types/Dual stack IP removed on Virtual Interface/is-ticketable false Dual Stack IP Added on Virtual InterfacerunRegTool.sh 127.0.0.1 set avm/agents/da//eventmanager/applications/event-corr elation/application-data/sub-applications/c om.sheer.metrocentral.framework.eventapplic ation.eventcorrelation.SendAlarmMessageUtil /types/Dual stack IP added on Virtual Interface/is-ticketable false Unsupress Service Alarms Name Command Dual Stack IP Removed on Virtual InterfacerunRegTool.sh 127.0.0.1 set avm/agents/da//eventmanager/applications/event-corr elation/application-data/sub-applications/c om.sheer.metrocentral.framework.eventapplic ation.eventcorrelation.SendAlarmMessageUtil /types/Dual stack IP removed on Virtual Interface/is-ticketable true Dual Stack IP Added on Virtual InterfacerunRegTool.sh 127.0.0.1 set avm/agents/da//eventmanager/applications/event-corr elation/application-data/sub-applications/c om.sheer.metrocentral.framework.eventapplic ation.eventcorrelation.SendAlarmMessageUtil /types/Dual stack IP added on Virtual Interface/is-ticketable true
8-36 Cisco Prime Network 4.3.2 User Guide Chapter 8 Drilling Down into an NE’s Physical and Logical Inventories and Changing Basic NE Properties Suppressing Service Alarms on Virtual Interfaces Step 3Choose Logical Inventory > Routing Entities > Routing Entity, and then click the Network Events Tab in the Prime Network Vision and Service Alarms Tab in the Prime Network Event Vision to verify the Service Alarms for Virtual Interfaces. Step 4Execute the RunReg tool to block the Virtual Interfaces. For example, you can use RunReg tool command either at the devices series or VNE Level or in the Tickets tab on device series. Step 5Repeat steps 1 through 4. The Virtual Interfaces does not show in Prime Network.
CH A P T E R 9-1 Cisco Prime Network 4.3.2 User Guide EDCS-1524415 9 Manage Device Configurations and Software Images Cisco Prime Network Change and Configuration Management (CCM) provides tools for managing the software images and device configuration files used by the devices in your network. For information on the devices supported by CCM, see the Cisco Prime Network 4.3.2 Supported VNEs - Addendum. For its Supported Protocols see the Support for Change and Configuration Management in 4.3.2 tables. These topics explain how to use CCM: Using the CCM Dashboard, page 9-1 Managing Device Software Images, page 9-3 Managing Device Configurations, page 9-26 Making Sure Devices Conform to Policies Using Compliance Audit, page 9-41 Using Compliance Audit for Device Compliance, page 9-66 Checking Image Management, Device Management, and Compliance Audit Jobs, page 9-71 Before using CCM, make sure you have completed the setup steps described in Setting Up Configuration Management, page 3-5. NoteCCM is also the launch point for the following Prime Network features which are described in the Cisco Prime Network 4.3 Customization Guide: Prime Network Transaction Manager, which manages and executes activations on groups of devices. Prime Network Command Manager, which provides a repository of all commands available in the system, and can be used to create new commands and command sequences which you can apply to groups of devices. Using the CCM Dashboard To launch CCM from a web browser, enter the following URL in the address bar: https://gateway-IP:8043/ccmweb/ccm/login.htm
9-2 Cisco Prime Network 4.3.2 User Guide EDCS-1524415 Chapter 9 Manage Device Configurations and Software Images Using the CCM Dashboard Figure 9-1 shows the CCM Dashboard, which contains four dashlets that display real-time information about the most frequently used software images, any devices with startup and running configurations that are not in sync, and recent device configuration changes. Figure 9-1 CCM Dashboard Dashlet Provides information about: Top Families The four largest device families in the network. (Smaller groups can be viewed by toggling to the tabular form.) From here, you can distribute and activate software images to a selected family. In some cases, the actual name of the device family will not be displayed. For example, if c6sup11, s2t54, and s3223 are displayed in this dashlet, you must search Cisco.com to identify the device families for these devices. The c6sup11 device corresponds to the Cisco Catalyst 6500 Series Supervisor Engine 1A / MSFC1 device family, s2t54 device corresponds to the Cisco Catalyst 6500 Series Supervisor Engine 2T device family, and s3223 device corresponds to the Cisco Catalyst 6500 Series Supervisor Engine 32 / MSFC2A device family. NoteIf you have enabled the Right to Left (Hebrew) settings in your browser, you may face resizing issues when you hover the cursor over this dashlet. Configuration Sync Status(Cisco IOS) Devices for which the startup and running device configurations are in sync or not in sync. Whenever a Cisco IOS configuration file is retrieved from a device and copied to the archive, CCM compares the latest version of the startup configuration with the latest version of the running configuration file. If there is a mismatch, CCM adds the device to the list of out-of-sync devices. The information is refreshed whenever you click the Dashboard. A “100% Unavailable” message is displayed when there are no Cisco IOS device images or if the initial configuration sync up setting is not enabled (controlled by the “Enable/Disable Initial config sync up on restart” setting on the Configuration Management Settings page).