InCa help

InCa

Managing DOCSIS and EuroDOCSIS based

networks.

User's guideCopyright © 2002-2005 iKron Kft.

InCa – User's Guide

ContentsI.Introduction......................................................................................................................... 5

1.About the system.......................................................................................................... 5II.Components and operation............................................................................................... 6

1.InCa components.......................................................................................................... 62.IP network structure...................................................................................................... 6

2.1.Network groups...................................................................................................... 62.2.IP address assignment strategy ............................................................................ 7

3.CoS profiles................................................................................................................... 74.Cable modem software updates................................................................................... 75.Clients – terminal nodes................................................................................................ 76.Terminal node statuses, connection between the statuses and the system ................ 8

6.1.Statuses................................................................................................................. 86.2.Operating terminal nodes....................................................................................... 9

III.Using the system............................................................................................................ 101.The user interface....................................................................................................... 10

1.1.Getting to know the interface............................................................................... 101.1.1.The menu system......................................................................................... 101.1.2.Connection of windows................................................................................. 101.1.3.Search page................................................................................................. 111.1.4.The list page................................................................................................. 111.1.5.Editing page.................................................................................................. 111.1.6.Special data items........................................................................................ 12

1.1.6.1.Fields with selection icon....................................................................... 121.1.6.2.Telephone number................................................................................ 121.1.6.3.E-mail address...................................................................................... 12

1.2.Menu structure..................................................................................................... 131.3.Network menu item.............................................................................................. 13

1.3.1.Structure....................................................................................................... 131.3.1.1.CATV..................................................................................................... 131.3.1.2.Headend................................................................................................ 131.3.1.3.CMTS.................................................................................................... 131.3.1.4.Physical interface.................................................................................. 141.3.1.5.Logical interface.................................................................................... 151.3.1.6.IP network............................................................................................. 151.3.1.7.IP pool................................................................................................... 16

1.3.2.IP address.................................................................................................... 161.3.3.Network group.............................................................................................. 161.3.4.CoS 1.0......................................................................................................... 161.3.5.CoS 1.1......................................................................................................... 17

1.3.5.1.US Flow................................................................................................. 171.3.5.2.DS Flow................................................................................................. 181.3.5.3.IP packet classifier................................................................................ 18

1.3.6.Package........................................................................................................ 191.3.7.City................................................................................................................ 201.3.8.Street............................................................................................................ 201.3.9.Upstream...................................................................................................... 20

1.4.Cable modem menu item..................................................................................... 201.4.1.Cable modem data....................................................................................... 20

2


1.4.2.Online........................................................................................................... 211.4.2.1.Search conditions.................................................................................. 211.4.2.2.The result list......................................................................................... 221.4.2.3.Cable modem information page............................................................ 25

1.4.3.All.................................................................................................................. 251.4.4.Save / Individual........................................................................................... 251.4.5.Save / Grouped............................................................................................ 261.4.6.Manufacturer................................................................................................ 261.4.7.Type.............................................................................................................. 261.4.8.Software versions......................................................................................... 261.4.9.Supplier........................................................................................................ 271.4.10.Stock........................................................................................................... 27

1.5.Client menu item.................................................................................................. 271.5.1.Client data.................................................................................................... 271.5.2.Terminal node data....................................................................................... 271.5.3.Search.......................................................................................................... 281.5.4.Save............................................................................................................. 281.5.5.Terminal node settings................................................................................. 28

1.5.5.1.Status.................................................................................................... 281.5.5.2.Package................................................................................................ 281.5.5.3.Modem.................................................................................................. 29

1.5.6.Lists.............................................................................................................. 291.6.Statistics.............................................................................................................. 29

1.6.1.Network......................................................................................................... 291.6.2.Consumption summary................................................................................. 301.6.3.Cable modem............................................................................................... 301.6.4.Client............................................................................................................ 301.6.5.Terminal node............................................................................................... 30

1.7.Operation............................................................................................................. 301.8.Other.................................................................................................................... 31

1.8.1.Letter templates............................................................................................ 311.8.2.Permissions.................................................................................................. 31

1.8.2.1.Users..................................................................................................... 311.8.2.2.User data............................................................................................... 31

1.8.3.User settings................................................................................................. 311.8.4.System parameters...................................................................................... 32

1.9.Log out................................................................................................................. 322.Application server........................................................................................................ 32

IV.Starting to use the system............................................................................................. 351.Network configuration................................................................................................. 35

1.1.Defining the IP addresses.................................................................................... 351.2.Defining the network groups................................................................................ 351.3.Defining the server............................................................................................... 351.4.Defining IP networks and pools .......................................................................... 351.5.Defining the service areas................................................................................... 36

2.Package...................................................................................................................... 362.1.Adding CoS 1.0 profiles....................................................................................... 362.2.Adding CoS 1.1 profiles....................................................................................... 362.3.Creating packages............................................................................................... 36

3.Modem data................................................................................................................ 36

3


3.1.Cable modem manufactures................................................................................ 363.2.Cable modem types............................................................................................. 373.3.Suppliers.............................................................................................................. 373.4.Modems............................................................................................................... 37

4.Client, terminal node................................................................................................... 374.1.Adding new clients............................................................................................... 374.2.Adding new terminal nodes.................................................................................. 37

V.Examples........................................................................................................................ 381.Example 1................................................................................................................... 38

1.1.Add a new Network group ................................................................................... 381.2.Add a new IP network and an IP pool within it for the modems: .........................381.3.Add a new private IP network and two IP pools within it for the clients' devices:....391.4.Add a new public IP network and an IP pool within it for the clients' devices:..... 391.5.Create suitable CoS 1.0 profiles for your services............................................... 401.6.Create suitable CoS 1.1 profiles for your services............................................... 411.7.Define suitable packages for your services ........................................................ 43

2.Example 2................................................................................................................... 442.1.Defining a CoS 1.1 profile.................................................................................... 44

VI.Support for performing daily tasks................................................................................. 461.Receiving cable modems............................................................................................ 462.Entering new subscription........................................................................................... 463.Suspending the service............................................................................................... 464.Withdrawing service suspension ................................................................................ 475.Replacing cable modems at clients............................................................................. 476.Checking the operation of the system......................................................................... 47

6.1.Checking the application server........................................................................... 476.2.Checking the network.......................................................................................... 47

4


I.IntroductionThe introductory chapter presents a brief description of the InCa system.

1.About the systemInCa is an application for managing DOCSIS and EuroDOCSIS based internet service

provision on CATV networks.

Main features:

• Separated client and terminal node maintenance

• Cable modem maintenance including manufacturers, types, software versions

• Generating configuration files for cable modems

• DHCP service for cable modems and other customer premises equipment

• Full logging and retrieval facilities

• QoS according to EuroDOCSIS / DOCSIS 1.0. Settings according to EuroDOCSIS /

DOCSIS 1.1.

I.Introduction 5


II.Components and operationThe present chapter describes the components of the system, and its operation.

1.InCa componentsThe InCa consists of two components: a web interface and the application servers.

The dynamic web interface is JSP based, it requires a JSP server. It allows you to

manage the client and modem data, control and monitor the network.

The application servers provide data for the CMTS, the cable modems and the customer

premises equipment (netserver), and collect information about the operation of the

network (adminserver).

2.IP network structureAll items in the IP network have an IP address.

