Monday, September 21

802.3ad MultiMode Dynamic VIF and an HP Procurve Switch

These are the configs to get LACP and 802.1q working between a NetApp and HP Procurve. An HP "Trunk". There are other ways to configure this, but after an e-mail to NetApp and phone call to HP, it sounds like this is the "preferred" way to configure the two devices together.

You will notice that VLAN 1 is tagged on the HP Procurve Trunks. VLAN 1 must be tagged or the NetApp will not communicate over it. By default it is not tagged on HP or Cisco switches.

IP addresses, VLAN Numbers and Hostnames have been changed.


/ETC/RC
hostname NAS01
vif create lacp vif0 e0a e0b
vlan create vif0 1 10
ifconfig vif0-1 `hostname`-vif0-1 netmask 255.255.255.0 wins
ifconfig vif0-10 `hostname`-vif0-10 netmask 255.255.255.0 wins
route add default 192.168.1.1 1
routed on
options.dns.enable on
options.nis.enable off
savecore

/ETC/HOSTS
127.0.0.1 localhost
192.168.1.2 NAS01 NAS01-vif0-1
10.0.0.2 NAS01 NAS01-vif0-10

Below is the HP config. Before you run the Trunk (ports) (trunkname) lacp command for the ports connected to the Filer, you need to drop down to each interface and run "lacp passive". I know it doesn't show up in the config, but if you run the trunk command without the LACP passive command it will place "LACP Active" in the configuration. I was unable to get the Trunk to come up properly when this was in place. Also, you'll want to turn Flow Control on for the ports the NAS is using.

Running configuration:

; J9022A Configuration Editor; Created on release #N.11.15


interface 25
name "NAS01e0a"
flow-control
exit
interface 26
name "NAS01e0b"
flow-control
exit
trunk 25-26 Trk1 LACP

vlan 1
name "Production"
untagged 1-20,27-36,Trk4-Trk6
ip address 192.168.1.3 255.255.255.0
tagged Trk1
no untagged Trk2-Trk3
exit
vlan 10
name "Storage"
untagged Trk2-Trk3
no ip address
tagged Trk1
exit






Saturday, September 19

Backup Exec System Recovery, Can't Map Drive to Restore Server

I was trying to map the machine that needed to be recovered to a network share from the Symantec Backup Exec System Recovery Bootable Recovery CD.. The interface would map the drive but never let me get into it. It also wouldn't ask me for credentials.

I found a way around this, if you go back to the screen where you select the file image to use, click browse. Double Click Computer. Select your C drive, but don't double click it. Hold Down Shift + F10. A menu should come up with an option to go to the command line.

Map your share from the command line:

net use r: \\server\sharename /user:domain\username password

I was then able to get back to the browse window and select the image to restore from the share.

Friday, September 18

Hyper-V no VHD Mount?

Apparently you can't mount VHD's straight to your OS anymore in Hyper-V. I remember being able to do this in VS2005. Lame.