Cisco Cisco Catalyst Blade Switch 3130 for Dell M1000E 백서
Design Guide
totally independent of the switch fabric. This Fast Ethernet port (Fa0) defaults to a DHCP client
from a DHCP server external on the network attached to the Enclosure. The user can also set a
static IP address for the Fast Ethernet port via the CMC interface or the serial port.
from a DHCP server external on the network attached to the Enclosure. The user can also set a
static IP address for the Fast Ethernet port via the CMC interface or the serial port.
When the CBS3130 is operated as a standalone switch, it operates in the same manner as the
CBS3030. However, when a collection of CBS3130s are connected via the high speed ring ports,
the switches operate as a single entity. In this mode, only the Fa0 port on the Master switch is
active. The Fa0 ports on the member switches are temporarily disabled. If the ring breaks, the two
separate new rings will have two new Master switches, and therefore, the Fa0 ports of those two
Master switches will both be active. For more information on this, see the Virtual Blade Switch
Operations Section in this document.
CBS3030. However, when a collection of CBS3130s are connected via the high speed ring ports,
the switches operate as a single entity. In this mode, only the Fa0 port on the Master switch is
active. The Fa0 ports on the member switches are temporarily disabled. If the ring breaks, the two
separate new rings will have two new Master switches, and therefore, the Fa0 ports of those two
Master switches will both be active. For more information on this, see the Virtual Blade Switch
Operations Section in this document.
In-Band Management
In-band management uses logical isolation to separate management traffic from data traffic. VLANs
segregate the two traffic types that are sharing the bandwidth of the uplink ports. This practice is
common where applications running on the servers must be managed along with the network
infrastructure devices.
segregate the two traffic types that are sharing the bandwidth of the uplink ports. This practice is
common where applications running on the servers must be managed along with the network
infrastructure devices.
In-band management traffic uses the uplink trunk ports located on the Cisco Catalyst Blade Switch
3130s for management. It is recommended that you do not put the user ports in the same VLAN as
the management VLAN.
3130s for management. It is recommended that you do not put the user ports in the same VLAN as
the management VLAN.
The Cisco Catalyst Blade Switch 3130 supports multiple switched virtual interfaces (SVIs) to be
active at the same time; however, the Cisco Catalyst Blade Switch 3130 does not perform any
routing functions between SVIs. By default, the SVI is created as VLAN 1 and enabled during the
setup phase of the installation. The VLAN is often referred to as the “management VLAN.” Cisco
Systems
active at the same time; however, the Cisco Catalyst Blade Switch 3130 does not perform any
routing functions between SVIs. By default, the SVI is created as VLAN 1 and enabled during the
setup phase of the installation. The VLAN is often referred to as the “management VLAN.” Cisco
Systems
®
recommends that the user change the management VLAN to something other than
VLAN 1. Therefore, it is important to create an SVI with another VLAN and allow this VLAN on the
external front panel ports. In addition, you can manage the switch using the Fa0 port using the
Onboard Administrator on the rear of the enclosure.
external front panel ports. In addition, you can manage the switch using the Fa0 port using the
Onboard Administrator on the rear of the enclosure.
For best practices in selecting the management VLAN, please visit:
Serial Console Port
The front panel of the Cisco Catalyst Blade Switch 3130 has a serial port that can be used to
manage the switch through the CLI. In addition, the CMC controls an internal serial port that can
be directed to the CBS3130 by using the “connect switch-x” command in the CMC CLI. The CLI
can be accessed by connecting directly to the external console port, by connecting via the
RACADM command in the CMC, or remotely by using terminal servers and IP connectivity
protocols such as telnet or SSH. Even when the switches are connected via the high speed ring
ports, all console ports are active. However, traffic is routed to the CPU on the Master switch.
Therefore, every console port acts the same. If the user is connecting the switches to a console
server, then the user should hook up at least two console cables per Virtual Blade Switch, to insure
connectivity in case of switch outage.
manage the switch through the CLI. In addition, the CMC controls an internal serial port that can
be directed to the CBS3130 by using the “connect switch-x” command in the CMC CLI. The CLI
can be accessed by connecting directly to the external console port, by connecting via the
RACADM command in the CMC, or remotely by using terminal servers and IP connectivity
protocols such as telnet or SSH. Even when the switches are connected via the high speed ring
ports, all console ports are active. However, traffic is routed to the CPU on the Master switch.
Therefore, every console port acts the same. If the user is connecting the switches to a console
server, then the user should hook up at least two console cables per Virtual Blade Switch, to insure
connectivity in case of switch outage.
© 2008 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.
Page 15 of 29