The IP addresses of the cable modems are assigned dynamically and automatically based

on the parameters of the package associated with the cable modem.

The addresses of the customer premises equipment are generated as they are defined in

the packages. The devices may have either fixed or dynamic IP addresses.

2.1.Network groupsThe IP address ranges handled by the InCa system are divided into groups. In a network

group there must be IP addresses for both the cable modems and the customer premises

equipment.

This grouping enables the service provider to handle different IP address ranges together,

therefore, it is easier to define the IP addresses of devices using a given package.

Furthermore, if network groups are defined for different client groups, it is possible to

completely separate the networks of the client groups, giving opportunity for example to

create a VPN consisting of private IP addresses.

II.Components and operation 6


2.2.IP address assignment strategy During the connection process, first the cable modem gets an IP address. On the basis of

the MAC address of the cable modem, the system first defines the terminal node and then

the package which can be used at that terminal node. Then the system chooses one of

the cable modem IP addresses assigned to the given network group.

Secondly, the CPE gets an IP address. This time, regarding the cable modem used for the

connection, the package and the appropriate network group are defined, then the IP

address is assigned according to the conditions (private/public) specified in the package.

3.CoS profilesThe InCa manages CoS profiles compliant with both DOCSIS 1.0 and 1.1 standards.

In case of the packages the CoS profile of both standards must be defined. After the cable

modem has logged in, it gets the configuration file which is compliant with the standard

used by the cable modem.

4.Cable modem software updatesThe system allows the remote replacement of the internal software of the cable modems.

First, the cable modem software must be saved in the system on the CABLE MODEM /

SOFTWARE VERSION page. Next, you must set the update to be the default software version in

the CABLE MODEM / TYPE window.

Once it is done, the cable modems automatically download the updates when they are

logged in.

Logging in may be forced by the RESET button of the CABLE MODEM / ONLINE window.

5.Clients – terminal nodesThe client is the financer partner using the cable modem internet service. One client may

have several terminal nodes working independently.

The terminal node is the cable modem connection point. At a terminal node, there is one

subscription (package) and one cable modem. (There is one special exception which will

be discussed later at the recording of the terminal nodes.)

