EVB Operations Overview
1. Define VSI types in the VSIDB. The VSIDB exports the database when the G8264
2. Create a VM. Specify VSI type for each VM interface. See the SNSC, FSM, or IBM
VSIDB Synchronization
394
G8264 Application Guide for ENOS 8.4
The ENOS includes a pre‐standards VSI Type Database (VSIDB) implemented
through the System Networking Switch Center (SNSC), the IBM Flex System
Manager (FSM), or the IBM System Networking Distributed Switch 5000V. The
VSIDB is the central repository for defining sets of network policies that apply to
VM network ports. You can configure only one VSIDB.
Note: This document does not include the VSIDB configuration details. Please see
the SNSC, FSM, or IBM System Networking Distributed Switch 5000V guide for
details on how to configure VSIDB.
The VSIDB operates in the following sequence:
metering sends a request.
System Networking Distributed Switch 5000V guide for details on how to specify
the VSI type.
The hypervisor sends a VSI ASSOCIATE, which contains the VSI type ID, to the
switch port after the VM is started. The switch updates its configuration based on
the requested VSI type. The switch configures the per‐VM bandwidth using the
VMpolicy.
The ENOS supports the following policies for VMs:
ACLs
Bandwidth
The switch periodically checks for VSIDB changes based on the configured
interval. You can configure this interval using the following command:
RS G8264(config)# virt evb vsidb <number>
RS G8264(confvsidb)# [no] updateinterval <time in seconds>
To disable periodic updates, use the "no updateinterval" command.
If the switch finds that the VSIDB has changed, it updates the local VSIDB cache.
When the cache is successfully updated, it sends a syslog message.
After updating the local VSIDB cache, the switch disassociates any VM whose type
ID or VLAN no longer exists in the updated cache.
The switch updates the local VSIDB cache when any of the following takes place:
When, at the configured refresh interval, the switch finds that the VSIDB
configuration has changed since the last poll.
When a VM sends an ASSOCIATE message, but the VSI type does not exist in
the local VSIDB cache.
When a VM sends an ASSOCIATE message, and the VSI type exists but the VSI
type's VLAN ID does not exist in the local VSIDB cache.