Fujitsu PRIMERGY BX900 User manual

Configuration Guide
PRIMERGY BX900/BX400
Blade Server Systems
Ethernet Connection Blade Module SB6 / SB11a / SB11
IBP Version
English

PRIMERGY BX400/BX900 Connection Blades
Ethernet Connection Blades
PY CB Eth Switch/IBP 1 GB 18/6 (SB6)
PY CB Eth Switch/IBP 1 GB 36/12 (SB11a)
PY CB Eth Switch/IBP 1 GB 36/8+2 (SB11)
Configuration Guide
IBP version
Edition July 2011

©2011 Fujitsu Technology Solutions 2
Comments… Suggestions… Corrections…
The User Documentation Department would like to know your opinion on this manual. Your
feedback helps us to optimize our documentation to suit your individual needs.
Fax forms for sending us your comments are included at the back of the manual. There you
will also find the addresses of the relevant User documentation Department.
Copyright and Trademarks
Copyright © 2011 Fujitsu Technology Solutions GmbH.
All rights reserved.
Delivery subject to availability; right of technical modifications reserved.
All hardware and software names used are trademarks of their respective manufacturers

©2011 Fujitsu Technology Solutions 3
Content
1Configuration Guide Overview................................................................................ 6
2Configuring Management ........................................................................................ 7
2.1 Configuring In-band Management IP setting............................................................... 8
2.2 Configuring oob IP setting........................................................................................ 11
2.3 Configuring default gateway setting.......................................................................... 13
2.4 Upload Firmware Image and Configuration File........................................................ 15
3Overview Uplink and downlink.............................................................................. 17
4Packet handling in different group types ............................................................. 18
5Configuring Uplink Sets......................................................................................... 23
5.1 Creating Uplink Sets................................................................................................. 23
5.2 Configuring Link State.............................................................................................. 25
5.3 Configuring Backup Port........................................................................................... 26
6Configuring Port Groups ....................................................................................... 27
7Configuring VLAN Groups..................................................................................... 29
8Configuring Service LAN....................................................................................... 32
9Configuring Service VLAN..................................................................................... 33
10 Combining Port Groups and Service (V)LAN....................................................... 34
11 Configuring downlink LAG .................................................................................... 38
11.1 Configuring Link Aggregation with LACP.................................................................. 38
11.2 Configuring Static Link Aggregation.......................................................................... 40
11.3 Configuring Load Balance of Link Aggregation......................................................... 42
12 Private Network...................................................................................................... 44
13 Configuring QoS..................................................................................................... 46
13.1 Configuring priority control........................................................................................ 46
13.2 Configuring priority control rewrite............................................................................ 48
13.2.1 IP Precedence value rewrite..................................................................................... 48
13.2.2 Change queue of packets in VLAN........................................................................... 51
14 Configuring IGMP/MLD Snooping......................................................................... 53
15 Configuring IEEE 802.1X Authentication.............................................................. 54
15.1 Using Local User Name/ Password.......................................................................... 54
15.2 Using Remote RADIUS Server................................................................................. 56
16 Configuring Port Mirroring .................................................................................... 58
17 Configuring SNMP Agent....................................................................................... 59
17.1 Configuring SNMP Community................................................................................. 59
17.2 Configuring SNMP User........................................................................................... 60
17.3 Configuring SNMP Remote EngineID....................................................................... 61
17.4 Configuring SNMP Traps.......................................................................................... 62
17.5 Configuring SNMP Informs....................................................................................... 63

©2011 Fujitsu Technology Solutions 4
18 Configuring System Log........................................................................................ 64

©2011 Fujitsu Technology Solutions 5
Revision History
Revision Date Editor Remark
0.1 2/18/2009 Moore C. J. Lee 1st Draft
0.2 1/31/2011 Moore C. J. Lee Add SNMP informs
0.3 7/29/2011 Moore C. J. Lee Extended VLAN Group
0.35 1/19/2012 E.Schröer Merged SB6/SB11a/SB11

