© 2015 SpiderCloud Wireless, Inc. SCT-320 USC8050 Overview September 28th, 2015.

Author: Wilson Erique

0 downloads 2 Views

2 © 2015 SpiderCloud Wireless, Inc. Session Overview  Objective: To understand the installation, operation, and capabilities of the USC8050 management console.  Assumptions: The USC8050 server software is already installed at your site.  Lab Objectives: Configure USC8050, schedule periodic tasks, and view and search for USC8000 inventory. 2

3 © 2015 SpiderCloud Wireless, Inc. Class Agenda  Overview  Installation  USC8050 Client and User Interface  USC8050 Server Redundancy  Fault Management  File Operations / Upload Manager  Performance Monitoring  Common Tasks (Templates, Backup, Software Updates) 3

5 © 2015 SpiderCloud Wireless, Inc. USC8050 at-a-Glance  USC8050: Multi-tenant, Java-based GUI used to configure, manage, and monitor the USC8000.  Management Hierarchy: USC8050 manages the USC8088, which itself manages a network of USC8738. USC8050 connects to the core using the TR-069 protocol. It uses SNMP and syslog for notification.  Security: All traffic is sent through an IPsec tunnel. Users are segregated via Role-Based Access Control (RBAC), and optionally, SCP.  Location: The USC8050 server resides in the mobile operator core network, behind the security gateway.  Key Performance Indicators (KPIs): Collect, report, and export per USC8088. User-specified time frame with predefined and custom KPIs. 5

6 © 2015 SpiderCloud Wireless, Inc. USC8088 Configuration and Provisioning  TR-069 Standards-Based – TR-069: USC8088 configuration through the TR-069 interface – Purposes: Synchronizes USC8088 and USC8050 configurations  Tasks – One-Time On-Demand Tasks: Enable/disable cells, clear statistics, reboot – Scheduled Tasks: OS upgrades, network changes, KPIs, backups, log bundles – Advanced: Access to all parameters in the USC8000 data model  Configuration Templates – Create/modify/delete templates for commonly applied parameters – Templates tied to specific software version(s) – Can be applied to multiple USC8088 at once for consistent provisioning 6

8 © 2015 SpiderCloud Wireless, Inc. USC8050 Server Requirements  Server: Dedicated Intel Xeon 6-core 2.4 GHz or equivalent, 64-bit, 16 GB RAM, 1 TB free disk space for the partition containing the server and database.  OS: CentOS 5.8 or greater, RedHat Enterprise (RHE) 6.3 or 6.4. Install MySQL as a startup service before installing USC8050.  Secure: All traffic sent over an IPsec tunnel. Users are segregated via role-based access control.  Licensing: Per server instance.  Refer to the USC8050 Management System Installation and Administration Guide for the complete USC8050 server requirements. 8

10 © 2015 SpiderCloud Wireless, Inc. CentOS Install  CentOS Install: – Obtain / configure a static IP address. – Select Server then Customize now. – Highlight Servers and check MySQL.  Startup: USC8050 and MySQL will run as system services at startup. 10

11 © 2015 SpiderCloud Wireless, Inc. CentOS Security  Server Firewall: – Select FTP, SSH, and HTTPS. – Other ports must be manually entered.  Network Firewall: Permit access to/from these ports.  Details: The following ports are only used for outbound USC8050 traffic: – 53 (DNS queries) – 123 (to query NTP servers) – 161 (SNMP keepalives) – 7547 (to contact USC8088) 11

12 © 2015 SpiderCloud Wireless, Inc. Manual MySQL Install  Purpose: If Linux was provisioned without MySQL:  1. Remove any previous version of MySQL and its libraries from the USC8050 server.  2. Remove any other vestiges of the previous MySQL installation.  3. Download the software from the USC8050 customer support portal (support.spidercloud.com).support.spidercloud.com  4. Install the server and client RPM files.  5. Start the MySQL server and database services.  6. Change the MySQL administrative password and configure the server daemon to start on server boot.  7. Restart the MySQL process and verify the configuration. Refer to the USC8050 release notes for detailed instructions. 12

13 © 2015 SpiderCloud Wireless, Inc. Install USC8050  Install the USC8050 Package: – All 64 bit systems use “amd64”. – All 32 bit systems use “x86”. – Must run installer with root privileges. – Can run via wizard or command line.  Validate Install (optional, run on the USC8050 server) – service mysqld status – Service spidernet_server status  Operational Concerns – MySQL and USC8050 will auto-restart when server restarts. – Upgrades to the USC8088 OS require a new XSD file (data model) to be copied onto the USC8050 server. 13

