Thanks to all who joined us for the Gluware DemoFriday: “Software Enable Your Brownfield Network – Automate Multi-Vendor QoS on Routers and NAC.” During the DemoFriday, Gluware demonstrated how they can software enable the automation of brownfield enterprise networks and address use cases including multi-vendor quality-of-service (QoS) on routers and network access control (NAC) on existing switches. After the webinar, we took questions from the audience but unfortunately ran out of time before we could get to all of the questions. Read the full “Software Enable your Brownfield Network” Q&A below.
What does Gluware mean by “orchestration?” Does it include the virtual infrastructure?
To start, for Gluware, “automation” refers to automating a single task or network feature and having the ability to repeat that task many times. For example, to automate the configuration of SYSLOG servers on a device, once automated by Gluware you can add, modify, and remove SYSLOG servers configured on your devices.
For “orchestration,” to Gluware this means the ability to automate many different features (a feature set in combination), as well as the ability to automate across multiple device types. Examples include automating NTP, AAA, SYSLOG, and QOS across all routers and switches in the network. This could also mean orchestrating security policy with rules/ACLs across routers, switches, and firewalls.
Currently, Gluware is not a virtual infrastructure manager (VIM), however, if you’re using a virtual network function (like a router or firewall) once IP reachable, Gluware can be used for configuration management and compliance. Gluware is capable of making API calls to virtualization layers, including VIMs like VMware and even public clouds or OpenStack – it really depends on the customer use case.
When running from the cloud, what kind of cloud? And how does it connect to the network devices?
When running from a public cloud, Gluware requires a proxy server/jump host on premises — which is IP reachable — and is then used to connect to the devices securely via SSH.
Does Config Modeling require Gluware to perform the “onboarding” of the network features?
Today yes, Gluware provides onboarding of the network features. Then, once onboarded, the customers have full control of the feature for lifecycle management and any changes – typically made by editing the CLI [command line interface] provided, which is exposed natively in Gluware. To onboard, all that is required is the configuration CLI and “show” commands to examine the resulting configuration along with the platform details.
Over time, Gluware will expose more capabilities to customers for the self-onboarding of features.
What monitoring does Gluware provide?
Gluware is not a SNMP [simple network management protocol] based monitoring platform. Most customers already have these capabilities in place today, complementary to those existing platforms. Gluware’s focus is on network configuration, change management, and compliance. Gluware can monitor the configuration change as discussed via the Config Drift application.
Does Gluware require an agent to be installed on the network nodes?
No, Gluware does not require an agent. However, for some platforms, Gluware offers an optional agent, which can be used for change notification, backup and recovery, and more.
What if I require support for a vendor platform that is not currently supported?
Gluware is able to add vendor platforms and continues to add more over time based on customer demand. This quarter we are adding two additional vendors. It requires Gluware to release a vendor semantic engine (VSE) and then support it via the various applications like Config Modeling and Config Drift. The addition of vendors can take days to weeks depending on the complexity, and this is based on customer priority.