Fujitsu Siemens Computers PRIMERGY BX, PRIMERGY BX600 Description

Lan Switch and Router Blade

PRIMERGY BX Blade Server Systems

LAN Router and

Switch Blade

User Interface De

scri

ption

Editon March 2006

Lan Switch and Router Blade

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

Delivery subject to availability; right of technical modifications reserved.

All hardware and software names used are trademarks of their respective manufacturers.

Lan Switch and Router Blade

Important Notes

Introduction

Networking Planning

Making Network Connection

Configuration the Switch Blade

Web Base Command Interface

Command Reference

Using SNMP

System Defaulting

Troubleshooting and Tips

Lan Switch and Router Blade

CONTENTS

1 Important Notes...............................................................................................................10

1.1 Information About Boards.......................................................................................... 10

1.2 Compliance Statements ............................................................................................ 11

2 Introduction .....................................................................................................................14

2.1 Features of the Switch...............................................................................................14

2.1.1 MAC Address Supported Features................................................................15

2.1.2 Layer 2 Features...................................................................................................16

2.1.3 Spanning Tree Protocol Features.......................................................................... 18

2.1.4 Ethernet Switch Module Management Features ...................................................19

2.1.5 Security Features..................................................................................................... 21

2.1.6 Quality of Service Features...................................................................................21

2.1.7 Layer III Routing Features..................................................................................... 23

IP Routing..................................................................................................................23

Routing Information Protocol (RIP)............................................................................ 23

BOOTP/DHCP Relay Agent....................................................................................... 24

Virtual Router Redundancy Protocol (VRRP)............................................................ 24

Router Discovery .......................................................................................................24

Virtual LAN (VLAN) Routing ...................................................................................... 25

Route Redistribution .................................................................................................. 25

Route Preferences..................................................................................................... 25

Open Shortest Path First (OSPF).............................................................................. 26

DNS and DNS Relay ................................................................................................. 27

IP Multinetting............................................................................................................27

2.1.8 IP Multicast Features ............................................................................................27

IGMPv3...................................................................................................................... 27

Protocol Independent Multicast – Dense Mode (PIM-DM) ........................................28

Protocol Independent Multicast – Sparse Mode (PIM-SM)........................................29

Distance Vector Multicast Routing Protocol (DVMRP) ..............................................30

2.2 Description of Hardware............................................................................................31

2.2.1 Ethernet Ports .......................................................................................................31

2.3 Features and Benefits ...............................................................................................33

2.4

Notational Conventions

..............................................................................................34

2.5

Ta r g e t Group

..............................................................................................................35

2.6

Technical Data

...........................................................................................................36

3 Network Planning ............................................................................................................ 38

Lan Switch and Router Blade

3.1

Introduction to Switching

...........................................................................................38

3.2

Sample Applications

..................................................................................................39

4 Making Network Connections .........................................................................................41

4.1

Connecting to 1000BASE-T Devices

.........................................................................41

4.2

1000BASE-T Cable Requirements

............................................................................42

4.3

1000BASE-T Pin Assignments

...................................................................................43

5 Configuration the Switch Blade Module .......................................................................... 44

5.1 Overview ...................................................................................................................44

5.2 Connecting the Ethernet Switch Module ...................................................................45

5.3 Start up and Configuration the Ethernet Switch Module............................................ 47

5.4 Configuring the Terminal ...........................................................................................48

5.5 Booting Device ..........................................................................................................49

5.6 Software Download ...................................................................................................50

5.6.1 In BootROM Back Door CLI ..........................................................................50

5.6.2 In Operation Code CLI...................................................................................51

6 Web-Based Management Interface ................................................................................54

6.1 Overview ...................................................................................................................54

6.2 Main Menu ................................................................................................................55

6.2.1 System Menu.................................................................................................55

6.2.2 Switching Menu ........................................................................................... 113

6.2.3 Routing Menu ..............................................................................................153

6.2.4 Security Menu..............................................................................................212

6.2.5 QOS Menu...................................................................................................231

6.2.6 IP Multicast Menu ........................................................................................ 255

7 Command Reference .................................................................................................... 285

7.1 CLI Command Format.............................................................................................285

7.2 CLI Mode-based Topology ......................................................................................286

7.3 System Information and Statistics commands......................................................... 288

7.3.1 show arp...................................................................................................... 288

7.3.2 show calendar .............................................................................................288

7.3.3 show eventlog..............................................................................................289

7.3.4 show running-config ....................................................................................289

7.3.5 show sysinfo................................................................................................ 290

7.3.6 show system................................................................................................ 291

7.3.7 show hardware ............................................................................................291

7.3.8 show version................................................................................................292

7.3.9 show loginsession .......................................................................................293

Lan Switch and Router Blade

7.4 Device Configuration Commands............................................................................294

7.4.1 Interface.......................................................................................................294

7.4.2 L2 MAC Address and Multicast Forwarding Database Tables..................... 307

7.4.3 VLAN Management .....................................................................................312

7.4.4 GVRP and Bridge Extension .......................................................................326

7.4.5 IGMP Snooping ...........................................................................................336

7.4.6 Port Channel................................................................................................348

7.4.7 Storm Control...............................................................................................355

7.4.8 L2 Priority ....................................................................................................362

7.4.9 Port Mirror....................................................................................................364

7.5 Management Commands ........................................................................................ 366

7.5.1 Network Commands .................................................................................... 366

7.5.2 Serial Interface Commands ......................................................................... 373

7.5.3 Telnet Session Commands..........................................................................376

7.5.4 SNMP Server Commands ...........................................................................382

7.5.5 SNMP Trap Commands...............................................................................391

7.5.6 HTTP commands.........................................................................................395

7.5.7 Secure Shell (SSH) Commands .................................................................. 399

7.5.8 DHCP Client Commands.............................................................................401

7.5.9 DHCP Relay Commands.............................................................................402

7.6 Spanning Tree Commands......................................................................................405

7.6.1 Show Commands ........................................................................................405

7.6.2 Configuration Commands............................................................................412

7.7 System Log Management Commands .................................................................... 422

7.7.1 Show Commands ........................................................................................422

7.7.2 show logging buffered .................................................................................423

7.7.3 show logging traplog....................................................................................423

7.7.4 Configuration Commands............................................................................424

7.8 Script Management Commands..............................................................................429

7.8.1 script apply ..................................................................................................429

7.8.2 script delete .................................................................................................429

7.8.3 script list.......................................................................................................430

7.8.4 script show...................................................................................................430

7.9 User Account Management Commands..................................................................431

7.9.1 Show Commands ........................................................................................431

7.9.2 Configuration Commands............................................................................432

7.10 Security Commands................................................................................................434

Lan Switch and Router Blade

7.10.1 Show Commands ........................................................................................ 434

7.10.2 Configuration Commands............................................................................446

7.10.3 Dot1x Configuration Commands .................................................................448

7.10.4 Radius Configuration Commands................................................................ 455

7.10.5 TACACS Configuration Commands ............................................................459

7.10.6 Port Security Configuration Commands ......................................................462

7.11 CDP (Cisco Discovery Protocol) Commands.......................................................... 465

7.11.1 Show Commands ........................................................................................465

7.11.2 Configuration Commands............................................................................ 467

7.12 Link up & Port Backup State Commands ................................................................ 470

7.12.1 Show Commands ........................................................................................ 470

7.12.2 Configuration Commands............................................................................471

7.13 SNTP (Simple Network Time Protocol) Commands................................................ 474

