10GB Ethernet. It is here, it is blazing fast and it is probably expensive right now. But its going to get more popular in use and its adoption will drive the price down. I don't know how many homes might decide to move to it but it would be a huge upgrade cost to do so. But if you are running something like a Home studio for video production then it may be something that is needed. Even the hardware is starting to be forward thinking. The Buffalo TeraStation TS5410DN has a built in 10GB port on the back. Lots of NAS drives are starting to put them in. In this Video review by David Gewirtz just a month ago there was 6 of them and each one talked about 10GB Ethernet.
https://www.youtube.com/watch?v=5MArqG6Aouw
Data Centers have have been using this standard since 2007. Of course if you have Gigabit Ethernet and want to upgrade you are going to have to buy new switches and hardware that can support 10GB Ethernet. Plus you need to have Cat 6 Ethernet cable or Fiber cable to run it through your network. You can run it up to 100m (330ft) After that signal loss will occur. 10GB is the only standard that has come out that does not offer the option of Half duplex communication. The standard reads Full Duplex only. Would a home user ever use this standard? Sure they would, if they were in video or music production you will take all the speed you can get! Plus having 10GB to stream from your NAS box to your internet to upload, things are going to get done pretty quick! If you are a cloud provider for customers or Run a small data backup company you will want to have your backbone at 10GB speeds if at all possible to make sure that data will get to where it needs to be.
10GB Ethernet is almost here and its time to start thinking about putting budgets against it to make sure you have the speeds you need to transfer the ever increasing amount of data coming out of your network. This is a developing topic and I will discuss it more as it starts to make a larger headway into Mainstream networking. As always feel free to leave me feed back about my topics.
This is my technical blog. Here I will discuss current technologies as well as insights into working in the Information Technology field. I have 20 years of experience in my career and I think some of that knowledge will help others in the field.
Showing posts with label CAT5 cable. Show all posts
Showing posts with label CAT5 cable. Show all posts
Wednesday, July 12, 2017
Saturday, March 18, 2017
When buying networking equipment cheap is not always the way to go
There is an old saying "Cheap is not always good, and good is not always cheap" This holds very true when looking at networking products. A lot of these products send your data through your network and get it to the computers for the users to see and use. If you purchase a product that turns out to be poorly designed, you will find your self with a lot of angry calls at the help desk and wonder why. I have seen cases where the users do not consult their help desk and they go out and buy a piece of equipment and buy the cheapest one they can find. Then they hook it up and have problems with connectivity and call the help desk to find out why. Those routers that are 39.99, there is a reason they are that price. They are not good. They will not last, or they have limited features, or they break down every other day. I had a case where a company who I worked for did this very thing. We had provided them with a medium grade business router. It had a dual WAN connection so you could have 2 internet providers for redundancy and it had some decent features on it to manage the device even from a remote location. It was a major name brand and was about 4 years old. It had come time to replace the device but before we were able to it stopped working leaving the users unable to connect to the internet or their cloud to do work. So rather than call the help desk and let us work with them to try to resolve the issue they went to the store and bought a 39 dollar consumer grade router. I don't even remember what the name was, it was a brand I had never even heard of. So they brought it back to the office and plugged it in and put the old one off to the side. Now not only did they run it without changing any configuration leaving it vulnerable to be hacked into, they did not have any idea that we had special settings in the old device telling it how to send data to specific devices that needed to be configured in a special way. Now keep in mind, at this location we have a monitor tool connected remotely that pings their internet connection and reports if the ping stops working. So in the morning I was alerted the site went down and saw it drop out. I reached out to the office to inquire if they were having issues and offer support but the person had already left to go to the store to buy the device. It was a small office with 3 people and 2 of them were out that day. So about an hour goes by and I see the monitor tell me they are back online, so I figure ok they had an internet issue from their provider and the provider fixed it. Great! Nothing to worry about....
What followed was half a day troubleshooting and trying to get things working with that junk device the users purchased! I almost immediately found out that they had switched out the device and because the IP scheme was different, printers that went by IP address could not find the network. The old setup had 192.168.0.X and the new device had the way too popular 192.168.1.X So I had to go in and change that setting to fix that problem. Then I had to adjust the DHCP to go from 100 to 200 not 2 to 150.... Those were easy fixes and after changing the WiFi built in to match what they used to have with the same password (which was pretty secure with numbers and symbols) things were looking up. Then I came to the part to add in firewall rules to forward ports to their respective devices... If you never did this basically you tell the router, if you see traffic coming from a port named 1088 for example: send that data to this address, xxx.xxx.xxx.xxx. That tells the router to take the traffic and send it to a specific device that needs data from the specific port address. This would have maybe worked if the developer working on the software for this router was not a complete bone head, who never worked with computers before... The interface to do this was mind boggling and even after I figured out what the hell they were trying to convey on the menus, the programming I put in to allow this did not work. So now the remote IP phones that were at worker's homes would not work. They had an IP based phone system and needed the workers to be able to work from home so we had implemented a PBX that would allow this. Sadly this would never work due to the poorly designed router, and we needed it sooner rather than later, as it was December in the North east and this area was prone to 20 inch snow storms... Now at this point, 3 hours into the call your ready to ask the user, why the **** did you go and buy this piece of **** without consulting me first???? But you cannot do that it is frowned upon and will cause tension on the other side of the phone call. Instead you must mute your phone take 3 deep breaths and then explain to them that they must hobble along today until you can overnight them the correct router they need to have their network run at optimal performance. You must also pray that there is a unit in stock in your storage and hope you can configure it and get it out the door to shipping by 3 pm... Luckily for this office, I did have a new unit in stock and was able to put all the settings in they needed, and was able to apply the latest firmware to give the device all the best security and feature patches the device manufacturer had. The only downside was the device was just a firewall/router without WiFi so they would have no WiFi as the WiFi units that tie together were not in stock and back ordered. The users were fine with this and said WiFi is not a huge deal and they could work without it for a few days. The silver lining on this was that when they got the new router that I sent over, we found a huge wiring issue that was causing network drops and the old router was not smart enough to tell them about it, but the new one did detect it in a rather off the wall way and thanks to its error logs I was able to find out this wire issue and have a tech go out and fix it. Now you might ask, "OK they spent 39.99 on the crap consumer grade router, how much did yours cost, 500 dollars? 750 dollars? 1000 dollars? Is it a large brand name that is huge and popular? "
No, the router we sent out is a Mid grade enterprise device and costs roughly 300 bucks with a 2 year warranty, that also includes a cloud log in to manage the device and there is no additional cost for that feature. So we didn't go top of the line for this new device but we did not go cheap either. Our idea has always been to get the users good hardware that will last, and suite the needs of the office without being too expensive and try to be future proof at the same time. The device we gave them fits that bill to a T and the company that makes it has been updating its firmware to add more features to give them more usability. These devices have been put into 95 percent of our locations we help manage and we don't have too many break down. We always try to make sure the locations know to contact us before they go and buy something so we can get them the right equipment. Spending money for a good product even if it is more money is always better in the long run when it comes to IT and hardware. You will improve the reliability of the network for users, and cut down on user frustration and wasted time calling the Help desk to fix an issue. So remember, Cheap is not always good and good is not always cheap.
What followed was half a day troubleshooting and trying to get things working with that junk device the users purchased! I almost immediately found out that they had switched out the device and because the IP scheme was different, printers that went by IP address could not find the network. The old setup had 192.168.0.X and the new device had the way too popular 192.168.1.X So I had to go in and change that setting to fix that problem. Then I had to adjust the DHCP to go from 100 to 200 not 2 to 150.... Those were easy fixes and after changing the WiFi built in to match what they used to have with the same password (which was pretty secure with numbers and symbols) things were looking up. Then I came to the part to add in firewall rules to forward ports to their respective devices... If you never did this basically you tell the router, if you see traffic coming from a port named 1088 for example: send that data to this address, xxx.xxx.xxx.xxx. That tells the router to take the traffic and send it to a specific device that needs data from the specific port address. This would have maybe worked if the developer working on the software for this router was not a complete bone head, who never worked with computers before... The interface to do this was mind boggling and even after I figured out what the hell they were trying to convey on the menus, the programming I put in to allow this did not work. So now the remote IP phones that were at worker's homes would not work. They had an IP based phone system and needed the workers to be able to work from home so we had implemented a PBX that would allow this. Sadly this would never work due to the poorly designed router, and we needed it sooner rather than later, as it was December in the North east and this area was prone to 20 inch snow storms... Now at this point, 3 hours into the call your ready to ask the user, why the **** did you go and buy this piece of **** without consulting me first???? But you cannot do that it is frowned upon and will cause tension on the other side of the phone call. Instead you must mute your phone take 3 deep breaths and then explain to them that they must hobble along today until you can overnight them the correct router they need to have their network run at optimal performance. You must also pray that there is a unit in stock in your storage and hope you can configure it and get it out the door to shipping by 3 pm... Luckily for this office, I did have a new unit in stock and was able to put all the settings in they needed, and was able to apply the latest firmware to give the device all the best security and feature patches the device manufacturer had. The only downside was the device was just a firewall/router without WiFi so they would have no WiFi as the WiFi units that tie together were not in stock and back ordered. The users were fine with this and said WiFi is not a huge deal and they could work without it for a few days. The silver lining on this was that when they got the new router that I sent over, we found a huge wiring issue that was causing network drops and the old router was not smart enough to tell them about it, but the new one did detect it in a rather off the wall way and thanks to its error logs I was able to find out this wire issue and have a tech go out and fix it. Now you might ask, "OK they spent 39.99 on the crap consumer grade router, how much did yours cost, 500 dollars? 750 dollars? 1000 dollars? Is it a large brand name that is huge and popular? "
No, the router we sent out is a Mid grade enterprise device and costs roughly 300 bucks with a 2 year warranty, that also includes a cloud log in to manage the device and there is no additional cost for that feature. So we didn't go top of the line for this new device but we did not go cheap either. Our idea has always been to get the users good hardware that will last, and suite the needs of the office without being too expensive and try to be future proof at the same time. The device we gave them fits that bill to a T and the company that makes it has been updating its firmware to add more features to give them more usability. These devices have been put into 95 percent of our locations we help manage and we don't have too many break down. We always try to make sure the locations know to contact us before they go and buy something so we can get them the right equipment. Spending money for a good product even if it is more money is always better in the long run when it comes to IT and hardware. You will improve the reliability of the network for users, and cut down on user frustration and wasted time calling the Help desk to fix an issue. So remember, Cheap is not always good and good is not always cheap.
Friday, July 3, 2015
A look at what being in IT is like
A lot of times I get asked what is it like to be an IT person? I can sum it up in one word... EXHAUSTING
There is always something new to learn. When I started the company I am at currently, in my first week I had to learn 7 different applications. AT warp speed... a call would come in, this application is not working right.... Ok, what is the application, how do I use it so I know how to tell the end user how to use it or what they are doing wrong. Then I have to learn this other application that helps me do MY job. It was a crazy time.
We as IT people don't get the luxury of taking a weekend to sit down with the manual and read about a new program and figure out how to make it do what we want. we usually learn it during a call with an end user, they need it to run right now and its not a common application like your standard say... photo editor program. When this happens you have to rely on you knowledge of how other applications work and how they are laid out. You have to remember the common things that all applications have that you have seen before, like an options menu, or that the Print command is always in the file menu.
Then on top of learning the 12 new versions of the software that you support that just got released yesterday, you have to be able to rapidly figure out what issue is happening as the next call comes in and be able to use your tools and skills to figure out why a network connection went down. Now there is no internet... and people cant get to their files.... this is a situation that can get even the calmest of managers seeing red and taking swigs of Maalox. If it were still 1999 the internet being down would not be a big deal, the users would have their applications in front of them on their local computer and they could get other things done and calmly wait for the internet to come back up to check their emails. Not so much anymore... Business happens at the speed of the internet and the internet has everything connected. If the internet connection goes down business stops. Money stops flowing. You get that call, you have to get the internet back up if you can or be able to work with the local provider to get the issue fixed. Now you have to be able to quickly troubleshoot from simple to more complex and make sure if its just one user or all the users. Again you have to use all the experience of doing this before to try to determine this quickly so that you can get to a resolution fast and move on to the next call. Now you find out it is the provider and that its out of your hands. Now you have to make sure to convey to the internet provider that the connection needs to be restored and that it needs to happen quickly, and then you have to tell the manager the news and convey that it will be ok and this happens from time to time and it will all get resolved quickly. That brings up another skill you need, the ability to put this into words that anyone can under stand. You cannot tell the finance manager that the T1 circuit is in fail over mode and there is a fiber splice. He will not know what that means and not know what the situation is. You have to be able to tell him that there is a connection issue but it will be resolved but there is physical damage that will have to be repaired by the provider and a crew will be out working on it. You have to be able to explain technical things to a non technical person. That can be hard to master. You are around other It people all day you throw the terms back and fourth constantly all day, "fiber splice," "CAT 5 Cable" Defragment the drive. Then you talk to a non It person and forget your not in the same field. You have to change your explanation on the fly as to what is going on. I see IT people all the time who are good but have trouble putting it into words that someone else can understand.
Its also good to actually learn some of the business aspects of the company you work for. It makes it easier to understand why things are done the way they are in the office. If you learn how the A/P department process payments to go out, you learn more and you may even find ways for them to do it differently that is better than whats done today. Learning some non IT skills is also good. Management love having an IT person that is well rounded. They will feel more confident in your ability and know you have a desire to know your company and learn new things. It can lead to better opportunities and even a little more pay. Which is always a plus.
So the next time you see your IT person and they have their head down and they are staring at their screen, they are not reading some non work thing just goofing off like you think, they are learning the new financial application which is rolling out next week and trying to figure out how to get the California office back online all while trying to explain to the CFO why the cloud costs so much if there is no physical server here in the office!
There is always something new to learn. When I started the company I am at currently, in my first week I had to learn 7 different applications. AT warp speed... a call would come in, this application is not working right.... Ok, what is the application, how do I use it so I know how to tell the end user how to use it or what they are doing wrong. Then I have to learn this other application that helps me do MY job. It was a crazy time.
We as IT people don't get the luxury of taking a weekend to sit down with the manual and read about a new program and figure out how to make it do what we want. we usually learn it during a call with an end user, they need it to run right now and its not a common application like your standard say... photo editor program. When this happens you have to rely on you knowledge of how other applications work and how they are laid out. You have to remember the common things that all applications have that you have seen before, like an options menu, or that the Print command is always in the file menu.
Then on top of learning the 12 new versions of the software that you support that just got released yesterday, you have to be able to rapidly figure out what issue is happening as the next call comes in and be able to use your tools and skills to figure out why a network connection went down. Now there is no internet... and people cant get to their files.... this is a situation that can get even the calmest of managers seeing red and taking swigs of Maalox. If it were still 1999 the internet being down would not be a big deal, the users would have their applications in front of them on their local computer and they could get other things done and calmly wait for the internet to come back up to check their emails. Not so much anymore... Business happens at the speed of the internet and the internet has everything connected. If the internet connection goes down business stops. Money stops flowing. You get that call, you have to get the internet back up if you can or be able to work with the local provider to get the issue fixed. Now you have to be able to quickly troubleshoot from simple to more complex and make sure if its just one user or all the users. Again you have to use all the experience of doing this before to try to determine this quickly so that you can get to a resolution fast and move on to the next call. Now you find out it is the provider and that its out of your hands. Now you have to make sure to convey to the internet provider that the connection needs to be restored and that it needs to happen quickly, and then you have to tell the manager the news and convey that it will be ok and this happens from time to time and it will all get resolved quickly. That brings up another skill you need, the ability to put this into words that anyone can under stand. You cannot tell the finance manager that the T1 circuit is in fail over mode and there is a fiber splice. He will not know what that means and not know what the situation is. You have to be able to tell him that there is a connection issue but it will be resolved but there is physical damage that will have to be repaired by the provider and a crew will be out working on it. You have to be able to explain technical things to a non technical person. That can be hard to master. You are around other It people all day you throw the terms back and fourth constantly all day, "fiber splice," "CAT 5 Cable" Defragment the drive. Then you talk to a non It person and forget your not in the same field. You have to change your explanation on the fly as to what is going on. I see IT people all the time who are good but have trouble putting it into words that someone else can understand.
Its also good to actually learn some of the business aspects of the company you work for. It makes it easier to understand why things are done the way they are in the office. If you learn how the A/P department process payments to go out, you learn more and you may even find ways for them to do it differently that is better than whats done today. Learning some non IT skills is also good. Management love having an IT person that is well rounded. They will feel more confident in your ability and know you have a desire to know your company and learn new things. It can lead to better opportunities and even a little more pay. Which is always a plus.
So the next time you see your IT person and they have their head down and they are staring at their screen, they are not reading some non work thing just goofing off like you think, they are learning the new financial application which is rolling out next week and trying to figure out how to get the California office back online all while trying to explain to the CFO why the cloud costs so much if there is no physical server here in the office!
Labels:
application,
CAT5 cable,
defragment,
exhausting,
Internet,
IT Person,
Maalox,
T1
Subscribe to:
Posts (Atom)