CPT400 Version 6 Student Guide

CPT400 - Network Management Training, v6
Student Guide
CPT400: Network Management Training

Version 6 Prizm version 3
Motorola: For General Business Use, CPT400v6.pdf

Canopy is a registered trademark of Motorola, Inc. MOTOROLA and the Stylized M Logo are registered in the US Patent & Trademark Office. All other product or service names are the property of their respective owners. Motorola, Inc. 2006.
Course Objectives (page 1 of 2)

At the end of the training, students will be able to:
Explain the importance of using a network or element management system for tasks such as fault management, configuration management, performance management, and network security. Identify how the Prizm system supports fault management, configuration management, performance management, and network security, either on its own or within the context of a larger network management system. Use consistent terminology relating to the Prizm system. Explain the logical flow of how events, polling, alerts and notifications are triggered, logged and actioned in Prizm. continued

Student Guide
Course Objectives (page 2 of 2)

At the end of the training, students will be able to:
Complete the Define Network process steps using Prizm. Complete the element auto-discovery process steps using Prizm. Set up elements for authentication within Prizm. Configure network elements in a consistent fashion using configuration templates. Establish events, alerts and notifications for element management within their network. View reports on network performance. Identify administrative and configuration options for Prizm management of both Prizm operations and network operations. Know what additional resources exist, and be able to find and use them, to support the installation, deployment and use of Prizm.
3

Course Outline
Section 1: Understanding Network Management Section 2: Prizm System Overview Section 3: Network Definition & Element Discovery Section 4: Monitor Elements Section 5: Templates & Profiles Section 6: Network Security Section 7: Management with Prizm
Student Guide
CPT400 within Overall Curriculum
CPT100: Overview of Canopy, RF and IP concepts (one day)
xxx200: Product-Specific technical training courses (one or two days): CPT200, BPL200, HZD200
CPT300: Advanced Canopy Training (one day)
CPT400: Network Management Systems (one day)

Housekeeping Items
Introductions Facilities Schedule: Breaks, Lunch

Student Guide
Section 1 Understanding Network Management

What Happens When

Scenario #1: Customer SM goes out of service at 4 am.
When and how do you find out? How do you debug? What are average down times? Do you deploy a technician to the site to debug?
8

Student Guide
What Happens When

Scenario #2: Its the AP that goes down, not a single SM.
When and how do you find out? How do you debug? What can you communicate to affected customers about projected down time?
What Happens When

Scenario #3: Customers call up to change their service. One wants more speed. Another wants lower pricing. What options can you offer? How do you implement the changes? How long does it take? Does it require a truck roll to the customers property?

10
Student Guide
Discussion Identify Network Management Concerns

11
Questions?

12
Student Guide
Section 2: Prizm System Overview

Prizm Defined Prizm Features Prizm Demo

What is the Prizm System

Element Management System for MOTOwi4 wireless networks Provides real-time monitoring and configuration management of Canopy network devices (AP, SM, CMMmicro), Motorola PTP devices* (BH), and Powerline MU devices (Gateway or Modem). Notifies operator when device performance falls outside user-defined thresholds Generates event logs and performance reports Integrates with higher-level network management system Exports system and customer data in a format usable by other application programs
* Limited configuration management for high-speed PTP products.

14
Student Guide
Prizm Interface Points

Business Mgmt OS
SNMP SOAP/XML
License Manager Database files Network elements
Prizm Server
Client Devices
For details on the Prizm architecture and on how Prizm communicates with network elements, databases, or other systems, see the Prizm Administration Guide.
15
Prizm Element Management Function & Features

View entire network and topology. Apply consistent configurations to network elements. Track history of all configuration changes. Provide secured, managed access to network elements. Authenticate each CPE device that attempts to register. Set data transmission rates on per-CPE basis. Suspend or re-activate individual CPEs. (optional) Integrate with a service providers RADIUS server for RADIUS-based authentication. Assign floating licenses (if necessary and available) to support software features.
16
Student Guide
Prizm Fault Monitoring Features

Set the criteria to trigger events, alerts and notifications that make sense for their network operations. Can use Prizm default definitions, or create your own. Establish control thresholds once, then let Prizm monitor the network. When events occur, Prizm will generate alerts and notifications based on the established criteria. Prizm supports complex queries, so alerts can be generated based on multiple attributes. Proactive alert notification supports faster troubleshooting and response times for network issues that occur.
17
Prizm Configuration Functions & Features

Define templates that reflect standard configuration options used in their network. Apply templates over-the-air after SM/CPE registration, simplifying the installation effort. Push out changes to templates automatically to all applicable modules. Update service plans for existing subscribers by applying a different template to an existing module. Bandwidth Service Plans and VLAN profiles function in the same way as configuration templates.
18
Student Guide
Prizm Performance Monitoring

View performance reports to identify where performance is degrading, before the situation becomes critical. Technical Support tool captures data for the Motorola technical support team, for faster trouble resolution. Create data archive files for longer-term historical reporting. Identify users who exceed their defined bandwidth parameters or usage. Identify suspicious activity on the network. Tie MAC addresses to IP addresses.
19
Prizm Task Scheduler

Set up routine tasks to run at off-hours automatically. Run software upgrades multiple times, to ensure completeness across the network. Run multiple concurrent upgrade activities. Implement configuration changes when you want them to occur. Activate or suspend elements based on customer account status changes.

20
Student Guide
Demo Prizm User Interface
Prizm

21
Recap Prizm GUI Features

Can set user-specific configurations, so same views open each time the user launches the Prizm client. Specify which columns display for element views. Undock specific windows, to keep open on users desktop. Ability to rename window tabs (temporary effect). Context-sensitive help. Context-sensitive menu structure. Right-click pop-up menus.

