Web traffic is not flowing from Foglight Experience Monitor (FxM) over to Foglight Experience Viewer (FxV). How do we integrate/connect these two appliances?
could be numerous causes
1. In the FxM installguide.pdf go to the section Foglight Experience Monitor and Foglight Experience Viewer in Chapter 7. This is the section about integrating FxM and FxV. Do everything it says to do there. When you get to the step in which you are configuring the Auxiliary Device setting (eth1) on the FxM machine, keep in mind that you can just assign that port to any IP that you would like to choose. Depending on the version you are using, steps 2 and 3 below may also be discussed in Chapter 7 of the FxM installguide.pdf. In older versions, those steps were not completely clear.
2. Go into the FxV Appliance Setup Utility (not the web console) Choose 2) Network Configuration | 2) Configure Network Cards. For eth1 you need to enter in an IP that is different from the eth1 IP you set up in FxM but that is also on the same subnet. For example, you might use 220.127.116.11 (for eth1 in FxM ) and 18.104.22.168 (for eth1 in FxV). This will get the traffic to go over the crossover cable from eth1 on FxM to eth1 on FxV. Make sure that a cable is physically attached from eth1 of FxM to eth1 of FxV.
3. In the FxV web console, go to Configure | Collectors. Set the Archiver IP Address From Collector field to use that private IP you had just set in step2 (e.g. 22.214.171.124).
Related Solution: SOL60863
The auxiliary port IP address you provide must be on its own unique subnet, and should not share the same subnet as the IP addresses assigned to the control ports on the Foglight Experience Monitor and Foglight Experience Viewer archiver. This ensures that traffic passes from one appliance to the other over the crossover cable and not over the network. If you fail to configure this correctly, the system may work only intermittently--especially if the capture traffic gets heavy and/or oncomplex multi-appliance configurations--due to routing problems caused by both eth0 and eth1 being on the same subnet. Other drawbacks are potential security issues and large amounts of traffic passing over your network unnecessarily.