Cisco Cisco Prime Network 3.10 Installation Guide
24
Step 6
Check the Activate on creation check box to load the AVM, change its administrative status to Up, to ensure that the
AVM is loaded on subsequent restarts of the unit.
AVM is loaded on subsequent restarts of the unit.
Step 7
Click OK. The new AVM is added to the selected unit and is activated. The AVM can now host VNEs.
To Add VNEs
To manage your network elements (NEs) with Cisco Prime Network, you must add VNEs to the system. Each VNE represents
a single NE. Adding a VNE involves specifying identifying information and defining the communication protocols the VNE will
use to communicate with the NE. When the VNE loads, Prime Network starts investigating the NE and automatically builds a
live model of it, including its physical and logical inventory, its configuration, and its status.
a single NE. Adding a VNE involves specifying identifying information and defining the communication protocols the VNE will
use to communicate with the NE. When the VNE loads, Prime Network starts investigating the NE and automatically builds a
live model of it, including its physical and logical inventory, its configuration, and its status.
For detailed information about adding and managing VNEs, see
.
For the purposes of this Quick Start Guide, we assume the following:
•
The default Telnet protocol (not SSH) will be used for network element access (reachability) and modeling.
•
ICMP will not be enabled.
•
The default polling values will be used to determine polling intervals.
•
No additional IP addresses other than the management IP address will be monitored for events.
Before you begin to add VNEs:
1.
Make sure that the devices to be managed by Prime Network are configured according to the prerequisites. See
.
2.
Reduced polling is the default polling method used to model VNEs. For information on configuration required on devices
to enable reduced polling, see Device Configuration Tasks for VNE Creation in
to enable reduced polling, see Device Configuration Tasks for VNE Creation in
Tip
Place devices of the same type together in an AVM to reduce the memory consumption of the VNEs.
3.
To speed up the procedure for adding VNEs to Prime Network, prepare the following information for each device in
advance:
advance:
a.
Device management IP address
b.
SNMPv1 or v2: read and write community strings
c.
SNMPv3: The username and, optionally, the authentication or privacy configuration.
d.
Telnet port number and login sequence.
4.
Consider which VNE scheme to specify for your VNEs, Product, IPcore, EMS, or Default scheme. The VNE scheme
determines the network element information that is collected by a VNE and populated in its model. You should choose the
scheme based on the device’s role in the network. If you want to designate a router as a core Provider or Provider Edge
device in an MPLS VPN network, use IPCore, otherwise you can use Product. For details, see “Device Configuration Tasks
For VNE Creation” in the
determines the network element information that is collected by a VNE and populated in its model. You should choose the
scheme based on the device’s role in the network. If you want to designate a router as a core Provider or Provider Edge
device in an MPLS VPN network, use IPCore, otherwise you can use Product. For details, see “Device Configuration Tasks
For VNE Creation” in the
5.
Make sure that the status of the AVM to which you will be adding VNEs is Up.
To add VNEs to an AVM:
Step 1
Navigate to the required AVM in the navigation tree.
Step 2
Right-click the AVM, then choose New VNE. The New VNE dialog box is displayed.
Step 3
In the General tab, specify the following mandatory information in the relevant fields:
a.
VNE name, which will server as a unique identifier for the VNE.
b.
Device management IP address of the network element.