Switch Benchmark Automated

Considering buying a new switch. Typically not all to big an issue. Check Datasheet and fine. For smaller use cases this is probably feasible but I experienced never the less reaching some limits. So what to do?

Right now I started to do a benchmark and wanted to test out in which configuration a network switch actually maxes out. Besides max- MAC entries, max routing entries or multicast groups particular the number of differen VLANs results in memory consumption, since each one needs dedicated buffering.

On top most VLANs need IP configurations set up and depending on your applications probably multiple of them. Unfortunately in my case exactly the later.

Now you may consider configuring max configurations some fun, but after several loops to find the setup maximum, this does not exactly look like productive work. To create multiple configurations which then might be Continue reading

How-To: Init HPE FF5700 FlexFabric Switches

Left alone by some consultants, which charged a lot and did not accomplish to much, I ended up configuring FF5700 felx fabric switches myself. Some of the insights, other posts will follow.

To start with the basic initialization settings, configuring management access and doing initial firmware maintenance. After unpacking the switch and mounting fans and power supplies connect through the serial console – although there is dhcp client running on the switch which probably allows you to gain management access over the network. Remember there is a Gigabit- Ethernet- Port on the backside of the switch, dedicated for management access only. The console port is adjacent. Default serial settings are 9600/n/1/n as with any other HPE switch.

After the boot procedure press enter and you have access to the switch. Elevate your access level to configuration mode with:

system-view

To start with I actually disable the DHCP client and activate LLDP for further use.

undo dhcp enable
lldp global enable

After that prepare the desired VLANs according to whatever you later use. I strictly recommend leaving the default VLAN untouched, leaving the Primary VLAN ID on 1 and transport that untagged on any switch to switch link, but remove all access and server Continue reading