Setting up an MTM400 Gbe Interface

Setting up an MTM400 GbE Interface

Power up the MTM400

Start the RUI and proceed to the "Input Card" page. Not the Config Page

Before connecting the Ethernet cable from the MTM400 GbE interface to the device under test, determine if you want ARP on or off.

ARP ON:

–If the monitored traffic requires "Active" multicast. The MTM400 will need to send "IGMP join" requests to the customer equipment.

–If you want to send or receive PING.

–If connecting to a switch or router and the traffic is unicast to the MTM400. This is not a typical application.

ARP OFF:

–Monitor passively on an Ethernet Switch where multicast traffic is being switched to all ports

–Monitor on a Fiber in Rx only mode. (Typically done with an opticalsplitter)

–If you are not sure, leave it OFF initially.

If you need to have ARP ON, set the"InputCard IP" address to an appropriate IP address (i.e. one that is valid on the customer's network), then set the"ARP ON" control.

Use the "Select Speed" control to set the appropriate Ethernet Link configuration. Typically "Auto 10/100/1000(Copper)"

If you need to use Fiber, obtain the appropriate 850nm, 1310nm, or 1550nm SFP module and insert into the SFP cage on the GbE interface board.

At this point, connect the appropriate Ethernet cable from the customer equipment to theMTM400 GbE board.

If you connect before this point and ARP is ON and you have not set the Card IP Address, the customer's equipment will likely ARP the MTM400 and will resolve an incorrect IP address in it's ARP table.

In some cases the Network element may disable the port when our MAC address is pluggedin due to the invalid IP address.

Is it connected ?

On the UI, scroll to the top of the "Readings", "Link Information" section. The "Line Speed" indicator should read the negotiated line speed on the connected network. (Should read1000, 100,10, or 1000(Optical))

It should not be a RED N/A. If the "Line Speed" is not correct there is no need to proceed until this problem is resolved.

In some cases, the customer's equipment is in Forced mode, the Ethernet Auto negotiation is turned off. If this is the case, the "Select Speed" control can be used to select one of the "Force" mode selections.

Traffic Flow ?

If all of the above is setup properly, the"Traffic" table on the MTM400 UI will Auto detect all of the streams running on the interface and start monitoring them. The "Total Bit Rate" indicator in the "Link Information section" will show the total bitrate of all of the traffic arriving on the Ethernet interface.

If all of the streams are showing up on the traffic table, you can stop here and select the stream you want to do more MPEG analysis on by clicking on it in the Traffic table.

If nothing shows up on the Traffic table and it is a multicast application, proceed to IGMP Setup, otherwise to No Traffic Flow.

IGMP Setup

Determine if the application requires "Active" Multicast.Active means that MTM400 will need to send IGMP join requests to the customer equipment.

IGMP setup (for Active Multicast)

–a) If the application requires Multi-session monitoring, then select the "Multi Session" pulldown under the "IGMP Configuration" section. Otherwise select "Single Session".

–b) If in Multi session mode, select the "IGMP Sessions" Table on the "Graph/Table" pulldown. The table will list all of theMulticast IP addresses that will be joined on the network. You can click on themto change them from the "UNSUBSCRIBED" state to the "SUBSCRIBED" state if needed. The "Insert" and "Delete" controls in the "IGMP Configuration" sectionof the UI are used tomanage this table. For Multi-session multicast monitoring (Active IGMP), these addresses will need to be populated fromacustomer.

–c) InSingle Session mode, type in the IP address of the Multicast session you want to join in the "Insert/Join" control.

No Traffic Flow ?

If there is still no traffic shown on the Traffic table and the Total Bitrate is 0, and the link has negotiated properly, you can try to ping the interface using the ping control at the bottom right of the UI in the "Diagnostics" section.

ARP is required to be ON with a valid IP address for Ping functionality. If the Ping functions, then you can try to turn IGMP Off and back on. This will resend the joins on the network.

Another option is to try to change linespeed, change from Auto Copper to Optical and back again or vice versa. This will reset the entire GbE interface, clear the traffic table and resend all of the IGMP joins on the network

PING test usage

Ping Control - Type the IP address of the device you want to PING on the customer's network. Set the Subnet mask(255.255.255.0 is typical) and set the Gateway IP address. Push the Send button.

The Traffic table will change to the "Ping Result" Table Automatically and display the result of the Ping. You can also send a Ping request to the MTM GbE interface from a remotedevice attached to the customer's network. Use the IP address in the "Input CardIP" Control.