Users Guide

New Features/Devices Supported in 6.2 24
Menu called Traffic Assessment with a select set of Traffic Flow Analyzer portlets.
(27261)
• VMWare ESX and KVM Controller Support
Basic support for management of VMWare ESX and KVM Controller devices was
added. The controllers are discovered/managed via WBEM protocol and require
WBEM and SSH authentication protocol at discovery time.
VMs will appear in the controller's reference tree, but can also be discovered
standalone.(27782) (27783)
• Localization of decimal point as a comma is now supported because many
countries use a comma for the decimal point rather than a dot. For example, a
number formatted in the US and most English speaking countries as 459.12
would be 459,12 in countries such as Mexico, Argentina and Morocco. (27813)
• License enabled for all action types include Configure Commands, External
Executable, Show Commands, Config File Generation, Perl Script and Script Only
Generation. (27796)
• Prior version of OMNM had vendor-specific performance monitors that were
seeded by the system during installation. These were named "Default Cisco
Monitor" and "Default Juniper Monitor". OMNM 6.2 no longer seeds these
monitors during installation, but if these monitors were seeded during the
installation of a prior version, they will still function properly. These monitors are
no longer seeded because OMNM 6.2 seeds performance monitors that perform
the same function and are work for all devices, regardless of vendor (including
Cisco, Juniper, Dell, etc.) These vendor-independent monitors are called "Default
Temperature Monitor", "Default CPU Monitor", "Default Memory Monitor" and
"Default IP Statistics Monitor". All four of these monitors target devices regardless
of vendor, so thus the vendor-specific monitors are not necessary. (27912)
• The site management portlet lets you restrict access to configured network
domains. Select the configuration icon (the wrench) which opens the Global Site
Settings dialog. Here the administrator can add networks that the primary site’s
central domain users can login from, or exclusions of things like a proxy server
within one of the permitted networks which allows external access to the web
server. When attempting to login from an IP address other than those permitted a
message appears saying Login is restricted from your current IP [IP Address].
Notice that you must check Login Restrictions Enabled to begin restricting access.
When you check that, global portal users can only log in from defined, permitted
networks. You can also elect to Apply Login Restrictions to Portal Admin with
that checkbox, too.
Currently only IPv4 address can be used. If end user wants to exclude all IPv6
addresses, s/he can specify IPv4 range as a permitted network range. If end user
doesn't specify any permitted network, then all IPv4 and IPv6 addresses are
permitted to see OMNM application.(27948)
• Under OMNM Add -> Applications in the Portal Applications -> Sample section, a
new portlet called iFrame is available. You can use the iFrame portlet to link a
URL and make it a page within OMNM. (27913)
• Auto Discovery AKA Zero touch provisioning is now supported. This feature
allow any device to be auto discovered via DCHP boot or USB boot. refer to the
user guide section Auto Discovery via DCHP boot or USB boot for configuration
details. (27994)