<?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: EAPS Warning: Received Health-Pdu from another Master in ExtremeSwitching (EXOS/Switch Engine)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/eaps-warning-received-health-pdu-from-another-master/m-p/52979#M14795</link>
    <description>This error only occurs when you have configured more than a single Master within an EAPS domain.  You can run: the &lt;B&gt;show eaps&lt;/B&gt; command to see a summary of your EAPS domains, If you have another Master you should see the following output:&lt;BR /&gt;
-----------------------------------------------------------------------&lt;BR /&gt;
Domain  State     Mo  En  Pri    Sec    Control-Vlan VID   Count Prio&lt;BR /&gt;
-----------------------------------------------------------------------&lt;BR /&gt;
dom01   Init  &lt;F&gt; M   Y    1      2     c1_vlan      (100 ) 1     N&lt;BR /&gt;
-----------------------------------------------------------------------Furthermore, an error will be logged every every time a participating nodes receives a second hello packet.  Your EAPS domain will remain in the Initialization state with [Fail timer expired] until you disable the rogue Master and disable it.&lt;BR /&gt;
&lt;BR /&gt;
In your case, that rogue Master is 02:04:96:8F:95:E2 if the switch that's currently logging this error is the known master.  You can then check your forwarding database to see the what switch in your network or within your stack that MAC belongs to.&lt;/F&gt;</description>
    <pubDate>Mon, 01 Jun 2015 13:51:00 GMT</pubDate>
    <dc:creator>Kawawa</dc:creator>
    <dc:date>2015-06-01T13:51:00Z</dc:date>
    <item>
      <title>EAPS Warning: Received Health-Pdu from another Master</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/eaps-warning-received-health-pdu-from-another-master/m-p/52977#M14793</link>
      <description>We have a setup with 3 EAPS domains, one of the domains we had to replace the stack master today, once that was done, the following message is showing up once a second on that stack: &lt;BR /&gt;
&lt;BR /&gt;
05/31/2015 13:06:49.85 &lt;EAPS.RXANOTHERMASTER&gt; Slot-1: EAPSD IDF01 - Received Health-Pdu from another Master (02:04:96:8F:95:E2) on the same domain.&lt;BR /&gt;
Slot 1 used to be the master, it is currently the backup on that stack.  Could that be causing that error message?&lt;BR /&gt;
&lt;BR /&gt;
Everything looks fine from an EAPS standpoint, and its been an hour with no other errors other than that warning, I'm just not a fan of unknown warning messages spamming my logs.&lt;BR /&gt;
&lt;BR /&gt;
This is the 'sh eaps' output from the stack in question: &lt;BR /&gt;
Slot-2 IDF01.4 # sh eaps idf01&lt;BR /&gt;
  Name: IDF01                                   Priority: Normal&lt;BR /&gt;
  State: Complete                               Running: Yes&lt;BR /&gt;
  Enabled: Yes    Mode: Master&lt;BR /&gt;
  Primary port:   6:53          Port status: Up Tag status: Tagged&lt;BR /&gt;
  Secondary port: 1:53          Port status: Blocked    Tag status: Tagged&lt;BR /&gt;
  Hello Egress Port: Primary&lt;BR /&gt;
  Hello timer interval: 1  sec  0  millisec&lt;BR /&gt;
  Fail timer interval:  3  sec  0  millisec&lt;BR /&gt;
  Fail Timer expiry action: Send alert&lt;BR /&gt;
  Last update: From Master Id 02:04:96:8f:95:e2, at Sun May 31 13:14:58 2015&lt;BR /&gt;
  EAPS Domain has following Controller Vlan:&lt;BR /&gt;
    Vlan Name                    VID&lt;BR /&gt;
    c1                           101&lt;BR /&gt;
  EAPS Domain has following Protected Vlan(s):&lt;BR /&gt;
    Vlan Name                    VID&lt;BR /&gt;
    HR                           30&lt;BR /&gt;
    IT                           17&lt;BR /&gt;
    LC                           170&lt;BR /&gt;
    QA                           19&lt;BR /&gt;
    ENG                          18&lt;BR /&gt;
    MFG                          21&lt;BR /&gt;
    CONF                         23&lt;BR /&gt;
    FLEX                         70&lt;BR /&gt;
    VOIP                         80&lt;BR /&gt;
    WIFI                         12&lt;BR /&gt;
    PRINT                        16&lt;BR /&gt;
    OFFICE                       22&lt;BR /&gt;
    REPAIR                       60&lt;BR /&gt;
    APPSENG                      20&lt;BR /&gt;
    CONFDMZ                      24&lt;BR /&gt;
    WIFIDMZ                      26&lt;BR /&gt;
    SecurityCameras              117&lt;BR /&gt;
  Number of Protected Vlans: 17&lt;BR /&gt;
