Hardware and Software Feature Matrix
This article lists the software release in which vEdge router hardware, Viptela network devices, and Viptela software features were first introduced. For information about specific features, refer to the Release Notes for your software release. For information about command options, refer to the Command Reference for configuration and operational commands.
vEdge Routers
| Router Model |
Software |
Documentation |
|---|---|---|
| vEdge 100 | 15.3.5 | vEdge 100 Router |
| vEdge 100b | 15.4.1 | vEdge 100b Router |
| vEdge 100m | 16.1 | vEdge 100m Router |
| vEdge 100wm | 16.3 | vEdge 100wm Router |
| vEdge 1000 | 14.1 | vEdge 1000 Router |
| vEdge 2000 | 14.2 | vEdge 2000 Router |
| vEdge 5000 | 17.2.2 | vEdge 5000 Router |
| vEdge Cloud | 16.1 | vEdge Cloud Router |
Overlay Network Devices
| Device | Software Release |
Documentation |
|---|---|---|
| vBond orchestrator (hardware only) | 14.1 | Deploy the vBond Orchestrator, vbond |
| • Multiple vBond orchestrators in overlay network | 16.1 | High Availability Overview |
| • Software vBond orchestrator (virtual machine) | 15.2 | |
| • Standalone vBond orchestrator (cannot coexist in device with vEdge router functionality) | 16.1 | vbond |
| • Support for multiple cores on vBond VM | 15.4 | show orchestrator summary |
| vEdge router | 14.1 | Deploy the vEdge Routers |
| • Up to 4 connections to vSmart controllers per router | 14.3 | Configuring High Availability Parameters, max-controllers |
| • Up to 8 connections to vSmart controllers per router | 15.4 | Configuring High Availability Parameters, max-control-connections |
| • USB dongle for LTE connections on vEdge 1000 routers | 16.1 | USB Dongle for Cellular Connection |
| vManage NMS | 15.2 | Deploy the vManage NMS |
| • Multiple vManage NMSs (VMs) | 15.3 | |
| • Up to 8 VM cores for a vMange NMS VM | 15.3.3 | show control summary |
| • vManage cluster | 16.1 | High Availability Overview |
| • vManage cluster support for up to 6,000 routers | 16.1 | High Availability Overview |
| • Multitenant vManage NMS | 17.2 | Use a Multitenant vManage NMS |
| vSmart controller (VMs) | 14.1 | Deploy the vSmart Controller |
| • Multiple vSmart controllers (up to 3 controllers) | 14.2 | |
| • Multiple vSmart controllers (2 or more) | 16.1 | High Availability Overview |
| • Support for up to 20 vSmart controllers by vManage NMS | 15.3.3 |
Control Plane
| Feature | Software Release |
Documentation |
|---|---|---|
| vEdge routers advertise connected and static routes to OMP, in addition to BGP and OSPF external routes | 15.1 | Configuring OMP, advertise |
| • Advertise BGP AS number to BGP neighbors |
17.1 |
overlay-as |
| • Advertise specific routes instead of all routes from a protocol | 16.3 | |
| • Aggregate routes before advertising them | 16.3 | |
| vSmart controllers discard routes rejected by OMP | 15.4 | Configuring OMP, discard-rejected |
| Controller groups to establish affinity between vSmart and vEdge devices. | 16.1 | Configuring Affinity between vSmart and vEdge Devices |
| DTLS | 14.1 | Security Overview |
| • Reset DTLS connections | 14.2 | clear control connections |
| • Track whether DTLS connection to vBond orchestrator is up | 14.1 | track-transport |
| • Tunable Hello timer and multiplier for DTLS tunnels; maximum values increased | 15.2; 16.2 | Configuring Network Interfaces, hello-interval, hello-tolerance |
| Extend WAN transport VPN (TLOC extension) | 15.4 | Configuring Network Interfaces, allow-same-site-tunnels, tloc-extension |
| GRE encapsulation for WAN transport connections | 15.2 | Configuring Network Interfaces |
| IPsec encapsulation for WAN transport connections | 14.1 | Configuring Security Parameters, ipsec |
| Iptables | 15.4 | iptables-enable |
| OMP | 14.1 | Configuring OMP, omp |
| • OMP hold time increased to 60 seconds | 14.2 | omp hold-time |
| OMP graceful restart | 14.2 | omp graceful-restart |
| • Maximum timer increased to 7 days | 15.3.5 | omp timers |
| Police flow of DTLS control session traffic | 14.2 | control-session-pps |
| Security certificates | 14.1 | |
| SHA-2 cryptographic secure hash algorithm | 15.2 | Control Plane Security Overview |
| TLOCs | 14.1 | color |
|
• Up to 7 per vEdge router |
15.4 17.1 15.2 |
|
| • Add TLOC colors private3 through private6 | 15.2 | |
| • Defined by {IP address, color, encapsulation} | 14.1 | tunnel-interface |
| • Load balancing data traffic across tunnels in multi-TLOC environment | 15.1 | Configuring Network Interfaces, encapsulation |
| • Restrict connections so they are between TLOCs of the same color | 15.1, 15.2 |
|
| • Set port offset | 14.1 | port-offset |
| • TLOC extension: Allow tunnels between vEdge routers in same site | 15.4 | Configuring Network Interfaces, tloc-extension |
| TLS | 14.3 | Configuring Security Parameters |
| • Tunable Hello timer and multiplier for TLS tunnels; maximum values increased | 15.2; 16.2 | |
| Transport VPN (VPN 0) | 14.1 | |
| Tunnel interfaces | 14.1 | Configuring Network Interfaces, tunnel-interface |
| • Associate carrier name with tunnel interface | 14.2 | |
| • Configurable hello interval and tolerance | 15.2 | hello-interval, hello-tolerance |
| • Preference for which tunnel to use for connection to vManage NMS | 16.3 | vmanage-connection-preference |
| Tunnel interface services |
14.1 |
allow-service |
| • All (configure all services with a single command) | 15.4 | |
| • BGP | 15.4 | |
| • DHCP | 14.1 | |
| • DHCPv6 | 16.3 | |
| • ICMP | 14.1 | |
| • Netconf | 14.1 | |
| • Netconf on vEdge Routers | 15.4 | |
| • NTP | 14.1 | |
| • OSPF | 15.4 | |
| • SSHD | 14.1 | |
| • STUN | 14.1 |
Data Plane
| Feature |
Software |
Documentation |
|---|---|---|
| AES-GCM-256 encryption algorithm for IPsec tunnels | 16.2 | Configuring Security Parameters |
| AH authentication for IPsec tunnels | 14.2 | authentication-type |
| AH-SHA1-HMA authentication for IPsec tunnels | 14.2 | authentication-type |
| Authentication "none" for IPsec tunnels | 14.2 | authentication-type |
| BFD |
14.1 |
Configuring High Availability Parameters, bfd color |
| • BFD Hello packet units in milliseconds (changed from seconds) | 15.1 | bfd color |
| • Clear counters for BFD transitions | 15.1.1 | clear bfd transitions |
| Cflowd traffic monitoring | 14.3 | Traffic Flow Monitoring with Cflowd |
| • Elements exported to cflowd collector: VPN identifier, sourceIPv4Address, destinationIPv4Address, ipDiffServCodePoint, destinationTransportPort, sourceTransportPort, protocolIdentifier, flowStartSeconds, flowEndSeconds, octetTotalCount, octetDeltaCount, packetTotalCount, packetDeltaCount, tcpControlBits, maximumIpTotalLength, minimumIpTotalLength, ipNextHopIPv4Address, egressInterface, ingressInterface, icmpTypeCodeIPv4, flowEndReason, paddingOctets | 14.3 | |
| • Additional elements exported to cflowd collector: ipClassOfService, ipPrecedence | 15.4.5 | |
| • Monitor ICMP, SCTP, TCP, and UDP flows | 14.3 | |
| • Monitor GRE and IPsec flows | 17.2.2 | |
| DHCP-learned route administrative distance of 1 (same as static routes) | 15.3 | Configuring Segmentation, ip dhcp-client |
| Domains in the overlay network | 14.1 | domain-id |
| ECMP hash key | 14.1 | ecmp-hash-key |
| • ECMP for traffic engineering and service chaining | 15.3 | |
| • Install ECMP routes only if next hop can be resolved | 15.3.3 | |
| • Set maximum number of OMP paths to install in vEdge router's route table | 15.2 | ecmp-limit |
| ESP authentication for IPsec tunnels | 14.2 | authentication-type |
| Flow control | 14.1 | flow-control |
| IKE Version 1 | 17.2 | Configuring IKE-Enabled IPsec Tunnels |
| IKE Version 2 | 17.2 | Configuring IKE-Enabled IPsec Tunnels |
| IPsec | 14.1 | Configuring Security Parameters, ipsec |
| • Anti-replay window | 14.1 | replay-window |
| • Regenerate IPsec keys | 14.2 | request security ipsec-rekey |
| • Rekeying timer | 14.1 | rekey |
| NAT: vEdge router as NAT | 14.2 | Configuring Centralized Data Policy, Configuring Local Internet Exit |
| • Multiple NAT interfaces on router | 15.1 | nat |
| • NAT port forwarding | 15.1 | Configure NAT Forwarding, port-forward |
| • NAT on the service side | 15.3 | Using a vEdge Router as a NAT Device, Configuring Service-Side NAT |
| • Port hopping; enabled by default | 14.3; 15.1 | port-hop |
| • Port hopping per TLOC | 17.2 | |
| • Initiate port hopping | 15.3.3 | request port-hop |
| • Respond to pings to NAT interface's IP address | 15.4 | respond-to-ping |
| • Static NAT | 16.3 | Configuring Service-Side NAT, static source-ip translate-ip |
| • Symmetric NAT | 16.2 | |
| • Track transport interface status | 17.2.1 | Configuring Local Internet Exit |
| Path MTU discovery for regular interfaces | 14.1 | mtu, pmtu |
| • Path MTU discovery for the transport tunnel | 15.1 | bfd color pmtu-discovery |
| Segmentation and VPNs | 14.1 | Configuring Network Interfaces, vpn |
| • Management VPN (VPN 512) | 14.1 | |
| • Service-side VPNs (VPNs except for VPN 0 and VPN 512) | 14.1 | |
| • VPN 512 optional on vEdge 100 routers | 16.1 | |
| SHA1-HMAC authentication for IPsec tunnels | 14.2 | authentication-type |
| Sites in overlay network | 14.1 | site-id |
| Static mapping between hostname and IP address in a VPN | 14.1 | host |
| TCP optimization | 17.2 | tcp-optimization |
Installation and System-Level Features
| Feature | Software Release |
Documentation |
|---|---|---|
| AAA (role-based access) | 14.1 | Configuring User Access and Authentication |
| • Authentication fallback | 15.2.8 | auth-falllback |
| • Authentication order | 14.1 | auth-order |
| • Authentication order for "admin" user | 16.2 | admin-auth-order |
| • Authentication order for console connections | 17.2 | admin-auth-order, auth-order |
| • Force user to log out when permissions change | 15.3 | usergroup |
| • Place user into group "basic" when remote server authenticates but does not specify a user group; home directory is /home/basic | 14.1 | |
| • Place user into two groups when remote and local user authentication specify two groups; home directory is /home/username | 15.2 | |
| • Reset locked user account | 15.4 | request aaa unlock-user |
| Archive running configuration | 14.2 | archive |
| ARP | 14.1 | arp |
| Banners for login and MOTD | 14.1 | banner login, banner motd |
| • Maximum banner length: 2048 characters | 15.1.1 | |
| CLI for configuration and monitoring | 14.1 | Configuration Management Commands, Operational Commands, Command Filters for CLI Operational Commands |
| Collection of system status information for troubleshooting | 14.1 | request admin-tech |
| • Restrict information to include in the admin-tech tar file. | 16.3 | |
| • Run only a single admin-tech command at a time on a device | 16.1 | |
| Confirm configuration commit | 14.1 | commit |
| Confirm software upgrade | 15.1 | request software upgrade-confirm, upgrade confirm |
| Console baud rate | 14.2 | console-baud-rate |
| Core files in /var/crash | 14.1 | show crash |
| • Delete core files | 15.2 | clear crash |
| Default gateway | 14.1 | |
| • Track default gateway | 15.3.5 | track-default-gateway |
| DHCP | 14.1 | Configuring Network Interfaces, dhcp-helper, dhcp-server, ip dhcp-client |
| • vEdge router as DHCP server | 14.3 | |
| • Set administrative distance of routes learned from DHCP server | 15.3 | dhcp-distance |
| • Set IP addresses to exclude | 14.3 | exclude |
| • Set IP address ranges to exclude | 15.1 | exclude |
| DNS servers | 14.1 | dns |
| • Clear DNS cache | 15.3 | clear dns cache |
| • DNS cache timeout | 15.2 | timer |
| FIPS 140-2 level 1 certification for the crypto module |
17.2 |
|
| Firmware (boot loader) upgrade | 15.3.5 | request firmware upgrade |
| GPS location | 14.1 | gps-location |
| Hosname | 14.1 | host-name |
| IEEE 802.1X authentication for WANs | 16.3 | Configuring IEEE 802.1X Authentication |
| IEEE 802.11i authentication for WLANs | 16.3 | Configuring IEEE 802.11i Authentication |
| IPv4 | 14.1 | Viptela Overlay Network Bringup, ip-address |
| IPv6 on transport-side interfaces | 16.3 | Segmentation (VPN) Overview |
| Monitor jobs on the local device | 15.4 | monitor start, monitor stop, show jobs |
| NAT: vEdge router as NAT | 14.2 | Using a vEdge Router as a NAT Device, Configuring Local Internet Exit, nat |
| • Load balancing across NATs | 15.1 | Configuring Local Internet Exit, nat |
| Netstat from CLI | 15.4.5 | tools netstat |
| NTP, Version 4 | 14.1 | Configuring Time and Location, ntp |
| • Set source interface to use when sending NTP packets | 15.4 | |
| • MD5 authentication keys to access NTP servers | 15.4 | |
| • Up to 4 NTP servers | 15.4 | |
| Organization name | 14.1 | Viptela Overlay Network Bringup, organization-name |
| Patch release software image numbering (4-digit image numbers) | 16.1 | |
| Ping | 14.1 | ping |
| • Ping both the primary and secondary host IPv4 addresses in a service VPN | 17.2.2 | |
| RADIUS |
14.1 |
Configuring User Access and Authentication, radius |
| • NAS attributes | 14.2 | |
| • Secret key (deprecate "key") | 15.3.8 | |
| • Set source interface to reach RADIUS server | 14.3 | |
| Reset configuration to factory default | 14.1 | request software reset |
| • Reset configuration to factory default | 15.4 | request reset configuration |
| RESTful APIs | 16.1 | vManage REST APIs |
| • Bulk APIs | 16.2 | Bulk APIs |
| Revert automatically to previous software image if upgrade fails | 15.1 | request software upgrade-confirm, upgrade confirm |
| SFP diagnostics | 16.1 | show interface sfp detail, show interface sfp diagnostic |
| SNMP (Versions 1 and 2) | 14.1 | Configuring SNMP, snmp |
| • 64-bit counters for interface MIBs | 15.4.5 | |
| • Private MIBs and traps | 15.2 | |
| • SNMP Version 3 | 16.2 | |
| • Standard MIBs | 14.1 | |
| Software image signing | 16.1 | Software Installation and Upgrade |
| Static routes for IPv4 | 14.1 | ip route |
| System (syslog) logging to local disk and remote server | 14.1 | Configuring System Logging, logging disk, logging server |
| • Clear contents of all syslog files on local device | 15.4 | request reset logs |
| • Changes to files where syslog message are stored on local device | 15.4 | See Software Operating System table, below. |
| • Set source address to use when sending syslog messages to remote server | 15.4 | |
| • Multiple syslog servers | 15.3 | |
| Software images installed on a device | See Software Operating System table, below. | |
| • 2 per device | 14.1 | |
| • 3 per device | 15.4 | |
| System IP address | 15.1 | system-ip |
| TACACS+ | 14.2 | Configuring User Access and Authentication, tacacs |
| • NAS attributes | 14.2 | |
| • Secret key (deprecate "key") | 15.3.8 | |
| • Set source interface to reach TACACS server | 14.3 | |
| Tcpdump | 14.1 | tcpdump |
| Timezone | 14.1 | clock |
| • IANA timezone database | 15.2 | |
| Traceroute | 14.1 | traceroute |
| Upgrade confirm (on vEdge routers) | 15.1 | request software upgrade-confirm, upgrade confirm |
| • On other Viptela devices | 15.2 | |
| USB controller, enable and disable | 15.3.2 | usb-controller |
| Use remote vManage NMS as software image repository | 17.2 | Software Installation and Upgrade |
| xterm as default terminal in device vshell | 15.4.3 | vshell |
| vContainer virtual machines (VMs) for vSmart Controllers | 16.2 | Deploy the vContainer Host |
| Virtual machine (VM) hypervisor | ||
| • ESXi | 15.2 | |
| • KVM | 16.1 | |
| • SCSI disk driver type | 15.2 | |
| • Virtio SCSI disk driver type | 16.2 | |
| Zero-touch provisioning | 14.3 |
Interfaces
See also Configuring Network Interfaces.
| Feature |
Software |
Documentation |
|---|---|---|
| Autonegotiation mode for Gigabit Ethernet interfaces | 15.3 | autonegotiate |
| Cellular interfaces | 16.1 | cellular, interface cellular profile |
| • CDMA radio access technology (RAT) type | 16.3.1 | technology |
| • LTE radio access technology (RAT) type | 16.1 | |
| Clear Don't Fragment (DF) bit | 14.2 | clear-dont-fragment |
| DHCP | ||
| • DHCP helper | 14.1 | dhcp-helper |
| • Up to 4 IP addresses on a DHCP interface Up to 8 IP addresses on a DHCP interface |
14.3 17.2.2 |
|
| • DHCP server | 14.3 | dhcp-server |
| Ethernet (eth) interfaces on devices hosted on virtual machines | 14.1 | interface |
| Full-duplex/half-duplex mode | 14.1 | duplex |
| Gigabit Ethernet (ge) interfaces on vEdge routers | 14.1 | interface |
| GRE tunnels to transport-side and service-side end points | 15.4.1 | Configuring Network Interfaces |
| Interface speeds | 14.1 | speed |
| • Autonegotiate interface speeds | 15.3 | |
| Loopback interfaces | 14.1 | interface |
| • Bind physical WAN interface to loopback interface | 14.2 | |
| LTE support on vEdge 1000 routers | 16.1 | cellular |
| • Circuit of last resort | 16.2.2 | last-resort-circuit |
| • Minimize control traffic | 16.3 | low-bandwidth-link |
| MAC accounting | 14.1 | mac-accounting |
| MAC addresses | 14.1 | mac-address |
| Management (mgmt) interfaces | 14.1 | interface |
| Maximum segment size (MSS) | 14.1 | tcp-mss-adjust |
| • Dynamic adjustment of MSS based on interface or tunnel MTU | 15.3 | |
| Monitor bandwidth usage on transport circuit | 16.2 | bandwidth-downstream, bandwidth-upstream |
| MTUs | 14.1 | mtu |
| • Maximum MTU 2000 bytes | 16.3 | |
| PMTU and MTU discovery | 14.1 | pmtu |
| Point-to-Point Protocol over Ethernet | 15.3.3 | pppoe-client |
| PPP virtual interface | 15.3.3 | ppp |
| • CHAP or PAP authentication | 15.3.3 | |
| • CHAP and PAP authentication | 17.1 | |
| Reset an interface | 15.3 | request interface-reset |
| Secondary IPv4 addresses for service-side interfaces | 17.1 | secondary-address |
| System interface | 14.1 | interface |
| Track interface tag | 15.3.8 | track-interface-tag |
| Traffic shaping | 14.1 | shaping-rate |
| Tunnel interface (in WAN transport VPN, VPN 0) | 14.1 | interface |
| VRRP | 14.1 | vrrp |
| • Track OMP session to determine status of master router | 14.1 | |
| • Track specific interfaces to determine status of master router | 15.2 | |
| Wireless LAN (WLAN) | 16.3 | wlan |
Routing Protocols
| Feature | Software Release |
Documentation |
| BGP | 14.1 | Configuring Overlay Unicast Routing, bgp |
| • Carry BGP AS path into OMP | 17.1 | propagate-aspath |
| Bridging | 15.3 | Configuring Bridging and IRB, bridge |
| IGMPv2 | 14.3 | Configuring Overlay Multicast Routing, igmp |
| Integrated routing and bridging (IRB) | 15.3 | Configuring Bridging and IRB |
| Multicast routing | 14.2 | Configuring Overlay Multicast Routing |
| • Control interface bandwidth allowed for multicast traffic. | 16.1 | multicast-buffer-percent |
| • Multicast replicator | 14.2 | multicast-replicator |
| • Use full interface bandwidth | 16.1 | |
| OMP | 14.1 | Configuring OMP, omp |
| • Advertise backup routes to vEdge routers | 15.2 | send-backup-paths |
| • Advertise learned BGP and OSPF external routes into OMP | 14.1 | |
| • Advertise connected and static routes into OMP | 15.1.1 | |
| • Assign overlap AS number to OMP | 17.1 | overlay-as |
| • Discard routes rejected by policy | 15.4 | discard-rejected |
| • Set maximum number of equal-cost routes to advertise; change maximum to 16 | 14.2; 15.2 |
send-path-limit |
| OSPF | 14.1 | Configuring Overlay Unicast Routing, ospf |
| • Clear entries in OSPF database | 14.2 | clear ospf database |
| PIM-SM | 14.2 | Configuring Overlay Multicast Routing, pim |
| • Auto-RP | 14.2 | auto-rp |
| • Clear mappings of multicast groups to RPs | 14.3 | clear pim rp-mapping |
| • SSM for first-hop routers | 16.1 | |
| Transport-side routing (BGP, OSPF in VPN 0) | 14.2 |
Policy and Forwarding
| Feature |
Software |
Documentation |
|---|---|---|
| Access lists (ACLs; localized data policy) | 14.1 | Configuring Localized Data Policy |
| • Set DSCP in access lists | 15.2 | |
| • Support multicast traffic (except for mirroring) | 16.3 | |
| Application-aware routing | 14.2 | Application-Aware Routing Configuration |
| • Multiple preferred colors | 17.1 | action |
| • Prefer a TLOC for data traffic that matches SLA parameters | 15.2 | action |
| • Prefer a TLOC for data traffic that does not match SLA parameters | 16.3 | action |
| Centralized control policy | 14.1 | Configuring Centralized Control Policy |
| • Match on list of TLOC colors (in addition to matching on individual colors) | 15.4 | match |
| • omp-tag option replaces tag option | 15.4 | action, match |
| • Direct matching routes or TLOCs using configured action | 16.3 | action |
| Apply policy—Add restrictions so that you cannot apply the same type of policy (for example, data-policy or control-policy) to sites lists that contain overlapping site IDs Overlapping site IDs for different types of policies (among app-route-policy, cflowd policy, control-policy, and data-policy) |
15.4 16.3 |
apply-policy |
| Centralized data policy | 14.1 | Configuring Centralized Data Policy |
| • Apply centralized data policy to data traffic entering local site from service side, from tunnel interface, or both | 15.3.3 | |
| • Set GRE encapsulation | 15.2 | |
| • Set IPsec encapsulation | 14.1 | |
| Cflowd traffic monitoring | 14.3 | Traffic Flow Monitoring with Cflowd |
| • Cflowd visibility to allow router to perform traffic flow monitoring on LAN traffic coming in to router | 15.3 | flow-visibility |
| • Configuring flow sampling interval | 16.3 | flow-sampling-interval |
| • Inactive flow timeout changed to 1 minute | 15.3 | flow-inactive-timeout |
| Class maps | 14.1 | Configuring Localized Data Policy, Forwarding and QoS Configuration Examples |
| • Change LLQ queue from queue 1 to queue 0 | 14.2 | class-map |
| Deep packet inspection (DPI) | 15.2 | Configuring Centralized Data Policy, app-visibility, policy lists |
| • Policy matching on specific applications and application families | 15.3 | |
| • DPI and NAT on same router | 15.4 | |
| Ingress traffic sent to specific queue | 15.3 | static-ingress-qos |
| Localized control policy (for BGP, OSPF) | 14.1 | Configuring Localized Control Policy |
| • Match and set tag value to pass into OMP (for BGP, OSPF) | 15.4 | |
| • Match OSPF inbound routes | 15.4 | route-policy |
| • Match OSPF tag | 17.1 | match |
| Log action for logging packet headers | 16.3 | log |
| Mirroring | 14.1 | Configuring Localized Control Policy, mirror |
| Packet loss priority (PLP) match in application-aware routing policy, centralized data policy, localized data policy (access lists) | 16.3 | Configuring Application-Aware Routing, Configuring Centralized Control Policy, Configuring Centralized Data Policy, match |
| Policers | 14.1 | policer |
| • Set rate to deliver packets to control plane | 15.4 | host-policer-pps |
| • Set number of ICMP error message to generate or receive | 15.4 | icmp-error-pps |
| Policy configuration workflow in vManage NMS | 17.1 | Configuration ► Policies |
| QoS maps | 14.1 | qos-map |
| QoS scheduling and shaping on vEdge Cloud routers | 16.3 | cloud-qos, cloud-qos-service-side |
| Rewrite rules | 14.1 | rewrite-rule |
| Service chaining: Support for firewall, IDP, IDS, four custom services | 14.1 | Service Chaining |
| • ECMP for traffic engineering and service chaining | 14.3 | Configuring Centralized Control Policy, Configuring Centralized Data Policy |
| • Services available via GRE interfaces | 15.4.1 | |
| SLA classes | 14.2 | sla-class |
| • Define by latency and loss | 14.2 | |
| • Define by jitter | 16.2 | |
| • Multiple preferred colors (TLOCs) | 17.1 | Configuring Application-Aware Routing, action |
| Split DNS | 17.2 | Configuring Split DNS |
| Variables in data policies for vEdge routers | 16.2 | Configure Policies |
Software Operating System
|
Feature |
Releases 15.4 and Later |
Releases 15.3 and Earlier |
|
Number of software images that can be installed on a device |
3 |
2 |
|
Hard disk partition size on vEdge routers |
Routers with factory-installed software:
Routers with software upgraded from Release 15.3 or earlier:
|
Primary: 2.0 GB |
|
Command to boot a software image |
||
|
Synchronize a configuration when activating (upgrading or downgrading) a previously activated image |
Previous image's configuration is always retained. |
You can choose to retain the previous image's configuration (sync, which is the default) or to return to the default-factory configuration (no-sync). |
|
Restore default-factory configuration |
Boot with image marked as "default" (via the request software set-default command). |
Boot with the configuration included when the router was shipped. |
| Display information about software images |
show software displays all installed images, marked as active, previous, and factory default. Also displays timestamp and whether upgrade-confirm was performed by user. |
show boot-partition displays active and secondary image versions. |
|
Issuing shell commands |
request execute command |
request execute "command" |
|
Syslog files on the local device (/var/log/vdebug and /var/log/vsyslog) |
Hostname and log message severity not included in the files. |
Hostname and log message severity included in the files. |
|
Configuration (confd) log files |
/var/log/auth.log (available in Releases 15.4.2 and later) |
/var/log/confd/audit.log |
vManage NMS
See also vManage NMS Product Help.
| Feature | Software Release |
Documentation |
|---|---|---|
| Automatically adjust vManage data volume size | 17.2 | request nms application-server |
| Basic vManage NMS | 15.2 | |
| Browser support: Safari | 15.2 | |
| • Chrome | 15.3 | |
| • Firefox | 15.3 | |
| Certificate management from vManage NMS | 15.2 | Security Certificates |
| Client user session idle timeout | 17.1 | Administration ► Settings |
| CloudExpress service | 16.3 | Using CloudExpress Service |
| • For sites with direct internet access (DIA) | 16.3 | |
| • For DIA sites that access the internet through a secure web gateway | 17.1 | |
| Cloud OnRamp Service | 17.2 | Configuring Cloud OnRamp Service |
| Collect data streams from vEdge routers | 17.2.2 | Administration ► Settings |
| Configuration templates | 15.3 | Device Configuration |
| • Edit templates simultaneously from one or more vManage servers | 17.2 | Configuration ► Templates |
| • Policy configuration workflow | 17.1 | Configuration ► Policies |
| • Roll back to previous router configuration | 17.2 | Configuration ► Templates |
| • View changes to configuration templates | 17.2 | Audit Log |
| Custom vManage server logo | 16.1 | request nms application-server update-logo |
| Device groups | 14.2 | |
| Display memory usage for vManage cluster statistics database | 17.1 | Administration ► Cluster Management |
| Login banner on vManage server | 16.1 | Administration ► Settings |
| Multiple versions of Viptela software image on vManage NMS | 15.4 | |
| Multitenancy | 17.2 | Use a Multitenant vManage NMS |
| Overwrite configuration from the CLI on devices managed by and configured from vManage NMS | 15.2 | commit |
| Replace and remove a vEdge router from vManage NMS | 15.4 | |
| Scrollbars | 16.1 | |
| SSH window based on the current browser size and does not readjust if you change window size; vertical scroll bar in SSH window. | 15.3.5 | |
| Start and stop the vManage NMS. | 15.4 | request nms-server |
| Statistics filtering | 16.1 | |
| Status of network devices | Determine the Status of a Network Device | |
| • Controller devices | 17.2 | |
| • vEdge routers |
15.2 |
|
| Support for up to 20 vSmart controllers | 15.3 | |
| Time ranges for filtering output | 16.1 | |
| Troubleshooting tools | vManage Troubleshooting How-Tos | |
| • Data traffic tunnel statistics | 17.2 | View Tunnel Health |
| • Debug log | 17.2.2 | Use Syslog Messages |
| • nping | 17.2 | Ping a Viptela Device |
| • Router bringup status | 17.2 | Troubleshoot Device Bringup |
| • View application-aware routing traffic data | 17.2 | Check Application-Aware Routing Traffic |
| • View control connections | 17.2.2 | View Control Connections |
| vAnalytics platform | 16.3 | View Network Performance with vAnalytics Platform |
| vEdge Cloud router lifecycle management | 17.1 | Install Signed Certificates on vEdge Cloud Routers, Decommission a vEdge Cloud Router |
Viptela Software Releases
Releases in 2017
- Release 17.2, October 2017
- Release 17.1, April 2017
Releases in 2016
- Release 16.3, December 2016
- Release 16.2, July 2016
- Release 16.1, April 2016
Releases in 2015
- Release 15.4, December 2015
- Release 15.3, August 2015
- Release 15.2, May 2015
- Release 15.1, February 2015
Releases in 2014
- Release 14.3, December 2014
- Release 14.2, August 2014
- Release 14.1, March 2014