<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Procurve 2848 routing? in Switches, Hubs, and Modems</title>
    <link>https://community.hpe.com/t5/switches-hubs-and-modems/procurve-2848-routing/m-p/4759690#M25459</link>
    <description>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.&lt;BR /&gt;&lt;BR /&gt;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.&lt;BR /&gt;&lt;BR /&gt;Any suggestions on the “best” way to accomplish this would be greatly appreciated.&lt;BR /&gt;&lt;BR /&gt;Building # 1 Switch:&lt;BR /&gt;&lt;BR /&gt;cdp run&lt;BR /&gt;mirror-port 1&lt;BR /&gt;interface 38&lt;BR /&gt;   no lacp&lt;BR /&gt;exit&lt;BR /&gt;interface 45&lt;BR /&gt;   no lacp&lt;BR /&gt;exit&lt;BR /&gt;interface 46&lt;BR /&gt;   no lacp&lt;BR /&gt;exit&lt;BR /&gt;trunk 45-46 Trk1 Trunk&lt;BR /&gt;ip default-gateway 192.168.1.1&lt;BR /&gt;ip routing&lt;BR /&gt;snmp-server community "public" Unrestricted&lt;BR /&gt;vlan 1&lt;BR /&gt;   name "TFC"&lt;BR /&gt;   untagged 1-44,47,Trk1&lt;BR /&gt;   ip address 192.168.1.1 255.255.255.0&lt;BR /&gt;   ip helper-address 192.168.1.22&lt;BR /&gt;   tagged 48&lt;BR /&gt;   ip proxy-arp&lt;BR /&gt;   exit&lt;BR /&gt;vlan 2&lt;BR /&gt;   name "CORP"&lt;BR /&gt;   ip address 192.168.2.1 255.255.255.0&lt;BR /&gt;   ip helper-address 192.168.1.22&lt;BR /&gt;   tagged 48&lt;BR /&gt;   ip proxy-arp&lt;BR /&gt;   exit&lt;BR /&gt;interface 2-44,47-48&lt;BR /&gt;   monitor&lt;BR /&gt;   exit&lt;BR /&gt;fault-finder bad-driver sensitivity low&lt;BR /&gt;fault-finder bad-transceiver sensitivity low&lt;BR /&gt;fault-finder bad-cable sensitivity low&lt;BR /&gt;fault-finder too-long-cable sensitivity low&lt;BR /&gt;fault-finder over-bandwidth sensitivity low&lt;BR /&gt;fault-finder broadcast-storm sensitivity low&lt;BR /&gt;fault-finder loss-of-link sensitivity low&lt;BR /&gt;fault-finder duplex-mismatch-HDx sensitivity low&lt;BR /&gt;fault-finder duplex-mismatch-FDx sensitivity low&lt;BR /&gt;ip route 0.0.0.0 0.0.0.0 192.168.1.2&lt;BR /&gt;no stack&lt;BR /&gt;spanning-tree Trk1 priority 4&lt;BR /&gt;ip ssh version 1-or-2&lt;BR /&gt;password manager&lt;BR /&gt;password operator&lt;BR /&gt;&lt;BR /&gt;TFC2848one# show ip rout&lt;BR /&gt;&lt;BR /&gt;                                IP Route Entries&lt;BR /&gt;&lt;BR /&gt;  Destination        Gateway         VLAN Type      Sub-Type   Metric     Dist.&lt;BR /&gt;  ------------------ --------------- ---- --------- ---------- ---------- -----&lt;BR /&gt;  0.0.0.0/0          192.168.1.2     1    static               1          1&lt;BR /&gt;  127.0.0.0/8        reject               static               0          250&lt;BR /&gt;  127.0.0.1/32       lo0                  connected            0          0&lt;BR /&gt;  192.168.1.0/24     TFC             1    connected            0          0&lt;BR /&gt;  192.168.2.0/24     CORP            2    connected            0          0&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;building #2 switch:&lt;BR /&gt;&lt;BR /&gt;cdp run&lt;BR /&gt;interface 17&lt;BR /&gt;   speed-duplex 100-half&lt;BR /&gt;exit&lt;BR /&gt;interface 45&lt;BR /&gt;   no lacp&lt;BR /&gt;exit&lt;BR /&gt;interface 46&lt;BR /&gt;   no lacp&lt;BR /&gt;exit&lt;BR /&gt;trunk 45-46 Trk1 Trunk&lt;BR /&gt;ip default-gateway 192.168.2.1&lt;BR /&gt;snmp-server community "adex" Unrestricted&lt;BR /&gt;vlan 1&lt;BR /&gt;   name "TFC"&lt;BR /&gt;   ip address 192.168.1.3 255.255.255.0&lt;BR /&gt;   tagged 48&lt;BR /&gt;   no untagged 1-44,47,Trk1&lt;BR /&gt;   exit&lt;BR /&gt;vlan 2&lt;BR /&gt;   name "CORP"&lt;BR /&gt;   untagged 1-44,47,Trk1&lt;BR /&gt;   ip address 192.168.2.3 255.255.255.0&lt;BR /&gt;   tagged 48&lt;BR /&gt;   exit&lt;BR /&gt;no stack&lt;BR /&gt;spanning-tree Trk1 priority 4&lt;BR /&gt;ip ssh version 1-or-2&lt;BR /&gt;password manager&lt;BR /&gt;password operator&lt;BR /&gt;&lt;BR /&gt;corp2848one# show ip route&lt;BR /&gt;&lt;BR /&gt;                                IP Route Entries&lt;BR /&gt;&lt;BR /&gt;  Destination        Gateway         VLAN Type      Sub-Type   Metric     Dist.&lt;BR /&gt;  ------------------ --------------- ---- --------- ---------- ---------- -----&lt;BR /&gt;  0.0.0.0/0          192.168.2.1     2    static               0          250&lt;BR /&gt;  127.0.0.0/8        reject               static               0          250&lt;BR /&gt;  127.0.0.1/32       lo0                  connected            0          0&lt;BR /&gt;  192.168.1.0/24     TFC             1    connected            0          0&lt;BR /&gt;  192.168.2.0/24     CORP            2    connected            0&lt;BR /&gt;</description>
    <pubDate>Tue, 01 Mar 2011 16:48:00 GMT</pubDate>
    <dc:creator>Mark E Wilson</dc:creator>
    <dc:date>2011-03-01T16:48:00Z</dc:date>
    <item>
      <title>Procurve 2848 routing?</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/procurve-2848-routing/m-p/4759690#M25459</link>
      <description>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.&lt;BR /&gt;&lt;BR /&gt;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.&lt;BR /&gt;&lt;BR /&gt;Any suggestions on the “best” way to accomplish this would be greatly appreciated.&lt;BR /&gt;&lt;BR /&gt;Building # 1 Switch:&lt;BR /&gt;&lt;BR /&gt;cdp run&lt;BR /&gt;mirror-port 1&lt;BR /&gt;interface 38&lt;BR /&gt;   no lacp&lt;BR /&gt;exit&lt;BR /&gt;interface 45&lt;BR /&gt;   no lacp&lt;BR /&gt;exit&lt;BR /&gt;interface 46&lt;BR /&gt;   no lacp&lt;BR /&gt;exit&lt;BR /&gt;trunk 45-46 Trk1 Trunk&lt;BR /&gt;ip default-gateway 192.168.1.1&lt;BR /&gt;ip routing&lt;BR /&gt;snmp-server community "public" Unrestricted&lt;BR /&gt;vlan 1&lt;BR /&gt;   name "TFC"&lt;BR /&gt;   untagged 1-44,47,Trk1&lt;BR /&gt;   ip address 192.168.1.1 255.255.255.0&lt;BR /&gt;   ip helper-address 192.168.1.22&lt;BR /&gt;   tagged 48&lt;BR /&gt;   ip proxy-arp&lt;BR /&gt;   exit&lt;BR /&gt;vlan 2&lt;BR /&gt;   name "CORP"&lt;BR /&gt;   ip address 192.168.2.1 255.255.255.0&lt;BR /&gt;   ip helper-address 192.168.1.22&lt;BR /&gt;   tagged 48&lt;BR /&gt;   ip proxy-arp&lt;BR /&gt;   exit&lt;BR /&gt;interface 2-44,47-48&lt;BR /&gt;   monitor&lt;BR /&gt;   exit&lt;BR /&gt;fault-finder bad-driver sensitivity low&lt;BR /&gt;fault-finder bad-transceiver sensitivity low&lt;BR /&gt;fault-finder bad-cable sensitivity low&lt;BR /&gt;fault-finder too-long-cable sensitivity low&lt;BR /&gt;fault-finder over-bandwidth sensitivity low&lt;BR /&gt;fault-finder broadcast-storm sensitivity low&lt;BR /&gt;fault-finder loss-of-link sensitivity low&lt;BR /&gt;fault-finder duplex-mismatch-HDx sensitivity low&lt;BR /&gt;fault-finder duplex-mismatch-FDx sensitivity low&lt;BR /&gt;ip route 0.0.0.0 0.0.0.0 192.168.1.2&lt;BR /&gt;no stack&lt;BR /&gt;spanning-tree Trk1 priority 4&lt;BR /&gt;ip ssh version 1-or-2&lt;BR /&gt;password manager&lt;BR /&gt;password operator&lt;BR /&gt;&lt;BR /&gt;TFC2848one# show ip rout&lt;BR /&gt;&lt;BR /&gt;                                IP Route Entries&lt;BR /&gt;&lt;BR /&gt;  Destination        Gateway         VLAN Type      Sub-Type   Metric     Dist.&lt;BR /&gt;  ------------------ --------------- ---- --------- ---------- ---------- -----&lt;BR /&gt;  0.0.0.0/0          192.168.1.2     1    static               1          1&lt;BR /&gt;  127.0.0.0/8        reject               static               0          250&lt;BR /&gt;  127.0.0.1/32       lo0                  connected            0          0&lt;BR /&gt;  192.168.1.0/24     TFC             1    connected            0          0&lt;BR /&gt;  192.168.2.0/24     CORP            2    connected            0          0&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;building #2 switch:&lt;BR /&gt;&lt;BR /&gt;cdp run&lt;BR /&gt;interface 17&lt;BR /&gt;   speed-duplex 100-half&lt;BR /&gt;exit&lt;BR /&gt;interface 45&lt;BR /&gt;   no lacp&lt;BR /&gt;exit&lt;BR /&gt;interface 46&lt;BR /&gt;   no lacp&lt;BR /&gt;exit&lt;BR /&gt;trunk 45-46 Trk1 Trunk&lt;BR /&gt;ip default-gateway 192.168.2.1&lt;BR /&gt;snmp-server community "adex" Unrestricted&lt;BR /&gt;vlan 1&lt;BR /&gt;   name "TFC"&lt;BR /&gt;   ip address 192.168.1.3 255.255.255.0&lt;BR /&gt;   tagged 48&lt;BR /&gt;   no untagged 1-44,47,Trk1&lt;BR /&gt;   exit&lt;BR /&gt;vlan 2&lt;BR /&gt;   name "CORP"&lt;BR /&gt;   untagged 1-44,47,Trk1&lt;BR /&gt;   ip address 192.168.2.3 255.255.255.0&lt;BR /&gt;   tagged 48&lt;BR /&gt;   exit&lt;BR /&gt;no stack&lt;BR /&gt;spanning-tree Trk1 priority 4&lt;BR /&gt;ip ssh version 1-or-2&lt;BR /&gt;password manager&lt;BR /&gt;password operator&lt;BR /&gt;&lt;BR /&gt;corp2848one# show ip route&lt;BR /&gt;&lt;BR /&gt;                                IP Route Entries&lt;BR /&gt;&lt;BR /&gt;  Destination        Gateway         VLAN Type      Sub-Type   Metric     Dist.&lt;BR /&gt;  ------------------ --------------- ---- --------- ---------- ---------- -----&lt;BR /&gt;  0.0.0.0/0          192.168.2.1     2    static               0          250&lt;BR /&gt;  127.0.0.0/8        reject               static               0          250&lt;BR /&gt;  127.0.0.1/32       lo0                  connected            0          0&lt;BR /&gt;  192.168.1.0/24     TFC             1    connected            0          0&lt;BR /&gt;  192.168.2.0/24     CORP            2    connected            0&lt;BR /&gt;</description>
      <pubDate>Tue, 01 Mar 2011 16:48:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/procurve-2848-routing/m-p/4759690#M25459</guid>
      <dc:creator>Mark E Wilson</dc:creator>
      <dc:date>2011-03-01T16:48:00Z</dc:date>
    </item>
    <item>
      <title>Re: Procurve 2848 routing?</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/procurve-2848-routing/m-p/4759691#M25460</link>
      <description>- create the third vlan&lt;BR /&gt;- tag the vlan on the ports that connect the two switches.&lt;BR /&gt;- DON't give the switch that does the routing an ip-adress in this vlan.&lt;BR /&gt;- untag a port in this vlan&lt;BR /&gt;- connect your separate internet router to this port&lt;BR /&gt;- untag ports for this vlan as necessary.&lt;BR /&gt;&lt;BR /&gt;hth &lt;BR /&gt;Pieter</description>
      <pubDate>Thu, 03 Mar 2011 11:08:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/procurve-2848-routing/m-p/4759691#M25460</guid>
      <dc:creator>Pieter 't Hart</dc:creator>
      <dc:date>2011-03-03T11:08:27Z</dc:date>
    </item>
  </channel>
</rss>

