OSPF Problem mit IBM z/OS 2.5

Forum zu aktuellen Geräten der LANCOM Router/Gateway Serie

Moderator: Lancom-Systems Moderatoren

Antworten
Henri
Beiträge: 401
Registriert: 23 Jul 2005, 01:42

OSPF Problem mit IBM z/OS 2.5

Beitrag von Henri »

Hallo,

wir haben ein Problem mit OSPF zwischen einen ISG-4000 (10.50.0953RU8) und IBM z/OS 2.5.

Hier der Fehler, kann mir jemand weiterhelfen?

Danke und Mit vielen Grüßen

Henri

https://www.ibm.com/support/pages/mustg ... ons-server

Sequence number mismatch OMPROUTE received a sequence number mismatch in a database descriptor packet. A neighbor might be attempting to restart the adjacency for some reason, resulting in sequence number mismatches. This event indicates that the neighbor was not receiving hello packets from OMPROUTE, experienced event 12 on its side, and is trying to restart.

[OSPF-Packet] 2022/07/20 16:46:30,131 : Packet [DB Description from: ID: 172.20.20.142, IP: 172.20.20.42] received on:
VLAN20_SERVER state: (dr) IP: 172.20.20.5/255.255.255.0 MTU: 1500 DR: 172.20.20.5 BDR: 172.20.20.42
[OSPF-Neighbor] 2022/07/20 16:46:30,131 : Neighbor 172.20.20.142 1 EX_START DRBackup 34.988s 172.20.20.42 0 0 0 is now MASTER
[OSPF-Neighbor] 2022/07/20 16:46:30,131 : Neighbor 172.20.20.142 1 EX_START DRBackup 34.988s 172.20.20.42 0 0 0 event: negotiation done
[OSPF-Neighbor] 2022/07/20 16:46:30,131 : Neighbor 172.20.20.142 1 EX_START DRBackup 34.988s 172.20.20.42 0 0 0 ->EXCHANGE
[OSPF-Neighbor] 2022/07/20 16:46:30,131 : Neighbor 172.20.20.142 1 EXCHANGE DRBackup 34.988s 172.20.20.42 0 0 13 SLAVE send DB description packet
[OSPF-Packet] 2022/07/20 16:46:31,134 : Packet [DB Description from: ID: 172.20.20.142, IP: 172.20.20.42] received on:
VLAN20_SERVER state: (dr) IP: 172.20.20.5/255.255.255.0 MTU: 1500 DR: 172.20.20.5 BDR: 172.20.20.42
[OSPF-Neighbor] 2022/07/20 16:46:31,134 : Neighbor 172.20.20.142 1 EXCHANGE DRBackup 33.985s 172.20.20.42 0 0 0 event: seq number mismatch
[OSPF-Neighbor] 2022/07/20 16:46:31,134 : Neighbor 172.20.20.142 1 EXCHANGE DRBackup 33.985s 172.20.20.42 0 0 0 ->EX START
[OSPF-Expert] 2022/07/20 16:46:25,563 : DD2 DD2 DD2 DD2 DD2 DD51 DD52 PD_MS0 PD_M0 DD2 DDPD0 DD61 DD63 CRL CRL DDC
[OSPF-Expert] 2022/07/20 16:46:31,134 : DDD
[OSPF-Neighbor] 2022/07/20 16:46:31,134 : Neighbor 172.20.20.142 1 EX_START DRBackup 33.985s 172.20.20.42 0 0 0 send DD negotiation packet
[OSPF-Packet] 2022/07/20 16:46:35,143 : Packet [Hello from: ID: 172.20.20.142, IP: 172.20.20.42] received on:
VLAN20_SERVER state: (dr) IP: 172.20.20.5/255.255.255.0 MTU: 1500 DR: 172.20.20.5 BDR: 172.20.20.42
[OSPF-Neighbor] 2022/07/20 16:46:35,143 : Neighbor 172.20.20.142 1 EX_START DRBackup 39.999s 172.20.20.42 0 0 0 event: two way received
[OSPF-Packet] 2022/07/20 16:46:36,144 : Packet [DB Description from: ID: 172.20.20.142, IP: 172.20.20.42] received on:
VLAN20_SERVER state: (dr) IP: 172.20.20.5/255.255.255.0 MTU: 1500 DR: 172.20.20.5 BDR: 172.20.20.42
[OSPF-Neighbor] 2022/07/20 16:46:36,144 : Neighbor 172.20.20.142 1 EX_START DRBackup 38.999s 172.20.20.42 0 0 0 is now MASTER
[OSPF-Neighbor] 2022/07/20 16:46:36,144 : Neighbor 172.20.20.142 1 EX_START DRBackup 38.999s 172.20.20.42 0 0 0 event: negotiation done
[OSPF-Neighbor] 2022/07/20 16:46:36,144 : Neighbor 172.20.20.142 1 EX_START DRBackup 38.999s 172.20.20.42 0 0 0 ->EXCHANGE
[OSPF-Neighbor] 2022/07/20 16:46:36,144 : Neighbor 172.20.20.142 1 EXCHANGE DRBackup 38.999s 172.20.20.42 0 0 13 SLAVE send DB description packet
[OSPF-Packet] 2022/07/20 16:46:37,146 : Packet [DB Description from: ID: 172.20.20.142, IP: 172.20.20.42] received on:
VLAN20_SERVER state: (dr) IP: 172.20.20.5/255.255.255.0 MTU: 1500 DR: 172.20.20.5 BDR: 172.20.20.42
[OSPF-Neighbor] 2022/07/20 16:46:37,146 : Neighbor 172.20.20.142 1 EXCHANGE DRBackup 37.996s 172.20.20.42 0 0 0 event: seq number mismatch
[OSPF-Neighbor] 2022/07/20 16:46:37,146 : Neighbor 172.20.20.142 1 EXCHANGE DRBackup 37.996s 172.20.20.42 0 0 0 ->EX START
[OSPF-Expert] 2022/07/20 16:46:31,563 : DD2 DD2 DD2 DD2 DD2 DD51 DD52 PD_MS0 PD_M0 DD2 DDPD0 DD61 DD63 CRL CRL DDC
[OSPF-Expert] 2022/07/20 16:46:37,146 : DDD
[OSPF-Neighbor] 2022/07/20 16:46:37,146 : Neighbor 172.20.20.142 1 EX_START DRBackup 37.996s 172.20.20.42 0 0 0 send DD negotiation packet
[OSPF-Packet] 2022/07/20 16:46:42,158 : Packet [DB Description from: ID: 172.20.20.142, IP: 172.20.20.42] received on:
VLAN20_SERVER state: (dr) IP: 172.20.20.5/255.255.255.0 MTU: 1500 DR: 172.20.20.5 BDR: 172.20.20.42
[OSPF-Neighbor] 2022/07/20 16:46:42,158 : Neighbor 172.20.20.142 1 EX_START DRBackup 32.985s 172.20.20.42 0 0 0 is now MASTER
[OSPF-Neighbor] 2022/07/20 16:46:42,158 : Neighbor 172.20.20.142 1 EX_START DRBackup 32.985s 172.20.20.42 0 0 0 event: negotiation done
[OSPF-Neighbor] 2022/07/20 16:46:42,158 : Neighbor 172.20.20.142 1 EX_START DRBackup 32.985s 172.20.20.42 0 0 0 ->EXCHANGE
[OSPF-Neighbor] 2022/07/20 16:46:42,158 : Neighbor 172.20.20.142 1 EXCHANGE DRBackup 32.985s 172.20.20.42 0 0 13 SLAVE send DB description packet
[OSPF-Packet] 2022/07/20 16:46:43,161 : Packet [DB Description from: ID: 172.20.20.142, IP: 172.20.20.42] received on:
VLAN20_SERVER state: (dr) IP: 172.20.20.5/255.255.255.0 MTU: 1500 DR: 172.20.20.5 BDR: 172.20.20.42
[OSPF-Neighbor] 2022/07/20 16:46:43,161 : Neighbor 172.20.20.142 1 EXCHANGE DRBackup 31.981s 172.20.20.42 0 0 0 event: seq number mismatch
[OSPF-Neighbor] 2022/07/20 16:46:43,161 : Neighbor 172.20.20.142 1 EXCHANGE DRBackup 31.981s 172.20.20.42 0 0 0 ->EX START
[OSPF-Expert] 2022/07/20 16:46:37,563 : DD2 DD2 DD2 DD2 DD2 DD51 DD52 PD_MS0 PD_M0 DD2 DDPD0 DD61 DD63 CRL CRL DDC
[OSPF-Expert] 2022/07/20 16:46:43,161 : DDD


