Hello,
Since upgrading to Prizm 3.1 I have been having problems with Bandwidth plans staying in effect. Below is the output of from the History tab in Prizm. It appears to me that the SM has Authenticated with the BAM in Prizm. However if you notice in the section below the “Authentication Occurred” field changes from True to False.
Also, It seems that I can set various bandwidth plans to SMs, but if the SM is rebooted it reverts back to the default values, however the name of the bandwidth plan still appears under the Bandwidth Config tab in the details view within Prizm…
Any thoughts?
3/28/08 10:00 AM Type: Set User: rseibel
Initial Discovery of Configuration Attributes General
MAC Address: ‘0A003E91AC35’
Authentication Control Authentication Account Expires: ‘Never’ Authentication Account State: ‘Active’
Authentication Key: ‘******’
Authentication Occurred: ‘True’
Bandwidth Control Bandwidth Allow License Use: ‘Disabled’
Bandwidth Hard Cap: ‘’
Bandwidth Service Plan: ‘WCS BW Service Plan (1536 Kbps Total, 1152 Kbps Down, 384 Kbps Up)’
Bandwidth Soft Cap: ‘’
Maximum Information Rate (MIR)
Bandwidth Uplink Sustained Rate: ‘250’
Bandwidth Uplink Burst Allocation: ‘500’
Bandwidth Downlink Sustained Rate: ‘1000’
Bandwidth Downlink Burst Allocation: ‘2000’
Committed Information Rate (CIR)
Bandwidth Low Priority Uplink CIR: ‘0’
Bandwidth Low Priority Downlink CIR: ‘0’
Bandwidth High Priority Channel Enable: ‘Disabled’
Bandwidth High Priority Uplink CIR: ‘0’
Bandwidth High Priority Downlink CIR: '0’
And then…
3/28/08 10:03 AM Type: Discovered User: SYSTEM
Authentication Control
Authentication Occurred: ‘True’ —> ‘False’ Web, Telnet, FTP Session Timeout: ‘’ —> ‘600’
Maximum Information Rate (MIR)
Bandwidth Uplink Sustained Rate: ‘250’ —> ‘20000’
Bandwidth Uplink Burst Allocation: ‘500’ —> ‘500000’
Bandwidth Downlink Sustained Rate: ‘1000’ —> ‘20000’
Bandwidth Downlink Burst Allocation: ‘2000’ —> ‘500000’ Bandwidth Broadcast MIR: ‘’ —> ‘0’
Rebooting the APs has seemed to resolve this issue for now…
However, I have rebooted the APs previous to noticing this issue since the upgrade.
Hopefully everything holds.
Thanks