BSNL MAAN Training

BSNL MAAN Training
© Tejas Networks Limited 2024. All rights reserved.

Training Schedule: IP MPLS
Time 11:00 AM – 12:00 PM 12:15 PM – 1:15 PM 2:00PM – 3:00PM
Installation &
Overview of A3 / A4
Commissioning Transport Deployment
Node
Day – 1 + Scenarios With CEF12T
+
Configuration &
Network Deployment
Integration from EMS
Tejas Networks Limited 2024. All rights reserved. 2

Brief Introduction of MAAN & Tejas
Proposed Products
3
© Tejas Networks Limited 2024. All rights reserved.
MAAN Tender Requirement
Power Supply
Controller, XC Packet Switching Tejas Proposed
Type of Node Power Redundancy Uplink/ Downlink Interfaces
Redundancy Fabric (Min) model
(Yes/No)
2x10G + 8x1G Base-X +
A3-Cat 1 DC Yes No 25 Gbps TJ1400P-4XCi
2x10/100/1000 Base-T + 4xE1
A3-Cat 2 DC Yes No 25 Gbps TJ1400P-4Xi
2x10/100/1000 Base-T
A4-Cat-1 AC Yes No 25 Gbps TJ1400P-4XCi
2x10/100/1000 Base-T + 4xE1
A4-Cat-2 AC Yes No 25 Gbps TJ1400P-4Xi
2x10/100/1000 Base-T
B3-Cat 1 DC Yes No 60 Gbps 4x10/100/1000 Base-T + TJ1400P-4XC
4xSTM-1 (O)
B3-Cat 2 DC Yes No 60 Gbps TJ1400P-4X
4x10/100/1000 Base-T
2x100G + 10x10G + 10x1G
B4-Cat 1 DC Yes No 300 Gbps Base-X + 4x10/100/1000 Base-T TJ1400P-H
+ 4xSTM-1 (O)
2x100G + 10x10G + 10x1G

B4-Cat 2 DC Yes No 300 Gbps TJ1400P-H
Base-X + 4x10/100/1000 Base-T
4x100G + 30x10G + 32x1G

C1 DC Yes Yes 800 Gbps Base-X + 4x10/100/1000 Base-T TJ1400-18
+ 4xSTM-1 (O)
.© Tejas Networks Limited 2024. All rights reserved. 4

Tejas IP/MPLS Router Platforms for MAAN
A3/A4 Cat-1/2 B3 Cat 2
Small Pizza
box OLT
TJ1400P-4X B3 Cat-1
Small Pizza
TJ1400P Series 1RU Platform box OLT
B4 Cat-1/2
TJ1400P-H
C1
Small Pizza
TJ1400 Series Redundant Platform box OLT
TJ1400-18

Overview of A3 / A4

Tejas Products for A3 & A4
A3 Cat-1 Model
TJ1400P-4XCi
A3 Cat-2 Model
TJ1400P-4Xi
TIMING NMS DC PSU-1 DC PSU-2
OAM +
PSU: Redundant DC USB
A4 Cat-1 Model
TJ1400P-4XCi
A4 Cat-2 Model
TJ1400P-4Xi
TIMING NMS AC PSU-1 AC PSU-2
OAM +
PSU: Redundant AC USB

A3 Configuration
1 3 5 7 8 9 10 11
1
1
Numbering Description Numbering Description

2 4 6
1 Alarm Out 6 USB port
2 Alarm In/DIAG 7 P1-12 (12*1G Base-X)
3 BITS port 8 P13-14 (2*10G)
4 TOD port 9 P17-20 (4*1G Base-T)
5 NMS port 10 4 E1 ports
11 DC Power supply
Note: Port 15 & Port 16 are disabled and not in use.

E1 interface is enabled only for A3 Cat-1.
DC power cable color codes
This section lists the color-coding scheme used for the various cables used in the system.
Power cable:
WARNING: Above are some of the DC wiring color code followed. Ensure that the correct polarity is connected
to the DC power supply unit, confirm the connection of the power cables to the + (positive) and - (negative)
leads at the power source.

