VLAN doesn’t not assign any ip address on a Host

[eandrcisco007]

I have got a bit of a strange issue when I am trying to add another vlan to one of our 6500 switches on another floor to separate a particular subnet from other vlans ,so the issue is it won’t assign any ip address to the host that is currently connected in to that particular port that the vlan is assigned to.

Just to break it up, we have currently the same vlan on 6500 VSS switch with bunch of host connected to it and I would like to add the same vlan on the switch that is located on the 2^nd floor with the same spec. to connect another host to it as part of the same team with the same configuration but it does not work!

Below is the configuration on the 6500 (L2) switch on the 2^nd floor that is connected to the main 6500 VSS via fiber.

int gig 5/41

Switchport

Switchport access vlan 23

Switchport mode access

No ip address

Spanning-tree portfast

Spanning-tree bpduguard enable

int vlan23

no ip address

Below is the configuration of the main 6500 VSS switch. (L3)

Int vlan 4

Description  Special Subnet

no ip address

Ip helper-address 192.168.2.100

Both switches are connected through port channel.

I wonder if anyone have experieneced the same issue or knows how to tweak into it and make it work.

[Jon Marshall]

Your configs are confusing ie.

1) your floor switch mentions vlan 23

2) your L3 switch mentions vlan 4 although your configuration shows the vlan 4 interface with no IP address which doesn't make a lot of sense.

If the connection between the two switches is an etherchannel trunk if you want the port on the floor switch to be in the same vlan as hosts connected to other switches just configure the port into that vlan and as long as the vlan is allowed on the trunk it should work.

Perhaps I have misunderstood what you are trying to do. If so please clarify.

Jon

[eandrcisco007]

Thank you Jon,

My bad!! it should read vlan 23 on both,

The configuration has done by someone else and i am kind of takeing over so i am trying to underatnd myself and tweak further... and yes the connection between swicthes are etherchannel. (check below please)

Floor swicth config

int gig ...

no ip address

channel-group 20 mode des

L3 switch config

no switchport

ip address .......

ip flow ingress

ip hello-interval eigrp 1 1

load interval 30

[Jon Marshall]

No problem, makes a bit more sense now.

Are there any other clients on the L2 switch that are already in vlan 23 ?

Assuming you have not run out of IPs in the DHCP scope if there are no existing clients in vlan 23 on the floor switch can you check the port channel configuration ie. is it a trunk and if so does it allow vlan 23 ?

Edit - you will need to check both ends of the link ie. on the floor switch and the VSS primary switch.

Jon

[eandrcisco007]

at this point ,no, but they are going to be addedd more clients on L2 switch,

There is no trunk configured between port chanells per above configuration.

[Jon Marshall]

If the etherchannel between the switches is not configured as a trunk then what vlan is the etherchannel in ?

If it is not vlan 23 then it won't work.

Perhaps you could post the port channel interface from both ends.

Jon

[eandrcisco007]

here you go:

PO Configuration on L2

Int po 7

ip address xx.xx.xx.xx

ip hello-interval eigrp 1 1

load-interval 30

PO Configuration on L3

Int po 7

no switchport

ip address xx.xx.xx.xx

ip hello-interval eigrp 1 1

ip flow ingress

load interval 30

[Jon Marshall]

Okay, I don't think the floor switch is L2 because the above is a L3 connection.

I suspect the floor switch is acting as a L3 switch and your are running EIGRP to exchange routes.

So can you do a "sh ip route" on the floor switch and see what you get.

If it is L3 then without reconfiguration you can't extend vlan 23 to it but do you really need to ie. you could just create a new vlan and route that.

First though have a look at the routing table as suggested.

Jon