7.13.1 Show Commands ........................................................................................ 474

7.13.2 Configuration Commands............................................................................476

7.14 System Utilities........................................................................................................ 481

7.14.1 clear.............................................................................................................481

7.14.2 copy ............................................................................................................. 489

7.14.3 delete...........................................................................................................491

7.14.4 dir................................................................................................................. 492

7.14.5 whichboot ....................................................................................................492

7.14.6 boot-system ................................................................................................. 493

7.14.7 ping..............................................................................................................493

7.14.8 traceroute ....................................................................................................494

7.14.9 logging cli-command.................................................................................... 495

7.14.10 calendar set ................................................................................................. 495

7.14.11 reload........................................................................................................... 496

7.14.12 configure......................................................................................................496

7.14.13 disconnect ...................................................................................................497

7.14.14 hostname.....................................................................................................497

7.14.15 quit ........................................................................................................ 497

7.15 Differentiated Service Command ............................................................................ 498

7.15.1 General Commands ....................................................................................499

7.15.2 Class Commands ........................................................................................ 500

7.15.3 Policy Commands........................................................................................ 508

7.15.4 Service Commands .....................................................................................514

7.15.5 Show Commands ........................................................................................ 515

Lan Switch and Router Blade

7.16 ACL Command ........................................................................................................ 523

7.16.1 Show Commands ........................................................................................ 523

7.16.2 Configuration Commands............................................................................526

7.17 CoS (Class of Service) Command .......................................................................... 530

7.17.1 Show Commands ........................................................................................ 530

7.17.2 Configuration Commands............................................................................533

7.18 Address Resolution Protocol (ARP) Commands..................................................... 540

7.18.1 Show Commands ........................................................................................ 540

7.18.2 Configuration Commands............................................................................542

7.19 IP Routing Commands ............................................................................................ 546

7.19.1 Show Commands ........................................................................................ 546

7.19.2 Configuration Commands............................................................................550

7.20 Open Shortest Path First (OSPF) Commands ........................................................555

7.20.1 Show Commands ........................................................................................ 555

7.20.2 Configuration Commands............................................................................564

7.21 Bootp/DHCP Relay Commands ..............................................................................584

7.21.1 show bootpdhcprelay................................................................................... 584

7.21.2 bootpdhcprelay cidoptmode ........................................................................585

7.21.3 bootpdhcprelay enable ................................................................................ 585

7.21.4 bootpdhcprelay maxhopcount .....................................................................585

7.21.5 bootpdhcprelay minwaittime ........................................................................586

7.21.6 bootpdhcprelay serverip .............................................................................. 586

7.21.7 ip dhcp restart..............................................................................................587

7.21.8 ip dhcp client-identifier.................................................................................587

7.22 Domain Name Server Relay Commands ................................................................588

7.22.1 Show Commands ........................................................................................ 588

7.22.2 Configuration Commands............................................................................589

7.23 Routing Information Protocol (RIP) Commands...................................................... 594

7.23.1 Show Commands ........................................................................................ 594

7.23.2 Configuration Commands............................................................................597

7.24 Router Discovery Protocol Commands ...................................................................604

7.24.1 show ip irdp .................................................................................................604

7.24.2 ip irdp...........................................................................................................605

7.24.3 ip irdp broadcast .......................................................................................... 605

7.24.4 ip irdp holdtime ............................................................................................ 605

7.24.5 ip irdp maxadvertinterval .............................................................................606

7.24.6 ip irdp minadvertinterval ..............................................................................606

Lan Switch and Router Blade

7.24.7 ip irdp preference......................................................................................... 607

7.25 VLAN Routing Commands ......................................................................................607

7.25.1 show ip vlan.................................................................................................607

7.25.2 vlan routing .................................................................................................. 608

7.26 Virtual Router Redundancy Protocol (VRRP) Commands ......................................609

7.26.1 Show Commands ........................................................................................ 609

7.26.2 Configuration Commands............................................................................ 611

7.27 Distance Vector Multicast Routing Protocol (DVMRP) Commands......................... 615

7.27.1 Show Commands ........................................................................................ 615

7.27.2 Configuration Commands............................................................................619

7.28 Internet Group Management Protocol (IGMP) Commands..................................... 620

7.28.1 Show Commands ........................................................................................ 620

7.28.2 Configuration Commands............................................................................624

7.29 Multicast Commands............................................................................................... 629

7.29.1 Show Commands ........................................................................................ 629

7.29.2 Configuration Commands............................................................................635

7.30 Protocol Independent Multicast – Dense Mode (PIM-DM) Commands...................641

7.30.1 Show Commands ........................................................................................ 641

7.30.2 Configuration Commands............................................................................643

7.31 Protocol Independent Multicast – Sparse Mode (PIM-SM) Commands ..................645

7.31.1 Show Commands ........................................................................................ 645

7.31.2 Configuration Commands............................................................................650

8 Using SNMP..................................................................................................................656

8.1

Supported MIBs

.......................................................................................................657

8.2

Accessing MIB Objects

............................................................................................659

8.3

Supported Tr a p s

......................................................................................................662

9 Default Settings.............................................................................................................663

9.1 The overview default settings for the system module are shown in the following table.

................................................................................................................................663

9.2 The default settings for all the configuration commands are shown in the following table.

................................................................................................................................665

10 Troubleshooting and Tips ..............................................................................................673

10.1

Diagnosing Switch Indicators

...................................................................................673

10.2

Accessing the Management Interface

......................................................................673

Information About Boards Important Notes

Lan Switch and Router Blade

1 Important Notes

Store this manual close to the device. If you pass the device on to third parties, you should pass this manual on with it.

Be sure to read this page carefully and note the information before you open the device.

You cannot access the switch blade without first opening the device. How to dismantle and reassemble the device is described in the Operating Manual accompanying the device.

Please observe the safety information provided in the “Important Notes” chapter in the device’s operating manual.

Components can become very hot during operation. Ensure you do not touch components when handling the device. There is a danger of burns!

The warranty is invalidated if the device is damaged during the installation.

1.1 Information About Boards

To prevent damage to the device or the components and conductors on it, please take great care when you insert or remove it. Take great care to ensure that the board is slotted in straight, without damaging components or conductors on it, or any other components.

Be especially careful with the locking mechanisms (catches, centering pins etc.) when you replace the board.

Never use sharp objects (screwdrivers) for leverage.

Boards with electrostatic sensitive devices (ESD) are identifiable by the label shown.

When you handle boards fitted with ESDs, you must, under all circumstances, observe the following points:

You must always discharge static build up (e.g., by touching a grounded object) before working.

The equipment and tools you use must be free of static charges.

Remove the power plug from the mains supply before inserting or removing boards containing ESDs.

Always hold boards with ESDs by their edges.

Never touch pins or conductors on boards fitted with

ESDs.

Compliance Statements Important Notes

Lan Switch and Router Blade

1.2 Compliance Statements

FCC Class A Compliance

This equipment has been tested and found to comply with the limits for a “Class A” digital device, pursuant to Part 15 of the FCC rules and meets all requirements of the Canadian Interference-Causing Equipment Regulations. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in strict accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures:

Reorient or relocate the receiving antenna. Increase the separation between equipment and the receiver. Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.

Consult the dealer or an experienced radio/TV technician for help.

Fujitsu Siemens Computers is not responsible for any radio or television interference caused by unauthorized modifications of this equipment or the substitution or attachment of connecting cables and equipment other than those specified by Fujitsu Siemens Computers. The correction of interferences caused by such unauthorized modification, substitution or attachment will be the responsibility of the user.

