- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- 4 5304 - 2 Datacenter - Full redundancy
Switches, Hubs, and Modems
1748197
Members
2527
Online
108759
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
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
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
тАО09-04-2007 07:47 AM
тАО09-04-2007 07:47 AM
4 5304 - 2 Datacenter - Full redundancy
Hi @ all,
we planned to modifiy our backboe with 2 additional 5304. So the plan is to install in each datacenter 2 5304 and connect them all together to reach full redundancy in the backbone Area.
We have also different VLAN's which must be on the Switches.
My questions are:
1)
How can we reach loadsharing over the connection between the switches? Must we use MSTP and GVRP?
2)
Is a 1x 1 GBit FIbre enough to connect each switches together?
3)
How must we implemented VRRP?
4)
Doen anybody have a example config for this scenario?
I say thank you for your help.
Kind Regards
Alen
we planned to modifiy our backboe with 2 additional 5304. So the plan is to install in each datacenter 2 5304 and connect them all together to reach full redundancy in the backbone Area.
We have also different VLAN's which must be on the Switches.
My questions are:
1)
How can we reach loadsharing over the connection between the switches? Must we use MSTP and GVRP?
2)
Is a 1x 1 GBit FIbre enough to connect each switches together?
3)
How must we implemented VRRP?
4)
Doen anybody have a example config for this scenario?
I say thank you for your help.
Kind Regards
Alen
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-04-2007 06:14 PM
тАО09-04-2007 06:14 PM
Re: 4 5304 - 2 Datacenter - Full redundancy
Hi
1- With Layer2 (MSTP) and Layer3 (XRRP) you can have full redundant network.
GVRP not recommended at all.
2- In case you are planning for full mesh, its better to have redundant link from each 5300, and better also to have dual links in case you have enough Mini-GBIC and fiber cores.
3- With the 5300, Layer3 redundancy can be done based on XRRP, and VRRP not available on that switches.
4- In most cases, with data center solutions, they will use OSPF ECMP for load balancing especially if the data center interconnects with the L4-L7 (Firewalls, Packet shapers, DMZs, Cache boxes, and any other devices like SSL and Data or WAN Acceleration ...).
The following link will explain how to implement OSPF with the 5300, it could be helpful:
http://www.hp.com/rnd/support/config_examples/5300xl_ospf_singlearea.pdf
Good Luck !!!
1- With Layer2 (MSTP) and Layer3 (XRRP) you can have full redundant network.
GVRP not recommended at all.
2- In case you are planning for full mesh, its better to have redundant link from each 5300, and better also to have dual links in case you have enough Mini-GBIC and fiber cores.
3- With the 5300, Layer3 redundancy can be done based on XRRP, and VRRP not available on that switches.
4- In most cases, with data center solutions, they will use OSPF ECMP for load balancing especially if the data center interconnects with the L4-L7 (Firewalls, Packet shapers, DMZs, Cache boxes, and any other devices like SSL and Data or WAN Acceleration ...).
The following link will explain how to implement OSPF with the 5300, it could be helpful:
http://www.hp.com/rnd/support/config_examples/5300xl_ospf_singlearea.pdf
Good Luck !!!
Science for Everyone
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-04-2007 06:48 PM
тАО09-04-2007 06:48 PM
Re: 4 5304 - 2 Datacenter - Full redundancy
Hi!
Thanx for answering.
Did you have an example config for this scenario in your bag? :)
1) How must I configure LoadSharing for the VLAN's or will this run by GRRP?
Thanx for answering.
Did you have an example config for this scenario in your bag? :)
1) How must I configure LoadSharing for the VLAN's or will this run by GRRP?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-05-2007 03:17 AM
тАО09-05-2007 03:17 AM
Re: 4 5304 - 2 Datacenter - Full redundancy
Hi
Check the attached file showing a sample XRRP and MSTP from my bag :)
In fact i used the 5300 as a Core with XRRP and 5400 as edge (i didn;t have the premium edge license to run VRRP)
The config for Core1 of the 5300:
hostname "SW5300-1"
console inactivity-timer 15
ip default-gateway 192.168.1.45
ip routing
logging facility syslog
logging 192.168.1.141
snmp-server community "public" Unrestricted
vlan 1
name "DEFAULT_VLAN"
untagged A1-A16,B1-B16
ip address 192.168.1.46 255.255.255.0
exit
vlan 2
name "VLAN2"
ip address 10.1.2.2 255.255.255.0
tagged A2,B1,B4
exit
vlan 3
name "VLAN3"
ip address 10.1.3.2 255.255.255.0
tagged A2,B1,B4
exit
vlan 4
name "VLAN4"
ip address 10.1.4.2 255.255.255.0
tagged A2,B1,B4
exit
xrrp
xrrp domain 2
xrrp instance 1 1
xrrp instance 2 1 ip 192.168.1.47 255.255.255.0
xrrp instance 1 2
xrrp instance 2 2 ip 10.1.2.3 255.255.255.0
xrrp instance 1 3
xrrp instance 2 3 ip 10.1.3.3 255.255.255.0
xrrp instance 1 4
xrrp instance 2 4 ip 10.1.4.3 255.255.255.0
ip route 0.0.0.0 0.0.0.0 192.168.1.1
spanning-tree
spanning-tree protocol-version MSTP
spanning-tree config-name "SPAN"
spanning-tree config-revision 8
spanning-tree instance 1 vlan 1 2
spanning-tree instance 1 priority 0
spanning-tree instance 2 vlan 3 4
spanning-tree instance 2 priority 1
spanning-tree hello-time 1 priority 0
The config for Core2 of the 5300:
hostname "SW5300-2"
console inactivity-timer 15
ip default-gateway 192.168.1.45
ip routing
snmp-server community "public" Unrestricted
vlan 1
name "DEFAULT_VLAN"
untagged B1-B24,C1-C24,D1-D24
ip address 192.168.1.47 255.255.255.0
exit
vlan 2
name "VLAN2"
ip address 10.1.2.3 255.255.255.0
tagged B2,B4,B6
exit
vlan 3
name "VLAN3"
ip address 10.1.3.3 255.255.255.0
tagged B2,B4,B6
exit
vlan 4
name "VLAN4"
ip address 10.1.4.3 255.255.255.0
tagged B2,B4,B6
exit
xrrp
xrrp domain 2
xrrp router 2
xrrp instance 2 1
xrrp instance 1 1 ip 192.168.1.46 255.255.255.0
xrrp instance 2 2
xrrp instance 1 2 ip 10.1.2.2 255.255.255.0
xrrp instance 2 3
xrrp instance 1 3 ip 10.1.3.2 255.255.255.0
xrrp instance 2 4
xrrp instance 1 4 ip 10.1.4.2 255.255.255.0
ip route 0.0.0.0 0.0.0.0 192.168.1.1
spanning-tree
spanning-tree protocol-version MSTP
spanning-tree B6 priority 0
spanning-tree config-name "SPAN"
spanning-tree config-revision 8
spanning-tree instance 1 vlan 1 2
spanning-tree instance 1 priority 1
spanning-tree instance 1 B6 priority 0
spanning-tree instance 2 vlan 3 4
spanning-tree instance 2 priority 0
spanning-tree hello-time 1 priority 1
So i think the attached drawing explains how is the setup.
Good Luck !!!
Check the attached file showing a sample XRRP and MSTP from my bag :)
In fact i used the 5300 as a Core with XRRP and 5400 as edge (i didn;t have the premium edge license to run VRRP)
The config for Core1 of the 5300:
hostname "SW5300-1"
console inactivity-timer 15
ip default-gateway 192.168.1.45
ip routing
logging facility syslog
logging 192.168.1.141
snmp-server community "public" Unrestricted
vlan 1
name "DEFAULT_VLAN"
untagged A1-A16,B1-B16
ip address 192.168.1.46 255.255.255.0
exit
vlan 2
name "VLAN2"
ip address 10.1.2.2 255.255.255.0
tagged A2,B1,B4
exit
vlan 3
name "VLAN3"
ip address 10.1.3.2 255.255.255.0
tagged A2,B1,B4
exit
vlan 4
name "VLAN4"
ip address 10.1.4.2 255.255.255.0
tagged A2,B1,B4
exit
xrrp
xrrp domain 2
xrrp instance 1 1
xrrp instance 2 1 ip 192.168.1.47 255.255.255.0
xrrp instance 1 2
xrrp instance 2 2 ip 10.1.2.3 255.255.255.0
xrrp instance 1 3
xrrp instance 2 3 ip 10.1.3.3 255.255.255.0
xrrp instance 1 4
xrrp instance 2 4 ip 10.1.4.3 255.255.255.0
ip route 0.0.0.0 0.0.0.0 192.168.1.1
spanning-tree
spanning-tree protocol-version MSTP
spanning-tree config-name "SPAN"
spanning-tree config-revision 8
spanning-tree instance 1 vlan 1 2
spanning-tree instance 1 priority 0
spanning-tree instance 2 vlan 3 4
spanning-tree instance 2 priority 1
spanning-tree hello-time 1 priority 0
The config for Core2 of the 5300:
hostname "SW5300-2"
console inactivity-timer 15
ip default-gateway 192.168.1.45
ip routing
snmp-server community "public" Unrestricted
vlan 1
name "DEFAULT_VLAN"
untagged B1-B24,C1-C24,D1-D24
ip address 192.168.1.47 255.255.255.0
exit
vlan 2
name "VLAN2"
ip address 10.1.2.3 255.255.255.0
tagged B2,B4,B6
exit
vlan 3
name "VLAN3"
ip address 10.1.3.3 255.255.255.0
tagged B2,B4,B6
exit
vlan 4
name "VLAN4"
ip address 10.1.4.3 255.255.255.0
tagged B2,B4,B6
exit
xrrp
xrrp domain 2
xrrp router 2
xrrp instance 2 1
xrrp instance 1 1 ip 192.168.1.46 255.255.255.0
xrrp instance 2 2
xrrp instance 1 2 ip 10.1.2.2 255.255.255.0
xrrp instance 2 3
xrrp instance 1 3 ip 10.1.3.2 255.255.255.0
xrrp instance 2 4
xrrp instance 1 4 ip 10.1.4.2 255.255.255.0
ip route 0.0.0.0 0.0.0.0 192.168.1.1
spanning-tree
spanning-tree protocol-version MSTP
spanning-tree B6 priority 0
spanning-tree config-name "SPAN"
spanning-tree config-revision 8
spanning-tree instance 1 vlan 1 2
spanning-tree instance 1 priority 1
spanning-tree instance 1 B6 priority 0
spanning-tree instance 2 vlan 3 4
spanning-tree instance 2 priority 0
spanning-tree hello-time 1 priority 1
So i think the attached drawing explains how is the setup.
Good Luck !!!
Science for Everyone
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