{"id":299,"date":"2019-01-08T08:49:53","date_gmt":"2019-01-08T08:49:53","guid":{"rendered":"https:\/\/iddles.co.uk\/?p=299"},"modified":"2019-01-08T09:52:35","modified_gmt":"2019-01-08T09:52:35","slug":"driving-cisco-aci-using-powershell","status":"publish","type":"post","link":"https:\/\/iddles.co.uk\/index.php\/2019\/01\/08\/driving-cisco-aci-using-powershell\/","title":{"rendered":"Driving Cisco ACI using PowerShell"},"content":{"rendered":"\n

One thing I have been working on for a long time is to create a set of PowerShell modules for Cisco ACI<\/a>.<\/p>\n\n\n\n

For those that don’t know ACI is Cisco’s Next Generation DataCentre switching fabric. Kind of the next step after Nexus in NX-OS mode. It uses modern tecnniques such as hardware controllers (APIC’s – C220 servers) along with Nexus 9500 and Nexus 93xxx switches to form a leaf-spine deployment.<\/p>\n\n\n\n

Whilst ACI has a GUI, MO and NX-OS like CLI (not perfect at all !) along with Python and even Ansible, these quickly run out of steam. Whilst Python is a great language it still takes some learning. Its also not so intuative when passing results between methods. <\/p>\n\n\n\n

I realised there is nothing for ACI to utilise PowerShell in a similar way that VMware’s NSX has the most excellent PowerNSX<\/a><\/p>\n\n\n\n

Hence, my first cut of ACI-PoSH<\/a> published to GitHub. There is a ton of work to do on this – documentation being a biggie – but it works.<\/p>\n\n\n\n

Development Process<\/h2>\n\n\n\n

I am quite lucky to have been involved in some large scale ACI deploments however when offline from these I have two enviroments that I use.<\/p>\n\n\n\n