Why did the trunk stop working after changing cisco to dlink?

Question

Computer networks

Hello. When replacing the Cisco Catalyst WS-C2950-24 switch with a D-Link DGS-3100-24, the port that goes into the trunk to another D-Link (DGS-1100-08) stopped working.
Physics is ok, maybe everything works on cisco, if you return it back + checked Lan with a tester, everything is ok.
I sin on configs
Here from cisco , here from dlink
Port 13.
In syslog dlink the port does not even rise, there are no errors

Answer 1

I don’t know much about Dlinks, and unfortunately the config is not speaking, unlike tsisok.
But what can and should be checked?
1. Enable port
2. The port is in trunk mode
3. The port has permission to pass vlan2 if I understood correctly
4. 1100-08 has no restrictions on poppy and something like that

Answer 2

I see that you have only 3 Wealans: Office tag 2, Edu tag 3, WiFi tag 4.
Port 13 is configured on Cisco:

interface FastEthernet0/13
 description Hotel_Trunk
 switchport access vlan 2
 switchport mode trunk

where the line switchport access vlan 2does not play any role, since the trunk mode is enabled and each wealan comes with a tag.
On D-Link, the trunk mode is a separate entity, it may not be on the 3100, I don’t remember exactly, but for example, on the 36 series it is. Therefore, there is a universal way to add all Wealans to port 13 manually in tag mode , but you only have such a line for port 13 in the config:
that is, only one port is added and that one is in untag mode . To correct the situation, you need to do this:

config vlan Office del 1:13
config vlan Office add tagged 1:13
config vlan Edu add tagged 1:13
config vlan WiFi add tagged 1:13

Be careful D-Link doesn't keep a close eye on how velans are added, so it won't swear if you throw in two different untag velans , for example . You have to control it yourself.
PS There is not enough config from 1100, then it would be possible to say exactly what is missing for pairing 3100 and 1100

Answer 3

I'm not a master in dlinks either, but in your config (for dlinks) it's not even close that the 13th port is somehow declared as a trunk ... But about ch1 (23rd and 24th ports) there is a big suspicion that he is the trunk. Try to plug into the higher dlink not the 13th port, but the 23rd or 24th.

Answer 4

Switch the interface to nonegotiate mode on the cisco:
sw1(config-if)# switchport nonegotiate
and then return the port from errdisabled or reboot