This really isn't a hard subject to grasp - unless you try to make it that way. What a lot of us are looking for is an easy way to ssh or telnet into our networks and do whatever it is we need to do, but don't want to be tethered to a laptop.
A real life example would be sitting at the ball park - NMS sends a text that "whatever" is down - pick up the cell phone telnet into the "whatever" device and take care of business. Surely you can see the simplicity in what we are looking for, but for some reason you feel the need to do "whatever it is" that you are doing with this thread. Not difficult. Mac > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > Behalf Of Matt Liotta > Sent: Tuesday, August 07, 2007 10:16 AM > To: WISPA General List > Subject: Re: [WISPA] Managing your network on the go-go-go! > > David E. Smith wrote: > > The original assumption was that "replacing my whole network" was > > where you were going with your statement, and I apologize for that > > misinterpretation. Not that your actual suggestion of "write a bunch > > of Web interfaces" is that much better... > > > I haven't actually suggested either. Your stated goal was to do some > basic things to a device that was only available via SSH from a cell > phone. Creating a web-based interface for those basic things doesn't > take a lot of work. > > Now if you want to manage your whole network from a cell phone I do > think it would take a lot of work. I also think you are crazy. Some > things shouldn't be managed from a cell phone. You really should just > use a laptop. > > In another email you mention that you would want to change BGP or OSPF > configs via a cell phone to fix a broken network. That too is crazy. > Something as important as BGP or OSPF simply shouldn't break on its > own. > It should only break when someone is changing a configuration. In that > case, wouldn't the person doing the breaking (or someone else at the > office) be responsible for using their computer to fix it? > > Oh, and multiply that by several times, as I have several different > > systems for which I'd need similar interfaces. I'd need one for > Trango > > (yes, they have a built-in Web interface but it stinks out loud), > > Alvarion (BreezeConfig is nice, but it's Windows-only), Mikrotik > > RouterOS (the Web interface is okay but there's a lot of stuff you > > can't easily do with it), and so on and so on. > > > I certainly understand your point as we have a variety of radio vendor > equipment with a variety of management interfaces. However, all of them > have SNMP interfaces, which gave us a common way to manage all of our > radios. You really need your own OSS to manage all of your network. We > looked around at smaller successful telecommunication companies and > found that all of them had a good OSS. As such, we decided to do the > same and it has been worth every penny. > > -Matt > > ----------------------------------------------------------------------- > --------- > WISPA Wants You! Join today! > http://signup.wispa.org/ > ----------------------------------------------------------------------- > --------- > -- > WISPA Wireless List: wireless@wispa.org > > Subscribe/Unsubscribe: > http://lists.wispa.org/mailman/listinfo/wireless > > Archives: http://lists.wispa.org/pipermail/wireless/ > > > > -- > No virus found in this incoming message. > Checked by AVG Free Edition. > Version: 7.5.476 / Virus Database: 269.11.8/940 - Release Date: > 8/6/2007 4:53 PM -------------------------------------------------------------------------------- WISPA Wants You! Join today! http://signup.wispa.org/ -------------------------------------------------------------------------------- -- WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
