Home

Forums

Stories

Knowledge Base

Business Community > All Threads > Management vlan (e.g. vlan160) IP address not accesible from ethernet port

< All Threads

Management vlan (e.g. vlan160) IP address not accesible from ethernet port

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

Management vlan (e.g. vlan160) IP address not accesible from ethernet port

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

jozoar

2020-07-25 18:30:36 - last edited 2020-07-27 16:32:32

Posts: 3

Helpful: 0

Solutions: 0

Stories: 0

Registered: 2020-07-25

Management vlan (e.g. vlan160) IP address not accesible from ethernet port

2020-07-25 18:30:36 - last edited 2020-07-27 16:32:32

Model: T2600G-28MPS(TL-SG3424P)

Hardware Version: V4

Firmware Version: 4.0.5 Build 20200109 Rel.69266(s)

Hi,

From different reason we can not use management vlan vlanID "1". Switch is connected to router with a one ethernet trunk dot1q, with more vlan inside. So I configured VLAN 160 - which is part of trunk, set IP address for Vlan 160. This ip address is reachable from router and it is working properly.

interface gigabitEthernet 1/0/1

description "connection_to_router"
speed 100
switchport general allowed vlan 160,181,300 tagged
no switchport general allowed vlan 1

interface vlan 160
ip address 10.50.160.13 255.255.255.0
description "mng"
no ipv6 enable

///The next, an ethernet port is set ass access port with Vlan160 untag.

interface gigabitEthernet 1/0/2
switchport general allowed vlan 160 untagged
no switchport general allowed vlan 1

///the isue is, after PC connection to interface gigabitEthernet 1/0/2, PC is not able to ping 10.50.160.13.

In wireshark I see arp from PC, but switch does not answer. In case I check it with VLAN1 instead vlan 160 it is working without any problem.Did I forget to configure anything?

thanks a lot for your hints,

jozef

1 Accepted Solution

R1D2

LV6

2020-07-26 11:57:07 - last edited 2020-07-27 16:32:32

Posts: 4334

Helpful: 1039

Solutions: 173

Stories: 3

Registered: 2015-12-05

Re:Management vlan (e.g. vlan160) IP address not accesible from ethernet port -Solution

2020-07-26 11:57:07 - last edited 2020-07-27 16:32:32

jozoar wrote

///The next, an ethernet port is set ass access port with Vlan160 untag.

interface gigabitEthernet 1/0/2
switchport general allowed vlan 160 untagged
no switchport general allowed vlan 1

In my opinion it should be:

interface gigabitEthernet 1/0/2

switchport general allowed vlan 160 untagged

switchport pvid 160

no switchport general allowed vlan 1

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻

Recommended Solution

Fae

2020-07-27 07:41:37

Posts: 3613

Helpful: 1355

Solutions: 474

Stories: 0

Registered: 2020-06-30

Re:Management vlan (e.g. vlan160) IP address not accesible from ethernet port

2020-07-27 07:41:37

@jozoar

jozoar wrote

From different reason we can not use management vlan vlanID "1". Switch is connected to router with a one ethernet trunk dot1q, with more vlan inside. So I configured VLAN 160 - which is part of trunk, set IP address for Vlan 160. This ip address is reachable from router and it is working properly.

Before you change the management VLAN, you need to confirm the port belongs to the new management VLAN.

The default PVID of all ports is 1, so we also need to change the PVID to 160 for the corresponding ports.

>> Omada EAP Firmware Trial Available Here << *Try filtering posts on each forum by Label of [Early Access]*

jozoar

LV1

2020-07-27 11:18:18

Posts: 3

Helpful: 0

Solutions: 0

Stories: 0

Registered: 2020-07-25

Re:Management vlan (e.g. vlan160) IP address not accesible from ethernet port

2020-07-27 11:18:18

Thanks for your suggestion,

I will check it in 60 minutes and I will let you know result.

In other way thanks a lot for your support.

have a nice day,

jozef

jozoar

LV1

2020-07-27 16:41:50

Posts: 3

Helpful: 0

Solutions: 0

Stories: 0

Registered: 2020-07-25

Re:Management vlan (e.g. vlan160) IP address not accesible from ethernet port

2020-07-27 16:41:50

Hi gys,

I tested it- Yes PVID and my misunderstanding what the PVID means was issue. It should be set in interface configuration.

thanks a lot for your support.

best regards

jozef

jozoar

2020-07-25 18:30:36 - last edited 2020-07-27 16:32:32

Posts: 3

Helpful: 0

Solutions: 0

Stories: 0

Registered: 2020-07-25

Information

Helpful: 0

Replies: 4

Management vlan (e.g. vlan160) IP address not accesible from ethernet port

Management vlan (e.g. vlan160) IP address not accesible from ethernet port

Information

Voters 0

Tags