22
Student Guide
Questions?

23
Section 3 Network Definition & Element Discovery

Define a Network Auto-Discover and Add Elements Import Network Information

Student Guide
Steps for Defining Network

1. Identify new network in Prizm. 2. Specify the subnet configuration(s) that Prizm should apply to elements in the network. 3. Add, discover or import network element information. 4. Confirm elements that Prizm should manage in the network.
These steps are detailed in Section 5.2 of the Prizm User Guide, Setting Up Network Views.
27
Step 1: Identify Network in Prizm

Network Define Networks opens list of existing networks within Prizm. Edit Add a Network creates a new network within Prizm. Select New Network to open the Network folder pane. Enter network name, description, and select the desired configuration options.
28
Student Guide
Step 2: Specify Subnet Configurations

Specifying the subnet configurations defines the IP addressing and SNMP parameters that Prizm will use when managing elements in the network. For segmented networks, you define multiple subnet configurations, one for each segment. This allows for different configurations within a large network. For non-segmented networks, one subnet configuration is defined and listed as Default.

29
Define Subnet Configuration Window (1)

1 2 3 4 5

30
Student Guide
1. Server Route IP Address: Specify the IP address for the segmented network; otherwise leave as Default. 2. Element NAT Server IP: When the Prizm server is behind a NAT device, enter the NAT servers IP address. 3. SNMP Element Configuration: For the first two options, Prizm will check current permissions relating to the element. If a change is required, Prizm will push that change to the element and initiate a reboot to put the change into effect. The third selection will force a reboot of the element. 4. Use the Edit Network Configuration menu to update passwords or SNMP community strings.
31
With the Subnet Configuration window still open, use the Edit Network Configuration menu to change the default SNMP community strings or to change the default passwords (the read/write passwords for the modules).
Note, Prizm does not support community strings that contain spaces.
32
Student Guide
5. Subnet Accessing Range: Specify up to 10 Classless Internet Domain Routing (CIDR) address blocks for Prizm to apply. Convert any IPv6 (hex) strings into IPv4 format Specify CIDR supernet mask bits in the Mask column 6. Trap Management: Enable if you want Prizm to overwrite current SNMP trap settings in the element. Enter up to 10 IP addresses of servers to which elements should send traps. 7. Auto IP Address Assignment: Enable if you want Prizm to assign IP addresses to each SM or BHS that is accepted into the network but does not have routable IP addresses. Complete the corresponding address assignment fields. Select Apply Changes to create the subnet.
33
Step 3: Add, Discover or Import Network Element Information

Options for network element discovery in Prizm: 1. Prizm auto-discovers network elements in a userdefined range of IP addresses. 2. User enters the IP addresses of AP and BHM modules, then lets Prizm discover the modules, along with the corresponding CPE devices. 3. Prizm auto-discovers CPE device when the unknown CPE attempts to register. 4. User imports network hierarchy file from CNUT. 5. Administrator migrates element data from BAM (Release 2.0 or 2.1) into Prizm.
34
Student Guide
Element Discovery from IP Address Range
Use the Edit Discover Network Elements menu. Specify the type(s) of discovery. Update SNMP strings and passwords if necessary. Enter the IP addresses or address ranges.
35
Element Discovery from CPE Devices Registration Attempt

What happens if SM, BHS or PLV modem attempts to register to an AP, BHM or PLV gateway that requires authentication. CPE device isnt accepted into a Prizm network, or device is listed as Ignore. Then Prizm can be set up to Place the element into the parents defined network, unless the parent device is not found in a Prizm network. In that case, place the element into a specified default network. Always place the element into a specified default network, defined by operator.
36
Student Guide
Element Discovery Import from CNUT
Canopy Network Updater Tool can generate a network archive file, which can be imported into Prizm. The import file includes Infrastructure elements Network hierarchy Additional IP information defined in CNUT. Ability to import the .net file is available to users with Administrator status within Prizm. Details on this process can be found in Section 5.2.7 of the Prizm User Guide.
37
Element Discovery Migrate from BAM

Users migrating from BAM 2.x to Prizm can migrate the element data already existing within the BAM software: Create a .bam file Import elements from the .bam file into Prizm When migrating elements from BAM into Prizm, the operator must then specify whether elements will be provisioned for bandwidth & authentication functionality only, or for full element management. Ability to import the .bam file is available to users with Administrator status within Prizm. Details on this process can be found in Section 5.2.8 of the Prizm User Guide.
38
Student Guide
Selecting a Default Network for Element Discovery

Select Edit Default Network Settings

39
Step 4: Confirm Network Elements

Auto-discovered or uploaded elements are placed into a Discovered Elements List in Prizm. Elements must be accepted into the network before Prizm will manage the elements. Elements are accepted for either bandwidth & authentication-only or full Prizm management operations. Users can tell Prizm to ignore the element, or delete the element from the list. Users can add element groups to provide their own element organization scheme in Prizm (for example, group a CMM-2 with its corresponding APs or BHs, or reflect a regional distribution of elements).
40
Student Guide
Performance Tips: Element Discovery

The Discovered Elements List window lists all elements identified by Prizm during the discovery process. The Mode field indicates how each element was discovered: Authentication Rejected: Bandwidth/ Authentication function rejected the element. Discovered Linked: CPE device discovered through its relationship to a master device (AP, BH, Gateway) Discovered SNMP: Discovered with accessible SNMP Discovered HTTP: Discovered by HTTP Review the elements Mode field to determine whether additional or corrective action may be required for the elements. Review all elements listed as generic to confirm they are listed correctly.
41
Accepting Network Elements (1)