A4 Configuration
1 3 5 7 8 9 10 11
2 4 6 Numbering Description Numbering Description

1 Alarm Out 6 USB port
2 Alarm In/DIAG 7 P1-12 (12*1G Base-X)
3 BITS port 8 P13-14 (2*10G)
4 TOD port 9 P17-20 (4*1G Base-T)
5 NMS port 10 4 E1 ports
11 AC Power supply
Note: Port 15 & Port 16 are disabled and not in use.

E1 interface is enabled only for A4 Cat-1.
A3/A4 Rear View
Models: TJ1400P-4XCi, TJ1400P-4Xi

A3-Cat-1 & A4 Cat-1 Parameters
TJ1400P-4XCi: 2x10G + 8x1G Base-X + 2x10/100/1000 Base-T + 4xE1.

• Suitable for A3-Cat-1 & A4 Cat-1 (With E1 Interface).
• Supports Modular AC as well as DC Power Supplies with Max Power Consumption of 140W.
• 1 RU, 19-inch rack-mountable chassis with front access AC/DC redundant power supplies and traffic
interfaces.
• Supports Extended Range of Operating Temperatures as per tender i.e. -15°C to 60°C
• SFP Types: 10G (Duplex LC SFP+), 1G Base-X (Duplex LC SFP).
Note: Only Industrial Type SFPs to be used with A3 and A4

A3-Cat-2 & A4 Cat-2 Parameters
TJ1400P-4Xi: 2x10G + 8x1G Base-X + 2x10/100/1000 Base-T

• Suitable for A3-Cat-2 & A4 Cat-2 (Without E1 Interface).
• Supports Modular AC as well as DC Power Supplies with Max Power Consumption of 140W
• 1 RU, 19 inches rack mountable chassis with front access AC/DC redundant power supplies and traffic
interfaces.
• Supports Extended Range of Operating Temperatures as per tender i.e. -15°C to 60°C
• SFP Types: 10G (Duplex LC SFP+), 1G Base-X (Duplex LC SFP)
Note: Only Industrial Type SFPs to be used with A3 and A4

A3 & A4 Physical Parameters
Parameters TJ1400P-4XCi / TJ1400P-4Xi

PSU Redundancy Yes (AC/DC)
Field Replaceable Fan Tray (s) Yes
Timing and OAM Interfaces NMS, USB, BITS, DIAG, ToD, Alarm In / Alarm Out
Dimensions (WxHxD) mm 444 x 44 x 260
Max Power Consumption 140 W

Network Deployment

MAAN BA Topology Overview

A3 / A4 – Planning for Access Network
Sample Planning – Hierarchical Architecture
C1
Access A3/A4
❑ A3 & A4 type nodes are MPLS-IP based &
used as access nodes.
B4 B4
❑ A3/A4 are Pizza box type nodes without
Access
redundancy in control Plane.
Aggregation
A3/A4
B4 B4
❑ 10G ports in A3/A4 can be used for uplink
connectivity with B3/B4 or C1
Pre-Aggregation
❑ A3/A4 is not advised to be part of B4/C1 ring
B3 B3
Access ❑ End client systems like OLT, Enterprise,
Access A3/A4 2G/3G/4G can be connected on 1G/10G ports
Access
A3/A4 of A3/A4 depending on Bandwidth
A3/A4 requirement.
A3/A4
A3/A4
© Tejas Networks Limited 2024. All rights reserved. 17

Architecture – AS (BGP Autonomous System)
B4/C1
B3 SER
A3/A4
B4/C1
A3/A4
B3
MPLS
Exchange
SDCA BA/OA Core
AS X MAAN BA 2
B4/C1
B3
A3/A4 SER
MAAN BA 1 B4/C1
A3/A4
Circle 1
BGP AS A BGP AS A
Each circle to have a unique BGP AS for MAAN

Architecture – Service B4/C1
B3
A3/A4
B4/C1 B4/C1
B3
SER
A3/A4
Exchange
CE SDCA BA/OA
ABR ABR
A3/A4 B3 B4/C1
AS A
OSPF Area 1 OSPF Area 2 OSPF Area 3

