Table Of Contents
BBSM User Groups, Permissions, and Interface
Private and Public IP Addresses (Multinets)
Introduction
Cisco Building Broadband Service Manager (BBSM) is a software-based service platform that enables customers to create, market, and operate broadband access services, such as high-speed Internet access. BBSM provides "plug-and-play" end-user connections and tiered service levels. With BBSM, you can provide your own services, which reduces support requirements and increases use.
This introductory chapter describes the following:
•
BBSM User Groups, Permissions, and Interface
The system essentially combines network access control and management functions that would normally be contained on multiple servers into one management device. These functions include the following:
•
•
•
•
•
•
•
BBSM is available as a preloaded server appliance, or you can purchase the software separately and install it yourself. If you are installing your BBSM, rather than using a factory installed BBSM, refer to the Cisco BBSM 5.2 and BBSD Installation Guide for instructions on installing BBSM and for the minimum hardware and software requirements. For information on obtaining the installation guide and other documentation, refer to the "Obtaining Documentation" section in the Preface to this user guide.
New in Software Release 5.2
This section briefly describes some of the new and upgraded features added to the 5.2 software release of BBSM. See the individual descriptions and configuration procedures for additional information.
Bandwidth reservation
Allows hotel guests to reserve minimum bandwidth for upcoming meetings and sets up classes of service (bandwidth rates) for these reservations. The feature adds a calendar interface for scheduling access codes and bandwidth management. The group bandwidth management does not affect the existing bandwidth throttling feature. Both can be used on the same BBSM server, but not for the same reservation.
Two-way PMS
Expands the BBSM interface to the PMS to be bidirectional. This provides the ability for BBSM to pull guest data from the PMS system. This data can then be used to enhance the end-user experience by providing customized content. This feature also provides an interface for viewing guest folios and guest checkout from the room.
Client selection between public and private IPs
Allows service providers to "upsell" their public IP addresses to VPN users as a premium service. Eliminates the VPN issues that occur with the use of private IP addressing. Allows service providers to confidently say that all VPN clients are supported.
Cable modem private IPs and client public IPs
Works with the client selection between public and private IPs feature. Allows for a more cost-effective allocation of VPN-capable public IP addresses to clients and of private IPs to cable modems. Both devices are granted IP addresses from one central DHCP server located on the BBSM server.
Mapping cable modem ports and locations in one step
Allows the technician to map the cable modem port and the location at the same time. Does not require an active session.
RADIUS prepaid account support
Allows Remote Authentication Dial-In User Service (RADIUS) end users to prepay for Internet service from the customer's Internet service provider (ISP).
Support for Cisco switch clustering
Reduces the number of required IP addresses from one per switch to one per cluster (up to 16 switches). BBSM can recognize the entire cluster through one manageable IP address.
Broadband roaming
Allows BBSM to support broadband roaming by adding a new client-BBSM interface and changes to the BBSM-RADIUS interface, while maintaining backwards compatibility with existing BBSM applications. This BBSM release supports the iPass Smart Client. Note that iPass is supported regardless of the page set configured on BBSM; however, a Secure Sockets Layer (SSL) certificate is required.
Session deactivation feature
Allows a BBSM administrator or operator to terminate any active session through the Dashboard, which enables the administrator to have additional control to deactivate any malicious users.
Better support for handheld devices
Provides improved support for micro browsers, such as the Compaq iPAQ device, to correctly display on-screen information.
New Page Set Wizard
Allows BBSM administrators to create their own custom DailyHotel page set by using a web-based wizard, which simplifies custom page set creation.
Improved Switch Discovery Wizard
Quicker and easier switch discovery to simplify configuration. Works with access points and switches in a bridged network topology.
Load balancing
Enables you to configure a number of BBSM servers into a load-balanced and redundant configuration. As additional users log on, the added traffic is balanced, which optimizes performance. Also, if one server becomes disabled, the second server is available to provide uninterrupted service.
MSDE "sa" and BBSD password changes
Provides a user-friendly way to change the Microsoft SQL Server Data Engine (MSDE) "sa" and BBSD login passwords.
New web API for posting PMS charges
Provides an interface for remote applications to post room charges to the PMS.
Improved GUI to simplify configuration and usability
Includes a new Start page for connecting to the Internet, improved port-mapping capabilities, improved navigation in WEBconfig, and the combination of two similar applications, Port Control and Subscription Port Control, into one application: Port Control.
Media and Deployment Options
BBSM manages the delivery of broadband services and the associated network elements. You can use the following media options for BBSM transmission:
•
–
–
•
•
•
Note
The BBSM system supports the following types of networks:
•
•
•
The BBSM server, which is the "router" that all traffic must pass through before reaching the Internet, is assigned router number 0. This number is predefined and always has an IP address of 127.0.0.1. It is a loopback address that the BBSM server uses to communicate with itself. (Figure 1-1 shows an example BBSM network.)
Figure 1-1 Typical BBSM Building Network
Bridged Networks
In a bridged network, packets do not pass through a router from the client to the BBSM server. BBSM is the "router" that connects the bridged network to the Internet. Broadcast packets reach all network computers. All switches are on the BBSM server internal network and are associated with router number 0, which is the BBSM server. (See Figure 1-2.)
Figure 1-2 Basic Bridged BBSM Network
Routed Networks
In a routed network, packets pass through one or more routers from the client to the BBSM server. Because BBSM does not have access to the client's broadcast packets, plug-and-play is not supported. All switches are associated with routers numbered other than "0" (BBSM), and these routers are reachable through gateways on the BBSM internal network. (See Figure 1-3.)
You must enter information within the BBSM network about routers that act as a client's default gateway. As an example, in Figure 1-3, you must specify routers 1 and 2, but router A does not need to be specified. Refer to the "Configuring Routers" section. Of course, the routers themselves still need to be configured separately.
Figure 1-3 Basic Routed BBSM Network
Mixed Routed and Bridged Network
Mixed routed and bridged networks include a bridged network and one or more routed networks. Some switches are on the BBSM server internal network, and others can be reached through gateways on the internal network. See Figure 1-4.
Figure 1-4 Basic Mixed and Routed BBSM Network
BBSM User Groups, Permissions, and Interface
The BBSM Dashboard comprises three primary components, Administration, Operations, and Reports, that are based on user permissions. To perform system functions, select one of the sections under components. The following are the permissions of the corresponding user groups:
•
•
•
The Dashboard and the three components are described in the sections that follow.
Dashboard
The Dashboard is the BBSM home page for accessing BBSM options. (See Figure 1-6.) You can access the Dashboard locally or remotely:
•
•
–
–
Figure 1-5 Enter Network Password
–
- Reports usernames are granted access to reports only.
- Operator usernames are granted access to reports and operations.
- Administrator usernames are granted access to all.
These usernames and passwords are created when a site is created. A site can be created in switch discovery or in WEBconfig during site configuration. (Refer to the "Running the Switch Discovery Wizard" section.)
Figure 1-6 Dashboard for Single Sites
If the BBSM system has multiple sites, the Dashboard contains a drop-down menu from which you select the desired site. (See Figure 1-7.) Then you select the desired Dashboard option.
Figure 1-7 Dashboard for Multiple Sites
Administration
The four Administration options allow you to perform all administrative tasks, including configuring the BBSM system. The Administration section requires that the user have the privileges of the Administrators user group, which is the default Windows 2000 Administrator group. These three options can be accessed only by users with full administrative rights:
•
•
•
•
Figure 1-8 BBSM WEBconfig Default Web Page and Navigation Bar
Table 1-1 describes the WEBconfig web page options.
Operations
The following are the options available under the Operations section of the Dashboard, which requires users to be in the Operators or Administrators user group. This group can view all reports and perform all functions located in the Operations section:
•
•
•
•
If you need to add Operator users, refer to your Windows 2000 documentation for instructions and then choose Start > Programs > Administrative Tools > Computer Management > Local Users and Groups to create the new users. After creating the users, add them to these two Windows groups:
•
•
Reports
The Reports option consists of the Reporting Pages section, which enables you to view BBSM operational data. Users can be in the Reports, Operators, or Administrator user group. The interface consists of seven web pages that are accessible from a toolbar at the top of the page. To close Reports and return to the Dashboard, click the Dashboard link in the upper right corner.
If you need to add Reports users, refer to your Windows 2000 documentation for instructions and then choose Start > Programs > Administrative Tools > Computer Management > Local Users and Groups to create the new users. After creating the users, add them to these two Windows groups:
•
•
Using Navigation Buttons
Most of the BBSM web pages use navigation buttons to locate the appropriate information that you want to see. Use the navigation buttons to locate the correct record before making changes. (See Table 1-2.)
When no records exist for that function, the button is disabled. For example, the First and Previous buttons are grayed out when you are viewing the first record.
Connecting a Client to BBSM
To connect a client to BBSM, the client should meet minimum requirements to ensure successful operation. This section describes those requirements and how end users connect to the BBSM server. Table 1-3 shows the operating system and browser versions that have been tested and are supported for BBSM software release 5.2.
The page set that the BBSM administrator selects in the Switch Discovery Wizard or from the Page Set drop-down menu in the WEBconfig Network Element Port Settings pop-up window determines which Start page the end user uses to connect to the Internet. Figure 1-9 shows the DailyHotel Start page that was customized using the Page Set wizard.
Figure 1-9 DailyHotel Start Page
The following example demonstrates a general connection sequence for an end user.
A hotel has purchased a BBSM server, set it up, and selected the DailyHotel page set. After checking into a hotel room, an end user with a laptop computer might do the following:
Step 1
Step 2
Step 3
Step 4
Advanced Topics
The following sections describe many BBSM features and components. Features not requiring detailed discussions are described in "Basic BBSM Configuration." The following are described in this section:
•
Bandwidth Reservation
BBSM software release 5.2 enables hotel customers to reserve bandwidth for meetings that require broadband access. When hotel customers reserve meeting rooms, they have the option of specifying a bandwidth reservation for their meeting. During the meeting when guests are logged in, the reserved bandwidth is available only to meeting room guests.
Being able to reserve bandwidth provides several specific advantages to the hotel:
•
•
Hotels that want to take advantage of bandwidth reservation do not need to buy any additional bandwidth. Instead, they can re-allocate their existing bandwidth. For example, if a hotel has 1,000 kbps of bandwidth currently allocated for guest use, a bandwidth reservation of 200 kbps would decrease the total amount of bandwidth available for general guest use to 800 kbps. In addition, reservations do not actually decrement the total hotel bandwidth unless someone is logged into the reservation. As soon as the last person using the reserved bandwidth logs out, the bandwidth is available again for guest use.
For this reason, it is important not to oversubscribe the network. If the full amount of bandwidth were reserved, no bandwidth would be left for hotel guests. Each hotel must determine how much bandwidth it wants to provide for its guests and weigh that against the increased revenue potential of the bandwidth reservation system.
Bandwidth Throttling and Bandwidth Reservation
BBSM software release 5.2 supports the bandwidth throttling feature used in previous releases and a new bandwidth reservation feature. These are described below:
•
•
http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121newft/121t/121t2/
clsbsshp.htmHow Reserved Bandwidth is Used
To access the reserved bandwidth, you connect to BBSM using an access code that is generated when you make the reservation. This is similar to the access code feature that existed in previous versions of BBSM. The number of needed access codes is specified when the reservation is made (the maximum number is 1,000). Because all access codes for a group (reservation) will share the reserved bandwidth, bandwidth is reserved per group, not per access code. Larger groups will require more bandwidth.
Access codes are normally used from the meeting room where a group is convening. However, the bandwidth reservation is not tied to any particular port, so users are not limited to the meeting room. If meeting room attendees are also hotel guests, they can use their access code to log in from their room, and they still receive their reserved bandwidth. (This depends on the page set that is available from the guest rooms, as not all page sets allow users to enter an access code.)
Although access codes are not confined to a port, they are confined to a site. For this reason, users at one hotel site cannot travel to another site and expect to connect using a single access code for both.
Modifying Bandwidth Reservations
A bandwidth reservation can be edited at any time with the calendar user interface described in the "Creating and Configuring Access Codes" section. If a hotel needs to change the bandwidth for any reservation, it can select a different class of service associated with that reservation before and during the event time.
If a bandwidth is modified during the event and users are logged into the reservation, the new bandwidth is not applied to existing users. The new bandwidth applies for the rest of the reservation time for all new clients logging in. This provides the hotel with some recourse in case the system becomes too heavily subscribed.
Preserving Historical Information
For auditing purposes, the access code system allows customers to view past and future reservations, including any bandwidth that was reserved. The Delete button can be used to delete a class of service only if no past or future reservations exist at this class of service. If reservations exist for this class of service, it cannot be deleted, but it can be disabled to prevent any new reservations from being made.
Classes of Service
BBSM creates bandwidth classes of service that correspond to different levels of Internet service. In a particular day, several different bandwidth reservations may exist that are composed of different classes. For example, if a hotel has set aside 500 kbps for meeting room bandwidth reservations, it could define three classes of service— 300 kbps, 200 kbps, and 100 kbps. Notice that the total bandwidth exceeds the maximum of 500 kbps, so the system would not allow all three classes of service to be reserved for one day. However, one day the system might have five reservations at the 100 kbps class, and the next day it might have three reservations—one at the 100 kbps class and two at the 200 kbps class. The reservation system would ensure that no more than 500 kbps are reserved for any one day, but the classes can be combined in any way to total 500 kbps. Because this solution provides greater flexibility, the bandwidth reservation feature on BBSM uses this class of service model.
BBSM administrators have the ability to add their own classes of service. In addition, the BBSM installation creates several predefined classes of service.
After a class of service is created, all properties can be modified until the class of service is used for a reservation. Once a reservation exists using the class of service, its name and bandwidth cannot be modified to ensure that the network does not become oversubscribed. A maximum of 64 classes of service can be created.
What Bandwidth Reservation Adds to Your Router
In some cases, the external router is managed by an ISP who may be concerned about the configuration that BBSM adds to the router. If you are working with an ISP who needs more information about what the bandwidth reservation feature adds to the router, this section describes the router configuration in more detail. Note that no BBSM bandwidth reservation commands are ever entered manually on the router; BBSM adds them automatically when the bandwidth reservation feature is used.
Bandwidth reservation uses the IOS Class-Based Shaping feature to configure the router. Refer to the following website for documentation about Class-Based Shaping:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121newft/121t/121t2/
clsbsshp.htmThe configuration added to the router consists of a policy map, several class maps (one for each class of service), and one extended access list for each class map. Some parts of the configuration are static, and some are dynamic, as follows:
•
•
None of the configuration is stored in permanent memory (NVRAM). It is only in the running configuration. If you reload your running configuration, you will erase the bandwidth reservation configuration.
All of the configuration settings on the router contain the string "BBSM." If you want to try out the bandwidth reservation feature, first create a reservation. (Refer to "Creating and Configuring Access Codes" section.) Then log in to BBSM as an end user using an access code. Now telnet to your external router and view the running configuration. Look for the BBSM string. The policy map, class maps, and extended access lists all have names that include this string. As mentioned earlier, when you deactivate the client session, the dynamic part of the configuration is removed. However, you can always reload the running configuration on the router to restore the previous configuration.
Page Sets
BBSM uses page sets made up of active server page (ASP) files, commonly called "pages." BBSM ships with default page sets that you can modify to meet your needs (see Table 1-4).
When the end user starts their session, the page set ASP files execute on the BBSM server and on the end user's browser. Different page sets contain different types of ASP files. By choosing specific page sets, you are selecting ASP files that associate an access policy and, if desired, an accounting policy with a specific port. These policies define the access and accounting methods that will be used for the end user's session. They are described briefly below:
•
•
If the end user will be entering sensitive information, such as credit card information, then you should use page sets that provide SSL. For these SSL page sets, you must buy and install an SSL certificate. For complete details on installing the certificate, refer to "Installing an SSL Certificate." The other default BBSM page sets transmit data in clear text.
To configuring your ports, you have the following page set options:
•
•
•
http://www.cisco.com/pcgi-bin/tablebuild.pl/bbsm52
For information on adding the custom page set to the list of available page sets, refer to the "Adding Custom Page Sets to BBSM" section.
Caution
If you are using multinets, note that the page set assigned to the user's port determines whether an administrator or operator provisions the multinet or the end user self-provisions the multinet. Table 1-4 shows which page sets the end user can self-provision.
Port Hopping
The port hopping feature allows wireless users to move from port to port without interrupting BBSM service. Within a BBSM network, users can move between like types of hardware, such as wireless access points, switch ports, or cable modems. Users cannot hop back and forth between wireless access points and wired switches. Also, mobility across subnets or cells operated by different customers is not supported.
Port hopping is disabled by default, and only the administrator can enable it. For procedures on different ways to configure port hopping, refer to the following sections:
•
•
•
When port hopping is enabled, BBSM keeps the session active when the user moves to another port or disassociates temporarily. For example, disassociation might occur when the signal is weak or an object comes between the wireless access point and the end user, which causes the user to associate suddenly with a secondary access point that might be configured to another aggregation switch port.
When a user dissociates from the BBSM network, BBSM searches for the user until one of the following occurs:
•
•
Transactions that occur while using port hopping are logged to the Transaction History report. Each time a port hop event occurs, BBSM makes an entry into the Transaction History report to record the event. You can view these transactions through the Reporting Pages link on the Dashboard.
Note the following about port hopping:
•
•
–
–
•
Note
•
•
–
–
•
Port hopping works with any BBSM page set. However, some page sets apply more than others; for example, as follows:
•
•
Private and Public IP Addresses (Multinets)
With BBSM software release 5.2, you can offer your end users the choice of using individually assigned private or public DHCP IP addresses:
•
•
To explain the difference between private and public IP addresses, we can compare the IP address to a phone number. A public IP address is equivalent to a full 10-digit telephone number (619-555-1234), and a private address is equivalent to an office extension number.
The end user's needs determine which type of IP address is the best one to use:
•
•
A BBSM server that is configured to support both private and public IP addresses is classified as multinet, because the internal NIC is configured with two distinct logical subnets. A singlenet BBSM server is configured as a single logical subnet and supports only one logical subnet of IP address.
For the initial configuration, the way that BBSM is configured for multinet differs based on whether BBSM is customer installed or factory installed:
•
•
Note
For additional information about multinet use, refer to the following sections:
•
•
•
RADIUS
The BBSM server has a built-in RADIUS client that complies with RADIUS standards, RFCs 2865 and 2866 and is compatible with any compliant RADIUS server, although the officially supported servers are Cisco ACS, Microsoft IAS, and Navis. This section describes the BBSM interface with the RADIUS server, including the RADIUS attributes that BBSM supports, user-provisioned bandwidth page sets, and prepaid RADIUS.
For details on BBSM configuration and reporting, refer to the following sections:
•
RADIUS Authentication and Authorization
Each time the end user connects to the BBSM server using a page set configured for RADIUS, BBSM prompts for a username and password and then sends this data to a configured RADIUS authentication server in an access-request packet. Note that the RADIUS authentication server does not have to be the same server as the RADIUS accounting server.
To provide redundancy in case the RADIUS server does not respond, you can configure multiple RADIUS servers in WEBconfig. This configuration includes the order in which these servers are contacted, with 1 being the first server contacted; 2, the second server contacted; and so on (Configuring RADIUS Billing). BBSM attempts to contact the servers until an access-accept packet is received:
•
•
RADIUS Accounting
BBSM saves Internet session information and then sends it to a configured RADIUS accounting server in start and stop accounting-request packets and, if configured, in interim-update packets. BBSM sends this data in the same ranked order and manner that it uses for access-request packets. With this session data, administrators can perform independent billing on a flat-rate or per-minute basis.
RADIUS Attributes
This section describes the RADIUS attributes that BBSM sends to the RADIUS server and receives from the server. Table 1-5 lists the access-request and accounting-request attributes by packet type, and Table 1-6 describes these attributes and several others that could be included in the access-accept packet from the RADIUS server.
Table 1-6 RADIUS Attribute Descriptions
User-Name
1
The end user enters this name to authenticate against the RADIUS server and access the Internet through BBSM.
User-Password
2
The end user enters this password to authenticate against the RADIUS server and access the Internet through BBSM. The password is encrypted before being sent to the RADIUS server.
NAT-IP-Address
4
Either the IP address of the BBSM external NIC or the IP address entered as the NAT IP address on the WEBconfig RADIUS Server web page.
NAS-Port
5
The NAS-Port value is a numeric value (therefore the leading zeros of the site number are dropped). BBSM maps the NAS-Port attribute as the following: aaabbccddd, where aaa = site number, bb = cluster, cc = switch, and ddd = port.
For example, if the site number = 1, the cluster number = 2, the switch number = 3, and the port number = 5, the NAS-Port number = 10203005.
Service-Type
6
The number 2 in this field indicates "Framed."
Framed-Protocol
7
The number 1 in this field indicates "PPP" (point-to-point protocol). Note that for historical reasons, BBSM sends 1 in this attribute even though clients do not usually use PPP.
Framed-IP-Address
8
IP address of client connecting to the Internet through BBSM.
Reply-Message
18
If this attribute is included in the Access-Accept packet, BBSM forwards this string to the Smart Client using the XML tag, <AuthenticationReply>.
Class
25
Use this attribute to send optional information to the accounting server. If this attribute is included in the Access-Accept packet, BBSM sends this information unmodified to the accounting server.
Vendor-Specific
26
The end-user bandwidth (in kbps). You can use the bandwidth Vendor-Specific attribute (VSA) in two different scenarios:
•
•
The following is the format for the BBSM bandwidth vendor-specific attribute (VSA):
–
–
–
–
–
–
Session-Timeout
27
If this attribute is included in the access-accept packet, BBSM terminates the session after the number of Session-Timeout seconds unless the session has terminated earlier for another reason.
Called-Station-Id
30
The MAC address of the BBSM internal NIC. The string is a sequence of 12 hexadecimal characters.
Calling-Station-Id
31
The MAC address of the client (end-user) NIC.
NAS-Identifier
32
The NAS Identifier value entered on the WEBconfig RADIUS Server web page. If no value is entered in this field, BBSM does not include this attribute in the RADIUS Access-Request packet.
Acct-Status-Type
40
The number contained in this field indicates one of the following types of Accounting-Request packets:
1 = Start Accounting-Request
2 = Interim-Update Accounting-Request
3 = Stop Accounting-Request
Acct-Input-Octets
42
The number of octets (bytes) that BBSM received from the end user during their session.
Acct-Output-Octets
43
The number of octets (bytes) that BBSM transmitted to the end user during their session.
Acct-Session-Id
44
The unique Session ID assigned to each BBSM end-user session used to identify all authentication and accounting messages generated for a single user session.
Acct-Session-Time
46
The number of seconds for which the end user received service.
Acct-Input-Packets
47
The number of packets that BBSM received from the end user during the user's session.
Acct-Output-Packets
48
The number of packets that BBSM transmitted to the end user during the user's session.
Acct-Terminate-Cause
49
The number contained in this field indicates how the session was terminated, as follows:
1 = User Request—Action by the end user caused the session to terminate; for example, the user visited the disconnect URL.
4 = Idle Timeout—Network equipment detected that the end user disappeared from the network.
5 = Session Timeout—The access policy determined that the session should end; for example, the session duration reached the Session-Timeout attribute specified in an Access-Accept.
6 = Admin Reset—Action by the administrator caused the session to terminate.
NAS-Port-Type
61
5 = Virtual.
User-Provisioned Bandwidth
The two user-provisioned bandwidth (UBand) page sets, RADIUSUBand and RADIUSUBandClear, allow administrators to define bandwidth offerings. The end user then chooses the desired bandwidth on the Start page, such as the following:
•
•
•
BBSM throttles the session at the selected bandwidth and sends the bandwidth VSA to the RADIUS accounting server in the start, stop, and interim-update accounting-request packets. Note that the administrator must ensure that the RADIUS accounting server is configured to accept this bandwidth so the data can be retrieved for bi
