Wired Intelligent Edge

Hi all,

I am using three 2530-48G switches named SW2, SW2 and SW3. In that, port 45+46 of SW1 trunks to 45+46 of SW2, and port 47+48 of SW1 trunks to 47+48 of SW3. Everything is ok untill i add a new VLAN in SW1 (not assign port to VLAN yet).

The network operates normally, but something wrong with SW1:

        - Can ping to SW1 but cannot  access by web and ssh interfaces, only access through console menu.

        - Cannot remove new added VLAN in console menu 

Actually i always operate them just by web-interface. So it so difficult for me with others. Please help me to get over this problem?

Thanks.

Hi,

please post config at least of SW1.

Since WebInterface is not working:

• Go to console
• Change from menu to CLI
• issue "show config"

Provide results here.

Regards, Jörg

Hi

---

@nvn199 wrote: Everything is ok untill i add a new VLAN in SW1 (not assign port to VLAN yet).

---

Which VLAN Id you added?

Generally adding a VLAN (without eventually assigning to that VLAN an IP Interface and untagging/tagging port(s) you need on the relevant switch) has not such damaging impact (not connecting anymore to Web Management)...at least if you simply created it as you wrote.

The output of show running config would be of help to better diagnose what's going on.

This is the config:

Startup configuration: 32

; J9772A Configuration Editor; Created on release #YA.15.17.0009
; Ver #07:c3.84.9c.63.ff.37.27:50
hostname "SWITCH1"
trunk 45-46 trk1 lacp
trunk 47-48 trk2 lacp
ip default-gateway 192.168.0.50
interface 1
   no power-over-ethernet
   exit
interface 2
   no power-over-ethernet
   exit
interface 3
   no power-over-ethernet
   exit
interface 4
   no power-over-ethernet
   exit
interface 5
   no power-over-ethernet
exit
interface 6
   no power-over-ethernet
   exit
interface 7
   no power-over-ethernet
   exit
interface 8
   no power-over-ethernet
   exit
interface 9
   no power-over-ethernet
   exit
interface 10
   no power-over-ethernet
   exit
interface 11
   no power-over-ethernet
   exit
interface 12
   no power-over-ethernet
   exit
interface 13
no power-over-ethernet
   exit
interface 14
   no power-over-ethernet
   exit
interface 15
   no power-over-ethernet
   exit
interface 16
   no power-over-ethernet
   exit
interface 17
   no power-over-ethernet
   exit
interface 18
   no power-over-ethernet
   exit
interface 19
   no power-over-ethernet
   exit
interface 20
   no power-over-ethernet
   exit
interface 21
   no power-over-ethernet
   exit
interface 22
   no power-over-ethernet
   exit
interface 23
   no power-over-ethernet
   exit
interface 24
   no power-over-ethernet
   exit
interface 25
   no power-over-ethernet
   exit
interface 26
   no power-over-ethernet
   exit
interface 27
   no power-over-ethernet
   exit
interface 28
   no power-over-ethernet
exit
interface 29
   no power-over-ethernet
   exit
interface 30
   no power-over-ethernet
   exit
interface 31
   no power-over-ethernet
   exit
interface 32
   no power-over-ethernet
   exit
interface 33
   no power-over-ethernet
   exit
interface 34
   no power-over-ethernet
   exit
interface 35
   no power-over-ethernet
   exit
interface 36
no power-over-ethernet
   exit
interface 37
   no power-over-ethernet
   exit
interface 38
   no power-over-ethernet
   exit
interface 39
   no power-over-ethernet
   exit
interface 40
   no power-over-ethernet
   exit
interface 41
   no power-over-ethernet
   exit
interface 42
   no power-over-ethernet
   exit
interface 43
   no power-over-ethernet
   exit
interface 44
   no power-over-ethernet
   exit
interface 45
   name "Trunk to SW2"
   no power-over-ethernet
   exit
interface 46
   name "Trunk to SW2"
   no power-over-ethernet
   exit
interface 47
   name "Trunk to SW3"
   no power-over-ethernet
   exit
interface 48
   name "Trunk to SW3"
   no power-over-ethernet
   exit
snmp-server community "public" unrestricted
vlan 1
   name "DEFAULT_VLAN"
   untagged 1-44,49-52,Trk1-Trk2
ip address 192.168.0.254 255.255.255.0
   exit
vlan 140
   name "Wifi"
   no ip address
   exit
management-vlan 140
spanning-tree Trk1 priority 4
spanning-tree Trk2 priority 4
no tftp server
no dhcp config-file-update
no dhcp image-file-update
password manager

Thanks

Hi,

you configured the new VLAN as "management VLAN". The switch will accept management connections only in that management vlan.

Since management vlan has some other difficulties, I'd suggest, you do not use this function for now. 

So remove that configuration and you should be able to connect again.

"no management-vlan" should be enough.

Regards,

Jörg

As Jörg wrote, the problematic configuration line is:

management-vlan 140

You have not configured any port to be untagged member of that VLAN (and you didn't assigned any IP to that VLAN 140)...so, basically, you locked out.

Remove the above line from configuration file and reload it via Console port and you should be able to connect again to your Aruba 2530 using the configured IP 192.168.0.254 through any of its ports (1-44 <- untagged members of VLAN 1).

Greetings!

Going into a bit more detail on the management VLAN — one thing to keep in mind if you do plan to use this feature is that the management VLAN does not participate in switch IP routing, so if your management workstations are on a different subnet from the management IP address, the switch will be unreachable.  If your goal is to limit management access to the switch, you may want to consider using the ip authorized-managers command or ACLs as an alternative.

It is done. I just "no management-vlan" .

Thanks for all you help.

Just for reference: Management VLAN.