Alcatel-Lucent 1340 INC Network Controller WEB GUI Console Guide
Below you will find brief information for Integrated Network Controller 1340. This guide covers the web-based graphical user interface (GUI) for managing and monitoring telecommunication networks. It provides access to configuration, alarm management, and performance monitoring for various network elements from multiple vendors. The GUI offers features like circuit connection/disconnection, tracing, alarm filtering, and performance data retrieval.
Advertisement
Advertisement
1340 Integrated Network Controller
(INC)
WEB GUI Console Guide
Release 20.0
Proprietary
This document contains proprietary information of Alcatel-Lucent and Unique Computer Services,
Inc. and is not to be disclosed or used except in accordance with applicable agreements.
Copyright © 2009 Alcatel-Lucent. Unpublished and not for publication. All rights reserved.
Copyright© 1994-2009 Unique Computer Services, Inc. All Rights Reserved.
Copyright
©
2009 Alcatel-Lucent
All rights reserved.
1340 Integrated Network Controller Web GUI Console User Guide
Table of Contents
Graphical User Interface WEB (GUI) Environment
1340 Integrated Network Controller WEB GUI Server Hardware 1-5
1340 Integrated Network Controller WEB GUI Server Software 1-5
Integrated Network Controller WEB GUI PC Recommendations 1-5
Interfaces to Integrated Network Controller
Multi-Vendor Network Element Support
List of Supported Network Elements
April, 2009 i
1340 Integrated Network Controller Web GUI Console User Guide
Table of Contents
Customize Table/CSV/Print Report
ii April, 2009
3-1
1340 Integrated Network Controller Web GUI Console User Guide
Table of Contents
“Default User” Card Management
April, 2009 iii
1340 Integrated Network Controller Web GUI Console User Guide
Table of Contents
iv April, 2009
1340 Integrated Network Controller Web GUI Console User Guide
Table of Contents
Backup Gateway vs Mutli Gateway
NE Management - NE Specific Features
NE Management on the ALU 1850 TSS-5
NE Management of the ALU 5620 SAM and ALU Ethernet Devices
NE Management of the ALU 1830 PSS 5-82
NE Management of the ALU 9500 MPR 5-83
Eastern Research DNX, Premisys IMACS, Generic SNMP Devices 5-87
Performing DNO from the NE Management Form
Performing the DNO Command via INC Cut Thru
NE Specific Information- Tellabs 5500
April, 2009 v
1340 Integrated Network Controller Web GUI Console User Guide
Table of Contents
vi April, 2009
1340 Integrated Network Controller Web GUI Console User Guide
Table of Contents
April, 2009 vii
1340 Integrated Network Controller Web GUI Console User Guide
Table of Contents
viii April, 2009
1340 Integrated Network Controller Web GUI Console User Guide
List of Figures
Function Tab after Tab Selection (Title Bar)
Service View Wizard tree - CNM mode using a logical service type
Service View Wizard tree - CNM mode - physical only
Service View Wizard tree - EMS mode
Customize Table/CSV/Print Report Icons
April, 2009 ix
1340 Integrated Network Controller Web GUI Console User Guide
List of Figures
New Window icon (“search in current window” mode)
New Window icon (“search in new window” mode)
The Cycle window available from the Admin menu.
3-5 Cycle windows are automatically raised as the top window on your desktop every n seconds. 3-8
NE Cut Thru Command/Response Form
NE Cut Thru - Change NE - Command History request
NE Cut Thru - Send to Multi NE
NE Cut Thru - Batch processing message
x April, 2009
1340 Integrated Network Controller Web GUI Console User Guide
List of Figures
Historical Alarms - Filter Chart
Alarm Notification Profile Creation
Alarm Notification - Adding a Profile
Alarm Notification - Users Tab
April, 2009 xi
1340 Integrated Network Controller Web GUI Console User Guide
List of Figures
Populate - post-NE selection and refresh
NE Management - Communication Tab
NE Management - Facilities Tab
Enable MAIN - Communication Tab
NE Management form Communications tab for ES64C login provi-
5-36 INC Network map with 5620 SAM Interface, two 7750s managed via
SAM, with a manually created “generic link” between them, and SAM Cut Thru. 5-79
5-37 NE Management of the 5620 SAM Interface.
xii April, 2009
1340 Integrated Network Controller Web GUI Console User Guide
List of Figures
7 Alarm List of alarms discovered from an Alcatel-Lucent 1830 PSS.
Network Map representation of the 9500 MPR, available cut through 8 to WebEML 5-84
Alcatel-Lucent 9500 MPR Radio Equipment View.
Alcatel-Lucent 9500 MPR Circuit Trace,
Filter by Tree - Selected group
Topological Refresh - Auto checkbox
April, 2009 xiii
1340 Integrated Network Controller Web GUI Console User Guide
List of Figures
Multi Level Maps - First Level
Multi Level Maps - Second Level
Multi Level Maps - Third Level
Multi Level Maps - NE Group Information
Multi Level Maps - Subnetwork Information
Multi Level Maps - NE Management Form
xiv April, 2009
1340 Integrated Network Controller Web GUI Console User Guide
List of Figures
April, 2009 xv
1340 Integrated Network Controller Web GUI Console User Guide
List of Figures
xvi April, 2009
Preface
Purpose
This manual describes the features of the 1340 Integrated Network Controller WEB Graphical User Interface (GUI) as they appear to a “console” level user of a 1340 Integrated Network Controller system.
Audience
This document is intended for network planners, administrators, maintenance engineers, and craft personnel who require an in-depth knowledge of the Integrated Network Controller WEB GUI.
Related Documents
The following documents provide additional information about the Integrated Network Controller system:
— 1340 Integrated Network Controller Application Installation Guide.
April, 2009 i
Electronic Documentation
Customer documentation is available on the Internet at “www.unique-inc.com” or on CD-ROM. Consult your account executive for details.
Ordering Documents
To order copies of documents, consult your account executive.
Copyrights
Copyright© 1994-2009 Alcatel-Lucent All Rights Reserved.
Copyright© 1994-2009 Unique Computer Services, Inc. All Rights Reserved.
Portions include software under the following terms:
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the
License.
Copyright © 1992-2009 FairCom Corporation. “FairCom” and “c-tree Plus” are trademarks of FairCom
Corporation and are registered in the United States and other countries. All Rights Reserved.
Copyright© 1993, 1994 mpack and munpack by Carnegie Mellon University All Rights Reserve
Permission to use, copy, modify, distribute, and sell this software and its documentation for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Carnegie Mellon University not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. Carnegie Mellon University makes no representations about the suitability of this software for any purpose. It is provided "as is" without express or implied warranty.
CARNEGIE MELLON UNIVERSITY DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS
SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS,
IN NO EVENT SHALL CARNEGIE MELLON UNIVERSITY BE LIABLE FOR ANY SPECIAL, INDI-
ii April, 2009
RECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
LOSS OF USE, DATA OR PROFITS, WHETHER IN OUT OF OR IN CONNECTION WITH THE USE
OR PERFORMANCE OF THIS SOFTWARE.
Portions of this software are derived from code written by Bell Communications Research,
Inc. (Bellcore) and by RSA Data Security, Inc. and bear similar copyrights and disclaimers of warranty.
Copyright© 1999 Open JMS by Exoffice Technologies Inc. All Rights Reserved
The following copyright notice pertains only to the graphical element libraries used in this product.
“Portions copyright ©1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001 by Cold Spring Harbor Laboratory.
Funded under Grant P41-RR02188 by the National Institutes of Health. Portions copyright 1996, 1997,
1998, 1999, 2000, 2001 by Boutell.Com, Inc. Portions relating to GD2 format copyright 1999, 2000 Philip
Warner. Portions relating to PNG copyright 1999, 2000 Greg Roelofs. Portions relating to libttf copyright©
1999, 2000 John Ellson ([email protected]). Portions relating to JPEG and to color quantization copyright
2000, Doug Becker and copyright © 1994-1998,Thomas G. Lane. This software is based in part on the work of the Independent JPEG Group. See the file README-JPEG.TXT for more information. Portions relating to WBMP copyright© 2000 Maurice Szmurlo and Johan Van den Brande. Permission has been granted to copy, distribute and modify gd in any context without fee, including a commercial application, provided that this notice is present in user-accessible supporting documentation. This does not affect your ownership of the derived work itself, and the intent is to assure proper credit for the authors of gd, not to interfere with your productive use of gd. If you have questions, ask. "Derived works" includes all programs that utilize the library. Credit must be given in user-accessible documentation. This software is provided "AS IS." The copyright holders disclaim all warranties, either express or implied, including but not limited to implied warranties of merchantability and fitness for a particular purpose, with respect to this code and accompanying documentation. Although their code does not appear in gd 2.0.1, the authors wish to thank David Koblas,
David Rowley, and Hutchison Avenue Software Corporation for their prior contributions.”
All logos are the property of their respective owners.
April, 2009 iii
iv April, 2009
Introduction
Chapter Contents
•
•
Graphical User Interface WEB (GUI) Environment on page 1-3
•
Other System Features on page 1-4
•
•
Network Element Types on page 1-12
•
Multi-Vendor Network Element Support on page 1-15
•
System Interfaces on page 1-25
•
System Interfaces on page 1-25
•
April, 2009 1-1
Introduction
Description
The Integrated Network Controller Web GUI is a software application designed to provide a graphical, point and click, interface to the 1340 INC Host. Together, the Integrated Network Controller Host (Core) and the
Integrated Network Controller Web GUI provide a user friendly environment through which telecommunication service providers and customers of those service providers can manage and monitor their communications networks. The Integrated Network Controller system provides network management capabilities including configuration management, alarm surveillance, and performance monitoring for various types of
Network Elements manufactured by various vendors.
1-2 April, 2009
Introduction
Graphical User Interface WEB (GUI) Environment
The Integrated Network Controller Graphical User Interface (GUI) is a web based interface to the Integrated
Network Controller Host. It provides point-and-click and Smart-Form access to the various capabilities of the Integrated Network Controller System. Network Management Capabilities
Alarm Management
Alarm management for the various network elements and facilities provisioned in the Integrated Network
Controller is accomplished by real-time monitoring and detection of the autonomous messages output by network elements connected to the 1340 Integrated Network Controller. The following are some of the alarm management functions available:
• Alarm Receipt, Display and Storage (including an Active Alarm Display)
• Alarm Filtering
• Alarm Sorting
• Alarm Acknowledgement and Comment
• Clearing Alarms
• Alarm Reports and Alarm History Reports
Configuration Management
The 1340 Integrated Network Controller GUI supports the ability to connect and disconnect facilities on network element types supported by 1340 Integrated Network Controller. The 1340 Integrated Network Controller GUI graphically displays the assigned facilities as well as the bandwidth of those facilities. It also provides graphical tracing of circuits traversing multiple network elements of various types. The following are some of the configuration management functions available:
• Circuit Connect/Disconnect
• Circuit Tracing
• Circuit ID and Comment Information
• Automatic Path Selection
• Connect Override and Continuation
Performance Management
Performance monitoring data can be retrieved from SONET network elements in real-time or can be scheduled for daily retrieval. 1340 Integrated Network Controller also logs all autonomous performance monitoring threshold crossings reported by network elements. The following are some of the performance management functions available:
• PM Retrieval
• Scheduled PM Retrieval and Data Storage
• PM Data Reports and Graphs
April, 2009 1-3
Introduction
Other System Features
Secure Customer Database - 1340 Integrated Network Controller provides secure customer database separation allowing customers of telecommunication providers to access, monitor, and configure their communication networks.
Graphical Equipment Views - The GUI provides detailed graphical representations of most supported network element types.
Cut-Thru to INC - the GUI provides a cut-thru window to the command line interface of 1340 Integrated
Network Controller. All non-interactive commands may be issued to Integrated Network Controller from the cut-thru window.
Cut-Thru to Network Elements - The NE Cut Thru feature provides Console GUI users with cut-thru
(pass-thru) access to any network element for command I/O in the native language of the selected network element. This feature is only available from a GUI connected to Integrated Network Controller via a LAN interface.
Generic TL1 Interface - The GUI has a generic TL1 interface to allow immediate communication with not yet supported network element types.
Graphs - The GUI has the functionality for creating various graphs of collected alarm and PM data.
On-line Help - On-Line Help is available in the GUI to provide users with quick access to helpful information on using the various functions and features.
Printing - GUI users can set up a printer to print reports and screen captures from the GUI.
NMS Functionality - 1340 Integrated Network Controller can be utilized as a Network Management System. This means that database facilities can be associated with a network element without the use of the customer partitioning and service view name features of 1340 Integrated Network Controller. These assignments are managed by using their physical representations.
EMS Functionality - 1340 Integrated Network Controller has optional software features that allow it to be utilized as an Element Management System for some network element types. See the Integrated Network
Controller EMS Supplement for detailed information.
ATM/FR Functionality - 1340 Integrated Network Controller has optional software features that allow for the management of ATM and Frame Relay networks. See the Integrated Network Controller ATM/FR Supplement for detailed information.
1-4 April, 2009
Introduction
Architecture
1340 Integrated Network Controller WEB GUI Server Hardware
The Integrated Network Controller GUI is a UNIX based software application and is supported on the following hardware platforms:
• SUN UltraSPARC based Servers
• HP PA-RISC based server
• HP IA based server
The minimum workstation requirements are as follows:
• Approximately 1024 Mb of RAM per 10 concurrent users
• 18 Gb Hard Disk
• CD/DVD-ROM Drive
1340 Integrated Network Controller WEB GUI Server Software
WebServer Software
• Apache 1.3 or Apache 2.0
• Sun iPlanet r4.1 or r6.0sp5
SUN Environment
The supported SUN environment for the Integrated Network Controller GUI is the Solaris 8 and 9 Operating
Systems.
Hewlett Packard Environment
The supported HP environment for the Integrated Network Controller GUI is the HP-UX 11i Operating System (including v1 11.11 and v2 11.23 (PA and IA))
NOTE:
The Common Desktop Environment (CDE) is required IF the Web GUI is launched from a server graphical console. Graphical consoles are often optional hardware components, ex., video card, color monitor, keyboard and mouse.
Integrated Network Controller WEB GUI PC Recommendations
For optimal performance, it is recommended that the Integrated Network Controller GUI be run in the following environment:
April, 2009 1-5
Introduction
• Intel Pentium® 4, AMD Athlon CPU @ 2.0 GHz or above
• 1 Gb of RAM
• 1280 X 1024 screen resolution
• Microsoft Windows XP Service Pack 2
• Microsoft Windows VISTA
• Microsoft Internet Explorer 6.0 or higher browser
Browser Settings
The following section describes some common preferences for browser settings:
Remove URL text from Window Pane
In some cases, use of Microsoft IE 6 or IE 7 will result in the display of a URL in the top of the Window pane. This behavior can be disabled by adding the 1340 INC URL to the Trusted Sites list.
— From the browsers menu, select Tools, Internet Options, Security, Trusted Sites, Sites navigation
— Enter the URL of the 1340 INC Web GUI and add it to the list.
Entry of the URL in the Sites list will eliminate it’s display when running the Integrated Network Controller
WEB GUI.
Character set encoding
Auto-selecting Character set encoding enabled may cause problems with webpages being displayed properly. If a webpage is not displayed properly try disabling the auto-select feature
View -> Encoding -> Uncheck Auto-select
Pop-up blockers
Most browsers come equipped with a Pop-up Manager. This manager can be used to allow or disallow pop-ups from specific URLs. The Pop-up Manager can also be completely disabled allowing all sites the ability to launch browser windows. It is recommended to enable the Pop-up blocker and identify specific
URLs.Whichever format is entered into the Allowed Sites, must be the URL entered in the browser’s
Address field.
NOTE:
Fully-qualified hostnames or IP addresses can be added to the “Allowed Sites” list.
Whichever format is entered into the Allowed Sites, must be the URL entered in the browser’s Address field.
Tools -> Pop-up Blocker -> Turn On Pop-up Blocker
1-6 April, 2009
Introduction
Tools -> Pop-up Blocker -> Pop-up Blocker Settings
Add the fully qualified hostname or IP address of the 1340 INC Web GUI server.
Select Add
Printing
Set the “Print background colors and images” for proper printing.
Tools -> Internet Options -> Advanced Tab -> Scroll to “Print” section.
Alarm Central Redraw
The Alarm Central frame will update (redraw) during the normal operations. To eliminate the momentary
“white” flash, set the “Check for newer versions of stored pages” to “Automatic”.
Tools -> Internet Options -> General Tab -> Temporary Internet Files -> Settings... ->
“Check for newer versions of stored pages:” select “Automatically
Cut and Paste to Clipboard
An enhancement has been added to the Web GUI which utilizes the clipbpoard for adding data to or taking data from various 1340 INC forms. Below are steps to modify the web browser to take advantage of this function.
If you’re using Internet Explorer 7, there are several enhanced and tighten security features that have been incorporated into IE7. One of them has been to restrict Clipboard data access by websites and web pages. In
Internet Explorer 7, installed on Windows XP or Windows Vista, the behaviour occurs when you visit a website or webpage that tries to access the information stored in Clipboard’s memory, as Clipboard’s memory stored data can be sensitive and private. For security purpose, IE7 will pop-up a warning alert message as below:
“Do you want to allow this webpage to access your Clipboard?”
If you allow this, the webpage can access the Clipboard and read information that you’ve cut or copied recently. Press or click “Don’t Allow” or “Allow” button to get pass the popup message.
This security feature can be disabled. To disable the pop up warning message about possible harmful or unauthorized Clipboard access, follow the steps below:
— Select Tools -> Internet Options.
— Select Security tab.
— Select “Internet” zone, then select “Custom level…” button.
— Scroll down to “Scripting” section (at the bottom few).
— Under “Allow Programmatic clipboard access” option, check or select (tick) Enable.
Default action for this option is Prompt, which causes the pop-up message whenever there is any attempt to access the Clipboard.
April, 2009 1-7
Introduction
— Click Ok twice to exit from Internet Options.
Changing the preference to Enable for “Allow Programmatic clipboard access” option can increase the security risk. It can be set to Disable to disallow access to Clipboard resident data. However, the better and more secure alternative is to edit the “Allow Programmatic clipboard access” setting for “Trusted sites” zone
(steps same as above, only select “Trusted sites” in step 3 instead of “Internet”), and add the websites that you trusted and selected into Trusted sites zone.
Disable Browser Click
By default the browser will sound a click what various GUI elements are selected or if a window refreshes.
— Open Control Panel.
— Select Sounds and Audio Devices.
— Select Sounds Tab.
— In “Program events:” list, scroll down to heading “Windows Explorer” and select “Start
Navigation” (it should be highlighted
— Select the “Sounds” pull-down menu, scroll until [None] is visible and select it.
— If for some reason a different sound is desired, either select one from the list or provide a path to custom sound file.
— Select the OK button.
— Close all appropriate windows.
Disable Security Report
There are times when accessing the 1340 INC Web GUI that a “Security Report” is displayed ( address field turns “redish-pink”), such as an unsigned certificate or a non-Trusted CA certificate. The following step will disable the error message from being displayed.
— Start the IE6 or IE7 browser.
— Select menu item “Tools”, select “Internet Option” (the Internet Options window will appear).
— Select the “Security” tab, select “Local Intranet”.
NOTE:
In most cases the 1340 INC Web GUI will be accessed by clients on the same network. If this is not the case select “Trusted Systems” instead of “Local Intranet”.
— On the “Local Intranet” window, select the “Sites” button (a Local Intranet window will appear).
— On the “Local Intranet” sub-window, select the “Advanced” button (a new Local Intranet window will appear).
1-8 April, 2009
Introduction
— Enter the URL of the 1340 INC Web GUI server in the “Add this Web site to the zone” field, select the “Add” button.
— The Web site will appear in the “Web sites” list.
NOTE:
If the “Require server verification (https:) for all sites in this zone” checkbox is enabled
(checked), everytime the site is visited a permission pop-up will appear. By default the check box is NOT checked because it is assumed that everything in the Intranet zone is trusted. On the other hand, if a server was has been added to the “Trusted Systems” zone, the value would be checked since the assumption is that the server is outside the intranet, i.e., part of the internet.
— Select “Close” on the Local Intranet sub-window.
— Select the “OK” button on the Local Intranet window
— Select the “OK” button on the “Internet Options” window
— Restart the browser and point it to the 1340 INC Web GUI address.
Disable Status Bar
The prerequisite for disabling the IE6 or IE7 Status bar is defining the URL as a trusted system either in
Local Intranet or Trusted Systems zone.
— Start the IE6 or IE7 browser.
— Select menu item “View”, remove the check mark next to “Status Bar” by selecting it.
— Restart the browser.
Remove Miscellaneous Window Pane Text
If by chance there is unwanted text in the Vista supplied version of IE7 window pane, ex., "Internet Explorer provided by ..." it can be removed.
— From the “Start” button, select “All Programs”
— Select “Accessories”
— Select “Run” and enter the following command followed by the “OK” button.
rundll32 iedkcs32.dll,Clear
Using a CLI Interface
1340 INC may be configured to communicate via a CLI (Command Line Interface) in the case of the specific Network Elements (See Chapter 5 - Configure - NE Management). In order for this communication to take place:
— Tools -> Internet Options (Security Tab)
— Select a Zone (1340 INC should be in the Trusted Sites zone)
April, 2009 1-9
Introduction
— Select the Custom Level button (the Security Settings - Zone window will be displayed)
— Scroll down to the Active X Controls and Plugins - Set “Initialize and Script Active X controls not marked as safe for scripting” to Enable
Photonic Manager (PhM) EMS Cutthrough
Access to the Photonic Manager on the PC is gained via the Network Map 1830 icon menu choice. In order to allow this access, the following steps must be followed:
— Tools -> Internet Options (Security Tab)
— Select a Zone (1340 INC should be in the Trusted Sites zone)
— Select the Custom Level button (the Security Settings - Zone window will be displayed)
— Scroll down to the Active X Controls and Plugins - Set “Initialize and Script Active X controls not marked as safe for scripting” to Enable
1-10 April, 2009
Introduction
Interfaces to Integrated Network Controller
Connectivity between the Integrated Network Controller Host and the 1340 Integrated Network Controller
GUI is accomplished via one of the following methods:
• serial (serial port)
• telnet (ethernet port)
• rlogin (ethernet port)
• modem (serial port)
serial
The serial interface is used to communicate via the serial port on the SUN/HP workstation. The serial interface is typically used for private line or direct asynchronous circuit connections.
rlogin
The rlogin interface is used to communicate via the ethernet port on the SUN/HP workstation. The rlogin interface is used for Local Area Network (LAN) connections to the 1340 INC host and uses the UNIX rlogin command.
telnet
The telnet interface is used to communicate via the ethernet port on the SUN/HP workstation. The telnet interface is used for Local Area Network (LAN) connections to the 1340 INC host and uses the UNIX telnet command.
modem
The modem interface is used to communicate via the serial port on the SUN/HP workstation. The modem interface is typically used when dialing with a modem to connect to the Integrated Network Controller host.
April, 2009 1-11
Introduction
Network Element Types
1340 Integrated Network Controller can monitor and manage Digital Cross-Connect Systems (DCS),
Add-Drop Multiplexers (ADMs), Dense Wavelength Division Multiplexers (DWDM), and Echo Cancellers
(EC) by way of the Integrated Network Controller Graphical User Interface (GUI). Shown below are the graphical icons which represent these network elements.
The following icons represent all supported vendors which manufacture Digital Cross-Connect Systems:
1/0 DCS
The 1/0 DCS terminates DS1 facilities but cross-connects these facilities at the DS0 level. Each
DS1 has 24 DS0 channels, which is equivalent to 64kb of bandwidth each.
3/1 DCS
The 3/1 DCS terminates DS3 facilities but cross-connects these facilities at the DS1 level. Each
DS3 has 28 DS1 channels, which is equivalent to 1.544mb of bandwidth each.
3/3 DCS
The 3/3 DCS terminates DS3 facilities and cross-connects these facilities at the DS3 level. Each
DS3 is equivalent to 45mb of bandwidth.
Broadband DCS
The Broadband DCS terminates SONET facilities and cross-connects them at the STS1, STS3C,
STS12C, and STS48C levels.
1340 Integrated Network Controller provides support for SONET ADMs in linear or ring topology. The following icons represent all supported vendors which manufacture Add-Drop Multiplexers. On the Integrated
Network Controller GUI, an indication may also be given as part of the icon to identify the node as part of a
UPSR (U), BLSR (B), or Linear (L) configuration.
OC-3 ADM
The OC-3 multiplexer can carry the equivalent of 3 DS3 facilities on a fiber optic transport backbone. Signals are cross-connected at the VT-1 and STS1 levels.
OC-3+ ADM
The OC-3+ multiplexer is a cross between an OC3 and an OC12. It can carry the equivalent of 12 high speed DS3s, but can only drop the equivalent of 3 DS3 facilities on the low speed side.
Cross-connects are performed at the VT-1 and STS1 levels.
1-12 April, 2009
Introduction
OC-12 ADM
The OC-12 multiplexer can carry the equivalent of 12 DS3 facilities on a fiber optic transport backbone. Signals are cross-connected at the STS1 and OC-3 levels.
OC-48 ADM
The OC-48 multiplexer can carry the equivalent of 48 DS3 facilities on a fiber optic transport backbone. Signals are cross-connected at the STS1, OC-3, and OC-12 levels.
OC-192 ADM
The OC-192 multiplexer can carry the equivalent of 192 DS3 facilities on a fiber optic transport backbone. Signals are cross-connected at the concatenated OC-3, OC-12, and OC-48 levels.
The following icon represents all supported vendors which manufacture DWDM devices:
DWDM
DWDM (Dense Wavelength Division Multiplexing) is a transport technique that employs light wavelengths to transmit data, for example, SONET OC-3, OC-12, or OC-48, ATM, etc.
The following icon represents Echo Canceller devices:
Echo Canceller
An echo canceller is a network device that enhances the voice quality of networks. A broadband echo canceller is a device that combines this function with SONET multiplexing capability.
The following icon is used to represent the Generic TL1 Interface.
Generic TL1 Interface Icon
The generic TL1 feature provides ‘generic’ interface support for network element access. This feature provides the user with options for quick access to new NE types prior to the release of the final ‘standard’ NE support. Under the generic TL1 node interface, all alarms received from the NE are mapped to Integrated Network Controller as Miscellaneous Alarms. The user may also use the ‘Cut-Thru’ option to establish native mode command sessions for circuit connect/ disconnect, card provisioning etc.
The following icon is used to represent the Generic TL1 Interface.
April, 2009 1-13
Introduction
Microwave Digital Radio
1340 INC manages the Alcatel-Lucent Microwave Digital Radio MDR-8000 (MDR-8000) and the Alcatel-Lucent Microwave Cross Connect 9500 (9500 MXC) devices for PM collection and alarm monitoring.
1-14 April, 2009
Introduction
Multi-Vendor Network Element Support
1340 Integrated Network Controller provides network management capabilities for a wide variety of vendors and types of network elements. 1340 Integrated Network Controller allows service providers and their customers to manage and monitor telecommunications networks comprised of the following Network Elements.
April, 2009 1-15
Introduction
List of Supported Network Elements
Acterna
Model Type
T3AS* Test Head
Adtran
* For PM collection/monitoring only
Release
Model Type Release
Anritsu
Opti 6100
1
ADM R5.2
1.
TDM/Optical support (no ethernet at this time)
Model Type
9620* Test Head
9622* Test Head
* For PM collection/monitoring only
Aethera (Positron)
Release
Model Type
OSR OC3 XTD OC3 ADM
OSR OC12 XTD OC12 ADM
Release
Cust mode
X
NMS mode
EMS mode
Cust mode
NMS mode
X
EMS mode
Cust mode
X
X
NMS mode
EMS mode
Cust mode
X
X
NMS mode
EMS mode
1-16 April, 2009
Introduction
Alcatel Lucent
Model
1631 LMC
1665
DMXplore
1671 SC
4
3/1 DCS 7.2.1
1665 DMX SONET ADM 5.0, 5.1.x, 6.0,
6.0.1, 6.0.2,7.0,
7.0.1, 7.1.x, R8.0
1665 DMXtend SONET ADM 2.0,3.0, 3.1.x, 4.0,
4.0.1,
4.0.2,5.0,5.0.1,
5.1.0,5.1.x, R8.0
SONET ADM 1.0.1, 2.0, 2.1.x
3.0.x, 4.0.x, 5.0.x
X
X
X
1675
LambdaUnite
1677
2
1678 MCC
1692 MSE
1695 WSM
1696 MS
1830
PSS-32,PSS-1
9
1850 TSS-5
1850 TSS-60
1850 TSS-100
1850 TSS-320
5620 SAM
5
®
6850, 7250,
7450, 7705,
7710, 7750 SR
6
9500 MPR
BSTDX8000
1
Type
BDCS
BDCS
OC192 ADM
BDCS
DWDM
DWDM
DWDM
DWDM
Ethernet Sw/
ADM
ADM
ADM
ADM
INTFC
ETHERNET
RADIO
ATM/FR
Release
6.01.01, 7.00.01,
7.00.02, 8.00.00,
8.00.01,8.00.20,
9.00.00, 9.01.00,
10.00.00,
10.05.00,10.05.03
11.01.00
X x.xx
X
5.2, 5.3, 5.4
3.2B
1.1, 3.0, 4.0, 4.5,
6.0
3.01
R1, R1.1
3.0.0, 4.0.0, 4.1.x,
5.0.x, 5.1
1.0, 2.0
1.1.x, 2.0.x, 2.1.x
2.0.0, R2.0.4
6.0
any
R1
7.0.x, 7.3.x
Cust mode
X
X
X
X
X
X
NMS mode
EMS mode
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
April, 2009 1-17
Introduction
Alcatel Lucent
Model
BSTDX9000
1
CBX500
1
DACS II
DACS II-ISX
DACS II CEF
DACS III
DACS IV
DDM-2000
OC1
DDM-2000
OC3 Linear
DDM-2000
OC3 Ring
OC3 ADM
DDM-2000
OC3+
DDM-2000
OC12 Linear
DDM-2000
OC12 Ring
DMXpress
UPSR
OC48 ADM
OC12 ADM
FT-2000 BLSR OC48 ADM
FiberReach
FiberReach
OC3
OC1 ADM
OC3 ADM
FiberReach
OC12
GX250
1
GX550
1
LiteSpan 2000/
2012
2
MDR-8000
3
9500 MXC
3
OC12 ADM
OC12 ADM
OC12 ADM
OC12 ADM
ATM
ATM
DLC
Microwave
Microwave
Type
ATM/FR
ATM/FR
1/0 DCS
1/0 DCS
1/0 DCS
3/1 DCS
3/1 DCS
OC1 ADM
OC3 ADM
Release
7.0.x, 7.3.x
8.0.3.x
7.0
7.0
5.5
15.0
8.0.2, 8.1.2
9.0.6, 11.0.4,
11.1.2,
15.0.2, 15.0.3
11.0.4rtr
5.1.2, 7.0.3
2.0.1
7.2.7, 9.1.0
2.1.2, 2.2.1
2.1.2, 2.2.1
2.1.2, 2.2.1
8.0.3.x
8.0.3.x
12
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
Cust mode
X
X
X
NMS mode
X
X
X
X
X
X
X
EMS mode
X
X
X
1-18 April, 2009
Introduction
Alcatel Lucent
Model Type Release
7.1.5
SONET 15.x
4.1.1
Cust mode
X
NMS mode
EMS mode
PSAX 1250
SLC-2000
8
WaveStar 2.5G
BLSR
WaveStar 10G
BLSR
WaveStar 400/
800G
7
ATM Edge
DLC
OC48 ADM
OC192 ADM
DWDM
4.1.2
X
X
X
X
X
2.0.3, 3.0.1,
3.0.2, 5.0, 7.1,
10.0
3.1.2
X X X
WaveStar
BWM
DCS X X
1.
Requires Navis
®
Stat, Fault, Core, DB servers with Release 8.0.3.x
2.
For EPM functions only
3.
Alarm monitoring/PM collection only, requires Alcatel-Lucent TSM-8000 fault server
4.
EMS supported beginning R4.
5.
SAM 5620 required for 6850, 7705, 7710, 7250, 7450, 7750 alarm management
6.
For all these devices requires SAM 5620 Interface, alarm management only.
7.
C-band frequencies only
8.
Partial support- SONET subsystem only
9.
INC Alarm management only. Support of PSS-32 or PSS-1 requires RM-Photonic Mgr. or use of alternate INC Cut Thru features for other management features.
April, 2009 1-19
Introduction
Ciena
Model
Multiwave Metro
Type
DWDM
Release
2.1
Cust mode
X
NMS mode
EMS mode
Cisco
Model
ONS 15454
ONS 15454
1
ONS 15310-MA
ONS 15310-CL
ONS 15327
ONS 15600
ONS 15800
Cisco 2811
2
Cisco 7609
Cisco 3750
Cisco 2650XM/2811
2
Cisco MGX1
3
Cisco MGX45
3
Type
SONET MSPP
DWDM MSTP
SONET ADM
SONET ADM
SONET ADM
BDCS
DWDM
Ethernet Switch
Ethernet Switch
Ethernet Switch
Shadow Router
ATM Switch
ATM Switch
Release
12.4.5B
12.2
12.2
12.2
any any
3.0, 3.2, 3.3, 3.4, 4.1, 4.6,
5.0, 6.x, 7.0, 8.x
8.x
7.0, 7.2, 8.x
7.0, 7.2
3.3, 3.4, 4.1, 7.x
R7.2, R8.0
1.1.2
X
X
X
X
X
X
X
X
X
X
X
Cust
Mode
X
NMS
Mode
X
EMS
Mode
1
Single and multi-shelf, contact customer representative for supported configurations.
2
When optionally used with the Cisco 7609
3
PM collection only, for CNMS
X
X
X
X
1-20 April, 2009
Introduction
Fujitsu
Model
FACTR OC3 UPSR
FACTR OC12 UPSR
FLM -6
FLM-150
FLM-150+
FLM-600
FLM-2400 UPSR
FLM-2400 BLSR
Flash 192 UPSR
Flash 192 BLSR
FLASHWAVE 4100 UPSR
FLASHWAVE 4300 UPSR
FLASHWAVE 4500 BLSR
FLASHWAVE 7120
Type Release Cust mode
OC3 ADM
OC12 ADM
OC1 ADM
OC3 ADM
OC12 ADM
OC12 ADM
OC48 ADM
7.x
7.x
4.x
10.01.5, 11.03.5,
12.02.6, 15.2S
12.02.6, 15.2S
12.02.5, 12.02.6,
15.2S
10.B1.7, 10.B2.5,
10.02.5, 10.03.6,
15.B2.6
OC48 ADM 10.B1.7, 10.B2.5,
10.02.5, 10.03.6,
15.B2.6
5.01, 5.2
OC192 ADM
OC192 ADM 3.2, 5.2
SONET ADM 3.x, 5.3, 6.1
SONET ADM 3.x
SONET ADM 3.1, 6.1, 7.1, 8.1,
9.1
DWDM/
CWDM
7.1.x
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
NMS mode
X
EMS mode
Generic
Model Type Release Cust mode
NMS mode
Generic TL1
1
Any Any
Any SNMP
2
Any Any X X
1.
Alarm Management features, Cut-thru
2.
Alarm Management features: snmp traps, uses standard ifOperStatus, ifAdminStatus tables
EMS mode
April, 2009 1-21
Introduction
NMS
Model
Mercury Echo Canceller
Type Release
Echo Canceller 1.1, 1.2, 5.3.7
Cust mode
X
NMS mode
X
EMS mode
Nortel
Model Type Release
OC3 Express
Optera 3300/3400
Optera 3300/3400
OC3/OC12 TBM
S/DMS TransportNode OC48
S/DMS TransportNode OC192
Optera 5200
Optical Metro 3500 OC12 UPSR
OC3 ADM
OC3 ADM
OC12 ADM
OC12 ADM
OC48 ADM
OC192 ADM
DWDM
OC12 ADM
Optical Metro 3500 OC48 UPSR
Optical Metro 3500 OC48 BLSR
OC48 ADM
OC48 ADM
Optical Metro 3500 OC192 BLSR OC192 ADM
Optical Multiservice Edge 6500 OC3,
OC12, OC48,
OC192 ADM
5.0
9, 10, 11.1
9, 10, 11.1
14.01, 14
15.01
7.2
3.1
R12.1, R14.0
R12.1, R14.0
R12.1, R14.0
R12.1, R14.0
R4.0
X
X
X
X
Cust mode
X
X
X
X
X
X
X
NMS mode
X
X
X
X
X
X
X
X
X
X
EMS mode
Sycamore (Eastern Research)
Model Type Release Cust mode
NMS mode
DNX * 1/0 DCS 8, 9, 10, 12, 14,
16.x, 16.2.1
X X
* Alarm Management features: SNMP traps and Proprietary MIB alarm tables
EMS mode
Telco
Model
EdgeLink 100*
Type
1/3 MUX
Release
2.5
Cust mode
X
NMS mode
EMS mode
1-22 April, 2009
Introduction
Tellabs
* EPM functions only
Model
530
3
532
3
5320L
1
5500
5500 NGX
4
7100
Type
1/0 DCS
1/0 DCS
1/0 DCS
3/1 DCS
DCS/ADM
DWDM
Release
2.6
6.3, 6.4
4.1, 6.1
7.0, 9.1, 10.0
2
,
11.0
2
R3.2
R3.0
X
X
X
Cust mode
X
X
1
Formerly the 532L (1340 INC manages LD100, HD100, HS100 equipment)
2
9.1 features supported in 10.0, 11.0 no break
3
Facility Discovery only, no equipment views
4
TDM/Optical Support (no ethernet at this time)
X
X
X
NMS mode
X
EMS mode
Telmar
Model Type Release
1603 SMX
1630 GSX
1
1631 SMC
1633
1648 PS
OC3 ADM
OC12 ADM
OC48 ADM
1/0 DCS
3/1 DCS
3/3 DCS
OC48 ADM
R3.01
R10.x
6.4
R3.2
1648 LS
CS1
2
OC48 ADM
1/0 DCS 9.1.3
CS1L
2
1/0 DCS
1.
EPM functions only
2.
Formerly the DSC CS1 and DSC CS1L
9.2.2
Cust mode
X
NMS mode
X
EMS mode
X
X
X
X
X
X*
X
X
April, 2009 1-23
Introduction
Verso
Model iMARC 912x iMARC 962x iMARC 9520
Type
CSU/DSU(T1)
CSU/DSU(DDS)
CSU/DSU(T3)
Release
2.0
2.0
1.3
Wiltron
Model Type
9967 * Test Head
* PM Collection/Monitoring only
Release
Zhone
X
X
Cust mode
X
Cust mode
X
NMS mode
EMS mode
NMS mode
EMS mode
Model Type Release Cust mode
NMS mode
EMS mode
Zhone IMACS * Channel Bank 3.6.1, 4.x, 5.3.7
X X
* Alarm Management features: traps, uses standard ifOperStatus, ifAdminStatus tables
1-24 April, 2009
Introduction
System Interfaces
Southbound Interfaces
1340 Integrated Network Controller supports a number of southbound application-application interface options which may be used to integrate end user management functionality between telecommunications providers, as well as customer-to-customer and customer-to-telecom provider. These options currently include; NMS-to-NMS (i.e. 1340 INC to 1340 INC), NMS-to-GNE (i.e, 1340 INC to SNC, 1340 INC to
SNMS, 1340 INC to Fujitsu NETSMART®), and NMS-to-NMA.
For example, if Telephone Company “A” owns and operates a Integrated Network Controller system and would like to monitor/control a ring(s) in Telephone Company “B”s territory, who also operates their own
Integrated Network Controller system, using the NMS-NMS interface would apply for this situation.
The NMS-NMS interface, or any of the above mentioned interfaces, would be represented on the GUI map display with an Interface Icon. This icon represents the communication path between the 2 Integrated Network Controller systems; Green if the communication is UP, and Blue if DOWN.
Displayed below is a diagram of a NMS-NMS interface.
Telephone
Company “A”
NMS
Telephone
Company “B”
NMS
Figure 1-1. NMS-NMS Interface Depiction
April, 2009 1-25
Introduction
The actual Integrated Network Controller systems will not be displayed on the GUI map display as shown above. The NMS-NMS interface will be represented by an interface icon as shown below.
NMS-to-NMS
Interface
Figure 1-2. NMS-NMS Interface Icon
1-26 April, 2009
Introduction
Northbound Interfaces
1340 I
ntegrated Network Controller
to NFM Interface
Integrated Network Controller supports a northbound interface to Alcatel-Lucent’s NFM. NFM is an alarm gathering system which interfaces to other Alcatel-Lucent systems. 1340 INC interfaces with NFM through a G2 interface specification. Once the interface is setup in 1340 INC, it will pass all alarms through a LAN connection to NFM in the specified G2 format.
1340 I
ntegrated Network Controller
to SNMP Interface
1340 Integrated Network Controller supports an SNMP Proxy Agent for multi-vendor SONET Add/Drop
Multiplexer (ADM) network elements, LambdaUnite® Multiservice Switchnetwork elements and Metropolis® WSM network elements, directly managed by 1340 INC or through the SNC EMS interface. The
SNMP Proxy Agent is based on SNMP (Version 2) MIBs (Managed Information Base) and acts as the proxy for each managed SONET NE. The Proxy Agent generates ADM alarm/PM report traps based on autonomous Alarm/PM events recorded. The traps are sent autonomously to interfacing SNMP Network Management applications such as HP OpenView and Micromuse Netcool.
1340 INC can process SNMP traps from any device and display the trap information in the 1340 INC Alarm
List. 1340 INC can also derive the interface alarms on an SNMPdevice by retrieving the ifAdminStatus and ifOperStatus MIB objects.
To manage an SNMP device, the SNMP device must be entered into 1340 INC via the NE Management form. The NE Type selection must be set to "GENERIC SNMP". The IP address and "read-access" SNMP community string must also be entered on this form
— SNMP Trap Processing - LinkDown trap with ifAdminStatus = up(1) will generate a
FAC category active LinkDown alarm against the ifIndex in the trap. LinkUp trap or
LinkDown with ifAdminStatus not equal to up(1) will clear any FAC LinkDown alarm against the ifIndex. If the ifIndex MIB object is missing from the LinkUp or LinkDowntrap, the trap will be generated as an ALERT category alarm. Additionally, if the ifAdminStatus is missing from the LinkDown trap, an ALERT category alarm will be generated instead of a FAC alarm. All traps (except LinkUp and LinkDown) are generated as ALERT category alarms. ALERTs are one-time events that do not stay active as
FAC alarms do. For any alarm, the alarm description text contains all of the MIB objects and values in the trap. The MIB objects will be listed by textual name if the MIB containing that object has been compiled into 1340 INC (see item "Compiling/Installing new MIBs into 1340 INC" below ). Otherwise, the trap MIB objects will be shown by
OID number. The name of the 1340 INC alarm will be the trap name from the MIB. If the MIB has not been compiled into 1340 INC, the alarm name will be the enterprise name concatenated with the trap number.
— Alarm Sync - The alarm sync (a.k.a. Match) feature can assert and clear FAC LinkDown alarm conditions by retrieving ifAdminStatus and ifOperStatus from the ifTable in the
SNMP device. A FAC LinkDown alarm is generated against the ifIndex if ifAdminStatus is not down(2) and ifOperStatus is down(2). If ifAdminStatus is down(2) or ifOperSta-
April, 2009 1-27
Introduction tus is not down(2), any FAC LinkDown alarm that exists against ifIndex is cleared. If the
SNMP device does not provide both ifAdminStatus and ifOperStatus objects, thenLink-
Down alarms cannot be asserted or cleared via the Alarm Sync feature.
— Compiling/Installing new MIBs into 1340 INC - To see trap names and MIB object names appear in 1340 INC alarms, the MIBs containing these objects must be compiled and installed onto 1340 INC. This is done by sending the MIB(s) to the 1340 INC development team for compilation. Two files are output from the MIB compilation: snmpinfo.datand straps.def. These 2 files are placed in /usr/cnc/snmp/srconf directory on the
1340 INC server - the back-end server in a multi-box configuration - overwriting the existing files. The brassd process on the 1340 INC server must then be restarted to load these new files. This is done by:
— /usr/cnc/snmp/bin/S566SnmpBrass stop
— /usr/cnc/snmp/bin/S566SnmpBrass start
Restarting the brassd process automatically restarts snmp_trap which is necessary for the new MIB files to take effect. After performing these steps, traps containing OIDs from these new MIBs will be seen in 1340 alarms with OID names instead of numbers.
1340 I
ntegrated Network Controller
to NSPM Interface
Integrated Network Controller supports a northbound system interface to the IDCM system. It is based on
TMF G7 CORBA 529. This interface provides the ability to perform flow-through provisioning in 1340
INC.
1340 I
ntegrated Network Controller
to DNA CA Interface
Integrated Network Controller supports a system interface to the DNA Capacity Analyzer (CA) system. This interface sends NMS level data for all 1340 NC supported network elements and EMS level data for the Tellabs Titan 5500 3/1 DCS to the DNA CA system.
1340 I
ntegrated Network Controller
TL1 Interface
Integrated Network Controller supports a full function northbound TL1 interface.
1-28 April, 2009
Introduction
Terms and Usage
In order to be clear in the use of terminology, the following section describes the terms that will be used to define various parts of the system. The use of different structures and constructs in a GUI based system can vary widely. This section is designed to provide clarity and consistency in the use of system specific terms.
Alarm Central - Shows a running record of alarms that are currently in the system.
CLI - Common Language Identifier - a code used to define a circuit or NE.
Facility/Port/AID - These terms are used interchangeably on various forms.
Filters - These items allow the user to display only the data designated (i.e. From “Date” - To “Date” will show only data records that were created between the given dates). Filters may be text boxes that allow users to enter data into, or drop down lists with pre-populated choices.
Form - A screen that contains specific data (i.e., Work List form, Display Problem PM form, etc.)
Function Tabs - The Function Tabs (Administration, Alarms, Configure, etc.) are designed to allow easy access to the information that is managed by the Integrated Network Controller system.
Main Display Area - Displays the results of any query launched from the Launch Area.
Launch Area - This area will display filters (specific to the tab and drop down menu chosen) that allow the user to easily search for data
Navigation Drop Down List - the list displayed when a specific line item in a report is selected. These lists allow the user to easily navigate from one form to another or move pertinent data from one form to another.
NE - Network Element - 1340 INC managed network elements, i.e. Alcatel-Lucent DACS IV, Tellabs 5500,
Alcatel 1631 LMC, Alcatel-Lucent DDM 2000 OC3, and Fujitsu FLM 150.
Options - These are selectable items that will display the data in a specified way.
PQV - Performance Quality Value - A value between 0 and 100 derived from the collected PM. This value represents the absolute quality based upon seconds that had performance problems. The value is displayed as a percentage of seconds in a twenty four hour period that there were no problems.
Service View - A logical name associated with a facility databased in the Integrated Network Controller system
April, 2009 1-29
Introduction
1-30 April, 2009
Getting Started
Chapter Contents
•
•
•
•
•
•
Service View Wizard on page 2-13
•
•
Search Capability on page 2-18
•
Customize Table/CSV/Print Report on page 2-19
•
•
•
•
April, 2009 2-1
Getting Started
Logging In
In order to login to the Integrated Network Controller system, the user must obtain the appropriate URL from their system administrator. Once the URL is executed, the Integrated Network Controller Login screen will be displayed.
Figure 2-1. Login Form
Fields:
• User ID: Unique Login ID of the user attempting to log in.
• Password: The password of the user attempting to log in.
Buttons:
• Login - Selected after the User ID and Password fields have been populated and the proper interface has been selected
• Clear - Clears the User Id and Password fields.
2-2 April, 2009
Getting Started
• Interfaces - a drop down list that contains the names of the systems that the user may log in to. These interfaces are defined in a file described in the Integrated Network Controller
Application Installation Guide.
Once the User ID and Password fields have been populated, and an interface has been chosen from the drop down list, the user will select the Login button. The screen will display the message “Initializing session please wait...” after which the Main Screen will be displayed.
NOTE:
The Server (by name), it’s IP Address, and the Browser that is being used, will be displayed in the lower left hand corner of the Login screen.
Timecheck
The Timecheck screen will be displayed if the time between the WEB GUI Server and the 1340 INC core are different or if the time between the WEB GUI Server and the user workstation are different (or both).
Figure 2-2. Timecheck
April, 2009 2-3
Getting Started
Message of the Day
There is a capability within the Integrated Network Controller system to display a “message of the day”.
This message is contained in a file as part of the UNIX ® file system and can be updated and changed, as appropriate. If the file is present, Integrated Network Controller will display the message upon successful login. If no file exists, the Integrated Network Controller main screen will be displayed. Please see your
UNIX® administrator for a description and location of this file.
Figure 2-3. Message of the Day
2-4 April, 2009
Getting Started
Welcome Screen
The main screen is the “home” from which all other 1340 INC usage is begun. It is made up of four primary areas.
Alarm Central: Shows a running record of alarms that are currently in the system.
ID Area: This area will display the Login ID of the user, the 1340 INC machine they are logged into, and the date and time
Function Tabs: Located along the top of the main screen, the Function Tabs are designed to allow easy access to the information that is managed by the Integrated Network Controller system.
Title Bar: Directly below the function tabs, this area is used to display menu choices
Launch Area: Located below Alarm Central. This area will display filters (specific to the tab and drop down menu chosen) that allow the user to easily search for data.
Main Display Area: Displays the results of any query launched from the Launch Area.
Figure 2-4. Welcome Screen
April, 2009 2-5
Getting Started
User Logos
If a User Logo is located on the WEB GUI server, that logo will be displayed on the Welcome and About screens. Console and console aliases will see a “Licensed to” qualifier and users and user aliases will see a
“Supplied by” qualifier. See the Integrated Network Controller Application Installation Guide for a detailed description and location of these files.
Figure 2-5. Welcome Screen with logo
2-6 April, 2009
Getting Started
Alarm Central
Alarm Central is designed to give users a view of the current state of alarms in the Integrated Network Controller system.
Figure 2-6. Alarm Central
When a new alarm is asserted, the icon of the associated alarm type (FAC, EQU, etc.) will begin blinking.
When the icon is selected, a new window will be displayed showing the pre-populated filters and the current alarm data. Once the alarm has been displayed, the icon will continue to show the alarm color (non-blinking) until the alarm is cleared. If an icon is selected of a type which has no current alarms, the Launch Area filter will be pre-populated with the selected type and the Main Display Area will be blank.
The area below Alarm Central is the ID Area and will display the Login ID of the user, the 1340 INC machine they are logged into, and the date and time.
Figure 2-7. ID Frame
April, 2009 2-7
Getting Started
Function Tabs
Function Tabs: The Function Tabs are designed to allow easy access to the information that is managed by the Integrated Network Controller system.
Figure 2-8. Function Tabs
When the cursor is moved over any of the tabs, the system will display the list of choices that are associated with that tab via a drop down list.
Figure 2-9. Function Tab Dropdown List
2-8 April, 2009
Getting Started
When a tab is selected, the drop down list items will be placed in the title bar area.
Figure 2-10. Function Tab after Tab Selection (Title Bar)
When any single item is selected, the item will become highlighted and the Launch area will be populated with the appropriate filters and selection criteria.
Figure 2-11. Menu Item Selection
April, 2009 2-9
Getting Started
General Usage
There are several constructs that are used throughout the Integrated Network Controller system that merit description:
<SEARCH>, <NEW>, <ADD>, <SUBMIT>, <UPDATE>, <DELETE>, <CLEAR> and
<CLOSE> buttons
These buttons may be located in the Launch Area, or on reports or forms:
The <Search> button executes the query as outlined using the selected filters and populates the main display area
The <New> button executes the search in a new window, leaving the original window displayed
The <Add> and <Submit> buttons will place information into the Integrated Network Controller database.
The <Update> button is used to re-enter information into the Integrated Network Controller database after it has been edited by a user.
The <Delete> button is used to remove information from the Integrated Network Controller database.
The <Clear> button displays the default values in the filter fields (if a default value exists), and clears any manually entered values from the filter fields. If the <Clear> button is selected on a window that was displayed via the <NEW> button, the fields return to the values originally used to open the <NEW> window.
The <Close> button closes the form or current window
!
CAUTION:
Use of the <BACK> button, <Forward> button, HOME key, or any special key, via keyboard, menu, or mouse, or browser shortcut keys (i.e.<ctrl> n, etc.) may cause unexpected results and should not be used.
More Options/Less Options
The “More Options” / ”Less Options” is a toggle value located in the Launch Area for various reports. It is displayed when there are a significant number of filters or options to choose from.
The “More Options” item allows the user to select more filters to narrow their search
The “Less Options” item allows the user to select less filters to broaden their search
2-10 April, 2009
Getting Started
Auto Refresh/Refresh Interval
Some forms allow for an automatic refresh of the data that is currently displayed. When the Auto Refresh checkbox is selected, the associated form will be automatically updated. The Refresh Interval is the value (in seconds) that will elapse before the next update. To change the Refresh Interval, the Auto Refresh box must be de-selected and then re-selected.
Line Selection from Reports
When the cursor is positioned over a line in a report, the line will turn from it’s current color to gray. When a specific line item is selected, the line will turn from gray to blue. This line will stay selected until a different line item is chosen. This allows the user to navigate from one report to another without losing the source of the navigation.
Type Ahead Capability
Many forms include drop down lists (such as NE, User, NE Type, etc.) as filters. In some instances, these lists contain hundreds of databased values, making it cumbersome to manually search the list for the value the user wishes to use.
As characters are entered into a popup box, the drop down list will automatically go to values in the list that match the characters entered.
Figure 2-12. Drop Down List Filter
If a character is typed into the popup field that does not match any of the values in the list, the popup box will turn red.
Copy and Paste TID
1340 INC offers the ability to copy and paste a selected TID from one form to another. Once a TID has been selected from the NE drop down list on a form, it is automatically “copied” and saved to the clipboard.
When the user then goes to any ensuing form that contains the NE field as a drop down list, they may select the field and use the <Ctrl> <v> character sequence or use the right mouse button to “paste” the previously chosen TID into the field.
April, 2009 2-11
Getting Started
NE List
As customers may be responsible for management of hundreds of network elements, the 1340 INC can be configured to automatically shorten the NE List on GUI forms. Via a GUI control file, the user may set up the 1340 INC so that as each character is typed in the NE field, a drop down list of only those NEs that match the typed characters are shown in a popup box to ease selection of a specific choice. See the 1340 INC
Installation Manual for details setting up the GUI control file to incorporate this feature.
2-12 April, 2009
Getting Started
Service View Wizard
The Service View Wizard allows the user to display all available service views (facilities). This icon (seen at the end of the Service View field) appears on many Integrated Network Controller forms and reports where service view will act as an input field or a filter option.
Figure 2-13. Service View Wizard icon
The Service View is the name used by end users to reference their facilities in the Integrated Network Controller database. When assigning facilities to a user’s partition, the console administrator consults with the end-user to determine the Service View for each facility. The format of the Service View varies depending on the type of facility, but is generally as follows:
Service Type Name.Facility.Timeslot
where
— Service Type Name = Alphanumeric name for facility. (up to 11 characters; can include underscore “_” character). There is a limit of 500 different service type names per user partition. The service type name is a logical name and usually describes the location and or function of the facility.
— Facility = Logical facility number. Does not have to match the Physical View. This allows the service type name to be re-used for additional assignments.
— Timeslot = Logical timeslot or channel number. Does not have to match the Physical
View.
The following example describes the relationship between the Physical View and The Service View using logical names.
A user has a T1 in a 1/0 DCS.
• The Physical View contains the physical identifier (AID) for a facility on a network element.
The number of fields may vary depending on the facility type and network element type.
For example, a physical view may be displayed as 100.25.1-24. This means that the T1 is in the DCS with NE ID 100, and it is in physical port/digroup/NPC number 25 in the
DCS. Since it is a T1, it has channels 1-24.
• The Service View should make the assignment easy to identify to the end user. Some examples using the same port as above are:
•
voice.25.1-24 = facility #25 used for voice circuits
•
data.25.1-24 = facility #25 used for data circuits
•
atlantat1.25.1-24 = T1 #25 located in Atlanta
•
atldata.25.1-24 = Atlanta data circuit #25
April, 2009 2-13
Getting Started
The Service View Wizard allows the user to choose a specific NE and level, of service views to be displayed.
A specific Service View can then be chosen via the tree and selected (via the <Select> drop down choice).
The selected view will then be automatically populated in the appropriate input field or filter field. The
<Cancel> button will close the Service View Wizard.
The format of the service views displayed by the Service View Wizard will vary based upon the mode and feature files defined in the Integrated Network Controller. The following are examples of typical Service
View trees.
Figure 2-14. Service View Wizard tree - CNM mode using a logical service type name
2-14 April, 2009
Getting Started
Figure 2-15. Service View Wizard tree - CNM mode - physical only
April, 2009 2-15
Getting Started
Figure 2-16. Service View Wizard tree - EMS mode
NOTE:
In EMS mode, the service views are listed in the tree by card
2-16 April, 2009
Getting Started
Lines per Page
At the bottom of displayed reports is a count of how many lines populate the report, and how many pages of data are contained in the report. The “Lines Per Page” and “Pages Per List” values are user defined and can be set in the View Tab via Preferences -> Miscellaneous.
The left and right arrows allow the user to go to the previous or next page, respectively, and the double arrow
(->>) or (<<- ) allows the user to go forward or backward, respectively, in increments of the value defined by the “pages per list” variable. The page the user is currently viewing will be highlighted, and the other pages will be underlined. The user may also display a specific page by entering the page number in the Page text box and selecting the <GO> button.
Selection of the <ALL> button will display all entries in the report, with an associated slide bar, if necessary.
NOTE:
If the user selects <ALL>, the report will be re-displayed in a paged format including a slider bar to move forward and backward through the report. The report will also display a <Return to Paged Report> button that allows the user to return to a “paged” display.
Figure 2-17. Lines per Page
April, 2009 2-17
Getting Started
Search Capability
Displayed reports offer the user the ability to search for a string within the report. Located at the bottom of the report form, the Search box allows the user to type in the string that they wish to search for. The search is
case insensitive and does not include the use of wildcards (i.e. *).
Figure 2-18. Search for Reports
Once the search has been executed, the report will be re-displayed showing all lines in the report that contained the search string with the search string highlighted in
red
. The report will also display a <Return to
Full Report> button that will allow the user to return to the complete report.
2-18 April, 2009
Getting Started
Customize Table/CSV/Print Report
These icons are located in the upper left corner of the Main Display Area on retrieved reports and are described in detail on the following pages. The icons from left to right are: Customize Table, Create a CSV
Output File, and Print Report.
Figure 2-19. Customize Table/CSV/Print Report Icons
April, 2009 2-19
Getting Started
Customize Table
This form allows the user to specify:
1. The fields that will be displayed in a retrieved report (via the left and right arrows)
2. The order in which the fields will be displayed (via the up and down arrows)
3. The sort order of the fields (in ascending or descending order)
4. Restoration of the default settings for the table specified (via the <DEF> button)
Figure 2-20. Customize Table
2-20 April, 2009
Getting Started
CSV
Appearance of the output from this selection is dependent upon the setting in the View -> Preferences->
Miscellaneous tab setting under the CSV layout choice. When the “Text” value is chosen, the output will be displayed as a comma-separated-values list (as shown). This file can then be saved and imported into a report generating application, or a spreadsheet. When the EXCEL value is chosen, the output will be displayed in a Microsoft® Excel spread sheet.
Figure 2-21. CSV Output
April, 2009 2-21
Getting Started
Print Report
Displays the retrieved data in a tabular format suitable for printing.
Figure 2-22. Print Report
2-22 April, 2009
Getting Started
This will automatically be followed by a display of printer choices local to the user’s PC
Figure 2-23. Print Choices
April, 2009 2-23
Getting Started
New Window
The New Window icon, shown in the figure below, allows the user to execute a search in a new window, while maintaining the data and display in the window from which it was launched.
Figure 2-24. New Window icon (“search in current window” mode)
When selected, the icon will change to show that the user is now in “new window” mode.
Figure 2-25. New Window icon (“search in new window” mode)
NOTE:
The new window selection will only affect the tabs and menu items. That is, if the user is currently in the Reports tab, then selects the New Window icon, only searches that are
not menu items in the Report tab will be executed in a new window.
2-24 April, 2009
Getting Started
Collapse/Reopen
The Collapse/Reopen icon, shown in the figure below, allows the user to collapse the Filter area of pop-up windows so as to allow a larger area to be displayed in the main frame.
Figure 2-26. Collapse/Reopen icon
April, 2009 2-25
Getting Started
Help
The Help icon is represented by the question mark (?) symbol.
Figure 2-27. Help
Selection of the Help (?) icon will display the following choices:
• Context Sensitive Help - Selection of this menu item will take the user to a description of the form that is currently active.
• xxx Help - The Help choice(s) listed here will vary based on the feature set available to the user of the Integrated Network Controller software (i.e. Console, User, Network Ethernet, ATM/FR, etc.) and selection of the menu item will take the user to the beginning of the specified document.
• Contact - Allows a user to send an e-mail message to the Integrated Network Controller support team.
• About - Will display the current GUI release version and copyright information.
Additionally, users (console users and end-users) may see documents that were placed in the 1340 INC local access directories by their system administrators. These line items will be in one of two formats:
• filename (e.g. circuitnotes.pdf, readme.txt)
• directory/filename (tipsdirectory/provisioning_notes.pdf)
Please see the Integrated Network Controller Application Installation Guide for instructions on setting up these directories.
2-26 April, 2009
Getting Started
Logging Out
The logout function is represented by the arrow symbol located in the upper right hand corner of the Main
Screen and may be selected whenever the user chooses to log out of the system.
Figure 2-28. Logout
Selection of the logout icon will display the following message.
Figure 2-29. Logout Verification
NOTE:
If unsaved changes have been made to preferences or network data, the user will also be prompted to save or cancel those changes when logging out.
April, 2009 2-27
Getting Started
2-28 April, 2009
Chapter Contents
•
Administration Tab on page 3-2
•
•
•
•
•
“Default User” Card Management on page 3-10
•
•
•
•
•
•
April, 2009 3-1
Administration Tab
The Administration Tab allows the user to access management functions of the Integrated Network Controller system.
Figure 3-1. Administration Tab
3-2 April, 2009
Become User/Alias
The become option allows the console user to change the current map display to any desired user in the user list. This will allow the console user to display a user’s network exactly in the same manner as the user views his own network. For example, a user might use large icons, have customized network element and user node labels, or magnify around the southeast United States. Becoming the user would change the console user’s display to take on these characteristics. If the user logs into 1340 INC with a user alias login-ID, the console user can become the user alias.
Figure 3-2. Become User/Alias
To return to the previously viewed console level display, select the Logout icon.
NOTE:
The User/Alias drop down list displays a list of users that the selecting user may become.
Entries that are indented under the users are aliases of that user.
April, 2009 3-3
Plus Charge Option
The Become User /Alias form also has a check box labeled ‘+Charge’ (Plus Charge). Checking this option will put an entry in the 1340 INC daily transaction log. This option is used in the event an 1340 INC user contacts an 1340 INC console administrator to make a connection for the user which could be a billable transaction. This entry in the transaction log will allow console administrators to keep a tally of connections or disconnections made for customers of 1340 INC and render a bill for such transactions.
3-4 April, 2009
Change Password
The Change Password form allows console users to change their own password.
Figure 3-3. Change Password
Buttons:
• Submit - processes the password change request
• Clear - clears the form of any input
NOTE:
PASSWORD RULES:
n n
They must be at least 6 characters in length, but cannot exceed 8 characters in length.
The first character must be alpha, and the remainder can be made up of any combination of alphanumeric characters and the special characters
“_” (underscore), “!” (exclamation), “.”(period), and “$” (dollar sign).
April, 2009 3-5
n n
Use of spaces, caret (“^”), at (“@”), pound (“#”), colon “:”, and the ampersand (“&”) is prohibited.
Passwords cannot be repeated. That is, a previously used password cannot be re-used.
3-6 April, 2009
Cycle Windows
This feature, when enabled, automatically raises each window containing an 1340 INC WEB GUI to the top of your desktop, for a set duration. This feature is useful when it is necessary to view, or cycle through, a number of WEB GUI forms that are monitoring different functions.
The Cycle Windows form is available as a menu choice under the Admin menu of the main display. The
Cycle Windows form can only be used in the 1340 INC main window. The main window is that window that contains the menu choices, and Alarm Central. If you attempt to open the Cycle form in a separate window, the operation will be denied.
When the Cycle form is displayed it will contain a list of all of the open 1340 INC WEB GUI windows. For each window a View time, in seconds, for the window to remain on top can be set. When the Start Cycle button is pressed, each window in that list will be raised to the top of the other windows on your desktop for the specified number of seconds. When the Stop Cycle button is pressed, the cycling action will stop. If a new window is opened or closed, then use the Refresh button on the Cycle Windows form to refresh the list of
Windows. To skip over a form (that is, do not raise the window), set the View Time to 0.
Figure 3-4. The Cycle window available from the Admin menu.
April, 2009 3-7
Figure 3-5. Cycle windows are automatically raised as the top window on your desktop every
n seconds.
NOTE:
The Cycle Windows form will display only first level windows, and only first level windows can be set to cycle to the top of your desk top. A first level window is a window that is directly opened from the Main window, and not indirectly from another. For examples, windows opened as a navigation from another window are not first level windows.
3-8 April, 2009
Dashboard
The Dashboard form allows the user to get a snapshot view of specific system statistics. Via selection of checkboxes in the filter area, the user may view T1 availability (also called Active Link Examination or
ALEX), Active Alarms and Interfaces. It also includes the number of NEs in the system and how many of those NEs are up.
The Legend can be displayed or hidden based upon selection of the Legend checkbox.
Figure 3-6. Dashboard
April, 2009 3-9
“Default User” Card Management
When the Associate Alarms with Default User checkbox is selected on the NE Management form, equipment alarms are mapped to the NE default user. By default, all equipment alarms that cannot be correlated to an assigned facility, will be mapped to the default user. It is possible, however, to direct only a subset of alarms to the default user by setting filters which identify particular customers, NE types or particular NEs which should be mapped.
These filters are controlled by a set of files which can either be maintained using a standard editor, or through the WEB GUI and they allow the user to filter by User per NE type, one specific NE, or an NE type system wide. See the Integrated Network Controller System Installation Guide for details on maintaining the file names and locations that control these filters.
Figure 3-7. “Default User” Card Mgt
Buttons:
• Add - allows the user to add an entry
• Update - allows the user to edit/update and entry
3-10 April, 2009
• Delete - allows the user to delete an entry
• Clear - clears the form of any input
April, 2009 3-11
INC Cut Thru
The INC Cut Thru form allows the user access to 1340 INC specific commands via the GUI. When a command is typed into the Command text box and submitted (via the <Submit> button), an output screen will be displayed listing the command responses.
Figure 3-8. INC Cut Thru form
3-12 April, 2009
INC Messenger
The INC Messenger feature allows GUI users that are logged in to converse with other GUI users that are logged in. This is accomplished via the use of the User list that is displayed when INC Messenger is selected from the Admin menu. Use of this feature will be driven by a command privilege administered via the Alias
Management form. If the privilege is turned off for a console alias or user alias, they will still be able to send and receive messages, but they will not be able to initiate an IM session.
The following list defines what users will be available (assuming they are logged in) to each type of login.
Console - users defined in User Group (View -> User Group) and associated aliases, other console logins, and console aliases
Console aliases - users defined in User Group (View -> User Group) and associated aliases, other console logins, and console aliases.
Users - Aliases of themselves, console logins, and console aliases
User Aliases - other aliases of the same user, the user they are an alias of, console logins and console aliases.
NOTE:
Users will not be able to IM other users or aliases of other users.
Selection of the <Search> button will display the INC Messenger Buddy Report.
April, 2009 3-13
When selected, the INC Messenger form will be displayed
Figure 3-9. INC Messenger
3-14 April, 2009
When the <Search> button is selected, the INC Messenger Buddy Reports will be displayed.
Figure 3-10. INC Messenger Buddy Report
Column Definitions:
• User: Login ID.
• TTY: Port number used to distinguish multiple logins for a single login id.
• Name: Name of the user, as defined in the Alias Mgmt form or User Information form.
• Owner: Meaningful for aliases. If console, owner = console, if user, owner = user. However, if a console alias, owner = console, if a user alias, owner = aliased user.
Once a “buddy” has been selected, the IM chat window will be displayed. The title bar shows the User and
TTY port of the user you are “IM-ing”. The text line displays the senders login id, the time of the message and the text being sent.
April, 2009 3-15
NOTE:
The senders input will be displayed in red , the receiver’s responses will be displayed in blue.
Figure 3-11. INC Messenger Chat Screen
Buttons:
• Close - closes the form
• Send - sends the message to the selected buddy.
3-16 April, 2009
Log Files
The Log Files feature allows users to view system log files that have been created within the past 30 days.
These log files are records of TL1 messages sent to and received from, network elements being monitored by Integrated Network Controller, including autonomous messages sent by the network element.
Figure 3-12. Log Files
Filter:
• Type - Allows the user to choose the type of log file being viewed
•
All - all log files created
•
Daily - log files created each day
•
NE - log files created for a specific NE
April, 2009 3-17
•
CGRP - log files created for a specific Communications Group
•
Restore - log files created as a result of a user executing a Restore on an NE.
These logs are saved based on the NEID and the date that the Restore was executed.
•
NE Cut Thru Batch - log files created as a result of a user executing a <Batch> command from the NE Cut Thru form.
NOTE:
The NE and CGRP logs are created by executing a Watch on a specific NE or Comm
Group and will only be present based upon that execution
Navigation Drop Down List:
• Browse - opens up the selected log file for viewing (browsing)
Figure 3-13. Browsing a Log File
3-18 April, 2009
Text Fields:
• Page - Allows the user to navigate to a specific page by entering the page number and selecting the GO button. The number of lines is set on the View -> Preferences - Miscellaneous tab in the Browse Logs Lines Per Page field. As these files can get quite large, this value should be set accordingly.
• Search - Allows the user to enter a character string and search backward or forward via arrow buttons. This search is case insensitive.
April, 2009 3-19
Match
The match function may be used in two ways:
• to synchronize the cross-connection status of the 1340 INC facility database with the cross-connect status of facilities within the network element. A cross-connect match can be performed by User, by NE, or by Subnetwork.
• to synchronize the 1340 INC alarm database with the alarm status for a network element. An alarm match can be performed by NE or by Subnetwork. The alarm match will query the selected NE for any active alarms and compare them to the 1340 INC alarm data base.
1340 INC sends the appropriate alarm query command to the network element based on its type. For some SONET network elements, 1340 INC will also send a condition query, which will allow for matching of environmental and other types of alarms. After the match has completed, the 1340 INC alarm status will match the NE alarm status.
Once all appropriate fields have been populated and the <Submit> button is selected, the match function will take place and a message window will appear indicating the completion status of the match.
The <Schedule> button located at the bottom of the Match form allows console and console alias users to schedule an alarm match or cross connect match. Selection of the <Schedule> button will display the Scheduled Command Management form with the user and command fields pre-populated. Once all information has been entered on this form, the user may schedule the command via the <Submit> button.
3-20 April, 2009
Figure 3-14. Match
Select Buttons:
• by User - Allows match to be performed on a specific user (XCON match only)
• by NE - Allows match to be performed on a specific NE
• by SBNK - Allows match to be performed on a specific subnetwork
Fields:
• User - List of available users
• NE - List of network elements defined in 1340 INC
• SBNK - List of subnetworks defined in 1340 INC
• Service View - Available for “by User” XCON match
• Physical View - Available for “by NE” XCON match
• XCON ID - Available for “by User” XCON match
April, 2009 3-21
Select Buttons:
• Alarm Match / XCON Match - These choices are only displayed if the NE or SBNK choice has been made
3-22 April, 2009
NE Cut Thru
The NE Cut Thru allows cut-thru (pass-thru) access to any NE for command I/O in the native language of the selected network element. A maximum of 10 cut thru sessions may be established to any single NE and a maximum total of twenty (20) cut thru sessions may be established per login.
Figure 3-15. NE Cut Thru
Filter:
• NE - Allows the user to cut-thru to the NE specified. This list will be made up of NE’s that are associated with their selected user partition(s), and are currently UP.
• NE (manual type) - Allows the user to cut-thru to any NE by typing in the correct TID or
NEID
Buttons:
• Cut Thru - Opens up the NE Cut Thru Command/Response form
April, 2009 3-23
• Clear - clears the selected values in the launch area
Once the user selects the Cut-Thru button, the NE Cut Thru Command/Response form is displayed allowing users to enter commands and receive responses from the selected NE.
The Launch Area contains a box titled “NE Commands” which is a list of default commands for the type of
NE being cut thru to. Each line contains a command that may be selected and transmitted to the NE. When a command is chosen and followed by selection of the <Select> button, the “Selected Command” text bar will become populated with the actual command syntax to be issued to the network element. If AIDs or additional parameters are needed in a command, the associated text box will become sensitive and the user may type the AIDs or parameters required for the command.
The Main Display Area will now contain a message stating “You are now in Cut Thru to NE-ID xxxx”
(where xxxx is the ne-id of the node that will be receiving the commands). Once a command has been chosen and the <Send> button has been selected, the Main Display Area will display the command and any associated response to the command. Each command that is sent to the NE will also be automatically saved in the
“Command History” drop down box. The user may then select a command from that box using the <Select> button, edit the command (if desired) and issue it to the NE via the <Send> button located below the Main
Display Area.
Figure 3-16. NE Cut Thru Command/Response Form
3-24 April, 2009
NOTE:
As noted, 1340 INC allows 10 cut thru sessions per NE and 20 cut thru sessions per login. In order to accomodate this number of sessions, the connection limit in IE (versions 6 and 7) must be configured as follows:
• Start the Registry Editor ( in the Windows RUN window, type regedit)
• Navigate to HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings
• From the Edit menu, select New-> DWORD Value and add the following registry values
•
Value name: MaxConnectionsPer1_0Server
•
Value data: 30
•
Base: Decimal
•
Value name: MaxConnectionsPerServer
•
Value data: 30
•
Base: Decimal
• Exit the Registry Editor
NOTE:
If the user does not have the appropriate privilege to send a command (set via the Alias
Management form) , a message will be displayed indicating the lack of privilege and the associated command.
NOTE:
A “Please Wait” message popup will be displayed if the response to the cut-thru command is large.
Launch Area
The “NE Commands” box contains a list of TL1 commands that may be sent to the network element that
1340 INC is communicating with (cut thru to).
The “Documents” area is a list of documents that can be selected and viewed by the user. These documents are based on the type of NE being cut thru to and reside in a directory on the 1340 INC GUI Server. They are placed there at the user’s discretion. If there are no documents present, then there will be no “Documents:” header displayed in the launch area. Please see the Integrated Network Controller Application Installation
Guide for information on the setup of this capability.
April, 2009 3-25
Text Fields
These boxes will contain the words “Enter Value” when AIDs or additional parameters are needed in a command, allowing the user to type the AIDs or parameters required.
• AID 1
• AID 2
• Parameter 1
• Parameter 2
NOTE:
These labels are user definable and can be set up via a file on the 1340 INC GUI Server.
Please see the Integrated Network Controller Application Installation Guide for information on the setup of this capability.
Buttons - Launch Area
• Select - Populates the “Selected Command” text bar with the chosen command
• Clear - de-selects chosen values from the NE Commands box and the AID and Parameter fields
• Close - Closes the Cut-Thru form
Script Management on page 3-33
3-26 April, 2009
• Change NE - Allows the user to change the NE that is currently being cut-thru to.
Figure 3-17. NE Cut Thru - Change NE
April, 2009 3-27
The Change Cut Thru NE popup will show the NE that currently has a cut thru session established as well as a drop down list of NEs that the user may change to (those that are in the users Viewed NEs list). When a change is selected, the user will be prompted with the following message requesting whether to save or clear the command history.
Figure 3-18. NE Cut Thru - Change NE - Command History request
3-28 April, 2009
• Send to Multi NE - Displays the Send to Multiple NEs form, allowing users to send the same command to more than one NE. The command is selected in the same way as when sending a command to a single NE. Once the <Send> button is selected, the command will be issued to each NE in the Send To list in succession and all NEs in the Available list will be removed. If the command is successful, the NE will be moved back to the Available list. If a command is unsuccessful, it will remain in the Send To list. In either case, the command/response output will be displayed.
NOTE:
Commands are not necessarily formatted the same for different NE types. If a user chooses to send a command to more than one NE type at a time (i.e. an ALU DMX and a
Cisco 15454, the command may succeed for one NE and not the other).
Figure 3-19. NE Cut Thru - Send to Multi NE
April, 2009 3-29
Fields (on Multi NE form)
•
Send To - the list of NEs that the selected command will be sent to.
•
Available - the list of available NEs that the command can be sent to.
•
Move Options: these checkboxes allow the user to move an entire subnetwork, entire NE group, or an entire Comm group from the Available list into the Send
To list.
•
Filter by (with Filter button) - allows the user to select an NE type. Selection of the <Filter> button will populate the Available list with all NEs of that type from the user’s Viewed NE list (NEs that the user can send commands to).
Checkbox (on Multi NE form)
•
On Send Keep Avail List - if selected, the NEs in the Available list will continue to be displayed after selection of the <Send> button. Otherwise, NEs in the
Available list are removed upon selection of the <Send> button.
Buttons (on Multi NE form)
•
Stop Multi Send - stops sending the selected command to multiple NEs
•
Close Multi Send - closes the Send to Multiple NEs form
•
Batch - allows the user to send a single command to multiple NEs. This processing is done in the background, so that cut thru command processing can continue.
A batch name must be entered for the <Batch> button to become sensitive. Once the <Batch> button is selected, the following message will be displayed:
Figure 3-20. NE Cut Thru - Batch processing message
As shown, once the batch processing is complete, an alert will be sent to Alarm Central, and the output can be viewed by looking at the Admin -> Log Files -> NE Cut Thru Batch.
3-30 April, 2009
NOTE:
The alert generated by batch processing cut thru commands is an INC alarm. Therefore, under the View -> Preferences -> Alarm Age/Filter tab, the INC category must be set to
Process=Yes, Filter = No.
Drop Down Lists - Main Display Area
• Output -
•
All - Allows the user to see all messages to and from the network element displayed in the Main Display Area
•
Just Mine - Displays only those commands and corresponding responses sent by the user
•
Split - Splits the output screen so that the user can see all commands and responses in one frame, and just their own in another frame.
NOTE:
The value that is selected for Output will be saved as a user preference so that each time the user logs in, the Output field will be set to their previously selected choice.
• Command History - contains a record of all commands sent during the current cut-thru session
•
Select (Command History) - Populates the “Send” text bar with the chosen command
• Available Scripts - contains a list of all currently defined scripts
•
Select (Available Scripts) - Populates the “Send” text bar with the selected script
• Script Timeout - number of allowable seconds between execution of each command in the script. The default value is 30 seconds. Expiration of the timeout value will cause the script to fail.
Buttons - Main Display Area
• Send - Sends the selected commnand or script to the NE.
NOTE:
The maximum number of characters allowable in an FE command is 240.
• Case Sensitive - Selection of this checkbox indicates that the TL1 command being sent will be case sensitive (not converted to upper case).
• Clear - Clears the display screen
• Print - Prints the display screen to a selected system printer
• Auto Scroll - allows the user to turn auto scrolling on (selected), or off (unselected). If auto scrolling is turned off, the user must use the scroll bar to scroll.
April, 2009 3-31
• Save to Script - The Script Management form must be open for this button to be sensitive.
Selection of this button will turn control over to the Script Management form and will populate the Script Contents area with the currently selected command. This allows the user to build and save scripts easily.
3-32 April, 2009
Script Management
The script management feature provides the ability to manage scripts containing TL1 commands. Scripts can be created, edited, and deleted from the Script Management form.
Console can edit and delete console scripts. Console aliases can edit and delete their own scripts and have read access to console scripts and other aliases’ scripts.
Existing scripts are listed in the Scripts text box. Users may name their scripts as they are created via the
Script Name text box.
Figure 3-21. Script Management Form
Buttons - Launch Area
The buttons on the Script Management Form perform the following functions:
• Refresh - refreshes the Scripts list
• Select - selects the highlighted script in the list and populates the Script Contents area of the form
• Load - copies the contents of the highlighted script to the Script Contents field. This allows users to use existing scripts as templates for new scripts.
April, 2009 3-33
• Close - closes the form
Buttons - Main Display Area
• Add - creates the script
• Update - updates the selected script
• Delete - deletes the selected script
• Clear - clears the Script Contents portion of the form
Creating Scripts
Enter TL1 commands in the Script Contents field in either of the following ways:
• Type commands in the Script Contents field
OR
• Select a command from the NE Commands list and select the <Select> button to populate the command line, followed by the <Save to Script> button
When the script is complete, THEN
• Select the <Add> button on the Script Management form
Four different parameters can be passed to a script as follows:
• $1 is replaced by the value entered in AID1
• $2 is replaced by the value entered in AID2
• $3 is replaced by the value entered in Parameter1
• $4 is replaced by the value entered in Parameter2
An example of a line in a script with parameters for substitution is as follows: ent-crs-sts1::$1,$2:;
When the script with this substitution line is selected from the Available Script list, the AID 1 and AID 2 fields will display the “Enter Value” message, indicating that the user must enter the values desired for the script to run.
Comments can be entered on lines using the following rules:
• '#' is at beginning of a line
• there is white space preceding the '#'
3-34 April, 2009
• '#' is preceded by semicolon ';'
An example of a line in a script with a comment is: rtrv-crs-vt1::all:; # Get all VT1 cross-connects
Executing Scripts
On the NE Cut Thru Form:
• Select a script from the Available Scripts dropdown list
• Choose the <Select> button to populate the command line
• If desired, enter a value in the Script Timeout field to set the number of seconds to wait for each command in the script to complete. The default value is 30 seconds. Expiration of the timeout value will cause the script to fail.
• Choose the <Select> button to populate the command field
• If any substitutions are required, fill in the desired values
• Select the <Send> button to execute the script
Editing Scripts
• Select a script from the Scripts list
• Choose the <Select> button to populate the Script Contents area
• Edit as required
• Select the <Update> button
Deleting Scripts
• Select a script from the Scripts list
• Choose the <Delete> button
April, 2009 3-35
Watch
The 1340 INC WEB GUI provides the ability to perform the watch command. This command opens a file containing all the messages sent to and received from the specified network element(s). This option assists users in identifying troubles related to link problems, failed commands, etc. by allowing the user to see exactly what command is sent to and what response is received from the network element.
Users can watch all NEs, a single NE, or all NEs in a communication group. When selected, the watch command opens a separate window which connects to the 1340 INC host. All watch messages are displayed in this window.
By default, the “Turn Watch Off On Close” checkbox is selected. This will cause the watch file that is being opened to automatically close when the user closes the watch form. If this is un-selected, the watch file will remain open on the 1340 INC host even though the user closes the watch form in the GUI. If for some reason it is desired to leave a watch file open and close it at a later time, then the user is able to access the Watch NE form and select the appropriate NE or COMM Group and check the “Turn Watch Off Now” box and select the <Submit> button. This will close the watch file on the 1340 INC host.
The <Status> button allows the user to see the status of the watch command at any point. Selection of the
<Status> button will open a separate window listing the specific processes being watched.
Figure 3-22. Watch
3-36 April, 2009
Figure 3-23. Watch Command/Response Window
Buttons:
• Close - Closes the window
• Print - Allows the user to print the output
• Clear - Clears the window of any existing output
The Auto Scroll selection allows the user to stop the scrolling of output within the window.
April, 2009 3-37
3-38 April, 2009
Alarms
Chapter Contents
•
•
•
•
•
•
•
April, 2009 4-1
Alarms
Alarms Tab
The Alarm Tab allows the user to execute searches of the alarm database via different categories, using a variety of filters.
Figure 4-1. Alarms Tab
Alarm Descriptions
Alarms are grouped into the following categories:
• FAC -is a Facility alarm and indicates that a circuit or a facility has failed (i.e. fiber cut)
• EQU - is an Equipment alarm and indicates a circuit pack failure or removal
• NE - indicates an alarm on the NE to 1340 INC connection status
• QoS - is a Quality of Service alarm indicating that a TCA (Threshold Crossing Alert) or PM
(Performance Monitoring) threshold has been crossed
• ALERT - is informational only
• MISC - is for Miscellaneous alarms (alarms that don’t fit into any other category)
• SYS - is a System Health indication and is designed to alert users to any customer problem
(i.e. running out of disk space)
• INC - is for internally generated alarms that pertain to problems with the 1340 INC application (i.e. a scheduled report did not run at the scheduled time)
4-2 April, 2009
Alarms
Active Alarms
The Active Alarms report displays all alarms that are currently active in the Integrated Network Controller system. Use of the Auto Refresh feature allows the list to be updated dynamically. Alarms will then be added to, and removed from the list as assert and clear messages are received. The list can be sorted by column and the sort selection is maintained when the list automatically updates. The Severity of alarms displayed follows the Preferences selected by the user (in the View ->Preferences tab - Alarm Age/Filter tab).
Figure 4-2. Active Alarm List
Filters:
• User - Displays information for the specified user only
• NE - Displays information for the Network Element specified
• Ack ID - Displays alarms acknowledged by that user.
• Sev - Displays only alarms of the specified severity level
• Types -Displays only the types selected
April, 2009 4-3
Alarms
•
FAC - Facility
•
EQU - Equipment
•
NE - Network Element
•
MISC Miscellaneous
Column Definitions:
• Select - a select checkbox that allows a user to select a single alarm to execute operations on.
Selection of the checkbox will make the buttons below the list sensitive.
NOTE:
Selection of the “Select” column heading will select all alarms in the list.
• Assert Time - The time that the alarm asserted
• SEV - The severity of the alarm as indicated on the alarm message
• ATYPE - The type of alarm
• User - user to whom the alarm is assigned
• Circuit ID - Circuit identifier
• NE - The network element that contains the alarm
• AID - The physical AID that is in alarm
• ACK - Indicates the 1340 INC user that has acknowledged the alarm
• Level - The level of the alarm as indicated on the alarm message, ex. OC
• SA - Identifies the alarm as service affecting or non-service affecting
• Description - Displays a textual description of the alarm
• Duration - The amount of time the alarm has been active (in Hours:Minutes:Seconds)
4-4 April, 2009
Alarms
Navigation Drop Down List:
• Acknowledge - Allows the user to acknowledge the selected alarm
• Clear - Allows the user to clear the selected alarm
• Comment - Allows the user to enter a comment to be displayed with the selected alarm
• Detail - Displays the Alarm Detail for the selected alarm.
Figure 4-3. Alarm Detail Report
The Alarm Detail Report also displays a navigation drop down list (when the first line is highlighted by placing the mouse over it and selecting the left mouse button).
Navigation (from Alarm Detail Report)
•
Acknowledge - Allows the user to acknowledge the selected alarm
•
Clear - Allows the user to clear the selected alarm
•
Comment - Allows the user to enter a comment to be displayed with the selected alarm
April, 2009 4-5
Alarms
•
CLI Report - Displays the CLI Report for the selected alarm
•
Connect Report - Displays the Connect Report for the selected alarm
•
Equipment View - Displays the Equipment View of the NE the alarm asserted on
•
Maintenance - Displays the Update Maintenance State form. See
for additional information.
•
Retrieve PM - Displays the retrieved PM on the selected facility
•
Ticket - The Trouble Ticket feature allows Integrated Network Controller users to send messages on a specific alarm. The Trouble Ticket form will be pre-populated with the alarm type, severity, alarm time, user, Network Element, service view, AID, circuit ID, CLI code, and the alarm message. The user may then enter comments in the ticket note field. The ticket is sent via selection of the <Submit> button.
Figure 4-4. Trouble Ticket
— Once the e-ticket is sent, all of the data contained in the form is forwarded to the Integrated Network Controller server and saved. An e-mail is then sent to the trouble ticket administrator so they may enter the information into their ticketing system.
4-6 April, 2009
Alarms
— This feature is available to both console and end-users. Console users can request a ticket on any alarm, however, end users may only request tickets for EQU (Equipment) and FAC (Facility) alarms. The location of the ticket data and the e-mail ids of persons who will receive the ticket data is tunable.
•
Trace - Displays the Circuit Trace for the selected facility
• Equipment View - Displays the Equipment View of the NE the alarm was asserted on
• Maintenance - Displays the Update Maintenance State form. See
Maintenance State on page 5-47
for additional information.
• Trace - Displays the Circuit Trace for the selected facility
Buttons:
• Acknowledge - allows the user to acknowledge the selected alarm
• Clear - allows the user to clear the selected alarm
• Comment - allows the user to add a comment to the selected alarm
April, 2009 4-7
Alarms
Alarm List
The Alarm List allows the user to filter alarms so that only specific alarms will be displayed.
Figure 4-5. Alarm List
Filters:
• From/ To - The range of dates and times for which the user would like to see alarm data
• User - Displays information for the selected user only
• NE - Displays information for the Network Element specified
• To NE - Displays alarms between two nodes (NE and To NE)
• Circuit ID - Circuit ID
• AID - Access Identifier
• Status - Alarm status (All, In Alarm, Clear, New)
4-8 April, 2009
Alarms
• Type - Displays only the types selected
•
All - All types of alarms
•
FAC - Facility
•
EQU - Equipment
•
NE - Network Element
•
QoS - Quality of Service
•
Alert
•
MISC - Miscellaneous
•
SYS - System
• Sev - Alarm severity (All, Critical (CR), Major (MJ), Minor (MN), or Other)
• Outage - Minimum outage to search on
• SBNK - Subnetwork ID
• Comm - NE Communication Group that the NE belongs to (Find all alarms on NE x that are in group y)
• Ack Id - Acknowledged by a specific user (show all alarms ack’d by this user)
• Level - Alarm Level (T1, STS1, etc.)
• ATYPE - Alarm type (show only alarms of this type)
NOTE:
The Level and ATYPE are not forced to uppercase since some alarm types (SNMP) can have both upper and lower case.
• Exclude List checkbox - Filter alarms as per the Exclude List (defined in View -> Preferences
-> Alarm Age/Filter tab)
• NE Group - Allows the user to select a specific NE Group to search for
Column Definitions:
• Select - a select checkbox that allows a user to select a single alarm to execute operations on.
Selection of the checkbox will make the buttons below the list sensitive.
NOTE:
Selection of the “Select” column heading will select all alarms in the list.
• Assert Time - Time that the alarm occurred
• Clear Time - Time that the alarm cleared (if appropriate)
• STAT - Status of the alarm (In Alarm, Cleared)
• Type - Category of the alarm (1340 INC type)
April, 2009 4-9
Alarms
• SEV - Severity of the alarm (From NE)
• ATYPE - Condition type as reported by the NE
• SA - Service Affecting (SA) or Not Service Affecting (NSA)
• User - user to whom the alarm is assigned
• Circuit ID - Circuit Identifier (if the port is connected and has a Circuit ID
• NE - Network Element that the alarm is being reported on
• AID - Access Identifier that the alarm is being reported on
• Level - Level of the alarm (T1, STS1, etc.)
• SBNK - Subnetwork Identifier (if the port/aid/facility belongs to a subnetwork)
• ACK - User who has acknowledged the alarm
• Outage - amount of time that the port/aid/facility has been in alarm
• Description - Displays a textual description of the alarm
Navigation Drop Down List:
• Acknowledge - Acknowledge the selected alarm
• Add to Exclude List - Adds the selected alarm to the Exclude List (see View -> Preferences
->Alarm Age/Filter tab). When an alarm is added to the Exclude List from this menu, it will be displayed in the View -> Preferences ->Alarm Age/Filter tab Exclude Filters section.
• Clear - Allows the user to clear the selected alarm
• Comment - Allows the user to enter a comment for the selected alarm (displayed in the
Alarm Detail Form)
• Detail - Displays the Alarm Detail form
• Equipment View - Displays the Equipment View of the NE that the alarm asserted on.
• Maintenance - Navigates to the Update Maintenance State form, allowing the user to change the state of the circuit.
• Maintenance - Navigates to the Update Maintenance State form, allowing the user to change
the state of the selected facility. See
Maintenance State on page 5-47
for additional information.
• Trace - Displays the Facility Trace form for the selected line
Buttons:
• Acknowledge - allows the user to acknowledge the selected alarm
• Clear - allows the user to clear the selected alarm
4-10 April, 2009
Alarms
• Comment - allows the user to add a comment to the selected alarm
April, 2009 4-11
Alarms
Historical
The Historical Alarm Report provides the user with historical information for alarm data. Specifically, it displays the NE, FAC, EQU, QoS, ALERT and MISC alarms by date and type when the Level of the report requested is Summary, or by user and type for a single day, when the Detail report is requested.
Figure 4-6. Historical Alarms
Filters:
• Level - The level of report being requested (summary or detail). Summary allows alarm counts to be sorted by date and type. Detail allows alarm counts to be sorted by user and type for a specific day (see that when Detail is the level chosen, only the From date is sensitive)
• Detail - Only sensitive when Level is set to Detail, this field may be set to User or NE.
• From/To - The range of dates and times for which the user would like to see alarm data.
When the level is detail, only the From value is sensitive.
4-12 April, 2009
Alarms
• User - Displays information for the specified user only
• NE - Displays information for the specified Network Element
• Service View - Displays only the Service View specified
• Records - The type of records to be displayed (all or only non-zero)
• Display - Allows the user to choose Counts or Outage to be displayed. Counts are a total of times the alarm of each type has occurred (been asserted and cleared). Outage is the total number of seconds that the alarm was in 1340 INC.
• Min - Minimum value on which to search i.e. only this value and greater will be displayed
The data will be displayed in both graphical and tabular format. The columns in the table may be sorted by selecting the column heading that the user wants to sort on. The icons located above the table allow the user to display the data in different formats (Line Chart (default), Plot Chart, Area Chart, Bar Chart, and Stacked
Bar Chart.
• Filter Chart - Selection of the Filter Chart icon allows the user to graph only selected columns and re-draw the graph. The graph will be reduced, however the table will still show all data
Figure 4-1. Historical Alarms - Filter Chart
April, 2009 4-13
Alarms
Columns Definitions
The columns displayed in the Historical Alarm Report will vary based upon the search criteria used in the filters section and the Viewed values in the View -> Preferences -> Alarm tab -> Historical Alarm Filters section.
4-14 April, 2009
Alarms
New Alarm List
The New Alarm List allows users to get all alarms that have occurred since the last “New” alarm search was done, thus clearing the flashing icons located in the Alarm Central area of the GUI.
This is equivalent to running the Alarm List report with the Status value set to New. If the user runs this report directly from the Alarm Tab, the Search is done automatically (that is, there is no need to select the
<Search> button).
Figure 4-1. New Alarm List
April, 2009 4-15
Alarms
Notifications
When this feature is enabled on the system, E-mail notification of alarms can be provisioned via alarm noti-
fication profiles. When alarm assert and clear messages are received (and/or acknowledged) by Integrated
Network Controller, an e-mail notification message will be sent to each user that is set up to receive e-mails based upon the specified profiles. A user may set up and manage profiles via the “Manage Notification Profiles” menu item, or view a list all existing profiles via the “View Notification Profiles” menu item.
Figure 4-2. Notification Management
4-16 April, 2009
Alarms
Setup (of Alarm Profiles)
The alarm notification profile setup form will be available to all user and user alias logins. The user can specify a set of filters and destination criteria. Escalation is implicitly provided by the ability to specify multiple e-mail notification profiles
• A login (customer login, customer alias login) can create one or more E-mail Alarm Notification profiles, dependent on permissions. The profile contains specifications and filters for e-mailing an alarm notification.
!
WARNING:
• The ability to create a profile is a user command privilege defined when an alias is created.
There are two command privileges, (one to allow access to “all” profiles, and one to limit access to “own” profiles), and two functions within each privilege (one for query only, and one for execution). For the “all” option, user logins will have access to all profiles under that customer (when that privilege is enabled).
• The user may Add, Update, or Delete a profile (subject to privileges) and may also Load a new profile from an existing profile.
Figure 4-3. Alarm Notification Profile Creation
April, 2009 4-17
Alarms
When a valid Login ID and Profile Name has been entered, the user may select the <Add> button to display the Alarm Notification form.
Figure 4-4. Alarm Notification - Adding a Profile
Login - 1340 INC login (User id)
Profile Name - user defined name for e-mail notification profile. Can be up to 24 characters in length and cannot include spaces or the ‘^’ character. This profile name must be unique to the user. That is, a single user cannot have two profiles with the same name.
4-18 April, 2009
Alarms
Alarm Notification General Tab
The General tab contains the fields and values that will be used to configure the alarm notification profile for a user.
Status
Disable - When set to yes, the profile will be inactive and alarm e-mails will not be sent as defined in the profile. This allows the users to turn off or disable an alarm profile as needed.
Time Period
Time Period - the days of the week and times of the day that e-mail notification will be sent (days/times that the profile is enabled).
NOTE:
The time values are displayed in military time, i.e. 0:00 is 12 AM, 23:59 is 11:59 PM.
Event Type
• Event Type - In an e-mail profile, it is possible to specify two different notification criteria for the alarm:
•
Assert: This type of e-mail profile pertains to the occurrence of the alarm.
•
Acknowledge State: This type of e-mail profile pertains to the acknowledgement status of the alarm.
• Email ID - e-mail address or list of addresses that the alarms will be sent to. If multiple e-mail addresses are listed, they must be delimited by spaces. The maximum number of e-mail addresses allowed is limited by the width of the editable field (up to 255 characters). The use of the ‘^’ is prohibited in allowable e-mail addresses.
FAC: Facility alarms
EQU: Equipment alarms
• Process Alarm: Allows the user to select yes or no from the drop down list to decide on processing of each alarm type.
• Filter Alarm: Allows the user to select yes or no from the drop down list to dictate filtering for each alarm type. If the user selects yes, the Email Alarm Filters are used to specify specific filtering
• Age Alarm: When defining an Assert profile this value allows the user to set the time (in seconds) that the alarm is active prior to sending a notification e-mail. In the case of an
Acknowledge State profile, an e-mail notification is sent if the alarm is not acknowledged within a specified time period (as indicated with the age alarm drop down list), and an e-mail notification is sent when the alarm is acknowledged or cleared, whichever occurs first.
April, 2009 4-19
Alarms
NOTE:
The user must choose to have either FAC alarms, EQU alarms, or both, processed.
Email Alarm Filters:
If the user chooses to filter either the FAC or EQU alarms (or both by selecting YES from the “Filter Alarm” drop down list under the associated type), they may then select any combination of filters for a profile. The filters include:
• Service Affecting - Service Affecting (SA), Non-Service Affecting (NSA)
• Alarm Severity - Critical, Major, Minor, Other
• Alarm Level - OC*, STS*, VT*, T*, EQPT*
• Level Filter - allows users to enter alarm levels that will be processed by the alarm notification feature.
For example, a user may set SA to YES, Critical to YES and the OC* value to YES to see all Critical, Service Affecting, OC3, OC12, OC48, and OC192 level alarms. Additionally, if the user entered T3 in the
Level Filter box, they would see all T3 alarms that are critical and service affecting in the system.
Buttons:
• Add - Add a newly defined profile to the database
• Update - Apply changes that have been made to a profile
• Delete - Delete a profile from the database
• Refresh - Update the form with the most current data
• Clear - Clear the fields of the Alarm Notification form in order to create a new profile.
• Test - When selected, a test e-mail is sent to the e-mail destination(s) in the current profile.
• Close - Close the form
Miscellaneous
• There is a system based, tunable throttling mechanism available. If more than N e-mails are sent within T time for a user, then e-mails will be stopped for that user until they fall back below threshold N in time T. The log will record the failed e-mails, and a system health alert will be raised. See the system administrator for access to this feature.
4-20 April, 2009
Alarms
Alarm Notification NE Tab
The NE tab contains a list of NEs that are to be included in (or excluded from) the defined profile. For ease of editing, the user has the option to select all NEs (via the double arrow). However, at least one NE must be selected for a profile to be valid. When editing a profile owned by another alias, any NEs that are not available to that alias, as defined by the Alias Management form, are protected (listed in the Protect column) and may not be selected. If the alias that owns the profile has NEs selected that are not available to the alias editing the profile, they will not be visible, and will not be modified in the database upon update.
Figure 4-5. Alarm Notification - NE Tab
April, 2009 4-21
Alarms
Alarm Notification Users Tab
The Users tab contains a list of users that are to be included in (or excluded from) the defined profile. For ease of editing, the user has the option to select all users (via the double arrow). However, at least one user must be selected for a profile to be valid. When editing a profile any users that are not available to that alias, as defined by the Alias Management form, are protected (listed in the Protect column) and may not be selected. If the alias that owns the profile has users selected that are not available to the alias editing the profile, they will not be visible, and will not be modified in the database upon update.
Figure 4-6. Alarm Notification - Users Tab
4-22 April, 2009
Alarms
Alarm Notification Report
This report is a list of the existing e-mail alarm notification profiles. The scope of the report is determined by the command privileges (only self, or all profiles). The report lists the profile name, and associated information for that profile. It is possible to select profiles from the report.
Figure 4-7. Alarm Notification Report
Filters:
• User - Display a specific User’s profiles
• Login ID - Display a specific Login’s profiles.
• Profile Name - Display a specific profile, or any profile with this string in the profile name.
Columns:
• Login - Integrated Network Controller ID associated with the profile
• Profile Name - User defined name of the e-mail notification profile
April, 2009 4-23
Alarms
• Owner - A system defined user
• Status - Indicates whether the profile is enabled or disabled
• Event Type - indicates whether this is an Assert or Acknowledge profile.
• Email ID (s) - all e-mail addresses that will be notified when an alarm meeting the profile criteria is met.
Navigation Drop Down List:
• Load Profile - Displays the Alarm Notification form in “add” mode with the data for the selected profile. This allows the user to copy a profile to another Login ID and/or profile name.
• Test Email - sends a test message to the e-mail addresses specified in the profile.
4-24 April, 2009
Alarms
Problem Alarms
The Problem Alarms form is a historical report showing alarms that have cleared on a chosen day and the statistics associated with each alarm while it was active for each alarm category.
Figure 4-8. Problem Alarm Report
Filters
• Date- The date for which the user would like to see alarm data
NOTE:
When the “More Options” value is chosen, the user may enter a range of dates.
• User - Displays problem alarms for the specified user only
• NE - The Network Element for which the user would like to see alarm data
• Service View - Displays only the Service View specified
• Type - Display only the selected type of alarms (Default is Facility)
April, 2009 4-25
Alarms
• Count - Display only the ports whose total alarm count is at least this number
• Outage - Displays the alarms whose total outage is at least this number of seconds
• Lines - Display only this number of lines
Column Definitions:
When Type = Facility:
• Date - The date that the alarm cleared
• User - The user partition to which the circuit in alarm was assigned
• Circuit ID - The circuit identifier
• NE - Network Element that the alarm was reported on
• Service View - Facility that the alarm was reported on
• Total - Total number of alarms in all categories for a particular circuit
Columns that are listed after the Total column will vary based upon selections made in the View -> Preferences tab on the Alarm tab -> Historical Alarm Filters section.
When Type = NE:
• Date - The date that the alarm cleared
• NE - Network Element that the alarm was reported on
• Count - Number of time the alarm has occurred
• Outage - Cumulative time between the assert of the alarm and the clear of the alarm (in hours:minutes:seconds)
When Type = NON-Facility:
• Date - The date that the alarm cleared
• NE - Typically SYS for System Health alarms
• AID - Access Identifier - for system health alarms, this is typically a process that has had a failure
• Count - Number of time the alarm has occurred
• Outage - Cumulative time between the assert of the alarm and the clear of the alarm (in hours:minutes:seconds)
Navigation Drop Down List:
• Alarm List - Displays the Alarm List for the selected port
• Historical - Displays the Historical Alarm Report for the selected NE and Service View
4-26 April, 2009
Alarms
• Trace - Displays the selected circuit on the Facility Trace form
April, 2009 4-27
Alarms
4-28 April, 2009
Configure
Chapter Contents
•
•
•
•
Change TC/Line Code on page 5-30
•
•
•
•
Maintenance State on page 5-47
•
•
•
Eastern Research DNX, Premisys IMACS, Generic SNMP Devices on page 5-87
•
•
•
•
Scheduled Commands on page 5-97
•
Subpartition Management on page 5-101
April, 2009 5-1
Configure
•
•
5-2 April, 2009
Configure
Configure Tab
The Configure Tab allows the users access to the various configuration functions available within the Software Integrated Network Controller system.
Figure 5-1. Configure Tab
April, 2009 5-3
Configure
Alias
The addition, deletion, and modification of aliases is performed on the Alias Management Form.
In general, aliases are created when multiple users are accessing the Integrated Network Controller system.
The following are benefits of creating an alias for each individual:
• Separate login and password
• Separate audit trail of commands performed
• Ability to restrict the use of certain commands
• Ability to restrict access to certain network elements
A user alias:
• can perform all user commands or any defined subset
• can access only the user database it is an alias of
• can access network elements containing user assignments or any defined subset
5-4 April, 2009
Configure
Alias Tab
The Alias Tab is used to define, modify, and delete aliases.
Figure 5-2. Alias Tab
The form contains a list of existing aliases, and the following fields:
•
User ID - the Integrated Network Controller user that the alias is associated with.
For a console alias, this would be “console”, for a user alias this would be the created user database name.
NOTE:
This field is only displayed to console logins in CNM mode.
•
Alias ID - the actual alias ID. This is the login ID for the alias.
April, 2009 5-5
Configure
•
Template checkbox - Used to define an alias as a template. If an alias that has been defined as a template is selected from the existing alias list, the Template checkbox will be checked.
NOTE:
ALIAS ID, ALIAS NAME and ALIAS PASSWORD RULES: n n n n
The Alias ID and Alias Password must be at least 6 characters in length, but cannot exceed 8 characters in length.
The first character must be alpha, and the remainder can be made up of any combination of alphanumeric characters and the special characters
“_” (underscore), “!” (exclamation), “.”(period), and “$” (dollar sign).
Use of spaces, caret (“^”), at (“@”), pound (“#”), colon “:”, and the ampersand (“&”) is prohibited.
Passwords cannot be repeated. That is, a previously used password cannot be re-used for the same alias.
•
Alias Name - this field allows the user to define a secondary name by which the alias would be known (i.e. a more familiar name) and can be up to 25 characters in length.
•
Template ID - allows the user to select a previously defined template alias from which to inherit command and NE access privilege. If selected, then the Inherit from Template values will be sensitive. Use of templates is particularly useful when managing many aliases with the same set of privileges. n n
If an alias that has been defined as a template is selected from the existing alias list, the Template checkbox will be checked, and the Template ID field will be insensitive (because a Template cannot have a Template, it can only be a Template).
Creation and modification of alias templates is driven by command privilege. On the User Commands tab, the Execute command “add/modify system aliases” must be enabled in order to create and change templates.
When this command is disabled, the Template checkbox will not be displayed on the Alias Management form and the user will not have access to any defined templates. Aliases can then be created but templates cannot . Additionally, if the Execute command “assign a list of commands to a user alias” is disabled, the Alias Managment form will not be available under the Configure tab.
NOTE:
Changes made to a template id (users, command privilege or NE access) will not be seen by the template user until after a logout-login sequence.
•
Alias Password/Verify Password - the alias password.
5-6 April, 2009
Configure
•
Partition - Used in conjunction with the ATM/FR and Metro Ethernet features of the Integrated Network Controller. This allows the user to assign a specific partition to a defined alias. Refer to the Integrated Network Controller ATM/FR Supplement or the Integrated Network Controller Metro Ethernet Supplement for a detailed description of this field.
•
Email - This is the e-mail address to which the NE notifications will be sent.
•
Comment - Allows the user to put in any free form text (up to 80 characters) to be associated with the defined alias (i.e. contact information for the alias)
•
Receive ATM/FR SLA Reports - Selection of this button is used in conjunction with the ATM/FR capabilities. Refer to the Integrated Network Controller ATM/
FR Supplement for a detailed description of this function.
•
Receive Metro Ethernet SLA Reports - Selection of this button is used in conjunction with the Metro Ethernet capabilities. Refer to the Integrated Network
Controller Metro Ethernet Supplement for a detailed description of this function.
•
Receive NE Notifications - Selection of this button allows the defined alias to receive notifications of maintenance activity for NEs on which they have facilities assigned. The actual notification will be sent via the NE Notification form.
This feature is available only in CNM mode.
See “NE Notification” on page 91.
•
End Session on Idle Timer - If selected, this alias will be logged out after a pre-defined number of minutes. Refer to the Integrated Network Controller
Application Installation Guide for a detailed description of the set up of the file related to this feature.
•
NE Cut Thru Permission - Selection of these buttons will give users access to specific TL1 commands in the NE Cut Thru form (See Chapter 3 - Administration). Refer to the Integrated Network Controller Application Installation Guide for a detailed description of the set up of the files related to this feature.
NOTE:
The selection of the NE Cut Thru choice is mutually exclusive. That is, the user can select only one of the choices (Admin, General, Maintenance, or Reports).
• Inherit from Template (Preferences, Users, Commands, NEs) - Allows users to inherit specific settings from a previously defined template (exisiting Template alias) listed in the
Template ID field. This establishes a relationship between the defined alias and the template such that if changes are made to the template, those changes are inherited by the alias. It should be noted that when the Template ID is cleared (no longer applied) to an alias, the alias will revert to the permissions defined on the alias form (it’s own permissions).
NOTE:
These choices are only available (sensitive) if a template is used, and the selections made from the “Inherit from Template” choices will dictate the viewable tabs and menu items as well as the ability to view preferences as the defined alias (i.e. if the NEs tab is unse-
April, 2009 5-7
Configure
lected, then the NEs tab will be viewable, allowing the user to select NE’s for that alias, as the NEs are not being inherited from the specified template.).
• Include in Load (Alias, Users, Commands, NEs) - Allows the user to copy settings for one alias from another by “loading” information into the alias form.
•
Enter information for alias being defined
•
Choose an existing alias from the choice box whose attributes are to be copied
•
Select Users, Commands or NEs as desired
•
Select the <Load> button
5-8 April, 2009
Configure
Users Tab
The Users tab is used to define the set of user partitions viewable by a console alias.
Figure 5-3. Users Tab
This tab is only displayed when 1340 INC is used in CNM mode and is only applicable to aliases of console.
April, 2009 5-9
Configure
User Commands Tab
The User Commands tab is used to define the set of user commands that an alias may perform. The list shows all Integrated Network Controller user commands broken into two categories:
• Query Commands - commands that show data or report information
• Execute Commands - commands that act upon or change data
Figure 5-4. User Commands Tab
5-10 April, 2009
Configure
The following is a list of all the possible selections on the User Commands Tab:
Note that some functions are only available in the Integrated Network Controller Command Line (CL) interface.
Query:
• audit NMS database vs. NE database (CL only function)
• basic atm/frame historical pm reports
• basic metro ethernet historical pm reports
• enhanced real-time facility/NMS monitoring (CL only function)
• establish a loopback for a set of facilities
• ethernet QOS
• ethernet service
• page text files (CL only function)
• premium atm/frame historical pm reports
• read mail sent to you (CL only function)
• release a loopback for a set of facilities
• retrieve CLI CODE (circuit ID) information
• retrieve CLI CODE (circuit ID) information for SRM/MJU/DMB entities
• retrieve alarm maintenance state information
• retrieve atm/fr real time PM
• retrieve circuit trace information
• retrieve command execution information
• retrieve facility/user node associations (CL only function)
• retrieve list of Threshold Crossing Alarms
• retrieve list of User aliases
• retrieve list of alarms
• retrieve list of allocated facility/SRM/MJU/DMB entities (CL only function)
• retrieve list of channels under evasive testing (CL only function)
• retrieve list of commands available to a user alias
• retrieve list of cross-connected DMBs
• retrieve list of cross-connected SRMs/MJUs
• retrieve list of cross-connected facilities
• retrieve list of defined macros
April, 2009 5-11
Configure
• retrieve list of established facilities
• retrieve list of linked inter-NE facilities
• retrieve list of protected circuits
• retrieve list of ring cross-connected facilities
• retrieve list of scheduled PM channels
• retrieve list of scheduled commands
• retrieve list of user partitions (CL only function)
• retrieve list of user subpartitions (CL only function)
• retrieve list of virtual interconnect facilities (CL only function)
• retrieve metro ethernet real time pm
• retrieve performance alarms/data from NE
• retrieve ring utilization reports
• retrieve scheduled PM data
• retrieve Problem Alarm report
• retrieve Problem PM report
• retrieve trunk conditioning code information
• send a message to the console administrator
• view alarm email notification profiles
• view alarm email notification profiles for all logins
• virtual switched network (VSN)
Execute:
• add/delete list of scheduled PM channels
• add/delete/modify user partitions (CL only function)
• add/delete/modify user subpartitions
• add/modify system aliases
• add/update remote interfaces
• allocate atm/frame resources
• allocate metro ethernet resources
• assign a list of user commands to an alias
• cancel a scheduled command
• change trunk conditioning information
• connect DMB circuits
5-12 April, 2009
Configure
• connect SRM/MJU circuits
• connect facility circuits
• create a define macro
• disconnect DMB circuits
• disconnect SRM/MJU circuits
• disconnect facility circuits
• disestablish SRM DSOBs
• establish SRM DSOBs
• ethernet QOS
• ethernet service
• make NMS match the NE for a set of facilities
• modify the facility CLI CODE information around a ring
• move SRM DSOB or MJU master leg
• provide a re-route command to protect a circuit
• provide evasive testing of circuits
• remove a defined macro
• rename a service view
• restricted interface to Network Elements (CL only function)
• ring connect facility circuits
• ring disconnect facility circuits
• schedule commands for timed execution
• send email notifications for alarms
• send email notifications for alarms for all logins
• send messages to other users
• send trouble ticket information
• set facility/user node associations
• take down evasive test setup
• tie facility to remote system
• unprotect facilities under protection
• virtual switched network (VSN)
April, 2009 5-13
Configure
Console Commands Tab
The Console Commands tab is used to define the set of console commands that an alias may perform. The list shows all Integrated Network Controller console commands broken into two categories:
• Query Commands - commands that show data or report information
• Execute Commands - commands that act upon or change data
Figure 5-5. Console Commands Tab
5-14 April, 2009
Configure
The following is a list of all the possible selections on the Console Commands Tab:
Query:
• display system control messages
• retrieve SRM/MJU/DMB statistics for NMS
• retrieve current connectivity information for NEs
• retrieve database statistics from NMS
• retrieve facility information from NMS database
• retrieve facility statistics from NMS
• retrieve list of IDLs in NMS
• retrieve list of SLC facilities in NMS
• retrieve list of allocated DMBs for a user
• retrieve list of allocated SRMs/MJUs for a user
• retrieve list of allocated facilities for a user
• retrieve list of command denials and alarms
• retrieve list of equipped network elements
• retrieve list of logged in users
• retrieve list of timezones assigned to users
• retrieve list of users assigned to a console alias
• retrieve list of users in NMS
• retrieve per user allocation information
• retrieve per-NE information
Execute:
• add/del/update network elements
• add/modify a user in NMS
• allocate DMB resources to a user
• allocate SRM/MJU resources to a user
• allocate facility resources to a user
• allocate system resources to a user
• allow console user to execute as a user
• assign a list of users to a console alias
• assign/modify/delete SLC facilities in NMS
April, 2009 5-15
Configure
• backup network element database
• change current network element release
• combine one NE with another
• create IDLs in NMS by associating channels in NMS
• delete a user from NMS
• download a network element release
• equipment provisioning and protection switching
• force NE DB update to remote MUXes
• make the NE match NMS for a set of circuits
• manage network element login and passwords
• manual alarm clear
• modify SRM/MJU/DMB CLI CODE information
• modify facility CLI CODE information
• modify user information
• perform on-line backup of NMS databases
• provide control of protected links
• release DMB resources from a user
• release SRM/MJU resources from a user
• remove IDL designations from channels in NMS
• remove an alias from NMS
• restore network element database
• send/receive NE commands in native NE-mode
• set alarm maintenance states
• set/modify the timezone for a user
• support for ethernet functions
• sync up with atm provisioning system
• sync up with metro ethernet provisioning system
• turn on-line billing data collection on/off
5-16 April, 2009
Configure
NEs Tab
The NE Tab is used to define the set of network elements an alias may access. It should be noted that if all
NEs are in the Available to Alias category, any ensuing NEs added, will automatically be viewable on the user’s GUI.
Figure 5-6. NEs Tab
Select Boxes:
• Move Options
•
Entire subnetwork - places all nodes in the subnetwork into the selected list
•
Entire NE group - places all nodes in the nodes defined NE Group into the selected list
•
Entire Communications group - places all nodes in the defined Comm group into the selected list
April, 2009 5-17
Configure
Alias Management Functions
The following are step-by-step instructions for performing functions on the Alias Management Form. Begin each function on the Alias Management Form - Alias Tab. To be able to create a user alias, the user must be a part of your currently selected “User Group”.
Creating an Alias:
1.
Enter the User for which an alias will be created by selecting from the User List or by typing the User ID in the User ID field.
2.
Enter the Alias ID to be created in the Alias ID field
3.
Enter an alias name (a secondary name that the alias will be known as)
4.
Enter a password for the new alias ID in the Alias Password Field
5.
Re-enter the same password in the Verify Password Field
6.
If creating a console alias, go to the Users Tab to define the allowed users
7.
Go to the Commands Tabs as appropriate to define the allowed commands set
8.
Go to the NE Tab to select the allowed network elements
9.
Click on the <Add> button
Modifying an Existing Alias:
1.
Highlight the alias to be modified, in the list on the Alias Tab
2.
Click on the <Select> button
3.
If modifying a console alias, go to the Users Tab to make updates to allowed users if desired
4.
Go to the Commands Tabs to make updates to the allowed commands if desired
5.
Go to the NE Tab to make updates to the allowed network elements if desired
6.
Click on the <Update> button
Deleting an Alias:
1.
Highlight the alias to be deleted, in the list on the Alias Tab
2.
Click on the <Select> button
3.
Click on the <Delete> button
5-18 April, 2009
Configure
Copying an existing Alias’ profile to another existing alias:
Here, an existing alias’ permissions are being copied to another already existing alias. For clarity, the alias with the desired permissions will be referred to here as the “source alias”, and the alias that is being updated will be referred to as the “target alias”.
1.
Highlight the “target alias” in the list and select the <Select> button
2.
Select the check boxes corresponding to the permissions you wish to copy (Users, Commands, NEs) from the “source alias”
3.
Highlight the “source alias” in the list and select the <Load> button
4.
A message will be displayed that the load of the “source alias” is complete
5.
Select the <Update> button. The “target alias” is now updated with the selected permissions of the “source alias”
Copying an existing Alias’ profile to a new alias:
Here, a new alias is being created with the permissions of an existing alias. For clarity, the alias with the desired permissions will be referred to here as the “source alias”, and the alias that is being created will be referred to as the “new alias”. When managing many aliases, or aliases with complex permissions, it is quicker to create one alias as a “source alias” and then perform the following steps to create new aliases with the same permissions.
1.
Enter the User ID and the Alias ID for the “new alias” being created
2.
Enter the password for the “new alias”
3.
Select the check boxes corresponding to the permissions you wish to copy (Users, Commands, NEs) from the “source alias”
4.
Highlight the “source alias” in the list and click <Load>
5.
Select the <Add> button. The “new alias” is now created with the same permissions as the “source alias”.
Use of the Template ID field for multiple aliases:
In some cases, there will be more than one alias for the same user, where each alias will have identical command and access privilege. In those cases, it may be more desirable to use the Template ID field to copy existing command and NE access privilege.
1.
Enter the User for which an alias will be created by selecting from the User List or by typing the User ID in the User ID field.
2.
Enter the Alias ID to be created in the Alias ID field
3.
Enter an alias name (a secondary name that the alias will be known as)
4.
Enter the alias name to be copied (the template) in the Template ID field
5.
Enter a password for the new alias ID in the Alias Password Field
April, 2009 5-19
Configure
6.
Re-enter the same password in the Verify Password Field
7.
Click on the <Add> button
5-20 April, 2009
Configure
Assign/Release
The Assign/Release Management feature of Integrated Network Controller allows the user to assign and release facilities on a per user basis and per facility basis.
Figure 5-7. Assign/Release Management
April, 2009 5-21
Configure
Assign
The Assign form allows users to assign facilities to a user partition.
Figure 5-8. Assign
Fields:
• NE - The NE value may be populated in one of two ways:
•
The NE drop down list. Once an NE is selected, additional fields will be populated with information retrieved from the Integrated Network Controller database
•
Entry of the NE ID into the text field accompanying the <Load NE> button. Once the button is selected, additional fields will be populated with information retrieved from the Integrated Network Controller database
The user must then select the AID and TC/Line Code of the facility they wish to assign. These fields are
mandatory and must be populated prior to selecting the <Submit> button.
5-22 April, 2009
Configure
• Service View Prefix - Displays the Service view prefix associated with facilities assigned to this user on this NE.
• Surveillance Only - used to set, or un-set, the surveillance state of a particular facility. The choices are Default (assume the default setting of the NE), Yes (set the facility to surveil-
(Default Assignments to ‘Surveillance Only’) for additional information.
• Service View State - The alarm state of the NE.
• Ring Assignment - Value may be Normal, East, or West
• Options - Options are used in cases where there may be multiple versions of a pack type, i.e. a single port OC3 card vs. a 4 port OC3 card. Indicating the specific pack type allows
1340 INC to execute the facility assignment correctly. These indicators (G, Q, P) distinguish the different pack types, but are not related to the connection rate.
•
Grouped - This option is used on AIDs that show a “G” as the first character in the TC Line Code format under AID Help.
•
Quad - This option is used on AIDs that show a “Q” as the first character in the
TC Line Code format under AID Help
•
Pass-Thru - This option is used on OC3 Plus NEs to indicate that they are
Passthru facilities. In this case, the highspeed trunk conditioning will be preceded by a “P” in the TC Line Code format under AID Help
•
non PM - used to indicate facilities on which performance monitoring data will not be collected.
• Service View - not mandatory, but if populated, the value must be a valid service view.
• CLI - free form text input box
• Comment - free form text input box.
Buttons:
• Submit - Send the assign request to the Integrated Network Controller database
• AID Help - Displays the valid AIDs and the TC/Line codes that they may be assigned with for this NE.
• Update DNO - executes a DNO operation on the selected NE
• Clear: Clear all fields and selected options
April, 2009 5-23
Configure
Release
The Release form allows users to release or “unassign” facilities from a specific user.
Figure 5-9. Release
Fields:
• User - user whose facility is going to released
• Service View - the service view name for the assigned facility
• Override - if selected, any ties or connections associated with the entity being released, will be removed from the 1340 INC database
Buttons:
• Submit: Send the release request to the Integrated Network Controller database
• Clear: Clear all fields and selected options
5-24 April, 2009
Configure
Populate
Using the Populate tab allows the user to assign (populate) the 1340 INC database very quickly by selecting one, some, or all available (AVAIL) facilities on the form. Likewise, the Populate Tab allows the user to release facilities from the 1340 INC database very quickly by selecting one, some, or all previously assigned
(USED) facilities on the form. The facilities listed on the form are generated by selecting an NE followed by selecting the <Refresh> button or by selecting an NE followed by selecting the <Update DNO> button and then selecting the <Refresh> button. Once an NE has been selected from the drop-down list, the data fields at the top of the form will be populated with the associated data.
Method one listed above, selecting the <Refresh> button, sends a query to the 1340 INC DNO data base to see if a DNO has ever been performed on the selected network element. If the DNO has never been performed then the ‘Last DNO’ field on the form will state “*** No DNO Data ***”. Next, the query is directed to the 1340 INC facility database to see which facilities are already assigned to the selected NE and to which user partition.
DNO (Dynamic Network Operation) refers to the operation of sending several queries to the NE in order to obtain information related to circuit pack type, active/standby status, CLEI codes, etc. Once obtained, this information is stored in a card data base. The DNO query is only sent to SONET network elements.
The list of assigned facilities which populate the form will be marked with ‘USED’ in the Assign column.
All other unassigned facilities will be marked as AVAIL in the Release column. Placing a check mark(s) in the Assign column next to any unassigned facility(s) will allow the user to assign the selected facility to any desired user partition. They may also enter a circuit ID and comment. Clicking the right mouse on any unassigned facility will produce a pop-up list of valid facility types (TC Codes) for the selected network element.
April, 2009 5-25
Configure
Figure 5-10. Populate - pre-NE selection
5-26 April, 2009
Configure
Figure 5-11. Populate - post-NE selection and refresh
Fields:
• NE - ID of the network element that the assignment/release is being made in. The NE value may be populated in one of two ways:
•
The NE drop down list. Once an NE is selected, additional fields will be populated with information retrieved from the Integrated Network Controller database
•
Entry of the NE ID into the text field accompanying the <Load NE> button. Once the button is selected, additional fields will be populated with information retrieved from the Integrated Network Controller database
• User - the user that the assignment/release is being executed for
• Last DNO - the date of the most recent DNO performed on the network element
• NE CLI - the CLI of the network element
• NE Type - the equipment type of the network element
• NE Comment - comment information associated with the network element
April, 2009 5-27
Configure
• Service View Prefix - string that is used as a prefix when generating service view names
• Surveillance Only - Surveillance Only - used to set, or un-set, the surveillance state of a particular facility. The choices are Default (assume the default setting of the NE), Yes (set the facility to surveillance only) or No. See
Assignments to ‘Surveillance Only’) for additional information.
• Service View State - the alarm state of the NE (Clear, Maint, Block)
• Activation - the date that the network element was changed from the Clear state, if applicable
• Expiration - the date that the network element will be returned to the Clear state, if applicable
• High Speed 1 - if checked, high speed, side 1, facility entries will be generated in the table upon selection of the <Refresh> button
• High Speed 2 - if checked, high speed, side 2, facility entries will be generated in the table upon selection of the <Refresh> button
• Low Speed - if checked, low speed facility entries will be generated in the table upon selection of the <Refresh> button
• Slot - if checked, displays a drop-down list of slots in the selected NE that may be chosen.
Facility entries for that slot will be displayed in the table upon selection of the <Refresh> button.
NOTE:
This item will be displayed for a set of network elements managed by 1340 INC that are considered multi-ring. These elements have the flexibility to provision most any interface card in any interface slot, and to designate multiple pairs of optical ports as UPSR,
BLSR or 1+1 optical pairs.
Column Definitions:
• Assign - check marks are entered by clicking in the field to indicate that the selection should be assigned to the database. If already assigned, this field will contain the word, Used.
• Release - checkmarks are entered by clicking in the field to indicate that the selection should be released from the database. If the selection is available for assignment, this field will contain the word, Avail
• AID - the Access Identifier or physical representation of the entity being assigned
• VCM - virtual concatenation member. Used on certain network element types to indicate the member number of the virtual concatenation. Primarily used in Ethernet Service applications.
• User - the user database the assignment is being made to
• Service View - the service view name for the assignment
• TC - the trunk conditioning code for the assignment
5-28 April, 2009
Configure
• Grp - Group - used on AIDs that show a “G” as the first character in the TC Line Code format under AID Help. This field is displayed to distinguish different versions of similar circuit packs.
• Quad - used to distinguish different versions of similar circuit packs (e.g. OC3 card vs. a 4 port OC3 card)
• Pass-Thru - This option is used on OC3 Plus NEs to indicate that they are Passthru facilities.
In this case, the highspeed trunk conditioning will be preceded by a “P” in the TC Line
Code format under AID Help
• non-PM - used to indicate facilities on which performance monitoring data will not be collected.
NOTE:
The Grp, Quad, and Passthru columns are used in cases where there may be multiple versions of a pack type, i.e. a single port OC3 card vs. a 4 port OC3 card. Indicating the specific pack type allows 1340 INC to execute the facility assignment correctly. These indicators (G, Q, P) distinguish the different pack types, but are not related to the connection rate.
• Ring - This field applies only to certain NEs and may be set to NONE, UPSR, or BLSR. If
UPSR or BLSR is selected, additional values may be set to either East or West (to indicate direction) and 1-99 (to indicate ring number). These fields are provided in order to more easily identify the facilities which belong to multiple rings subtending off of a main ring.
• CLI - the CLI or circuit ID for the assignment
• Comment - comment field for additional information about the assignment
Buttons:
• Refresh - Re-displays the form showing the existing facility assignments, if any
• Send Assign - Submits the assignment commands to the 1340 INC host
• Send Release - Submits the release commands to the 1340 INC host
• Update DNO - performs the DNO function for the selected NE
• Clear: Clear all fields and selected options
April, 2009 5-29
Configure
Change TC/Line Code
The WEB GUI allows the user to change line codes and framing formats on any circuit which allows such changes. For example: a DS1 with a line code and framing format of SF AMI (referred to in 1340 INC as
DS1) could be changed to ESF B8ZS (referred to in 1340 INC as DS1E-B8ZS). Once all the fields have been populated, the change is executed via selection of the <Submit> button.
NOTE:
Changing line codes and framing formats must be performed on all segments of an end-to-end circuit. The customer equipment must also be configured to support the requested changes before the circuit will work properly.
For the Tellabs 5500 3/1 DCS, the Change TC/Line Code function provides growth, degrowth, and in-servicing of facilities. The Line Code Parameters and Framing Parameters drop down lists are used to support this functionality.
Figure 5-12. Change TC/Line Code
5-30 April, 2009
Configure
Circuits
The Circuits form allows users to connect or disconnect circuits that are managed by the Integrated Network
Controller system.
Figure 5-13. Circuit Connection Form
Connection Request:
• Type - type of circuit being connected
•
Single NE - used for making a single cross connect within one network element.
In the case of a ring connect, this will include low-speed facilities only. In the case of an A-Z type connection, this will include low-speed and high-speed facilities.
April, 2009 5-31
Configure
•
A-Z Connection - option that establishes an end-to-end circuit across a “mesh” network consisting of DCS, ADM, and DWDM network elements. After the user selects the desired A and Z service-view names, Integrated Network Controller automatically selects the circuit path and establishes all necessary cross connections.
NOTE:
If A-Z is selected, the Use Exclude List checkbox will become sensitive. If this option is selected, the <Set Exclude List> button will become sensitive. Selection of this button opens up a form allowing the user to choose NEs that they do not want to be used as part of circuit provisioning in the A-Z path.
Figure 5-14. Exclude List
•
Subnetwork - allows the user to select a facility in two different nodes and a path between them. 1340 INC will put up all the necessary connections in all the nodes at one time.
NOTE:
Available NEs for each connection will be based on the Type selected. For example, if a
Subnetwork Connection (also known as a Ring Connect) is chosen, only those NE’s that
5-32 April, 2009
Configure are configured for Subnetwork Connections will be in the NE drop down list. Once a
FROM NE is chosen, only NEs that are allowable TO NEs will be in the TO drop down list.
• Level - The transmission rate at which the circuit will be connected.
NOTE:
When the NE is selected, the Level drop down box will only list choices that are available to that NE (i.e. An OC12 node will not have OC48 listed as a level choice).
• Range / Use Range - Selection of the Use Range checkbox will make the Range drop down list become sensitive and will indicate that the connection will use more than one facility of the chosen level (i.e. 8 VT1s, 4 STS1’s, etc.).
• Create Unique Circuit ID’s for Range (Append ‘- # #’) - When connecting ranges, the user can choose an incremental two digits at the end of the id, so that all circuits in the range will have the same circuit prefix, but will be differentiated by the appended digits (i.e. rgwtest-01, rgwtest-02, rgwtest03, etc.)
• TC/Trouble Code - available only for DS0 level connections. These trunk conditioning/trouble codes are set to one of the values in the drop down list and are used to define the signalling (TC), and the value to be sent on a line in case of signal failure (Trouble Code).
• State - allows a “state” to be associated with every cross-connect. The date and time that a cross-connect entered each state is also stored. If these cross-connect states are used, a connection must go through each state. For example, a cross-connect can’t be entered with the Activate state without being in the Pending state first. However, it is possible to send the connection with more than one state (Pending/Activate). The choices for the cross-connect state are as follows:
•
Pending - cross-connect is in the Integrated Network Controller database but is not in the NE. This is a way of “reserving” the facilities in the database before they are ready for actual connection.
•
Activate - cross-connect is in the Integrated Network Controller database and in the NE. When the state is changed from “Pending” to “Activate” the appropriate connect command is issued to the network element.
•
InEffect - cross-connect is in the Integrated Network Controller database and in the NE. This state could be used to indicate to Integrated Network Controller users that the connection is up and working and has been turned over to the user.
Changing the state from “Activate” to “InEffect” does not alter the status of the connection in the network element.
• User - a drop down list that displays users that are in the currently selected “User Group”
From Information:
• NE - the originating endpoint of the circuit, or the “from” side of a cross-connect (required).
This drop down list displays the network elements that contain assignments for the selected user.
April, 2009 5-33
Configure
• Ring/STS # - allows the user to select which currently configured ring and which STS the connection will be put up on. These choices are only available for SubNetwork (Ring) connects.
• Service View - the Service View of the facility being connected.
• Unprotected - allows the user to choose to have ports selected in the Service View field unprotected. This is typically used in UPSR ring to ring configurations.
• Path Service View - List of available paths for the circuit connection. This option is used when the Path Selection is set to Manual
• Path Protection - allows the user to have paths selected in the Path Service View field unprotected. This is typically used in UPSR ring to ring configurations.
• Path Selection - Allows the user to select a path manually or automatically
• Path Criteria - option that indicates that Integrated Network Controller should automatically pick the circuit path for the user based on one of the following options (these options become sensitive when the Path Selection is set to Automatic):
•
Shortest - select the shortest route
•
Capacity - select the route with the most remaining capacity
•
HS1 - select an available route going in the high speed 1 (east) direction
•
HS2 - select an available route going in the high speed 2 (west) direction
NOTE:
PATH - the route that a circuit travels from the originating endpoint to the terminating endpoint. This field is used for connections that traverse multiple nodes.
To Information:
• NE - the terminating endpoint of the circuit, or the “to” side of a cross-connect (required).
This drop down list displays the network elements that contain assignments for the selected user.
• Service View - the Service View of the facility being connected
• Virtual - This icon only appears if virtual facilities have been assigned. This “wizard” will display a list of available “Virtual” facilities to be connected
Figure 5-15. Virtual icon
5-34 April, 2009
Configure
Connection Information:
• Options -
•
DB Only - indicates that the user desires to perform the connect or disconnect in the Integrated Network Controller database only. No commands will be sent to network elements.
•
Override - indicates that the user desires to override (or disconnect) any existing connections to perform the requested function.
•
One Sided - indicates that the user desires to have Integrated Network Controller connect the selected low-speed facility to the selected high-speed facility only.
The low-speed will not be connected in both high speed directions. This only applies to network elements that allow one-sided connections.
•
Unswitched - option that creates an unswitched (formerly 0 x 1) connection in
Alcatel-Lucent DMX NEs. Typically used for overlays on UPSR facilities.
•
BLSR A NE /BLSR Z NE - drop down lists allowing users to choose NEs for
BLSR connections. They are required on: n
Node only connections with BLSR n
Subnetwork Connections (Ring Connects) with a BLSR on one of the ends
• Circuit ID - 50 character (no spaces) field designed to accommodate a circuit ID. Valid characters are: All alphanumeric, - (dash), / (forward slash), _ (underscore). Leading and trailing spaces will be automatically stripped from the entry. Allows the association of a circuit ID with an end-to-end circuit made up of multiple cross-connects. If left blank, then a cross-connect ID (XCON ID) will be generated automatically by 1340 INC.
• Order Number - 15 character field designed to be used for a provisioning order number.
• User Tag - 10 character alphnumeric field designed to be used for a user name for whom a provisioning order is being executed. (This is separate from the User ID field). Use of the special characters #, $, %, @, and ! are also allowable.
NOTE:
User tags that are assigned at connection time can be used to filter on other INC reports
(including the Alarm List, Facility Report, Linked Report, Trace, etc.) Use of the User
Tag on the Connect Form, as well as it’s use as a filter, is governed by a setting in an INC system file and the creation of an associated user tag list. When configured for this feature, the associated reports and forms will contain a User Tag field in the Filter section.
Please see the 1340 Integrated Network Controller Application Installation Guide for additional information on setting up the associated files.
Buttons:
• Preview - Used to view a proposed AZ connection. See
AZCON Preview and Path Choice on page 5-36
April, 2009 5-35
Configure
• Submit: Send the connection request from Integrated Network Controller to the NE
• Schedule: Create a “Scheduled Command” based on the currently populated form so that the command can be executed at a particular time or repetitively on a designated schedule
• Macro: - Create a “Macro” based on the currently populated form so that the command can be executed with a symbolic name
• Clear: Clear all fields and selected options
AZCON Preview and Path Choice
When a user selects the A-Z connection type, the <Preview> button on the Connection form will become sensitive. When the appropriate fields have been populated (i.e. NE, Service View, etc.), selection of the
<Preview> button will display the Preview AZ Connection form.
Figure 5-16. AZCON Preview and Path Choice
This form will display a graphical view of the proposed connection as well as the Connection commands table. The high speed paths that will be used will be displayed in a drop down menu (see arrow) . These paths can be changed by selecting any of the paths in the drop down menu.
5-36 April, 2009
Configure
If a different high speed path is chosen, selection of the <Update> button will re-display the Preview AZ
Connection form with the new choices. When the desired high speed path is chosen, selection of the <Submit> button will execute the connection commands necessary to provision the AZ connection as defined.
April, 2009 5-37
Configure
Subrate Connections
Integrated Network Controller allows users to set up subrate and bridging connections. These connections are performed in the same manner as SONET TDM connections.
The following units are supported:
• SRM - Subrate Digital Multiplexer
• MJU - Multi-Junction Unit
• DMB - Digital Multipoint Bridge (Voice or Data)
NOTE:
The Move Subrate Backbone checkbox on the connection form is used when the user wants to move an SRM DS0 B or MJU conference master to another facility.
5-38 April, 2009
Configure
End Locations
End locations represent the location where an end-customer facility starts (A) and ends (Z). These facilities are not internode facilities. Using the Show End Locations checkbox on the Map View will change the display to reflect all end-user locations and the facilities which support them.
When selected, a list of allocated end locations will be displayed. Highlight the desired end location and click on the <Select> button. The selected record will populate the right side of the report with the associated
User, Name, and ID values. Make any desired modifications in the text editable fields (Address 1, Address
2, Contact Name, Contact Telephone, Contact Fax, and Comment) and select the <Update> button located at the bottom of the form.
Modifying end location information is optional, but useful, when initially setting up the GUI. It allows the user to identify each end location with a logical name, for example, Headquarters Bldg.
Figure 5-17. End Locations Report
In order for end locations to be displayed on the Map View, the Show Links option must also be selected. If the Show Labels option is selected on the Map View and the Node Label on the Preferences ->Map tab is set to NE Name, the end location name will be displayed next to the end location in the Map View.
April, 2009 5-39
Configure
Column Definitions:
• User - owner of the end location
• Name - user definable end location name. Default value is of the form User.NEID
• ID - end location identification
5-40 April, 2009
Configure
Groups
There are two types of network element groups in the Integrated Network Controller GUI:
• Subnetwork Group - SBNK
• Network Element Group - NE
A subnetwork group is defined as a group of network elements, usually a SONET ring, which all have the same subnetwork ID. For example, each ADM in a three node OC-3 ring could be assigned the subnetwork
ID of “1”.
A network element group can be created as a grouping of any network elements the user desires. A network element group can contain all or part of one or more subnetwork groups. The following are examples of possible network element groups:
• All network elements in a particular city, state, or geographical region
• All network elements belonging to a particular customer
• All network elements belonging to a production, or test network
The benefits of defining subnetworks and network element groups include the following:
• Ability to combine multiple NE icons into a grouped icon that takes up less space in the display area
• Ability to associate common information with multiple network elements
An alias list may be supplied to 1340 INC listing the aliases that have the appropriate privilege level to create, edit, or delete groups. If an alias does not have these priveleges, these forms will still be displayed, but all fields will be “read only”, and the <Add>, <Update>, and <Delete> buttons will not be available. Please see the Integrated Network Controller Application Installation guide for information on using this feature.
Figure 5-18. Groups
April, 2009 5-41
Configure
NE Group Management
Network element groups are not created automatically. When an NE Group is in the grouped state, a single icon will represent all of the network elements that are a part of the group. If the “Show Labels” option is selected on the Map view, then the label displayed will be based upon the user’s selection on the View ->
Preferences - Map Tab - Node Label drop-down list.
If the Group NEs checkbox is selected on the Map View, then all the NE groups currently defined will be grouped or ungrouped. If the Group NEs function is performed from a particular NE’s drop-down menu, then only that NE group will be grouped or ungrouped.
When the form is opened for the first time, the value “--NEW--” will be listed in the NE Group drop down list (by default): Select the <Search> button. The following form will be displayed.
Figure 5-19. NE Group Management Form
To create a network element group:
• Enter a unique NE Group ID number - required. This number can be between 1 and 9999.
5-42 April, 2009
Configure
• Enter a Group Name - required
• Fill in the rest of the optional fields on the form as desired
• Choose subnetworks to include in the Group from the Subnetworks “In Group/Out of Group” list
NOTE:
There may also be an NEs “In Group/Out of Group” list, if there are NE’s defined in
1340 INC that are not part of a defined subnetwork (i.e. certain DCS network elements).
• Select the <Add> button at the bottom of the form
• The NE Group created will now be listed in the NE Group drop-down list located in the Filter/Launch area
When additional groups are created, the Include in Select drop-down list (located in the Launch/ Filter area) allows users to filter the Group NEs list to show all NEs, or only NEs that are currently unused (not in another NE group).
The Align ID field will be used in conjunction with the Align Nodes function on the Map View.
NOTE:
Align ID is defined on either the NE Management, the Groups -> Subnetwork Management form, or the Groups -> NE Group Management form. When using the Align ID choices for sort order, if nodes are displayed individually, the Align ID value on the NE
Mgmt form will be used; If nodes are grouped into a Subnetwork, the Align ID value on the Groups -> Subnetwork Management form will be used. If nodes are grouped into an
NE Group, the Align ID value on the Groups -> NE Group Management form will be used. The Align ID is displayed in parentheses when the left mouse button is used to select a node on the Map Display.
• Group’s Group - displays the group name that this group is a part of (if any)
• Background/Icon Size/Latitude/Longitude - These fields are primarily used in conjunction with the Multi-Level Map feature (described in “Chapter 6 - View” of this document).
The values in Background and Icon Size willl indicate the Map View appearance. The
Latitude and Longitude fields will dictate the position of the Group on the Map.
NOTE:
If the choice “Current” , located in the Background drop down menu is chosen, selection of the associated item will open up the group, subnetwork, or NE with the current background used .
Grouping of Groups
Integrated Network Controller allows the user to create a “group of groups”. The procedure for creating a group of groups is identical to that of creating a group of NEs. The Group’s Group ID (seen on the NE
Group Information form) is the identifier of the highest level of Grouped Group hierarchy that the chosen
April, 2009 5-43
Configure group is a part of. A zero indicates that the displayed group is not a member of a higher level group. Adding a previously defined group to a newly created group can be accomplished by entering the Group ID that the chosen group is to be a part of. The icon for a “grouped group” is also identical to that of a single NE group.
Once created, the “grouped group” icon will display additional choices in the Node Navigation Drop Down list that will allow users to group or ungroup at various levels. These include:
• Group NE Top - groups the NE to it’s highest level group
• Group NE - groups the NE one level
• Group Group - groups an NE group to the next highest level group
• Group Group Top - groups the NE group to it’s highest level group
• Ungroup Group - ungroups the NE group to it’s next lowest level group
• Ungroup Group Bottom - ungroups the NE group to it’s lowest level group
The ability to edit or delete NE group information is also available via this form.
NOTE:
Created NE Group IDs will be shown in the drop down lists immediately, but must be saved locally, on the map, in order for the group information to be displayed when queried.
5-44 April, 2009
Configure
Subnetwork Management
When network elements are added to the Integrated Network Controller database and are assigned a particular subnetwork ID, the associated subnetwork group is automatically created by Integrated Network Controller. Without performing any other task, the GUI user can group and ungroup the subnetwork in the Map
View area by selecting/de-selecting the Group Subnetwork checkbox. The grouped icon label will be the subnetwork ID.
If the user wants to give the subnetwork a more descriptive name and/or associate some general information with the subnetwork group, he can do this on the Groups -> SubNetwork Management form. To add or change information associated with a subnetwork group, highlight the appropriate SBNK entry in the list on the left side of the form then click the “Search” button under the list. Fill in the fields on the form as desired, then click the “Update” button.
If a subnetwork name is associated with a subnetwork ID, then the name will appear along with the ID on other GUI forms and reports.
Figure 5-20. Subnetwork Management Form
April, 2009 5-45
Configure
• The Align ID field will be used in conjunction with the Align Nodes function on the Map
View.
NOTE:
Align ID is defined on either the NE Management, the Groups -> Subnetwork Management form, or the Groups -> NE Group Management form. When using the Align ID choices for sort order, if nodes are displayed individually, the Align ID value on the NE
Mgmt form will be used; If nodes are grouped into a Subnetwork, the Align ID value on the Groups -> Subnetwork Management form will be used. If nodes are grouped into an
NE Group, the Align ID value on the Groups -> NE Group Management form will be used. The Align ID is displayed in parentheses when the left mouse button is used to select a node on the Map Display.
• Group - displays the name of the group that this subnetwork is a part of (if any)
• Background/Icon Size/Latitude/Longitude - These fields are primarily used in conjunction with the Multi-Level Map feature (described in Chapter 6 of this document). The values in Background and Icon Size willl indicate the Map View appearance. The Latitude and
Longitude fields will dictate the position of the Subnetwork on the Map.
5-46 April, 2009
Configure
Maintenance State
The Update Maintenance State feature is used to identify a facility or network element as being in one of the following states:
• Normal state (Clear)
• Maintenance state (Maint)
• Alarm blocked state (Block)
• Miscellaneous alarm blocked state (MBlock)
For facilities or NEs in the Clear state, the GUI processes and displays all alarms as usual.
For facilities or NEs in the Maint state, the GUI will or will not display alarms based on the user’s defined preferences. Users can turn the display of Maint alarms on or off via the View -> Preferences - Alarm Tab -
Maintenance Alarms selection list. If set to “YES”, the
1
GUI will display all normal and maintenance alarms on the GUI. As alarms in the maintenance state are received, they will be marked as ‘ALM-MAINT’ in the STAT field in the Alarm List. Alarms identified as Maintenance alarms will stay in the maintenance state for the specified time as defined on the Update Maintenance State form. Even though Maint alarms may or may not be displayed to the GUI user, the alarms will still be processed by 1340 INC and saved in the alarm database.
For facilities or NEs in the MBlock state, the GUI will not display any miscellaneous type alarms. The
MBlock state will also keep any miscellaneous alarms from being recorded, or saved, in the 1340 INC alarm data base.
For facilities or NEs in the Block state, the GUI will not display any alarms. The Block state will also keep any alarms from being recorded, or saved, in the 1340 INC alarm data base.
Placing a facility or NE in one of these alarm states keeps undesired alarms from being reported to the GUI user. There are various reasons why a GUI user may choose to use this feature; the facility is a newly turned up facility and may alarm frequently until turn-up is complete, the customer equipment has been turned off or disconnected from the facility, or the facility is alarming and clearing repeatedly.
1.
April, 2009 5-47
Configure
Figure 5-21. Update Maintenance State form
Fields:
• Type - Allows the user to select an NE or Service View whose state will be updated
• User - Becomes sensitive only when the Type=Service View. Allows the user to specify the owner of the facility whose state will be updated
• NE - Allows the user to select an NE whose state will be updated or an NE on which the facility owned by the user will be updated
• Service View - Service View of the facility to be updated
• Entire Circuit - Allows the user to put an entire circuit (as opposed to just one port ( facility) into a maintenance state
• Current State - Displays the state the NE or facility is currently in
• New State - Allows the user to select the state to change the NE or facility to.
• Activation - Displays the current activation date and time for the selected NE or facility
5-48 April, 2009
Configure
• Expiration - Displays the current expiration date and time for the selected NE or facility
• New Expiration: Days:/Hours: - Allows the user to select a new expiration value for the selected NE or facility
NOTE:
If the New State value is set to Block or MBlock (for an NE), or Maint or Block (for a specific service view) a calendar popup will be displayed next to the New Expiration
Days field. This popup will allow the user to select a specific day that the selected state of the NE or facility will expire.
April, 2009 5-49
Configure
Macros
Macros allow users to create symbols that represent Integrated Network Controller commands.
Figure 5-22. Macro Management
5-50 April, 2009
Configure
Macro Definition
The symbol name is a string of alphanumeric characters with no spaces. The first character cannot be numeric. The underscore (_) is the only special character allowed and it can be the first character, if desired.
The definition is the command(s) that the symbol name represents. If more than one command is to be used in a definition, the commands must be separated by a semicolon (;). The Macro definition may not exceed
200 characters in length.
A user may only define one symbol at a time. If user attempts to use a previously defined symbol, the new definition will override the old definition only when the override option is selected.
Figure 5-23. Macro Definition
April, 2009 5-51
Configure
Macro List
The Macro List is a list of existing Macros.
Figure 5-24. Macro List
Navigation Drop Down List:
• Modify - Allows the user to change the structure of the existing Macro
• Remove - Allows the user to delete the Macro
• Run - Allows the user to execute the selected Macro
NOTE:
When running 1340 INC in CNM mode, console and console alias logins cannot execute end-user defined macros.
5-52 April, 2009
Configure
Stacking Macros
Macros can also be stacked. Stacking commands is useful when many connections or disconnections need to be performed all at once, such as disaster recovery, or switching from a primary data center to a backup center. The example below describes the method used to set up such a macro.
The following Symbol Names and Definitions are entered into Integrated Network Controller using the
Macro Definition form one at a time.
Symbol Name
•
dis1
•
con1
•
con2
•
dis2
•
con3
•
recover
Definition disconnect data.1 data.2
connect data1 idl.1
connect idl.2 data.3
disconnect voice.1 idl.6
connect voice.1 idl.8
dis1;con1;con2;dis2;con3
As shown above, the symbol named ‘recover’ can be executed to perform the five previously defined symbols. This is also referred to as a macro.
April, 2009 5-53
Configure
NE Management
The NE Management form provides the capability to add, delete, and modify network elements. Network
Element information currently in the 1340 INC data base can also be queried via this feature. The NE Management form can be accessed in the following ways.
• Menu Bar - Configure - NE Management
• NE Pop-Up Menu - NE Management
• NE Summary Report Navigation Drop Down List - NE Management
Figure 5-25. NE Management
Filters (View/Modify):
• NE List - A drop down list of the TIDs (Target Identifiers) of Network Elements currently defined in 1340 INC. When an NE is selected from this list, the NE Management form will be populated with the associated NE data.
5-54 April, 2009
Configure
• NE ID - Allows the user to enter the Network Element Identification number of any NE currently defined in 1340 INC. A message will be displayed if a number is entered for an
NE that is not defined in the 1340 INC database.
NOTE:
The NE ID field can also accept a TID, allowing the user to enter a case sensitive text value in this field.
Filters (Add):
• NE Type - Allows the user to select a network element type to be added to the 1340 INC database (in accordance with the license file).
• Initialize From Existing NE - Used to copy the information from one NE to one (or more)
new NEs. This can be a GNE or an RT. The NE value entered in this box must be the NE value of the NE being copied (that is, an already existing NE).
•
Enter the NE in the Initialize From Exisiting NE box.
•
Select the NE Type.
•
Select the <Add New NE> button. The NE Management form will now be populated with the information of the existing NE. The NE value can now be changed to the value desired. Selection of the <TAB> button will populate the associated
NE values (e.g. TID, Default Service Name, etc.)
NOTE:
If the user is adding a new NE and initializing from an existing GNE, they will be prompted to change the Comm Group to the next available number.
•
Once all appropriate information has been added, select the <Add> button to add the NE to the 1340 INC database.
Fields:
• NE - Allows the user to enter the Network Element Identification number of any NE currently defined in 1340 INC. A message will be displayed if a number is entered for an
NE that is not defined in the 1340 INC database.
• TID - Target Identifier of the selected NE
• Gateway - The Gateway checkbox is sensitive if the NE type is a SONET network element.
Selecting the Gateway checkbox indicates the NE ID is the Gateway Network Element
(GNE) through which 1340 INC will communicate with all other network elements in the same communications group.
April, 2009 5-55
Configure
• Backup Gateway - The Backup Gateway checkbox is sensitive if the NE type is a SONET network element. Selecting the Backup Gateway checkbox indicates the NE ID is the
Backup GNE through which 1340 INC will communicate with all other network elements in the same communications group in the event the Primary GNE communications link is down.
5-56 April, 2009
Configure
• Multi-Gateway -
It is possible to provision two active gateway NEs to an NE communication group. A group of network elements that are connected together by a communcations network is called a communication group (Comm
Group) in 1340 INC. For example, SONET network elements may communicate to each other using OSI protocols over the SONET DCC. The NE that 1340 INC connects directly to, in order to communicate with that NE and the other NEs on the network is called the Gateway network element (GNE) in 1340 INC. It is possible, however, in 1340 INC, to identify a second Gateway network element to the same network. Communications to the other NEs (also referred to as RTs or Remote Terminal), can then be made through either
GNE. This provides for redundancy and increased communications integrity.
In the following example, four NEs are networked together, and 1340 INC is directly connected to NE1 which is the GNE for the entire communication group. Communications to NE2, NE3 and NE4 is via NE1.
If a fault occurs at point X, then 1340 INC loses communication to NE3 and NE4. If a second GNE link is established to NE4, as identified by the dashed line, however, then 1340 INC can communicate to NE3 and
NE4 using the second GNE link.
1340 INC
NE1
Figure 5-26. Multi-GNE Diagram
NE2
X NE3
NE4
April, 2009 5-57
Configure
To identify an NE as a Multi Gateway NE, go to the Communication tab of the NE Management form. You must first disable the NE, and wait for communications to be taken down. Then select the Multi Gateway checkbox in the upper right corner. When you do so, then the gateway communications information becomes active. For example, for LAN communications, you now enter a Port and a Remote System Name or IP. After you Update this information, and re-enable communications this NE becomes a Multi Gateway
NE.
Figure 5-27. Multi-GNE selection
5-58 April, 2009
Configure
When the Multi Gateway is provisioned, the NE Management form will display the other Gateway in the
Multi GNE field for the Gateway and Multi Gateway NEs.
Figure 5-28. Multi-GNE example
Backup Gateway vs Mutli Gateway
It is also possible to provision an NE as a Backup Gateway. This is an older protection strategy that is still supported by 1340 INC. A backup gateway is a protection gateway network element that is used only if communications to the gateway network element fail. In this case only one of the NEs, either the Gateway or the Backup Gateway is communicating to 1340 INC. If communications to the Gateway fail, then 1340
INC uses the Backup Gateway to communicate to the Comm Grp. In the above example, if NE1 is the
Gateway NE, and NE4 is identified as the Backup Gateway, and if 1340 INC is communicating through the
Gateway NE1, and a fault occurs at point X, then no switchover occurs, and communications to NE3 and
NE4 are lost. An NE cannot be both a Multi Gateway NE and a Backup Gateway and you cannot create a
Backup Gateway to a Multi Gateway.
April, 2009 5-59
Configure
• NE Type - The type of network element that the displayed information pertains to.
• GNE - Displays the TID of the GNE for the selected NE.
• Backup GNE - Displays the TID of the Backup GNE (if one is defined)
Buttons:
The following describes the functions of the buttons at the bottom of the NE Management Form:
• Update - used to update the 1340 INC database with modified information for a network element. Some fields on the NE Management form may not be updated unless the NE is disabled.
• Delete - used to delete the selected NE from the 1340 INC database. When deleting an NE, the following steps must be executed:
— Remove DCC connections. This can be accomplished by selecting the Neighbors tab, deleting the information in the “To NE” column and selecting the UPDATE button.
— Remove all cross connects associated with the NE.
— Disable communications to the NE. This is accomplished by selecting the Communications tab, selecting the DISABLE checkbox and selecting the UPDATE button.
— Once communications has been disabled, the DELETE button will become sensitive and may be selected.
— A confirmation box will be displayed. Enter “yes” to confirm the deletion and select
SEND.
• Change NE Type - This button allows the user, for a select set of NEs, to upgrade an NE type, within an NE family or manufacturer model, to a higher optical rate, e.g. OC48 to
OC192, or different optical application, e.g. LINEAR to UPSR, in the 1340 INC database. The NE types that are supported are:
— Alcatel-Lucent DMX family (including DMXtend and DMXplore)
— Cisco 15454/15310/15327 families
— Fujitsu 4500/4300/4100 families
— Nortel 3500/3400 families
When communications to the NE are disabled or down, then this button becomes sensitive. When it is selected, a popup is displayed from which it is possible to select a new NE Type. Only a choice of valid NE
Types are presented. If the user selects Change NE Type on the form, then that NE type will be placed into the NE Type field at the top of the form. The information can then be updated to the 1340 INC database.
• Reset Link - causes 1340 INC to reset the communications link to the selected network element.
• NE Summary - displays the NE Summary Report. When selected, the report will display all nodes in the same subnetwork and communications group.
• Card Inventory - displays the Card Inventory Report for the selected NE
• Equipment View - displays the Equipment View for the selected NE
5-60 April, 2009
Configure
• Update DNO - performs the DNO function for the selected NE
• Auto Discover - performs the EMS Auto Discovery function
• NE Notification - displays the NE Notification form. See
for a description of this feature.
• Backup DB - performs the EMS Backup DB function
• Restore DB - performs the EMS Restore DB function
• Sync - initiates a synchronization between configuration information in the NE, and the 1340
INC database. This function is specific to ATM/FR and ME II type network elements.
• Set TOD - Sets the Time of Day at the NE to the time of the 1340 INC Core Server. If the communication link to the NE is down, the command will be buffered and sent when the link comes back up.
NOTE:
Fields described on the NE Management form and it’s associated tabs are driven by a number of factors (feature files, NE Type, etc.). Not all fields described are visible at all times. Contact your system administrator for additional information.
April, 2009 5-61
Configure
General Tab
Contains basic network element specific information pertaining to the selected NE. Default user and default service view provide information used when assigning facilities.
• NE Name - 14 Character field used for NE icon label
• NE Group ID - 1-12000 All NEs with same NE group ID can be grouped into 1 icon
• SBNK ID - 1-12000, All NEs within a ring should have the same SubNetwork ID
• SBNK Name - Name associated with a SBNK ID on the Subnetwork/Group Management form
• TID - Target ID - A 1-20 length character string . The TID uses the alphanumeric characters
(letters A-Z, numbers 0-9) and exlcudes special characters except for #,%,+, - (hyphen) and _ (underscore). TIDs cannot start with a number and cannot contain a . (period).
Each NE must have a unique TID within the 1340 INC database.
• APS ID
•
Nortel OC48 - unique ID for each NE in a ring, value 0-15
•
Nortel Optera DWDM - All shelves within an Optera have the same ID - values
0-15
• Band - this selection applies to DWDM NEs
• Align ID - user defined value used in conjunction with the Align function. Used when this field is populated and the Align ID sort is used on the Node Align form.
• CLI - 40 character field used to identify the NE
• Node Type - drop-down list of nodes types
• Comment1 - 70 character field for free-form text input
• Comment2 - 70 character field for free-form text input
• Contact Name - 29 character field for free-form text input
• Address1 - 29 character field for free-form text input
• Address2 - 29 character field for free-form text input
• Telephone - 20 character field for free-form text input
• Fax - 20 character field for free-form text input
• Default User - default partition name used when assigning facilities
NOTE:
If there is a field displayed next to the Default User pull down, the user may manually enter a default user name. This is primarily used in a multibox configuration. Any manually entered default user name will override any name chosen from the pull down list.
• Default Service Name - default service name used when assigning facilities
5-62 April, 2009
Configure
• NE State
•
Clear - Allows all alarms to display on GUI
•
Block - Blocks all alarms from the GUI and not stored in alarm data base
•
MBlock - Blocks Miscellaneous (non-assigned) alarms from the GUI and not stored in the alarm data base
• Activation - date in which Block or MBlock is activated
• Expiration - date in which Block or MBlock will expire
• Latitude/Longitude - displays the values in Degrees, Minutes, and Seconds of the Node’s location on the Map View. These fields are also associated with the Multi-Level Map feature. This feature is described in detail in Chapter 6 of this document.
• Default Assignments to ’Surveillance Only’ - selection of this box allows the console user to control a customer’s provisioning access to assigned facilities. Facilities can be assigned to a customer as “config” (which gives a customer access to all 1340 INC provisioning and monitoring features), or as “surveil” (which restricts the customer to surveillance of the facility only). The customer surveillance feature is built upon the Subpartition feature, previously only available to Command Line Interface (CLI) users. What was previously subpartition 8 is now reserved as the surveillance partition. All facilities, not part of other partitions by default, are assigned to this partition called the SurvOnly partition.
Within this partition, a facility can be configured for Config usage or Surveil. This feature is an optional feature which is enabled on all GUI forms by the
USE_SURVEIL_PARTITION system define, and is disabled by default. Unless overridden at assign time, or changed by the Subpartition form, all assigned facilities will assume the state as set by the NE (on the NE Management form). There are options on the provisioning management forms for assign and populate to set, or un-set, the surveillance state of a particular facility. The choices are Default (assume the default setting of the NE), Yes (set the facility to surveillance only) or No. The Subpartition Management form provides the ability to change the surveillance state of already assigned facilities.
Facilities can be assigned to different partitions (1 through 7) and/or to a different usage state (Surveill or Config). A Subpartition Report is provided to display the information in each partition (1-7) and the surveillance partition. In addition, the facility report status column will also flag facilities which are set for surveillance only
• Associate Equipment Alarms with Default User - when selected, equipment alarms for this
NE will be assigned to the default user
April, 2009 5-63
Configure
Communication Tab
Used to display/enter the various information used to establish and maintain communication between 1340
INC and the network element.
Figure 5-29. NE Management - Communication Tab
Fields:
• COMM Group - the communications group ID. All network elements that 1340 INC communicates with via the same communications path are in the same COMM Group. If the new NE is an RT (remote terminal) of an existing ring then the COMM Group ID must be the same ID as the GNE.
• COMM Type:
5-64 April, 2009
Configure
•
X25: Selecting the COMM Type ‘X25’ will prompt the user with a Port #, Login,
Password, SVC/PVC and Address.
• Disable Communication - this checkbox is used to place communication to the NE in a sleep state. 1340 INC will not attempt to communicate with the NE while in the disable mode.
• Auto DNO and/or Event DNO - if these checkboxes are selected then 1340 INC will automatically perform a DNO query based on the amount of time the NE link was down or if an event occurs such as a card switch.
• Ethernet DNO - if this checkbox is selected, can only be enabled when Auto DNO is enabled.
1340 INC will automatically run DNO when changes to Ethernet provisioning information is detected.
• Auto Alarm Sync - if this checkbox is selected, 1340 INC will automatically synchronize alarms when either of the following occur:
•
The link to the NE is restored after being down for a specified period of time.
•
The NE state is changed from Block to Clear
• Port:
•
LAN: If the NE is going to be a new GNE (Gateway or Backup Gateway) then the COMM Type field becomes sensitive. Selecting the COMM Type ‘LAN’ will prompt the user with a Port #, Login, Password, and Remote System Name/IP
Address.
•
SERIAL: The user will be prompted for a Baud Rate via a drop down list with the choice 1200, 2400, 4800, 9600, or 19200.
•
FIBER: The user will be prompted for a Datakit Path (DK Path).
•
For an NE with COMM Type=LAN, the Port # field contains the socket used to access the NE via the Remote System Name or IP address. For accessing an
Alcatel-Lucent DCS II via a LAN connection, enter Port #=23 in this field.
•
For an NE with COMM Type=X25, the Port # field contains the x25 port being used to access the NE via an X25 packet network. An example of an X25 port number is X251215. Valid port numbers can be found in the Console Command
Line Interface document, located in the chapter labeled “Equipping Network Elements and 1340 INC ports.” The Address field is used to enter the X121 address
(NTN) of the NE.
• Mux Number - Only applicable in a multi-box environment. Back-end system that manages this NE.
• NE Login - The login ID created in the network element that 1340 INC will use to log in to the NE.
• Password/Verify Password - The password associated with the NE Login
• No Login - If the network element does not require a login, this option should be selected
• Use GNE - If this option is selected, 1340 INC will use the NE Login and Password entered for the GNE of the same COMM group.
April, 2009 5-65
Configure
• Remote System Name or IP - the system name or IP address of the NE
NOTE:
The following network rules apply to the allowable values for the IP address:
•
first octect = 1-255
•
second octet = 0-255
•
third octet = 0-255
•
fourth octet = 1-254
• NE Timezone - allows the user to set the timezone that the NE is located in
• SUB Type - allows the user to describe the NE type and configuration. This will be displayed on the NE icon when displayed on the Map
• External Access / Data - allows users access to the following types of external interfaces
•
TELNET - when selected, the Data field will allow input of an IP address for access to an external IP address
•
HTTP - when selected, the Data field will allow input of a URL address. Typically used for access to an NE Management Interface application.
•
EXEC - when selected, the Data field will allow input of a path to an executable application on the resident host.
Communication Tab - NE Specific Information
The format of the communications tab will vary depending upon the type of network element being defined.
For example, if X.25 is chosen as the COMM Type, the user may supply a second SVC or PVC Address.
Conversely, a second Remote System Name/IP address may also be defined depending on the type of network element being databased.
5-66 April, 2009
Configure
NE Password Hiding
This feature provides an optional system wide setting used to hide network element passwords. If enabled, no network element passwords will appear on 1340 INC forms, reports, and log files.
If this feature is enabled, network element password input on the NE Management form - Communication
Tab, will require two fields for validation (Password and Verify Password)
Users should be aware that if this feature is enabled, then network element passwords will not be visible to any users. This could be an issue in the effort to troubleshoot a connectivity problem with a network element.
Changing the GNE of a Ring
In order to change the GNE of a particular communications ring, the following steps must be executed:
• Disable communications to the ring (Disable the GNE and the RT being changed to a GNE)
• On the NE Management form for the RT node which is to become the new GNE:
•
Check the Gateway checkbox
•
On the Communications tab, change the Comm Group ID to an unused communications group number.
NOTE:
The user will be prompted to change the Comm Group to the next available number.
•
On the Communications tab, add the “Port #”
•
On the Communications tab, add the “Remote System Name /IP”
• For each RT NE in the original communications group, change the Comm Group ID (NE
Management form, communications tab) to the same Communications Group ID as the new GNE.
• On the NE Management form for the original GNE node
•
Uncheck the Gateway checkbox
•
On the communications tab, change the Comm Group ID to the same Comm
Group ID as the new GNE node.
• Enable the new GNE node and the old GNE node.
April, 2009 5-67
Configure
Neighbors Tab
The Neighbors Tab is used to enter and display the neighbor (tie) information for SONET network elements.
This information defines the network topology and associates network elements that are connected optically.
Figure 5-30. NE Management - Neighbors Tab
Column Definitions:
• From Port/Slot - The facility on the currently selected NE that is to be tied
• To NE - The NE ID of the NE that the facility is being tied to
• To NE Type - The “To NE” is this type of network element
• To Port/Slot - The facility on the “To NE” that the facility is being tied to. This contains a drop down list of possible selections
5-68 April, 2009
Configure
Mates Tab
A new Mates tab is available on the NE Management form. It is applicable to NEs which are flexible multi-ring NEs, that is, NEs which can manage multiple rings of different rates, but where it is not possible for 1340 INC to determine the UPSR line pair information. Specifically, these NEs are:
• Cisco 15454 family
• Cisco 15310 family
• Fujitsu 4500 family
• Fujitsu 4300 family
• Nortel 3500 family
• Alcatel-Lucent Lambda Unite
The Mates tab is used to display the protection group information for the optical facilities discovered by
DNO. It is also used to create UPSR mate information in the 1340 INC database. This information is used to help Populate assignments for CNM customers, and for automatic assignment of facilities for NMS customers. The mate, or E/W pair information is then used by Connection Management to create the proper cross connect commands.
1340 INC Connection Management generates cross connect commands across single or multiple NEs. The optical facilities may be UPSR, BLSR, 1+1 protected, or unprotected. The 1340 INC connection management form only prompts for a single From AID and a single To AID. 1340 INC automatically tracks and generates the proper cross connect commands across three (or four) AIDs that are often required for UPSR/
BLSR cross connects at the NE. Connection Management uses information stored with the facilities to determine if it is part of a protection group, and what kind of protection group it is. DNO discovers the protection group information. UPSR protection group information, however, is often not maintained by NEs.
In this case it is necessary to input into 1340 INC, the UPSR protection information, that is, what UPSR lines are providing the West and East directions of the UPSR ring.
The Mates tab is provided on the NE Management form so UPSR protection information can be input to
1340 INC. 1340 INC will use this information when DNO runs to derive the correct West and East AIDs for the UPSR cross connect. The DNO information then drives the creation of facilities. For CNM customers, the DNO information is used by the Populate form, and for NMS customers this information is used to automatically create the cross connect facilities. The Mates tab displays the BLSR and 1+1 protection information that has been derived from the NE by DNO and the current UPSR pairs that were provisioned by a 1340
INC operator.
April, 2009 5-69
Configure
Figure 5-31. NE Management - Mates Tab
The From Port/Slot and Mate Port/Slot columns identify the protected lines on the NE. If the Mate Port/
Slot information says No Mate, then the From Port/Slot is not protected. The Ring Type column shows the current protection scheme that is assigned to the line pair. It is blank if no protection is assigned. The Role may either be assigned to be West/East for UPSR and BLSR protection schemes or Working/Protect for 1+1 protection schemes. If BLSR or 1+1 protection group information has been discovered by the DNO of the
NE, then that information is displayed in the form and it cannot be changed.
If a Mate Port/Slot says No Mate, then a Mate Port/Slot can be assigned. The drop down choice list will show all lines, on that NE, that are of the same type that can be assigned to be UPSR protected. When another line is chosen the Ring Type will be set to UPSR, and the Role will be automatically set to West.
Once a choice is selected, then the From Port/Slot entry that corresponds to the Mate Port/Slot that was selected will also be automatically filled in, the Ring Type will be set to UPSR and the Role will be set to
East. The roles may be changed by using the pull down menu.
5-70 April, 2009
Configure
If a Mate Port/Slot is displayed, and the Ring Type is set to UPSR, then the Mate Port/Slot association can be removed by selecting No Mate from the pull down menu.
When the UPSR mate information has been entered, then the Update button will update the 1340 INC protection database with the information. If the Auto DNO is not set on the NE, then DNO must be run, after the protection database is updated, in order to refresh the DNO records for populate or auto assignment. If the Auto DNO is enabled on the NE, then the DNO will automatically run, and reset the facility assignments with the proper West/East information.
April, 2009 5-71
Configure
Info Tab
The Info Tab contains status information pertaining to the selected NE. These fields are information only and are not editable.
Figure 5-32. NE Management - Info Tab
NOTE:
Time Difference - The difference in time between 1340 INC and the NE (1340 INC time
- NE time). The value will be displayed as a positive or negative number accordingly
(from the perspective of the NE). That is, if it is 10:00 PM at 1340 INC and 9:00 PM at the NE, the column displayed in the report will be -01:00:00. If it is 9:00 PM at 1340
INC and 10:00 PM at the NE, the field will contain the value +01:00:00.
5-72 April, 2009
Configure
Facilities Tab
The Facilities tab contains statistical information about the specified network elements facilities
Figure 5-33. NE Management - Facilities Tab
Column Definitions:
• User - if present, the user assigned facilities on this NE
• Total # Fac - number of STS1 equivalent port records (facilities) in 1340 INC
• Total # Chan - number of T1 equivalent port records (channels) in 1340 INC
• Total Fill - (number of channels) divided by (number of facilities multiplied by 28)
• XCon # Fac - number of STS1 equivalent facilities in 1340 INC that are cross connected
• XCon # Chan - number of T1 equivalent facilities in 1340 INC that are cross connected
April, 2009 5-73
Configure
• XCon Fill - XCon # Chan divided by Total # Chan
• Partial # Fac -number of STS1 equivalent facilities in 1340 INC with less than 14 T1 ports assigned
• Partial # Chan - number of T1 equivalent facilities on STS1 facilities in 1340 INC with less than 14 channels assigned
• Partial Fill - Partial # Chan divided by (Partial # Fac multiplied by 28)
• Partial % Tot - Partial # Chan divided by Total # Chan
• Full # Fac - number of STS1 equivalent port records (facilities) in 1340 INC that are fully assigned
• Full # Chan - number of T1 equivalent ports in 1340 INC that are fully assigned
• Full Fill - Full # Chan divided by (Full # Fac multiplied by 28)
• Full % Tot - Full # Chan divided by Total # Chan
NOTE:
Additional tabs may be present for ATM/FR or Metro Ethernet users. Refer to the Integrated Network Controller ATM/FR Supplement or the Integrated Network Controller
Metro Ethernet Supplement for further information regarding those tabs.
5-74 April, 2009
Configure
NE Management - NE Specific Features
Some network elements have a specific set of functions and features in addition to the standard capabilities when being managed by the 1340 INC.
NE Management on the ALU 1850 TSS-5
The ALU 1850 TSS-5 allows the user the ability to communicate to VLNC40 and VLNC60 cards via CLI or
SNMP interfaces when the unit is equipped with one or the other or both card types in the Main-1 or Main-2 slots.
Figure 5-34. Enable MAIN - Communication Tab
When the Enable MAIN checkbox is selected, the following fields will be displayed:
• CLI/SNMP IP Address - the IP address of the card used for CLI and SNMP communication
• CLI Port - the CLI telnet port on the card for CLI communication (the default is 23)
• SNMP Port - the port on the card for SNMP communication (the default is 161)
• CLI Login /Password / Verify Password - the login and password used to allow CLI communication between 1340 INC and the card
• Privileged Password / Verify Password - an additional password required to allow communication between 1340 INC and the card. This password is required at the CLI in order to enable access for configuration changes
• SNMP Community: Read - the SNMP community string sent in GET, GETNEXT, and GET-
BULK requests from 1340 INC to the card
April, 2009 5-75
Configure
• SNMP Community Write - the SNMP community string sent in SET requests from 1340 INC to the card
• SNMP Community Trap - the SNMP community placed in TRAP/NOTIFICATIONS from the card to 1340 INC
• SNMP Version - indicates which version of SNMP will be used to communicate between
1340 INC and the card (usually V2C)
When the Disable CLI Communications checkbox is selected, the user will not be able to use the CLI interface between 1340 INC and the card.
!
WARNING:
The customer is able to set the PROMPT of a VLNC40 or VLNC60 Command Line
Interface using the “set prompt” command on the CLI. 1340 INC requires that the
PROMPT start with the string “ALU” (i.e. “ALU123” would be valid, “123ALU” would not be.
SUB Type for the 1850 TSS-5
The SUB Type for the 1850 is also set on the Communications Tab of the NE Management form. The available choices are No SubType , OC12 UPSR, OC12 Linear, OC3 UPSR, and OC3 Linear. The MapView will then display the associated indication (as appropriate) as part of the TSS node icon (U for UPSR, L for Linear ,OCn for No Sub Type) . The NE Summary Report will, likewise, show the TSS SUB Type in the Type column.
NE Management on the ALU 1678
The Ethernet Management interface from 1340 INC to the ES64C cards is now both CLI and SNMP based.
1340 INC maintains a link to the Command Line Interface for provisioning and the SNMP interface for data reads. A link is maintained to each active ES64C CLI which provides a more robust interface for command
5-76 April, 2009
Configure integrity. In order to effectively use this interface, a TL1 user login must be maintained for each CLI login on the NE. This is provisioned via the NE Management form, and must be performed before the Ethernet
Management form is available for that ES64C card.
Figure 5-35. NE Management form Communications tab for ES64C login provisioning.
NE Management of the ALU 5620 SAM and ALU
Ethernet Devices (SAM NEs)
An interface to the Alcatel-Lucent 5620 Service Access Module (SAM) is supported for management of certain Alcatel-Lucent ethernet devices (SAM NEs) . These devices are:
• 6850
• 7250
• 7450
• 7705
April, 2009 5-77
Configure
• 7710
• 7750 SR
Through the SAM interface, INC will:
• Automatically discover and equip the device in the INC database.
• Manage changes to the devices’ equippage via notifications from SAM
• Manage alarms associated with the device and map these to the appropriate device in the
INC database.
• Synchronize the alarm information of the INC database with SAM.
• Display the 5620 SAM on the device on the INC map with the associated alarm states.
• Provide a 5620 GUI launch capability from INC.
NOTE:
The 5620 SAM client software must be installed on the PC that runs the INC WEB GUI browser in order for INC to be able to launch the SAM GUI.
5-78 April, 2009
Configure
Figure 5-36. INC Network map with 5620 SAM Interface, two 7750s managed via SAM, with
a manually created “generic link” between them, and SAM Cut Thru.
April, 2009 5-79
Configure
Use the NE Management form to equip access to the SAM server. Two IP addresses may be entered when the SAM redundancy feature is required. The Port is the http port on the SAM Server, and the Login and
Password are the login/password on the SAM server.
It is also necessary to enable the SAM feature by setting various variables in the system_defines feature file.
This enables the Jave Message Service for SAM messages, access to the SAM URL for requests, and ftp information for information exchange.
Figure 5-37. NE Management of the 5620 SAM Interface.
NE Management access is also provided for the ALU devices. The NE Management form is, however, for display only. The devices are automatically provisioned and deprovisioned using information from the SAM server. In the NE Management form the TID correponds to the device “Site name” and the IP address in the
NE Management form represents the “Site ID” as retrieved from the SAM Server for that device.
5-80 April, 2009
Configure
Figure 5-38. ALU 7750 SR alarms mapped to the proper INC NE, alarm detail displays all of
the SAM alarm details
April, 2009 5-81
Configure
NE Management of the ALU 1830 PSS
INC provides network representation and alarm management of the Alcatel-Lucent 1830- PSS. The 1830
PSS is Alcatel-Lucent’s newest DWDM offering, supporting R-OADM, F-OADM and TOADM capabilities with integrated OAM capabilities for traffic supervision. INC provides access to the 1354 RM Photonic manager for 1830 detailed provisioning and control of the 1830.
INC supports provisioning of the 1830 PSS from the NE Management form. Once the first 1830 is provisioned and communicating with INC, INC supports automatic discovery of the rest of the 1830 network. The network map will display the 1830s and their topological links with each other.
Figure 6. Network Map representation of Alcatel-Lucent 1830 PSS, Cut Thru choice to the
1354 RM Photonic Manager
5-82 April, 2009
Configure
NOTE:
The 1354 RM PhM graphical user interface application must be installed on the same PC that is running the INC WEB GUI browser in order for INC to be able to launch the 1354
RM PhM GUI.
INC receives the SNMP traps from each 1830, and matches alarm information for active 1830 alarms using the SNMP interface. All INC alarm management features are supported for the 1830.
Figure 7. Alarm List of alarms discovered from an Alcatel-Lucent 1830 PSS.
NE Management of the ALU 9500 MPR
INC supports the Alcatel-Lucent 9500 MPR Radio. The 9500 provides cross connect and transmission interfaces for T1, T3 and Ethernet over microwave Radio. INC supports the 9500 MRP for Network Management (NMS) features. NMS features include: equipment and facility discovery, equipment view, alarm management features, connection management, and performance management features. Cut thru to
WEBeml, the Alcatel-Lucent PC application that provides detailed craft control of the 9500, is also available from the INC WEB GUI.
The following hardware is supported:
— MOD-300 Module (MSS/Radio) - radio interface
— DS3/E3-2 Module (MSS-DS3) - 2 port DS3
— TDM-32 Module (MSS-DS1) - 32 port DS1
— Core Module (MSS/CORE) - 4 port ethernet and core processor
April, 2009 5-83
Configure
The 9500 MPR is managed via an SNMP interface, and the SNMP access information is provisioned from the NE Management form. Once a 9500 MPR is provisioned and communicating to INC, then other neighboring 9500 MPR are automatically discovered and provisioned into the INC database along with the Neighbor information.
Figure 8. Network Map representation of the 9500 MPR, available cut through to WebEML
NOTE:
WebEML must be installed on the same PC as the INC WEB GUI browser, and in the default installation location in order to be accessable to INC.
5-84 April, 2009
Configure
Figure 9. Alcatel-Lucent 9500 MPR Radio Equipment View.
April, 2009 5-85
Configure
In order to manage network level connection across multiple 9500 MPR radio NEs, it is necessary to be able to match circuit facilities from one radio. Each Radio and Ethernet facility AID, therefore, is further qualified by VlanID. Each connection through an Ethernet and Radio on the 9500 is created with a Vlan ID, and the facility servicing that connection is qualified by Vlan ID. INC will always automatically create one facility with VlanID on each Ethernet/Radio facility to identify the radio. For each subseqent cross connect on the Ethernet/Radio, additional ETH or RADIO facility AIDs will be automatically created to contain the connection, each identified with the associated VlanID. When the cross connect is deleted, then the facility, will be released and will no longer appear on the Facility report.
Figure 10. Alcatel-Lucent 9500 MPR Circuit Trace,
NOTE:
At this time, INC will only manage circuits via connect match. INC Circuit Management does not support 9500 cross connect. 9500 MPR cross connects need to be created using
Cut thru to WebEML or other means.
5-86 April, 2009
Configure
Eastern Research DNX, Premisys IMACS,
Generic SNMP Devices
1340 INC (ems, nms modes only) supports alarm monitoring/synchronization on the Eastern Research DNX and Premisys IMACS devices via a generic SNMP interface. In addition, a “Generic SNMP” device is supported via the same interface should the need arise to support new equipment in the field via this interface.
These node types will be displayed as stand alone icons on the 1340 INC network map (i.e. without any links to other nodes). The network map icons will indicate the status of the communication link to 1340 INC and the highest level alarm on the node.
In the following description, the term “SNMP device” refers to a DNX, IMACS or Generic SNMP device.
1340 INC can process traps from any SNMP device and display the trap information in the 1340 INC Alarm
List. 1340 INC can also derive the interface alarms on a SNMP device by retrieving the ifAdminStatus and ifOperStatus MIB objects. To manage a SNMP device, the SNMP device must be entered into 1340 INC via the NE Management form. The NE Type selection must be set to one of the three types listed above.The IP address and “read-access” SNMP community string must also be entered on this form.
The following is a description of the SNMP Trap Processing logic used in 1340 INC in support of the above mentioned devices:
A LinkDown trap with ifAdminStatus = up(1) will generate a FAC category active LinkDown alarm against the ifIndex in the trap. LinkUp trap or LinkDown with ifAdminStatus not equal to up(1) will clear any FAC
LinkDown alarm against the ifIndex. If the ifIndex MIB object is missing from the LinkUp or LinkDowntrap, the trap will be generated as an ALERT category notification. Additionally, if the ifAdminStatus is missing from the LinkDown trap, an ALERT category notification is also generated instead of an FAC alarm. All other traps (i.e. except LinkUp and LinkDown) are generated as ALERT category event notifications. ALERTs are one-time events that do not stay active as FAC alarms do.
For any alarm, the alarm description text contains all of the MIB objects and values in the trap. The MIB objects will be listed by textual name if the MIB containing that object has been compiled into 1340 INC
(procedure described below). Otherwise, the trap MIB objects will be shown by OID number.
The name of the 1340 INC alarm will be the trap name from the MIB if the device MIB has been compiled into 1340 INC. If the MIB has not been compiled into 1340 INC, the alarm name will be the enterprise name concatenated with the trap number.
The following is a description of the alarm synchronization logic used in 1340 INC in support of these devices:
The alarm sync (a.k.a. Match) feature can assert and clear FAC LinkDown alarm conditions by retrieving ifAdminStatus and ifOperStatus from the ifTable in the SNMP device.
A FAC LinkDown alarm is generated against the ifIndex if ifAdminStatus is not down(2) and ifOperStatus is down(2). If ifAdminStatus is down(2) or ifOperStatus is not down(2), any FAC LinkDown alarm exists against ifIndex is cleared. If the SNMP device does not provide both ifAdminStatus and ifOperStatus objects, thenLinkDown alarms cannot be asserted or cleared via the Alarm Sync feature.
April, 2009 5-87
Configure
The following procedure is recommended if a new device is added to 1340 INC as a “Generic SNMP” type
(described above):
Compiling/Installing new MIBs into 1340 INC:
To see trap names and MIB object names appear in 1340 INC alarms, the MIBs containing these objects must be compiled and installed onto 1340 INC. This is done by sending the MIB(s) to the 1340 INC development team for compilation. Two files are output from the MIB compilation: snmpinfo.dat and straps.def.
These two files should then copied to the /usr/cnc/snmp/srconf directory on the 1340 INC server - the back-end server in a multi-box configuration - overwriting the existing files. The brassd process on the 1340
INC server must then be restarted to load these new files. This is done by executing the following:
/usr/cnc/snmp/bin/S566SnmpBrass stop
/usr/cnc/snmp/bin/S566SnmpBrass start
Restarting the brassd process automatically restarts snmp_trap which is necessary for the new MIB files to take effect.
After performing these steps, traps containing OIDs from these new MIBs will be seen in 1340 INC alarms with OID names instead of numbers.
5-88 April, 2009
Configure
DNO
Performing DNO from the NE Management Form
The DNO command performs auto-discovery of equipment inventory which is used to display equipment views and is used in the assign database.
Upon completion of the addition of a new network element, a DNO should be performed once the communication to the NE is established. Located at the bottom of the NE management form is a NE Link status field.
The field will by highlighted in blue if 1340 INC is NOT currently communicating with the selected NE, light blue if the NE is in the disabled (DSBL) state, or green if 1340 INC IS communicating with the selected NE.
When the communication state is UP (green) click the Update DNO button located at the bottom of the form. Upon completion of the DNO operation the user will be presented with an Update DNO message box stating that the “DNO completed successfully.” or “DNO completed with errors.” If the DNO operation fails then the user should try to perform the DNO query via the 1340 INC Cut Thru as described below.
The DNO operation can also be performed from the Equipment View form and the Provisioning Management (assign/release) form.
Performing the DNO Command via INC Cut Thru
The DNO command can be executed with a command by selecting the 1340 INC Cut Thru option from the
Admin pulldown. Performing the DNO function by hand would be useful if the DNO failed when performed from the NE Management form via the Update DNO button. Clicking the Update DNO button sends a specific set of queries to the specified network element. If any one of the DNO queries fail, then the overall
DNO operation would be unsuccessful. Launching the DNO command from the Cut Thru command line would allow the user to see which query failed and why.
At the Cut Thru input command line type: dno -n NE-id [-v]
-v = verbose mode
April, 2009 5-89
Configure
Once the DNO has completed successfully (via the GUI or the Cut Thru), the user may then select the <Card
Inventory> button located at the bottom of the NE Management form to display card specific information for the NE.
Columns displayed will vary based upon the type of Network Element being reported on
NE Specific Information- Tellabs 5500
DNO on a Tellabs 5500 can be done on a per shelf basis. It is not required to run the DNO on all of the shelves at any one time. To execute a shelf level DNO execute the following steps:
• Select the Equip View choice from the node drop down menu (or the NE Mgmt form for the node)
• Right mouse click on the specific shelf that requires the DNO to be run.
• Select the Shelf View item from the drop down menu.
• Select the Update DNO button on the Shelf View form.
5-90 April, 2009
Configure
NE Notification
The NE Notification feature is available in CNM mode only and is used to send maintenance information to aliases who have facilities assigned on the specified NE. In order for the messages to be received, the aliases must have the checkbox “Recieve NE Notification” selected in their definition on the Alias Management form. 1340 INC will then be able to associate the defined alias with the e-mail address to which to send the notification.
Figure 10-1. NE Notification
Fields:
• NE - The network element that the outage will affect
• Date/Time - The date and time of the expected outage
• Expected Outage - amount of time in hours and minutes that the specified NE will be down
• Contact Info - free form text box. Typically, the name or e-mail address of the person sending the notification message.
April, 2009 5-91
Configure
• Information - free form text box, allowing user to enter additional information concerning the expected NE outage
5-92 April, 2009
Configure
Protection
The protect command provides facility/channel protection. Facility/Channel protection is the capability of automatically rerouting a circuit when a Carrier Group Alarm (CGA), also referred to as Facility (FAC), or an Equipment (EQU) condition has been identified by Integrated Network Controller.
The protect command triggers a command sequence based on a specified alarm type. The command entered in the Command: field will be scheduled for execution wait_time seconds after the alarm has occurred. If the alarm idles within the period given, the scheduled protection command will be cancelled and will remain as the protection for the specified channel(s). If the protection command executes, the protection entry is removed from the data base.
Figure 10-2. Protection Management
April, 2009 5-93
Configure
Protection Creation
In the example below, for user “rgwuser”, the Service View ‘N2501_ls.41345.1 is the facility protected, the
Wait Time has been set to 1 minute, the Alarm Type is set to All (FAC and/or EQU), and the Command ‘db restore’ is the protection macro. In the event an FAC or EQU alarm occurs and does not clear within 1 minute from time of receipt, the macro “db restore” will execute.
Figure 10-3. Protection Creation
5-94 April, 2009
Configure
Protection List
The Protect List is used to display the list of protected facilities, or to remove circuit protection for a given user and facility and may be filtered by specific user.
Figure 10-4. Protection List
Column Definitions:
• ID - a Integrated Network Controller generated identification number
• Service View - the Service View of the facility being protected
• Type - Alarm type defined in the protection creation
• Delay - the amount of time the alarm must be in before the protection command defined is executed
• Command - the command to be executed
April, 2009 5-95
Configure
Navigation Drop Down List:
• Unprotect - The unprotect command is used to remove protection from a channel or facility which has been configured for protection using the protect command. To remove protection from a channel/facility highlight the desired facility and select Unprotect. Integrated
Network Controller will inform you if the unprotect was successful or if there was an error. If a command is queued to be executed, the unprotect command will “dequeue” it and remove the request from the database.
5-96 April, 2009
Configure
Scheduled Commands
Scheduling commands is a function which allows a user to set up a one time or cyclic schedule for command execution. Scheduled commands are used to connect circuits, disconnect circuits, move bridged units, etc.
For example, connecting a college professor’s lecture to a remote college campus via video conference could be scheduled every day at 11:00 AM. A T1 to the professor’s location could be connected to a T1 to the remote campus. A second scheduled command could be set up to disconnect the two T1’s every day at
12:00 PM.
Figure 10-5. Scheduled Command Management
April, 2009 5-97
Configure
Command Scheduler
The Command Scheduler allows the user to set up the specific schedule and command to be executed.
Figure 10-6. Command Scheduler
Fields:
• User - user that the command will be executed for
• Time (Required) - Slide bar entry that indicates the time of day that the command will be executed.
• Day - Drop down list used to select a day of the week. Would be used if a command were being scheduled for every Monday or every Friday, etc.
• Date - Slide bar entry used to set a particular date for command execution.
• Cycle - If it is desired to have the command executed more than once, these options are used to set the cycle
•
None - No cycle, command will be executed one time only
5-98 April, 2009
Configure
•
N Minutes - Command will execute every “N” minutes. Enter the number of minutes in the Minutes field.
•
Hourly - Command will execute once an hour beginning with the time set in the
Time field, then 60 minutes later, etc.
•
Daily - Command will execute once a day at the time set in the Time field.
•
Weekly - Command will execute once a week using the Day or Date field and the
Time field.
•
Weekdays - Command will execute every week day, Monday through Friday.
•
Weekends - Command will execute every week end day, Saturday and Sunday.
• Minutes - Used only if the Cycle option, N Minutes, is selected. The number of minutes between command executions is entered here. This value can be from 1 to 32000.
• Contid - (contingency ID) allows the user to associate a command with a contingency group.
This group ID can range from 1 to 99. Any command within a contingency group will not execute unless the previously scheduled command within the same group executes successfully. If the command in the contingency group is delayed, all subsequent commands will be delayed until that command executes.
• Command - Required field containing the command that will be executed. This field can be up to 256 characters long.
April, 2009 5-99
Configure
Command Schedule List
The Command Scheduled List is the list of commands which have been scheduled to run. Select the desired user from the User List drop down list and select the <Search> button. The scheduled commands for the selected user are now displayed.
Descheduling a command is performed when a scheduled command is no longer needed. To deschedule a listed command, highlight the command and select Deschedule from the navigation list. The command is now removed from the schedule.
Figure 10-7. Command Schedule List
5-100 April, 2009
Configure
Subpartition Management
Use of SubPartition Management is an option which is enabled on GUI forms by the
USE_SURVEIL_PARTITION system define, and is disabled by default. The Subpartition Management form provides the ability to change the surveillance state of already assigned facilities. Facilities can be assigned to different partitions (1 through 7) and/or to a different usage state (Surveill or Config). What was previously subpartition 8, is now reserved as the surveillance partition. All facilities, not part of other partitions by default, are assigned to this partition called the SurvOnly partition. Within this partition, a facility can be configured for Config (which gives a customer access to all 1340 INC provisioning and monitoring features) or Surveil (which restricts the customer to surveillance of the facility only). A Subpartition Report is provided to display the information in each partition (1-7) and the surveillance partition. In addition, the facility report status column will also flag facilities which are set for surveillance only. Unless overridden at assign time, or changed by the Subpartition form, all assigned facilities will assume the state as set by the
“Default Assignments to Surveillance Only”). Additionally, there
are options on the Assign/Release Management forms (See
) for assign and populate to set, or un-set, the surveillance state of a particular facility. The choices are Default (assume the default setting of the NE), Yes (set the facility to surveillance only) or No.
Figure 10-8. Subpartition Management
April, 2009 5-101
Configure
Fields:
• User - user whose subpartition is being configured
• NE - NE on which the facility being managed is located
• Level - level of the facility (DS0, STS1, etc.)
• Service View - service view of the facility being configured
• Partition Index - partition that the facility is assigned to
• Usage - Suveil (for facilities that are tagged as surveillance only) or Config (for facilities that allow configuration capability)
5-102 April, 2009
Configure
Tie
Tieing is used to associate one end of a facility on an NE with the other end of the same facility which terminates on another NE. After facilities are tied in the 1340 INC database, the GUI will display the facility as a line between the two network elements.
Tie Management
Figure 10-9. Tie Management
April, 2009 5-103
Configure
Tie
Figure 10-10. Tie
Fields:
• From NE - the NE ID of one of the network elements where the facility terminates
• From View - the physical digroup or AID that terminates in the “From NE”
• External Tie - Selection of this checkbox provides console administrators with the ability to enter database “ties” representing facilities that link 1340 INC supported network elements and unsupported network elements. When the External Tie check box is selected, the “To NE” and “To View” fields below it become text fields where the administrator can enter information pertaining to the unsupported NE. The entered information will be displayed on the corresponding Trace Form, Linked Report, and Tie Report.
• To NE - the NE Id of the network element on the other end of the facility
• To View - the physical digroup or AID that terminates in the “To NE”
5-104 April, 2009
Configure
• Available Aids - a list of facilities that are available for tieing
• Tie ID - 50 character field designed to be used for a provisioning circuit ID. This field will allow for the association of a circuit ID with a tie.
• Type - used to indicate in the 1340 INC database if a tie between two elements has additional elements in between that are not represented in 1340 INC. There are two choices for the tie type:
•
Direct - used to indicate that the tie is between two network elements that are
“next to” each other with no other elements in between
— Default - type of Direct tie. This is typically used with SONET network element types and set via the Neighbors tab on the NE Management form.
•
Indirect - used to indicate that the tie is between two network elements that are not “next to” each other because there are one or more additional elements in between them
April, 2009 5-105
Configure
Untie
The Untie form allows the user to remove or “undo” an existing tie. Only the From NE and From View fields need to be populated since 1340 INC has a database entry for the existing tie and therefore has a record of the To side. The External Tie checkbox must be selected if the user is removing an external tie.
Figure 10-11. Untie
5-106 April, 2009
Configure
User Info
1340 INC provides secure user database separation allowing customers of telecommunication providers to access, monitor, and configure their communication networks.
User databases securely separate users from each other, and protect the network elements. Users are not able to perform any network management function on any facility that is not assigned to their database. Users are not able to perform functions on network elements that are not allowed by the 1340 INC application.
When a user is “created”, a secure database is defined in the 1340 INC system, and a user ID and password are associated with the database. This database is only accessible by the Console administrator and the user who is provided with the user ID and password for the database.
When the database is initially created, it is empty. Console assigns facilities to the user database that represent real network facilities that belong to the user. When the user logs into 1340 INC, he can only view and manage those assignments. He will only receive alarms that are on facilities in his database. He is not able to manage any facilities that are not assigned to him.
The command set available to a user is a subset of the commands available to the Console administrator.
Users do not have direct access to network elements nor do they do not have the ability to add assignments to their database.
The following functions related to User management can be executed via the User Info Form:
• Add a User
• Modify an existing User’s password, User ID, login limit, contact information, allocated symbols, or allocated scheduled commands
• Delete a User
• View information about a User
April, 2009 5-107
Configure
Figure 10-12. User Info - General Tab
Form Description:
• User List - located on the left hand side of the User Info Form. This contains a list of any users that are currently defined on the 1340 INC Host.
• Tabs - tabs displayed will be driven by the feature set defined for 1340 INC. The User Information Form can have the following tabs:
— General - used to perform User Management functions or as a report for viewing information about a selected user
— Facilities - used as a report to view statistical information about a selected user’s database assignments, if applicable
— Units - used as a report to view statistical information about a selected user’s subrate database assignments if applicable
— NAVIS Customers - used for ATM/FR users. Further description of this tab can be found in the Integrated Network Controller ATM/FR Supplement.
5-108 April, 2009
Configure
— ATM/FR - used for ATM/FR users. Further description of this tab can be found in the
Integrated Network Controller ATM/FR Supplement.
— Metro Ethernet - used for ATM/FR users. Further description of this tab can be found in the Integrated Network Controller Metro Ethernet Supplement.
Fields:
• User ID - (Required) - the name of the user database and the user login ID
NOTE:
USER ID AND PASSWORD RULES:
n n n n
They must be at least 6 characters in length, but cannot exceed 8 characters in length.
The first character must be alpha, and the remainder can be made up of any combination of alphanumeric characters and the special characters
“_” (underscore), “!” (exclamation), “.”(period), and “$” (dollar sign).
Use of spaces, caret (“^”), at (“@”), pound (“#”), colon “:”, and the ampersand (“&”) is prohibited.
Passwords cannot be repeated. That is, a previously used password cannot be re-used.
• Owner - (Required) - usually the same as the User ID, but can be a different ID for representing the owner of the user database
• User Name - (Required) - full name of the person or company using the user database
• Password - (Required) - password for the user ID
• Verify Password - (Required) - password entered again for verification
• Address1 - address field for the user, intended use is for the user’s street address
• Address2 - additional address field for the user, intended use is for the user’s city, state, and zip
• Contact Name - name of a contact person responsible for the user database
• Telephone - telephone number for the contact person
• Fax - fax number for the contact person
• Comment - any additional comments about the user
• Number of Logins - (Required) - the number of simultaneous logins allowed for the user
• Number of Aliases - (Required) the number of end-user aliases allowed per user
• Symbols
— Allocated - the number of macros the user can have
— Used - the number of macros the user has used
April, 2009 5-109
Configure
• Scheduled Commands
— Allocated - the number of scheduled commands the user can have scheduled at a time
— Used - the number of scheduled commands the user currently has scheduled
Buttons:
• Select - populates the form with information about the user highlighted in the user list column
• Add - adds the user to the 1340 INC Host
• Update - updates the user information for the selected user
• Delete - deletes the selected user from the 1340 INC Host
• Merge - allows the database from one customer to be merged into the database of another.
Once the merge has completed successfully, the “from” customer may be deleted.
NOTE:
The Merge function will only take place if the service names of the customers being merged are different.
• Partition - a display of partitions that exist for the selected user
• Clear - clears the fields on the form
Adding a User
1.
Fill in all required fields: User ID, Owner, User Name, Password, Verify Password,
Number of Logins
2.
Fill in optional fields with appropriate information as desired
3.
Select the <Add> button
Modifying an existing User
Use this procedure to accomplish any of the following tasks:
— Reset a User’s Password
— Change a User’s ID
— Update a User’s Contact information
— Update a User’s login limit
— Modify the number of allocated symbols for a User
— Modify the number of allocated scheduled commands for a User
5-110 April, 2009
Configure
1.
Highlight the User in the list on the left side of the form, then click the <Select> button
2.
Modify the information for the User as desired
3.
Select the <Update> button
NOTE:
A user may also change their own password via the Admin menu -> Change Password function.
Deleting a User
1.
Highlight the User in the list on the left side of the form, then click the <Select> button
2.
Select the <Delete> button
NOTE:
Users with database assignments can not be deleted from the 1340 INC Host. All database assignments should be released prior to deleting a User.
User Access Throttling
1340 INC can be configured to throttle user access. That is, the system can be set up so that only a specified number of logins are permitted at any one time, and when the threshold amount is exceeded, the user will recieve an error message indicating that too many login attempts have been made. Please see the 1340 Inte-
grated Network Controller Installation Guide for details on configuring this feature.
April, 2009 5-111
Configure
5-112 April, 2009
View
Chapter Contents
•
•
•
•
•
•
Alarm Age/Filter Tab on page 6-36
•
•
Miscellaneous Tab on page 6-41
•
•
April, 2009 6-1
View
View Tab
The View Tab allows the user to set their system display and alarm retrieval preferences, as well as define the user information that will be available to them.
Figure 6-1. View Tab
6-2 April, 2009
View
Map View
The Map View allows the user to display their network with a user defined graphical background (usually a map). The colors of the display are set via the Preferences -> Map tab. This form is auto-launched upon selection (that is, there is no need to select the <Search> button after selecting Map View for the first time).
Figure 6-2. Map View
Selected filters are saved from session to session for a user. It should also be noted, that if the user changes to the Table View option, the selected Refresh Interval value is shared.
April, 2009 6-3
View
Checkboxes:
Selection of any of the following choices will dictate the information displayed
• Filter by Tree - Selection of this box allows the user to display defined NE groups and subnetworks. Selection of this filter will add the Show Groups checkbox to the Launch
Area. Initially, the NE Groups and Subnetworks choices will be shown with an accompanying “+” sign. Selection of the “+” sign will display all defined entities of that type.
There may also be another item in the tree called “Ungrouped NEs”. Selection of this checkbox will display all network elements that are not currently part of a Subnetwork or
NE Group.
Figure 6-3. Filter by Tree
6-4 April, 2009
View
When the Show Groups checkbox is selected (followed by selection of the <Search> button), those “groups”
(NE Groups and Subnetworks) that are currently listed in the Network View box in the launch area will be displayed.
Figure 6-4. Show Groups
April, 2009 6-5
View
Once a specific NE Group or Subnetwork has been selected (via selection of it’s associated checkbox followed by selection of the <Search> button), then only those selected items will be displayed in the Map
View display area
Figure 6-5. Filter by Tree - Selected group
NOTE:
When the user has selected Filter by Tree (is in Filter by Tree mode), the node drop down menus will no longer contain “grouping” menu items (i.e. Group Subnetwork,
Ungroup Group, etc.)
• Reset Tree - Allows the user to set the tree back to it’s starting point (i.e. subnetworks or groups have been opened and the user wants to go back to everything being unopened).
• Show Links - displays links (facilities) from network element to network element, or network element to user nodes
6-6 April, 2009
View
• Show Group Links - displays links between groups if either end of the link is a group
• Show Labels - displays the label chosen (NEID, TID, etc.) in the Preferences -> Map tab
• Show User Nodes - displays user node associated with each NE. User nodes represent the location where an end-customer facility starts.
• Only Nodes in Alarm - Displays only nodes in alarm
• Group NEs - Displays NEs, user nodes, and facilities that have been defined as members of a group as one NE group icon.
• Group SBNKs - Displays all defined subnetworks as individual grouped icons.
Selection of the <Search> button will refresh the Map view.
Display Drop Down Lists (for Map View):
• Icon Size - Allows the user to choose the size of the icon in the map view.
• Background - Allows the user to choose a background for their network display.
NOTE:
If the background selection is one of the Grid choices, (i.e. grid.10x10, etc.), then the user can zoom to a specific node area by double clicking the grid box that the node is located in.
Buttons:
• Regroup - Allows users to go back to a grouped map view (that is, if the Group NEs and/or
Group SBNKs checkboxes are selected and the user has ungrouped any of the groups, selection of this button will go back to a Map View displaying the group icons)
More Options/Less Options:
Display Drop Down Lists:
•
Columns - Allows the user to define the number of columns that NE data will be displayed in.
•
Order - Allows the user to select the order by which the icons will be aligned.The icons can be aligned in Align ID/Alarm Status, Align ID/Node Info, Alarm Status, Node ID, Node Name, or Location order.
•
Alignment - Allows the user to select either Top (aligns in rows), or Left (aligns in columns).
•
Density - Allows the user to select Minimum or Maximum for proximity of icons in the display.
April, 2009 6-7
View
Buttons :
•
Align Nodes - The <Align Nodes> button is used to align NEs, Grouped Subnetworks, or NE Groups in a user defined manner. This is done in order to better organize the appearance of icons on the map display. The icons can be aligned from the top or left side of the map display with a density of maximum or minimum.
• Align End Locations - Moves all end locations below and to the left or right of each network element. If the user changes the icon size, the <Align End Locations> button needs to be reselected.
• Topology Refresh - Selection of this button will re-download the map information so as to include any database information that has changed which affects the user's display. This button will turn red when an event occurs that requires the user to refresh the topology
(i.e. addition/deletion of a node to/from the map).
•
Topology Refresh Auto checkbox - Selection of this checkbox will run a topological refresh every sixty minutes. Contact your system administrator for infomation on setting up this feature. Note that a topological refresh is different from the
Auto Refresh because the information is re-retrieved (much like logging in initially), as opposed to being pulled from the existing database copy.
Figure 6-6. Topological Refresh - Auto checkbox
Auto Refresh/Refresh Interval
Some forms allow for an automatic refresh of the data that is currently displayed. When the Auto Refresh checkbox is selected, the associated form will be automatically updated. The Refresh Interval is the value (in seconds) that will elapse before the next update. To change the Refresh Interval, the Auto Refresh box must be de-selected and then re-selected.
6-8 April, 2009
View
GNE Indication:
The GNE of each subnetwork displayed on the map will be indicated by the white icon adjacent to the NE that has been defined by the user as the GNE.
Figure 6-7. GNE Indication
April, 2009 6-9
View
Multi-Level Maps:
This feature, which is associated with the Background and Icon Size values, allows users to define different map backgrounds and icon sizes based upon the NE Group level they are viewing. In the following example,the user views their NEs with the United States acting as the background and their icon size set to
Medium.
There is a Group defined as Texas Subnetworks displayed in Texas.
Figure 6-8. Multi Level Maps - First Level
6-10 April, 2009
View
When the user selects Ungroup Groups from the group drop-down menu, the following map is displayed showing the subnetworks at the next group level. This map uses a jpeg picture file of Texas as it’s background with the icon size defined as Large.
Figure 6-9. Multi Level Maps - Second Level
When the Dallas subnetwork (dallas sbnk) is then ungrouped (via the Ungroup Subnetwork item in the drop-down menu), the following map is displayed.
April, 2009 6-11
View
This map shows node 812 and uses a jpeg picture file of the city of Dallas as it’s background with the icon size again defined as Large.
Figure 6-10. Multi Level Maps - Third Level
These background files can be .jpg or .gif files that are stored on the web server machine (machine from which the WEB GUI is loaded). The files must be of the form name.jpg (i.e. texas.jpg). With each .jpg or .gif file, there also needs to be a file stored on the web server that contains the associated Latitude and Longitude of the form name.xy (i.e texas.xy). The format of this file will be xxx.yyyyyy where xxx is between 1 and
180 (degrees), and yyyyyy is from 000000 to 999999 (minutes and seconds). These value are the top left hand corner and lower right hand corner of the picture file (gif or jpg) expressed as latitude and longitude.
i.e. If the values are 30.826780, -87.714843:25.085988,-80-002441, the upper left corner latitude is
30.826780, the upper left corner longitude is -87.714843, the lower right corner latitude is 25.085988 and the lower right corner longitude is -80-002441.
6-12 April, 2009
View
NOTE:
The absolute value of the negative numbers are used when displaying the maps
Please see the Integrated Network Controller Application Installation Guide for additional directions for setting up these files.
April, 2009 6-13
View
In addition to the files that are set up on the webserver, the Latitude and Longitude values, associated background picture file, and selected icon size must be entered on the forms that pertain to the NE Group or Subnetwork being displayed. The Latitude and Longitude must also be entered on the individual NE
Management form for NEs being displayed at the specified level. The forms displayed below show the NE
Group Information , Subnetwork Information and NE Management forms from the US/Texas/Dallas example above.
Figure 6-11. Multi Level Maps - NE Group Information
6-14 April, 2009
View
Figure 6-12. Multi Level Maps - Subnetwork Information
April, 2009 6-15
View
Figure 6-13. Multi Level Maps - NE Management Form
NOTE:
If the choice “Current” , located in the Background drop down menu is chosen, selection of the associated item will open up the group, subnetwork, or NE with the current background used (i.e. instead of Texas, the Ungroup Group of the Dallas Subnetworks would use the United State background).
6-16 April, 2009
View
Map Toolbar Icons:
These icons allow the user to manipulate the nodes on their Map display.
• Select - The Select mode is the default mode for controlling the display area. For example, if the user performs the ‘Move’ function, the current mode would be ‘Move’. Choosing the
Select icon will change the current mode back to Select.
• Previous View - This icon is used to change the map display back to the previous zoom level view. For example, if the Magnify option is used to magnify the southeast United States, performing the PREV function will change the map back to the entire United States view.
• Zoom In - The Zoom In icon is used to enlarge a region of the map area. To magnify a map region, select the Zoom In icon. Then, position the mouse above and to the left of the target area, hold and drag the mouse below and to the right of the target area and release the mouse button. If the magnification is too large, reselect the magnify option and repeat the process mentioned above. When the magnify option is no longer needed, perform the
‘Zoom Out’ function.
• Zoom Out - The Zoom Out function changes the map area back to the user’s default map.
April, 2009 6-17
View
• Center Map- Selection of this button, followed by selection of a node on the map, will realign the map so that the selected node is in the center of the map field.
NOTE:
When this icon is selected, the system will stay in “center” mode, giving the user the ability to “pan” their map view until the Center Map function is terminated (via the
<Select> icon).
• Find Node- Allows the user to find a specific node, subnetwork, or NE group on the map.
Once the entity is chosen from the appropriate drop down list, the user selects the <Find> button and a white circle will be displayed around the entity. Selection of the <Back> button will return the user to the Map toolbar icons. When the Find Node operation is selected, the user may also use the Zoom option (the <Zoom> button will be displayd along side the <Find> button). When an NE is selected, followed by selection of the
Zoom button, INC will find the entity being searched for, and also automatically expand the group it is contained in, and zoom to the location on the map that contains that group of NEs.
• Grab Nodes- If the map display has been re-sized (i.e. using the Magnify function), the
<Grab> button will bring all of the nodes belonging to the user to the center of the new map display.
6-18 April, 2009
View
• Move Nodes - A GUI user may reposition user nodes and network element icons in the display area at any time. To move an icon (node) to a different location on the map display, select the Move icon. Then, select-and-drag the icon to its new position and release the mouse. The GUI will remain in the Move mode allowing the user to move multiple network elements and user nodes without having to reselect the Move icon. When all nodes have been moved to their desired location, the user can choose the ‘Select’ button to return the GUI to the Select mode. If several (more than one) NEs are being moved one after another, a 3 second pause (with no clicking) will result in the map being redrawn with the new NE locations. A gray shadow of each NE will show it’s new location during this period, allowing the user to better position each NE in the desired location.
NOTE:
To save the new coordinates of the moved icon(s), the ‘Save’ button must be selected before logging out.
NOTE:
When a user network is downloaded from 1340 INC to the GUI for the first time, all nodes for the network selected are displayed, one on top of the other, in the center of the display area. The GUI user should use the <Move> button to position the network elements and user nodes to the desired locations in the display area or the <Align> button to organize the map display.
• Reset Nodes- Resets the X Y coordinates for any icon to the most recently saved values.
April, 2009 6-19
View
• Save Map - The Save function is used to save network element data. NE data is defined as the placement of all icons on the map display. If any icon is moved and the Save function is performed, the new coordinates of the icons will be saved in 1340 INC. In the event the user forgets to save the data, the user will be prompted to save NE data upon logging out.
NOTE:
In some cases, aliases may not be granted permission to save NE locations on the Map
Display. In these cases, the user may still move NE locations, but the positioning will only be for the current session and the Save Map icon will not be displayed in the Map
Toolbar. Please see the Integrated Network Controller Application Installation Guide for instructions on setting this privilege.
• Print Map - Allows the user to print a hardcopy version of the Map view.
• Legend - Selection of the <Legend> button will display a legend of network elements and facility types.
NOTE:
These icons can be customized to be Icons Only (as shown), Icons and Text, or Text
Only depending upon user preference. Please see the Integrated Network Controller
Application Installation Guide for instructions on setting this preference.
6-20 April, 2009
View
Node Navigation Drop Down List:
• NE Details - Displays NE related information (i.e. TID, Type, NEID, etc.)
Figure 6-14. NE Details
• Alarm List (Current) - Displays the Alarm List report showing current alarms for the selected
NE
• Assign - Displays the Assign/Release Management form for the selected NE
• Assign Report - Displays the Assign Report for the selected NE
• Comm Group Report - Displays the Comm Group report for the selected NE
April, 2009 6-21
View
• Connect - Displays the Connection Setup pop-up window. This pop-up allows the user to select the Type, From NE, Ring, STS#, and To NE values. When the <Connect> button is selected, the Circuit Management - Connection Request form will be pre-populated with the selected values. It should also be noted that based on the Type and Ring chosen, only available NEs will be included in the drop down list, and unavailable NEs will be grayed out on the map.
Figure 6-15. Connection Setup
• Connect Report - Displays the Connect Report for the chosen NE
• Cut Thru to NE - Opens a cut thru session to the selected NE
• Disconnect - Displays the Circuit Management - Disconnection Request form for the selected
NE
• Equipment View - Displays a picture of the selected NE. The picture will reflect circuit packs as found in the card database, if a successful DNO query has been executed, or, the cards displayed will reflect those facilities assigned to the user in 1340 INC if a DNO query has not been performed. Pack details may be displayed by selecting a card (via the left
6-22 April, 2009
View mouse button) and choosing the Card Details drop down menu item. This will display information such as circuit pack type, alarm states, CLEI codes, etc. The view may be expanded or reduced via the Size drop down filter.
Figure 6-16. Equipment View
Navigation (from Equipment View):
•
Alarm List - Displays the Alarm List Report for the selected slot
•
Card Details - Displays the card specific information for the selected card
•
Card Inventory Report -Displays the Card Inventory Report for the selected NE
•
CLI Interface - Opens a telnet window allowing the user to execute command line input (on NEs that support the CLI interface)
•
Connect Report - Displays the Connect Report for the selected slot (facility cards only)
•
Equipment Management - Displays the Equipment Management form for the selected NE
•
Ethernet Management - Displays the Ethernet Management form for the selected
NE
April, 2009 6-23
View
•
Facility Report - Displays the Facility Report for the selected slot (facility cards only)
•
NE Management - Displays the NE Management form for the selected NE
•
Utilization Report - Displays the Utilization Report for the selected NE
NOTE:
The Equipment View on the Alcatel-Lucent 1678 offers console users the ability to execute a cut thru to the Command Line Interface (CLI) for the ES64 card, for ethernet provisioning. Running DNO on this NE will discover the IP information of associated ES64 circuit packs and thus allow attempts to telnet directly to the CLI. This implies that the
PC browser that 1340 INC is running on, has telnet access to the 1678 NE.
• Facility Report - Displays the Facility Report for the selected NE
• Group Subnetwork - Groups the selected NE into it’s defined subnetwork
• Linked Report - Displays the Linked Facility Report for the selected NE
• NE Management - Displays the NE Management Report for the selected NE
• NE Usage - Displays the Node Usage Report for the selected NE
• NE User - Displays the NE User List for the selected NE
6-24 April, 2009
View
Figure 6-17. NE User List
April, 2009 6-25
View
• Ring Layout - Displays the Ring Layout for the selected NE. This is a graphical representation of the ring to which the selected network element belongs. The icons in the display will reflect the current alarm status of the network element when the form is opened.
NOTE:
Holding the mouse over the NE icon will show the “tip” containing the TID/NEID, NE type, and the associated tie information. If a TIE ID is associated with any of the ties displayed, it will be shown as part of the layout and will also be shown as part of the associated “tip” .
Figure 6-18. Ring Layout
Filters (for Ring Layout):
•
NE - Network Element for which the Ring Layout is being displayed
•
Ring # - ring number for which the Ring Layout is being displayed.
6-26 April, 2009
View
•
Ring STS # - STS number for which the Ring Layout is being displayed
•
Ring TS # - timeslot number for which the Ring Layout is being displayed
•
Show AIDs - allows the user to display or “hide” the AIDs on the Ring Layout display
NOTE:
In the case of DMX network elements, this value will be in the form of an AID (Access
Identifier)
•
Bay # - bay number for which the Ring Layout is being displayed
•
Shelf # - shelf number for which the Ring Layout is being displayed
Node Navigation Drop Down (from Ring Layout):
•
Alarm List (NE) - Displays the Alarm List Report for the selected NE
•
Connect Report - Displays the Connect Report for the selected NE
•
Facility Report - Displays the Facility Report for the selected NE
•
Linked Report - Displays the Linked Report for the selected NE
•
NE Usage - Displays the NE Usage Report for the selected NE
• Subnetwork Report - Displays the Subnetwork Report for the selected NE
April, 2009 6-27
View
• Trace - Displays the Trace Setup pop-up window. This pop-up allows the user to select the
User, NE, and Service View that they wish to trace. When the <Trace> button is selected, the Trace form will be displayed.
Figure 6-19. Trace Setup
• Utilization Report - Displays the Utilization Report for the selected NE
• Watch - Opens the Watch setup window for the selected NE
NOTE:
If a Network Element has been made part of a group,or a grouped group, then additional drop down items will exist for those functions.
6-28 April, 2009
View
Preferences
The Preferences tabs allow the user to define their choices for various GUI display and behavior items.
Figure 6-20. Preferences
Buttons:
• Apply - Applies changes that have been made on the Alarm Colors, Map and Miscellaneous tabs locally (for the current session), but does not save the changes to the database permanently. For the changes to be seen, the user must refresh (via the <Search> or <Topology Update> buttons). When logging out, the user will be asked if changed preferences should be saved permanently.
• Save - Saves changes to the database permanently
NOTE:
On the Alarm, Alarm Age/Filter, and PM tab, any changes made must be Saved (Select the <Save> button) for the changes to take effect in the current session. Selecting
<Apply> will not make the changes effective in the current session.
April, 2009 6-29
View
• Defaults - Returns filter values to their default value
6-30 April, 2009
View
Alarm Tab
Figure 6-21. Alarm Tab
Historical Alarm Filters
The Historical Alarm Filters control the output of the Problem Alarms Report and the Historical Alarms
Report found under the Alarm tab. Select the desired alarm types to be viewed and select the Save button.
Auto Clear QoS and Alerts
The Auto Clear QoS and Alerts feature allows the user to set a time (in minutes) that defines the number of minutes a Qos or Alert will stay as an active alarm and on the New Alarm List. When the time is reached, the alarm will be automatically cleared, the Alarm Central icons will be updated (stop blinking), and the NE icon located on the Map View will also be updated.
Each QoS or Alert alarm is, of course, treated individually, and will assert and clear within the time selected.
However, the Alarm Central icon may continue to blink, if, during the selected time after an alarm asserts, another alarm of the same type is asserted. It should also be noted that this feature works in concert with the acknowledgement of alarms. That is, if an alarm is acknowledged on a node, and therefore displays the ACK
April, 2009 6-31
View color, followed by an assert and clear of a Qos or Alert, the node will go back to the ACK color (or the highest severity alarm currently present on the node).
New Alarm Timer
The New Alarm Timer allows the user to determine how often (in seconds), that newly occurring alarms will pop up on their display.
New Alarm Sound
When selected, the New Alarm Sound indicates that a user will hear an audible alarm sound when a new alarm is asserted or cleared.
Alarms are categorized by type (EQU,FAC,NE (Link), QoS, Alert, Misc, and SYS), as well as by severity
(CR, MJ, MN, Other). Each alarm also has two states (Assert and Clear). Via sound files (that must be stored as .wav form files), the user can associate a specific sound with each type/severity and assert/clear occurrence.
The .wav files must be stored in /usr/cnc/web/app/sounds on the 1340 INC GUI server. There are default
.wav files for both alarms and clears (called alarm.wav and clear.wav respectively) that are included as part of the 1340 INC installation. However, if a user would like to use other .wav files, the files must be named using the following format in order to associate each alarm with the correct .wav file.
Type_Severity_alarm.wav or Type_Severity_clear.wav
So, if a user wanted a specific sound for a Critical Equipment alarm, the file would be named
EQU_CR_alarm.wav. Likewise, a clear would be named EQU_CR_clear.wav.
When more than one alarm/event occurs simultaneously, alarms are “bundled” and passed to the GUI all at once. In this case, the sound file associated with the alarm of the highest severity will be heard. When this occurs, therefore, alarms/events of lower severity will not be represented via their associated audible notification. It is recommended that use of the audible alarm feature be used to supplement visual/alarm indicators, not as a replacement.
New Alarm Icon
The New Alarm Icon setting allows the user to see an alarm icon associated with an NE, when a new alarm is asserted on that NE. The drop down list allows the user to choose the amount of time (in seconds) that the icon will stay on. When an alarm is asserted in INC, the icon will appear on the top right hand corner of the
NE icon on the Map or Table View. The NE drop down menu from the NE in alarm will then have the choice
“Alarm List (New)” allowing the user to display alarms that have been asserted since the previous view.
6-32 April, 2009
View
Figure 6-22. New Alarm Icon
Maintenance Alarms
The Maintenance Alarms filters allow the user to process or not process alarms which have been put into the maintenance state. The default expiration fields (Days and Hours), are used when the user selects an active alarm and places it into the maintenance state. These values will keep the facility in the maintenance state for the defined duration.
Topology Alerts
Allows the user to choose to display Topology Alerts to the screen as they occur.
April, 2009 6-33
View
Alarm Colors Tab
Figure 6-23. Alarm Colors Tab
Alarm Color
Alarm colors can be changed by the user. To change an alarm color, select the color to be changed, then select the color choice from the drop down list.
NOTE:
The “Acked” value will indicate that all alarms are acknowledged. When all active alarms on an NE are acknowledged then the NE alarm color will take on the selected
“Acked” alarm color. Likewise for the global status indicators, when all alarms of that category are acknowledged, the indicator will take on the selected “Acked” alarm color.
6-34 April, 2009
View
Alarm Text Color
When changing alarm colors, the alarm text color may also need to be changed so that the text is readable.
April, 2009 6-35
View
Alarm Age/Filter Tab
Figure 6-24. Alarm Age/Filter Tab
Process/Filter Alarms
The Alarm Age/Filter option allows the user to process or not process alarms and delay the display of an alarm. For example, if the user selects NO for the Process FAC alarms, the FAC icon on the Alarm Central display will change to black. Any black alarm icon in the Alarm Central region indicates that alarms are not being processed for the associated alarm category.
The FAC, EQU, NE Status, Miscellaneous and Sys Health alarm categories have an Age drop down list which has a range of 0 through 600 seconds. These alarm types have assert and clear alarm messages which are received from the network element. When the alarm asserts (comes into the GUI), the corresponding alarm icon will change to the appropriate alarm color. When the alarm clears, the alarm icon will change to the clear color. Choosing any number of seconds above 0 will cause the GUI to wait for that number of seconds after the alarm asserts before displaying the alarm. If the clear message is received within the selected
6-36 April, 2009
View number of seconds, the alarm icon will never change to the alarm icon color. If no clear message is received within the selected number of seconds, the alarm icon will change to the alarm icon color.
Each alarm category has a Filter choice box. If this value is set to YES, then the alarm category selected will use the additional Alarm Filters located in the Alarm Include Filters section of the form. If an individual alarm category, for example EQU, has the Filter choice set to NO, then the user will see all EQU alarms. If the value is set to Include, then the category will be filtered based upon the Alarm Include Filters. If the value is set to Exclude, then the category will be filtered based upon the Exclude Alarm Filters, and if the
Filter value is Both, then the category will be filtered through Include and Exclude filters.
NOTE:
These filters are used to filter new alarms to the GUI. Users can still see all alarms, regardless of the filter settings, via the Alarm List form.
Alarm Include Filters
If the user sets the Filter choice to YES for a specific category, then that category only will use the filters in the Alarm Filters section. The user will receive any alarm that matches the “YES” selections in this section.
Additionally, if the user enters a value in the Level Filter text box (i.e. T3), they will also see those level alarms displayed. Any alarm other than the category selected will display all SAs and NSAs, all Severities, and all Levels of their respective alarm categories.
Alarm Exclude Filters
This form allows the user to select specific alarms, by level and by atype (alarm type) that they do not want to see on their Alarm List display. Alarms will still be added to the 1340 INC database, but will not be viewed on the GUI. The user may select up to 50 alarms to be placed on the exclude list. The wild card character ‘*’can be used in either the Level or ATYPE field (* alone matches all strings, *ABC matches anything with ABC in the string, and ABC* matches anything beginning with ABC). Note that the Level and ATYPE fields are not forced to uppercase.
For these Filter settings to take effect, the <Save> button must be selected, the <Apply> button will not place the choices into effect.
April, 2009 6-37
View
Map Tab
The Map tab allows the user to set colors and labels for the display of the Map view.
Figure 6-25. Map Tab
Map Color
This is divided into the Map, Map Border, and Off Map and Map Text sections. Each value can be set to the color of the user’s choosing.
Node Label
This allows the user to choose which label type (NEID, TID, etc.) is displayed on the Map View. It does not affect the lables on the Table view.
6-38 April, 2009
View
Node Label on Alarm
This allows the user to show the selected node label type when the node is in alarm, even if the Show Labels choice is not selected on the Map View form.
Show Multiple End Locations
This field allows the user to display more than one end location node for each NE, if applicable.
NOTE:
The user must execute a <Topology Refresh> at the Map View in order to see this change take place.
Zoom to Subnetwork
If set to “YES”, when the user ungroups a subnetwork, their map display will “zoom in” and show only the nodes in that subnetwork.
Zoom to Group
If set to “YES”, when the user ungroups a group, their map display will “zoom in” and show only the nodes in that group.
Background
Allows the user to select the background that will be displayed when viewing the Map View
Icon Size
Allows the user to set the icon size that will be used on the Map View
April, 2009 6-39
View
PM Tab
Figure 6-26. PM Tab
PM Filters
The PM Filters affect the output of the Problem PM and Display PM reports. The user should select the desired filters and select the Save button located on the bottom of the form. After the Save has completed, the Problem PM and Display PM reports will reflect the selected filters.
6-40 April, 2009
View
Miscellaneous Tab
The Miscellaneous tab allows the user to set values for a variety of system parameters.
Figure 6-27. Miscellaneous Tab
Lines per Page
A count of how many lines the user wants to see per page on displayed reports
Pages per List
A count of how many pages of data the user wants grouped at one time in a report
Word Wrap
Shortens the length of lines in displayed reports such that information is continued on the next line.
April, 2009 6-41
View
Print Layout
Dictates how the graphics are sized for printing. The user must set their Page Setup locally for printing to match preferences
CSV Layout
This preference allows the user to either choose Text, which will write the output to a comma separated value file, or EXCEL which will write the output directly to a Microsoft® Excel spread sheet.
Trace Level
Used to turn up tracing to allow debugging of a GUI software trouble.
!
WARNING:
Users should not change the default Trace Level value unless instructed by a system administrator.
TimeZone
Allows users of ATM/FR, MEII, and Network Ethernet facilities to view data specific to them in the requested timezone. See the Integrated Network Controller Application Installation Guide for information on setting up the file that defines choices for this menu.
Security
The GUI has an automatic logout feature. If set to LOGOUT, this function will automatically logout the user after the specified period of inactivity
Security Timer
This is the value (in minutes) that a session must be inactive in order for the Security Lock (automatic logout) to take place.
Load Menu Selection In
Current Window - if set, all menu selections will load in the window the user is currently active in
New Window - if set, all menu selections will load data in a new window
NOTE:
This functionality can also be achieved using the New Window icon on the Main Screen.
6-42 April, 2009
View
Browse Log Lines Per Page
Allows the user to set the number of lines they would like to see displayed when viewing Browse Logs.
Start Screen
Allows the user to automatically display the chosen form upon login. Once the choice is made, the user must logout and login to see the choice take effect.
April, 2009 6-43
View
Table View
The Table View allows the user to display their NE information in tabular format. The user may select from a variety of filters to define the details of the display. This form is auto-launched upon selection (that is, there is no need to select the <Search> button after selecting Table View for the first time).
Figure 6-28. Table View
Selected filters are saved from session to session for a user. It should also be noted, that if the user changes to the Map View option, the selected Refresh Interval value is shared.
Filters:
• View - allows the user to select which NEs will be displayed based on communications and alarm state criteria.
• Label - allows the user to choose which label type the node will be identified by.
• Group - allows the user to display NEs in defined Subnetwork groups or NE groups.
6-44 April, 2009
View
• Columns - allows the user to choose the number of columns in which the NE data will be displayed
Find Node in Table
• NE - allows the user to search the table for a specific NE
• Group - allows the user to search the table for a specific NE group. Upon selection of the
<Search> button, the NEs in the group will be highlighted
• SBNK - allows the user to search the table for a subnetwork. Upon selection of the <Search> button, the NEs in the subnetwork will be highlighted
NOTE:
The “Find Node in Table” search feature is designed to run in a top-down fashion. That is, it will search for an NE first (if that field is populated), Group second (if that field is populated), and a subnetwork last (if the SBNK field is populated)
Column Definitions:
• Count - Number of items listed in the table
• Total NE - Number of NEs that are in the table (including those defined as part of a subnetwork or NE group)
• Up NE - Number of NEs that are currently Up
• Disabled NE - Number of NEs that are currently in the Disabled state
• Down NE - Number of NEs that are in a “Link Down” state
• NE in Alarm - Number of NEs that currently have an alarm condition
Navigation Drop Down List:
• NE Details - Displays NE related information (i.e. TID, Type, NEID, etc.)
• Alarm List - Displays the Alarm List report for the selected NE
• Assign - Displays the Assign form, with the selected NEs information pre-populated
• Assign Report - Displays the Assign Report for the selected NE
• Comm Group Report - Displays the Comm Group report for the selected NE
• Connect - Displays the Connect form, with the selected NEs information pre-populated
• Connect Report - Displays the Connect Report for the selected NE
• Disconnect - Displays the Disconnect form, with the selected NEs information pre-populated
• Equipment View - Displays the Equipment View of the selected NE
• Facility Report - Displays the Facility Report for the selected NE
• Linked Report - Displays the Linked Facility Report for the selected NE
April, 2009 6-45
View
• NE Management - Displays the NE Management Report for the selected NE
• NE Usage - Displays the Node Usage report for the selected NE
• NE USER - Displays the NE USER List for the selected NE
• Ring Layout - Displays the Ring Layout for the selected NE.
• Subnetwork Report - Displays the Subnetwork Report for the selected NE
• Utilization Report - Displays the Utilization Report for the selected NE
• Watch - Displays the Watch form with the selected NEs information pre-populated
6-46 April, 2009
View
User Group
Before a console user can manage a User database, it must be added to the console user’s User Group. The
User Group form provides the means for selecting the users that will be available to the console user.
This form contains the list of selectable user partitions. If logged in as “console”, then this list will contain all the partitions defined on the 1340 INC host. If logged in as a console alias, then this list will contain the partitions that have been allowed for the alias. To select or un-select a user, use the arrows to add to the
Viewed or Hidden lists.
Figure 6-29. User Group
Checkboxes:
• Include All Nodes (no Links or End User Nodes) - Used to display all network elements defined in 1340 INC including elements which have no assigned facilities. If this option is not selected, only network elements with assigned user facilities will be displayed.
• Just Include Only Nodes of Selected Users (no Links or End User Nodes) - Used to display network elements for only the selected users.
April, 2009 6-47
View
Selecting user “console”
Selecting user ‘console’ on the User Group form along with the desired user partitions allows the GUI user to receive common card and equipment type alarms along with the facility alarms that are associated with individual users.
Selecting a user the first time
If this is the first time a network is selected, all nodes for that network will be displayed, one on top of the other, in the center of the Map View display area. The GUI user would then use the Move Node option to position the network elements and user nodes to the desired locations in the display.
Saving Network Data
The console user will be prompted to Save Network Data when logging out of 1340 INC. Saving network data will guarantee the position of the network elements and end location nodes upon the user’s next login.
6-48 April, 2009
PM
Chapter Contents
•
•
Display Circuit PM on page 7-3
•
•
•
Retrieve Circuit PM on page 7-11
•
•
•
Scheduled PM List on page 7-17
April, 2009 7-1
PM
The PM Tab
The PM Tab gives users the ability to retrieve and display Performance Monitoring data.
Figure 7-1. PM Tab
7-2 April, 2009
PM
Display Circuit PM
Display Circuit PM displays PM data that is gathered for all ports along the entire path of a selected circuit.
The specific counts displayed will be dictated by the monitor types (MONTYPES), selected in the Preferences -> PM tab.
Figure 7-2. Display Circuit PM
Filters:
• Date - The date that the user would like PM to be collected for
• User - The user that PM is to be collected for
• NE - Network Element whose data is being requested
• Service View - Displays the Service View. This may be specified via selection from the Service View Wizard
• Circuit ID - Circuit Identifier
• Location - NEND (Near End), or FEND (Far End)
April, 2009 7-3
PM
• Period - Collection period for which the user wishes to retrieve PM data (24 hour only)
Columns Definitions:
The columns displayed will be the TYPE of PM data that was collected on the specified circuit as well as the counts on each port that makes up the circuit. The ports will also be labelled as (AZ) or (ZA) indicating their respective locations.
7-4 April, 2009
PM
Display PM
Display PM retrieves the PM data for the specified user and service view and displays the information in both graphical and tabular format.
Figure 7-3. Display PM
Filters:
• From/To - The range of dates and times for which the user would like to see PM data
• User - The user whose PM will be displayed
• NE - Network Element on which to execute the search
• Service View - Displays only the Service View specified
• Location - NEND (Near End), or FEND (Far End)
• Period - Collection time period for which the counts will be displayed
April, 2009 7-5
PM
• Start Time / End Time - For 15 minute period counts only, this allows the user to select the 15 minute periods that will be displayed
The data will be displayed in both graphical and tabular format. The columns in the table may be sorted by selecting the column heading that the user wants to sort on. The icons located above the table allow the user to display the data in different formats (Line Chart (default), Plot Chart, Area Chart, Bar Chart, and Stacked
Bar Chart).
• Filter Chart - Selection of the Filter Chart icon allows the user to graph only selected columns and re-draw the graph. The graph will be reduced, however the table will still show all data
Figure 7-4. Display PM - Filter Chart
Columns Definitions:
The columns displayed in the Display PM report will be a function of the NE type on which the PM data was collected and will contain the counts for the various PM counters available for the period specified.
7-6 April, 2009
PM
Problem PM
The Problem PM form is used to identify facilities which have been scheduled for periodic PM collection and have non-zero counts.
Figure 7-5. Problem PM
For each facility/port, all counts (where at least one of the counts retrieved is non-zero) are indicated in a separate column showing the monitor type. A special Performance Quality Value is calculated to provide a quantitative assessment of the quality of the facility using specific monitor types. The PQV is based upon the following formula:
100 * (86400 - (ESP+SESP+UAS)) / 86400
This formula uses the errored seconds, severely errored seconds and unavailable seconds, subtracted from and divided by, the number of seconds in a day and multiplied by 100 to get the percentage of seconds in a day that service was unaffected. The PQV is calculated only for specific element types and only where those monitor types are available for that facility.
April, 2009 7-7
PM
Filters:
• Date (From/To) - The date for which the user would like to see collected PM data displayed for problem ports
NOTE:
When the “More Options” value is chosen, the user may enter a range of dates.
• User - Displays PM data only for the user specified
• NE - Displays PM data on only the Network Element specified
• Service View - Displays only the Service View specified
• Circuit ID - displays only the information for the circuit ID specified
• From PQV - The lowest PQV to be displayed
• To PQV - The highest PQV to be displayed
NOTE:
The wildcard character “ * ” can be used to filter on a Circuit ID or substring. That is, if the user wishes to find a Circuit ID that contains the characters AB, they can enter either
*AB or AB* into the Circuit ID field to find <anything> AB or AB <anything>, respectively.
• Location - Location on which PM is collected (Near End, Far End, or Both)
• Count - Display only the ports whose collected PM values are at least this number
• Circuit Level - Value can be either YES or NO.
•
If the value is set to YES, only one (1) segment per circuit which meets the filtering criteria (the one with the lowest PQV) will be displayed
•
If the value is set to NO, then all segments that meet the filtering criteria will be displayed
• Failed Only - Will display only records on which PM collection failed. If this is set to YES, there will be an additional column displayed that will show the reason for the failure.
This column will contain the 4 character code and the denial string from the NE. The codes are NE specific and are documented in the TL1 Manuals for each NE.
NOTE:
The PM configuration file can be set up to automatically deschedule a port for PM collection based upon the NE type and the 4 character denial code. Contact your system administrator to configure this file.
Column Definitions:
• Date - The date that the PM information displayed was collected
7-8 April, 2009
PM
• Circuit ID - Contains the circuit identifier
• NE - Network Element that the circuit is connected on
• Service View - Facility/Port that the problem PM was collected on
• PM Type - Level at which the performance monitoring data was collected (T1, T3, etc.)
• LOC - Near End (NEND) or Far End (FEND)
• PQV - PQV value for the associated service view
• Max - The greatest value of the PM values collected
NOTE:
Columns that are listed after the Max column will vary based on the NE type and the types of performance monitoring data being collected. Display of these columns is set in the View -> Preferences drop down menu under the PM tab.
Navigation Drop Down List:
• Alarm List - Displays the alarm list for the selected facility
• CLI Report - Displays the CLI report for the selected entry
• Display PM- Displays the PM data collected over the previous 7 days (by default). This information can be viewed up to the previous 45 days.
April, 2009 7-9
PM
• Graph PQV - Displays the historical graph of the PQVs on the selected circuit. The data is displayed in both graphical and tabular format. Note that this graph can be printed directly to a system defined printer via the Print icon.
Figure 7-6. Graph PQV
• Retrieve Circuit PM - Displays the Retrieve Circuit PM report for the selected circuit
• Retrieve PM - Retrieve and display PM for the selected circuit
• Trace - Display the selected circuit on the Circuit Trace form
7-10 April, 2009
PM
Retrieve Circuit PM
The Retrieve Circuit PM form is used to retrieve all collected 24 hour PM on a specific circuit, regardless of what monitor types (MONTYPES) are set in the PM preferences tab.
Figure 7-7. Retrieve Circuit PM
Filters:
• User - User who owns the circuit that PM is being retrieved for
• NE - Network Element whose data is being requested
• Service View - Displays only the Service View specified
• Circuit ID - Circuit Identifier
• Location - Near End (NEND) or Far End (FEND)
April, 2009 7-11
PM
Column Definitions:
The columns displayed will be the TYPE of PM data that was collected on the specified circuit, as well as the counts for each type on each port that makes up the circuit.The ports will also be labelled as (AZ) or
(ZA) indicating their respective locations.
7-12 April, 2009
PM
Retrieve PM
The Retrieve PM form is used to query network facilities when a degradation of service is reported or suspected within the network.
Figure 7-8. Retrieve PM
Filters:
• User - User for whom PM data is being retrieved
• NE - Network Element on which the PM is being collected
• Service View - Displays only the Service View specified
• Period - Collection period that the user wishes to retrieve PM data (15 minute, 1 day, or both)
• Day - Day that the user wishes to see the PM values collected for (Today, Yesterday)
• Time - Used in conjunction with the 15 minute period, this allows the user to select a specific
15 minute period
April, 2009 7-13
PM
• Location - NEND (Near End), or FEND (Far End)
• Level - Allows the user to receive PM on a different carrier level (i.e. OC3) for the Service
View specified
• Mon Level - Allows the user to choose a value and qualifier that the system will filter displayed PM counts on. The value must be entered manually, and the qualifier chosen from the drop down list. For example, 1500 UP will only show PM counts of 1500 and greater.
If the Default value is left in the qualifier list, no filtering will be done on the counts. The
Mon Level may also be a negative number greater than -10,000 (i.e. -9999, -9998, etc.) as some PM counts (temperature, decibels, etc.) can have negative values.
NOTE:
If a network element that does not produce PM data is selected by the GUI user a warning message will appear informing the user that the chosen NE is not PM capable.
Columns Definitions:
• Service View - Service view that was retrieved
• Mon Type - Type of PM data that was retrieved
• Location - Near End (NEND) or Far End (FEND)
• Validity - Valid (data collected for an entire requested period (24 hour or 15 minute), or Partial (data collected for a portion of the requested period)
• Value - Number of PM violations retrieved
• Date -Month/Day/Year that the retrieval was executed
• Time- Time that the retrieval was executed
• Period - PM period collection (15 minute or 1 day)
• AID Type - TC level of the AID being retrieved
• Level - Carrier level of the circuit (T1, T3, etc.)
• Collection Interval - Displays the amount of time “into” the requested interval that the amount represents. This value will be 0-24 for 1 day PM retrievals, and 0-15 for 15 min
PM retrievals
Navigation Drop Down List:
• Deschedule PM - Allows the user to deschedule PM collection on the selected service view
• Display Circuit PM - Displays the Circuit PM Report for the selected circuit
• Display PM - Displays the stored PM data for the selected circuit
• Graph PQV - Displays the graph of the last 30 days of PQVs on the selected circuit
• Retrieve Circuit PM - Displays the Retrieve Circuit PM report for the selected service view
• Trace - Displays the selected circuit on the Circuit Trace report
7-14 April, 2009
PM
Schedule PM
The Schedule PM form is used to schedule and deschedule automatic performance monitoring data retrieval of 24 hour counts of the specified facility. Performance Monitoring data is information about the health of facilities that are associated with SONET network elements. A SONET network element constantly monitors the integrity of its facilities for various network events such as errored seconds and maintains 24 hour counts of those events. Using the Schedule PM option, Integrated Network Controller will automatically retrieve the previous day 24 hour PM counts for the specified facility.
The Schedule PM Form allows the user to select a user, service view and period, for which PM will be collected. Select the desired facility from the list and it will populate the Schedule PM form. If PM retrieval is desired at the OC-3, OC-12,OC-48, or OC-192 level, use the Override drop down list on the form. Select the
Location (NEND, FEND, or BOTH). After all desired options have been selected, select the <Submit> button. To Deschedule PM collection, select the Deschedule option, populate the form with the appropriate information, and select the <Submit> button.
Figure 7-9. Schedule PM
April, 2009 7-15
PM
Fields:
• User - user for whom PM data retrieval is being scheduled
• Service View - Displays only the Service View specified
• Period - Collection period that the user wishes to retrieve PM data for (24 hour)
• Override - Used to select a PM collection on a specific Optical Carrier level (OC3, etc.)
• Location - Near End, Far End, or Both
7-16 April, 2009
PM
Scheduled PM List
The Schedule PM List is the list of any facility which is a part of the PM schedule
Figure 7-10. Schedule PM List
Filters:
• User -The user for whom PM is being collected
• NE - The Network Element on which PM will be collected
• Service View - The Service View for which PM collection is scheduled
Columns Definitions:
• Service View - Service View that was retrieved
• Type - Type of PM data that was retrieved
• LOC (Location) - Near End (NEND) or Far End (FEND)
April, 2009 7-17
PM
• Report Type - Indication of the time period that PM data was collected
• Auto - An indication of whether automatic PM collection has been scheduled for this user and service view
Navigation Drop Down List:
• Deschedule - Navigates to the Schedule PM List with the Deschedule option selected and the associated information populating the form
• Display PM - Displays the stored PM data for the selected circuit
7-18 April, 2009
Reports
Chapter Contents
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
April, 2009 8-1
Reports
•
System Transactions on page 8-48
•
•
8-2 April, 2009
Reports
The Report Tab
The report tab allows the user to quickly generate and access the various reports managed by the Integrated
Network Controller system.
Figure 8-1. Report Tab
April, 2009 8-3
Reports
Assign
The Assign Report is used to query the 1340 INC data base for some or all facilities within a users partition.
When the Assign Report is accessed via the NE Pop-Up menu, the NE field will be pre-populated. When accessing from the Report Menu, select the desired user or user and NE and select the <Search> button.
Figure 8-2. Assign Report
Filters:
• User - allows the console user to filter on a specific end user
• NE - allows the console user to search for all assignments within an NE for a specific end
user
Navigation Drop Down List:
• CLI Report - displays the CLI Report for the facility selected
8-4 April, 2009
Reports
• Release - navigates to the Release form to allow the user to release the selected facility
April, 2009 8-5
Reports
Card Inventory
The Card Inventory report is used to display card specific information for a specified NE Type, Subnetwork,
Network Element, or AID. Information displayed includes card Type, CLEIs, PIDs, Active/Standby status,
Version, etc. A DNO (Dynamic Network Operation) query retrieves the equipped cards (RTRV-EQPT), card status (RTRV-STATE-EQPT), and several other pieces of information, depending on the type of network element.
Some network element types do not allow for the necessary queries in order to build a card inventory data base, therefore, a card report query cannot be performed on these element types.
The Card Inventory Report can be accessed in the following ways.
• Menu Bar - Report - Card Inventory Report
• Equipment View - Popup Menu from cards
• NE Management form
Figure 8-3. Card Inventory Report
8-6 April, 2009
Reports
Filters:
• NE Type - Type of Network Element to be displayed
• SBNK - Displays card data only for the specified subnetwork
• COMM - Allows the user to search for cards associated with an NE in a specific Communications group.
• NE - Displays CLI data on only the Network Element specified
• AID - Allows the user to search on a specific access identifier
• Status - Allows the user to Hide or Show the status of each card in the report
• TAGS (Tag Wizard) - Selection of the tag wizard will allow the user to select further filtering options (tags), based upon the column headers for a specific NE Type.
• The Operator field allows the user to select the AND or OR operator for additional filtering.
Columns Definitions:
Only the NE and AID columns are generic to this report. Additional column information displayed will be based upon the card type requested. Consequently, only the NE and AID columns can be “edited” via the
Customize Report icon located at the top of the report.
April, 2009 8-7
Reports
CLI
The CLI (Circuit Layout Identifier) report allows the user to search for specific circuits based upon a number of filtering options (usually the circuit’s CLI code (Circuit ID), or comment field) as well as navigate to additional forms once the desired circuit is found.
Figure 8-4. CLI Report
Filters:
• User - Displays the data for the specified user
• NE - Displays CLI data on only the Network Element specified
• Service View - Allows the user to search on a physical view
• CLI - CLI string or portion of the CLI string to be searched for
• Comment - Allows the user to search on a comment string
8-8 April, 2009
Reports
NOTE:
The CLI and Comment filters may be populated with any portion of the string being searched for. The search is case insensitive for either field, but spaces are not allowed in the CLI field search. It should also be noted that the CLI Report cannot be run with the default value of ALL in the USER and NE fields due to the large quantity of data that would likely be returned. One of the fields (User, NE, CLI, or Comment) must be populated with specific search data.
Columns Definitions:
• User - User the report was filtered by
• Service View - Service View corresponding to associated Physical View
• Physical View - NEID.AID identifier
• CLI Code - CLI code or Circuit ID
• Comment - Comment field.
Navigation Drop Down List:
• Display Circuit PM - Display the Display Circuit PM form for this circuit
• Display PM - Displays the PM data for the selected service view
• Retrieve Circuit PM - Display the Retrieve Circuit PM form for the selected circuit
• Retrieve PM - Displays the Retrieve PM Report for the selected service view
• Trace - Displays the Circuit Trace for the selected circuit
April, 2009 8-9
Reports
Command Schedule
The Command Schedule List is the list of commands which have been scheduled to run. When the <Search> button is selected, the scheduled commands for the user will be displayed.
Figure 8-5. Command Schedule List
Filters:
• User - Allows the console user to display scheduled commands for a specific user
Columns Definitions:
• CMD ID - An Integrated Network Controller generated command identifier
• Scheduled Time - Time that the command is scheduled to run
• Cycle - Cycle that the command is scheduled to run on
• Command Text - Command that will be executed
8-10 April, 2009
Reports
Navigation Drop Down List:
• Deschedule - executed when a scheduled command is no longer needed. To deschedule a listed command, highlight the command and select Deschedule from the drop down list.
The command is now removed from the schedule.
April, 2009 8-11
Reports
Connect
The Connect Report allows the user to query Integrated Network Controller for circuit connections by user, network element, circuit id, service view, or type. Any combination of filters is acceptable.
Figure 8-6. Connect Report
Filters:
• User - Displays connect data only for the user specified
• NE - Displays connect data on only the Network Element specified
• To NE - Displays circuits from the “NE” filter to this NE only
• Service View - Allows the user to search on a physical view
• Circuit ID - Circuit Identifier
• Type - The following TYPE options are available:
8-12 April, 2009
Reports
•
All: Displays all connections on the chosen NE. Both ports will be on the same
NE.
•
Ring : Displays all “ring” connections, i.e. subnetwork connections, from low speeds on the chosen NE. The ports reported are the endpoints of the ring circuit.
•
AZ : Displays all AZ connections, i.e. connections put up with A and Z endpoints
Columns Definitions:
• Circuit ID - The Circuit Identifier
• A-End Service View - Service view of one end of the connection
• A-End TC - Trunk Conditioning on one end of the connection
• A-End Location - An end node of the connection. This value is only stored for the following node types (ALU FT-2000, Nortel OC48, ALU Wavestar 10G, and ALU Bandwidth
Manager,), and will display N/A in all other cases.
• Z-End Service View - Service view of one end of the connection
• Z-End TC - Trunk Conditioning on one end of the connection
• Z-End Location - An end node of the connection. This value is only stored for the following node types (ALU FT-2000, Nortel OC48, ALU Wavestar 10G, and ALU Bandwidth
Manager), and will display N/A in all other cases.
• Type- Type of connection
• State - Status of the connection (Pending, Active, In Service)
• Pending - Time the connection was put into the Pending state
• Activation - Time the connection was put into the Active state
• In Service - Time the connection was put into the In Service state
• Order Number- Order number of the connection request (if applicable)
• Customer - Customer the connection is being executed for
• User Tag - User associated with this connection
• Who - User that put the connection up
April, 2009 8-13
Reports
Navigation Drop Down List:
• Disconnect - Displays the Circuit Management Disconnect form
• Trace - Displays the Circuit Trace form for the selected line
• Update Circuit Info - Displays the Circuit Management form allowing the user to edit the
Circuit Id information associated with the chosen circuit
Figure 8-7. Update Circuit Info form
8-14 April, 2009
Reports
Facility
The Facility report is used to display a list of facilities assigned in the 1340 INC database. There are various filters which may be used to specify the desired output. Any combination of filters is acceptable.
Figure 8-8. Facility Report
Filters:
• User - Displays facility data only for the specified user
• NE - Displays facility data on only the Network Element specified
• To NE - Displays facility data from the “NE” to this NE only
• Service View - Allows the user to search on a specific service view
Columns Definitions:
• Service View - Service view of the facility
April, 2009 8-15
Reports
• Status - Describes whether the physical timeslots associated with the logical service views are in order (contiguous) or not. This column will also indicate if the facility is surveillance only via the “Surveil” keyword.
• Connected - Number of timeslots that are connected
• Linked - Number of timeslots that are linked
• NE - Network Element the facility is located on
• TC/Line Code -Trunk Conditioning of the facility
Navigation Drop Down List:
• CLI Report - Displays the CLI Report for the selected facility
• Connect Report - Displays the Connect Report for the selected facility
• Linked Report - Displays the Linked report for the selected facility
• Protect - Displays the Protection Creation form for the selected facility
• Rename - Allows the user to change the name of a service view to a logical name (i.e.
N2501.111.01 to north_data_101)
8-16 April, 2009
Reports
Historical
Historical Reports allow the user to display information about the various resources being used in the system.
Figure 8-9. Historical Reports
April, 2009 8-17
Reports
Resources Report
The Resources Summary Report is a graphical and tabular representation of data showing the various system resources (User, GUIs, Logins, etc.) that are allocated and available
Figure 8-10. Resources Summary Report
Filters:
• From/To - the dates for which the report will be generated
• Cycle - cycle of time for which the report will be displayed
• Which - category of resource that the user wishes to see displayed (Allocated, Available, or
Maximum)
• Profile - auto selects the Type(s) that are associated with each specified profile. The user may deselect and select individual Type(s) to override this grouping
8-18 April, 2009
Reports
• Type - resource that the user wishes to see in the report (Logins, Facilities, GUIs, etc.)
The data will be displayed in both graphical and tabular format. The columns in the table may be sorted by selecting the column heading that the user wants to sort on. The icons located above the table allow the user to display the data in different formats (Line Chart (default), Plot Chart, Area Chart, Bar Chart, and Stacked
Bar Chart).
April, 2009 8-19
Reports
Usage Report
The Usage Summary Report is a graphical and tabular representation of data showing the amount of facilities, cross-connects, and timeslots allocated and used
Figure 8-11. Usage Summary Report
Filters:
• From/To - the dates for which the report will be generated
• Type -Facility or Unit
• Cycle - cycle of time for which the report will be displayed
• Profile - Allows the user to select a profile type to narrow the data being displayed
• NE - Only sensitive (selectable) when Profile choice is NE ID
8-20 April, 2009
Reports
• User - Only sensitive (selectable) when Profile choide is User
The data will be displayed in both graphical and tabular format. The columns in the table may be sorted by selecting the column heading that the user wants to sort on. The icons located above the table allow the user to display the data in different formats (Line Chart (default), Plot Chart, Area Chart, Bar Chart, and Stacked
Bar Chart).
April, 2009 8-21
Reports
Linked
A link is defined as a facility which begins at a network element and ends at another adjacent network element. The Linked Facility Report displays linked facilities and provides several filters which can be used to search for a specific service view, network element, or user. Any combination of filters is acceptable.
Figure 8-12. Linked Facility Report
Filters:
• User - Displays data only for the user specified
• NE - Displays data on only the Network Element specified
• To NE - Displays data from the NE above, to this NE only
• Service View - Allows the user to search on a specific service view
• Tie ID - Allows the user to search on a specific Tie ID
8-22 April, 2009
Reports
Column Definitions:
• From NE - Network element whose links are being searched for
• From Service View - Service View that the link originates from
• To NE - Network element where the link terminates
• To Service View - Service View that the link terminates on
• Tie ID - Associated Tie ID for the displayed link
Navigations:
• Update Tie ID - Displays the Tie form, allowing the user to edit the Tie ID information
April, 2009 8-23
Reports
Macro
The Macro List is a list of existing Macros. See Chapter 5 for a description of Macro creation.
Figure 8-13. Macro List
Filter:
• User - displays only macros defined for the specified user
Columns Definitions:
• Symbol - value used in the Macro definition that is associated with the defined command
• Definition - command that the symbol name represents
Navigation Drop Down List:
• Modify - Allows the user to change the structure of the existing Macro
8-24 April, 2009
Reports
• Remove - Allows the user to delete the Macro
• Run - Allows the user to execute the selected Macro
NOTE:
Macros for console and console aliases may only be executed (run) when logged in as console or the console alias, respectively. They cannot be executed for users while logged in as console or a console alias.
April, 2009 8-25
Reports
NE Reports
The NE Reports form provides the user with a list of reports that can be retrieved to display 1340 INC information relating to the databased network elements. To access any of these options select the desired report.
These reports are used in conjunction with the Map View and Table View functions.
Figure 8-14. NE Reports
8-26 April, 2009
Reports
COMM Group Report
The COMM Group Report displays all network elements that belong to the same communications group.
Each network element which is defined as an add-drop-multiplexor is associated with a communication group. The communication group is established from Integrated Network Controller to an interface
(NMS-to-GNE, NMS-to-NMA or NMS-to-NMS) or from Integrated Network Controller to a gateway network element (GNE). Every network element within the given ring or every network element beneath the interface, for example, a GNE Interface, uses the same unique communication group ID.
An example would be if Integrated Network Controller were directly connected to a GNE. The GNE could have a COMM Group ID of 1. All network elements beneath the GNE would also carry a COMM Group ID of 1.
Figure 8-15. Comm Group Report
Filters:
• Comm Group - Communications group for which the report is being displayed
April, 2009 8-27
Reports
Columns Definitions:
• NE ID - Network Element Identification
• TID - Network Element Target Identifier
• NE Name - Network Element name
• NE CLI - Defined CLI code for the network element
• SBNK - Subnetwork that the network element belongs to
• Comm Type - GNE (Gateway Network Element) or RT (Remote Terminal)
• STAT - Indication of the communication status of the NE
• Alarm - Highest severity alarm on the network element
• NE Type - Vendor and model of the network element
• Release - Displays the firmware release number running on the NE
• Address - Displays the IP address of the NE
• GNE - Displays the Gateway Network Element for the NE
Navigation Drop Down List:
• Alarm Report - Displays the Alarm Report for the selected NE
• CLI Report - Displays the CLI Report for the selected NE
• Connect Report - Displays the Connect Report for the selected NE
• Facility Report - Displays the Facility Report for the selected NE
• NE Management - Displays the NE Management form for the selected NE
• Utilization Report - Displays the Utilization Report for the selected NE
8-28 April, 2009
Reports
NE Group Report
The NE Group Report allows the user to search on a particular NE Group to see all of the nodes that make up that group. The report consists of a list of all NEs which have been defined as being a part of the given NE
Group.
The alarm column will contain an alarm code representing the highest severity alarm that currently exists in that network element. The SBNK column shows the subnetwork ID of the NE if it is an ADM or DCS if it is a digital cross-connect system.
Figure 8-16. NE Group Report
Filters:
• NE Group - Network Element group for which the report is being displayed
Columns Definitions:
• NE ID - Network Element Identification
April, 2009 8-29
Reports
• TID - Network Element Target Identifier
• NE Name - Network Element name
• NE CLI - Defined CLI code for the network element
• SBNK - Subnetwork that the network element belongs to, or DCS if the NE is a Digital Cross
Connect System
• Comm Type - GNE (Gateway Network Element) or RT (Remote Terminal)
• STAT - Indication of the communication status of the NE
• Alarm - Highest severity alarm on the network element
• NE Type - Vendor and model of the network element
• Release - Displays the firmware release number running on the NE
• Address - Displays the IP address of the NE
• GNE - Displays the Gateway Network Element for the NE
Navigation Drop Down List:
• Alarm Report - Displays the Alarm Report for the selected NE
• CLI Report - Displays the CLI Report for the selected NE
• Connect Report - Displays the Connect Report for the selected NE
• Equipment View - Displays the Equipment View for the selected NE
• Facility Report - Displays the Facility Report for the selected NE
• NE Management - Displays the NE Management form for the selected NE
• Utilization - Displays the Utilization Report for the selected NE
8-30 April, 2009
Reports
NE Usage Report
The NE Usage Report will display information about the high speed facilities in the chosen network element. This information will be displayed in a color coded format depicting whether a channel is connected to a low speed facility (Green), not connected (Yellow), connected as Pass Thru (Blue), connected as part of an inter-ring connection (red), or not provisioned in the Integrated Network Controller data base (Gray). The information may be filtered by NE, Ring number, Bay number, or Shelf number.
Figure 8-17. NE Usage Report
Filters:
• NE - Network Element for which the NE Usage Report is being displayed
• Ring # - ring number for which the NE Usage Report is being displayed
NOTE:
In the case of DMX network elements, this value will be in the form of an AID (Access
Identifier)
April, 2009 8-31
Reports
• Bay # - bay number for which the NE Usage Report is being displayed
• Shelf # - shelf number for which the NE Usage Report is being displayed
Navigation Drop Down List:
• Trace - Displays the Circuit Trace for the selected facility
8-32 April, 2009
Reports
Subnetwork Report
The Subnetwork Report allows the user to search on a particular subnetwork to see all of the nodes that make up that subnetwork. The report consists of a list of all NEs which have been defined as being a part of the given subnetwork.
In the example below, the list contains five NEs which make up subnetwork 3. NE-id 1555 is the GNE
(Gateway Network Element) and the remaining NEs are RTs (Remote Terminals).
Figure 8-18. Subnetwork Group Report
Filters:
• Subnetwork - Subnetwork for which the report is being displayed
Columns Definitions:
• NE ID - Network Element Identification
April, 2009 8-33
Reports
• TID - Network Element Target Identifier
• NE Name - Network Element name
• SBNK - Subnetwork that the network element belongs to
• Comm Type - GNE (Gateway Network Element) or RT (Remote Terminal)
• STAT - Indication of the communication status of the NE
• Alarm - Highest severity alarm on the network element
• NE Type - Vendor and model of the network element
• Release - Displays the firmware release number running on the NE
• Address - Displays the IP address of the NE
• GNE - Displays the Gateway Network Element for the NE
Navigation Drop Down List:
• Alarm - Displays the Alarm report for the selected NE
• CLI - Displays the CLI report for the selected NE
• Connect Report - Displays the Connect Report for the selected NE
• Equipment View - Diplays the Equipment View for the selected NE
• Facility Report - Displays the Facility Report for the selected NE
• NE Management - Displays the NE Management form for the selected NE
• Utilization - Displays the Utilization Report for the selected NE
8-34 April, 2009
Reports
Utilization Report
The Utilization Report is designed to allow customers to identify how much of a SONET ring is used, and what capacity is still available. Each line of the report shows the ring layout for a single rail, while each column shows the NE usage for a single NE on the ring
• The column headings of the report display the TID/NEID of the NE and the AID of the line or of the first rail on the line (based upone NE type). The columns display the level of the connections or assignments on the rail, e.g. VT1, STS1, etc.
• Every column of the report is one NE on the ring. The NEs appear in the order of their path around the ring.
• The status of the facility between any two NEs may be displayed as different types of lines, or as colors, or both, depending upon the options chosen on the form. They may be connected as a pass-through or drop, provisioned but not connected, or not provisioned. The two directions for circuits on a UPSR ring are arbitrarily identified as active or protection. Lines show the individual assign/connect status for each endpoint of the link, but the color is the same for the entire link, using the color of the highest status.
• If a Tie ID has been defined for a particular rail, it will be displayed at the top of that rail
• For connected facilities, the circuit name (either CLI or Circuit ID) appears above each line.
For subsequent rails of a concatenated payload (i.e.STSn), the circuit name is replaced with the bandwidth value (e.g. “STS3”).
• For dropped connections, the facility AID is displayed below the line.
• Each line of the report displays a single rail around the ring, using the smallest granularity of the assignments for that STS on all NEs. For example, if the rail is assigned/connected as
VT1s on any NE, then the STS is reported as 28 lines, one for each VT1. If the assigned level is greater than STS1, then the other STSs are skipped, and the level is displayed next to the circuit name.
• The report does not include NEs that are only used for transport for a ring overlay. When the path for one rail does not pass through a specific NE that is in the path of other rails, as may occur when ring overlays exist, the NE is displayed as not provisioned.
• The legend at the top of the form describes the meaning for each type of line and color
April, 2009 8-35
Reports
Figure 8-19. Utilization Report
Filters:
• User - Displays information for the specified user on the chosen NE
• NE - Displays information for the selected NE
• Ring # - ring number for which the Utilization Report is being displayed
NOTE:
In the case of DMX network elements, this value will be in the form of an AID (Access
Identifier)
Navigation Drop Down List:
• Trace - Displays the Circuit Trace form for the selected circuit
• Update Circuit Info - Displays the Circuit Management form allowing the user to edit the
Circuit Id information associated with the chosen circuit
8-36 April, 2009
Reports
NOTE:
In order to print this report, the Internet Option “Print background colors and images” must be set on the Tools -> Internet Options -> Advanced tab of Microsoft Internet
Explorer
April, 2009 8-37
Reports
NE Summary
The NE Summary Report provides general information about network elements defined in the 1340 INC system. This query is done on a system wide basis, not just on the elements that are currently displayed on the GUI.
Figure 8-20. NE Summary Report
Filters:
• NE Type - Allows the user to filter on just one network element type (i.e. DMXs)
• Status - Allows the user to display all network elements or only those network elements that are either UP, DOWN, or DISABLED
• NE - Allows the user to filter on a particular TID/NEID
NOTE:
The NE field can accept a TID or an NEID, and allows the user to enter a case sensitive text value in this field. The user may also use the wild card character “*” to search for an
8-38 April, 2009
Reports
NE. If the first character is a *, (i.e. *DM) then it will match all NEs that have the string anywhere in it. If the last character is a *, (i.e. DM*) then it will match all NEs that start with that string.
• SBNK - Allows the user to filter on a specific subnetwork
• Comm - Allows the user to filter on a particular Comm Group
• Time Diff - The difference in time between 1340 INC and the NE (1340 INC time - NE time).
The value will be displayed in the report as a positive or negative number accordingly
(from the perspective of the NE). That is, if it is 10:00 PM at 1340 INC and 9:00 PM at the NE, the column displayed in the report will be -01:00:00. If it is 9:00 PM at 1340
INC and 10:00 PM at the NE, the report column will contain the value +01:00:00 When a value is entered in the filter field (in minutes), the report will display all NEs whose time difference is greater than that number of minutes different than 1340 INC ( greater than or less than). If no value is entered, the report will show the time difference between
1340 INC and the NE or NONE if there is no difference. This time difference processing allows 1340 INC to adjust appropriately when collecting PM.
NOTE:
In addition to using the drop down list, the user may also manually enter the value of a specific NE, SBNK, or Comm Group to be searched for.
Navigation Drop Down List:
• Alarm List - Displays the Alarm List for the selected NE
• Comm Group Report - Displays the Communications Group report for the selected NE
• Equipment View - Displays the Equipment View for the selected NE
• NE Cut Thru - Opens a TL1 cut thru window to the selected NE
• NE Management - Displays the NE Management form for the selected NE
• Ring Layout - Displays the Ring Layout of the selected NE
• Subnetwork Report - Displays the Subnetwork Report for the selected NE
April, 2009 8-39
Reports
NE Transactions
The NE Transaction Report is a list of TL1 commands that have been sent to an NE. Integrated Network
Controller allows a user to filter and search for specific transaction information.
Figure 8-21. NE Transaction Report
Filters:
• Login ID - login id whose transactions the user wishes to search for
• NE - allows the user to filter on a particular TID/NEID
• Source - area of the system from which the command originated (i.e. Auto Discovery, Match,
PM, etc)
• Type - based upon the Source choice above, these are the types of commands available within each Source
• From/To - date range for which the user wishes to see transaction activity
8-40 April, 2009
Reports
Navigation Drop Down List:
• Browse Log - Displays the Daily log, showing the command and response of the transaction navigated from. The exception is if the Type is “restore” and the source is “backup”, in which case, the Restore Log will be displayed.
April, 2009 8-41
Reports
Protect
The Protect List is used to display a list of currently protected facilities and remove circuit protection for a given facility. See Chapter 5 for a description of Protection creation.
Figure 8-22. Protect List
Column Definitions:
• ID - an Integrated Network Controller generated identification number
• Service View - the Service View of the facility being protected
• Type - Alarm type defined in the protection creation
• Delay - the amount of time the alarm must be in before the protection command defined is executed
• Command - the command to be executed
Navigation Drop Down List:
8-42 April, 2009
Reports
• Unprotect - The unprotect command is used to remove protection from a channel or facility which has been configured for protection using the protect command. To remove protection from a channel/facility highlight the desired facility and select Unprotect. Integrated
Network Controller will inform you if the unprotect was successful or if there was an error. If a command is queued to be executed, the unprotect command will “dequeue” it and remove the request from the database.
April, 2009 8-43
Reports
State
The State Report will query the Integrated Network Controller system for a list of all facilities or network elements identified as in the Maint, Block, or MBlock state.
Figure 8-23. State Report
Filters:
• User - Displays data only for the user specified
• NE - Displays audit data on only the Network Element specified
• Service View - Allows the user to search for a specific service view
Columns Definitions:
• User - User that is assigned the listed facility or NE
• Service View - facility that is assigned to the user
8-44 April, 2009
Reports
• State - Current state of the facility or NE
• By - User that put the facility or NE into the current state
• Activation - Date and time that the facility was put into it’s current state
• Expiration - Date and time that the facility will revert to the CLEAR state
• NE - Network Element that the facility is on
• Type - Object that is in the current state (Facility or NE)
Navigation Drop Down List:
• Update Maintenance - Displays the Update Maintenance State form so that users may change the alarm maintenance state of a facility or NE.
April, 2009 8-45
Reports
SubPartition
The Subpartition Report is used to display the information in each partition (1-7) as well as the surveillance partition. See
Subpartition Management on page 5-101
for additional information.
Figure 8-24. Subpartition Report
Filters:
• User - user the report will be generated for
• NE - displays subpartition data only for the network element specified
• Partition Index - displays data only for the partition specified. Default is Surv Only (subpartition 8)
• Usage - filters on usage type (All, Surveillance only, or Configuration)
8-46 April, 2009
Reports
Columns Definitions:
• Service View - service view of the facility in the subpartition
• TC/Line Code - line code (level) of the facility
• Partition Name - subpartition the facility belongs to
• Partition Index - subpartition number the facility belongs to (1-7, or 8 for surveillance only)
• Usage - Config (configuration capable), or Surveil (surveillance only)
April, 2009 8-47
Reports
System Transactions
The System Transactions Report is used to query Integrated Network Controller for a list of system (1340
INC) transactions for a given day. These reports are kept for the previous seven days.
Figure 8-25. System Transactions Report
Filters:
• Login ID - id of the user the report is being generated for
• Types - All transactions, or Commands only
• Day - The day for which the search is being executed
• From/To - the range of time for which the report will be run
• Status - Indication of whether the transaction failed or succeeded
• Records - All or Last 20
8-48 April, 2009
Reports
Columns Definitions:
• Login ID- Login that executed the transaction
• Owner - Owner of the login that executed the transaction
• Port - Port from which the transaction took place
• Time - Time that the transaction was executed
• Type - Type of transaction that was executed
• Status - Indication of whether the transaction succeeded or failed
• Elapsed Time - Time from issue to completion of transaction request
• Command - Command that was executed
April, 2009 8-49
Reports
Tie
The Tie Report is used to display all inter-nodal facilities on DCS and SONET network elements.
Figure 8-26. Tie Report
Filters:
• NE - Displays tie data for only the Network Element specified
• NE ID - Allows the user to enter a specific Network Element Idenitification number for tie data display
Columns Definitions:
• From NE - network element where the tie originates
• From NE View - physical digroup or AID that the tie originates on
• To NE - network element where the tie terminates
8-50 April, 2009
Reports
• To NE View - physical digroup or AID that the tie terminates on
• Type - type of tie (Direct (D) or Indirect (I))
• Tie ID - tie identification field. A value is displayed only if a Tie ID was entered when the tie was created.
Navigation Drop Down List:
• Update Tie ID - Displays the Tie form, allowing the user to edit the Tie ID information
• Untie - Displays the Untie form so that the user may untie the selected tie.
April, 2009 8-51
Reports
Trace
The Circuit Trace form allows the user to view the structure of a circuit from end to end. Circuits may be contained in one network element, or may be carried through a number of network elements. The information is displayed in both graphical and tabular format.
Figure 8-27. Trace
For performance monitoring, the Performance Quality Value may be optionally displayed with the graphical trace. When enabled (via the Display PQV option), the PQV for each facility will be shown on the graphical trace. If there is no PM data, or the PQV is not supported on that port, then an error message will be displayed. If an error is returned from the NE, the 4 character error code will be displayed (i.e. SNVS (System
Not in Valid State) etc.). These codes are defined in the NE specific documentation. Running the Retrieve
PM command for the associated port will also display the complete error string returned from the NE for further clarification.
The PQV from PM collected earlier than the current day is also available. A PQV Threshold can be specified to provide a reference.
Filters:
• User - User that owns the facility being traced
8-52 April, 2009
Reports
• NE - Allows the user to select an NE on which to trace a circuit
• Service View - (Required) the service view of the circuit to be traced
• Leg # -The leg number of the unit being traced, this option applies to subrate units
• Show SBNK - This option is only valid on ring configuration NEs and is used to show connections in both directions.
• Show Physical - This option will display data in physical mode (as opposed to logical)
NOTE:
If Show Physical is set to “YES”, some navigations from the node drop down list will be unavailable
• PQV
•
Display - Show the PQV on the graphical display. This option must be selected in order for the PQV Date and PQV Threshold filters to be used. If this option is selected, the PQV may also contain a bracketed “[ ]” value indicating whether or not the port is currently on the Work List and what state it is currently in (S =
Study, I = Investigate, R = Repair, C = Chronic, T=Trouble, and $=Paid)
•
Date - User definable date from which to display PQV data.
•
Thresh - A user definable threshold value from 1 to 100.
Columns Definitions:
• Circuit ID - Contains the circuit identifier
• From Service View - Contains the service view name of the “From” side of each cross-connect in the trace
• From TC/LC - contains the trunk conditioning code or facility type of the From Service View
• To Service View - contains the service view name of the facility that the “From Service
View” is connected to
• To TC/LC - contains the trunk conditioning code or facility type of the To Service View
• Linked to Service View - contains the service view name of the facility that the “To Service
View” is linked to
• Rate - contains the circuit rate if applicable (Subrate connections)
Buttons:
• Map View - displays the map view with a zoomed in view of the ring on which the circuit trace was executed. The path of the circuit will be highlighted with the add and drop nodes circled. It should also be noted that the Map View displayed will have only Show
End Locations, Icon Size, and Background as choices in the Filter area
April, 2009 8-53
Reports
• Reverse Trace - This button will ONLY appear if there is a RING circuit within the trace. It is designed to allow the user to see both directions of a defined circuit (generally m1- m2 directions). When selected, an additional trace window will be displayed showing the trace in the opposite direction.
Navigation Drop Down List (from Node):
• Alarm List (NE) - Displays the alarm list for that network element
• Alarm List (Circuit) - Displays the alarm list for that circuit
• Connect Report - Displays the Connect Report for the NE
• Disconnect - Displays the Disconnect form for the selected circuit
• Display Circuit PM - Displays the Circuit PM for the selected circuit
• Display FROM PM (AZ) - Displays the stored PM of the FROM side of the circuit
• Display TO PM (ZA) - Displays the stored PM of the TO side of the circuit
• Equipment View - Displays the Equipment View of the selected NE
• Facility Report - Displays the Facility report for the selected NE
• Graph FROM PQV - Displays a historical graph of the last 30 days of the FROM side PQV values
• Graph TO PQV - Displays a historical graph of the last 30 days of the TO side PQV values
• Linked Report - Displays the Linked report for the selected NE
• NE Cut Thru - opens a cut thru session to the selected NE
• NE Usage - Displays the Node Usage report for the selected NE
• Retrieve Circuit PM - Displays the Retrieve Circuit PM form for the selected circuit
• Retrieve FROM PM (AZ) - Displays 15 minute and 24 hour PM for the FROM side of the selected NE
• Retrieve TO PM (ZA) - Displays 15 minute and 24 hour PM for the TO side of the selected
NE
• Ring Layout - Displays the Ring Layout for the selected NE
• Subnetwork Report - Displays the Subnetwork Report for the selected NE
8-54 April, 2009
Index
Symbols
“Default User” Card Management
A
Activate
Active Alarms
Add
Administration
Alarm
Alarm Age/Filter Tab
Alarm Central
Alarm Colors Tab
Alarm Detail
Alarm List
Alarm Management
Alarm Tab
Alarms
Alias Tab
Architecture
Assign
ATM/FR
Audience
Auto Refresh
A-Z Connection
B
Become User/Alias
C
Card Inventory
Change Password
Changing the GNE of a Ring
Circuit ID
Clear
CLI
Close
April, 2009
Comm Group Report
Command Schedule List
Communication Tab
Configuration Management
Connect
Connect Report
Conventions
Copywrights
CSV
CSV Layout
Customize Table
Customize Table/CSV/Print Report
Cut and Paste TID
Cycle Windows
D
Dashboard
DB Only
Delete
Description
Detail
Display PM
DNO
Documents
Ordering Documents
Summary
E
Eastern Research DNX, Premisys IMACS,
Generic SNMP Devices
Echo Canceller
EMS
End Session on Idle Timer
e-ticket
External Tie
IN-1
Index
F
Facility
Facility/Port/AID
Filter by Tree
Filters
Form
Function Tabs
G
General Tab
Graph PQV
Grouping of Groups
H
Hardware
Help
How To
Modify number of allocated sched cmds
Modify number of allocated symbols
Update User login limit
I
ID Area
INC Cut Thru
INC Messenger
InEffect
Info Tab
Integrated Network Controller TL1 Interface
Integrated Network Controller to DNA CA Inter-
face
Integrated Network Controller to NFM Interface
Integrated Network Controller to NSPM Inter-
face
Integrated Network Controller to SNMP Inter-
face
Interfaces
modem
serial
telnet
L
Launch Area
Less Options
Lines per Page
List of Supported Network Elements
Load Menu Selection In
Log Files
Logging In
M
Macro Definition
Macro List
Main Display Area
Main Screen
Maintenance
Maintenance State
Match
Miscellaneous Tab
More Options
Multi-Level Maps
N
Navigation Drop Down List
NE
NE Cut Thru Permission
NE Group Management
NE Group Report
NE List
IN-2 April, 2009
Index
NE Management
Backup Gateway Network Element
Gateway Network Element
NE Management Form
Neighbors Tab
NE Notification
NE Password Hiding
NE Summary
NE Transaction Report
Neighbors Tab
NEs Tab
Network Element Support
Network Elements
1/0 DCS
3/1 DCS
3/3 DCS
DWDM
OC-12 ADM
OC-192 ADM
OC-3 ADM
OC-48 ADM
Network Elements List
Network Management Capabilities
New
New Alarm List
New Window
NMS
Node Usage Report
O
OC-192 ADM
OC-48 ADM
One Sided
Options
Order Number
Override
P
Password Hiding
Path Criteria
Pending
Performance Management
Plus Charge Option
PM Tab
Populate
PQV
Preface
Preferences
Print Layout
Print Report
Problem Alarms
Problem PM
Protection Creation
Protection List
Provisioning
Purpose
R
Receive ATM/FR SLA Reports
Receive Metro Ethernet SLA Reports
Receive NE Notifications
Refresh Interval
Release
Retrieve PM
Ring
Ring Layout
S
Scheduled Commands
Search
Search Capability
Security Lock
Security Timer
Service View
Service View Wizard
Software
Common Desktop Environment
SUN Environment
Stacking Macros
State
Submit
April, 2009 IN-3
Index
Subnetwork Management
Subnetwork Report
Subpartition Management
SubPartition Report
Supported Network Elements List
System Interfaces
Southbound
System Transactions
T
TC/Trouble Code
The PM Tab
The Report Tab
Ticket
Tie
Tie Management
TimeZone
Timezone
Title Bar
Trace
Trace Level
Trouble Ticket
Type Ahead Capability
U
Unprotect
Unswitched
Untie
Update
Update Maintenance State
User Commands Tab
User Group
User Info
User Tag
Utilization Report
V
View Tab
W
Watch
WebServer Software
IN-4 April, 2009
Download
Public link updated
The public link to your chat has been updated. You may view and manage your chat links after registration here.
Document public link
Advertisement
Key features
Point and click interface
Alarm management
Configuration management
Performance management
Secure customer database
Graphical equipment views
Cut-thru to INC and Network Elements
Generic TL1 interface
Graphs
On-line Help
Frequently asked questions
The 1340 Integrated Network Controller WEB GUI is a software application designed to provide a graphical, point and click, interface to the 1340 INC Host.
The 1340 INC Host is the core component of the 1340 Integrated Network Controller system, providing the central management and control functions for the network.
The 1340 Integrated Network Controller supports a wide range of network elements, including Digital Cross-Connect Systems (DCS), Add-Drop Multiplexers (ADMs), Dense Wavelength Division Multiplexers (DWDM), and Echo Cancellers (EC).
You can access the Integrated Network Controller WEB GUI via a serial port, telnet, rlogin, or modem connection.
For optimal performance, a minimum of 1GB RAM, a 2.0 GHz processor, and a 1280 x 1024 screen resolution is recommended.
