0% found this document useful (0 votes)
852 views5 pages

V-Sol GPON OLT Configuration Guide

The document configures VLANs, line profiles, service profiles, and assigns them to PON interfaces to provide network access to ONUs. VLANs 471-478 are created and assigned to uplink ports. Line and service profiles are created for each VLAN and assigned to the corresponding PON interface.

Uploaded by

M.S. FARHAD
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
852 views5 pages

V-Sol GPON OLT Configuration Guide

The document configures VLANs, line profiles, service profiles, and assigns them to PON interfaces to provide network access to ONUs. VLANs 471-478 are created and assigned to uplink ports. Line and service profiles are created for each VLAN and assigned to the corresponding PON interface.

Uploaded by

M.S. FARHAD
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd

==================vlan create============================

vlan 471 - 478

=====================vlan assign in uplink port======================


interface range giga 0/1-8
switchport mode trunk
switchport trunk vlan 471 - 478

exit

===================IP MANAGEMENT==========================
interface vlan 1603
ip address 1472.28.28.476 [Link]
exit
ip route [Link] [Link] 1472.28.28.476

====================line profile create=============================


profile line id 1 name PON-01-vlan-471
tcont 1 dba default1
gemport 1 tcont 1
service 1 gemport 1 vlan 471
service-port 1 gemport 1 uservlan 471 vlan 471
commit
exit

profile line id 2 name PON-02-vlan-472


tcont 1 dba default1
gemport 1 tcont 1
service 1 gemport 1 vlan 472
service-port 1 gemport 1 uservlan 472 vlan 472
commit
exit

profile line id 3 name PON-03-vlan-473


tcont 1 dba default1
gemport 1 tcont 1
service 1 gemport 1 vlan 473
service-port 1 gemport 1 uservlan 473 vlan 473
commit
exit

profile line id 4 name PON-04-vlan-474


tcont 1 dba default1
gemport 1 tcont 1
service 1 gemport 1 vlan 474
service-port 1 gemport 1 uservlan 474 vlan 474
commit
exit

profile line id 5 name PON-05-vlan-475


tcont 1 dba default1
gemport 1 tcont 1
service 1 gemport 1 vlan 475
service-port 1 gemport 1 uservlan 475 vlan 475
commit
exit

profile line id 6 name PON-06-vlan-476


tcont 1 dba default1
gemport 1 tcont 1
service 1 gemport 1 vlan 476
service-port 1 gemport 1 uservlan 476 vlan 476
commit
exit

profile line id 7 name PON-07-vlan-477


tcont 1 dba default1
gemport 1 tcont 1
service 1 gemport 1 vlan 477
service-port 1 gemport 1 uservlan 477 vlan 477
commit
exit

profile line id 8 name PON-08-vlan-478


tcont 1 dba default1
gemport 1 tcont 1
service 1 gemport 1 vlan 478
service-port 1 gemport 1 uservlan 478 vlan 478
commit
exit

=======creating 8 pcs srv profile with separate separate vlan=========

profile srv id 1 name PON-01-vlan-471-1G


portvlan eth 1 mode tag vlan 471
commit
exit

profile srv id 2 name PON-02-vlan-472-1G


portvlan eth 1 mode tag vlan 472
commit
exit

profile srv id 3 name PON-03-vlan-473-1G


portvlan eth 1 mode tag vlan 473
commit
exit

profile srv id 4 name P0N-04-vlan-474-1G


portvlan eth 1 mode tag vlan 474
commit
exit

profile srv id 5 name PON-05-vlan-475-1G


portvlan eth 1 mode tag vlan 475
commit
exit

profile srv id 6 name PON-06-vlan-476-1G


portvlan eth 1 mode tag vlan 476
commit
exit

profile srv id 7 name PON-07-vlan-477-1G


portvlan eth 1 mode tag vlan 477
commit
exit

profile srv id 8 name PON-08-vlan-478-1G


portvlan eth 1 mode tag vlan 478
commit
exit

==================================================================
profile srv id 10 name PON-01-vlan-471-2G
portvlan eth 1 mode tag vlan 471
portvlan eth 2 mode tag vlan 471
commit
exit

profile srv id 11 name PON-02-vlan-472-2G


portvlan eth 1 mode tag vlan 472
portvlan eth 2 mode tag vlan 472
commit
exit

profile srv id 12 name PON-03-vlan-473-2G


portvlan eth 1 mode tag vlan 473
portvlan eth 2 mode tag vlan 473
commit
exit

