add hsrp and test...

set the priorities on one side first all the same... the higher priority... keep it simple... once you know it's working then adjust... after a few times hsrp becomes manual labor... develop patterns for working these things out...

we know we have vlan 1 on dls1 at 172.16.1.1 and vlan 1 on dls2 as 172.16.1.2... so what virtual ip address will you pick... in the net acad lab they have you bust the ip's, ie. 172.16.1.3 and 1.4 on dls1 and dls2, just so you can have 172.16.1.1 as the virtual ip... who gives a shit... how about 172.16.1.3 or .5... i like 5 because it's glaring... 

interface Vlan1
 ip address 172.16.1.1 255.255.255.0
 standby 1 ip 172.16.1.5
 standby 1 priority 110
 standby 1 preempt
!
interface Vlan10
 ip address 172.16.10.1 255.255.255.0
 shutdown
 standby 1 ip 172.16.10.5
 standby 1 priority 110
 standby 1 preempt
!
interface Vlan20
 ip address 172.16.20.1 255.255.255.0
 standby 1 ip 172.16.20.5
 standby 1 priority 110
 standby 1 preempt
!
interface Vlan30
 ip address 172.16.30.1 255.255.255.0
 standby 1 ip 172.16.30.5
 standby 1 priority 110
 standby 1 preempt

dls2#sh standby brie
                     P indicates configured to preempt.
                     |
Interface   Grp  Pri P State   Active          Standby         Virtual IP
Vl1            1    90  P Standby 172.16.1.1      local           172.16.1.5
Vl10          1    90  P Standby 172.16.10.1     local           172.16.10.5
Vl20          1    90  P Standby 172.16.20.1     local           172.16.20.5
Vl30          1    90  P Standby 172.16.30.1     local           172.16.30.5
dls2#

i also like putting in the priority 90 as opposed to allowing the default 100 which doesn't show up in sh run...

dls1#sh standby brie
                     P indicates configured to preempt.
                     |
Interface   Grp  Pri P State   Active          Standby         Virtual IP
Vl1           1    110 P Active  local           172.16.1.2      172.16.1.5
Vl10         1    110 P Active  local           172.16.10.2     172.16.10.5
Vl20         1    110 P Active  local           172.16.20.2     172.16.20.5
Vl30         1    110 P Active  local           172.16.30.2     172.16.30.5
dls1#

 dls1(config)#int vlan 10
dls1(config-if)#shut
dls1(config-if)#
*Mar  2 07:17:05.305: %HSRP-5-STATECHANGE: Vlan10 Grp 1 state Active -> Init
*Mar  2 07:17:07.310: %LINK-5-CHANGED: Interface Vlan10, changed state to admini
stratively down
*Mar  2 07:17:07.318: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan10, ch
anged state to down

dls2#sh stand brie
                     P indicates configured to preempt.
                     |
Interface   Grp  Pri P State   Active          Standby         Virtual IP
Vl1           1    90  P Standby 172.16.1.1      local           172.16.1.5
Vl10         1    90  P Active  local           unknown         172.16.10.5
Vl20         1    90  P Standby 172.16.20.1     local           172.16.20.5
Vl30         1    90  P Standby 172.16.30.1     local           172.16.30.5
dls2#

once we destroyed vlan 10 on dls1,  vlan 10 on dls2 came to the rescue...  don't forget when you add hosts to the access switches use the virtual ip 172.16.10.5 or whatever associated vlan...

and of course you realize that there is no new standby because vlan 10 on dls1 is still down...