I work on an enterprise network with multiple different systems-including servers, thin clients, SAN, and terminal concentrators (serial connections for telnetting into the connected servers). I just started but it does seem like I mostly wait until things break to do any work as most of the production network is already set-up and used for testing by testing engineers for space systems. There are multiple proprietary systems/software being used by the sys admins/engineers. This environment is very server/systems heavy, not so much traditional networking going on as far as I can tell. Also, the network is mostly closed off from the outside world with 1 egress point from a core router to simulate a WAN connection for certain systems/scenarios that I'm am not privy to. I am still learning this network so this is about as much minute articulation I can convey currently.
I was looking for ideas on what to do during my down-time. The most I could come up with so far is to physically map out at the very least the rack elevations, and devices IP's for SSH, telnetting, etc? Also, maybe map out each P2P connection for physical troubleshooting and my own selfish understanding. I'm sure there is plenty of project ideas, but it could be a lot of "I don't know what I don't know" happening right now. Any extra ideas for projects I could work on, things I can implement, other things I'm not thinking of right now? Thanks for all your help!
No comments:
Post a Comment