You may use unshielded twisted-pair (UTP) cables for RJ-45 connections – Category 3 or greater for 10 Mbps connections, Category 5 for 100 Mbps connections, and Category 5 or 5e for 1000 Mbps connections.

Wear an anti-static wrist strap or take other suitable measures to prevent

electrostatic discharge when handling this equipment.

Industry Canada - Class A

This digital apparatus does not exceed the Class A limits for radio noise emissions from digital apparatus as set out in the interference-causing equipment standard entitled “Digital Apparatus,” ICES-003 of the Department of Communications.

Cet appareil numérique respecte les limites de bruits radioélectriques appli- cables aux appareils numériques de Classe A prescrites dans la norme sur le matériel brouilleur: “Appareils Numériques,” NMB-003 édictée par le ministère des Communications.

Compliance Statements Important Notes

Lan Switch and Router Blade

Japan VCCI Class A

CE Mark Declaration of Conformance for EMI and Safety (EEC)

This information technology equipment complies with the requirements of the Council Directive 89/336/EEC on the Approximation of the laws of the Member States relating to Electromagnetic Compatibility and 73/23/EEC for electrical equipment used within certain voltage limits and the Amendment Directive

93/68/EEC. For the evaluation of the compliance with these Directives, the following standards were applied:

RFI Emission: • Limit class A according to EN 55022:1998

• Limit class A for harmonic current emission according to EN 61000-3-2/1995

• Limitation of voltage fluctuation and flicker in low-voltage supply system according to EN 61000-3-3/1995

Immunity: • Product family standard according to EN 55024:1998

• Electrostatic Discharge according to EN 61000-4-2:1995

(Contact Discharge: ±4 kV, Air Discharge: ±8 kV)

• Radio-frequency electromagnetic field according to EN 61000-4-3:1996

(80 - 1000 MHz with 1 kHz AM 80% Modulation: 3 V/m)

• Electrical fast transient/burst according to EN 61000-4-4:1995 (AC/DC power supply: ±1 kV, Data/Signal lines: ±0.5

kV)

• Surge immunity test according to EN 61000-4-5:1995

(AC/DC Line to Line: ±1 kV, AC/DC Line to Earth: ±2 kV)

• Immunity to conducted disturbances, Induced by radio-frequency fields:

EN 61000-4-6:1996 (0.15 - 80 MHz with 1 kHz AM 80% Modulation: 3 V/m)

• Power frequency magnetic field immunity test according to EN 61000-4-

8:1993 (1 A/m at frequency 50 Hz)

• Vol tage dips, short interruptions and voltage variations immunity test according to EN 61000-4-11:1994 (>95% Reduction @10 ms, 30% Reduction @500 ms, >95% Reduction @5000 ms)

LVD:

• EN 60950 (A1/1992; A2/1993; A3/1993; A4/1995; A11/1997)

Do not plug a phone jack connector in the RJ-45 port. This may damage

this device. Les raccordeurs ne sont pas utilisé pour le système télépho- nique!

Compliance Statements Important Notes

Lan Switch and Router Blade

Taiwan BSMI Class A

Australia AS/NZS 3548 (1995) - Class A

Features of the Switch Introduction

Lan Switch and Router Blade

2 Introduction

The

PRIMERGY BX

Blade Server system is a modular server system that can integrates up to 10 server modules, four Ethernet Switch Modules (one switch will be included in the base enclosure, the other three are optional) and two Management Modules (MMB). The Ethernet Module provides networking or Switch functions to PRIMERGY BX Blade Server. The Management Modules provides a single point of control for the PRIMERGY BX Blade Server.

The PRIMERGY BX600 Ethernet Switch Modules are 18-port devices that are connected to servers through the mid-plane connectors located on PRIMERGY BX Blade Server middle plane. The device has 18 ports. The ports numeration starts from the internal ports g1-g10 connected to server blades, and ports g11-g16 are the external ports connecting the Ethernet Switch Module to the network through the internal ports. The g17 is the XFP module interface and the g18 port is 10 G the module for CX4 interface.

• six external RJ-45 connectors for 10/100/1000 Base-T copper ports (uplinks).

• two external module CX4 or XFP connectors for 10 Gigabit ports (uplinks).

• 10 internal ports connected to servers through PRIMERGY BX Blade Server mid-plane connector of a VHDM type.

The terminal connection to the device is provided through the MMB board only. No access point is provided on the Ethernet Switch Module front panel. For debugging and management purposes, a UART bus of each Ethernet Switch Module is connected to the MMB board. The MMB board can select for management only one switch at a time.

The Ethernet Switch Module receives a power supply (12 V dc) through the mid-plane connector. A four system LED indicates the Ethernet Switch Module status (Power module,MMB-selected or not, CX4 and XFP interface or not).

The following figure illustrates the PRIMERGY BX600:

Figure 1-1. PRIMERGY BX600 GESwitch Blade Front Panel

2.1 Features of the Switch

The switch provides a wide range of advanced performance-enhancing features. Multicast filtering provides support for real-time network applications. Port-based and tagged VLANs, plus support for automatic GVRP VLAN registration provide traffic security and efficient use of network bandwidth. QoS priority queueing ensures the minimum delay for moving real-time multi-media data across the

Features of the Switch Introduction

Lan Switch and Router Blade

network. Flow control eliminates the loss of packets due to bottlenecks caused by port saturation. And broadcast storm suppression prevents broadcast traffic storms from engulfing the network. Some of the management features are briefly described below.

Head of Line Blocking

Head of Line (HOL) blocking results in traffic delays and frame loss caused by traffic competing for the same egress port resources. HOL blocking queues packets, and the packets at the head of the queue are forwarded before packets at the end of the queue.

Flow Control Support (IEEE 802.3X)

Flow control enables lower speed devices to communicate with higher speed devices, by requesting that the higher speed device refrains from sending packets. Transmissions are temporarily halted to prevent buffer overflows.

Back Pressure Support

On half-duplex links, the receiving port prevents buffer overflows by occupying the link so that it is unavailable for additional traffic.

Jumbo Frames Support

Jumbo frames are frames with an MTU size of up to 9K bytes, and better utilize the network by transporting the same data using less frames. The main benefits of this facility are reduced transmission overhead, and reduced host processing overhead. Less frames leads to less I/O interrupts. This facility is typically used for server-to-server transfers.

MDI/MDIX Support

The Ethernet Switch Module automatically detects whether the cable connected to an RJ-45 port is crossed or straight through. Standard wiring for end stations is Media-Dependent Interface (MDI) and the standard wiring for hubs and switches is known as Media-Dependent Interface with Crossover (MDIX).

Auto Negotiation

Auto negotiation allows an Ethernet Switch Module to advertise modes of operation. The auto negotiation function provides the means to exchange information between two devices that share a point-to-point link segment, and to automatically configure both devices to take maximum advantage of their transmission capabilities.

2.1.1 MAC Address Supported Features

MAC Address Capacity Support

The Ethernet Switch Module supports up to 8K MAC addresses. The Ethernet Switch Module reserves specific MAC addresses for system use.

Static MAC Entries

MAC entries can be manually entered in the Bridging Table, as an alternative to learning them from incoming frames. These user-defined entries are not subject to aging, and are preserved across resets and reboots.

Self-Learning MAC Addresses

The Ethernet Switch Module enables automatic MAC address learning from incoming packets. The MAC addresses are stored in the Bridging Table.

