|
|
Products Center
EMS
VigorCMS |
|
|
Vigor Central Management
System Server ( VigorCMS Server)
is a multi-tier architecture, flexible and
easy to use for system management. It can
manage 1,000 to 5,000 Vigor devices, depends
on the capacity of sever. A step-by-step configuration
wizard makes users deploy large numbers of
devices to customer sites easily. VigorCMS
provides configuration management, topology
management, security management, fault management
and backup / restore management.
Configuration management allows users to have
a remote control on devices, or central control
by auto provisioning. When Vigor devices are
set to "Auto Provisioning", these
devices will get all settings from the EMS
server or the Provisioning server while they
are booting up. Another feature in configuration
management is the diagnostic functions used
to test the device, make sure that the device
is working well.
Topology management provides auto discovery
and manually add or remove devices. A layer
architecture is used to show subnet-device
relationship. When any fault occurs in some
devices within the subnet, an alarm warning
signal icon is shown in the subnet so that
operator can view the status of managed devices
immediately.
Security management uses a resource-role concept
to managers. For authentication, VigorCMS
server has a default mechanism to implement.
VigorCMS server will maintain an access control
list to do authority, grant users with some
privilege to resources.
Fault management includes alarm collection,
status polling, event logging and alert trigger.
VigorCMS server monitors all managed devices
in a fixed cycle, and the device will report
alarm while device problem occurs. VigorCMS
server will keep some system events so that
trace messages will be stored in the database
or files for tracing.
A notification mechanism provides trigger
to users when any event or alarm received
by VigorCMS server. In general, system will
send e-mail to users once the condition is
fulfilled the filters set by administrator.
VigorCMS also provides Northbound interface
to other NMS. NMS can collect the status of
devices managed from VigorCMS by using Web
Service.
Main Features and Benefit
- Manage up to 5,000 SNMPv1, v2c
agents for one server instance
- Support Standard MIB II, RFC1213,
RFC2662, IEEE802.11 MIB, Proprietary
VoIP MIB, Proprietary VPN MIB, Proprietary
ADSL MIB
- Manage the Vigor3300 or VigorAccess
devices with one IP address
- Integrate VigorView management tool
- Support schedule software upgrade
- Invoke Web interface, telnet and
ping functions for remote control
- Support auto-discovery
- Support auto-provisioning
- Support alarm management
- Auto alerting by e-mail
- Trap handling capability (150 traps/sec)
- Role-based security management
- Topology management
- Performance measurement, including
dynamic chart and report generation
- Support device polling
- Device panel view
- Northbound interface with NMS
- Online help and alarm trouble-shooting
- VigorCMS server can be in the Windows
2000, XP, NT, Linux and Sun Solaris
- GUI can be in the Windows 2000,
XP and NT
- Support Open Database Connectivity,
any JDBC-compliant SQL database can
be used as the backed database server,
for example: Oracle, MS SQL server,
Sybase, DB2 and MySQL
- Standard J2EE platform is supported,
so any J2EE server could be used as
an application server, for example:
BEA web logic, IBM web sphere, JBoss
|
|
|
|
Technical
Specifications of VigorCMS |
| Platform
Requirement |
Minimum - Sever / Client |
CPU : Intel P4 1G-MHz compatible |
| SDRAM : 512 Mbytes, 1G Mbytes is recommended
|
| Hard disk 50G, support RADI5 is recommended
|
| Dual Giga-bit NIC card |
| OS Platform - Server / Client |
Linux Red Hat advanced server |
| Windows 2000 server or XP |
| Solaris 8 or 9 |
| Minimum - Client |
CPU : Intel P3 500 MHz |
| SDRAM : 128 Mbytes, 256 Mbytes is recommended
|
| Hard disk : 500 Mbytes |
| Ethernet Adapter |
| OS platform - Client |
Windows 2000 / XP |
| JDK 1.4 |
| UNIX or Linux operating
system with X-windows, or Sun workstation |
| CMS supports for FCAPS functions |
| Security functions - Access
Control - 3 Levels minimum ( Admin, Users, Read-only
) |
| CLI supports per ADSL2+ node |
| Remote SW upgrade |
| Manage all sub-tended Switch
as on single NE |
| SNMP Version 1 / Version 2c |
| RFC 1157-1213 SNMP / SNMP v2
MIB |
| RFC 1284 / 1623 Ethernet-link
interface MIB partial support |
| RFC 1286 / 1493 Bridge MIB
partial support |
| Provide enough and full MIB
databases FCAPS, Remote SW upgrade and so on |
| Provide in-band channel for
CMS |
| CMS must export display result
to report. The report can be sent to printer, and
can be saved with text or EXCEL format |
| History log of operation register
and operation content. History log can be deleted
only by system administrator who has top authority |
| Configuration management |
Auto detect network topology
; display current topology dynamically |
| Can disable / enable each user
port ; can display port status |
| Can display port line parameter
: line code ( such as ADSL2+ / ADSL2 / G.dmt / G.lite
), line transmission path ( such as Fast / Interleave
Path ), line speed mode ( such as Fixed Rate / Adaptive
Rate ) , line noise margin ( such as Noise Margin
› 6 dB ), port transmit power, target
noise margin, maximum noise margin, max transmit rate,
min transmit rate, max interleave depth , etc... |
| Can provision by script |
| Auto detect network topology;
display current topology dynamically |
| Fault Management |
Alarm display : faceplate display
; alarm severity can be distinguished by various color
( critical , major minor ) ; display each port's alarm
status ; display alarm created time, alarm level,
alarm status ( on / acknowledged / cleared ), alarm
description, etc |
| Alarm prompt : Audible alarm
prompt and eject alarm message window ; unacknowledged
alarm should send alarm prompt sound at intervals
; alarm prompt can be distinguished by various sound
according to alarm level |
| Alarm class : At least Critical,
Major, Minor and Warring |
| Equipment alarm : |
Node fault alarm, interface alarm , power
/ fan alarm, Line alarm |
| Forward error correction |
| Cyclic redundancy check |
| Loss of Signal |
| Loss of Frame |
| Loss of Power |
| Loss of Link |
| Communication alarm : When CMS
loses communication with NE, CMS should send out alarm |
| Alarm log : inquire, classify
and statistic, backup, delete alarm log |
| Performance management |
Collect each port's statistic
periodically |
Statistic of ADSL2+ port
Line Attenuation ( Current )
- Line Attenuation ( Current )
- Noise Margin ( Current )
- Total Output Power
- Maximum Attainable Rate
- Current Rate
- Channel Data Block Length
- Interleave Delay
- Payload Transmit Rate
- Best transmit Rate |
Count event at intervals of
15 min and 24 hours
- Loss of Signal
- Loss of Frame
- Loss of Power
- Loss of Link
- Error Seconds
- Transmit Blocks
- Receive Blocks
- Corrected Blocks
- Uncorrectable Blocks |
| Data Inquiry : List data by
table or graphics |
| Data Processing : Save, print
and delete data |
| Performance analysis : Analyze
port's status like traffic, usage percent, availability,
fault percent |
| Security Management |
Account management |
| Database backup / restore |
| Log of operation including operator's
login and logout time |
|
|
|
Page last modified : 18 June 2008 |