IGP
MPLS LSP MPLS LSP MPLS LSP
MPLS
BGP BGP LSP BGP LSP BGP LSP
LU LU LU LU
VLAN/IP L2VPN/L3VPN/CEM VLAN/IP
Service LSP
A3/A4 Node Commissioning

4/29/2024

Safety Precaution
Read the following precautions while handling and installing
• Wear an anti-static wrist strap or a heel grounder, before you remove a module from its package or from the
shelf.
• In the process of replacing a node, place the node on an anti-static cover or on an anti-static foam.
• Avoid touching the solder side of the module, the pin connector, or the components.
• Inspect each module for damage before inserting the component into the shelf.
• Store the uninstalled node inside an anti-static cover and place this cover in its original packaging box.
• Avoid stacking nodes on or against each other. Check the stacking limit symbol, if any, on the package box.
• Avoid forcing nodes into their packaging material.
• Avoid storing several nodes in the same container.
• Allow each module to reach room temperature before you insert the module into the shelf.

Safety Precaution
• When not in use, pluggable modules are packed inside an anti-static bag and placed inside foam packaging to
prevent damage to the exposed connector terminals.
• To prevent damage to cards in storage, follow procedures that prevent accumulation of dirt or dust on the pin
connectors and damage to the printed circuit board. This situation is typical for printed circuit boards stored
in areas where the humidity can exceed 95% and the temperature can exceed 70°C.
• While transporting cards, pack each module in its original anti-static container and padding or in an anti-static
bag. In case the original packing material is lost, place the module in an anti-static bag and use another
container with sufficient padding.
• Clean air filters every 15 to 30 days

Mounting the chassis in a rack
Perform the following steps to install the TJ1400 node in a rack:
• Depending on the access requirements, decide which side you want to use as the front side in the rack.
• Determine the position of the chassis in the rack and the rack holes to use for mounting. Note that the node
should always be installed in a rack starting at the bottom and working upwards to maintain the rack stability.
• Move the chassis to the required rack position.
Install a cage nut on the rack post

Mounting the chassis in a rack
• Align the holes on the mount angles (both Left and Right) of the chassis with the mounting holes in the rack.
• If cable routers/guides are required to install (optional), then position the cable router/guide such that its
mounting holes are aligned with holes on the mount angle and the rack post.
Installing node into the rack

Node Initialization
Installation, commissioning, and testing process

Commission the node
We need to follow the procedures for commissioning the node. Commissioning is executed through
the CLI.
Connect the PC to the NMS interface.

• You have a PC and an Ethernet cable with RJ-45 connector.
• You have MobaXterm or Putty in the PC.
Note: After powering up the node, wait for few minutes for the node software to come up. The Status/Active
LED indicates the UP status of the node.

Login uncommissioned Node
• Ensure the IP address of the PC is in the same IP
subnet of the node. If you are commissioning the
node for the first time, then set any address to the
PC other than 192.168.1.254 in the 192.168.1.0
subnetwork.

Log in to an un-commissioned node
Before logging in to an un-commissioned node:
• Ensure that the PC is connected to the NMS interface of the node through an Ethernet cable with RJ-45
connectors.
• Perform the following steps to log in to an un-commissioned node:
1. Launch MobaXterm or Putty application and execute the following command:
telnet < node ip > port number(1010)
Note: Once the node is upgraded node can be reachable through telnet < node ip >
Note: The TELNET port access is on default port 23.

The following login prompt appears:
• If the node does not respond, check the physical connection. Ping the TJ1400 IP (192.168.1.254) address
using the command prompt and check the ping response received. If no response is received then contact
Technical Support Information.

• If the login screen appears then enter the default username and password at the login prompt.
Username: tejas
Password: j72e#05t

Set date and time
To set the date and time on the node, execute the following commands from the configure terminal:
• tejas(config)# system date <month/day/year>
• tejas(config)# system time <hh:mm:ss>

