Cisco Cisco Prime Network 3.8 Merkblatt
© 2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.
Page 3 of 4
A side-by-side comparison of the options for Cisco and third-party device management is provided in Table 2.
Table 2.
Cisco Prime Network Cisco and Third-Party Device Management Options
Features and Functions
VNE for Cisco
Devices
Devices
VNE for Third-
Party Devices
Party Devices
User-Defined
VNE with
Generic
Template
(Note 2)
VNE with
Generic
Template
(Note 2)
Generic VNE
(Note 1)
(Note 1)
Model for IP and Ethernet topology, logical attributes for
routing table, Address Resolution Protocol (ARP), and
bridge using standard SNMP MIB
routing table, Address Resolution Protocol (ARP), and
bridge using standard SNMP MIB
Standard SNMP traps monitoring
Device identifications
User extensibility 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
using device-specific MIB
Note 3, Note 6
Support for device-specific SNMP traps and syslogs per
customer specifications
customer specifications
Note 3
Change and configuration management
Compatibility with Cisco Prime Network update releases
Support for service requests of device OS and
management interface changes that affect device
inventory discovery and event monitoring
management interface changes that affect device
inventory discovery and event monitoring
Field extensions for additional physical inventory, events,
and device maintenance upgrades
and device maintenance upgrades
Note 4
Note 4
Note 4
Activation script using Command Builder
Note 5
Note 5
Note 5
Notes:
1. The generic VNE is not customizable. It is the default for any device not recognized by Cisco Prime Network.
2. The user-defined generic VNE is created using the Cisco Prime Network VCB generic template at run time.
3. The feature is contingent on device configuration and instrumentation available in customer
1. The generic VNE is not customizable. It is the default for any device not recognized by Cisco Prime Network.
2. The user-defined generic VNE is created using the Cisco Prime Network VCB generic template at run time.
3. The feature is contingent on device configuration and instrumentation available in customer
’s lab devices.
4. Field extensions can be performed by customers, a systems integrator (SI), or Cisco AS. For example, soft properties can be
added using VCB and other extensions can be scripted using Command Builder.
5. Activation is typically handled by Command Builder and performed by customers, an SI, or Cisco AS.
6. Layer 2: Ethernet, VLAN, Dot1Q, QinQ, Cisco EtherChannel, Link Aggregation, PoS, ATM, IMA, FR, PPP, DSL, VPLS, Local
6. Layer 2: Ethernet, VLAN, Dot1Q, QinQ, Cisco 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, and service
activation.
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, and service
activation.
Device Support
Cisco Prime Network, starting with Release 4.2, will no longer natively support third-party devices and their related
services. If customers wish to manage third-party devices after transitioning to Version 4.2, customers will need to
engage Cisco Advanced Services for support.
More information about supported Cisco devices and third-party devices, software versions, and device contents
can be found in the