Navigating Cisco Prime Campus Manager Tasks in LMS 4.1

Transcription

1 CHAPTER 4 Navigating Cisco Prime Campus Manager Tasks in LMS 4.1 CiscoWorsk Campus Manager (CM) is an integral component of Cisco Prime LAN Management Solution. As an enterprise solution for network management, Campus Manager provides a suite of web-based network management tools that enable administrators to obtain various types of graphical views of their network topology and end-user information. This chapter provides mapping of CM tasks in LMS 4.1. It explains: Campus User Tracking Tasks Visualization Tasks Tasks and Job Management Tasks Administrative Tasks Campus User Tracking Tasks This section provides information on the following Campus Manager User Tracking tasks in LMS 4.1: Tasks Acquisitions Tasks Administration Tasks 4-1

2 Campus User Tracking Tasks Chapter 4 Navigating Cisco Prime Campus Manager Tasks in LMS 4.1 Table 4-1 Campus User Tracking Tasks Tasks Viewing Quick Using Report Generator Creating Custom Viewing List of Custom Layouts Viewing Archived List Acquisitions Tasks Viewing and interpreting acquisition information Tracking > Tracking > > Report Generator Tracking > > Custom Tracking > > Custom Layouts Tracking > > Archives Tracking > Acquisition > Inventory: User Tracking > Quick Report > Inventory: User Tracking > Report Designer: User Tracking > Custom > Report Designer: User Tracking > Custom Layouts > Report Archives: User Tracking Inventory > User Tracking Settings: Acquisition Summary Or User Tracking > Acquisitions Info You can view the reports on end hosts or IP phones, based on the filter criteria using which you want to generate the report. The Report Generator in User Tracking allows you to view System-defined reports and Custom reports. You can generate the following reports: Duplicates End Hosts History IP Phones MAC Report Switch Port Report Wireless Report You can also schedule to generate these reports immediately, once, daily, weekly, monthly or quarterly. You can create Custom reports for End Hosts or IP Phones. You can view the list of Custom layouts. Standard layouts are available after a fresh install. You can view a list of archived user tracking reports using the Archive option. You can view acquisition summary from the Asset menu. 4-2

3 Chapter 4 Navigating Cisco Prime Campus Manager Tasks in LMS 4.1 Campus User Tracking Tasks Table 4-1 Campus User Tracking Tasks (continued) Configuring User Tracking Acquisition Actions Administration Tasks Modifying Acquisition Settings Modifying Acquisition Schedule Modifying Ping Sweep Options Configuring Subnet Acquisition Modifying Delete Interval Tracking > Acquisition > Actions Acquisition > Acquisition Settings Acquisition > Schedule Acquisition Acquisition > Ping Sweep Acquisition > Configure Subnet Acquisition Acquisition > Delete Interval Inventory > User Tracking Settings: Acquisition Actions Or User Tracking > Acquisition Action User Tracking > Acquisition Settings User Tracking > Acquisition Schedule User Tracking > Ping Sweep User Tracking > Subnet Acquisition configuration Admin > Network: Purge Settings > User Tracking Purge Policy You can trigger the following acquisitions: Device based Acquisition Subnet based Acquisition IP Phone Acquisition You can modify User Tracking Acquisition settings using the Acquisition Settings option You can modify UT acquisition schedule using the Acquisition Schedule option. A ping sweep (also known as an ICMP sweep) is a basic network scanning technique used to determine the range of IP addresses that map to live end hosts (computers). You can use a single ping to find out whether a specific end host exists on the network. You can modify Ping Sweep option. You can configure LMS to perform User Tracking Acquisition on selected subnets. These configurations are used for User Tracking Major Acquisition and Configured Subnets based acquisition. You can choose to include or exclude specified subnets to perform User Tracking major acquisition. You can modify the time interval for deleting entries from the End Host Table, IP Phone Table or the History Table from the database 4-3