Features of the Switch Introduction

Lan Switch and Router Blade

Automatic Aging for MAC Addresses

MAC addresses from which no traffic is received for a given period are aged out. This prevents the Bridging Table from overflowing.

Port Security

Port security prevents unauthorized users from accessing your network. It allows each port to learn, or be assigned, a list of MAC addresses for devices authorized to access the network through that port. Any packet received on the port must have a source address that appears in the authorized list, otherwise it will be dropped. Port security is disabled on all ports by default, but can be enabled on a per-port basis.

Address Filtering –

This switch provides a packet filter for all traffic entering the CPU port and hence potentially forwarded or routed to the management network. The packet filter is rule/pattern based and constitutes a set of patterns which when matched will DROP the packet, and a further set of patterns which when matched will ACCEPT the packet.

MAC Multicast Support

Multicast service is a limited broadcast service, which allows one-to-many and many-to-many connections for information distribution. Layer 2 Multicast service is where a single frame is addressed to a specific Multicast address, from where copies of the frame are transmitted to the relevant ports.

2.1.2 Layer 2 Features

IGMP Snooping

IGMP Snooping examines IGMP frame contents, when they are forwarded by the Ethernet Switch Module from work stations to an upstream Multicast router. From the frame, the Ethernet Switch Module identifies work stations configured for Multicast sessions, and which Multicast routers are sending Multicast frames.

Port Mirroring

Port mirroring monitors and mirrors network traffic by forwarding copies of incoming and outgoing packets from a monitored port to a monitoring port. Users specify which target port receives copies of all traffic passing through a specified source port.

Broadcast Storm Control

Storm Control enables limiting the amount of Multicast and Broadcast frames accepted and forwarded by the Ethernet Switch Module. When Layer 2 frames are forwarded, Broadcast and Multicast frames are flooded to all ports on the relevant VLAN. This occupies bandwidth, and loads all nodes connected on all ports.

VLAN Supported Features

The switch supports up to 228 VLANs. A Virtual LAN is a collection of network nodes that share the same collision domain regardless of their physical location or connection point in the network. The switch supports tagged VLANs based on the IEEE 802.1Q standard. Members of VLAN groups can be dynamically learned via GVRP, or ports can be manually assigned to a specific set of VLANs. This allows the switch to restrict traffic to the VLAN groups to which a user has been assigned. By segmenting your network into VLANs, you can:

Features of the Switch Introduction

Lan Switch and Router Blade

1) Eliminate broadcast storms which severely degrade performance in a flat network.

2) Simplify network management for node changes/moves by remotely configuring VLAN membership for any port, rather than having to manually change the network connection.

3) Provide data security by restricting all traffic to the originating VLAN, except where a connection has been configured between separate VLANs using a router or Layer 3 switch.

VLAN Support

VLANs are collections of switching ports that comprise a single broadcast domain. Packets are classified as belonging to a VLAN based on either the VLAN tag or based on a combination of the ingress port and packet contents. Packets sharing common attributes can be grouped in the same VLAN.

Port Based Virtual LANs (VLANs)

Port-based VLANs classify incoming packets to VLANs based on their ingress port. For more information, see "Defining VLAN Ports Settings".

IEEE802.1V Protocol Based Virtual LANs (VLANs)

VLAN classification rules are defined on data-link layer (Layer 2) protocol identification. Protocol based VLANs isolate Layer 2 traffic for differing Layer 3 protocols.

Full 802.1Q VLAN Tagging Compliance

IEEE 802.1Q defines an architecture for virtual bridged LANs, the services provided in VLANs and the protocols and algorithms involved in the provision of these services. An important requirement included in this standard is the ability to mark frames with a desired Class of Service (CoS) tag value (0-7).

GVRP Support

GARP VLAN Registration Protocol (GVRP) provides IEEE 802.1Q-compliant VLAN pruning and dynamic VLAN creation on 802.1Q trunk ports. When GVRP is enabled, the Ethernet Switch Module registers and propagates VLAN membership on all ports that are part of the

active underlying "Spanning Tree Protocol Features" topology.

GMRP Protocol

GARP Multicast Registration Protocol (GMRP) is a Generic Attribute Registration Protocol (GARP) application that provides a constrained multicast flooding facility similar to IGMP snooping. GMRP and GARP are industry-standard protocols defined by the IEEE

802.1p.GMRP provides a mechanism that allows bridges and end stations to dynamically register group membership information with the MAC bridges attached to the same LAN segment and for that information to be disseminated across all bridges in the Bridged LAN that supports extended filtering services. The operation of GMRP relies upon the services provided by the GARP. GMRP software components run on both the switch and on the host. On the host, GMRP is typically used with IGMP: the host GMRP software spawns Layer 2 GMRP versions of the host's Layer 3 IGMP control packets. The switch receives both the Layer 2 GMRP and the Layer 3 IGMP traffic from the host. The switch uses the received GMRP traffic to constrain

Features of the Switch Introduction

Lan Switch and Router Blade

2.1.3 Spanning Tree Protocol Features

Spanning Tree Protocol (STP)

Spanning Tree Protocol (STP, IEEE 802.1D) – This protocol adds a level of fault tolerance by allowing two or more redundant connections to be created between a pair of LAN segments. When there are multiple physical paths between segments, this protocol will choose a single path and disable all others to ensure that only one route exists between any two stations on the network. This prevents the creation of network loops. However, if the chosen path should fail for any reason, an alternate path will be activated to maintain the connection.

IEEE 802.1w Rapid Spanning Tree

Rapid Spanning Tree Protocol (RSTP, IEEE 802.1w) – This protocol reduces the convergence time for network topology changes to about 10% of that required by the older IEEE 802.1D STP standard. It is intended as a complete replacement for STP, but can still interoperate with switches running the older standard by automatically reconfiguring ports to STP-compliant mode if they detect STP protocol messages from attached devices.

IEEE 802.1s Multiple Spanning Tree

IEEE 802.1s Multiple Spanning Tree - The IEEE 802.1s is the supplement to IEEE Std 802.1Q adds the facility for VLAN bridges to use multiple spanning trees, providing for traffic belonging to different VLANs to flow over potentially different paths within the virtual bridged LAN.802.1s supports spanning tree by per VLAN.

Fast Link

STP can take up to 30-60 seconds to converge. During this time, STP detects possible loops, allowing time for status changes to propagate and for relevant Ethernet Switch Modules to respond. 30-60 seconds is considered too long of a response time for many applications. The Fast Link option bypasses this delay, and can be used in network topologies where forwarding loops do not occur.

Link Aggregation

One Aggregated Links may be defined, with up to 2 member ports, to form a single Link Aggregated Group (LAG). This enables:

• Fault tolerance protection from physical link disruption

• Higher bandwidth connections

• Improved bandwidth granularity

• High bandwidth server connectivity LAG is composed of ports with the same speed, set to full-duplex operation.

Link Aggregation and LACP

LACP uses peer exchanges across links to determine, on an ongoing basis, the aggregation capability of various links, and continuously provides the maximum level of aggregation capability achievable between a given pair of systems. LACP automatically determines, configures, binds and monitors the port binding to aggregators within the system.

BootP and DHCP Clients

DHCP enables additional setup parameters to be received from a network server upon system startup. DHCP service is an on-going process. DHCP is an extension to BootP. For more information on DHCP, see "Defining DHCP IP Interface Parameters".

Features of the Switch Introduction

