If mac id of TB is 1,it should send out who-is. Or you can send me email, I want to check it remotely. It is easier for me to find what is the problem.
My email is chelsea(at)temcocontrols(dot)com
Chelsea, our goal is to make things simple. Let this work for any mac ID.
I checked and it doesn’t matter if the MAC id isn’t the smallest, as long as it’s a network device it will actively send who-is
I’m not sure that I understand what you’re asking me to email you? I could put a traffic analyzer on the MSTP trunk and watch the traffic when I initiate a discovery command, but I don’t have time to do that, nor should I have to. If the new units perform the same as this existing unit that I bought a year ago for testing, then I’ll know that these units are not ready for commercial applications (for me) and I’ll be using other gateways in their place.
Jon: We will get you where you want to be, there is no question.
Chelsea, we want to see both Temco and 3rd party MSTP subnet devices on the tree in Yabe and T3000.
Maurice/Chelsea: I have received my shipment of new NB routers and have connected 2 of the new ones to my network and they are exhibiting the same behavior as my ‘bench’ test unit. I’ve run a series of MSTP trunk data captures using both the NB and BASRT routers, both in a Yabe who-is test, as well as a Jace Discovery command (my ultimate use case scenario). How would you like me to present the results of my testing to you for analysis? It’s a total of 10 files.
Also, with the BASRT online, when I map the meter into the Jace I get values. If I unplug the BASRT and plug in the NB, the meter values read down. This tells me that the NB is not passing the requests for data values to the MSTP trunk.
Email the captures to chelsea(at)temcocontrols(dot)com. Send a summary and be sure to name the files so we know what is going on in each of them.
I sent the files and summary to Chelsea yesterday.
She will report back first thing monday