Cisco Prime™ Network virtual network element (VNE) device driver technology is a key enabler for Cisco Prime Network to manage end-to-end IP next-generation networks (NGNs). Included with purchase, Cisco Prime Network VNE drivers support a wide range of Cisco® and non-Cisco devices that may be deployed across access, aggregation, edge, and core network domains. Cisco Prime Network VNE drivers use Simple Network Management Protocol (SNMP), Command Line Interface (CLI) and eXtended Markup Language (XML) device interfaces to discover physical inventory and logical configuration of managed devices. VNE drivers translate the discovered information into a detailed software representation of the device, which forms the basis for all further device and network management functionality for device health and change monitoring, VNE drivers periodically check the device as well as interpret autonomous event messages, such as SNMP notification and syslog messages, that devices send to Cisco Prime Network.
For customers with multivendor environments, Cisco Prime Network offers third-party VNE drivers for many commonly deployed, non-Cisco network elements including those from Alcatel-Lucent, DragonWave, Huawei, Juniper and RAD. These third-party VNE drivers are supported and maintained by Cisco as part of the Cisco Prime Network product. This support includes VNE upgrades for device releases to maintain management interface compatibility. For non-Cisco devices that are not supported by a Cisco Prime Network third-party VNE driver, Cisco Prime Network offers two VNE alternatives:
• Cisco Prime Network provides a "generic VNE" that uses standard MIB- system and interface data to create a baseline model of any network element supporting SNMP.
• Beyond the baseline device model, customers can also create extensible, user-defined VNE drivers for specific non-Cisco device types. Cisco Advanced Services (AS) routinely provides expert support for either of these approaches and further customization.
Benefits
Network operators benefit from using Cisco Prime Network as a highly available and scalable platform to manage both Cisco and non-Cisco devices. Through its inherent ability to support Cisco and non-Cisco devices, the VNE driver technology allows Cisco Prime Network to support heterogeneous networks without requiring excessive customization costs. The mediation layer formed by the VNE driver technology is also the enabler for reducing the need for replication of mediation and abstraction layers through a common source of network-derived network element, network, and service inventory details plus network status and fault information. With the combination of frequently updated support for Cisco devices, third-party VNE drivers available for many commonly deployed non-Cisco devices, and rapid creation of VNE customizations and extensions, VNE driver technology offers service providers investment protection by keeping the element and network management updated and relevant as the network evolves.
Cisco Prime Network Third-Party VNE Drivers
Cisco Prime Network Third-Party VNE Reference Guide
A full list of Cisco Prime Network third-party VNE drivers for the latest release of Cisco Prime Network 3.8 is available in the most recent version of the Cisco Prime Network Third-Party VNE Reference Guide.
Cisco Prime Network Third-Party VNE Features
A side-by-side comparison of the options for third-party device management offered within Cisco Prime Network is provided in Table 1.
Table 1. Cisco Prime Network Third-Party Device Management Options
Features and Functionalities
Network Management Technology Group (NMTG)-Developed VNE for Cisco Device
NMTG-Developed VNE for Third-Party Device
User-Defined VNE with Generic Template
(Note 2)
Generic VNE
(Note 1)
Model for IP and Ethernet topology, logical attributes for routing table, Address Resolution Protocol (ARP), bridge using standard SNMP MIB
ü
ü
ü
ü
Monitor standard SNMP traps
ü
ü
ü
ü
Device identification
ü
ü
ü
User extensible with Cisco Prime Network Toolkit
ü
ü
ü
Physical Inventory discovery using device-specific MIB
ü
ü Note 3
Layer 2/Layer 3 logical inventory and topology discovery using device-specific MIB
ü
ü Note 3, Note 7
Support for device-specific SNMP traps and syslogs per customer specification
ü
ü Note 3
Image management and configuration archive/restore
ü
Maintain compatibility with Cisco Prime Network update release
ü
ü
Support service requests for device OS and management interface changes that affect device inventory discovery and event monitoring
ü Note 4
ü
Cisco Prime Network Right to Manage (RTM) and Software Application Support (SAS) cost (Cisco Prime Network will have a new RTM structure)
Groups A, B, C and D
Groups A, B, C and D
Group A
Group A
Field extension for additional physical inventory, events, and device maintenance upgrade
Note 5
Note 5
Note 5
Activation scripting using soft properties and Command Builder Cost
Note 6
Note 6
Note 6
Notes:
1. Generic VNE is not customizable. It is the default for any device not recognized by Cisco Prime Network.
2. User-defined generic VNE created using the VNE Customization Builder generic template at run time.
3. Contingency on device configuration and instrumentation available in customer lab devices.
4. VNE for Cisco IP NGN devices are also updated based on an interlock with Cisco releases.
5. Field extension of VNEs can be done by customer, their system integrator (SI) or AS. The customization is private to customer.
6. Activation is handled typically handled by soft properties and Command Builder scripting done by SI or AS.
7. Layer 2: Ethernet, VLAN, Dot1Q, QinQ, EtherChannel, Link Aggregation, POS, ATM, IMA, FR, PPP, DSL, VPLS, Local Switching, LLDP; Layer 3: IP and Routing, MPLS, LDP, MPLS-TE, VRF, RSVP-TE, MP-BGP, OSPF, PW, GRE, BFD; not all Cisco Prime Network advanced features will be supported for Cisco Prime Network third-party VNEs. For example, the following are not included: Image Management, Configuration Archive Restore, Event Correlation, Impact Analysis, Service Activation.
Ordering Information
A Right-to-Manage license for each non-Cisco device managed by Cisco Prime Network is required as listed in Table 2. The device series and device type determines the appropriate Right-to-Manage group.
Table 2. Right-to-Manage Part Numbers for Cisco Prime Network
Product Number
Description
NETWORK-3-NC-A-RTM
Prime Network 3.x - Non Cisco - Group A Right to Manage for non-Cisco devices
NETWORK-3-NC-B-RTM
Prime Network 3.x - Non Cisco - Group B Right to Manage for non-Cisco devices
NETWORK-3-NC-C-RTM
Prime Network 3.x - Non Cisco - Group C Right to Manage for non-Cisco devices
NETWORK-3-NC-D-RTM
Prime Network 3.x - Non Cisco - Group D Right to Manage for non-Cisco devices
To place an order contact your local Cisco account representative or visit the Cisco Download Software page at and click Cisco Prime Network VNE Drivers for Non Cisco Devices.
To request that Cisco evaluate developing a new third-party VNE, please contact a Cisco account team.
For More Information
For more information about Cisco Prime Network, visit http://www.cisco.com/go/primenetwork, contact your local Cisco account representative, or send an email to ask-prime@cisco.com. You can also contact ncvd-pteam@cisco.com for any assistance for customer evaluation of any third-party drivers with specific Cisco Prime Network releases.