The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter describes learning of interface topology and association of the remote cable MSO links solution.
To control and report traffic in the context of a remote interface, you must map the topology in terms of the available CMTS interfaces and their associated bandwidth. This map must include keys that are used by the SCE to associate subscriber traffic with specific interfaces.
The SCE learns the interface topology by retrieving the CMTS configuration using the Simple Network Management Protocol (SNMP) and converting the configuration to a virtual links map. Virtual links are provisioned to the relevant SCEs.
VLM queries the CMTS device and learns the upstream and downstream channels, their names, and their rates. VLM supports a single primary channel per wideband group. For primary channels within a wideband group, VLM queries the CMTS for resource allocation that is reserved for legacy modems.
For downstream channels, VLM obtains the mapping information of the channels to wideband groups. For the wideband channels, VLM extracts the:
•Wideband to narrowband mapping to detect a primary channel
•Wideband name from the Interface MIB
•Mapping of channels that belong to the wideband group and their rates to calculate the wideband rate
The parameters for the primary and secondary channels include:
•Peak Information Rate (PIR)
•Committed Information Rate (CIR)
Table 3-1 list the parameters and their values for primary and secondary channels and the dynamic AGCs.
Interface association awareness is achieved through DHCP integration. The CMTS IP (specifically, the Relay-Agent IP, or giaddr) is part of the DHCP dialog and upstream and downstream interface IDs are included in the Relay-Agent option (for example, option 82 [encoded in suboption 1, the circuit ID]). This information allows the SCE to uniquely identify upstream and downstream interfaces to which a subscriber is mapped, even in cases in which more than one CMTS is connected to an SCE.
Note If multiple CMTS devices connected to an SCE have the same SNMP SysName, the VLM fails to identify the duplication and results in an unpredictable behavior.
The SCE DHCP sniffer login event generator (LEG) extracts the CMTS IP and reports it to the subscriber manager, which performs the appropriate virtual-link association, allowing the SCE to manage the traffic correctly.
Wideband channels are associated with three AGCs in a two level hierarchy and the cable modems are mapped to their respective AGC. For information on the AGC mapping see Bandwidth Control Enhancements and Mapping of Cable Modems Through DHCP Sniffing.
Note The VLM device learning does not support interfaces that are directly associated to a Mac domain; it only supports interfaces associated to a bonding group.
When the VLM queries the CMTS device, it reads all the IP addresses from the CMTS device IP table and creates the mapping table that is used to map IPs to the CMTS device to which they are related. Many of the IP addresses that are read from the CMTS device are not used by subscribers which can cause the mapping table to become too big and unmanageable. To prevent this, the VLM dynamically selects and releases the giaddr values from the IP table.
When a subscriber logs in, the CMTS device appends the giaddr to the DHCP transaction. For giaddr that is new to the DHCP LEG (or an existing giaddr that was not used during previous logins):
•If the login giaddr value is known to the VLM (related to one of the CMTS devices), the VLM updates the DHCP LEG with the policy mapping table related to the login giaddr value.
•If the login giaddr value is unknown to VLM (if the IP is not related to any device in the VLM), the VLM opens the SNMP connection using the login giaddr value as an IP address, and queries the SNMP connection to get the device host name (sysName OID):
–If a device exists with the same host name, it indicates that a new IP was added to the device therefore the VLM:
•Queries the device to learn the new updates
•Updates the policy mappings based on the query output and updates the LEG
•Login operations continues on the device
–If the device host name is invalid, it indicates one of the following causes:
•Device is not configured as expected (sysName MIB value is not set).
•Device was not intended to be part of the VLM solution.
•Subscriber is logged in without a vlink policy mapping.
–If the device host name is valid, name is new to the VLM, and the dynamic device feature is enabled:
•VLM creates a new device using the device host name.
•Login operations using the same giaddr value are blocked by the LEG.
•VLM starts querying the new device and updates its policy mappings accordingly.
•Login continues on the device.
From Service Control Application for Broadband Release 3.6.5, for a static device configuration, you can disable learning new giaddr during login. After you disable learning new giaddr, if the SM identifies that the relay agent does not belong to any known CMTS, the SM continues to login instead of doing a query. During periodic queries, the SM continues to learn new giaddrs. To disable learning new giaddr during login, set enable_dynamic_giaddrs_learning to false.
•For giaddr that is known to the DHCP LEG (or an existing giaddr that was in use during the previous logins):
–If the policy mappings are found, a subscriber is created using the policy mappings.
–During a login operation if the policy mappings are not found:
•All login operations related to the device that belongs to the giaddr are put on hold by the DHCP LEG.
•Based on the giaddr value received from DHCP, the VLM identifies the device associated with the giaddr, and queries the device.
•After the query is completed, the policy mappings are updated in the LEG.
Note When the VLM queries a device, all login operations of the affected device is stored in a queue. After completing the query operations the login process resumes and there is no loss of login operations. Each subscriber is logged in with their respective mappings.
•VLM defines a lease time for each dynamic giaddr. If no further login operations occur during the lease time period:
–VLM removes the giaddr from its list of giaddr values.
–IP value is no longer a giaddr in the CMTS device (when performing p3vlink --show-device -d <device>, the giaddr attribute does not contain the removed IP).
–LEG removes the entries from the mapping table that are related to the giaddr.
–For each subscriber, the VLM checks if the subscriber giaddr custom property is the same as the removed giaddr and if so, changes the property to be the IP address of the CMTS device.
The following example shows the current details of a subscriber:
p3subs --show -s lynn_jones
Name: lynn_jones
Domain: subscribers
Mappings:
IP: 1.1.1.13/32
Properties:
downVlinkId=7 Name=device1_1_Cmts8/1-downstream1
upVlinkId=4 Name=device1_1_Cmts8/1-upstream1
Custom Properties:
giaddr=1.1.1.1
Command terminated successfully
If the IP address 1.1.1.1 is the removed giaddr and 2.2.2.2 is the CMTS device IP address, the result of the lease time operation is as follows:
p3subs --show -s lynn_jones
Name: lynn_jones
Domain: subscribers
Mappings:
IP: 1.1.1.13/32
Properties:
downVlinkId=7 Name=device1_1_Cmts8/1-downstream1
upVlinkId=4 Name=device1_1_Cmts8/1-upstream1
Custom Properties:
giaddr=2.2.2.2
Command terminated successfully
•When a CMTS device reboots, the CMTS allocates new ifIndex values for the interfaces, specifically when the downstream ifIndex values are changed and the VLM mappings are no longer synchronized. The VLM monitors the upstream and downstream parameters of option 82 and compares the values against the mapping tables. If a mismatch is found in the DHCP transaction parameters, VLM initiates a synchronization process with the CMTS device. During this process:
–DHCP transactions of the affected CMTS device are placed on hold. The VLM buffer is capable of storing 100,000 DHCP events per CMTS.
–LEG queues up the subscriber login request.
–On completion of device query operation, the VLM notifies the LEG.
–LEG removes the stored messages in the queue and restarts the login operation.
–DHCP transactions of any newly detected CMTS device is stored in the queue until VLM queries the new CMTS information.
SCE virtual links emulate the physical interfaces of the CMTSs and the VLM provisions the links with the bandwidth required to control the traffic:
1. For each CMTS physical interface (either upstream or downstream), the VLM creates a virtual link on the SCE.
2. VLM maps traffic that travels from a subscriber that is associated to this interface to the virtual link.
3. To create the proper association of subscribers to virtual links, the VLM creates a mapping between the DHCP information (CMTS-ID, upstream-ID, downstream-ID) and the virtual link IDs.
–VLM creates a channel and an upstream virtual link for every upstream-ID on a CMTS.
–VLM creates a legacy channel or wideband and legacy channels for a downstream virtual link for every downstream-ID on a CMTS.
Subscriber management logic is required to associate subscribers with their upstream and downstream virtual links based on the attributes that the DHCP LEG extracts from the DHCP traffic.
For a downstream virtual link, the Subscriber Manager (SM) login determines if the subscriber is associated with legacy or wideband cable modems. Depending on the subscribers modem types they are mapped either to wideband or legacy (primary) channels:
•Subscribers with wideband cable modems are mapped to the wideband channel beneath the VLink.
•Subscribers with legacy modems are mapped to legacy channels beneath the VLink.
In addition to the virtual links association, the subscriber is also assigned a package. In terms of bandwidth management, you can only use schemes that use one virtual-link-controller per direction; therefore, you should design the bandwidth controller architecture (committed information rate, peak information rate, and assurance level) accordingly.