©2011 Fujitsu Technology Solutions 6
1 Configuration Guide Overview
This guide describes the PRIMERGY BX400/BX900 Ethernet Connection Blade specific
functions that you might encounter. Basically, the guide describes how to configure your switch
or how to configure software features on your switch. It also provides detailed information
about commands that have been created or changed for use by the Ethernet Connection
Blade.
Where “BX900” is shown in the examples below, it is synonymous to “BX400” when working
on a Primergy BX400 Blade Server System.
This document provides the following guidelines:
−Configuring Management
−Configuring Uplink Sets
−Configuring Port groups
−Configuring VLAN groups
−Configuring service LAN
−Configuring service VLAN
−Combining Port groups and service (V)LAN
−Configuring Downlink LAG
−Configuring Private Network
−Configuring QoS
−Configuring IGMP/MLD snooping
−Configuring IEEE 802.1X Authentication
−Configuring Port Mirroring
−Configuring SNMP Agent
−Configuring System Log
Mode Prompt
privileged EXEC mode (BX900-CB1)#
Configuration mode (BX900-CB1)(Config)#
Interface mode (BX900-CB1)(Interface BX900-CB1/0/1)#
Interface range mode (BX900-CB1)(if-range)#

©2011 Fujitsu Technology Solutions 7
2 Configuring Management
The BX900 Ethernet Connection Blade could be managed via two kinds of method. One is to
use console redirection from management blade, the other is to use IP network connection.
Two management interfaces for IP network connection, in-band and out-of-band management
interfaces, are provided for users to access and to manage the Ethernet Connection Blade.
Both of these two management interfaces could be configured to get the IP address via use
DHCP at a time, but not simultaneously.
The BX900 Ethernet Connection Blade supports only one default gateway in the system. User
could assign the default gateway for in-band management or out-of-band management
interface, but not simultaneously. If the gateway for the in-band management is set it is only
valid for the in-band management. If the user tries to set also the gateway for the out-of-band
management there will be an error message saying that the gateway for the in-band
management is already set and it is therefore not allowed to configure a second one. If the
gateway for the out-of-band management is set it is only valid for the out-of-band
management. Again an appropriate error message will be shown if it is tried to configure the
in-band management gateway. If user configure one of these two management ports to get the
IP address from DHCP server, the default gateway got from DHCP server will be overridden
the existed one. That is, the default gateway will always be valid for the management port
which is configured to use DHCP if the IP and default gateway are assigned by DHCP server
successfully.
This chapter will describe how to configure IP address for the in-band and out-of-band
management interfaces and how to configure the default gateway for the system on the BX900
Ethernet Connection Blade.

©2011 Fujitsu Technology Solutions 8
2.1 Configuring In-band Management IP setting
This section will describe how to configure the in-band management IP setting.
Beginning in privileged EXEC mode, follow these steps to configure management IP setting for
in-band management interface:
Command Purpose
Step 1 configure Enter global configuration mode.
Step 2 ip address protocol
<bootp|dhcp|none> To set IP management interface to use bootp, dhcp or none.
Step 3 ip address <ipaddress> <netmask>
[<vlanId>] To set a fixed IP address and net mask for management interface.
Step 4 exit Return to privileged EXEC mode.
Step 5 show ip interface Verify the configuration.
To configure a fixed IP address for the in-band management interface, use ip address
protocol none global configuration command. To set an IP address and net mask for
in-band management interface, use ip address global configuration command. To display
IP setting of in-band management interface, use show ip interface privileged EXEC
command.
In this example, in-band management interface is set to use IP address 192.168.2.1and
net mask 255.255.255.0. With this configuration, any untagged packets with the
destination IP of Ethernet Connection Blade will be allowed to access the Ethernet
Connection Blade.
(BX900-CB1)#configure
(BX900-CB1)(Config)#ip address protocol none
Changing protocol mode will reset ip configuration.
Are you sure you want to continue? (y/n)y
(BX900-CB1)(Config)#ip address 192.168.2.1 255.255.255.0
(BX900-CB1)(Config)#exit
(BX900-CB1)#show ip interface
IP address and netmask: 192.168.2.1 255.255.255.0,
and address mode: User specified.
InBand Mgmt Granted Ports: BX900-CB1/0/1, BX900-CB1/0/2, BX900-CB1/0/3,
BX900-CB1/0/4, BX900-CB1/0/5, BX900-CB1/0/6,
BX900-CB1/0/7, BX900-CB1/0/8, BX900-CB1/0/9,
BX900-CB1/0/10, BX900-CB1/0/11, BX900-CB1/0/12,
BX900-CB1/0/13, BX900-CB1/0/14, BX900-CB1/0/15,

