- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-11-2021 09:49 AM
I have a 2960s switch at a branch office with a trunk that was recently changed to a Meraki. The subnet ended up mismatched for the management VLAN of the switch.
Meraki---trunk w native VLAN 10---2960 SW.
I can change the VLAN IP on the MX to match the subnet of the of the switch management vlan 10 and add a route at the DC to be able to ping the switch and SSH to to it. But the trick is that I need to change both the gateway and the VLAN 10 IP address at the same time.
Idea 1: If I set the VLAN 10 IP address to DHCP would the default gateway be picked up from the Meraki DHCP server and over-ride the statically configured default gateway?
Idea 2: Is there any way to issue two commands to the switch such as to manually set the IP address of Vlan 10 and update the gateway with a single command input?
Wish: I wish the Meraki had an SSH client like an ISR has. Then I could just SSH to the Meraki and then
SSH from it to the switch without the need for the gateway to be correct on the switch.
2960
int Gig 1/0/1
switchport trunk native vlan 10
switchport mode trunk
int Vlan 10
desc MGT VLAN
ip address 10.90.10.2 255.255.255.0
ip default-gateway 10.90.10.1
Meraki MX
VLAN 10 IP 10.240.100.1 255.255.255.0
Solved! Go to Solution.
- Labels:
-
Catalyst 2000
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-11-2021 11:41 AM
You ask " I'm not sure if that would over-ride the statically configured ip gateway". I have not done this on a 2960 switch so am not speaking from experience. But I am pretty confident that changing the vlan to use DHCP would not over ride a statically configured ip gateway.
I believe that there is an approach that would work for you.
- put a file on an TFTP server (or perhaps FTP) which has the several commands that you need to issue to change the vlan IP address and the default-gateway
- access the switch (SSH or telnet)
- on the switch schedule a reload in a couple of minutes (to recover in case this does not work)
- copy tftp running-config (supplying appropriate parameters for the copy of the file with the commands to the switch)
- if you lose connectivity then the changes did not work right. Wait for the reload. Then you will be back where you started.
- if the changes worked and you still have connectivity, check running config to verify the new commands are there and then cancel the scheduled reload.
A similar approach might be to put the file with the several commands into flash and do copy flash:<file> running-config
Rick
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-11-2021 09:52 AM
If you have device in the same network can use to Login then you can change the Gateway and IP
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-11-2021 10:00 AM - edited 10-11-2021 10:09 AM
If I set the Meraki VLAN 10.to 10.90.10.1/24 then I can SSH to the switch at 10.90.10.2.
But if I then changed the gateway on the switch to 10.240.100.1 I would lose access and
no longer be able to update the ip address on its vlan 10 to 10.240.100.2. If I changed
the IP address on the switch VLAN 10 to 10.240.100.2 first I would no longer be able
to reach it because the gateway would still be 10.90.10.1 and the Meraki lacks an
SSH client to be able to access it locally.
If I changed VLAN 10 on the switch to DHCP and let the Meraki hand out an address
and gateway - I'm not sure if that would over-ride the statically configured ip gateway.
Am I missing something?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-11-2021 11:41 AM
You ask " I'm not sure if that would over-ride the statically configured ip gateway". I have not done this on a 2960 switch so am not speaking from experience. But I am pretty confident that changing the vlan to use DHCP would not over ride a statically configured ip gateway.
I believe that there is an approach that would work for you.
- put a file on an TFTP server (or perhaps FTP) which has the several commands that you need to issue to change the vlan IP address and the default-gateway
- access the switch (SSH or telnet)
- on the switch schedule a reload in a couple of minutes (to recover in case this does not work)
- copy tftp running-config (supplying appropriate parameters for the copy of the file with the commands to the switch)
- if you lose connectivity then the changes did not work right. Wait for the reload. Then you will be back where you started.
- if the changes worked and you still have connectivity, check running config to verify the new commands are there and then cancel the scheduled reload.
A similar approach might be to put the file with the several commands into flash and do copy flash:<file> running-config
Rick
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-11-2021 01:46 PM
I am glad that my suggestion was helpful. Thank you for marking this question as solved. This will help other participants in the community to identify discussions which have helpful information. This community is an excellent place to ask questions and to learn about networking. I hope to see you continue to be active in the community.
Rick
