HP’s ProLiant DL120 G5 SATA Rack Server


 
Thread Tools Search this Thread
Operating Systems HP-UX HP Server News and Podcasts RSS HP’s ProLiant DL120 G5 SATA Rack Server
# 1  
Old 09-09-2008
HP’s ProLiant DL120 G5 SATA Rack Server

Continually looking for ways to save money without sacrificing performance? Hear how the ProLiant DL120 G5 SATA Rack Server delivers the latest in performance at an affordable cost

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

3 More Discussions You Might Find Interesting

1. Hardware

Connect SATA Laptop HardDrive to Desktop SATA Slots

Hello everybody, I need to connect a laptop 2.5 SATA hard drive to a Desktop board (which uses 3.5' SATA hard drives). I've tried the connectors and they fit excellent in the 2.5 SATA connectors. The problem is that the laptop hard drive uses 5v and the PC's power source sends 12v. So, my... (4 Replies)
Discussion started by: Zykl0n-B
4 Replies

2. UNIX for Advanced & Expert Users

trying to setup a sata drive using a sata to scsi adaptor

trying to setup a sata drive using a sata to scsi adaptor I have a sata 1TB Deskstar that I had setup before and during shipment from a facilty to another, the disk failed. The handling was not great, lots of throwing boxes, etc. I have a new disk from Hitachi (thankyou Hitachi) anyway, I don't... (1 Reply)
Discussion started by: mndavies
1 Replies

3. Red Hat

Installation problem in HP Proliant DL-380 G5 server

Dear Sir, I have one HP Proliant DL-380 G5 Server, i tried to install Redhat Enterprise Verison 4, when i am trying to install the linux operating system it is coming one error message your hard disk not found, we are using Serial Scsi harddisk 146 GB, array controller is p400. i would... (1 Reply)
Discussion started by: sadiquep
1 Replies
Login or Register to Ask a Question
DUMP_FTS(8)							OpenIB Diagnostics						       DUMP_FTS(8)

NAME
DUMP_FTS - dump InfiniBand forwarding tables SYNOPSIS
dump_fts [options] [<startlid> [<endlid>]] DESCRIPTION
dump_fts is similar to ibroute but dumps tables for every switch found in an ibnetdiscover scan of the subnet. The dump file format is compatible with loading into OpenSM using the -R file -U /path/to/dump-file syntax. OPTIONS
-a, --all show all lids in range, even invalid entries -n, --no_dests do not try to resolve destinations -M, --Multicast show multicast forwarding tables In this case, the range parameters are specifying the mlid range. Port Selection flags -C, --Ca <ca_name> use the specified ca_name. -P, --Port <ca_port> use the specified ca_port. Local port Selection Multiple port/Multiple CA support: when no IB device or port is specified (see the "local umad parameters" below), the libibumad library selects the port to use by the following criteria: 1. the first port that is ACTIVE. 2. if not found, the first port that is UP (physical link up). If a port and/or CA name is specified, the libibumad library attempts to fulfill the user request, and will fail if it is not possible. For example: ibaddr # use the first port (criteria #1 above) ibaddr -C mthca1 # pick the best port from "mthca1" only. ibaddr -P 2 # use the second (active/up) port from the first available IB device. ibaddr -C mthca0 -P 2 # use the specified port only. Debugging flags -d raise the IB debugging level. May be used several times (-ddd or -d -d -d). -e show send and receive errors (timeouts and others) -h, --help show the usage message -v, --verbose increase the application verbosity level. May be used several times (-vv or -v -v -v) -V, --version show the version info. Configuration flags -t, --timeout <timeout_ms> override the default timeout for the solicited mads. -y, --m_key <key> use the specified M_key for requests. If non-numeric value (like 'x') is specified then a value will be prompted for. --node-name-map <node-name-map> Specify a node name map. This file maps GUIDs to more user friendly names. See FILES section. --config, -z <config_file> Specify alternate config file. Default: /etc/infiniband-diags/ibdiag.conf FILES
CONFIG FILE /etc/infiniband-diags/ibdiag.conf A global config file is provided to set some of the common options for all tools. See supplied config file for details. NODE NAME MAP FILE FORMAT The node name map is used to specify user friendly names for nodes in the output. GUIDs are used to perform the lookup. This functionality is provided by the opensm-libs package. See opensm(8) for the file location for your installation. Generically: # comment <guid> "<name>" Example: # IB1 # Line cards 0x0008f104003f125c "IB1 (Rack 11 slot 1 ) ISR9288/ISR9096 Voltaire sLB-24D" 0x0008f104003f125d "IB1 (Rack 11 slot 1 ) ISR9288/ISR9096 Voltaire sLB-24D" 0x0008f104003f10d2 "IB1 (Rack 11 slot 2 ) ISR9288/ISR9096 Voltaire sLB-24D" 0x0008f104003f10d3 "IB1 (Rack 11 slot 2 ) ISR9288/ISR9096 Voltaire sLB-24D" 0x0008f104003f10bf "IB1 (Rack 11 slot 12 ) ISR9288/ISR9096 Voltaire sLB-24D" # Spines 0x0008f10400400e2d "IB1 (Rack 11 spine 1 ) ISR9288 Voltaire sFB-12D" 0x0008f10400400e2e "IB1 (Rack 11 spine 1 ) ISR9288 Voltaire sFB-12D" 0x0008f10400400e2f "IB1 (Rack 11 spine 1 ) ISR9288 Voltaire sFB-12D" 0x0008f10400400e31 "IB1 (Rack 11 spine 2 ) ISR9288 Voltaire sFB-12D" 0x0008f10400400e32 "IB1 (Rack 11 spine 2 ) ISR9288 Voltaire sFB-12D" # GUID Node Name 0x0008f10400411a08 "SW1 (Rack 3) ISR9024 Voltaire 9024D" 0x0008f10400411a28 "SW2 (Rack 3) ISR9024 Voltaire 9024D" 0x0008f10400411a34 "SW3 (Rack 3) ISR9024 Voltaire 9024D" 0x0008f104004119d0 "SW4 (Rack 3) ISR9024 Voltaire 9024D" SEE ALSO
dump_lfts(8), dump_mfts(8), ibroute(8), ibswitches(8), opensm(8) AUTHORS
Ira Weiny < ira.weiny@intel.com > DUMP_FTS(8)