©2011 Fujitsu Technology Solutions 9
BX900-CB1/0/16, BX900-CB1/0/17, BX900-CB1/0/18,
BX900-CB1/0/19, BX900-CB1/0/20, BX900-CB1/0/21,
BX900-CB1/0/22, BX900-CB1/0/23, BX900-CB1/0/24,
BX900-CB1/0/25, BX900-CB1/0/26, BX900-CB1/0/27,
BX900-CB1/0/28, BX900-CB1/0/29, BX900-CB1/0/30,
BX900-CB1/0/31, BX900-CB1/0/32, BX900-CB1/0/33,
BX900-CB1/0/34, BX900-CB1/0/35, BX900-CB1/0/36,
BX900-CB1/0/37, BX900-CB1/0/38, BX900-CB1/0/39,
BX900-CB1/0/40, BX900-CB1/0/41, BX900-CB1/0/42,
BX900-CB1/0/43, BX900-CB1/0/44, BX900-CB1/0/45,
BX900-CB1/0/46, BX900-CB1/0/47, BX900-CB1/0/48
InBand Mgmt Denied Ports: -
(BX900-CB1)#
In this example, assign a VLAN ID for the in-band management interface. With this
configuration, the received tagged packets with the same VLAN ID will be allowed to
access the Ethernet Connection Blade. Otherwise, the packets will be dropped.
(BX900-CB1)#configure
(BX900-CB1)(Config)#ip address protocol none
(BX900-CB1)(Config)#ip address 192.168.2.1 255.255.255.0 100
(BX900-CB1)(Config)#exit
(BX900-CB1)#show ip interface
IP address and netmask: 192.168.2.1 255.255.255.0 on VLAN 100,
and address mode: User specified.
InBand Mgmt Granted Ports: BX900-CB1/0/1, BX900-CB1/0/2, BX900-CB1/0/3,
BX900-CB1/0/4, BX900-CB1/0/5, BX900-CB1/0/6,
BX900-CB1/0/7, BX900-CB1/0/8, BX900-CB1/0/9,
BX900-CB1/0/10, BX900-CB1/0/11, BX900-CB1/0/12,
BX900-CB1/0/13, BX900-CB1/0/14, BX900-CB1/0/15,
BX900-CB1/0/16, BX900-CB1/0/17, BX900-CB1/0/18,
BX900-CB1/0/19, BX900-CB1/0/20, BX900-CB1/0/21,
BX900-CB1/0/22, BX900-CB1/0/23, BX900-CB1/0/24,
BX900-CB1/0/25, BX900-CB1/0/26, BX900-CB1/0/27,
BX900-CB1/0/28, BX900-CB1/0/29, BX900-CB1/0/30,
BX900-CB1/0/31, BX900-CB1/0/32, BX900-CB1/0/33,
BX900-CB1/0/34, BX900-CB1/0/35, BX900-CB1/0/36,

©2011 Fujitsu Technology Solutions 10
BX900-CB1/0/37, BX900-CB1/0/38, BX900-CB1/0/39,
BX900-CB1/0/40, BX900-CB1/0/41, BX900-CB1/0/42,
BX900-CB1/0/43, BX900-CB1/0/44, BX900-CB1/0/45,
BX900-CB1/0/46, BX900-CB1/0/47, BX900-CB1/0/48
InBand Mgmt Denied Ports: -
(BX900-CB1)#

