You should find this article useful. In the article, they use VLAN 1. You would just want to substitute 1 with whatever VLAN you want to run your management traffic over. I believe some switches do have a 'management-vlan' specific command, but this one doesn't. You would create it using standard commands. The bottom of the article also goes into detail RE SSH Telnet, HTTP, and HTTPS for management.   [URL]
Many thanks for taking the time to read and reply. We have a mainly flat network, that I'm wanting to VLAN.We have an N3000 stack as our core, and this is setup with VLANs and routing, mainly for another building that we completed last year, that has an Aruba network that has been VLANed. All of this is working fine. I now want to start to push out VLAN on our flat network. Our core N3000 is setup with an IP address of 10.10.5.59/16 in VLAN 10 (no IP address on VLAN 1). The majority of downstream switches (which have IP addresses configured on VLAN 1) are setup as:switchport access vlan 10. This works fine. Our core N3000 is connected to another N3000 in our second server room. This second switch is IP address 10.10.5.60/16 on VLAN 10. Again, no IP address on VLAN 1. The N1548 is downstream of the second server room switch. It's IP address is 10.10.5.64/16 on VLAN 1. There is 10 Gb fibre connection between the switches, and I want to trunk this for VLANs. I can't just use the command:switchport mode trunkas the downstream switch loses connection. But I can addswitchport trunk native vlan 10to keep the connection. I read that having the management VLAN on different VLANs is not a good idea, so I decided to try the following on the N1548.Add VLAN 20 and assign a IP address of 10.20.20.102/24 (this VLAN is already setup on the core and second N3000 switches).I've added VLAN 20 and assigned 10.20.20.102. Core N3000 is 10.20.20.11 and second N3000 is 10.20.20.103.I then thought I'd connect on 10.20.20.102, remove the 10.10.5.60 IP address from VLAN 1, and assign it to VLAN 10. However, I can't connect on 10.20.20.102. Checking the web interface, VLAN 20 is showing as inactive? From the second N3000 (10.10.5.60) I can ping the core on VLAN 20 (10.20.20.11), and I can ping the second N3000 VLAN 20 (10.20.20.103) from my workstation and from the core N3000 (10.10.5.59). As you can probably tell, I'm pretty new to this. What am I missing?
N3000 to N1548 trunk with different native VLANs?