[ixpmanager] LAG inter-switch connections
Rowan Thorpe
rowan at rowanthorpe.com
Thu Jul 24 18:08:37 IST 2014
On 15:56 Wed 23 Jul 2014, Barry O'Donovan wrote:
> ..[snip]..
> This section of the documentation should help: http://git.io/bleSzg
It most certainly did, thanks (not that I hadn't already browsed it many times
in the past when I was first setting things up - just that it dropped way off
my mental stack since then...). Sorry for the noise.
In the end the problem wasn't really a LAG issue, just that they changed the
ports (more specifically created an aggregate port and changed the underlying
physical port at the same time), and expected IXP-M to auto-register the
changes - not knowing that trunk graphs are still hand-configured. I have
started a local wiki page with "IXP-admin-but-not-sysadmin gotchas" for such
things (actually "IXP-admin-but-not-the-person-who-installed-it" also applies
here - for other sysadmins who are assisting with maintenance but don't have
time to search through all the installation docs in order to get a handle on
things). Possibly some "IXP-M usage and maintenance" documentation like that
would be useful to have extracted to a separate page of bullet-points (like a
cheatsheet), reduced down from the (many pages of) installation instructions? I
think it would help reduce cognitive load and flatten the learning curve for
admins who aren't devs.
--
Rowan Thorpe
mailto:rowan at rowanthorpe.com
sip:rowan at rowanthorpe.com
xmpp:rowan at rowanthorpe.com
http://status.rowanthorpe.com (microblog)
http://www.rowanthorpe.com
PGP fingerprint:
BB0A 0787 C0EE BDD8 7F97 3D30 49F2 13A5 265D CCBD
----
Please avoid sending Word, PowerPoint or Excel attachments
See http://www.gnu.org/philosophy/no-word-attachments.html
----
"There is a great difference between worry and concern. A worried person sees
a problem, and a concerned person solves a problem."
- Harold Stephens
----
Please feel free to correct my Greek when it is wrong, so I can improve.
More information about the ixpmanager
mailing list