It won't work if you have a vlan accross some equipements, with no IP adress. Like you provide a layer 2 connectivity between 2 customers equipements, passing through your switchs.
or if you have a router with some IP adresses on vlans interfaces, then a trunk to a switch on which you connect customers, the switch as no IP adress in the vlans he carry
I use the visible label also for this. Regards, Aubin Galinotti Luis Fernando Lacayo wrote:
Hi,We handle this when we create the network, we name it VLAN-xxx and that is all it takes...Luis On Tue, 2009-07-21 at 15:52 +0200, Thomas Pöhler wrote:Hi there,first off I would like to give a big up to all developers of racktables. It really saves us a lot of work.We are kind of new to Racktables and currently transferring all information into racktables. There is one point that’s especially interesting to me. Where do you store your VLAN configuration of your Switch Ports. At the moment we abuse the „Visible Label“ Field for that. E.g. we tag it like “01 (VLAN1 U, VLAN2 T, VLAN3 T, VLAN4 T, VLAN 100T)“ . How do you store this information? Is a more complex VLAN solution planned?Best Regards from Cologne, GermanyThomas Pöhler-- Turtle Entertainment GmbH Thomas Pöhler, IT Operations Manager Siegburger Str. 189 D-50679 Cologne Germany fon. +49 221 880449 331 fax. +49 221 880449 399http://www.turtle-entertainment.com/ <http://www.turtle-entertainment.de/>http://www.esl.eu/ http://www.consoles.net Managing Directors: Jens Hilgers, Ralf Reichert Register Court: Local Court Cologne, HRB 36678-- ______________________________________________________ Luis Fernando Lacayo Chicago Public Schools Senior Unix Administrator ITS/ UNIX Infrastructure Office: 773-553-3835 Cell: 773-203-4493 lflacayo@xxxxxxxxxxxxx <mailto:lflacayo@xxxxxxxxxxxxx> ______________________________________________________ "In God we trust, the rest we monitor ..."