14 © 2015 SpiderCloud Wireless, Inc. Install New Data Model Files  USC8050 installation files contain a default version of the data model in a file called USC8000.xsd.  Each USC8088 software version will have a corresponding version of an XSD file.  For example SCOS version 3.2.0 would have also produced a file named scos-3.2.0-data-model.xsd.  USC8050 must contain a data model file for every SCOS software version run by USC8088 that it manages.  USC8050 will use the XSD file corresponding to the USC8088 SCOS version if it is loaded onto the server, otherwise it will use the default XSD file to manage the USC8088.  Some parameters may not be functional with the default XSD. 14

15 © 2015 SpiderCloud Wireless, Inc. USC8050 Licensing  License Structure – One license per USC8050 server. – Each license can manage up to 400 USC8088. – The actual number of managed devices depends upon the licensing agreement.  Request License – Generates licensing request – Submit license request via email  Install License – License returned as file – Save file locally – Install file, server turns off – Restart server: Service spidernet_server restart 15

16 © 2015 SpiderCloud Wireless, Inc. Add a USC8088 to USC8050  You commission a USC8088 through the Local Configuration Interface (LCI)  Configure the USC8088 with the USC8050 IPv4 or IPv6 IP address and port number.  USC8050 monitors port 7547 for new USC8088 and adds them once they are detected. 16

