Powershell DSC for Networking (or external devices in general)

i've been writing full .net library , rest api service broker cisco network equipment precise parsing of output , show commands (open source.. share soon) , have been building full fsm managing cisco devices accounts locks, states, etc...

since adopting powershell dsc, i'm working on trying manage infrastructure well. example, i'd powershell dsc allows me specific define topology , configuration of network.

more importantly, i'd manage devices powershell dsc objects well.

is there method in powershell dsc allow description of topology?

an example :

switch (is type access switch)

 switch ports 1-24 access ports

 switch ports 25-26 uplink ports

 switch port 25 connected distribution switch port 2

 switch port 26 connected distribution switch b port 2

access port (is type of cisco switch port)

 access port has spanning tree port fast

 access port has 802.1x port authentication

802.1x port authentication (is cisco device feature)

 802.1x requires aaa radius configuration

 802.1x has mac authentication bypass

etc...

so, i'd configure entire network using dsc style configuration.

cisco devices lack powershell agent on them. 

cisco ucs servers did kinda ugly. instead of adding powershell agent, implemented full set of powershell tools , made ucs dsc part of location configuration of server. has no ability handle fail-over , bit of mess.

is there clean way of configuring , pushing/pulling configs external (non-powershell) devices?

powershell dsc has no methods of type request.  have search dsc configurations have been built others or design , build own.

start posting scripts , modules in vendors forum.  convert scripts dsc.

dsc not available on non-windows systems.  again - post in vendor forums see if has been updated per vendor.

a dsc configuration can applied external devices  cannot pushed or pulled without vendor support.

most major vendors supply api access devices.  many supply wmi (cim) access in way.  provide snmp.

mostly need more research.  vendor forums best place advice experienced techs.

---

\_(ツ)_/

Windows Server  >  Windows PowerShell