1. From the Network menu, select Define Networks.

42
Student Guide

1. From the Network menu, select Define Networks. 2. From the left-hand pane, under the desired network, click on Discovered Elements.

43

1. From the Network menu, select Define Networks. 2. From the left-hand pane, under the desired network, click on Discovered Elements. 3. From the right-hand pane, select (with checkbox) the elements to be accepted.

44
Student Guide

4. Use the Edit menu to accept the elements for bandwidth & authentication, or for full Prizm element management. Operators can forbid element reboots during the accept process.

45

Bandwidth Service Plans
Full Prizm Management: Elements accepted without authentication required are given values that match the default bandwidth service plan. Verify these values are correct, or change them, or apply the appropriate bandwidth service plan to the elements. Bandwidth/Authentication Operations: As part of the accept process, Prizm prompts operators to assign a bandwidth service plan to the element(s) being accepted (Provision Network Elements window). VLAN profiles can also be assigned, if desired.
46
Student Guide
Provision Network Elements Window

47

Depending on the size of the network, the accept process may take some time. A progress bar and an Accepting Elements management console window will be displayed. Subject to licensing, operators can change an element from bandwidth/authentication-only operations to full Prizm management.

48
Student Guide
Installation Tip: Setting up the CMM4

Prizm includes monitoring and management of the Cluster Management Module-4 and its EtherWAN switch. The CMM4 and the EtherWAN switch are discovered and listed separately within the Prizm system: CMM4 icon: CMM4 EtherWAN switch (generic switch icon): Before installing the CMM4, read and note the MAC addresses of the module and the switch. After discovery of the CMM4 and the switch, use the MAC addresses to move the switch to its associated CMM4.
49
Range of Element States in Prizm

Prizm provides a management state attribute for elements: Managed: fully managed by Prizm Provisioned: Bandwidth/Authentication only Suspended (Management): Prizm management was suspended; registration and BAM provisioning can still occur. Suspended (Authentication): Bandwidth/ Authentication management was suspended; no authentication allowed. Accepting: was Provisioned, but upon next registration will be fully Prizm managed.
50
Student Guide
Communication Options
Prizm can communicate with CPE devices in two ways: Routing the communication to an IP address By SNMP proxy, requests sent through the proxy in the AP/Powerline MU gateway to CPE device
Canopy AP must be running system release 8 or later Use SNMP Proxy if Available checkbox is checked in Prizm, when network is defined No routable IP address associated with the CPE device Uses port 61002 on the AP/gateway

51
Installation Tip: Firewall in Certain Modules
An optional high-level firewall can be set on a permodule basis (Canopy Release 8) If enabled, then the Prizm servers IP address must be listed in the modules IP Access Control parameters.
Use the modules Configuration page - Security tab to enable the IP Access Control feature, and then enter the corresponding Prizm servers IP address.
52
Student Guide
Questions?

53
Section 4 Monitor Elements

Relationship of Polling, Alerts, and Notifications Defining Polling, Alerts and Notifications Element Tags Processing of Alerts Performance Tuning

Student Guide
Definitions
Event: Activities within the network being monitored, that are recorded by the Prizm system. These can be initiated by elements, by the Prizm system, or by users. A sub-classification of Events, generated either by element traps or defined through the Prizm Alert Definition screens. An alert requires an acknowledgement (autoacknowledgement is supported). Alerts can also trigger a notification message. Message sent to a user account when alerts of a defined filter criteria occur. Message sent is configurable by user, lengths can be customized. Periodic checks that Prizm conducts to gather information from the MOTOwi4 network devices being managed.
Alert:
Notification:
Polling:

55
Example Process Flow Polling, Alerts & Notifications within Prizm

Setup
Network operator defines alert parameters and notification procedures
Polling
Prizms Polling Service collects information from network elements via SNMP Prizms Polling Service updates the database with information collected.
SQL database

56
Student Guide

Alerts
Network operator defines alert parameters and notification procedures Prizms Polling Service collects information from network elements via SNMP Prizms Alert Service periodically checks the database for alert conditions. Prizms Polling Service updates the database with information collected.
SQL database
Parameters exceeded?
Yes Log an Alert

in the database.
No

57

Notifications
Network operator defines alert parameters and notification procedures Prizms Polling Service collects information from network elements via SNMP Prizms Alert Service periodically checks the database for alert conditions. Prizms Polling Service updates the database with information collected.
SQL database
Parameters exceeded?
Yes Log an Alert

in the database.
No
Send notification based on predefined parameters.
Prizms Notification Service periodically checks the database for alerts logged.
Alerts exist?
Yes
No
58
Student Guide
Key Points: Polling, Alerts, Notifications
Key Point: Using Prizm Effectively
Timing matters. Schedule more frequent alert and notification checking for critical system events. Once you set up the polling, alerts and notifications to support your operations, then let Prizm do the monitoring of your network. Only the most recent polling information is in the SQL database. For views of data captured over time, create and view historical reports.

59
Alert Setup in Prizm

Users define alerts within Prizm, specifying the criteria that must be met to trigger each alert. User can customize any criteria to fit the needs of their element monitoring and management. (See User Guide, Section 5.3.2) Can select from pre-defined alerts in Prizm (See User Guide, Section 5.3.3) Select whether alerts should be manually cleared or automatically cleared. Select whether a color change will be displayed for the relevant network element (yellow, orange, reddish-orange or red).

60
Student Guide
Defining Alerts within Prizm