17 © 2015 SpiderCloud Wireless, Inc. Link the USC8088 to USC8050  Purpose: Tell the USC8088 how to find USC8050.  Unique ID: Four parameters used to identify each USC8000: – Serial Number (not configurable) – Customer ID, Location ID, Cluster ID  Setup: Use the USC8088 (Local Commissioning Interface (LCI): – Select EMS then Manage EMS – Specify the USC8050 server IP address – Change EnableCWMP to true – The USC8088 will connect via port 7547 using the URL shown on the top of the screen 17

19 © 2015 SpiderCloud Wireless, Inc. USC8050 Client  Two Options: – Browser-Based HTTPS: Supports most standard browsers, Java required – Client: Downloadable Java client for Windows or Linux  Which Client? – Policy: If Java is disabled on browsers by group policy, use the client – HTTPS + Java: Runs on PCs, Macs, and Linux on all major browsers – GUI, User Experience: Identical interface  Who Has Access? Using RBAC, the client can be restricted to monitoring (read-only) or operational (r/w) staff  Browser URL : Must include https://  Concurrent Client Sessions: Limited by per license agreement 19

21 © 2015 SpiderCloud Wireless, Inc. Work Area  Context Sensitive: The display and actions vary depending upon the task selected.  Button Bar: At the top of the screen, activates work area panels, such as Inventory, Scheduled Tasks, Alarms, or Configuration Templates.  User Configurable Views: Each user can define up to two views for later reuse. 21

22 © 2015 SpiderCloud Wireless, Inc. Work Area (Inventory View)  Inventory: Information about USC8088, IP interfaces, USC8738, and cells.  Columns: Change per type of inventory.  Options: Screen display can be exported to CSV files or printed. 22

23 © 2015 SpiderCloud Wireless, Inc. Work Area (Configuration Panel)  Displays configuration states of components of selected USC8088 and its radios: – Equipment: configured USC8738 and radios – IP: Ethernet ports, forwarding tables, DHCP, QoS – UMTS: core, Radio Access Network (RAN), and cell – LTE: core, Radio Access Network (RAN), and cell – System Management: USC8088 information such as name, location, contacts, and USC8050 server connection – Advanced: for experienced users, more information on a later slide – Export All: export the USC8088 data model, see next slide for more information 23

24 © 2015 SpiderCloud Wireless, Inc. Work Area (Configuration Panel >> Export All)  Exports the current USC8000 system configuration (data model): – All writable parameters of the USC8000 – ASCII text that replicates the CLI configuration or XML for machine processing – Support for flat XML or structured XML – Select the format from a drop-down box when naming the file – Use to compare configurations and store system snapshots 24

25 © 2015 SpiderCloud Wireless, Inc. Work Area (Configuration Panel >> Advanced) 25  F or advanced users. Requires system knowledge and familiarity with the SCOS data model and its tree-based hierarchy.  Purpose : Setup uncommon USC8000 configuration changes  Step 1 : Select the Advanced tab.  Step 2: Locate and change the parameter (refer to the SCOS NB Data Model Reference Guide).  Shortcut : Enter a keyword into the filter box in the upper left of the screen. Matching database elements display.

26 © 2015 SpiderCloud Wireless, Inc. Tree View: Overview  Provides graphical representation of alarms, connectivity, and operational state of the USC8000  Expand and collapse elements for targeted topology viewing  Selecting tree view elements dynamically filters the content of the work area  Right-click elements for context sensitive commands, tools, and on-demand tasks  Right-click a USC8088 to view its configuration  Organize network into devices, subnets, subnet groups, and sites  Initiate ping, refresh, or open an SSH session 26

27 © 2015 SpiderCloud Wireless, Inc. Tree View: Grouping and Status  Group by location, subnet, customer  Quick search options  Device Status Pending configuration / alarms X Disconnected Maintenance Mode OK X Unmanaged  USC8088 right-click menu  Show configuration  Ping  SSH to USC8088  On-demand tasks  Place or remove from maintenance mode  Performance management 27

28 © 2015 SpiderCloud Wireless, Inc. Tree View: Options  One USC8088 can be placed into multiple groups.  Subnet groups are the default view.  Use Groups for USC8088 with some common attribute. Each USC8088 can only live in one Group.  All views are visible by default.  Access to specific views can be tied to user profiles. Question: Why might you restrict certain users to certain views? One answer: Operator responsibilities (per customer or per geography) 28

29 © 2015 SpiderCloud Wireless, Inc. Administration Tab: Overview  Manages: – Access Control: users, profiles, viewing permissions, authentication method, passwords, and connected users – Audit Trail: read-only display of system activities – Northbound Interface: alarm forwarding and SNMP agent settings – Email: email groups and SMTP parameters – Fault Management: event configuration and forwarding, custom events, and trap reception parameters, fault correlation, threshold crossing alerts – Server Settings: maintenance mode, file transfer, syslog server, and redundancy – Database Settings: server redundancy and single and dual database configuration – Geographical Maps: upload and remove map images – Performance Configuration: configure polling interval for predefined system and cell performance counters, and custom KPI creation and configuration

30 © 2015 SpiderCloud Wireless, Inc. User Management and Security  User Management – Add/modify/delete users and user profiles – Restrict users to specific workstation(s), views – Lock/logoff users – View connected users  Security – User authentication (username/password) – Enable external LDAP or RADIUS authentication – Authenticated and encrypted sessions (client-server) – Per user permissions (profile based) – Audit trail logging 30

32 © 2015 SpiderCloud Wireless, Inc. User Administration, Profiles  Setup privileges for groups of users.  Three preset roles: – Admin: access to view all screens and configure all USC8050 and USC8088 objects – Tech: access to view all screens other than the Administration tab and configure all USC8088 objects – Viewer: access to view all screens other than the Administration tab 32

33 © 2015 SpiderCloud Wireless, Inc. User Security Configuration Examples  Password Management – Structure: Enforce requirements (such as length, special characters) – Expiration: Parameters about when user must change password  Specific Workstation: Requires a specific username to access USC8050 via a specific IP address  Exclusivity: Permit or deny multiple users to login under one username at the same time  Force Logout: Select user, force disconnect  Lock Account: Prevents user from logging in 33

34 © 2015 SpiderCloud Wireless, Inc. User Security: External Authentication  Description – Authenticate USC8050 users through external RADIUS or LDAP (Lightweight Directory Access Protocol) server – Centrally manage user credentials and profiles – Automatic fallback to internal authentication when needed  Benefits – Manage users through a single location for multiple servers or OSSs – Enforce global security and access control policies 34

36 © 2015 SpiderCloud Wireless, Inc. Audit Trail  Overall – Displays last 1000 USC8050 activities (1 million entries retained) – Per Requested Activity: User : Includes Login ID, Client IP Address, Operation Date and Time Activity: Operation Description, Sequence Number, Permitted/Denied  Other Capabilities – Export: To CSV file, Print – Filter: By Date/Time Range, Operation Name, Operation Status, Username, User IP Address 36

37 © 2015 SpiderCloud Wireless, Inc. Northbound Interface  Alarm Forwarding – Forwarding events to a trap target that mark alarms or clear them – Forward SNMP traps to multiple targets by creating an SNMP managers group (a collection of one or more trap targets that share the same SNMP configuration) – Forwards traps generated by its managed USC8088 and by USC8050 itself  SNMP Agents – The USC8050 SNMP agent supports SNMP V2C and V3 versions – Support for WALK, GET, GET-NEXT, and GETTABLE in the USC8050 MIB – Support for SET only for the System group in MIB-II and USC8050 MIB 37

38 © 2015 SpiderCloud Wireless, Inc. Email Setup  Purpose: Sends alerts and notifications to administrators. Used by “scheduled tasks” and other functions.  Email Groups: Define administrative groups based on one or more email addresses.  SMTP Server: No SMTP server on USC8050. Local SMTP server used to send USC8050 email. 38

39 © 2015 SpiderCloud Wireless, Inc. Questions  True of False: USC8050 includes an SMTP (mail) server. – False: An external SMTP server must be specified to enable email notifications.  True of False: USC8050 includes an FTP server. If so, why use it? – True – Purpose: Used for backup/restore and loading O/S images.  True of False: A USC8050 license is required for each USC8000. – False: A USC8088 manages a single USC8000, USC8050 manages multiple USC8088. Licenses are per USC8050 server and specify the maximum number of USC8088 that can be managed. 39

40 © 2015 SpiderCloud Wireless, Inc. Email: Daily KPI Reports  Configure daily KPI reports from the Scheduled Task tab  Report formats are based on templates  Reports are sent to email groups configured in the Administration tab  Select or configure the: – report template – list of USC8088 – report name and description – dependency task – start time – frequency (default does not repeat) – name of email group – report format (default ASCII) 40

41 © 2015 SpiderCloud Wireless, Inc. Email: Daily Event Summary Reports  Configure daily event summary reports per USC8088 from the Scheduled Task tab.  Select predefined and custom event types for the report from the Administration >> Fault Management tab. Reports are sent to email groups configured in this tab.  Select or configure the: – list of USC8088 – report name and description – dependency task – start time – frequency (default does not repeat) – name of email group 41

43 © 2015 SpiderCloud Wireless, Inc. Redundant Architecture  USC8050 and MySQL database run the same server in the same partition  Supports (optional) 1:1 redundancy (active and standby mode with mirrored images)  Standby USC8050 server monitors the active server  Automatic failover upon server outage, with no impact on normal operation other than USC8050 client logout 43 Operator Network IPsec USC8088 USC8738 SeGW Java Client Application (Windows or Linux) HTTPS Active Server Standby Server

44 © 2015 SpiderCloud Wireless, Inc. Redundant Server Requirements  Two servers with identical hardware and MySQL database configurations.  One instance of USC8050 and the database with the same software version per server. The database must be on the same physical server and partition as USC8050.  Two USC8050 licenses allowing the same maximum number of USC8088 with the same expiration date. Your Cisco representative will provide the required licenses.  Both servers must be on the same IPv4 or have different IPv6 prefixes subnet with IP reachability.  Each server has a unique IP address. They share one or two common “virtual” IP addresses.  Both server IP addresses and the virtual IP address(es) must be in the same subnet.  Both servers must be configured to be in the same time zone. 44

45 © 2015 SpiderCloud Wireless, Inc. Redundant Server Requirements (cont.)  The administrator must assign and configure the following parameters on both USC8050 servers in order to enable redundancy: – IP address of each server – Port number of each server – Username and password for authentication – One or two virtual IP addresses – Connection settings (timeout, number of retries)  USC8050 supports both IPv4 and IPv6 IP address formats.  Both USC8050 servers must use the same IP address version. You cannot use and IPv6 address on one server and an IPv4 address on the other. 45

46 © 2015 SpiderCloud Wireless, Inc. Redundant Server Behavior  In normal operations both servers are operational.  The active server handles all network management tasks.  The active server sends all database set actions and synchs with the standby server using a secure SSL connection.  The standby server automatically assumes all its duties after failover.  Switchovers are transparent to connected USC8088.  The virtual address(es) are assigned to the active server, and are used to communicate with the active server. 46

47 © 2015 SpiderCloud Wireless, Inc. Redundant Server Pairing Wizard  Use the graphical wizard to automate redundant server pairing and the breaking of existing redundant pairs.  Access through Tools >> Launch Pairing Wizard.  Option for a second virtual IP address used for traffic to the northbound Network Management System (NMS).  The system runs a verification script to ensure that the configuration is valid before applying the changes.

49 © 2015 SpiderCloud Wireless, Inc. Alarms and Events 49  Alarms: Major operational concerns (for example, link down).  Events: Similar, but more granular, and more frequent.  Differences: All alarms have corresponding events. For example, clearing an alarm creates an event.  Use: Alarms are used to track day-to-day operations. Events are more diagnostic.  Similarities: Both events and alarms can be printed, sorted, exported, and filtered.  Differences: Alarms can be cleared, annotated, and acknowledged. Events cannot.

50 © 2015 SpiderCloud Wireless, Inc. Fault Management Overview  Purpose: Sends alerts and notifications.  Setup: Can be sent to administrators by email or forwarded to NBI using SNMP traps. The severity per event is configurable. 50

51 © 2015 SpiderCloud Wireless, Inc. Fault (details)  Fields – Sequence Number: All events are serialized – Severity: Info, cleared, warning, minor, major, critical – Source: Device reporting fault 51

52 © 2015 SpiderCloud Wireless, Inc. Alarm Options  Helpdesk Operations – Annotate: Add ticket number, assignee, and comments. – Manage: Clear to remove alarm. Acknowledge to confirm that an alarm has been viewed/processed by a given user. – Filter: Display only alarms based on alarm time, type, severity, alarm type. 52

53 © 2015 SpiderCloud Wireless, Inc. USC8050 Fault Management Configuration  USC8050-specific fault management parameters configured on the Administration >> Fault Management >> Events Configuration tab  The top section of check box/drop-down list combinations configure actions for all events in the system  The lower section configures individual event actions  Enable SNMP V1/2, V3, or both in the Trap Receive tab 53

54 © 2015 SpiderCloud Wireless, Inc. USC8050 Lab (Views)  1. Views (Network Control >> Topology) – Create three unique views for a single USC8088: Three groups: subnet, Liverpool, Acme Widgets.  2. Inventory (View >> Inventory) – Export the system inventory to a CSV file. – Sort the inventory by cell ID and primary scrambling code by cell (good for troubleshooting).  3. Access Control (Administration >> Access Control) – Create a new user group that can only view Acme Widgets USC8088.  4. Log Files (Faults >> Events) – Show all activities that transpired during a one hour time span. Can you limit this search to a specific USC8088?  5. Create Two Custom Events (Administration >> Fault Management >> Custom Events) – Create one using auto-complete and one using a regular expression. 54

55 © 2015 SpiderCloud Wireless, Inc. Network Management System Integration  Overall – Purpose: To permit SNMP traps to be forwarded to another NMS – Routing: Traps are first sent to USC8050, then forwarded  Options – Specify Multiple Servers – Support for SNMP v2C and v3 – Heartbeat (5 min default) 55

56 © 2015 SpiderCloud Wireless, Inc. Threshold Crossing Alerts (TCAs)  Description – Alerts the NOC on deviations from normal operation or performance – User-defined KPI thresholds – Examples: CDR > 1%, CPU > 50%. – Severity based alarms triggered on KPI threshold crossing – Alarms can be forwarded as SNMP traps on the NBI  Benefits – The NOC can be alerted and take action immediately on system performance degradation 56

57 © 2015 SpiderCloud Wireless, Inc. Configuring Threshold Crossing Alerts  Use the Threshold Crossing Alert Wizard to configure TCAs: Administration >> Performance Configuration – Select New Threshold Crossing Alert. – Enter a unique name and description and select the type of alert. – Enter the KPI type, KPI, and trigger type in the text boxes, select the upper and lower thresholds that will trigger or clear the threshold crossing alert, and select the counter. – From the drop-down lists, select the raise and clear action type: Email, SNMP trap, (trigger a) Tasks, or Alarms. 57

58 © 2015 SpiderCloud Wireless, Inc. Assigning TCAs to a USC8088  Once you have created one or more TCAs, assign them individually to USC8088: – In the tree view: right-click the USC8088 and select Assign Threshold Crossing Alert. A secondary window opens. – Select the TCAs to assign or assign all and click OK. 58

59 © 2015 SpiderCloud Wireless, Inc. Fault Correlation Framework  Description – Interface for developing intelligent fault and event correlation rules – Reduces alarm redundancy by grouping events referring to the same symptom and highlighting probable system fault – Automatic action depending on correlation the rule logic  Benefits – Provides higher visibility into service affecting alarms – Reduces the number of alarms seen by higher level OSS 59

60 © 2015 SpiderCloud Wireless, Inc. Configuring a Custom Fault Correlation Rule  Use the Fault Correlation Wizard to configure custom fault correlation rules: Administration >> Fault Management >> Fault Correlation – Enter a unique name and description of the custom rule. – Select the rule type, whether the trigger raises or clears an alarm, optionally define a custom corrective action, whether to suppress alarms that match this rule and for which time period. – From the drop-down lists, select the raise and clear action type: Email, SNMP trap, (trigger a) Tasks, or Alarms. 60

61 © 2015 SpiderCloud Wireless, Inc. Assigning a Rule to a USC8088  Once you have created one or more TCAs, assign them individually to USC8088: – In the tree view: right-click the USC8088 and select Assign Fault Correlation. A secondary window opens. – Select the custom fault correlation rule to assign or assign all and click OK. 61

63 © 2015 SpiderCloud Wireless, Inc. File Operations  On the USC8088 – Clients: FTP, SCP, and TFTP – Servers: SCP, upload manager daemon – Index Numbers: Each file server instance requires an index number  Through USC8050 – Downloads: Can be scheduled or requested on demand – Uploads: As they appear, files are moved to pre-configured servers  Through the CLI – On demand uploads ( file put ) or downloads ( file get ) 63

64 © 2015 SpiderCloud Wireless, Inc. File Operations (cont.)  Common Uses: To move images, XSD files, USC8050 backups, log bundles, error logs  SCP – USC8050 : SCP server and client included – Fingerprint: Public cert of remote server is automatically accepted by SCSN. This simplifies automated file transfer.  SCP Setup – SSH to USC8050. Create new SCP user (non-root, non-shell) – On USC8050 GUI, enter username/password/ IP address 64

65 © 2015 SpiderCloud Wireless, Inc. Index Numbers  Purpose: Used to label and differentiate multiple instances  Examples: File servers, network management destinations  File Management: A separate index number must be created for each file type (such as backup), even if all reside on the same server  Structure: Positive integer 65

66 © 2015 SpiderCloud Wireless, Inc. Upload Manager  Structure: The upload manager is a per-USC8088 daemon, always looking for files to move from the USC8088 to remote file server(s)  What it is not: Not a GUI-based manager  Operates on: Backups, KPI reports, log bundles, and debug logs  Instances: A separate file management index number is required for each type of file 66

67 © 2015 SpiderCloud Wireless, Inc. Upload Manager (Options)  Failover: Up to three servers (primary, secondary, tertiary) can be designated per file type. Upload manager tries the primary first.  Overwrite: The default is to overwrite existing destination files.  Permission Syntax: Uses UNIX style syntax for user/group/other. For example: rw-rw-r– 67 Question: What permissions are granted by rw-rw-r- ? Answer: The owner and group can read/write the file. Others can only read the file.

68 © 2015 SpiderCloud Wireless, Inc. Upload Manager Configuration (Step 1)  Navigate 1) Right-click the USC8088 2) Select Show Configuration 3) Select the Advanced tab 4) Expand System 5) Expand File Management  Create Instance 1) Right-click on File Management and Add File Management 2) Assign a number 3) Create new upload target instance (assign a number) 4) Specify timeout or attempts 5) Specify ModuleID (file type) 68

