This is the start of a series of posts about my adventures in getting a Cisco IWAN project deployed.
To start with, the new gear order was as follows:
- HQ
- Two Cisco ISR 4331 routers (Cisco ONE for WAN license)
- One to terminate MPLS and one for Internet
- Two CSR 1000V routers in an HA pair
- Cisco WAAS virtual central manager (vCM)
- Cisco WAAS virtual application engine (AE)
- Cisco Prime VM
- Cisco virtual network analysis module (vNAM)
- LiveAction Pro
- Site 1 (MPLS only)
- Cisco ISR 4351 (Cisco ONE for WAN license)
- UCS E-160D-M2 server
- 64GB RAM
- 3x 900GB drives in RAID 5
- Site 2 (Dual connected)
- Two Cisco ISR 4351 (Cisco ONE for WAN license)
- Two UCS E-160D-M2 servers
- 64GB RAM
- 3x 900GB drives in RAID 5
- Site 3 (VPN Only)
- Cisco ISR 4351 (Cisco ONE for WAN license)
- UCS E-160D-M2 server
- 64GB RAM
- 3x 900GB drives in RAID 5
For the remote sites, this will completely replace any routers, firewalls, servers, and/or WAN accelerators deployed. From the HQ side this will augment the existing environment, as the current hardware still needs to support sites that aren’t migrating to the ISR solution yet.
 |
| IWAN topology |
There were a few iterations of the design process. I would recommend working with your Cisco partner to figure out what the best design would be for your environment