Alcatel Dual Layer Configuration

Summary

Dual Layer Networking prepared to ensure LAN’s traffic flow among themselves without reaching Antikor v2.
If any client which in a LAN wants to reach an external address, it shall get service from Antikor v2 otherwise it wants to reach an internal but different LAN, it will suffice to get service from backbone switch.

Network Topology

Configuration

The configurations these are required for the backbone switch shown below:

Spine Switch

spine_sw. show configuration snapshot
! Stack Manager :
! Chassis :
system name OmurgaRektorluk
! Configuration:
! VLAN :
vlan 1 enable name "VLAN 1"
vlan 100 enable name "Engineer"
vlan 101 enable name "Architect"
vlan 102 enable name "idari"
vlan 100 ip 10.33.100.1 255.255.255.0
vlan 101 ip 10.33.101.1 255.255.255.0
vlan 102 ip 10.33.102.1 255.255.255.0
! VLAN SL:
! IP :
ip service all
! IPX :
! IPMS :
! AAA :
aaa authentication console "local"
aaa authentication ftp "server2" "server3" "local"
aaa authentication http "server2" "server3" "local"
aaa authentication snmp "local"
aaa authentication ssh "server2" "server3" "local"
user password-size min 1
user password-history 0
! PARTM :
! AVLAN :
! 802.1x :
! QOS :
! Policy manager :
! Session manager :
! SNMP :
snmp security no security
snmp authentication trap enable
! RIP :
! IPv6 :
! IPRM :
ip static-route 0.0.0.0/0 gateway 172.24.42.1 metric 1
! RIPng :
! Health monitor :
! Interface :
interfaces 1/1 hybrid FORCED-COPPER
interfaces 2/1 hybrid FORCED-COPPER name "ANTIKOR"
! Udld :
! Port Mapping :
! Link Aggregate :
! VLAN AGG:
! 802.1Q :
vlan 100 802.1q 1/1 "TAG PORT 1/1 VLAN 100"
vlan 101 802.1q 1/1 "tag port 1/1 vlan 101"
vlan 102 802.1q 1/1 "TAG PORT 1/1 VLAN 102"
vlan 100 802.1q 2/1 "TAG PORT 2/1 VLAN 100"
vlan 101 802.1q 2/1 "TAG PORT 2/1 VLAN 101"
vlan 102 802.1q 2/1 "TAG PORT 2/1 VLAN 102"
! Spanning tree :
bridge mode 1x1
! Bridging :
! Bridging :
! Port mirroring :
! UDP Relay :
! Server load balance :
! System service :
debug fscollect disable
! SSH :
! Web :
! AMAP :
! LLDP :
! Lan  Power :
! NTP :
ntp client enable
! RDP :
! VLAN STACKING:
! Ethernet-OAM :

Faculty of Engineering and Architecture Switch:

Note: Depending on demand, more endpoints can be carried as many times as desired.

muhmim_sw. show configuration snapshot
! Stack Manager :
! Chassis :
system name Engineer_Architect
! Configuration:
! VLAN :
vlan 1 enable name "VLAN 1"
vlan 100 enable name "Engineer"
vlan 101 enable name "Architect"
vlan 102 enable name "Administrative"
vlan 100 ip 10.33.100.2 255.255.255.0
vlan 101 ip 10.33.101.2 255.255.255.0
vlan 102 ip 10.33.102.2 255.255.255.0
! VLAN SL:
! IP :
ip service all
! IPX :
! IPMS :
! AAA :
aaa authentication ssh "server2" "server3" "local"
user password-size min 1
user password-history 0
! PARTM :
! AVLAN :
! 802.1x :
! QOS :
! Policy manager :
! Session manager :
! SNMP :
snmp security no security
snmp authentication trap enable
! RIP :
! IPv6 :
! IPRM :
! RIPng :
! Health monitor :
! Interface :
interfaces 1/1 hybrid FORCED-COPPER
interfaces 1/2 hybrid copper speed 1000
interfaces 1/2 hybrid copper duplex full
interfaces 1/3 hybrid copper speed 1000
interfaces 1/3 hybrid copper duplex full
interfaces 1/4 hybrid copper speed 1000
interfaces 1/4 hybrid copper duplex full
! Udld :
! Port Mapping :
! Link Aggregate :
! VLAN AGG:
! 802.1Q :
vlan 100 802.1q 1/1 "TAG PORT 1/1 VLAN 100"
vlan 101 802.1q 1/1 "tag port 1/1 vlan 101"
vlan 102 802.1q 1/1 "TAG PORT 1/1 VLAN 102"
vlan 100 802.1q 1/2 "TAG PORT 1/2 VLAN 100"
vlan 101 802.1q 1/3 "TAG PORT 1/3 VLAN 101"
vlan 102 802.1q 1/4 "TAG PORT 1/4 VLAN 102"
! Spanning tree :
bridge mode 1x1
! Bridging :
! Bridging :
! Port mirroring :
! UDP Relay :
! Server load balance :
! System service :
debug fscollect disable
! SSH :
! Web :
! AMAP :
! LLDP :
! Lan  Power :
! NTP :
ntp client enable
! RDP :
! VLAN STACKING:
! Ethernet-OAM :

Testing

From pc2 to pc0 tracert image;

When we run traceroute from PC 2 to PC 0, we saw that the traffic did not go as far as Antikor v2 and turn around to right destination Network from Backbone Switch.

Please follow Antikor v2 Dual Layer Configurations Manual for required settings on the Antikor v2 side.

Troubleshooting

Runing Command	Error Message	Solution Suggestion
`ping 10.2.1.2`	— Ping statistics for 10.0.0.1 — 5 packets transmitted, 0 packets received, 100.0% packet loss	Check the status of the ports.
		Review VLAN settings.

Back PDF