Service	Before ISP Innovations	After ISP Innovations
DNS is the "Domain Name System", which translates Domain Names into IP numbers (IP numbers are the actual "addresses" for computers on the Internet), and IP numbers into Domain Names. All services offered by ISP's depend on DNS working perfectly.	DNS changes are made by people typing into text files, with no "history" of what changed, or was added These changes must be made by a "qualified technician", otherwise, if a mistake is made (e.g., a semicolon in the wrong place), then DNS for the whole ISP could stop working, causing *all* services to grind to a halt. Even with qualified technicians, typos are possible, which can cause serious problems The person doing the configuration is not necessarily aware of failures in new configuration The new functionality has to be either verified a with second (time-consuming) step, or is not verified Some functionalities may not be being used, due to inexperienced users DNS configurations are rarely "archived" DNS changes do not cause notifications to Administrator DNS configuration is time-consuming	DNS changes are made by a program, with 0% failure rate, and "history" of what changed The program knows what to do because a user used a Shell Menu program or a Web Gui to answer questions about DNS additions, changes, or deletions. There are no possibilities of errors, and work is done quickly and easily. Anyone can make DNS changes Typos are not possible The system "checks for errors" as the DNS is being created, and makes any problems obvious to user, if they arise The new functionality is automatically verified by the system All DNS functionalities are made available by System Each new DNS configuration is archived, (before and after) with date of change, and who did it. Each change to DNS configuration causes changes to be emailed to Administrator DNS configuration takes seconds
Web Site Hosting is, next to email, probably the most in-demand service on the Internet. Considering how many companies offer this service, setting up Web Sites, maintaining them, and making sure they are working after setup, and 24 hours a day after that, is very important. ISP Innovations offers tools to make setting up Web Sites effortless, amazingly quick, and with a zero percent failure rate. These tools can be used by anybody, irregardless of "technical know-how" and allow for easy configuration of all of the "Web Site Features" required by the customer. After the setup, the tools check the work, and display the results to the user, and be sure they were successful.	Setting up Web Hosting (i.e. adding a new user) must be made by a qualified technician Setting up Web Hosting was time-consuming, and sometimes did not work Each step required the user to type into a text file, with no "history" of what changed Typographical errors are quite possible, and frequent To make sure that the new Web Site is working, requires a separate (time-consuming) step. Any configuration errors (typographical or otherwise) might cause *all* the Web Sites hosted by the ISP to stop working, or "break" a Web Site other than the one they are adding, which may go unnoticed until customer(s) complain. Some functionalities may not be being used, due to inexperienced users Web "stats" are not automatically configured, it is another job, which must be configured (and verified as operational) FTP is not automatically configured, it is another job, which must be configured (and verified as operational) Email is not automatically configured, it is another job, which must be configured (and verified as operational) You cannot "roll back to previous configuration", if changes cause problems Web Hosting configurations are frequently not "archived", in case of server failure Web Hosting configuration changes do not cause notifications to Administrator Frequently, each and every Web Site is not "monitored" on an hourly ( or more frequent) basis, so that any failure might go unnoticed by ISP until the customer calls and complains, possibly with loss of revenue.	Web Hosting can be configured by anyone Adding a Web Site takes seconds and the Web Site is "tested". Web Hosting changes are made by a program, with 0% failure rate, and "history" of what changed Typos are not possible The new Web Site is "tested & verified" immediately in real-time and the status reported to the user doing the configuration (and administrator) All Web Sites are then "tested & verified" immediately in real-time and the status reported to the user doing the configuration (and administrator) The program offers all "features" to the person configuring the Web Site Web "stats" are automatically configured and 'verified' as operational FTP is automatically configured and 'verified' as operational Email is automatically configured and 'verified' as operational You *can* "roll back to previous configuration" if necessary Each new router configuration is archived, (before & after) with date of change Each new router configurations causes changes to be emailed to Administrator Each and every Web Site is "monitored", and warnings sent out when anything fails or looks "suspicious"
MRTG is a program which shows bandwidth "graphs", for you and your customers, so you know where your bandwidth goes. Many ISP's browse the MRTG graphs in order to see: customer's bandwidth usage (sometimes as a 95th percentile) in order to invoice customers. which customers are using more bandwidth that they should, customers which we call "Offenders". The ISP Innovations "MRTG Assistant" makes all MRTG configuration setting up, modifying, and viewing a breeze.	The user's bandwidth (95th percentile or otherwise) is *not* collected into one nice report, and one must view every graph and write it down, in order to invoice & bill customers. New routers are time-consuming to add to the MRTG system, requiring many steps, some which have to be repeated multiple times You have to view hundreds of graphs to spot "Offenders" The "Offenders" graphs are not saved, and after a few hours, the offending bandwidth has scrolled off of the daily graph... MRTG only shows "Bandwidth Offenders", and not Customers who use too many IP #'s or too many Mac #'s MRTG typically puts hundreds of graphs on one page, which takes a long time to load into browser, and is hard to navigate MRTG does not provide all of the available information MRTG sometimes makes it hard to see "trends", because it takes too long to look at hundreds of "pictures" When the the router configuration changes, MRTG configuration has to be re-run to "update for router changes". Most ISPs either Do not re-run configuration, and new interfaces are not represented Redo configuration by hand after router is updated, requiring extra time and effort Re-run configuration on a regular basis every day, or several times per day, which can, if problems occur, invalidate all MRTG past, present, and future for that router When (or if) MRTG configuration is regenerated after router is changed, it does not show the user, or report the "changes detected" to the Administrator. If the configuration becomes invalid, it could take days or weeks before someone notices the data is invalid or even missing. Graphs could become invalidated after router reboot. Graphs will become invalidated if you rename your router. 95th percentile support is not included with MRTG, and if desired, is a separate configuration step, (complete with possibilities of typographical or improper configuration errors). Creating Customer Invoices from MRTG graphs can be very time consuming and difficult. If many routers are running MRTG, it is frequently difficult to see "the big picture", i.e how many configurations are there, and how exactly are they configured. If you want separate interfaces on one router to have MRTG runs of different frequencies (i.e. every 5 minutes for serial interfaces, but every 10 minutes for other interfaces), this is not one of the MRTG options.	The user's bandwidth (95th percentile or otherwise) is collected into one nice report, or separate customer invoices. New routers are added to the MRTG system, and configured in seconds by the ISP Innovations "MRTG Assistant" You get daily emails with a summary of "Offenders", and warning emails when bandwidth exceeds "danger" levels The "Offenders" daily graphs are "frozen" (copied) for future viewing There are 3 types of Offender: a) bandwidth "Offenders", b) IP # Offenders, and c) Mac # Offenders Our system has a "Table of Contents" (indexed by "Customer Name", "Interface #, or Interface Description). Our system provides additional SNMP information which MRTG does not provide, like IP #'s used by interface, Mac #'s used by interface, and more... Our system provides Reports & Summaries of the Graphs, because sometimes a few words are better than 700 pictures. This makes it easy to spot "trends". Our MRTG monitor detects when the router changes, and immediately re-runs the configuration maker. When MRTG config is regenerated (after a router change is detected), and "changes detected" are emailed to Administrator. Graphs do not become invalidated after router reboot. There is a "rename router" sub-system which allows you to rename router, and all log files and html pages are updated. 95th percentile support is included, no extra configuration is required, it is set up transparently to user, and it is tested in real-time. Creating Customer Invoices requires no work at all, as the "MRTG Assistant" can make Invoices directly from MRTG logs, to your pre-configured specifications. The MRTG "Assistant" allows you to see exactly what is happening with your full MRTG system. We support "separate MRTG interface intervals" which allows finer granularity control for specified interfaces
Routers are the core of the ISP's business. Cisco is the brand chosen by most, as they are the most reliable. Routers control where Internet traffic goes. All services offered by ISP's depend on routing working perfectly.	Router cpu may climb to dangerous levels, (with Denial of Service Attacks, or Kazaa), with no notifications until router is non-functional, at which time one cannot log into the router Router changes (i.e. new users) must be made by a qualified technician Router changes are typed in, with ho "history" of what changed Even with qualified technicians, typos are possible, which can cause serious problems Router changes are time-consuming Router changes must be 'verified' by a second (also time-consuming) step, or there is no guarantee the new functionality works. You cannot "roll back to previous configuration", if changes cause problems Router configurations are rarely "archived", in case of router failure Router changes do not cause notifications to Administrator It takes time & effort (logging into the router) to see what IP's or Mac Addresses any particular DSL customer is using Finding DSL users using more than one Mac Address, or more than the allotted number of IP's, can be difficult & time-consuming When a customer exceeds their allotted resources, no warnings are generated, and they can get more service than they pay for, unless they are rate limited.	Router cpu is "monitored", and warnings sent out when it exceeds "trigger" level Router changes (new users) can be made by anyone Router changes are made by a program, with 0% failure rate, and "history" of what changed Typos are not possible You *can* "roll back to previous configuration" if necessary Router changes take seconds Router changes are verified transparently, and the status (success or failure) is quickly reported to user configuring the service. Each new router configuration is archived, (before & after) with date of change Each new router configurations causes the changes to be emailed to Administrator Simple Web Reports show what IP's or Mac Address any particular DSL customer is using Simple Web Reports *instantly* show DSL users using more than one Mac Address, or more than the allotted number of IP's Emails can be automatically generated (to the System Administrator, and/or customer) when customers abuse their resources, and billing rates can automatically increase at these times.