Netmon Docs · Device Configuration Guide

HPE Aruba ArubaOS-Switch (ProVision)v7.0.20

Set up port mirroring and sFlow v5 export on HPE Aruba ProVision (AOS-S) switches so Netmon can see the traffic crossing them.

This page covers HPE Aruba ProVision switches running ArubaOS-Switch (AOS-S) — the 2530, 2540, 2930F, and 2930M families. AOS-S supports local port mirroring for SPAN-style packet capture and sFlow v5 for flow export.

Mirror traffic (SPAN)

AOS-S calls SPAN “port mirroring.” A local mirroring session designates one exit (mirror) port, then assigns one or more source ports whose traffic is copied to it. Connect the exit port to the Netmon sniffer NIC.

  1. Enter global configuration and define the exit (mirror) port that connects to Netmon.

    switch(config)# mirror-port <EXIT-PORT>

  2. Enter each source interface to be monitored and enable mirroring of its traffic.

    switch(config)# interface <SOURCE-PORT>
switch(eth-<SOURCE-PORT>)# monitor

  3. Repeat step 2 for every additional source port you want copied to the exit port.

    switch(eth-<SOURCE-PORT>)# interface <SOURCE-PORT-2>
switch(eth-<SOURCE-PORT-2>)# monitor

  4. Verify the session.

    switch(eth-<SOURCE-PORT>)# show monitor
Important

Do not connect the exit (mirror) port back into the production LAN. It carries copied traffic and is intended only for the Netmon sniffer NIC; cabling it into a production segment will loop mirrored frames back onto the network.

Note

The commands above are as documented for the 2930F/2930M. The 2530 and 2540 use the same mirror-port / interface ... monitor syntax; see the Aruba 2530 Management and Configuration Guide for those platforms.

Connect the exit port to a Netmon NIC set to Sniffer (manual); see Receiving the Data in Netmon.

Source: Configuring a source switch in a local mirroring session, ArubaOS-Switch 16.10 Management and Configuration Guide. https://arubanetworking.hpe.com/techdocs/AOS-S/16.10/MRG/WB/content/wc/cnf-sou-swi-loc-mir-ses.htm

Export flow data

AOS-S exports flow data using sFlow v5. There is no NetFlow/IPFIX exporter on this platform, so use the sFlow target. Netmon listens for sFlow on UDP 6343 — which is also the AOS-S default destination port — so no port override is required. You configure an sFlow receiver instance (1, 2, or 3), then enable flow sampling and counter polling on the ports of interest.

  1. Enable an sFlow receiver instance pointing at Netmon. The UDP destination port defaults to 6343 and matches the Netmon listener; you may state it explicitly.

    switch(config)# sflow <RECEIVER-INSTANCE> destination <netmon-ip> 6343

  2. Enable flow sampling on the ports you want sampled, choosing a non-zero sampling rate (skipcount).

    switch(config)# sflow <RECEIVER-INSTANCE> sampling <PORT-LIST> <SAMPLING-RATE>

  3. Enable counter polling on those ports with a non-zero polling interval (seconds).

    switch(config)# sflow <RECEIVER-INSTANCE> polling <PORT-LIST> <POLLING-INTERVAL>
Note

The <RECEIVER-INSTANCE> must be 1, 2, or 3. To disable sampling or polling on a port list, repeat the relevant command with a value of 0; to remove the receiver, use no sflow <RECEIVER-INSTANCE> destination <netmon-ip>.

Important

A CLI-owned sFlow instance cannot be modified via SNMP. If you configure sFlow here, manage it from the CLI. So that Netmon attributes the flow records to the correct device, ensure the switch sources its sFlow datagrams from the IP address Netmon already knows the switch by (its management IP).

After the switch is exporting, enable Allow Netflow Data Collection for this device in Netmon; see Receiving the Data in Netmon.

Source: Configuring sFlow (CLI), ArubaOS-Switch 16.10 Multicast and Routing Guide. https://arubanetworking.hpe.com/techdocs/AOS-S/16.10/MCG/WB/content/common%20files/cnf-sfl-cli.htm

PreviousHPE Aruba ArubaOS-CX NextDell PowerSwitch OS10