©2011 Fujitsu Technology Solutions 11
2.2 Configuring oob IP setting
This section will describe how to configure the out-of-band (oob) management IP setting.
Beginning in privileged EXEC mode, follow these steps to configure management IP setting for
out-of-band management interface:
Command Purpose
Step 1 configure Enter global configuration mode.
Step 2 oob protocol
<bootp|dhcp|dhcp6|none> To set IP management interface to use bootp, dhcp, dhcpv6 or none.
Step 3 oob ip <ipaddr> <netmask> To set a fixed IP address and net mask for
management interface.
Step 4 exit Return to privileged EXEC mode.
Step 5 show oob Verify the configuration.
To configure to get IP address via DHCP protocol for the out-of-band management
interface, use oob protocol dhcp global configuration command. To set an IP address
and net mask for out-of-band management interface, use oob ip global configuration
command. To display IP setting of out-of-band management interface, use show oob
privileged EXEC command.
In this example, out-of-band management interface is configured to get the IP address via
DHCP protocol.
(BX900-CB1)#configure
(BX900-CB1)(Config)#oob protocol dhcp
Changing protocol mode will reset ip configuration.
Are you sure you want to continue? (y/n)y
(BX900-CB1)(Config)#exit
(BX900-CB1)#show oob
IP Address..................................... 172.16.2.125
Subnet Mask.................................... 255.255.255.0
Default Gateway................................ 172.16.2.254
IPv6 Address................................... FE80::21E:68FF:FE85:F760/64
OOB interface Configured Protocol.............. DHCP
Burned In MAC Address.......................... 00:1E:68:85:F7:60
(BX900-CB1)#

©2011 Fujitsu Technology Solutions 12
In this example, out-of-band management interface is configured with a fixed IP address
192.168.2.1 and a net mask 255.255.255.0.
(BX900-CB1)#configure
(BX900-CB1)(Config)#oob protocol none
Changing protocol mode will reset ip configuration.
Are you sure you want to continue? (y/n)y
(BX900-CB1)(Config)#oob ip 192.168.2.1 255.255.255.0
(BX900-CB1)#show oob
IP Address..................................... 192.168.2.1
Subnet Mask.................................... 255.255.255.0
Default Gateway................................ 0.0.0.0
IPv6 Address................................... FE80::21E:68FF:FE85:F760/64
OOB interface Configured Protocol.............. None
Burned In MAC Address.......................... 00:1E:68:85:F7:60
(BX900-CB1)#

©2011 Fujitsu Technology Solutions 13
2.3 Configuring default gateway setting
This section will describe how to configure the default gateway for the system.
Beginning in privileged EXEC mode, follow these steps to configure default gateway from
out-of-band management interface:
Command Purpose
Step 1 configure Enter global configuration mode.
Step 2 oob protocol
<bootp|dhcp|dhcp6|none> To set IP management interface to use bootp, dhcp, dhcpv6 or none.
Step 3 oob ip <ipaddr> <netmask> To set a fixed IP address and net mask for
management interface.
Step 4 oob gateway <gateway> To set the default gateway address.
Step 5 exit Return to privileged EXEC mode.
Step 6 show oob Verify the configuration.
To configure the default gateway for the out-of-band management interface, use oob
gateway global configuration command. To display IP setting of out-of-band management
interface, use show oob privileged EXEC command.
In this example, out-of-band management interface is configured with a fixed IP address
10.1.20.1 and default gateway 10.1.20.254.
(BX900-CB1)#configure
(BX900-CB1)(Config)#oob protocol none
Changing protocol mode will reset ip configuration.
Are you sure you want to continue? (y/n)y
(BX900-CB1)(Config)#oob ip 10.1.20.1 255.255.255.0
(BX900-CB1)(Config)#oob gateway 10.1.20.254
(BX900-CB1)(Config)#exit
(BX900-CB1)#show oob
IP Address..................................... 10.1.20.1
Subnet Mask.................................... 255.255.255.0
Default Gateway................................ 10.1.20.254
IPv6 Address................................... FE80::21E:68FF:FE85:F760/64
OOB interface Configured Protocol.............. None
Burned In MAC Address.......................... 00:1E:68:85:F7:60
(BX900-CB1)#

