Switch ID: ETHERNET0 ent1 Port VLAN ID: 101 Switch ID: rbRMHA_VSWITCH ent2 Port VLAN ID: 102 Switch ID: rbRMHA_VSWITCH # # uname -uL; /usr/ios/cli/ioscli ioslevel; oslevel -s IBM,0221E0B2V 1 rt13v1 3.1.0.00 7200-03-02-1845 # entstat -d ent7|grep -E "^Port\ VLAN|Switch" Port VLAN ID: 102 Switch ID: rbRMHA_VSWITCH Switch Mode: VEPA #  # uname -uL; /usr/ios/cli/ioscli ioslevel; oslevel -s IBM,0221E0B2V 2 rt13v2 3.1.0.00 7200-03-02-1845 # entstat -d ent5|grep -E "^Port\ VLAN|Switch" Port VLAN ID: 101 Switch ID: rbRMHA_VSWITCH Switch Mode: VEPA # The VEPA mode of the switch ensures complete isolation between connected VM Virtual  Ethernet adapters. They have connectivity only with the VIOS trunk adapter. The KSYS daemon is implemented as a Resource Monitoring and Control (RMC) resource  manager, and the  ksysmgr  CLI as an RMC client application. RMC is a subset function of  Reliable Scalable Cluster Technology (RSCT). Before going into detail about the KSYS  subsystem, we introduce some basic RMC concepts and terminology. RSCT is a set of software components that provide generic clustering services for AIX and  Linux platforms. It consists of various core subsystems, such as Group Services, Topology  Services, and System Registry. RMC is a subsystem of RSCT that is a generalized framework for managing, monitoring, and  manipulating system resources. By system resources, we mean various physical or logical  entities that are represented in an abstracted way in the RMC framework. Any resource  abstraction, simply called  resource , has  attributes  that describe configuration and state  characteristics of the modeled entity and  actions  to model behavior and changes, like in usual  object-oriented approaches. Resources with similar characteristics are instances of  predefined  resource classes . 52  Implementing IBM VM Recovery Manager for IBM Power Systems Resource Monitoring and Control concepts 2.2.4 KSYS as a Resource Monitoring and Control subsystem