First use the Events Define Alerts menu option to display current alerts in the system, sorted by Source and User.
Then use the Edit menu to either add a new alert or add a predefined alert.

61
Predefined Alerts List

Prizm includes the following predefined alerts that can be activated for your network.

62
Student Guide
Predefined Alerts Detail

Users can add the predefined alert as defined within Prizm, or they can edit the alerts parameters to customize the alert for their network.

63
Adding New Alerts Detail

Fields to define for a new alert are the same as the fields defined for predefined alerts. Alerts should have a unique name assigned. Use the Source field to group similar types of alerts.

65
Student Guide
Acknowledging and Clearing Alerts

Acknowledge: Temporary state, indicates the item is being worked. Prizm will not trigger duplicate alerts. Cleared: Condition that triggered the alert has been resolved.
Manual: Use for alerts that require immediate action be taken
Example: Alert generated when an AP goes down.
Automatic: Use for alerts that create historical entries in the log
Example: Alert that runs once per day to log the number of active SMs in a network.
66
Use the Acknowledge state to track open work items

Import/Export of Alert Definition

An alert definition can be saved off as an XML file, and then reloaded into Prizm. Select the alert from the list in the Define Alerts window. Select File Import/Export, then: Export Alert to create the XML file. Import Alert to reload the alert definition.

67
Student Guide
Other Allowed Actions for Alerts

Within Prizm, you can perform the following additional actions pertaining to alerts: Modify alert configuration Activate or de-activate an alert Trigger alert to run immediately Create or reload alert definition file in xml Delete the alert Reset the alerts history Set a delay offset for all alerts Set a minimum time period for users or administrators Each of these tasks is detailed in the Prizm User Guide, within Section 5.3.
68
Define an Alert Notification

Notifications must be defined before Prizm will send messages to users and/or administrators when events trigger alerts. Notifications are grouped and mailed based on the parameters defined for the notifications (See next slide). Notifications are sent once per time period specified, for all alerts that match the criteria for the notification.

69
Student Guide
Customizing Notifications
Source: unique ID for grouping multiple alerts into one notification. Scope: private (alerts tied to one user ID) or shared (all users). Severity: Options correspond to definitions set by International Telecommunications Union. Period: frequency for notifications to be sent, ranging from 5 minutes to 24 hours. Address(es): Enter recipient addresses for any of three formats: long, medium, or short. Suspend: Select checkbox to stop notification from being sent, without deleting the definition from the system.
See Prizm User Guide, Section 5.3.13
70
Element Tags as Additional Filters

Text labels known as element tags can be applied to elements within the Prizm system. Element tags are optional. Use element tags within Prizm for additional filters or identification of a subset of your network components. Element tags are not passed to the element or to any other MOTOwi4 device. Using element tags, you can create any number of categories to meet the monitoring needs of your network.
71
Student Guide
Setting Up Element Tags (1)

First, select the element to be tagged by placing a checkmark in the box next to the element name. Then, select Edit Network Element Operations - Edit Element Tag(s) from the menu.

72
Setting Up Element Tags (2)

A list of available element tags will display. Select any of the available tags with a checkmark to apply those tags to the element identified; - or Select the New Tag button to open the Add New Tag window. Each new tag can be identified as Private, Shared or Controlled when defined.

73
Student Guide
Using Tags When Defining Alerts

When adding new alerts, you can limit the alert to elements that contain a specific element tag. To do this, select the down arrow next to Criteria in the Define Alert window. This opens the Specify Element Criteria window, pictured here. When you select the down arrow under Element Tag, all available element tags are displayed. You can then select the element tag which should be applied for this particular alert.
74
Lab 1 Events and Alerts

View a filtered Event List. Define an alert. Define a notification.
Prizm

75
Student Guide
Lab 1 Tasks to Complete

1. Launch Prizm and log in to your user account. 2. Define a filtered event view on informational events occurring within the past 12 hours. (See User Guide, Section 5.3.1). 3. Define an alert for elements going offline (See User Guide, Section 5.3.2). 4. Define a notification so that an email message is sent to you when the offline alert is triggered (See User Guide, Section 5.3.12). - End of Lab Motorola: For General Business Use, CPT400v6.pdf
76
Tips Regarding Alerts & Notifications (1)

To customize notifications: When defining alerts, create a unique identifier in the Source field. Use this unique identifier when defining notifications. In this way, you will receive notifications for that group of alerts. Example 1: Create multiple Source categories that reflect tiered service levels in your network. Define alerts that match the service level criteria, such as upload / download capacity, or that would notify you when service was degraded. Use the tiered Source categories to set how often notifications are sent. Example 2: Create Source categories to reflect different types of equipment in your network, such as Advantage or nonAdvantage. Set alerts and notifications relevant to the performance expectations for each type of equipment.
77
Student Guide

Watch system performance: The time period frequency defined for Prizm to send notifications can affect overall system performance. For example, setting a time frequency of 5 minutes for a large network will consume some bandwidth. Monitor your networks performance after youve set up alert and notification parameters. Consider setting longer time periods for non-urgent messages (every 12 or 24 hours, for example). Use more frequent notifications sparingly: for example, with Major or Critical alerts, or for a small portion of a network that needs closer monitoring.
78

Set up different notifications for different devices: You can send long, medium, or short notification messages to different devices. Use this flexibility to control the number of messages sent out, and to take advantage of different device types. For example, send a short message to a pager for Major and Critical alerts. Send medium or long message to an email account. The subject line of the notification does not indicate the message length of short, medium, or long, so avoid sending duplicate messages to the same account; the user will have to open the redundant messages.
79
Student Guide
Questions?

