vlan showes shutdown?

[ryezak]

I am trying to enable an interface to be in access mode with a vlan 5 on it.

I went into the interface vlan5 and then ran the command
no shutdown
then saved the command.
When I do a show run it show the vlan 5 on the interface but it says shutdown.

How do you enable a vlan?

 

[MrNick0483]

The vlan does not come up and up until there is an active port in it.

 

[ryezak]

active port meaning the assigned physical interface or the trunk port?

 

[vipergg]

I think you are talking 2 different things here , doing a no shut on int vlan 5 is the SVI . If its a layer 2 switch like a 2950 then you can only have 1 SVI active because it is used "only" to manage the switch . I think you are getting the layer 2 and layer 3 ends mixed up . A vlan on a swithport is a layer 2 function and all that is needed is switchport access vlan X on the switchport.

 

[North323]

is the vlan admin down? or down down? what mode is your switch in? client? server? transparent?

 

[ryezak]

when I do a show run on the 2950 switch it says

Vlan X
shutdown

But I have went into the interface and ran the "no shut.."

Client? Server ? transparent?

Refresh me? how will I know which to use?

 

[ryezak]

ok I read up on the VTP modes to run in.
I decided to leave the switch in server mode and gave it a VTP name.
My concern is how do I get the Vlan to show up as active or not shut down.
Notice 5 and 112 are listed as shutdown.

Any ideas why?

interface VLAN1
ip address 192.168.1.70 255.255.255.0
no ip directed-broadcast
no ip route-cache
!
interface VLAN5
description kozak
ip address 192.168.168.204 255.255.255.0
no ip directed-broadcast
no ip route-cache
shutdown
!
interface VLAN112
no ip directed-broadcast
no ip route-cache
shutdown
!
ip default-gateway 192.168.1.254
snmp-server engineID local 000000090200000652C59E40
snmp-server community private RW
snmp-server community public RO
!

 

[vipergg]

You can only have 1 active svi to manage the box . Int vlan 1 is probably active so shut down vlan 1 and no shut vlan 5 .Get rid of the address on vlan 1 and get rid of the int vlan 112 statement , it is doing nothing...

 

[burtsbees]

Yes---to expand on what viper said, you can set up vlan1 with an ip, no shut, and then set up another vlan(5, say) and no shut---as soon as you hit enter, it will automatically take the new SVI (vlan5) and shut it down, as you will see in sh run, ALTHOUGH it WILL take the "no shut" command...the writers of the IOS just didn't think to put a message like, "You can only have one active SVI at a time, for management---please shut down vlan1 before attempting to "no shutdown" the new SVI."

/

 

[ryezak]

So every vlan creates its own broadcast domain. I made fa0/12 a trunk port to handle vlan 5 and 112.
112 I have not worked with yet.
My question is do every vlan need there own DHCP server?
Or do you usually put a route in of the vlan to the gateway IP?
Anyone have a sample config of how to do this?

 

[madwok]

Be carefull on bringing up a VTP server into a production
network. It can wipe out all your existing VLANs.

==
One DHCP server can be configured to service DHCP requests from many different network segments .

If you use a dedicated DHCP server such as Win or Linux, you might have to use the command ip helper on routers that are connecting your VLANS to the DHCP server .

 

[ryezak]

I was thinking of using the 1841 router which has DHCP.
It should be able to handle many different network segments?
Ip helper? I would use this instead of a defined route?
thanks

 

[madwok]

ip helper is only useful if you wish the routers to forward the DHCP broadcast, which normally being filtered by routers.

1841, with correct IOS, can handle DHCP request from multiple network segments.

You just define various DHCP pools wherein you can define the network, mask, gateway, wins, dns etc. for each VLAN or network segment .

Ex:

ip dhcp excluded-address 10.207.126.1. 10.207.126.20
! reserve 20 ip address for servers etc.
!
ip dhcp pool VLAN1
network 10.207.126.0 255.255.255.0
default-router 10.207.126.1
dns-server 4.2.2.2
.
.
.
ip dhcp pool VLANx
network x.x.x.x x.x.x.x
default-router x.x.x.x
dns-server x.x.x.x

 

[burtsbees]

Exactly---since this is router-on-a-stick, the broadcasts do not go through the router, per se, (actually they do), but all the vlans are logically AND physically directly connected---no ip helper-address or ip forward-protocol command is needed.

Echoing Madwok...he gets the credit.

/