Lan Switch and Router Blade

2.1.4 Ethernet Switch Module Management Features

The PRIMERGY BX600 can either be managed through the console port (out-of-band management) or through the network (in-band management) with SNMP, TELNET or HTTP

protocols.

Various Files of Management Operation:

z There are three types of files for the PRIMERGY BX600:

 Configuration Files: The file stores system configuration information

 Operation Code: Executed after system boot-up, also known as Run Time Image

 BootRom Image: The images brought up by loader when power up. Also known as

POST (Power On Self-Test)

z Due to the size of flash memory, the PRIMERGY BX600 supports only two copies for

Configuration files and Operation Code respectively, but only one copy for BootRom

Image.

Duplication of Management file

The PRIMERGY BX600 can copy those three types of files in three different ways.

1. Local file to local file copy: The PRIMERGY BX600 can copy an existed local Configuration File to another local file. Copy exited local Operation Code to another local file is not permitted.

2. Remote TFTP Server to Local file copy: The PRIMERGY BX600 can support to download Configuration File or Operation Code from remote server to local file.

3. Local file to remote server: The PRIMERGY BX600 can support to upload an existed local Configuration File to the remote server.

4. Running Config to local file copy

5. Running Config to remote TFTP server

6. Local file to Running Config copy

7. Remote TFTP server to Running Config copy

Select Start-up Files

Users can select one of two copies for Configuration Files and Operation Codes as start-up file which is used as default bootup configuration and execution image, And the other copy of Configuration File and Operation Code will be used for backup.

Save Configuration as file

Users can save the running configuration as a file for future use. This newly saved configuration file can be selected as start-up file later on. Or users can upload this saved

configuration to the remote server for backup.

Provision

The PRIMERGY BX600 allows users to select the Configuration files to configure the system. There are two timings to configure system: Start-up and Run time.

Start-up: Select the Configuration File for start-up purpose.

Run time: Users can choose a new configuration file to reconfigure the system while system

Start up and Configuration the Ethernet Switch Module  Configuration the Switch Blade Module

Lan Switch and Router Blade

running, without rebooting the system. This function is available for CLI only.

SNMP Alarms and Trap Logs

The system logs events with severity codes and timestamps. Events are sent as SNMP traps to a Trap Recipient List.

SNMP Version 1,Version 2, and Version 3

Simple Network Management Protocol (SNMP) over the UDP/IP protocol. To control access to the system, a list of community entries is defined, each of which consists of a community string and its access privileges. There are 2 levels of SNMP security read-only and read-write.

Web Based Management

With web based management, the system can be managed from any web browser. The system contains an Embedded Web Server (EWS), which serves HTML pages, through which the system can be monitored and configured. The system internally converts web-based input into configuration commands, MIB variable settings and other management-related settings.

Configuration File Download and Upload

The Ethernet Switch Module configuration is stored in a configuration file. The Configuration file includes both system wide and port specific Ethernet Switch Module configuration. The system can display configuration files in the form of a collection of CLI commands, which are stored and manipulated as text files.

TFTP Trivial File Transfer Protocol

The Ethernet Switch Module supports boot image, software and configuration upload/download via TFTP.

Remote Monitoring

Remote Monitoring (RMON) is an extension to SNMP, which provides comprehensive network traffic monitoring capabilities (as opposed to SNMP which allows network Ethernet Switch Module management and monitoring). RMON is a standard MIB that defines current and historical MAC-layer statistics and control objects, allowing real-time information to be captured across the entire network.

Command Line Interface

Command Line Interface (CLI) syntax and semantics conform as much as possible to common industry practice. CLI is composed of mandatory and optional elements. The CLI interpreter provides command and keyword completion to assist user and shorten typing.

Syslog

Syslog is a protocol that allows event notifications to be sent to a set of remote servers, where they can be stored, examined and acted upon. Multiple mechanisms are implemented to send notification of significant events in real time, and keep a record of these events for after-the-fact usage.

SNTP

The Simple Network Time Protocol (SNTP) assures accurate network Ethernet Switch Module clock time synchronization up to the millisecond. Time synchronization is performed by a network SNTP server. Time sources are established by Stratums. Stratums define the distance from the reference clock. The higher the stratum (where zero is the highest), the more accurate the clock.

Features of the Switch Introduction

Lan Switch and Router Blade

2.1.5 Security Features

SSL

Secure Socket Layer (SSL) is an application-level protocol that enables secure transactions of data through privacy, authentication, and data integrity. It relies upon certificates and public and private keys. SSL version 3 and TLS version 1 are currently supported.

Port Based Authentication (802.1x)

Port based authentication enables authenticating system users on a per-port basis via an external server. Only authenticated and approved system users can transmit and receive data. Ports are authenticated via the Remote Authentication Dial In User Service (RADIUS) server using the Extensible Authentication Protocol (EAP).

Locked Port Support

Locked Port increases network security by limiting access on a specific port only to users with specific MAC addresses. These addresses are either manually defined or learned on that port. When a frame is seen on a locked port, and the frame source MAC address is not tied to that port, the protection mechanism is invoked.

RADIUS Client

RADIUS is a client/server-based protocol. A RADIUS server maintains a user database, which contains per-user authentication information, such as user name, password and accounting information. For more information, see "Configuring RADIUS Global Parameters".

SSH

Secure Shell (SSH) is a protocol that provides a secure, remote connection to an Ethernet Switch Module. SSH version 1 and version 2 are currently supported. The SSH server feature enables an SSH client to establish a secure, encrypted connection with a Ethernet Switch Module. This connection provides functionality that is similar to an inbound telnet connection. SSH uses RSA Public Key cryptography for Ethernet Switch Module connections and authentication.

TACACS+

TACACS+ provides centralized security for validation of users accessing the Ethernet Switch Module. TACACS+ provides a centralized user management system, while still retaining consistency with RADIUS and other authentication processes.

2.1.6 Quality of Service Features

The PRIMERGY BX600 support the mapping of DSCP (Differentiated Service Code Point) to CoS queues. Therefore, packet with different DSCP value can be scheduled to separated CoS queues for different services. DSCP definition is backward compatible with TOS definition. Hence PRIMERGY BX600 also support the mapping of TOS to CoS queues. And packet with difference precedence can be scheduled to different prioritized CoS queues.

Access Control List (ACLs)

Packet filtering can help limit network traffic and restrict network use by certain users or devices. ACLs filter traffic as it passes through a switch and permit or deny packets crossing specified interfaces or VLANs. An ACL is a sequential collection of permit and deny conditions

Start up and Configuration the Ethernet Switch Module  Configuration the Switch Blade Module

Lan Switch and Router Blade

that apply to packets. When a packet is received on an interface, the switch compares the fields in the packet against any applied ACLs to verify that the packet has the required permissions to be forwarded, based on the criteria specified in the access lists. The first match decides whether the switch accepts or rejects the packets. Because the switch stops testing after the first match, the order of conditions in the list is critical. If no conditions match, the switch rejects the packet. If there are no restrictions, the switch forwards the packet; otherwise, the switch drops the packet. The switch can use ACLs on all packets it forwards, including packets bridged within a VLAN.

These access lists are supported on Layer 2 interfaces: Standard IP access lists using source addresses and Extended IP access lists using source and destination addresses and optional protocol type Information. The switch examines ACLs associated with all inbound features configured on a given interface and permits or denies packet forwarding based on how the packet matches the entries in the ACL. In this way, ACLs are used to control access to a network or to part of a network.

