Powervault MD3060e - Revision history

Adj: /* Cabling */

2025-05-26T17:09:40Z

Cabling

← Older revision		Revision as of 17:09, 26 May 2025
Line 220:		Line 220:

	== Cabling ==		== Cabling ==
	Serial Attached SCSI (SAS) devices have 2 connections for host IO. Serial AT Attachement (SATA) devices have just one. SATA devices ''can'' be connected to a SAS connector and the single host IO connection will be used. In the MD3060e enclosure, the lower EMM is attached to the connectors the SATA drives use. The enclosure itself is attached to both. So, if using only SATA drives, make sure the server in question is actually attached to EMM 1, the lower one. ~~With~~ ~~SAS~~ ~~drives,~~ ~~either~~ EMM ~~works~~ ~~fine,~~ ~~but path redundancy is established by attaching~~ a ~~host~~ ~~(server)~~ to ~~both~~ ~~EMMs~~.		Serial Attached SCSI (SAS) devices have 2 connections for host IO. Serial AT Attachement (SATA) devices have just one. SATA devices ''can'' be connected to a SAS connector and the single host IO connection will be used. In the MD3060e enclosure, the lower EMM is attached to the connectors the SATA drives use. The enclosure itself is attached to both. So, if using only SATA drives, make sure the server in question is actually attached to EMM 1, the lower one. And a connection to EMM 0 will provide a second path for SAS drives.

Adj: /* Firmware updates */

2025-05-26T16:48:49Z

Firmware updates

← Older revision		Revision as of 16:48, 26 May 2025
Line 218:		Line 218:

	FLASH Programming complete - rebooting		FLASH Programming complete - rebooting

			== Cabling ==
			Serial Attached SCSI (SAS) devices have 2 connections for host IO. Serial AT Attachement (SATA) devices have just one. SATA devices ''can'' be connected to a SAS connector and the single host IO connection will be used. In the MD3060e enclosure, the lower EMM is attached to the connectors the SATA drives use. The enclosure itself is attached to both. So, if using only SATA drives, make sure the server in question is actually attached to EMM 1, the lower one. With SAS drives, either EMM works fine, but path redundancy is established by attaching a host (server) to both EMMs.

Adj: /* Firmware updates */

2025-05-24T01:38:18Z

Firmware updates

← Older revision		Revision as of 01:38, 24 May 2025
Line 138:		Line 138:


	<main>:c		<main>:'''c'''

	Entering Admin mode		Entering Admin mode
Line 163:		Line 163:
	[?] Help		[?] Help

	<main>:l		<main>:'''l'''

	_________________________________________________________________		_________________________________________________________________
Line 179:		Line 179:
	[?] Help		[?] Help

	<main>:g		<main>:'''g'''

	Enter Source IP Address. . . . . : 172.17.0.18		Enter Source IP Address. . . . . : '''172.17.0.18'''

	File Name. . . . . . : MD3060e_Firmware_039F.esm		File Name. . . . . . : '''MD3060e_Firmware_039F.esm'''

Adj: /* Firmware updates */

2025-05-24T01:37:18Z

Firmware updates