07/20 16:46:31 Trace levels active: -t2 -d1 -6t0 -6d0 -s0
07/20 16:46:31 ODAT at storage location: 20207708
07/20 16:46:33 EZZ7910I Sending multicast, type 1, destination 224.0.0.5 net 2 interface ETH2
07/20 16:46:33 EZZ7876I -- OSPF Packet Sent ------ Type: Hello
07/20 16:46:33 EZZ7878I OSPF Version: 2 Packet Length: 48
07/20 16:46:33 EZZ7878I Router ID: 172.20.20.142 Area: 0.0.0.20
07/20 16:46:33 EZZ7878I Checksum: fd71 Auth Type: 0
07/20 16:46:33 EZZ7878I Hello_Interval: 10 Network mask: 255.255.255.0
07/20 16:46:33 EZZ7878I Options:
07/20 16:46:33 EZZ7878I Router_Priority: 1 Dead_Router_Interval: 40
07/20 16:46:33 EZZ7878I Backup DR: 172.20.20.42 Designated Router: 172.20.20.5
07/20 16:46:33 EZZ7878I Neighbor: 172.20.20.5
07/20 16:46:33 inet_output: socket = 6, size = 48, flags = 2000004, destination = 224.0.0.5
07/20 16:46:34 EZZ7911I Retransmitting packet, type 2, 172.20.20.42 -> 172.20.20.5
07/20 16:46:34 EZZ7876I -- OSPF Packet Sent ------ Type: Database Description
07/20 16:46:34 EZZ7878I OSPF Version: 2 Packet Length: 32
07/20 16:46:34 EZZ7878I Router ID: 172.20.20.142 Area: 0.0.0.20
07/20 16:46:34 EZZ7878I Checksum: c784 Auth Type: 0
07/20 16:46:34 EZZ7878I DD options: DD flags: I M Master
07/20 16:46:34 EZZ7878I DD sequence no: 62d812c3
07/20 16:46:34 inet_output: socket = 6, size = 32, flags = 2000004, destination = 172.20.20.5
07/20 16:46:34 ezaorort (1st): Recv completes with 20 bytes
07/20 16:46:34 ezaorort (2nd): Recv completes with 232 bytes
07/20 16:46:34 ezaorort: Packet from 172.20.20.5 on 172.20.20.42 with index 2
07/20 16:46:34 EZZ7877I -- OSPF Packet Received -- Type: Database Description
07/20 16:46:34 EZZ7878I OSPF Version: 2 Packet Length: 212
07/20 16:46:34 EZZ7878I Router ID: 172.20.20.5 Area: 0.0.0.20
07/20 16:46:34 EZZ7878I Checksum: 470a Auth Type: 0
07/20 16:46:34 EZZ7878I DD options: DD flags: Slave
07/20 16:46:34 EZZ7878I DD sequence no: 62d812c3
07/20 16:46:34 EZZ7878I LS age: 861 LS options:
07/20 16:46:34 EZZ7878I LS type: Router LS ID: 172.20.20.5
07/20 16:46:34 EZZ7878I LS orig: 172.20.20.5 LS sequence no: 80000003
07/20 16:46:34 EZZ7878I LS checksum: 15af LS length: 36
07/20 16:46:34 EZZ7878I LS age: 1671 LS options: E
07/20 16:46:34 EZZ7878I LS type: AS External LS ID: 10.0.100.0
07/20 16:46:34 EZZ7878I LS orig: 172.20.20.5 LS sequence no: 80000002
07/20 16:46:34 EZZ7878I LS checksum: 2ddc LS length: 36
07/20 16:46:34 EZZ7878I LS age: 1671 LS options: E
07/20 16:46:34 EZZ7878I LS type: AS External LS ID: 10.0.201.0
07/20 16:46:34 EZZ7878I LS orig: 172.20.20.5 LS sequence no: 80000002
07/20 16:46:34 EZZ7878I LS checksum: d1d2 LS length: 36
07/20 16:46:34 EZZ7878I LS age: 1671 LS options: E
07/20 16:46:34 EZZ7878I LS type: AS External LS ID: 10.0.202.0
07/20 16:46:34 EZZ7878I LS orig: 172.20.20.5 LS sequence no: 80000002
07/20 16:46:34 EZZ7878I LS checksum: c6dc LS length: 36
07/20 16:46:34 EZZ7878I LS age: 1671 LS options: E
07/20 16:46:34 EZZ7878I LS type: AS External LS ID: 10.0.203.0
07/20 16:46:34 EZZ7878I LS orig: 172.20.20.5 LS sequence no: 80000002
07/20 16:46:34 EZZ7878I LS checksum: bbe6 LS length: 36
07/20 16:46:34 EZZ7878I LS age: 1671 LS options: E
07/20 16:46:34 EZZ7878I LS type: AS External LS ID: 10.0.205.0
07/20 16:46:34 EZZ7878I LS orig: 172.20.20.5 LS sequence no: 80000002
07/20 16:46:34 EZZ7878I LS checksum: a5fa LS length: 36
07/20 16:46:34 EZZ7878I LS age: 1671 LS options: E
07/20 16:46:34 EZZ7878I LS type: AS External LS ID: 92.50.68.80
07/20 16:46:34 EZZ7878I LS orig: 172.20.20.5 LS sequence no: 80000002
07/20 16:46:34 EZZ7878I LS checksum: b8a3 LS length: 36
07/20 16:46:34 EZZ7878I LS age: 1671 LS options: E
07/20 16:46:34 EZZ7878I LS type: AS External LS ID: 172.20.5.0
07/20 16:46:34 EZZ7878I LS orig: 172.20.20.5 LS sequence no: 80000002
07/20 16:46:34 EZZ7878I LS checksum: 139f LS length: 36
07/20 16:46:34 EZZ7878I LS age: 1671 LS options: E
07/20 16:46:34 EZZ7878I LS type: AS External LS ID: 192.168.178.0
07/20 16:46:34 EZZ7878I LS orig: 172.20.20.5 LS sequence no: 80000002
07/20 16:46:34 EZZ7878I LS checksum: a0bb LS length: 36
07/20 16:46:34 EZZ7908I Received packet type 2 from 172.20.20.5
07/20 16:46:34 EZZ7919I State change, IPv4 OSPF neighbor 172.20.20.5, new state 32, event 5
07/20 16:46:34 EZZ7919I State change, IPv4 OSPF neighbor 172.20.20.5, new state 8, event 7
EZZ7921I OSPF adjacency failure, neighbor 172.20.20.5, old state 32, new state 8, event 7
07/20 16:46:35 EZZ7919I State change, IPv4 OSPF neighbor 172.20.20.5, new state 16, event 14
07/20 16:46:35 EZZ7909I Sending unicast type 2 dst 172.20.20.5 net 2 interface ETH2
07/20 16:46:35 EZZ7876I -- OSPF Packet Sent ------ Type: Database Description
07/20 16:46:35 EZZ7878I OSPF Version: 2 Packet Length: 32
07/20 16:46:35 EZZ7878I Router ID: 172.20.20.142 Area: 0.0.0.20
07/20 16:46:35 EZZ7878I Checksum: c782 Auth Type: 0
07/20 16:46:35 EZZ7878I DD options: DD flags: I M Master
07/20 16:46:35 EZZ7878I DD sequence no: 62d812c5
07/20 16:46:35 inet_output: socket = 6, size = 32, flags = 2000004, destination = 172.20.20.5
07/20 16:46:35 ezaorort (1st): Recv completes with 20 bytes
07/20 16:46:35 ezaorort (2nd): Recv completes with 52 bytes
07/20 16:46:35 ezaorort: Packet from 172.20.20.5 on 172.20.20.42 with index 2
07/20 16:46:35 EZZ7877I -- OSPF Packet Received -- Type: Database Description
07/20 16:46:35 EZZ7878I OSPF Version: 2 Packet Length: 32
07/20 16:46:35 EZZ7878I Router ID: 172.20.20.5 Area: 0.0.0.20
07/20 16:46:35 EZZ7878I Checksum: c230 Auth Type: 0
07/20 16:46:35 EZZ7878I DD options: DD flags: I M Master
07/20 16:46:35 EZZ7878I DD sequence no: 62d812c4
07/20 16:46:35 EZZ7908I Received packet type 2 from 172.20.20.5
Henri
Beiträge: 401
Registriert: 23 Jul 2005, 01:42

