Cisco Viptela vManage support

Viptela vManage Alarms in ENA

To add an instance of Viptela vManage to ENA

Viptela device details

From ENA v17.0 P08 upwards, you can add vManage Cloud Controller device types and manage your Cisco Viptela (SD-WAN) alarms in ENA. ENA continuously retrieves the following information for each vManage Cloud Controller device:

• list of vEdge devices with key inventory-related attributes for each.
• list of alarms associated with a vManage Cloud Controller.

These details are displayed on the Summary dashboard for the vManage Cloud Controller and vEdge device types.

Viptela vManage Alarms in ENA:

Viptela vManage alarms on the Viptela dashboard and severity map to ENA EMS incidents and events and severity. All vManage alarms are active, but some of them might have been already acknowledged on the Viptela dashboard. In this case, opening and then closing events are raised to reflect this acknowledgement.

The ENA incidents and events (and severities) are as follows:

• vManage Alarm incident
  •  vManage Alarm 
  •  vManage Alarm Closed 
• vManage Poller Failed incident
  •  vManage Poller Failed 
  •  vManage Poller Success 
• vManage Poller Overrun incident
  •  vManage Poller Overrun 
  •  vManage Poller Overrun Cleared 

You can forward vManage events and incidents to third parties as you can with all other ENA events and incidents, such as BMC TrueSight Operations Management Events integration, Slack and Splunk.

To add an instance of Viptela vManage to ENA:

1. [usual method of adding a device].
2. In the Device Type field, select Cloud Controller.
3. In the Controller Type field, select vManage.
4. Complete the fields and click Add, otherwise click Cancel.

Viptela device details:

ENA collects the following information for each Viptela device:

Device inventory

• board type
• bootloader version (SNMP/API)
• build number
• device ID
• device model
• device name
• device type
• FIPs mode
• latitude, longitude
• local system IP
• personality
• serial number (SNMP/API)
• site-ID
• system IP
• time zone
• total CPU count
• UUID
• version

Device status

• certificate validity
• CPU usage (5 minute average) (SNMP/API)
• disk available & used
• memory utilization (SNMP/API)
• reachability
• state & state description

Control connections - a list of peers providing:

• controller group ID
• local & remote color
• peer protocol
• peer system IP, private IP, public IP
• peer type
• public & private port
• site-ID
• state

SLA class definitions

• class index
• class name
• jitter
• latency
• packet loss

BFD (bidirectional forwarding detection) session status

• source & destination IPs
• color
• source & destination ports
• site ID
• protocol
• uptime
• state
• uptime & last updated timestamps