Originally posted by codywatkins
Also, is there any loss of functionality if I buy an XL and install the EN software (I think a lot of the ones on eBay are this??)
No. While you won't own an -EN license ... *shrug*
And the ONLY benefit from the EN version is the ability to do VLANs and VLAN trunking?
As far as I know that is the only disadvantage. If you intend to run spanning tree you may want to watch out for the possibility that the non-EN image may not offer it, but that's just speculation. I haven't had a non-EN in ages.
Originally posted by KDAWebServices Yes, you are correct, XL-EN has 8MB, XL has 4MB which will stop newer IOS images from being loaded, also means the XL will run out of steam before the XL-EN in my experience.
Ah. So would it be correct to say that purchasing a XL without EN would be a big security risk as the latest IOS would not be able to be loaded onto the switch ?
I don't know about you, but I don't expose the administrative IP addresses on my switches to the public Internet. I think this practice makes it relatively safe to run even older IOS images on layer 2 infrastructure.
Originally posted by jsw6 I don't know about you, but I don't expose the administrative IP addresses on my switches to the public Internet. I think this practice makes it relatively safe to run even older IOS images on layer 2 infrastructure.
The only problem I see here is that it would be colocated.
Im thinking I will go for the Catalyst 2912-XL-EN. One more question: to get the latest IOS releases do we have to pay? It would be second hand, so we wouldn't have an account with cisco.
I believe the 2924XL (non-EN) does not have the ability to cluster as well . . . but chances are, if you are not using vlans on the switch, there wouldn't be too much need to change configs on them often.
Since the non-EN lacks vlan support I doubt there will be much need for vlan reconfiguration on it. I have never liked switch "stacking" / "clustering" anyway, and am more comfortable managing multiple switches than trusting something like VTP to do it for me... and allow someone to accidentally blow away all the VLAN configuration for the VTP domain by mistake with an unconfigured high revision roll-forward.