← Older revision		Revision as of 01:37, 24 May 2025
Line 119:		Line 119:

	== Firmware updates ==		== Firmware updates ==
			This can be done over the network using TFTP. Get an updated firmware ZIP file from Dell's support web site. Tell Dell you're looking for support for a PowerVault MD3060e or enter the Dell Service Tag from the chassis. Unpack the ZIP file, and place the <code>.esm</code> file located inside into the TFTP server's root directory. Then, on the EMM again, go to the Admin menu, and select the <code>l</code> (Load Image) option.

			_________________________________________________________________

			ESM Applications 2 User Menu

			(Wembley60 Tray 00, ESM-A, OEM 0, EBOD, FW 03.9F, Slots 60)

			_________________________________________________________________
			[c] Admin Interface
			[d] Dump State Capture Buffer (large)
			[e] Display Enclosure Status and Health
			[i] Display Enclosure Inventory
			[n] Display Network Configuration
			[p] Dump Configuration Profile
			[s] List Seven Segment Display Codes
			[?] Help


			<main>:c

			Entering Admin mode


			_________________________________________________________________

			ESM Applications 2 Admin Menu

			(Wembley60 Tray 00, ESM-A, OEM 0, EBOD, FW 03.9F, Slots 60)

			_________________________________________________________________
			[c] Command Line Interface
			[d] Dump State Capture Buffer (large)
			[e] Display Enclosure Status and Health
			[i] Display Enclosure Inventory
			[l] Load Image
			[n] Set Network Configuration
			[p] Dump Configuration Profile
			[q] Quit Admin Interface (Return to User-level menu)
			[r] Reboot the ESM (Temporary drive path loss will occur!)
			[s] List Seven Segment Display Codes
			[t] Set Enclosure Tray ID
			[?] Help

			<main>:l

			_________________________________________________________________

			ESM Applications 2 Load Image Menu

			(Wembley60 Tray 00, ESM-A, OEM 0, EBOD, FW 03.9F, Slots 60)

			_________________________________________________________________
			[d] Load factory defaults using Xmodem (auto reboot)
			[e] Load factory defaults using tftp (auto reboot)
			[f] Load firmware using Xmodem
			[g] Load firmware using tftp
			[q] Quit and return to admin menu
			[?] Help

			<main>:g

			Enter Source IP Address. . . . . : 172.17.0.18

			File Name. . . . . . : MD3060e_Firmware_039F.esm




			Received 1154260Bytes
			Firmware Download Complete

			_________________________________________________________________

			ESM Applications 2 Load Image Menu

			(Wembley60 Tray 00, ESM-A, OEM 0, EBOD, FW 03.9F, Slots 60)

			_________________________________________________________________
			[d] Load factory defaults using Xmodem (auto reboot)
			[e] Load factory defaults using tftp (auto reboot)
			[f] Load firmware using Xmodem
			[g] Load firmware using tftp
			[q] Quit and return to admin menu
			[?] Help

			<main>:
			FLASH Update in progress * DO NOT POWER DOWN ESM *

			FLASH Updating Boot code
			FLASH Boot code is up-to-date

			FLASH Updating FPGA code
			FLASH FPGA code is up-to-date

			FLASH Updating Application code
			FLASH Appl code is up-to-date

			FLASH Programming complete - rebooting

Adj: /* Set EMM up for DHCP */

2025-05-23T20:06:47Z

Set EMM up for DHCP

← Older revision		Revision as of 20:06, 23 May 2025
Line 51:		Line 51:

	== Set EMM up for DHCP ==		== Set EMM up for DHCP ==
			This one is pretty simple, too. Go to the Admin menu, select the network config option, set IP address value to "<code>.</code>"
	[p] Dump Configuration Profile		[p] Dump Configuration Profile
	[s] List Seven Segment Display Codes		[s] List Seven Segment Display Codes
Line 109:		Line 110:

	<main>:		<main>:
			Then reboot the EMM with the "<code>r</code>" menu option.

	== Crashing an EMM over the network ==		== Crashing an EMM over the network ==

Adj: /* Set EMM up for DHCP */

2025-05-23T20:03:56Z

Set EMM up for DHCP

← Older revision		Revision as of 20:03, 23 May 2025
Line 51:		Line 51:

	== Set EMM up for DHCP ==		== Set EMM up for DHCP ==
			[p] Dump Configuration Profile
			[s] List Seven Segment Display Codes
			[?] Help

			<main>:'''c'''

			Entering Admin mode


			_________________________________________________________________

			ESM Applications 2 Admin Menu

			(Wembley60 Tray 00, ESM-A, OEM 0, EBOD, FW 03.9F, Slots 60)

			_________________________________________________________________
			[c] Command Line Interface
			[d] Dump State Capture Buffer (large)
			[e] Display Enclosure Status and Health
			[i] Display Enclosure Inventory
			[l] Load Image
			[n] Set Network Configuration
			[p] Dump Configuration Profile
			[q] Quit Admin Interface (Return to User-level menu)
			[r] Reboot the ESM (Temporary drive path loss will occur!)
			[s] List Seven Segment Display Codes
			[t] Set Enclosure Tray ID
			[?] Help

			<main>:'''n'''

			Enter "." for the IP Address to set DHCP mode.
			DHCP Currently Enabled. . . . . . : Yes

			IP Address. . . . . [172.16.10.116] : '''.'''
			A Reboot is required for DHCP to take effect

			_________________________________________________________________

			ESM Applications 2 Admin Menu

			(Wembley60 Tray 00, ESM-A, OEM 0, EBOD, FW 03.9F, Slots 60)

			_________________________________________________________________
			[c] Command Line Interface
			[d] Dump State Capture Buffer (large)
			[e] Display Enclosure Status and Health
			[i] Display Enclosure Inventory
			[l] Load Image
			[n] Set Network Configuration
			[p] Dump Configuration Profile
			[q] Quit Admin Interface (Return to User-level menu)
			[r] Reboot the ESM (Temporary drive path loss will occur!)
			[s] List Seven Segment Display Codes
			[t] Set Enclosure Tray ID
			[?] Help

			<main>:

	== Crashing an EMM over the network ==		== Crashing an EMM over the network ==

