<?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: Sys Logging to PCM in Switches, Hubs, and Modems</title>
    <link>https://community.hpe.com/t5/switches-hubs-and-modems/sys-logging-to-pcm/m-p/4302372#M16487</link>
    <description>I've rediscovered the switch via its loopback interface but still no syslogs unfortunately.</description>
    <pubDate>Thu, 13 Nov 2008 16:44:18 GMT</pubDate>
    <dc:creator>Jason Scott</dc:creator>
    <dc:date>2008-11-13T16:44:18Z</dc:date>
    <item>
      <title>Sys Logging to PCM</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/sys-logging-to-pcm/m-p/4302367#M16482</link>
      <description>We have 3 8200 switches that I'd like to enable sys logging on to PCM. I've added the logging x.x.x.x command but nothing is showing in PCM (it works for other 5300 switches). I believe, because we have many routed vlans configured, the sys logs are originating from an address other than the one configured in PCM. &lt;BR /&gt;&lt;BR /&gt;Is there any way to configure a source ip address for sys log messages?</description>
      <pubDate>Fri, 07 Nov 2008 14:03:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/sys-logging-to-pcm/m-p/4302367#M16482</guid>
      <dc:creator>Jason Scott</dc:creator>
      <dc:date>2008-11-07T14:03:47Z</dc:date>
    </item>
    <item>
      <title>Re: Sys Logging to PCM</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/sys-logging-to-pcm/m-p/4302368#M16483</link>
      <description>Edit: I've seen in the main PCM logs, sys log messages coming from the loopback address configured on the 8200s, so that answers part of the question. However I would still prefer to have messages coming from our vlan 1 address.</description>
      <pubDate>Fri, 07 Nov 2008 15:43:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/sys-logging-to-pcm/m-p/4302368#M16483</guid>
      <dc:creator>Jason Scott</dc:creator>
      <dc:date>2008-11-07T15:43:59Z</dc:date>
    </item>
    <item>
      <title>Re: Sys Logging to PCM</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/sys-logging-to-pcm/m-p/4302369#M16484</link>
      <description>That's great if they're coming from the loopback address. Can you delete the switch from PCM and rediscover it by it's loopback address instead? I believe the syslog data will start to show then.</description>
      <pubDate>Sat, 08 Nov 2008 01:45:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/sys-logging-to-pcm/m-p/4302369#M16484</guid>
      <dc:creator>Matt Hobbs</dc:creator>
      <dc:date>2008-11-08T01:45:09Z</dc:date>
    </item>
    <item>
      <title>Re: Sys Logging to PCM</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/sys-logging-to-pcm/m-p/4302370#M16485</link>
      <description>the router default uses i'ts fist interface that's "up" as router id.&lt;BR /&gt;A loopback-interface is allways up.&lt;BR /&gt;you can manually issue a&lt;BR /&gt;   ip router-id IP-ADDR&lt;BR /&gt;command to change the default behaviour.&lt;BR /&gt;I think this will also be used for sending syslog messages.</description>
      <pubDate>Mon, 10 Nov 2008 08:50:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/sys-logging-to-pcm/m-p/4302370#M16485</guid>
      <dc:creator>Pieter 't Hart</dc:creator>
      <dc:date>2008-11-10T08:50:15Z</dc:date>
    </item>
    <item>
      <title>Re: Sys Logging to PCM</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/sys-logging-to-pcm/m-p/4302371#M16486</link>
      <description>Thank you both, I'll try those suggestions. All our switches and routers use vlan 1 for management (10.5.1.x) whereas our loopback is 10.240.240.1. I'd like to maintain the vlan 1 map if possible.&lt;BR /&gt;&lt;BR /&gt;We also have OSPF running so I'm slightly cautious about changing the router ID. Testing required I think :)</description>
      <pubDate>Mon, 10 Nov 2008 08:55:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/sys-logging-to-pcm/m-p/4302371#M16486</guid>
      <dc:creator>Jason Scott</dc:creator>
      <dc:date>2008-11-10T08:55:52Z</dc:date>
    </item>
    <item>
      <title>Re: Sys Logging to PCM</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/sys-logging-to-pcm/m-p/4302372#M16487</link>
      <description>I've rediscovered the switch via its loopback interface but still no syslogs unfortunately.</description>
      <pubDate>Thu, 13 Nov 2008 16:44:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/sys-logging-to-pcm/m-p/4302372#M16487</guid>
      <dc:creator>Jason Scott</dc:creator>
      <dc:date>2008-11-13T16:44:18Z</dc:date>
    </item>
  </channel>
</rss>