80
Section 5: Templates & Profiles

Configuration Templates Bandwidth Service Plans VLAN Profiles

Student Guide
Defining and Using Templates

With templates, you can set up and apply consistent element configurations across your network. Use Network Define Configurations to view existing configuration templates. Use Edit Add Configuration Custom Configuration or Edit Update Configuration to add or change templates. Templates can be applied to individual elements, or to branches of a network. Be sure the MOTOwi4 modules are updated to the current software release before applying templates.
82
Template Parameters
The available parameters for templates correspond to the configuration parameters for MOTOwi4 modules.
See Section 8.3.2 of the Prizm User Guide for lists of the parameters that can be defined in a template.
83

Student Guide
Demo Defining Templates
Prizm
See Prizm User Guide Section 8.3, Using Canopy Element Configuration Templates, to follow along with the demo.
84
Additional Template Options

Templates can be copied & modified to quickly create similar sets of configurations. Timing of the module reboot is up to the operator: Can perform reboot when template is applied Can manually reboot each module from the modules web pages Can ask Prizm to reboot modules at a later point in time Use the History tab of the element details pane to view previous and new values for the configuration parameters.
85
Student Guide
Sample Element History Window

86
Tips for Using Templates

Set up templates that reflect the different service levels you offer clients. Apply the appropriate template as new customers are added, for ease of use and consistency within your network. Create smaller templates with descriptive names, to make your management easier. Use the template grouping capability to keep your configuration menu options clearer. Make copies of templates with different values for different purposes, such as clear field template, standard value template.
87
Student Guide
Performance Tip: Identifying Configuration Changes

Operators can set up alerts to notify them when an elements configuration value has changed. Use Element Tags to identify the elements that should be checked for this occurrence. Set up an alert to be notified when a value from the previous Prizm-initiated configuration has changed. If the alert is generated, use the Configuration History tab in the elements Detail pane to view the parameter, its previous and its present values.

88
Managing Bandwidth with Prizm

1. Establish data transmission rates using a configuration template Useful for individual module adjustments 2. Define a bandwidth service plan Can apply to a group of modules Useful for enforcing tiered service plans Any changes made to a plan are automatically applied to all affected modules 3. Use either #1 or #2 from an external network manager through the Northbound Interface to Prizm
89
Student Guide
Defining Bandwidth Service Plans

Operators can define service plans using Network Define Configurations, then Edit Add a Configuration Bandwidth Service Plan.
Note: If you import element information from the BAM system, Prizm will create service plans that reflect those elements configurations.
90
Options for VLAN Configuration in Prizm
1. Establish VLAN attributes using a configuration template Useful for individual module adjustments 2. Define a VLAN profile Can apply to a group of modules Useful when establishing VLANs in your network Any changes made to a profile are automatically applied to all affected modules 3. Use either #1 or #2 from an external network manager through the Northbound Interface to Prizm
91
Student Guide
Applying VLAN Profiles

VLAN must be enabled on the Canopy AP. CPE must be authenticated before it can accept a VLAN profile. How and when VLAN profiles take effect depends on how a module entered the network. Most effective scenario: CPE device is authenticated, then the applicable VLAN profile is applied; no reboot required. See Table 25 in the Prizm User Guide for other scenarios that can occur for applying VLAN profiles.
Note: If you import element information from the BAM system, Prizm will create VLAN profiles that reflect those elements configurations.
92
More on VLAN Profiles

When an element is dissociated from a VLAN profile, the element retains the last VLAN values that were applied, but does not accept additional profile changes. If VLAN is disabled for a CPE, the CPE must be rebooted before that change goes into effect.

93
Student Guide
Define VLAN Profile
Operators can define VLAN profiles on the Network Define Configurations menu, then selecting Edit Add a Configuration VLAN Profile.

94
Questions?

95
Student Guide
Section 6: Network Security

Authentication Passwords User Security

Prizms Authentication Feature
Authenticate each CPE device that attempts to register to an Access Point or Powerline MU gateway. Assign floating licenses (if necessary and available) to support software features. Suspend individual CPE devices, which stops ongoing monitoring but retains configuration data and history. Re-activate suspended modules. (optional) Integrate with a service providers RADIUS server for RADIUS-based authentication.
97
Student Guide
Authentication Set-up
If using redundant Prizm servers for bandwidth & authentication, make sure all servers IP addresses are listed with all APs/gateways. Use the Edit Configure Authentication Settings AP Authentication menu to assign authentication server IP addresses.

98
Demo Bandwidth & Authentication Using Prizm
d idth an Bandw n nticatio Authe m in Priz

99
Student Guide
Changing Element Management Passwords
Administrators can set, change or remove element passwords. (Optional) Select the elements that require password changes. Use the Edit Network Element Operations Configure Security Clear Passwords menu to open a Task Attributes window. Enter the desired passwords for display and/or management of the elements. If elements not already selected, use search criteria to define the elements to be changed. Select the operation to Run Now or Run Later.
101
Change Element Passwords: Task Attribute Window, General Tab
Use the ellipsis buttons to change the passwords.

102
Student Guide
Change Element Passwords: Task Attribute Window, Elements Tab
You can add or remove elements from the list, or use Selection Criteria to define broader categories for applying the change.
Choose to run the operation now or later.

103
User Maintenance
Two type of user accounts, administrator and user. Users can be assigned different access levels within Prizm: read, write, admin. Different permission levels can be set for different networks defined within Prizm. Different permission levels can be set for the different functions available within Prizm. Custom, controlled views can be defined, and then permissions set per user to access those views.
For details on user maintenance, see Section 4.5 and Section 11 in the Prizm User Guide.
104
Student Guide
User Maintenance: Other Security Features
Administrators can: Set up access to a specific set of elements and/or views. Better control of users access to network information Configure security policies per user Access attempts, user password rules, user session rules Create login banners to display system-related messages Can be applied to all users or specific users

