Perhaps, I wish it was still allowed to run earlier code, they've had honor-based "restrictions" before and I just think that it should continue like that. Locking down stuff will only make people find keygens/license generators and do it anyway if they don't honor the restrictions in the first place.
If it's purely because there is NEW hardware that require the new software in the newer MX5/10/40-T series then fine, if it's for locking down ports/enforcing license restrictions then they have a very skewed priority, instead of fixing bugs they introduce lock-downs. :-P Just my 2c. //T 2012/3/22 Per Granath <per.gran...@gcc.com.cy>: > I suspect the 10.4 would not lock down the XE ports on the chassis, so there > is a reason for not allowing it to work... > > >> It's quite weird, especially since I can "upgrade" the system to a full MX80 >> with licences only, and if I do that I expect that I will be able to run my >> standard release (10.4R8.5) which I run on my other MX80s (which is the full >> MX80 btw). >> >> So basically, I feel a bit cheated that I had to "wait" for MX5 to be >> released >> when I could get a MX80-5G. >> >> I'm going to try to install 11.2R5.4 (recommended release) on it now, I do >> not >> trust a R1-release. Ever. ;-) I might also try create a technical support >> ticket or >> raise hell with my SR to try to make the 10.4-series to support MX5/10/40s >> unless someone else has done it already. -- Timh Bergström Head of System Operations Videoplaza/System Operations timh.bergst...@videoplaza.com +46 727 406 845 S:t Eriksgatan 46 Stockholm www.videoplaza.com skype: timh_bergstrom gtalk: timh.bergst...@videoplaza.com linkedin: _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
