1. Adapters – If you have a device and don't see an adapter for that device, please post it here.
2. ZipTie is built on Eclipse and can be extended with fully functional “applications”, complete with their own UI and business logic. Create a useful application of your choice. However, all applications must work
across the supported matrix for ZipTie (Windows, Linux, etc.).
3. Graphical device viewer – Create a graphical view of a device based on its configuration. Similar to CiscoView (http://www.cisco.com/en/US/products/sw/cscowork/ps4565/index.html)
4. Topology viewer
5. Service Path Analysis
6. Spanning-tree visualization
7. MRTG Integration
8. Device Monitor – for the inventory of devices, display up/down status (response time.... Red light, green light), CPU utilization, interface traffic utilization
9. Switch port reports for tracking unused ports and last-used ports
10. Software advisor to see the latest operating system for a device
11. ACL viewer
12. ACL manipulator
13. ARP Tracker - Read ARP tables and maintain historic MAC/IP address pairings
14. SysLog summary – Show abbreviated SysLog with only important info shown
15. Route Checker - report on the status and health of route table sychronization and stability
16. Syslog setup
17. Change banner
18. Show Tacacs setup
19. Show Radius setup
20. Show NTP setup
21. SNMP Community String Change
Adapters versus APIs
The concept of creating an adapter for a device is great and works very well for many network platforms (i.e. routers, switches, etc). We are interested in expanding this concept to creating standard APIs with systems running applications or services that have equal importance to network functions. For example, many enterprises use Microsoft DHCP and DNS. These are core network services running on a Windows platform. Would it be possible to create an adapter or API that interfaces with such a service or system? The reason for requesting this relates to network change and configuration management of servers. We all struggle with daily administration of server IP addresses. A typical enterprise has server IP addresses embedded in many places; such as the server NIC or OS configuration itself, DHCP, DNS, Load Balancing, Firewalls and/or VPN ACLs, QOS ACLs, Network Management and Monitoring Systems, and the list goes on and on. In considering the day to day support with making changes to the server environment, there is a very large cascading effect to many other network and security services. Just knowning if, when or where an IP address appears in all of these configurations is a challenge itself. Coordinating timely changes to all these systems is something entirely different. The ability to create adapters or APIs for external systems or services would provide a means for "querying" such platforms about IP addresses about to change. This would at the very least provide a road map for what needs to be updated and/or where to focus efforts for change. Having a tool that simply lets you enter the IP address of a current server and return hits on where or how that IP address appears in different devices, systems or configurations would be a great start. Having adapters or APIs that interface with all those devices or systems so one could automate IP address configuration changes across the board would be a welcome site among many network staff. Are there currently any efforts underway to develop a tool as described above? Thanks much!