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".
On your 2960 you have both "switchport access vlan 10" and "switchport mode trunk". Here's what I have on a 4948:
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 activeinterface 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
exitswitchport trunk allowed vlan x[,y...]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".
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".
Doesn't seem to be working. Multicast fails in vsan.
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.
NOT!
(Don't laugh at the color, they were on sale a while back and sitting on a shelf)
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...!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
