07-08-2013 03:27 AM - edited 03-07-2019 02:16 PM
Hi, folks.
Anybody encountered any differences in these two releases ???
Following setup:
Two Cat WS-C3560E-48PD-S:
First one:
Switch Ports Model SW Version SW Image
------ ----- ----- ---------- ----------
* 1 54 WS-C3560E-48PD 15.0(2)SE C3560E-IPBASEK9-M
Second one:
Switch Ports Model SW Version SW Image
------ ----- ----- ---------- ----------
* 1 54 WS-C3560E-48PD 15.0(2)SE2 C3560E-UNIVERSALK9-M
License Level: ipbase
License Type: Permanent
Next reload license Level: ipbase
I have found that the first one doesn't support parts of the "device-sensor" configuration that the second one
has:
switch1(config)#device-sensor ?
filter-list Sensor Protocol Filter List Configuration
filter-spec Sensor Protocol Filter Spec Configuration
notify Options for when to trigger identity update events
switch1(config)#device-sensor accounting
^
% Invalid input detected at '^' marker.
switch2(config)#device-sensor ?
accounting Trigger accounting updates with sensor TLVs/Options
filter-list Sensor Protocol Filter List Configuration
filter-spec Sensor Protocol Filter Spec Configuration
notify Options for when to trigger identity update events
switch2(config)#device-sensor accounting
switch2(config)#
What happens with the device-sensor data on switch1 ??? Is it still sent via radius accounting to the profiling ISEs and therefore will
show up in the ISE identity database ???
Rgs
Frank
07-08-2013 05:26 AM
Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
My understanding, in theory, both IPBase and Universal with an IPBase license should offer the same feature support. The latter, though, is usually a bigger image as it supports additional features via license activation.
It's interesting you've found a feature that the Universal allows access to, via an IPBase license, that's not in the IPBase image. Perhaps it's a possible license "bug"?
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide