I have a 3750-12S-S which was the third switch in a stack of 3 3750. We want to run it as a seperate switch in a different location so I removed it from the stack by powering it off, unplugging the stack cables and then powering it up again.
When the switch came up again all of the 12 interfaces were numbered Gi3/0/1-12. Despite erasing the config and rebooting the switch, the interfaces will not reset back to Gi1/0/1-12. I have noticed the following command in the running config:
"switch 3 provision ws-c3750g-12s". I suspect this is causing the problem but I am unable to remove it from the config without it reappearing on the next power-cycle.
WARNING: Changing the switch number may result in a
configuration change for that switch.
The interface configuration associated with the old switch
number will remain as a provisioned configuration.
Do you want to continue?[confirm]
The part that we really need to focus on is
"The interface configuration associated with the old switch
number will remain as a provisioned configuration."
Which means that configuration that was associated with switch number 3 will remain as
Gi5/0/1 and will not change to Gi1/0/1 . Infact , renumbering will provision another switch
with the new number with default config. So what is really the solution of this ? The
solution is to move the config manually , or do not change the switch numbers. Once you put the config on a newly provisioned #1 switch , then unprovision switch # 3 and save the config. That should effectively move every thing to switch 1.
Same problem here. A WS-C3750G-24PS was naively stacked following a WS-C3750-48P, thinking the stack would behave as the 3550 Gigastack used to. Now unstacked, the 24PS config shows interfaces gi1/0/1-28 (God knows where they came from) plus its own (as gi2/0/1-28), but the 48P shows only its own (fa1/0/1-48 plus gi1/0/1-4). I am able to manage them individually now, but it's confusing having the odd mix of bogus interfaces on the 24PS. I wish the 3750 Getting Started Guide had a stronger warning about this, other than "refer to the switch software configuration guide".
I sort-of figured it out. The old config provisioned this switch as switch 2, and for some reason the provisioning carried over through the reboot. Where do I request implementation of a "back-in-the-box" command? Seems to me this would become a common requirement in a large environment.
This document gives several answers on frequently asked questions for PFRv3 channel state behavior.
Q1: What are all the channel operational states from a BR (border role) perspective and what are the rules/conditions to be in each st...
The need was to reach an host inside a LAN through a VPN connection managed by the LAN gateway (Cisco 1921).
The LAN gateway performs NAT and there was a dedicate nat rule for the host i wanted to reach through VPN.
I couldn't connect to the hos...
We have 3 identical switches configured by someone else and would like to claim some of the Gigabit ports(G1/G2/G3/G4) for use on servers. When we try to change the wiring and configuration, we run in to connectivity issues. Attached is a des...