1 Rookie

 • 

16 Posts

January 22nd, 2011 22:00

Can you put interface's 1/g21 - 1/g24 with a MTU of 9216 as well as the 'port-channel 1' interface?

909 Posts

January 24th, 2011 12:00

Port 19 and 20 and in general mode.   You have set the vlan of this port to 30 untagged.  This sets the port to transmit vlan 30 packets untagged.  You did not set the PVID.   The PVID tells the switch how to classify untagged packets received on this port.   Since you did not set it, untagged packets received on this port are put in vlan 1.

2 different ways to fix this:

- set ports 19 and 20 to access mode in vlan 30

switchport mode access

switchport access vlan 30

- Or leave them in general mode but set the pvid by adding this to the port configuration:

switchport general pvid 30

 

6 Posts

January 24th, 2011 12:00

I set 21-24 mtu 9216 but no change.

If I plug my laptop (10.10.10.55) in #19 on switch 2 I can ping all the other vlan 10 IPs.

 

If I set it to 172.30.1.55 I can only ping 172.30.1.28 that exists on the same switch. I cannot ping 172.30.1.27. It seems that the only VLAN being trunked is VLAN 10.

10 Posts

January 24th, 2011 13:00

Setting the PVID on the interfaces isn't enough. You should also tag the VLANs on the trunk:

interface port-channel 1
spanning-tree portfast
switchport mode trunk
switchport trunk allowed vlan add 10,30 tagged
mtu 9216
exit


best regards

nrls24

6 Posts

January 24th, 2011 14:00

Hi nrls24,

switchport trunk allowed vlan add 10,30 tagged

isn't a valid command. It won't let me add tagged to the end.

6 Posts

January 24th, 2011 14:00

I tried

switchport general pvid 30    - can ping IP on same switch only.

Then I tried:

interface range ethernet 1/g19-1/g20

switchport mode access

switchport access vlan 30

- I cannot even ping 172.30.1.28 from 172.30.1.55 on the same switch, ports 19 & 20.

I think I must be missing something else. I thought that vlan1 was not trunked by default. Is my vlan10 actually thinking it is vlan1 then?

909 Posts

January 25th, 2011 12:00

Some definitions for PowerConnect switchport mode:

trunk: all packets transmitted are tagged.  untagged received traffic is dropped.  tagged received traffic is dropped if it is not tagged in one of the member vlans. 

access: all packets are tranmitted untagged.  untagged received traffic is accepted and switched in the ports define vlan.  tagged received traffic is dropped.

general: can be configured to trasmit tagged or untagged traffic per vlan.  untagged received traffic is accepted and switch in th defined PVID.  tagged received traffic is dropped if it is not in one of the ported tagged vlans.

So this:

switchport mode access

switchport access vlan 99

Is equivalent to this:

switchport mode general

switchport general allowed vlan add 99 untagged

switchport general pvid 99

And this:

switchport mode trunk

switchport trunk allowed vlan add 99,100

Is equivalent to:

switchport mode general

switchport general allowed vlan add 99,110 tagged

switchport general pvid 4095                      (this is the drop vlan)

 

10 Posts

January 25th, 2011 14:00

Hi wdtech,

just try this:

 

!Current Configuration:
!System Description "Powerconnect 6224, 3.2.0.7, VxWorks 6.5"
!System Software Version 3.2.0.7
!Cut-through mode is configured as disabled
!
configure
vlan database
vlan 10,30
exit
snmp-server location dell_rack
hostname sw1
stack
member 1 1
exit
ip address 192.168.1.3 255.255.255.0
ip default-gateway 192.168.1.1
username admin password xxxxxxxxxxxxxxxxxxxxxxxx level 15 encrypted
!
interface ethernet 1/g7
mtu 9216
spanning-tree portfast
switchport access vlan 10
exit
!
interface ethernet 1/g8
mtu 9216
spanning-tree portfast
switchport access vlan 10
exit
!
interface ethernet 1/g9
mtu 9216
spanning-tree portfast
switchport access vlan 10
exit
!
interface ethernet 1/g10
mtu 9216
spanning-tree portfast
switchport access vlan 10
exit
!
interface ethernet 1/g11
mtu 9216
spanning-tree portfast
switchport access vlan 10
exit
!
interface ethernet 1/g12

mtu 9216
spanning-tree portfast
switchport access vlan 10
exit
!
interface ethernet 1/g13
mtu 9216
spanning-tree portfast
switchport access vlan 10
exit
!
interface ethernet 1/g14
mtu 9216
spanning-tree portfast
switchport access vlan 10
exit
!
interface ethernet 1/g19
mtu 9216
spanning-tree portfast
switchport access vlan 30
exit
!
interface ethernet 1/g20
mtu 9216
spanning-tree portfast
switchport access vlan 30
exit
!
interface ethernet 1/g21
channel-group 1 mode on
exit
!
interface ethernet 1/g22
channel-group 1 mode on
exit
!
interface ethernet 1/g23
channel-group 1 mode on
exit
!
interface ethernet 1/g24
channel-group 1 mode on
exit
!
interface port-channel 1
switchport mode trunk
switchport trunk allowed vlan add 10,30
mtu 9216
exit
exit

 

or

 

interface port-channel 1
switchport mode general
switchport
general allowed vlan add 10,30 tagged
mtu 9216
exit
exit

10 Posts

January 25th, 2011 14:00

Hi wdtech,

sorry,  the keyword tagged is only needed when the port is in general mode. This part of the configuration is o.k. 

So it should work, when you set your ports in access mode.

best regards

nrls24

 

6 Posts

January 27th, 2011 23:00

Hi wdtech,

just try this:

 

!Current Configuration:
!System Description "Powerconnect 6224, 3.2.0.7, VxWorks 6.5"
!System Software Version 3.2.0.7
!Cut-through mode is configured as disabled
!
configure
.

.

.

 

Thanks! I'll try tomorrow when I get back to the office.

6 Posts

January 28th, 2011 17:00

nrls24,

I tried both, both prevent me pinging either vlan10 or vlan30 across the LAG.

Thanks for the suggestions though.

April 29th, 2011 10:00

Hey - I was running into the same issues but was able to solve by tagging the iSCSI VLAN (in my case VLAN 10)

1.) Switching->VLAN->LAG Settings:  Port VLAN Mode = 'General' and assigning a PVID of 1 (in my case I wanted to tag traffic for the default VLAN).

2.)  in the Switching->VLAN->VLAN Membership: add the desired VLAN (ex. VLAN 10 for iSCSI) to the LAG as tagged 'T'

I can now ping across the LAG group..

I'm still fumbling my way through the switch configuration but maybe this will help you and/or somebody else down the road..

 

 

2 Posts

May 4th, 2011 19:00

I was wondering if anyone was able to get this to work?

I'm facing the same challenge on my network

Could you post the working configuration?

I've been in contact with Dell support and I was not able to get this working - I'm desperate now because this ISCSi has to be up and working by morning:<(

 

Thanks

1 Message

August 27th, 2016 11:00

Your Ip addresses between the switches is on VLAN 1 and in order for you to ping them will be to have a layer 3 device

No Events found!

Top