Allied Telesis™ AlliedView Network Management System 14.0 (SP0) Administration Guide Issue 1 Copyright © 2012 Allied Telesis, Inc. All rights reserved Information in this document is subject to change without notice.
Introduction to the AlliedView NMS Product Congratulations on your purchase of the Allied Telesis™ Network Management System product. This product allows administrators to query and control all aspects of Allied Telesis products in their network. Who Should Read This Guide? This document is for network administrators who need in-depth knowledge of the NMS and its applications. Many of these applications are only available to administrators and allow them to control the actions available to users.
• Chapter 12 explains the capabilities of the Northbound interface. • The Appendix explains how to export to a file tabular data displayed in the Fault Management, Performance, and Network Inventory views. For the iMG/RG, it includes sample configuration files. Tracking Updates since the Previous Release Section 1 of this document includes a Reason for Update table, allowing the user to see what features have been added or changed.
Copyright © 2012 Allied Telesis, Inc. All rights reserved Information in this document is subject to change without notice.
Table of Contents 1 Product Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -1-1 1.1 Intended Audience for this Guide - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-1 1.2 How this Document is Organized- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-1 1.3 Reason for Update - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-2 1.
2.8.1 2.8.2 2.8.3 2.8.
3.10.1 Overview (Standard versus Custom Loads) - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-49 3.10.2 Load Import GUI (Standard Loads) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-49 3.11 Accessing the NMS Database - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-54 4 Security Administration- - - - - - - - - - - - - - - - - - - - - - - - - - 4-1 4.
5.3.1 Overview of the Provisioning Interface - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -5-9 5.3.2 Backup/Restore (with Purge Button)- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5-14 5.3.3 Command Script Management- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5-21 5.3.4 Configuration File Management - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5-27 5.3.
5.6.3 Provision New Customer/Port (Triple Play Form) - with Preferences - - - - - - - - 5.6.4 Provision New Customer Port for Ethernet - - - - - - - - - - - - - - - - - - - - - - - - - - 5.6.5 Provision New Customer/Port for ADSL - - - - - - - - - - - - - - - - - - - - - - - - - - - 5.6.6 Provision New Customer/Port for CES8 (DS1/E1 Form) - - - - - - - - - - - - - - - - 5.6.7 Provision New Customer/Port for NTE8 (DS1/E1 Form) - - - - - - - - - - - - - - - - 5.6.
5.9.6 Telnet / SSH to a Device- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5-262 5.9.7 Browse Device (Rapier Device Only) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5-263 5.9.8 Rediscovery Device (When Required) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5-263 5.9.9 Managed Object Properties - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5-263 5.9.
6.8.2 Extending the Island-Based VLAN - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 6-36 6.9 Example Configurations for HVLAN, Translations- - - - - - - - - - - - - - - - - - - - - - - - 6.9.1 Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 6.9.2 HVLAN Configuration - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 6.9.
6.13.6 Troubleshooting the EPSR Configuration - - - - - - - - - - - - - - - - - - - - - - - - - - - 6-150 6.13.7 Status of Transit Nodes for AlliedWare Plus Devices- - - - - - - - - - - - - - - - - - - - 6-156 6.14 SuperLoop Prevention (Superring) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 6-157 6.14.1 Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 6-157 6.14.
6.22.5 Implementing Port Authentication with Triple-Play - - - - - - - - - - - - - - - - - - - - 6-255 7 Provisioning the iMG/RG- - - - - - - - - - - - - - - - - - - - - - - - -7-1 7.1 Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 7-1 7.1.1 Roadmap for this Section- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 7-1 7.
7.7.2 Managed Object Properties for the iMG/RG - - - - - - - - - - - - - - - - - - - - - - - - - - 7-124 7.7.3 Creating Custom Views for an Access Island - - - - - - - - - - - - - - - - - - - - - - - - - - 7-128 7.8 Provisioning the iMG/RG (Application Manager) - - - - - - - - - - - - - - - - - - - - - - - - - 7-136 7.8.1 Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 7-136 7.8.
7.15.1 7.15.2 7.15.3 7.15.4 7.15.
9.5.5 Setting Up Event Filters for SYSLOG Events - - - - - - - - - - - - - - - - - - - - - - - - - - 9-27 9.6 Configuring System Logs (NMS System Log Server) - - - - - - - - - - - - - - - - - - - - - - - - 9-27 9.6.1 Configuring the System Log Server - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 9-29 9.6.2 Applying Log Filters - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 9-30 9.6.
11.9 Graphs - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 11-14 11.10 CWMP- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 11-15 12 Northbound Interface - - - - - - - - - - - - - - - - - - - - - - - - - 12-1 12.1 Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 12-1 12.
TOC-14 AlliedView NMS Administration Guide (Table of Contents)
1. Product Overview 1.1 Intended Audience for this Guide This document is for those who are responsible for all aspects of configuring and administrating the network or networks they manage. After reading this document, the user should be able to control all aspects of the AlliedView NMS and be able to instruct all users on tasks they may perform and the impact of any changes they have made. 1.
Reason for Update 1.3 Reason for Update The following tables list the updates for Release 14.0. TABLE 1-1 Changes to the AlliedView NMS Administration Guide in Release 14.0 (SP0) Feature 12.5 Functionality 14.0 Functionality Notes LAG Auto negotiation For iMAP and SBx3112, ports needed to be compatible with manual settings. If link was set to Auto Negotiate, could not be included in LAG. Link can be set to Auto Negotiate, and if links are compatible, it will be included.
User Privileges at the NMS and Product Level The AlliedView Network Management System (NMS) 1.4 The AlliedView Network Management System (NMS) For managing a network, the AlliedView NMS product provides a powerful client that presents the network and its devices in a user-friendly way, allowing its users to learn quickly how the network is configured, how to reconfigure elements when necessary, and how to spot problems (or potential problems) before they degrade network performance.
Levels of Support (Enterprise Edition) Using Default Prompt for Device Account Used by Allied- 1.5 Levels of Support (Enterprise Edition) The Enterprise Edition is introduced primarily for the smaller enterprise customer managing a network of less than 100 devices. All features of the Service Provider Edition (SE) are supported in the Enterprise Edition with the exception of customer provisioning of voice, video, and data services.
Full Support, Excluding iMG/RG Managed Devices (Firmware Interop) 1.6 Managed Devices (Firmware Interop) 1.6.1 Full Support, Excluding iMG/RG Table 1-3 lists the devices that the AlliedView NMS 12.0 supports. More details about the support features for specific products is included in subsequent tables, since there may not be full support for all features. Note: Because of the Firmware Decoupling feature, there is no need for a column “Upgradeable Firmware (Patch)”.
Managed Devices (Firmware Interop) TABLE 1-3 Full Support, Excluding iMG/RG Device Support for the AlliedView NMS 14.0 Family (Level of Support) AT-8000 Devices Latest Compatible Firmware1 Notes AT-8012M 3.3.* NMS 12.0 Support End-of-Life (EOL) 3.0.0.* Full range of support is 1.0.0.19 up to 3.0.0.44.
Full Support, Excluding iMG/RG TABLE 1-3 Managed Devices (Firmware Interop) Device Support for the AlliedView NMS 14.0 Family (Level of Support) Devices Latest Compatible Firmware1 AT-8500 AT-8516FSC 1.4.* Notes NMS 12.0 End-of-Life (EOL) AT-8524M AT-8525 AT-8525 AT-8524POE AT-8550GB AT-8550SP AT-8600 AT-8624POE 2.9.1-20 AT-8624T/2M AT-8624XL AT-8624PS AT-8624EL AT-8648T/2SP AT-8700 AT-8724XL 2.9.1-20 Not supported: AT-8724XLDC 2.6.1-04+ AT-8724XLDCNEBS 2.6.2 AT-8748XL 2.6.
Managed Devices (Firmware Interop) TABLE 1-3 Device Support for the AlliedView NMS 14.0 Family (Level of Support) AT-9000 Full Support, Excluding iMG/RG Devices Latest Compatible Firmware1 AT-9000/28 2.1.2 AT-9000/28SP AT-9000/52 Notes LLDP and LLDP-MED for this device is not supported in NMS release 12.2; values cannot be retrieved through SNMP (available lldp mibs does not return corresponding values). Mode LED indicator is fixed in the ACT Mode. The NMS has no provision for Mode Selection.
Full Support, Excluding iMG/RG TABLE 1-3 Managed Devices (Firmware Interop) Device Support for the AlliedView NMS 14.0 Family (Level of Support) Devices Latest Compatible Firmware1 x600 AT-x600-24Ts 5.4.2-* (AlliedWare Plus) AT-x600-24TsXP AT-x600-24Ts-POE AT-x600-48Ts AT-x600-48TsXP AT-x610-24Ts (AlliedWare Plus) AT-x610-24Ts-PoE+ 5.4.2-* AT-x610-24Ts/X AT-x610-24Ts/X-PoE+ AT-x610-48Ts AT-x610-48Ts/X AT-x610-48Ts/X-PoE+ The Stack-XG card can be swapped during operation (e.g.
Managed Devices (Firmware Interop) TABLE 1-3 Full Support, Excluding iMG/RG Device Support for the AlliedView NMS 14.0 Family (Level of Support) RG203 Devices Latest Compatible Firmware1 Notes 6.* NMS 12.0 End-of-Life (EOL) NMS 12.0 End-of-Life (EOL) RG203TX-SIP/H323 RG203TX v2-SIP/H323 RG213 RG213-H323 RG213-MGCP RG213-SIP Rapier Rapier24 2.3.1-* (Full Support) Rapier48 2.7.0-* Rapier “G” RapierG6 2.7.3-09 NMS 12.0 End-of-Life (EOL) 2.9.1-20 NMS 12.0 Support End-of-Life (EOL) 2.7.
Full Support, Excluding iMG/RG TABLE 1-3 Managed Devices (Firmware Interop) Device Support for the AlliedView NMS 14.0 Family (Level of Support) Devices Latest Compatible Firmware1 iMAP 7100 6.1.12 NMS 12.0 Support End-of-Life (EOL) 16.0.* iMAP releases are supported up to two releases prior to the current release. Therefore, in release 12.0, releases prior to iMAP 11.0 are not supported.
Managed Devices (Firmware Interop) TABLE 1-3 Basic Management Support Device Support for the AlliedView NMS 14.0 Family (Level of Support) GS Series Devices Latest Compatible Firmware1 CentreCOM-FS808M 1.0.3 CentreCOM-GS924M 1.6.6 Notes CentreCOM-GS916M CentreCOM-GS908M CentreCOM-GS924M v2 2.1.0 CentreCOM-GS916M v2 CentreCOM-GS908M v2 CentreCom 9048XL CentreCOM 9048XL 2.1.0 1. Compatible Firmware defines the device software releases that the NMS is able to manage.
Basic Management Support TABLE 1-4 Managed Devices (Firmware Interop) Devices Supported by NMS - Network Inventory, IP Maps, Alarms (Continued) Family Devices Extreme Summit X250e X250e-24t Notes X250e-24p X250e-24x X250e-48t X250e-48p X250e-24tDC X250e-24xDC X250e-48tDC Extreme Summit X450a X450a-24t X450a-48t X450a-24tDC X450a-24xDC X450a-24x X450a-48tDC Juniper SSG-550M SSG 550M NetScreen NS-208 NS-50 NS-5XT A10 AX3200 A100-AX3200 AlliedView NMS Administration Guide (Product Overview) 1
Managed Devices (Firmware Interop) iMG/RG Types Supported (3-8-03 and 4-n) 1.6.3 iMG/RG Types Supported (3-8-03 and 4-n) 1.6.3.1 iMG/RG Device Support (up to 3-8-03) Table 1-5 lists a history of iMG/RG devices, and includes those that support 3-8-03. Note: This table lists all of the iMG/RGs that can be upgraded to 3-7 (using the Migration tool) and then which of those devices can be upgraded to 3-8.
Overview TABLE 1-5 Levels of Support History of iMG/RG Releases Through 3-8-03 (Continued) Device1 Previous 3-72 3-8-01 3-8-02 3-8-03 iMG634-WB-R2 - Yes Yes Yes Yes iBG915-FX 3-6 Yes Yes Yes Yes Notes 1. Refer to 7.17 for functional groupings of iMGs/RGs. 2. With the Migration Tool, allows the offline migration of 2-5 im.conf to 3-7 format. 3. iMG726BD-ON has same processor and feature support with LAN and BD interfaces (no optional modules). 1.6.3.
Levels of Support Allied Telesis, AlliedWare, and AlliedWare Plus Products For the Provision feature group, if a product supports all the features, there is All in the first row TABLE 1-7 Product Support Features for the AlliedView NMS in 14.0 Support Features iMAP 90001 T-1000 Rapier SB/9800 Family2 Family3 x900 Family4 5 x6006 x6107 SBx3112 View Chassis Y -- Y Y Y8 Y Y Y Device Log Management Y Y Y Y Y Y Y Y Backup/Restore Y N Y Y Y Y Y Y Command Script Mgmt.
AR, AT, and GenBand Products Levels of Support 7. Includes the x610-24SPs/X, x610-24Ts, x610-24Ts-PoE+, x610-24Ts/X, x610-24Ts/X-PoE+, x610-48Ts, x610-48TsPoE+, x610-48Ts/X, x610-48Ts/X-PoE+ 8. For x900 stacked and SBx908 stacked, the chassis view shows both ETH0 ports as green, although only one should be green (the stack member with the connected eth0 port). 9. Card Management not supported. The device has no available card/slot. 10.When the SBx3112 is running R15.
Levels of Support TABLE 1-8 AR, AT, and GenBand Products Product Support Features for the AlliedView NMS in 14.
Specific Market Devices Levels of Support 1.7.4 Specific Market Devices Table 1-9 and Table 1-10 list the support features for the AlliedView NMS for other products. Note: Contact your Allied Telesis Customer Representative for detailed information on using these devices, since many of them fulfill specific market requirements. TABLE 1-9 Product Support Features for the AlliedView NMS in 14.
Levels of Support Specific Market Devices 2. Includes the X250e-24t and X450a-24t 3. Includes the BD 8810 and BD8806 4. For Extreme devices, there is the option to specific additional files for backup. TABLE 1-10 Product Support Features for the AlliedView NMS in 14.
Specific Market Devices Levels of Support 4. Includes the GS924M, GS916M, GS908M, GS924M v2, GS916M v2, GS908M v2 5. Includes the FS808M, FS926M, FS917M, FS909M, FS909M-PS and FS917M-PS. 6. There is no info via SNMP or CLI that shows the duplex mode. The duplex led will always be gray. 7. The color of disabled port will not turn orange when module/port is disabled via CLI 8. There is no info via SNMP or CLI that shows the duplex mode. The duplex led will always be gray. 9.
Levels of Support Devices Supported by SwimView 1.7.5 Devices Supported by SwimView Table 1-11 lists the devices that are discoverd and viewed/modified by SwimView. Note: Contact your Allied Telesis Customer Representative for detailed information on using these devices with SwimView, since many of them fulfill specific market requirements.
Document Media Document Conventions 1.8 Document Conventions To help the reader use this document, the following conventions are used: • Menu selections are in bold/italic, with -> for accessing a submenu, such as Policy -> Add Policy. • Descriptions of properties are in a two-column table, with the order of properties matching the order of policies matching those shown on the window. • Names of windows and window elements (such as Tool Tips) are in bold, such as the Restore Configuration window.
Copyrights 1-24 AlliedView NMS Administration Guide (Product Overview) Using Online Help with NMS
2. Installing and Starting Up 2.1 Overview The AlliedView NMS software is delivered as a CD-ROM, which includes both server and client (application interface) software. 2.2 AlliedView NMS Installation Refer to the AlliedView NMS Installation Guide for the system requirements, limitations, and the installation and startup procedures. Note: The monitor used with the client and server machines should have a resolution of 1280x1024 or better. 2.
Using the Logs Console Configuration Limits for Clients If at anytime you wish to change the password, select Tools -> Change Password from the main menu bar, and the Password Configurator form will reappear. 2.3.2 Configuration Limits for Clients The AlliedView NMS server can support up to five GUI client connections at the same time. Note: Connecting to the AlliedView NMS server using an html client counts as one of the five allowed users. 2.
Configuration Limits for Clients The Application Screen FIGURE 2-2 Console File Window 2.5 The Application Screen When you log in to the Application interface, the default screen that is displayed shows a map containing the map symbols that represent the discovered network devices. Refer to the following figure. You can find the common Menu Bar, Toolbar, Map Toolbar, AlliedView NMS Client Tree, Alarm Count Panel, Status Bar, and the AlliedView NMS Panel displayed in the user interface.
Broadcasting a Message Configuration Limits for Clients FIGURE 2-3 Initial Network Interface 2.6 Broadcasting a Message The option File -> Broadcast Message can be used to send messages to all the clients. When this option is selected, the message is sent to all the clients managed by the main AlliedView NMS Server by default. (The option chosen does not matter.) When this option is selected, a dialog that contains the following details pops up. Refer to the following figure.
Configuration Limits for Clients Restart / Shut Down the Server The following table lists the properties for broadcasting a message. TABLE 2-1 Properties for Broadcasting a Message Property Details for Broadcast Message Properties Message The message to be broadcast. Option Two message options. The option Send to my FE client only is not supported. The other option is Send to all clients.
Resource Management Setting the Custom Security Policy (Required) 2.8 Resource Management 2.8.1 Setting the Custom Security Policy (Required) This must be set for the server. • Find the java runtime environment (jre). It’s usually located in: :/Program Files/Java/jre* or use the Control Panel Java Plug-in tool “Advanced” tab to see the exact path of the java runtime. • Open the java.policy file in lib/security (under the jre path).
Resource Management Table (Tools -> Resource Management) Resource Management 2.8.2 Resource Management Table (Tools -> Resource Management) To view the status of the server configuration, the user selects Tools -> Resource Management from the main menu. The Resource Management Window appears, as shown in the following figure. Note: This table should only be used by the Administrator. FIGURE 2-5 Resource Manager Window - Back End Only 2.8.
Resource Management Client Memory Monitor FIGURE 2-6 2-8 Client Memory Monitor AlliedView NMS Administration Guide (Installing and Starting Up)
3. File Administration 3.1 Overview Many administrative tasks for the AlliedView NMS are done by adding, changing, and deleting files on the server. However, directly accessing these files should not be attempted, since a loss of AlliedView NMS functionality could result. For this reason, the AlliedView NMS provides GUI-based functions (mainly the Discovery Configurator) that make updating the AlliedView NMS files easy and less error-prone.
Overview TABLE 3-1 Task List for File Administration (Continued) Task Screen / Form Name (if Applicable) Section AlliedView NMS Backup and Restore AlliedView NMS Backup (3.4.1) AlliedView NMS Restore (3.4.4) Device Backup Limit (3.4.5) Node Limiting, Registering NMS load AlliedView NMS License Manager (3.5) Software Downloads Software Configuration (Modify Release Configuration, Create Custom Load buttons) (3.6) Monitor AlliedView NMS server/processes Status Monitoring (3.
Overview Discovery Configurator (Service Provider) 3.2 Discovery Configurator (Service Provider) 3.2.1 Overview AlliedView NMS discovers devices in a network and then, based on the properties of the device, constructs ManagedObjects for each discovered device. There are several ways to invoke the Discovery Configurator panel. • For both windows and Solaris, Invoke the Discovery Configurator as a standalone tool by invoking file DiscoveryConfigurator.bat in the /bin/admintools directory.
Discovery Configurator (Service Provider) Schedule Tab To schedule the time, choose an hour and select one or more days of the week. Nightly rediscovery is recommended. At least once a week is required, with no more than once every 24 hours. The buttons are defined as follows, and have the same function for all tabs: • Save Changes - Saves the configuration to the NMS database and leaves the dialog up. • Close - Dismisses the dialog, but before doing so will prompt to save changes if changes are pending.
SNMP Tab Discovery Configurator (Service Provider) 3.2.3 SNMP Tab FIGURE 3-3 Discovery Configurator – SNMP Tab Only devices that respond to SNMP can be discovered and managed by the AlliedView NMS. The NMS will perform “SNMP Ping” operations with each of the given read communities until a device responds or all communities have been tried and failed. (SNMP Pings are essentially SNMP get requests for selected system variables.
Discovery Configurator (Service Provider) CWMP Tab Communities will be attempted in the order displayed. The order may be modified by selecting a row and then clicking on the up/down buttons. Communities may be added, modified, or deleted with the Add, Modify or Delete Buttons. The Add button will add to the list whatever is in the Read or Write text field. The Modify button will replace whatever is in the selected row with whatever has been typed in the Read or Write text field.
CWMP Tab Discovery Configurator (Service Provider) FIGURE 3-4 The CWMP tab consists of 2 lists, one of ACS usernames and one of CPE usernames. Since order is significant, credentials in each list may be reordered by clicking the arrow buttons below each list until the desired order is attained. There is a password associated with each username. Duplicates are allowed. Note: Password displays are blotted. Some duplicates may be difficult to distinguish from others.
Discovery Configurator (Service Provider) CLI Logins Tab 3.2.5 CLI Logins Tab The CLI Login Manager allows the user to specify a list of CLI username/password pairs that will be used by the Discovery Process to determine the CLI username and password for individual devices. The username and password discovered for each device are used for all CLI interactions with the device.
CLI Logins Tab Discovery Configurator (Service Provider) Once a device has been discovered by SNMP, more detailed discovery requiring a CLI login is required to manage the device. The NMS attempts to log into each device until it either discovers an accepted login or all login attempts are rejected. The login sequence generally follows the order of the logins in the table. The order may be modified by selecting a row and then clicking on the up or down buttons.
Discovery Configurator (Service Provider) Network Discovery Tab 3.2.6 Network Discovery Tab FIGURE 3-6 Discovery Configurator – Network Discovery Tab This tab specifies networks to discover (or exclude from discovery). The discovery process will attempt to discover devices at all IP addresses in the network (or exclude all such addresses if configured for exclusion). Networks can be added, modified, or deleted with the Add, Modify, and Delete buttons.
Network Discovery Tab Discovery Configurator (Service Provider) If SNMP discovery is enabled, network discovery will normally use the parameters configured on the SNMP tab, but they can be overridden for specific networks and subnets by selecting the SNMP option on this tab.The properties to fill in depend on the SNMP version selected. A version of SNMP can be chosen to override what is configured for the network.
Discovery Configurator (Service Provider) Node Discovery Tab 3.2.7 Node Discovery Tab FIGURE 3-8 Discovery Configurator – Node Discovery Tab. This tab specifies specific nodes to discover (or exclude from discovery). Nodes can be added, modified, or deleted with the Add, Modify, and Delete buttons. The “Discover Node” toggle, when checked, means to discover the node. When unchecked, that node will be ignored (excluded) from discovery.
Node Discovery Tab Discovery Configurator (Service Provider) FIGURE 3-9 Setting Properties for SNMPv3 The user can add networks and nodes in the Network Inventory screen as Managed Objects and this will take effect immediately. The menu choice: • Network Inventory / Edit -> Add Network • Network Inventory / Edit -> Add Node brings up the dialog to add a network or node. Refer to 3.2.9.2.
Discovery Configurator (Service Provider) Other Discovery Tab 3.2.8 Other Discovery Tab FIGURE 3-10 Discovery Configurator – Other Discovery Tab This tab lists sysOIDs (SNMP system Object Identifiers) of devices to be included for discovery. Any device discovered by way of SNMP will be rejected unless its sysOID is one of these from this table. The defaults for this table are the Allied Telesis devices fully-supported by the AlliedView NMS.
Example Configurations FIGURE 3-11 Discovery Configurator (Service Provider) Discovery Configurator – Other Discovery Tab - Translate Display Option 3.2.9 Example Configurations 3.2.9.1 Setting up Discovery - Procedure The tabs in the Discovery Configurator from right to left are the sequence that should be followed when setting up discovery. The following procedure should be done when the NMS has just been installed and the server has not been started. 1.
Discovery Configurator (Service Provider) Example Configurations 3.2.9.2 Adding a Network or Node from the Network Inventory To immediately add an individual node or network, the administrator goes to the Network Objects tree, selects Network Inventory node, and then clicks from the pull-down menu Edit -> Add Node or Edit -> Add Network. This brings up the Add Node and Add Network panels as shown in the following figures.
Example Configurations Discovery Configurator (Service Provider) FIGURE 3-13 Add Node (From Network Inventory) AlliedView NMS Administration Guide (File Administration) 3-17
Discovery Configurator (EE) Overview 3.3 Discovery Configurator (EE) 3.3.1 Overview The EE version of the Discovery Configurator is available in NMS Release 12.0, is similar to the SE version but has the following features: 1. The GUI allows enabling/disabling of Discovery 2. ICMP Discovery (using Ping) can be configured, and SNMP Discovery is optional. 3. The local network can be discovered using a simple option. 4. Rediscovery can be disabled. 5. DHCP support is provided. 6.
Basic Tab Discovery Configurator (EE) 3.3.2 Basic Tab The Basic tab is displayed where the SE version displays the Schedule tab. Refer to the following figure.
Discovery Configurator (EE) Basic Tab Buttons for the Basic tab are: • Enable Discovery -The default is checked; if not checked, Discovery will not be performed. • Discover Local Network - The default is not checked; if checked, nodes from the local network (where the NMS resides) are discovered. • Rediscover Already Discovered Nodes - If checked (the default), nodes already discovered are rediscovered based on the rediscovery interval that has been set.
SNMP Tabs Discovery Configurator (EE) 3.3.3 SNMP Tabs Refer to the following figure. FIGURE 3-15 SNMP - EE Version SNMP discovery can be enabled or disabled. If disabled, the rest of this tab is grayed-out. If enabled, the NMS will use this configuration during network discovery to test IP addresses for the presence of SNMP-enabled devices.
Discovery Configurator (EE) CWMP Tab 3.3.3.1 SNMPv2 For most devices, only read communities are used during discovery. Some devices, including iMG/RGs, require discovering write communities as well. Communities will be attempted in the order displayed. The order may be modified by selecting a row and then clicking on the up/down buttons. Communities may be added, modified, or deleted with the Add, Modify or Delete Buttons. The Add button will add to the list whatever is in the Read or Write text field.
CLI Logins Tab Discovery Configurator (EE) 3.3.5 CLI Logins Tab Refer to the following figure.
Discovery Configurator (EE) CLI Logins Tab Status polling via ICMP or SNMP does not require CLI access; CLI discovery is only required when device configuration (backups, port management, VLAN management, etc.) is desired and is only applicable to fully-supported devices (refer to Section 1). Once a device has been discovered by way of SNMP, more detailed discovery requiring a CLI login is required to manage the device.
Network Discovery Tab Discovery Configurator (EE) 3.3.6 Network Discovery Tab FIGURE 3-17 Network Discovery Tab - EE Version This tab specifies networks to discover (or exclude from discovery). The discovery process will attempt to discover devices at all IP addresses in the network (or exclude all such addresses if configured for exclusion). Networks can be added, modified, or deleted with the Add, Modify, and Delete buttons.
Discovery Configurator (EE) Node Discovery Tab When “Set of Nodes” is selected, the DHCP option becomes available. Use this option if IP addresses are assigned dynamically. The NMS will then use MAC addresses to identify hosts rather than IP addresses or host names. If SNMP discovery is enabled, network discovery will normally use the parameters configured on the SNMP tab, but they can be overridden for specific networks and subnets by selecting the SNMP option on this tab.
AlliedView NMS Backup (On Demand) Backup and Restore This tab specifies specific nodes to discover (or exclude from discovery). Nodes can be added, modified, or deleted with the Add, Modify, and Delete buttons. The “Discover Node” toggle, when checked, means to discover the node. When unchecked, that node will be ignored (excluded) from discovery. The “Discover Parent Network” tab means to discover all the devices in the parent network as well.
Backup and Restore AlliedView NMS Backup (Scheduled) FIGURE 3-20 Backup Process Complete Window The controlling of where the backup is written to is explained in 3.4.3. 3.4.2 AlliedView NMS Backup (Scheduled) To backup the NMS server on a schedule, choose from the main menu Tools -> NMS Database Backup, and the option Scheduled. A dialog box appears, as shown in Figure 3-21.
AlliedView NMS Backup (Scheduled) Backup and Restore FIGURE 3-21 NMS Backup Schedule AlliedView NMS Administration Guide (File Administration) 3-29
Backup and Restore Configuring Backup Parameters for AlliedView NMS 3.4.3 Configuring Backup Parameters for AlliedView NMS A backup of the NMS configuration can be performed on demand or on a schedule. When the files are being backed up on demand, the console window shows the path where the files are being copied. When the files are being backed up on a schedule, the Backup Destination field (seen in Figure 3-21) shows this path. The path used is controlled by the file: /conf/AT_NmsBackupFiles.
Restore the AlliedView NMS (GUI Screens) FIGURE 3-23 3. Starting the AlliedView NMS Recovery Feature (Windows) Selecting the NMS exec file brings up the NMS Restore Tool. Use the Browse button to bring up the relevant backup file. In searching there is the Zip option to search through only zip type files. Refer to the following figure. FIGURE 3-24 4.
Backup and Restore Restore the AlliedView NMS (GUI Screens) FIGURE 3-25 FIGURE 3-26 3-32 AlliedView NMS Restore - Start AlliedView NMS Restore - Finish AlliedView NMS Administration Guide (File Administration)
Device Backup (Per-Device Limit) Backup and Restore 3.4.5 Device Backup (Per-Device Limit) Daily backups of a large network will eventually use up all the disk memory unless customers manually purge old files. One feature to address this is using file configuration as follows: The limit is configured in conf/AT_NmsBackupFiles.conf The property is ATIDEVICE_BACKUP_LIMIT Setting this to zero is equivalent to no limit. Setting this to a non-zero number is the number of device backups allowed.
AlliedView NMS License Manager Overview 3.5 AlliedView NMS License Manager 3.5.1 Overview In release 10.0, there is a change to the license manager strategy that involves the following changes: • The license key is associated with the customer who has registered the license rather than the hardware where the key was installed.
Installing a License (Using the License Key Manager) FIGURE 3-27 AlliedView NMS License Manager License Manager Tool The license key installation user interface has three main sections: • Current License Information (Top): This section has information on the key that is already installed. It displays the license status including user information, product and all components being licensed. • License File Selection (Middle): This section allows the user to select the license file to be applied.
AlliedView NMS License Manager Installing a License (Using the Console Mode) FIGURE 3-28 License History When the user selects the Apply button, the selected file is read and checked, installed, and then verified. If there is an error during these steps, the installation will stop. If there are no errors, the key is also stored at another location if needed later for recovery. 3.5.
Verifying the License After Installation AlliedView NMS License Manager cd /bin AT_LicenseInstaller.bat -help Printing help: -help Usage (all parameters are optional): AT_LicenseInstaller [options] Where options are: -help - Print this message (cannot be used with other options) -g - Run in GUI mode (default and all other options are ignored) -c - Run in console mode (other options may be added) Parameters below can only be used in console mode (-c) if needed to bypass text menu options.
AlliedView NMS License Manager FIGURE 3-29 Viewing the License Configuration License Expired/Invalid at Server Startup • Server runtime: Once the server has started, and if the key is found to be invalid, the server is stopped. There will be warning messages in the logs that allow the user to correct the problem before the server is stopped. 3.5.4.
Viewing the License Configuration AlliedView NMS License Manager FIGURE 3-30 Splash Screen at Startup FIGURE 3-31 About NMS Screen The License Key information is also included in the Status Monitoring Panel. Refer to 3.9.
AlliedView NMS License Manager Migrating Existing Licenses 3.5.6 Migrating Existing Licenses NMS License Keys issued prior to R10.0 will no longer be valid. Therefore effective with NMS R10.0, all customers upgrading from R9.0 to R10.0 will be required to get a new license key from Allied Telesis. Upgrading a properly licensed NMS R9.0 server to R10.0 will result in the license status being placed back into Evaluation status.
Overview File Keys to Identify Downloadable Files 3.6 File Keys to Identify Downloadable Files 3.6.1 Overview As explained in Section 5.3.9, Software Configuration is an MDTI application that downloads OS releases onto supported devices/components. Since there are many steps and constraints involved in this operation, the MDTI application is a considerable simplification of the process, especially when downloading to multiple devices.
Log Files for Debugging the AlliedView NMS Server TABLE 3-2 Overview Example Device Type File Keys Component Type Component Category Telesis (TN) iMAP Required File Keys - ADSL24AE NEW_ADSL24AE_LOAD - ADSL48 NEW_ADSL48A_LOAD - FX20 NEW_FX20_LOAD - CFC24a NEW_CFC24_LOAD - CFC56 NEW_CFC56_LOAD etc. etc. Rapier Types Rapier NEW_RELEASE NEW_PATCH NEW_GUI_RESOURCE NEW_HELP a. The CFC loads are for the cfc24univ load type.
Overview Commands for the Allied Telesis Tools Submenu 3.8 Commands for the Allied Telesis Tools Submenu Table 3-3 lists the command equivalents for the Allied Telesis Tools submenu. TABLE 3-3 Commands for Allied Telesis Tools Submenu Menu Name Windows Solaris Admin Tool AT_Update.bat AT_Update.sh Discovery Configurator DiscoveryConfigrator.bat DiscoveryConfigurator.sh License Key Form AT_LicenseForm.bat AT_LicenseForm.sh Uninstall Uninstaller.exe Uninstaller.
Status Monitoring Overview 3.9 Status Monitoring Starting in Release 8.0, the Status Monitoring feature allows the administrator to track the connections, processes, and overall status of the server(s) that make the AlliedView NMS, To access this feature, select Tools -> Status Monitoring from the Main Menu. The main window appears, as shown in the following figure.
Status Table Status Monitoring 3.9.
Status Monitoring TABLE 3-4 Status Table Status Monitoring Window (Continued) Status Type Field Description Network Inventory Table Columns Each row contains: - Type - type of network objects. Note: New network objects will be automatically added to the list. - Discovered - the total number of discovered objects. - Managed - the total number of managed objects. - Unmanaged - the total number of unmanaged objects. Port Inventory Tables for iMAPs.
Status Table TABLE 3-4 Status Monitoring Status Monitoring Window (Continued) Status Type Field Description User Connections Active User Connection Displays all active user connections to the server. Each row contains: - User Name - the name of the currently connected user. - Total - the number of connections a user has currently established to the server. Selecting a user name will display the individual threads of that user in the lower box.
Status Monitoring TABLE 3-4 Menu Options (Export) Status Monitoring Window (Continued) Status Type Field Description License Keys Name Name of the License Feature.Up to four features can be listed. ID Type Depending on the feature, this can mean whether the feature is temporary or has a certain limit Create Date When the feature was installed Expiration Date When the feature expires or Not Restricted (permanent) 3.9.
Overview (Standard versus Custom Loads) Downloading Device Files 3.10 Downloading Device Files 3.10.1 Overview (Standard versus Custom Loads) Device loads that are transferred to the NMS and then loaded onto devices are in two main types: • Standard load - This is usually a set of device loads that is pre-packaged for a release and is known to be compatible with certain NMS loads. Starting in NMS release 10.
Downloading Device Files Load Import GUI (Standard Loads) • execute AT_FwLoadImport.sh The tool can be used to load firmware into the NMS from either a CD (or file system) or an FTP server. The tool displays a list of files available for download, their timestamps, and whether or not they're already loaded into the NMS. By checking the “Get” boxes, files can be selected for download. The Get Files button will load the selected files into the NMS.
Load Import GUI (Standard Loads) Downloading Device Files FIGURE 3-35 Load Import for CD/File System AlliedView NMS Administration Guide (File Administration) 3-51
Downloading Device Files Load Import GUI (Standard Loads) FIGURE 3-36 3-52 Changing Directories for Browsing AlliedView NMS Administration Guide (File Administration)
Load Import GUI (Standard Loads) Downloading Device Files FIGURE 3-37 Upload Status as Getting Files AlliedView NMS Administration Guide (File Administration) 3-53
Accessing the NMS Database Load Import GUI (Standard Loads) FIGURE 3-38 Load Import Tool for ftp Server 3.11 Accessing the NMS Database The database used is MySQL. To access the database use the following: username=guest / password=public Contact Professional Services for more information.
4. Security Administration 4.1 Overview Administrators can configure security settings by accessing Security Administration. Security levels are achieved through the creation and defining of Users and Groups. Levels of access are defined in terms of what nodes can be viewed and what operations can be performed. Administration tasks are performed using the Security Administration wizard, which is invoked by clicking the Tools --> Security Administration menu item.The following figure appears.
Overview TABLE 4-1 Task List for Security Administration - User Task Screen / Form Name (if Applicable) Section Add User User Wizard (4.2) Configure User - Associate Groups Select Groups (4.3.2) - User Profile User Profile Tab (4.3.3) - Audit Trails Audit Trails for User Tab (4.3.4) - Change Password - Assign Operations (4.3.5) Permitted Operations for User Tab - Delete (4.3.6) (4.3.7) Add Group Groups Wizard (4.4) - Set Scope Scope Settings (4.4.
Add a New User 4.2 Add a New User For adding a new user you can follow any one of the options. • Choose the File menu from the menu bar and select New under which you can select the option AddUser. • Click the Add User icon in the Toolbar • Right-click the node named Users in the left-side tree, which is a parent node. This brings up the following figure, the User Administration wizard.
Add a New User FIGURE 4-3 User Administration Wizard (2) This User Administration screen shows the user account and password expiry in number of days. By default both values will be zero indicating that the user account and password never expire. If you need to set an expiry date for user account and password, uncheck the corresponding check boxes, and then enter the expiry period in the number of days.
Add a New User FIGURE 4-4 User Administration Wizard (3) Users can be associated with existing groups by clicking the appropriate check boxes of the groups when the checkbox Group based permissions is checked. You can also see the allocated operations for the existing groups by clicking on the right arrow for that group. Note: You can associate the new user to a new group by entering the new group name in the corresponding text box and clicking Add Group.
User Settings Overview 4.3 User Settings 4.3.1 Overview For performing user-level tasks, select the particular user in the left-side tree of the main Security Administration window under the parent node Users. 4.3.2 Associating Groups to User After selecting the particular user, click Setting Groups in the lower right corner of the Member Of panel to associate the user with any of the existing groups or to remove the user from the already associated group, as shown in the following figure.
Setting User Profile User Settings FIGURE 4-6 Setting User Profile The Security Administration tool has the provision to display the current status of the users using separate icons for different user status as shown in the left-side tree under the Users node. The various user status reflected in the User Interface (UI) are shown in the following table.
User Settings Viewing Audit Trails FIGURE 4-7 User Profile Wizard After making the necessary changes click the Ok button for updating the server. 4.3.4 Viewing Audit Trails The audit trails of all the users can be viewed by selecting the View -> Audit Trails menu or clicking the Audit Trails icon. This displays the Audit Details window where the various operations performed by the users along with the status whether the operation was a success or failure are displayed. Refer to the following figure.
Change the User Password User Settings FIGURE 4-8 Audit Trail Details - File You can save the audit details in a file for future reference to identify any access violation. To clear all the previous audit details, click Clear Trails. Note: Actions such as command input for a device can also be recorded by the SYSLOG application; the benefit of the Audit is that it shows commands that were invoked using the NMS as well as the user who invoked the command. 4.3.
Adding a new group Delete User FIGURE 4-9 Permission Tree Hierarchy The operations tree is a union of the operations included or excluded of the groups and the directly assigned operations. Thus you can assign permissions to the operations that are not associated with the group for the user. In order to modify the permissions set to the user through groups, go to the Permitted Operations For Group tab after selecting the particular group, and then click Set Permissions to do the necessary changes.
Delete User Adding a new group FIGURE 4-10 Groups Wizard (1) After entering the group name, click Next, which invokes the second screen of the Groups Wizard, as shown in the following figure.
Adding a new group Group and Scope Settings FIGURE 4-11 Groups Wizard (2) You can assign operations for the group by: • Selecting (checkmark) the check boxes to include the operations • Ticking the check box (x) to exclude operations • Leaving the check box empty so that it inherits its parent operation permission. After selecting the operations, click Finish to saving the changes permanently in the server. 4.4.1 Group and Scope Settings 4.4.1.
Group and Scope Settings Adding a new group FIGURE 4-12 Scope Settings To add a new scope, perform the following: • Give the property name and property value for the selected operation scope. • Click Add in the wizard. • Click Ok to save the changes and to exit. 4.4.1.3 Edit a Scope To edit a scope, select it and click Edit. The inputs given for the respective operation's scope that can be edited are Property Name and Property Value. 4.4.1.
Custom View Scope (CVS) Assigning Users to Group 4.4.2 Assigning Users to Group Users can be assigned to the group by selecting the particular group from the left side of the Security Administration window under the parent node Groups and in the Members tab screen in the right, click Setting Users. This invokes the Select Users Wizard where you can see all the user names in the left-side column and the selected users for the particular group in the rightside column.
Add Authorized Scope for a Custom View Scope Custom View Scope (CVS) Following are the list of tasks that can be done for the selected Custom View Scope of a group. 4.5.2 Add Authorized Scope for a Custom View Scope Generally Custom View Scopes are added through the group and scope settings. To add authorized scope to the available Custom View Scope of the group, select the relevant Custom View Scope Name and click Add AuthorizedScope, which will invoke the Scope Settings form.
Permissions Tree TABLE 4-3 Deleting Authorized Scope Operators for Setting Scope Criteria Operator Description \ (Back Slash) This is used when the name of the object itself contains a comma. This character is called an escape sequence, since it avoids searching of the objects, as if it were two different names. Example: If an object with name “a, b” has to be searched, then the property key - name and the value - “a\, b” is given.
Permissions Tree Permissions Tree FIGURE 4-14 Permissions Tree Configuration (Includes AT Devices) 4.6.2 Permissions Tree The Permissions Tree contains a list of operations that are provided by default in the NMS. Assigning different operations to different users is an administrative function. The different operations that can be assigned are explained in the following tables.
Permissions Tree Permissions Tree 4.6.2.1 Administrative Operations TABLE 4-4 Administration Operations Operation Description Services Clear Discovery This operation is used when the Discovery process has stopped. NMS Backup This Operation starts the backup process by setting BackUpInProcess variable to true and suspends all NMS Schedulers. Once the backup process is over, automatically resets the BackUpInProcess variable to false, to resume NMS Schedulers.
Permissions Tree Permissions Tree 4.6.2.3 Topology Topology is used to add, update, delete and filter out the core Managed Objects from the database. The various operations grouped under the topology module are listed in the table given below. All are under Modify Object. TABLE 4-6 Operations for Topology Operation Description Start and Stop Discovery This Operation is used to set the discovery status for the particular Object.
Permissions Tree TABLE 4-8 Permissions Tree Operations for Trap Parsers and Filters Operation Description Get Trap Parsers This Operation is for viewing the Trap Parsers present in the server. Set Trap Parsers This Operation is for modifying the existing Trap Parser or creating a new Trap Parser. 4.6.2.6 Alerts Alerts are generated when a failure or fault is detected in the network devices. The generated Alerts get displayed in the Alert Viewer.
Permissions Tree Permissions Tree 4.6.2.8 Polling Unit Polling units mentioned here refer to PolledData objects which are the basic unit of data collection. These define what data to be collected and from which network device. PolledData can be added via Client User interface. The operations possible with PolledData objects are listed below.
Permissions Tree Permissions Tree can be added for the Managed object or existing PolledData can be removed using Poll Filters. Different operations possible with Poll Filters are listed in the following table. TABLE 4-13 Operations for Poll Filters Operation Description Get Poll Filters This operation permits retrieval of Poll Filters from the database and display them. If excluded will not allow you to view the Poll Filters list.
RADIUS Remote Authorization (RADIUS / Tacacs+) on Devices TABLE 4-15 Operations for AT Object Operation Operation Description Device Information Operation Permits the display of device information SNMP Agent Operation Permits SNMP Agent operations SNMP Community Operation Permits SNMP Community operations Configure VLAN Operation Permits VLAN configuration operations (Includes EPSR) Card Management Operation Permits card management operations Port View Operation Port Management Operation (c
Remote Authorization (RADIUS / Tacacs+) on Devices Tacacs+ (Using the CLI Login Manager) FIGURE 4-15 Filling out the MO Property Form for Remote Authentication 4.7.2 Tacacs+ (Using the CLI Login Manager) For Tacacs+, the user can provision on a per-device basis as well, but the administrator can also provision this on a systemwide basis, using the special User ID TACPLUS_USER, and then filling in the appropriate password.
Overview NMS RADIUS Client Support 4.8 NMS RADIUS Client Support 4.8.1 Overview Starting in NMS Release 11.0 SP5, RADIUS Authentication for NMS user logins is supported. Prior to this feature, NMS supported devices that used RADIUS/TACACS (see 4.7), but NMS user ids were not authenticated via these methods. With this feature, an open source RADIUS client is integrated into the NMS server, using a central RADIUS server on the customer’s network. Note: RADIUS is specified in RFC 2865 (http://www.ietf.
NMS RADIUS Client Support RADIUS Configurator Tool (with Valid License) FIGURE 5 Overview - NMS Server with RADIUS Client 4.8.2 RADIUS Configurator Tool (with Valid License) Once this feature is installed the login procedure is transparent; the client interface is the same with or without RADIUS authentication. The main change to the NMS server is the addition of the AT_ConfigureRadius tool, which can be launched as follows: 1. On Windows, double-clicking AT_ConfigureRadius.
RADIUS Configurator Tool (with Valid License) FIGURE 4-1 NMS RADIUS Client Support Error Message for Invalid License The purpose of this tool is to configure the NMS server as a RADIUS client-that is, enable/disable RADIUS authentication and create a list of server contact information (address and port) and shared secrets to be used during authentication when enabled.
NMS RADIUS Client Support RADIUS Configurator Tool (with Valid License) Servers can be added via the fields on the lower part of the display.
RADIUS Configurator Tool (with Valid License) NMS RADIUS Client Support Multiple servers can be added. Servers can be designated by IP addresses or valid host names. During login, the authentication process will try each server in the order displayed, from top to bottom, until one server accepts the authentication request or all servers have rejected it. The order can be changed with the arrow buttons. Note that: • The Add button will not allow adding a server that already exists in the table.
NMS RADIUS Client Support RADIUS Configurator Tool (with Valid License) Whereas only one server may be added at a time and only one may be modified at a time, multiple servers may be deleted by selecting multiple rows and clicking on the Delete button. FIGURE 8 RADIUS Configurator - Deleting Servers Changes are not saved until either the OK or Apply button is selected. Note: 4-30 When activating the NMS client, set the Status to ‘On’ before selecting OK or Apply.
RADIUS Configurator Tool (with Valid License) NMS RADIUS Client Support All changes won't take effect until the server is restarted. So after changing the State to ‘On” and selecting OK or Apply, the modifications are completed and the tool displays the following message: FIGURE 9 Note: Message - RADIUS Configured, need to Restart When RADIUS is activated or deactivated, the NMS server is shut down. It must then be restarted.
NMS RADIUS Client Support RADIUS Configurator Tool (with Valid License) RADIUS Authentication State=DISABLED Server ----------10.52.18.79 10.52.18.77 10.52.18.78 Auth Port --------1812 1812 1645 Acct Port --------1814 1814 1646 Secret --------nmssecret nmssecret nmssecret $ ./AT_ConfigureRadius.sh enable RADIUS Authentication State=ENABLED Server ----------10.52.18.79 10.52.18.77 10.52.18.
Example Configurations NMS RADIUS Client Support 4.8.3 Example Configurations 4.8.3.1 Overview The following examples go through setting up of the NMS RADIUS Client Support and include inputs at both the RADIUS and NMS servers. Regardless of the platform used (FreeRadius or Cisco Secure ACS), there are four main steps. The first three are for configuring the RADIUS server: 1. Identify the Vendor Specific Attribute (VSA) that names the permission groups 2.
NMS RADIUS Client Support Example Configurations 4.8.3.2 FreeRadius Example FreeRadius is a free RADIUS server and is installed on 10.52.18.79. Note: Downloads and documentation are available at http://freeradius.org/. To configure for the NMS, begin with cd to /usr/local/etc/raddb and perform the following steps: Note: For the account Keith_K, the password being defined on RADIUS is different than the password assigned when it had been created on the NMS.
Example Configurations NMS RADIUS Client Support FIGURE 4-1 Configuring NMS as RADIUS Client 4.8.3.3 Cisco Secure ACS Example Cisco Secure ACS is a widely-used fee-based RADIUS and TACAC server available from http://www.cisco.com. It comes in platform-specific versions, including various Windows versions. Note: The NMS is the RADIUS client, which is known as the NAS in the RFC, and is called the AAA Client in Cisco terminology.
NMS RADIUS Client Support 2. 2. 3. Feature Interactions (RADIUS Server De-activated or Use CSUtil.exe -listUDV to list available slot numbers and identify one that is unassigned. If none are unassigned, this RADIUS instance has reached its maximum and cannot be used. Either free one or get another server. Add the NMS server as the RADIUS client. 1. Use CSUtil.exe -addUDV c:\ACS_Data\allied-telesis.ini to import the VSA file. 2.
Feature Interactions (RADIUS Server De-activated or Unavailable) NMS RADIUS Client Support 2. Change which users belonged to which permission groups. 3. Assign new user IDs and passwords, and associate them with a group or groups Note: To make these changes, the RADIUS server may need to be restarted. Refer to the appropriate documentation.
NMS RADIUS Client Support 4-38 Feature Interactions (RADIUS Server De-activated or AlliedView NMS Administration Guide (Security Administration)
5. Controlling and Provisioning Network Devices 5.1 Overview In providing network management functions, the AlliedView NMS can provision a single device. However, in many cases a set of devices should be provisioned together, and the AlliedView NMS provides a GUI that allows the administrator to create a set of devices and then use wizards that allow provisioning across that set of devices.Figure 5-1 highlights the various options that appear when choosing a device.
Overview TABLE 5-1 Task List for Provisioning Task Screen / Form Name (if Applicable) View Chassis Provision Allied Telesis Device Section (5.2) Overview of Provisioning Application (5.3.1) - Backup/Restore Device Backup/Restore in pull-down (5.3.2) - Command Script Management Command Script Mgmt in pull-down (5.3.3) - Configuration File Management Configuration File Mgmt in pull-down (5.3.4) - Device Information Device Information in pull-down (5.3.
Overview TABLE 5-1 Task List for Provisioning (Continued) Task Screen / Form Name (if Applicable) Section Card Management Card Management (5.5.1) Create (5.5.3) GE3, GE8 (5.5.4, 5.5.5) ADSL16 (5.5.6) ADSL24, ADSL24AE (5.5.7) SHDSL24 (5.5.8) CFC (5.5.9, 5.5.10) FE10 (5.5.11) FX10 and FX20 (5.5.12) POTS (5.5.13) - Card can support MGCP or SIP CES8 (5.5.14) NTE8 (5.5.15) ADSL24A/B (5.5.16) PAC24A, PAC24C (5.5.17) EPON2 (5.5.18) VDSL24 (5.5.19)) ADSL48A (5.5.20) GE24POE (5.5.
Overview TABLE 5-1 Task List for Provisioning (Continued) Task Screen / Form Name (if Applicable) Section - Port Management (iMAP Devices) Port Management (iMAP Devices) Application (5.6.2) New Triple Play (5.6.3) New Ethernet (5.6.4) New ADSL (5.6.4) New CES8 (5.6.6) New NTE8 (5.6.7) New SHDSL (5.6.8) New EPON (5.6.9) New ONU (5.6.10) New VDSL24A/B (5.6.11) View Triple Play (5.6.12) View Status (5.6.13) Add Voice Line (5.6.14) View iMG/RG (5.6.15) View Ethernet (5.6.16) View ADSL (5.6.
View Chassis TABLE 5-1 Task List for Provisioning (Continued) Task Screen / Form Name (if Applicable) Section Network Services HVLANs Section 6. Network VLANs Profile Management QoS Management Customer Management Enhanced Protection Switched Ring (EPSR) UPC Monitoring Query/Control Device - Alarms/Events Alarm Panel and Network Events panel (5.9.1) - Performance Configured Collection Panel (5.9.2) - Compare Configuration Files iMap Device, Applications (5.9.
View Chassis Display Types FIGURE 5-2 Chassis view of a Rapier Product For iMAP products, the chassis view reflects which cards are configured and in what slot they are located. A graphical representation of each provisioned card is displayed, including the colors of any LEDs and any markings on the card face. An example is shown in the following figure.
Display Types View Chassis • Card is installed but not provisioned - The card appears grayed-out and has the label “NOT PROVISIONED” across the front as shown in the following figure. FIGURE 5-4 An Example NOT PROVISIONED Card in the Chassis View • Unknown card - When the chassis view detects a card that is not supported, it displays the board with an “Unknown Board” image. Refer to the following figure.
View Chassis Note: Display of VLAN-based HVLANs (Tunneling) For the AT-x610, stacking will not start until after the unit has been booted and the stack-XG card has already been inserted. If the card is removed (or is replaced), and the x610 is not rebooted, the chassis view shows a duplicate image. 5.2.2 Display of VLAN-based HVLANs (Tunneling) For the iMAP and SBx3112, an outer tag can be applied for certain ethernet-based cards, allowing an outer VLAN to be applied to several customer interfaces.
Notes on Chassis View Provisioning a Device 5.2.3 Notes on Chassis View Following are device-specific notes on the chassis view: • 9000 devices • Displaying port status/alarms in the Chassis View is supported. • Filler plates are included in the chassis view. • Support the FAN8 module in the 9700. This module is always displayed (even if removed for maintenance). The states of the Pull, Fault and Insrv LED components on the Fan module in Chassis View reflect those of the LEDs on the physical device.
Provisioning a Device Overview of the Provisioning Interface application remains with its set of devices and state: if the user then decides to return to the first application, it retains that status and set of devices. FIGURE 5-8 Selecting a Device for Backup/Restore The selected device is included in the Selected Devices column. The following table describes the buttons that are available once an application is selected.
Overview of the Provisioning Interface TABLE 5-2 Provisioning a Device Buttons Common to Applications (Continued) Button Icon Meaning Description Search Brings up search dialog allowing search by column for a text string, with options for starting row and matching cases shown here: Table cells with the text are highlighted yellow. Search Next Once a text string is found, find the next table cell that has the text string.
Provisioning a Device Overview of the Provisioning Interface FIGURE 5-9 Selecting the Application Manager to View all Applications Many of the buttons are grayed out because an application has not been selected. At this point, the user can double-click on one of the Applications in the table (or select the application, and then click GO) and it will invoke the specific application window.
Overview of the Provisioning Interface Provisioning a Device Table 5-3 lists the options for the AppManager window. Clicking Done closes the window. TABLE 5-3 Options for the Add / Remove Devices for an Application Option Description Available Devices Available devices for the application are in black. Clear Clear all devices from the Selected Devices list. Add / Remove Sends a device from one column to another.
Provisioning a Device Backup/Restore (with Purge Button) FIGURE 5-11 Copy Device List for an Application - File The example shown in Figure 5-11 would occur if the user has previously collected data for devices 172.16.33.14 and 172.16.33.15, and then right-clicks device 172.16.33.16 for the SNMP Community application.
Backup/Restore (with Purge Button) FIGURE 5-12 Note: Provisioning a Device Collected Data for Selected Devices for Device Backup Restore (Network Selected) If for any devices the data cannot be collected, the row is dark; the Tooltip for that row will include the reason, such as “Unable to Connect.” 5.3.2.2 Performing Backups At this point the user can perform the following: • Select multiple devices and perform a backup only. • Select one device and perform a backup or restore.
Provisioning a Device Backup/Restore (with Purge Button) FIGURE 5-13 TABLE 5-4 Initial Backup Window Backup Device Configuration Fields Field Meaning Listed Device(s) Device(s) that will have a backup created. Devices in subnet Backs up all devices for the specified subnet. The query is done when the task is executed, so that for a recurring task, new devices added since that task was created will be backed up during the next execution of the task.
Backup/Restore (with Purge Button) FIGURE 5-14 Provisioning a Device Recurring Backup Schedule Window - File In Figure 5-14, the backup has been scheduled for Sunday morning at 4 a.m. every week. Clicking Finish adds the backup to the schedule. Note: It is highly recommended that you configure your device configuration backup to run on a recurring schedule to preserve configuration changes made by the NMS.
Provisioning a Device Backup/Restore (with Purge Button) 5.3.2.3 Restore Configuration (Options Depend on Device Type) Once a device or set of devices has a backup file, it can be restored. Select a device that has a backup file and click Restore Configuration. One of the following figure appears, depending on the device to be restored. For Rapier/Switchblade devices only, the Rapier/Switchblade options are enabled, as shown below.
Backup/Restore (with Purge Button) FIGURE 5-16 Provisioning a Device Restore Configuration for iMAP Devices Only For iMAPS and Rapier/Switchblade devices, the Rapier/Switchblade filename option is enabled but checkboxes are disabled, as shown below.
Provisioning a Device Backup/Restore (with Purge Button) For iMG/RGS only, these cannot be selected with iMAPs, Rapiers, etc, and the entire lower panel is removed, as shown below. FIGURE 5-18 Restore Configuration for iMG/RG Devices There is the option to make the restored file the default configuration. If this option is chosen, the Restart Rapier checkbox is active and can be used to restart the Rapier with the restored file. The following table lists the options available.
Command Script Management Provisioning a Device FIGURE 5-19 Note: Purge Backup Dialog The value for what appears is from the AT_NmsBackupFiles.conf configuration file. The number must be greater than 0. Refer to 3.4.5. The dialog includes a “Purge” button to activate purging and a “Cancel” button to dismiss the dialog without executing a purge. Selecting Purge brings up the confirmation dialog. If the user confirms the operation, then all but the latest number of files per device will be deleted.
Provisioning a Device Command Script Management FIGURE 5-20 TABLE 5-6 Command Script Mgt Window Command Script Mgmt Buttons/Fields Button/Field Description Upload Retrieves a file from the device. The user has to pick a file name from a list retrieved from the device. It can be stored either under the user's scripts path or under the user's devicespecific in the server-side file system. Refer to 5.3.3.1.
Command Script Management Provisioning a Device FIGURE 5-21 Upload Window for Script Mgt Files 5.3.3.2 Download/Execute To download and then execute script files, select one or more devices in the Command Script Mgmt window and click Download/Execute.
Provisioning a Device Command Script Management FIGURE 5-22 Download Window After finding the appropriate file and clicking Download, the Download Command Script window appears, which lists the devices the script will be execute on, as shown in the following figure. Note: The blank field allows the user to specify a filename to use on device in case the server-side name is too long, missing the extension, etc. The extension must be .scp.
Command Script Management Provisioning a Device FIGURE 5-24 Command Script Execution If the network connection to the device is lost or the script fails to complete, the error Connection Lost or script not completed may appear in an Errors window and in the Command Script window, as shown in the following figure. FIGURE 5-25 Failure to Run Script Whatever script output received up to the point of failure will be displayed in the Output Window.
Provisioning a Device Command Script Management 5.3.3.3 Edit Files The Edit Files button brings up the unloaded multi-paged editor, from which command scripts can be written, saved and edited. The Edit window functions are described in 5.3.15. For command script files, the Editor displays the contents of a Command Line Interface (CLI) script. The script file contains one or more CLI commands. Comments are identified as a hash (#) as the first character on a line.
Configuration File Management Provisioning a Device 5.3.4 Configuration File Management For Rapier and iMAP devices, the configuration file is an ASCII-formatted file that contains the complete configuration of the device. When the device is rebooted, the configuration file can replace the currently active (running) configuration. Note: Significant configuration changes made using configuration files will not be reflected in the NMS until the devices are rediscovered.
Provisioning a Device Configuration File Management FIGURE 5-27 Upload Window for Configuration Mgt Files Click Next to bring up the Schedule Panel, where the user can select Now (default), One Time (Schedule) or Recurring date/ time. Clicking on Finish begins execution immediately (Now). Note: Blank names are suitable for recurrent uploads since new names will be chosen by the system as uploads are performed.
Device Information Provisioning a Device FIGURE 5-28 Download Config File Form - From Backup Directory 5.3.4.3 Edit Window This Edit window has the same functions for Configuration and Script files, and is described in 5.3.15. 5.3.4.4 Delete Window The Delete window brings up a list of configuration files for the selected device(s), from which the user may delete, and is described in 5.3.16. 5.3.
Provisioning a Device SNMP Agent FIGURE 5-30 Change Device Information Window In this window the Name, Location and Contact can be changed. When more than one device is chosen, the Change Info button is activated; clicking it also brings up the Change Device Information window, but only the Location and Contact information can be changed. 5.3.6 SNMP Agent The Simple Network Management Protocol (SNMP) involves the device agent, which controls the managed objects in the device.
SNMP Agent Provisioning a Device FIGURE 5-32 SNMP Agent Panel To modify the agent for one or more devices, select the rows, and then click Modify (now active). The following figure appears. FIGURE 5-33 Configure SNMP Agent Panel The following table lists the options available. TABLE 5-8 SNMP Agent Fields Option Description Agent status A checkbox to enable or disable the device(s).
Provisioning a Device SNMP Community 5.3.7 SNMP Community An SNMP community helps to define the relationship between the AlliedView NMS and the Management Information Base (MIB) of the device, in essence defining the operations that can be performed on various objects in the device. For each device there may be multiple communities, with each community providing a set of operations.
SNMP Community Provisioning a Device FIGURE 5-35 Create SNMP Community Form AlliedView NMS Administration Guide (Controlling and Provisioning Network Devices) 5-33
Provisioning a Device SNMP Community FIGURE 5-36 Modify SNMP Community Form When the Copy button is clicked, a two-page form appears. Both pages are shown in the following figures.
SNMP Community Provisioning a Device FIGURE 5-38 Copy SNMP Community Form (Second Page) - File The following table lists the options available. TABLE 5-9 Community Configuration Fields Option Description Community Name A text box when adding (creating) a community name, a drop-down of community names when modifying a community name. When adding a community, clicking on the Add/Remove button adds the community.
Provisioning a Device SNMP Community FIGURE 5-39 Delete Snmp Community Window The user can then select the communities for the Target Device (or Select All) and by clicking OK, delete those communities.
Obtaining SW Loads Provisioning a Device 5.3.8 Obtaining SW Loads The user can go to the web site and get the appropriate files (xml/tar) they wish to use for their specific NMS configuration and place them in the /swdownload directory. 5.3.9 Software Configuration (Standard Loads) When the Software Configuration application is chosen and the Collect Data icon is clicked, the following figure appears. FIGURE 5-40 Software Configuration Panel 5.3.9.
Provisioning a Device Software Configuration (Standard Loads) 5.3.9.2 Modifying Software Configuration The table shows for the selected devices all of the filetypes for the devices. When the user selects the devices and clicks Modify Release Configuration, the Modify Release Configuration form appears, as shown in the following figure. Caution: For the devices that will receive downloads, do not set their telnet idle session time-out to any value less than 6 minutes.
Software Configuration (Standard Loads) Provisioning a Device Table 5-10 lists the options available. TABLE 5-10 Software Download Buttons/Fields Option Description Loads A pull-down menu for choosing the software release for the device. For iMAP devices, the user can select loads that assume Annex A or Annex B cards are being loaded. Delete old release files if space needed A checkbox that tells the device to delete old release files before loading the chosen release file.
Provisioning a Device Software Configuration (Standard Loads) 5.3.9.3 Purge Load Files The Purge Load Panel lists all the load bundles and gives a summary of their contents. Older load bundles can be selected for deletion. When deleted, all files making up the load bundle will be deleted. “Obsolete” bundles are bundles in which all files are superseded by 2 or more versions from other bundles. Any bundle can be deleted any time, but “obsolete” bundles are pre-selected for convenience.
Software Configuration (Standard Loads) Provisioning a Device Once you have accessed the site, you will go through a series of forms where you enter your id, password, give general customer details, and correlate an OS with the serial numbers of your devices. You must also fill in details on the device for each serial number. (Note that you do not have to enter information for all your devices and can revisit your account later.
Provisioning a Device Software Configuration (Standard Loads) selected attributes appear. This would mean changing either the Select Props to View or Additional Props to match what you wish to capture. You can then select the row with the mouse, use Control-C to copy, then go to the appropriate window and Control-V to paste. 5.3.9.
Software Configuration (Standard Loads) Provisioning a Device An MTAC can be one of 9 types, depending on the type of device for which it can be used to generate passwords: 1. AT-AR-7/400 for AT-AR700 series devices 2. AT-AR-RAPIER/8800 for Rapier devices 3. AT-86/8700xl for 8600 and 8700 series devices 4. AT-AR750 5. AT-AR-SB/9800 (SB) for Switchblade devices 6. AT-AR-89/9900 for AT-8900 series devices 7. AT-AR440S and 450S 8. AT-AR-SB/9800 (9800) for 9800 series devices 9.
Provisioning a Device Software Configuration (Standard Loads) When a row of the table is selected with the cursor, the modifiable details of the selected MTAC are displayed in the fields below the table. Changes are committed with the Modify button. If an MTAC id is changed, the previous id will be deleted and replaced with the new id New MTACs can be added with the Add button. MTACs with duplicate ids cannot be added. All fields (MTAC, Password, and Type) are mandatory.
Software Configuration (Standard Loads) Provisioning a Device The second panel displays all the devices, their serial numbers, their supported releases, and their passwords, if any. Refer to Figure 5-46. FIGURE 5-46 MTAC Wizard - Second Panel Devices and releases can be selected from the table for password generation. Although any or all rows from the table can be selected, the ones that already have passwords will be ignored during password generation. The Back button returns to the MTAC panel.
Provisioning a Device Software Configuration (Standard Loads) FIGURE 5-47 Possible Error Messages for MTAC Wizard Panel (2) 3. Third Wizard Panel - Passwords will be generated for the following devices The 3rd panel provides the user a chance to confirm selections before committing them, as shown in Figure 5-48. FIGURE 5-48 MTAC Window - Third Panel For each password to be generated, this panel displays the device, the release, the MTAC type, and the MTAC that will be used.
Software Configuration (Standard Loads) Provisioning a Device If all passwords are successfully generated, a popup display will indicate so. Upon acknowledging this popup, the wizard will be dismissed. If any errors are detected during password generation, a popup message will indicate so and the wizard will remain up for modifications. An example of the success popup dialog is Figure 5-49.
Provisioning a Device Software Configuration (Custom Loads) 5.3.10 Software Configuration (Custom Loads) The Custom load configuration is entered from the Software Configuration application using the Create Custom Load button, as shown in Figure 5-40, at the beginning of this subsection on Software Configuration. This button is device independent and therefore enabled with or without any devices selected.
Software Configuration (Custom Loads) FIGURE 5-51 Provisioning a Device Custom Device Loads Form When the Details button is selected, the form is brought up, it shows the name and description of the selected load, all the types belonging to the load, and all the details for any selected type from the table. If the load is a standard load, none of the fields are modifiable. The details consist of a table of File Keys and File Names.
Provisioning a Device Software Configuration (Custom Loads) FIGURE 5-52 Custom Device Loads Form - Standard Load If the load is a custom load, then types can be added, modified, and deleted. See Figure 5-53.
Software Configuration (Custom Loads) FIGURE 5-53 Provisioning a Device Custom Device Loads Form - Custom Load To add a new type, begin by choosing the type from the combo box in Type Details, as shown in Figure 5-54. The file keys for the type are predefined and will appear in the File Keys column. The File Names will normally be blank, but in some cases where a file name was listed for the same key from the previous type, if any, the name will default to the previous name.
Provisioning a Device Software Configuration (Custom Loads) If the type selected from the combo box already exists in the load, its row in the table above will be highlighted and its details will be defaulted to their existing values. Push the Add button after entering all the details and verify the new type is added to the table. If you do anything else instead of pushing the Add button, a popup dialog will ask whether or not to finish the addition for the device.
Software Configuration (Custom Loads) Provisioning a Device The file name can be typed, pasted (with ctl-v), or selected with a file chooser. The file chooser will list all the files loaded in the device's category directory (either swdownload/Rapier or swdownload/MAP). See Figure 5-55. In some cases, one or more file names will be optional for a load. When unneeded for iMAP devices, the field should be left blank. For Rapier devices, the field should be set to NONE.
Provisioning a Device Software Configuration (Custom Loads) 5.3.10.1 Creating a Custom Load for the SBx3112 For the SBx3112 load release 16.0.x, there is a common line card load that includes the text string sma (currently x31sma_16.0.1.tar). If you try to use the Software Configuration feature and select the standard SBx3112 load, you will receive a ‘Card not Supported’ error. Refer to the following figure. FIGURE 5-57 Download Standard iMAP/SBx3112 - Will fail for SBx3112.
Software Configuration (Custom Loads) FIGURE 5-58 Provisioning a Device Creating Custom Load Name Then press the Add button. The Name is added to the Load Name list in the upper panel. Possible error messages are: • A Description is Required • Load Already Exists Pushing the Details button brings up the Load Details window. Under Load details, select the SBx3112 from the pull-down. Refer to the following figure.
Provisioning a Device Software Configuration (Custom Loads) FIGURE 5-59 Selecting Device for Load Details The Load details panel lists the types of loads for the device. For the CFC200, select Browse and choose the appropriate cfc200 file. For the line cards, select the same sma-type file for all. Refer to the following figure.
Software Configuration (Custom Loads) FIGURE 5-60 Provisioning a Device Adding Line Card Loads for SBx3112 (same file) Click on Add. Then click Modify on the Load panel. This custom load is now added, and will appear as a possible load for the Modify Release Configuration, as described in 5.3.
Provisioning a Device Software Configuration (Custom Loads) FIGURE 5-61 Note: 5-58 Custom Load for SBx3112 for Software Device Another option is to use the Card Management feature an load each card individually with the sma line card load.
Using Custom Loads to Reduce Unneeded Card Types Provisioning a Device 5.3.11 Using Custom Loads to Reduce Unneeded Card Types Standard loads are defined to load software for all card types a device may support at a given release level. In most cases, this will be more software than necessary since most devices will not contain all possible card types. Download times and memory usage will be greater than necessary.
Provisioning a Device Using Custom Loads to Reduce Unneeded Card Types p FIGURE 5-63 5-60 Custom Load Containing Only Necessary Files AlliedView NMS Administration Guide (Controlling and Provisioning Network Devices)
SysLog Management Provisioning a Device 5.3.12 SysLog Management The SysLog Management application allows you to manage logs from the managed devices in the AlliedView NMS. When the SysLog Management application is chosen and the Collect Data icon is clicked, the following figure appears. FIGURE 5-64 SysLog Management Panel From this panel, you can delete selected rows by pressing the Delete button. A confirmation window confirms the deletion.
Provisioning a Device LLDP Protocol and Associated Features (LAG/VCS Monitor- 5.3.13 LLDP Protocol and Associated Features (LAG/VCS Monitoring) The LLDP protocol feature on devices is a way to advertise data that is useful for discovering information about a network link port. If the administrator manually enables LLDP for each device and sets the direction as BOTH, the links between the devices will appear on the physical map GUI as the devices are (re)discovered.
LLDP Protocol and Associated Features (LAG/VCS Monitoring) FIGURE 5-67 Provisioning a Device LLDP MultiDevice Wizard for Multiple iMAP Devices - First Panel Note the Re initialization Delay attribute has Mixed rather than a numeric value. This means there are different values of the devices. Inputting a New Value (such as 2) will change the value to 2 for all the selected devices. The second panel brings up a panel that controls the options for the multiple devices.
Provisioning a Device FIGURE 5-68 LLDP Protocol and Associated Features (LAG/VCS Monitor- LLDP MultiDevice Wizard for Multiple iMAP Devices - Second Panel The pull-downs are as follows: • LLDP Mode - The options are TX, RX, BOTH or OFF. Note that to activate LLDP so that the links are drawn on the physical map, this must be set to BOTH. The specific attributes for the ports can then be set. • LLDP Notification - This can be set to ON or OFF.
LLDP Protocol and Associated Features (LAG/VCS Monitoring) Provisioning a Device • Delete from All - delete all options from all ports if the option is applied to any or some ports. • Other options • Add to All - make the one option apply to all ports. This would take priority over the ALL Row. • Delete from All - make the one option be deleted for all ports. This would take priority over the ALL Row. • No Change - Keep the current value regardless of any changes made with the ALL option.
Provisioning a Device FIGURE 5-70 LLDP Protocol and Associated Features (LAG/VCS Monitor- LLDP MultiDevice Wizard for Single Device Options - Second Panel To configure the many possible options, the following concepts are used: • ALL Ports row - This row controls multiple actions as follows: • Mode - Selecting this cell brings up a pull-down of Modes, and selecting one means selecting the Mode for all ports on the device, including OFF, which disables LLDP for all ports.
LLDP Protocol and Associated Features (LAG/VCS Monitoring) Provisioning a Device 5.3.13.3 LAG and VCS Support The Physical Network Map shows the discovered devices and the physical connections (links) between them. The physical link icon between devices appears if the both devices support LLDP, and the NMS actively supports the LLDP functionality of the device. Note: The physical links can also be manually created using the Link Operation function. Refer to 6.2.4.
Provisioning a Device LLDP Protocol and Associated Features (LAG/VCS Monitor- FIGURE 5-73 • Show LAG Links option - Right click on the LAG links icon and select Show LAG Links to bring up the LAG/VCS screen. Refer to the following figure.
LLDP Protocol and Associated Features (LAG/VCS Monitoring) Provisioning a Device The LAG ID can be as follows: • - Port is not down and LAG channel is up • Not Configured - Port is not configured for LAG but the neighboring port is • - (AlliedWare devices) - Port is not associated with any LAG Channel • Chassis View - In the Chassis View for a device, ports that are members of a LAG are labeled “LA”.
Provisioning a Device MPEG Test 5.3.14 MPEG Test The MPEG Test feature allows the user to setup, monitor, and view the results of MPEG tests run on the iMG/RGs in a network. With the feature the user can set up a “Network Test” across multiple iMG/RGs in a network. Once set up, the AlliedView NMS runs an MPEG test on the selected iMG/RGs using the mpeg testing functionality included with the iMG/RGs devices.
MPEG Test Provisioning a Device FIGURE 5-78 Create MPEG Test Form Fields to datafill are: • Test Name - This should be descriptive, and becomes the Name of the test in the Task List Details window. • Channel List - The multicast IP address(es) for the channel(s) to be tested. If multiple channels are entered, each channel will be tested sequentially. (If multiple iMG/RGs were selected, all iMG/RGs will be tested simultaneously.) Example values would be 225.1.1.11, 225.1.1.
Provisioning a Device MPEG Test FIGURE 5-79 Create MPEG Test - Recurring Schedule For the recurring schedule, the user can choose: • • • • Now - Clicking on Finish starts the test immediately. Hold - This sets no time; the test is activated through the View Tasks window. One Time - Sets one time only to run the test Recurring - This is set on a minute basis and can be one time, a specific time every week (shown in the above figure), or a specific time on a day of the month.
MPEG Test Provisioning a Device FIGURE 5-80 Viewing Test Results for MPEG Test To review specific test results, double-click on a row in the table or right click on a row and select View Test Result MPEG Test Results Details panel, as shown in the following figure.
Provisioning a Device MPEG Test The “Combine Device Data” Radio button combines all the data from each iMG/RG into a single row entry, as shown below.
MPEG Test Provisioning a Device The “Combine Channel Data” Radio button combines all the data from each multicast into a single row entry, as shown below.
Provisioning a Device MPEG Test To delete the test results, select one or more tests form the Test Results panel, right click, and select Delete Test Result. (Note that View Test Result is grayed out.) Refer to the following figure. FIGURE 5-84 Deleting MPEG Test Results To modify the schedule/recurrence of a test, select Tools -> View Tasks, and select the Task Name (the Name entered for the test) form the View Tasks table. Select View Details, and then the Modify Schedule button.
Using the Edit Functions Provisioning a Device 5.3.15 Using the Edit Functions The Edit window has the same functions for both the Command Script Management and Configuration File Management functions, and so the explanation for how the window works can apply to both types of files. In the Command Script application, the Edit window brings up the unloaded multi-paged editor. The editor has Open and Save as buttons that work with the server file system.
Provisioning a Device Using the Edit Functions FIGURE 5-87 File Pull-down for Edit of Scripts Selecting the File -> Open menu item brings up a listing of the latest files from the server file system for the devices highlighted on the Command Script Mgmt panel when the editor was launched. Files can be viewed as a simple list or with details (Size, Type, when Modified). Template files can also be created and included. Refer to Figure 5-88 and Figure 5-89.
Using the Edit Functions FIGURE 5-89 Provisioning a Device Files Available for Edit from Server File System (Details View) Once a file is opened and edited, it can be saved on the Server File System. Files can be saved as templates for future script writing. Refer to Figure 5-90. Note: Since files are being saved to the server (rather than a device), unrestricted filenames and extensions are allowed.
Provisioning a Device Using the Edit Functions FIGURE 5-90 Saving Files after Editing 5.3.15.2 Edit Menu The Edit menu has conventional options (CUt, Copy, Paste, Delete, Select All). Right-clicking in the text area will bring up these options as well. Refer to Figure 5-91.
Using the Edit Functions Provisioning a Device FIGURE 5-91 Edit Menu Options for Text Files 5.3.15.3 Search Menu The Search menu provides for searching within the current window. Conventional Find and Replace options are provided. Refer to the following figures.
Provisioning a Device Using the Edit Functions FIGURE 5-92 5-82 Search Find Option AlliedView NMS Administration Guide (Controlling and Provisioning Network Devices)
Using the Delete Function Provisioning a Device FIGURE 5-93 Search Replace Option 5.3.15.4 Window Menu The Window menu provides changing between open files. Each time a file is entered, the cursor, text selections, and scroll bar are in the same state they were in when that file was left. The Window menus changes dynamically as files are opened, created, and closed. FIGURE 5-94 Window Menu for File Editor 5.3.
Provisioning a Device Using the Delete Function With no devices selected, the Delete button brings up a file chooser that provides navigation among all the user's directories and lets the user delete one or more files from the same directory. Select one or more files to delete: When the files for deletion for a device are listed, the user can select the details icon and see the file properties, as shown in the following figure.
Using the Delete Function Provisioning a Device FIGURE 5-97 Multi-File Delete Window With two or more devices selected, this wizard displays all the files with names common to all the selected devices. Files with any other names will be left out. No file properties or pathnames can be displayed since they may differ among the various devices even though the file names are the same. This wizard will delete selected files from all the device directories in one operation. Refer to the following figure.
Provisioning a Device SNMPv3 USM Configuration 5.3.17 SNMPv3 USM Configuration This SNMPv3 uses the User-Based Security Model (USM) and is specified in RFC2574. The USM has the concept of multiple users where each user provides secret keys for authentication and privacy. The authentication protocols specified for use are HMAC-MD5 and HMAC-SHA. The privacy protocol specified is CBC-DES. From the panel the administrator can activate this model for one or devices, similar to other MDTI applications.
SNMPv3 USM Configuration Configure VLAN (Chassis View) 5.4 Configure VLAN (Chassis View) To configure a VLAN for a single device, right-click the device, and then select Provision -> Configure VLAN. The VLAN chassis configuration screen will open immediately and fill in the present VLAN configuration. Refer to the following figures for examples of the configuration screen.
Configure VLAN (Chassis View) FIGURE 5-101 SNMPv3 USM Configuration VLAN Configuration Screen (iMAP Device) The following table gives an overview of the fields, graphics, and buttons available. TABLE 5-12 VLAN Configuration Options Screen Item Description Create If creating a VLAN on the device, select this button first. You will see a Create New VLAN form. Fill in the Name and ID, and then click OK, and the VLAN is added to the Vlan Interfaces pull-down.
SNMPv3 USM Configuration TABLE 5-12 Configure VLAN (Chassis View) VLAN Configuration Options Screen Item Description Link Ports These are the ports that are used for connection to another device and are used as part of one or more Network VLANs including the current VLAN. On the display, these will be identified with the capital letter L. A Link Port cannot be changed from the VLAN Configuration screen.
Configure VLAN (Chassis View) TABLE 5-12 SNMPv3 USM Configuration VLAN Configuration Options Screen Item Description View Last Action This will open up the Recent Commands... window and show what command and response were involved in the last action on the form. Close Closes the form. Note: If this VLAN Configuration form is invoked from the Chassis View, the Close button is replaced with the Chassis View button, to return to the first view of the device.
Overview Card Management 5.5 Card Management 5.5.1 Overview This application for the iMAP 9000 and SBx3112 devices allows the user to view, in a table format, the configuration of the device and then provision/configure its cards. Moreover, this table is updated real time as changes occur to the cards. Note: Controlling the card configuration involves understanding how provisioning data works in the iMAP devices, so an overview of provisioning data is given after the description of the application.
Card Management 5-92 Accessing the Card Management Application FIGURE 5-103 Card Management Window for iMAP 9400 FIGURE 5-104 Card Management Window for iMAP 9700 AlliedView NMS Administration Guide (Controlling and Provisioning Network Devices)
Creating a Card (Pre-provisioning) TABLE 5-13 Card Management Card Management Application Window Field/Button Description Device Name The Name given to the device in the Managed Objects property table Slot The slot in the iMAP device that contains the card. Card Type For allowed card types refer to the iMAP Component Specification. Status Three parts: ADMIN STATE-OPERATIONAL STATE-Status. Only the ADMIN STATE can be controlled by the user. Refer to 5.5.24.
Card Management Creating a Card (Pre-provisioning) FIGURE 5-105 FIGURE 5-106 5-94 Create Card Window for ADSL Card Create Card Window for GE8 Card AlliedView NMS Administration Guide (Controlling and Provisioning Network Devices)
Creating a Card (Pre-provisioning) Card Management FIGURE 5-107 Create Card Window for SHDSL24 Card FIGURE 5-108 TABLE 5-14 Create Card Window for CES8 Card Create Card Details Field/Button Description Device The device name and the slot number for the card. Type The type of card that can be provisioned in the selected slot. Profile The profile used to provision the card.
Card Management TABLE 5-14 GE3 Card Create Card Details Field/Button Description Preferred Load For cards that have software loads, this is the software that will load when the card restarts. In normal operation this should be the same as the running load. For the GE1 card this field does not appear. Refer to 5.5.24. Create Creates the card in the provisioning data. The Card Management window will refresh and the card will come up in a state of UP-DOWN-NotInstalled.
GE8 Card TABLE 5-15 Card Management GE3 Card Details Field/Button Description Profile The template for provisioning data. The default is AutoProv. If the blank pull-down is chosen, there is no profile (manually provisioned). Modify Activated when the Profile is changed. Disable Disables the card. Active only when the Admin State is UP. Enable Enables the card. Active only when the Admin State is DOWN. Restart Reboots the card. For the GE1, there is no software load.
Card Management TABLE 5-16 ADSL24 (Annex B) and ADSL24AE ADSL Card Details Field/Button Description Device The device name and the slot number for the card (5-11 for the iMAP MAP n400, 0-7, 14-21 for the iMAP MAP n700 in duplex mode. Admin. State If UP, the ADSL is capable of providing service. If DOWN, can Run Diags. Oper. State The ADSL is providing service. This state is not controllable but depends on the Admin. State. Status The current state of the card.
CFC24 Card in Simplex and Duplex Card Management • Swap Activity - This button appears on the ACTIVE CFC24 window and, after confirmation by a prompt, swaps activity. Table 5-17 lists the fields/buttons available for the CFC24 details and highlights what is unique for the duplex CFC24. Note: For a description of what occurs during a Swap Activity of CFC24s and the conditions that would prevent this from occurring, refer to the iMAP Series User Guide.
Card Management CFC24 Card in Simplex and Duplex FIGURE 5-112 TABLE 5-17 CFC24 Card Details (Duplex) CFC24 Card Details Field/Button Description Device The device name and the slot number for the card (2,4 for the iMAP n400, 8-9, 12-13 for the iMAP n700 in duplex mode. Admin. State If UP, the CFC24 is capable of providing service. In Duplex mode both CFCs should be UP. If DOWN, can Schedule Diags. Oper. State The CFC24 is providing service.
CFC56, CFC100, and CFC200 Card TABLE 5-17 Card Management CFC24 Card Details (Continued) Field/Button Description Diags Schedule Whether the Schedule Diags. button has been used to schedule diagnostics on the active (simplex) or inactive (duplex) CFC24 card. Modify Activated when the Profile, Preferred Load, or Temporary Load is changed. Disable Disables the card. Active only when the Admin State is UP. In duplex, this cannot be done to the Active CFC24 card. Enable Enables the card.
Card Management FE10/FX10 Card FIGURE 5-113 TABLE 5-18 FE10/FX10 Card Details FE10/FX10 Card Details Field/Button Description Device The device name and the slot number for the card. Admin. State If UP, the FE10 is capable of providing service. If DOWN, can Run Diags. Oper. State The FE10 is providing service. This state is not controllable but depends on the Admin. State. Status The current state of the card.
FX20 Card TABLE 5-18 Card Management FE10/FX10 Card Details Field/Button Description Modify Activated when the Profile is changed. Disable Disables the card. Active only when the Admin State is UP. Enable Enables the card. Active only when the Admin State is DOWN. Restart Reboots the card. For the FE10, there is no software load. Run Diags Runs diagnostics. Active only when the Admin state is DOWN, so must Disable first. 5.5.
Card Management POTS24 Card FIGURE 5-114 FIGURE 5-115 5-104 Create POTS 24 Card Form Card Management - POTS24 - General Tab AlliedView NMS Administration Guide (Controlling and Provisioning Network Devices)
POTS24 Card Card Management 5.5.13.1 POTS24 Card - General Tab TABLE 5-19 POTS24 Card Details - General Tab Field/Button Description Device The device name and the slot number for the card. Admin. State If UP, the POTS24 is capable of providing service. If DOWN, can Run Diags. Oper. State The POTS24 is providing service. This state is not controllable but depends on the Admin. State. Status The current state of the card.
Card Management TABLE 5-20 POTS24 Card POTS24 Card Details - Protocols Tab for IP/RTP Field/Button Description Domain Name Optional domain name for the interface. RTP DSCP Settings The DSCP (Differentiated Services Code Point, RFC 2474) value for RTP packets transmitted from the POTS24 card. The default value is 46. VLAN P bits (0..7) The 802.1p priority bit setting for RTP packets transmitted from the POTS24 card. The default value is 6. Modify Activated when a value has been changed.
POTS24 Card Card Management 5.5.13.3 POTS24 Card - Protocols - MGCP Tab FIGURE 5-116 TABLE 5-21 POTS24 Card - Protocols/MGCP Tab POTS24 Card Details - Protocols Tab for MGCP Field/Button Description Profile The profile that has been applied to the card Call Agent (or None) The IP address of the network call agent that the card will communicate with.
Card Management TABLE 5-21 POTS24 Card POTS24 Card Details - Protocols Tab for MGCP (Continued) Field/Button Description Max. Retransmit Delay (100..4000 ms) Also known as RTO-MAX in RFC 3435, this is the maximum amount of time to wait for an acknowledgement from the call agent before retransmitting a packet. The default value is 4000 milliseconds. UDP Port Specifies the UDP (User Datagram Protocol) port the MGCP application in the POTS24 card will use for receiving packets.
POTS24 Card TABLE 5-22 Card Management POTS24 SIP Attributes - (Defaults are in Bold) POTS24 Card Attribute Description Profile The Profile that has been applied to the card Transport The Transport type of the outgoing messages. When set to UDP Accept TCP, the IP Phone will accept incoming TCP messages. (TCP) TCP Port The TCP port on which the Stack listens. (5060) UDP Port The UDP port on which the Stack listens (5060) Registrar (Host port) The Registrar IP address or domain name.
Card Management TABLE 5-22 POTS24 Card POTS24 SIP Attributes - (Defaults are in Bold) (Continued) POTS24 Card Attribute Description Call Forwarding Busy Sub-tab After CFW Busy has been activated, incoming calls are forwarded only if the endpoint is busy, i.e., all lines are active. ON-Prefix ON-Suffix OFF-Prefix Call Forwarding Busy Sub-tab After CFW No Reply has been activated, incoming calls are forwarded only if the endpoint does not answer before a pre-configured time-out.
CES8 Card TABLE 5-24 Card Management POTS24 Card Details - Statistics Tab for SIP Field/Button Description SIP Statistics Statistics supported for the SIP application running on the POTS24 card are defined in the ATN SNMP Enterprise MIB. Invites Received / Retransmitted: The total number of invite messages received and retransmitted. Non-Invites Received / Retransmitted: The total number of non-invite messages sent and retransmitted.
Card Management CES8 Card FIGURE 5-118 CES8 Card Details All the fields for the General tab are the same as for other cards except for the following: • Port Type - This can be DS1 (the default) or E1. Note that the card must be disabled before the Port Type can be changed. • Timing Ref. - The timing reference is where the card will get its clocking reference from.
NTE8 Card Card Management FIGURE 5-119 CES8 Card Details- Protocols Tab The Protocols tab is used to fill in the interface attributes of the DS1 card. The only required fields are the VLAN, IP Address, and Subnet mask values, and these must have valid entries or a Set Card Failed window appears. Note: An IP Interface is required before any DS1/E1 ports can be provisioned for CES. For details on these fields, refer to the iMAP User Guide.
Card Management ADSL24A, ADSL24B, and ADSL24E Card • Run Diags. - Runs a set of diagnostics. The card must be disabled first. If there are failures, there are messages and logs that can be accessed using the Log Manager. 5.5.16 ADSL24A, ADSL24B, and ADSL24E Card The ADSL24A can be deployed for Annex-A and Annex-B. The ADSL24AE card is available in iMAP release 14.0. Refer to the iMAP Component Specification for details on the card, and the Allied Telesis Feature Guide for details on provisioning.
GE24POE Note: Card Management For more information on provisioning the iMAP 9100, refer to the iMAP User Guide. 5.5.22 GE24POE The GE24POE card is unique to the SBx3112, and can be loaded in any slot in the SBx3112 chassis except for the CFC200 slots. Refer to 5.5.25. 5.5.23 Controlling Card Software (Download and Restart) The Card Details window includes a Download button that brings up the Download software window.
Card Management Overview of Provisioning Data, Profiles, and Card States Caution: For the devices that will receive downloads, do not set their telnet idle session time-out to any value less than 6 minutes. This minimum is needed to ensure the NMS is aware the download is complete and can proceed with any further steps. TABLE 5-25 Download Software Window Fields/Buttons Field/Button Description Available Loads This panel lists the loads available and their size.
Power Over Ethernet (POE) Management on SBx3112 Card Management In Manual Provisioning Mode, provisioning data must be explicitly created and modified. The data is persistent over reboots and restarts of the device and the removal of the card. It is important to note that insertion of a card when in the Manual Provisioning Mode does not create/provision the card in the database; this must be done using the Create Card button.
Card Management Power Over Ethernet (POE) Management on SBx3112 FIGURE 5-121 SBx3112 Pull-down for POE Management This will launch a separate NMS window that will show the overall power settings for the shelf. This window will show each POE card and how much power is allocated to it, requested by it, and the actual usage. In this way the customer can manage the power distribution across the cards. Refer to the following figure.
XE Cards (XE1, XE1S, XE4, XE6SFP, and XE6) FIGURE 5-123 Port Management (iMAP Devices) Power Over Ethernet Management Form - Ports 5.5.26 XE Cards (XE1, XE1S, XE4, XE6SFP, and XE6) The XE1 card on the iMAP provides a 10GE link between 10G products. The XE4 and XE6SFP cards, unique to the SBx3112, provides four and six of these ports. The XE6 card, used in the iMAP 9700 and 9810 products, provides six of these ports. All have a general tab and allow for Enable, Disable, Restart, and Run Diags.
Port Management (iMAP Devices) Accessing the Port Management Application • Close - This closes the Application. • Help - This brings up the context-sensitive help file. For complete information about port management and statistics, refer to the iMAP User Guide. 5.6.2 Accessing the Port Management Application To access the Port Management application, right-click the device, and then select Provision -> Port Management. (You can also select the device.
Accessing the Port Management Application FIGURE 5-124 TABLE 5-26 Port Management (iMAP Devices) Port Management Form (here for iMAP 9700) Port Management Application Window Field/Button Description Device Name The Name given to the device in the Managed Objects property table Port The slot.
Port Management (iMAP Devices) TABLE 5-26 Port Management Application Window (Continued) Field/Button Description Description An ID that can be given to uniquely identify the port. In most cases, the subscriber’s telephone number is used. For rules on DS1/E1 customer IDs, refer to 6.16.
Provision New Customer/Port (Triple Play Form) - with Preferences Port Management (iMAP Devices) 5.6.3 Provision New Customer/Port (Triple Play Form) - with Preferences 5.6.3.1 Overview Selecting a non-provisioned port that is not an xDSL/CES8/NTE8/EPON port and then clicking Provision New Customer/ Port invokes the Provision New Triple Play Customer form, as shown in Figure 5-125. This form includes the most important attributes for the port to ensure quality subscriber service.
Port Management (iMAP Devices) TABLE 5-27 Provision New Customer/Port (Triple Play Form) - with Pref- Provision Port for Triple Play Customer Form Panel Field/Button Description RG General Configuration RG General Profile A pull-down with the pre-defined general profiles for the RG. When provisioning the RG the user should have already defined all the RG profile types. Refer to 7.4.2. RG MAC Address The MAC address that uniquely identifies the RG device.
Provision New Customer/Port (Triple Play Form) - with Preferences TABLE 5-27 Port Management (iMAP Devices) Provision Port for Triple Play Customer Form Panel Field/Button Description Voice Configuration POTS: The attributes that support iMAP Devices that have ports that can support the POTS aspect of triple play. Specific attributes are controlled by the POTS Port Profile selected. Derived Voice The attributes for Voice over IP provided by iMG/RGs.
Port Management (iMAP Devices) Provision New Customer/Port (Triple Play Form) - with Pref- 5.6.3.3 Guided Input As shown in Figure 5-125, fields that require datafill are highlighted to help the user fill out the applicable fields. The highlighted fields work as follows: • Fields that require datafill are highlighted. • When more than one field is highlighted, at least one of these fields require datafill. • After one field is filled in, any fields that still require input are highlighted.
Provision New Customer/Port (Triple Play Form) - with Preferences FIGURE 5-126 Port Management (iMAP Devices) Triple Play for ADSL Bonded Ports The display of these fields is controlled by new Preference entries, Bonded ADSL Ports, and Additional POTS Port when Bonded. Selecting a Blank profile entry enables the Bonded Port field, but makes it not required. Selecting a blank bonded port removes any extra POTS line fields that are visible. Refer to the following figure.
Port Management (iMAP Devices) Provision New Customer Port for Ethernet 5.6.4 Provision New Customer Port for Ethernet For an ethernet port, a form allows the user to provision a Customer ID and apply a profile so that the port can be placed in service. Refer to the following figure. FIGURE 5-128 Provision New Ether-Like Port 5.6.5 Provision New Customer/Port for ADSL Selecting a non-provisioned ADSL port brings up the Triple Play Form that already includes the Access Device and selected port.
Provision New Customer/Port for CES8 (DS1/E1 Form) Port Management (iMAP Devices) 5.6.6 Provision New Customer/Port for CES8 (DS1/E1 Form) Selecting a non-provisioned port that is a DS1/E1 port and then clicking Provision New Customer/Port invokes the Provision New DS1/E1 Customer form, as shown in Figure 5-129. This form includes the most important attributes for the port to ensure quality subscriber service. Table 5-28 lists these attributes.
Port Management (iMAP Devices) TABLE 5-28 Provision New Customer/Port for CES8 (DS1/E1 Form) Provision Port for DS1/E1Form Panel Field/Button Description Port Configuration Device A drop-down of all the devices that have CES8 cards configured as DS1 ports (or, if the port is an E1, all the devices that have CES8 cards configured as E1 ports). Ports A drop-down of the ports (card.slot) in the selected device that are DS1 or E1, depending on the port type being configured.
Provision New Customer/Port for NTE8 (DS1/E1 Form) Port Management (iMAP Devices) 5.6.7 Provision New Customer/Port for NTE8 (DS1/E1 Form) Selecting a non-provisioned port that is a DS1/E1 port and then clicking Provision New Customer/Port invokes the Provision New NTE-DS1 Port form, as shown in Figure 5-129. This form includes the most important attributes for the port to ensure quality subscriber service. Table 5-29 lists these attributes.
Port Management (iMAP Devices) TABLE 5-29 Provision New Customer/Port for NTE8 (DS1/E1 Form) Provision Port for NTE8-DS1/E1Form Panel Field/Button Description Port Profile The available profiles for the port type (DS1 or E1) appear in the drop-down list. When the port is provisioned, it will inherit the attributes of that profile. MLPPP Instance The MLPPP that the DS1/E1 will be associated with.
Provision New Customer / Port for SHDSL16/24 TABLE 5-29 Port Management (iMAP Devices) Provision Port for NTE8-DS1/E1Form Panel Bottom of Form Field/Button Description Timing Reference Where the port will get its clocking reference from. Provision Enabled only after the minimum number of correct fields have been data filled, and these fields have been data filled with valid values. 5.6.
Port Management (iMAP Devices) Provision New Customer / Port for EPON2 FIGURE 5-132 Provision EPON Port To provision on EPON port, the user should select a port that has a status of Unknown with no Customer ID and then select the activated Provision New Customer Port button. Warning: If the user tries to provision a port with configured ONUs, the ONU configurations are destroyed, as shown in the following figure.
Provision New Customer / Port for EPON2 FIGURE 5-133 Port Management (iMAP Devices) Trying to Provision an EPON with Configured ONUs FIGURE 5-134 Provision New EPON Port AlliedView NMS Administration Guide (Controlling and Provisioning Network Devices) 5-135
Port Management (iMAP Devices) Provision New Customer / Port for ONU 5.6.10 Provision New Customer / Port for ONU The ONU is part of the configuration that includes the EPON2 card (for passive optical network) and the Optical Networking Unit (ONU). Note: For complete information about the EPON2 card, ONU, QoS policies being associated with VLANs, etc. refer to the iMAP User Guide.
Provision New Customer / Port for VDSL24A/B FIGURE 5-136 Port Management (iMAP Devices) Triple Play Form for an ONU Customer Port Note the following attributes of the Triple Play Form when provisioning an ONU: • The Slot.Port has three digits for the ONU. • The MAC address that has been assigned to the ONU is displayed. Note: If the administrator is provisioning an iMG646PX-ON, the iMG/RG General Configuration Panel would be filled in, as shown in Section 7. 5.6.
Port Management (iMAP Devices) Provision New Customer / Port for VDSL24A/B FIGURE 5-137 Provision VDSL Port Note the following on filling out the Triple-Play form for VDSL: • The pull-down for the iMG/RG General configuration is left blank. • The Voice Configuration panel is left blank.
Overview of Triple Play Service Management Form Port Management (iMAP Devices) 5.6.12 Overview of Triple Play Service Management Form Once a port is configured for video, data, or voice, the Triple Play Service Management Form is used to view or modify the port’s attributes. Depending on the type of port configured and the services configured on that port, this management form displays the various attributes in a hierarchical multi-tab format.
Port Management (iMAP Devices) FIGURE 5-138 5-140 Status Tab Example Status Form (POTS24 and Derived Voice using GenBand) AlliedView NMS Administration Guide (Controlling and Provisioning Network Devices)
Add Derived Voice Line for GenBand (on Status Tab Form) Port Management (iMAP Devices) 5.6.14 Add Derived Voice Line for GenBand (on Status Tab Form) When the GenBand configuration is being used, the administrator can add a voice line immediately on the Status form by clicking the Add Derived Voice Line button.
Port Management (iMAP Devices) FIGURE 5-140 iMG/RG Tab Add Voice Line Form (more than one MGC Device Configured) Note: This form is only used when the GenBand is providing the derived voice. Note: The NMS does not support GenBand provisioning with TR-008. 5.6.15 iMG/RG Tab This form lists all the major attributes of the iMG/RG and its services, and includes the attributes that were filled out as part of the iMG/RG Profiles. Refer to Section 7 for details about provisioning the iMG/RG.
iMG/RG Tab Port Management (iMAP Devices) 5.6.15.4 IP Routes Tab This form shows the IP Route assignments that were data filled in the associated RG General Profile (IP Routes tab). The user selects a route in the New IP Routes Panel, selects or deselects the Enable tic box, and then selects the different attributes from the pull-downs. Note: The user should not change individual fields since they would no longer match those of the associated General Profile. 5.6.15.
Port Management (iMAP Devices) Ether-like Config. Tab (Upstream and Downstream) 5.6.16 Ether-like Config. Tab (Upstream and Downstream) Following are the types of ether-like ports that can be provisioined. • • • • • • • • • • See “Ether-Like Port (General Tab)” on page 144. See “Ether-Like Port (General Tab) - iMG/RG” on page 146. See “Ether-Like Port (Port Statistics Tab)” on page 146. See “Ether-Like Port (Port Thresholds Tab)” on page 147.
Ether-like Config. Tab (Upstream and Downstream) TABLE 5-30 Port Management (iMAP Devices) Ether-like Port Management for iMAP Devices - General Tab - Upstream Field/Button Description Admin. State/Status: The Administrative State can be controlled and determines the Operational State. Refer to 5.5.24. Oper. State/Link State: The ability of the port to provide service. The Administrative State must be up and then the system determines if the port can provide service.
Port Management (iMAP Devices) Ether-like Config. Tab (Upstream and Downstream) 5.6.16.2 Ether-Like Port (General Tab) - iMG/RG When the Ethernet port interfaces with an iMG/RG, there are additional fields that appear. Refer to the following figure. FIGURE 5-142 Ether like Port Management Window - iMG/RG Many of the values for the RG-specific fields are controlled by the Profile being used. These are explained in 7.4.
Ether-like Config. Tab (Upstream and Downstream) FIGURE 5-143 TABLE 5-31 Port Management (iMAP Devices) Ether like Port Management Window - Port Statistics Tab Provision Port Form for Port Management - Port Statistics Tab Field/Button Description RMON Statistics: Lists the standard RMON statistics. For an explanation, refer to the iMAP User Guide. Interface Statistics: Lists the standard faults for an ethernet port.
Port Management (iMAP Devices) FIGURE 5-144 TABLE 5-32 Ether-like Config. Tab (Upstream and Downstream) Ether like Port Management Window - Port Thresholds Tab Provision Port Form for Port Management - Port Thresholds Tab Field/Button Description Name One of the RMON statistics Interval Interval in number of seconds, from 2 to 3600 (one hour) Rising Threshold The number at which an alarm/log is raised when the number is exceeded.
Ether-like Config. Tab (Upstream and Downstream) FIGURE 5-145 TABLE 5-33 Port Management (iMAP Devices) Ether like Port Management Window - Device Data Collection Tab Provision Port Form for Port Management - Device Data Collection Tab Field/Button Description Interval The period of time in seconds statistics will be gathered for a bucket, from 2 to 3600 (one hour) Buckets Requested The number of buckets that will be filled before the first bucket is overwritten, from 1 to 2700.
Port Management (iMAP Devices) FIGURE 5-146 TABLE 5-34 Ether-like Config.
Ether-like Config. Tab (Upstream and Downstream) Port Management (iMAP Devices) 5.6.16.7 Ether-Like Port (IP Filters Tab) For traffic management, the iMAP devices allow the user to control a set of filters on ports, with each classifier given a rank or precedence (the lower the number, the higher the precedence). This form allows the user to list the classifiers that have already been defined and to control the precedence. Refer to the following figure and table.
Port Management (iMAP Devices) ADSL Configuration Tab 5.6.16.8 Ether-Like Port (Port Log Tab) Selecting the Port Log tab invokes a table that lists all the port-related management logs that have been generated. This window has the same columns as the ADSL Port Management window for Port Log. For a description of management logs and the meaning of fields, refer to the iMAP Log / Troubleshooting Manual. 5.6.16.9 Ether-Like Port (DS3-SFP Tab) Starting in release 12.
ADSL Configuration Tab Port Management (iMAP Devices) FIGURE 5-149 ADSL Configuration Form - Status Tab For a data-only port using ADSL (no POTS or Derived Voice configuration), only the Video/Data Port panel has status information on the state of the port. Included is Alerts Panel that lists the current associated alarms. If the ADSL port is part of a Bond configuration, the Port details tab is expanded to show the Bond status, as well as status of all the ADSL ports.
Port Management (iMAP Devices) ADSL Configuration Tab FIGURE 5-150 ADSL Status - Bonded Port 5.6.17.2 ADSL Configuration Tab - Overview The ADSL Configuration tab has the following associated forms, each with its own tab: • • • • • • • • • General VCs/VLANs Video DHCP FDB PMON Thresholds RMON Thresholds Device Data Coll. IP Filters These are shown in the following figures. Following each figure is a table that describes the panels/fields of the form.
ADSL Configuration Tab Port Management (iMAP Devices) 5.6.17.3 ADSL Configuration Tab - General FIGURE 5-151 TABLE 5-36 ADSL Configuration Form - General Tab ADSL Configuration Form, General Tab Field/Button Description Admin. State The Administrative State can be controlled and determines the Operational State. Refer to 5.5.24. Oper. State/Link State The ability of the port to provide service. The Administrative State must be up and then the system determines if the port can provide service.
Port Management (iMAP Devices) TABLE 5-36 ADSL Configuration Tab ADSL Configuration Form, General Tab (Continued) Field/Button Description Connection State The connection state, such as Idle or Showtime Actual Line Std. The line standard that was actually chosen. Actual Databoost Whether the DATABOOST feature has been implemented Actual Line Type The line type that was actually chosen. Actual Upstream/Downstream Rate The upstream/downstream rate that was actually attained. Max.
ADSL Configuration Tab TABLE 5-36 Port Management (iMAP Devices) ADSL Configuration Form, General Tab (Continued) Field/Button Description Power Mgmt Trim The maximum aggregate transmit power reduction (trimming) that can be performed with each power trim operation in the Low Power state. Power Mgmt Trim Delay The amount of time that must elapse before an additional reduction (trimming) of power occurs in the Low Power state.
Port Management (iMAP Devices) FIGURE 5-152 ADSL Configuration Tab ADSL General Tab with ATM Bond Attributes Each ADSL port has it's own general tab and rates tab. The values for the Profile name and Customer ID are from the Triple_play provisioning form (refer to TBS). Some fields that appear on a regular ADSL port's general tab are moved to the ATMBOND tab since they are tied to the Bond rather than the port.
ADSL Configuration Tab Port Management (iMAP Devices) Refer to the following figu FIGURE 5-153 FIGURE 5-154 ADSL General Tab with ATM Bond - Single Port Attributes ADSL General Tab with ATM Bond - Single Port Rate Attributes AlliedView NMS Administration Guide (Controlling and Provisioning Network Devices) 5-159
Port Management (iMAP Devices) ADSL Configuration Tab 5.6.17.4 ADSL Configuration Tab - VCs/VLANs The ability to correlate the port to Virtual Channels (VCs) and then the VC to one or more VLANs is configured through this tab. Note: The ADSL16 and ADSL8S cards allow up to four VCs to be configured per port, while the ADSL24 card allows only one VC per port. The ADSL24A/B card supports 4 VCs. Figure 5-160 shows the ADSL statistics once they have been enabled.
ADSL Configuration Tab Port Management (iMAP Devices) 5.6.17.5 ADSL Video Tab Refer to 5.6.30. 5.6.17.6 ADSL Configuration Tab - DHCP Tab Refer to 5.6.28. 5.6.17.7 ADSL Configuration Tab - FDB Tab Refer to 5.6.29. 5.6.17.8 ADSL Configuration Tab - PMON Thresholds Tab Selecting the PMON Thresholds tab brings up a form (Figure 5-156) that allows thresholds to be set for the ATU-C and ATU-R statistics.
Port Management (iMAP Devices) FIGURE 5-157 ADSL Configuration Tab ADSL Bonding - PMON Thresholds 5.6.17.9 ADSL Configuration Tab - Device Data Collection Tab The Device Data Collection form is a way to configure buckets that will collect statistics and the interval at which they are filled.
ADSL Configuration Tab Port Management (iMAP Devices) FIGURE 5-158 ADSL Configuration Form - Device Data Coll. Tab The Add History brings up a form that allows the user to enter the number of buckets to be configured and at what interval (in seconds). 5.6.17.10 ADSL Configuration Tab - IP Filters Incoming data to the ADSL ports (the ingress ports) can be filtered by IP address or a range of IP addresses. Figure 5-159 shows the IP Filters tab, while Table 5-38 shows the buttons and fields available.
Port Management (iMAP Devices) FIGURE 5-159 5-164 ADSL Configuration Tab ADSL Configuration Form - IP Filters Tab AlliedView NMS Administration Guide (Controlling and Provisioning Network Devices)
ADSL Configuration Tab TABLE 5-38 Port Management (iMAP Devices) IP Filters Form Field/Button Description Port IP Filters Rank - Also called precedence, it is the rank a precedence a classifier has in a port. The highest rank is 1, and then in descending order. IP Filtering should have a precedence of 51-69. Classifier Name - This is the name given to the grouping of IP addresses or range of addresses. Field Match(es) - The range of IPSOURCE addresses is specified as a subnet and a mask.
Port Management (iMAP Devices) FIGURE 5-160 ADSL Configuration Tab ADSL Statistics Form - PMON Stats Tab The ATU-C and ATU-R statistics have the following measurements: • • • • • Valid Intervals Invalid Intervals Previous Day Monitored Seconds Current 15 min. Time Elapsed Current 1 Day Time Elapsed The table for each statistic type gives the count for the periods.
ADSL Configuration Tab Port Management (iMAP Devices) FIGURE 5-161 PMON Stats - ADSL Bonding 5.6.17.13 ADSL Statistics Tab - RMON Stats RMON Statistics deal with packet flows and highlight errors as well as overflows of packets. The QOS Statistics are counters for each priority queue that allow the user to see the ratio of sent versus dropped packets. These are cumulative and so produce no management logs. These counters can be reset to 0 by selecting Reset QOS Statistics.
Port Management (iMAP Devices) FIGURE 5-162 TABLE 5-39 ADSL Configuration Tab ADSL Statistics Form - RMON Stats Tab View Details Form, RMON Stats Tab Field/Button Description Interface Statistics Counts of input and output octets as well as errored input and output packets. RMON Statistics RMON error statistics QOS Statistics Shows the number of packets sent and dropped for each queue.
ADSL Configuration Tab TABLE 5-39 Port Management (iMAP Devices) View Details Form, RMON Stats Tab (Continued) Field/Button Description Reset RMON Statistics Resets the RMON statistics to 0. Reset QOS Statistics Resets the QOS statistics to 0. 5.6.17.14 ADSL Statistics Tab - Graph Stats Once the statistics have been enabled, they can be graphed both in real-time and for statistics that have been collected.
Port Management (iMAP Devices) TABLE 5-40 SHDSL Port Management Form ADSL Statistics Form - Graph Stats Tab (Continued) Field/Button Description New Interval This is used when changing the polling interval. When a new one is entered, the Reset Polling Interval Button is enabled, to allow the interval to be changed.
SHDSL Port Management Form Port Management (iMAP Devices) 5.6.18.1 SHDSL Port (Status Tab) This tab is essentially the same as the ADSL Status tab, with the Video/Data Port, Voice, and Alerts panels. Since SHDSL is a high-speed data application, only the Voice/Data Port panel has information. 5.6.18.2 SHDSL Configuration Tab - Overview The SHDSL Configuration tab has the following forms: • • • • • • • • General VCs/VLANs Video DHCP FDB PMON Thresholds Device Data Collection IP Filters 5.6.18.
Port Management (iMAP Devices) FIGURE 5-166 TABLE 5-41 SHDSL Port Management Form SHDSL Configuration Tab - General - Bonded SHDSL Configuration Tab - General Field/Button Description WireMode Whether the port is 2-wire (Normal) or 4-wire (Bonded) Admin. State/Status The Administrative State can be controlled and determines the Operational State. Refer to 5.5.24. For a bonded pair, the Admin State determines the Oper. State of both wire pairs. Oper.
SHDSL Port Management Form TABLE 5-41 Port Management (iMAP Devices) SHDSL Configuration Tab - General Field/Button Description Actual Receiver Gain Receiver Gain in db. Actual SNR (STU-C, STU-R) The signal-noise ratios that were actually attained. Actual Attenuation (STU-C, STU-R) The attenutation that was actually attained.
Port Management (iMAP Devices) Voice Port Management (Tabbed Form) 5.6.18.6 SHDSL Configuration Tab - DHCP Tab Refer to 5.6.28. 5.6.18.7 SHDSL Configuration Tab - FDB Tab Refer to 5.6.29. 5.6.18.8 SHDSL Configuration Tab - PMON Thresholds This form shows (any) threshold values for the STU-C/R statistics. Note: The thresholds are set for both the STU-C and STU-R at the same time and cannot be set separately. 5.6.18.
Voice Port Management (Tabbed Form) FIGURE 5-167 Port Management (iMAP Devices) POTS24 Configuration Tab - Status AlliedView NMS Administration Guide (Controlling and Provisioning Network Devices) 5-175
Port Management (iMAP Devices) Voice Port Management (Tabbed Form) 5.6.19.3 POTS24 Voice Configuration Tab - POTS Each port on the POTS24 provides an analog interface to a physical customer loop. Configurable attributes for each line interface specify the capabilities of the line that affect analog waveform transmission and packetization of the analog waveform. Differences between the SIP versus MGCP protocol parameters are noted in the table below.
Voice Port Management (Tabbed Form) TABLE 5-42 Port Management (iMAP Devices) POTS24 Voice Configuration Tab - POTS Field/Button Description Status: The status of the port that follows form the Administrative State and Operational State. For meanings, refer to the iMAP User Guide, Section 4.
Port Management (iMAP Devices) TABLE 5-42 Voice Port Management (Tabbed Form) POTS24 Voice Configuration Tab - POTS Field/Button Description Modem Jitter Buffer Delay Used with jitter buffering, this is the amount of time that the first packet is delayed. Note: The default in release 8.0 was changed from 30ms to 10ms Packet Loss Concealment: Specifies whether Packet Loss Concealment is enabled.
Voice Port Management (Tabbed Form) FIGURE 5-169 TABLE 5-43 Port Management (iMAP Devices) POTS24 Statistics Tab - Graphs Stats POTS24 Statistics Tab - Graphs Stats Field/Button Description Hidden Statistics: Statistics not added to the resulting graph View Statistic: Enabled when a statistic is chosen form Hidden Statistics, clicking this button adds it to the graph/ Hide Statistic: Enabled when a statistic is chosen form Graphed Statistics, clicking this button deletes it from the graph/ Dis
Port Management (iMAP Devices) Voice Port Management (Tabbed Form) 5.6.19.6 POTS24 Diagnostics Tab - POTS This form allows the user to run a set of diagnostics on the port interface. Refer to the following figure and table. In iMAP release 12.
Voice Port Management (Tabbed Form) Port Management (iMAP Devices) A panel across the top on the Diagnostics tab shows port state information that applies to both Test Tone and Diagnostics functionality. FIGURE 5-170 POTS24 Diagnostics Tab - Port Status New rows have been added to the Diagnostics Results table to display the Capacitance test results and details/values.
Port Management (iMAP Devices) Voice Port Management (Tabbed Form) A new panel has been added specifically for handling Test Tone information FIGURE 5-172 POTS24 Diagnostics Tab - Test Tone Information The button Modify Test Tone is used when modifying the Test Tone information. Note that when turing the Test Tone status to On and making changes to the Time-out, there is a warning about service. Refer to the following figure.
CES8 Port (DS1/E1 Port Management Tabbed Form) TABLE 5-44 Port Management (iMAP Devices) POTS24 Diagnostics Tab - POTS Field/Button Description Diagnostic Results Refer to the iMAP User Guide for an explanation of these test functions. Diagnostic: Result For each test, there is a Result field that says PASS or FAIL and a Details field that gives the specific test result. Modify Test Tone For making changes to Test Tone settings. When changing state to ON, there is a service warning.
Port Management (iMAP Devices) CES8 Port (DS1/E1 Port Management Tabbed Form) 5.6.20.1 DS1/E1 Port Tab FIGURE 5-175 TABLE 5-45 CES DS1 Port Tab (For E1, Label and Type are E1) CES DS1 Port Management - DS1 Port Tab Field/Button Description Device: / Port: Non-editable, this is the port (or ports) that are being displayed. Admin. State/Status: Administrative State of the port. This depends on the state of the associated card. Oper. State/Link Status Operational State of the port.
CES8 Port (DS1/E1 Port Management Tabbed Form) TABLE 5-45 Port Management (iMAP Devices) CES DS1 Port Management - DS1 Port Tab Field/Button Description Framing Always Unframed, since that is the only type of CES currently supported. Direction Whether the DS1 interfaces a customer or the network. Loop Back: Whether to set the port for loopback, and if so either LINE or INWARD (This is normally done before putting the port in service.
Port Management (iMAP Devices) CES8 Port (DS1/E1 Port Management Tabbed Form) FIGURE 5-176 TABLE 5-46 CES PSPAN Tab CES DS1 Port Management - PSPAN Tab Field/Button Description PSPAN ID: This ID is the format vlan:subinterface:pspanid. Note that the subinterface and pspanid are provided by the AlliedView NMS as part of CES provisioning. Admin. State/Status: Administrative State of the PSPAN. This depends on the state of the associated port. Oper.
CES8 Port (DS1/E1 Port Management Tabbed Form) TABLE 5-46 Port Management (iMAP Devices) CES DS1 Port Management - PSPAN Tab Field/Button Description UDP Port: The UDP port for this end of the connection. This must be unique within an IP address on a card Peer UDP Port: The UDP at the other end of the connection. Bytes per Packet: The default is 193 for DS1, 256 for E1. Note: Refer to 6.16 on how this is controlled in a dual configuration. Jitter Buffer Size: The size of the jitter buffer.
Port Management (iMAP Devices) CES8 Port (DS1/E1 Port Management Tabbed Form) 5.6.20.
CES8 Port (DS1/E1 Port Management Tabbed Form) TABLE 5-47 Port Management (iMAP Devices) CES DS1 Port Management - Stats Graph Tab Field/Button Description Display The attribute that controls the display: - Absolute Values - Rate Per Second - Million Per Second Polling Interval: The Current Polling Interval in seconds New Interval: Sets a new interval for polling. This is set with the Reset Polling Interval button.
Port Management (iMAP Devices) FIGURE 5-180 NTE8 Port Management Form CES DS1 Port Management - Port Log Tab 5.6.21 NTE8 Port Management Form The DS1/E1 Port Management Form for the NTE8 provides all the relevant information for both single and dual NTE8 endpoints; when the port is part of a dual endpoint configuration, the port dynamically changes so that both endpoints appear in the form. Note: 5-190 Refer to 6.17 for a walk-through of provisioning the near and far ends of an NTE8.
NTE8 Port Management Form Port Management (iMAP Devices) 5.6.21.1 DS1/E1 Port Tab FIGURE 5-181 TABLE 5-48 NTE DS1 Port Management Form - DS1/E1 Tab NTE DS1 Port Management - DS1 Port Tab Field/Button Description Device: / Port: Non-editable, this is the port (or ports) that are being displayed. Admin. State/Status: Administrative State of the port. This depends on the state of the associated card. Oper. State/Link Status Operational State of the port.
Port Management (iMAP Devices) TABLE 5-48 NTE8 Port Management Form NTE DS1 Port Management - DS1 Port Tab Field/Button Description Loop Back Status The DS1/E1 port is considered operationally DOWN when a loopback is configured, because no “thru service” can be provided.
NTE8 Port Management Form Port Management (iMAP Devices) 5.6.21.2 PPP Tab FIGURE 5-182 NTE DS1 Port Management Form - PPP Tab (Linked Connection) For information on the parameters, refer to the iMAP User Guide. 5.6.21.3 Eth Interface Tab This form has two sub-tabs, General and IpFilters.
Port Management (iMAP Devices) FIGURE 5-183 NTE8 Port Management Form NTE DS1 Port Management Form - Eth Interface Tab (General) For information on the parameters, refer to the iMAP User Guide.
NTE8 Port Management Form FIGURE 5-184 TABLE 5-49 Port Management (iMAP Devices) NTE DS1 Port Management Form - Eth Interface Tab (IpFIlters) NTE DS1 Port Management - Eth Interface - IP Filters Tab Field/Button Description Allowed Addresses Other Classifiers Port IP Filter Counters For the Eth interface the traffic management counters: - Match - Number of packets that match any of the criteria - Filter - Number of packets dropped because they do not match any of the criteria - Policed - Number of
Port Management (iMAP Devices) FIGURE 5-185 NTE8 Port Management Form NTE DS1 Port Management Form - PMON Statistics Tab • Enable Statistics - Activates all the statistics • Disable Statistics - Deactivates all the statistics • Reset Statistics - Sets all the statistics to 0 5-196 AlliedView NMS Administration Guide (Controlling and Provisioning Network Devices)
NTE8 Port Management Form Port Management (iMAP Devices) 5.6.21.5 Stats Graph tab FIGURE 5-186 TABLE 5-50 NTE DS1 Port Management Form - Stats Graph Tab NTE DS1 Port Management - Stats Graph Tab Field/Button Description Hidden Statistics: Statistics not added to the resulting graph View Statistic: Enabled when a statistic is chosen form Hidden Statistics, clicking this button adds it to the Graphed Statistics (Maximum of 6), which is the current list of statistics being graphed.
Port Management (iMAP Devices) TABLE 5-50 NTE8 Port Management Form NTE DS1 Port Management - Stats Graph Tab Field/Button Description Display The attribute that controls the display: - Absolute Values - Rate Per Second - Million Per Second Polling Interval: The Current Polling Interval in seconds New Interval: Sets a new interval for polling. This is set with the Reset Polling Interval button.
NTE8 Port Management Form FIGURE 5-187 Port Management (iMAP Devices) NTE DS1 Port Management Form - Stats Graph Tab 5.6.21.7 DS1 Port Management - Port Log Tab This form lists the PORT logs associated with the port(s) and can therefore provide a history of provisioning as well as any errors or problems. Refer to the following figure.
Port Management (iMAP Devices) FIGURE 5-188 SHDSL Bonding (Card Level to Port Level) NTE DS1 Port Management - Port Log Tab 5.6.22 SHDSL Bonding (Card Level to Port Level) In prior releases the SHDLS WireMode was set in the Card Management application, as shown in 5.5.8. This support will remain for iMAP systems running earlier software version. However, when both of these conditions are true: • iMAP systems are running release 7.
SHDSL Bonding (Card Level to Port Level) FIGURE 5-189 Port Management (iMAP Devices) SHDSL Configuration - General Tab with Bonded Option AlliedView NMS Administration Guide (Controlling and Provisioning Network Devices) 5-201
Port Management (iMAP Devices) FIGURE 5-190 View the EPON2 Port Configuration Triple Play Form for SHDSL with Bonding Option Using the Triple Play form, individual even numbered ports can be bonded to the next higher odd port. Therefore, when the user selects an even numbered port, the “Bond To:” selector is enabled. Either the next port, or a blank entry, can be selected. Provisioning will set the wire mode appropriately.
View the EPON2 Port Configuration FIGURE 5-191 Port Management (iMAP Devices) EPON Port Management - Tabbed Form TABLE 5-51 EPON Port Management - General Tab Field/Button Description Admin. State/Status Whether the EPON2 can go into service and therefore pass traffic Oper. State/Link State When the Admin State is up, whether the link is passing traffic Availability Status Dependency, meaning the state of the upstream component determines this component’s status.
Port Management (iMAP Devices) ONU Configuration (as ON1000 or as part of iMG646PX-ON) TABLE 5-51 EPON Port Management - General Tab Field/Button Description BRUUM Policy This policy is for the same VID as the downstream-only video stream, but it applies to all upstream traffic from that ONU, and known/learned unicast downstream traffic to that ONU. The ONU/VLAN association and corresponding SLA must be provisioned if unicast or broadcast traffic is required for operation (e.g.
VDSL24 Port Port Management (iMAP Devices) The user can see the VLAN id and QoS Policy as highlighted in the figure. The default QoS policy is named “NONE” and can be associated with one or more VLANs. The user has the option of selecting one of the VLANs as the untagged VLAN, and so the selection uses a radio button. Note: Refer to 6.11.11 for details on policies for the EPON/ONU. Note: Refer to Section 7 for complete information on provisioning the iMG/RG.
Port Management (iMAP Devices) FIGURE 5-193 TABLE 5-52 VDSL24 Port VDSL Configuration - General Tab VDSL Configuration Form, General Tab Field/Button Description Admin. State/Status The Administrative State can be controlled and determines the Operational State. Refer to 5.5.24. Oper. State/Link State The ability of the port to provide service. The Administrative State must be up and then the system determines if the port can provide service.
VDSL24 Port TABLE 5-52 Port Management (iMAP Devices) VDSL Configuration Form, General Tab (Continued) Field/Button Description Status The status of the port that follows form the Administrative State and Operational State. For meanings, refer to the iMAP User Guide, Section 4. - ONLINE - IN TEST - FAILED - OFFLINE - DEPENDENCY - DEGRADED - NOT INSTALLED - INITIALIZATION REQUIRED - TERMINATING Connection State The connection state, such as Idle or Showtime Actual Line Std.
Port Management (iMAP Devices) TABLE 5-52 VDSL24 Port VDSL Configuration Form, General Tab (Continued) Field/Button Description RFI Bands Specifies the radio frequency interference bands to filter from the VDSL link. To avoid interference it is necessary to introduce power control (notching) in one or more of these bands. Transport Protocol Used to specify the type of transport used when operating in VDSL mode.
VDSL24 Port TABLE 5-53 Port Management (iMAP Devices) VDSL Configuration Form, Rate Settings Tab (Continued) Field/Button Description Actual Upstream/Downstream INP The actual impulse noise protection value for upstream Max. Upstream Rate Specifies the maximum upstream bit rate to attain for a VDSL port. The valid range for this parameter is from 32Kb to 14848. Leaving this rate to the default of 10000 (10Mbps) ensures the higher downstream rates (50 Mbps) for VDSL Min.
Port Management (iMAP Devices) Statistics Tab 5.6.25.2 VDSL Configuration - VCs/VLANs Tab This screen is determined by the mode of the port. If the port is in VDSL mode and using ATM, there is only a VPI/VCI of 0/ 35 that cannot be changed. If the port is in VDSL mode and using PTM, there is no VCI, only a data channel. In ADSL mode, the VPI/VCI follow the ADSL configuration (up to four VPI/VCI). VDSL Configuration - Other Tabs The remaining tabs follow the same concepts as the ADSL configuration.
Statistics Tab Port Management (iMAP Devices) The table for each statistic type gives the count for the periods. The Fault Statistics are counters, which are part of the ATN Enterprise MIB, that help to monitor the ADSL port by incrementing continuously until reset. By doing this, the history of certain events can be shown over time in order to obtain a more accurate view of what is happening with the ADSL port.
Port Management (iMAP Devices) Statistics Tab 5.6.26.
Port Log Tab TABLE 5-54 Port Management (iMAP Devices) Stats Graph Tab Field/Button Description Add Historical Data from NMS: Adds the data collected previously from NMS port management Add Historical Data from Device: Adds the data collected previously (buckets) from the device 5.6.27 Port Log Tab Selecting the Port Log tab invokes a table that lists all the port-related management logs that have been generated. Refer to previous sections on the port log tab. (5.6.17.15, 5.6.19.
Port Management (iMAP Devices) Video Tab FIGURE 5-197 TABLE 5-55 Video Tab Video Tab Field/Button Description System-wide Information These are the IGMP attributes that have been set for the device. Card information The attributes for the ADSL/VDSL card, such as the multicast Group Limit Port IGMP Statistics The good vs.
Video Tab TABLE 5-55 Port Management (iMAP Devices) Video Tab (Continued) Field/Button Description Learned STB Multicast Info VID - The multicast VLAN MAC - The STB MAC Addresses that were learned and are in the FDB IP - The IP addresses being used for the multicast traffic Note: These three attributes are placed in a table to allow the user to see the association between a VLAN ID, MAC address, and its associated IP addresses.
Port Management (iMAP Devices) ATM Bonding 5.6.31 ATM Bonding For ATM Bonding, the Service Management Form allows the user to add and remove ports. Note: To create the ATM Bonding Group, the user should create an ATM Bonding Profile, and then use that Profile as part of provisioning with the Triple Play form. Refer to 5.6.3.4. The result should be an ATM Bonding Group that contains all of its members. 5.6.31.1 Status The status tab includes the status of the ATM Bond as well as the associated ports.
ATM Bonding Port Management (iMAP Devices) 5.6.31.2 Bonding Group - Viewing and Changing the Bonding Configuration The General subtab for ATM Bonded ports gives information on both the ATM Bond and the ADSL members. Refer to the following figure. FIGURE 5-199 ATMBOND Tab From this tab it is possible to enable and disable the ATM Bonding group, as well as add and remove ports to the bond.
Port Management (iMAP Devices) FIGURE 5-200 ATM Bonding Selecting a Port to add to Bonding Group • Enable ATM Bonding Group - If the group is disabled, the Enable button is available. Pressing the Enable button drives the ports to an Operational Status of UP, and then sets the ATM Bonding group to UP. At this point Port Management will show the root port as Type ATMBOND and the secondary port will no longer be in the port list. Refer to the following figure.
ATM Bonding Note: Port Management (iMAP Devices) The port retains all of its settings, and so you will need to change the settings (preferably through a Profile), if another application requires different settings. Refer to the following figure.
Port Management (iMAP Devices) ATM Bonding 5.6.31.5 Destroying the ATM Bonding Group To destroy the ATM Bonding Group, go to the primary port in the Port Management table. Select De-provision Customer Port, then choose Select All and De-provision. The Root port goes to Down and can now be provisioned for other applications. Refer to the following figure.
ATM Bonding Port Management (iMAP Devices) 5.6.31.6 PMON Thresholds AtmBond statistics are on a new tab. PMONs can be set for the for each ADSL line. RMONs are tied to the Bond interface. PMON statistics can be collected for each Interface FIGURE 5-204 ATMBOND Statistics 5.6.31.
Port Management (iMAP Devices) ATM Bonding FIGURE 5-205 ATMBOND Diags 5.6.31.8 Network Inventory - Customer Ports For ATMBOND ports a Managed Object is created to represent the ATMBOND. Its port number is preceded by ‘atmbond:”, and it has the same number as its primary port. Its type is “ATMBOND”. The primary ADSL ports type is changed to “ATMBOND-PRI” and each secondary ADSL port to “ATMBOND-SEC”. All Managed Objects will share the same CustomerID and IfIndex.
STP Tab Port Management (iMAP Devices) 5.6.32 STP Tab For each port configuration tab, there is an STP tab or sub-tab that shows the current STP attributes. Refer to the iMAP User Guide for details.
Port Management (non-iMAP Devices) Rapier/Switchblade Devices 5.7 Port Management (non-iMAP Devices) As Table 1-7 shows, port management is also provided for the Rapier and Switchblade devices (these include the 8700 and 9800 series). Note: For complete information on Rapier and Switchblade devices, go to http://www.alliedtelesis.co.nz/ documentation/ 5.7.
Rapier/Switchblade Devices FIGURE 5-208 Port Management (non-iMAP Devices) Ether like Port Management (Rapier Device) - Port Statistics Tab This form lists the standard RMON statistics.
Port Management (non-iMAP Devices) TABLE 5-57 Rapier/Switchblade Devices Provision Port Form for Port Management (Rapier Device) - Stats Graph Tab Field/Button Description Hidden Statistics: Statistics not added to the resulting graph View Statistic: Enabled when a statistic is chosen form Hidden Statistics, clicking this button adds it to the graph/ Hide Statistic: Enabled when a statistic is chosen form Graphed Statistics, clicking this button deletes it from the graph/ Display The attribute
GenBand Reports Port Management (non-iMAP Devices) 5.7.2 GenBand Reports 5.7.2.1 CPE Reports This table is accessed by right clicking on the GenBand icon and choosing Display CPE Report. This brings up the following figure. FIGURE 5-211 GenBand CPE Report This table provides the values for the GenBand connection to the CPE and includes: • CPE Name - When provisioned by the NMS, includes the IP address of the associated iMAP and port.
Port Management (non-iMAP Devices) GenBand Reports FIGURE 5-212 5-228 GenBand Line Report AlliedView NMS Administration Guide (Controlling and Provisioning Network Devices)
Dual End Line Testing (DELT) Port Management (non-iMAP Devices) 5.7.3 Dual End Line Testing (DELT) 5.7.3.1 Overview of DELT DELT provides information about the quality of the link between the ADSL card and the modem by collecting upstream and downstream values for attainable rate, line attenuation, signal attenuation, signal-to-noise margin, power spectrum density, and aggregate transmitted power.
Port Management (non-iMAP Devices) Dual End Line Testing (DELT) FIGURE 5-213 DELT Testing Tab 5.7.3.3 Initiate a DELT Diagnostic Clicking the Diagnose Interface button will initiate a DELT. A confirmation dialog box appears indicating that service may be disrupted, if confirmed the ATI activity dialog appears until the test starts. While running, all the buttons are disabled except for View Exported Test. The “DELT Status” field indicates “Running” or “In Progress” while the test is running.
Dual End Line Testing (DELT) Port Management (non-iMAP Devices) FIGURE 5-214 Graph of DELT Parameter Results 5.7.3.6 Export DELT Results to a File Clicking the Export Test Results button displays an export dialog similar to the one used for exporting other data from the NMS. Data is stored on the NMS server. If the File Chooser button is clicked, you can navigate to a directory on the server and select an existing file or create a new one.
Port Management (non-iMAP Devices) FIGURE 5-215 Dual End Line Testing (DELT) Exporting DELT Results to a File 5.7.3.7 Export DELT Results to Web Page As with other export operations, the data can optionally be exported to an HTML page and viewed with a browser. The page can then be saved using the browser.
Dual End Line Testing (DELT) Port Management (non-iMAP Devices) FIGURE 5-216 Exporting DELT Results to a Web Page 5.7.3.8 Viewing Exported DELT Results DELT results exported to a file can be viewed from using the View Exported Test button on the Port Details ADSL diagnostics tab. First a file chooser is displayed to select the file containing the test results.
Port Management (non-iMAP Devices) Dual End Line Testing (DELT) After a file is selected the test result viewer is displayed. The viewer window also has a View Exported Test button so that additional tests can be displayed and compared. A maximum of eight (8) tests can viewed simultaneously from a single client, in addition to the port details window. Refer to the following figure. FIGURE 5-218 View Graph Results 5.7.3.
Single-End Line Testing (SELT) Port Management (non-iMAP Devices) • H(f) Imaginary - The imaginary component of the characteristic function. • H(f) Real - The real component of the characteristic function. • H(f) Amplitude - The amplitude of the characteristic function. This is computed from the real and imaginary components. Amp = sqrt( r*r + i*i) where r is the real component and i the imaginary component. • H(f) Phase - The phase of the characteristic function.
Port Management (non-iMAP Devices) Single-End Line Testing (SELT) FIGURE 5-219 Running the SELT Test Select OK, and the test will begin. As it goes through testing, the state will change, until the test is complete and with a status of Success. Refer to the following figure. FIGURE 5-220 SELT Test Complete Once the test is complete, the user can view the results on a browser or save the test results for later analysis.
Diagnostics for ATMBOND Port Management (non-iMAP Devices) 5.7.
Port Management (non-iMAP Devices) Support of CWMP with TR-069 Devices 5.7.6 Support of CWMP with TR-069 Devices Caution: Caution: Due to inter operability problems, do NOT use the TR-069 CPE WAN Management Protocol (CWMP) to manage Comtrend 5631 CPE. Otherwise, service may be interrupted. Instead, use the Comtrend web GUI for configuration and management. Contact your ATI representative for details. 5.7.6.
Support of CWMP with TR-069 Devices Port Management (non-iMAP Devices) 5.7.6.2 Basic Functions The following functions are provided: • Provisioning of the Comtrend device using the NMS Video and internet services can be provisioned using the NMS Triple-Play GUIs, using TR-069. Existing Profiles can be used with the Comtrend CPE as with other iMG/RGs. • Backup and Restore The Comtrend configuration files can be backed up and restored as with other CPE devices.
Port Management (non-iMAP Devices) Support of CWMP with TR-069 Devices • The upstream port cannot be determined, and so provisioning is done using the CPE MAC address. This is similar to provisioning an iMG without an iMAP. Refer to 7.11. • An Auto-Configuration Server (ACS) URL must be configured in the CPE for using TR-069 for communicating with the ACS (the NMS).
Support of CWMP with TR-069 Devices FIGURE 5-224 Port Management (non-iMAP Devices) Comtrend Boot Configurator The fields in this form are as follows: • Mgmt. VLAN - The VLAN used for sending and receiving configuration information and downloads to the CPE. • Trap Host - The IP address of the Auto Configuration Server (ACS) - the NMS. • ACS URL - An ACS URL is required to be configured in CPE for using TR-069 for communication with the ACS server (NMS).
Port Management (non-iMAP Devices) Support of CWMP with TR-069 Devices Run the Comtrend Boot Configurator at the NMS server. Check the Save Only checkbox before clicking OK. Then copy the configuration file to a PC connected to a LAN port on the Comtrend. Use the web GUI on the Comtrend to update settings with the configuration file. • Method 2 Install and run the NMS server software on a PC connected to a LAN port on the Comtrend. You must run the NMS server software so the TFTP server is running.
Support of CWMP with TR-069 Devices Port Management (non-iMAP Devices) FIGURE 5-226 Note: 7. Updating Comtrend with Configuration File The following steps are optional. After the Comtrend has rebooted, to verify settings, select Device Info > WAN. The WAN Info page should show the CPE Mgmt service provisioned with the VLAN specified in step 2. Refer to Figure 5-227. FIGURE 5-227 8. Comtrend WAN Info Select Management > TR-069 Client.
Port Management (non-iMAP Devices) FIGURE 5-228 5-244 Support of CWMP with TR-069 Devices Comtrend TR-069 client - Configuration AlliedView NMS Administration Guide (Controlling and Provisioning Network Devices)
Support of CWMP with TR-069 Devices Port Management (non-iMAP Devices) 5.7.6.8 Staging - Method 2 • Prerequisites: • The Comtrend is set to factory defaults. • A local PC (desktop/laptop, etc.) has been loaded with the NMS release 11.0 SP5 software. • The local PC is connected to a LAN port on the Comtrend device. The PC obtains an IP address automatically from the Comtrend. The specific steps are as follows: 1. Start up the local NMS on the local PC (Programs->AlliedView NMS->Start NMS Server). 2.
Port Management (non-iMAP Devices) Support of CWMP with TR-069 Devices 5.7.6.9 Example Procedure - Provisioning At an NMS client on the network, the Comtrend is provisioned as follows: 1. Bring up the Triple Play form for Bonded ports, as explained in 5.6.3.4. Refer to Figure 5-230. 2. For the Comtrend device, you must enter a Description (Customer ID) of 15 characters or less.
Support of CWMP with TR-069 Devices FIGURE 5-231 4. Port Management (non-iMAP Devices) Comtrend Device in iMG/RGs table Go to the Nodes table and find the upstream iMAP device for the Comtrend. Right-click on the node, then click Discover Attached iMG/RGs. The Comtrend device now has the upstream port filled in at the iMG/RG table, and provisioning is complete. 5.7.6.10 Managed Object Properties Right-click on the Comtrend row in the iMG/RG table.
Port Management (non-iMAP Devices) Support of CWMP with TR-069 Devices FIGURE 5-233 Comtrend Device Parameters (1) FIGURE 5-234 Comtrend Device Parameters (2) Several parameters are collected during discovery and by calling operations to retrieve basic device information and these few are required to manage the CPE using (CWMP) TR-069.
POE View / Modify Port Port Management (non-iMAP Devices) 5.7.6.11 CWMP Browser Also available in NMS release 11.0 SP5 is a CWMP browser that allows the user to view and change the parameters on a TR-069 compliant device. The tool is accessed by selecting Tools -> CWMP Browser (directly above SNMP MIB Browser). The TR-069 Operations Form appears. In the Device pull-down are available TR-069 devices available for the NMS, which in release 11.0 SP5 are the Comtrend devices. 5.7.
Scheduling and Controlling Provisioning Tasks One Time 5.8 Scheduling and Controlling Provisioning Tasks 5.8.1 One Time When a task is to be performed one time only, the user will see the One Time Schedule type form that as the options of having the AlliedView NMS perform the task. Refer to the following figure. FIGURE 5-236 One-time Task Form The user can select: • Now - The task begins as soon as the AlliedView NMS is able to perform it.
Recurring Scheduling and Controlling Provisioning Tasks In this form, the user can double-click on the specific task and get details of the status of the task. (This is especially useful if the task as failed, as seen in the figure.) The user also has the following options for the specific task(s) that are chosen: • Download - Download the file onto the device. (Software Download only).
Scheduling and Controlling Provisioning Tasks View Tasks Form 5.8.3 View Tasks Form Once a task has been performed or placed in a schedule, it is added to the main task table, the View Tasks Form, which allows the user to query or immediately activate a task, as well as to abort a task that is in progress. The Task Table is accessed by selecting Tools -> View Tasks from the main menu. The following figure appears.
Alarms/Events Other Device Control Tasks FIGURE 5-240 Cleanup Button for View Tasks Window The user selects the Cleanup button, and then selects a date. After pressing Select, the user sees the Task Window select all of the tasks that meet that criteria. The user can then select Remove, and all of the tasks prior to that date are removed. 5.9 Other Device Control Tasks 5.9.
Other Device Control Tasks File Comparison (Text Files) 5.9.3 File Comparison (Text Files) The Configuration File Comparison feature compares and displays two text files side-by-side with their differences highlighted. Text files can be selected for comparison from the Configuration File Management, Command Script Management, and Device Backup/Restore applications. Any two text files from any two devices can be compared.
File Comparison (Text Files) TABLE 5-59 Other Device Control Tasks Scenarios for Text File Comparison Task Application Steps View Latest Changes Config File Mgmt 1. User navigates to Config File Mgmt. 2. User right-clicks on a single row. 3. User selects the Compare Files button. 4. The latest differing config files for the device are displayed side-by-side with their differences highlighted. 5. The names, dates, and sizes of the files compared are also displayed. 1.
Other Device Control Tasks File Comparison (Text Files) 5.9.3.1 Viewing Latest Config File Changes from MAP Device Following is an example of the first scenario to show the screens and responses for viewing the latest changes. For configuration comparison on a device, right click on the device and select View Config Changes. Refer to the following figure.
File Comparison (Text Files) Other Device Control Tasks This will display the latest two text backup files from the selected device, side-by-side, with their differences highlighted. See the following figure. Differences are indicated by highlighting text. Plain text shows lines that are the same in both files. Red text shows lines on the left which are not on the right while blue shows lines on the right which are not on the left. Missing lines are padded with blanks.
Other Device Control Tasks File Comparison (Text Files) FIGURE 5-243 Only One Backup file - No Comparison Possible If there are no backup files, and the display will be empty and a notice will pop up indicating no backup files exist for the device. See the following figure.
File Comparison (Text Files) Other Device Control Tasks At the top of the display are the file names, their dates, and their sizes. These are updated whenever the files are compared, so they always indicate exactly which files are being compared. When the user enters other files into the file-selection boxes at the bottom of the display (explained below), they will not take effect until the Diff button is pushed. Therefore the bottom file names may not match the displayed data.
Other Device Control Tasks File Comparison (Text Files) • No files found in user’s subdirectory - When brought up from Config File Management, config files are searched for in the user's config file subdirectory instead of the backup directory. This message is displayed if no files are found for the device in the user's subdirectory.
Discover Attached iMG/RGs Other Device Control Tasks 5.9.4 Discover Attached iMG/RGs For a detailed explanation of how DHCP is set up so that iMG/RGs can be discovered and configured, refer to Section 7. On initial discovery of the iMG/RG (out of the box or provisioned to a different Access Island), the bootstrap VLAN is used. Subsequent discoveries are performed using the RGMgmt VLAN. This option will (re)discover all the iMGs/RGs attached to the iMAP device that use the RGMgmt VLAN.
Other Device Control Tasks Telnet / SSH to a Device 5.9.6 Telnet / SSH to a Device To access a device using telnet or SSH, there are the following options. 5.9.6.1 Access a Telnet or SSH-enabled Device Use Tools -> Open Telnet or Tools-> Open SSH to connect to any device that is telnet- or SSH-enabled and is accessible. Refer to the following figure that is used for SSH-enabled devices. FIGURE 5-247 Accessing a Device for SSH Note: For SSH, the user-specified Time-out is ignored.
Browse Device (Rapier Device Only) Other Device Control Tasks 5.9.7 Browse Device (Rapier Device Only) To access the Web-enabled on-device management GUI, right-click the device and choose Browse Device. The Browse Device feature is not currently supported for iMAP devices. If an iMAP device is chosen, the following example window appears. 5.9.8 Rediscovery Device (When Required) This option picks up any changes made to the selected device.
Other Device Control Tasks Update Status • Max - The device’s status is rolled-up from the current status of all its components in the database, however they were determined (which themselves may have been ping, snmpping, or max), without actually going to the device. Thus with max, a router’s status would be the maximum status of all its interfaces.
Overview Manage CLI Users 5.10 Manage CLI Users Note: This option is available only to users in the Admin group. This option is used to specify common CLI login-passwords for a set of devices. This data is then used during the discovery process to log in on each device and save the username/password pair on a per-device basis. Note: This function is part of the Discovery Panel. 5.11 Customer Cutover 5.11.
Customer Cutover Cutover Scenarios/Restrictions • Cutover only applies to ports of the same interface type, such as ADSL to ADSL, since otherwise source port parameter settings would not map to destination port parameter settings. • To ensure parameter compatibility, cutover is restricted to destination ports on devices running the same or higher version of software as the source device, and for ADSL and VDSL, the same annex (A, B, or C).
Procedure Overview TABLE 5-60 Customer Cutover Provisioning Guidelines/Restrictions for the Customer Cutover Feature Interface Type Card Type Notesa VDSL VDSL24A Annex of destination card must match annex of source card XE VDSL24B Annex of destination card must match annex of source card XE1 Not Supported XE1S Not Supported XE4 Not Supported XE6 Not Supported XE6SFP Not Supported a. If text is Supported, assumes both network and customer direction unless noted otherwise. 5.11.
Customer Cutover Procedure Example - Transfer to different cardtype 5.11.4 Procedure Example - Transfer to different cardtype In this example, the user wishes to transfer the 24 ports of an ADSL24 card to an ADSL48A card. (This example would be fairly typical, since many system upgrades involve installing ADSL48A cards and transferring over existing ports.) 5.11.4.
Procedure Example - Transfer to different cardtype FIGURE 5-249 Customer Cutover Selecting Source Ports The user then selects the now active Cut-Over Customer Button, and the Customer CutOver panel appears, as shown in the following figure. Note that the initial destination device is the same as the source device.
Customer Cutover Procedure Example - Transfer to different cardtype FIGURE 5-250 Initial Customer Cut Over Screen The user now selects a different device in the Destination Device pull-down. Once selected, the NMS searches the destination device and then lists all the available destination ports, as shown in the following figure.
Procedure Example - Transfer to different cardtype Customer Cutover In most cases, the destination has a one-to-one mapping between ports on the card. However, the user is free to select various destination ports, as shown in the following figure. Note: Although the destination ports are valid since they are the same type, the NMS will produce an error message if the user tries to transfer an Annexed port to a non-Annexed port.
Customer Cutover Procedure Example - Transfer to different cardtype 5.11.4.2 Physically disconnect/reconnect the ADSL cables The user now disconnects the ADSL cable(s) and connects them to the ADSL 48 card. Note: To connect the ADSL cables to another card, the user may need to change the cabling facilities. Also note that the cable type is probably the same, but if the user were going from an ADSL16 card to an ADSL24/48 card, the connections would have to be changed and a different cable type used.
Procedure Example - Transfer of iMG to different Port FIGURE 5-254 Customer Cutover Original Ports Ready to be Re-Provisioned The procedure is now complete, with the iMG/RGs up on the destination ports and passing traffic, and the original ports deprovisioned. 5.11.5 Procedure Example - Transfer of iMG to different Port This type of procedure is more complex since when the iMG is moved to a different port, the NMS database will be updated with the new location (upstream port).
Customer Cutover Procedure Example - Transfer of iMG to different Port In this example, six iMGs are being transferred from FX10 ports to FX20 ports. Also, the source and target ports are on the same device, but the target ports could be on a different device. Caution: If performing cut-over to a different device, the VLAN network must be pre-configured to maintain IP connectivity after the cables are moved over to the new ports. (Refer to Section 7 on how Access Islands are configured to guarantee this.
Procedure Example - Transfer of iMG to different Port Customer Cutover The user first brings up the Port Management Form for the source device and highlights the appropriate source ports, which must be provisioned ports with a Customer ID, as shown in the following figure. FIGURE 5-255 Selecting Source Ports for iMG/RG Cutover The user then clicks on the Cut-Over Customer button. The Customer Cut-Over Panel appears, with the Source Device, Ports, Types, and Customer IDs filled in.
Customer Cutover Procedure Example - Transfer of iMG to different Port FIGURE 5-256 Data filling Destination Ports to be Provisioned The user selects the appropriate ports and then clicks on Provision Destination. The Task Details panel appears, and this shows the status of each port as the attributes are copied over. (Each port goes through the status sequence Validated - Working... - Provisioned.) Refer to the following figure.
Procedure Example - Transfer of iMG to different Port FIGURE 5-258 Customer Cutover All Port Attributes Copied over to Target Ports 5.11.5.2 Physically disconnect/reconnect the iMGs to the new Ports The user now disconnects the optic fiber from the FX10 port and connects it to the FX20 port. Note: To connect the FX10 cable to the FX20 port, the user may need to change the cabling facilities.
Customer Cutover Procedure Example - Transfer of iMG to different Port FIGURE 5-259 Note: Selecting iMG/RGs and Updating DHCP Client The Update DHCP Client process will fail if the iMG/RG is not powered up and VLAN IP connectivity is lost. Refer to the Note in 5.11.5.1. FIGURE 5-260 DHCP Recovery Complete 5.11.5.4 Copy over the iMG attributes Returning to the Task Details Form, the user selects the appropriate ports and selects Complete.
Procedure Example - Transfer of iMG to different Port FIGURE 5-261 Customer Cutover Completing the iMG/RG Provisioning or Cutover When the provisioning is complete, the iMG/RG table shows the new upstream ports. (The task is deleted automatically once cut-over status for all customers has completed successfully). Refer to the following figure. FIGURE 5-262 iMG/RG Table when Provisioning is Complete 5.11.5.
Customer Cutover Procedure Example - Transfer of iMG to different Port FIGURE 5-263 Original Ports Ready to be Re-Provisioned The procedure is now complete, with the iMG/RG up on the destination ports and passing traffic, and the original ports de-provisioned.
6. Configuring Network Services 6.1 Overview As a network management product, the AlliedView NMS can allow network-based services to be configured. Table 6-1 lists the network services that are configured in AlliedView NMS release 14.0. TABLE 6-1 Network Services in AlliedView NMS Release 12.0 Network Service Description Notes / Section Overview of Network Services Refer to 6.1 Topology Maps and Inventory tables 6.2 Network VLANs Creating, Extending, and Trimming 6.3 through 6.8 HVLAN - 6.9.
Overview Profile Management TABLE 6-1 Network Services in AlliedView NMS Release 12.0 Network Service Description Notes / Section Diagnostic Audit Provides the capability to run diagnostic audits on certain network entities. Currently, the auditable entities are: Refer to 6.21. • Network VLANs • CES Circuits Port Authentication Refer to 6.22. a. VLAN Translations may be needed when configuring the VLANs on the iMG6x6MOD. This involves interaction between the iMG and Port Profiles. Refer to 7.9.
NTE8 Service Topology Maps and Inventory Tables 6.1.5 NTE8 Service The NTE8 card is used to allow DS1/E1 facilities to connect (backhaul) the ethernet network, with both ends of the DS1/E1 connections being on iMAP 9000 devices. Refer to the iMAP User Guide for a complete description of the NTE8 configuration. Note: Refer to 5.5.15 and 5.6.21 for an overview of the NTE8 card and DS1/E1 port attributes. The NTE8 configuration always has dual endpoints, since there must be an iMAP 9000 device at each end.
Topology Maps and Inventory Tables FIGURE 6-1 VLAN Network Map (Layer 3) Network Objects used for Network VLANs 6.2.2 VLAN Network Map (Layer 3) By containing symbols for routers and the layer 2 subnetworks, this map shows all VLAN networks and their Layer-3 (IP) connectivity. On this map, an IP-based Network VLAN will include its router connections. An island-based Network VLAN will still appear as a layer 2 subnetwork symbol, but it will have no router connections. Refer to Figure 6-2.
VLAN Sub Maps (Layer 2) Topology Maps and Inventory Tables FIGURE 6-2 VLAN Network Map Double-clicking any of the Network VLAN symbols or selecting one of the VLAN network nodes in the VLAN Network tree will open up the VLAN Network Map (layer 2), a map of the individual Network VLAN. 6.2.3 VLAN Sub Maps (Layer 2) Each VLAN network symbol on the layer 3 topology map has its associated layer 2 topology map.
Topology Maps and Inventory Tables Physical Network Map FIGURE 6-3 Note: IVLAN Map (Layer 2) The connectivity on the layer 2 VLAN subnetwork map is derived from the physical link connectivity that is configured and viewed in the Physical Network map. If physical links have been created on the Physical Networks map, the Network VLANs will appear here. This also allows Network VLANs to be configured even if the physical connections do not exist. Refer to 6.2.4.
Physical Network Map Topology Maps and Inventory Tables FIGURE 6-4 Physical Network Map The ability to add, delete, and view physical links is useful in the following scenarios: • Viewing existing Network VLANs - As the physical connections are created and configured, if there is an existing Network VLAN that uses that physical connection, its submap will automatically be configured and added to the VLAN Network nodes.
Topology Maps and Inventory Tables Physical Network Map • Network VLAN Manager - Shows all Network VLANs in a hierarchy To create a physical link, select Network Service -> Link Operations from the pull-down menu or right click anywhere on the map area. The Layer 2 Links form appears, as shown in Figure 6-5. This form displays the links associated with the Nodes and/or Links that are currently selected. If no links are selected, it displays all Links in the NMS database.
VLAN Interfaces Inventory Table Topology Maps and Inventory Tables FIGURE 6-6 Add Links Form for a Physical Connection From this form, enter the name that will be given to the link. Use the Select Device to select which devices will be the end points of the link. Once the devices are selected, the available ports are shown in the pull-down menu for the Port. When the Apply button is clicked, the new link is automatically added to the Layer 2 Links table.
Topology Maps and Inventory Tables FIGURE 6-7 TABLE 6-2 VLAN Interfaces Inventory Table Network Inventory for VLAN Interfaces VLAN Interfaces Inventory Table Column Description VLAN Interface Name The name of the VLAN interface on the device, which can be specified when creating a Network VLAN using the GUI wizard. Refer to 6.3.1. ID The VLAN interface ID (device name and VLAN ID). Type The type of interface. Always VlanInterface in this inventory table.
Physical Links Inventory Table Topology Maps and Inventory Tables • Managed Object Properties - The base properties of the interface, including the IP address and netmask if it is part of a VLAN. • Delete Object and Traces - This will delete the VLAN IF and all its sub-elements, so there is a confirmation window. • Manage/UnManage - The interface will (or will no longer) be polled by the AlliedView NMS. The color of the row icon turns to gray.
Creating Network VLANs Alarm Indicators from the Maps and Inventory Tables When the Physical Links table is the active panel, the Link menu pull-down appears and the following options are available: • Managed Object Properties - The base properties of the physical link. • Alarms/Events - This will invoke the Fault Management tables for Alarms and Events on the selected link. • Manage/UnManage - The link may be set to unmanaged to indicate that it is not a real link, but rather a modelled link.
Modify the Network VLAN Link Configuration FIGURE 6-9 TABLE 6-4 Creating Network VLANs Create VLAN Net Form - Initial VLAN Information Create VLAN Net Form Column Description Working Nodes Nodes that are to be included in the Network VLAN. Nodes not in the original working nodes can be included in a VLAN by following an existing or newly created link to a new node. This is not recommended, though, as the auto-selected VLAN ID and VLAN Name may clash with entries already on these new nodes.
Creating Network VLANs Modify the Network VLAN Link Configuration FIGURE 6-10 Create VLAN Net Form - Modify Links Any links that were selected from the Physical Map when the Wizard was started are displayed in the Vlan Path Links table on this form. The available physical links from each device are listed in the Add Links subform.
Configure the VLAN Interfaces (Service Ports) FIGURE 6-11 Creating Network VLANs Adding Vlan Path Links - File There is also the option to create a physical link by clicking Create New Link, and a new physical connection between two devices and their ports can be created. This uses the same form as shown in 6.2.4. 6.3.3 Configure the VLAN Interfaces (Service Ports) The next step is to configure the VLAN interfaces by adding any service ports to the Network VLAN.
Creating Network VLANs Configure the VLAN Interfaces (Service Ports) FIGURE 6-12 Configure VLAN Interface Form - File If this is an IP-based VLAN, you can enter the IP address in the cell in the IpAddress column, and the network mask in the cell in the Mask column. This must be extended to a specific address within the subnet. For the port row, click the IpAddress cell and enter the IP address, and then click the Mask cell and enter the network mask.
Configure the VLAN Interfaces (Service Ports) FIGURE 6-13 Creating Network VLANs Edit Ports Form Clicking on the ports and then clicking Close adds these to the Service Ports cell that was chosen. Multiple ports may be selected pressing the Shift or Ctrl key while clicking. The same port must not be selected in both the Tagged Ports and Untagged Ports lists. This error will be detected when the Close button is clicked. The form will not close until the error is corrected.
Extending Network VLANs FIGURE 6-14 Configure the VLAN Interfaces (Service Ports) Test Network VLAN Form (with error and option to ignore) 6.4 Extending Network VLANs Once a Network VLAN is created, the general procedure for extending it is as follows: 1. Open the Network VLAN submap associated with the VLAN. This can be done by right-clicking the desired VLAN on the main Network VLAN map and selecting Open Submap from the pop-up menu. 2.
Configure the VLAN Interfaces (Service Ports) FIGURE 6-15 Extending Network VLANs Extending a Network VLAN The Extend Network VLAN form that appears when you select Extend Vlan from the pop-up menu is shown in Figure 616. FIGURE 6-16 Extend Network VLAN Form (Physical Link) This form shows Network VLAN Name, the VLAN ID (VID), and the available links from the device selected. (At this point a new physical link can be created between this device and the device that will include the Network VLAN.
Extending Network VLANs Configure the VLAN Interfaces (Service Ports) Select one of the available physical links to activate the Next button. The form that shows the available VLAN IFs on this physical link is displayed, as shown in Figure 6-17. FIGURE 6-17 Extend Network VLAN Form (VLAN Interface) - File Select one of the VLAN Interfaces. (At this point a new VLAN Interface can be created on the device.) Select one of the available VLAN Interfaces to activate the Next button.
Configure the VLAN Interfaces (Service Ports) Trimming or Splitting Network VLANs The IP address and network mask can be entered in cells IP Address and Network Mask respectively by clicking the cell and entering the value. Note: When you click the IP Address cell, the cell will be filled with the subnet address, and when you click the Network Mask cell (or any other cell), the cell will be filled with the network mask for the subnet.
Network VLAN Manager (Excluding EPSR) FIGURE 6-20 Overview Delete Network VLANs Form Select one of the VLAN IDs, and then click Delete VLAN. A form showing all the associated VLAN Interfaces that will also be deleted will appear. If this is what you wish to do, click Finish. The Task Details window then will appear. Note: VLAN Interfaces with VID of 1, the default VLAN, will not be deleted. 6.7 Network VLAN Manager (Excluding EPSR) 6.7.
Using the Network VLAN Hierarchy Network VLAN Manager (Excluding EPSR) 6.7.3 Using the Network VLAN Hierarchy Viewing the Network VLAN Manager/Analyzer is done from the Physical Network map. From the Network Service menu, select VLAN -> Network VLAN Manager. The Network VLAN Manager/Analyzer form appears, as shown in the following figure. The View Networked VLANs view is selected.
Network VLAN Manager (Excluding EPSR) TABLE 6-5 Using the Device VLAN Hierarchy Network VLAN Functions on the Network VLAN Manager Type of VLAN Function Description LINKPORT View Link Port Brings up the Port Management Form. View Neighbor Link Port... Brings up the port management form for the next port in the VLAN hierarchy in the left panel. Delete Logical Link Brings up the Delete Virtual Link form, which deletes the VLAN path between two devices (not the physical link). Delete Assoc.
Importing Physical Link Configurations Network VLAN Manager (Excluding EPSR) Right clicking on the Network VLAN, VIF Device, or LINKPORT Node node allows the administrator to perform various tasks, listed in the following table TABLE 6-6 Device VLAN Functions on the Network VLAN Manager Type of VLAN Function Description VLAN Interface (VIF) Device View VLAN Interface... Brings up chassis view for the VLAN Interface chosen Extend VLAN... Extends the chosen VLAN. Refer to 6.4 Resync Device...
Network VLAN Manager (Excluding EPSR) FIGURE 6-23 Importing Physical Link Configurations Example Physical Link Spreadsheet To view the spreadsheet, open the file with Excel. Note: The Excel file cannot be viewed on the Solaris platform. To ensure that all files in the state directory are available, select Reload Profiles. To actually import the spreadsheet, select Import/Export. As the links are loaded, progress messages will appear, as shown in Figure 6-24.
Exporting Physical Link Configurations FIGURE 6-24 Network VLAN Manager (Excluding EPSR) Error Messages When Importing Physical Links Figure 6-24 shows an example of error messages, when the spreadsheet contains links that already physically exist. 6.7.6 Exporting Physical Link Configurations The physical link configuration can be exported to an Excel file as well. If the user provides a file name that ends with .
Network VLAN Manager (Excluding EPSR) FIGURE 6-25 Viewing VLAN Outage Statistics Exporting Link Configuration Data to an Excel File If the user selects an existing profile or specifies the name of an existing profile, the data will be imported from the specified Excel file and not re-exported. Any existing links included in the file will be skipped. 6.7.
Viewing VLAN Outage Statistics Network VLAN Manager (Excluding EPSR) FIGURE 6-26 Note: Sample VLAN Outage Monitoring Timeline For protection schemes, such as EPSR, when there is a break in the network VLAN topology due to link failure, an alternate path allows traffic to continue to run. As a result, these will not be recorded as outages and therefore will not appear for that networked VLAN. For more detail on EPSR, refer to 6.13.
Example of Creating Network VLANs FIGURE 6-28 Sample Island-Based Network VLAN Network Vlan Outage Details Window 6.7.7.2 Resetting Monitor Time To reset the monitor time (i.e. set the monitor start time to the current monitor time), select a VLAN from the list, and then click Reset Monitor. 6.7.7.3 Refreshing all Network VLANs To refresh all of the VLANs in the list, click Refresh All. 6.7.7.
Sample Island-Based Network VLAN FIGURE 6-29 Example of Creating Network VLANs Sample Island-Based VLAN Networks Figure 6-30 shows the three devices on the physical network map. Note that the Rapier 48i already has a physical link to another device.
Example of Creating Network VLANs FIGURE 6-30 Sample Island-Based Network VLAN Three Devices Included in the Island-Based VLAN To create the physical links, select and Shift-select to include all three devices, and then right-click to select Network Service > Link Operation.The Layer 2 Links form appears. Select Add Link, and then select the link name, device number, and port number to configure the example. Figure 6-31 shows Link_#20 being configured.
Sample Island-Based Network VLAN Example of Creating Network VLANs FIGURE 6-31 Creating a Physical Link Once the two physical links (Link_#20 and Link_#21) are created in the AlliedView NMS, the Network VLANs that will use the links (Training and Sales) can be created. Still on the Physical Network map, Select and shift-select the three devices, and then right-click Network Services -> VLAN -> Create VLAN. The Create VLAN form will appear.
Example of Creating Network VLANs FIGURE 6-32 Sample Island-Based Network VLAN Sample Values for the Training Network VLAN Click Next, and the Modify Links form appears. Check the checkbox for Link_#20 and Link_#21 from 172.16.33.2. Do not select Link#5, since that is not part of this Network VLAN. Figure 6-33 shows Link_#21 about to be added.
Sample Island-Based Network VLAN FIGURE 6-33 Example of Creating Network VLANs Adding Link_#20 and Link_21 to the Network VLAN After adding the relevant physical links, click Next. The Configure Vlan Interfaces form appears, and shows the VLAN interfaces over the physical links.
Example of Creating Network VLANs Extending the Island-Based VLAN the devices that have service ports. In the example the service ports would be 11.0 Untagged for 172.16.33.11 and 0.6 Untagged for 172.16.33.18. Click Next, and the Test Network VLAN form appears. This will test the connectivity between all three devices.Click Finish and the Task Details form will show the tests and if they are successful, as shown in Figure 6-35.
Extending the Island-Based VLAN FIGURE 6-36 Example of Creating Network VLANs Adding a Physical link to Extend a Network VLAN Now that the physical link is created, go to the Training VLAN in the VLAN Network map, Right-click on the device in the Network VLAN that has the new link (172.16.33.18) and select Extend VLAN. The Extend Network VLAN form appears, which includes the new physical link, as shown in Figure 6-37. Note that you could create the new physical link here is desired.
Example of Creating Network VLANs Extending the Island-Based VLAN Select the link and click Next.The Select/Create VLAN Interface form appears. Since the Training VLAN is not yet created on the .13 device, click Create VIF. The Create New VLAN form appears, with the Training VLAN with the VLAN ID of 30 already filled in. Click OK and the VLAN Interface will be added, as shown in Figure 6-38. FIGURE 6-38 Creating the VLAN IF on the extended Network VLAN Device Select the row and click Next.
Overview Example Configurations for HVLAN, Translations FIGURE 6-39 Updating the VLAN IF on the Extended Network VLAN Device 6.9 Example Configurations for HVLAN, Translations 6.9.1 Overview Note: The Port-based HVLAN and translation feature are not compatible on the same port. Once a port is configured with the HVLAN option, it cannot use the translation feature, and vice-versa. This applies to the cards that support both of these features (GE3, XE1, GE8). 6.9.
Example Configurations for HVLAN, Translations FIGURE 6-40 HVLAN Configuration Example HVLAN Configuration This example assumes the physical links (Link-10-20 and Link-0_0-2) have already been created, as explained in 6.2.4. On the Physical Network map, Select and shift-select the three devices, and then right-click Network Services -> VLAN -> Create VLAN. The Create VLAN form will appear (Initial VLAN Information). Fill in the fields for the VID502, as shown in Figure 6-41.
HVLAN Configuration Example Configurations for HVLAN, Translations FIGURE 6-41 Create VLAN for HVLAN Configuration Clicking on Next brings up the Modify Links Form, where the user selects a device from the Available Links Form pulldown, and then adds the appropriate link, as shown in Figure 6-42.
Example Configurations for HVLAN, Translations FIGURE 6-42 HVLAN Configuration Selecting Links and Adding to the HVLAN Configuration Clinking Next brings up the Configure VLAN Interfaces Form, as shown in Figure 6-43. For the iMAP 9000 devices, the type must be changed to HVLAN, which the figure illustrates. At this point the user can click on the Service Ports column and select which ports will included.
HVLAN Configuration FIGURE 6-43 Example Configurations for HVLAN, Translations Configure Vlan Interfaces Form (iMAP 9000 Devices are Type HVLAN) Now that the Vlan Interfaces are configured, it can be tested. Clicking on Next brings up the Test Network Vlan form, (Figure 6-44), and then clicking on Finish runs the test and provides the results, as shown in Figure 6-45. If a test does not succeed, an error window appears with a message as to why the test failed.
Example Configurations for HVLAN, Translations HVLAN Configuration FIGURE 6-44 Test Network VLAN Form (Finish to run Test) FIGURE 6-45 Testing Results for the HVLAN Configuration Extending this HVLAN configuration usually involves adding another iMAP 9000 device with service ports that support multiple VLANs on its untagged ports. The steps are similar to the steps in 6.8.
HVLAN Configuration Example Configurations for HVLAN, Translations the list. The user would then select this Vlan and select Next. The Vlan Operations Form appears with the CREATE operation for the HVLAN502. Selecting Finish will run the tests to check if the configuration is valid.
Example Configurations for HVLAN, Translations VLAN Translations Configuration 6.9.3 VLAN Translations Configuration 6.9.3.1 Setting up VLAN Translations To set up VLAN translations, the basic sequence is: 1. Create the VLAN that will become the translated VLAN that will go through the network. 2. Associate this translated VLAN with the appropriate interfaces, both on the customer side (where the translation will take place), and the network side (as the translated VLAN goes through the network). 3.
VLAN Translations Configuration Profile Management • ADSL24A/B, SHDSL24, ADSL24SA, ADSL24AE, NTE8, VDSL24A/B, ADSL48A/B (customer interfaces) • The following cards do not support VLAN translation: • CES8 • The Port-based HVLAN and translation feature are not compatible on the same port. Once a port is configured with the HVLAN option, it cannot use the translation feature, and vice-versa. This applies to the cards that support both of these features (GE3, XE1, GE8).
Profile Management Profile Configuration Parameters - Devices and Scoping 6.10.1 Profile Configuration Parameters - Devices and Scoping 6.10.1.1 Devices There are many different types of devices and ports in the network and each type has a different set of parameters associated with it.
Profile Configuration Parameters - Devices and Scoping Profile Management Note: For the ADSL port profile the user can specify for a service VLAN the VC (0-3) as well as the VPI, VCI, and framing. Note: The ADSL-Bond profile is used to support the G.bond (ITU G.998) for ADSL interfaces. It includes references to a primary and secondary ADSL port profile. Refer to 6.10.12. Note: Port Direction is available for the port profile for ether-like ports.
Profile Management TABLE 6-7 Profile Configuration Parameters - Devices and Scoping Comparison of Ethernet Port Parameters for Profile Management Parameter Rapier Device Switchblade / 9800 Device Multicast limit x Master/Slave mode x Ingress limit (I Series only) x Egress limit (I Series only) x Acceptable traffic (VLAN or ALL) x x Input Filtering (On or OFF) x Multicast MODE (A, B, or C) x FC Length x Jumbo x iMAP Device (9x00) Flow Control x x x QOS Policy x x x STP (wi
Profile Configuration Parameters - Devices and Scoping Profile Management using the wildcard (*) that is part of the name. For example, if Profile Scoping has the value 192.168.100.*, it includes all IP address under the 192.168.100.xxx network. By having this Profile Scoping value, provisioning is controlled as follows: • Whenever a Profile is part of provisioning (such as Triple Play or deploying a Profile), only those devices that match the Profile Scoping are available.
Profile Management Creating a Profile 6.10.2 Creating a Profile The profile feature allows the user to create, device, card, port, and iMG/RG profiles, as well as removing an association with a profile. There are two ways to access this menu: • At the Physical Network Node, right click away from the device icons and select, for example, Profile -> (or one of the other profile types). • At the Network Service Data Node, click on the Profiles leaf.
Creating a Profile Profile Management FIGURE 6-48 Create Profile for Ethernet Port - Product Type Tab Each product type has a tool tip that includes the specific products that belong to that group. Refer to the following figure. FIGURE 6-49 Tooltip for Product Type Tab 6.10.2.3 Etherlike Profile for GE24POE includes POE To configure the GE24POE port on the SBx3112, the POE tab is included with the Etherlike Profile, as shown in the following figure.
Profile Management Creating a Profile FIGURE 6-50 Etherlike Profile for POE The three values to be filled in are: • Power Over Ethernet State - Whether to enable or disable the feature • Priority - Ports with lower priority will stop being powered when the system cannot allocate enough power to all ports. • Power Shutoff Limit - Power will be cut off if it exceeds the set threshold For detailed information on the parameters, refer to the SBx3112 Product Guide. 6.10.2.
Viewing and Modifying Profiles Profile Management 6.10.3 Viewing and Modifying Profiles Once the profiles are created, they can be viewed by selecting the Profile node under the Network Data Services object, as shown in the following figure. FIGURE 6-51 Viewing the List of Profiles (includes POTS24 Card Profiles) The profiles can be viewed like other attributes, so they can be sorted, scrolled, and have a search function.
Profile Management Deploying a Profile 6.10.5 Deploying a Profile To deploy a profile means to apply the configuration values assigned in a Profile to a set of objects (devices or ports) in the network. Note: The set of objects on which to apply the Profile must be of the same type as the Profile.
Deploying a Profile Profile Management FIGURE 6-52 Deploy on Port Profile Form AlliedView NMS Administration Guide (Configuring Network Services) 6-57
Profile Management Deploying a Profile FIGURE 6-53 FIGURE 6-54 6-58 Deploy on Device Profile Form Deploy an iMG/RGDeploy iMG/RG Profile AlliedView NMS Administration Guide (Configuring Network Services)
Redeploying a Profile Profile Management 6.10.6 Redeploying a Profile There are times when a user needs to re-synchronize the parameters stored in the Profile on the NMS with the configuration of the actual devices or ports in the network. This could be needed after a change is made to the Profile, or when the user wants to reset any temporary changes made to individual ports in the network back to the Profile configuration. To re-apply or re-deploy a profile to the network, follow these steps: 1.
Profile Management Deploying Changes to a Profile FIGURE 6-55 Deploy Port Profile Form - Scheduling 6.10.8 Deploying Changes to a Profile When a Profile is modified on the NMS, any device or port in the network using that profile will no longer be consistent with the Profile on the NMS. When modifying a Profile on the NMS, the NMS will allow the user to have the NMS automatically push the changes in the profile to the objects (devices or ports) in the network to which the profile had been applied.
Keeping the Profile Parameters and Ports/Devices in Sync Note: Profile Management The table used to display the Port Profile usage will be that same table that indicates the Customer ID associated with each port. This panel is named “Configured Ports”. 1. Select the “Ports” panel under the Network Inventory Object. 2. The Ports panel will contain a table that lists the configured ports in the network.
Profile Management Coordination of External and NMS Profiles FIGURE 6-56 ADSL Details - NMS and Interface Profile Whenever a profile is deployed by the NMS to the port, the Interface Profile Name will be set to the port Profile name. Note that there is no other way to change the Interface Profile Name via the NMS.
Coordination of External and NMS Profiles FIGURE 6-58 Profile Management NMS and External Profile Name Match AlliedView NMS Administration Guide (Configuring Network Services) 6-63
Profile Management ADSL G.Bond Creation and use of Profiles 6.10.12 ADSL G.Bond Creation and use of Profiles In release 11.0, there is support for G.bond (ITU G.998) for ADSL interfaces. Note: Refer to the Allied Telesis iMAP User Guide for detailed information on provisioning G.Bond, feature operation, and alarms/performance monitoring. To provision this, there is the profile called ADSLBOND, and it contains references to two regular ADSL profiles, referred to as the Primary and Secondary profiles.
Multiple VC Support on ADSL Port Profile Management 6.10.13 Multiple VC Support on ADSL Port As part of configuring the iMG/RG, there is the option of datafilled multiple VCs for the ADSL connection. This is explained in 7.5.9. 6.10.14 Multiple VC Support on SHDSL Port In NMS release 11.0 SP4, the SHDSL Profile allows the user to configure up to four VCs. 6.10.15 Multiple VC Support on VDSL Port 6.10.15.
Profile Management Multiple VC Support on VDSL Port FIGURE 6-60 VDSL Profile - VCs in ATM Mode When the Transport Protocol is set to PTM the user will receive a warning, as shown in the following figure.
Multiple VC Support on VDSL Port FIGURE 6-61 Profile Management Setting the Transport Protocol to PTM (VDSL Port) After clicking OK, the administrator can go to the VC/VLAN tab and see that there are no VCs, as shown in the following figure.
Profile Management Multiple VC Support on VDSL Port FIGURE 6-62 VC/VLAN Tab when VDSL in PTM Mode The Modify VDSL Profile VC/VLAN tab has two tables, one for the current settings in the profile, and one for putting in changes. This has the same behavior as the Create VDSL Profile, in that the Transport protocol settings alter these tables. Refer to the following figures.
Multiple VC Support on VDSL Port Profile Management FIGURE 6-64 Modify Profile after Mode set to PTM 6.10.15.3 Triple Play Service Management Form The Triple Play Service Management form, VDSL Configuration tab also reflects the multiple-VC provisioning, as shown in the following figures.
Profile Management Multiple VC Support on VDSL Port FIGURE 6-66 FIGURE 6-67 Message if Change Mode to PTM VCs/VLAN tab when in PTM Mode Changes to the View/Modify tabs are done on a per tab basis. As an example, if someone makes changes to the General tab and then makes changes to the VCs/VLANs tab, pressing the “Modify” button will only pick up the current tabs changes. Because of this, an administrator can change the Transport to “ATM” (from “PTM”) and then make changes to the VCs/VLANs table.
Multiple VC Support on VDSL Port FIGURE 6-68 Profile Management Message to Save Protocol Change before changing VC Configuration AlliedView NMS Administration Guide (Configuring Network Services) 6-71
Profile Management DS3 SFP Support 6.10.16 DS3 SFP Support To provide DS3 support, in iMAP release 12.0 the 9000 iMAP devices (except the 9100) add support for a DS3 SFP. (This is currently the MiRICi-T3, which integrates a complete DS3 interface and a Gigabit Ethernet interworking function into the form factor of a standard SFP optics device.) Note: For complete information on the DS3 SFP feature, refer to the iMAP User Guide.
DS3 SFP Support Profile Management FIGURE 6-70 Warning when no Egress Rate Limiter is Set AlliedView NMS Administration Guide (Configuring Network Services) 6-73
Profile Management DS3 SFP Support FIGURE 6-71 Warning When Egress Rate Limiter is Set To provision the DS3 SFP, select an unused Ethernet port (GE or GE8) and select Provision New Customer/Port. The only fields that need to be filled in are the Customer ID and Port Profile, as shown in the following figure.
DS3 SFP Support Note: Profile Management For traffic to flow, both the DS3 and GE interfaces must be operationally up, and any condition that causes one to go operationally down (such as an alarm or being administratively disabled) will cause the other to go operationally down with a failing condition and alarm. Once the port is provisioned, you can review the in the Service Management Details for the port.
Profile Management DS3 SFP Support FIGURE 6-74 6-76 DS3-SFP tab AlliedView NMS Administration Guide (Configuring Network Services)
Changes for the Enterprise Edition Profile Management 6.10.17 Changes for the Enterprise Edition The EE version has most of the features of the Service Provider Edition, except for the following: 6.10.17.1 Customer Management is Removed In the Tools menu the option Customer Management is removed.
Profile Management Changes for the Enterprise Edition 6.10.17.2 Cannot Provision / Deprovision Customer Port from Inventory View The right-click menu in the ports table does not include the Provision and Deprovision Customer/Port. Refer to the following figure.
Changes for the Enterprise Edition Profile Management 6.10.17.3 Cannot Provision / Deprovision iMG / RG (or run MPEG Test) When right-clicking on the iMG/RG in the NMS inventory table, the options to provision or deprovision an iMG/RG, as well as run an MPEG test on the iMG/RG, are not available. Refer to the following figure.
Profile Management Changes for the Enterprise Edition 6.10.17.4 Cannot Provision / Deprovision Customer Port in Port Management Window In the Port Management window, the buttons for provisioning / de provisioning a customer port are removed, with only the button Port available. Refer to the following figure.
Changes for the Enterprise Edition Profile Management 6.10.17.5 No CPE Services Profiles Menu Option For the menu item Network Services - Profile, the CPE Services Profile menu item will not be available, since creating new iMG/RG profiles will not be allowed. Refer to the following figure.
Quality of Service (QoS) Network Management Overview 6.11 Quality of Service (QoS) Network Management 6.11.1 Overview Configuring QoS capabilities on the various iMAP device types is fairly detailed and complex. Since the same QoS configuration is often applied across multiple devices, it is convenient for the network manager to define QoS Policies (configuration information) in the NMS and then separately deploy the policies to a specific set of devices and their ports.
Overview Quality of Service (QoS) Network Management • QoS Policy Flow - A QoS Flow refers to a sub-stream of packets on a port that satisfies a set of classification conditions. For example, a stream of packets classified by the condition that their destination TCP port is 80 (i.e., TCPDPORT=80) is considered a QoS Flow. • QoS Priority Action - A QoS Priority Action is to take a QoS Policy Flow and to prioritize it according to the 802.1 VLAN priority fields or the IP DSCP/TOS fields.
Quality of Service (QoS) Network Management TABLE 6-10 Overview Traffic Management Summary Table - DSL- and TDM-based Cards (Continued) SHDSL24a ADSL 24 ADSL 24AE ADSL 24A/B b VDSL 24A/B NTE8c DROP X X X X X X FORWARD X X X X X X COUNT X X X X X X SETVPRIORITY X X X X X X SETIPTOS X X X X X X SETIPDSCP X X X X X X MOVEPRIOTOTOS X X X X MOVETOSTOPRIO X X X X X X X X Classifier Match Fields Classifier Actions ARP Filtering X X 64 1 1 64 6
Overview Quality of Service (QoS) Network Management j. Classifier capacity is an approximation. The features enabled on a port or interface, such as such as IGMP, DHCPRELAY, VLAN (for per-VLAN UFO and HVLAN), EPSR, INTERFACE (TAGALL option for HVLAN), ACCESSLIST, and CLASSIFIER, classifiers on surrounding ports, content of the user classifiers, and many other factors influence the number of classifiers available on a given port or interface.
Quality of Service (QoS) Network Management TABLE 6-11 Overview Traffic Management Summary Table - Ethernet-based Cards (Continued) - iMAP and SBx3112 Classifier Match Fields Egress Port Rate Limit Increments FE10/ FX10 FX20 GE2 GE3 XE1 GE4/ GE2RJ GE8 EPON2a 1 Mbps 64 Kbps 8 Mbps 1 Mbps 1 Mbps 8 Mbps 1 Mbps (c) GE24POE XE4 8 Kbps 8 Kbps 4 8 4 8 8 4 8 (d) (d) 128 128 1024 128 128 Number of Ingress Traffic Meters 63 256 127 2048 1024 Number of Ingress Traffic Counters 32
Overview Quality of Service (QoS) Network Management specified classifier. When the condition(s) preventing the classifier’s installation is corrected (such as, HVLAN is removed from the port) the classifier will be automatically installed and its status will be updated at the user’s CLI session. • FE2, GE2, FE10, FX10, ADSL24, GE3 - Supports ETHFORMATs of 802.3 and EthII. Note that each of these formats consumes twice as many hardware resources as ETHFORMAT=802.3tagged, 802.
Quality of Service (QoS) Network Management QoS Flows 6.11.2 QoS Flows To create a QoS flow, a set of classifier conditions that is device-specific is defined and given a name. Within this set, multiple parameters can be defined, which create an “AND” condition. To add logical OR’s to the flow definition, another set of classifier conditions is added.
QoS Flows Quality of Service (QoS) Network Management To access the Policy Flow Form, select QoS -> Packet Flow. Table 6-13 describes the fields. Figure 6-81 shows an example QoS Policy Flow Form. TABLE 6-13 Options for the QoS Policy Flow Form Option Purpose Target Device Classes The device classes to be included in this Flow. Set Targets Brings up the Edit QOS Device Class List, allowing the user to select any combination of device classes to include.
Quality of Service (QoS) Network Management TABLE 6-13 QoS Flows Options for the QoS Policy Flow Form Option Purpose Save Flow If a new flow has been defined, an existing been has been changed, or targets have been removed, makes the changes permanent. If the parameters for some device classes are incomplete, a message box will appear with options to Fix, Skip, or Cancel. The Fix button will take you to the in error device class entry.
QoS Priority Action Quality of Service (QoS) Network Management FIGURE 6-81 Sample QoS Policy Flow Form - Rapier 6.11.3 QoS Priority Action To create a set of priority actions (which can be associated with a QoS Flow), one or more priority action parameters are defined and given a name. Note: These parameters can be applied to one or more device classes, as long as they all support the same parameter. If they do not, an error message appears.
Quality of Service (QoS) Network Management QoS Priority Action Table 6-14 lists the allowable actions that can be assigned to a flow.
QoS Priority Action Quality of Service (QoS) Network Management FIGURE 6-82 QoS Priority Action Form - iMAP Device . TABLE 6-15 Options for the QoS Priority Action Form Option Purpose Target Device Classes The device classes to be included in this Flow. Set Targets Brings up the Edit QOS Device Class List, allowing the user to select any combination of device classes to include.Press and Hold the SHift key to select more than one device class.
Quality of Service (QoS) Network Management TABLE 6-15 QoS Traffic Action Form Options for the QoS Priority Action Form Option Purpose Device Class table Table of the Device Classes, Targets, and a description of the device class. Supported indicates there are no detected errors. Priority Action Name A pull-down of all existing actions. If selected, the parameters of the selected action appear in the form. Device Class A pull-down of the device classes that are included in this policy.
QoS Traffic Action Form TABLE 6-16 Quality of Service (QoS) Network Management QoS Traffic Actions for Device Classes Function SwitchBlade Rapier iMAP AlliedWare Plus Ingress Traffic Policing - handling non-conforming traffic - MAXBANDWIDTH RATE METER EXCEEDACTION BUFFERSIZE PBS EXCEEDREMARKVALUE NCDROP NCFORWARD NCREMARKDSCP NCCOUNT Egress Traffic Limiting / Scheduling MAXBANDWIDTH - MINBANDWIDTH RATE CBS BUFFERSIZE CIR FAIRHASHEDFLOWS EBS WEIGHT EIR STATS Congestion Control
Quality of Service (QoS) Network Management FIGURE 6-83 6-96 QoS Traffic Action Form QoS Traffic Action Form - Rapier AlliedView NMS Administration Guide (Configuring Network Services)
QoS Traffic Action Form TABLE 6-17 Quality of Service (QoS) Network Management Options for the QoS Traffic Action Form Option Purpose Target Device Classes The device classes to be included in this Traffic Action. Set Targets Brings up the Edit QOS Device Class List, allowing the user to select any combination of device classes to include.Press and Hold the SHift key to select more than one device class. Targets can also be added/removed by clicking the “Target” checkbox.
Quality of Service (QoS) Network Management QoS Policy Action Form 6.11.5 QoS Policy Action Form The device classes may also have action parameters at the policy/port level. Figure 6-84 shows an example QoS Policy Rule Form. Table 6-18 describes the fields. Note: A policy action can be created that supports an iMAP device with a “None” option.
QoS Policy Action Form TABLE 6-18 Quality of Service (QoS) Network Management Options for the QoS Policy Action Form Option Purpose Target Device Classes The device classes to be included in this Flow. Set Targets Brings up the Edit QOS Device Class List, allowing the user to select any combination of device classes to include.Press and Hold the Shift key to select more than one device class. Targets can also be added/removed by clicking the “Target” checkbox.
Quality of Service (QoS) Network ManagementQoS Policy Maintenance Window (Defining a Policy) 6.11.6 QoS Policy Maintenance Window (Defining a Policy) Once all the attributes for a QoS policy have been created, they are associated to create or define a policy which has a unique name. Note: The names for a Policy can be up to 15 characters and should be lower case. Moreover, underscores and spaces are not allowed. Figure 6-85 shows the QoS Policy Maintenance window.Table 6-19 explains the options.
QoS Policy Maintenance Window (Defining a Policy) TABLE 6-19 Quality of Service (QoS) Network Management Options for the QoS Policy Maintenance Window Option Purpose Target Device Classes The device classes to be included in this Policy. Set Targets Brings up the Edit QOS Device Class List, allowing the user to select any combination of device classes to include.Press and Hold the SHift key to select more than one device class.
Quality of Service (QoS) Network Management FIGURE 6-86 QoS Policy Rule Form Analyze Rules Window 6.11.7 QoS Policy Rule Form To associate a flow, a priority action, and a traffic action the QoS Policy Rule Form is used. This form is accessed on the QoS Policy Maintenance Form by clicking on the Add Rule button. Figure 6-87 shows an example QoS Policy Rule Form. Table 6-17 describes the fields.
Viewing Default Flows, Priorities, Actions, and Policies FIGURE 6-87 TABLE 6-20 Quality of Service (QoS) Network Management QoS Policy Rule Form Options for the QoS Policy Rule Form Option Purpose Target Device Classes The device classes that are included in this policy. This value is read-only. Priority Action Pairs Two pull-downs that have the available Flow Descriptions and Priority Actions. Select one from each to include in the rule. Note that each flow name can only be used once in a policy.
Quality of Service (QoS) Network Management Example of an iMAP Device Class Policy 6.11.9 Example of an iMAP Device Class Policy 6.11.9.1 Overview Figure 6-88 shows a sample QoS configuration for a network, and it has the following attributes: • The types of traffic flows are associated with specific VIDs. • The video Head End uses the VLAN ID (VID) range of 3xx; these are then divided up into regions so that certain VIDS are configured on upstream devices that connect with an iMAP product.
Example of an iMAP Device Class Policy Quality of Service (QoS) Network Management 1. Click on the Network Services menu and select Create/Edit QoS Configuration -> Create/Edit Flows 2. The QOS Policy Flow Dialog window appears. 3. Click on New Flow and enter qos_voice as the New Name, then Select. 4. The Edit QOS Device Class List appears. Select Telesyn only, then Select. 5. The default classifier (ETHFORMAT=ANY) appears in the Flow Classifiers list. Change this as follows: 1.
Quality of Service (QoS) Network Management Example of a Rapier/SwitchBlade Policy 4. Repeat these steps with the BURSTSIZE parameter, selecting the pull-down 32KB. 5. In the pull-down of parameters, select NCCOUNT. The option ON or OFF appears in a pull-down. Select ON. 6. Click on Click Here to Add or Replace Parameter. This adds the NCOUNT parameter to the list. 6. Click on Save Traffic Action and OK to confirm.
Example of a Rapier/SwitchBlade Policy Quality of Service (QoS) Network Management • The user can create the flows, priorities, and actions first, and then in creating the policy create the rules that associate these together. • The user can create a policy first, and then use the Flow Descriptors, Priority Actions, and Traffic Actions buttons to create new flows, priorities, and actions before defining the Rule Table.
Quality of Service (QoS) Network Management FIGURE 6-90 6-108 Example of a Rapier/SwitchBlade Policy QoS Flow for enterprise Policy (CRM server) AlliedView NMS Administration Guide (Configuring Network Services)
Example of a Rapier/SwitchBlade Policy FIGURE 6-91 Quality of Service (QoS) Network Management QoS Flow for enterprise Policy (web_traffic) AlliedView NMS Administration Guide (Configuring Network Services) 6-109
Quality of Service (QoS) Network Management FIGURE 6-92 6-110 Example of a Rapier/SwitchBlade Policy QoS Flow for enterprise Policy (medium_priority_data) AlliedView NMS Administration Guide (Configuring Network Services)
Example of a Rapier/SwitchBlade Policy FIGURE 6-93 Quality of Service (QoS) Network Management QoS Priority for enterprise Policy (high_priority) AlliedView NMS Administration Guide (Configuring Network Services) 6-111
Quality of Service (QoS) Network Management FIGURE 6-94 6-112 Example of a Rapier/SwitchBlade Policy QoS Traffic for enterprise Policy (64K_limit) AlliedView NMS Administration Guide (Configuring Network Services)
Example of an EPON/ONU Interface Policy Quality of Service (QoS) Network Management 6.11.11 Example of an EPON/ONU Interface Policy Creating policies for the EPON/ONU involves the same steps as creating policies for the various device types, but the administrator should understand the EPON/ONU interfaces and how policies work on these interfaces. Note: The user should refer to the iMAP User Guide for complete information about provisioning the components that make up the EPON configuration.
Quality of Service (QoS) Network Management FIGURE 6-95 TABLE 6-22 Example of an EPON/ONU Interface Policy Default EPON and ONU QoS Policies QoS Flows for EPON Interfaces Flow Classifier Parameters IpFilterFlow IPSADDR= Notes &PROTOCOL=IP onuflow TABLE 6-23 ETHFORMAT=ANY QoS Actions for EPON Interfaces Flow Action Parameters EPON_BRUUM MINDOWNSTREAMRATE=1M; Notes MAXDOWNSTREAMRATE=2M; DOWNDELAYSENSITIVITY=TOLERANT DOWNBURSTSIZE=10K EPON_IPMC MINUPSTREAMRATE=0 MAXDOWNSTREAMR
Example of an EPON/ONU Interface Policy TABLE 6-24 Quality of Service (QoS) Network Management QoS Actions for ONU Interfaces Flow Action Parameters ONU_INTERNET MINDOWNSTREAMRATE=0K Notes MAXDOWNSTREAMRATE=4M DOWNDELAYSENSITIVITY=TOLERANT DOWNBURSTSIZE=5K MINUPSTREAMRATE=1M MAXUPSTREAMRATE=2M UPDELAYSENSITIVITY=TOLERANT UPBURSTSIZE=3K ONU_VIDEO MINDOWNSTREAMRATE=20M MAXDOWNSTREAMRATE=512M DOWNDELAYSENSITIVITY=TOLERANT DOWNBURSTSIZE=30K MINUPSTREAMRATE=128K MAXUPSTREAMRATE=256K UPDELAYSENSITIVITY=
Quality of Service (QoS) Network Management TABLE 6-25 Example of an EPON/ONU Interface Policy Default QoS Policies for EPON and ONU Interfaces Policy Flow Priority Action eponbruum IpFilterFlow Allow None AnyOtherIp Deny None AllPackets ONUPriority EPON_BRUUM IpFilterFlow Allow None AnyOtherIp Deny None AllPackets ONUPriority EPON_IPMC IpFilterFlow Allow None AnyOtherIp Deny None AllPackets ONUPriority ONU_VIDEO IpFilterFlow Allow None AnyOtherIp Deny None AllPacke
Example of an EPON/ONU Interface Policy FIGURE 6-97 Quality of Service (QoS) Network Management Example ONU Port Profile Note: The administrator can also create and view QoS policies using the CLI. When policies are created by the AlliedView NMS, they are shown at the CLI with the prefix “NMS_” added and may append an “_a” or “_b” to the name. When policies that are created at the CLI, they appear on the ONU and EPON port details screens with a question mark appended.
Quality of Service (QoS) Network Management Note: QoSPolicies for the FX20 Interface In release 10.0 SP2, the EPON supports VLAN translations. As a result, the translated VLAN ID is also included as part of setting the QOS policies. 6.11.12 QoSPolicies for the FX20 Interface 6.11.12.1 Overview The AlliedView NMS GUI for QoS allows the administrator to configure ingress traffic parameters on the iMAP ports. (Refer to 6.11.1.
QoSPolicies for the FX20 Interface Quality of Service (QoS) Network Management 6.11.12.2 Overview of GUI This feature uses the GUI framework that is used to configure SLA bandwidth parameters for ONU interfaces, as detailed in 6.11.11, but instead of defining QoSPolicies for each VLAN on an ONU, an NMS Policy consists of a set of rules in which each rule maps a queue to a specific traffic action.
Quality of Service (QoS) Network Management FIGURE 6-99 1. QoSPolicies for the FX20 Interface QoSPolicy or FX20 Egress Queues As mentioned in 6.11.12.2, the Traffic Flows are pre-defined and Traffic Priority is not used, so the first step is to create a Traffic Action (or set of Traffic Actions) that will be associated with the queues. • Select Network Services -> QoS -> Actions -> Traffic Action - This brings up the QoS Traffic Action Form.
QoSPolicies for the FX20 Interface Quality of Service (QoS) Network Management • The QOS Traffic Action form appears with its list of attributes. For the FX20 queue, only four are used, so select these and edit the values. Note: Although not necessary, you should delete the other attributes so that only the key attributes are highlighted. Refer to the following figure. • Click on Save Traffic Action, and click OK on the confirmation window.
Quality of Service (QoS) Network Management 2. QoSPolicies for the FX20 Interface With the Traffic Actions created, the QosPolicy (with its set of Rules) can be created. • Select Network Services -> QoS -> Policy - This brings up the QoS Policy Maintenance Form. Note: You can also go to the Network Service data node and select QoS policies -> Actions, and select an existing Policy • Select the New Policy button, and enter the New Policy Name, following the Policy naming conventions.
QoSPolicies for the FX20 Interface 3. Quality of Service (QoS) Network Management Add the rules that will make up this policy. • Select Add Rule under Row Operations. • On the QOS Policy Rule Form, select the Flow as one of the pre-defined queue selections, and Traffic Action as one of the Actions that you created in Step 1. Refer to the following figure.
Quality of Service (QoS) Network Management 5. QoSPolicies for the FX20 Interface The QoSPolicy can now be incorporated into an Ether-like port profile. Refer to the following figure. Caution: The Profile should be given a descriptive name, such as in the figure, to help ensure that this Profile is not included on a Triple_play provisioning form for ethernet ports other than the FX20.
Overview (QoS Deployments Table) Troubleshooting Policies and Profile Management 6.12 Troubleshooting Policies and Profile Management 6.12.1 Overview (QoS Deployments Table) Since QoS Deployment has interrelationships with Profiles and Ports, there are some help procedures to understand these relationships and to use them to troubleshoot problems that may occur. To view the status of policies, there is the QoS Deployments table, which lists the attributes of the policies and their deployment status.
Troubleshooting Policies and Profile ManagementDetermine whether a QoS Policy has the Desired Con- • If, on the other hand, you would like to update the QoS Policy on all devices, the simplest way to force the NMS to redeploy the policy is to modify the QoS Policy definition and resave it. This will cause all deployments of that policy to be flagged with a status of “policy_changed”, which will force all policies to be redeployed on the next Profile deployment.
Redeploying Policies Troubleshooting Policies and Profile Management FIGURE 6-105 Redeploy Policy Clicking on Finish at this point will redeploy the policy for that device. Clicking on Next brings up the Select Deployments form. This allows the user to redeploy a policy to the set of devices that have the policy deployed and to schedule the redeployment. Refer to the following figure. The table includes all the devices that have the policy.
Troubleshooting Policies and Profile Management FIGURE 6-106 6. Redeploying Policies Select Deployments For multiple devices, and to update port parameters as well, locate the affected port Profiles and use the Profiles table to redeploy to all affected devices.
Overview of EPSR Topology Protection Switching-EPSR 6.13 Protection Switching-EPSR 6.13.1 Overview of EPSR Topology In Ethernet-based layer 2 Metropolitan Area Networks (MAN), Spanning Tree Protocol (STP) is normally used to provide redundancy to achieve high availability and continuous access to resources. The iMAP and Allied Telesis Guides explain in detail how STP works and how it is configured. Starting in AlliedView NMS release 4.
Protection Switching-EPSR Overview of EPSR Topology FIGURE 6-107 Example Ring Topologies 6.13.1.3 Summary of EPSR Configuration Data When the network administrator uses the AlliedView NMS GUI to configure an EPSR topology, the following components are involved. These will be explained in more detail as the AlliedView NMS GUI forms are described and an example configuration is created. • Ring Network VLAN - A VLAN in which the VLAN Interface in each device has two tagged linked ports, and forms a loop.
The Network VLAN Manager Application - Configure Control Ring Note: Protection Switching-EPSR Currently, EPSR is the only protection scheme used. • Control Data (part of the TAPS protocol) • HelloTime – The rate at which the protocol Health control message is sent by the master node for this EPSR domain. • FailOverTime – Time for which the master node waits before declaring that it has detected a break in the ring for this EPSR domain.
Protection Switching-EPSR The Network VLAN Manager Application - Configure Control Selecting this option brings up the Configure EPS Control Ring Panel. Click on Create Protection Domain to bring up the Create New VLAN Protection Domain dialog, as shown in Figure 6-110. Note: For AlliedWare Plus devices, which include the SB x908, x900-12X and -24X series, the Protection Domain Name can contain special characters except for percent sign ‘%’.
The Network VLAN Manager Application - Configure Control Ring FIGURE 6-111 Protection Switching-EPSR Creating Control Ring (Apply Protection Domain) The user at this point can change the following attributes of the control ring (refer to Table 6-26). • • • • Interface #1/Primary (whichever one is chosen as the Primary) Is Master Is Enabled EPSR+ - Enhanced Recovery, this is defaulted to the recommended settings, and is disabled if unavailable on the node software release.
Protection Switching-EPSR TABLE 6-26 The Network VLAN Manager Application - Configure Control Fields for the Configuration of the EPS Control Ring Panel Option Purpose Create New Protection VLAN Domain Dialog Protection Domain - The name of the domain that will include all of the devices that are part of the Network VLAN. Naming conventions are up to 15 characters (spaces not allowed). Hello Time and Failover Time - Refer to 6.13.1.3.
The Network VLAN Manager Application - Configure Control Ring Note: Protection Switching-EPSR In release 12.0, the EPSR+ field is included as well. FIGURE 6-112 View EPSR Control Ring Panel The Delete and Modify buttons are now activated. To modify the control ring, the user can choose one of the editable fields (explained in Table 6-26) and select Modify Protection Domain. The task list window will appear as the application changes the Control Ring attributes for each device.
Protection Switching-EPSR The Network VLAN Manager Application - Configure Control 6.13.2.5 Show EPS Control Ring Map Once a valid control ring is configured, selecting the Network VLAN and right clicking on Show (Detached) Map brings up an icon map that shows the devices and links and their associated states. This figure can also be shown by clicking on the Network VLAN under the VLAN Network node. Refer to the following figure.
The Network VLAN Manager Application - Configure Data Ring • • Protection Switching-EPSR LINKS-DOWN is red PRE-FORWARDING is orange 6.13.3 The Network VLAN Manager Application - Configure Data Ring 6.13.3.1 Create/Protect EPS Data Ring Usually, once the EPS Control Ring is created and configured (with its domain), a new EPS Data ring is created.
Protection Switching-EPSR The Network VLAN Manager Application - Configure Data FIGURE 6-115 Creating an EPSR Data Ring by Cloning Control Ring The user fills in the VID and the Vlan Name. The user clicks on OK, and this brings up the Protection Ring Configuration Panel with all columns filled in, as shown in Figure 6-116. If more than one control ring could be applied to the data network VLAN, these will appear in the Possible EPS Ring Protections list. The user should select the one that will be used.
Configuration Guidelines Protection Switching-EPSR Finally, the user selects Configure Protection Scheme. The Task List window appears as the data ring attributes are applied to the devices. The data ring is now included in the protection domain of the associated control ring. Table 6-27 lists the fields of the Configure EPS Data Ring panel.
Protection Switching-EPSR Example Scenario • The ports used for EPSR are gigabit ethernet ports only. • EPSR and other protection schemes (STP/RSTP) are mutually exclusive; ports that use EPSR will have STP disabled. • Ensure that a loop is not created while provisioning the protected VLANs (or ensure that there is no traffic on the protected VLANs until the VLAN is added to the EPSR domain).
Example Scenario Protection Switching-EPSR FIGURE 6-118 Example Spreadsheet 6.13.5.2 Create a Closed Network VLAN that will become the Control Ring Using the Network VLAN Manager, create a new networked-VLAN, as shown in Figure 6-119 FIGURE 6-119 Creating a Network-VLAN to Become a Control Ring In the resulting Initial Vlan Information window, fill in the Control VLAN values, as shown in Figure 6-120.
Protection Switching-EPSR Example Scenario 6.13.5.3 Configure the Control Ring With the network VLAN (Ctrl301) created, use the Network VLAN Manager to configure the Control Ring, as shown in Figure 6-121. Figure 6-122 warns the user about disconnecting unprotected Network VLANs and that STP will be disabled. FIGURE 6-121 Configuring Network VLAN as Control Ring FIGURE 6-122 STP Safety Warning Clicking on Yes brings up the Create New VLAN Protection Domain Dialog.
Example Scenario Protection Switching-EPSR FIGURE 6-123 Creating Control VLAN Domain Clicking on OK, the configuration that will be created is shown in Figure 6-124.
Protection Switching-EPSR Example Scenario FIGURE 6-124 Configuration for Control Ring Panel Clicking on Create Protection Domain invokes the Task Manager, which lists the task being performed for each device. Once the tasks complete successfully, click on the Ctrl301 VLAN IF and the map shows graphically how the control VLAN is configured, as shown in Figure 6-125. Refer back to Figure 6-117 to see how the GUI matches the planned configuration.
Example Scenario Protection Switching-EPSR 6.13.5.4 Create a Data Ring A preferred way to create a Data Ring is to clone the just created Control Ring. In the Network VLAN Manager, select the Control Ring Network VLAN (Ctrl301) and right click on Create/Protect EPS Data RIng, as shown in Figure 6-126. FIGURE 6-126 Creating a Data Ring from an Existing Control Ring The Create New Data Protection Ring Dialog appears, as shown in Figure 6-127.
Protection Switching-EPSR Example Scenario FIGURE 6-128 Configuration for Data Protection Ring Clicking on Configure Protection Scheme brings up the Task window to perform the configuration for each device. Once done, selecting the VLAN IF for prot302 shows the GUI, in Figure 6-129. Compare this to Figure 6-117.
Example Scenario Protection Switching-EPSR FIGURE 6-129 GUI for Configured Protection Data Ring 6.13.5.5 Reconfigure the Control and Data Rings Now that the Control Ring and Data Ring are configured, another device may need to be added to the configuration. Performing this involves combining many of the network services tasks, summarized as follows: • Reconfigure the links between two current devices and the new device. • Delete the link between the current devices.
Protection Switching-EPSR Example Scenario 6.13.5.6 Modify/Unprotect the Data Ring The configured Data Ring can be modified if necessary. Select the Data Protection Ring and select View EPS Data Protection, as shown in Figure 6-129. FIGURE 6-130 View Data Protection Ring The VLAN Protection Scheme panel appears, showing the Domain, Data VIDs, etc, for the Data Protection Network VLAN, as shown in Figure 6-131.
Example Scenario Protection Switching-EPSR FIGURE 6-131 View Protection Ring Configuration At this point the user could select one of the Primary Interfaces and click on Unprotect, as shown in Figure 6-132. FIGURE 6-132 Selecting an Interface on a Device and Unprotect After the Task Details Window had opened and closed, the user could select the VLAN IF and see that the Network VLAN no longer had a protection scheme, as shown in Figure 6-133. Since 11.1 of 68.
Protection Switching-EPSR FIGURE 6-133 Troubleshooting the EPSR Configuration GUI for Network VLAN no Longer with a Protection Scheme 6.13.6 Troubleshooting the EPSR Configuration Using the AlliedView NMS GUI allows the network administrator to more easily understand and resolve the following maintenance scenarios: • The EPS Control and Data rings are not configured properly and so cannot provide the protection service as described in 6.13.
Troubleshooting the EPSR Configuration Protection Switching-EPSR • There is an incomplete loop (usually a missing link or device. In Figure 6-134, a control ring has been configured following the example in Figure 6-117. The .80 device is the master node and the .30 node is a transit node and both are configured (and connected) with the Ctrl300 as the network VLAN. The .20 device is also connected to the ring but is not protected by the Control VLAN Ctrl300. Note that these Ctrl300 labels are in red.
Protection Switching-EPSR Troubleshooting the EPSR Configuration FIGURE 6-136 EPSR Domains table Note that the domain name nms is not included for the .20 device for the Ctrl VID 300. Since the links and VLAN interface do exist (according to the GUI maps), the problem must be that the .20 device is not protected by any EPSR Control ring and is not part of a domain. To resolve this problem, the user can bring up the VLAN Interfaces on .
Troubleshooting the EPSR Configuration FIGURE 6-138 Protection Switching-EPSR GUI when EPSR Activated • Network Inventory - The table now includes the LINK DOWN and FAILED states for domain nms and the changed FORWARDING and BLOCKING states that reflect the VLAN map GUI. FIGURE 6-139 EPSR with FAILED States • Alarms - Viewing the alarms shows all of the associated alarms, as highlighted below.
Protection Switching-EPSR Troubleshooting the EPSR Configuration FIGURE 6-140 6-154 Alarms of EPSR with FAILED state AlliedView NMS Administration Guide (Configuring Network Services)
Troubleshooting the EPSR Configuration Protection Switching-EPSR 6.13.6.3 EPSR Failed (No Ports for Data Flow on Device(s) When both paths are broken there is no data path to or from a device, so data service is lost on that port. In this case, the map GUI and alarms reflect this loss of service situation. • Protection Ring - Both links for device .20 are shown as blocked, so data traffic for this Protection VLAN cannot be received or transmitted on the device.
Protection Switching-EPSR Status of Transit Nodes for AlliedWare Plus Devices FIGURE 6-142 Alarm View for EPSR Failure 6.13.7 Status of Transit Nodes for AlliedWare Plus Devices When AlliedWare Plus devices, which include the SB x908, x900-12X and -24X series, are included in the EPSR ring as Transit Nodes, their state may or may not reflect any changes that may have occurred. This occurs because the devices fail to send a trap when the EPSR state changes.
Overview SuperLoop Prevention (Superring) 6.14 SuperLoop Prevention (Superring) 6.14.1 Overview Prior to release 9.0., if all the following conditions were present, a loop could occur between nodes when the EPSR feature was working correctly: • The network had two or more EPSR domains. • The protected (data) VLAN overlapped two or more EPSR domains. • The EPSR domains and the overlapping protected VLANs shared a common link.
SuperLoop Prevention (Superring) FIGURE 6-143 Overview Example Configuration for SuperLoop Feature Following the example shown in the figure, the user wishes to have one ring at priority 126 and the other at 125. The major steps to create this configuration are as follows: 1. Create the first EPS Ring with a Control VLAN of 710, with a domain name of ctrl710. This is the same as creating an EPS Ring is Section 6.13, but the user specifies Priority=126. 2.
Creating the EPSR SuperRIng SuperLoop Prevention (Superring) At the end of the procedure, all created rings are part of the SuperRing, and any Protected VLANs created on the original ring will be protected by the SuperRing domain. Additional Protected VLANs can be added after the Super-Ring is created by selecting any one of the control ring maps and creating a protected VLAN on it. The NMS will automatically extend that data VLAN to all of the peer domains.
SuperLoop Prevention (Superring) Creating the EPSR SuperRIng FIGURE 6-145 Configure EPS Control Ring Panel The Network VLAN should be highlighted on the left panel. (If not select the loop Network VLAN), then select “Create Protection Domain”. This brings up the Create New VLAN Protection Domain Dialog Form, as shown in the following figure. FIGURE 6-146 Create New VLAN Protection Domain Dialog (Initial) Enter the Protection Domain Name = jptDom710 and the EPSR Priority=126.
Creating the EPSR SuperRIng FIGURE 6-147 SuperLoop Prevention (Superring) Create New VLAN Protection Domain Dialog (Complete) FIGURE 6-148 Create New VLAN Protection Domain (Task List) AlliedView NMS Administration Guide (Configuring Network Services) 6-161
SuperLoop Prevention (Superring) Creating the EPSR SuperRIng The figure above shows the components of the EPSR Domain that are to be created at each node. After the Domain is created, then the VLAN interfaces of the selected loop NVLAN (top left) will be added to the Domain as control VLANs. Click on the “Apply Protection Domain” button to activate the tasks.
Creating the EPSR SuperRIng SuperLoop Prevention (Superring) 6.14.2.2 Create Second EPS Ring that is a Peer of First EPS Ring The steps to create the second, peer EPS Ring are similar to the first. In choosing a looped Network VLAN where there is a shared link with another EPS Ring, the user must put in a non-zero value for the EPSR Priority, and this value must be different than the first ring. Select the Network VLAN and click on Create Protection Domain.
SuperLoop Prevention (Superring) FIGURE 6-152 Creating the EPSR SuperRIng Configuring the Second EPS Ring with Different EPSR Priority Finish by selecting OK, and the system will show how the devices will be configured. The user can change the node which will be Master at this point. Refer to the following figure.
Creating the EPSR SuperRIng FIGURE 6-153 SuperLoop Prevention (Superring) Configure EPS Control Ring Panel for Second Ring FIGURE 6-154 GUI for Second EPS Ring AlliedView NMS Administration Guide (Configuring Network Services) 6-165
SuperLoop Prevention (Superring) Creating the EPSR SuperRIng The VLAN Link from Port 7.5 on Node 10.52.30.37 to Port 9.5 on Node 10.52.30.35 is now a Shared EPSR Link, since it is also a link of Ring jptCtrl710. Since the rings jptCtrl720 and jptCtrl710 share a link and both have priorities greater than 0, they are peers forming a Super-Ring. Also, note that the Transmit Domains are disabled, and they cannot be enabled until the entire SuperRIng has at least one Protected VLAN on it. 6.14.2.
Creating the EPSR SuperRIng FIGURE 6-157 SuperLoop Prevention (Superring) Creating Second Protected VLAN for SuperRing - Warning Fill-in the VID and VLAN Name (for new Protected NVLAN to be created) in the resulting menu FIGURE 6-158 Configuring the Protected VLAN for Control VLAN In the above form enter the VLAN ID and the VLAN name. The form notes that this GUI will create the VLAN interfaces along the same path as the Control VLAN.
SuperLoop Prevention (Superring) FIGURE 6-159 Creating the EPSR SuperRIng Creating the Protection VLAN over multi-EPSR Domains This table displays the components of the Data VLAN that will cause it to be protected by the Domains indicated in the table. Clicking on the “Protect…” button performs the operations on each device to create the jptProt815 NVLAN and put it into the both Peer Domains, jptDom710 and jptDom720, resulting in the following map for jptProt815.
Creating the EPSR SuperRIng SuperLoop Prevention (Superring) 6.14.2.4 Enable the EPS Domains Now that the SuperRing has at least one Protected VLAN on it, the domains can all be enabled. Select one of the control VLANs and on the map select View EPS Control ring, as shown in the following figure. FIGURE 6-161 FIGURE 6-162 View one of the EPSR Control Rings View one EPS Control VLAN (used to enable Protection Domain) Click on the tic boxes under Is Enabled, and then Modify Protection Domain.
SuperLoop Prevention (Superring) Creating the EPSR SuperRIng FIGURE 6-163 FIGURE 6-164 6-170 Protection Domain Enabled Enabled Control VLAN (Part of SuperRing) AlliedView NMS Administration Guide (Configuring Network Services)
Creating the EPSR SuperRIng FIGURE 6-165 SuperLoop Prevention (Superring) Enabled Peer Control VLAN (Part of SuperRing) 6.14.2.5 Adding Protected VLANs to the SuperRing Additional Protected Vlans can be added to Super-Ring by selecting any one of the EPS Rings that make up the SuperRing, as shown in the following figure. FIGURE 6-166 Creating Second Protected VLAN for SuperRing A Warning is given to indicate that the data ring will be extended to multiple domains, as shown below.
SuperLoop Prevention (Superring) FIGURE 6-167 Creating the EPSR SuperRIng Creating Second Protected VLAN for SuperRing - Warning As with the first Protected VLAN, the GUIs lead the user through creating the second Protected VLAN. Note that the Protect Network VLAN Panel shows that all of the nodes of the SuperRing will have the VLAN added, as shown in the following figures.
Creating the EPSR SuperRIng FIGURE 6-169 SuperLoop Prevention (Superring) Task List showing Protected VLAN extends to all Nodes in SuperRing Selecting the Control VLAN in the left panel and then Configure Protection Scheme will take the Second Protected VLAN (816) and extend it over the entire SuperRing. When the Protected VLAN is created and the user clicks on the leaf for VLAN 816, all the nodes of the two EPS Rings are included, as shown in the following figure.
SuperLoop Prevention (Superring) FIGURE 6-170 Creating the EPSR SuperRIng Protected VLAN across Multiple EPS Control VLANs (816) 6.14.2.6 Viewing Network Inventory The Netwrok Inventory View shows the status of the SuperLoop, as shown in the following figure.
Overview Customer Management 6.15 Customer Management 6.15.1 Overview Provisioning services for customers usually involves setting the values of many parameters that vary depending on the type of service customers have requested, the service features to be provided, and the components to be configured. The Network Service applications available using the AlliedView NMS, such as Profiles and Quality of Service Policies, allow ports on the devices to be configured efficiently and without errors.
Customer Management Add New Triple Play Customer - Four Examples 1. POTS24 for analog voice only - This is for an analog phone or modem. 2. POTS24 and ADSL for analog voice and video/data- This is using a Residential Gateway and the ADSL/POTS24 cards. 3. Ethernet - This is using a Residential Gateway and the FE10 card for digital voice and data/video 4. ADSL - This is for analog voice and data.
Add New Triple Play Customer - Four Examples Note: Customer Management In this figure, the underlined numbers in the fields match the Configuration 1 numbers in Figure 6-173. FIGURE 6-174 Triple Play Form - POTS24 Only 6.15.2.2 Configuration 2 - POTS24 and ADSL Card, Analog Phone Only In this configuration, an analog phone, data, and video are provided using an ADSL card and a separate POTS24 card that are combined using the Customer ID. (The POTS24 and ADSL card can be on separate systems if needed).
Customer Management Add New Triple Play Customer - Four Examples [ FIGURE 6-175 Triple Play Form - POTS24 and ADSL Card, Analog Phone Only 6.15.2.3 Configuration 3 - FE10 Card, Digital Phone Only, Video and Data In this configuration, an iMAP 9000 is used, and using the FE card video and data are configured as well as a digital phone. The top and bottom panels are used, with the Gateway for the Derived Voice the IP Address on the Gateway Device.
Add New Triple Play Customer - Four Examples FIGURE 6-176 Customer Management FE10 Card, Digital Phone Only, Video and Data 6.15.2.4 Configuration 4 - ADSL for Data and Analog Phone with Splitter In this configuration, only the top panel is filled out for the data service, since the phone service is split off from the iMAP device and goes to the Class 5 device.
Customer Management Add DS1/E1 Customer FIGURE 6-177 ADSL for Data, Analog Phone with Splitter 6.15.3 Add DS1/E1 Customer This is part of provisioning a CES customer, and brings up the Provision New DS1/E1 Port Form. The fields on this form are explained in 5.6.6. A configuration with example values is shown in 6.16.3. 6.15.
View/Modify Customer Ports Customer Management FIGURE 6-178 Find Subscriber/Ports Form Once the port(s) appear, the user can either double-click a port or select the port and click on View/Modify Details to bring up the relevant Port Management Form, where attributes can be viewed and modified. Note: The View/Modify Details button is enabled when one entry is selected.
Customer Management Deprovision Customer Ports FIGURE 6-179 Ambiguous Use of Customer ID 6.15.5 Deprovision Customer Ports This form allows the user to quickly find the ports/voice lines associated with a subscriber ID and deprovision them. Note: This form can also be accessed from the Port Inventory or Port Management main screen by right-clicking on the relevant port and selecting De-Provision Customer/Port.
Overview (CES8 and iMG6x6MOD Configurations) FIGURE 6-180 FIGURE 6-181 Circuit Emulation Service De-provision Ports Form - ADSL/POTS De-provision Ports Form - DS1 Endpoints (CES) 6.16 Circuit Emulation Service 6.16.1 Overview (CES8 and iMG6x6MOD Configurations) Circuit Emulation is a service that is provided by Allied Telesis using the following: • CES8 card - The CES8 card is used to provide “Pass-thru” Circuit Emulation Service for both E1 and DS1 circuits Note: Refer to 5.5.14 and 5.6.
Circuit Emulation Service CES8 Configuration - Overview of Steps The CES configuration can be either single or dual port; in a dual port configuration both ends of the CES circuit are iMAP DS1/E1 ports managed by the NMS, while in a single port configuration, only one DS1/E1 port is configured on an iMAP device managed by the NMS. • iMG6x6MOD - With the iMG6x6MOD, a circuit emulation service can also be provided. The DS1/E1 port on the iMG can connect to either a CES8 card or another iMG6x6MOD.
Create/Provision CES8 card to Support DS1 Ports (Same Device) Circuit Emulation Service 6.16.3 Create/Provision CES8 card to Support DS1 Ports (Same Device) The following steps are followed to create a connection between two ports on different cards in the same device, In Figure 6-182, this would be the A to A connection. (The B to B connection is for a port that is connected to a port that is outside the managed network.) Note: The two ports can also be on different devices in the same managed network.
Circuit Emulation Service Note: Create DS1 Profile (DS1 and P-SPAN) At this point, the card attribute Ports Type for the General Tab can be changed, but the card would need to be disabled, and there is a warning about the need to disable the card. The Profile can also be changed, and there is a warning that such a change will destroy existing provisioning data. 6.16.
Provision the Two DS1 Ports Circuit Emulation Service FIGURE 6-185 Note: Creating a DS1 Profile (PSPAN tab) If the user has already defined PSPAN Configuration Attributes and Counter Thresholds at the iMAP, the default for these in the Profile is set to False (read only), so they will not be affected. Otherwise, the user could define them here. 6.16.5 Provision the Two DS1 Ports Selecting from the main menu Tools -> Customer Management -> Add DS1 Customer brings up the Provision New DS1 Port Form.
Circuit Emulation Service Provision the Two DS1 Ports FIGURE 6-186 FIGURE 6-187 6-188 Provision a New DS1 Port (Dual Points) Result of Success (Fields Ready for next Customer) AlliedView NMS Administration Guide (Configuring Network Services)
View Provisioning Results Circuit Emulation Service 6.16.6 View Provisioning Results To see the results of the dual endpoint provisioning, go to the Port Management window for the device and sort on Customer ID. Refer to the following figure. FIGURE 6-188 Viewing Dual Endpoints - Same Customer ID This shows that ports 12.4 and 16.5 are the endpoints. By double-clicking on either of these rows, the DS1 Port Management tabbed form appears, and one can view/modify the details of the configuration.
Circuit Emulation Service View Provisioning Results 6.16.6.1 DS1 Port Tab The following figure shows the form that appears when the user double-clicks on port 16.5. The port 16.5 is on the left, since that is the row that was selected; if the user selected 12.4, port 12.4 would appear on the left. The user can change attributes that are part of the Profile, but after clicking on Modify the user would see the Profile with an ‘*” next to it, meaning the Profile is out-of-sync.
View Provisioning Results Circuit Emulation Service 6.16.6.2 PSPAN Tab The following figure shows the PSPAN tab for the two endpoints. As with the DS1 tab, the row selected is the port that appears on the left. The main attributes of the PSPANs are at the top of the form and are read only. The editable attributes are at the bottom of the form. Note, however, that the Peer IP Address and Peer UDP Port are read only since this is a two-port configuration.
Circuit Emulation Service View Provisioning Results 6.16.6.3 PMON Statistics Tab This tab shows the PMON Statistics tab. Refer to the following figure. Note that the table lists the 16.5 and 12.4 Port and PSPAN statistics together. When the user presses the function buttons (Enable, Disable, etc.), they are applied to both ports.
View Provisioning Results Circuit Emulation Service 6.16.6.4 Stats Graph Tab This form makes graphs of the statistics and allows the stats used to be saved as a list and reloaded later. Refer to the following figure. Note: The statistics for each endpoint have the suffix -A or -Z to identify each one. The -A is the port on the left side of the two ports shown at the top of the form, and the -Z is the right side.
Circuit Emulation Service View Provisioning Results 6.16.6.5 Port Thresholds Tab This form allows the user to modify the threshold values for the DS1/E1 and PSPAN statisitcs.When a new value is entered in the New Value field, the Modify button is enabled.
View Provisioning Results Circuit Emulation Service 6.16.6.6 Port Log Tag The following figure shows the Port Log tab for the two endpoints. Note that since these cards are on the same device; there is no need for a device column, and the Device name repeated twice on the top of the form. (If the two endpoints were on different devices, a Device column would be added, and the user could sort by Device.
Circuit Emulation Service Provisioning iMG6x6MOD with T1/E1 Card and CES 6.16.7 Provisioning iMG6x6MOD with T1/E1 Card and CES In release 10.0, it is possible to configure an iMG6x6MOD with a T1/E1 card. This card has two ports, where both are configured as either DS1 or E1 signal formats (for the two T1 or E1 ports respectively). The DS1 configuration (T1) is shown below. At the other end of the DS1 connection, a CES8 port can be configured.
Provisioning iMG6x6MOD with T1/E1 Card and CES Circuit Emulation Service 6.16.7.1 Create RG_CES_DS1 Profiles This has similar attributes to the iMAP CES DS1 profile, except that this will be for a DS1 port on the iMG6x6MOD. Select Network Services -> Profile -> iMG/RG Service Profiles -> Create iMG/RG CES-DS1 Port Profile. Refer to the following figures which show two profiles; each profile could be applied to a different DS1 port on the CES card on the iMG6x6MOD.
Circuit Emulation Service Provisioning iMG6x6MOD with T1/E1 Card and CES FIGURE 6-197 Creating a RG-CES-DS1 Profile - DS1 (15 dB) The following figure shows the PSPAN tab attributes that are datafilled as part of the RG-CES DS profile. The key attributes RTP and Bytes per Packet should match the Peer end. FIGURE 6-198 Creating a RG-CES-DS1 Profile - PSPAN 6.16.7.2 Create an iMG/RG CES Service Profile Select Network Services -> Profile -> Create iMG CES- Service Profile.
Provisioning iMG6x6MOD with T1/E1 Card and CES Circuit Emulation Service Key attributes are: • • • • Ports Type: {DS1/E1} CES VLAN ID - This is used if the Open Access model is being used. See 6.16.7.3. Port 1 RG-CES Port Profile Port 2 RG-CES Port Profile The CES VLAN ID can be specified here to support common CES VLANs across customers. The RG-CES Port Profiles will also be used in the Port Management screens when RG port details are displayed.
Circuit Emulation Service Provisioning iMG6x6MOD with T1/E1 Card and CES 6.16.7.3 Create an iMG/RG General Profile Create an iMG/RG General Profile. This has attributes for provisioning other services on the iMG6x6MOD as well as other iMG/RG types. Note that there is a CES VLAN Id field. If the Access Island model is being used, set the Include Service VLAN in Profile to True, and the VLANs are editable.
Provisioning iMG6x6MOD with T1/E1 Card and CES Circuit Emulation Service 6.16.7.4 Provision the Triple-Play Form As mentioned in 7.2.4, there are different strategies to provisioning the iMG/RG. In this example, the iMG646MOD is already known to the iMAP, and now the Triple Play Form will be filled out and then applied. Refer to the following figure.
Circuit Emulation Service FIGURE 6-202 Provisioning iMG6x6MOD with T1/E1 Card and CES Triple Play Form - Selecting General Profile brings up CES Service Config Selection of the CES Service Profile permits entry of the following parameters.
Provisioning iMG6x6MOD with T1/E1 Card and CES FIGURE 6-203 Circuit Emulation Service Task Panel as iMG646MOD/T1Conpletes 6.16.7.5 Viewing Results Once the iMG646MOD is provisioned, the user can view the details by going to the RG table and selecting View/Modify Details from the pull-down, as shown in the following figures.
Circuit Emulation Service FIGURE 6-205 Provisioning iMG6x6MOD with T1/E1 Card and CES Right Clicking on the iMG646MOD and View/Modify Details The IMG/RG -> Mgmt Info tab now shows the CES VLAN, similar to the other services. FIGURE 6-206 iMG/RG -> Mgmt Info tab The CES Service Tab provides the specific CES parameters and allows the user to view/change the DS1 ports.
Provisioning iMG6x6MOD with T1/E1 Card and CES FIGURE 6-207 Circuit Emulation Service View the CES Service Parameters Selecting the View/Modify CES Port buttons brings up the CES DS1/E1 Port Management Panel, with a different panel for each port, 1 and 2. These tabs allow the user to view and change the parameters if necessary. Refer to the following figures.
Circuit Emulation Service FIGURE 6-208 6-206 Provisioning iMG6x6MOD with T1/E1 Card and CES CES-DS1 Port Parameter Form - Port 2 on the iMG6x6MOD AlliedView NMS Administration Guide (Configuring Network Services)
Provisioning iMG6x6MOD with T1/E1 Card and CES FIGURE 6-209 Circuit Emulation Service CES-DS1 PSPAN Parameter Form - Port 2 on the iMG6x6MOD AlliedView NMS Administration Guide (Configuring Network Services) 6-207
Circuit Emulation Service FIGURE 6-210 6-208 Provisioning iMG6x6MOD with T1/E1 Card and CES CES-DS1 PMON Statistics Parameter Form - Port 2 on the iMG6x6MOD AlliedView NMS Administration Guide (Configuring Network Services)
Provisioning iMG6x6MOD with T1/E1 Card and CES FIGURE 6-211 Note: Circuit Emulation Service CES-DS1 Graph Statistics Parameter Form - Port 2 on the iMG6x6MOD Only the CES8 Stats are currently available in graph format. Use the PMON Statistics tab for iMG statistics.
Circuit Emulation Service FIGURE 6-212 Note: 6-210 Provisioning iMG6x6MOD with T1/E1 Card and CES CES-DS1 Port Thresholds Parameter Form - Port 2 on the iMG6x6MOD Only the CES8 thresholds appear. The iMG does not support thresholds that can be set.
Provisioning iMG6x6MOD with T1/E1 Card and CES FIGURE 6-213 Note: Circuit Emulation Service CES-DS1 Port Log Parameter Form - Port 2 on the iMG6x6MOD Only the CES8 port logs appear. The iMG port does not support the Port Log feature.
Circuit Emulation Service FIGURE 6-214 Note: 6-212 Provisioning iMG6x6MOD with T1/E1 Card and CES CES-DS1 Port and PSPAN Parameter Form - Port 1 on the iMG6x6MOD In the example configuration, the peer end of Port 1 is not managed by the NMS. In this case, the one-sided screens will appear with the iMG supported tabs only.
Provisioning iMG6x6MOD with T1/E1 Card and CES FIGURE 6-215 NTE8 Dual Circuit Provisioning PMON Statistics Form - Port 1 on the iMG6x6MOD 6.17 NTE8 Dual Circuit Provisioning In Release 7.0, the NTE8 card is used to allow DS1/E1 facilities to connect (backhaul) the ethernet network, with both ends of the DS1/E1 connections being on iMAP 9000 devices. Refer to the iMAP User Guide for a complete description of the NTE8 configuration. Note: Refer to 5.5.15 and 5.6.
NTE8 Dual Circuit Provisioning Main Provisioning Steps The NTE8 configuration always has dual endpoints, since there must be an iMAP 9000 device at each end. Moreover, each end must be correctly provisioned for the logical hierarchy (DS1, PPP, MLPP, ETH) of the NTE8. Finally, the hierarchy for each endpoint in a pair must be the same. Configuring an MLPPP interface and its associated ETH interface is less straight-forward than the PPP interface, since the MLPPP can be associated with one or more ports.
Create/Provision NTE8 cards to Support DS1 Ports (Different Devices) 2. NTE8 Dual Circuit Provisioning Select an MLPPP Interface to use for the bundle. Note: The selection is constrained by MLPPP bundle consistency on both ends; once a PPP is associated with an MLPPP, the peer PPP must be associated with the peer MLPPP. This will become clear in the examples. 6.17.
NTE8 Dual Circuit Provisioning Create DS1 Profile FIGURE 6-217 6-216 Viewing DS1 Profile - General Tab AlliedView NMS Administration Guide (Configuring Network Services)
Provisioning one NTE8 Circuit FIGURE 6-218 NTE8 Dual Circuit Provisioning Viewing DS1 Profile - DS1 Thresholds Tab (Note non-0 values) 6.17.4 Provisioning one NTE8 Circuit Selecting from the main menu Tools -> Customer Management -> Add NTE DS1 Customer brings up the Provision New NTE-DS1 Port Form. This is the form where the main task for Provisioning the NTE8 endpoints are done.
NTE8 Dual Circuit Provisioning Provisioning one NTE8 Circuit • When the user clicks on Provision, the task completes, and the user selects Yes to continue data filling the form, the Customer ID field is cleared and the just provisioned ports are no longer available in the Port pull-down. Refer to the following figures. Note: Any specified QoS Policy is applied tot he common Ethernet interface.
Adding PPPs to the MLPPP NTE8 Dual Circuit Provisioning FIGURE 6-220 Result of Success (Fields Ready for next Customer) 6.17.5 Adding PPPs to the MLPPP Once the NTE8 DS1 circuit has been set up, with a PPP and associated MLPPP at each end, the user can add DS1s/PPPs to the existing MLPPPs. By filling out the NTE provisioning forms, the user can ensure the provisioning goes smoothly and the correct parameters are entered. Refer to the following figure while reading below.
NTE8 Dual Circuit Provisioning FIGURE 6-221 6-220 Adding PPPs to the MLPPP Provision New NTE-DS1 Port - Dual PPP AlliedView NMS Administration Guide (Configuring Network Services)
Viewing Provisioning Results - Port Inventory Table NTE8 Dual Circuit Provisioning 6.17.6 Viewing Provisioning Results - Port Inventory Table To see the results of the dual endpoint provisioning, go to the Port Inventory window and sort on the Customer ID. The two ports are placed together since they share the same Customer ID. Refer to the following figure. Note: The user can also go to the Port Management window for the device and sort on Customer ID.
NTE8 Dual Circuit Provisioning Viewing Provisioning Results - Port Details Form FIGURE 6-223 6-222 DS1 Tab for NTE Example AlliedView NMS Administration Guide (Configuring Network Services)
Viewing Provisioning Results - Port Details Form NTE8 Dual Circuit Provisioning 6.17.7.2 PPP Tab The following figure shows the PPP tab for the two endpoints. As with the DS1 tab, the row selected is the port that appears on the left. The main attributes of the PPPs are at the top of the form and are read only. Note that the pull-down for the MLPPP includes the currently configured MLPPP and its connection to its peer MLPPP (MLPPP 21.8).
NTE8 Dual Circuit Provisioning Viewing Provisioning Results - Port Details Form 6.17.7.
Viewing Provisioning Results - Port Details Form NTE8 Dual Circuit Provisioning 6.17.7.4 PMON Statistics Tab This tab shows the PMON Statistics tab. Refer to the following figure. Note that the table lists the 14.0 and 21.0 Port statistics together. When the user presses the function buttons (Enable, Disable, etc.), they are applied to both ports.
NTE8 Dual Circuit Provisioning Viewing Provisioning Results - Port Details Form 6.17.7.5 Stats Graph Tab This form makes graphs of the statistics and allows the stats used to be saved as a list and reloaded later. Refer to the following figure. Note: The statistics for each endpoint have the suffix -A or -Z to identify each one. The -A is the port on the left side of the two ports shown at the top of the form, and the -Z is the right side.
Viewing Provisioning Results - Port Details Form NTE8 Dual Circuit Provisioning 6.17.7.6 Port Thresholds Tab This form allows the user to modify the threshold values for the DS1/E1 and PPP statisitcs.When a new value is entered in the New Value field, the Modify button is enabled. These thresholds are set on the device and when crossed will cause thresholds crossing traps to be sent to the AlliedView NMS. These are displayed in the Event/Alarm tables.
NTE8 Dual Circuit Provisioning Viewing Provisioning Results - Port Details Form FIGURE 6-229 6-228 Port Log Tab for two Endpoints AlliedView NMS Administration Guide (Configuring Network Services)
Viewing NTE8 Endpoints on Physical Map NTE8 Dual Circuit Provisioning 6.17.8 Viewing NTE8 Endpoints on Physical Map Creation of PPP or MLPPP circuits through the NMS (or through CLI, directly) will trigger a discovery process on the devices so that they will know which Device and Port is currently at their far-end. This information is collected during NMS discovery of devices and will generate appropriate links on the Physical and VLAN maps, showing VLAN connectivity.
Upstream Control Protocol (UCP) Display Viewing NTE8 Configuration Faults 6.17.9 Viewing NTE8 Configuration Faults When the NTE8 configuration is set up and running, faults can be generated on four components: • • • • NTE8 Card DS1/E1 port (such as LOS, LOF, Receiving AIS, etc.) PPP (Configuration Failure, Peer Disabled, etc.) MLPPP Note: Refer to the iMAP User Guide for a complete description of these faults, and the iMAP Log Manual for a complete list of alarms.
VLAN Submap Display Upstream Control Protocol (UCP) Display • VLAN type (STD or Upstream) • UCP Node Type (Primary, Secondary, Primary and Secondary, Upstream, Non-Upstream) • UCP status (active, standby) Node types are updated using SNMP traps from the relevant devices. 6.18.1 VLAN Submap Display Each VLAN interface on a VLAN submap has a UCP Node-type label on top of the VLANIF symbol that can be one of the following for i MAP 6.
Upstream Control Protocol (UCP) Display FIGURE 6-233 Events View (Change of State) UCP Status in the Network Inventory Table for the VLAN Interfaces (Highlighted) 6.18.3 Events View (Change of State) When the active/standby status of the Primary/Secondary Node changes (because of failures in the network or administrative changes), SNMP traps are sent from the device indicating a state change. In the Events view, they appear as Info status events.
Events View (Change of State) Link Discovery 6.19 Link Discovery For VLAN-related features of the NMS, such as the VLAN topology maps, EPSR, and UPC features, the NMS depends on accurate link information to piece together the broadcast domain for each extended VLAN. The LLDP protocol is a feature on devices and this provides the information needed by the AlliedView NMS to provide the GUI for Link Discovery. This subsection describes these interfaces and the specific functions Link Discovery.
Software Upgrade with EPSR Overview 6.20 Software Upgrade with EPSR 6.20.1 Overview Section 5.3.9 explains the software download application and how it can be used to control the download process for one or more devices and prevent errors. A special situation occurs when the devices are part of an EPSR configuration, because the order in which the devices are downloaded will prevent service outage.
Upgrading all Nodes for an EPSR Ring Software Upgrade with EPSR FIGURE 6-235 Physical Map showing Ring Configuration FIGURE 6-236 EPSR - Control VLAN over Physical Links AlliedView NMS Administration Guide (Configuring Network Services) 6-235
Software Upgrade with EPSR Upgrading all Nodes for an EPSR Ring FIGURE 6-237 EPSR - Data VLAN over Physical Links In the physical map, the user could highlight the three devices, right click and select Software Configuration. This would bring up the Software configuration with all three devices included, as shown below. FIGURE 6-238 Devices Chosen for Software Upgrade The user would select all three devices and click on the now active Modify Release Configuration button.
Upgrading all Nodes for an EPSR Ring FIGURE 6-239 Software Upgrade with EPSR Modify Device Software Configuration Window - Select Load for Multiple Devices When the user selects Next, the AlliedView NMS checks the EPSR configuration and, using the configuration rules listed above, determines the order in which the devices should be loaded.
Software Upgrade with EPSR Upgrading One Node that is part of an EPSR Configuration FIGURE 6-240 FIGURE 6-241 Resolving Conflicting VLAN Sets Selecting a VLAN to ignore during Upgrade 6.20.3 Upgrading One Node that is part of an EPSR Configuration In the previous example, the EPSR configuration included three devices, and all three devices were selected for a software upgrade.
Upgrading One Node that is part of an EPSR Configuration Software Upgrade with EPSR • Additional EPSR Successor Nodes Detected - A successor node must be included in the upgrade procedure. The user should ensure all the listed devices are checked and select Next. • Additional EPSR Predecessor Nodes Detected - A predecessor node must be included in the upgrade procedure. The user should ensure all the listed devices are checked and select Next.
Software Upgrade with EPSR FIGURE 6-243 Upgrading Devices when EPSR not Properly Configured Select Additional Predecessor Devices to Upgrade 6.20.4 Upgrading Devices when EPSR not Properly Configured If EPSR has been improperly configured and the user selects one or more devices to upgrade, a GUI with an error message appears that warns the user that if the error is not fixed the configuration will fail or data service may be disrupted. Refer to the following figure.
Network VLANs Diagnostic Audit FIGURE 6-244 Error Condition for Upgrade 6.21 Diagnostic Audit The NMS provides the capability to run diagnostic audits on certain network entities. Currently, the entities that can be audited are: • Network VLANs • CES Circuits Audits are started from the “Diagnostic Audit Reporting” window, which can be launched from various menus within the NMS. The appropriate Audit Entity IDs will appear in the window, based on the menu from which it was launched.
Diagnostic Audit Network VLANs FIGURE 6-245 Audit Selection for Network VLAN Selecting the Audit VLAN menu item brings up the Diagnostic Audit screen with the selected VLAN, as shown in the following figure. FIGURE 6-246 Diagnostic Audit Panel The Run Audit button starts the audit and resulted in the following audit report.
Network VLANs Diagnostic Audit FIGURE 6-247 Example Audit Report AlliedView NMS Administration Guide (Configuring Network Services) 6-243
Diagnostic Audit Audit the CES Circuit on the iMG6x6MOD or CES8 Card 6.21.2 Audit the CES Circuit on the iMG6x6MOD or CES8 Card A similar audit capability is provided for CES Circuits.
Audit the CES Circuit on the iMG6x6MOD or CES8 Card FIGURE 6-249 Diagnostic Audit CES Circuit Audit Panel The Run Audit button starts the audit and results in the following audit report.
Diagnostic Audit Audit the CES Circuit on the iMG6x6MOD or CES8 Card FIGURE 6-250 6-246 Results of Running CES Audit AlliedView NMS Administration Guide (Configuring Network Services)
Port Authentication for a Device Port Authentication (802.1x) 6.22 Port Authentication (802.1x) The main components of Port Authentication are: • The Authenticator - the port on the SBx3112 that wishes to enforce authentication before allowing access to services that are accessible behind it. The SBx3112 plays this role. • The Supplicant -the user device attached to the Authenticator that wishes to access services offered by the authenticator's system.
Port Authentication (802.
Port Authentication for a Device Port Authentication (802.1x) The Port_Auth_Mgmt screen appears, with device information and a set of tabs, one for Port Authentication and one for Radius. Refer to the following figures. Note that for AlliedWare Plus devices, this is a new window in release 12.3.
Port Authentication (802.1x) FIGURE 6-254 Profiles with the Port Authentication Feature Port Authentication Configuration - AlliedWare Plus Device 6.22.2 Profiles with the Port Authentication Feature To configure Port Authentication for a port, the Profiles can be used so that the feature is automatically enabled when the port is brought into service. The following Profiles include Port Authentication.
Profiles with the Port Authentication Feature FIGURE 6-255 Port Authentication (802.1x) Profile for Port Authentication for iMAP (SBx3112) The Profile itself has a Port Authentication tab, with options for 802.1x and MAC Authentication. For AlliedWare Plus devices, there is the added field Radius Group, when a set of Radius servers are combined with a group label. (If there is not a group, the label “Radius” is filled in.). Refer to the following figure.
Port Authentication (802.1x) FIGURE 6-256 6-252 Profiles with the Port Authentication Feature Profile for Port Authentication - SBx3112 for NMS 12.
Etherlike Port Profile FIGURE 6-257 Port Authentication (802.1x) Profile for Port Authentication - AlliedWare Plus Devices for NMS 12.3 (Includes MAC Authentication) 6.22.3 Etherlike Port Profile With this Profile the Port Authentication tab is used, and it provides the attributes needed to activate Port Authentication. (Refer to device specific documents, such as the SBx3112 Software Reference manual, for details on these fields.) Refer to the following figure.
Port Authentication (802.1x) FIGURE 6-258 Feature Support (AlliedWare Plus and iMAP Devices) Profile for Etherlike Port - Port Authentication 6.22.
Implementing Port Authentication with Triple-Play Port Authentication (802.1x) • Roaming – to be able to move supplicant to other port not re-authentication • Supplicant Mac – enable port auth specified MAC address • Keytransmit – transmit 802.1x authentication key These items are not in the profiles nor in the view/modify screen, as explained below. For settings that are common between the AlliedWare Plus devices and iMAP devices (the SBx3112), there are some differences in the settings, as listed below.
Port Authentication (802.1x) FIGURE 6-259 Note: Implementing Port Authentication with Triple-Play Service Management Form - Port Authentication Active Once Port Authentication is enabled (by setting to Enabled at both device and port), you cannot add or delete a VLAN on that port. The following type of error is seen in the console window when modifying a VLAN on a port (via view/modify the port or deploy/apply the port profile): delete VLAN=40 interface=1.2 Processing.....
7. Provisioning the iMG/RG 7.1 Overview The SE version of this document includes all iMG-related information. 7.1.1 Roadmap for this Section Use this table as a reference for this Section. TABLE 7-1 Provisioning the iMG/RG in Release 12.0 Provisioning Component Section Network Modeling (Access islands, open Access, Multi-Service VLANs 7.2.2 iMG/RGs Supported 7.2.3 Provisioning Strategies 7.2.4 DHCP 7.2.5 Remote ID for iMAP device 7.2.6 Customer ID Naming 7.2.
Provisioning Strategy Main Concepts (Profiles, Triple Play Form, DHCP Discovery) 7.2 Provisioning Strategy 7.2.
Deployment Models (Access Islands, Open Access, multi-service VLANs) Provisioning Strategy For each service provider’s wiring center exchange, there can be a Provider Edge-Access Network (PE-AN), and these can be divided into Multi-service Access Island Networks. These Access Islands are basically one leaf of the larger network, and can be the initial configuration when a small number of RGs are initially deployed.
Provisioning Strategy Deployment Models (Access Islands, Open Access, multi- 7.2.2.2 Multiple ISPs (Open Access) In networks where there are multiple service providers for various services, each VLAN may be used for a service type and ISP. The result is a set of VLANs for each service type, as shown in the following figure. Refer to 7.9 for details on the multiple ISP configuration. FIGURE 7-2 Note: The default is the Access Island model. iMG634 = 10.56.7.224 FXS = IP Subnet FXS = 172.16.33.
Deployment Models (Access Islands, Open Access, multi-service VLANs) Provisioning Strategy 7.2.2.3 VLANs Providing more than one Service A VLAN can also be configured to support more than one service. The following figure shows an example of this. = video VLAN (VID 40) = IP Subnet = shared (voice, data) VLAN (VID 10) iMG646PX-ON = 10.56.7.223 ONU 4.0.0 ETH 4.0.0 FXS FXS Ethernet Data to PC 10 10 EPON = 172.16.33.
Provisioning Strategy iMG/RG Types Supported 7.2.2.4 Provisioning the iMG7x6MOD This type of iMG is highlighted because of the flexibility in provisioning both the WAN and LAN cards. Refer to the following figure.
Provisioning Strategies Provisioning Strategy 7.2.4 Provisioning Strategies The main tasks involved in provisioning the iMG/RG are: 1. Setting up the DHCP configuration. This is done on DHCP server(s) and iMAPs, and is done at initial iMAP installation. 2. Creating Profiles. This is done upon initial setup of the iMAPs that participate in the Access Island. Note: Items 1 and 2 only need to be done once. The remaining tasks are done for each customer using an iMG/ RG. 3.
Provisioning Strategy Configuring Components for DHCP Discovery 7.2.5 Configuring Components for DHCP Discovery 7.2.5.1 Overview For the RG to be discovered using DHCP, the user must configure the following tools and files correctly. Note: For the iMG/RGs to use DHCP correctly, all iMAPs must use DHCP Relay, not DHCP Snooping. Refer to the Allied Telesis Software Reference Manual for details on the differences between the two types of DHCP.
Configuring Components for DHCP Discovery Provisioning Strategy • The Messages area only displays the processing log. The configuration summary is only displayed in the Summary tab • The release 4 tab is for the NextGen iMGs Refer to the following figures and tables.
Provisioning Strategy FIGURE 7-7 7-10 Configuring Components for DHCP Discovery iMG/RG Boot Load Configurator Tool - Release 2 (and Release 3) AlliedView NMS Administration Guide (Provisioning the iMG/RG)
Configuring Components for DHCP Discovery TABLE 7-2 Provisioning Strategy RG/iMG Boot Load Configurator Tool - Release 2 and Release 3 Tabs Attribute Value Mgmt VLAN ID The VLAN identifier that will be placed into the im.conf file. This is the final RGMgmt vlan which the RG will use while it is in service for a particular customer in a particular access island. (If the same customer moves and takes the RG it will not work if the new residence is not serviced from the same Access Island.
Provisioning Strategy TABLE 7-2 Configuring Components for DHCP Discovery RG/iMG Boot Load Configurator Tool - Release 2 and Release 3 Tabs Attribute Value Messages Messages show the progress and status of each load creation. The initial messages include the path to the software repository (where the zip files reside), the path to the TFTP server root (where the loads will be placed), and a summary of any existing loads already residing in the TFTP directory tree.
Configuring Components for DHCP Discovery FIGURE 7-8 Provisioning Strategy iMG/RG Boot Load Configurator Tool - Release 4 (NextGen iMG) AlliedView NMS Administration Guide (Provisioning the iMG/RG) 7-13
Provisioning Strategy TABLE 7-3 Configuring Components for DHCP Discovery RG/iMG Boot Load Configurator Tool - Release 4 Tab Attribute Value Mgmt VLAN ID The VLAN identifier that will be placed into the im.conf file. This is the final RGMgmt vlan which the RG will use while it is in service for a particular customer in a particular access island. (If the same customer moves and takes the RG it will not work if the new residence is not serviced from the same Access Island.
Configuring Components for DHCP Discovery TABLE 7-3 Provisioning Strategy RG/iMG Boot Load Configurator Tool - Release 4 Tab Attribute Value OK The OK button creates the load from the parameters entered and also creates a new MD5SUM file for all the files in the load. After successfully creating one load, additional loads can be creating by editing the parameters and selecting OK repeatedly. Close Exits the tool.
Provisioning Strategy Configuring Components for DHCP Discovery Note 1: The VLAN VID is in decimal and the value in the DHCP server in this example mst be in HEX, i.e.
Configuring Components for DHCP Discovery Provisioning Strategy 7.2.5.4 DHCP Relay Configured on the iMAPs (VLAN Configuration) The DHCP Relay configuration in the iMAP associated with the RG must be data filled so that DHCP instances match the correct IP address for the DHCP server and are associated with the correct VLAN. The iMAP should be provisioned with at least two DHCP relay instances where data service VLANs (like RGBootstrap, RGVoice, Video, Internet VLANs) are in one relay instance (e.g.
Provisioning Strategy Configuring Components for DHCP Discovery The iMAP should be provisioned with a unique DHCP “Remote ID” so that the DHCP server can clearly identify where DHCP messages are coming from. Refer to 7.2.6 for an overview of naming conventions that should be followed so that administrators can easily label and configure the iMG/RG configuration. Caution: Ensure that DHCP Relay is enabled on the iMAP network (upstream) interfaces, as well as the interfaces to the iMG/RG.
Configuring Components for DHCP Discovery Provisioning Strategy ip pim dr-priority 100 ip pim sparse-mode passive ip dhcp-relay agent-option ip dhcp-relay information policy replace ip dhcp-relay server-address 10.52.201.36 ! interface vlan601 //internet ip address 10.52.110.241/28 ip dhcp-relay agent-option ip dhcp-relay information policy replace ip dhcp-relay server-address 10.52.201.
Provisioning Strategy Naming Conventions to Identify Components (DNS) 7.2.6 Naming Conventions to Identify Components (DNS) 7.2.6.1 Overview The DNS naming conventions for components are extremely important for administrators because they help in allowing services to be delivered to subscribers within a specific Access Island. Note: When dynamic DNS services are required (as in the case of the G6) the voice DHCP server must be separate from the rgboot/rgmgmt.
Naming Conventions to Identify Components (DNS) TABLE 7-5 Provisioning Strategy Recommended Naming Convention for Remote ID of iMAP for DHCP Attribute Value nnnn.... Characters that help identify the device and any attributes for its location, type, etc. Examples iMAP 1 9700 = SPSI-AI00-MAP1x7 iMAP 2 9400 = SPSI-AI00-MAP2x4 iMAP 5 9810 = SPSI-AI00-MAP5x8 x3112 NCSU = SPSI-AI00-x3112-NCSU With the domain suffix of “ai.corp.int”: The fully qualified name for the first iMAP would be: SPSI-AI00-MAP1x7.
Provisioning Strategy Naming Conventions to Identify Components (DNS) 7.2.6.5 Detailed steps for DHCP Discovery Refer to Figure 7-9 for the first four steps for DHCP discovery. FIGURE 7-9 DHCP Discovery - Bootstrap VLAN 1. The RG powers up and sends a DHCP discover message over the untagged VLAN for its port. 2. The iMAP adds the Remote ID, slot.port, and VID information to the circuit ID and forwards the DHCP discover message to the DHCP server over the inband iMAP Management interface.
Naming Conventions to Identify Components (DNS) FIGURE 7-10 Provisioning Strategy DHCP Discovery - Management VLAN 6. The DHCP server provides the new IP address. 7. The AlliedView NMS uses DHCP Listener to discover the RG (its IP, and Circuit ID attributes such as MAC) in the RGMgmt VLAN. 8. The AlliedView NMS telnets to the RG, and using CLI it configures the RG and saves this to FLASH on the RG. 9. The user should then connect the LAN devices.
Provisioning Strategy Naming Conventions to Identify Components (DNS) Refer to the following figure, which shows what must be configured and how the process works. Before VoIP can work, the following must have already been done, or voice service will not work: 1. Profiles have been filled out correctly to support voice service. In particular, in the Voice profile for the RG, the voice domain name must be filled out, and the voice VLAN that is filled in for the RG General profile has already been created.
Naming Convention for Customer IDs (Triple Play Form) Provisioning Strategy 1. The AlliedView NMS puts together the FQDN for the RG voice interface (i.e. rgvoip-.domain) and the port of the iMAP (as _slot.port). The AlliedView NMS also adds the line entries that were filled out in the Triple-Play form. 2. The AlliedView NMS configures each voice line that has been set up for the RG (creates the voice VLAN, creates the voice IP interface, enables DHCP) 3.
Provisioning Strategy Changing Customer IDs To change the customerID, the administrator must change the customerID for all three types; this is done by changing the CustomerID for all three areas on the Triple-Play Service Management form. Refer to 6.15.4 and 7.10.10.
Changing Customer IDs Viewing iMG/RG on the AlliedView NMS 7.3 Viewing iMG/RG on the AlliedView NMS Once the iMG/RGs have been provisioned, they can be viewed in various ways that allow the administrator to track their configuration and their status. Figure 7-12 shows the physical node, with the iMAPs grouped according to their Access Island. Note the following: • The IDs of the iMAPs follow the naming convention explained in 7.2.6.
Viewing iMG/RG on the AlliedView NMS FIGURE 7-13 7-28 Changing Customer IDs iMG/RG Inventory View Sorted by Upstream Port AlliedView NMS Administration Guide (Provisioning the iMG/RG)
Overview Creating RG Profiles with Field Descriptions 7.4 Creating RG Profiles with Field Descriptions 7.4.1 Overview 7.4.1.
Creating RG Profiles with Field Descriptions FIGURE 7-14 7-30 General Profile RG General Profile - Mgmt Info AlliedView NMS Administration Guide (Provisioning the iMG/RG)
General Profile Creating RG Profiles with Field Descriptions FIGURE 7-15 RG General Profile - Mgmt.
Creating RG Profiles with Field Descriptions TABLE 7-7 General Profile Create RG General Port Profile Form - Mgmt InfoTab Attribute Value Profile Name A descriptive name that should match the service/function provided The prefix of profile name should start with a short but meaningful name that indicates the routing function and the Access Island and the service potential of the general profile, with the number of ports. Refer to 7.4.1. This is used for scoping.
General Profile TABLE 7-7 Creating RG Profiles with Field Descriptions Create RG General Port Profile Form - Mgmt InfoTab (Continued) Attribute Value New Limited User Password Password for the Limited User New Manager Password Password for the user that the AlliedView NMS uses when it provisions the device. The userID is part of AlliedView NMS, has super user privileges, and cannot be changed. Super User Login The super user that can be created and changed by the administrator.
Creating RG Profiles with Field Descriptions FIGURE 7-16 General Profile RG General Profile - Wireless Tab The wireless tab allows the iMG634WA/WB to be configured, and uses the standard wireless parameters.
General Profile Creating RG Profiles with Field Descriptions FIGURE 7-17 RG General Profile - Port Assignment Tab AlliedView NMS Administration Guide (Provisioning the iMG/RG) 7-35
Creating RG Profiles with Field Descriptions TABLE 7-8 General Profile Create RG General Port Profile Form - Port Assignment Tab Attribute Value Port Assignments The selection made here controls which fields appear on the Provision New Triple Play Customer form. Settings - Port assignments will not be displayed when provisioning a new customer. The values as set in the profile will be used.
General Profile TABLE 7-8 Creating RG Profiles with Field Descriptions Create RG General Port Profile Form - Port Assignment Tab Attribute Value Advanced Port params Brings up specific features: - Disable on Power Failure feature for the port. Refer to 7.15.2. - Flow Control - Refer to 7.16 - DSCP Status - Enables the support of DSCP IP field on the incoming frames. Refer to the Allied Telesis Gateway Software Reference Manual, command SWITCH SET SUPPORT DSCP.
Creating RG Profiles with Field Descriptions TABLE 7-9 RG Internet Profile Create RG General Port Profile Form - IP Routes Tab Attribute Value IP Route IP Routes that are available for the RG The user should always create a route to the “back office” management subnets. (The AlliedView has one as well that is unavailable to the user.) Enabled Activates the other IP Route Fields Subnet Subnet address Mask Mask over the subnet address, usually 255.255.255.
RG Internet Profile Creating RG Profiles with Field Descriptions • Session Chaining - Some applications spawn their own secondary sessions. This process is known as session chaining. When secondary sessions are successfully established, the source/destination addresses of the session will also be added to the table of currently open primary sessions. • Firewall - The Firewall feature ensures that only traffic that has been already defined is allowed to access the internal network.
Creating RG Profiles with Field Descriptions FIGURE 7-19 7-40 RG Internet Profile iMG/RG Internet Profile - General Tab AlliedView NMS Administration Guide (Provisioning the iMG/RG)
RG Internet Profile TABLE 7-10 Creating RG Profiles with Field Descriptions Create RG Internet Port Profile Form Attribute Value Profile Name A descriptive name that should match the service/function provided. Note: Profiles that use the Access Island (AI) concept have the ‘Include Internet VLAN in Profile’ set to False. For the Open Access (OA) model, the field is set to True and a VLAN number can be entered in the ‘iMG/RG Internet VLAN ID’ field (2..
Creating RG Profiles with Field Descriptions TABLE 7-10 RG Internet Profile Create RG Internet Port Profile Form Attribute Value iMG/RG Local Customer VLAN Id VLAN that is local to the RG only Use DHCP to Obtain WAN IP Address If True, use DHCP Discovery to obtain the network-side IP address for the RG. If False, static IP provisioning and IP/masks must be manually entered.
RG Internet Profile Creating RG Profiles with Field Descriptions 7.4.3.3 Security Tab This tab controls whether the Security System and its subsystems will be enabled, and if so, the attributes for these subsystems. Therefore, the user should note that if the Security is set to Disabled, the fields to Enable Firewall and NAT in their tabs are disabled. Refer to the following figures.
Creating RG Profiles with Field Descriptions TABLE 7-11 RG Internet Profile Create RG Internet Profile Security Tab Attribute Value Triggers A set of attributes that allows an application to open a secondary port to transport packets. A trigger opens a secondary port dynamically, and allows you to define the length of time the port can be inactive before it is closed. - Trigger Name - a label that helps identify the trigger. It cannot start with a digit.
RG Internet Profile Creating RG Profiles with Field Descriptions 7.4.3.
Creating RG Profiles with Field Descriptions FIGURE 7-22 7-46 RG Internet Profile RG Internet Profile - Firewall Tab -Port Filters Attributes AlliedView NMS Administration Guide (Provisioning the iMG/RG)
RG Internet Profile Creating RG Profiles with Field Descriptions FIGURE 7-23 TABLE 7-12 RG Internet Profile - Firewall Tab -Validators Attributes Create RG Internet Profile Firewall Tab Attribute Value Firewall Whether the feature is Enabled or Disabled. This option is activated only for Routed Service. Note: Include Firewall Info as part of Profile Security does not have to be enabled to enter IDS and Port Filters. Whether IDS and Port Filters are included in the profile.
Creating RG Profiles with Field Descriptions TABLE 7-12 RG Internet Profile Create RG Internet Profile Firewall Tab Attribute Value IDS parameters Whether IDS is Enabled or Disabled. If Enabled, the IDS Parameters window is activated. Note: IDS parameters can be datafilled and enabled regardless of whether the FIrewall feature is enabled, since IDS applies to the iMG/RG, and is not associated with specific Firewall attributes.
RG Internet Profile TABLE 7-12 Creating RG Profiles with Field Descriptions Create RG Internet Profile Firewall Tab Attribute Value Validators - Blocks the traffic to/from the IP addresses/masks defined. All other traffic is allowed. - Validator Name - A label to help identify the validator. It cannot start with a digit.
Creating RG Profiles with Field Descriptions RG Internet Profile 7.4.3.5 NAT Tab The NAT form allows you to set up static ip address/port mappings to the local address space. FIGURE 7-24 TABLE 7-13 RG Internet Profile - NAT Tab Create RG Internet Profile NAT Tab Attribute Value NAT Whether the feature is Enabled or Disabled. This option is activated only for Routed Service. IKE Translation Specifies how Internet Key Exchange Packets are translated.
Video Profile Creating RG Profiles with Field Descriptions 7.4.
Creating RG Profiles with Field Descriptions TABLE 7-14 Video Profile Create RG Video Port Profile Form Attribute Value Profile Name A descriptive name that should match the service/function provided Example Names: • Flood - This would match the NONE for IGMP Mode (IGMP Snooping turned off) • Snoop (646 and 656) - Note that all RG600 series RG/IMG will support snooping in the next sw release. • Proxy - The RG performs the IGMP function.
Voice Port Profile TABLE 7-14 Creating RG Profiles with Field Descriptions Create RG Video Port Profile Form Attribute Value IGMP Security Enabled or Disabled When “learning” is enabled the RG will only allow those trusted hosts (STB) if specified in the Triple Play screen to participate in IGMP (ask for broadcast channels When “autolearning” is enabled as well as “learning” the RG when booting up will automatically learn “X” number of trusted hosts (STB) as specified in the video profiles “trusted h
Creating RG Profiles with Field Descriptions FIGURE 7-26 Voice Port Profile RG Voice Port Profile (MGCP) FIGURE 7-27 7-54 RG Voice Port Profile (SIP) AlliedView NMS Administration Guide (Provisioning the iMG/RG)
Voice Port Profile TABLE 7-16 Creating RG Profiles with Field Descriptions Create RG Voice Port Profile Form Attribute Value Profile Name A descriptive name that should match the service/function provided The prefix of profile name could include the string that identifies the Access Island as well as the service potential, such as: SPSI-AI01-UpTo4Line Note: Profile Scoping VOIP Type The user would give this name to the profile because it would have four voice lines filled in; if the user had one
Creating RG Profiles with Field Descriptions TABLE 7-16 Voice Port Profile Create RG Voice Port Profile Form Attribute Value Advanced VOIP Params Sets attributes for RTCP (Control parameters for RTP) or SIP. Also includes the type of MGCP/SIP to be used in the Profile: iMG/RG MGCP Profile (for example Genband) iMG/RG Admin Profile (for example Sonus) This is where the LCFO option is added. Refer to 7.13.
Voice Port Profile TABLE 7-16 Creating RG Profiles with Field Descriptions Create RG Voice Port Profile Form Attribute Value Create Activated when a Profile Name has been typed, it creates the profile with the entered values. Cancel Closes the window FIGURE 7-28 Advanced Line Attributes - SIP (Arrows for 12.
Creating RG Profiles with Field Descriptions Business Group ID for SIP 7.4.6 Business Group ID for SIP The concept the Business Group ID for SIP is specific to Lucent and Sonus. To configure this ID, access the iMG/RG -> Voice Service Tab. If the user chooses the Voip Type as SIP, and then under Advanced VOIP Attributes chooses the iMG/RG Admin. Profile as Lucent or Sonus and clicks on Done, the New Line Configuration table will now include the Bus. Group ID. Refer to the following figure.
Overview Basic Configurations with Sample Profiles 7.5 Basic Configurations with Sample Profiles 7.5.1 Overview The following descriptions isolate each service. In most cases services are bundled, but describing each service and its specific Profile(s) allows key fields/values to be highlighted.
Basic Configurations with Sample Profiles Transparent LAN Service (TLS) 7.5.2 Transparent LAN Service (TLS) Most commonly, TLS is used to join two sites (usually of a business) through the upstream switches of the RGs. This is an Ethernet transport service, at layer 2. Note that data must be untagged. Refer to Figure 7-30. FIGURE 7-30 TLS Configuration The following screen examples show the sample profiles included with the AlliedView NMS and what they contain .
Transparent LAN Service (TLS) Basic Configurations with Sample Profiles FIGURE 7-31 FIGURE 7-32 RG General Profile for TLS - Mgmt Info Tab RG General Profile for TLS - Port Assignment Tab AlliedView NMS Administration Guide (Provisioning the iMG/RG) 7-61
Basic Configurations with Sample Profiles Internet - Bridged 7.5.3 Internet - Bridged In Internet - Bridged service, a data device (such as a PC) connects with the ISP on the same VLAN, so there is no routing. In essence, the RG is like one end of a TLS connection. Refer to Figure 7-33. FIGURE 7-33 Internet - Bridged Configuration The following table lists the sample profiles included with the AlliedView NMS and what they contain.
Internet - Bridged Basic Configurations with Sample Profiles FIGURE 7-34 Internet Bridged Service - Profile “Bridged Service” AlliedView NMS Administration Guide (Provisioning the iMG/RG) 7-63
Basic Configurations with Sample Profiles Internet - Routed 7.5.4 Internet - Routed In Internet - Routed service, the RG has a routing function; there are two VLANs, one local to the RG and one for transport to the ISP. The RG IP address is included in packets from the data device. The DHCP function on the LAN side of the RG is included in the Triple Play form. Refer to Figure 7-35.
Internet - Routed Basic Configurations with Sample Profiles The following table lists the sample profiles included with the AlliedView NMS and what they contain. TABLE 7-20 Example Profiles for Internet - Routed Profile Type Example Profile Name Description RG General Profile “Internet_Routed_or_NAT” In Mgmt. Info tab, Internet VLAN (400) filled in.
Basic Configurations with Sample Profiles FIGURE 7-37 7-66 Internet - Routed Internet Routed Service - Profile “Routed custSec” - Security Tab AlliedView NMS Administration Guide (Provisioning the iMG/RG)
Internet - Routed - NAT Basic Configurations with Sample Profiles 7.5.5 Internet - Routed - NAT In Internet - Routed NAT service is similar to the Routed service, with the key difference that IP numbering is local; the ISP sends packets to an RG IP address that is defined on a VLAN that is not local to the RG. A local VLAN is defined for the local IP numbering. Refer to Figure 7-38.
Basic Configurations with Sample Profiles TABLE 7-21 Internet - Routed - NAT Example Profiles for Internet - Routed - NAT Profile Type Example Profile Name RG General Profile “Internet_Routed_or_NAT” Description In Mgmt. Info tab, Internet VLAN (400) filled in.
Internet - Routed - NAT Basic Configurations with Sample Profiles FIGURE 7-40 Internet Routed NAT Service - Profile “Routed/all security” - Security Tab FIGURE 7-41 Internet Routed NAT Service - Profile “Routed/all security” - Security Tab AlliedView NMS Administration Guide (Provisioning the iMG/RG) 7-69
Basic Configurations with Sample Profiles FIGURE 7-42 7-70 Internet - Routed - NAT Internet Routed NAT Service - Profile “Routed/all security” - NAT Tab AlliedView NMS Administration Guide (Provisioning the iMG/RG)
Video - Snooping Basic Configurations with Sample Profiles 7.5.6 Video - Snooping In Video - Snooping service, the iMAP uses the STB/MAC locking feature, so the iMAP tracks the STB usage. IGMP is enabled in the iMAP so that it can track the joins/leaves via snooping. Refer to Figure 7-39. Note that when video is set to NONE, all video streams go to all ports, so a 100 meg data stream must be used. With snooping, the STB only gets the video stream it is requesting, which helps prevent blocking.
Basic Configurations with Sample Profiles TABLE 7-22 Video - Snooping Example Profiles for Video - Snooping Profile Type Example Profile Name RG General Profile “Video_only” Description In Mgmt. Info tab, Video VLAN (500) filled in. Port Assignment tab has one or more ports filled, as Video IP Routes not used RG Video “Snooping” IGMP Node is Snooping The IGMP time-out must be at least 10 seconds greater than the router queries, but not so much higher that it will time-out.
Video - Proxy Basic Configurations with Sample Profiles 7.5.7 Video - Proxy In Video - Proxy service, the joins/leaves are performed by the RG and so IGMP is disabled on the iMAP. The iMAP supports eight Multicast groups per MAC (up to six). With proxy, the iMAP sees only one MAC, that of the RG, and up to eight MC groups. Refer to Figure 7-45. FIGURE 7-45 Video - Proxy Configuration The following table lists the sample profiles included with the AlliedView NMS and what they contain.
Basic Configurations with Sample Profiles TABLE 7-23 Video - Proxy Example Profiles for Video - Proxy Profile Type Example Profile Name RG General Profile “Video_only” Description In Mgmt. Info tab, Video VLAN (500) filled in. Port Assignment tab has one or more ports filled, as Video IP Routes tab has no entries.
Voice - Public and Private Basic Configurations with Sample Profiles 7.5.8 Voice - Public and Private For voice service, a major choice is whether to include voice service on an internet VLAN (Public) or to use a separate VLAN for voice (Private). This choice, as well as whether IP addresses will be allocated statically or dynamically, are attributes for each type of Voice service. Moreover, each of these services is on an RG basis; the specific service types cannot be shared on the same RG.
Basic Configurations with Sample Profiles Voice - Public and Private The following table lists the sample profiles included with the AlliedView NMS and what they contain. TABLE 7-24 Example Profiles for Voice Profile Type Example Profile Name RG General Profile “Voice_only” Description In Mgmt. Info tab, Voice VLAN (600) filled in. Port Assignment tab has no ports datafilled.
Voice - Public and Private Basic Configurations with Sample Profiles FIGURE 7-49 RG Voice Profile - “SIP1” AlliedView NMS Administration Guide (Provisioning the iMG/RG) 7-77
Basic Configurations with Sample Profiles ADSL iMG with multiple VCs 7.5.9 ADSL iMG with multiple VCs The user can provision the iMG/RG General Profile and ADSL Port Profile so that the ADSL-based iMG/RG can support service VLANs with different VC configurations. The format used to specify a specific VLAN/VC combination is vc:.:. In the following figure, the RG General Profile has the internet VLAN configured on a different VC with VPI=0 and VCI=36.
ADSL iMG with multiple VCs FIGURE 7-51 Basic Configurations with Sample Profiles Triple Play Form with Profiles to Configure VLAN/VC for Internet Service AlliedView NMS Administration Guide (Provisioning the iMG/RG) 7-79
Basic Configurations with Sample Profiles ADSL iMG with multiple VCs The user also must be aware that when provisioning an ADSL iMG/RG, the profiles must be aligned so that the services can be provisioned. The main guidelines are: • When specifying the VC in an iMG/RG profile, and the profile is applied to a non-DSL iMG/RG, the VPI, VCI, and Framing attributes are ignored.
ADSL iMG with multiple VCs Basic Configurations with Sample Profiles Once the iMG/RG is provisioned and in service, the user has the option to change the settings in the Triple Play Service Management window. Moreover, once this is updated, the NMS will update the iMAP port configuration if necessary. In the following figure, the user has decided to change the internet VLAN so that it is on VLAN 21 (rather than 20), and has VPI=1, VCI=45.
Basic Configurations with Sample Profiles ADSL iMG with multiple VCs After choosing Save iMG/RG Configuration, the user will see that the NMS will make the necessary changes, and in the ADSL Configuration -> VCs/VLANs tab the changes are reflected. Refer to the following figure.
Overview Datafilling the Triple Play Form - Examples 7.6 Datafilling the Triple Play Form - Examples 7.6.1 Overview Note: Before the Triple-Play form is filled out, the following has already been performed: • The relevant RG profiles have been created • The relevant iMAP port profiles have been created. • If voice service is being provided, the initial voice handling configuration (such as G6) is done. Refer to 5.6.3 for an overview of the Triple Play form and its fields.
Datafilling the Triple Play Form - Examples Configuration 1 Example - POTS, Derived Voice, Internet, 7.6.
Configuration 1 Example - POTS, Derived Voice, Internet, Video, TLSDatafilling the Triple Play Form - Examples The following figure shows how the Triple Play form is filled out to reflect these profiles, since most of the values are automatically datafilled when the Profiles are included. Note the use of Scoping for both the RG General and the RG Voice Profiles, as shown in Figure 7-57 and Figure 7-58. The Profile Scoping field is set to the Access Island Prefix (AI01) with the wildcard (*).
Datafilling the Triple Play Form - Examples FIGURE 7-57 Configuration 1 Example - POTS, Derived Voice, Internet, RG General Profile for Configuration 1 FIGURE 7-58 7-86 RG Voice Profile for Configuration 1 AlliedView NMS Administration Guide (Provisioning the iMG/RG)
Configuration 2 - Multiple Video, Data, Derived Voice Datafilling the Triple Play Form - Examples 7.6.
Datafilling the Triple Play Form - Examples FIGURE 7-60 7-88 Configuration 2 - Multiple Video, Data, Derived Voice Triple Play Customer Form for RG 646 - Configuration 2 AlliedView NMS Administration Guide (Provisioning the iMG/RG)
Configuration 3 - Static Provisioning (no DHCP) FIGURE 7-61 FIGURE 7-62 Datafilling the Triple Play Form - Examples RG General Profile for Configuration 2 - Mgmt. Info RG General Profile for Configuration 2 - Port Assignment Once the RG is pre-provisioned, it appears in the Network Inventory View under iMG/RGs. Right clicking on the device and selecting View/Modify Details brings up the tabbed form that includes all of the device attributes. Subsection 7.
Datafilling the Triple Play Form - Examples Configuration 3 - Static Provisioning (no DHCP) 7.6.4.1 Prerequisites (Profiles and Hard-coded Values) Before setting up a static model, the user should create some profiles that in critical ways do not have certain values filled in. This will control the Triple Play form when these Profiles are chosen. The following figures show two profiles: • HomeNetworkInet-StaticIP - Note that the Use DHCP to Obtain IP Address is set to False.
Configuration 3 - Static Provisioning (no DHCP) FIGURE 7-64 Datafilling the Triple Play Form - Examples RG Voice Profile - Static Configuration Moreover, some hard-coded values must be known before beginning the procedure, since these static Profiles will make certain fields appear that must be filled in on the Triple Play form: • RGMgmt IP Address - This does not need to be known if the user sets up discovery so that the IP address is included in the Discovery process.
Datafilling the Triple Play Form - Examples Configuration 3 - Static Provisioning (no DHCP) - VLAN=1 untagged - IP address = 192.168.1.1 - DHCP=Off 5. telnet into the ADSL modem using the 192.168.1.1 address. 6. Change the IP address to the unique IP address. 7. Save the configuration and set this as the default - You can now take the RG to the customer site if not already there. 7.6.4.
Configuration 3 - Static Provisioning (no DHCP) FIGURE 7-65 Datafilling the Triple Play Form - Examples Triple Play Form for Static Provisioning After clicking on Provision, the AlliedView NMS stores all of the values. If the RG has previously been discovered, the values in the Triple-Play form are applied. If the RG has not been discovered, discovery can be done in two ways: • Wait for the 24-hour discovery cycle to discover the RG.
Datafilling the Triple Play Form - Examples FIGURE 7-66 Configuration 3 - Static Provisioning (no DHCP) Adding the RG to. the Network Manually (Add Node Form) When the user clicks on Add Node, the AlliedView NMS immediately begins configuring the RG. In the iMG/RG table (under Network Inventory), the RG with the ID “Static Customer” at first has no columns filled in since it has not been discovered. Once discovered, the columns begin to fill in.
Configuration 3 - Static Provisioning (no DHCP) FIGURE 7-67 Datafilling the Triple Play Form - Examples Adding RG with Static Values - Discovery Complete Note that the Upstream Port field is not filled in, since DHCP discovery was not used.
Datafilling the Triple Play Form - Examples Configuration 3 - Static Provisioning (no DHCP) 7.6.4.5 Viewing Static Configuration Viewing the status windows shows the differences between the statically and dynamically configured iMG/RG. The following figures list the tabbed windows that show these differences.
Configuration 3 - Static Provisioning (no DHCP) FIGURE 7-69 Datafilling the Triple Play Form - Examples Static iMG/RG Configuration - Internet Service Tab AlliedView NMS Administration Guide (Provisioning the iMG/RG) 7-97
Datafilling the Triple Play Form - Examples FIGURE 7-70 7-98 Configuration 3 - Static Provisioning (no DHCP) Static iMG/RG Configuration - Voice Service Tab AlliedView NMS Administration Guide (Provisioning the iMG/RG)
Configuration 4 - EPON/ONU Interface Connected with iMG646PX-ONDatafilling the Triple Play Form - Examples 7.6.5 Configuration 4 - EPON/ONU Interface Connected with iMG646PX-ON This example is similar to the first two examples, but the use of Profiles is highlighted because of the use of EPON/ONU specific QoS policies, as explained in 6.11.11. FIGURE 7-71 Triple-Play for the EPON/ONU Figure 7-71 shows the Triple-Play form when filled out for the ONU interface.
Datafilling the Triple Play Form - Examples FIGURE 7-72 Configuration 4 - EPON/ONU Interface Connected with Service Management Window -> iMG/RG Tab for EPON/ONU Figure 7-72 shows the Service Management Form once the iMG/RG is configured. The iMG/RG-> Mgmt. Info tab provides a summary of all the main attributes.
Configuration 4 - EPON/ONU Interface Connected with iMG646PX-ONDatafilling the Triple Play Form - Examples FIGURE 7-73 Service Management Window -> ONU Configuration Tab for EPON/ONU Figure 7-73 shows the Service Management Form with the ONU Configuration tab. On this form the user can change the VLAN-QoS policy association. The available VLANs and policies are included in the pull-down menus. Note: The EPON supports translations.
Datafilling the Triple Play Form - Examples Configuration 5 - Voice Service Provided by SIP 7.6.6 Configuration 5 - Voice Service Provided by SIP Configuration 5 is similar to Configuration 1, but in this example the voice service is provided by SIP. Refer to the following figure.
Configuration 5 - Voice Service Provided by SIP FIGURE 7-75 Datafilling the Triple Play Form - Examples Triple Play Form with SIP for Voice AlliedView NMS Administration Guide (Provisioning the iMG/RG) 7-103
Datafilling the Triple Play Form - Examples Configuration 6 - Multi-Service VLAN 7.6.7 Configuration 6 - Multi-Service VLAN Configuration 6 involves placing more than one service on a VLAN. = voice VLAN (VID 10) = IP Subnet = shared (video, data) VLAN (VID 40) iMG646PX-ON = 10.56.7.223 ONU 4.0.0 ETH 4.0.0 FXS EPON = 172.16.33.18 Internet (IP 2) Data to PC 10 10 Video (IP 1) Ethernet FXS BD Fiber 40 Ethernet NMS (IP 3) Ethernet Video to Set Top Box iMG646 Customer = 10.56.7.
Configuration 6 - Multi-Service VLAN Datafilling the Triple Play Form - Examples 7.6.7.1 RG Forms FIGURE 7-77 Shared VLAN - RG General - Mgmt.
Datafilling the Triple Play Form - Examples FIGURE 7-78 7-106 Configuration 6 - Multi-Service VLAN Multi-service VLAN - Internet - General Profile AlliedView NMS Administration Guide (Provisioning the iMG/RG)
Configuration 6 - Multi-Service VLAN FIGURE 7-79 Datafilling the Triple Play Form - Examples Multi-service VLAN - Video Profile AlliedView NMS Administration Guide (Provisioning the iMG/RG) 7-107
Datafilling the Triple Play Form - Examples FIGURE 7-80 7-108 Configuration 6 - Multi-Service VLAN Multi-service VLAN - Voice Profile AlliedView NMS Administration Guide (Provisioning the iMG/RG)
Configuration 7 - iMG7x6MOD with HPNA Datafilling the Triple Play Form - Examples 7.6.8 Configuration 7 - iMG7x6MOD with HPNA The iMG7x6MOD can be configured using the RG forms. Moreover, VLAN translation may be needed to ensure the iMG can be integrated into the network.
Datafilling the Triple Play Form - Examples FIGURE 7-82 Configuration 7 - iMG7x6MOD with HPNA Ethernet Port Profile for VLAN Translation (20=201,40=901,10) Note that when provisioning the iMG Profiles, the user does not include any translation information. For example, the RG General profile could be filled out as in Figure 7-83.
Configuration 7 - iMG7x6MOD with HPNA FIGURE 7-83 Datafilling the Triple Play Form - Examples RG General Profile for iMG646MOD (No translations datafilled) For the HPNA, the Port Assignment tab includes the HPNA port, with the options as shown in Figure 7-84 and Table 7-28.
Datafilling the Triple Play Form - Examples FIGURE 7-84 TABLE 7-28 Configuration 7 - iMG7x6MOD with HPNA RG Profile - Port Assignment for HPNA Provisioning the iMG/RG in Release 10.0 Pull-down Option Description Internet (Untagged) The HPNA can support only internet service Video (Untagged) The HPNA can support only video service Internet (Tagged) The HPNA supports internet service, but could support video service as well.
Configuration 8 - AlliedWare Plus Device Datafilling the Triple Play Form - Examples 7.6.9 Configuration 8 - AlliedWare Plus Device The iMG/RG can be configured with AlliedWare Plus upstream devices (x908, x600, x900) in the same way as iMAP ports (all components provisionable, pre-provisioning so that iMG/RG comes into service automatically). Following is an example configuration.
Datafilling the Triple Play Form - Examples Configuration 8 - AlliedWare Plus Device The Triple-Play form can be used to pre-provision the iMG/RG using the already created Profiles. The Triple-Play form is filled out as with other upstream devices, as shown Figure 7-87. The few points to note in configuring iMG/RGs to AlliedWare Plus devices are: • In 12.1, when an AW+ product is first installed, you must use NMS to deprovision the ports before provisioning the ports.
Configuration 9 - Microsoft© Mediaroom™ with the iMG/RG FIGURE 7-87 Datafilling the Triple Play Form - Examples Triple Play Form with x908 Upstream Device Once the form is filled in and the NMS has performed provisioning in software, the iMG will begin its provisioning either immediately (if the iMG/RG is already connected and powered on), or later (when the iMG /RG is connected and powered on). When complete, the iMG is listed and includes its IP address, upstream port, and the associated profiles.
Datafilling the Triple Play Form - Examples Configuration 9 - Microsoft© Mediaroom™ with the iMG/RG Examples where this type of communication is useful include: • • • • Sharing a networked printer in the home where there are multiple PCs Recording TV broadcast to DVR and viewing on demand content from DVR to PC or STB Viewing video, pictures and music library stored in PC to TV Future applications may also include networked appliances (e.g. smart refrigerator, etc.
Configuration 9 - Microsoft© Mediaroom™ with the iMG/RG Datafilling the Triple Play Form - Examples 7.6.10.1 RG General Profile When the iMG is configured for media room, the LAN ports that participate are expected to be shared where local media devices can be connected to any of the LAN ports and get service as normal. In this configuration a new service is configured for a LAN port called “'Internet/Video” to indicate that the port can be used for video or data traffic. Refer to the following figure.
Datafilling the Triple Play Form - Examples Configuration 9 - Microsoft© Mediaroom™ with the iMG/RG The routes table in General profile allows up to 10 different routes in the iMG because media room devices connected to the iMG may request services configured in separate subnets on the upstream network. Refer to the following figure.
Configuration 9 - Microsoft© Mediaroom™ with the iMG/RG Datafilling the Triple Play Form - Examples 7.6.10.2 RG Internet Profile On the Internet Profile with the Security tab there is the field “Rapid Route” that is used to configure the iMG for media room support. This enhances NAT routing functionality in CPE for better throughput of routed traffic. Refer to the following figure.
Datafilling the Triple Play Form - Examples Configuration 9 - Microsoft© Mediaroom™ with the iMG/RG 7.6.10.3 RG Video Profile The video profile includes two fields needed to support the media room configuration. Since Media Room services are routed, the video profile allows obtaining the IP address for video service using DHCP since this must be a valid reachable IP address.
Configuration 9 - Microsoft© Mediaroom™ with the iMG/RG Datafilling the Triple Play Form - Examples • Set local IP addresses in General Internet Info tab. • Video Profile • Set IGMP mode to Proxy. • Enable Use DHCP for Video IP interface so that it is not necessary to always specify a valid IP address. • Enable Multicast Acceleration parameter. After configuring all profiles, the user provisions the iMG using the Triple Play form and profiles are included as with other configurations.
Datafilling the Triple Play Form - Examples Configuration 10 - Video with static IP Address (iMG1000 and 7.6.11 Configuration 10 - Video with static IP Address (iMG1000 and 2000 Series) In most networks, routers for security reasons will not accept source ip addresses of all zeros or will ensure that the igmp traffic (including joins/leaves) has a proper IP address.
Configuration 10 - Video with static IP Address (iMG1000 and 2000 Series)Datafilling the Triple Play Form - Examples FIGURE 7-95 Showing the Video IP Address Panel (Display Preferences Option) Once configured, the iMG/RG -> Video Service tab shows the Video IP Address and Video IP Mask, as shown below.
Provisioning the iMG/RG (Managed Object Properties) Overview 7.7 Provisioning the iMG/RG (Managed Object Properties) 7.7.1 Overview • Managed Object Properties for the iMG/RG Section 8 of the AlliedView NMS User Guide describes all the relevant managed objects and their properties so that the user can control how the MO is provisioned. This is especially helpful in understanding how MO properties can be filtered in Custom Views. • Custom Views As explained in 7.2.
Managed Object Properties for the iMG/RG FIGURE 7-97 Provisioning the iMG/RG (Managed Object Properties) Managed Object Properties Form for an iMG/RG AlliedView NMS Administration Guide (Provisioning the iMG/RG) 7-125
Provisioning the iMG/RG (Managed Object Properties)Managed Object Properties for the iMG/RG TABLE 7-29 Managed Object Properties for Nodes Custom Map View Property MO Form Property Description for Nodes Example Name The device name, which is a unique name that is used as the key in the database. This name cannot be changed. name Type The type of the object, such as whether it is a network, node, or an interface object, or something user specified, like router, switch, etc.
Managed Object Properties for the iMG/RG TABLE 7-29 Provisioning the iMG/RG (Managed Object Properties) Managed Object Properties for Nodes (Continued) Custom Map View Property MO Form Property Description for Nodes Example SysLocation A string value to identify where the device is located sysLocation Building_A (This would assume the device was located in Building_A) Category The family of the device category Telesis (includes all MAP devices) Rapier* (all Rapier devices) RG* (all RG devices)
Provisioning the iMG/RG (Managed Object Properties)Creating Custom Views for an Access Island TABLE 7-30 Managed Object Properties for Ports Custom Map View Property MO Form Property Description for Ports Name The device name, which is a unique name that is used as the key in the database. This name cannot be changed. name Type The type of the object, such as whether it is a network, node, or an interface object, or something user specified, like router, switch, etc.
Creating Custom Views for an Access Island Provisioning the iMG/RG (Managed Object Properties) • critical, major, minor Click on the More button and then Select Additional Criteria to include more attributes that will filter this form. Use the exact name for the criteria and follow the rules above. You can also choose Select Props to View to select which fields will appear in the view. (This is different than defining the criteria to filter a view.
Provisioning the iMG/RG (Managed Object Properties)Creating Custom Views for an Access Island 1. Select the Network Node that will have the Custom View as a sub-node (this can also be done later). 2. Right click on this Node and select Custom Views -> Add Custom Map (or Control-N) 3. On the Map Properties form, fill in the Name you wish to give this Custom Map. (You can also choose the parent node here if you wish to change this.) 4.
Creating Custom Views for an Access Island 3. Provisioning the iMG/RG (Managed Object Properties) On the Object Properties form, fill in the Name you wish to give this Custom View. (Note that in this case you cannot choose the parent node.) Click on the More button to include the attributes that will filter this form.
Provisioning the iMG/RG (Managed Object Properties)Creating Custom Views for an Access Island • Fast Ethernet - cardType=FE*, type=Card • POTS - cardType=POTS*, type=Cardtype=Card • VDSL - cardType=VDSL*, type=Card Note: For a complete list, refer to the AlliedView NMS User Guide. FIGURE 7-101 Example Custom View for Card Types 7.7.3.
Creating Custom Views for an Access Island • • • • Provisioning the iMG/RG (Managed Object Properties) ethIfIndex = <> (null, since an available port does not have an Ethernet index value) customerID = <> (null, since an available port does not have a customer ID) type = CustPort parentKey = dot18* (This narrows the view down to the Access Island.) An example would be a Custom View that showed all GE ports on Access Island 01.
Provisioning the iMG/RG (Managed Object Properties)Creating Custom Views for an Access Island FIGURE 7-102 7-134 Custom View for G6 Events in last 48 hours AlliedView NMS Administration Guide (Provisioning the iMG/RG)
Creating Custom Views for an Access Island Provisioning the iMG/RG (Managed Object Properties) • All RG/iMG events in the network - Refer to the following figure.
Provisioning the iMG/RG (Application Manager) Overview 7.8 Provisioning the iMG/RG (Application Manager) 7.8.1 Overview Caution: If AlliedView NMS users are accessing applications via an IP route that includes Network Address Translation (NAT), certain AlliedView NMS modules may not work correctly as the server may send information to the clients over different ports than those initiated by the clients.
Backup/Restore Provisioning the iMG/RG (Application Manager) FIGURE 7-105 List of CPE Devices available for an Application 7.8.2 Backup/Restore This follows the same steps as for Allied Telesis Devices. Refer to Section 5. 7.8.3 Device Configuration This follows the same steps as for Allied Telesis Devices. Refer to Section 5. 7.8.4 Software Configuration This follows the same steps as for Allied Telesis Devices. Refer to Section 5.
Provisioning Guidelines for Models Open Access 7.9 Provisioning Guidelines for Models 7.9.1 Open Access Figure 7-106 shows an example configuration in which there are nine Service Providers, three for each type of service. As a result, there are nine VLANs that exist for these services, and changing a service provider for a service requires a different VLAN to be used. With the updated iMG/RG profile GUIs in 9.0, the following is done to provision the Open Access model: • Mgmt.
Open Access Provisioning Guidelines for Models FIGURE 7-106 iMG/RGs in a Network with Multiple Providers for each Service Once the Open Access model is configured, the Service Management Form is similar to the Access Island model; on the Mgmt. Info tab, the service VLANs are read only, and so the user must go to the individual service tabs to change a VLAN. Refer to the following figure.
Provisioning Guidelines for Models FIGURE 7-107 7-140 Open Access Service Management - iMG/RG -> Mgmt.
Multi-service VLANs Provisioning Guidelines for Models 7.9.2 Multi-service VLANs Note the following when provisioning a multi-service VLAN configuration: • If the internet service is Routed NAT and on the same VLAN as the RG Mgmt VLAN, you must have the Firewall=ON and two port filters to allow TCP and ICMP traffic. Otherwise the NMS will lose connectivity and cannot discover the iMG.
Provisioning Guidelines for Models iMG6x6MOD/iMG7x6MOD - Translation and HPNA Diagnos- 7.9.3 iMG6x6MOD/iMG7x6MOD - Translation and HPNA Diagnostics 7.9.3.1 Need for Translation of VLAN Numbering for iMG6x6MOD With the iMG6x6MOD product, the media converter used between the coax and ethernet interfaces has untagged VLANs on the ethernet interfaces, numbered 201 and 901. The VLANs used on the LAN ports must also have these two VIDs configured.
iMG6x6MOD/iMG7x6MOD - Translation and HPNA Diagnostics FIGURE 7-108 2. Provisioning Guidelines for Models HPNA Testing - Master Tab View the HPNA network stations information - The user can view the information about the stations in the HPNA network. The information to be displayed is shown in the diagram. The Stations sub-tab contains the HPNA Network station information.
Provisioning Guidelines for Models iMG6x6MOD/iMG7x6MOD - Translation and HPNA Diagnos- FIGURE 7-109 7-144 HPNA Testing - Stations Tab AlliedView NMS Administration Guide (Provisioning the iMG/RG)
iMG6x6MOD/iMG7x6MOD - Translation and HPNA Diagnostics 3. Provisioning Guidelines for Models View the HPNA network statistics - The user can view the statistics for each of the stations in the HPNA network. The Statistics Tab contains the HPNA Network station statistics. The tab will show a table where each row is a different statistic and each column is a station in the HPNA Network. The user can press the “Reset Statistics” button, and the HPNA statistics on the iMG are set back to 0.
Provisioning Guidelines for Models 4. iBG915-FX View the HPNA performance metrics The user can view the performance metrics between each pair of stations in the HPNA network. The tab will show a table where each row is a different from-station/to-station pair and each column is a metric. The user then presses the “Collect Performance Metrics” buttons to start the data collection. Refer to the following figure. FIGURE 7-111 5.
iBG915-FX Note: Provisioning Guidelines for Models CPU-based rate limiting is supported, as with the iMG MOD devices. This feature is included in the following subsections. 7.9.4.2 Changes to the GUI • iMG/RG Voice Profile Windows The iMG/RG Voice Profile screen is modified to allow the user to specify the configuration to be applied to lines 5 through 8. Refer to the following figures.
Provisioning Guidelines for Models FIGURE 7-114 7-148 iBG915-FX Modify iMG/RG Voice Profile for iBG915-FX AlliedView NMS Administration Guide (Provisioning the iMG/RG)
iBG915-FX Provisioning Guidelines for Models • iMG/RG Voice Service Tab on the Triple Play Service Management Window The iMG/RG Voice Service Tab of the Triple Play Service Management window is updated to show the current configuration of all eight voice lines on the iBG915-FX. In addition, the user can make updates to those additional lines. Refer to the following figure.
Provisioning Guidelines for Models iBG915-FX • iMG/RG Internet Service Tab on the Triple Play Service Management Window The iMG/RG Service Tab of the Triple Play Service Management window shows the Service Rate Limiting fields. (PPPoE continues not to be shown.). Refer to the following figure.
iBG915-FX Provisioning Guidelines for Models • iMG/RG Port Assignment Tab on the Triple Play Service Management Window The iMG/RG Port Assignment Tab of the Triple Play Service Management window is updated to show the current configuration of the five LAN ports on the iBG915-FX. In addition, the user can make updates to those ports. Refer to the following figure.
Provisioning Guidelines for Models iBG915-FX • Provision New Triple Play Customer Window The Provision New Triple Play Customer Window is updated to allow the user to enter the configuration of up to eight voice lines (depending on the number of voice line configured in the selected iMG/RG voice profile). Refer to the following figure.
iBG915-FX Provisioning Guidelines for Models • GenBand G2/G6 - Add Voice Line Window The window that allows that user to configure a voice line for an IBG915-FX on the GenBand G6 is modified to allow the user to specify telephone ports 5-8. Refer to the following figure.
Provisioning Guidelines for Models iMG with WAN 1G Module 7.9.5 iMG with WAN 1G Module 7.9.5.1 Overview Products such as the AT-iMG7x6MOD can support the same card configuration as the AT-iMG6x6MOD, described in 7.6.8. In addition, it can support the following: • 1 Gigabit Bidirectional WAN Module • 1 Gigabit Bidirectional WAN Module with a Gigabit LANRJ-45 connection, allowing both the LAN and WAN ports to be configured on one module.
iMG with WAN 1G Module Provisioning Guidelines for Models For existing Ethernet port profiles these changes are not an issue, because they will not have the port direction field explicitly set. However, new port profiles should be created with the port direction set to match the provisioning scenario in which they will be used, as follows: The following iMAP GE ports should have new profiles set with the direction of Customer when connecting with with a 1G WAN card • • • • GE8 on the 9x00 iMAP GE4 (5.
Provisioning Guidelines for Models FIGURE 7-122 7-156 iMG with WAN 1G Module Setting the GE Port profile to Provision the VLANs AlliedView NMS Administration Guide (Provisioning the iMG/RG)
iMG with WAN 1G Module Provisioning Guidelines for Models FIGURE 7-123 Setting the GE Port profile to set Port Direction AlliedView NMS Administration Guide (Provisioning the iMG/RG) 7-157
Provisioning Guidelines for Models iMG with WAN 1G Module As with other profile settings, the port direction can be (re)set on the Customer Management Form, under the Ether-like Configuration tab. Refer to the following figure. Caution: With the iMG7x6MOD, do not change the port direction once it has been set for Customer. To change the direction will mean a loss of service.
iMG with WAN 1G Module Provisioning Guidelines for Models The RG General Profile is changed to include the G-Lan port (the port available when the 1 Gigabit WAN with RJ-45 LAN card is used). When this card is used, the General Profile includes the altered Port Assignments to allow the customer to provision services on the G-Lan port. Note: For the iMG726BD-ON, there are 2 G-Lan ports. The settings for the G-Lan will apply to both ports when the profile is applied.
Provisioning Guidelines for Models Split Management for Wireless iMG 7.9.6 Split Management for Wireless iMG 7.9.6.1 Overview This feature allows a subscriber (rather than an NMS administrator) to configure wireless parameters on wireless iMG devices. This is done by accessing the web GUI that can be accessed on the device with a user ID / password.
Split Management for Wireless iMG Provisioning Guidelines for Models 7.9.6.2 Setting up Split Management - New CPE The iMG/RG General Profile has the field Split Management and also shows the default user ID / password (admin / admin). Note that the user ID/ password are read-only. Refer to the following figure. In the Internet Service Profile, with the internet service type set to “Routed Service”, the local IP addresses are used to access the device.
Provisioning Guidelines for Models Split Management for Wireless iMG 7.9.6.3 Setting up Split Management - Existing CPE If a device is already provisioned, the feature is by default de-activated. This is shown by accessing the Service Management form for the iMG and going to the iMG/RG tab, Mgmt. Info subtab, as shown in the following figure. FIGURE 7-127 Mgmt.
Split Management for Wireless iMG Provisioning Guidelines for Models 7.9.6.4 Viewing the Service Management Form Once Split Management is enabled, the iMG/RG -> Mgmt. Info tab will show that Split Management is Enabled and Subscriber Login and Password. The subscriber should immediately change the password (refer to 7.9.6.5). Also, the Mgmt. Subnets are listed as follows: For Routed internet service, nms and split_management are automatically added to the list.
Provisioning Guidelines for Models FIGURE 7-129 7-164 Split Management for Wireless iMG Service Management Form - Bridged Service AlliedView NMS Administration Guide (Provisioning the iMG/RG)
Split Management for Wireless iMG Provisioning Guidelines for Models 7.9.6.5 The Subscriber Using the Feature Once the feature is activated, the subscriber can connect to the iMG over the web interface using the default id / password of admin / admin. Although the subscriber at this point can change wireless parameters, it is recommended that the subscriber first change the password for security. Note: While the feature is activated, the NMS administrator cannot modify the wireless parameters.
Provisioning Guidelines for Models Changing VoIP Endpoint Syntax 7.9.7 Changing VoIP Endpoint Syntax As described in 7.4.5, for MGCP configurations that do not use GenBand, there is the option in the RG Voice profile to enter the VoIP endpoint that will be used.
Provisioning Custom VLANs Provisioning Guidelines for Models 7.9.8 Provisioning Custom VLANs Although the RG General Profile is used to define VLANs for specific services, the iMG can support up to 14 VLANs. Each port can be connected to any VLAN in in any combination of tagged, untagged bridged and routed configurations. Note: When modular devices (iMG 726, iMG746, etc.) are used, one VLAN is used to manage HPNA and CES.
Provisioning Guidelines for Models FIGURE 7-132 Provisioning Custom VLANs Panel to Add/Remove/Modify Custom VLANs (Once Profile is Created) This panel includes the name and indication if the VLAN is tagged on WAN port. The table format used works similar to others in NMS where the top table shows current values and the bottom table is for editing. Since iMGs cannot have more than 14 VLANs, this will limit the number of VLANs in device to 14 (including Default and all service VLANs).
Provisioning Custom VLANs Provisioning Guidelines for Models FIGURE 7-133 Advanced Port Attributes - Custom VLANs AlliedView NMS Administration Guide (Provisioning the iMG/RG) 7-169
Provisioning Guidelines for Models Error Conditions when Provisioning 7.9.9 Error Conditions when Provisioning 7.9.9.
Overview Installation Procedures 7.10 Installation Procedures 7.10.1 Overview With the use of the AlliedView NMS profiles and DHCP, the installation, reconfiguration, and de-installation of iMGs/RGs does not involve complex (and therefore error-prone) procedures. These procedures can be grouped into two main areas: 1. Installing, reconfiguring, and removing the iMG/RG using AlliedView NMS 2.
Installation Procedures Pre-provision Future Customer (Provision iMAP Port, no 7.10.2.2 Moving the iMG/RG to another Port (Re-provisioning) As explained in 7.1, an administratively efficient way to provision the iMG/RG is by using Access Islands, with each Access Island having its own unique set of VLANs.
Pre-provision Future Customer (Provision iMAP Port, no Services) FIGURE 7-134 Installation Procedures Profile for DVLK-AI01-Vacant - Mgmt Info AlliedView NMS Administration Guide (Provisioning the iMG/RG) 7-173
Installation Procedures Pre-provision Future Customer (Provision iMAP Port, no FIGURE 7-135 7-174 Profile for DVLK-AI01-Vacant - Port Assignment AlliedView NMS Administration Guide (Provisioning the iMG/RG)
Pre-provision Future Customer (Provision iMAP Port, no Services) FIGURE 7-136 Installation Procedures Profile for DVLK-AI01-Vacant - IP Routes AlliedView NMS Administration Guide (Provisioning the iMG/RG) 7-175
Installation Procedures Provision a new Customer (out of the box) - Triple Play FIGURE 7-137 Provision Triple Play - No Services 7.10.3.4 Add Services to an Already Provisioned Port When services must be added to the pre-provisioned port, the same steps are used when adding services to a port that already has some service(s) configured, using the View/Modify Customer window. Following is a summary of these steps. For details, refer to the procedures in the rest of this Subsection. 1.
Provision a new Customer (out of the box) - Triple Play Installation Procedures 7.10.4.2 Pre-requisite Procedures Before performing this procedure, the user should have already done the following: 1. At the iMAP, ensure the following are already configured: • VLANs for DHCP and services have been created. • The iMAP card/port that interfaces the iMG/RG has been installed and enabled. 2. User has work order that should include the following: • Attributes that will be used for GenBand configuration 3.
Installation Procedures Provision a new Customer (out of the box) - Triple Play 6. Enter a port Profile. Only those port profiles relevant for the type of port are available. 7. Select an Internet Svc. Profile, in this case HomeNetworkInet. Note that the Local IP Addr, Mask, and DHCP Start/End addresses are datafilled. 8. Select an Video Svc. Profile, in this case Video-Proxy. Note that the Local IP Addr, Mask, and DHCP Start/End addresses are datafilled. 9. Select a Derived Voice Svc.
Provision a new Customer (out of the box) - Triple Play Installation Procedures • To provision, select Hold and then Provision. • To provision at set time, click on Schedule, enter the date/time, and then Provision Note: 13. At this point, the user can provision other ports, since the iMG/RG has not been connected to the iMAP; all that is being provisioned is the iMAP port. Review the Triple Play Service Management Form, as shown in Figure 7-139.
Installation Procedures FIGURE 7-140 Provision a new Customer (out of the box) - Triple Play IMG/RG Table - iMAP Port Configured, no iMG/RG Configured Note the following: • The Customer ID, Type (Family level), and Upstream Port are identified. • The iMG/RG IP address, software release, and associated profiles are not included. These are filled in as a result of plugging in the iMG/RG by the customer, which begins the DHCP configuration steps. 15. End of this part of the Procedure 7.10.4.
Provisioning / De-Provisioning Voice Service Installation Procedures 7.10.5 Provisioning / De-Provisioning Voice Service 7.10.5.1 Overview When a customer has video and data service (double-play), and wishes to add voice service, the use of AlliedView NMS makes this possible, through the use of profiles, with a small number of steps. Moreover, adding or removing a second line for a service is accomplished using only a few GUI screens.
Installation Procedures 5. Provisioning / De-Provisioning Voice Service In the RG General profile pull-down, select the Profile DeskLab-3Play-1Video, as shown in Figure 7- 141. FIGURE 7-141 Applying Different RG General Profile for Triple-Play 6. Click on Modify. 7. Note the results - The VLAN defined in the General Profile is added. 8. Still in the Mgmt. Info tab, select the Voice Service tab 9. For the Voice Service Profile pull-down, select VOIPPhone. Refer to Figure 7-142.
Provisioning / De-Provisioning Voice Service FIGURE 7-142 Installation Procedures Applying Voice Profile 10. Click on Modify. 11. Select the Status tab (there are no sub-tabs). 12. Click on Add Voice Line. The Add Voice Line form appears. 13. In the Add Voice Line form, note that the Voice Endpoint (used for DNS) is already defined, as well as the interface group. These were defined in the Voice service profile. 14.
Installation Procedures Provisioning / De-Provisioning Voice Service FIGURE 7-143 15. Click on the now activated Add. 16. Back on the Status tab, click on Update Customer Info. 17. Note the results. 18. End of Procedure Note: Add Voice Line (line 1) For the Open Access Model, the same procedure would be used, with the administrator ensuring that there was no conflict in VLAN configuration between the iMG/RG General Profile and the Voice Service Profile. 7.10.5.3 Add Second Voice Line 1.
Provisioning / De-Provisioning Voice Service FIGURE 7-144 Installation Procedures Add Voice Line (line 2) 8. Click on the now activated Add. 9. Back on the Status tab, click on Update Customer Info. 10. Note the results. Refer to Figure 7-145. 11. End of Procedure.
Installation Procedures Provisioning / De-Provisioning Voice Service FIGURE 7-145 Results of Second Voice Line Added 7.10.5.4 Remove Second Voice Line 1. Find the iMG/RG for the customer in the iMG/RGs table using various methods: • Bring up the iMG/RGs node in the Network Inventory table and do a search (Ctrl-F) on the Customer ID. • Bring up the Ports node in the Network Inventory table and do a search (Ctrl-F) on the Customer ID. 2. Right click on the iMG/RG or Port and select View/Modify Details.
Provisioning / De-Provisioning Voice Service FIGURE 7-146 Installation Procedures Two MGC Tabs (one for each Voice Line) 5. Click on Remove. 6. When the Confirmation window appears, click on Yes. 7. Note the results. The MGC tab is removed and only one MGC tab remains. 8. End of Procedure. 7.10.5.5 Remove Voice Service (Triple- to Double-Play) 1. Ensure the pre-requisites are met: • General Profile available to support the result of customer having no voice service (double play) 2.
Installation Procedures Provisioning / De-Provisioning Voice Service FIGURE 7-147 5. Deleting Voice Profile Click on Modify. Note: At this point you could select Save iMG/RG Configuration, and the customer would have no voice service but still have it configured on the RG. 6. Select the Mgmt. Info tab (still under the iMG/RG tab). 7. For the iMG/RG General Profile, select the double-play General Profile the customer will use. Refer to the following figure.
Provisioning / De-Provisioning Voice Service FIGURE 7-148 Installation Procedures Customer Using Profile for Double Play (no Voice) 8. Select Save iMG/RG Configuration. 9. As the changes takes effect, any phone connected to the RG will no longer have dial tone. 10.
Installation Procedures Provisioning / De-Provisioning Video Service 7.10.6 Provisioning / De-Provisioning Video Service 7.10.6.1 Overview When a customer has voice and data service (double-play), and wishes to add video service, the use of AlliedView NMS makes this possible, through the use of profiles, with a small number of steps. Moreover, adding or removing a second line for a service is accomplished using only a few GUI screens.
Provisioning / De-Provisioning Video Service Installation Procedures • Bring up the iMG/RGs node in the Network Inventory table and do a search (Ctrl-F) on the Customer ID. • Bring up the Ports node in the Network Inventory table and do a search (Ctrl-F) on the Customer ID. 3. Right click on the iMG/RG or Port and select View/Modify Details. This brings up the Triple Play Service Management screen. 4. Select the iMG/RG tab, which automatically shows the Mgmt. Info tab. 5.
Installation Procedures Provisioning / De-Provisioning Video Service FIGURE 7-151 Applying Video Profile 10. Click on the now active Modify. 11. Note the results - The Video Service Profile changes form None to Video-Proxy with the Video Svc. VLAN from the RG GeneralMgmt profile Note: Do not make changes to the IGMP values, or the video service will be out of synch with the video profile. (If you do so, and * will appear next to the Profile Name.) 12. Return to the Mgmt. Info sub-tab. 13.
Provisioning / De-Provisioning Video Service FIGURE 7-152 Installation Procedures Applying Different RG General Profile for Triple-Play (Second VIdeo) 6. Click on Modify. 7. Click on Save iMG/RG Configuration. 8. Back on the Status tab, click on Update Customer Info. 9. Note the results: On the iMG/RG Port Assignments tab, there are two ports for Video, 1 and 3, as shown in the following figure. 10. Restart cpe (iMG/RG). 11. End of Procedure.
Installation Procedures Provisioning / De-Provisioning Video Service FIGURE 7-153 Results of Second Video Line Added (Ports) 7.10.6.4 Remove Second Video Line 1. Ensure the prerequisites are met: • An RG General Profile exists that supports more than one video, i.e. DeskLab-3-play-1Video. 2. Find the iMG/RG for the customer in the iMG/RGs table using various methods: • Bring up the iMG/RGs node in the Network Inventory table and do a search (Ctrl-F) on the Customer ID.
Provisioning / De-Provisioning Video Service FIGURE 7-154 Installation Procedures Applying Different RG General Profile for Triple-Play (Remove Second VIdeo) 6. Click on Modify. 7. Click on Save iMG/RG Configuration. 8. Back on the Status tab, click on Update Customer Info. 9. Note the results. In the Port Assignments tab, there is only one video port. Refer to the following figure. 10. At the iMG/RG/Mgmt. Info tab, select Save iMG/RG Configuration. 11. Restart the CPE (iMG/RG) 12.
Installation Procedures Provisioning / De-Provisioning Video Service FIGURE 7-155 Results of Second Video Line Removed 7.10.6.5 Remove Video Service (Triple- to Double-Play) 1. Ensure the pre-requisites are met: • General Profile available to support the result of customer having no video service (double play) 2. Right click on the iMG/RG or Port and select View/Modify Details. This brings up the Triple Play Service Management screen. 3. Select the iMG/RG - Video Service tab. 4.
Provisioning / De-Provisioning Video Service FIGURE 7-156 5. Installation Procedures Deleting Video Profile Click on Modify. Note: At this point you could select Save iMG/RG Configuration, and the customer would have no video service but still have it configured on the RG. 6. Select the Mgmt. Info tab (still under the iMG/RG tab). 7. For the iMG/RG General Profile, select the double-play General Profile the customer will use. Refer to the following figure.
Installation Procedures Change Quality of Existing Data Service FIGURE 7-157 Customer Using Profile for Double Play (no Video) 8. Select Save iMG/RG Configuration. 9. Back on the Status tab, click on Update Customer Info. 10. Note the results: any video connected to the RG will no longer work. 11. END OF PROCEDURE 7.10.7 Change Quality of Existing Data Service This will be supplied in a future release.
Reprovision Existing iMG/RG so incorporated into AlliedView NMS Installation Procedures 7.10.8 Reprovision Existing iMG/RG so incorporated into AlliedView NMS In this scenario, the iMG/RG has already been provisioned either locally or using the ZTC components. If the user wishes to take the existing iMG/RG and transfer control over to the NMS, the NMS will make a best effort and try to ensure that all of the features on the iMG/RG can be controlled by the NMS.
Installation Procedures De-Provision iMG/RG from AlliedView NMS FIGURE 7-158 De provision Ports Form There are three options for deletion: • iMG/RG - Deletes the Customer ID and all associated profiles. The user can now provision a new Customer ID for the iMG /RG and build a service set from profiles. • Ports (iMAP) - De-provisions the iMG/RG, the associated profiles, and the associated ports. If a POTS24 was being used to provide voice service, the POTS24 port would appear here as well.
De-Provision iMG/RG from AlliedView NMS Installation Procedures 3. Select the Customer ID option for all three panels, then click on De-Provision. 4. The RG will reboot. 5. In the iMG/RG table, the Customer ID is deleted and all profile information is deleted. Refer to Figure 7-159 FIGURE 7-159 6. Note: If iMG/RG equipment is to remain unprovisioned on this port temporarily (waiting for new customer to move in etc...), then the deletion of the RG object and traces is optional. FIGURE 7-160 7.
Installation Procedures 4. 5. De-Provision iMG/RG from AlliedView NMS The RG will reboot. In the iMG/RG table, the Customer ID is deleted and all profile information is deleted. Refer to Figure 7-161. FIGURE 7-161 iMG/RG Table after Deleting RG 6. Access the device using telnet. Right click on the iMG/RG in the iMG/RG table and select Telnet to Device. Refer to the following figure. 7. Login to the iMG/RG. 8. Set back to factory defaults (>sys config set factory) 9.
De-Provision iMG/RG from AlliedView NMS FIGURE 7-163 Installation Procedures Delete RG-Port Association (Delete Object and Traces) 13. When the RG is reconnected, the default VLAN for the RG is used at the start for DHCP discovery. Therefore, this would most likely be for connecting the RG to an iMAP that is in any Access Island than where it was de-provisioned. 14. END OF PROCEDURE 7.10.9.
Installation Procedures Changing a Customer ID 7.10.10 Changing a Customer ID 7.10.10.1 Overview Section 7.2.7 listed the naming conventions to follow for Customer IDs. To change a Customer ID, the administrator must enter the changed ID for all three configuration areas (tabs) on the Triple Play Service Management form. • Connection Type - Ether-like, ADSL, or ONU • iMG/RG • Voice All three are filled in the Service Management form.
iMG/RG Recovery Installation Procedures 7.10.11 iMG/RG Recovery This procedure is used when the iMG/RG has gone into Recovery Mode. This could happen, for example, if during the middle of an upgrade procedure the iMG/RG lost power and as a result went into Recovery mode. Note: The iMG/RG will have a constant red light on when it has entered Recovery mode. There are two procedures that can be used, depending on whether the existing RG is to be recovered or a new iMG.RG is to be swapped. 7.10.11.
Installation Procedures Configuring multi-service VLAN 7.10.13 Configuring multi-service VLAN For a description of a multi-service VLAN model, refer to 7.6.7. This subsection gives procedures that involve creating three possible configurations. For all of the procedures the following apply: • The port configuration for each IMG is the same (two voice, two video, one data). This allows the same General profile to be used for all configurations, even if the type of iMG (EPON, FX, ADSL) is different.
Configuring multi-service VLAN TABLE 7-32 Voice Installation Procedures iMG Forms for Voice, Video/Data VLAN Configuration iMG_MGCP_two_line FIGURE 7-165 Since this is not a shared VLAN and uses MGCP, an existing form can be used Figure 7-169 General Form for Multi-service VLAN - Mgmt.
Installation Procedures FIGURE 7-166 7-208 Configuring multi-service VLAN General Form for Multi-service VLAN - Port Assignment Tab AlliedView NMS Administration Guide (Provisioning the iMG/RG)
Configuring multi-service VLAN FIGURE 7-167 Installation Procedures Internet Form for Multi-service VLAN - General Internet Info Tab - Configuration 1 AlliedView NMS Administration Guide (Provisioning the iMG/RG) 7-209
Installation Procedures Configuring multi-service VLAN FIGURE 7-168 7-210 Video Form for Multi-service VLAN - Configuration 1 AlliedView NMS Administration Guide (Provisioning the iMG/RG)
Configuring multi-service VLAN Installation Procedures FIGURE 7-169 2. Voice Form for Multi-service VLAN - Configuration 1 Data fill the Triple-Play Form. Since there are three different customers and types of interfaces, the Customer ID for each must be unique, and the slot.Port will be different. (The iMAP could be the same if all of the interface cards were on the same iMAP. Refer to the following table.
Installation Procedures Configuring multi-service VLAN FIGURE 7-170 7-212 Triple-Play Form EPON Interface - Configuration 1 AlliedView NMS Administration Guide (Provisioning the iMG/RG)
Configuring multi-service VLAN Installation Procedures FIGURE 7-171 FIGURE 7-172 Triple-Play Form FX Interface - Configuration 1 Triple-Play Form ADSL Interface - Configuration 1 AlliedView NMS Administration Guide (Provisioning the iMG/RG) 7-213
Installation Procedures Configuring multi-service VLAN 7.10.13.2 Creating a Data and Video/Voice VLAN (Configuration 2) In this configuration, the Data VLAN is on a separate VLAN, and video and voice share a single VLAN. Refer to the following figure and notes in 7.10.13 before performing the procedure. iMG646PX-ON = 10.56.7.223 ONU 4.0.0 ETH 4.0.0 = IP Subnet = voice, video VLAN (VID 10) FXS = data VLAN (VID 20) FXS Ethernet EPON = 172.16.33.
Configuring multi-service VLAN 1. Installation Procedures Create the appropriate iMG profiles. Refer to the following table and figures. TABLE 7-34 iMG Forms for Voice, Video/Data VLAN (Configuration) 2 Form Name Attributes Reference General iMG_one_data_two_video Since the port and VLAN configuration is the same for all iMGs, the same General Form is used in all configurations Figure 7-165 - Mgmt.
Installation Procedures Configuring multi-service VLAN FIGURE 7-175 7-216 Video Form for Multi-service VLAN - Configuration 2 AlliedView NMS Administration Guide (Provisioning the iMG/RG)
Configuring multi-service VLAN Installation Procedures FIGURE 7-176 2. Voice Form for Multi-service VLAN - Configuration 2 Data fill the Triple-Play Form. Since there are three different customers and types of interfaces, the Customer ID for each must be unique, and the slot.Port will be different. (The iMAP could be the same if all of the interface cards were on the same iMAP. Refer to the following table.
Installation Procedures Configuring multi-service VLAN FIGURE 7-177 Triple-Play Form EPON Interface - Configuration 2 FIGURE 7-178 7-218 Triple-Play Form FX Interface - Configuration 2 AlliedView NMS Administration Guide (Provisioning the iMG/RG)
Configuring multi-service VLAN FIGURE 7-179 Installation Procedures Triple-Play Form ADSL Interface - Configuration 2 7.10.13.3 Creating a Video and Data/Voice VLAN (Configuration 3) In this configuration, the Video VLAN is a separate VLAN, and data and voice share a single VLAN. Refer to the following figure and notes in 7.10.13 before performing the procedure.
Installation Procedures Configuring multi-service VLAN = video VLAN (VID 40) = IP Subnet = shared (voice, data) VLAN (VID 10) iMG646PX-ON = 10.56.7.223 ONU 4.0.0 ETH 4.0.0 FXS FXS Ethernet Data to PC 10 10 EPON = 172.16.33.18 BD Fiber 40 Ethernet Ethernet Video to Set Top Box Video to Set Top Box Video Head iMG646 Customer = 10.56.7.
Configuring multi-service VLAN 1. Installation Procedures Create the appropriate iMG profiles. Refer to the following table and figures. TABLE 7-36 iMG Forms for Voice, Video/Data VLAN (Configuration) 2 Form Name Attributes Reference General iMG_one_data_two_video SInce the port and VLAN configuration is the same for all iMGs, the same General Form is used in all configurations Figure 7-165 - Mgmt.
Installation Procedures Configuring multi-service VLAN FIGURE 7-182 7-222 Video Form for Multi-service VLAN - Configuration 3 AlliedView NMS Administration Guide (Provisioning the iMG/RG)
Configuring multi-service VLAN Installation Procedures FIGURE 7-183 2. Voice Form for Multi-service VLAN - Configuration 3 Data fill the Triple-Play Form. Since there are three different customers and types of interfaces, the Customer ID for each must be unique, and the slot.Port will be different. (The iMAP could be the same if all of the interface cards were on the same iMAP. Refer to the following table.
Installation Procedures Configuring multi-service VLAN FIGURE 7-184 Triple-Play Form EPON Interface - Configuration 2 FIGURE 7-185 7-224 Triple-Play Form FX Interface - Configuration 3 AlliedView NMS Administration Guide (Provisioning the iMG/RG)
Configuring multi-service VLAN FIGURE 7-186 Installation Procedures Triple-Play Form ADSL Interface - Configuration 3 AlliedView NMS Administration Guide (Provisioning the iMG/RG) 7-225
Provisioning the iMG/RG (no iMAP or AW+) Overview 7.11 Provisioning the iMG/RG (no iMAP or AW+) 7.11.1 Overview Note: Section 7.6.9 provides an overview of provisioning the iMG/RG on AlliedWare Plus (AW+) devices, and how it has the same feature coordination as with iMAPs. When both the iMG/RG and upstream port are controlled by the NMS, certain provisioning features can be coordinated, allowing the administrator to provision, query, and control one or more iMG/RGs quickly and efficiently.
DHCP Provisioning Provisioning the iMG/RG (no iMAP or AW+) Pre-provision: - Fill out MAC Address of the iMG/RG on the Triple Play form - RGbootConfigurator set up with Download file with TFTP Enable - dhcpd.
Provisioning the iMG/RG (no iMAP or AW+) FIGURE 7-188 DHCP Provisioning dhcpd.conf File - Snippet 7.11.2.2 iMGs/RGs at Release 4 and above (NextGen) As described above, the TFTP Discovery option is used to handle customer provisioning without an iMAP or AlliedWare Plus upstream device and without forwarding DHCP Relay messages to the NMS (option 82). The iMGs at release 4 and above do not support TFTP discovery, and so the RGbootConfigurator does not have the TFTP Discovery option (tab 4; refer to 7.2.
GUI Provisioning Provisioning the iMG/RG (no iMAP or AW+) 7.11.3 GUI Provisioning With the Display Preferences feature (5.6.3), the administrator sees only the fields that are relevant for the provisioning scenario, and fields that need to be filled in are highlighted as the user fills out the fields. In the Display Preferences GUI, there is the iMG/RG Configuration Panel. When selected, the Triple Play form limits the shown fields to only those that are iMG/RG related. Refer to the following figures.
Provisioning the iMG/RG (no iMAP or AW+) FIGURE 7-190 7-230 GUI Provisioning Triple Play Form without iMAP-related Fields AlliedView NMS Administration Guide (Provisioning the iMG/RG)
GUI Displays Provisioning the iMG/RG (no iMAP or AW+) 7.11.4 GUI Displays Once the iMG/RG is provisioned, the Details Panels are changed as follows: • There is no Eth/ADSL tab. • The statistics tab doesn't have PMON or RMON stats • The graph Stats Tab only lists iMG stats Refer to the following figure.
Provisioning an iMG/RG with the LAN4 Feature Overview 7.12 Provisioning an iMG/RG with the LAN4 Feature 7.12.1 Overview The AlliedView NMS can manage the ADSL iMG 624/34 family over the Ethernet lan4 interface. Moreover, the iMG/RGs must be using the 3-7 release and up. Refer to the following figure. Note: In this configuration the 624/634 becomes a replacement for the manufacture discontinued iMG-613TX. The new iMG6x4-R2 only supports iMG firmware version 3-7 and up.
Profiles Provisioning an iMG/RG with the LAN4 Feature FIGURE 7-193 RG General Profile - Port 4 has Management Option Also note that once “Management” is selected for a Port in the Create Profile wizard, the Admin State of the node is automatically set to “Enabled” and the user is not allowed to set it to “Disabled” as long as the service is set to “Management”. Refer to the following figure.
Provisioning an iMG/RG with the LAN4 Feature Service Management GUI 7.12.3 Service Management GUI Once the RG is discovered and configured by the NMS, the “Management” service is not used by the system. Once the NMS has discovered the node is managed via LAN 4 it no longer allows the customer to change the port 4 service in the View/Modify wizard. This is accomplished by removing the Port 4 entry in the “Port Assignments” table of the iMG/RG., as shown in the following figure.
Custom View Provisioning an iMG/RG with the LAN4 Feature FIGURE 7-196 Selecting Properties for a Custom View In the next frame that opens select the “Additional table Columns” button, as shown in the following figure.
Provisioning an iMG/RG with the LAN4 Feature FIGURE 7-197 Custom View Selecting Additional Table Columns From here additional properties that are in the database can be entered and labeled. In our case the property we need to enter is “adslLinkConnected”, the label chosen for this example is “Adsl Mgmt”, indicating whether the iMG/RG is managed via an ADSL port. Refer to the following figure.
Custom View Provisioning an iMG/RG with the LAN4 Feature FIGURE 7-198 Adding AdslMgmt Column The end result of apply this custom view is shown below. The top two RGs show an ADSL managed 634B-R2 box and a LAN4 managed 634B-R2 device, as shown in the following figure.
Provisioning an iMG/RG with the LAN4 Feature Procedure - Initial Installation of iMG with LAN4 7.12.5 Procedure - Initial Installation of iMG with LAN4 In the following procedure, an iMG634B is pre-provisioned at the NMS; the customer then connects the LAN4 port as the uplink and then powers up the iMG. 7.12.5.1 Pre-provision the NMS 1. Ensure the correct firmware and bootstrap files available and are loaded using the Boot Load configurator.
Procedure - Initial Installation of iMG with LAN4 FIGURE 7-201 4. Provisioning an iMG/RG with the LAN4 Feature Triple-Play form Using General Profile for LAN4 Review the iMG/RG table. Note that there are still no associated profiles and no IP address, as shown in the following figure. FIGURE 7-202 iMG Pre-provisioned 7.12.5.2 Connect the iMG and Power On 5. Connect the customer equipment to one or more LAN ports 1, 2, and 3. 6. Plug the ethernet uplink into LAN4. 7. Power on the iMG. 8.
Provisioning an iMG/RG with the LAN4 Feature Procedure - Initial Installation of iMG with LAN4 FIGURE 7-203 9. iMG Provisioned using LAN4 The tabs for the Details screen are the same as an ADSL uplink, with the one difference the Port Assignments tab has no port 4, as shown in Figure 7-195.
Deprovision the iMG and Re-provision with the ADSL UplinkProvisioning an iMG/RG with the LAN4 Feature 7.12.6 Deprovision the iMG and Re-provision with the ADSL Uplink In this procedure, the iMG that currently uses LAN4 for the uplink is de-provisioned and then re-provisioned using the ADSL port as the uplink. 7.12.6.1 Deprovision the iMG with the LAN4 Uplink 1. Right click on the iMG and select De-provision Customer iMG/RG. Select all of the options, as shown in the following figure. FIGURE 7-204 2.
Provisioning an iMG/RG with the LAN4 FeatureDeprovision the iMG and Re-provision with the ADSL 7.12.6.2 Pre-provision the iMG for ADSL Management 3. If not done already, create profiles for the iMG. If the service/VLAN configuration is the same, the only profile that is different is the General Profile, with the Port Assignments tab having port 4 not set to Management. 4. Fill in the Triple Play Form with the profiles, and select an ADSL port for the Slot.Port, as shown in the following figure.
Deprovision the iMG and Re-provision with the ADSL Uplink LCFO 7.13 LCFO The Loop Current Feed Open option is used to indicate that the calling/called party has gone onhook and is a useful feature for businesses that have key systems that transfer calls. This is available on all iMGs that are 3-7 and up. Both MGCP and SIP are supported.
LCFO Deprovision the iMG and Re-provision with the ADSL Uplink FIGURE 7-209 Advanced VOIP Attributes (SIP) - LCFO The LCFO option is also displayed from the “Advanced VOIP Params...” button that is on both the Port Management View/ Modify “Voice Service” tab, and the iMG/RG Voice Service Profile display. Note: When LCFO is enabled, it applies to all VoIP lines on the iMG/RG.
iMG GR909 Diagnostics iMG/RG Diagnostic Features 7.14 iMG/RG Diagnostic Features This section lists and describes the diagnostic features that are available for the various iMG/RG models. 7.14.1 iMG GR909 Diagnostics In the MOD iMGs and the iMG726-BD-ON, the GR909 diagnostic feature was added in release 3.7.4. In NMS release 12.0, the NMS supports this GR-909 diagnostic functionality. With the NMS, the user can view and modify voice enabled lines on a CPE.
iMG/RG Diagnostic Features iMG GR909 Diagnostics • Port State These are polled from the device and updated approximately every 30 seconds while the tab is displayed. Each line has an internal and external test results field. When a row is selected, the last diagnostic results are displayed in the details panels. The Test check box selects lines that the buttons will perform actions against.
iMG LAN Diagnostics iMG/RG Diagnostic Features 7.14.2 iMG LAN Diagnostics In the MOD iMGs and the iMG726-BD-ON, the LAN diagnostic feature was added in release 3.7.4. In NMS release 12.0, the NMS supports this LAN diagnostic functionality. With the NMS, the user can diagnose CPE LAN ports. This diagnosis will detect faults in the subscriber's private network cables.
iMG/RG Diagnostic Features iMG LAN Diagnostics FIGURE 7-214 Warning when Diagnosing LAN Ports While diagnosis is underway, the test results display “Working” as shown below. FIGURE 7-215 LAN Port Diagnostics in Progress When completed, the results for each interface will be displayed in the Test Result field. Notice the Glan interface, when present, will contain an additional Tx/Rx pair.
iMG LAN Diagnostics iMG/RG Diagnostic Features FIGURE 7-216 LAN Port Diagnostics Complete For more information on these tests refer to the ATI Gateway Product Family Software Reference Manual.
System Power Management System Power Management 7.15 System Power Management This feature allows the user to modify power management for the device. When enabled at the device level, specified ports immediately shut down, usually so that services such as lifeline POTS can continue as long as possible on battery backup. When disabled, battery power traps are not sent from the device and port-based power management settings will have no effect. The table below shows iMG devices running 3.
System Power Management System Power Management FIGURE 7-217 System Power Management - RG General Profile AlliedView NMS Administration Guide (Provisioning the iMG/RG) 7-251
System Power Management FIGURE 7-218 LAN Ports Power Management System Power Management - iMG/RG -> Mgmt. Info 7.15.2 LAN Ports Power Management In 3-8, there is also for certain iMG/RGs the ability to configure power management per LAN port, so that a port is automatically disabled in case of power failure. (Before 3-8, some devices had a default setting that of disabling all LAN ports except port 1.) The NMS supports this feature on iMG/RGs as listed in Table 7-38.
LAN Ports State System Power Management FIGURE 7-219 LAN Port Power Management on Service Management Form 7.15.3 LAN Ports State In the Service Management Form for iMG/RG -> Port Assignments, the field Oper. State shows the state of the port: • Up - Include the time the link has been active • Down - The port is out of service because of a problem or it has been disabled. • Power Down - The port is out of service because of the Port Power Management feature.
System Power Management LAN Ports State FIGURE 7-220 7-254 Oper.
TEL Ports Power Management System Power Management 7.15.4 TEL Ports Power Management In 3-8, there is, similar to the LAN Port Power Management, the ability for certain iMG/RGs the ability to configure power management per voice port, so that a port is automatically disabled in case of power failure. The NMS supports this feature on iMG/RGs as listed in Table 7-38.
LAN Flow Control Voice Ports State • Powered Down - The Power Management Feature has activated and on the voice port the Disable on Power Failure was set to Enabled. This status field can be seen on Figure 7-221. 7.16 LAN Flow Control On ingress traffic, when internal ingress queues are almost full or the rate limit is exceeded, the iMG/RG sends a PAUSE frame for all traffic on the port. (The downstream device must ensure traffic is not lost.
Voice Ports State LAN Flow Control FIGURE 7-223 Flow Control for LAN Ports - Service Management Form AlliedView NMS Administration Guide (Provisioning the iMG/RG) 7-257
Port-Based Rate Limiting - Reference Voice Ports State 7.17 Port-Based Rate Limiting - Reference Following are the rules and tables to use to select port-based rate limiting for the iMG/RG for that include release 3-7. The settings that are possible depend on the type of iMG/RG and the software release that the device is using. The following table lists the device types and loads supported. Refer to this table when reviewing the rate limits. Note: A value of 0 disables the tx or rx ratelimiting function.
Voice Ports State TABLE 7-39 Port-Based Rate Limiting - Reference Functional Groupings of iMG/RG (Continued) Group Model Load Name Characteristics Uniqueness ADSL B iMG624A-R2 iMG624A-R2 8/32 Meg Flash/RAM iMG634A/B-R2 iMG634A/B-R2 Marvell Switch iMG634WA/WB-R2 iMG634WA/ WB-R2 Solos Processor Third Generation ADSL CPE Greater performance - able to support 2 INP.
Port-Based Rate Limiting - Reference 7-260 AlliedView NMS Administration Guide (Provisioning the iMG/RG) Voice Ports State
8. Setting Up Performance Management 8.1 Overview Performance monitoring basically means collecting useful data from network devices and determining how efficiently the network is functioning. Performance is measured based on factors such as: • Number of bytes of data received (over a period) by a particular interface of a device. • Number of bytes of data sent (over a period) by a particular interface of a device. • An estimate of the interface's current bandwidth in bits per second.
Data Collection Screen Overview Use the following table to locate the task you wish to perform. Use the screen or form name to locate the relevant section. TABLE 8-1 Task List for Performance Monitoring Task Screen / Form Name (if Applicable) Section Data Collection Screen Configured Collection (8.2.2) Data Collection (Statistics) - Overview (8.3.1) - Create Polling Filters Create, Modify, Delete (8.3.2) - Create Statistic DataCollection Detailed Properties (8.3.
Overview Data Collection The following table lists the components in.the following figure. TABLE 8-2 Data Collection Screen Components Component Description for Data Collection Screen Components Property Columns For every statistic the associated properties are displayed in columns, such as Statistic name, Poll ID, Data Identifier, DNS Name, interval etc. Some of the properties are as follows: Statistic Name - A string to identify the Statistic uniquely.
Data Collection Polling Objects FIGURE 8-2 Data Collection Flow The flowchart elements are as follows: • Managed Object - Created by the Topology feature, it is an entity that represents a device or part of a device (such as a port, card, or interface), and has properties. • Polling Object - Created by Performance Management, it is an object that has two properties: • Match Criteria • Data Collection Criteria • Polled Data - The actual name (statistic) for the data to be collected in the database.
Polling Objects Data Collection FIGURE 8-3 Modify Polling Properties Form - File 8.3.2.1 Adding a Polling Object To add a polling object: 1. Select the Add radio button under the list of polling objects (left panel). 2. Fill in the fields under Polling Properties as follows: • Name - Required, a string to identify the Polling Object. • Status - Checked means active and so the data collection for the associated Polled Data can be done.
Data Collection • • • • Polling Objects Global: status, type, managed, Boolean: isGroup, isContainer, isSNMP, is DHCP, isRouter, isNode, isNetwork, isInterface, System: sysName, sysOID, Interface: ifSpeed, ifDescr, ifIndex Use the More and Fewer buttons to get the correct number. Note: The Fewer button will remove the last criteria you added. The criteria are set as an AND condition. To change this, define a User Class. Contact ATI support for examples of user class files on the AlliedView NMS Server.
Polling Objects TABLE 8-3 Data Collection Data Configuration Fields Field Description Save Collected Data If unchecked, specifies data will not be stored, and can be viewed only by the Real Time monitoring using Current StatisticGraph you do not want to store the collected data, “uncheck” this check box. Default: True (Checked). Save Absolute This option is applicable only for Counter type OIDs. By default, data collected for Counter type OIDs is not stored as it is.
Data Collection 3. Add a Statistic Under Collection Statistics, select a Data Object from the list and change the field values as needed. Note: Check the Advanced checkbox to enable all of the fields and checkboxes, if necessary. Repeat for each Data Object you need to change. 4. When you are done, click Apply to make the change to the database. 8.3.2.3 Delete a Polling Object Deleting a Polling Object means to delete all the statistics associated with the Data Identifiers.
Add a Statistic Data Collection FIGURE 8-4 Data Collection for Adding a Statistic The following table lists the properties and descriptions. TABLE 8-4 Properties for Adding a Statistic Property Description Name Any meaningful string for the Data Identifier. Required. SnmpVersion One of the three SNMP versions - VI, V2 or V3. Required. Read Community Enter the string with which the devices are identified in a network.
Data Collection TABLE 8-4 Add a Statistic Properties for Adding a Statistic (Continued) Property Description Active If you uncheck the check box, the data collection will be stopped for this OID. (The statistic row once created will be blue.) To activate data collection, check the box. Default value: True (checked). Period The time interval for periodic data collection. For example, if set to 2, for all the Data identifiers, data will be collected once in every 2 seconds. Default value: 300 seconds.
Overview TABLE 8-4 Threshold Notification Properties for Adding a Statistic (Continued) Property Description parentObj Name of the Managed Object which acts as the parent for this Data Identifier. Poll ID A unique number associated with each Statistic to identify the Statistic. Poll ID is automatically generated so no two Statistics will have the same Poll ID. Advanced Allows the optional values to be modified. 8.3.3.
Threshold Notification Overview • Min - When collected data drops below a value, report an error • Equal - When collected data equals a value, report an error • What message should be generated when the threshold is exceeded. • At what value should this threshold get reset. Thresholds are defined and associated with statistics. A single statistic can have many thresholds indicating a severity such as Critical, Major, Minor, etc.
Add Threshold Threshold Notification Assume you want to set the number of pages to be loaded in a printer to depend on the Toner level. Moreover, when the toner level is 80% of the number of pages to be printed, you wish to be notified. To achieve this, you create a Percentage Threshold with a value 80. Collect data for two Statistics, Toner level and Number of pages in the printer. Divide the first by the second to find the percentage.
Threshold Notification Add Threshold FIGURE 8-6 Threshold Properties (type long) The following table lists the properties for the threshold form. TABLE 8-5 Properties for Thresholds Property Description Name Any action in a network can be captured and an appropriate name can be given to the event generated on such actions. For example, when ManagedObjects are added into the database an event can be generated. This event may be named as AddMOevent.
Associate Thresholds with Statistics TABLE 8-5 Threshold Notification Properties for Thresholds (Continued) Property Description Threshold Type Type of Threshold value you are going to specify. Possible values are Max, Min or Equal: Max - If Collected value exceeds Threshold value, an event will be generated. Min - If Collected value is less than Threshold value, an event will be generated. Equal - If Collected value is equal to Threshold value, an event will be generated.
Threshold Notification Note: 8-16 Associate Thresholds with Statistics You cannot modify the threshold values from this dialog box.
9. Setting Up Fault Management 9.1 Overview Network Events are entities that represent the various happenings in the network devices. Events can convey general information or the current status of the devices in a network. There are many powerful tools that allow an Administrator to control how managed objects (specific aspects of a device) report changes in their state.
Overview Task Overview FIGURE 9-1 Fault Management Configuration for the AlliedView NMS 9.1.2 Task Overview The following table lists the tasks that can be done at the Application interface. If you are using NMS, use the Screen Name as well to locate the relevant section. For all menu options, refer to the AlliedView NMS User Guide Appendix. TABLE 9-1 Task List for Fault Management Task Form/Screen Name (if Applicable) Section Review Events Screen Network Events (9.
Task Overview TABLE 9-1 Event View Task List for Fault Management (Continued) Task Form/Screen Name (if Applicable) Section Configure Event Parsers Telesis Event Parser Configuration (9.4) Configure Event Filters Telesis Event Filter Configuration (9.5) Review Alarm Screen Alarms (9.7) Alarm Propagation Alarms (9.8) Configure Alarm Filters Telesis Alarm Filter Configuration (9.9) Configure System Logs (System Log Configuration) (9.
Configuring Trap Parsers Task Overview FIGURE 9-3 Trap Parser Configuration Form Select a Trap Parser from the list to see how the fields are configured for that Trap parser. The following table describes these fields at a general level, as well as the option buttons. Many of the fields will have a variable name, discussed after this table. TABLE 9-2 Trap Parser Configuration Form Option Description Trap Port Port that receives the trap.
Task Overview TABLE 9-2 Configuring Trap Parsers Trap Parser Configuration Form Option Description TrapOID A TrapOID uniquely identifies an SNMP v2c or SNMPv3 trap and comes along with the Trap PDU. The TrapOID can be a match criteria. When the TrapOID has a value that starts with the Object Identifier the match criteria is met. Wildcard (*) can be used. When the Trap Object Identifier of the incoming trap must match exactly the TrapOID, put the value in brackets (<>).
Configuring Trap Parsers TABLE 9-2 Using Trap Values in the PDU Trap Parser Configuration Form Option Description Load from MIB Loads the trap file from the mibs directory so the traps can translated to a trap parser. This is explained in more detail below. Load from File Loads the trap file from the conf directory. This is explained in more detail below. Save to File Brings up the Save to File form. Save the trap parsers as a file. The default path is to the conf directory.
Using Trap Values in the PDU TABLE 9-3 Configuring Trap Parsers Tokens to Access the Properties of the Trap PDU (Continued) Token Description $Source If the device corresponding to the source address contained by the trap received, has already been discovered by AlliedView NMS, then this token will fetch the name of the parentManaged object, corresponding to the interface object matching the source address of the received trap.
Configuring Trap Parsers TABLE 9-3 Loading from a MIB Tokens to Access the Properties of the Trap PDU (Continued) Token Description $AgentMO This tag (or token) facilitates the accessing of managed object properties.The tag can be used to access any properties of the Parent managed object for the interface object corresponding to the agent address of the received trap. (Fetching the Managed Object is similar to the $Agent tag mechanism).
Reordering the Trap Parser List Configuring Event Parsers same matching criteria are replaced. If the Trap Parser name is the same, there is confirmation prompt to replace the existing one. Once loaded, the Apply to Server button makes the changes permanent. The trap parsers in the trap.parsers file will load the next time the AlliedView NMS server starts. 9.3.4 Reordering the Trap Parser List The list for Trap Parsers is in the order the AlliedView NMS tries to find a match.
Configuring Event Parsers Setting Event Parsers [ FIGURE 9-4 Event Parser Configuration Form 9.4.2 Setting Event Parsers Select an Event Parser from the list to see how the fields are configured for that Event parser. The following table describes these fields at a general level, as well as the option buttons. Many of the fields will have a variable name, discussed after this table. TABLE 9-4 Event Parser Configuration Form Option Description Name Name of the event.
Setting Event Parsers TABLE 9-4 Configuring Event Parsers Event Parser Configuration Form (Continued) Option Tokenizer String Description Allows you to break up the input field into a series of tokens that can then be used in the output Event object. The tokenizer definition is a string with the tokens represented by $1, $2, etc. Only positive integers are allowed following '$'.
Configuring Event Parsers TABLE 9-4 Setting Event Parsers Event Parser Configuration Form (Continued) Option Description More Configure additional criteria based on other properties of the event, which could also include the User properties, apart from the given default set of Event properties. In the first column of the dialog, specify the “name of the property”, which could be any valid property of the Event including its user property.
Relationship Between User Properties and Custom Views TABLE 9-4 Configuring Event Parsers Event Parser Configuration Form (Continued) Option Description Help Invokes this table. Close Closes the form. If no changes were applied to the server, they are lost. If changes have been made, there is a prompt on whether to apply the changes. If the event object contains the trap pdu information, you can make use of the trap pdu information while defining the output events.
Configuring Event Parsers FIGURE 9-5 Changing Severity of Default Events (i.e. Status Update Fail- Setting the Event Parser to Produce Alarms for SYSLOG The usual scenario would be the device in the Physical Network view would show the device has a major alarm. Right clicking Alarms/Events -> Alarms on the affected device would show Figure 9-6. (This would also show up in the Events view as a network event.).
Changing Severity of Default Events (i.e. Status Update Failure) Configuring Event Parsers The process involves creating an Event Parser that examines all events, identifies the ones pertaining to lost connectivity, and changes their severity from Major to Critical. 9.4.5.2 View the Default Status Failure Event 1. Disconnect a device, which will produce the Event Node Failure. 2. Select the device and click on Update Status to force a default event to occur. 3.
Configuring Event Parsers Changing Severity of Default Events (i.e. Status Update Fail- FIGURE 9-8 5. Viewing Object Details Copy the message text (using ctl-c) so the text can be used in the new event parser to identify events of this type. 9.4.5.3 Bring up the Event Parser Configuration Dialog From the event browser, select Edit -> Configure ->Event Parsers. The Event Parser Configuration Form will appear, as was shown in Figure 9-4. 9.4.5.4 Configure the Event Parser 1. Click on Add Event Parser.
Changing Severity of Default Events (i.e. Status Update Failure) FIGURE 9-9 Note: Configuring Event Parsers Creating an Event Parser and Changing the Severity The Match Strings are used to identify which events you want to change. The Output Strings say how to change those events. In this case we're changing all those that match the existing message text exactly. 9.4.5.5 Limit to a Specific Device Type If you want to you can restrict this modification to one device type.
Configuring Event Parsers Changing Severity of Default Events (i.e. Status Update Fail- 3. Click on the tic box, and then OK to add the type criteria. 4. The Event Parser Configuration Form is now the only form that is on the screen. Click on Update, Apply, and Close. Now only AT-AR745's when disconnected will go critical and all the others will still be major. 9.4.5.6 Ensure the Event Parser is created 1. Select Edit -> Configure ->Event Parsers again. 2.
Changing Severity of Port-based Alarms Configuring Event Parsers 9.4.6 Changing Severity of Port-based Alarms Two attributes for the Event object are PortProfile and Customer ID. Using these attributes, the administrator can configure an Event Parser that can filter an Event that includes these attributes and changes the default priority.
Configuring Event Filters Overview FIGURE 9-13 Configuring Event Parser with portProfile Property 9.5 Configuring Event Filters 9.5.1 Overview Event Filters provides a way to setting a matching criteria to filter events and then configuring an action (such as an email) for these events. Select Edit -> Configure -> Event Filters from the main menu of the Network Events Panel. The Event Filter Configuration form appears, as shown in the following figure.
Overview Configuring Event Filters FIGURE 9-14 Event Filter Configuration Form AlliedView NMS Administration Guide (Setting Up Fault Management) 9-21
Configuring Event Filters Setting Event Filters 9.5.2 Setting Event Filters The user can add, modify, or delete an Event Filter from the left side of the form. Refer to the following table for all options. TABLE 9-5 Event Filter Configuration Form Option Description / Fields Filter Name Name of the filter. This field matches the filter chosen in the Configured Filter List.
Setting Event Filters TABLE 9-5 Configuring Event Filters Event Filter Configuration Form Option Description / Fields Setting Match Criteria Determines whether the incoming event should be filtered or not. If a field is left blank, it is automatically matched. The condition for the event filter to be applied is that all the match criteria specified should be satisfied. If one criteria fails, the filter will not be applied. The following expressions can be used, while specifying the match criteria.
Configuring Event Filters TABLE 9-5 Setting Event Filter Actions Event Filter Configuration Form Option Description / Fields Delete Filter Icon Allows a Filter Name to be deleted. Update Filter Updates the Event Filter so it is ready to be applied to the NMS server. Cancel File Cancels any changes made. Apply Makes changes to the server. Help Brings up this section of the User Guide. 9.5.
Setting Event Filter Actions TABLE 9-6 Configuring Event Filters Action Types and Associated Fields for Event Filter Actions (Continued) Action Type Filter Action Detail Description Run Command Action Run Command Action Name Name of this action required for identification. Run Command This is used to specify the actual command to be executed in the NMS server machine. The command specified here should not require a shell to run unless the shell program is specified in the command.
Configuring Event Filters TABLE 9-6 Example of Setting an Event Filter Action Action Types and Associated Fields for Event Filter Actions (Continued) Action Type Filter Action Detail Description Send Trap Action Send Trap Action Name Name of this action required for identification Trap Destination This is used to specify the hostname (IP address) of the host to which the SNMP trap will be sent. Destination Port The port to which the trap is to be sent.
Setting Up Event Filters for SYSLOG Events 6. Configuring System Logs (NMS System Log Server) Click OK. To add more actions, click and add more action types and details. Cancel any filters or actions by clicking Cancel as they appear in context. The resulting alert filters and actions can be reordered by drag and drop. To delete an alert filter, select a filter from the list and then click also be deleted. from the Alert Filter panel.
Configuring System Logs (NMS System Log Server)Setting Up Event Filters for SYSLOG Events • The filtering of logs produced by the device that are sent to the NMS is controlled by applying log filters. This is described in 9.6.2. • Controlling what actions to take upon the reception of system logs is controlled through the Event Filter, described in 9.5. Details on filtering for system logs are given in 9.5.5.
Configuring the System Log Server Configuring System Logs (NMS System Log Server) 9.6.1 Configuring the System Log Server The AlliedView NMS System Log Server is automatically configured to Enabled during installation. You can view the current configuration and modify it to better meet your requirements, if necessary. To view the current configuration, select Tools -> System Log Configuration for the Panel-Specific Menu. The System Log Server Configuration form, shown in the following figure, will appear.
Configuring System Logs (NMS System Log Server) Applying Log Filters • Log to Database - Enables or disables storing of logs in the NMS database. • Log to Local File - Enables or disables storing of the logs to a local file, /logs/syslog.
Configuring Log Actions Configuring System Logs (NMS System Log Server) FIGURE 9-16 Modify Log Properties Form - File To add a filter, select the desired filter in the Available Filters list, and then click Add>>. To remove a filter, select the filter you want to remove in the Apply Filters list, and then click <
Alarm View Display Disabling and Re-enabling Logs from a Device FIGURE 9-17 Log Management Viewer 3. To sort the logs, click the header on which you want to sort (e.g. Device SeqID, Device Date, etc.) until the desired sort is performed (up arrow for descending or down arrow for ascending). 4. Click Close to close the window. 9.6.5 Disabling and Re-enabling Logs from a Device You can disable logs from a device as follows: 1.
OTHER Event Type Alarm View Display FIGURE 9-18 Alarm View Main Panel Refer to the NMS User Guide for general information on navigating in the view and using the search tool.
Alarm Propagation Overview 9.8 Alarm Propagation 9.8.1 Overview In a network, components (managed objects) are in a hierarchy, and faults at one level usually affect the status of another level. Network administrators need to understand how the AlliedView NMS reports and propagates alarms so that they can control what alarms appear in the Alarm View and quickly locate and resolve them.
Controlling Alarm Propagation Alarm Propagation 9.8.2.1 Example 1 - Parent Object set to Max for Polling-Based Alarms (default) • The administrator sets the Tester attribute for interfaces (IF) in the MO Property Form to PING or SNMPPING, so if an interface fails, a major alarm is reported by the interface. • For the parent node, the administrator sets the Tester attribute to Max.
Configuring Alarm Filters Overview 9.9 Configuring Alarm Filters 9.9.1 Overview Alert filters are used to filter and modify the properties of an incoming alert. When the alert matches specified criteria, an action (such as sending an email) will occur. To parse alarms, select Edit -> Configure -> Alarm Filters from the main menu of the Alarms Panel. The Alert Filter Configuration form appears as shown in Figure 9-20.
Example to Configure Alarm Filter and Actions Configuring Alarm Filters 9.9.2 Example to Configure Alarm Filter and Actions 9.9.2.1 Summary Procedure Adding an alarm filter and an action is done as follows. Note: An alarm filter must have at least one action. 1. Click 2. Modify the alert filter name as needed and the match (Source and Severity) criteria fields. If needed, expressions can be used: wildcard (*), negation (!), and separators (,). Use the More option if needed.
Configuring Alarm Filters Example to Configure Alarm Filter and Actions FIGURE 9-21 2. Accessing the Alert Filters Window Create the filter and set up the basic criteria for filtering. The steps would be: 1. Select the button on the bottom left 2. Rename the filter to something that will indicate its use. 3. Add a match criteria. Here the source is the incoming address and it can be wild-carded by using the “*”. 4. Refer to the following figure, which displays these three steps.
Example to Configure Alarm Filter and Actions Configuring Alarm Filters 3. To create a criteria beyond the Source and Severity, select Advanced. The Match Criteria Properites sceen appears. 4. In this example we will setup a filter to eliminate an alarm that comes in with the message “Unable to login to this device….”. Enter this using a wildcard in the Message field as shown in Figure 9-23, then select OK. 5. Back on the Alert Filters screen, we need to associate it with some action to take.
Configuring Alarm Filters FIGURE 9-24 6. Example to Configure Alarm Filter and Actions Add Action Window (Notifications when Criteria Met) Since we want to suppress the “Unable to Login..” alarm so that we no longer see it in the alarm list, select the Suppress Action type and New.button, as shown in Figure 9-24. The Suppress Action window appears, as shown in the Figure 9-25. FIGURE 9-25 7.
Example to Configure Alarm Filter and Actions 8. Back on the Add Action screen, select the Noticfication Type you created (here Suppress_Alarm) and Select Add, as shown in Figure 9-26. FIGURE 9-26 9. Configuring Alarm Filters Adding an Action to the Alert Filter This returns you to the Alert Filters window, and Suppress_Alarm is added to the Actions List. Refer to Figure 9-27.
Configuring Alarm Filters 10. Example to Configure Alarm Filter and Actions With the attributes for the Alert Filter complete, click on Apply. The new filter name (Filter_iMG_LoginFailure) is now added to the list of Alert Filters, and this filter will be applied when processing alarms. Refer to the following figure. FIGURE 9-28 Alert Filter added to List 11. With the Alert Filter added, Click on Load/Save. This brings up the Filter Details window that allows you to save the filters to the alert.
Overview Retrieval of Alarms during (Re)Discovery (Telesis MAP Devices Only) 9.10 Retrieval of Alarms during (Re)Discovery (Telesis MAP Devices Only) 9.10.1 Overview Prior to release 6.0, the (re)discovery process included establishing communication and transferring configuration information, but did not include alarm processing. In release 6.0, a feature, Alarm Retrieval During (Re)Discovery, allows the administrator to have alarm retrieval included during (re)discovery.
Retrieval of Alarms during (Re)Discovery (Telesis MAP Devices Only) Restrictions / Limitations FIGURE 9-29 Retrieve Alarms Form The following options are available on the retrieve alarms dialog: • Enable retrieve alarms: When selected it will enable this feature and current alarms on MAP devices will be displayed during discovery. • Display retrieved Info alarms: When selected it will enable displaying retrieved alarms that have 'Info' severity.
10. Using the HTML Interface 10.1 Overview The administrative tasks that can be done from the html interface are: • Manage/Unmanage • Start/Stop Discovery • Delete Object(s) The html interface and how these tasks are accessed are explained in detail in the AlliedView NMS User Guide. Note: To quit the html interface, use the Logout option. Closing the browser will require 30 minutes for the client session to time out. Refer to the AlliedView NMS User Guide for details.
Overview 10-2 AlliedView NMS Administration Guide (Using the HTML Interface)
11. Built-in Browsers - SNMP MIB and CWMP 11.1 Overview - SNMP MIB Management Information Bases (MIBs) are a collection of definitions that define the properties of the managed objects. To enable a management application to operate intelligently on the data available on the managed device, the manager needs to know the names and types of managed objects in the device. This is made available by the MIB modules. A MIB describes a set of managed objects.
MIB Browser Screen and Toolbar 11.2 MIB Browser Screen and Toolbar The information contained in the MIBs can be retrieved and viewed by accessing the MIB Browser from the Tools menu. The Mib Browser panel is shown in the following figure. FIGURE 11-1 MIB Manager View The operations allowed with the Mib Browser are available through the series of icons in the Toolbar at the top of the Mib Browser’s main window. You can hide the Toolbar by de-selecting the ToolBar item in the view menu.
Overview Loading and Unloading MIBs 11.3 Loading and Unloading MIBs 11.3.1 Overview To load the MIB files in the Mib Browser, use the LOAD MIBs button or select File -> Load MIB menu item. This brings up the Load a Mib File Screen as shown in the following figure. Note: The MIB Browser for NMS is strict on syntax, and if there is an error, such as an extra comma in the object type list, the MIB will not load.
Loading and Unloading MIBs Loading Options (Directly, as Compiled Files, Using MySQL) 11.3.2 Loading Options (Directly, as Compiled Files, Using MySQL) The Mib Browser has the following Mib Settings for loading the MIBs, as shown in the following figure. FIGURE 11-3 Options for Loading MIBs • Loading MIBs directly. • Loading MIBs as compiled files. • Loading MIBs from database. You can also load MIBs directly in plain text format, although for large MIBs the loading time will be higher.
Loading MIBs from a Database Loading and Unloading MIBs The compiled MIB files reduce the loading time, leading to performance improvement. The applications and the applets have the option of loading the MIB files directly or as compiled MIB files. The Load MIBs from compiled File option is provided in the dialog box to decide whether to load MIB from compiled MIBs or not. By default, this option is enabled. If this is unchecked, the user can directly load the MIB file as provided.
MIB Browser Settings Unloading MIBs 11.3.6 Unloading MIBs To unload the loaded MIB, select the node of the MIB Tree then click the UNLOAD MIB icon or select the File -> UnLoad MIB menu item. This removes the MIB Tree of the unloaded MIB 11.4 MIB Browser Settings The Mib Browser can be used for MIB browsing and to view and operate on available data through an SNMP agent. The Mib Browser allows configuration of various options needed for SNMP operations.
Multi-Varbind Request MIB Browser – Table Operations To do multiple-variable SNMP SET, ensure that the proper OIDs and values are given in the text fields before adding them to the list. Check the Multi-Var check box before doing the multiple variable SET. To delete the varbind(s) from the list select the varbind(s) from the list and click Delete to delete the varbind(s) from the list. To edit the varbinds added in the list, select a varbind and click Edit.
MIB Browser – Table Operations TABLE 11-3 Multi-Varbind Request SNMP Properties (Continued) Option Functions for SNMP Properties Settings Pops up another dialog box in which the following options can be set. Polling Interval - sets the polling interval for the retrieval of the tables. By default, it is 5 seconds. Page Size (Rows) - sets the number of rows to be retrieved. No of Column View - sets the number of columns to be displayed in the SNMP Table - Panel. Default is 5 columns.
Multi-Varbind Request Trap Viewer 5. Right-click the table header, and then select the add a new row to the table option. This displays a window for entering the values of the table. 6. Set the value for the column with RowStatus syntax to 4 for creating a new row, and then enter the values. Note: 7. If the RowStatus is not present in the table definition, then you can only modify the existing row by double-clicking the corresponding cell in the table. Click OK after entering all the values. 11.
Trap Parser Overview The trap table has the following properties: • • • • Class - Defines the Severity of the Trap. Source - Displays the IP address of the source from where the trap was send. Date - Displays the date of receiving the trap. Message - By default, contains the VarBind list of the Trap, if any, else it is blank. To view more details of the received trap, right-click a table entry and choose View Trap Details. Sorting of trap table columns is done by clicking the corresponding columns.
Overview Trap Parser FIGURE 11-6 Trap Parser Editor Each incoming trap must have the Match Criteria to show the traps in the Trap Table. You may enter any number of parser match criteria into a single parser file with a different parser name. The Trap Viewer looks for a match criterion sequentially. Thus, if a match is found for a received trap, the trap is shown on the Trap Table.
Trap Parser Procedure to Create a Parser File • Enterprise OID - The enterprise field is the SNMP enterprise identifier in the trap, which is used to uniquely identify traps for a particular application. The parser is applied only when the trap enterprise field starts with the enterprise field you specify. The only exception is that when the enterprise field is left blank, the trap is allowed to be parsed. • OID and Value - This extends the match criteria.
Adding a Trap Definition from MIBs to a Parser File: Trap Parser 11.8.3 Adding a Trap Definition from MIBs to a Parser File: 1. Choose the MIB file (standard or any other) in the MIB File text field. 2. The setting of the MIB is automatically shown on the MatchCriteria and Output Event parameters sections. If any modification is made after saving to a file, you must click Mod below the Trap list box, and then choose the same file from the Save option.
Graphs Setting Trap Parser Parameters • Agent - 192.168.1.1 • Port - 4001 The TrapParser gets trap from any trap originator and parses the trap event. 11.9 Graphs The Mib Browser enables a real-time plotting of SNMP data on a graph. Currently, two types of graph are supported: line graph and bar graph. The SNMP data to be polled should be of integer or unsigned integer data type. Typically, the values that are plotted are of type Counter, Gauge, or Timeticks.
Setting Trap Parser Parameters CWMP 11.10 CWMP The CPE WAN Management Protocol (CWMP) is a messaging protocol designed for communication between the CPEdevices and the management system. Specifications for this protocol are written by The Broadband Forum (formally DSL Forum) in technical reports, and the TR-069 defines the messaging format based on XML for communicating using CWMP. Previously, the discovery process and also all NMS supported operations used CLI or SNMP to communicate to the devices.
CWMP 11-16 Setting Trap Parser Parameters AlliedView NMS Administration Guide (Built-in Browsers - SNMP MIB and CWMP)
12. Northbound Interface 12.1 Overview A northbound interface on an NMS/EMS allows other software applications (higher level network management systems) to communicate with (or manage) the lower level NMS without the user acting on the lower level NMS directly.
SOAP Implementation TABLE 12-1 Overview (Apache Axis) Northbound Interface APIs for Release 10.0 Capability Detail Autonomous events configuration for clients allow clients to receive network events from the NMS immediately without the need for the client to poll the NMS every time.
WSDL Note: SOAP Implementation With a standard northbound interface, the higher level NMS would not have to implement different clients to communicate with NMS/EMS from different vendors. However, specific interfaces may be more useful to the client because operations will be specific to clients' needs. 12.2.2 WSDL WSDL is a language used to describe the services published by an interface.
User Interaction Web Services Activation FIGURE 12-1 Client / Server Model for AlliedView NMS 12.3 User Interaction 12.3.1 Web Services Activation Web services in NMS will not be activated by default and can be activated at runtime when needed by the NMS administrator. When not in use the administrator can also deactivate web services provided by NMS. The script AT_WebService.bat/sh can be used to enable and disable the APIs when executed as below.
User Security User Interaction 12.3.1.3 Deactivate Web Services (Axis/SOAP) This operation must be done after the server is started. 1. Change directories to /bin 2. Execute AT_WebService.bat/sh with 'undeploy' parameter • AT_WebService.bat undeploy (for Windows installations) • AT_WebService.sh undeploy (for Solaris installations) 12.3.
User Interaction Available Operations • Use the WSDL provided with client code generator tools (e.g. wsdl2java, wsdl2cpp, etc.) to generate client stub source code for the client to use when calling remote objects. (faster and easier to follow) • Use an IDE software packages that read the WSDL and guide the client development based on the available interface.
Available Operations TABLE 12-2 User Interaction Operations Table Module / Operation Parameters Types Return Types Notes Inventory/ getNodes MO match criteria (Nodes) List of object properties (Nodes) Return a list of node object properties matching the criteria Inventory/ getCards MO match criteria (Cards) List of object properties (Cards) Return a list of node object properties matching the criteria Inventory/ getPorts MO match criteria (Ports) List of object properties (Ports) Return a
User Interaction TABLE 12-2 Available Operations Operations Table Module / Operation Parameters Types Return Types Notes Faults/ setEventTarget - Target server IP address None Sets up a target server and port as a receiver of events that match the specified criteria. None Remove the server with address and port from events receiver.
Provision Parameters TABLE 12-2 User Interaction Operations Table Module / Operation Parameters Types Return Types Notes Provision/ Provision parameters Status of the operation Status returned can indicate the operation has started or completed if time-out is specified. Provision parameters Status of the operation Status returned can indicate the operation has started or completed if time-out is specified. Provision parameters Status of the operation.
User Interaction TABLE 12-3 Provision Parameters Provision Parameters Keys Values Description UNTAGGED_VLAN Untagged VLAN for iMAP port TLS_VLAN A VLAN for transparent LAN PROVISION_DATA (TRUE/FALSE) Include iMAP port in provision DEPROVISION_DATA (TRUE/FALSE) Include iMAP port in deprovision PROVISION_RG (TRUE/FALSE) Include RG device in provision DEPROVISION_RG (TRUE/FALSE) Include RG device in deprovision RG_PROFILE_VLANS (TRUE/FALSE) Specify where to
13. Appendices 13.1 Exporting Tabular Data Data displayed in tabular form in the AlliedView NMS can be exported to a file on the NMS server or to your Web browser for viewing. Tabular data appears in the following views: • Fault Management • Performance • Network Inventory The procedure for exporting tabular data is the same for all of these views. Note: The one exception is the Performance view; this is explained separately, in 13.1.1.2.
Exporting Tabular Data Exporting the Entire Table FIGURE 13-2 Export Alarms Data Form - No Criteria Set The Export Alarms Data from consists of a destination panel and a database match criteria panel. In the destination panel, you can select the destination for the exported data as either a file on the NMS server or your Web browser. In the Database Match Criteria panel, you can specify the match criteria, a qualifier, and a match string.
Exporting the Entire Table 3. Exporting Tabular Data Click OK to export the data. A confirmation dialog box will appear indicating that the data export was successful. Click OK in the confirmation dialog box. The following figure shows an example of how to export all major alarms on device to file alarms_major using the percent sign (%) as the data separator. The resulting data file is described in 13.1.3. FIGURE 13-3 Export Major Alarms Data Example 13.1.1.
Exporting Tabular Data Exporting the Entire Table FIGURE 13-4 Viewing Instances in a Device for a Statistic When exporting the statistical data in a table, the user can isolate this instance as part of the match criteria. The following figure shows setting up the instance criteria for the statistic and the results (in a web browser). Note that the time between each polled value is 15 seconds.
Exporting Selected Items Exporting Tabular Data FIGURE 13-5 FIGURE 13-6 Setting the Criteria for Performance (Instance) Results of Performance Statistic by Instance (15-second Intervals) 13.1.2 Exporting Selected Items To export manually selected items from a data table, select the items you wish to export (use SHIFT+left-click to select multiple items), and then select Edit -> Export Selected Rows from the Panel-Specific Menu Bar.
Exporting Tabular Data FIGURE 13-7 Viewing a Data Export File Export PhysicalLinks Data Form - Exporting Selected Data The Database Match Criteria panel does not appear on this form since the items were manually selected. On this form, select a target for the exported data as described in the previous paragraphs. The resulting data file is described in the following section. 13.1.
Viewing Data on a Web Browser Exporting Tabular Data FIGURE 13-8 Exported Data File Example- File 13.1.4 Viewing Data on a Web Browser If you exported the data to your Web browser, the data will be displayed in a new browser window. An example is shown in the following figure. You can use the menus in your Web browser to view, print, or save the information.
Exporting Tabular Data Viewing Data on a Web Browser FIGURE 13-9 13-8 Tabular Data Displayed in a Web Browser AlliedView NMS Administration Guide (Appendices)
dhcpd.conf dhcpd Files 13.2 dhcpd Files Following is a complete example of a dhcpd file, with comments highlighted. There are five files, since DHCP-related configurations for each Access Island are placed in separate configuration files. 13.2.1 dhcpd.conf # dhcpd.
dhcpd Files dhcpd.conf } } on expiry { if ((substring(option vendor-class-identifier,0,8)="iMG646PX") or (substring(option er,0,9)="iMG646MOD")) { log (info, concat( " LEASE EXPIRE>> ",binary-to-ascii(10, 8, ".", leased-address), " MAC: ",binary-to-ascii(16,8,":",hardware), " associated to iMAP: ",(option agent.remote-id), " INTERFACE: ",binary-to-ascii(10, 8, ".", substring(option agent.circuit-id, 0, 2)), ", VLAN: ",binary-to-ascii(10, 16, "", substring(option agent.
dhcpd Includes dhcpd Files 13.2.2 dhcpd Includes 13.2.2.1 spsi-ai00-class # # # # # # # # # # # # # # # # # # # # # spsi-ai00-class for Service Provider Solutions Interop (SPSI) lab Access Island 0 Jul-15-08 JWS: modified for migration of nms server ip from 10.52.110.4 to 10.52.201.
dhcpd Files dhcpd Includes (option vendor-class-identifier = "iMG606BD")); option vendor-class-identifier "iMG606BD"; } class "SPSI-AI00-iMG606BD-R2Mgmt" { match if ((substring(option agent.remote-id,0,9)="SPSI-AI00") and (substring(option agent.circuit-id,2,2)="\x01\x2c") and (option vendor-class-identifier = "iMG606BD-R2")); option vendor-class-identifier "iMG606BD-R2"; } class "SPSI-AI00-iMG613RFMgmt" { match if ((substring(option agent.remote-id,0,9)="SPSI-AI00") and (substring(option agent.
dhcpd Includes dhcpd Files option vendor-class-identifier "iMG634A-R2"; } class "SPSI-AI00-iMG634WAMgmt" { match if ((substring(option agent.remote-id,0,9)="SPSI-AI00") and (substring(option agent.circuit-id,2,2)="\x01\x2c") and (option vendor-class-identifier = "iMG634WA")); option vendor-class-identifier "iMG634WA"; } class "SPSI-AI00-iMG646BDMgmt" { match if ((substring(option agent.remote-id,0,9)="SPSI-AI00") and (substring(option agent.
dhcpd Files dhcpd Includes } class "SPSI-AI00-iMG746MODMgmt" { match if ((substring(option agent.remote-id,0,9)="SPSI-AI00") and ((substring(option agent.circuit-id,2,2)="\x01\x2c") or (substring(option agent.circuit-id,3,2)="\x01\x2c")) and (option vendor-class-identifier = "iMG746MOD")); option vendor-class-identifier "iMG746MOD"; } class "SPSI-AI00-iBG915FXMgmt" { match if ((substring(option agent.remote-id,0,9)="SPSI-AI00") and (substring(option agent.
dhcpd Includes dhcpd Files option tftp-server-name "10.52.201.4"; option vendor-class-identifier "RG613TX"; } class "SPSI-AI00-RG624ABoot" { match if ((substring(option agent.remote-id,0,9)="SPSI-AI00") and (substring(option agent.circuit-id,2,2)="\x00\xc8") and (option vendor-class-identifier = "RG624A")); filename "ADSL/AI00/RG600A"; option tftp-server-name "10.52.201.4"; option vendor-class-identifier "RG624A"; } class "SPSI-AI00-RG634ABoot" { match if ((substring(option agent.
dhcpd Files dhcpd Includes option tftp-server-name "10.52.201.4"; option vendor-class-identifier "iMG616BD"; } class "SPSI-AI00-iMG616BD-R2Boot" { match if ((substring(option agent.remote-id,0,9)="SPSI-AI00") and (substring(option agent.circuit-id,2,2)="\x00\xc8") and (option vendor-class-identifier = "iMG616BD-R2")); filename "FIBER/AI00/IMG616BD-R2"; option tftp-server-name "10.52.201.4"; option vendor-class-identifier "iMG616BD-R2"; } class "SPSI-AI00-iMG616WBoot" { match if ((substring(option agent.
dhcpd Includes dhcpd Files match if ((substring(option agent.remote-id,0,9)="SPSI-AI00") and (substring(option agent.circuit-id,2,2)="\x00\xc8") and (option vendor-class-identifier = "iMG634WA")); filename "ADSL/AI00/IMG634WA"; option tftp-server-name "10.52.201.4"; option vendor-class-identifier "iMG634WA"; } class "SPSI-AI00-iMG646BDBoot" { match if ((substring(option agent.remote-id,0,9)="SPSI-AI00") and (substring(option agent.
dhcpd Files dhcpd Includes match if ((substring(option agent.remote-id,0,9)="SPSI-AI00") and (substring(option agent.circuit-id,2,2)="\x00\xc8") and (option vendor-class-identifier = "iMG726BD-ON")); filename "FIBER/AI00/IMG726BD-ON"; option tftp-server-name "10.52.201.4"; option vendor-class-identifier "iMG726BD-ON"; } class "SPSI-AI00-iMG726MODBoot" { match if ((substring(option agent.remote-id,0,9)="SPSI-AI00") and ((substring(option agent.circuit-id,2,2)="\x00\xc8") or (substring(option agent.
dhcpd Includes dhcpd Files option tftp-server-name "10.52.201.4"; option vendor-class-identifier "iMG2504"; } class "SPSI-AI00-iMG2524Boot" { match if ((substring(option agent.remote-id,0,9)="SPSI-AI00") and (substring(option agent.circuit-id,2,2)="\x00\xc8") and (option vendor-class-identifier = "iMG2524")); filename "FIBER/AI00/iMG2524"; option tftp-server-name "10.52.201.
dhcpd Files dhcpd Includes (substring (option agent.circuit-id,2,2)="\x01\x90") and (substring(option vendor-class-identifier,0,8)="iMG616W") ) or ( (substring (option agent.remote-id,0,9)="SPSI-AI00") and (substring (option agent.circuit-id,2,2)="\x01\x90") and (substring(option vendor-class-identifier,0,7)="iMG634A") ) or ( (substring (option agent.remote-id,0,9)="SPSI-AI00") and (substring (option agent.
dhcpd Includes dhcpd Files ( (substring (option agent.remote-id,0,9)="SPSI-AI00") and ((substring (option agent.circuit-id,2,2)="\x01\x90") or (substring (option agent.circuit-id,3,2)="\x01\x90")) and (substring(option vendor-class-identifier,0,9)="iMG746MOD") ) or ( (substring (option agent.remote-id,0,9)="SPSI-AI00") and (substring (option agent.circuit-id,2,2)="\x01\x90") and (substring(option vendor-class-identifier,0,8)="iBG915FX") ) or ( (substring (option agent.
dhcpd Files dhcpd Includes match if ( ( (substring(option agent.remote-id,0,9)="SPSI-AI00") and (substring(option agent.circuit-id,2,2)="\x02\x58") ) or ( (substring(option agent.remote-id,0,9)="SPSI-AI00") and (substring(option agent.circuit-id,3,2)="\x02\x58") ) ); set circuit-id = concat(option agent.circuit-id,"@",option agent.remote-id); spawn with pick(option agent.
dhcpd Includes dhcpd Files 13.2.2.2 spsi-ai00-awplus-class # # # # # spsi-ai00-awplus-class for Service Provider Solutions Interop (SPSI) lab Access Island 0, AlliedWare Plus access ports for provisioning 3play iMGs Jul-7-10 JWS: copied from spsi-ai00-class, modified for AW+ Jul-23-10 JWS: changed for aw+ dhcp snooping Apr-3-12 JWS: added img1505 ###################################################################### # AGENT REMOTE ID: # None, since not supported by AW+ 5.3.3-0.
dhcpd Files dhcpd Includes 13.2.2.3 spsi-ai00-subnet # # # # # # # # # # # # # # # # # # # spsi-ai00-subnet for Service Provider Solutions Interop (SPSI) lab Access Island 0 Jul-15-08 JWS: modified for migration of nms server ip from 10.52.110.4 to 10.52.201.4 Aug-11-08 JWS: modified for migration of dns domain from stelar.net to spsi.lab.telesyn.
dhcpd Includes dhcpd Files key rndckey; } pool { authoritative; range 10.52.111.132 10.52.111.190; # default-lease-time 86400; default-lease-time 300; # max-lease-time 86400; max-lease-time 300; option routers 10.52.111.129; option subnet-mask 255.255.255.192; option broadcast-address 10.52.111.191; option domain-name "rgvoip.spsi.lab.telesyn.corp"; option domain-name-servers 10.52.201.
dhcpd Files allow members of "SPSI-AI00-iMG746MODBoot"; allow members of "SPSI-AI00-iMG1505Boot"; allow members of "SPSI-AI00-iMG1525Boot"; allow members of "SPSI-AI00-iMG2504Boot"; allow members of "SPSI-AI00-iMG2524Boot"; allow members of "SPSI-AI00-iMG634WABoot"; allow members of "SPSI-AI00-iMG624ABoot"; allow members of "SPSI-AI00-iMG624A-R2Boot"; allow members of "SPSI-AI00-iMG634ABoot"; allow members of "SPSI-AI00-iMG634A-R2Boot"; allow members of "SPSI-AI00-RG634ABoot"; allow members of "SPSI-AI00-RG
dhcpd Includes dhcpd Files allow members of "SPSI-AI00-iMG2524Mgmt"; allow members of "SPSI-AI00-iMG624AMgmt"; allow members of "SPSI-AI00-iMG624A-R2Mgmt"; allow members of "SPSI-AI00-iMG634AMgmt"; allow members of "SPSI-AI00-iMG634A-R2Mgmt"; allow members of "SPSI-AI00-iMG634WAMgmt"; allow members of "SPSI-AI00-RG634AMgmt"; allow members of "SPSI-AI00-RG624AMgmt"; allow members of "SPSI-AI00-RG613TXMgmt"; allow members of "SPSI-AI00-ComtrendMgmt"; } } # RG/iMG Internet & PC vlan subnet subnet 10.52.110.
dhcpd Files dhcpd Includes 13.2.2.4 spsi-ai00-awplus-subnet # spsi-ai00-awplus-subnet for Service Provider Solutions Interop (SPSI) lab Access Island 0, # AlliedWare Plus access ports for provisioning 3play iMGs # Jul-7-08 JWS: copied from spsi-ai00-subnet, modified for AW+ # Apr-3-12 JWS: added img1505 ###################################################################### # AGENT REMOTE ID: # None, since not supported by AW+ 5.3.3-0.4 # AGENT CIRCUIT ID: # Vlan 201 (RGBoot) = vlan201 = 10.52.110.
dhcpd Includes dhcpd Files range 10.52.110.226 10.52.110.238; default-lease-time 86400; max-lease-time 86400; option routers 10.52.110.225; option subnet-mask 255.255.255.240; option broadcast-address 10.52.110.
dhcpd Files DNS Configuration File 13.2.3 DNS Configuration File options { allow-transfer { 10.3.0.5; }; directory "/etc/named.d/"; /* 10.3.0.5 is the redundant DNS (slave) * 10.4.0.5 is the primary DNS * 10.3.0.2 and 166.163.128.5 are two DHCP servers * If there is a firewall between you and nameservers you want * to talk to, you might need to uncomment the query-source * directive below. Previous versions of BIND always asked * questions using port 53, but BIND 8.
DNS Configuration File dhcpd Files zone "6.48.10.in-addr.arpa." { type master; allow-update { dhcp-srvr; }; file "ddns/10.48.6.ndb"; }; zone "7.48.10.in-addr.arpa." { type master; allow-update { dhcp-srvr; }; file "ddns/10.48.7.ndb"; }; /*RG FORWARD LOOKUP DDNS*/ zone "rg" { type master; allow-update { dhcp-srvr; }; file "ddns/rg.ndb"; }; /**/ /*END OF DDNS*/ /**/ /*Fixed REVERSE LOOKUP DNS files here...*/ zone "2.1.10.in-addr.arpa." { type master; file "networks/10.1.2.ndb"; }; zone "3.1.10.in-addr.
dhcpd Files 13-32 AlliedView NMS Administration Guide (Appendices) DNS Configuration File