105
User Maintenance: Add or Change User Accounts

Select Tools Administrator - User Manager. From the User Manager tab, select Edit Add User or Edit Update User. Complete information in the General tab.

106
Student Guide
Add or Update User Account, Security Tab

107
Add or Update User Account, Permissions Tab

108
Student Guide
Global Settings for User Accounts

Use File Settings Edit Settings for preferences and security policies that affect all user accounts.

109
Global Settings, Security Policies

110
Student Guide
Creating System-Wide Messages
Within the User Manager, select the Banners tab and then Edit Add Banner to create systemwide banner messages that display at login.

111
Questions?

112
Student Guide
Section 7: Management with Prizm

Reporting User Task Scheduler Customer Manager Software Development Kit Server Administrator Tool Northbound Interface

Reporting within Prizm

Prizm supports multiple methods for viewing and saving the data that is generated within the system. Online Reports Printing Reports Data Export PDF or Text File

114
Student Guide
Online Reports
Online Reports are any display of information within the Prizm system. Use File Print or File Print Preview to change the online view into report format. Examples: Event Log, Filtered Event List (custom defined), System Log (administrators only).

115
Printing Reports
Printing Reports: Any view within Prizm can be formatted and printed as a report, either hard copy or electronic.

116
Student Guide
Selecting and Customizing Reports (1)

If you have selected elements from a network view before selecting File Print, then you will be prompted to select the type of report you wish to view.
Depending on the report selected, you can further choose the information to be displayed.
117
Data Export
Data Export The data displayed by Prizm can be exported to .CSV, .XML, .XLS, or .NET file types.

118
Student Guide
PDF or Text File

PDF or Text File From the Print Preview display, you can save the report as a PDF file or plain text file.

119
Tips for Prizm Reporting

Use the tabs (both horizontal and vertical) to view several different types of information about network elements.

120
Student Guide
Customizing Report Details

Use the Columns button to then choose the information you want to view on screen.

121
Lab 2 Viewing and Customizing Reports

Create both standard and custom online reports. Export reports to various file formats. Print a report. Customize online graphical display of element details.
Prizm

122
Student Guide
Lab 2 Tasks to Complete (1)

1. Launch Prizm and log in to your user account. 2. View the Event Log online (See User Guide, Section 6.2.1). 3. Create a custom online report by filtering the event set (See User Guide, Section 6.2.3). 4. Export an online report to a text file (See User Guide, Section 7.3.2). 5. Using the custom online report created in step 3, select File Print Preview or File Print to see a printed version of the data. Be sure to print to PDF for this lab. - continued Motorola: For General Business Use, CPT400v6.pdf
123
Lab 2 Tasks to Complete

6. Customize an online graphical display of element details. 1. Open a network view. 2. Highlight an element in the list. 3. Click the Show Details button. 4. Select the Statistics tab, then one of the following tabs: Summary, Ethernet Traffic, RF Link or RF Traffic. 5. Use the Customize button to change the graphical display. 6. Use the View Data button to see tabular presentation of information. - End of Lab -

124
Student Guide
Viewing Licensing Information

The Help Show Licensing menu will provide details on the numbers of licenses in use by Prizm.

125
Task Scheduler Overview

Use Prizm to more effectively manage the network and Prizm itself. Set up a variety of tasks to be run whenever the operator chooses. Save task setup for easier repeat efforts. Create follow-up reports to track if any tasks failed, or were only partially completed.

126
Student Guide
Task Scheduler Categories

Users can schedule any of the following types of operations: For elements: clear logs, configure, reboot, update software or firmware Within Prizm: Activate or suspend accounts, activate or suspend management by Prizm, refresh element data, send local information to Tech Support. Select Tools Task Scheduler, then Select Edit Add New Task to open the Select Task Category dialog box (see next slide).

127
Example 1: Element Configuration Task (1)
Select the category for the task to be performed. In this example, we are setting up a configuration change for network elements.

128
Student Guide

Enter a name for the task. Select Modify Attributes to set up what is to be changed, for which elements.

129
From the Task Attributes window, select the Elements tab, then define the selection criteria for the elements to be changed.

130
Student Guide
In this example, we are changing the polling interval for certain elements.

131
Select Modify Schedule to set up when, and how often, the task should run.

132
Student Guide
Set up the desired scheduling options and timing for the task.

133
Example 2: Software Upgrade

Step 1: Load Software Package
Use File Settings Edit Settings Select Manage Packages to load software packages into Prizm, before running an upgrade job via the Task Scheduler.

134
Student Guide
Example 2: Software Upgrade

Step 2: Set up in Task Scheduler
Use Tools Task Scheduler, then Edit Add New Task. Select the appropriate task in the Software Updater category. In the Task Configuration dialog box, enter a name for the task. Next to Attributes, select the Modify button. Use the Task Attributes dialog box to set up the details for the software upgrade (see next slide).

135
Example 2 Software Upgrade, Task Attributes

Use the Configuration tab to complete the settings and selections for the software update job. Use the Packages tab to select the particular software package to be applied.
Use the Elements tab to select the elements for the upgrade.

136
Student Guide
Example 2 Software Upgrade, Scheduling

Back in the Task Configuration dialog box, select Modify Schedule to set the timing (and frequency) for the job to be run.

137
Task Scheduler Additional Details

