Aruba & ProVision-based
1753670 Members
5197 Online
108799 Solutions
New Discussion

Re: Cannot access 5308xl http or telnet

 
sparkymarcopolo
Advisor

Re: Cannot access 5308xl http or telnet

Found the issue,

 

All the untagged ports have moved from the default lan to a vlan that is not in use.

 

I tried setting various ports on the unused one to 'no' but the web interface said it could not complete the task. So I then set a port that was untagged to tagged and it accepted it, problem is it knocked some users off the network.

 

Is there a quick easy way to sort tagging without causing issues because I can see various tagged port replicated between vlans so I'm a little confused.

EricAtHP
Esteemed Contributor

Re: Cannot access 5308xl http or telnet

Sorry, I thought you had inband access again to the switch.

 

If I understand correctly, you should have telnet and web access from a client in the default vlan using the 10.0.0.32 ip address. Is it possible that the client you are using isn't connected to a port in VLAN 1?

 

Can you share the whole config? From your serial console session, do a "show run" and then copy and paste the output to a file and attach it or just copy and paste into here. If there is private info in your config please don't share it or obscure it in some way.

EricAtHP
Esteemed Contributor

Re: Cannot access 5308xl http or telnet

That makes more sense.

 

From the CLI, you can quickly and easily change port VLAN membership. First go to the VLAN context and then configure the ports that should be tagged or untagged. Here is an example.

 

HP 5308# config

HP 5308(config)# vlan 1

HP 5308(vlan-1)# tagged 23-24

HP 5308(vlan-1)# untagged 1-5,8,10,20-22

 

If you move all ports at the same time, there should be no noticeable disruption to your users.

sparkymarcopolo
Advisor

Re: Cannot access 5308xl http or telnet

I thought I'd try it again this morning while it was quiet and all the untagged ports are back to the default vlan, we're back to where we were before the issues.

 

Can I take it that untagged ports can only be assigned to one vlan at a time?

 

Whereas you can have a untagged port on one vlan, but also the same port tagged on another vlan?