Computer network problems can cause network software problems and disruptions to business continuity. The scale of this disturbance can vary depending on the source of the disturbance and the consequences it has on your infrastructure network. Network problems can cause downtime (how come the language …?) And this downtime can vary depending on how well you plan planning contingencies. Good management of your network system files can help you minimize downtime and make it easier for you to troubleshoot your network problems.
There are not a few types of network problems that can cause disruption to a computer, disruption of local networks, to disruptions to the global network of business connections in your corporate.
This is a common network problem that you encounter with the impact of network cable breakdowns that can affect the performance of a computer on the network because of the breakup of your patch cable because it was bitten by a mouse; dominant network problems in one building block because the cable breaks between switches (uplink cable); or even dominant in the majority of computers in your LAN network due to failure of backbone cable.
The dominant network problem on a computer may not be a big problem except that of the general’s computer or your director. But the dominant network problems in your LAN network in bulk or even globally dominant in your corporate business can create a cold sweat. In a large-scale network infrastructure system, a redundancy system must be implemented. So that if a failure occurs in one network path it will not result in network failure in long periods.
In a residential multi switch network, the Spanning Tree Protocol (STP) must be enabled and tuned manually. STP is a service that allows the switch-2 network and bridge-2 of your LAN to be connected to each other in a redundant manner with a mechanism that can prevent bridging loops. The bridging loop is a data packet that is circling in the network looking for addresses to exhaustion and the end of koid. This bridging loop can cause your network traffic to crash or be called broadcast storm.
The scale of the disruption of the impact of network device failures can also vary, from merely a computer because of the failure of the NIC – LAN card; number of computers due to switch failure; or even wide-scale causes of failure on central switches that connect server networks. For lan card failures between computers it can be replaced with your backup network card.
So what if the network failure impacts damage to the switch? Your design regarding network redundancy will be very helpful in securing your network failure. The need for load balancing and redundancy must be assessed for every need according to the use of redundancy links; router device; switches and multi-homed hosts that have critical properties. The purpose of this redundancy system is to ensure the availability of services where there is no single point of failure.
Let’s look at the picture above regarding the system of redundancy.
Switch redundancy; If a problem occurs due to a failure on switch A, Switch B can still be useful for supplying links to the server and also to the two channel switches and links to the WAN. This type of network problem will not affect the server down system.
Router redundancy will create a WAN link backup when problems occur between routers. For example, between routers that connect your frame relay network to other offices, there are still backup links on the other router.
Link redundancy – will backup the link if there is a network problem with the link being disconnected to the server or to the switch.
We can apply this redundancy system to the previous scenario model that connects both the Mining and HR offices with unique two underground Cat5e UTP cables as redundancy links. Make sure that both of these redundancy cables are not connected to the same switch, because if there is a failure on the switch it will be useless.
For internet link redundancy, the router is actually already in the market a little with two or more WAN ports to the point that it doesn’t need two routers. This type of router is often for small medium offices where two WAN ports can failover – failback. So if the main link fails, it will failover to the backup link. Or you can also create two links load balancing, let’s say FVS336G Dual Wan Gigabit SSL VPN Firewall.
Although system failure is not the impact of network infrastructure failure, your users will still call you with the following questions: “Hello Agus … is there a network problem? I can’t access my email … or something like this “I can’t access the internet … or even a question from a radio operator” Hello Agus … how come I can’t access the folder President Director … why is that? ”
System failure can be caused by a problem with your DHCP server so that clients do not accept an IP address. Or it could be because there is a problem with your Directory Services system so that clients cannot log on to the network. Or it could be because there is a problem with registering names in your DNS system.
This type is also a network problem that is not due to physical network infrastructure failure, but your network system will be flooded with traffic from the influence of viruses that attack the system server and infect all computers in your network. The performance of your network system will be the slowest even to say collapsed. What you can do with this virus attack is to implement best practice security policy, your system defense must be very immune.
All kinds of network problems, you as a network and system administrator must be able to solve the problem. It doesn’t matter whether the problem is the failure of your network device; or your computer system problems; or an intruder that attacks your system infrastructure system. A good redundancy network design and a good management system is an obligation on a network scale that has a broad and complex nature.
VW Corporate Theme By VWThemes