When you connect the monitoring point to AppNeta Performance Manager (APM), the port that you use matters because only one is pre-configured to acquire an IP address by DHCP. Similarly, certain ports are pre-configured to enable usage monitoring out of the box.

What port do I use?

The following table describes the ports that are pre-configured. Use the port in the ‘to AppNeta’ row to connect the device to your APM service instance.

m22 m25 m30 m35 r40 r45 r400
to AppNeta E1 E0 E3 E0 E5 E5 E5
Out-of-band cabling E0 E5 E0 E5 E0 E0 E0@1G and E6@10G
Inline cabling N/A E4/E5 E0/E1 E4/E5 E0/E1 E0/E1 E0/E1@1G and N/A@10G
Console port settings N/A Speed = 19200 (115200 for m25/m35) , Data bits = 8, Stop bits = 1, Parity = None, Flow control = XON/XOFF

The complete list of ports for each device model and their intended usage is described in the Complete Port Descriptions table.

Old m22s: In case you have an older m22 with no port labels, the port closest to the LED array is E1 . The other is E0.

r400 SFPs: The r400 has one 10G interface, E7, with VLAN support, which can be used for monitoring. It also has one receive-only 10G interface, E6, which is meant for out-of-band flow collection. The r400 ships with two 10Gbps 850nm multi-mode transceivers: Finisar FTLX8571D3BCL, but you can swap these out for your own 10G SFPs if necessary.