Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Dieter Hermanns wrote: > > yoyo64 schrieb: >> HI >> >> I suspect a problem since changes have been made on our IP plan, >> I know that both eth1: cards MUST be on same network, but not the same as >> eth0: >> >> Can you confirm that ? >> >> If yes, is this configuration good, or not ? >> >> eth0:0 >> >> LAN <--eth0: SVR1 : eth1: ---cross cable --- eth1: SVR2 :eth0 --> LAN >> >> on SVR1: >> eth0 Lien encap:Ethernet HWaddr 00:10:18:16:5E:51 >> inet adr:10.64.1.21 Bcast:10.64.127.255 Masque:255.255.248.0 >> adr inet6: fe80::210:18ff:fe16:5e51/64 Scope:Lien >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> RX packets:63364858 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:94816479 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 lg file transmission:1000 >> RX bytes:210941296 (201.1 Mb) TX bytes:247399813 (235.9 Mb) >> Interruption:11 >> eth0:0 Lien encap:Ethernet HWaddr 00:10:18:16:5E:51 >> inet adr:10.64.1.23 Bcast:10.64.7.255 Masque:255.255.248.0 >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> RX packets:0 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 lg file transmission:1000 >> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) >> Interruption:11 >> eth1 Lien encap:Ethernet HWaddr 00:14:5E:45:79:8C >> inet adr:10.64.100.120 Bcast:10.64.100.255 >> Masque:255.255.128.0 >> adr inet6: fe80::214:5eff:fe45:798c/64 Scope:Lien >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> RX packets:12017664 errors:1 dropped:0 overruns:0 frame:1 >> TX packets:20355766 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 lg file transmission:1000 >> RX bytes:1060768598 (1011.6 Mb) TX bytes:2424749092 (2312.4 >> Mb) >> Interruption:11 MÃ�©moire:d0100000-d0110000 >> >> >> on SVR2: >> eth0 Lien encap:Ethernet HWaddr 00:10:18:16:6C:19 >> inet adr:10.64.1.22 Bcast:10.64.7.255 Masque:255.255.248.0 >> adr inet6: fe80::210:18ff:fe16:6c19/64 Scope:Lien >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> RX packets:513891 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:10879 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 lg file transmission:1000 >> RX bytes:43061255 (41.0 Mb) TX bytes:2330132 (2.2 Mb) >> Interruption:48 >> eth1 Lien encap:Ethernet HWaddr 00:14:5E:C9:5D:AB >> inet adr:10.64.100.118 Bcast:10.64.100.255 >> Masque:255.255.128.0 >> adr inet6: fe80::214:5eff:fec9:5dab/64 Scope:Lien >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> RX packets:21292603 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:12582649 errors:1 dropped:0 overruns:0 carrier:0 >> collisions:0 lg file transmission:1000 >> RX bytes:3554036526 (3389.3 Mb) TX bytes:1109266413 (1057.8 >> Mb) >> Interruption:16 MÃ�©moire:d0100000-d0110000 >> >> And last but not least, what about gateway configuration ? >> >> I suspect problem beacause nmblookup answer 3 ip for my domain master, it >> have to be one IP >> nmblookup -U 10.64.1.23 -R "DEP64#1b" >> querying DEP64 on 10.64.1.23 >> 10.64.1.21 DEP64<1b> >> 10.64.1.23 DEP64<1b> >> 10.64.100.120 DEP64<1b >> >> >> Thanks a lot for your response > > there is no need for a gateway since both hosts are connected via cross > cable. > > Either your mask or broadcast on both eth1 is wrong, this pair does not > match: > I suppose your mask should be 255.255.255.0! > > your suspect nmblookup problem should be solved by editing your appropiate > smb.conf > > HTH > -- > Dieter Hermanns Telefon: +49(0)241 910508 0 > Fränz & Jaeger GmbH Telefax: +49(0)241 910508 40 > Schurzelter Str. 27 Email : dh at fraenz-jaeger.de > 52074 Aachen Web : www.fraenz-jaeger.de > GF: Dipl.Phys. Thomas Fränz USt.-Ident Nr.: DE220975410 > Dipl.-Ing. Dieter Jaeger Amtsgericht Aachen HRB 8785 > > _______________________________________________ > drbd-user mailing list > drbd-user at lists.linbit.com > http://lists.linbit.com/mailman/listinfo/drbd-user > > Thanks a lot for your help My eth0: and eth0:0 Ip adresses are mandatory, so I expect to change only eth1: as below SVR1: inet adr:10.100.1.21 Masque:255.255.248.0 SVR2: inet adr:10.100.1.22 Masque:255.255.248.0 I found that despite there are on same mask, they are not on same subnet (see exemples on internet) - What do you think about this configuration ? Add to this, my eth1: are used for drbd purpose (see my drbd.conf below) - Can I change without any damage for datas, IP's adress ? # # drbd.conf # var lib mysql resource r2 { protocol C; incon-degr-cmd "echo '!DRBD! pri on incon-degr' | wall ; sleep 60 ; halt -f"; startup { degr-wfc-timeout 120; # 2 minutes. } disk { on-io-error detach; } syncer { rate 100M; group 1; al-extents 257; } on svr-dep64 { device /dev/drbd/2; disk /dev/sdb6; address 10.64.100.120:7789; meta-disk internal; } on svr-secours { device /dev/drbd/2; disk /dev/sdb6; address 10.64.100.118:7789; meta-disk internal; } } # var www resource r3 { protocol C; incon-degr-cmd "echo '!DRBD! pri on incon-degr' | wall ; sleep 60 ; halt -f"; startup { degr-wfc-timeout 120; # 2 minutes. } disk { on-io-error detach; } syncer { rate 100M; group 1; al-extents 257; } on svr-dep64 { device /dev/drbd/3; disk /dev/sdb5; address 10.64.100.120:7790; meta-disk internal; } on svr-secours { device /dev/drbd/3; disk /dev/sdb5; address 10.64.100.118:7790; meta-disk internal; } } # home resource r6 { protocol C; incon-degr-cmd "echo '!DRBD! pri on incon-degr' | wall ; sleep 60 ; halt -f"; startup { degr-wfc-timeout 120; # 2 minutes. } disk { on-io-error detach; } syncer { rate 100M; group 1; al-extents 257; } on svr-dep64 { device /dev/drbd/6; disk /dev/sdc1; address 10.64.100.120:7793; meta-disk internal; } on svr-secours { device /dev/drbd/6; disk /dev/sdc1; address 10.64.100.118:7793; meta-disk internal; } } # partages resource r5 { protocol C; incon-degr-cmd "echo '!DRBD! pri on incon-degr' | wall ; sleep 60 ; halt -f"; startup { degr-wfc-timeout 120; # 2 minutes. } disk { on-io-error detach; } syncer { rate 100M; group 1; al-extents 257; } on svr-dep64 { device /dev/drbd/5; disk /dev/sdd1; address 10.64.100.120:7791; meta-disk internal; } on svr-secours { device /dev/drbd/5; disk /dev/sdd1; address 10.64.100.118:7791; meta-disk internal; } } -- View this message in context: http://www.nabble.com/Ip-problems-since-changes-tp20598233p20600049.html Sent from the DRBD - User mailing list archive at Nabble.com.