An ACL is a sequential collection of permit and deny conditions. The switch tests packets against the conditions in an access list . The first match determines whether the switch accepts or rejects the packet. Because the switch stops testing after the first match, the order of the conditions is critical. If no conditions match, the switch denies the packet.

The PRIMERGY BX600 supports these types of ACLs or access lists for IP:

• Standard IP access lists use source addresses for matching operations.

• Extended IP access lists use source and destination addresses for matching operations and optional protocol-type information for finer granularity of control.

Standard ACLs are the oldest type of ACL. Standard ACLs control traffic by comparing the source address of the IP packets to the addresses configured in the ACLs. Extended ACLs control traffic by comparing the source and destination addresses of the IP packets to the addresses configured in the ACLs. Rules can be configured to inspect up to six fields of a packet: Source IP, Destination IP, Source L4 Port, Destination L4 Port, TOS Byte, Protocol Number.

Strict scheduling for priority queue

In addition to WRR, PRIMERGY BX600 also supports Strict scheduling ensures that the highest priority packets will always get serviced first, ahead of all other traffic, and that the other three queues will be serviced using WRR scheduling

WRR (Weighted Round Robin)

The PRIMERGY BX600 supports Weighted Round Robin (WRR) scheduling. The WRR queuing algorithm ensures that the lower priority packets are not entirely starved for bandwidth and are serviced without compromising the priority settings administered by the network

manager.

Differentiated Services

Network resources are apportioned based on traffic classification and priority, giving preferential treatment to data with strict timing requirements according to network management policy. The PRIMERGY BX600 supports the Differentiated Services(Diffserv). The Diffserv is a method of offering quality-of-service treatment for network traffic without the need for a resource reservation protocol. An administration specifically provisions the network equipment to identify the following: The classes of traffic in the network & The QoS treatment the classes of traffic receive.

Diffserv controls the traffic acceptance throughout the DiffServ domain, the traffic transmission

Start up and Configuration the Ethernet Switch Module  Configuration the Switch Blade Module

Lan Switch and Router Blade

throughout the Diffserv domain and the bandwidth guarantee within the network nodes. By controlling the acceptance, the transmission and bandwidth, a policy-based range of services is established.

There are 3 keys QoS building blocks to configure Diffserv. Class, Policy and Services

2.1.7 Layer III Routing Features

IP Routing

The PRIMERGY BX600 IP Routing layer (IPv4 support) contains the IP Forwarding layer, Address Resolution Protocol (ARP) Mapping Layer, and Routing Table Object (RTO). PRIMERGY BX600 also provides that each port which is be configured to participate in the routed network.

The IP Routing layer provides the following functions:

ARP Mapping (Table)/Static ARP

For maintaining the ARP Table used to correlate IP and MAC addresses. The table contains both static entries configured by user and entries dynamically updated based on information in received ARP frames.

Static ARP can be defined in the ARP table. When static entries are defined, a permanent entry is entered and is used to translate IP address to MAC address.

Routing Table Object (RTO)

The Routing Table Object manages a common routing table for all registered routing protocols.

IP Forwarding Layer

The IP Forwarding layer forwards received IP packets that cannot be forwarded through the hardware.

Routing Information Protocol (RIP)

The Routing Information Protocol, or RIP, has been a long-standing protocol used by routers for exchanging route information. RIP is a distance vector protocol whereby each route is characterized by the number of gateways, or hops, a packet must traverse to reach its intended destination. RIP categorized as an interior gateway protocol and operates within the scope of an autonomous system.

RIP is designed such that its routers send the contents of their routing table every 30 seconds to each adjacent router. These periodic updates allow routes to remain active in the route table; absence of a route from the updates causes the route to be declared unusable after 180 seconds have elapsed, and to be removed from the table after an additional 120 seconds passes without the route appearing in an update message.

Two versions of RIP are in current use:

RIPv1 defined in RFC 1058

- The RIP routing messages are specified by IP destination network and hop count and not

include the concept of subnets.

- The RIP routing messages are broadcast to all stations on the attached network.

Start up and Configuration the Ethernet Switch Module  Configuration the Switch Blade Module

Lan Switch and Router Blade

RIPv2 defined in RFC 1723

- The RIP routing messages are extended to include subnet mask and gateway

information.

- For network traffic, the RIP routing message is sent to a multicast address.

- Add an authentication scheme to improve security for updating route tables.

RIPv2 enhancements defined in RFC 2453

- An implementation of RIP must use simple split horizon and use spilt horizon with

poisoned reverse.

- An implementation of RIP must implement triggered update for deleted routes and may

implement triggered updates for new routes or change of routes. RIP implementations

must also limit the rate at which triggered updates may be transmitted.

- An implementation of RIP should support host routes.

The PRIMERGY BX600 Managed Switch supports both versions of RIP.

BOOTP/DHCP Relay Agent

In the majority of network configurations, BOOTP/DHCP clients and their associated servers do not reside on the same IP network or subnet. Therefore, some kind of third-party agent is required to transfer BOOTP/DHCP messages between clients and servers. Such an agent is known as a "BOOTP/DHCP relay agent”.

PRIMERGY BX600 Relay Agent also will support to relays BOOTP and DHCP requests. The agent relays requests from a subnet without a BOOTP/DHCP server to a server or next-hop agent on another subnet. BOOTP/DHCP relay agent only processes BOOTP/DHCP messages and generates new BOOTP/DHCP messages as a result.

Virtual Router Redundancy Protocol (VRRP)

PRIMERGY BX600 supports Virtual Router Redundancy Protocol (VRRP) is designed to provide backup for the failing router without requiring any action on the part of the end station. It is based on the concept of having more than one router recognize the same IP address. One of the routers is elected the “master” router and handles all traffic sent to the specified virtual router IP address. If the master router fails, one of the backup routers will be elected in its place, and will start handling traffic sent to the address. This change will be transparent to end stations.

VRRP increases the availability of the default path without requiring configuration of dynamic routing or router discovery protocols on every end station. The greater default path availability is accomplished by using any of the virtual router IP addresses on the LAN as the default first hop router for the end stations. Multiple virtual routers can be defined on a single router interface on, but only one IP address can be assigned to a given virtual router.

Router Discovery

The router discovery messages do not constitute a routing protocol. Instead, the router discovery messages enable hosts to discover the existence of neighboring routers through the use of router advertisement. Router advertisement is unsuitable for determining the best route to a particular destination. If a host chooses a poor first-hop router for a particular destination, it should receive an Internet Control Message Protocol (ICMP) Redirect from that router, identifying a better one.

Features of the Switch Introduction

Lan Switch and Router Blade

PRIMERGY BX600 router discovery, a router periodically multicasts a Router Advertisement from each of its multicast interfaces, announcing the IP address(es) of that interface. Hosts discover the addresses of their neighboring routers simply by listening for advertisements. Since a host knows the address of its neighbors, the host can send IP data grams beyond its directly attached subnet.

Virtual LAN (VLAN) Routing

PRIMERGY BX600 incorporates both 802.1Q VLAN bridging and routing functions. The internal bridging function can be an interface to the routing function and the routing function can be an interface to the bridging function will support. Even though PRIMERGY BX600 supports both 802.1Q VLAN bridging and routing functions, each port cannot operate as both a router port and an 802.1Q bridge port.

