Configuring an SNMP Subagent for a Virtual Switch

Add the new VSWITCH switchname keyword to a HOME statement in a z/VM® TCP/IP stack to define an interface which can be used by SNMP for communicating network management information for the virtual switch.

• Select a z/VM TCP/IP stack that has the SNMP service and SNMP subagent. It is recommended that the network connection for the stack providing connectivity to the SNMP service from the Network Management System (NMS) is separate from the managed virtual switches, so that a failure of a virtual switch connection can be reported to the NMS using SNMP traps.
• Update the TCP/IP configuration file for that stack, defining DEVICE, LINK, START, and HOME statements to provide an interface that can be reached by the NMS. Use the VSWITCH switchname option on the HOME statement to identify the virtual switch name.
• Update the TRAP destination file (SNMPTRAP DEST) to define a list of managers to which LINK_UP and LINK_DOWN traps are to be sent.
• Ensure that an SNMP subagent has been configured to provide VSWITCH MIB data. For information on setting up an SNMP subagent, refer to Configuring the SNMP Servers in the z/VM: TCP/IP Planning and Customization.