OPNsense
  • Home
  • Help
  • Search
  • Login
  • Register

  • OPNsense Forum »
  • International Forums »
  • German - Deutsch »
  • CARP Problem
« previous next »
  • Print
Pages: 1 2 [3]

Author Topic: CARP Problem  (Read 17675 times)

Sven-J

  • Newbie
  • *
  • Posts: 47
  • Karma: 1
    • View Profile
Re: CARP Problem
« Reply #30 on: February 22, 2019, 10:04:32 am »
Quote from: mimugmail on February 22, 2019, 09:53:22 am
Du hast doch im Post oben von allen Maschinen und Interfaces tcpdumps gemacht .. jetzt müsste man nur noch wissen welche Firewall welche IPs hat, dann kommt man dem vielleicht näher

Moin,

FW01 -> 251 / xxx.xxx.142.179
FW02 -> 252 / xxx.xxx.142.180
CARP -> 254 / xxx.xxx.142.178


Viele Grüße
Sven
Logged

mimugmail

  • Hero Member
  • *****
  • Posts: 6766
  • Karma: 494
    • View Profile
Re: CARP Problem
« Reply #31 on: February 22, 2019, 12:28:02 pm »
<DEHAM01-CORE-01>display interface Bridge-Aggregation 4
Bridge-Aggregation4
Current state: UP
IP packet frame type: Ethernet II, hardware address: 5c8a-3850-2335
Description: LACP-FW-2-trunk
Bandwidth: 20000000 kbps
20Gbps-speed mode, full-duplex mode
Link speed type is autonegotiation, link duplex type is autonegotiation
PVID: 3
Port link-type: Trunk
 VLAN Passing:   3, 10, 40, 42-44, 47, 150, 500-506, 547, 551-552, 1000-1003, 1011, 1020, 1150, 4000-4001
 VLAN permitted: 3, 10, 40-4094
 Trunk port encapsulation: IEEE 802.1q
Last clearing of counters: Never
Last 300 seconds input:  0 packets/sec 126 bytes/sec 0%
Last 300 seconds output:  12 packets/sec 2172 bytes/sec 0%
Input (total):  2361306 packets, 2234309304 bytes
        1517489 unicasts, 1323 broadcasts, 842494 multicasts, 0 pauses
Input (normal):  2361306 packets, - bytes
        1517489 unicasts, 1323 broadcasts, 842494 multicasts, 0 pauses
Input:  0 input errors, 0 runts, 0 giants, 0 throttles
        0 CRC, 0 frame, - overruns, 0 aborts
        - ignored, - parity errors
Output (total): 5115311 packets, 1190861340 bytes
        776382 unicasts, 141679 broadcasts, 4197250 multicasts, 0 pauses
Output (normal): 5115311 packets, - bytes
        776382 unicasts, 141679 broadcasts, 4197250 multicasts, 0 pauses
Output: 0 output errors, - underruns, - buffer failures
        0 aborts, 0 deferred, 0 collisions, 0 late collisions
        0 lost carrier, - no carrier




Wie hast du der OPNsense beigebracht das native VLAN 3 ist? die LACP's von FW1 und FW2 unterscheiden sich ...
Logged
WWW: www.routerperformance.net
Support plans: https://www.max-it.de/en/it-services/opnsense/
Commercial Plugins (German): https://opnsense.max-it.de/

Sven-J

  • Newbie
  • *
  • Posts: 47
  • Karma: 1
    • View Profile
Re: CARP Problem
« Reply #32 on: February 22, 2019, 12:34:19 pm »
Vlan 3 wird nicht benutzt ist nur für Security Reasons auf jedem Port. Die Firewall benutzt ab vlan10 aufwärts.

Gesendet von meinem SM-N950F mit Tapatalk

Logged

mimugmail

  • Hero Member
  • *****
  • Posts: 6766
  • Karma: 494
    • View Profile
Re: CARP Problem
« Reply #33 on: February 22, 2019, 12:41:31 pm »
<DEHAM01-CORE-01>display interface Bridge-Aggregation 2
PVID: 1
Port link-type: Trunk
 VLAN Passing:   1(default vlan), 10, 40, 42-44, 47, 150, 500-506, 547, 551-552, 1000-1003, 1011, 1020, 1150, 4000-4001
 VLAN permitted: 1(default vlan), 10, 40-4094

