Quanta LB6M (10GbE) -- Discussion

artlessknave

New Member
Mar 16, 2017
13
2
3
36
Hello,

I'im trying to figure out how to trunk catalyst 2960g to lb6m. I have the ports physically connected like this:
lb6m cisco
0/25 = Gi0/41
0/26 = Gi0/42
0/27 = Gi0/43
0/28 = Gi0/44

where 26-28 are in 1/1 and 42-44 are in Po1, while 25 and 41 are is normal
i want the etherchannel to have all 4 ports and do nothing but connect the quanta to the cisco in the exact same way port 25 currently is doing ( i have 25 separate so i can have things work while muck about with the aggregation), however I cannot find anything that helps me figure out why it doesnt work when I enable the trunked ports.
it LOOKS like the trunk is right, but then...things dont work. i suspect my extremely limited understanding is either missing a key component or what i want is just not possible.

I thought I had it partially working where I could ping by IP but not hostname, however, that doesnt work now and I suspect it only seemed to work because I had other interfaces connected elsewhere.

I started this project with pretty much zero knowledge and while im getting pretty good at reconfiguring things through sheer repetition....not getting anywhere is frustrating

any ideas that at least point me in a useful direction would be much appreciated.
both configs are attached.

edit: Note that i have the trunk shutdown on the lb6m due to it not working (and the lb6m not having to reset and disconnect everything when i modify ports which the cisco seems to do), and the cisco will disable more than one port that connects to the same network aka the lb6m. thats not part of the problem
 

Attachments

Last edited:

Terry Kennedy

Well-Known Member
Jun 25, 2015
1,118
569
113
New York City
www.glaver.org
any ideas that at least point me in a useful direction would be much appreciated.
both configs are attached.
On your 2960 you have both "switchport access vlan 10" and "switchport mode trunk". Here's what I have on a 4948:
Code:
interface Port-channel1
description Trunk to PowerConnect 8024
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
!
interface TenGigabitEthernet1/49
description Trunk to PowerConnect 8024 1/2
switchport trunk encapsulation dot1q
switchport mode trunk
channel-protocol lacp
channel-group 1 mode active
!
interface TenGigabitEthernet1/50
description Trunk to PowerConnect 8024 2/2
switchport trunk encapsulation dot1q
switchport mode trunk
channel-protocol lacp
channel-group 1 mode active
On your LB6M, you have the ports in shutdown. On the Dell PowerConnect 8024 (also runs FASTPATH Routing, but may not use the same syntax as the LB6M):
Code:
interface Te1/0/23
channel-group 1 mode active
description "Trunk to Catalyst 4948-10GE 1/2"
switchport mode trunk
switchport general acceptable-frame-type tagged-only
exit
!
interface Te1/0/24
channel-group 1 mode active
description "Trunk to Catalyst 4948-10GE 2/2"
switchport mode trunk
switchport general acceptable-frame-type tagged-only
exit
!
interface port-channel 1
description "Trunk to Catalyst 4948-10GE"
switchport mode trunk
switchport general acceptable-frame-type tagged-only
exit
If you want to limit the trunk to a specific subset of VLANs on the Cisco side, you'd use:
Code:
switchport trunk allowed vlan x[,y...]
I'm not sure what the equivalent on the LB6M side is.
 

artlessknave

New Member
Mar 16, 2017
13
2
3
36
On your 2960 you have both "switchport access vlan 10" and "switchport mode trunk". Here's what I have on a 4948:
Code:
interface Port-channel1
description Trunk to PowerConnect 8024
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
!
interface TenGigabitEthernet1/49
description Trunk to PowerConnect 8024 1/2
switchport trunk encapsulation dot1q
switchport mode trunk
channel-protocol lacp
channel-group 1 mode active
!
interface TenGigabitEthernet1/50
description Trunk to PowerConnect 8024 2/2
switchport trunk encapsulation dot1q
switchport mode trunk
channel-protocol lacp
channel-group 1 mode active
On your LB6M, you have the ports in shutdown. On the Dell PowerConnect 8024 (also runs FASTPATH Routing, but may not use the same syntax as the LB6M):
Code:
interface Te1/0/23
channel-group 1 mode active
description "Trunk to Catalyst 4948-10GE 1/2"
switchport mode trunk
switchport general acceptable-frame-type tagged-only
exit
!
interface Te1/0/24
channel-group 1 mode active
description "Trunk to Catalyst 4948-10GE 2/2"
switchport mode trunk
switchport general acceptable-frame-type tagged-only
exit
!
interface port-channel 1
description "Trunk to Catalyst 4948-10GE"
switchport mode trunk
switchport general acceptable-frame-type tagged-only
exit
If you want to limit the trunk to a specific subset of VLANs on the Cisco side, you'd use:
Code:
switchport trunk allowed vlan x[,y...]
I'm not sure what the equivalent on the LB6M side is.


oops, forgot to mention, i have the trunk shutdown on the lb6m due to it not working (and the lb6m not having to reset and disconnect everything when i modify ports which the cisco seems to do), and the cisco will disable more than one port that connects to the same network aka the lb6m. thats not part of the problem

