Table of Contents

Chapter 1.

Network Connectivity...........................................................................................2
1.1Purpose and scope of the Document
1.2Introduction

Chapter 2

Access Site Connectivity ...................................................................................3

2.1 Connecting an access site
2.2 MLS Configuration

1
 C-DOT MAX-NG NETWORK
CONNECTIVITY

1.1 PURPOSE AND SCOPE OF THE DOCUMENT

This document provides an overview of C-DOT MAX-NG access site
connectivity to the core network. It also provides information regarding LAN
and WAN IP provisioning and the procedure to configure MLS card.

1.2 INTRODUCTION
During the migration of MAX system to MAXNG the most important point is
the reachability of the access site to the core network. Each access site is
allocated an IP pool of 64, 128 or 256 IPs depending upon the capacity of the
MAX system. This pool of IP is referred as LAN IP pool. Similarly, three WAN
IP pools of 4 IPs in redundant mode are allocated to each site for creation of
interfaces between access site and MPLS network. These interfaces are created
in redundant mode. For getting accessibility between MAX-NG access node
and core network, information pertaining to WAN IPs need to be shared with
the administrator of the MAX exchange at least 15 days before migration so
that the configuration at the BSNL’s MPLS PE router can be done. The
information consists of the IP pool for LAN and WAN interfaces, VLAN
numbers,interface IPs to be configured at BSNL PE router end etc. Three
VLANs, IPTAX, SSTP and CDOT-VOIP are created at both BSNL PE router
and CDOT MLS card. Each VLAN is provided an unique VRF-ID. A unique
LAN IP pool is given to each SDCA which is required for the configuration of
all the access gateways which will be installed at access site in each
BM/RBMs and in CACU chassis. This IP pool is required to be publish at PE
router for all the three VRFs.

2
 ACCESS SITE CONNECTIVITY

2.1 CONNECTING AN ACCESS SITE

Suppose an access site is allocated, LAN IP pool starting from 10.187.35.0 to
10.187.35.255 of 256 IPs denoted as 10.187.35.0/24 and WAN IP pool
10.189.107.40/30, 10.189.107.44/30 and 10.189.107.48/30. For redundant
interfaces the IP pools are 10.189.107.52/30, 10.189.107.56/30 and
10.189.107.60/30 . These WAN IPs are required to create interfaces between
different VLANs. These VLANs are IPTAX , SSTP and CDOT-VOIP VLAN
with unique VRF ID and required to be created at both the end.

2.2 MLS CONFIGURATION

Once configuration at PE router is done, configuration at MAX-NG access
node is required. For configuration at MAX-NG node, CACU chassis need to be
physically installed and power-on. Once the physical installation of CACU is
done insert the MLS card in the corresponding slot at CACU chassis and
connect the minicom cable to the thin client. Allocate an IP to the thin client
from the list of LAN IPs allocated to the given site, run minicom from the thin
client as shown in fig-1 and configure the management IP of MLS as given in
the IP list (fig-3). The management IP of the MLS will act as a gateway IP for
the given pool. As there is a provision of two MLS cards, dual gateways support
is available.

3
fig-1

Fig-2

4
 Fig-3 (IP configuration in MLS)

Once the IP of the MLS is set, it can be accessed through internet browser and
rest of the configuration can be done through GUI interface of the MLS.

Fig-4 MLS card GUI interface

Now create WAN interfaces at MLS card, these interfaces should be as per the
WAN IPs allocated and as per the configuration done at PE router end. For

5
creation of the IP interfaces from the left pane select Configuration IP, a
window will open showing the VLAN 1 configuration (fig-5) which is the
native VLAN for the subnet allocated to that site.

Fig -5 VLAN1 configuration of the MLS