Set date and time
To see the system time, execute the following commands from the privilege terminal:
• tejas# show date
• tejas# show time

IP Configuration
To set the Ethernet IP and Router IP on the node, execute the following commands from the configure
terminal:
system name BSNLMAAN router-id 20.20.20.20
• Enter the command as Y. (Node goes on a reboot)

Demo Set up
Loopback id-1
LU loopback id- 2
192.168.105.80 192.168.105.90
1/1/1 1/1/1
LB- 192.168.105.80 LB- 192.168.105.90

Interface IP- 10.10.10.1 Interface IP 10.10.10.2
LU-20.20.20.1 LU-20.20.20.2
Area- 0.0.0.10
VLan- 10
AS NO.- 100

BSNL_MAAN_SETUP

Interface Configuration
• Configuration of DCN loopback address:
Configure terminal
int loopback <id>
ip add <DCN_loopback-address> 255.255.255.255
no shut
end

• Configuration of LU loopback address:
Configure terminal
int loopback <id>
ip add <LU_loopback-address> 255.255.255.255
no shut
end

Vlan &IP address configuration:
configure terminal
int <port-speed> <chassis>/<slot-no>/<port-No.>
set mpls enable
no shut
vlan <A>
ip add <A.B.C.T> 255.255.255.254
end

Vlan &IP address configuration:
configure terminal
int <port-speed> <chassis>/<slot-no>/<port-No.>
set mpls enable
no shut
vlan <B>
ip add <A.B.C.U> 255.255.255.254
set mpls enable
no shut
end

Configuration Output
Show command for Interface configuration:
• show ip interface brief

OSPF Configuration
configure terminal
router ospf
router-id <DCN_loopback-address>
net <A.B.C.U> area 0.0.0.<A>
net <A.B.C.T> area 0.0.0.<A>
net <DCN_loopback-address> area 0.0.0.<A>
net <LU_loopback-address> area 0.0.0.<A>

OSPF Configuration
configure terminal
VLAN <A>
ip ospf network point-to-point
exit
VLAN <B>
ip ospf network point-to-point
exit
end

Show command for OSPF configuration:
• show run ospf
• Show ip ospf neighbour

Route Map Configuration
configure terminal
route-map Deny_LU deny
match community comm-num 6553602
end

Show command for Route map configuration:
• show route-map

BGP Configuration
configure terminal
router bgp <AS.NO>
bgp router-id <DCN_loopback-address>
nei <ABR_R4-DCN-loopback-1> remote-as <AS.NO>
nei <ABR_R4-DCN-loopback-1> update-source <DCN_loopback-address>
nei <ABR_R5-DCN-loopback-1> remote-as <AS.NO>
nei <ABR_R5-DCN-loopback-1> update-source <DCN_loopback-address>

BGP Configuration
address-family ipv4
nei <ABR_R4-DCN-loopback-1> active
nei <ABR_R4-DCN-loopback-1> route-map Deny_LU in
nei <ABR_R5-DCN-loopback-1> active
nei <ABR_R5-DCN-loopback-1> route-map Deny_LU in
exit

Enabling address family
address-family vpnv4
exit
address-family l2vpn
exit
address-family ipv4-label-unicast
exit
end

Show command for BGP configuration:
• show run bgp
• show ip bgp summary

A3/A4 Node Upgradation
through CLI

Node Upgrade
• Log on to node through CLI
• copy <username> <password> <ip_addr> <directory>
• check upgrade
• load upgrade
• invoke upgrade coldbootupgrade
Note: Node goes on reboot

A3/A4 Node Upgradation
through GUI

Node Upgrade
• Log on to node through GUI
• Click on Maintenance >>> Unified operations >>> Unified upgrade
• Enter <username> <password> <ip_addr> <directory>
• Check upgrade
• Load upgrade
• Invoke upgrade
• Commit upgrade
Note: Node goes on reboot

TEJAS ELEMENT MANAGEMENT
SYSTEM.

