- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: How much hardware - a sysadmin should know ?
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-01-2000 04:28 PM
тАО11-01-2000 04:28 PM
Also What is the difference between a sysadmin adn HP-Engineer.
Waiting curiously for your answers.
Thanks,
.......Madhu
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-01-2000 05:38 PM
тАО11-01-2000 05:38 PM
Re: How much hardware - a sysadmin should know ?
IMHO :
1. Ideally, the more hardware knowledge a sysadmin has the better. Minimally, I think one needs to be comfortable with 'ioscan' and be able to relate its output to physical slots, cables, device files, and the priority of devices on a SCSI bus. A basic modem knowledge never hurts. These things become very important if you are configuring and managing MC/ServiceGuard clusters.
2. The distinction between a 'sysadmin' and an 'engineer' blurs when both become well-rounded in software and hardware. A sysadmin focuses on software whereas an engineer focuses on hardware. A sysadmin writes scripts and configures hardware with software tools. Obviously this includes constructing and maintaining filesystems, swapspace, networks, etc. A sysadmin monitors performance and understands how to tune a system for performance. A sysadmin uses and leverages hardware monitoring and diagnostic tools like EMS, Predictive Support, and STM to track the health of the hardware and (automatically or otherwise) alert the engineer of a need to replace a failing or defunct component.
An engineer installs and/or replaces hardware and generally performs the updates of processor and disk firmware. An engineer is knowledgeable running and interpreting the output of proprietary hardware diagnostic tools in order to isolate exactly which component is faulty. Classicly, an engineer does not write code (scripts, etc.); tune systems performance; nor configure filesystems, swapspace, networks, etc.
The best sysadmins and the best engineers are keen observers, have good deductive skills, and thrive on problem solving. The best sysadmins are "junior engineers"; the best engineers are "junior sysadmins". The best of either are both.
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-01-2000 05:42 PM
тАО11-01-2000 05:42 PM
Re: How much hardware - a sysadmin should know ?
In a large environment, multiple OS environment this knowlege will be much less as the administrative tasks increase in both quantity and complexity.
In most cases a sys-admin should know the basic components, how they work, and how to tell if critical components are going bad. I.E disk drives, memory, etc... but there is no set answer.
An HP engineer usually has a degree, and/or a certain amount of tested troubleshooting skills on both HP Hardware and HP-UX. A sys-admin can know as much, but not very often.
Hope it helps.
Shannon
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-02-2000 06:56 AM
тАО11-02-2000 06:56 AM
Re: How much hardware - a sysadmin should know ?
Understanding I/O layout & SCSI pathing.
Some understanding about different SCSI bus characteristics.
Some understanding of modems.
Familiarity with Hot-swap devices and replacements.
Some knowledge of CPU & memory card/board configurations.
Some understanding of terminal servers.
Basic understanding of disk technologies (RAID, disk array, ESA, etc.)
Basic understanding of networking hardware (NIC, hub, switch, router).
Basic understanding of printers & print drivers (Perhaps my least faorite of all admin activities, but unfortunately necessary).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-02-2000 07:57 AM
тАО11-02-2000 07:57 AM
Re: How much hardware - a sysadmin should know ?
Also, if upgrades are in the works, look at the specs between the new and old. See how different stats are available and see how different capacities are available between systems. There is a lot to know but start with your own environment first.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-02-2000 08:07 AM
тАО11-02-2000 08:07 AM
Re: How much hardware - a sysadmin should know ?
To my mind "Your own environment" also includes the lumpy bits.
I believe that you should be able to deal with almost every problem associated with your servers.
What do you do on a 24/7 production server and the network card dies
-Wait until a Hp engineer can get to you (4hours to my company can be ?400,000 in sales)
- no you down the devel server and borrow its card - back up in 20 min max.
Also by knowing whats inside helps on the software side.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-02-2000 08:09 AM
тАО11-02-2000 08:09 AM
Re: How much hardware - a sysadmin should know ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-02-2000 08:20 AM
тАО11-02-2000 08:20 AM
Re: How much hardware - a sysadmin should know ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-02-2000 09:13 AM
тАО11-02-2000 09:13 AM
SolutionA further comment. On mission critical systems one mirrors, uses intelligent RAID, implements dual LANS, and implements high-availability solutions like MC/ServiceGuard, etc.
To a very large extent this obviates the need to scramble to steal hardware from another server in the event of a crisis.
We pay HP support for support. If they install hardware we purchase, or replace a defective component, and something goes awry, then it's not money out of our pocket.
As Alan noted, a basic understanding of the hardware technologies and mechanics is an asset for everyone. To me, that's the important part. I'll leave the actual maintenance to the engineer for the reasons I've given above.
Regards to all, Jim.
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-02-2000 12:47 PM
тАО11-02-2000 12:47 PM
Re: How much hardware - a sysadmin should know ?
I'm both a systems administrator with more than a couple of decades experience and a hardware engineer with two years formal experience. What HP would call a CE or a customer engineer.
A systems administrator should first be good at his primary job, keeping the box running day in and day out. This is what they are being paid for.
Second a good systems administrator should know their hardware well enough to do several things: diagnose a problem to at least the "obvious" level, pull the board, replace the board, test the result. They should also know the protocols used by their box: types of SCSI interfaces and their differences, modems, tape drives and tapes, basic networking protocols such as TCP/IP, routers and bridges, the seven layer model and where things fit in there etc, power, what their box requires, what a UPS is, how to maintain one, switch to bypass mode and back, the difference between 110, 208 and 480 and how to be a jackleg electrician.
In other words, when a professional of any stripe sticks their nose in your room, stick to them like white on rice, learn everything you can from them, do the dirty tasks alongside them, stare over their shoulders and hold the flashlight for them, bring them coffee, everything you can in order to learn, learn, learn.
After more than 2 decades I still stick to everyone who steps into the computer room, sometimes to prevent screw ups and sometimes to learn from them like I was a green novice.
The more you know, the more you're worth.