Filter
Top Products
REVIEW DRAFT—CISCO CONFIDENTIAL
A-20
Cisco Prime Network 4.0 User Guide
OL-29343-01
Appendix A Icon and Button Reference
Badges
VNE Communication State Badges
VNE Investigation State Badges
Table A-15 VNE Communication State Badges
Badge State Name Description
None 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.
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.)
None 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.
Device Partially Reachable The element is not fully reachable because at least one protocol is not operational.
Device Unreachable The connection between the VNE and the device id down because all of the protocols
are down (though the device might be sending traps or syslogs).
None 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 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.
Table A-16 VNE Investigation State Badges
Badge State Name Description
None 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) by a user.
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 Prime Network functionality so that it recognizes unsupported devices, use
the VNE Customization Builder. See the Cisco Prime Network 4.0 Customization
Guide.
Discovering The VNE is building the model of the device (the device type was found and is
supported by Prime Network). A VNE remains in this state until all device commands
are successfully executed at least once, or until there is a discovery timeout.