69 © 2015 SpiderCloud Wireless, Inc. Upload Manager Configuration (Step 2)  Create 1) Create new Upload Target instance (assign a number). 2) Enter file server details. 3) Save.  CLI Alternative set System FileManagement 3 Enable true ModuleID DatabaseBackup MaxAttempts 3 UploadTarget 100 Enable true Host backupserver.example.com Username SCadmin Password correcthorsebatterystaple RemotePath /usr/local/scbackup RemotePermissions rw-r--r– Protocol SCP Priority Primary 69

70 © 2015 SpiderCloud Wireless, Inc. Questions  True of False: Uploads and downloads can be scheduled through USC8050 – False: Only downloads can be scheduled.  Can files be uploaded automatically? If so, how? – True – Through the upload manager.  True of False: A single file server can be used to hold all backups, error bundles, etc. – True: But each file type requires a unique index number. 70

72 © 2015 SpiderCloud Wireless, Inc. Performance Monitoring Overview  Predefined and custom performance monitoring statistics enable system administrators and network operators to: – monitor the health of the network – detect and locate problems in radio components – determine long-term performance trends  System-wide data represent the aggregate performance of UMTS and LTE subsystems across the entire USC8000.  Per-cell data collection is used for localization and validation of performance issues.  Equipment data collection is enabled by default.  System-wide, per-cell data, and custom collection are disabled by default and must be explicitly enabled.

