Cisco Cisco Broadband Access Center Telco Wireless 3.8 發佈版本通知
6
Cisco Broadband Access Center 3.8.1 Release Notes
OL-27175-02
New Features in Cisco BAC 3.8.1
Configurable VSAs
This feature is introduced to push the newly added VSA (Vendor Specific Attribute) information to HNB
GW as part of Radius accept. A new script file, addCustomVSA.sh is introduced to configure the
custom VSA details in the PAR Server and update the custom VSA information in car_ep.properties.
GW as part of Radius accept. A new script file, addCustomVSA.sh is introduced to configure the
custom VSA details in the PAR Server and update the custom VSA information in car_ep.properties.
This script configures the custom VSA to the CAR sever if it is not existing. Otherwise, the script
removes the existing VSA and configures the new custom VSA.
removes the existing VSA and configures the new custom VSA.
Boot Notification Alarm and Value Change Inform for FAP
This feature supports sending a Boot Notification alarm to NMS whenever it receives Boot/Bootstrap
informs from FAP. This helps to auto clear all outstanding alarm of an FAP whenever FAP reboots.
Whenever DPE receives event named "1 BOOT" or "0 BOOTSTAP" from FAP, then the
Boot Notification SNMP alarm is raised with severity as "Cleared" for those corresponding events.
informs from FAP. This helps to auto clear all outstanding alarm of an FAP whenever FAP reboots.
Whenever DPE receives event named "1 BOOT" or "0 BOOTSTAP" from FAP, then the
Boot Notification SNMP alarm is raised with severity as "Cleared" for those corresponding events.
If the FAP sends both queued and expedited event in “4 Value Change” Inform, the DPE processes both
the events and convert them into traps. This is achieved by setting the value of the new custom property
- FC-ENABLE-CPE-ALARM - to true. This property also needs to be added in
/IPDevice/properties/available/pg.
the events and convert them into traps. This is achieved by setting the value of the new custom property
- FC-ENABLE-CPE-ALARM - to true. This property also needs to be added in
/IPDevice/properties/available/pg.
Additional Security Features
The following additional security features have been implemented in this release:
•
A new mandatory input field, Current Password, is shown during the Change Password operation,
along with the New Password and Confirm Password fields.
along with the New Password and Confirm Password fields.
•
Cross site scripting (XSS) scripts are eliminated by providing strong input validation in blocking all
invalid inputs. It is done by passing all the requests through a filter.
invalid inputs. It is done by passing all the requests through a filter.
•
To eliminate Cross Site Request Forgery (CSRF), all the POST requests get validated for the valid
token. If the token in request matches with the token available in token cache, then it is a valid user
request and the page is processed; else the session becomes invalid.
token. If the token in request matches with the token available in token cache, then it is a valid user
request and the page is processed; else the session becomes invalid.
SAC Allocation to Devices
During GA Provisioning flow, Cisco BAC pushes the SAC (Service Area Code) values to devices based
upon mapping files (.csv) with comma separated list. The list can include any of the following comma
separated values:
upon mapping files (.csv) with comma separated list. The list can include any of the following comma
separated values:
•
INSEE, SAC
•
2G CELLID, SAC
•
3G CELLID, SAC
Updating the SAC value to the device takes the below precedence:
1.
If macro CELLID is present in 3G SAC mapping file, then the device is updated with the SAC value
corresponding to 3G macro CELLID of the device.
corresponding to 3G macro CELLID of the device.
2.
If macro CELLID is present in 2G SAC mapping file, then the device is updated with the SAC value
corresponding to 2G macro CELLID of the device.
corresponding to 2G macro CELLID of the device.