topic Re: Trunk EXOS switch to a Cisco switch in ExtremeSwitching (EXOS/Switch Engine)

Trunk EXOS switch to a Cisco switch

gonzoessex — Sun, 05 May 2019 00:38:58 GMT

Hello,

I've worked with Cisco switches for years and never used an Extreme switch before. I have to trunk one to our Cisco network so have a Cisco switch and Extreme switch in a GNS3 lab.

I have had no luck getting a dot1q trunk working. I have the 2 switches connected and a workstation plugged into either switch.

I want to use to start very basic:

VLAN 100 (sales)
Native VLAN 999

Cisco
VLAN 100 IP should be 172.16.1.250/24

Extreme
VLAN 100 IP should be 172.16.1.251/24
Trunk should be on port 12
Workstation in port 1 in VLAN 100

Can someone help with the Extreme config?

Thanks

Re: Trunk EXOS switch to a Cisco switch

Tomasz — Mon, 06 May 2019 02:48:28 GMT

Hi,

If I understand your case correctly, you would need this:

code:

  create vlan 100 //it'll create VID 100 with name VLAN_0100, OR do "create vlan [somename] tag 100" instead; in any case you can refer to VLANs by "vlan [vid]" or "[vlan name]" in any command since couple of last firmware release versions; this enhancement allows you to issue a command for a range of VLANs, e.g. create vlan 101-120
  create vlan 999
  configure vlan 100 ipaddress 172.16.1.251/24 //or with full dotted-decimal notion for a netmask; you can also abbreviate, "conf vlan 100 ip" would do the job as well
  configure vlan 100 add ports 1,12 tagged //you can mix dash and comma for a list of ports, e.g. "1-2,5,8-12,23"
  configure vlan 999 add ports 12 tagged
  configure vlan 999 add ports 1 (untagged - by default)

If I'm not 100% correct with getting the idea at the moment, you can easily modify these commands to get your intended result.
I'd recommend you have a look at EXOS Command Reference Guide any time you need to understand the command beyond what a question mark in the CLI tells you, and EXOS User Guide whenever you want to read entire chapter on how a certain feature works and how to configure it step by step. These can be found here and you can use top-right dropdown to select your EXOS firmware version: https://www.extremenetworks.com/support/documentation/extremexos-22-6/

Hope that helps,
Tomasz

Re: Trunk EXOS switch to a Cisco switch

gonzoessex — Mon, 06 May 2019 20:36:02 GMT

Hello,

I have configured what you said and put a workstation into port 1 on 172.16.1.20 and tried to ping 172.16.1.251 and it failed. I want to get the local LAN working before the trunk works.

Here is my config:

#
# Module vpex configuration.
#

#
# Module vlan configuration.
#
configure vlan default delete ports all
configure vr VR-Default delete ports 1-12
configure vr VR-Default add ports 1-12
configure vlan default delete ports 1,12
create vlan "VLAN100"
configure vlan VLAN100 tag 100
create vlan "VLAN_0999"
configure vlan VLAN_0999 tag 999
disable port 1
disable port 2
disable port 3
disable port 4
disable port 5
disable port 6
disable port 7
disable port 8
disable port 9
disable port 10
disable port 11
disable port 12
configure vlan Default add ports 2-11 untagged
configure vlan VLAN100 add ports 12 untagged
configure vlan VLAN_0999 add ports 12 tagged
configure vlan VLAN_0999 add ports 1 untagged
configure vlan VLAN100 ipaddress 172.16.1.251 255.255.255.0

#
# Module mcmgr configuration.
#

Re: Trunk EXOS switch to a Cisco switch

Tomasz — Mon, 06 May 2019 20:42:09 GMT

Hello,

for that to be working (pinging VLAN 100 IP address) you have to have the workstation on port 1 in that VLAN. I wasn't sure what kind of a workstation is that.
What you could do right now:

code:

configure vlan 999 delete ports 1
configure vlan 100 add port 1

There is also an option to only issue the second command if you had auto-move feature for untagged ports enabled (this can be checked with "show vlan" and modified with "configure vlan untagged-ports auto-move").

Hope that helps,
Tomasz

Re: Trunk EXOS switch to a Cisco switch

gonzoessex — Tue, 07 May 2019 01:08:10 GMT