i was under the impression that the trunk ports had to be in a separate vlan, but if i understand this config that doesnt seem to be the case

i think i get what this does
channel-protocol lacp

but far less sure what purpose this serves
switchport trunk encapsulation dot1q
 

Terry Kennedy

Well-Known Member
Jun 25, 2015
1,118
569
113
New York City
www.glaver.org
i think i get what this does
channel-protocol lacp
There are several ways to bundle ports together. LACP is the industry-standard way of doing this, which both switches support. PAGP is an older version, proprietary to Cisco. Some switches also support "on", which means "don't negotiate anything, just assume the other switch is doing the same thing".
but far less sure what purpose this serves
switchport trunk encapsulation dot1q
Likewise, there are a number of ways of tagging packets with VLAN IDs. ISL (inter-switch link) is an older method. Some switches also support "encapsulation negotiate" which means "use whatever mode the other switch used to send packets to me".
 

alex1002

Member
Apr 9, 2013
519
19
18
At least on an unrelated device (Dell PowerConnect 8024) running FASTPATH Routing, "ip igmp snooping" is on by default and doesn't show in the config. You can turn it off with "no ip igmp snooping [vlan xx]" (where [vlan xx] is the optional VLAN number to apply it to). You can display the status with "show ip igmp snooping".
Doesn't seem to be working. Multicast fails in vsan.
(FASTPATH Routing) #show igmpsnooping

Admin Mode..................................... Disable
Multicast Control Frame Count.................. 0
IGMP Router-Alert check........................ Disabled
Interfaces Enabled for IGMP Snooping........... None
VLANs enabled for IGMP snooping................ None




Sent from my iPhone using Tapatalk
 

Terry Kennedy

Well-Known Member
Jun 25, 2015
1,118
569
113
New York City
www.glaver.org
Doesn't seem to be working. Multicast fails in vsan.
(FASTPATH Routing) #show igmpsnooping

Admin Mode..................................... Disable
Multicast Control Frame Count.................. 0
IGMP Router-Alert check........................ Disabled
Interfaces Enabled for IGMP Snooping........... None
VLANs enabled for IGMP snooping................ None
IGMP should work with or without snooping - all snooping does is enable the switch to learn which ports are interested in multicast streams, instead of flooding them to all ports.
 

alex1002

Member
Apr 9, 2013
519
19
18
IGMP should work with or without snooping - all snooping does is enable the switch to learn which ports are interested in multicast streams, instead of flooding them to all ports.
VMware vsan require multicast and can't get it to work with this switch. I really need some help on this.


Sent from my iPhone using Tapatalk
 

HyperNet

New Member
Mar 19, 2017
5
0
1
This thing is LOUD. too loud for a home switch, even in my basement.
...
The 3 fans at the back, I have a problem. I read here that people put 4000rpm spinners, but I don't see how that could be enough airflow without frying things. I am with Jonathan/jmoll that putting 120mm fans seems to be the best way to keep airflow going with less noise.
...
I am guessing everyone else is living with the noise.
NOT! ;)

The standard fans are rated at 24 CFM at full speed. This switch was designed so that one fan could fail and it would still operate within acceptable thermal criteria.

I did extensive searches on DigiKey for 40MM 12V fans that were quiet and none of them had a high enough CFM rating. NONE. I'm not will to risk premature HW failure so for me the 120MM option was the only one.

I call it "The 2U Stacker" ;) (Don't laugh at the color, they were on sale a while back and sitting on a shelf)
These push out 75 CFM but are DEAD QUIET! My temp went from 45C with the standard fans to 41C with this setup. Dual stack for hw redundancy.

I used a nibbler tool to cut the inner hole in the top case and placed it right over the Broadcom chip/heatsink.

FanStack.JPG

You connect the 3 wire connectors onto the 4 wire headers, with the black wire to the right, using the 3 header pins on the right.

As you can see, "show env" will report the fans operational with speeds and duty cycle so you'll still get traps if one fails.

FanEnv.JPG
 
Last edited:

HyperNet

New Member
Mar 19, 2017
5
0
1
Next I'm going to place a 120 MM fan in front of the power supplies and have a cardboard guide directing airflow right into their ends so those fans can be replaced with whisper quiet low CFM fans.
 

Kartoff

New Member
Feb 17, 2017
22
5
3
44
Guys, i saw that one of the most commented thematics are about fans... I was very concerned after reading how loud are these switches...
But now i can clearly say that i can take a breath because all 4 switches that arived are ok :) LB6M have 3 fans and LB8 have 4 but now they are in same room as my PC and all are working and i can stay here all day :) Maybe if i put more load to them they will become more louder but now they are not... In the matter of fact i can say even that they are quiet now... They randomly increase fan RPM time to time but for few seconds so its not a big deal...

Just my 2 cents :)
 

jdowning