When a port is enabled for bridging (the default) rather than routing, all normal bridge processing is performed for an inbound packet associated with a VLAN. Its MAC Destination Address (DA) and VLAN ID are used to search the MAC address table and the packet was forwarded depend on MAC table. If routing is enabled for the VLAN and the MAC DA of an inbound unicast packet is that of the internal bridge-router interface, the packet will be routed. An inbound multicast packet will be forwarded to all ports in the VLAN, plus the internal bridge-router interface if it was received on a routed VLAN.

Route Redistribution

Route Redistribution allows routers running different routing protocols to exchange routing information on the network. A route redistribution implementation must consider that different routing protocols use different ways of expressing the distance to a destination. Also routing metrics in different protocols may have different formats and allow a different range of values.

For example,

the RIP route metric is a single integer from 1 to 16.

the OSPF route metric is a 24 bit integer.

PRIMERGY BX600 implementation of route redistribution has the following configuration characteristics:

- For each routing protocol (OSPF, RIP), the administrator may specify which routes are redistributed (OSPF, RIP, static, connected).

- When OSPF redistributes, the administrator may optionally specify a metric, metric type (external type 1 or external type 2), and a tag value. The administrator may specify whether OSPF redistributes subnetted routes.

- When RIP redistributes, the administrator may optionally specify a metric. When RIP redistributes from OSPF, the administrator may specify one or more types of OSPF routes to be accepted. Valid values are internal, external 1, external 2, NSSA external 1, and NSSA external 2.

- For each pair of source and destination routing protocols, the administrator may optionally specify an access list to filter routes by destination address and mask.

Route Preferences

Use route preference to configure the default preference for each protocol (e.g. 60 for

Features of the Switch Introduction

Lan Switch and Router Blade

static routes, 150 for OSPF Type-2). These values are arbitrary values in the range of 1 to 255 and are independent of route metrics. Most routing protocols use a route metric to determine the shortest path known to the protocol, independent of any other protocol.

The best route to a destination is selected by using the route with the lowest preference value. When there are multiple routes to a destination, the preference values are used to determine the preferred route. If there is still a tie, the route with the best route metric will be chosen. To avoid problems with mismatched metrics (i.e. RIP and OSPF metrics are not directly comparable) you must configure different preference values for each of the protocols.

The reference configure value is below

• Static - The static route preference value in the router. The default value is 1. The range is 1 to

255.

• OSPF Intra - The OSPF intra route preference value in the router. The default value is 8. The

range is 1 to 255. The OSPF specification (RFC 2328) requires that preferences must be given to the routes learned via OSPF in the following order: intra < inter < type-1 < type-2.

• OSPF Inter - The OSPF inter route preference value in the router. The default value is 10. The

range is 1 to 255. The OSPF specification (RFC 2328) requires that preferences must be given to the routes learned via OSPF in the following order: intra < inter < type-1 < type-2.

• OSPF Type-1 - The OSPF type-1 route preference value in the router. The default value is 13.

The range is 1 to 255. The OSPF specification (RFC 2328) requires that preferences must be given to the routes learned via OSPF in the following order: intra < inter < type-1 < type-2.

• OSPF Type-2 - The OSPF type-2 route preference value in the router. The default value is 150.

The range is 1 to 255. The OSPF specification (RFC 2328) requires that preferences must be given to the routes learned via OSPF in the following order: intra < inter < type-1 < type-2.

• RIP - The RIP route preference value in the router. The default value is 15. The range is 1 to

255.

Open Shortest Path First (OSPF)

The Open Shortest Path First (OSPF) protocol uses within larger autonomous networks in preference to RIP. OSPF is a link-state protocol that multicasts table updates only when a change has taken place and transmits only the changed portion of the table. To give preferences to certain routes, OSPF uses both administratively assigned costs for a given router and link-states as metrics. In addition, OSPF supports variable-length subnet masks.

OSPF can operate within a hierarchy. The largest entity within the hierarchy is the autonomous system (AS), a collection of networks under a common administration sharing a common routing strategy. This is sometimes called a

routing domain. An AS can be divided into

a number of areas or groups of contiguous networks and attached hosts. Routers within the same area share the same information, so they have identical topological databases. Information is sent in the form of link-state advertisements (LSAs) to all other routers within the same hierarchical area. An area's topology is not visible to routers outside the area.

Two different types of OSPF routing occur as a result of area partitioning: Intra-area and Interarea. Intra-area routing occurs if a source and destination are in the same area. Inter-area routing occurs when a source and destination are in different areas. An OSPF backbone distributes information between areas.

PRIMERGY BX600 supports OSPF version 2 in accordance with RFC 2328. PRIMERGY BX600 also provides a compatibility mode for the RFC 1583 OSPF specification, which allows interoperability with OSPF version 2 routers using the older implementation.

Features of the Switch Introduction

Lan Switch and Router Blade

DNS and DNS Relay

The DNS protocol controls the Domain Name System (DNS), a distributed database with

which you can map host names to IP addresses. When you configure DNS on your switch, you

can substitute the host name for the IP address with all IP commands, such as ping, telnet, traceroute, and related Telnet support operations.

To keep track of domain names, IP has defined the concept of a domain name server, which holds a cache (or database) of names mapped to IP addresses. To map domain names to IP addresses, you must first identify the host names, specify the name server that is present on your network, and enable the DNS.

DNS relay acts as a forwarder between the DNS Clients and the DNS Servers. PRIMERGY BX600 DNS Relay designed for home/office users that don’t need to know name

server also can access to Internet. Only setting DNS server on client station points toward that switch.

IP Multinetting

PRIMERGY BX600 support an IP Multinetting function. It is the process of configuring more than one IP address on a network interface. IP Multinetting is also synonymously called IP Aliasing or Secondary Addressing. Typical uses of IP Multinetting are:

Reorganizing servers with no other machine updates.

Virtual hosting of Web and FTP servers

2.1.8 IP Multicast Features

IGMPv3

Internet Group Management Protocol (IGMP) is the multicast group membership discovery protocol. Three versions of IGMP exist. Versions 1 and 2 are widely deployed. Since IGMP is used between end systems (often desktops) and the multicast router, the version of IGMP required depends on the end-user operating system being supported. Any implementation of IGMP must support all earlier versions.

The following list describes the basic operation of IGMP, common to all versions. A multicast router can act as both an IGMP host and an IGMP router and as a result can respond to its own IGMP messages. The PRIMERGY BX600 implementation of IGMPv3 supports the multicast router portion of the protocol (i.e. not the host portion). It is backward compatible with IGMPv1 and IGMPv2.

PRIMERGY BX600 IGMPv3 the multicast router function is below:

1. One router periodically broadcasts IGMP Query messages onto the network.

2. Hosts respond to the Query messages by sending IGMP Report messages indicating their group memberships.

3. All routers receive the Report messages and note the memberships of hosts on the network.

4. If a router does not receive a Report message for a particular group for a period of time, the router assumes there are no more members of the group on the network.

Features of the Switch Introduction

Lan Switch and Router Blade

All IGMP messages are raw IP data grams, and are sent to multicast group addresses, with a time to leave (TTL) of 1. Since raw IP does not provide reliable transport, some messages are sent multiple times to aid reliability.

IGMPv3 is a major revision of the protocol and provides improved group membership latency. When a host joins a new multicast group on an interface, it immediately sends an unsolicited IGMP Report message for that group. IGMPv2 introduced a Leave Group message, which is sent by a host when it leaves a multicast group for which it was the last host to send an IGMP Report message. Receipt of this message causes the Querier possibly to reduce the remaining lifetime of its state for the group, and to send a group-specific IGMP Query message to the multicast group. The Leave Group message is not used with IGMPv3, since the source address filtering mechanism provides the same functionality.