Now as per the example mentioned in the section above , at BSNL MPLS end
interfaces are created at two different PE routers for redundancy. At a cisco
routers interfaces created using WAN IP pools 10.189.107.40/30,
10.189.107.44/30 and 10.189.107.48/30. One interface is for IPTAX VLAN
(VLAN ID=2900) and IP given to this interface is 10.189.107.42 at BSNL end.
Similarly SSTP VLAN and CDOT-VOIP VLANS are created with VLAN ID
2901 and 2902 and IPs 10.189.107.46 and 10.189.107.50 respectively.
For redundant interfaces the IP pools are 10.189.107.52/30, 10.189.107.56/30
and 10.189.107.60/30 used at Huawai router VLAN created are 2700, 2701 and
2702 for IPTAX, SSTP and CDOT-VOIP VLANs and the interface IPs are
10.189.107.54, 10.189.107.58 and 10.189.107.62.
Similar interfaces need to be created at MAX-NG node also. An interface
towards cisco PE router need to be created at MLS1 and towards huawai router
the interface will be created from MLS2. With respect to Huawai router at
MLS2 , VLANs 2700, 2701 and 2702 will be created with the interface IPs
10.189.107.53, 10.189.107.57 and 10.189.107.61 respectively as shown in fig-6.

6
For creating interfaces click on “add interface” and enter the VLAN id, Ip
address and mask length. After the interfaces are added, create IP routes. Create
a default route with network 0.0.0.0 mask length 0, the default gateway for this
default route will be the interface IP of IPTAX VLAN. This indicates that any
network IP other than the specified network will be routed towards IPTAX
VLAN as it may be the address belonging to media IP of IPTAX. Similarly a
network 10.187.0.0/24, is a pool allocated to MAX-NG and will be routed
towards CDOT-VOIP VLAN and the gateway IP will be 10.189.107.60 which
is an IP address forCDOT-VOIP interface created at Huawai PE router, refer
fig-7. Select mode as “router” from the drop down and click to “save” button
once interfaces and routes are added.

Fig-6 Adding interfaces

7
Fig-7 Add IP routes

From the left pane select Spanning tree  Bridge setting and do the STP bridge
configuration as shown in fig-8

Fig-8 STP bridge configuration

8
Now from the left pane click on VLANs Configuration a window will open
showing Global VLAN configuration. Here all the ports of MLS are visible
with their mode and Port VLAN as shown in fig-9

Fig -9 Global VLAN configuration

The mode of the port can be Access or Trunk and can be selected from the drop
down and Port VLAN can be defined according to the configuration. Default
value of Port VLAN is
1.

9
 Fig-10 Allowing Access VLAN

It is also to be noted that against the field “allowed access VLAN” all the
VLANs number to be given see fig-10.
In the face plate of MLS card two optical ports 21 and 22 are available which
are used for uplink connectivity. An SFP of 1310 or 1550 nm wavelength can
be used in these ports depending the SFP type available at BSNL end. An
optical patch cord is used for the connectivity of MLS and PE router. The
“Mode” of the port 21 or 22 which is being used for uplink is to be set as Trunk
port as shown in fig-11.

Fig-11

On selecting the required port as Trunk all the VLANs 1-4095 will be allowed
and Egress port setting wiil be by default set as Untag Port VLAN now save the
setting from the button given below. After all the configuration is done, in the
left pane select Configuration  save startupconfig to save the configuration as
shown in fig-12.

10
 Fig-12 Saving the configuration

After the configuration is done, one should be able to ping the core network
from MLS and behind MLS i.e. from LAGU, thin client etc.

11
 CONFIGURATION REQUIRED
FOR DUAL UPLINK REDUNDANCY

For Dual Uplink connectivity at migration site, following are the requirements:
Both Uplinks must be physically UP and configured.

Configuration Required at PE Router

 BFD ECO configured should be with parameters

bfd min-transmit-interval 200

bfd min-receive-interval 200
bfd min-echo-receive-interval 200
bfd detect-multiplier 3

 Static routing with track configuration for all VPN interfaces.

 Latest Patch must be installed in both LAGU & CACU.

At C-DOT MLS card end,

 RSTP should be configured at both MLS cards with following
parameters and also shown in below screenshot

Hello Time 1
Forward Delay 4
Max Age 6
Maximum Hop Count 6

12
 Transmit Hold Count 2

 Please configure BFD ECO for all VRF/VLAN interface and static
routing with BFD for both Uplink.

 Please configure BFD ECO for all VRF/VLAN interface and static
routing with BFD for both Uplinks.

 Additional setting required for NTP and Trap configuration is as follows:

