Mo, 27.06.2016 Wartungsarbeiten?

Wartungsarbeiten? Oder lokales Routingproblem bei uns (OVH)?

dus-a und fra-b sind nicht betroffen, die restlichen 4 sind jeweils immer wieder für ein paar Minuten weg.

Obwohl, die Tunnel halten

IP-Adressen und AS Nummern bitte.

Ich möchte nicht ausschließen, dass das Problem hier lokal ist.

AS: 201701
IP address for eth0: 164.132.62.120
IP address for tun-ffrl-uplink: 185.66.195.64
IP address for tun-ffrl-ber-a: 100.64.5.79
IP address for tun-ffrl-fra-a: 100.64.5.81
IP address for tun-ffrl-dus-a: 100.64.5.83
IP address for tun-ffrl-ber-b: 100.64.5.85
IP address for tun-ffrl-fra-b: 100.64.5.87
IP address for tun-ffrl-dus-b: 100.64.5.89

Oder in Langform:

router id 185.66.195.64;
protocol direct announce {
        table master;
        import where net ~ [185.66.195.64/32];
        interface "tun-ffrl-uplink";
};
protocol kernel {
        table master;
        device routes;
        import none;
        export filter {
                krt_prefsrc = 185.66.195.64;
                accept;
        };
        kernel table 42;
};
protocol device {
        scan time 15;
};
function is_default() {
        return (net ~ [0.0.0.0/0]);
};
template bgp uplink {
        local as 65125;
        import where is_default();
        export where proto = "announce";
};
protocol bgp ffrl_ber_a from uplink {
        source address 100.64.5.79;
        neighbor 100.64.5.78 as 201701;
};
protocol bgp ffrl_fra_a from uplink {
        source address 100.64.5.81;
        neighbor 100.64.5.80 as 201701;
        preference 120;
};
protocol bgp ffrl_dus_a from uplink {
        source address 100.64.5.83;
        neighbor 100.64.5.82 as 201701;
        preference 110;
};
protocol bgp ffrl_ber_b from uplink {
        source address 100.64.5.85;
        neighbor 100.64.5.84 as 201701;
};
protocol bgp ffrl_fra_b from uplink {
        source address 100.64.5.87;
        neighbor 100.64.5.86 as 201701;
};
protocol bgp ffrl_dus_b from uplink {
        source address 100.64.5.89;
        neighbor 100.64.5.88 as 201701;
        preference 120;
};

BGP Session hat in der Tat geflappt:

bird> show protocols all legacy_100_64_5_81 name proto table state since info legacy_100_64_5_81 BGP master up 16:49:45 Established Preference: 100 Input filter: ipv4_ffdus_in Output filter: community_out Routes: 1 imported, 1 exported, 1 preferred Route change stats: received rejected filtered ignored accepted Import updates: 1 0 0 0 1 Import withdraws: 0 0 --- 0 0 Export updates: 798895 2 798892 --- 1 Export withdraws: 2875 --- --- --- 0 BGP state: Established Neighbor address: 100.64.5.81 Neighbor AS: 65125 Neighbor ID: 185.66.195.64 Neighbor caps: refresh AS4 Session: external multihop AS4 Source address: 100.64.5.80 Hold timer: 139/240 Keepalive timer: 1/80

Log:

root@bb-a.fra2.fra.de.ffrl.de ~log # cat syslog | grep legacy_100_64_5_81
Jun 27 11:34:00 bb-a bird: legacy_100_64_5_81: Error: Hold timer expired
Jun 27 12:31:11 bb-a bird: legacy_100_64_5_81: Error: Hold timer expired
Jun 27 13:22:11 bb-a bird: legacy_100_64_5_81: Error: Hold timer expired
Jun 27 13:44:28 bb-a bird: legacy_100_64_5_81: Error: Hold timer expired
Jun 27 13:45:44 bb-a bird: legacy_100_64_5_81: Received: Connection collision resolution
Jun 27 13:58:03 bb-a bird: legacy_100_64_5_81: Error: Hold timer expired
Jun 27 14:26:18 bb-a bird: legacy_100_64_5_81: Received: Hold timer expired
Jun 27 14:34:45 bb-a bird: legacy_100_64_5_81: Error: Hold timer expired
Jun 27 15:01:04 bb-a bird: legacy_100_64_5_81: Error: Hold timer expired
Jun 27 15:06:50 bb-a bird: legacy_100_64_5_81: Error: Hold timer expired
Jun 27 15:15:07 bb-a bird: legacy_100_64_5_81: Received: Hold timer expired
Jun 27 15:23:03 bb-a bird: legacy_100_64_5_81: Error: Hold timer expired
Jun 27 15:35:41 bb-a bird: legacy_100_64_5_81: Error: Hold timer expired
Jun 27 15:44:40 bb-a bird: legacy_100_64_5_81: Received: Hold timer expired
Jun 27 15:50:58 bb-a bird: legacy_100_64_5_81: Received: Hold timer expired
Jun 27 16:06:07 bb-a bird: legacy_100_64_5_81: Received: Hold timer expired
Jun 27 16:30:43 bb-a bird: legacy_100_64_5_81: Error: Hold timer expired
Jun 27 16:40:50 bb-a bird: legacy_100_64_5_81: Error: Hold timer expired
Jun 27 16:48:57 bb-a bird: legacy_100_64_5_81: Received: Administrative shutdown

Da so gut wie alle anderen BGP sessions seit dem 24.6 (da haben wir die Kiste rebootet) stabil sind tippe ich auf ein Problem an eurer Konnektivität.

VG
takt

1 „Gefällt mir“

Da meine zweite Maschine stabile Sessions hatte habe ich die Kiste dann mal durchgebootet.
Danke für’s Nachschauen.