©2011 Fujitsu Technology Solutions 14
Beginning in privileged EXEC mode, follow these steps to configure default gateway from
in-band management interface:
Command Purpose
Step 1 configure Enter global configuration mode.
Step 2 ip address protocol
<bootp|dhcp|none> To set IP management interface to use bootp, dhcp, or none.
Step 3 ip address <ipaddr> <netmask> To set a fixed IP address and net mask for
management interface.
Step 4 ip default-gateway <gateway> To set the default gateway address.
Step 5 exit Return to privileged EXEC mode.
Step 6 show ip redirects Verify the configuration.
To configure the default gateway for the in-band management interface, use ip
default-gateway global configuration command. To display IP setting of in-band
management interface, use show ip redirects privileged EXEC command.
In this example, in-band management interface is configured with a fixed IP address
192.168.2.1 and default gateway 192.168.2.254.
(BX900-CB1)#configure
(BX900-CB1)(Config)#ip address protocol none
Changing protocol mode will reset ip configuration.
Are you sure you want to continue? (y/n)y
(BX900-CB1)(Config)# ip address 192.168.2.1 255.255.255.0
(BX900-CB1)(Config)#ip default-gateway 192.168.2.254
(BX900-CB1)(Config)#exit
(BX900-CB1)#show ip redirects
ip default gateway 192.168.2.254
(BX900-CB1)#
!
The gateway of in-band and out-of-band (oob) management interface can’t be set
at the same time. If the gateway of oob has been set, you have to remove it before
you configure the gateway of in-band management interface.

