cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
5363
Views
0
Helpful
19
Replies

VLAN config issue

33sanders
Level 1
Level 1

     I am configuring VLANS on 2960x switches by building.  We have about 15 buildings and would like to have each building be in its own VLAN.  This issue I am having is that we have some devices that are static IP's and when those devices are pluged in, they do not work.  Cannot ping them.  For example, our maintenance department has some energy management devices that are addressed 10.20.1.x and printers are address 10.10.101.x.  So when i configure vlan 55, ip address 10.55.1.2, set the switch ports to switchports access vlan 55 and plug any device with a static ip in to that switch, it doesnt work.  It is possible to have these devices on the same vlan as everthing else in thier building without changing their IP address? 

19 Replies 19

No, you don't.

Also, I think routing should be on your 4506 and not on 2960.

2960's are definitely layer 2/access switches and not capable of routing.

Refer to this thread:

https://supportforums.cisco.com/thread/2061029

On your 4506, try this:

interface GigabitEthernet2/10

switchport

switchport trunk ?

it should have encapsulation command.

Routing is enabled on the 4506.  The above example was from the 4506: 

4506(config-if)#switchport trunk ?

  allowed  Set allowed VLAN characteristics when interface is in trunking mode

  native   Set trunking native characteristics when interface is in trunking

           mode

  pruning  Set pruning VLAN characteristics when interface is in trunking mode

The 2960x does have limited layer 3 features after IOS 12.2(55)SE.  You can set static routes but no routing protocols.

That is incorrect, it is true the 2960 is a L2 switch, the 'X', however, is L3 capable.

But as said, you should not be configuring your trunk ports as access ports, by default all VLANS are a member of the trunk group, without a trunk configured the traffic will never be able to leave the switch (Unless it's sourced from the native VLAN), which yours isn't!

You need to understand the basics as you have multiple problems, from your last comment the reason you can't ping the SVI (the switch) is because it and the node connected are on different networks, i.e. 10.20.x.x and 10.55.x.x.

Also check the SVI is not shutdown!

Sometimes you don't always have a choice of encapsulation, it is only the higher end switches that provide both dot1q and ISL, hence you have to specify which will be used, the latter is being deprecated anyway.

Martin

On your 2960 you need to define the vlans that Allen bradley controllers are currently  on  and set the ports they are attached to to those vlans and if the trunking is setup right it should work .  If for instance they are currently in say vlan 20 on the 2960  define this.  Adjust your vlan for whatever they are currently using.

conf t'

vlan 20

name AB-controller

interf g0/20

descr AB controller

switchport mode access

switchport access 20

switchport host

This is how it looks now:  

2960

interface GigabitEthernet1/0/52   -- port to 4506
 switchport mode trunk

interface GigabitEthernet1/0/13 -- Port of the 10.20. device
 switchport access vlan 140
 switchport mode access
 spanning-tree portfast

 

4506:

interface GigabitEthernet4/48
 switchport mode trunk

 

Still can not talk to the 10.20. device.