Thanks, I'm now onto the trunk to the Cisco switch. On the trunk port on the extreme what show trunk commands are there to see the state of it please as it seems the trunk is not working?

I've configured the Cisco side like I normally do on dot1q and set the native vlan to 999 and allowed all vlans.

On the extreme it's not so easy to see like a Cisco switch lays it out:

configure vlan default delete ports all
configure vr VR-Default delete ports 1-12
configure vr VR-Default add ports 1-12
configure vlan default delete ports 1,12
create vlan "VLAN100"
configure vlan VLAN100 tag 100
create vlan "VLAN_0999"
configure vlan VLAN_0999 tag 999
configure vlan Default add ports 2-11 untagged
configure vlan VLAN100 add ports 1,12 untagged
configure vlan VLAN_0999 add ports 12 tagged
configure vlan VLAN100 ipaddress 172.16.1.251 255.255.255.0

The workstation on the extreme (port 1) can ping vlan 100 now which is good.

Re: Trunk EXOS switch to a Cisco switch

Tomasz — Tue, 07 May 2019 01:23:42 GMT

Yeah, the CLI is totally different but once you get used to it, it's really convenient.
On Extreme you don't allow all, you have to explicitly configure VLANs to be contained within a port, either tagged or (just one of them, like Native VLAN) untagged. For any interswitch communication and trunking I'd recommend to do ports tagged in all necessary VLANs while leaving untagged ports in VLANs only for end systems like PCs and so on.
To see things I'd recommend to begin with:

code:

show vlan
show vlan [name or id]
show ports [port list] information detail
show ports [port list] vlan (since couple of fw releases)
show ports [port list] (optionally with 'no-refresh', try and see the difference, that keyword gives you one-shot and normal show ports by default will refresh every second)
show fdb

Those are the most basic commands to understand how your VLANs and ports are configured besides just doing config output (like show config | grep vlan).

