Code upgrade 6.0.188 on mesh controllers..with or without LAG enabled.

Unanswered Question

/* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-qformat:yes; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:"Times New Roman"; mso-fareast-theme-font:minor-fareast; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin;}

We upgraded code to 6.0.188  on  two mesh controllers and here r the observations..

After the code upgrade one of the controller after probably 30 mins rebooted and was not reachable. Console access showed the config script. This controller has LAG enabled. Looks like the code upgrade wipes out the LAG info or the VLAN Tag so the controllers are not reachable.

The second controller was not in LAG. This one after the code upgrade displayed a web based dialog. I was able to key in the values and was back in business.

So if you have remote controller and no way to have console access it is better to disable LAG so u will have access after the code upgrade enable LAG. This may depend on the code base you are going from.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)


This Discussion



Trending Topics: Other Wireless Mobility

client could not be authenticated
Network Analysis Module (NAM) Products
Cisco 6500 nam
reason 440 driver failure
Cisco password cracker
Cisco Wireless mode