How we tested the Nortel BayStack 5510.
We loaded eight 5510-48T switches in a rack and connected them in a full-ring topology. Specifically we tested the BayStack 5510-48T hardware, with firmware Version 0.0.16 and software Version 3.0.1.00.
All tests were executed using 11 Spirent SMB 6000 chassis with 66 Terametrics XD four-port Gigabit Ethernet cards and 60 Terametrics two-port Gigabit Ethernet cards (384 ports total). All tests were run using Smartflow v2.20 software.
We ran four categories of tests – stack functions, performance, redundancy, and management. The following lists the test methodology by category.
Stack Function Tests
Replicated Console Port: We verified replication of the console port on all switches in the stack.
Reboot Time: We rebooted the stack from the front UI button and measured time for the console user interface to become active again.
Switch Renumber: Here, we renumbered the switches from the user interface, rebooted the stack and checked the stack order.
Base Unit Failover: We verified that the base unit fails over to another switch in the stack when the base unit fails.
Redundancy Test
Cross-Stack Multi-link Trunking: We connected the first port of four switches in one stack to the first port of four switches in the second stack. We configured the connections into a multi-link trunk. We verified that packets flow between the stacks over the multi-link trunk. To test proper failover, we pulled the cables from one switch in the stack.
Performance Tests
Throughput: We tested maximum throughput before loss in a full-mesh traffic pattern over all 384 ports of the stack with all ports in full-duplex 1000Base-T mode. Because the Smartbits cards can support a maximum of 64K flows, the number of flows was reduced by grouping the first 16 ports of each switch in the stack in a full-mesh traffic pattern, then the second set of 16 ports of all switches was configured in a full-mesh traffic pattern, then the third set of 16 ports. This arrangement satisfies the Smartbit flow limit but still sends the same value of traffic across the stack. We ensured that all stack cables were connected and operational. We repeated the test after disconnecting one of the stack cables. We then repeated the test for one switch in a stand-alone configuration.
Packet Latency: We measured packet latency of all ports in a full-mesh traffic pattern specified in the throughput test over 384 ports of an eight-switch stack at 50% and 80% maximum throughput before loss.
Management
Menu Interface: We verified the usability and functionality of the menu while configuring and managing the switch.
Command-line interface: We verified the usability and functionality of the CLI user interface while configuring and managing the switch.