New Member
Mar 19, 2017
1
0
1
120
I have two servers hooked up to my switch. When I try to ping the switch's management IP (192.168.100.2) from either server, I get not response. The # of packets sent ticks up on their switch port when pings are attempted, so I know its traveling through the right interface on the server to the switch. The switch also cannot ping either server IP. Both servers are on ports 0/1 and 0/3 respectively and their interfaces are tagged with VLAN 10 and static IPs are set.

My configuration is below. I just wiped and re-setup the switch with this simpler config, hoping that it was something over-complicated in my prior config. No dice, however. I'm sure I'm missing something simple, hoping you folks can help me out.

Code:
!Current Configuration:

!

!System Description "Quanta LB6M, 1.2.0.18, Linux 2.6.21.7"

!System Software Version "1.2.0.18"

!System Up Time          "0 days 1 hrs 33 mins 30 secs"

!Additional Packages     FASTPATH QOS

!Current SNTP Synchronized Time: Not Synchronized

!

network protocol none

network parms 192.168.1.4 255.255.255.0 192.168.1.1

vlan database

vlan 10,30,40

vlan routing 10 10

vlan routing 30 30

vlan routing 40 40

exit

ip ssh server enable

configure

username "******" password ******* level 1 encrypted

aaa authentication enable "enableList" enable

line console

exit

line telnet

exit

line ssh

exit

spanning-tree configuration name "spanprimary"

port-channel name 1/1 1gbLAN

interface 0/25

addport 1/1

exit

interface 0/26

addport 1/1

exit

interface 0/27

addport 1/1

exit

interface 0/28

addport 1/1

exit

!

interface 0/1

vlan pvid 10

vlan participation include 10,30,40

exit

interface 0/2

exit

interface 0/3

vlan pvid 10

vlan participation include 10,30,40

exit

interface 0/4

exit

interface 0/5

vlan pvid 10

vlan participation include 10,30,40

exit

interface 0/6

exit

interface 0/7

exit

interface 0/8

exit

interface 0/9

exit

interface 0/10

exit

interface 0/11

exit

interface 0/12

exit

interface 0/13

exit

interface 0/14

exit

interface 0/15

exit

interface 0/16

exit

interface 0/17

exit

interface 0/18

exit

interface 0/19

exit

interface 0/20

exit

interface 0/21

exit

interface 0/22

exit

interface 0/23

exit

interface 0/24

exit

interface 0/25

exit

interface 0/26

exit

interface 0/27

exit

interface 0/28

exit

interface 1/1

vlan participation include 10,30,40

exit

interface 1/2

exit

interface 1/3

exit

interface 1/4

exit

interface 1/5

exit

interface 1/6

exit

interface 1/7

exit

interface 1/8

exit

interface 1/9

exit

interface 1/10

exit

interface 1/11

exit

interface 1/12

exit

interface 1/13

exit

interface 1/14

exit

interface 1/15

exit

interface 1/16

exit

interface 1/17

exit

interface 1/18

exit

interface 1/19

exit

interface 1/20

exit

interface 1/21

exit

interface 1/22

exit

interface 1/23

exit

interface 1/24

exit

interface 1/25

exit

interface 1/26

exit

interface 1/27

exit

interface 1/28

exit

interface 1/29

exit

interface 1/30

exit

interface 1/31

exit

interface 1/32

exit

interface 1/33

exit

interface 1/34

exit

interface 1/35

exit

interface 1/36

exit

interface 1/37

exit

interface 1/38

exit

interface 1/39

exit

interface 1/40

exit

interface 1/41

exit

interface 1/42

exit

interface 1/43

exit

interface 1/44

exit

interface 1/45

exit

interface 1/46

exit

interface 1/47

exit

interface 1/48

exit

interface 1/49

exit

interface 1/50

exit

interface 1/51

exit

interface 1/52

exit

interface 1/53

exit

interface 1/54

exit

interface 1/55

exit

interface 1/56

exit

interface 1/57

exit

interface 1/58

exit

interface 1/59

exit

interface 1/60

exit

interface 1/61

exit

interface 1/62

exit

interface 1/63

exit

interface 1/64

exit

interface 2/10

routing

ip address 192.168.100.4 255.255.255.0

exit

interface 2/30

routing

ip address 192.168.30.4 255.255.255.0

exit

interface 2/40

routing

ip address 192.168.40.4 255.255.255.0

exit

router rip

exit

router ospf

exit

exit
 

RADCOM

New Member
Aug 27, 2012
11
4
3
I have long been a watercooling/PC modder. Loving the posts on the fan modding. Why not use a 140mm or 200mm fan I'm thinking[emoji4] I gave a 3d printer so hypernet I can make your cardboard guide from plastic perhaps.

Sent from my SM-N9005 using Tapatalk
 

Drewy

Active Member
Apr 23, 2016
207
55
28
52
Mmmm I'm not convinced that I did anything. I played with Observium a while back and got it to connect pretty quickly.
From Observium: skip ping, protocol v2c, transport udp, port 161, SNMP community (password) public (I think).
 
  • Like
Reactions: fvanlint