More details on tasks, and examples, are available in the Prizm User Guide, Section 11.7.

138
Student Guide
Customer Manager
With the Prizm Customer Contact Manager, you can: Maintain basic customer contact information tied to specific MOTOwi4 network elements Import customer contact data into the Prizm system (.csv file format, using format defined within Prizm). Tie any number of MOTOwi4 network elements to a unique customer record. Use Prizm to send email to an individual customer or group of customers. Set user permissions for accessing and updating this type of information, maintain security of the data.
139
Adding Customer Information

From the Tools menu, select Customer Contact Manager. From the Edit menu, select Import Customer(s) to import a .csv file of customers with contact information. (Reference the Prizm User Guide Section 7.4.1 for file format.) From the Edit menu, select Add Customer, Update Customer or Delete Customer to perform the desired action on an individual customer record. Use the Update Customer option to associate a customer with a specific network element.
140
Student Guide
Additional Administrative Functions

Software Development Kit: provides instructions, code examples and details for customization of Prizm operations. A Community Forum exists on the Canopy website for users of the SDK. Server Administrator Tool: start or stop the Prizm server; update server configuration; update database configuration.
For details on these and other administrative options, see the Prizm Administration Guide.
141
Other Management Tips

Use the archive capability of the Prizm systems maintenance operations to retain MAC/IP address data offline. You may need this data to respond to inquiries from authorities investigating improper Internet use. Administrators can access a MOTOwi4 elements web pages through Prizm. The read-write permissions defined in Prizm transfer to the module pages. (See User Guide, Section 8.7).

142
Student Guide
Questions?

143
Course Wrap-Up

Student Guide
Additional Resources Prizm

Extensive information is available in the Prizm documentation: User Guide, Administration Guide, Release Notes and Setup Guide. Use the Canopy Users Forums to interact with other users of Canopy products and Prizm. View the materials available on the Canopy website relating to Prizm, also the Knowledge Base and the Channel Members site (if available to you).
145
Please complete a course evaluation.

146
Student Guide
Appendices
Prizm Deployment Considerations Review: SNMP and Trap Information

Prizm Deployment Considerations

148
Student Guide
Prizm Deployment Key Decisions

When planning your purchase and installation of Prizm software, three key decisions will guide your hardware purchasing and equipment setup. Will you run a single server or redundant server configuration for bandwidth/authentication and license management? What operating system will you use? How many elements do you plan to manage within your network?

149
Prizm Deployment Redundancy Planning
Authentication Redundancy:
Provides a backup for SM authentication and bandwidth settings Can be deployed with up to 2 redundant servers for each Prizm server
License Management Redundancy:

The License Manager software tool receives requests and issues authorization to run a specific piece of software. Can be deployed as a single server, or 3 servers for high availability. No charge download from Canopy website.
Database Redundancy:
Each Prizm server requires access to a database. If the databases are separate, they need to be synchronized, either manually or by using the database engines tool. Prizm does not perform this synchronization.
150
Student Guide
Prizm Deployment Example Configurations

The Two Most Common Configurations
Configuration 1: Single Server Configuration 2: Three Servers
Server 3
LM
Server 2
DB
Redundant Server
LM
Server 1
DB
Server 1
Prizm Server
LM
DB
Prizm Server
LM

151
Prizm Deployment Licenses

Prizm requires both per-server and per-element software licenses.
Prizm server license kit includes a server license and 10 Prizm license packs Optional: Up to two redundant server licenses can be added for bandwidth and authentication functionality only A Prizm Element License Pack is required for each:
Canopy AP PTP 100/400/600 ( 1 per each link ) Powerline MU Gateway
1. Per-Server Licenses
Prizm 3.0 Server License Kit Optional: 1 or 2 Redundant Server License(s)
2. Per-Element Licenses
Element Prizm Element 3.0 Element Licenses Licenses License Pack
No separate license packs are required for CPE devices
3. Floating Feature Licenses

Element Element Canopy Lite SM Licenses Licenses Throughput Upgrades License
Prizm is required for managing the floating optional radio features including:
Canopy Lite SM throughput upgrades Advantage SM upgrades
Element Element Advantage SM Licenses Licenses Upgrade License
152
Student Guide
Prizm Deployment OS & Element Count
Hardware Option A Windows Operating System Red Hat Enterprise Linux v4 Managed Element Count Yes Yes
Hardware Option B No Yes up to 25,000 elements
< 10,000 elements
Note: Prizm currently operates on a 32-bit OS, not 64-bit. A 64-bit version of Prizm is planned for a future release.
153
Prizm Deployment Hardware Options

Hardware Option A: Dell Precision 390*
Processor: Intel Core 2 Duo E6400, 2.13 GHz/ 1066 MHz/ 2 MB L2/Dual core/ VT OS: Windows XP Professional Memory: 4 GB, 667 MHz, DDR2 SDRAM memory Precision 390 32-bit Other features not listed here, complete specs available in the Prizm Deployment Guide.
Hardware Option B: PowerEdge 1900*

Processor: Dual Core Intel Xeon 5130, 4 MB Cache, 2 GHz, 1333 MHz FSB OS: Windows Server 2003 R2, Standard x64 Edition, includes 5 CALs Memory: 8 GB, 667 MHz (8x 1GB), Dual ranked fully buffered DIMMs Other features not listed here, complete specs available in the Prizm Deployment Guide.
*or equivalent machine, following the specifications provided. Prizm Deployment Guide can be found on the Canopy website.
154
Student Guide
Prizm System Installation Requirements