4 Campus User Tracking Tasks Chapter 4 Navigating Cisco Prime Campus Manager Tasks in LMS 4.1 Table 4-1 Campus User Tracking Tasks (continued) Configuring Trunk for End Host Discovery Specifying Purge Policy Specifying Domain Name Display Importing Information on End Host Users Understanding Dynamic Updates Acquisition > Configure Trunk For End Hosts Discovery > User Tracking Purge Policy > Domain Name Display End Host Table Import Dynamic Updates User Tracking > Acquisition in Trunk Admin > Network: Purge Settings > User Tracking Report Purge Policy Admin > Network: Display Settings > Domain Name Display User Tracking > Table Import User Tracking > Dynamic Update Process Status Normally UT Acquisition discovers end hosts connected only to access ports. If you enable this feature UT Acquisition discovers end hosts connected to non-link trunk ports also. You can specify the intervals at which old reports and jobs are to be purged, using the Purge Policy option. You can save the Purge Policy, so that the older jobs and archives are purged at the specified interval. You can specify the way in which domain names are to be displayed in User Tracking, using the Domain Name Display option. You can import from a file, user names and notes for end hosts already discovered, using the End Host Table Import option. User Tracking generates reports on various functions and attributes of the end hosts and devices connected to your network that are managed by LMS. These reports are generated by polling the network at intervals set by the network administrator. In addition to polling the network at regular intervals, LMS tracks changes about the end hosts and users on the network to provide real-time updates. Dynamic Updates are asynchronous updates that are based on SNMP MAC notifications traps. 4-4

5 Chapter 4 Navigating Cisco Prime Campus Manager Tasks in LMS 4.1 Campus User Tracking Tasks Table 4-1 Campus User Tracking Tasks (continued) Enabling SNMP Traps on Switch Ports Configuring SNMP Trap Listener Configuring Dynamic User Tracking Dynamic Updates > Device Trap Dynamic Updates > Trap Listener Dynamic Updates > Dynamic User Tracking User Tracking > Device Trap User Tracking > Trap Listener User Tracking > Dynamic User Tracking You must configure the Cisco switches for sending SNMPv1/SNMPv2 MAC Notification Traps when a host is connected to or disconnected from that port. Even if the device is managed with SNMPv3, LMS processes only SNMPv1/SNMPv2 traps. LMS receives SNMP traps directly from the switches if you configure the port to direct the traps through primary listeners such as HP OpenView (HPOV) or Cisco Prime Device Fault Manager (DFM) applications. You can configure certain properties in Dynamic User Tracking to enhance the security of the system. These properties make the server receive traps only from specified devices and with specified community strings. 4-5

6 Visualization Tasks Chapter 4 Navigating Cisco Prime Campus Manager Tasks in LMS 4.1 Visualization Tasks This section provides information on the Campus Manager Visualization tasks in LMS 4.1. Table 4-2 Visualization Tasks Using Topology Services Enabling RMON to Measure Bandwidth Utilization Visualization > Topology Services > Launch Topology Services Visualization > RMON > Topology Or Monitor > Monitoring Tools:Topology Services Admin > Network: Monitor/ Troubleshoot > RMON Topology Services is an application that enables you to view and monitor your network including the links and the ports of each link. Topology Services displays the network topology of the devices discovered by LMS, through Topology Maps. Besides these Maps, the application includes numerous reports that help you to view the physical and logical connectivity in details. Bandwidth Utilization is the measure of traffic flowing across a link. LMS highlights bandwidth utilization across links, in the Topology maps. It computes the bandwidth utilization by taking the best estimate of the mean physical layer network utilization on the links, during the sampling time interval. In Topology Map, LMS can differentiate the links using colors, based on the bandwidth utilized by them. You can customize the filters to display bandwidth utilization. 4-6