73 © 2015 SpiderCloud Wireless, Inc. Performance Monitoring Overview (cont.)  PM data is enabled and disabled for a selected USC8088 for equipment and on a system-wide and per-cell basis from the tree view.  You can clear all existing PM data from the USC8050 database.  USC8050 automatically compacts older data to improve performance management performance.  Compacted older data is available for recall for reporting and performance charts and tables.

74 © 2015 SpiderCloud Wireless, Inc. Key Performance Indicators (KPIs) 74  KPIs : System-wide, cell, or equipment  Report Period: Between two dates or over the last X hours or days  Polling: Data collected every 15 minutes  Aging: Reports for older data (>1 day) are based on less frequent sampling  Views: Multiple KPIs can be displayed on the USC8050 GUI. One, four, or nine graphs can be displayed simultaneously.  Data Export: CSV or raw text

75 © 2015 SpiderCloud Wireless, Inc. KPI Reporting 75  Predefined Reports : global, cell specific, hardware-based, and custom KPIs  Acronyms (in order of appearance)  RRC: Radio Resource Control  SRB: Signaling Radio Bearer  CS: Circuit Switched (voice sessions)  PS: Packet Switched (data session)  SHO: Soft Handover  InterRAT: Handover between two cells with different Radio Access Technology  Persistence: Reports stay on GUI until they are deleted  Refresh: Reports continually refresh while being viewed. Polling interval can be modified.