<DEHAM01-CORE-01>display interface Bridge-Aggregation 4
PVID: 3
Port link-type: Trunk
 VLAN Passing:   3, 10, 40, 42-44, 47, 150, 500-506, 547, 551-552, 1000-1003, 1011, 1020, 1150, 4000-4001
 VLAN permitted: 3, 10, 40-4094

Ich verstehe nicht wieso BA2 und BA4 nicht identisch konfiguriert sind, was ist da der Hintergrund?
Logged
WWW: www.routerperformance.net
Support plans: https://www.max-it.de/en/it-services/opnsense/
Commercial Plugins (German): https://opnsense.max-it.de/

Wurzlsepp

  • Newbie
  • *
  • Posts: 2
  • Karma: 0
    • View Profile
Re: CARP Problem
« Reply #34 on: February 23, 2019, 05:18:19 pm »
Moin,

B2 und B4 sind nicht gleich weil der Switch-Admin einen Fehler gemacht hat.
Das Problem ist dennoch B4 und nicht etwa CARP in meinen Augen. Die Opnsense Box registriert die LACP Lakete des Switch möglicherweise nicht oder wir haben ein Übertragungsproblem (Layer 1). Dagegen spricht aber dass der Link auf Failover scheinbar funktioniert.
Siehe Status der BAs auf dem System:
<DEHAM01-CORE-01>display link-aggregation verbose Bridge-Aggregation 1
Loadsharing Type: Shar -- Loadsharing, NonS -- Non-Loadsharing
Port Status: S -- Selected, U -- Unselected, 
             I -- Individual, * -- Management port
Flags:  A -- LACP_Activity, B -- LACP_Timeout, C -- Aggregation,
        D -- Synchronization, E -- Collecting, F -- Distributing,
        G -- Defaulted, H -- Expired

Aggregate Interface: Bridge-Aggregation1
Aggregation Mode: Dynamic
Loadsharing Type: Shar
Management VLAN : None
System ID: 0x8000, 5c8a-3850-22ef
Local:
  Port             Status  Priority Oper-Key  Flag
--------------------------------------------------------------------------------
  XGE1/0/27        S       32768    5         {ACDEF}
  XGE2/0/27        S       32768    5         {ACDEF}
Remote:
  Actor            Partner Priority Oper-Key  SystemID               Flag   
--------------------------------------------------------------------------------
  XGE1/0/27        3       32768    427       0x8000, 2c76-8a54-2530 {ACDEF}
  XGE2/0/27        4       32768    427       0x8000, 2c76-8a54-2530 {ACDEF}
<DEHAM01-CORE-01>display link-aggregation verbose Bridge-Aggregation 12
                                                                     ^
 % Wrong parameter found at '^' position.
<DEHAM01-CORE-01>display link-aggregation verbose Bridge-Aggregation 2
Loadsharing Type: Shar -- Loadsharing, NonS -- Non-Loadsharing
Port Status: S -- Selected, U -- Unselected, 
             I -- Individual, * -- Management port
Flags:  A -- LACP_Activity, B -- LACP_Timeout, C -- Aggregation,
        D -- Synchronization, E -- Collecting, F -- Distributing,
        G -- Defaulted, H -- Expired

Aggregate Interface: Bridge-Aggregation2
Aggregation Mode: Dynamic
Loadsharing Type: Shar
Management VLAN : None
System ID: 0x8000, 5c8a-3850-22ef
Local:
  Port             Status  Priority Oper-Key  Flag
--------------------------------------------------------------------------------
  XGE1/0/28        S       32768    4         {ACDEF}
  XGE2/0/28        S       32768    4         {ACDEF}
Remote:
  Actor            Partner Priority Oper-Key  SystemID               Flag   
--------------------------------------------------------------------------------
  XGE1/0/28        1       32768    466       0x8000, 5cb9-01d7-8348 {ACDEF}
  XGE2/0/28        2       32768    466       0x8000, 5cb9-01d7-8348 {ACDEF}
<DEHAM01-CORE-01>display link-aggregation verbose Bridge-Aggregation 3
Loadsharing Type: Shar -- Loadsharing, NonS -- Non-Loadsharing
Port Status: S -- Selected, U -- Unselected, 
             I -- Individual, * -- Management port
Flags:  A -- LACP_Activity, B -- LACP_Timeout, C -- Aggregation,
        D -- Synchronization, E -- Collecting, F -- Distributing,
        G -- Defaulted, H -- Expired

