- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- Procurve 2848 routing?
Switches, Hubs, and Modems
1753328
Members
4871
Online
108792
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
03-01-2011 08:48 AM
03-01-2011 08:48 AM
Procurve 2848 routing?
We have two buildings connected via fibre. Each building has two Procurve 2848’s. Currently there are two Vlans set-up (one for each building), and everything seems to be working properly.
However, I would like to create a third Vlan in building #2. This Vlan would need to access all network resources in both buildings, but would have a separate internet connection. The two existing Vlans share a T1 connection (located in building #1), and I would like a third Vlan to use a cable connection located in building #2. I have an extra 2848 that could be used, but I would prefer not to use the additional switch.
Any suggestions on the “best” way to accomplish this would be greatly appreciated.
Building # 1 Switch:
cdp run
mirror-port 1
interface 38
no lacp
exit
interface 45
no lacp
exit
interface 46
no lacp
exit
trunk 45-46 Trk1 Trunk
ip default-gateway 192.168.1.1
ip routing
snmp-server community "public" Unrestricted
vlan 1
name "TFC"
untagged 1-44,47,Trk1
ip address 192.168.1.1 255.255.255.0
ip helper-address 192.168.1.22
tagged 48
ip proxy-arp
exit
vlan 2
name "CORP"
ip address 192.168.2.1 255.255.255.0
ip helper-address 192.168.1.22
tagged 48
ip proxy-arp
exit
interface 2-44,47-48
monitor
exit
fault-finder bad-driver sensitivity low
fault-finder bad-transceiver sensitivity low
fault-finder bad-cable sensitivity low
fault-finder too-long-cable sensitivity low
fault-finder over-bandwidth sensitivity low
fault-finder broadcast-storm sensitivity low
fault-finder loss-of-link sensitivity low
fault-finder duplex-mismatch-HDx sensitivity low
fault-finder duplex-mismatch-FDx sensitivity low
ip route 0.0.0.0 0.0.0.0 192.168.1.2
no stack
spanning-tree Trk1 priority 4
ip ssh version 1-or-2
password manager
password operator
TFC2848one# show ip rout
IP Route Entries
Destination Gateway VLAN Type Sub-Type Metric Dist.
------------------ --------------- ---- --------- ---------- ---------- -----
0.0.0.0/0 192.168.1.2 1 static 1 1
127.0.0.0/8 reject static 0 250
127.0.0.1/32 lo0 connected 0 0
192.168.1.0/24 TFC 1 connected 0 0
192.168.2.0/24 CORP 2 connected 0 0
building #2 switch:
cdp run
interface 17
speed-duplex 100-half
exit
interface 45
no lacp
exit
interface 46
no lacp
exit
trunk 45-46 Trk1 Trunk
ip default-gateway 192.168.2.1
snmp-server community "adex" Unrestricted
vlan 1
name "TFC"
ip address 192.168.1.3 255.255.255.0
tagged 48
no untagged 1-44,47,Trk1
exit
vlan 2
name "CORP"
untagged 1-44,47,Trk1
ip address 192.168.2.3 255.255.255.0
tagged 48
exit
no stack
spanning-tree Trk1 priority 4
ip ssh version 1-or-2
password manager
password operator
corp2848one# show ip route
IP Route Entries
Destination Gateway VLAN Type Sub-Type Metric Dist.
------------------ --------------- ---- --------- ---------- ---------- -----
0.0.0.0/0 192.168.2.1 2 static 0 250
127.0.0.0/8 reject static 0 250
127.0.0.1/32 lo0 connected 0 0
192.168.1.0/24 TFC 1 connected 0 0
192.168.2.0/24 CORP 2 connected 0
However, I would like to create a third Vlan in building #2. This Vlan would need to access all network resources in both buildings, but would have a separate internet connection. The two existing Vlans share a T1 connection (located in building #1), and I would like a third Vlan to use a cable connection located in building #2. I have an extra 2848 that could be used, but I would prefer not to use the additional switch.
Any suggestions on the “best” way to accomplish this would be greatly appreciated.
Building # 1 Switch:
cdp run
mirror-port 1
interface 38
no lacp
exit
interface 45
no lacp
exit
interface 46
no lacp
exit
trunk 45-46 Trk1 Trunk
ip default-gateway 192.168.1.1
ip routing
snmp-server community "public" Unrestricted
vlan 1
name "TFC"
untagged 1-44,47,Trk1
ip address 192.168.1.1 255.255.255.0
ip helper-address 192.168.1.22
tagged 48
ip proxy-arp
exit
vlan 2
name "CORP"
ip address 192.168.2.1 255.255.255.0
ip helper-address 192.168.1.22
tagged 48
ip proxy-arp
exit
interface 2-44,47-48
monitor
exit
fault-finder bad-driver sensitivity low
fault-finder bad-transceiver sensitivity low
fault-finder bad-cable sensitivity low
fault-finder too-long-cable sensitivity low
fault-finder over-bandwidth sensitivity low
fault-finder broadcast-storm sensitivity low
fault-finder loss-of-link sensitivity low
fault-finder duplex-mismatch-HDx sensitivity low
fault-finder duplex-mismatch-FDx sensitivity low
ip route 0.0.0.0 0.0.0.0 192.168.1.2
no stack
spanning-tree Trk1 priority 4
ip ssh version 1-or-2
password manager
password operator
TFC2848one# show ip rout
IP Route Entries
Destination Gateway VLAN Type Sub-Type Metric Dist.
------------------ --------------- ---- --------- ---------- ---------- -----
0.0.0.0/0 192.168.1.2 1 static 1 1
127.0.0.0/8 reject static 0 250
127.0.0.1/32 lo0 connected 0 0
192.168.1.0/24 TFC 1 connected 0 0
192.168.2.0/24 CORP 2 connected 0 0
building #2 switch:
cdp run
interface 17
speed-duplex 100-half
exit
interface 45
no lacp
exit
interface 46
no lacp
exit
trunk 45-46 Trk1 Trunk
ip default-gateway 192.168.2.1
snmp-server community "adex" Unrestricted
vlan 1
name "TFC"
ip address 192.168.1.3 255.255.255.0
tagged 48
no untagged 1-44,47,Trk1
exit
vlan 2
name "CORP"
untagged 1-44,47,Trk1
ip address 192.168.2.3 255.255.255.0
tagged 48
exit
no stack
spanning-tree Trk1 priority 4
ip ssh version 1-or-2
password manager
password operator
corp2848one# show ip route
IP Route Entries
Destination Gateway VLAN Type Sub-Type Metric Dist.
------------------ --------------- ---- --------- ---------- ---------- -----
0.0.0.0/0 192.168.2.1 2 static 0 250
127.0.0.0/8 reject static 0 250
127.0.0.1/32 lo0 connected 0 0
192.168.1.0/24 TFC 1 connected 0 0
192.168.2.0/24 CORP 2 connected 0
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-03-2011 03:08 AM
03-03-2011 03:08 AM
Re: Procurve 2848 routing?
- create the third vlan
- tag the vlan on the ports that connect the two switches.
- DON't give the switch that does the routing an ip-adress in this vlan.
- untag a port in this vlan
- connect your separate internet router to this port
- untag ports for this vlan as necessary.
hth
Pieter
- tag the vlan on the ports that connect the two switches.
- DON't give the switch that does the routing an ip-adress in this vlan.
- untag a port in this vlan
- connect your separate internet router to this port
- untag ports for this vlan as necessary.
hth
Pieter
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