Re: OSPF Problem mit IBM z/OS 2.5

Beitrag von Henri »

Vermutlich hört LANCOM nicht auf die 224.0.0.6.

224.0.0.5 The Open Shortest Path First (OSPF) All OSPF Routers address is used to send Hello packets to all OSPF routers on a network segment. No
224.0.0.6 The OSPF All Designated Routers (DR) address is used to send OSPF routing information to designated routers on a network segment.
Screenshot 2022-07-21 at 11.11.08.png
Du hast keine ausreichende Berechtigung, um die Dateianhänge dieses Beitrags anzusehen.
Frühstücksdirektor
Beiträge: 70
Registriert: 08 Jul 2022, 12:53
Wohnort: Aachen

Re: OSPF Problem mit IBM z/OS 2.5

Beitrag von Frühstücksdirektor »

Nur mal so eine Idee:

hast du schon mal mit den unterschiedlichen OSPF-Schnittstellen-Typen (unter OSPF-Schnittstellen) was probiert? Standard beim LANCOM ist Broadcast. Es gibt noch NMBA, P2P und P2MP. Macht der IBM was Anderes und es passt nicht zusammen? Beide Seiten müssen natürlich zusammen passen.
Hat der IBM eine "besondere" Konfiguration bei OSPF?

Ob der LANCOM auf 224.0.0.6 hört sieht man mit Show IGMP-Groups auf der CLI.
Henri
Beiträge: 401
Registriert: 23 Jul 2005, 01:42

Re: OSPF Problem mit IBM z/OS 2.5

Beitrag von Henri »

danke, das habe ich nicht, lt. Wireshark kommt das Packet von der anderen Seite, das hilft dann nicht.
Die Besonderheit besteht eher darin, das i.d.R. auf der anderen Seite eine besonders grosse CISCO oder Juniper Box steht und kein LANCOM Gerät.
Weiterhin ist ein OS und soll nur die GW Informationen über OSPF bekommen. Also kein Router, was auch die 224.0.0.6 erklärt.

Mit vielen Grüßen

Henri
Frühstücksdirektor
Beiträge: 70
Registriert: 08 Jul 2022, 12:53
Wohnort: Aachen

Re: OSPF Problem mit IBM z/OS 2.5

Beitrag von Frühstücksdirektor »

Probiere doch mal dem LANCOM eine höhere Router Priorität zu geben, so dass dieser immer DR wird, unter OSPF-Schnittstellen.
Henri
Beiträge: 401
Registriert: 23 Jul 2005, 01:42

Re: OSPF Problem mit IBM z/OS 2.5

Beitrag von Henri »

das ist nicht das Problem, das ACK Paket hat 224.0.0.6 als Destination und kommt nicht an.

Mit vielen Grüßen

Henri
Antworten