If I touch it, I then own it (warranty). "That Dell guy messed with it and now it doesn't work". I don't touch anything until I confirm the serial number matches what is in my ticket. Thanks, it is really cool you do this. So much on you tube is from folks who want to get rich with youtube, they really don't use the the item they are reviewing. You are doing it old school, meaning, you are a guy who lives this and has enough courage to share when you can.
And this is EXACTLY why I don't touch other people's equipment. Could I fix it? Maybe. Should I? Heck nope. I can most assuredly guarantee you that I am not making bank off of UA-cam. I get like $150 every other month because I don't give a crap about the algorithm. God bless!
Reminds me of one of my jobs installing and troubleshooting home security systems. I started working for another company (the grass is always greener you know) and my duty was to troubleshoot systems that were already installed. Every time I went out to a home to troubleshoot, the system was horrid - installed incorrectly and straight-up unauthorized installation methods (speaker installed INSIDE the alarm box, wrong wires - not fire rated etc…) so I ended up spending time fixing other issues aside from what I was called out to do. Ended up taking longer and that was an issue (I was taking too long). I told the dispatcher lady every time I went out everything was a mess, and she told me I’m not expected to do “housecleaning”, just fix the issue the customer was complaining about. Well, I didn’t work there long, because the whole mess was a cluster… I couldn’t in good faith just leave things in a mess and installed in violation of the company (it was Brinks at the time).
@@NetworkAdminLife Exactly! It would torment me if I left a site knowing something wasn’t done right. Especially dealing with alarm systems - if someone didn’t hear the alarm speaker because it was installed inside the alarm box and ended up not getting out of a burning house, that could end up a life or death issue. Leaving that place was one of the best career decisions I had ever made.
Grace & Peace 2 you brother! Techno Porn is hilarious!! Thanks 4 another great video coming from the the MDF! Boundaries are super important and often crossed and overlooked in I.T. We sometimes have to tell the telco and ISP people, hey, everything on the outside of the building is your responsibility, everything on the inside is ours...meaning the demarcation point or that little box attached to the outside of the building Well as usual, be well, be safe and God Bless brother! 🙏🏽
The reminds me of my time working in a data center for a large investment bank where I had to deal with different silos and networking guys. Good stuff.
Very helpful. Company I’m with has racks with many different entities that service the many pieces of hardware mounted in just the one rack. Luckily, my colleagues are well aware of these boundaries and know how to do their jobs effectively and know who to call when the issue becomes out of their scope/range which keeps the organization running smoothly.
That's great. We have a mini-colo down at the county office. We have some equipment in their data center but it is locked in a cage they don't even have access to. Only the server guy and myself have keys Trouble is, I don't have a way to get into the data center! LOL! God bless!
This is the job I want someday. Its the only thing I have ever found that I actually enjoy. Which is Networking or just system administration. Hopfully I can just get my foot in the door this year.
This video is a good rendition of every day at my last job. AT&T, Cisco, off-hours, escalations. We were low-man on the contractor totem pole and I was lead. 80% of the issues handed to me weren't my job till they were. Load balancers, Web, software, DBs, networking, reporting; name it. So happy to be gone.
That's the problem with a lot of companies. They think they can hire an IT guy that can fix anything. As complex as systems are getting these days, those type of IT guys get burned out pretty quick. God bless!
I don't know why the algorithm(s) landed me here, but I'm glad they did. I appreciate you dumbing down the word "demarc" to boundaries for the greens. As a younger sysadmin, I've been more recently leaning into the whole concept of boundaries lately. The problem is (not tooting my horn) that network and system admins are smart people. We can learn and figure shit out on the fly. The problem is that all the other specialists soon learn that we're often the smartest people in the room and turn off their brains, and begin to rely on us for most everything. As far as I'm concerned, if there's an issue with only a *specific application* and *everything else* is working dandy, and the *system requirements* have been met, it's no longer my problem - the boundary is within the application. If *every* application is having an issue? Then we can talk, but don't bring me an application-specific issue and make it my problem. We have domains of specialization for a reason.
Glad you landed here too! And dude, it sounds like you live inside my brain! You are obviously a man who's been there done that bought the t-shirt, and now use it as a rag to wash the car with. I always tell people that being a network admin is a lot like being a lawyer, you spend 99% of your time trying to prove your client (the network) is not guilty. The remaining 1% you spend trying to bail your client out (by fixing it). I really love it when they fix "the network problem" by rebooting a server somewhere. God bless!
we use Network Termination Equipment (NTE) for end points in the building, and Network Termination Device (NTD) for managed devices on the network. so things like the endpoint of a telco would be the NTE and the router attached to it that is managed by them or another company would be the NTD.
shorts seem to fit the short attention span of the target demographic and not by coincidence, the datamining needs of the providers. we are feeding the beast.
Techno-porn? Would this be the "amateur" category? Same thoughts on your lack of network and power monitoring. What is going on there? You need some professional help?
You had to follow a wire? Why don't you have cable plant and cross-connect documentation for your DC? I get it is their circuit, but don' t you identify endpoints of the cables in your tray?
I get government on top of hospital, PCI and normal business segregation makes for many silos, yet difficulty like this is an excellent opportunity to drive change from within. Or you can continue to throw your hands up, put your finger on your nose and say "not it".
Okay, three different comments. I'm going to reply to all three on this comment. Your comments come from a younger go-getter and that's great. But I have far more years behind me than in front of me. Also, there is no team to manage all this hardware, it's me. Just me. I don't have the luxury of time to do these wonderful things you suggest. Wish I did. Lastly, why do you assume I don't monitor my network? I have a feeling this is the first video on my channel that you've watched. God bless!
Oh, and to be more specific on not being able to ping the UC Daivs router,; it's because it is apparently misconfigured. My network monitoring software can ping everything on my network but their router.
If I touch it, I then own it (warranty). "That Dell guy messed with it and now it doesn't work". I don't touch anything until I confirm the serial number matches what is in my ticket. Thanks, it is really cool you do this. So much on you tube is from folks who want to get rich with youtube, they really don't use the the item they are reviewing. You are doing it old school, meaning, you are a guy who lives this and has enough courage to share when you can.
And this is EXACTLY why I don't touch other people's equipment. Could I fix it? Maybe. Should I? Heck nope. I can most assuredly guarantee you that I am not making bank off of UA-cam. I get like $150 every other month because I don't give a crap about the algorithm. God bless!
Reminds me of one of my jobs installing and troubleshooting home security systems. I started working for another company (the grass is always greener you know) and my duty was to troubleshoot systems that were already installed. Every time I went out to a home to troubleshoot, the system was horrid - installed incorrectly and straight-up unauthorized installation methods (speaker installed INSIDE the alarm box, wrong wires - not fire rated etc…) so I ended up spending time fixing other issues aside from what I was called out to do. Ended up taking longer and that was an issue (I was taking too long). I told the dispatcher lady every time I went out everything was a mess, and she told me I’m not expected to do “housecleaning”, just fix the issue the customer was complaining about. Well, I didn’t work there long, because the whole mess was a cluster… I couldn’t in good faith just leave things in a mess and installed in violation of the company (it was Brinks at the time).
If I am assigned to fix something, I'll leave it better than I found it for sure. God bless!
We have all been there a time or two.
@@NetworkAdminLife Exactly! It would torment me if I left a site knowing something wasn’t done right. Especially dealing with alarm systems - if someone didn’t hear the alarm speaker because it was installed inside the alarm box and ended up not getting out of a burning house, that could end up a life or death issue. Leaving that place was one of the best career decisions I had ever made.
God bless you sir & thank u for the great content 👊🏾💫
So nice of you! God bless.
Grace & Peace 2 you brother! Techno Porn is hilarious!! Thanks 4 another great video coming from the the MDF! Boundaries are super important and often crossed and overlooked in I.T. We sometimes have to tell the telco and ISP people, hey, everything on the outside of the building is your responsibility, everything on the inside is ours...meaning the demarcation point or that little box attached to the outside of the building Well as usual, be well, be safe and God Bless brother! 🙏🏽
God bless Sam!
The reminds me of my time working in a data center for a large investment bank where I had to deal with different silos and networking guys. Good stuff.
That's awesome. God bless!
Very helpful. Company I’m with has racks with many different entities that service the many pieces of hardware mounted in just the one rack. Luckily, my colleagues are well aware of these boundaries and know how to do their jobs effectively and know who to call when the issue becomes out of their scope/range which keeps the organization running smoothly.
That's great. We have a mini-colo down at the county office. We have some equipment in their data center but it is locked in a cage they don't even have access to. Only the server guy and myself have keys Trouble is, I don't have a way to get into the data center! LOL! God bless!
@@NetworkAdminLife And yet they wouldn’t like us tailgating, go figure lol
This is the job I want someday. Its the only thing I have ever found that I actually enjoy. Which is Networking or just system administration. Hopfully I can just get my foot in the door this year.
Best of luck! God bless!
right there with you with my certifications and nearing my bachelors. this is our year.
my old job i would be the guy att would of sent out back in the days. i love this thanks for sharing.
Glad you enjoyed it! God bless!
This video is a good rendition of every day at my last job. AT&T, Cisco, off-hours, escalations. We were low-man on the contractor totem pole and I was lead. 80% of the issues handed to me weren't my job till they were. Load balancers, Web, software, DBs, networking, reporting; name it. So happy to be gone.
That's the problem with a lot of companies. They think they can hire an IT guy that can fix anything. As complex as systems are getting these days, those type of IT guys get burned out pretty quick. God bless!
I don't know why the algorithm(s) landed me here, but I'm glad they did. I appreciate you dumbing down the word "demarc" to boundaries for the greens.
As a younger sysadmin, I've been more recently leaning into the whole concept of boundaries lately. The problem is (not tooting my horn) that network and system admins are smart people. We can learn and figure shit out on the fly. The problem is that all the other specialists soon learn that we're often the smartest people in the room and turn off their brains, and begin to rely on us for most everything.
As far as I'm concerned, if there's an issue with only a *specific application* and *everything else* is working dandy, and the *system requirements* have been met, it's no longer my problem - the boundary is within the application. If *every* application is having an issue? Then we can talk, but don't bring me an application-specific issue and make it my problem. We have domains of specialization for a reason.
Glad you landed here too! And dude, it sounds like you live inside my brain! You are obviously a man who's been there done that bought the t-shirt, and now use it as a rag to wash the car with. I always tell people that being a network admin is a lot like being a lawyer, you spend 99% of your time trying to prove your client (the network) is not guilty. The remaining 1% you spend trying to bail your client out (by fixing it). I really love it when they fix "the network problem" by rebooting a server somewhere. God bless!
Hi from a Infrastructure Manager from Georgia. Yep 100% on the boundaries you talk about LOL.
Yep. I don't get paid to troubleshoot other people's equipment. God bless!
@@NetworkAdminLife God bless you too.
funny you laid out the boundaries re the phone - i currently have a cisco phone issue ticket. some work, others don't, seems to be error by telco
we use Network Termination Equipment (NTE) for end points in the building, and Network Termination Device (NTD) for managed devices on the network.
so things like the endpoint of a telco would be the NTE and the router attached to it that is managed by them or another company would be the NTD.
And in this case, neither the router nor the telco equipment are managed by me. So it can be a bit of a struggle at times. God bless!
hey am a cisco ccnp certified i dream to be in a such place . have a good time bro
Keep trying. Your time will come. God bless!
shorts seem to fit the short attention span of the target demographic and not by coincidence, the datamining needs of the providers. we are feeding the beast.
Better to feed the beast than be eaten by it. God bless!
Glad to hear AT&T is just as bad to work with in your area too :)
It sure is! How can they not know they disconnected a hospital's main DID trunk??! God bless!
as i was listening to this i'm thinking 'this sounds like me dealing with att on a weekend'.
Please do more Extreme “how to” MLT SMLT Isid
I'll see what I can do. God bless!
do you have ccna? or ccnp .thanks
I have held MCSE, MCSA, CCNA at one time. All my certifications have lapsed. God bless!
Face palm........ and ya I learned that lesson early in my career lol
And sometimes we have to learn the same lesson multiple times. At least I do. God bless!
@@NetworkAdminLife true da.
I love copper
Who doesn't? God bless!
@@NetworkAdminLife Beep beep!
do you think a network engeer , the age ?
I don't think age matters. It's knowledge and an ability to research and find answers. God bless!
hello sir nice
Thanks and welcome. God bless!
Easiest way to troubleshoot Ubiquity is to replace it with a real piece of kit.
All I can say to that is LOL! With you, not at you. God bless!
Don’t step on my toes
Um, okay. God bless!
Techno-porn? Would this be the "amateur" category? Same thoughts on your lack of network and power monitoring. What is going on there? You need some professional help?
You had to follow a wire? Why don't you have cable plant and cross-connect documentation for your DC? I get it is their circuit, but don' t you identify endpoints of the cables in your tray?
IF you have network access to ping, why are you not monitoring?
I get government on top of hospital, PCI and normal business segregation makes for many silos, yet difficulty like this is an excellent opportunity to drive change from within. Or you can continue to throw your hands up, put your finger on your nose and say "not it".
Okay, three different comments. I'm going to reply to all three on this comment. Your comments come from a younger go-getter and that's great. But I have far more years behind me than in front of me. Also, there is no team to manage all this hardware, it's me. Just me. I don't have the luxury of time to do these wonderful things you suggest. Wish I did. Lastly, why do you assume I don't monitor my network? I have a feeling this is the first video on my channel that you've watched. God bless!
Oh, and to be more specific on not being able to ping the UC Daivs router,; it's because it is apparently misconfigured. My network monitoring software can ping everything on my network but their router.