Week 12 Reflection

This week has been a great one. I got to work on some firewall configurations for a firewall going to a Head Start location in Burlington, which was a great experience in a live environment. I have noticed this week that the availability of our systems is key (which is obvious), but even when implementing a new system, that doesn't work, we take the mentality of if it isn't broke, don't fix it. Which kind of happened with setting up the failover firewall with a VPN tunnel to Oak Harbor Campus from Mount Vernon Campus, because we ended up reverting to the old configuration, because the new configurations for the failover firewall were not working. But on the other hand, this morning I had to replace a UPS with a UPS that would work because the front desk stations at the help desk weren't connected to the network. So this is a case for fixing something because it is broken (UPS had a puffed-out battery). A lot of the fixes and solutions in IT can feel very context-dependent on the situation. I hope to have another great week.

Comments

Post a Comment

Popular posts from this blog

Friday, April 18

Today was a slow day. I ended up doing two classroom calls, one of which had a speaker issue, which was not being able to hear audio out of the speaker. To fix this, I noticed the Extron was stuck in a reboot, so I unplugged it and plugged it back in then it appeared to work like normal. The next classroom call was an Elmo video display issue, for which the fix was to replace the VGA cord, and it worked after this. Then the rest of the day I spent imaging laptops and organizing the tech workroom.
Read more

Wednesday, April 23

Today, I started by joining a walk around campus with an HVAC worker, an electrical worker, someone from maintenance, and the network admin I am interning with. The point of the walk around was to identify access for electrical and network wires for meters that will go into the boiler rooms all around the campus. Then, for the rest of the day, I was inputting more phone info about the VoIP system for the E911 system that will be implemented later. Still have to work out a few of the mystery phones in the Excel spreadsheet by tracking them down, but I inputted every VoIP phone from every building on campus in this Excel sheet, and the new names for the interfaces on the switches are based on the room they are found in.
Read more

Week 1 Reflection

This first week interning felt like jumping straight into it, which is normal but still comes as a bit of a shock to the system. With my time working in IT in general, it seems to be a very team-focused profession. For example, the network admin and I got stuck on how to properly configure VLANs and how to give access to said VLANs on the switches, because they were all Aruba switches and not HP, which is what he is used to. But thank goodness for online forums, resources, and working as a team. What I learned this week about how my employer manages their IT resources is that they use a lot of segmentation, and how it can keep certain responsibilities and access to resources depending on where an end user's machine is placed in a VLAN/ subnet. For example, a podium PC shouldn't have access to printing, and a faculty's personal machine is allowed to print, which is due to network segmentation of the device.
Read more