archives

force10 Config

This tag is associated with 9 posts

Force10 DCB Configuration – S4810 + MXL Sample / Example

. First, some background on DCB itself. DCB is an extension to Ethernet that enables the dedication of resources in the converged network. To ensure lossless delivery and latency-sensitive scheduling of storage, service traffic, and I/O convergence of LAN over a unified fabric, IEEE data centre bridging adds the following extensions to a classical Ethernet … Continue reading

Force10 S4810 VLT – Quick Configuration sample

. I have already given a non-technical synopsis on VLT in one of my previous posts here https://hasanmansur.com/2012/10/15/force10-s4810-stacking-vs-vlt/ As mentioned, VLT Is a Dual Active Control Plane implementation, of a Multi System LAG. Cisco vPC is a similar technology. VLT is beneficial in environments where the downstream devices like servers or access/distribution switches need to build … Continue reading

Force10 S60 – iSCSI configuration example – stacked, isolated.

. First, I would highly recommend you have a view of my earlier post that summarizes the various (platform independent) optimizations you can implement on an iSCSI fabric. These could be configured upfront, or tried  re-actively in case you have any performance or packet loss issues. the post can be found here https://hasanmansur.com/2012/10/14/switch-fabric-setup-for-equalogic-iscsi-powerconnect-switches/ . Force10 S60 … Continue reading

Force10 – Layer 2 Parameters – configuration ( VLANs, STP)

. I will start here with STP. As covered in one of my earlier posts, When configuring Spanning Tree on Force10 switches, you should accommodate whether your fabric is isolated, or inter-connects to other switches. The implications are as follows: On an isolated fabric or isolated switch segments, like the ones often used in iSCSI deployments, the … Continue reading

Force10 MXL Switch for M1000e Blade Chassis

. This is the first of three posts on MXL blade switches. While this gives an overview of the switch, the other two posts give configuration details for setting these up as Data and iSCSI fabrics, within M1000e Blade Chassis. The posts can be accessed here: Data fabric, M1000e: https://hasanmansur.com/2012/10/17/force10-mxl-configuration-data-fabric-for-m1000e-blade-chassis/ iSCSI Fabric, M1000e: https://hasanmansur.com/2012/10/17/force10-mxl-configuration-iscsi-fabric-for-m1000e-blade-chassis/ __ The MXL … Continue reading

Force10 MXL configuration – Data fabric for M1000e blade chassis

. If you see an issue where the MXL switch refuses to boot when placed in the M1000e chassis, be mindful that this may not be a hardware issue. the previous MXL firmware version, specifically version 8.3.16.1, does not support M1000e midplane version 1.0. This however, is resolved in the new revision 8.3.16.2. this is … Continue reading

Force10 MXL configuration – iSCSI fabric for M1000e blade chassis

. First, I would highly recommend you have a view of my earlier post that summarizes the various (platform independent) optimizations you can implement on an iSCSI fabric. These could be configured upfront, or tried  re-actively in case you have any performance or packet loss issues. the post can be found here https://hasanmansur.com/2012/10/14/switch-fabric-setup-for-equalogic-iscsi-powerconnect-switches/ If you see … Continue reading

Force10 S4810 – Stacking Vs. VLT

. Cisco offers three solutions for eliminating STP. These comprise the stacking feature on 3750/2950 models, VSS on 6500s, and vPC on Nexus 5k/7k platforms. An important point to remember in comparison of these three methods is that in vPC, the control planes of the peer switches are separate, unlike Stacking/VSS where all switches are … Continue reading

Cisco and Force10 – STP Spanning Tree Interoperability

. Cisco Implements a proprietary flavor of spanning tree protocol, which is Per-VLAN in nature. This gives rise to certain considerations in a multi-vendor environment. Any third party switches that implement STP based on the IEEE standard, have a spanning tree implementation that has a single instance span the entire switch, regardless of the number of VLANs … Continue reading