- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- redundant link with loop protection
Switches, Hubs, and Modems
1752795
Members
6100
Online
108789
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
07-18-2010 12:13 PM
07-18-2010 12:13 PM
redundant link with loop protection
I'm trying to setup a redundant link between switches in our san environment, but keep ending up in a broadcast storm when I attach the trunk. I've attached a diagram of our environment, showing what I'm trying to achieve. I've attempted to implement an MSTP config that would allow our SAN vlans to communicate through this redundant link, while blocking our Production vlan from creating the loop.
Here is the config on both switches:
hostname "ProCurve 2910al-24G - SW1"
module 1 type J9145A
interface 13
flow-control
exit
interface 14
flow-control
exit
interface 15
flow-control
exit
trunk 23-24 Trk1 LACP
trunk 21-22 Trk2 LACP
ip default-gateway 192.168.0.3
ip routing
vlan 1
name "DEFAULT_VLAN"
no untagged 1-20,Trk1-Trk2
no ip address
ip igmp
exit
vlan 10
name "Production"
untagged 1-12,16-20,Trk1-Trk2
ip address 192.168.0.171 255.255.255.0
ip igmp
exit
vlan 2
name "iSCSI1"
untagged 13-14
ip address 10.10.20.100 255.255.255.0
ip address 10.10.40.100 255.255.255.0
tagged Trk2
jumbo
exit
vlan 3
name "iSCSI2"
untagged 15
ip address 10.10.60.100 255.255.255.0
tagged Trk2
jumbo
exit
ip authorized-managers 192.168.0.0 255.255.255.0 access Manager
spanning-tree
spanning-tree Trk1 priority 4
spanning-tree Trk2 priority 4
spanning-tree config-name "prod-span"
spanning-tree config-revision 1
spanning-tree instance 1 vlan 2 3
spanning-tree instance 1 priority 4
spanning-tree instance 2 vlan 10
spanning-tree instance 2 priority 3
primary-vlan 10
no autorun
password manager
password operator
hostname "ProCurve 2910al-24G - SW2"
module 1 type J9145A
interface 13
flow-control
exit
interface 14
flow-control
exit
interface 15
flow-control
exit
trunk 23-24 Trk1 LACP
trunk 21-22 Trk2 LACP
ip default-gateway 192.168.0.3
ip routing
vlan 1
name "DEFAULT_VLAN"
no untagged 1-20,Trk1-Trk2
no ip address
ip igmp
exit
vlan 10
name "Production"
untagged 1-12,16-20,Trk1-Trk2
ip address 192.168.0.171 255.255.255.0
ip igmp
exit
vlan 2
name "iSCSI1"
untagged 13-14
ip address 10.10.20.100 255.255.255.0
ip address 10.10.40.100 255.255.255.0
tagged Trk2
jumbo
exit
vlan 3
name "iSCSI2"
untagged 15
ip address 10.10.60.100 255.255.255.0
tagged Trk2
jumbo
exit
ip authorized-managers 192.168.0.0 255.255.255.0 access Manager
spanning-tree
spanning-tree Trk1 priority 4
spanning-tree Trk2 priority 4
spanning-tree config-name "prod-span"
spanning-tree config-revision 1
spanning-tree instance 1 vlan 2 3
spanning-tree instance 1 priority 4
spanning-tree instance 2 vlan 10
spanning-tree instance 2 priority 3
primary-vlan 10
no autorun
password manager
password operator
Here is the config on both switches:
hostname "ProCurve 2910al-24G - SW1"
module 1 type J9145A
interface 13
flow-control
exit
interface 14
flow-control
exit
interface 15
flow-control
exit
trunk 23-24 Trk1 LACP
trunk 21-22 Trk2 LACP
ip default-gateway 192.168.0.3
ip routing
vlan 1
name "DEFAULT_VLAN"
no untagged 1-20,Trk1-Trk2
no ip address
ip igmp
exit
vlan 10
name "Production"
untagged 1-12,16-20,Trk1-Trk2
ip address 192.168.0.171 255.255.255.0
ip igmp
exit
vlan 2
name "iSCSI1"
untagged 13-14
ip address 10.10.20.100 255.255.255.0
ip address 10.10.40.100 255.255.255.0
tagged Trk2
jumbo
exit
vlan 3
name "iSCSI2"
untagged 15
ip address 10.10.60.100 255.255.255.0
tagged Trk2
jumbo
exit
ip authorized-managers 192.168.0.0 255.255.255.0 access Manager
spanning-tree
spanning-tree Trk1 priority 4
spanning-tree Trk2 priority 4
spanning-tree config-name "prod-span"
spanning-tree config-revision 1
spanning-tree instance 1 vlan 2 3
spanning-tree instance 1 priority 4
spanning-tree instance 2 vlan 10
spanning-tree instance 2 priority 3
primary-vlan 10
no autorun
password manager
password operator
hostname "ProCurve 2910al-24G - SW2"
module 1 type J9145A
interface 13
flow-control
exit
interface 14
flow-control
exit
interface 15
flow-control
exit
trunk 23-24 Trk1 LACP
trunk 21-22 Trk2 LACP
ip default-gateway 192.168.0.3
ip routing
vlan 1
name "DEFAULT_VLAN"
no untagged 1-20,Trk1-Trk2
no ip address
ip igmp
exit
vlan 10
name "Production"
untagged 1-12,16-20,Trk1-Trk2
ip address 192.168.0.171 255.255.255.0
ip igmp
exit
vlan 2
name "iSCSI1"
untagged 13-14
ip address 10.10.20.100 255.255.255.0
ip address 10.10.40.100 255.255.255.0
tagged Trk2
jumbo
exit
vlan 3
name "iSCSI2"
untagged 15
ip address 10.10.60.100 255.255.255.0
tagged Trk2
jumbo
exit
ip authorized-managers 192.168.0.0 255.255.255.0 access Manager
spanning-tree
spanning-tree Trk1 priority 4
spanning-tree Trk2 priority 4
spanning-tree config-name "prod-span"
spanning-tree config-revision 1
spanning-tree instance 1 vlan 2 3
spanning-tree instance 1 priority 4
spanning-tree instance 2 vlan 10
spanning-tree instance 2 priority 3
primary-vlan 10
no autorun
password manager
password operator
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-18-2010 12:21 PM
07-18-2010 12:21 PM
Re: redundant link with loop protection
Here is a corrected config for switch 2:
hostname "ProCurve 2910al-24G - SW2"
module 1 type J9145A
interface 13
flow-control
exit
interface 14
flow-control
exit
interface 15
flow-control
exit
trunk 23-24 Trk1 LACP
trunk 21-22 Trk2 LACP
ip default-gateway 192.168.0.3
ip routing
vlan 1
name "DEFAULT_VLAN"
no untagged 1-20,Trk1-Trk2
no ip address
ip igmp
exit
vlan 10
name "Production"
untagged 1-12,16-20,Trk1-Trk2
ip address 192.168.0.171 255.255.255.0
ip igmp
exit
vlan 2
name "iSCSI1"
untagged 13-14
ip address 10.10.30.100 255.255.255.0
ip address 10.10.50.100 255.255.255.0
tagged Trk2
jumbo
exit
vlan 3
name "iSCSI2"
untagged 15
ip address 10.10.70.100 255.255.255.0
tagged Trk2
jumbo
exit
ip authorized-managers 192.168.0.0 255.255.255.0 access Manager
spanning-tree
spanning-tree Trk1 priority 4
spanning-tree Trk2 priority 4
spanning-tree config-name "prod-span"
spanning-tree config-revision 1
spanning-tree instance 1 vlan 2 3
spanning-tree instance 1 priority 4
spanning-tree instance 2 vlan 10
spanning-tree instance 2 priority 3
primary-vlan 10
no autorun
password manager
password operator
hostname "ProCurve 2910al-24G - SW2"
module 1 type J9145A
interface 13
flow-control
exit
interface 14
flow-control
exit
interface 15
flow-control
exit
trunk 23-24 Trk1 LACP
trunk 21-22 Trk2 LACP
ip default-gateway 192.168.0.3
ip routing
vlan 1
name "DEFAULT_VLAN"
no untagged 1-20,Trk1-Trk2
no ip address
ip igmp
exit
vlan 10
name "Production"
untagged 1-12,16-20,Trk1-Trk2
ip address 192.168.0.171 255.255.255.0
ip igmp
exit
vlan 2
name "iSCSI1"
untagged 13-14
ip address 10.10.30.100 255.255.255.0
ip address 10.10.50.100 255.255.255.0
tagged Trk2
jumbo
exit
vlan 3
name "iSCSI2"
untagged 15
ip address 10.10.70.100 255.255.255.0
tagged Trk2
jumbo
exit
ip authorized-managers 192.168.0.0 255.255.255.0 access Manager
spanning-tree
spanning-tree Trk1 priority 4
spanning-tree Trk2 priority 4
spanning-tree config-name "prod-span"
spanning-tree config-revision 1
spanning-tree instance 1 vlan 2 3
spanning-tree instance 1 priority 4
spanning-tree instance 2 vlan 10
spanning-tree instance 2 priority 3
primary-vlan 10
no autorun
password manager
password operator
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP