<?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 Re: Core Switch IP Static Route question in Switches, Hubs, and Modems</title>
    <link>https://community.hpe.com/t5/switches-hubs-and-modems/core-switch-ip-static-route-question/m-p/7078584#M34161</link>
    <description>&lt;P&gt;Hi! could you please post the output of the &lt;FONT color="#0000FF"&gt;show ip route static&lt;/FONT&gt; CLI command? that output is necessary to understand the metric and distance values [*] associated with the two standard static routes manually added on your ProCurve switch (case of same destination networks through different next-hop gateways).&lt;/P&gt;&lt;P&gt;[*] multiple standard static routes can be configured with the same metric to obtain Load Sharing or with different metrics to provide a Primary Route and one or more Backup Routes.&lt;/P&gt;</description>
    <pubDate>Mon, 10 Feb 2020 20:38:50 GMT</pubDate>
    <dc:creator>parnassus</dc:creator>
    <dc:date>2020-02-10T20:38:50Z</dc:date>
    <item>
      <title>Core Switch IP Static Route question</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/core-switch-ip-static-route-question/m-p/7078576#M34160</link>
      <description>&lt;P&gt;Hi, What is the implications of having duplicate static routes setup pointing to different IPs?&lt;/P&gt;&lt;P&gt;ip route 192.168.30.0 255.255.255.0 192.168.4.5&amp;nbsp; -&amp;nbsp; The site FW/Edge Switch&lt;BR /&gt;ip route 192.168.30.0 255.255.255.0 192.168.220.1&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have this configured on our core HP Pro curve&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 10 Feb 2020 19:11:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/core-switch-ip-static-route-question/m-p/7078576#M34160</guid>
      <dc:creator>fakiee</dc:creator>
      <dc:date>2020-02-10T19:11:47Z</dc:date>
    </item>
    <item>
      <title>Re: Core Switch IP Static Route question</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/core-switch-ip-static-route-question/m-p/7078584#M34161</link>
      <description>&lt;P&gt;Hi! could you please post the output of the &lt;FONT color="#0000FF"&gt;show ip route static&lt;/FONT&gt; CLI command? that output is necessary to understand the metric and distance values [*] associated with the two standard static routes manually added on your ProCurve switch (case of same destination networks through different next-hop gateways).&lt;/P&gt;&lt;P&gt;[*] multiple standard static routes can be configured with the same metric to obtain Load Sharing or with different metrics to provide a Primary Route and one or more Backup Routes.&lt;/P&gt;</description>
      <pubDate>Mon, 10 Feb 2020 20:38:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/core-switch-ip-static-route-question/m-p/7078584#M34161</guid>
      <dc:creator>parnassus</dc:creator>
      <dc:date>2020-02-10T20:38:50Z</dc:date>
    </item>
    <item>
      <title>Re: Core Switch IP Static Route question</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/core-switch-ip-static-route-question/m-p/7078687#M34164</link>
      <description>&lt;P&gt;IP Route Entries&lt;/P&gt;&lt;P&gt;Destination Gateway VLAN Type Sub-Type Metric Dist.&lt;BR /&gt;------------------ --------------- ---- --------- ---------- ---------- -----&lt;BR /&gt;0.0.0.0/0 192.168.4.5 199 static 1 1&lt;BR /&gt;10.0.55.0/24 192.168.4.5 199 static 1 1&lt;BR /&gt;10.0.101.0/24 192.168.4.5 199 static 1 1&lt;BR /&gt;10.2.0.0/16 192.168.220.1 220 static 1 1&lt;BR /&gt;10.3.0.0/16 192.168.220.1 220 static 1 1&lt;BR /&gt;10.5.0.0/21 192.168.4.5 199 static 1 1&lt;BR /&gt;10.7.0.0/24 192.168.4.5 199 static 1 1&lt;BR /&gt;10.8.12.0/24 192.168.4.5 199 static 1 1&lt;BR /&gt;10.8.20.0/24 192.168.4.5 199 static 1 1&lt;BR /&gt;10.9.1.0/24 192.168.4.5 199 static 1 1&lt;BR /&gt;10.10.1.0/24 192.168.4.5 199 static 1 1&lt;BR /&gt;10.11.0.0/16 192.168.4.5 199 static 1 1&lt;BR /&gt;10.12.0.0/16 192.168.4.5 199 static 1 1&lt;BR /&gt;10.14.1.0/24 192.168.4.5 199 static 1 1&lt;BR /&gt;10.17.0.0/16 192.168.4.5 199 static 1 1&lt;BR /&gt;10.41.0.0/16 192.168.4.5 199 static 1 1&lt;BR /&gt;10.70.0.0/16 192.168.4.5 199 static 1 1&lt;BR /&gt;10.80.0.0/24 192.168.4.5 199 static 1 1&lt;BR /&gt;10.90.0.0/16 192.168.4.5 199 static 1 1&lt;BR /&gt;10.91.0.0/16 192.168.4.5 199 static 1 1&lt;BR /&gt;10.100.8.0/24 192.168.4.5 199 static 1 1&lt;BR /&gt;10.101.0.0/16 192.168.4.5 199 static 1 1&lt;BR /&gt;10.241.0.0/16 192.168.4.5 199 static 1 1&lt;BR /&gt;127.0.0.0/8 reject static 0 0&lt;BR /&gt;192.168.0.0/22 192.168.4.5 199 static 1 1&lt;BR /&gt;192.168.6.0/24 192.168.4.5 199 static 1 1&lt;BR /&gt;192.168.10.0/23 192.168.4.5 199 static 1 1&lt;BR /&gt;192.168.26.0/23 192.168.4.5 199 static 1 1&lt;BR /&gt;192.168.30.0/24 192.168.4.5 199 static 1 1&lt;BR /&gt;192.168.30.0/24 192.168.220.1 220 static 1 1&lt;BR /&gt;192.168.31.0/24 192.168.4.5 199 static 1 1&lt;BR /&gt;192.168.41.0/24 192.168.4.5 199 static 1 1&lt;BR /&gt;192.168.52.0/24 192.168.4.5 199 static 1 1&lt;BR /&gt;192.168.60.0/23 192.168.4.5 199 static 1 1&lt;BR /&gt;192.168.62.0/24 192.168.4.5 199 static 1 1&lt;BR /&gt;192.168.70.0/24 192.168.4.5 199 static 1 1&lt;BR /&gt;192.168.90.0/24 192.168.4.5 199 static 1 1&lt;BR /&gt;192.168.91.0/24 192.168.4.5 199 static 1 1&lt;BR /&gt;192.168.99.0/24 192.168.4.5 199 static 1 1&lt;BR /&gt;192.168.112.0/22 192.168.4.5 199 static 1 1&lt;BR /&gt;192.168.136.0/22 192.168.4.5 199 static 1 1&lt;BR /&gt;192.168.168.0/22 192.168.4.5 199 static 1 1&lt;/P&gt;</description>
      <pubDate>Tue, 11 Feb 2020 12:24:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/core-switch-ip-static-route-question/m-p/7078687#M34164</guid>
      <dc:creator>fakiee</dc:creator>
      <dc:date>2020-02-11T12:24:34Z</dc:date>
    </item>
  </channel>
</rss>