Adj: /* Gather network config */

2025-05-23T20:00:51Z

Gather network config

@@ Line 8: / Line 8: @@
 == Gather network config ==
 From a machine with an IP address in the 192.168.128.0/24 range, <code>telnet</code> to 192.168.128.101.  There is no password needed.  Send a newline (Return or Enter key) and you'll probably be greeted by a menu.  If no menu appears, send a <code>?</code> and a newline to the EMM.
 == Set EMM up for DHCP ==

Adj: /* Crashing an EMM over the network */

2025-05-23T13:06:00Z

Crashing an EMM over the network

← Older revision		Revision as of 13:06, 23 May 2025
Line 8:		Line 8:
	== Gather network config ==		== Gather network config ==
	From a machine with an IP address in the 192.168.128.0/24 range, <code>telnet</code> to 192.168.128.101. There is no password needed. Send a newline (Return or Enter key) and you'll probably be greeted by a menu. If no menu appears, send a <code>?</code> and a newline to the EMM.		From a machine with an IP address in the 192.168.128.0/24 range, <code>telnet</code> to 192.168.128.101. There is no password needed. Send a newline (Return or Enter key) and you'll probably be greeted by a menu. If no menu appears, send a <code>?</code> and a newline to the EMM.

			== Set EMM up for DHCP ==

	== Crashing an EMM over the network ==		== Crashing an EMM over the network ==
Line 14:		Line 16:

	and wait forever. Power cycling may be required to bring it back to life at this point.		and wait forever. Power cycling may be required to bring it back to life at this point.

			== Firmware updates ==

Adj: /* Crashing an EMM over the network */

2025-05-22T23:15:45Z

Crashing an EMM over the network

← Older revision		Revision as of 23:15, 22 May 2025
Line 10:		Line 10:

	== Crashing an EMM over the network ==		== Crashing an EMM over the network ==
	$ sudo nmap -O -p 1- 172.16.10.116		$ '''sudo nmap -O -p 1- 172.16.10.116'''
	Starting Nmap 7.93 ( https://nmap.org ) at 2025-05-22 13:12 UTC		Starting Nmap 7.93 ( https://nmap.org ) at 2025-05-22 13:12 UTC

Adj: Created page with "4U tall. And space for 60 3.5inch (or 2.5inch) drives inside. == Attaching to the network == Each of the two rear mounted "enclousure management modules" ("EMMs") has a seri..."

2025-05-22T13:27:21Z

Created page with "4U tall. And space for 60 3.5inch (or 2.5inch) drives inside. == Attaching to the network == Each of the two rear mounted "enclousure management modules" ("EMMs") has a seri..."

New page

4U tall. And space for 60 3.5inch (or 2.5inch) drives inside.

== Attaching to the network ==
Each of the two rear mounted "enclousure management modules" ("EMMs") has a serial interface and an 8P8C modular jack for 100baseT Ethernet connectivity. The factory default IP addresses for these are 192.168.128.101 for EMM 0 (the top one) and 192.168.128.102 for EMM 1 (the bottom one). There is also a serial interface on each of the EMMs with a Mini-DIN 6 pin connector. Dell part numbers for the correct serial cables are CT109 and MN657. I have not used these and hope to not need them.

https://www.dell.com/support/kbdoc/en-us/000141824/pulling-logs-on-md3060e-via-serial-for-sds-solutions has some documentation on this.

== Gather network config ==
From a machine with an IP address in the 192.168.128.0/24 range, <code>telnet</code> to 192.168.128.101. There is no password needed. Send a newline (Return or Enter key) and you'll probably be greeted by a menu. If no menu appears, send a <code>?</code> and a newline to the EMM.

== Crashing an EMM over the network ==
$ sudo nmap -O -p 1- 172.16.10.116
Starting Nmap 7.93 ( https://nmap.org ) at 2025-05-22 13:12 UTC

and wait forever. Power cycling may be required to bring it back to life at this point.