profile srv id 13 name P0N-04-vlan-474-2G


portvlan eth 1 mode tag vlan 474
portvlan eth 2 mode tag vlan 474
commit
exit

profile srv id 14 name PON-05-vlan-475-2G


portvlan eth 1 mode tag vlan 475
portvlan eth 2 mode tag vlan 475
commit
exit

profile srv id 15 name PON-06-vlan-476-2G


portvlan eth 1 mode tag vlan 476
portvlan eth 2 mode tag vlan 476
commit
exit

profile srv id 16 name PON-07-vlan-477-2G


portvlan eth 1 mode tag vlan 477
portvlan eth 2 mode tag vlan 477
commit
exit

profile srv id 17 name PON-08-vlan-478-2G


portvlan eth 1 mode tag vlan 478
portvlan eth 2 mode tag vlan 478
commit
exit
====================================================================
profile srv id 18 name PON-01-vlan-471-4G
portvlan eth 1 mode tag vlan 471
portvlan eth 2 mode tag vlan 471
portvlan eth 3 mode tag vlan 471
portvlan eth 4 mode tag vlan 471
commit
exit

profile srv id 19 name PON-02-vlan-472-4G


portvlan eth 1 mode tag vlan 472
portvlan eth 2 mode tag vlan 472
portvlan eth 3 mode tag vlan 472
portvlan eth 4 mode tag vlan 472
commit
exit

profile srv id 20 name PON-03-vlan-473-4G


portvlan eth 1 mode tag vlan 473
portvlan eth 2 mode tag vlan 473
portvlan eth 3 mode tag vlan 473
portvlan eth 4 mode tag vlan 473
commit
exit

profile srv id 21 name P0N-04-vlan-474-4G


portvlan eth 1 mode tag vlan 474
portvlan eth 2 mode tag vlan 474
portvlan eth 3 mode tag vlan 474
portvlan eth 4 mode tag vlan 474
commit
exit

profile srv id 22 name PON-05-vlan-475-4G


portvlan eth 1 mode tag vlan 475
portvlan eth 2 mode tag vlan 475
portvlan eth 3 mode tag vlan 475
portvlan eth 4 mode tag vlan 475
commit
exit

profile srv id 23 name PON-06-vlan-476-4G


portvlan eth 1 mode tag vlan 476
portvlan eth 2 mode tag vlan 476
portvlan eth 3 mode tag vlan 476
portvlan eth 4 mode tag vlan 476
commit
exit

profile srv id 24 name PON-07-vlan-477-4G


portvlan eth 1 mode tag vlan 477
portvlan eth 2 mode tag vlan 477
portvlan eth 3 mode tag vlan 477
portvlan eth 4 mode tag vlan 477
commit
exit

profile srv id 25 name PON-08-vlan-478-4G


portvlan eth 1 mode tag vlan 478
portvlan eth 2 mode tag vlan 478
portvlan eth 3 mode tag vlan 478
portvlan eth 4 mode tag vlan 478
commit
exit

==============line and srv profile set in pon interface=================


interface gpon 0/1
onu auto-learn line-profile name PON-01-vlan-471
onu auto-learn srv-profile name PON-01-vlan-471-1G
exit
interface gpon 0/2
onu auto-learn line-profile name PON-02-vlan-472
onu auto-learn srv-profile name PON-02-vlan-472-1G
exit
interface gpon 0/3
onu auto-learn line-profile name PON-03-vlan-473
onu auto-learn srv-profile name PON-03-vlan-473-1G
exit
interface gpon 0/4
onu auto-learn line-profile name PON-04-vlan-474
onu auto-learn srv-profile name P0N-04-vlan-474-1G
exit
interface gpon 0/5
onu auto-learn line-profile name PON-05-vlan-475
onu auto-learn srv-profile name PON-05-vlan-475-1G
exit
interface gpon 0/6
onu auto-learn line-profile name PON-06-vlan-476
onu auto-learn srv-profile name PON-06-vlan-476-1G
exit
interface gpon 0/7
onu auto-learn line-profile name PON-07-vlan-477
onu auto-learn srv-profile name PON-07-vlan-477-1G
exit
interface gpon 0/8
onu auto-learn line-profile name PON-08-vlan-478
onu auto-learn srv-profile name PON-08-vlan-478-1G
exit
write
loopback detect enable
fan tem 20
ip dns [Link] [Link]
no login-access-list deny telnet [Link] [Link]
no login-access-list deny snmp [Link] [Link]
web verification-code disable
web login timeout 30
write