13
For this , Go to Configuration -> System -> NTP Mode should be Enabled and
enter SBC FVIP of PR Site in Server 1 option and in Server 2 option, enter
SBC FVIP (GR Site) IP address. In below screenshot, Chandigarh Core Site is
taken as PR site and Gurugram is taken as GR site.

PR SITE
NTP SERVER GR SITE
NTP
SERVER

14
Trap Configuration Settings in MLS card

For trap configuration settings, go to Configuration -> System -> Security

-> SNMP -> Trap. Mode should be Enabled. Add Entries of NGEMS
Server of both PR and GR sites. In below screenshot , NGEMS server IP
are 10.187.1.39 and 10.187.1.40 i.e. of Chandigarh Primary Site.
10.187.0.167 and 10.187.0.168 are NGEMS server IP of Gurugram Site
in GR configuration with Chandigarh site. Here , Chandigarh is PR site
and Gurugram is GR site.

15
16
Procedure for Updating MLS CE Service & Uploading of CEServices3_65-MLSSD1_SW002.dat file in
MLS Card

1. Login into MLS through Firefox Web Browser by entering IP address in Thin Client PC.

2. Enter Username admin and Password is not required.

3. Go to Maintenance -> Software -> Upload option

17
4. Then Select Browse option in MLS GUI and select file from Destination in Thin Client where
file is saved/copied.

5. Then select Upload option in GUI and Do not give hard reset/reboot to MLS card when
Uploading and Firm Updation is going ON. Wait for 5 to 10 minutes.

18
 MLS Uplink Removal Alarm Configuration

Background information:

Since the uplink alarm from an MLS card cannot be sent to the NGEMS after the uplink has been
removed, we need to make routes so that one MLS card can send alarms through the other MLS
card whose uplink is intact.

For such a configuration, we add the two physical IP addresses and one floating IP address of the PR
NGEMS servers and one floating IP address of the GR NGEMS server in snmp trap configuration.

To make sure uplink trap is sent from one MLS card to the other, we add one extra route in each
MLS card under routing configuration, which is the IP address of the other MLS card.

For the MLS uplink removal alarm detection over NGEMS servers, the configuration to be done is as
follows:

1. Configuration of SNMP Traps:

→ Create three entries for the PR NGEMS server IP addresses:

Example : Two entries of the physical IP addresses of the NGEMS servers

(10.187.1.39 and 10.187.1.40 as shown in the screenshot)

One entry of the floating IP address of NGEMS server

(10.187.1.41 in the screenshot)

→ Create one entry for the GR NGEMS server IP address:

Example:

The floating IP address of the GR NGEMS server 10.187.0.169

19
 PR-EMS1 IP : 10.187.1.39

PR-EMS2 IP : 10.187.1.40

PR-EMS FVIP : 10.187.1.41

GR-EMS FVIP : 10.187.0.169

2. Configuration of Static Route for NGEMS.

→ Static Route Creation in MLS-1:

Note: There are two limitations in the MLS card configuration that we cannot add a
mask length smaller than /30 and the network addresses have to be multiples of 4,
such as 4,8,12,16 and so on.

Therefore, to add the physical IP address of the first NGEMS server on the MLS-1,
we have to configure an IP address such that the NGEMS -1 server is covered.

This is shown in the example below:

20
 For reaching 10.187.1.39, we use the network IP 10.187.1.36/30 so that we can
reach the IP address 10.187.1.39.

For this MLS-1 card, the gateway should be the IP address of the other MLS (MLS-
2) card, which is shown as 10.188.14.7 here.

Example :

→ Static Route Creation in MLS-2

For the static routes on the MLS-2 card, we include the physical IP address of the
NGEMS -2 server and the floating IP address of the NGEMS server.

For this, we add a network IP address to include the both given our limitation of /30
and multiple of 4.

Example here is that 10.187.1.40 includes the IP addresses 10.187.1.40 and

10.187.1.41, that is the physical IP address of the NGEMS server 2 and the floating
IP address of the NGEMS servers.

For the second MLS card, the gateway IP address should be the IP address of the
first MLS card, shown as 10.188.14.4 here.

21
Example :

22