using VLAN's to contain legacy decnet\declan broadcasts 3

[us10696]

I am trying to set up a VLAN to contain declan/decnet service broadcasts from three legacy mainframes using a 3524XL. Only a handful of Windows workstations on our large bridged network (650 nodes) need contact these hosts and they do it through ip and client software for windows. For political reasons I can't split up the large bridged network with routers.

When the legacy clunkers are hanging on the ports assigned to the new VLAN number, I can't ping them from the large bridged network side. So I have my broadcast containment but I can't work on these devices through the Windows clients. Are other commands needed to get the vlan working a sit should?

Am I missing something on making this level 2 vlan solution work? Do I need a level 3 solution with routing and subnetting? I have an old 2514 router that might do that, and then I could assign non-routable ip's to the legacy mainframes, and use host tables on the workstations to get to the mainframes through the trusty old 2514.

 

[IPKONFIG]

You need a layer 3 device to communicate between vlans. The 2514 would be good for this. Although, I believe your 3524XL switch can route too! Just build router interfaces on your switch.

"I can picture a world without war. A world without hate. A world without fear. And I can picture us attacking that world, because they'd never expect it."
- Jack Handey, Deep Thoughts

 

[baddos]

The 3524xl won't do layer3, so you'll need to use that 2500 router or hookup another layer3 switch to your layer2 3524xl switch.

 

[byteya]

I was doing this in our setup here. I kept ALL devices that need to access our VMS boxes in one VLAN. Everything worked the best this way. When we had things running more "flat" the decnet stuff was having problems handling broadcasts from all the other equipment. I'm not sure, but I would say you have to avoid routing this traffic if you want it to be stable.

J

*J*