5406 config

[serpel]

cenk ;-)

[cenk sasmaztin]

ABE :-) sorry can't see attach folder

[serpel]

you are welcome.
have a nice day.
alex

[Jef van Eijk]

Hi,

it was the management vlan option.
But how to access the switch trough http without this option?

[cenk sasmaztin]

no need for http or telnet access managemet vlan command

management vlan command for security
for unreachable other vlan users managemet vlan

if you can want managemet vlan routing all other vlan you must be remove management vlan command .

[Jef van Eijk]

Thats what i mean. When i disable management the i can't access the siwtch anymore trough http or telnet, only the console.

[EckerA]

Hi,
i'm not sure cos we don't use this feature, but i guess now the configuration:
ip authorized-managers 192.168.1.35 255.255.255.255
ip authorized-managers 192.168.1.2
kicks in.
try removing this optinon and retry to connect to the switch via telnet and http.
Alex

[Jef van Eijk]

How are you manage your switch then?

[EckerA]

sorry,
what i meant was we don't use ip authorized-managers.
of course we manage our switches via telnet.
but i never had any problems to reach a switch via http or telnet without the management vlan.
Alex

[proc_1]

Hi,
when you have a configuration like

ip authorized-managers 192.168.1.35 255.255.255.255

ip authorized-managers 192.168.1.2

you will be able to telnet or http from only
the device with the above 2 ip addresses.

if you want to manage switch from 192.168.1.*
change the mask to 255.255.255.0 or else
add the ip addresses of all devices you want to
access switch through telnet or http by using

ip authorized-managers 192.168.*.*(replace * with your desired IP)
Always make one vlan as your management vlan
(default vlan 1) and never assign this as a user vlan.(don't assign management vlan ip to any user)
anil