Unsolved

This post is more than 5 years old

4 Posts

4990

January 19th, 2007 17:00

Management VLAN

Hello,
 
I Have 2716 as a "core" switch and 3448 as distribution switch. I created 3 new VLANs (2, 101 and 102) with trunk LAG between them and that part is working. VLAN1 is not used for anything.
 
I have 2 questions:
First, how do I configure 2 switches so that workstation plugged in 2716 port can manage both switches? I know that I can assign IP address to specific VLAN on 3448, but this is not the case with 2716.
And second, is it possible to configure access port on 3448 to be trunk port, but to default to specific VLAN if device connected to it is not VLAN aware? Like dot1q native VLAN.
 
Thank you for help
Alex

7 Posts

January 29th, 2007 01:00

Let me start by saying that I'm no expert however I've done some configuring of VLAN's on similar equipment and here is my understanding of it:
 
We have several 2724 switches which are in the same family as your 2716 switch. If I'm not mistaken these are NOT managed switches. Because of this the GVRP will not flow between the switches:
  • The 3448 will not be aware of the VLAN's created on each of the other switches
  • The 2716 switches will not be aware of the VLAN's on the other switches
  • You cannot assign a management IP to a VLAN, the IP you assign is for the entire switch.

In our environment the 2724 switches are connected to 5324 switches. Everything connected to the 2724 switches is on the same network / VLAN (no seperation, lets say VLAN 1254).

  • I leave the 2724 switches configured as normal (uses the default VLAN1)
  • I configure the port (8) on the 5324 that connects to the 2724 as follows:
    • VLAN Port Settings:
      • Port Mode: General
      • PVID: 1254
      • Frame Type: Admit All
    • VLAN Membership Settings
      • Select VLAN 1254
      • Tick port 8 until U appears
        • The U means that untagged traffic is present and will automatically be assigned the 1254 VLAN tag when entering / exiting.
    • Apply each of these settings

Now that you have done this you should be able to reach the management IP on the other end. I'm not sure if the 3448 is a router as well (our 5324 switch isn't, we use another device to do all our routing) but traffic should be able to transverse the switches.

I hope I've made some sense, I spent ages working some of this stuff out.

Message Edited by Box293 on 01-28-200709:24 PM

No Events found!

Top