Aggregate Interface: Bridge-Aggregation3
Aggregation Mode: Dynamic
Loadsharing Type: Shar
Management VLAN : None
System ID: 0x8000, 5c8a-3850-22ef
Local:
  Port             Status  Priority Oper-Key  Flag
--------------------------------------------------------------------------------
  XGE1/0/29        S       32768    7         {ACDEF}
  XGE2/0/29        S       32768    7         {ACDEF}
Remote:
  Actor            Partner Priority Oper-Key  SystemID               Flag   
--------------------------------------------------------------------------------
  XGE1/0/29        3       32768    427       0x8000, ac16-2d8c-0b14 {ACDEF}
  XGE2/0/29        4       32768    427       0x8000, ac16-2d8c-0b14 {ACDEF}
<DEHAM01-CORE-01>display link-aggregation verbose Bridge-Aggregation 4
Loadsharing Type: Shar -- Loadsharing, NonS -- Non-Loadsharing
Port Status: S -- Selected, U -- Unselected, 
             I -- Individual, * -- Management port
Flags:  A -- LACP_Activity, B -- LACP_Timeout, C -- Aggregation,
        D -- Synchronization, E -- Collecting, F -- Distributing,
        G -- Defaulted, H -- Expired

Aggregate Interface: Bridge-Aggregation4
Aggregation Mode: Dynamic
Loadsharing Type: Shar
Management VLAN : None
System ID: 0x8000, 5c8a-3850-22ef
Local:
  Port             Status  Priority Oper-Key  Flag
--------------------------------------------------------------------------------
  XGE1/0/30        U       32768    6         {ABCG}
  XGE2/0/30        U       32768    6         {ACD}
Remote:
  Actor            Partner Priority Oper-Key  SystemID               Flag   
--------------------------------------------------------------------------------
  XGE1/0/30        0       32768    0         0x8000, 0000-0000-0000 {DEF}
  XGE2/0/30        2       32768    466       0x8000, 2c76-8a5c-f8f0 {ACG}
Logged

Wurzlsepp

  • Newbie
  • *
  • Posts: 2
  • Karma: 0
    • View Profile
Re: CARP Problem
« Reply #35 on: February 24, 2019, 11:02:01 pm »
So, Rätsel etwas entwirrt.
Firmware Update auf der 10Gbit Karte
LACP geht
FW02 nun überall Backup. FW01 Master.
Sieht soweit gut aus, wir beobachten weiter.
Logged

mimugmail

  • Hero Member
  • *****
  • Posts: 6766
  • Karma: 494
    • View Profile
Re: CARP Problem
« Reply #36 on: February 25, 2019, 06:51:55 am »
Super, das war mir auch neu. Aber du bist jetzt nicht der der den Thread erstellt oder?
Logged
WWW: www.routerperformance.net
Support plans: https://www.max-it.de/en/it-services/opnsense/
Commercial Plugins (German): https://opnsense.max-it.de/

Sven-J

  • Newbie
  • *
  • Posts: 47
  • Karma: 1
    • View Profile
Re: CARP Problem
« Reply #37 on: February 25, 2019, 06:53:35 am »
Quote from: mimugmail on February 25, 2019, 06:51:55 am
Super, das war mir auch neu. Aber du bist jetzt nicht der der den Thread erstellt oder?
Nein er ist mein Super Netzwerker :)

Gesendet von meinem SM-N950F mit Tapatalk

Logged

rainerle

  • Full Member
  • ***
  • Posts: 151
  • Karma: 9
    • View Profile
Re: CARP Problem
« Reply #38 on: February 28, 2019, 05:30:45 pm »
Hallo zusammen,

ich hatte mit meiner Installation das gleiche Problem. Als dieser Thread durchlief, hab' ich auch die Firmware bei meinen Netzwerkkarten upgedated.

Jetzt läuft das. Die Büchsen wurden 10/2018 ausgeliefert, die Firmware auf den Karten war aber schon etwas älter...

Besten Gruß und Dank!
Rainer

 
Logged
  • Print
Pages: 1 2 [3]
« previous next »
  • OPNsense Forum »
  • International Forums »
  • German - Deutsch »
  • CARP Problem
 

OPNsense is an OSS project © Deciso B.V. 2015 - 2024 All rights reserved
  • SMF 2.0.19 | SMF © 2021, Simple Machines
    Privacy Policy     | XHTML | RSS | WAP2