Here at $WORK we had something go out on our network. I say something as the keepers of that portion of the LAN/WAN just said they had an issue. Anyway my portion of the LAN/WAN where my servers reside had issues. I have remote servers that are connected back to my building over a VPN tunnel. When this outage occurred people in my remote offices could not connect to their server (which is at their site). The outage was for two hours. One of my servers was having issues as the load average of that server was steadily climbing (it got to 59 when I was notified). I figured that when the outage occurred that server was in the middle of sending a remote print job and when the connection went down the print job did not die and was chewing up process cycles.
What bewildered me was why my users could not connect to that server. They are on the same physical switch as the server so I figured they just could not get off site. My users connect via ssh and use a static ip to point to when they connect. My question is this. In the normal Ethernet/TCP/IP protocol wouldn't the switch direct the packets to the port where the destination IP is connected. All of my users machines have routes to the default router at their site which connects to the switch that the users and my servers connect to. So for sake of explanation. UsersPC(192.168.1.10) is routed to router(192.168.1.1) and tries to ssh to server(192.168.1.11). The netmask is 255.255.254.0 of the PC and Server. If I sever the connection from 192.168.1.1 out to the WAN should that have any effect on the users from connecting to 192.168.1.11? I understand that I will have DNS issues since most of my users point to a DNS server in my building (across the VPN) but if we are not using a DNS call (using the IP address directly) there should not be any lag because of no way to connect to DNS? I understand I should be using DNS but suffice it to say it is a long story as to why it is this way. We are taking steps to put the DNS at the site to relieve some traffic. Also my servers are old end of life SCO 5.0.6 boxes that are holding a legacy app that is in the process of being replaced (another long project and equally long story) so I am trying to make the best of a bad scenario. SCO is very finicky with network traffic. Shouldn't the switch send the packets directly to the port that my server is connected to? If this is going to be a long discussion we can discuss off list or just point me to a good document that explains this I found this link https://www.safaribooksonline.com/library/view/ethernet-switches/9781449367299/ch01.html but it does not discuss the setup when you have a router in the mix. Thanks in Advance. -- John J. Boris, Sr.
_______________________________________________ Tech mailing list Tech@lists.lopsa.org https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
