Posts

Viptela provides an automatic provisioning software as a service (SaaS) called zero-touch provisioning (ZTP) The default configuration that is shipped on non-wireless hardware vEdge routers includes the following commands that allow the ZTP process to occur automatically: system vbond ztp.viptela.com—Configures the initial vBond orchestrator to be the Viptela ZTP SaaS server. vpn 0 interface ip dhcp-client—Enables DHCP on one of the interfaces in VPN 0, which is the transport interface. This interface must be connected to the Internet, MPLS, metro Ethernet, or other WAN network....

A phone that has never been registered to Cisco CallManager would be in Unknown status. But, a phone that was registered to the Cisco CallManager at some point of time can be in Unregistered or Unknown status depending on a service parameter in the “RIS Data collector” service. This parameter specifies the RIS database information storage period for any unregistered or rejected device information from the Cisco CallManager service. After the time specified in this parameter expires, Cisco CallManager removes the expired entries during the next RIS database cleanup time (specified in the RIS Cleanup Time of the Day parameter) Default: 3 Minimum: 1 Maximum: 30 Unit: day...

Key components of the solution: vManage Network Management System (NMS)—The vManage NMS is a centralized network management system that lets you configure and manage the entire overlay network from a simple graphical dashboard - in the data center. vSmart Controller—The vSmart controller is the centralized brain of the Viptela solution, controlling the flow of data traffic throughout the network. The vSmart controller works with the vBond orchestrator to authenticate Viptela devices as they join the network and to orchestrate connectivity among the vEdge routers - in the data center....

Here is how I usually configure NEW-Guest-Endpoints purge policy and options we have. Administration > identity Management > Settings > Endpoint Purge ElapsedDays—Number of days since the object is created. For every day purge: " Elapsed Days less than 1 “: This should work for brand new endpoints, but what if you implement this purge rule after ISE has already learned the MAC addresses for a few days. Now they will never get purged....