7 Chapter 4 Navigating Cisco Prime Campus Manager Tasks in LMS 4.1 Tasks Tasks This section provides information on the Campus Manager tasks in LMS 4.1. Table 4-3 Tasks VLAN > VLAN Creating VLANs > VLAN > Create Creating PVLANs > PVLAN > Create PVLAN Deleting PVLAN > PVLAN > Delete PVLAN > Workflows:VLAN > Configure VLAN > Workflows:VLAN > Configure VLAN > Workflows: VLAN > Create Private LAN > Workflows: VLAN > Delete Private LAN A Virtual Local Area Network (VLAN) allows you to create logical broadcast domains that can span across a single switch or multiple switches, regardless of physical positioning. A VLAN contains a group of devices on one or more LANs. You can create amd delete VLANs using VLAN wizard. Allows you to create a VLAN by selecting devices or entities to be included in the VLAN. Domain Selector helps you to select devices in Switch Clouds and VTP Domains. A Private VLAN (PVLAN) is a VLAN that isolates devices at Layer 2 (L2), from other ports within the same broadcast domain or subnet. PVLAN segregates traffic at L2 and converts a broadcast segment into a non-broadcast multi-access segment. To create a Private VLAN, you must designate one VLAN as primary and another as either isolated, community, or two-way community VLAN. Then, you can assign additional VLANs as secondary VLANs. After creating primary and secondary VLANs you must associate the secondary VLANs to the respective primary VLANs. You delete a configured PVLAN. 4-7

8 Tasks Chapter 4 Navigating Cisco Prime Campus Manager Tasks in LMS 4.1 Table 4-3 Tasks (continued) Configuring Promiscuous Ports VLAN Port Assignment > PVLAN > Configure Promiscuous Ports > VLAN Port Assignment Creating Trunk > Trunk > Create Trunk Modifying Trunk Attributes > Trunk > Modify Trunk Attributes > Workflows: VLAN > Configure Promiscuous Ports > Workflows: VLAN > Configure Port Assignment > Workflows: VLAN > Create Trunk > Workflows: VLAN > Modify Trunk You must associate the promiscuous ports to the PVLANs you have created, to receive traffic from outside the PVLAN. VLAN Port Assignment is an application that displays device, port, and related VLAN information for an associated VTP domain in a tabular format and helps you manage ports on your network VLANs. A Trunk is a point-to-point link carrying traffic for several VLANs, and are typically used to connect switches. Instead of configuring several access links to carry multi-vlan traffic, its economical to do it with a single trunk link. Allows you to modify trunk attributes. 4-8

9 Chapter 4 Navigating Cisco Prime Campus Manager Tasks in LMS 4.1 and Job Management Tasks and Job Management Tasks This section provides information on the Campus Manager and Job Management tasks in LMS 4.1. Table 4-4 and Job Mgmt Tasks Using the Job Browser > Report Jobs Generating > Report Generator Viewing Archived Using Job Management Browser > Report Archives Job Mgmt Admin > Jobs: Browser > Fault and Event: Best Practices > Deviation > Fault and Event: Best Practices > Discrepancies > Technology: VLAN > Inventory: Device Attributes > Report Archives Admin > Jobs: Browser You can manage Report Jobs using the Job browser. You can also view the output of completed jobs, stop running jobs or delete jobs if required. Generate the following reports: Best Practices Deviations Report Device Attributes Report Discrepancies Report Port Attributes Report VLAN Report The report output that is created from a scheduled report is stored in the reports archive. The archive displays the list of completed report jobs and you can view or delete them. The Job Browser enables you to view the status of all LMS Jobs (User Tracking jobs, reports). The job details that you can view here include the job ID, the job type, the job status, the job description, the job owner, the time the job is scheduled to run at, the time of job completion, and the schedule type. 4-9

