I think this is a good idea and generally in the right direction. I am sure the group can help refine it some more.
Just a few days ago Alex got an assignment to create a network topology database for individual customers. I am sure he would welcome this initiative. The problem our support guys face is that they do not have a good knowledge of the customer setup while answering questions and trying to help debug. So we end up asking repetitive questions leading to frustrations. Nish -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bill Flood Sent: Monday, August 25, 2003 9:47 PM To: '[EMAIL PROTECTED]' Subject: [smartBridges] HOW IS YOUR SYSTEM SET UP? I've been thinking about this for weeks. As a group we need to identify how are systems are configured end-to-end. Start there, then determine who is having problems. Statistically, it would be interesting to find out which solutions work the best, which don't. How many ways can a WISP be setup? I would say that there has to be some common configurations used. Start there, then when this is determined add some detail, which types of equipment / servers are used. Do you use statically assigned IP's or do you use DHCP? Public or private IP's? Do you mix manufactures or do you use just SB? Which access points have trouble, what is the percentage of SB to other equipment? Are the other manufactures equipment also having trouble? Of the clients which have trouble are they talking to a SB access point? I foresee a flow chart. A means to troubleshoot these problems LOGICALLY not emotionally. Possibly, Smartbridges will see this as a benefit also and give us a secure page or two to display this troubleshooting flow chart. As we discuss our problems on this list we have no idea how any of us are set up. If this could be determined, if we had solid ground to work with, we as a group could Help one another technically, logically and find commonalities, solutions and problem areas. Once we bring emotion into this list we go NO WHERE. Is it worth YOUR TIME to help create a troubleshooting format / flowchart. To explain your setup so that an identifier can be assigned to it so when you have a problem you could say " my system is set up like this: A: T1-> Cisco 2510 -> Server-Firewall ->Shaper -> Radio P-t-P Radio[Alvarion] -> APPO [SB] Or set up like: B: xDSL -> Router -> Server -> Radio The list Daddy could set up a timed reminder that would mail the website out to the list with these different configurations listed. SB could control the access in the same manner that they are currently using for updates and secure SB info. New people on the list should be encouraged to use this troubleshooting guide to figure out their configuration before asking questions to the list. We need some rules of engagement, so we as a group of SB users can help and support each other with technology, logic and an accumulated knowledge base. Who is interested? Who can help? I appreciate your time in reading this. Bill Flood AirRunner Networks LLC The PART-15.ORG smartBridges Discussion List To Join: mailto:[EMAIL PROTECTED] (in the body type subscribe smartBridges <yournickname> To Remove: mailto:[EMAIL PROTECTED] (in the body type unsubscribe smartBridges) Archives: http://archives.part-15.org The PART-15.ORG smartBridges Discussion List To Join: mailto:[EMAIL PROTECTED] (in the body type subscribe smartBridges <yournickname> To Remove: mailto:[EMAIL PROTECTED] (in the body type unsubscribe smartBridges) Archives: http://archives.part-15.org
