Cisco Cisco UCS B440 M1 High-Performance Blade Server 백서
© 2012 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public.
Page 40 of 106
Figure 14. Private Network
On Oracle RAC, private interconnect traffic does not travel northbound from Cisco UCS Fabric Interconnect B.
This behavior provides two advantages:
●
It results in very low latency for Oracle RAC traffic, in microseconds, because the Cisco UCS 6140 Fabric
Interconnects are part of the Cisco Nexus 5000 Series.
●
Oracle RAC traffic can be kept at the access-switch level, far away from the core of the network.
Only in the event of a Cisco UCS failure (for example, an IOM failure) could Oracle RAC traffic reach the data
center gateways. This behavior was considered acceptable for a failure state.
Note:
Because of the pinning setup, Cisco effectively has only 50 percent of the available Cisco UCS
northbound (public) bandwidth. Although 160 Gbps is physically available, only 80 Gbps is effectively used in the
Cisco setup for public traffic. However, the 80 Gbps is guaranteed during any kind of failure.
Multicasting for Cisco UCS Traffic
Because the traffic that needs to be multicast stays local to the Oracle RAC subnet, no special setup is required
on the Cisco Nexus 7000 Series or Cisco UCS components.