ELEMENT MANAGEMENT SYSTEM OVERVIEW.
• A Element Management System (EMS) is an application or set of applications that lets network administrators manage a network’s independent
components inside a bigger management framework. EMS may be used to monitor both software and hardware components in a network. EMS
permits the user to monitor their entire business operations using a central computer.
• The functionalities supported by EMS include:
• Network monitoring: NMS software monitors network hardware to ensure all devices are operating correctly and are not near or at full capacity.
• Device detection: When a new device is connected to the network, it can be recognized, configured, and added to the network using NMS.
• Performance analysis: NMS can analyse the current and historical performance of a network. This includes the overall performance of the network,
individual devices, and connections.
• Device management: NMS provides a simple way to manage multiple devices from a central location.
• Fault management: If a device in the network fails, NMS can detect it and reroute the traffic. This action is accomplished using a set of preconfigured
rules.

TEJAS SUBTENTED EMS
• ADD SUBTENTED EMS
Once the installation of the Element Management System (EMS) and subtended EMS is completed, users can log into
the EMS interface using valid credentials. This involves accessing the EMS application, entering the appropriate URL,
providing the assigned username and password, and clicking the login button. The EMS authenticates the user's
credentials, checks authorization levels, and, upon success, grants access to the EMS dashboard or main interface.

TEJAS SUBTENTED EMS
• After successfully logging into the home page of the Element Management System (EMS), users can initiate the
process of adding a subtended EMS by clicking on the "Add Subtended EMS" button located in the left top corner.
This action prompts a form to appear, where users must fill in essential details such as the subtended EMS IP address,
name, EMS type, as well as the associated username and password. These details are crucial for establishing
communication and coordination between the main EMS and the subtended EMS.

TEJAS SUBTENTED EMS
• Upon the successful addition of the subtended EMS, users can observe the configuration state column displaying
"IN_SYNC" and the communication state column indicating "AVAILABLE."

ADD NODES IN EMS
• STEPS TO ADD NODES IN EMS
To add nodes in the Element Management System (EMS), the user needs to follow a specific navigation path. Starting
from the home page, the user should navigate to the "Manage Nodes" section. Once on the "Manage Nodes" page,
users can find options or buttons to add new nodes to the network.

ADD NODES IN EMS
• To add a node in the Element Management System (EMS), users can follow a simple process. Click on the "Add NE"
button located in the left top corner of the interface. In the ensuing form, enter the node's router ID in the "Node IP"
field, along with details such as the subtended EMS name, partition label, and communication protocol, set to SNMP
v1. Choose the default SNMP community username and password. Finally, click on the "Add Node" button to
complete the node addition process.

ADD NODES IN EMS
• Upon successful addition of nodes in the Element Management System (EMS), the "Communication status" column
will indicate "Available," confirming that the nodes are actively communicating with the EMS. Additionally, the "EMS
Sync state" column will display "ACTIVE," signifying that the synchronization state between the EMS and the added
nodes is established and operational. These status indicators assure users that the nodes are integrated seamlessly
into the EMS, and communication channels are open and available for efficient network monitoring and
management.

TOPOLOGY LINK CONFIGURATION BETWEEN THE
NODES FROM EMS
• STEPS TO CONFIGURE TOPOLOGY LINK FROM ‘MANAGE IP MPLS’ PAGE IN EMS
To configure Topology Link between the nodes from the EMS (Element Management System), users need to navigate to
the "Manage IP MPLS" page, where user can see multiple nodes that has added to the EMS.

NODES FROM EMS
To establish a connection between two nodes in the physical topology view, the user should first select the two nodes
they want to link. Next, they should locate and click on the "Create Topology Link" button located in the top bar.

NODES FROM EMS
To configure a connection between nodes in the physical topology view, the user must first select the dedicated source
and destination partitions. If the TL Type (Topology Link Type) isn't already chosen, it needs to be set to 'Ethernet'.
Additionally, the capacity should be adjusted based on the port capacity of the nodes involved. The source and
destination ports will then be automatically selected based on the corresponding nodes. It's essential to keep the TL
mode set to 'Online'. Once these settings are adjusted, the user can proceed by clicking on the 'Submit' button. This
action will finalize the configuration, establishing the desired connection between the selected nodes.