You can also enable CDP on EXOS BTW if you wish. STP can be also set with PVST+ encapsulation for interswitch ports (that's a per port config).

If you wish we could establish some 1h session on Thursday or Friday to sort some things out live.

Hope that helps,
Tomasz

Re: Trunk EXOS switch to a Cisco switch

EtherMAN — Tue, 07 May 2019 01:30:22 GMT

Let me see if I can help translate IOS to EXOS for vlans.. If you think of vlans as the standard is written Tagged means you add a tag id to a vlan that can be trunked across a switch port. So all vlans to be trunked must be created with the appropriate tag ID and then the vlans needing to be trunked to another switch or device must be added tagged to the interface that connects the devices together...

Untagged is the same as a native vlan .. you can only have on untagged vlan per port just like you can only have one native vlan per port.. Pretty simple if you thing about it... Untagged means the vlan id is removed from the header and now it is a plain ethernet frame .. Native vlan is just a vlan that has had the tag id removed.

In your case if you want the PC to be part of the 172.16.1.0/24 broadcast domain you must untag vlan 100 on the port the work station is on... If you want the workstation to be on your native vlan 999 then 999 must be untagged on the workstation port on the Extreme switch...

Re: Trunk EXOS switch to a Cisco switch

gonzoessex — Tue, 07 May 2019 01:38:25 GMT

Thanks goes so my config looks wrong based on your descriptions:

VLAN 999 (Native) needs to be untagged on port 12 (trunk), and VLAN 100 tagged on ports 1 (workstation) and Port 12 Trunk?

# Module vlan configuration.
#
configure vlan default delete ports all
configure vr VR-Default delete ports 1-12
configure vr VR-Default add ports 1-12
configure vlan default delete ports 1,12
create vlan "VLAN100"
configure vlan VLAN100 tag 100
create vlan "VLAN_0999"
configure vlan VLAN_0999 tag 999
configure vlan Default add ports 2-11 untagged
configure vlan VLAN100 add ports 1,12 untagged
configure vlan VLAN_0999 add ports 12 untagged
configure vlan VLAN100 ipaddress 172.16.1.251 255.255.255.0

Re: Trunk EXOS switch to a Cisco switch

EtherMAN — Tue, 07 May 2019 01:49:39 GMT

you are correct. If there is no reason for you to have your native vlan on the Extreme switch you do not have to even create it. It is not recommended to have untagged vlans on a trunk port ....

Re: Trunk EXOS switch to a Cisco switch

gonzoessex — Tue, 07 May 2019 02:16:04 GMT

Normally I set the native vlan on the Cisco side:

code:

interface GigabitEthernet3/3
 switchport trunk encapsulation dot1q
 switchport trunk native vlan 999
 switchport mode trunk
 media-type rj45
 negotiation auto

Extreme (tagged all on the trunk like you suggested)

code:

configure vlan default delete ports all
configure vr VR-Default delete ports 1-12
configure vr VR-Default add ports 1-12
configure vlan default delete ports 1,12
create vlan "VLAN100"
configure vlan VLAN100 tag 100
create vlan "VLAN_0999"
configure vlan VLAN_0999 tag 999
configure vlan Default add ports 2-11 untagged
configure vlan VLAN100 add ports 12 tagged
configure vlan VLAN100 add ports 1 untagged
configure vlan VLAN_0999 add ports 12 tagged
configure vlan VLAN100 ipaddress 172.16.1.251 255.255.255.0

Attempt to ping the Cisco switch:

code:

* Extreme-SW1.19 # ping 172.16.1.250
Ping(ICMP) 172.16.1.250: 4 packets, 8 data bytes, interval 1 second(s).
Request timed out
Request timed out
Request timed out
Request timed out

code:

* Extreme-SW1.21 # sh vlan 100

VLAN 100: sh vlan VLAN100
VLAN Interface with name VLAN100 created by user
  Admin State:     Enabled   Tagging:  802.1Q Tag 100
  Description:     None
  Virtual router:   VR-Default
  IPv4 Forwarding:   Disabled
  IPv4 MC Forwarding: Disabled
  Primary IP:     172.16.1.251/24
  IPv6 Forwarding:   Disabled
  IPv6 MC Forwarding: Disabled
  IPv6:        None
  STPD:        None
  Protocol:      Match all unfiltered protocols
  Loopback:      Disabled
  NetLogin:      Disabled
  OpenFlow:      Disabled
  QosProfile:     None configured
  Egress Rate Limit Designated Port: None configured
  Flood Rate Limit QosProfile:    None configured
  Suppress ARP:    Disabled
  Proxy ARP:      Entry required
  Ports:  2.      (Number of active ports=2)
    Untag:   *1
    Tag:    *12

From the Cisco switch it can see the Extreme ok:

code:

Switch#sh cdp ne det
-------------------------
Device ID: Extreme-SW1
Entry address(es):
  IP address: 172.16.1.251
Platform: EXOS-VM,  Capabilities: Switch
Interface: GigabitEthernet3/3,  Port ID (outgoing port): Slot:  1, Port: 12
Holdtime : 159 sec

From the Extreme

code:

Extreme-SW1.20 # show cdp neighbor


Extreme-SW1.21 #

Re: Trunk EXOS switch to a Cisco switch

Tomasz — Tue, 07 May 2019 03:02:26 GMT

On Extreme you got IP address on a VLAN 100, for that I suppose you have to configure GigabitEthernet3/3 with trunk allowed vlan 100?
What is your output on EXOS with 'show cdp'?

How is your IP address configured on Cisco? Is it in interface vlan 100?

Re: Trunk EXOS switch to a Cisco switch

gonzoessex — Tue, 07 May 2019 03:04:09 GMT

Already added that, but same issue.

Re: Trunk EXOS switch to a Cisco switch

Tomasz — Tue, 07 May 2019 03:08:17 GMT

Hmm.. please try 'show fdb port 12' and you will see in what VLAN you see a MAC adress of a Cisco switch. If it's in VLAN 100, it should be there with VLAN 100 mentioned if you wish to see both of them in 100.

Re: Trunk EXOS switch to a Cisco switch

gonzoessex — Tue, 07 May 2019 03:14:02 GMT

Interesting:

code:

Extreme-SW1.22 # show fdb port 12
MAC                                      VLAN Name( Tag)  Age  Flags          Port / Virtual Port List
------------------------------------------------------------------------------------------------------


Flags : d - Dynamic, s - Static, p - Permanent, n - NetLogin, m - MAC, i - IP,
        x - IPX, l - lockdown MAC, L - lockdown-timeout MAC, M- Mirror, B - Egress Blackhole,
        b - Ingress Blackhole, v - MAC-Based VLAN, P - Private VLAN, T - VLAN translation,
        D - drop packet, h - Hardware Aging, o - IEEE 802.1ah Backbone MAC,
        S - Software Controlled Deletion, r - MSRP,
        X - VXLAN, Z - OpenFlow, E - EVPN


Total: 0 Static: 0  Perm: 0  Dyn: 0  Dropped: 0  Locked: 0  Locked with Timeout: 0
FDB Aging time: 300
Extreme-SW1.23 #

code:

Extreme-SW1.23 # sh port 12
Port Summary Monitor                      Mon May  6 20:14:21 2019
Port     Display              VLAN Name           Port  Link  Speed  Duplex
#        String               (or # VLANs)        State State Actual Actual
========================================================================
12                            (0002)              E     A     100    FULL

Re: Trunk EXOS switch to a Cisco switch

Tomasz — Tue, 07 May 2019 03:18:36 GMT

Could you show us from Cisco running config how is the IP address on it configured at the moment?

BTW 'show fdb' command also lets you to display just per-vlan forwarding database ('show fdb vlan ').

Re: Trunk EXOS switch to a Cisco switch

gonzoessex — Tue, 07 May 2019 03:24:30 GMT

There's not much to it on Cisco:

code:

interface GigabitEthernet3/3
 switchport trunk allowed vlan 100,999
 switchport trunk encapsulation dot1q
 switchport trunk native vlan 999
 switchport mode trunk
 media-type rj45
 duplex full
 no negotiation auto
!
interface Vlan100
 ip address 172.16.1.250 255.255.255.0
!
ip forward-protocol nd

Re: Trunk EXOS switch to a Cisco switch

gonzoessex — Tue, 07 May 2019 03:26:08 GMT

Just rebooted the Extreme switch:

Bingo (bug?)

code:

Extreme-SW1.2 # sh fdb
MAC                                      VLAN Name( Tag)  Age  Flags          Port / Virtual Port List
------------------------------------------------------------------------------------------------------
0c:8e:73:ec:32:0f                          VLAN100(0100) 0071  d m            12
0c:8e:73:ec:32:0f                        VLAN_0999(0999) 0071  d m            12


Flags : d - Dynamic, s - Static, p - Permanent, n - NetLogin, m - MAC, i - IP,
        x - IPX, l - lockdown MAC, L - lockdown-timeout MAC, M- Mirror, B - Egress Blackhole,
        b - Ingress Blackhole, v - MAC-Based VLAN, P - Private VLAN, T - VLAN translation,
        D - drop packet, h - Hardware Aging, o - IEEE 802.1ah Backbone MAC,
        S - Software Controlled Deletion, r - MSRP,
        X - VXLAN, Z - OpenFlow, E - EVPN


Total: 2 Static: 0  Perm: 0  Dyn: 2  Dropped: 0  Locked: 0  Locked with Timeout: 0
FDB Aging time: 300
Extreme-SW1.2 # ping 172.16.1.250
Ping(ICMP) 172.16.1.250: 4 packets, 8 data bytes, interval 1 second(s).
16 bytes from 172.16.1.250: icmp_seq=0 ttl=255 time=46 ms
16 bytes from 172.16.1.250: icmp_seq=1 ttl=255 time=9.649 ms
16 bytes from 172.16.1.250: icmp_seq=2 ttl=255 time=38 ms
16 bytes from 172.16.1.250: icmp_seq=3 ttl=255 time=21 ms


--- 172.16.1.250 ping statistics ---
4 packets transmitted, 4 packets received, 0% loss
round-trip min/avg/max = 9/28/46 ms
Extreme-SW1.3 #

Re: Trunk EXOS switch to a Cisco switch

Tomasz — Tue, 07 May 2019 03:27:35 GMT

Oh, works now. 🙂
Please post us the version you are running from the output of 'show version'. Then it might become clear if it was kind of a bug or other uncommon behavior.

Re: Trunk EXOS switch to a Cisco switch

gonzoessex — Tue, 07 May 2019 04:56:58 GMT

Image : ExtremeXOS version 22.5.1.7