Cisco Catalyst switch - Keep VLAN UP

I have a Cisco 3750X switch. I am configuring layer 3 SVIs and I do not have access to the device to physically connect devices. I want to put the devices in UP/UP state. I beleive there's a way to do this with VLAN State active or some other command. Does anyone know the configuration needed so I can fully configure and test ping on SVIs?
LVL 1
jbla9028Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

JustInCaseCommented:
This should work.
Add interface to your VLANs and under interface issue no keepalive. Port should come up, so VLAN too.
0
Jan SpringerCommented:
have you tried putting the one of the physical interfaces of that vlan into loopback mode?
0
jbla9028Author Commented:
I have not. how do I do that?
0
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

Jan SpringerCommented:
take an rj45 loop connector and plug it into the interface.

the pinouts should be 1 to 3 and 2 to 6.
0
jbla9028Author Commented:
Jan, thank you but I do not have physical access to the device for a few weeks. I thought there was another way that could be done via CLI to set the SVI into UP/UP.  on a router its called no autostate. That command however is only available on Cisco routers.



http://packetlife.net/blog/2009/nov/9/svi-autostate/
0
Jan SpringerCommented:
some router interfaces can be soft forced into loopback but i don't see where the 3750 interfaces can do this.
0
JustInCaseCommented:
Did you tried to add VLAN to trunk (and check is really VLAN created, just in case, I know it should, but...)?
switchport trunk allowed vlan add xx

If SVI exist on switch, you should add 1 port to forwarding state and adding VLAN to trunk could do that.
I just checked, it worked in GNS3, but on a real switch, who knows. :)
0
Jan SpringerCommented:
at least one physical interface passing that vlan has to be up/up before the vlan can come up/up.
0
JustInCaseCommented:
Is there anything connected to switch? Or there's no nothing at all attached to switch, not on a single port?
0
Jan SpringerCommented:
you can't have just any port.  the switch has to have a vlan connected port in up/up or that vlan being passed and recognized across a trunked interface for the vlan interface to be up/up.
0
JustInCaseCommented:
Yes that's right (I forget that I have already did something on config - my suggestion don't work), but how author is connected to switch? Out of band?
0
Jan SpringerCommented:
yes and a software loop doesn't appear to be an option.
0
jbla9028Author Commented:
I am currently connected to the switch via the console port. No cables are connected to interfaces. It not a critical issue so I will be able to eventually hook up the interface and set interface to trunk all traffic to test. I just figured there had to be some way. It looks like on 4500 switches it works.
0
Jan SpringerCommented:
my misunderstanding.  i thought you wouldn't have physical access for a few weeks.  this is a good opportunity to create a loopback rj45 connector.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Craig BeckCommented:
I don't think you can do this on a switch.  For a SVI to be UP/UP at least one port must be in the STP forwarding state.  If you issue the no keepalive command on a port it will itself be UP/UP, but STP will not be forwarding on that port, so the SVI will stay UP/DOWN.  You don't need a port to be in a trunk though - it can be an access port.

Why, if you don't have any devices connected to the VLAN, do you want the SVI to be UP anyway?
0
aleghartCommented:
IIRC, if the SVI is down, then you can't use that IP address for telnet/ssh/http access to the switch.

Is this 3750 trunked to another switch?  Put the same VLAN on another switch and the trunk.  Give the second switch an IP address on that VLAN.

That should get the two switches talking to each other, wouldn't it?
0
Craig BeckCommented:
@aleghart - that's correct, although the switch is already reachable remotely via IP so I don't imagine the requirement is simply to telnet/SSH to the switch using a different IP.
0
aleghartCommented:
Sometimes, you remove the IP that's in the user LAN, and use only a management VLAN for access.  Makes it easy to limit access to the management interfaces, and helps lock down in a WAN environment where many subnets are routed to other sites.

Site A user LAN subnet can see Site B's user LAN subnet, but not the management subnet.
0
Craig BeckCommented:
I know that, but access to switch via WAN is up obviously so no management access via user LAN is in effect at the moment.
0
jbla9028Author Commented:
unfortunately none of these worked. I ended up getting interfaces setup and the IPs came up. Thank you for the help though.
0
Craig BeckCommented:
You should ask for the question to be deleted then, instead of picking an incorrect answer.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Switches / Hubs

From novice to tech pro — start learning today.