Transport Deployment Scenarios
With CEF12T

TJ1400-7 eNodeB : BBU Modules
CEF12T
CEF12
TJ1400-7
RAC
Radio Access Controller Card
▪ 3Nos. of CPRI interface ports (P1 to P3) to connect to RRH & P4 for Backhaul connectivity
CEF Module
▪ Controller Card for Backhaul Connectivity(CEF12) with 1*1GE and Electrical GE
▪ Integrated transport & Controller Card (CEF12T) with 2*10GE, 2*1GE and 4*E1 interfaces to support integrated transport
functionality

2G+3G+4G Transport Solution with CEF12T
E1
2G BTS eNB
(CEF12T) 2G+3G+4G
VLAN
3G NB VLANs Core BSC
CPAN/MAAN
E1
2G BTS eNB Node STM-1
(CEF12T) 2G+3G+4G
CEM Drop Shelf/ B3 (2G E1s)
VLAN VLANs
(Cat-1)/ B4 (Cat-1)/C1
3G NB
BSNL Transport network

VLAN eNB
2G+3G
(CEF12T)
NB
RNC
2G BTS
E1 CPAN/MAAN
Node
2G+3G+4G
3G NB VLAN
eNB VLANs
(CEF12T)

2G+3G+4G Transport Solution with CEF12T (10G
Ring) BSC
E1 eNB
2G BTS (CEF12T)
VLAN STM-1
3G NB 2G+3G+4G
Core (2G E1s)
VLANs
E1 CEM Drop Shelf/ B3
2G BTS eNB (Cat-1)/ B4 (Cat-1)/C1
(CEF12T) CPAN/MAAN
10G Ring
VLAN
3G NB eNB
Node
(CEF12T)
VLAN eNB
2G+3G
NB (CEF12T) BSNL Transport network
2G+3G+4G
E1 VLANs
2G BTS
eNB RNC
(CEF12T)
VLAN
3G NB
eNB 2G BTS
(CEF12T)
Tejas Networks Limited 2024. All rights reserved. 69 3G NB
2G+3G+4G Transport Solution with CEF12T (10G
Ring) BSC
E1 eNB
2G BTS (CEF12T)
VLAN STM-1
3G NB 2G+3G+4G
Core (2G E1s)
VLANs
E1 CEM Drop Shelf/ B3
2G BTS eNB (Cat-1)/ B4 (Cat-1)/C1
(CEF12T)
10G Ring
VLAN
3G NB CPAN/MAAN
Node
VLAN eNB
2G+3G
NB (CEF12T) BSNL Transport network
2G+3G+4G
E1 VLANs
2G BTS
eNB RNC
(CEF12T)
VLAN
3G NB
eNB 2G BTS
(CEF12T)
Tejas Networks Limited 2024. All rights reserved. 70 3G NB
E1 Transport Scenario Via CEF12T RNC
BSNL IP
BSNL CPAN
3G NodeB NW
1G (O)
Site2 Site1 BSC
Dark fiber BSNL E1
CEF12T CEF12T E1 Node
10G (O) 10G (O)
1G (O)
E1
3G NodeB 2G BTS
Site1: 1. Existing 2G BTS to be connected to CEF12T CEM Ports Via E1 interface
2. Existing 3G NodeB to be connected to CEF12T P2 Port Via Optical 1G Interface
3. Combined traffic of 2G+3G will transported via P3 Port towards BSNL CPAN NW.
Site2: 1. P1 port of CEF12T Connected BSNL CPAN via P2 interface receive the traffic from Site1
2. Existing 3G NodeB to be connected to CEF12T P1 Port Via Optical 1G interface
3. CEF12T E1 Port to connected BSNL E1 Traffic Node to transport E1 traffic of Site1 which received Via CPAN further to establish communication towards BSC.
4. Site1 and Site2 combined 3G traffic to be transported via P3 Port toward BSNL IP MPLS network further to establish communication towards RNC.

