Filter
Top Products
2-21
Cisco Prime Network 4.0 User Guide
OL-29343-01
Chapter 2 Working with the Prime Network Vision Client
Prime Network Vision Status Indicators
Table 2-11 and Table 2-12 describe network element communication and investigation states and shows
the related badge for each state.
Table 2-11 VNE Communication States
State Name Description Badge
Agent Not Loaded The VNE is not responding to the gateway because it was stopped, or it was just
created. This communication state is the equivalent of the Defined Not Started
investigation state.
None
VNE/Agent Unreachable The VNE is not responding to the gateway. This can happen if the unit or AVM is
overutilized, the connection between the gateway and unit or AVM was lost, or the
VNE is not responding in a timely fashion. (A VNE in this state does not mean the
device is down; it might still be processing network traffic.)
Connecting The VNE is starting and the initial connection has not yet been made to the device.
This is a momentary state. Because the investigation state decorator (the hourglass)
will already be displayed, a special GUI decorator is not required.
None
Device Partially Reachable The VNE is not fully reachable because at least one protocol is not operational.
Note This is the default behavior. You can change the settings that determine when
Cisco Prime Network moves a VNE to Device Unreachable. For more
information, see the Cisco Prime Network 4.0 Administrator Guide.
Device Unreachable The connection between the VNE and the device is down because all of the protocols
are down (though the device might be sending traps or syslogs).
Note This is the default behavior. You can change the settings that determine when
Cisco Prime Network moves a VNE to Device Unreachable. For more
information, see the Cisco Prime Network 4.0 Administrator Guide.
Tracking Disabled The reachability detection process is not enabled for any of the protocols used by the
VNE. The VNE will not perform reachability tests nor will Cisco Prime Network
generate reachability-related events. In some cases this is desirable; for example,
tracking for Cloud VNEs should be disabled because Cloud VNEs represent
unmanaged network segments.
Because this is a user-defined mode (rather than an error or transitional mode),
Cisco Prime Network does not display a decorator for this state. To troubleshoot a
VNE that is in this state, see the Cisco Prime Network 4.0 Administrator Guide.
None
Table 2-12 VNE Investigation States
State Name Description Badge
Defined Not Started A new VNE was created (and is starting); or an existing VNE was stopped. In this
state, the VNE is managed and is validating support for the device type. (This
investigation state is the equivalent of the Agent Not Loaded communication state.)
A VNE remains in this state until it is started (or restarted).
None
Unsupported The device type is either not supported by Prime Network or is misconfigured (it is
using the wrong scheme, or is using reduced polling but the device does not support
it).
To extend Cisco Prime Network functionality so that it recognizes unsupported
devices, use the VNE Customization Builder. See the Cisco Prime Network 4.0
Customization Guide.