76 © 2015 SpiderCloud Wireless, Inc. Prerequisites for Per-Cell KPI 76  Default Off: Performance management data collection is disabled by default  Enable Collection: For one or more cells  Why Enable? Collect KPIs on cell availability, troubleshoots cell-specific issues, monitor per-cell traffic

77 © 2015 SpiderCloud Wireless, Inc. The Performance Tab  Displays snapshots of collected performance monitoring data for a selected USC8088.  A view is the computation of a one or more KPI for a selected time period.  A page can display one or more views.  Each KPI is color-coded with a color key on the bottom for ease of viewing.  Charts contain a scrollbar on their button bar to adjust the displayed start or end period.  The scrollbar does not adjust the data in the associated table.

78 © 2015 SpiderCloud Wireless, Inc. The Performance Tab (cont. 1)  The display can toggle between a chart and a table: – display multiple charts and tables in the same window – arrange views – determine whether one, four, or nine views display simultaneously per page – navigate between pages – save views per user such that they restore on next login  The chart X axis shows the time increments.  The chart Y axis shows the KPI.

79 © 2015 SpiderCloud Wireless, Inc. The Performance Tab (cont. 2)  A number of cell statistics display more than one measured KPIs.  For example, the statistic RRC Connection Statistics per Cell contains the KPIs listed at the bottom of the chart.