Prizm Server
32-bit operating system only: Red Hat Enterprise Linux version 4 OR Windows 2000, 2003, XP Pro One of the following databases: Microsoft SQL Server Enterprise Edition 2003, MySQL 4.1, or Postgres 8.0 Java 2 Runtime version 1.5.06 or greater
Prizm Client
Windows or Linux operating system Java 2 Runtime version 1.5.06 or greater (Windows or Linux OS) One of the following web browsers: Microsoft Internet Explorer version 6 or greater; Netscape version 7.n or greater; Mozilla version 1.4 or greater; Firefox version 1.5.n or greater
See the Prizm User Guide and current Release Notes for details.
155
Prizm and RADIUS

Prizm supports maintenance of CPE device authentication and bandwidth configuration on a RADIUS server. Prizm acts as proxy server between the AP and the RADIUS server. Prizm passes authentication and bandwidth configuration information from RADIUS to the AP. The Prizm GUI and the AP cannot be used to change the information stored on the RADIUS server. Using Prizm, operators can see latest values that RADIUS passed to the elements. When RADIUS is used, certain Prizm commands are not available, such as import/accept elements for bandwidth & authentication provisioning, activate/suspend authentication accounts, or assign bandwidth service plans.
156
Student Guide
Review: SNMP and Trap Information

157
Review SNMP Commands

SNMP is comprised of three basic commands: Get: The monitoring software retrieves data by way of an agent from the managed device Set: The monitoring software changes data on a managed device by way of an agent Trap: The managed device sends an unsolicited message to the monitoring software

158
Student Guide
Prizms Use of SNMP

Prizm uses SNMP (Simple Network Management Protocol) to communicate with and manage MOTOwi4 network elements. Prizm will periodically poll the network devices to gather information stored in the MIBs. (SNMP get) Prizm will change MOTOwi4 network device settings using configuration templates (SNMP set) Prizm will receive SNMP traps sent by the network devices (SNMP trap) Prizm includes an SNMP agent for integration with a network management system
159
Traps Sent by AP Modules

GPS sync lost GPS sync established Subscriber Module registration lost Subscriber Module registration completed Radar signal detected Radar signal no longer detected
Advanced Programming Note: Additional traps can be defined, but should be done so with caution. See the Prizm Administration Guide for instructions.
160
Student Guide
Resources for SNMP and MIB Information

SNMPv1 RFC1175 SNMPv2 RFC1902 SMI (Structure of Management Information) RFC1155 Canopy System User Guide Section 24, Managing Through a Network Management Station, discusses SNMP and MIB in relation to the Canopy system. Canopy website Knowledge Base (found under the Support menu) of www.canopywireless.com; search for SNMP and/or MIB. SNMP White Papers: http://www.david-guerrero.com/papers/snmp http://www.cisco.com/univercd/cc/td/doc/cisintwk/ito_doc/snmp.h tm
161

CPT400 Version 6 Student Guide

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

CPT400 Version 6 Student Guide

Hochgeladen von

Copyright:

Verfügbare Formate

CPT400 - Network Management Training, v6

CPT400: Network Management Training

Motorola: For General Business Use, CPT400v6.pdf

Course Objectives (page 1 of 2)

Motorola: For General Business Use, CPT400v6.pdf

CPT400 - Network Management Training, v6

Course Objectives (page 2 of 2)

Motorola: For General Business Use, CPT400v6.pdf

CPT400 - Network Management Training, v6

CPT400 within Overall Curriculum

CPT100: Overview of Canopy, RF and IP concepts (one day)

CPT300: Advanced Canopy Training (one day)

CPT400: Network Management Systems (one day)

Motorola: For General Business Use, CPT400v6.pdf

Motorola: For General Business Use, CPT400v6.pdf

CPT400 - Network Management Training, v6

Section 1 Understanding Network Management

Motorola: For General Business Use, CPT400v6.pdf

What Happens When

Motorola: For General Business Use, CPT400v6.pdf

CPT400 - Network Management Training, v6

What Happens When

What Happens When

Motorola: For General Business Use, CPT400v6.pdf

CPT400 - Network Management Training, v6

Discussion Identify Network Management Concerns

Motorola: For General Business Use, CPT400v6.pdf

Motorola: For General Business Use, CPT400v6.pdf

CPT400 - Network Management Training, v6

Section 2: Prizm System Overview

Motorola: For General Business Use, CPT400v6.pdf

What is the Prizm System

* Limited configuration management for high-speed PTP products.

CPT400 - Network Management Training, v6

Prizm Interface Points

License Manager Database files Network elements

Prizm Element Management Function & Features

CPT400 - Network Management Training, v6

Prizm Fault Monitoring Features

Prizm Configuration Functions & Features

CPT400 - Network Management Training, v6

Prizm Performance Monitoring

Prizm Task Scheduler

Motorola: For General Business Use, CPT400v6.pdf

CPT400 - Network Management Training, v6

Demo Prizm User Interface

Motorola: For General Business Use, CPT400v6.pdf

Recap Prizm GUI Features

Motorola: For General Business Use, CPT400v6.pdf

CPT400 - Network Management Training, v6

Motorola: For General Business Use, CPT400v6.pdf

Section 3 Network Definition & Element Discovery

Motorola: For General Business Use, CPT400v6.pdf

CPT400 - Network Management Training, v6

Steps for Defining Network

Step 1: Identify Network in Prizm

CPT400 - Network Management Training, v6

Step 2: Specify Subnet Configurations

Motorola: For General Business Use, CPT400v6.pdf

Define Subnet Configuration Window (1)

Motorola: For General Business Use, CPT400v6.pdf

CPT400 - Network Management Training, v6

Define Subnet Configuration Window (2)