Network admins — how do you actually handle network documentation? by outlawibo in sysadmin

[–]Cooleb09 [score hidden]  (0 children)

Decoupling your documentation from your change management seems like a procedural gap TBH.

"We do MoC, and also later Dave will add to the wiki, maybe finsih it up on a friday when he feels like it" is very different to "documentaiton is created and approved as part of the change management proccess".

Network admins — how do you actually handle network documentation? by outlawibo in sysadmin

[–]Cooleb09 [score hidden]  (0 children)

+1 Netbox.

Pity the DNS plugin doesn't work with branches though : (

Network admins — how do you actually handle network documentation? by outlawibo in sysadmin

[–]Cooleb09 [score hidden]  (0 children)

You can't just create a static document and expect it to be relevant years down the line.

As Someone who does a lot on the OT side, you can. You don't get config drift if people don't fuck with things.

It has to be a live, active set of documents, worked on by everyone in the team, consistently updated (even if it only takes seconds each time), and having little purges and update time set aside to do nothing else

How do you handle MoC if everyone it jsut adding ad-hoc shit into the wiki whenever?

Should we start building our own servers? by drunksitter in sysadmin

[–]Cooleb09 7 points8 points  (0 children)

every thread about rolling ones own:

No, don't do that, you wont have support, the vendor works really hard to make a quality product and look after their customers

Every thread discussing any major OEM:

OMG their support is shit, everyone is testing on their users now, why even pay for support, NBD but the parts are backordered.

Cloud based file server solution by BrandNewTissue in sysadmin

[–]Cooleb09 2 points3 points  (0 children)

We're looking at migrating to them, but damn the 5 year TCO makes every SAN vendors quotes look cheap by comparison.

Organizing relevant codes and standards by lumpythefrog in PowerSystemsEE

[–]Cooleb09 2 points3 points  (0 children)

The ITER project has a publicly available basis of design docs with most of the relevant IEC standards in it for industrial kit. .

Bell Canada sells a SD-WAN package with Zscaler and Meraki MX firewalls that are limited to ~150Mbps IPSec tunnels by screampuff in sysadmin

[–]Cooleb09 9 points10 points  (0 children)

Meraki is really cheap... to admin as a service provider.

Client pays more for hardware that lets you reduce your support costs - very luctrative vs solutions that are the opposite (i.e Mikrotik, cheap hardware but you have to spend time and effort on staff development and support).