&lt;BR /&gt;&lt;/EAPS.RXANOTHERMASTER&gt;</description>
      <pubDate>Mon, 01 Jun 2015 01:16:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/eaps-warning-received-health-pdu-from-another-master/m-p/52977#M14793</guid>
      <dc:creator>Ron_Prague</dc:creator>
      <dc:date>2015-06-01T01:16:00Z</dc:date>
    </item>
    <item>
      <title>RE: EAPS Warning: Received Health-Pdu from another Master</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/eaps-warning-received-health-pdu-from-another-master/m-p/52978#M14794</link>
      <description>Trace the MAC address of the stack I'm warning message is it of the same stack ?</description>
      <pubDate>Mon, 01 Jun 2015 06:17:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/eaps-warning-received-health-pdu-from-another-master/m-p/52978#M14794</guid>
      <dc:creator>PARTHIBAN_CHINN</dc:creator>
      <dc:date>2015-06-01T06:17:00Z</dc:date>
    </item>
    <item>
      <title>RE: EAPS Warning: Received Health-Pdu from another Master</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/eaps-warning-received-health-pdu-from-another-master/m-p/52979#M14795</link>
      <description>This error only occurs when you have configured more than a single Master within an EAPS domain.  You can run: the &lt;B&gt;show eaps&lt;/B&gt; command to see a summary of your EAPS domains, If you have another Master you should see the following output:&lt;BR /&gt;
-----------------------------------------------------------------------&lt;BR /&gt;
Domain  State     Mo  En  Pri    Sec    Control-Vlan VID   Count Prio&lt;BR /&gt;
-----------------------------------------------------------------------&lt;BR /&gt;
dom01   Init  &lt;F&gt; M   Y    1      2     c1_vlan      (100 ) 1     N&lt;BR /&gt;
-----------------------------------------------------------------------Furthermore, an error will be logged every every time a participating nodes receives a second hello packet.  Your EAPS domain will remain in the Initialization state with [Fail timer expired] until you disable the rogue Master and disable it.&lt;BR /&gt;
&lt;BR /&gt;
In your case, that rogue Master is 02:04:96:8F:95:E2 if the switch that's currently logging this error is the known master.  You can then check your forwarding database to see the what switch in your network or within your stack that MAC belongs to.&lt;/F&gt;</description>
      <pubDate>Mon, 01 Jun 2015 13:51:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/eaps-warning-received-health-pdu-from-another-master/m-p/52979#M14795</guid>
      <dc:creator>Kawawa</dc:creator>
      <dc:date>2015-06-01T13:51:00Z</dc:date>
    </item>
    <item>
      <title>RE: EAPS Warning: Received Health-Pdu from another Master</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/eaps-warning-received-health-pdu-from-another-master/m-p/52980#M14796</link>
      <description>02:04:96:8F:95:E2 is a non-EAPS VLAN ip address on slot 1 of the IDF01 stack.  We use a separate copper drop for SNMP monitoring.&lt;BR /&gt;
VLAN Interface with name NMS created by user&lt;BR /&gt;
    Admin State:         Enabled     Tagging:   802.1Q Tag 4094&lt;BR /&gt;
    Description:         None&lt;BR /&gt;
    Virtual router:      VR-Default&lt;BR /&gt;
    IPv4 Forwarding:     Disabled&lt;BR /&gt;
    IPv4 MC Forwarding:  Disabled&lt;BR /&gt;
    Primary IP:          172.16.25.13/24&lt;BR /&gt;
    IPv6 Forwarding:     Disabled&lt;BR /&gt;
    IPv6 MC Forwarding:  Disabled&lt;BR /&gt;
    IPv6:                None&lt;BR /&gt;
    STPD:                None&lt;BR /&gt;
    Protocol:            Match all unfiltered protocols&lt;BR /&gt;
    Loopback:            Disabled&lt;BR /&gt;
    NetLogin:            Disabled&lt;BR /&gt;
    OpenFlow:            Disabled&lt;BR /&gt;
    TRILL:               Disabled&lt;BR /&gt;
    QosProfile:          None configured&lt;BR /&gt;
    Egress Rate Limit Designated Port: None configured&lt;BR /&gt;
    Flood Rate Limit QosProfile:       None configured&lt;BR /&gt;
    Ports:   3.           (Number of active ports=2)&lt;BR /&gt;
       Untag:   *1:49,  *6:51,   6:52&lt;BR /&gt;
  &lt;BR /&gt;