IGMPv3 also allows hosts to specify the list of hosts from which they want to receive traffic. Traffic from other hosts is blocked inside the network. It also allows hosts to block packets for all sources sent unwanted traffic.

IGMPv3 adds the capability for a multicast router to learn which sources are of interest to neighboring systems for packets sent to any particular multicast address. This information gathered by IGMP is provided to the multicast routing protocol (i.e. DVMRP, PIM-DM, and PIM-SM) that is currently active on the router in order to ensure multicast packets are delivered to all networks where there are interested receivers.

Protocol Independent Multicast – Dense Mode (PIM-DM)

Protocol Independent Multicast (PIM) protocols are not dependent on any particular unicast routing protocols to construct forwarding information for multicast packets, although unicast information is needed for forwarding packets. The Dense Mode version of PIM is most appropriate for networks with relatively plentiful bandwidth and with at least one multicast member in each subnet.

PIM-DM assumes that all hosts are part of a multicast group and forwards packets to hosts until informed that group membership has changed. A group membership change results in the multicast delivery tree being pruned.

The PIM-DM protocol operates as follows:

1. The first message for any (source, group) pair is forwarded to the entire multicast

network, with respect to the time-to-live (TTL) value in the packet.

2. TTL restricts the area flooded by the packet.

3. All leaf routers with no members in a directly attached subnet send prune messages to the upstream router.

4. Any branch for which a prune message is received is deleted from the delivery tree.

PRIMERGY BX600 will use PIM-DM’s RPF to correctly forward message. PIM-DM Reverse Path Forwarding (RPF), which is the fundamental concept in multicast routing that enables routers to correctly forward multicast messages down the distribution tree. RPF makes use of the existing unicast routing table to determine the upstream and downstream neighbors and build a source-based shortest-path distribution tree. A router forwards a multicast message only if the multicast message is received on the upstream interface. This RPF check helps to guarantee that the distribution tree will be loop-free.

The multicast messages contain the source and group information so that downstream routers can build up their multicast forwarding tables. If the source goes inactive, the tree is torn down. Multicast messages arriving at a router over the proper receiving interface (i.e., the interface that provides the shortest path back to the source) are forwarded on all downstream interfaces until unnecessary branches of the tree are explicitly pruned. In addition to the prune messages, PIM-DM uses graft messages and assert messages. Graft messages are used

Features of the Switch Introduction

Lan Switch and Router Blade

when a new host wants to join a group, and assert messages are used to shut off duplicate flows.

PRIMERGY BX600 PIM-DM can be enabled but will only become operational when both routing and IGMP are enabled and operational.

Protocol Independent Multicast – Sparse Mode (PIM-SM)

Protocol Independent Multicast sparse mode (PIM-SM), like PIM dense mode (PIM-DM), uses the unicast routing table to perform the Reverse Path Forwarding (RPF) check function instead of maintaining a separate multicast route table. Therefore, regardless of which unicast routing protocol(s) is (are) used to populate the unicast routing table (including static routes), PIM-SM uses this information to perform multicast forwarding; hence, it too is protocol independent.

The unicast routing table is used to determine the path that PIM control messages such as Join messages take to get to the source subnet, and data flows along the reverse path of the Join messages. Based on received Join/Prune messages, routers maintain a set of mappings between the incoming interfaces and outgoing interfaces for each known multicast group.

PIM-SM uses two scenarios in the network for building information trees, which are used for inter-domain routing. They are

- Source sending data for a multicast group

- Receiver of a multicast group requesting data

In both the above scenarios PIM-SM makes use of the following concepts

Rendezvous Point (RP): RP is the root of a shared distribution tree down which all multicast

traffic flows.

Designated Router (DR): DR is responsible for sending 'Join' messages to the RP for

members on the network and for sending 'Register' messages to the RP for sources on the network.

PIM-SM is used to efficiently route multicast traffic to multicast groups that may span wide area networks and where bandwidth is a constraint. PIM-SM uses shared trees by default and implements source-based trees for efficiency this data threshold rate is used to toggle between trees. PIM-SM assumes that no hosts want the multicast traffic unless they specifically ask for it. It creates a shared distribution tree centered on a defined “rendezvous point” (RP) from which source traffic is relayed to the receivers. Senders first send the multicast data to the RP, which in turn sends the data down the shared tree to the receivers. Shared trees centered on a RP do not necessarily provide the shortest/optimal path. In such cases PIM-SM provides a means to switch to more efficient source specific trees.

The PRIMERGY BX600 IP Multicast implementation of PIM-SM supports both automatic RP router election and user specified RP designation.

Automatic RP determination

The RP for a given IP group address (G) may be determined by the protocols specified in

section 2.6 of RFC 2362. PRIMERGY BX600 supports these protocols.

Static RP designation

The user may specify which router shall be the RP for a given IP group address via the

user interface. This information will be used to designate the RP for the group if no

information for the group address has been obtained via the automatic RP determination

protocols. Note that if the router learns of an RP for a group via the automatic mechanism

Features of the Switch Introduction

Lan Switch and Router Blade

it will take priority over a static designation.

Source Sending Data

As soon as an active source sends a packet to the DR that is attached to this source, the DR is responsible for “Registering” this source with the RP and requesting the RP to build a tree back to that DR. The DR encapsulates the multicast data from the source in a special PIM-SM message called the 'Register message' with the multicast data encapsulated in the message. After the sources register with the RP the data is forwarded down the shared tree to the receivers.

Receiver Requesting Data

PIM Sparse mode uses the explicit join model whereby; the receivers send PIM Join messages to a designated “Rendezvous Point” (RP). In order to join a multicast group G, a host (receiver) conveys the membership information through the IGMP to DR. When a DR gets a membership indication from IGMP for a new group, DR looks up the RP associated to the group and sends a join message to the RP.

The router can switch to a source's shortest path tree (SP- tree) if the data rate of packets received from a specific source over the shared tree exceeds the threshold value during a specified time interval. The routers (RP and the last hop DR of the receiver) dynamically create a source specific shortest path tree using Join/Prune messages and stop traffic from flowing down the shared RP tree (using Register Stop Messages when the RP has no downstream receivers for the group or that particular source) when the data rate reaches a threshold value.

Distance Vector Multicast Routing Protocol (DVMRP)

The Distance Vector Multicast Routing Protocol (DVMRP) is a hop-based method of

building multicast delivery trees from multicast sources to all nodes of a network. The delivery trees are built by pruned and grafted messages, therefore the tree is shortest path to multicast source and is relatively efficient. The multicast group information forward by a distance-vector algorithm, therefore, the propagation is slow. DVMRP is used for optimized high delay (high latency) relatively low bandwidth networks.

DVMRP resembles the Routing Information Protocol (RIP). The DVMRP module exchanges probe packets and report packet with the multicast group member hosts sitting in the directly connected network. Based on the information exchange, the DVMRP module creates a database (multicast routing table) for each of the interfaces in the multicast router. The database consists of information types as:

Multicast group entries

Timers

Counters

Flags

Dependencies

States

The multicast router uses the database of information to route multicast packets from the source (that is not sitting in the same LAN as the hosts) to the member hosts.

+ 644 hidden pages

Fujitsu Siemens Computers PRIMERGY BX, PRIMERGY BX600 Description

Specifications and Main Features

Frequently Asked Questions

User Manual