80 © 2015 SpiderCloud Wireless, Inc. The Performance Tab (cont. 3)  Charts have buttons that allow the following actions: – Export to CSV: opens the Export to CSV dialog box and exports the KPIs after calculation – Export raw data: opens the Save dialog box and creates a file with the raw KPI values – Save As: opens the Save dialog box – Print: opens the Print dialog box – Zoom in and zoom out  Graphs have buttons that allow the following actions – Export to CSV: opens the Export to CSV dialog box and exports the KPIs after calculation – Export raw data: opens the Save dialog box and creates a file with the raw KPI values

82 © 2015 SpiderCloud Wireless, Inc. Common Tasks  Create a Template  On-Demand Tasks  Scheduled Tasks (one time or recurring)  Configuring USC8088  Backups (USC8088 and the USC8050 database)  USC8088 Software Update and Revert  USC8050 Software Update  KPI Report Generation Templates 82

83 © 2015 SpiderCloud Wireless, Inc. Templates 83  Purpose  Bulk: Primarily used to apply change(s) to many USC8000s  One-Time: Can be used to schedule a single change  Creation  Use keywords (for example, SNMP) to locate data model elements  Review the data reference model first

84 © 2015 SpiderCloud Wireless, Inc. Template Creation 84  Structure  Template Name: Shows up in the template list  From/To: Ensures the scheduled change is only applied to USC8088 with specific versions of the operating system  Caveat: The Add button is often hidden at the bottom of the panel

85 © 2015 SpiderCloud Wireless, Inc. Template Import / Export  Purpose: Two reasons to import templates: – Efficiency: Reuse templates for common tasks (for example, new syslog server used by multiple USC8088) – Consistent Provisioning: Provision USC8088 consistently throughout the USC8000  Method – Export: Select existing template, as if to modify. Select Export. This creates an XML file. – Import: Login to destination USC8050 server 85

