This page contains a Flash digital edition of a book.

How to Save Money with Troubleshooting Devices Looking for Trouble By Andrew Lane, European Marketing Manager, Ideal Industries Networks

With more and more companies being heavily reliant on Ethernet, network professionals are tasked with minimising downtime by identifying and repairing problems as quickly as possible. Andrew Lane discusses the benefits that network troubleshooting devices

offer, and explains the key things to look out for when selecting a product.

Ethernet protocol has been widely used in office environments for a number of years, and has more recently found its way into industrial and public sector applications. Ethernet is the dominant protocol in the workplace; it connects all kinds of equipment, from PCs to phones, machinery, security and building management systems. A significant number of businesses

and organisations are therefore completely reliant on their Ethernet networks. Slow performance and network faults have a direct impact on efficiency and productivity, in turn affecting the bottom line. Of course, non-productive

downtime has always been an issue for any business, but as economically challenging times continue, it has the potential to be even more damaging. For today’s office worker, network failures can make it impossible to work. For a factory manager, they can be catastrophic and can shut production down. In each of these situations, network issues will cost the business money. As Ethernet is a key element of

modern security systems, which might include IP CCTV cameras and access control, network failures can have other critical implications too.

IT happens

Any user of Ethernet has to accept that there will inevitably be network issues from time to time, especially when 100MB Ethernet is being used, which requires good connections and cabling. In terms of the potential issues,

devices might fail to connect to other devices. There can be IP address conflicts, PoE and VoIP devices might not work properly, servers can go down and of course, the network can run slowly. PC users can also cause issues. For

example, someone might add a rogue device like a printer to the network without the IT administrator’s knowledge, or an employee might be slowing the system down by downloading a large amount of data. Passive cabling problems will always

pose a big risk. Two very common problems affecting data transmissions

32 NETCOMMS europe Volume II, Issue 1 2011

Today’s troubleshooting devices should have ‘touch and test’ capabilities, and the user shouldn’t need to consult a lengthy instruction manual.

are damaged cables and disorganised, untidy patch panels. When such issues arise, they are

a matter of urgency. Since there is such a heavy reliance on Ethernet, network professionals will find themselves under a lot of pressure from their customers to resolve problems immediately. Since network issues will invariably

occur, and network professionals will often be called in to identify and rectify them, it makes sound commercial sense for them to invest in a purpose-designed, troubleshooting tool to save time and money. With higher productivity, higher

profitability and customer satisfaction achieved, this is a relatively small outlay. In an era when businesses need to work as efficiently as possible, it is a smart investment that will pay for itself many times over.

Free aware

Some network professionals choose to rely on freeware or software in order to identify network problems. However, these are generally designed for network monitoring and their capabilities are limited, particularly in troubleshooting. For example, PC software cannot detect hardware or PoE devices, and since there’s only one Ethernet port on a laptop, inline testing is not an option. Furthermore, there is no fibre capability and critically, cable faults cannot be traced. If you rely on software based solutions, you will always need a secondary device or have to call in outside contractors, costing even more time and money. Freeware only works if the internet

works, and it requires the use of a laptop. Testing a network with a laptop is a laborious, cumbersome task, and

Page 1  |  Page 2  |  Page 3  |  Page 4  |  Page 5  |  Page 6  |  Page 7  |  Page 8  |  Page 9  |  Page 10  |  Page 11  |  Page 12  |  Page 13  |  Page 14  |  Page 15  |  Page 16  |  Page 17  |  Page 18  |  Page 19  |  Page 20  |  Page 21  |  Page 22  |  Page 23  |  Page 24  |  Page 25  |  Page 26  |  Page 27  |  Page 28  |  Page 29  |  Page 30  |  Page 31  |  Page 32  |  Page 33  |  Page 34  |  Page 35  |  Page 36  |  Page 37  |  Page 38  |  Page 39  |  Page 40  |  Page 41  |  Page 42  |  Page 43  |  Page 44  |  Page 45  |  Page 46  |  Page 47  |  Page 48  |  Page 49  |  Page 50  |  Page 51  |  Page 52  |  Page 53  |  Page 54  |  Page 55  |  Page 56  |  Page 57  |  Page 58  |  Page 59  |  Page 60