1. © 2009 Voltaire Inc.1 Fabric Management in VM environment Marina Lipshteyn, Voltaire

2. © 2009 Voltaire Inc.2 Existing approach is to have port profile manager Port Profile Manager External Switch OS/Hypervisor Manager IEEE 802.1x / EAPOL RADIUS

3. © 2009 Voltaire Inc.3 Active Fabric Manager role ► Discovery Discovery of virtual/physical switches, VEPA elements and their capabilities Discovery of physical and/or logical topology ► Policy/Configuration repository (eg. maintain port profile and states, endpoint authentication) ► Resource Management: Distribute policy across resources to meet the requirements specified in high level and drive security, QoS configurations in individual elements. For example: if there is a rate limiter both in the NIC and on the switches, determine the appropriate place for configuration. Resource allocation and validation  Resource management: eg. total number of ACLs supported by each device.  Verification that the CIR traffic can be committed. ► Monitoring Distributed monitoring of physical/virtual elements Notifications and reporting of various fabric events (eg. migration )

4. © 2009 Voltaire Inc.4 Example: VM migration ► VM migrates to a different physical machine. ► VM has a port profile which now is used to register at the new machine. ► ACLs should be configured at the new ingress point and should be removed from the old ingress point. ► However, the number of supported ACLs on the new ingress point now exceeds the limit (ACL compiler implementation dependent). ► The migration can not be done - invalid status must be propagated. ► Validation should be done by fabric manager.

5. © 2009 Voltaire Inc.5 Actors and Interactions Server/VM Manager Port/Fabric Manager Service Automation & Orchestration, Admins Set server/app policy Set vep/fabric policy,placement validation Reporting & monitoring Set/get (vm-nic) group policy, associations switches Hypervisors Discovery* (LLDP), State change requests Storage, license,.. managers Discovery* (LLDP/SNMP) push (switch) policy Change requests Monitoring* (SNMP,..) Deploy, migrate,.. * Current MIBs and mechanisms are associated with physical interfaces, may need to be extended Push/get policy State notifications, associations Get policy, Notifications

6. © 2009 Voltaire Inc.6 VM is registered at the new location – current passive Fabric Manager Server/VM Manager Port/Fabric Manager Service Automation & Orchestration, Admins switches Hypervisors 4 1 Register VM with the policy 6 2 Get vm-nic side policy by profile id 3 Configuration policy Get switch configuration 5 associate NO validation of Fabric resources is done. 8 Ack/ nack 7

7. © 2009 Voltaire Inc.7 VM is registered at the new location – active Fabric Manager with validation Server/VM Manager Port/Fabric Manager Service Automation & Orchestration, Admins switches Hypervisors 1 Validate/ placement filter of VM connectivity requirements INVALID! 2

8. © 2009 Voltaire Inc.8 VM is registered at the new location – active Fabric Manager Server/VM Manager Port/Fabric Manager Service Automation & Orchestration, Admins switches Hypervisors 2 3 Register VM with the policy Validate VM connectivity requirements 1 VALID Get vm-nic policy by profile id 5 Configuration policy 6 7 4 associate 8 Push switch policy 9 Ack/nack

9. © 2009 Voltaire Inc.9 Vport admin status down – can be Fabric Manager action Server/VM Manager Port/Fabric Manager Service Automation & Orchestration, Admins switches Hypervisors 2 1 Vport down 3 Find the relevant elements

10. © 2009 Voltaire Inc.10 Mirroring of a Vport – active Fabric Manager role Server/VM Manager Port/Fabric Manager Service Automation & Orchestration, Admins switches Hypervisors Mirror Vport 1 2 Configure mirrorring Find the relevant elements

11. © 2009 Voltaire Inc.11 Conclusion ► Previous examples show why Fabric Manager can not be static repository but requires dynamic behavior. ► Define API to Fabric Manager that enables set/get/validate of the policy, topology and capability discovery, state/configuration propagation.