If more than one cable modems are to be used at a particular location (city, street, building

number, building number #2), a separate terminal node must be saved for all the cable

modems which are to be installed.



6.Terminal node statuses, connection between the statuses and thesystem

6.1.StatusesThe InCa system uses the following terminal node statuses:

DEMAND: Initial status of the received demands which are to be processed.

Possible succeeding statuses: READY FOR CONNECTION, WAITING DEMAND, TERMINATED .

READY FOR CONNECTION: The demand can be fulfilled as for the administration. After switching

to this status, the system automatically changes the status to one of the following:

TO BE CONNECTED: if the terminal node located in an upstream capable area.

CANNOT BE CONNECTED: otherwise.

TO BE CONNECTED: This status informs the technical staff that the terminal node must be

connected.

Succeeding statuses: CONNECTION IN PROGRESS, TERMINATED .

CONNECTION IN PROGRESS: the technical staff informs the system by this status that they are

still working at the terminal node.

Succeeding statuses: CONNECTED, TERMINATED .

CONNECTED: By this status the technical staff informs the system that the terminal node has

been connected to the network, the system can be used.

Succeeding statuses: TERMINATED, SUSPENDED.

CANNOT BE CONNECTED: The system shows that the node cannot be connected as it is not

upstream capable. The system automatically switches to WAITING DEMAND status.

WAITING DEMAND: The unfulfilled demands are waiting for network development. If the

terminal node becomes upstream capable, the system automatically switches it to TO BE

NOTIFIED status.

Succeeding statuses: TO BE NOTIFIED, TERMINATED .

TO BE NOTIFIED: An earlier WAITING DEMAND has become connectable.

Succeeding statuses: READY FOR CONNECTION, TERMINATED .

TERMINATED: Service has ceased at the terminal node.

Succeeding statuses: RECONNECT.

RECONNECT: A terminal node which has been terminated can be reconnected to the system.

Succeeding statuses: READY FOR CONNECTION, TERMINATED .

SUSPENDED: A status for suspending a terminal node.

Succeeding statuses: CONNECTED, TERMINATED .



6.2.Operating terminal nodesThe system regards a terminal node operating if there is a package assigned to it, and its

status is either CONNECTION IN PROGRESS or CONNECTED .



III.Using the systemThe present chapter describes the user interface of the system and the commands of the

application server.

1.The user interface

1.1.Getting to know the interfaceThe InCa has a web user interface which can be accessed via a browser. The operating

parameters of the system can be set on this interface.

You find the InCa web interface at the address: https://inca-server-ipaddress

It is divided into three main parts:

• A two-line menu bar on the top of the page.

• Status bar below the menu bar

• The rest of the page is the largest part: the actual operations are performed here. It

always shows the page relating to the selected menu item.

1.1.1.The menu systemClicking the main menu items, an information page appears about the menu items of the

given menu group and the items become accessible.

If you select one of the menu items, the first window of its function group is shown.

1.1.2.Connection of windowsThe pages belonging to the functions are built up according to the same principle. The

chart below illustrates which page the different operations lead to.

III.Using the system 10

Search page List Editing page

Menu item

Search

New Search

New entry

Edit

BackSave

Delete


1.1.3.Search pageHere you can define which data you want to see in the list.

If no filter is set here, all items will be shown in the list.

The search result contains only the items which satisfy all the conditions.

Setting the search conditions:

Text box: looks for words starting by the given word. Checking the REGULAR EXPRESSION

checkbox, the system looks for items matching the given regular expression. Regular

expressions contain “*” and “?” characters which stand for any or one letter respectively.

Roll down list: the list will contain the rows belonging to the given item.

List: several items can be selected (CTRL+left click). The list will contain the rows

belonging to the given item(s).

1.1.4.The list pageHere, there is a complex table. Its top and bottom show the following control panel:

The text in the middle of the panel shows how many pages the list contains and which

page is actually shown. you can move forward and backward in the list by the right and left

arrows of the panel.

Clicking the NEW SEARCH button you get to the search window, the ADD NEW button leads to

the editing window, where new items can be added to the list.

The heading of the list is below the upper control panel, where you can set which column

you want to arrange the list by. Use the up and down arrows.

If you click the rows of the list you get to the editing page.

1.1.5.Editing pageThe data appear in two columns: the description of the data on the left, its value on the

right.

Input fields:

Text field: type the value of the data. In case of some data, the input must contain breaks

(e.g.: MAC address).

Roll down list: the possible data are included in the list.

Date field: type the date, or use the icon next to the field and chose the appropriate date

from the calendar.

Selection field: type the date, or use the search icon to look for the item and select it. If the



data is typed, the system checks if it is correct when the data is saved.

Several line field: type the data. Use the ENTER key for starting a new row.

Buttons:

BACK: back to the list window.

SAVE: save the new data or the modifications. If a fault occurs during saving, the system

informs us on the source of the error in a pop-up window.

1.1.6.Special data items

1.1.6.1.Fields with selection iconIn case of fields where there is a magnifier icon next to them, the icon brings up a new

window which contains all the selectable items.

The list is arranged in alphabetical order, if you click a letter in the bottom row of the

window, the data starting with the given letter appear. (If no data starts with a particular

letter, it will not appear in the bottom line.) If you have typed some letters into the field

before you clicked on the icon, the new window will be filtered with the specified prefix.

If you select one of the items in the list, the window will be closed and the selected item

will be entered in the field.

1.1.6.2.Telephone numberThe telephone numbers are stored in the system in the following format: + COUNTRY CODE /

AREA CODE TELEPHONE NUMBER.

1.1.6.3.E-mail addressThe email addresses are stored in the following format: [email protected], where TLD is the

top level domain, which is the last element of the domain name. ('hu' in Hungary)



1.2.Menu structure

1.3.Network menu item

1.3.1.StructureThis item shows the hierarchical structure of the system. The structure opens from left to

right.

1.3.1.1.CATVIt contains the data of the CATV company. (Only modifiable.)

DESCRIPTION: the name of the company

CITY, ADDRESS: the address of the company

1.3.1.2.HeadendIt lists the headends of the CATV company. (Only modifiable.)

DESCRIPTION: the description of the headend

CITY, ADDRESS: the address of the headend

CONTACT PERSON, TELEPHONE, FAX: how the headend can be contacted

1.3.1.3.CMTSIt lists the CMTSes located at the headends. (Only modifiable.)

The settings must comply with the values of the CMTS. Otherwise, some of the functions

of the system may not work.

CMTS basic data

TYPE: the type of the CMTS. (Cannot be modified.)

DOCSIS: the DOCSIS version of the CMTS (Value read from the CMTS.)

IP ADDRESS : IP address of the CMTS

SNMP READ / WRITE COMMUNITY: IDs necessary for accessing the CMTS using SNMP


Network Cable modem Client Statistics Operation OtherStructure Search Search Network Letter templatesIP address Online Client Traffic reports PermissionsNetwork group All Terminal node Cable modem User settingsCoS 1.0 Save Save Client System parametersCoS 1.1 Individual Client Terminal nodePackage Grouped Terminal nodeCATV Settings Lists

City Manufacturer DemandsStreet Type To be connectedUpstream Software version Connection in progress

Supplier ConnectedStock Restricted terminal nodes


TELNET ID / PASSWORD / PRIVILEGE PASSWORD: ID and password necessary for accessing the

CMTS using telnet

RSH ID: IDs necessary for accessing the CMTS using RSH

Ethernet interfaces

DESCRIPTION: the name of the Ethernet interface in the CMTS

SNMP NAME: the SNMP name of the Ethernet interface in the CMTS

1.3.1.4.Physical interfaceIt contains the physical interface of the CMTS. (Only modifiable.)

Downstream

It contains all the downstream channels of the CMTS. (Only modifiable.)

DESCRIPTION: the description of the channel

EURO-DOCSIS: the supported DOCSIS standard

TELNET NAME: the name of the channel using telnet

SNMP NAME: SNMP name of the channel

FREQUENCY: the frequency of the channel. Value must be between 91000000 Hz and

857000000 Hz.

MODULATION: the modulation of the channel. Possible values: 64QAM, or 256QAM.

POWER: the power of the signal transmitted on the channel. Value must be between 105

dBμV and 123.

In case of FREQUENCY, MODULATION and POWER, the system also reads the values from the

CMTS. If the two values are not equal, you can validate the modifications on the CMTS

by pressing the SAVE button.

Upstream

It contains all the upstream channels of the CMTS. (Only modifiable.)

DESCRIPTION:the description of the channel

TELNET NAME: the name of the channel using telnet

SNMP NAME: the name of the channel using SNMP

FREQUENCY: the frequency of the channel. Value must be between 6000000 Hz and

65000000 Hz on EuroDOCSIS system, and between 6000000 Hz and 41000000 Hz on

non-EuroDOCSIS system.

MODULATION: the modulation of the channel. Possible values: QPSK, or 16QAM.



BANDWIDTH: the bandwidth of the channel. Possible values: 0,2MHZ, 0,4MHZ, 0,8MHZ,

1,6MHZ, or 3,2MHZ.

POWER: the power of the signal transmitted on the channel. Value must be between 53

dBμV and 83 dBμV.

In case of FREQUENCY, MODULATION, BANDWIDTH and POWER, the system also reads the values

from the CMTS. If the two values are not equal, you can validate the modifications on the

CMTS by pressing the SAVE button.

1.3.1.5.Logical interfaceIt contains the CATV network interfaces of the CMTS. (Only modifiable.)

DESCRIPTION: the description of the channel

SNMP NAME: the name of the channel using SNMP

Server: the InCa server

DHCP MANDATORY: the online cable modems cannot communicate unless the CMTS (and

indirectly the InCa server) has assigned an IP address to them. (CMTS specific switch)

New IP network can be added by the NEW button next to the Logical interface.

1.3.1.6.IP networkYou can define the address ranges which the InCa can assign.

You must specify at the IP network settings:

1. If the address range is for the cable modems (CM) or for the customer premises

equipment (CPE)

2. which network group can use the address range

3. if the addresses of the range are public or private

4. what settings are to be used by the devices using the range

New IP network can be added by the NEW button next to the Logical interface.

DESCRIPTION: the name of the range

TYPE: what kind of devices the range is reserved for, Possible values: CM, CPE.

NETWORK GROUP: which network groups the packages using the range are assigned to

ADDRESS RANGE: definition of the range

GATEWAY: what address the devices of the range can use to access the other parts of the

network.

DNS, DNS 2: the primary and secondary DNS server to be used by the devices

SNMP TRAP SERVER: The cable modems send their SNMP trap massages to this server

NAT: whether the address must be translated or not in case of packets arriving from the



devices of the range. Possible values: PUB – translation is not needed, NAT – must be

translated.

New IP pool can be added by the NEW button next to the IP network.

1.3.1.7.IP poolThe IP networks can be divided into pools. In case of all pools you must specify the first

and last IP address of the pool, the way of assignment and the weight of the pool.

When you specify the pool, the first and last IP address need not be the same as the

boundary of the range.

The weight of the pool is used when the dynamic IP addresses are defined. If the device

can get an IP address from several ranges, the system decides depending on the weight.

New IP pool can be added by the NEW button next to the IP network.

DESCRIPTION: the name of the range

FIRST / LAST IP ADDRESS: the first and last IP address of the pool

ALLOCATION: the assignment method. Possible values: DYNAMIC – the address is defined

automatically by the InCa, FIXED – the address must be fixed at the terminal node settings.

1.3.2.IP addressIt lists the important addresses used by the system, for example the IP addresses of the

servers.

DESCRIPTION: the description of the IP address

IP ADDRESS: the IP address itself

REMARK: short remark to the IP address

If you change the IP address, it will be replaced everywhere where it is used.

1.3.3.Network groupYou can maintain the network groups in this menu item.

The list includes the number of cable modem and CPE IP networks assigned to the

network group.

DESCRIPTION: the name of the network group

REMARK: You can add a short remark to the network group.

1.3.4.CoS 1.0Here, you can specify the CoS profiles compliant with the DOCSIS 1.0 standard.

MAX DS RATE: maximum downstream rate (b/s).



MAX US RATE: maximum upstream rate (b/s).

GUARANTEED US CHANNEL DATA RATE: guaranteed upstream rate (b/s).

US CHANNEL PRIORITY: packet priority in the upstream. (Larger number = higher priority)

MAX US CHANNEL TRANSMIT BURST: the size of maximum burst (fast transferable data) in the

upstream (byte).

COS PRIVACY ENABLE: enable baseline privacy

1.3.5.CoS 1.1Here, you can specify the CoS profiles compliant with the DOCSIS 1.1 standard.

In the 1.1 standard, the communication between the CM and the CMTS is determined by

one-way data transfer channels (flows) and filters.

At least one one-way channel must be defined for both directions (US/DS). There must be

one default flow for both directions. The packets whuch do not fit any classifier will travel

on this flow.

You can set filters on the channels which say which packets can travel in the given

channel. The InCa system only supports the filters by IP packets.

DESCRIPTION: the name of the profile

US FLOW: US data transmission channels

DS FLOW: DS data transmission channels

1.3.5.1.US FlowDESCRIPTION: the name of the data transmission channel

DEFAULT US FLOW: the default US flow. The packets does not fit any US classifier will travel

on this flow.

TRAFFIC PRIORITY: packet priority on the upstream. (Larger number = higher priority)

MAX SUSTAINED TRAFFIC RATE: maximum transmission rate (b/s). The maximum number of

transmitted bytes in time T: T * (MAX SUSTAINED TRAFFIC RATE/8) + MAX TRAFFIC BURST.

MAX TRAFFIC BURST: the size of the burst (byte)

MIN RESERVED TRAFFIC RATE: Minimum reserved transmission rate (b/s)

ASSUMED MIN RESERVED RATE PACKET SIZE: It is the minimum size of the packets (byte) that the

CMTS assumes in order to get the minimum reserved bandwidth

MAX CONCATENATED BURST: it gives the maximum size of the concatenated DOCSIS packets

in case of burst traffic

SERVICE FLOW SCHEDULING TYPE: packet transmission scheduling type. Supported schedules:

• BEST EFFORT



• NON-REAL-TIME POLLING SERVICE

• REAL-TIME POLLING SERVICE

• UNSOLICITED GRANT SERVICE WITH ACTIVITY DETECTION

• UNSOLICITED GRANT SERVICE

REQUEST/TRANSMISSION POLICY: bitmask field, it determines the place of data transmission in

the different DOCSIS timegaps

NOMINAL POLLING INTERVAL: it is the interval by which transmission permissions can surely be

sent (microsec).

TOLERATED POLL JITTER: it is the maximum time from the beginning of the above specified

interval in which a transmission permission can be sent over (microsec).

UNSOLICITED GRANT SIZE: packet size using UGS

NOMINAL GRANT INTERVAL: It is sure that, using UGS, data can be transferred by this interval

(microsec).

TOLERATED GRANT INTERVAL: it is the maximum time from the beginning of the above specified

interval in which data can be sent over (microsec).

GRANT/INTERVAL: number of grants in a NOMINAL GRANT INTERVAL

IP TOS OVERWRITE AND/OR MASK: IP ToS overwrite, first binary AND operation with an AND

mask, then binary OR with an Or mask.

1.3.5.2.DS FlowDESCRIPTION: the name of the data transmission channel

DEFAULT DS FLOW: the default DS flow. The packets does not fit any DS classifier will travel

on this flow.

TRAFFIC PRIORITY: packet priority on the downstream. (Larger number = higher priority)

MAX SUSTAINED TRAFFIC RATE: maximum transmission rate (b/s). The maximum number of

transmitted bytes in time T: T * (MAX SUSTAINED TRAFFIC RATE/8) + MAX TRAFFIC BURST.

MAX TRAFFIC BURST: the size of the burst (byte)

MIN RESERVED TRAFFIC RATE: Minimum reserved transmission rate (b/s)

ASSUMED MIN RESERVED RATE PACKET SIZE: It is the minimum size of the packets (byte) that the

CMTS assumes in order to get the minimum reserved bandwidth

MAX DOWNSTREAM LATENCY: maximum interval between the time when a packet arrives at the

CMTS and the time when it is sent down (microsec).

1.3.5.3.IP packet classifierDESCRIPTION: the name of the classifier



RULE PRIORITY: priority of the classifier (Larger number = higher priority)

ACTIVATION STATE: if the classifier should be active after loading or not

IP TOS RANGE LOW / IP TOS RANGE HIGH / IP TOS MASK: IP Type of Service test.

The packet matches if the value masked by the value of the IP TOS MASK falls in the IP

TOS RANGE.

IP PROTOCOL: IP Protocol (RFC-1700) test. Two special values: 256 – all protocols, 257 –

TCP and UDP protocols.

SOURCE ADDRESS: source IP address

SOURCE PORT (START – END): source port range

DESTINATION ADDRESS: destination IP address.

DESTINATION PORT (START – END): destination port range

1.3.6.PackageHere, you can create and modify different access packages.

DESCRIPTION: the name of the package

NETWORK GROUP: the network group assigned to the package. The system assigns the IP

addresses of this network group to the given terminal node.

BASIC COS 1.0/1.1 PROFILE: the modems of the package which comply with the 1.0/1.1

DOCSIS standard use this CoS profile.

LIMIT: If this traffic limit is exceeded, the system automatically switches to the second CoS

profile. If no limit is set, the system will ignore all other CoS profile information.

2. COS 1.0/1.1 PROFILE: this is the CoS profile which is to be activated after reaching the

basic traffic limit.

2. LIMIT: If the next traffic limit is exceeded, the system automatically switches to the third

CoS profile. If no second limit is set, the system will ignore all other CoS profile

information.

3. COS 1.0/1.1 PROFILE: this is the CoS profile which is to be activated after reaching the

second traffic limit.

You can find the terminal nodes using a profile other than basic in the menu Client /

Restricted terminal nodes.

FIXED IP: the number of fixed IP addresses available for the CPEs.

The IP addresses must be recorded on the terminal node maintenance page.

DYNAMIC IP: the number of dynamic IP addresses available for the CPEs.



NAT: If the addresses assigned to the CPE must be translated or not. Switching it on

means translation is needed. If you the want to assign both public and private addresses

in the package, they can only be fixed addresses.

1.3.7.CityMaintaining cities.

The system can access cities only through this directory.

DESCRIPTION: the name of the city

ZIP CODE: the zip code of the city

TIME ZONE OFFSET (SEC): If the city is not in the same time zone as the InCa server, this value

shows the difference between them (in seconds).

1.3.8.StreetStreet maintenance. The system can only handle streets which are recorded in the

system.

CITY:the city where the street is

STREET: the name of the street

1.3.9.UpstreamThe list of upstream capable streets. The system can only handle the streets recorded in

this list.

CITY / STREET: the location of the UC street. It can only be set in case of NEW ENRTY.

BUILDING NUMBER: starting and ending number and side of the upstream capable section

REMARK: You can add a remark to the section.

TERMINAL NODES IN THE UC STREET: the system shows the terminal nodes on the given

upstream capable section. An upstream capable street cannot be deleted if there is a

terminal node with TO BE CONNECTED, CONNECTION IN PROGRESS, CONNECTED, or SUSPENDED status

in it.

1.4.Cable modem menu item

1.4.1.Cable modem dataThe system stores the following data about the cable modems:

MAC ADDRESS: The MAC address of the cable modem

The manufacturers usually indicates several MAC addresses of a cable modem. You

must enter the address of the CATV interface (HFC) into the InCa system.



TYPE: the type of the cable modem

DATE OF MANUFACTURING: the manufacturing date of the cable modem

SERIAL NUMBER: the serial number of the cable modem

SUPPLIER: the supplier of the cable modem

DELIVERY DATE: the date of purchase/delivery

INVOICE NUMBER: the invoice number issued by the supplier.

DATE OF INVOICE: the date of issue of the supplier's invoice

GUARANTEE: the date when the guarantee ends

STOCK: where the modem is stored

CONDITION : the technical condition of the modem

REMARK: remarks of the operator

MONITORING: when it is switched on, the InCa gets technical data from the modem more

frequently, which helps troubleshooting. “More frequently” is every minute by default.

1.4.2.OnlineThe list of online modems connected to the system. This menu item is used for testing the

status and the operating parameters of the system.

1.4.2.1.Search conditionsHere you can set the filtering parameters.

CMTS: you can select CMTS in case of more than one CMTS.

UPSTREAM: you can select certain upstreams, otherwise the list will contain all the

upstreams.

IP ADDRESS: search cable modems by IP address

MAC ADDRESS : search cable modems by MAC address

STATUS: search cable modems by status

MEASUREMENT DATA: data should come from the CMTS only or from the CMTS and the cable

modem.

ERROR FILTERING: you can get a list of cable modems with measurement data out of

tolerance limit

CLIENT ID: search cable modems by client id

TERMINAL NODE ID: search cable modems by terminal node id

CONTACT OF TERMINAL NODE: search cable modems by the contact person of the terminal node

PACKAGE: search cable modems by package

CITY: It lists the modems located at terminal nodes in the given city.



STREET: It lists the modems located at terminal nodes in the given street.

BUILDING NUMBER (FROM-TO): search cable modems by the building number of the terminal

node

1.4.2.2.The result listSID: the internal identifier of the cable modem on the CMTS. Clicking the SID you get to

the cable modem information page.

CHART: Combined / devided technical charts / avaiablilty

DS/US: downstream and upstream channel IDs

IP ADDRESSES: the IP addresses of the cable modems. Clicking the IP address you get to

the cable modem maintenance page.

MAC address: the MAC addresses of the cable modems. Clicking the MAC address you

get to the cable modem maintenance page.

STATUS: status of the cable modem. Clicking the status you get a chart which shows when

the modem was online.

CMTS RX / US SNR: measurement data read from the CMTS. Clicking the values, you

can see the diagrams of the logged measurement data.

CLIENT: the name of the client using the cable modem. Clicking the name, you get to the

client maintenance page.

TERMINAL NODE: the physical location of the cable modem. Clicking the address of the

terminal node, you get to the terminal node maintenance page.

PACKAGE: the actual package of the terminal node. Clicking the package you get to the

package maintenance page.

CM US RX / CM DS RX / CM DS MER: measurement data read from the cable modem.

Clicking the values, you can see the diagram of the logged measurement data. (It can only

be seen if you set the MEASUREMENT DATA to CMTS AND CABLE MODEMS on the SEARCH CONDITIONS

page.

CM RESET: you can initiate the reset of the cable modem

Colors of result list:

Color Meaningnormal functioning

bad value



acceptable value

offline modem

connected, but not registered modem

About the limits of technical data:

CMTS Rx

USSNR

CM US Tx





CM DS Rx

CM DS MER

1.4.2.3.Cable modem information pageOn this page, you can see data read directly from the cable modem. See the DOCSIS

standard for more details on the data. The links EVENTTABLE and FILTERTABLE lead to the

corresponding tables of the cable modem.

1.4.3.AllAfter setting the search conditions you get a list of modems of the given parameters. If you

click a row of the list, it leads you to the cable modem maintenance page.

Here you can modify the data of the cable modem and see its last operating parameters.

1.4.4.Save / IndividualThis is a page for saving the basic data of the cable modems.



1.4.5.Save / GroupedThis feature allows you to enter new cable modems fast if they were received from the

same supplier and belong to one series.

After setting the basic data, you must enter MAC ADDRESS; SERIAL NUMBER pairs in the last

field. The two values must be separated by a semicolon (;). One row is for one cable

modem.

1.4.6.ManufacturerYou can save the cable modem manufacturers.

DESCRIPTION: the name of the manufacturer

WWW: the web page of the factory

DOWNLOAD: the support page of the factory

REMARK: remark to the manufacturer

1.4.7.TypeCable modem type maintenance page.

DESCRIPTION: the name of the cable modem type

MANUFACTURER: the manufacturer of the cable modem

SOFTWARE VERSION (1.0): software compliant with the DOCSIS 1.0 standard

SOFTWARE VERSION (TRANSITIONAL): This software complies with the DOCSIS 1.1/2.0 standard

and can be installed on a modem using DOCSIS 1.0 code.

SOFTWARE VERSION (1.1/2.0): software compliant with the DOCSIS 1.1/2.0 standard

MCVC: manufacturer code verification certificate.

REMARK: remark to the cable modem types

1.4.8.Software versionsYou can store the different cable modem software versions on this page.

VERSION: the name of the software

TYPE: cable modem types which can be updated with the software

SOFTWARE: access path of the file to be uploaded

DOCSIS: the supported DOCSIS version

INSTRUCTIONS IN THE CONFIGURATION FILE: special instructions to be followed when the software

version is copied onto the cable modem.

REMARK: remark to the software version



1.4.9.SupplierList of cable modem suppliers.

DESCRIPTION: the description of the supplier

CONTACT: name of the contact person

TELEPHONE / E-MAIL: of the contact person

REMARK: remark to the supplier

1.4.10.StockIt is a page to maintain the stores used in the system.

DESCRIPTION: description of the store

1.5.Client menu item

1.5.1.Client dataClient data stored in the system:

NAME: the name of the client

ID: the id of the client. It is needed for getting traffic information.

EXTERNAL ID: the external id of the client for connecting to external software (e.g.: billing

software)

Password: the client's password for getting traffic information

CITY / ADDRESS: city and address of the client

CONTACT: name of the contact person.

TELEPHONE / E-MAIL: of the contact person. Letters regarding the terminal node (e.g.: traffic

limitation) are sent to this e-mail address.

REMARK: remark to the client

1.5.2.Terminal node dataTerminal node data stored in the system:

ID: the ID of the terminal node.

CLIENT: the financer of the terminal node

CONTACT: name of the contact person

TELEPHONE / E-MAIL: of the contact person

CITY / STREET / BUILDING NUMBER/ BUILDING NUMBER #2: location of terminal node

REMARK: remark to the terminal node.

LIMITABLE: whether it can be limited as specified in the package. In case it is switched off,

the modem at the terminal node always works by a basic CoS profile.



STATUS: status history of the terminal node

PACKAGE: package history of the terminal node

MODEM: history of modems assigned to the terminal node

VOIP TELEPHONE NUMBERS: preparation for VOIP phone calls (available from version 1.3)

1.5.3.SearchIn this menu item you can search clients and terminal nodes, and their data can be

modified.

1.5.4.SaveYou can add new clients and terminal nodes here.

1.5.5.Terminal node settings

1.5.5.1.StatusThe previous statuses can be seen in the STATUS table.

STATUS: the name of the status. If you want to modify the status you will only see those

statuses which the present one can be changed to.

DATE: date of status change. It can be preset.

MODIFICATION: time of status modification

MODIFIER: the user initiating the modification. If the system changes the status

automatically, the name of the modifier will be InCa.

By a special authorization any statuses can be set by-passing the order of statuses given

by the system.

1.5.5.2.PackageWhen you set the packages, you can see the package history.

PACKAGE: name of the chosen package. If the package allows the assignment of fixed IP

addresses, the possible IP pools appear under the title package. The necessary fixed IP

addresses can be entered in the IP column using the IP pool. If it is important which CPE

gets the fixed IP address, it is possible to define the MAC address of the CPE. If no MAC

address is given, it is not sure that the CPE will get a fixed IP address.

FURTHER DYNAMIC IP ADDRESSES: the number of dynamic IP addresses specified in the

package can be extended by further dynamic IP addresses per terminal node.

DATE: date of package modification

MODIFICATION: time of package modification

MODIFIER: the user initiating the package modification.



1.5.5.3.ModemThe modem must be assigned to its terminal node. By default, the Inca allows only one

cable modem per terminal node. If troubleshooting, testing or other reasons make it

necessary, it is possible to assign more than one cable modems to a terminal node.

In case you assign more than one modems to a terminal node, some of the tasks (traffic

restriction, restart due to the modification of the package, status or CoS profile) will be

performed only on the modem which was assigned last. If you want to install several

modems to a client, you must create as many terminal nodes as the required number of

modems.

MODEM: the MAC address of the assigned modem. Clicking the MAC address you get to

the modem maintenance page.

FROM / TO: the period of assignment

CHARTS: it shows the technical data of the modem even if it is not online

MODIFICATION: the date and time of assignment

MODIFIER: the user initiating the assignment

1.5.6.ListsHere, you find search results of preset parameters.

1.6.Statistics

1.6.1.NetworkPACKAGE LIST: list of current packages

IP-NETWORKS, IP POOLS AND THEIR CAPACITY: It presents the IP network elements as on the

Network/Structure page illustrating the number of free and assigned IP addresses in the

ranges and the pools.

FIXED IP ADDRESSES ASSIGNED: The assigned fixed IP addresses with filtering facility by IP

address, IP network, IP pool, and clients.

UPSTREAM CAPACITY: the used capacity of upstream capable network with filtering facility by

city and street. It can be done for any dates.

DHCP QUERIES: After filling in the IP and MAC addresses you have the following search

options:

• Search modem MAC by modem IP

• Search modem IP by modem MAC

• Search CPE IPs behind the modem by modem MAC



• Search CPE MACs behind the modem by modem MAC

• Search CPE IPs behind the modem by CPE MAC

• Search CPE MAC behind the modem by CPE IP

• Search CPE IP-MAC pairs behind the modem by modem IP

• Search CPE IP-MAC pairs behind the modem by modem MAC

1.6.2.Consumption summaryIt calculates the total consumption in the given time period of all clients. You can export

the result to a CSV (Comma-Separated Values) file.

1.6.3.Cable modemDISTRIBUTION BY TYPE: cable modem distribution by type, total number and number at terminal

node.

DISTRIBUTION BY MODEM CONDITION: distribution by the technical condition of the cable modems

1.6.4.ClientCLIENT LIST: You can have client lists filtered by different conditions.

CONTACT LIST (DIRECTORY): You can have client and terminal node contact lists filtered by

different conditions.

DISTRIBUTION OF CLIENTS: It counts the total number of clients and the number of clients with a

connected terminal node in a given time period on each day/week/month/year in form of a

table or a graph.

CONSUMPTION OF CLIENTS: It counts the daily/weekly/monthly/yearly total consumption and the

consumption per terminal nodes in a given time period in form of a table or a graph.

(Client filtering is also possible)

1.6.5.Terminal nodeLIST OF TERMINAL NODES: It gives a similar list to Client/Search/Terminal node which fits the

given search conditions.

TERMINAL NODE CONSUMPTION (DAILY): It calculates the daily consumption in the given time

period filtered by terminal nodes in form of a table or a graph.

TERMINAL NODE CONSUMPTION (PER MINUTES): It calculates the consumption on the given day per

minutes filtered by terminal nodes in form of a table or a graph.

1.7.OperationIt is a collection of the most frequently used search results.



1.8.Other

1.8.1.Letter templatesIt is a module for customising the letters sent by the InCa. Different macros (e.g.: client's

name) can be put into the text of the letters, which will be replaced by the value stored in

the database when the letter is posted.

1.8.2.PermissionsThis module is for maintaining the InCa users and their permissions.

1.8.2.1.UsersWhen the system is installed two users are created as a default:

ADMIN: A user with administrator rights. He has authorization for all the operations.

INCA: System user. You cannot log in the interface with it. It is the user who performs the

automatic operations of the system.

1.8.2.2.User dataNAME: user's name

ID: the name used for logging in the system

PASSWORD: the password for logging in the system, it must consist of at least six characters

PERMISSION: which module can be accessed by the the user and at what level. The system

uses the following permission levels:

• READ: data can be viewed

• MODIFY: data can be modified

• ADD: new data can be entered

• DELETE: data can be deleted

If the user tries to do an operation to which he has no right, he gets a massage saying:

'You are not authorised to perform the operation.')

The permissions are valid as soon as the modification is saved, it does not matter if the

actual users are logged in or not. .

1.8.3.User settingsThe user must type his/her current password before any modification.

OLD PASSWORD: the current password

NEW PASSWORD / VERIFY NEW PASSWORD: the new password twice



1.8.4.System parametersNUMBER OF LIST ITEMS: You can set the number of rows appearing in the list pages. If you set

this parameter to zero, all the rows will appear.

SNMP CONNECTION TIMEOUT FOR CMTS (SEC): waiting time (in seconds) for the SNMP

connection when connecting to CMTS

SNMP CONNECTION TIMEOUT FOR MODEM (SEC): waiting time (in seconds) for the SNMP

connection when connecting to modems

SNMP RESPONSE TIMEOUT FOR CMTS (SEC): waiting time (in seconds) for the SNMP answer

when getting data from CMTS

SNMP RESPONSE TIMEOUT FOR MODEM (SEC): waiting time (in seconds) for the SNMP answer

when getting data from modems

1.9.Log outThe logged user can log out.

The system gets to the initial status.

2.Application serverIn case of the installation of the basic system, the network management application server

waits for the commands on the InCa server (127.0.0.1) at the 8088 port, the administration

server waits at the 8089 port.

In case of a basic setup, in order to ensure a safe operation, the application servers can

be accessed only from inside the InCa server.

Initiate a telnet connection with the server first. When the connection is established you

can type the required commands.

Server commands:

• STOP – stop the server

• HALT – stop the server immediately

• RELOAD – reload the settings and continue working

• STATUS – show status

• GENERATE – make new config file for the DHCP server and use this

• OVERWRITE – overwrite CMTS config file

• RESET – forcing modem restart on the CMTS

• GET-MAC IP – show the MAC address of the modem by the IP address of the

modem



• GET-IP MAC – show the IP address of the modem by the MAC address of the

modem

• GET-CLIENT-IPS MAC – show the IP addresses behind the modem by the

MAC address of the modem

• GET-CLIENT-MACS MAC – show the MAC addresses behind the modem by

the MAC address of the modem

• GET-CLIENT-IP MAC - show the IP address behind the CPE by the MAC

address of the CPE

• GET-CLIENT-MAC IP - show the MAC address behind the CPE by the IP

address of the CPE

• GET-CLIENT-DATAS-IP IP - show the CPE IP-MAC address pairs behind the

modems by the IP address of the modem

• GET-CLIENT-DATA-MAC MAC - show the CPE IP-MAC address pairs behind

the modems by the MAC address of the modem

• HELP – help on the server commands

• LIST – list of subservers

Some services of the application server can be controlled in the form of COMMAND

SERVICE.

Services:

On the netserver

• TIME – TIME server

• TFTP – TFTP server

• DHCPC – generating DHCP configuration file

• CONFIG – generating cable modem configuration files

• CMTS_CONFIG – configuration of the headed

• INCA_INFO_PROVIDER – provides information to the web interface

On the adminserver

• LOG_BSR1000 – logging the Motorolla BSR 1000 based system

• LOG_AGGR – Summing of logged data

• COS – limiting the traffic

• MODEMINFO_COLLECTOR – collecting secondary information about modems

• TRANSACTION_LOG – logging the operations done on the InCa and sends a

letter about these transactions. In admin config.xml you can change destination



email address from the default inca@localhost to an other.

• TODO – handling background and future jobs

Service commands:

• START – start the service

• STOP – cease the service

• RESTART – restart the service

• RELOAD – Reload the settings and continue working

• STATUS – show status

The commands are not letter sensitive, so either small or capital letters can be used.

Form of IP addresses : xxx.yyy.zzz

Form of MAC address: aabbccddeeff

If a command is successfully done, you get a OK massage, if not, you get FAIL –

ERRORCODE: xxx.



IV.Starting to use the system

When the installation of the system is completed the database is nearly empty, it only

contains the basic parameters of the system (e.g.: hardware devices). In order to get the

system work, you need to record the necessary data on the InCa interface. The present

chapter helps you to do the first steps.

1.Network configurationYou can do the necessary configuration in the Network menu.

1.1.Defining the IP addressesYou can define the IP addresses to be used by the system in the Network / IP address

menu. It is essential to set the following IP addresses:

• IP address of the CMTS

• IP address of the primary DNS server

• IP address of the secondary DNS server

• IP address of the SNMP trap server

1.2.Defining the network groupsThe system requires at least one network group to be created. You can do so in the menu

Network / Network group.

1.3.Defining the serverThe modems can connect only if the server is specified on the logical interface (Network /

Structure / Logical if.), that is to say, it is set which InCa server will serve the given network

segment. You can do so after the servers have been started.

1.4.Defining IP networks and pools Set the address range in the Network / Structure / IP network menu. The system requires

at least one IP network for the modems and one for the devices of the client (CPE) and

one IP pool within them. It is advisable to choose private addresses (NAT) for the

modems, as it is not necessary to assign public addresses for them. When you define the

CPE networks, keep in mind what packages you want to create. If the package requires,

you need to have both public and private, and within them, both fixed and dynamic ranges

too.

IV.Starting to use the system 35


After the ranges are defined, you must provide for the translation of the required IP

addresses on a server connected to the CMTS as the InCa does not translate the

addresses.

1.5.Defining the service areasDefine the areas where you want to connect terminal nodes in the menu Network / City,

Network / Street and Network / Upstream. The terminal nodes can only be recorded if this

data is available.

2.PackageDefine the quality and other parameters of your service.

2.1.Adding CoS 1.0 profilesDefine profiles compliant with the DOCSIS 1.0 standard in the Network / CoS 1.0 menu.

At least one such profile is required.

2.2.Adding CoS 1.1 profilesDefine profiles compliant with the DOCSIS 1.1 standard in the Network / CoS 1.1 menu.

At least one such profile is required. You must create at least one DS flow and one US

flow within the CoS 1.1 profile.

2.3.Creating packagesDefine packages for your service. At least one package is required by the system. Pay

attention when you define the number of the IP addresses and the way they are assigned,

that it should comply with the IP networks and IP pools in the chosen network group. (e.g.:

You cannot assign only fixed IP addresses in the package while all the ranges in the

network group contain dynamic IP pools. )

3.Modem dataYou need to enter the data of the modems before you assign them to terminal nodes.

3.1.Cable modem manufacturesEnter the manufacturers of the applied modems in the menu Cable modem / Manufacturer

(e.g.: Motorola, 3com, etc.).



3.2.Cable modem typesEnter the types of the applied modems in the menu Cable modem / Type (e.g.: SB5100E,

etc.).

3.3.SuppliersEnter the companies who supply the modems in the menu Cable modem / Suppliers. It is

only an optional field, but it can be useful later on. (e.g.: guarantees)

3.4.ModemsEnter the modems which you want to assign to the terminal nodes in the Cable modem /

Save / Individual or Grouped menu.

4.Client, terminal node

The last step is to enter the data of the clients and their terminal nodes.

4.1.Adding new clients

Enter the data of your clients in the Client / Save / Client menu. It is enough to enter the

clients with several terminal nodes once. Here, you enter the financers, practically.

4.2.Adding new terminal nodes

Add new terminal nodes in the Client / Save / Terminal node menu.

– Enter the data of the terminal nodes

– Set the status of the terminal node to 'Connected'

– Assign a package to the terminal node. If the package contains only fixed IP

addresses, assign IP addresses from the fixed address ranges available in the

package.

– Give a modem from the stock to the terminal node.

If you have completed these steps, you can practically hand out the modem, which is

ready to connect to the system and serve the client.



V.Examples

The present chapter teaches you how to create service packages step by step starting

from the creation of IP ranges and CoS profiles to the definition of the packages.

1.Example 1Suppose you want to create the following packages:

Name ofpackage

Bandwidth (kbps) Number of fixed IPaddresses

Number of dynamicIP addresses

Bronze 256 / 64 0 1 privateSilver 512 / 128 1 private 1 privateGold 1024 / 128 1 private 3 privateBusiness 1024 / 256 1 public + 5 private 0

1.1.Add a new Network group Network / Structure / Network group - Add new: Demo network group

1.2.Add a new IP network and an IP pool within it for the modems: Adding a new IP network: Network / Structure / Logical if. / New

• Description: Modem network

• Type: Modem

• Network group: Demo network

• Address range: 10.1.0.0/24

• DNS: select an IP address from the preset primary DNS IP addresses

• DNS 2: select an IP address from the preset secondary DNS IP addresses

(optional)

• SNMP Trap server: select the IP address of the CMTS

• NAT: NAT

Adding a new IP Pool: Network / Structure / Logical if. / IP network (Modem network) / New

• Description: Modem pool

• First IP address: 10.1.0.1

• Last IP address: 10.1.0.253 (10.1.0.254 is reserved for the gateway)

V.Examples 38


• Provide for routing the range towards the CMTS

• Provide for address translation of the range (NAT)

1.3.Add a new private IP network and two IP pools within it for theclients' devices:Adding a new IP network: Network / Structure / Logical if. / New

• Description: CPE Private Network

• Type: CPE


• Address range: 10.0.0.0/24



(optional)


• NAT: NAT

Adding a new IP Pool containing fixed IP addresses: Network / Structure / Logical if. / IP

network (CPE Private Network) / New

• Description: CPE fixed private pool


• Last IP address: 10.0.0.127



Adding a new IP Pool containing dynamic IP addresses: Network / Structure / Logical if. /

IP network (CPE Private Network) / New

• Description: CPE dynamic private pool


• Last IP address: 10.0.0.253 (10.0.0.254 is reserved for the gateway)



1.4.Add a new public IP network and an IP pool within it for the clients'devices:Adding a new IP network: Network / Structure / Logical if. / New

• Description: CPE Public network

• Type: CPE

V.Examples 39



• Address range: 217.65.98.136/29



(optional)


• NAT: PUB

Adding a new IP Pool containing fixed IP addresses: Network / Structure / Logical if. / IP

network (CPE Public Network) / New

• Description: CPE fix private pool

• First IP address: 217.65..98.137

• Last IP address: 217.65..98.141


1.5.Create suitable CoS 1.0 profiles for your servicesAdd new CoS 1.0 profile for Bronze package: Network / CoS 1.0 / Add new

• Description: 256 / 64

• Max DS Rate: 256000

• Max US Rate: 64000

• Guaranteed US Channel Data Rate: 0

• US Channel Priority: 0

• Max US Channel Transmit Burst: 1578

Add new CoS 1.0 profile for Silver package: Network / CoS 1.0 / Add new







Add new CoS 1.0 profile for Gold package: Network / CoS 1.0 / Add new





V.Examples 40




Add new CoS 1.0 profile for Business package: Network / CoS 1.0 / Add new







1.6.Create suitable CoS 1.1 profiles for your servicesAdd new CoS 1.1 profile for Bronze package: Network / CoS 1.1 / Add new


• DS flow / Add new

• Default DS flow: yes

• Description: 256 / 64 DS Default

• Traffic Priority: 1

• Max Sustained Traffic Rate: 256000

• Max Traffic Burst: 1578

• US flow / Add new

• Default US flow: yes

• Description: 256 / 64 US Default




Add new CoS 1.1 profile for Silver package: Network / CoS 1.1 / Add new









V.Examples 41







Add new CoS 1.1 profile for Gold package: Network / CoS 1.1 / Add new














Add new CoS 1.1 profile for Business package: Network / CoS 1.1 / Add new














V.Examples 42


1.7.Define suitable packages for your services Defining Bronze package: Network / Package / Add new

• Description: Bronze

• Network group: Demo network group

• Basic CoS profile (1.0): 256 / 64


• Fixed IP (pcs.): 0

• Dynamic IP (pcs.): 1

• NAT: NAT

Defining Silver package: Network / Package / Add new

• Description: Silver






• NAT: NAT

Defining Gold package: Network / Package / Add new

• Description: Gold






• NAT: NAT

Defining Business package: Network / Package / Add new

• Description: Business






• NAT: Both

V.Examples 43


2.Example 2

Suppose you want to define a package, in which data is transferred at a speed of 512 /

128 k/s through HTTP protocol (it allows a greater bandwidth for browsing), while the rest

of the traffic goes at a speed of 128 / 64 k/s. In this case you can only use DOCSIS 1.1

profile.

You are supposed to perform the steps described in Example 1, only the definition of CoS

1.1 profile differs.

2.1.Defining a CoS 1.1 profile

Defining Default flows

• Description: 128 / 64 (extended FTP)



• Description: 128 / 64 (extended FTP) DS Default






• Description: 128 / 64 (extended FTP) US Default




Defining flows for FTP traffic


• Default DS flow: no

• Description: 128 / 64 (extended FTP) DS FTP




V.Examples 44


• IP Packet classifier / Add new

• Description: DS FTP classifier

• Rule priority: 0

• Activation state: yes

• Destination port: 80


• Default US flow: no

• Description: 128 / 64 (extended FTP) US FTP




• IP Packet classifier / Add new

• Description: DS FTP classifier

• Rule priority: 0

• Activation state: yes

• Destination port: 80

Remark: It is the default HTTP port, so not every HTTP protocol request will get greater

bandwidth only the traffic from port 80. If the user uses a url like

http://www.proba.com:8888/, it will not get greater bandwidth as it does not fit the

classifier.

V.Examples 45


VI.Support for performing daily tasks

1.Receiving cable modemsThe cable modems must be made known for the system by recording their data in the

CABLE MODEM/ SAVE menu item.

If the cable modems are of the same series (same type, date of manufacturing, supplier)

you can use the CABLE MODEM/ SAVE – GROUP menu item. If the purchased modem is of a

new type, the type must be entered in CABLE MODEM/ TYPE menu item.

2.Entering new subscriptionFirst of all, you should check in the NETWORK / UPSTREAM menu if the street is upstream

capable or not. If not, the demand can only be entered with WAITING DEMAND status.

If the financer of the new subscription has not been recorded in the system yet, go to

CLIENT / SAVE / CLIENT menu and enter the data.

If the financer is the same as the client at the terminal node, you do not need to enter his

data here. When you record the terminal node, tick the CREATE CLIENT checkbox and the

financer will be automatically created with the data entered at the terminal node.

Next, enter the data of the terminal node in CLIENT / SAVE / TERMINAL NODE, and set the

required package and parameters, finally assign the selected modem to the terminal node.

The status of the terminal node will be DEMAND automatically.

After that the person in charge (it may as well be the administrator) judges the demand

and sets the appropriate status.

If the terminal node is READY FOR CONNECTION , the system sill automatically change the

status to TO BE CONNECTED.

The technical staff will connect the demands in TO BE CONNECTED status and indicate the

fact by changing the status to Connected.

3.Suspending the serviceIf the service is to be suspended at a terminal node, find the terminal node in the CLIENT /

SEARCH / TERMINAL NODE menu and change its status to Suspended. As a result, the modem

at the terminal node will not be able to log in the system.

If it is a client who is to be suspended, find him in the CLIENT / SEARCH / CLIENT menu, then

suspend all his working terminal nodes in his data sheet.

VI.Support for performing daily tasks 46


4.Withdrawing service suspension The process is similar to that above, but the status should be changed to CONNECTED

status.

5.Replacing cable modems at clientsFind the terminal node in the CLIENT / SEARCH / TERMINAL NODE menu, withdraw the old

modem and assign the new one.

6.Checking the operation of the system

6.1.Checking the application serverThe operation of the application server can be checked though the port 8088 of the InCa

server.

Logging into the InCa netserver: TELNET 127.0.0.1 8088

Logging into the InCa adminserver: TELNET 127.0.0.1 8089

After receiving the prompt: STATUS[enter], or STATUS SERVICE[enter].

Massages:

'Unable to connect to remote host: Connection refused' - the application server is not

running.

In case of proper operation the server sends a BUSY/OK massage.

The application server continuously logs its operation in the log directory.

6.2.Checking the networkThe operation parameters can be checked using the CABLE MODEM / ONLINE list. If you set the

ERROR FILTERING: OUT OF TOLERANCE LIMIT button, the list will contain only the terminal nodes

where any of the measured values is out of the acceptable range.

VI.Support for performing daily tasks 47

InCa help

Documents

customer premises

performing

save individual

channel transmit

replacing

ip network

save grouped

technical