IBM 8677 Installation Guide - Page 87
Virtual, VLANs - service parts
UPC - 000435842312
View all IBM 8677 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 87 highlights
v TFTP server software must be running for TFTP services to work. v For the configuration file uploaded to a TFTP server to be saved correctly, you must first save switch module configurations to NVRAM. v Before the switch can upload its history log file to the TFTP server, an empty history log file must exist on the TFTP server. Virtual LANs (VLANs) VLANs allow multiple blade servers to be part of a logical group and prevents other servers that do not belong to a given group from gaining direct access to the group resources and data. The BladeCenter Ethernet switches can append a 4-byte VLAN tag to ingress frames on a per-port basis, and use the tag on certain frames to permit or block access to those frames at other ports. VLAN traffic can be restricted to a single BladeCenter unit or can extend across multiple BladeCenter units. When VLANs are extended across multiple BladeCenter units, intermediate switches use the VLAN tag to block frames from non-member destinations. When defining VLANs that span a chassis, consider the following: v Blade Server ports that are in the same VLAN must have the same VLAN ID v Define the same VLAN ID on both Ethernet switches for Blade Servers that use both switches to connect to the same external network. v Ethernet switch ports used to span multiple BladeCenter units must be configured as Tagged, with a specific default VLAN ID for any untagged packets. v The external ports and Link Aggregation Groups must be members of all VLANs that span multiple BladeCenter units. v The intermediate network device that interconnects the BladeCenter units must be configured to handle tagged VLAN packets for all applicable VLAN traffic that should be passed through the device. The BladeCenter unit default VLAN ID is 1 and includes all blade servers in the chassis. If multiple VLANs are required additional VLAN IDs must be configured. Review the following example to understand how VLANs can be configured. VLAN example The example shown in Figure 42 on page 78 defines three VLANs within a single BladeCenter unit and multiple VLANs extended to multiple BladeCenter units. Table 13 shows the defined VLAN parameters that are set to support this configuration. Egress packets for internal blade server ports must be Untagged. Table 13. Sample VLAN configuration definitions Port Number VLAN Id VLAN Name Tagged/Untagged Egress Packets 1 1 Default U 2 1 Default U 3 1 Default U 4 2 VLAN 2 U 5 2 VLAN 2 U 6 2 VLAN 2 U 7 3 VLAN 3 U 8 3 VLAN 3 U 9 3 VLAN 3 U Membership Egress/Forbid/None E 1 E 1 E 1 E 2 E 2 E 2 E 3 E 3 E 3 Chapter 5. Configuration considerations 77