summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-sysadm/2012-March/004351.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-sysadm/2012-March/004351.html')
-rw-r--r--zarb-ml/mageia-sysadm/2012-March/004351.html121
1 files changed, 121 insertions, 0 deletions
diff --git a/zarb-ml/mageia-sysadm/2012-March/004351.html b/zarb-ml/mageia-sysadm/2012-March/004351.html
new file mode 100644
index 000000000..af38535ad
--- /dev/null
+++ b/zarb-ml/mageia-sysadm/2012-March/004351.html
@@ -0,0 +1,121 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-sysadm] is the svn server down?
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20is%20the%20svn%20server%20down%3F&In-Reply-To=%3C1333199538.13656.15.camel%40localhost%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="004350.html">
+ <LINK REL="Next" HREF="004352.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-sysadm] is the svn server down?</H1>
+ <B>Michael Scherer</B>
+ <A HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20is%20the%20svn%20server%20down%3F&In-Reply-To=%3C1333199538.13656.15.camel%40localhost%3E"
+ TITLE="[Mageia-sysadm] is the svn server down?">misc at zarb.org
+ </A><BR>
+ <I>Sat Mar 31 15:12:18 CEST 2012</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="004350.html">[Mageia-sysadm] is the svn server down?
+</A></li>
+ <LI>Next message: <A HREF="004352.html">[Mageia-sysadm] is the svn server down?
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#4351">[ date ]</a>
+ <a href="thread.html#4351">[ thread ]</a>
+ <a href="subject.html#4351">[ subject ]</a>
+ <a href="author.html#4351">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>Le samedi 31 mars 2012 &#224; 12:51 +0200, nicolas vigier a &#233;crit :
+&gt;<i> On Sat, 31 Mar 2012, Michael Scherer wrote:
+</I>&gt;<i>
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; For the record, I see that 212.85.158.145 ( alamut default gateway,
+</I>&gt;<i> &gt; whose reverse is gateway-mageia.ielo.net ) is not answering to ping and
+</I>&gt;<i> &gt; on the other hand, the default gateway for zarb.org ( 212.85.158.1 )
+</I>&gt;<i> &gt; answer to ping.
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; And I am pretty sure that this gateway is after our switch from a
+</I>&gt;<i> &gt; network point of view, and so that this should answer fine if our switch
+</I>&gt;<i> &gt; is unplugged.
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; So I suppose that this device ( 158.45 ) do send network
+</I>&gt;<i> &gt; topology/routing with OSPF or RIP etc, and for some reason, it no longer
+</I>&gt;<i> &gt; announce the route for our network.
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; It could be caused by our switch being broken, but that would be rather
+</I>&gt;<i> &gt; strange, as I do not know any network equipment that would act like this
+</I>&gt;<i> &gt; ( doesn't mean that it doesn't exist, but usually, network is not that
+</I>&gt;<i> &gt; smart ).
+</I>&gt;<i>
+</I>&gt;<i> According to gradator, this is normal if the switch is down. When the
+</I>&gt;<i> port is down, OSPF automatically clear the route.
+</I>
+But what about the default gateway ? IIRC, that's not our switch ( as
+this is just a layer 2 switch ), so did it disappear on purpose once the
+network disappeared too ?
+
+
+&gt;<i> &gt;
+</I>&gt;<i> &gt; So what did IELO said exactly ?
+</I>&gt;<i>
+</I>&gt;<i> The port where our switch is connected is down.
+</I>
+&gt;<i> But even if the swich is not the problem, it would be a good idea to
+</I>&gt;<i> replace it for a bigger one, to allow us to connect the arm boards on
+</I>&gt;<i> it (instead of connecting them behind valstar). We also need to replace
+</I>&gt;<i> one of the disk on the arm boards which seems to be not working.
+</I>
+Connecting them behind valstar was also to protect them until we
+properly secured them, since the password is still weak and easy to
+attack from bruteforce. And AFAIK, we didn't plan to give direct access
+to people, so that was useless and I think moving to a bastion model for
+ssh access would be a improvement in term of security for others
+builders too ( jonund, ecosse, and maybe fiona, depending how the backup
+are done ).
+
+Also, just replacing the switch is not a improvement, since we will have
+the same issue if this switch break ( unlikely, but so was the current
+breakage, or the various hardware issues we faced each time we got there
+) so what about trying to have a more redundant setup ?
+
+Most, if not all, of our servers have 2 ethernet interface, so we could
+try to see if bonding could help ( in case of ethernet card failure ) or
+see if we can find a setup with 2 switchs ( one that doesn't cost too
+much, cause of course, cisco can solve the issue for us, we just cannot
+afford it ).
+
+Can we afford one or two switchs that support it ? ( I lost the name of
+the current flavor du jour in term of bonding )
+
+--
+Michael Scherer
+
+</PRE>
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="004350.html">[Mageia-sysadm] is the svn server down?
+</A></li>
+ <LI>Next message: <A HREF="004352.html">[Mageia-sysadm] is the svn server down?
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#4351">[ date ]</a>
+ <a href="thread.html#4351">[ thread ]</a>
+ <a href="subject.html#4351">[ subject ]</a>
+ <a href="author.html#4351">[ author ]</a>
+ </LI>
+ </UL>
+
+<hr>
+<a href="https://www.mageia.org/mailman/listinfo/mageia-sysadm">More information about the Mageia-sysadm
+mailing list</a><br>
+</body></html>