86 © 2015 SpiderCloud Wireless, Inc. Scheduled Tasks  Scheduling Wizard – Purpose: Create, modify, and delete tasks – Method: Define tasks, dependencies, start time, frequency.  Common Tasks – Backup: USC8050 server database which includes USC8088 configurations and exporting the USC8088 configuration to file – SW Upgrades: Upload/install software images – Maintenance: REM scans, reset statistics 86

87 © 2015 SpiderCloud Wireless, Inc. Scheduled Tasks (cont.)  Naming: When defining a task, the name of the task is specified at the end of the definition.  Results: Log (at bottom) shows task success or failure. The last failure is shown in details.  Dependency Tasks: Task B will not start if Task A did not complete. For example: – Task A: File transfer of software image onto a USC8088. – Task B: Update software image. 87

88 © 2015 SpiderCloud Wireless, Inc. Useful Scheduled Tasks  Log Bundle Creation – Purpose: Used by support for analysis and troubleshooting – Result: Log Bundle stays on the USC8088, in the directory error_incidents /  Software Update – Purpose: Can be use to schedule upgrades on many USC8088 with one task. Can be scheduled for off-hours. – Dependency Task: Load the new software image before install – Caveat: Must be loaded in a specific directories  USC8050 Backup – Purpose: Backs up configuration of all devices, exporting the USC8088 configuration, and USC8050’s own settings – Frequency: Scheduled daily by default. The frequency can be modified.  Others: Daily KPI report, REM scan, REM start, log rotation, file download 88

89 © 2015 SpiderCloud Wireless, Inc. Scheduling KPI Reports  The KPI report details activity polled from the previous 24 hours before the reference time, regardless of how often the report is generated.  Accessed through the Work Area >> Network Control >> Scheduled Tasks tab.  Select from predefined configuration templates.  Run this report on a daily basis shortly after the close of business hours to generate reports in a timely manner.  The system needs at least 48 hours of data polled after the USC8088 is actively managed by USC8050 to produce a meaningful report. 89

90 © 2015 SpiderCloud Wireless, Inc. USC8088 Configuration 90  Purpose: Setup and schedule common tasks and configuration changes.  Access : Right-click on a USC8088 to configure and select Show Configuration.  Common Options:  Equipment setup (IP/Radio/Advanced)  Configuration templates  Scheduled tasks

91 © 2015 SpiderCloud Wireless, Inc. Backup Overview 91  Two Types: Backup of USC8050 itself and backup of a USC8088.  USC8050 Backup  Backup of USC8050 itself  Predefined  Scheduled daily  Can be modified  Cannot be deleted  USC8088 Backup  Backup of the USC8088 running configuration  Predefined but not scheduled by default  Must be scheduled with the Add Task button  Restore  USC8050: Requires CLI  USC8088: Can be performed through the GUI

92 © 2015 SpiderCloud Wireless, Inc. USC8088 Database Backup 92  Prerequisite Setup upload target  Backup Contents Excludes certificates  Frequency Hourly, daily, or weekly  Options  Email success/failure of backup  Create dependency task  Include database logging (historical alarms and logged events)

94 © 2015 SpiderCloud Wireless, Inc. USC8088 Software Update (Step 2) 94  Schedule Update: Can be run immediately or scheduled for future.  Package: Filename previously downloaded. Do not modify the filename.  Clean (optional) resets the USC8088:  db: Removes the cellmgr-ini file.  data: Removes all persistent data (such as configuration, logfiles, and core files).  configuration: Removes the configuration and replaces it with the factory configuration.  Dependency Task (optional): Ensure that the download of the SCOS image has succeeded before upgrade.

95 © 2015 SpiderCloud Wireless, Inc. Schedule Exporting the USC8088 Configuration 95  Schedule exporting the current system configuration (the writable parameters of the data model) to a local or network drive.  The data model can be exported in one of three formats:  text: ASCII text format that replicates the CLI configuration.  flat XML: unstructured XML for machine to machine processing.  structured XML: XML for machine to machine processing with structured formatting for increased human readability.

96 © 2015 SpiderCloud Wireless, Inc. USC8050 Software Update  Method – Get Software: Place new x86 or AMD bits on existing USC8050 server. – Install: Run installer For example: [Desktop]#./USC8050_unix_4_0_0_30_x86.sh  Safe Overwrite – Installer: Removes the old version. – License and Config: Fully retained from previous USC8050 version.  Client Requirements – Browser: No change needed, new image automatically supported. – Standalone: When connecting to a newer software image, a link is provided to a compatible standalone image for download. 96

© 2015 SpiderCloud Wireless, Inc. SCT-320 USC8050 Overview September 28th, 2015.

Recommend Documents