ISE 1.2 - Bugs (upgrade)

[Giuliano Gerardi]

1) impossible to set a scheduled backup: calendar window shows "0" insted of the year or randomly "1900"... (forward button works, back button not) clicking "save" is useless as it doesn't respond (FF, Chrome, IE10)

2) Cliking on the nad interface from monitoring (real time authentications) leads to

"SNMP information is not configured for this device in ISE" on the old version only community "public" worked, now nor public nor others..

3) CLI is strangely behaving as lots of blank lines are pushed to terminal in between the last login information and the "ISELAB3315/admin#" (maybe this is a teraterm fault but never happened before)

this the result of 2h testing... quite a shame

[Ravi Singh]

I would recommend you to test it again with fresh installation. Because I have installed it today and till now everything is working fine

[Giuliano Gerardi]

can't, these are the migration tests for final upgrade of the distributed deployment.

if upgrade is unsuccessful will be a real mess...

[Marcin Latosiewicz]

Giuliano,

Open up a TAC case, the first one is for sure something we can look into.

I believe 3rd one is expected, although it would be good to see it live, it maybe due to the way your term is treating carriege return.

For second one it would be good to have a look and comapre prod on 1.1 and testing on 1.2.

M.

[ILKIN GASIMOV]

Hi. I still have the same issue with backward and save button. Patch 2 is installed and even ise-config was reset. 

[guardian-de]

Hi ... I did an upgrade from 1.1.4 to 1.2 and run into same issue 1.) backup schedules. Can you acknowledge, that you do not have this issue with fresh install ?

[Giuliano Gerardi]

Thank you Marcin

@guardian-de :          

same for me (upgrading from 1.1.4 to 1.2)

as for point 2 this is the debug snmp request on the switch:

Jul 31 08:43:30.312: SNMP: Packet received via UDP from 172.31.85.13 on Vlan32
Jul 31 08:43:30.320: SNMP: Queuing packet to 172.31.85.13
Jul 31 08:43:30.320: SNMP: V1 Trap, ent snmpTraps, addr 172.20.32.12, gentrap 4, spectrap 0
 lsystem.5.0 = 172.31.85.13
 ciscoMgmt.412.1.1.1.0 = 1
 ciscoMgmt.412.1.1.2.0 = 172.31.85.13
Jul 31 08:43:30.329: SNMP: Queuing packet to 172.31.85.13
Jul 31 08:43:30.329: SNMP: V1 Trap, ent snmpTraps, addr 172.20.32.12, gentrap 4, spectrap 0
 lsystem.5.0 = 172.31.85.13
 ciscoMgmt.412.1.1.1.0 = 1
 ciscoMgmt.412.1.1.2.0 = 172.31.85.13
Jul 31 08:43:30.572: SNMP: Packet sent via UDP to 172.31.85.13
Jul 31 08:43:30.824: SNMP: Packet sent via UDP to 172.31.85.13
Jul 31 08:43:35.320: SNMP: Packet received via UDP from 172.31.85.13 on Vlan32
Jul 31 08:43:35.345: SNMP: Queuing packet to 172.31.85.13
Jul 31 08:43:35.345: SNMP: V1 Trap, ent snmpTraps, addr 172.20.32.12, gentrap 4, spectrap 0
 lsystem.5.0 = 172.31.85.13
 ciscoMgmt.412.1.1.1.0 = 1
 ciscoMgmt.412.1.1.2.0 = 172.31.85.13
Jul 31 08:43:35.362: SNMP: Queuing packet to 172.31.85.13
Jul 31 08:43:35.362: SNMP: V1 Trap, ent snmpTraps, addr 172.20.32.12, gentrap 4, spectrap 0
 lsystem.5.0 = 172.31.85.13
 ciscoMgmt.412.1.1.1.0 = 1
 ciscoMgmt.412.1.1.2.0 = 172.31.85.13
Jul 31 08:43:35.597: SNMP: Packet sent via UDP to 172.31.85.13
Jul 31 08:43:35.874: SNMP: Packet sent via UDP to 172.31.85.13
Jul 31 08:43:40.320: SNMP: Packet received via UDP from 172.31.85.13 on Vlan32
Jul 31 08:43:40.328: SNMP: Queuing packet to 172.31.85.13
Jul 31 08:43:40.328: SNMP: V1 Trap, ent snmpTraps, addr 172.20.32.12, gentrap 4, spectrap 0
 lsystem.5.0 = 172.31.85.13
 ciscoMgmt.412.1.1.1.0 = 1
 ciscoMgmt.412.1.1.2.0 = 172.31.85.13
Jul 31 08:43:40.345: SNMP: Queuing packet to 172.31.85.13
Jul 31 08:43:40.345: SNMP: V1 Trap, ent snmpTraps, addr 172.20.32.12, gentrap 4, spectrap 0
 lsystem.5.0 = 172.31.85.13
 ciscoMgmt.412.1.1.1.0 = 1
 ciscoMgmt.412.1.1.2.0 = 172.31.85.13
Jul 31 08:43:40.580: SNMP: Packet sent via UDP to 172.31.85.13
Jul 31 08:43:40.832: SNMP: Packet sent via UDP to 172.31.85.13
Jul 31 08:43:45.320: SNMP: Packet received via UDP from 172.31.85.13 on Vlan32
Jul 31 08:43:45.328: SNMP: Queuing packet to 172.31.85.13
Jul 31 08:43:45.328: SNMP: V1 Trap, ent snmpTraps, addr 172.20.32.12, gentrap 4, spectrap 0
 lsystem.5.0 = 172.31.85.13
 ciscoMgmt.412.1.1.1.0 = 1
 ciscoMgmt.412.1.1.2.0 = 172.31.85.13
Jul 31 08:43:45.345: SNMP: Queuing packet to 172.31.85.13
Jul 31 08:43:45.345: SNMP: V1 Trap, ent snmpTraps, addr 172.20.32.12, gentrap 4, spectrap 0
 lsystem.5.0 = 172.31.85.13
 ciscoMgmt.412.1.1.1.0 = 1
 ciscoMgmt.412.1.1.2.0 = 172.31.85.13
Jul 31 08:43:45.580: SNMP: Packet sent via UDP to 172.31.85.13
Jul 31 08:43:45.831: SNMP: Packet sent via UDP to 172.31.85.13

[holger.moersfelder@global.ntt]

any update on the first topic ?

My new ISE installation show the same issue regarding setup of a scheduled backup.

regards

Holger Mörsfelder

[holger.moersfelder@global.ntt]

Hi Giuliano,

I opened today a Tac Case and got the information for Topic 1 that in relase 1.2 is a Bug opened .

CSCui44324.

Coming back when the BUG fix is available.

Regards Holger

[Giuliano Gerardi]

did the same, same answer

look at PMs (only used an other account)

[jgoethals]

I have this problem as well.

Is there a statusupdate for this?

[holger.moersfelder@global.ntt]

It will be fixed in patch 2 and ETA is probably next week. stated by cisco TAC last week.

Last update from cisco tac:

The patch 2 has been delayed to probably 6^th of September

[jgoethals]

Is there any news on the patch?

[holger.moersfelder@global.ntt]

Since 12th Sep patch2 isn't released on CCO yet.

[Jimmi Hvidtfeldt]

The patch has been released from Cisco now.

Works for me and the backup is working.

Very nice.