posted
Wayne, if you have it running correctly you should have a BLUE modem (not gray). If gray, you should be able to right click the modem and login (telnet password is required). Fromt he sounds of it, you are beyond that point.
After that, you can right click that modem and go to IP stats, settings and statistics, or Events. Select [b]view[/v] on any of those. Let it run for a minute or two and watch your stats. Do a couple downloads to see some change in those stats.
You can also gain that same view by going to FILE/IP STATS/VIEW.....etc.
Look around in there. There is a lot you can see/do with that GUI.
It says I'm correctly logged in as Admin under the modem but the modem is still gray.
When I try to select Settings and Statistics or IP Stats all menu items are under those menu items are grayed out and unselectable.
I can putty in or telnet in from within the iSite app and that works fine.
I can view events (although says that none have occurred)
I can download my option file
...so it's definitely communicating at least partially with the 3100 but the light certainly isn't blue. Any ideas?
I just noticed that it now reads "deactivated" in red letters next to my TDMA Remote #.
Is the ability to view Settings and Statistics & IP Stats something that is enabled and/or disabled in the modem's option file? If so I would request my config changed and the modem sent an update.
I quit and relaunched iSite.
I'm not getting "deactivated" anymore but I am seeing this in the console log around the time I've I tried to communicate with the modem using iSite.
falcon: XdrMsgHandler::ProcessData -- msg type 115 not registered falcon: XdrMsgHandler::ProcessData -- msg type 115 not registered falcon: XdrMsgHandler::ProcessData -- msg type 62 not registered falcon: XdrMsgHandler::ProcessData -- msg type 23 not registered falcon: XdrMsgHandler::ProcessData -- msg type 40 not registered falcon: XdrMsgHandler::ProcessData -- msg type 8 not registered
here's the version info from my modem: Application: falcon Code Version: 7.1.0.0 Build Comment: Release build Build Label: NetModem-7_1_1
We have had a handful of issues with Options files, but I must add that some of these issues were primarily "ID10T". Operators were fairly new the technology, and out of the 200 or so modems that we commissioned since the start of this year, we had to re-image about 4 of them due problems during the load. I do agree with you though to, the tool itself its very unlikely to cause any issues, the problem on the majority of these cases was the way the file was scripted and in couple of them, they were using the wrong NMS release to load the file. In addition, keep in mind that about half of our account are installed by certified Motosat techs, But most of them are not that familiar with Isite, As you know, if operators are familiar enough with Isite they can a lot of things to the remote, We had a guy in Honduras was pretty savvy, he was changing power levels, adjusting certain settings, we had to change the password on him to prevent him from keep messing with the modem. Most private VNOs don't release their password to their users, as far Motosat and EtherSAT goes, if you are not familiar with it, don't touch it. Isite it's great, I love it, comparing to every other tool I have used to manage satellite modem, it's by far the best.
Now changing gears, I will be notifying everyone, hopefully by next week of dates of the upgrade of EtherSAT's 8.0 NMS Rev. We want to make sure everyone on the same page and online during the upgrades, everyone will be notified by email and again I will be posting here as well. We look forward to this new phase of operations and we look forward for the benefits that will come along with it.
Franco.
Posts: 64 | From: Salt Lake City | Registered: Jun 2007
| IP: Logged |
We have had a handful of issues with Options files, but I must add that some of these issues were primarily "ID10T". Operators were fairly new the technology, and out of the 200 or so modems that we commissioned since the start of this year, we had to re-image about 4 of them due problems during the load. I do agree with you though to, the tool itself its very unlikely to cause any issues, the problem on the majority of these cases was the way the file was scripted and in couple of them, they were using the wrong NMS release to load the file. In addition, keep in mind that about half of our account are installed by certified Motosat techs, But most of them are not that familiar with Isite, As you know, if operators are familiar enough with Isite they can a lot of things to the remote, We had a guy in Honduras was pretty savvy, he was changing power levels, adjusting certain settings, we had to change the password on him to prevent him from keep messing with the modem. Most private VNOs don't release their password to their users, as far Motosat and EtherSAT goes, if you are not familiar with it, don't touch it. Isite it's great, I love it, comparing to every other tool I have used to manage satellite modem, it's by far the best.
Now changing gears, I will be notifying everyone, hopefully by next week of dates of the upgrade of EtherSAT's 8.0 NMS Rev. We want to make sure everyone on the same page and online during the upgrades, everyone will be notified by email and again I will be posting here as well. We look forward to this new phase of operations and we look forward for the benefits that will come along with it.
Franco.
Understand all Franco. I dont blame you for the "call us first" statement. I just thought it would be neat if the users were able to view some statistical data coming off their modem. I also knew that Motosat may have the logons locked down to prevent the dangerous from any self inflicted gunshot wounds (screwing things up bad).
As for 8.0.1.....these 3100 users are definitely going to require that UPGRADE PREPERATION PACKAGE to clean up FPGA space (3100s have a limited amt of memory). So I understand your desire to have them all (or most) of them online at one time.
Did you see that the GQoS overwrites the legacy QoS? There is a database conversion that coverts the legacy profiles (pre-8.0 profiles) to GQoS profiles, but they arent identical. Hopefully you guys wont have too many aches and pains when you roll them over.
Several new features with 8.0. The highlight is certainly GQoS, but the NMS activity logging, Ability to lock remotes to a particuar inbound (inroute) also caught my eye and could be of value.
posted
I logged into my modem's management IP address using iSite 7.1.1 and still the modem is still grayed out and the IP Stats menus are still dimmed.
Franco can you do whatever you need to do so that I can use iSite to view our IP Stats?
posted
Franco, with all this discussion of how interesting it would be to peer into the iSite program, I just happened to notice that I am running ver.6 of iSite and I believe the firmware in the 3100 is ver.7. A couple of questions. One, should these versions be the same and two, if they remain different will this have any effect on the future upgrade to ver.8. If I need to bring the iSite software up to ver.7 let me know and I will call you so that we can do this together.
-------------------- F3/D3 3.9.4/iDirect3100/123W/40'EuroTrans 2003 Enterprise Server/10 Workstations/Blackberry 8830 Tethered to MBR1000 Where In The World Am I (click here) Posts: 272 | From: Boca Raton | Registered: Mar 2005
| IP: Logged |
posted
I was hitting the LAN interface... then hit the management interface and tried again. Still no blue modem icon, still can't view IP Stats (sub menu is dimmed.)
I really want the real-time usage stats, that's my primary interest in running iSite.
posted
Mike, I haven't had any need to use iSite, the remote in iSite reads deactivated, maybe something MotoSat instituted. I would like to remind everyone that I am over 21 and have a white beard (which did not get that way from tinkering with my or my customers IT equipment, how else do you learn, certainly very little in a classroom and everything else that really matters is learned on site, so Franco can you unlock the 3100? I promise not to change anything (as I put my hand in the cookie jar!) And I certainly do not want to create more work for you or myself.
-------------------- F3/D3 3.9.4/iDirect3100/123W/40'EuroTrans 2003 Enterprise Server/10 Workstations/Blackberry 8830 Tethered to MBR1000 Where In The World Am I (click here) Posts: 272 | From: Boca Raton | Registered: Mar 2005
| IP: Logged |
posted
If Franco is anything like me, he is concerned with you guys changing power settings when you are under weather..on the user end. Adjusting power in an iDirect network doesnt do you any good because the NMS is going to adjust you back to Nominal C/N (the UCP sweet spot) anyway! So there is really no need to play with power. The NMS is in charge anyway!
Sounds like Motosat might have the network locked down, or they have an ACL in place preventing the PP from issuing that iDirect unit a tcp socket (thus enabling the stats). I know I opened a can of worms (Franco is probably cussing me at Motosat HQ's/NOC). It is Motosats decision whether or not to proceed.
quote:Originally posted by wayneco: I was hitting the LAN interface... then hit the management interface and tried again. Still no blue modem icon, still can't view IP Stats (sub menu is dimmed.)
I really want the real-time usage stats, that's my primary interest in running iSite.
wayne
Pretty sure they have you locked down. Just an assessment. You are doing everything right.
-------------------- Mike Posts: 567 | From: North Carolina | Registered: May 2007
| IP: Logged |
posted
Dangerous is carrying a too small weapon to get the job done! They don't understand the impact of having hundreds of users call in during a period of rain fade. Users need to know their rmtstat figures and their max power (one db compression value). This, so they can isolate rain fade and site related issues as they move around our great country.
Changing settings like max power or receive carrier freq is not necessary or desirable. If any of those configuration settings were changed, the NMS would flag an error for the network operator. He would not be happy.