Trunk issues

[KMNRuser]

We are in the process of replacing a legacy Juniper Core switch with a 2 stack Cisco 9300 configuration.

The VM Hosts within the environment are all configured in the current Vlan 1 on the Juniper switch.

We are trunking to these hosts.

We have the following configuration on the majority of these ports:

interface TwentyFiveGigE1/0/13

     description "Hostname Rack number Port number

     switchport trunk allowed vlan 1,3,6,22,80,254,255

     switchport mode trunk

We ran into issues wherein after the physical connections were moved, we were unable to ping these hosts in vlan 1.  

I am curious if in fact that by using the "allowed" command, is it possibly tagging vlan1, vs. if we simply did not use the "allowed" command, and let the port natively trunk all the vlans by default, which in that scenario does not tag the native vlan, could that possibly be causing the issue?

We do not route on the switch.  The routing takes place on the Firewall uplink.

We do have a Management IP on another vlan to access the switch.

Thank you for any input or feedback.

Sincerely,

Kevin

[amikat]

Hi,

To my knowledge there is no default trunk native vlan at Juniper (contrary to Cisco) so perhaps you may consider to configure Vlan 1 as tagged at Cat9300 trunk and check if there is any progress.

Best regards,

Antonin

[KMNRuser]

Hi Amikat,

What you are indicating seems to match what MHM has indicated.  We will try to do that on all links but the uplink to the Cisco Firewall which is where the gateway is.

[Hamed Fazel]

Hi @KMNRuser 

as far as I understand you have multiple links to the VMS. 

can you provide some more information by the output of these commands:

show spanning-tree vlan

show interface TwentyFiveGigE1/0/13 switchport