Thank you!
Contact Us:
trg@tejasnetworks.com
Tejas Networks Limited 2024. All rights reserved.

BSNL MAAN Training

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

BSNL MAAN Training

Uploaded by

Copyright:

Available Formats

BSNL MAAN Training

© Tejas Networks Limited 2024. All rights reserved.

Time 11:00 AM – 12:00 PM 12:15 PM – 1:15 PM 2:00PM – 3:00PM

Tejas Networks Limited 2024. All rights reserved. 2

2x100G + 10x10G + 10x1G

4x100G + 30x10G + 32x1G

.© Tejas Networks Limited 2024. All rights reserved. 4

.© Tejas Networks Limited 2024. All rights reserved. 5

.© Tejas Networks Limited 2024. All rights reserved. 6

.© Tejas Networks Limited 2024. All rights reserved. 7

Numbering Description Numbering Description

Note: Port 15 & Port 16 are disabled and not in use.

Tejas Networks Limited 2024. All rights reserved. 9

2 4 6 Numbering Description Numbering Description

Note: Port 15 & Port 16 are disabled and not in use.

.© Tejas Networks Limited 2024. All rights reserved. 11

TJ1400P-4XCi: 2x10G + 8x1G Base-X + 2x10/100/1000 Base-T + 4xE1.

Note: Only Industrial Type SFPs to be used with A3 and A4

Tejas Networks Limited 2024. All rights reserved. 12

TJ1400P-4Xi: 2x10G + 8x1G Base-X + 2x10/100/1000 Base-T

Note: Only Industrial Type SFPs to be used with A3 and A4

Tejas Networks Limited 2024. All rights reserved. 13

Parameters TJ1400P-4XCi / TJ1400P-4Xi

Field Replaceable Fan Tray (s) Yes

Dimensions (WxHxD) mm 444 x 44 x 260

Max Power Consumption 140 W

Tejas Networks Limited 2024. All rights reserved. 14

Tejas Networks Limited 2024. All rights reserved. 15

Tejas Networks Limited 2024. All rights reserved. 16

© Tejas Networks Limited 2024. All rights reserved. 17

Each circle to have a unique BGP AS for MAAN

Tejas Networks Limited 2024. All rights reserved. 18

OSPF Area 1 OSPF Area 2 OSPF Area 3

Tejas Networks Limited 2024. All rights reserved. 20

Tejas Networks Limited 2024. All rights reserved. 21

Tejas Networks Limited 2024. All rights reserved. 22

Tejas Networks Limited 2024. All rights reserved. 23

Install a cage nut on the rack post

Tejas Networks Limited 2024. All rights reserved. 24

Installing node into the rack

Tejas Networks Limited 2024. All rights reserved. 25

Tejas Networks Limited 2024. All rights reserved. 26

Connect the PC to the NMS interface.

Tejas Networks Limited 2024. All rights reserved. 27

Tejas Networks Limited 2024. All rights reserved. 28

Tejas Networks Limited 2024. All rights reserved. 29

Tejas Networks Limited 2024. All rights reserved. 30

Tejas Networks Limited 2024. All rights reserved. 31

• tejas(config)# system time <hh:mm:ss>

Tejas Networks Limited 2024. All rights reserved. 32

Tejas Networks Limited 2024. All rights reserved. 33

system name BSNLMAAN router-id 20.20.20.20

• Enter the command as Y. (Node goes on a reboot)

Tejas Networks Limited 2024. All rights reserved. 34

LB- 192.168.105.80 LB- 192.168.105.90

Tejas Networks Limited 2024. All rights reserved. 35

Tejas Networks Limited 2024. All rights reserved. 36

Tejas Networks Limited 2024. All rights reserved. 37

Tejas Networks Limited 2024. All rights reserved. 38

Tejas Networks Limited 2024. All rights reserved. 39

Tejas Networks Limited 2024. All rights reserved. 40

Tejas Networks Limited 2024. All rights reserved. 41

Tejas Networks Limited 2024. All rights reserved. 42