©2011 Fujitsu Technology Solutions 15
2.4 Upload Firmware Image and Configuration File
This section will describe how to upload the FW and configuration file from Ethernet
Connection Blade.
Beginning in privileged EXEC mode, follow these steps to upload firmware from Ethernet
Connection Blade:
Command Purpose
Step 1 copy image <filename> <url> To upload firmware specified in
<filename> to the <url> address where
<url>={xmodem | tftp://ipaddr/path/file |
ftp://user:pass@ipaddr/path/file}
To upload a firmware, use copy image privileged EXEC command.
In this example, a firmware will be uploaded via TFTP protocol to a TFTP server with IP
address 192.168.2.100.
!
Before performing the upload operation, you have to configure an IP address for
your Ethernet Connection Blade via DHCP protocol or manually.
(BX900-CB1)#copy image sb11a-sw-r-0.30.0213.biz tftp://192.168.2.100/sb11a-sw-r-0.30.0213.img
Mode........................................... TFTP
Set TFTP Server IP............................. 192.168.2.100
TFTP Path...................................... ./
TFTP Filename.................................. sb11a-sw-r-0.30.0213.img
Data Type...................................... Code
Management access will be blocked for the duration of the transfer
Are you sure you want to start? (y/n)y
TFTP code transfer starting
File transfer operation completed successfully.
(BX900-CB1)#

©2011 Fujitsu Technology Solutions 16
Beginning in privileged EXEC mode, follow these steps to upload configuration from Ethernet
Connection Blade:
Command Purpose
Step 1 copy startup-config <filename>
<url> To upload configuration file specified in <filename> to the <url> address where
<url>={xmodem | tftp://ipaddr/path/file |
ftp://user:pass@ipaddr/path/file}.
To upload a firmware, use copy startup-config privileged EXEC command.
In this example, a configuration file will be uploaded via TFTP protocol to a TFTP server
with IP address 192.168.2.100.
!
Before performing the upload operation, you have to configure an IP address for
your Ethernet Connection Blade via DHCP protocol or manually.
(BX900-CB1)#copy startup-config default.cfg tftp://192.168.2.100/backup_config.cfg
Mode........................................... TFTP
Set TFTP Server IP............................. 192.168.2.100
TFTP Path...................................... ./
TFTP Filename.................................. backup_config.cfg
Data Type...................................... Config File
Management access will be blocked for the duration of the transfer
Are you sure you want to start? (y/n)y
File transfer operation completed successfully.
(BX900-CB1)#

©2011 Fujitsu Technology Solutions 17
3 Overview Uplink and downlink
The ports (EXT37~EXT48 for SB11a, EXT37-EXT46 for SB11) connected to the external
network are called uplink port/external port, and the ports (INT1~INT36) connected to the NICs
of server blades are called downlink port/internal port. In SB11a, it provides 12 external ports
(8 RJ-45 ports and 4 SFP ports) and 36 downlink ports. In SB11, it provides 10 external ports
(8 RJ-45 ports and 2 SFP+ ports) and 36 downlink ports.
Uplink ports
Each uplink port is configured as a member of a LAG in default; it provides the external access
connection for Server Blade System. The configuration of uplink ports eliminates the need for
the Spanning Tree Protocol to prevent network loops and also provides a redundant function
for the external connection to improve network reliability.
In addition, the L2 failover feature is also provided for the uplink ports. With Network Adaptor
Teaming configured on the server blade Ethernet NIC, the servers can maintain redundant
links to multiple Ethernet Connection Blades within the Blade Server System to provide
enhanced reliability. The L2 failover feature allows the Ethernet Connection Blade to disable
the server-blade ports when all of its uplink ports are inactive. This causes the Network
Adaptor Teaming software to failover to the other Ethernet Connection Blade(s) in the Blade
Server System.
Downlink ports
Downlink port provides a network connection with 1Gbps full-duplex speed for the server
blades. The downlink ports could be configured as a member of a LAG to combine server
blade NICs connected to same Ethernet Connection Blade to provide a higher network
bandwidth for a server blade.

©2011 Fujitsu Technology Solutions 18
4 Packet handling in different group types
In IBP firmware version, it defines several groups, including Port groups, VLAN groups,
Service LAN, and Service VLAN. They provide different characteristics of handling packets.
Each group should combine an uplink set for its external connection. Packet handling in
different group types will be introduced in this chapter.
Port Groups
The downlink ports of Ethernet Connection Blade can be combined into Port Groups. Up to 36
port groups are available for the Ethernet Connection Blade with IBP firmware version. Each
Port Group could contain internal server ports (INT1-INT36).
All ports in a Port Group have the same configuration and are a member of a unique,
untagged/tagged VLAN. The packets are forwarded as it is received on Ethernet Connection
Blade, that is, tagged packets received from the server blades are forwarded include their tags
to all ports of the Port Group and untagged packets received from the server blades are
forwarded untagged to all ports of the Port Group. We call this as the VLAN transparent.
In addition, communication between Port Groups is not possible, nor is traffic from one group
visible in another group.
VLAN groups
The major difference to the traditional Port Group feature is that the grouping is defined on
VLAN base. It is similar to the port-based VLAN. Note that even though having identical VLAN
IDs, the VLANs in different VLAN port groups are different VLANs.
The incoming untagged packets received from the server blades will be tagged with the user
defined group VLAN tag and forwarded to the Uplink Set of the VLAN port group. The packets
leave the uplink(s) as tagged packets, the VLAN tag is not removed at the uplink(s). If the
server blade is sending tagged packets, they are dropped, except the tag is identical to the
defined Service VLAN ID. In this case it is handled according the Service VLAN definition,
forwarded to the Service VLAN Uplink Set.
The incoming tagged packets received at the uplink ports of VLAN port group are forwarded to
the downlink (server blade); according to their group VLAN tag definition. The tag is removed
at the downlink port, so that the server blades are receiving untagged packets. Packets tagged
with VLAN IDs other than defined by VLAN groups are dropped at the uplink(s), except those
tagged with the Service VLAN ID. They are handled according to Service VLAN group
definition.
Within the set of VLAN Port Groups sharing the same Uplink Set, one VLAN can be optionally
defined as “native VLAN”. This changes the tagging behavior at the uplink port for this native
VLAN ID. Incoming untagged packets are not dropped, but are tagged with the native VLAN ID
and forwarded to all the downlinks of this VLAN group. Incoming packets tagged with the
native VLAN ID are dropped at the uplink. Tagged packets with a VLAN ID that does not match
the VLAN ID of any other VLAN Port Group defined for this uplink set will be dropped. All