Configure the S4048-ON ToR switches as follows, in accordance with recommended best practices:
- Enable Simple Network Management Protocol (SNMP).
- Configure Virtual Link Trunking (VLT) between the two S4048-ON switches using at least two of the 40 GbE link ports. VLT provides a loop-free environment by presenting two physical switches as one logical switch while not losing bandwidth for the devices connecting to it over two separate links.
- Configure the management IP address on each switch.
Note: The management IP address on the two switches is also used as the VLT backup link.
- Enable Rapid Spanning Tree Protocol (RSTP) on the switches.
A default bridge priority value of 32768 or higher ensures that neither of the ToR switches becomes the root bridge when plugged in to the core datacenter network.
- Enable spanning tree edge-port and spanning tree portfast on the ports that are used for Oracle Database private interconnect traffic. Doing so prevents any delays of the Oracle Grid infrastructure’s Cluster Synchronization Services (CSS) misscount that might lead to missed network heartbeats and Oracle node evictions.
- Create a port channel on both S4048-ON switches by using the port that connects to the S3048-ON management switch. Ensure that the port channel is configured as a VLT peer link aggregation group (LAG) on both switches.
- Enable jumbo frames (mtu 9216) on the ports to be used for Oracle Database private interconnect traffic.
- Configure the network traffic for Oracle public, backup and recovery, private interconnect, and private management on separate VLANs.
The following table shows an example of a VLAN configuration for the different traffic types.
Table 20. Example of VLAN IDs on S4048-ON switches
Oracle public, backup and recovery
Oracle private interconnect
Note: VLAN IDs that are shown in the preceding table are examples. Network administrators can use VLAN IDs that conform to their network policies and standards as long as the Oracle public and private networks are on two separate VLANs.