Search
-
Re: Systems Vs. Networking
Here's my experience Company X Network Tier 1 (Network Technicians/Analysts) - 25+ people Tier 2 (Network Engineers + Packet guys) - 15+ people Tier 2 (Wireless Network Engineers) - 4 - 6 people Tier 3 (Network Architects) - 4 - 6 people Network Security (If you consider this as network team) Around 5 - 8 people Server… -
Re: Systems Vs. Networking
I was part of networking. The networking and systems teams had around 15 or so people each but also divided up into sub-teams. I will say this... I don't quite recall where I said that networking people are not busy. I did not say that I was not busy. Just to repeat... if you are involved in continual hardware/software… -
Re: Systems Vs. Networking
-
Re: Systems Vs. Networking
-
Re: Systems Vs. Networking
Where I used to work, network is expected to provide proof that it isn't a network issue. Hence, the 5-6 FTE dedicated to do just packet analysis. FW guys don't even check the logs properly and expect network to answer every single network problem. That was the whole reason why we needed read-only access to the Check Point… -
Re: Systems Vs. Networking
You sir, have obviously never administered a good sized network. If things worked the way they were supposed to all the time, there wouldn't be ANY network admins! Of course things break! You can always optimize a network, someone always needs something done. Just because an infrastructure is in place doesn't mean that… -
Re: Systems Vs. Networking
I would disagree. There are companies out there that still operate in silos. Though, I have to say it is changing. The position that I was in was purely routing and switching. No other technology was involved. Sure, we had access to Infinistream Console, ACE Analyst and ACE Live, and Check Point Firewall (read only for… -
Re: Systems Vs. Networking
Oh boy, this argument again. Almost every network engineer that I know that doesn't work for an ISP wears more than one hat, i.e. many are also voice engineers. Inside corporate networks, no news is usually good news, if your network engineering team is always busy this is usually a sign of a needlessly complex network or… -
Re: Systems Vs. Networking
-
Re: Systems Vs. Networking
23 results