Hello again to all! I'm testing one of our switches for a customer who wants my personal assurtance that we properly convert tap signals from a single mode fiber in-line matrix switch into mult mode fiber outout to a NetScout probe.
We were given a NetScout one port Gig probe with Ethernet transport for the test (it belongs to customer and is brand new out of the box). When we access the probe through the console port, the Ethertnet transport and the Gig moniotr port are both visible. We have assigned an IP - read/write community string is being left as public for the test.
Using Sniffer Quick Connect to connect to RMON (following Sniffer's instructions in the Help menu), we get as far as Sniffer automatically starting the local proxy server on the workstation that is running SniffView and Sniffer finds/recognizes the Ethernet transport card. It does NOT fin the Gig monitor card and the attempt to connect/capture fails.
One of my collegues conducted a similar test a year or so ago and forwarded me the log file showing his successful connection. It appears that in our present efforts, when Sniffer attempts to find the Gig card, it fails to do so and terminates the session.
We have now been able to successfully (on the first try) connect and initiate a capture using WildPackets RMON Grabber utility. Thus, we have concluded that the RMON probe is functional and working properly. I still have a strong desire to be able to do this from Sniffer for future tesing purposes - anyone have ideas on what we're missing here?
Owen O'Neill
Datacom Systems Inc.
Northeastern SE
We were given a NetScout one port Gig probe with Ethernet transport for the test (it belongs to customer and is brand new out of the box). When we access the probe through the console port, the Ethertnet transport and the Gig moniotr port are both visible. We have assigned an IP - read/write community string is being left as public for the test.
Using Sniffer Quick Connect to connect to RMON (following Sniffer's instructions in the Help menu), we get as far as Sniffer automatically starting the local proxy server on the workstation that is running SniffView and Sniffer finds/recognizes the Ethernet transport card. It does NOT fin the Gig monitor card and the attempt to connect/capture fails.
One of my collegues conducted a similar test a year or so ago and forwarded me the log file showing his successful connection. It appears that in our present efforts, when Sniffer attempts to find the Gig card, it fails to do so and terminates the session.
We have now been able to successfully (on the first try) connect and initiate a capture using WildPackets RMON Grabber utility. Thus, we have concluded that the RMON probe is functional and working properly. I still have a strong desire to be able to do this from Sniffer for future tesing purposes - anyone have ideas on what we're missing here?
Owen O'Neill
Datacom Systems Inc.
Northeastern SE