Stack Topology is a Ring&lt;BR /&gt;
Node MAC Address    Slot  Stack State  Role     Flags&lt;BR /&gt;
------------------  ----  -----------  -------  ---&lt;BR /&gt;
*00:04:96:8f:96:3f  2     Active       Master   CA-&lt;BR /&gt;
 00:04:96:8f:96:5a  3     Active       Standby  CA-&lt;BR /&gt;
 00:04:96:8f:d2:4f  4     Active       Standby  CA-&lt;BR /&gt;
 00:04:96:8f:96:40  5     Active       Standby  CA-&lt;BR /&gt;
 00:04:96:8f:96:4f  6     Active       Standby  CA-&lt;BR /&gt;
 00:04:96:8f:b3:1e  1     Active       Backup   CA-&lt;BR /&gt;
* - Indicates this node&lt;BR /&gt;
Flags:  (C) Candidate for this active topology, (A) Active Node&lt;BR /&gt;
        (O) node may be in Other active topology &lt;BR /&gt;
  &lt;BR /&gt;
The stack has 2x10GB fiber top and bottom that are the EAPS ports, 1:53 secondary, 6:53 primary.&lt;BR /&gt;
&lt;BR /&gt;
Slot 1 in this stack has a copper Gbic in port 1:49 untagged in the NMS vlan which is not protected via EAPS or the control vlan.&lt;BR /&gt;
This is the same exact configuration we had prior to the top of stack switch changeout we did this weekend.  The only difference in the stack right now is that slot 1 is the backup and slot 2 is the master. (And the same configuration on our other two EAPS domains)&lt;BR /&gt;
&lt;BR /&gt;
Why would a non-EAPS, non-control vlan be advertising EAPS information, and what can I do to fix that?&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Mon, 01 Jun 2015 21:49:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/eaps-warning-received-health-pdu-from-another-master/m-p/52980#M14796</guid>
      <dc:creator>Ron_Prague</dc:creator>
      <dc:date>2015-06-01T21:49:00Z</dc:date>
    </item>
    <item>
      <title>RE: EAPS Warning: Received Health-Pdu from another Master</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/eaps-warning-received-health-pdu-from-another-master/m-p/52981#M14797</link>
      <description>When you create a stack the stack will use a mac address 02:04:96.xxx which is in fact just the masters mac address starting with 02 instead of 00. This is the stack mac address which will stay the same even if the backup takes over from the master or if the master slot is removed.&lt;BR /&gt;
However for this to work the stack mac address must be configured right and sometimes when adding nodes to a stack this must be re-configured on these new stack units. &lt;BR /&gt;
I think the new master slot did not have the stack mac address configured so when the backup slot took over the stack started using a different mac address. The other switches in the ring detected the eaps master   changed its mac address and started to log this event.&lt;BR /&gt;
To correct this from happening again you must ensure the stack mac address is configured right.&lt;BR /&gt;
You can do this using the command "configure stacking mac-addresss"&lt;BR /&gt;
&lt;BR /&gt;
&lt;A href="http://documentation.extremenetworks.com/exos_commands/EXOS_All/EXOS_Commands_All/r_configure-stacking-macaddress.shtml" target="_blank" rel="nofollow noreferrer noopener"&gt;http://documentation.extremenetworks.com/exos_commands/EXOS_All/EXOS_Commands_All/r_configure-stacki...&lt;/A&gt;&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Tue, 02 Jun 2015 13:35:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/eaps-warning-received-health-pdu-from-another-master/m-p/52981#M14797</guid>
      <dc:creator>OscarK</dc:creator>
      <dc:date>2015-06-02T13:35:00Z</dc:date>
    </item>
  </channel>
</rss>

