I have a 10/100 duplex pod that I can't get the B channel to get a link light. When I pull a trace I only see the A channel. My config is a switch on channel A and a workstation on Channel B and I'm in pass through mode. Both devices are 100/full. The workstation is on line and I have tried switching cables so worksation is on channel A. When I do this the trace is reversed. Don't know if this is a hardware problem with the pod or a config problem. Anybody know the settings to connect to the serial port so the pod config can be checked?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Sniffer Duplex Pod Problem
- Thread starter Steve1910
- Start date
- Thread starter
- #4
I would need a crossover if I connaected a hub to hub or switch to hub. The workstation is active on the network. I have also figured that the console connector is running at 19200 8N1. I can know see the boot screen but do not get a login prompt. Thanks for the reply.
Can't you check the pod by going to Pod Configuration on the Agent box? If you connect directly to the DS Pro platform with keyboard and monitor or RD32 in to it, under Start Programs Distributed Sniffer, there should be a selection just below probeviewerr called Pod Configuration.
Also double check the documentation - IIRC you should be using all straight through or regular Ethernet cables - no crossovers unless you go into a switch to switch link - I might be mistaken about this but correct cable type is crucial.
Another crucial fact - the pod is designed to work with the ET02. If you're trying to use it with an ET03, ET05 or with the Ethernet port of a Gig analyzer, there may be issues.
Using the Pod inline is okay for testing but has major drawbacks in a production link in terms of fault tolerance. My employer (who is an ad sponsor of this forum) makes a copper full duplex 10/100 fault tolerant tap that allows easier connection of the Pod. In the interest of full disclosure (and so as not to be shilling a product!), I'll mention that both Shomiti and Net Optics also makes such taps.
Owen O'Neill
Datacom Systems Inc.
Northeastern SE
Also double check the documentation - IIRC you should be using all straight through or regular Ethernet cables - no crossovers unless you go into a switch to switch link - I might be mistaken about this but correct cable type is crucial.
Another crucial fact - the pod is designed to work with the ET02. If you're trying to use it with an ET03, ET05 or with the Ethernet port of a Gig analyzer, there may be issues.
Using the Pod inline is okay for testing but has major drawbacks in a production link in terms of fault tolerance. My employer (who is an ad sponsor of this forum) makes a copper full duplex 10/100 fault tolerant tap that allows easier connection of the Pod. In the interest of full disclosure (and so as not to be shilling a product!), I'll mention that both Shomiti and Net Optics also makes such taps.
Owen O'Neill
Datacom Systems Inc.
Northeastern SE
- Thread starter
- #6
Thanks for the reply. The doc's specify straight through cables, and like I said the workstation is online which would indicate correct cabling.
I'm currently using the pod with Sniffer Portable Pro ver 4.7. This is on my laptop using the NAI provided pcmcia card with the correct drivers installed (that part is working). On the pod config screen there are no options to turn on or off the channels. I don't know what you mean by the ET02, all connections are hard set to 100/full. Also I'm looking into acquiring some UTP and Fiber taps.
The problem I have is that I have over 600 facilities around the country that have no permanently installed taps. I'm currently mirroring ports on the switches to collect traces, but the nature of switches is not to pass layer 1 errors. The only way to capture these errors is to tap the line. This pod is supposed to work in this way, but does not want to cooperate.
The doc's say the RS232 port is for manf config only and they don't give info on how to check the config. At this point I think this may be a hardware problem, but have no way to confirm this. Thanks for the help.
I'm currently using the pod with Sniffer Portable Pro ver 4.7. This is on my laptop using the NAI provided pcmcia card with the correct drivers installed (that part is working). On the pod config screen there are no options to turn on or off the channels. I don't know what you mean by the ET02, all connections are hard set to 100/full. Also I'm looking into acquiring some UTP and Fiber taps.
The problem I have is that I have over 600 facilities around the country that have no permanently installed taps. I'm currently mirroring ports on the switches to collect traces, but the nature of switches is not to pass layer 1 errors. The only way to capture these errors is to tap the line. This pod is supposed to work in this way, but does not want to cooperate.
The doc's say the RS232 port is for manf config only and they don't give info on how to check the config. At this point I think this may be a hardware problem, but have no way to confirm this. Thanks for the help.
I'll see what else I can find out. Ther ET02, ET05 etc are Distributed Sniffers. Sniffer Pro incl v4. is supposed to support the pod. I think one of my colleagues may have some expereicne connecting to it directly for config purposes dating back to when we did some testing a couple years ago.
One thing to consider (which it appears you already have)is the possibility of a hardware problem. If some predecessor in your organization left the pod sitting around and you're now putting it into use, it may have been left idel for good reason. The first few generations of FD pods that were introduced were problem prone and many, many of them had to be replaced. I believe the units started achieving a higher level of reliability perhaps in 2001 heading towards 2003 but even then - problems were still widely reported.
Keep in mind that like NAI's other "pod" products (e.g. the ATM Book), you MUST power cycle it by pulling the plug on the AC side NOT the DC side. The units can be damaged beyond easy repair if power cycled the wrong way. You've probably already tried this but with the Book products, problems are sometimes fixed by power cycling the pod and then power cycling the PC while the units are already cabled together - start the PC reboot as soon as you pull the power on the pod. It's worth a try.
Owen O'Neill
Datacom Systems Inc.
Northeastern SE
One thing to consider (which it appears you already have)is the possibility of a hardware problem. If some predecessor in your organization left the pod sitting around and you're now putting it into use, it may have been left idel for good reason. The first few generations of FD pods that were introduced were problem prone and many, many of them had to be replaced. I believe the units started achieving a higher level of reliability perhaps in 2001 heading towards 2003 but even then - problems were still widely reported.
Keep in mind that like NAI's other "pod" products (e.g. the ATM Book), you MUST power cycle it by pulling the plug on the AC side NOT the DC side. The units can be damaged beyond easy repair if power cycled the wrong way. You've probably already tried this but with the Book products, problems are sometimes fixed by power cycling the pod and then power cycling the PC while the units are already cabled together - start the PC reboot as soon as you pull the power on the pod. It's worth a try.
Owen O'Neill
Datacom Systems Inc.
Northeastern SE
- Status
Similar threads
- Locked
- Question