10 Administrative Tasks Chapter 4 Navigating Cisco Prime Campus Manager Tasks in LMS 4.1 Administrative Tasks This section provides information on the following Campus Manager Administrative tasks in LMS 4.1: Data Collection Tasks Other Admin Settings Debugging Options Table 4-5 Admin Tasks Data Collection Tasks Viewing Summary of Data Collection Settings Modifying SNMP Timeouts and Retries Scheduling Data Collection Data Collection Data Collection > SNMP Timeouts and Retries Data Collection > Schedule Data Collection Device Poller Data Collection > Device Poller Restricted Topology View Configuring Fault Poller Settings Topology > Restricted Topology View Topology > DFM Poller Settings Topology Groups Groups Admin > Collection Settings : Data Collection Admin > Collection Settings : Data Collection > Data Collection SNMP Timeouts and Retries Admin > Collection Settings : Data Collection > Data Collection Schedule Admin > Collection Settings : Data Collection > Data Collection Critical Devices Poller Admin > Network: Monitor/Troubleshoot > Retricted Topology View Admin > Network: Monitor/Troubleshoot > Fault Poller Settings for Topology Admin > System: Group Management View a summary of the Data Collection settings Modify the SNMP timeouts and retries when Data Collection fails for a particular device with SNMP timeout exceptions. Allows you to schedule the day and time of data collection. Poll the entire network for device and link status periodically. You can: Configure the time interval at which the network is polled. Poll only a critical set of devices. Topology Services display all the devices discovered by LMS. Enable polling to display fault information in Topology Maps and N-Hop view portlet. The Topology Groups feature in LMS allows you to create customized views, of the network, in which devices are grouped according to various criteria. A view may be considered as a group of devices or device elements. 4-10

11 Chapter 4 Navigating Cisco Prime Campus Manager Tasks in LMS 4.1 Administrative Tasks Table 4-5 Admin Tasks (continued) Using Administration Other Admin Settings Understanding Discrepancies and Best Practices Deviations Purging Jobs and Archived Debugging Options Setting up Debugging Options for Data Collection Setting up Debugging Options for and Setting up Debugging Options for Device Groups Other Admin Settings > Discrepancies Other Admin Settings > Purge Settings Debugging Options > Data Collection Debugging Options > and Debugging Options > Device Groups > System: ANI Server Analysis > System: Data Collection Metrics > System: Device Support Admin > Network: Best Practices Deviation Settings Admin > Network: Purge Settings > Layer2 Services Purge Settings Admin > System: Debug Settings > Data Collection Admin > System: Debug settings > Layer2 and Admin > System: Debug Settings These reports allow you to view an analysis of the ANI Server, details of devices discovered, Data Collection metrics, and list of devices supported. LMS provides reports on discrepancies, such as network inconsistencies and anomalies or misconfiguration in the discovered network. This makes it easy to identify configuration errors such as link-speed mismatches on either end of a connection. Discrepancies are computed at the end of each data collection schedule. LMS also reports Best Practices Deviations. These are variations from the normal or recommended practices in a network. These do not have any serious impact on the functioning of the network. You can purge jobs or report archives in LMS. By default, purging is disabled. You can set the trace, and debugging, for Data Collection You can enable debugging for and in LMS. You can enable debugging for the errors related to System defined or User defined groups. 4-11

12 Administrative Tasks Chapter 4 Navigating Cisco Prime Campus Manager Tasks in LMS 4.1 Table 4-5 Admin Tasks (continued) Setting Debugging Options for Topology Debugging Options for User Tracking Server Debugging Options for User Tracking Debugging Dynamic Updates Debugging Options > Topology Debugging Options > User Tracking Server Debugging Options > User Tracking Debugging Options > Dynamic User Tracking Admin > System: Debug Settings > Topology Admin > System: Debug Settings > User Tracking Server Admin > System: Debug Settings > User Tracking Admin > System: Debug Settings > Dynamic User Tracking You can enable debugging for Topology Services client side activities. The debugging information will be available in the Java Console. Debug events related to all User Tracking server side processes. You can debug events related to User Tracking client side activities. You can set the debugging options required for Dynamic Updates. Enable debugging, records all the required information to the log files. 4-12