Your SlideShare is downloading. ×
Sclends basic network troubleshooting
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Sclends basic network troubleshooting

138
views

Published on

Published in: Technology

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
138
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
7
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • Good morning. This is Rogan Hamby. It is April 2nd, 2013. I apologize in advance for the sound quality. I’m doing this in office during lunch and with the a lot of movement outside my door it is not ideal. Hopefully the clock tower won’t be too loud.
  • But why does it fail to do these?
  • Transcript

    • 1. Is Evergreen Slowing Down – Basic NetworkTroubleshootingRogan Hamby, June 13th 2013
    • 2. Is Evergreen slowing down?
    • 3. There could be several culprits.
    • 4. Staff Client Issues
    • 5. There are known memory leaks inthe staff client. These are beingactively addressed by thecommunity.
    • 6. If this is happening it probably isn’thappening the same at all stations.Reboot the troubled station.
    • 7. Network Issues
    • 8. From your local switch having fits toa router in Tennessee dying tosomeone in Atlanta doing a thirteenterabit backup we are at the mercyof the pipes inbetween.
    • 9. Usually these problems will growslowly. All machines will be affectedbut it may not seem like that at firstas some activities are more prone tointerruption.
    • 10. Staff facing patrons and thosefunctions moving large data frames(e.g. cataloging) will usually noticefirst because lost packets andlatency have the greatestperceivable impact.
    • 11. Now it’s important to look at yournetwork path. There are manycommon elements in the paths fromSCLENDS member libraries to thehosting facility but no universal onesexcept the last few.
    • 12. If you use ICMP or UDP based toolsbe aware of the false positives theycan give since they are oftenblocked.
    • 13. I recommend that you use TCPbased trace routes.
    • 14. Windows – Pingplotter Prohttp://www.pingplotter.com/pro/
    • 15. Linux – traceroute -T
    • 16. Mac – Path Analyzer ProUses protocol paths, not just hops.http://www.pathanalyzer.com/
    • 17. If the issue is on your local LAN oranywhere in SC and ongoing youneed to either address the issueinternally or with the State level e-rate board.
    • 18. If the issue is outside SC we can lookat trying to appeal for a remedy orsome kind of routing but we can’tguarantee results.
    • 19. If the issue is at the hosting facilitywe can fix the issues immediately.
    • 20. Standard Traceroute
    • 21. TCP Based Path
    • 22. So… what if everything so far looksclear?
    • 23. It’s a SERVER(s)!
    • 24. Our SetupLoad BalancerApp ServersProductionReplicationand ReportingDatabase Servers
    • 25. How can I tell which has just gone tomeet Werner Jacob?(warning: broad simplifications ahead)
    • 26. If it’s the DB servers then everythinggoes to heck starting with databaseretrieval and the errors will say ‘SQL’in them somewhere usually. But it’squick!
    • 27. If it’s only the replication one thenonly reports will be affectedincluding notices.
    • 28. App bricks – its very rare for all fourapp bricks to fail at once so usuallysome machines will do fine whileothers have issues or it appearsrandom.
    • 29. Example: When catalogers havetemplate issues, they may have lostthem on one brick but not others.
    • 30. When a brick crashes you willusually get errors referencingvarious PM files (perl modules) orspecific scripts.
    • 31. When it’s the load balancer –everything slows down painfully andeverything goes to heck. Eventuallystations will time out and errors willreflect that.
    • 32. Don’t jump to conclusions but theseexamples should give you someinsight into the kinds of things tolook for.
    • 33. Copy errors. Observe and report.Communicate on listserv. IRCchannel is also available specific toSCLENDS. Call Rogan in anemergency (he’s not always at hisdesk).

    ×