Filter
Top Products
Defining a G.SHDSL Management Channel 168
Models 2616RC, 3096RC & 3196RC Admin Reference Guide 11 • In-band management
Note
It is very important that these addresses do not exist on the Ethernet
side. If they do, both the 3096RC and the existing device will attempt
to reply to ARP requests.
Configure the Model 3096RC for a G.SHDSL in-band management channel
The factory default for the G.SHDSL in-band management channel is shown in the following figure.
In configuring the management channel, you will configure the Name, protocol type, G.SHDSL port, and the
IP address and mask.
To configure these parameters, click on Modify Management Channels…. The Name, Protocol Type, Port, IP
Address, and IP Mask parameters are configurable as follows:
Name—click on the G.SHDSL hyperlink in the Interface Type column to go directly to the G.SHDSL web
page. On the G.SHDSL port to be used for management, enter the desired Name into the Circuit ID field.
Save by clicking on the Submit button.
Protocol Type—Select ppp-ipcp(1) for a routed PPP link or ppp-bcp(2) for a bridged PPP link.
Port—Select the G.SHDSL port which was previously named as the management port. After saving this con-
figuration, you will see the Circuit ID name appear in the Name field of the G.SHDSL in-band management
link.
IP Address—The IP address depends if the application management link is routed (IPCP) or bridged (BCP).
• For a routed PPP link using IPCP, the IP address of the WAN IPCP link functions as an unnumbered inter-
face and must be a subnet different from the subnet of the T-DAC. If the T-DAC’s Ethernet IP address/
mask is 192.168.200.10/24, then one possibility for the IPCP link is 10.11.2.30/32. (See the following
Example 2.)
• For a bridged PPP link using BCP, there are two options. The IP address can be in a different subnet than
the T-DAC’s IP subnet. The second option is for the BCP subnet to be a subnet of the T-DAC’s IP subnet.
(See the following Example 1).
IP Mask—As for the IP address, the application management links can be routed IPCP) or bridged (BCP).
• For IPCP, the subnet mask is 255.255.255.255 (/32). (See the following Example 2.)
• For BCP, there are two scenarios. The first BCP scenario is for BCP links having a subnet different than the
T-DAC’s Ethernet IP address/subnet (the mask is dependent on the user’s management management sub-
net). The second BCP scenario is for BCP links using IP addresses within the T-DAC’s Ethernet subnet.
The BCP subnet must be a subnet of the T-DAC’s. If the T-DAC’s mask is /24, then the BCP subnet must