Common questions

Powered by AI

Configuring a GPON interface to auto-learn from line and service profiles simplifies device deployment and management, as it allows automatic assignment of profiles to a newly connected ONU. The process involves specifying the line profile and associated service profile using the commands: 'onu auto-learn line-profile name [line profile]' and 'onu auto-learn srv-profile name [service profile]'. This configuration allows the GPON interface, like 'interface gpon 0/1', to dynamically apply settings without manual intervention . This functionality is important for large-scale deployments where automated provisioning reduces errors and time.

Creating VLANs in an uplink trunk port is crucial for segregating traffic into isolated networks, providing enhanced security and network management. In the given configuration, VLANs 471 to 478 are created and assigned to a range of ports in trunk mode. This is done using the command 'interface range giga 0/1-8 switchport mode trunk' followed by 'switchport trunk vlan 471 - 478' . This setup ensures that the specified range of VLANs can communicate across connected devices while maintaining separation from other VLANs.

IP routing in the management interface is configured with a default route using the command 'ip route 0.0.0.0 0.0.0.0 1472.28.28.476', pointing all unspecified network traffic to the gateway at IP 1472.28.28.476. This configuration ensures that devices on the network can access resources outside their local network by directing them to the gateway IP for outbound communication . This is significant because it facilitates communication across different subnets and to external networks, enabling functional inter-network operations.

The DNS configuration within the system assigns Google's public DNS servers using the command 'ip dns 8.8.8.8 8.8.4.4' . This setup provides robust, reliable, and fast DNS resolution for network devices, crucial for translating domain names into IP addresses. The use of well-known DNS servers enhances reliability and speed, also providing redundancy. This contributes to overall network functionality by ensuring accessibility and efficient name resolution across the network.

TCONT (Transmission Container) is a fundamental component in the line profile configuration of a GPON network, responsible for defining the logical channels for traffic. In the configuration, each line profile includes a 'tcont 1' command, specifying the TCONT ID. This configuration affects how bandwidth is allocated and managed across the network, enabling, for example, dynamic bandwidth allocation to optimize resource use while maintaining Quality of Service (QoS). It plays a critical role in ensuring efficient data transmission and handling of varying traffic loads.

Tagging mode in VLAN configuration refers to adding a VLAN identifier to packets as they traverse trunk links, ensuring they are recognized and processed according to their respective VLANs. In the configurations, the eth port is set to 'mode tag vlan' for several profiles. This usage is crucial for maintaining VLAN separation across switch environments and ensuring that traffic maintains its VLAN association as it moves through different parts of a network . Utilizing tagging is essential for traffic segregation and improving the efficiency and security of network traffic management.

Line profiles and service profiles serve different purposes in configuring a GPON interface. Line profiles mainly define the characteristics and resources allocated to an Optical Network Unit (ONU), such as the TCONT and DBAs. Service profiles, on the other hand, specify how traffic is managed by designating VLAN tagging and port VLAN modes. For example, in the configuration, 'line-profile name PON-01-vlan-471' is associated with its corresponding 'srv-profile name PON-01-vlan-471-1G', linking the underlying network setup to how services are delivered to end users .

Different VLANs across multiple Ethernet ports allow separate logical networks within the same physical network, improving security and traffic management. The configuration uses profiles such as 'profile srv id 18' to assign VLANs to multiple ports (eth 1 to eth 4 in this case) in tagged mode. This allows each port to be part of the specified VLAN, such as VLAN 471 for 'PON-01-vlan-471-4G' . By doing so, the same VLAN can span multiple physical ports, supporting network scaling and flexible network topology design.

Enabling 'loopback detect' in a GPON configuration helps prevent network loops, which can cause broadcast storms and network congestion. This feature is particularly useful in environments where physical loops are possible due to incorrect cabling or misconfigurations. The loopback detection command ('write loopback detect enable') ensures that the network can automatically identify and mitigate such issues by shutting down the affected port or disabling the loop prone devices . Activation of this feature is crucial in maintaining network stability and reliability.

The configuration enhances network security by denying specific access methods. Using commands like 'no login-access-list deny telnet 0.0.0.0 0.0.0.0' and 'no login-access-list deny snmp 0.0.0.0 0.0.0.0', it prevents unauthorized Telnet and SNMP access . These restrictions decrease vulnerabilities by blocking potential exploitation through widely attacked protocols, and thereby reduce the attack surface for unauthorized access to network devices, enhancing overall security.

You might also like