Cisco Systems 3.5 6.8 Defining VNEs

Managing AVMs and VNEs

Cisco Systems, Inc. Page 89

While in maintenance mode (temporary state) a VNE:

• Does not change state on its own, unless the user explicitly (manually)

switches the VNE back to active state.

• Never polls the device.

• Does not report any alarms, including device reachability.

• Maintains any existing links.

• Does not fail on verification requests.

For more information about maintenance mode, refer to page 104.

The table below describes the status of a VNE depending on the Admin and

Oper modes, as displayed in the Status column of the VNEs table. The

Admin mode is the administrative instructions that are sent to the VNE. The

Oper mode is the actual status of the VNE, for example, Up.

Status Admin Mode Oper Mode

Up Up Up

Shutting Down Down Up

Down Down Down

Starting Up Up Down

Unreachable Up

Unreachable

For example, if the user starts the VNE, the Admin status is Up but the Oper

status is Down and has not started yet (because the Server is busy), the status

is Starting Up. If the VNE is Up and running and the user stops the VNE,

the Admin status is Down but the process is not terminated immediately, the

status is Shutting Down.

6.8 Defining VNEs

The user adds and defines a new VNE for the system using Sheer DNA

Manage; this VNE corresponds to a Network Element (NE) and should only

be added to the system once. As the VNE loads, Sheer DNA starts

investigating the NE and automatically builds a live model of it, including its

physical and logical inventory, its configuration, and its status.

When adding a new VNE, Sheer DNA creates the registry information of the

new VNE in the Sheer DNA Unit. The newly created VNE has an

administrative status of Down and uses the default community strings and

polling rates. The VNE inherits these properties from the configuration

record that corresponds to the device type.