I'm changing the layer 3 interfaces to layer 2 and even though I have removed the IP addresses from the VLAN interfaces, the switch will not remove the "vlan routing X" statements from the config.  The only thing that works if I completely delete the VLAN from the database.  Are there any other options?

Config:

!System Software Version 3.3.11.2

vlan database
vlan 30

vlan routing 1 1
vlan routing 30 5

interface vlan 30
name "vMotion"
exit

Error when removing the routing:

console(config-if-vlan30)#no routing

Could not get the internal interface number associated with the Unit-Slot-Port.

Am hitting this problem for the second time now that ports seem to lock up and am unable to revover them by shut/no shut. Only means to recover the ports seems to be
 through rebooting the switch. Clients are Dell and HP computers and no BPDU device known to have caused this although the port should be recoverable anyway.

Anyone know of this problem and what means to recover the ports ?

Re

Kjartan

Port     Type         Duplex  Speed Neg      ctrl State       Pressure Mode
-------- ------------ ------  ----- -------- ---- ----------- -------- -------
gi1/0/1  1G-Copper    Full    1000  Enabled  On   Up          Disabled Off    
gi1/0/2  1G-Copper    Full    1000  Enabled  On   Up          Disabled On     
gi1/0/3  1G-Copper    Full    1000  Enabled  On   Up          Disabled On     
gi1/0/4  1G-Copper    Full    1000  Enabled  On   Up          Disabled Off    
gi1/0/5  1G-Copper      --      --     --     --  Down*           --     --    
gi1/0/6  1G-Copper      --      --     --     --  Down*           --     --    
gi1/0/7  1G-Copper      --      --     --     --  Down*           --     --    
gi1/0/8  1G-Copper      --      --     --     --  Down*           --     --    
gi1/0/9  1G-Copper      --      --     --     --  Down*           --     --    
gi1/0/10 1G-Copper      --      --     --     --  Down           --     --    
gi1/0/11 1G-Copper    Full    1000  Enabled  On   Up          Disabled Off  

interface gigabitethernet1/0/5
 description PC-VLAN-244
 spanning-tree portfast
 spanning-tree guard root
 spanning-tree bpduguard enable
 switchport access vlan 244

       Unit             SW version         Boot version         HW version      
------------------- ------------------- ------------------- -------------------
         1               4.1.0.16            1.0.0.14            00.00.02      

Hello,

I have a question about our PowerConnect M8024-k ISCSI config. Currently we stacked both swithes but at our next maintenance window we are going to create an LAG. But for now I want to verify that our config is correct.

The switch is connected as followed:

Interface te1/0/1 to te1/0/9: blade servers
Interface te2/0/1 to te2/0/9: blade servers

Interface te1/0/17 to te1/0/20: 3x Equallogic
Interface te2/0/17 to te2/0/20: 3x Equallogic

Somehow it looks like it is not performing to the max, most times I get 1GB/s max when the EQLs are moving pages. Can someone have an quick look at our config and see if it is missing something?

Thanks in advance.

Kind regards.

The config:

!Current Configuration:
!System Description "PowerConnect M8024-k, 5.1.4.5, VxWorks 6.6"
!System Software Version 5.1.4.5
!Cut-through mode is configured as disabled
!System Operational Mode "Normal"
!
configure
no mode simple
slot 1/0 2    ! PCM8024-k
slot 2/0 2    ! PCM8024-k
sntp unicast client enable
sntp server *
clock summer-time recurring EU
clock timezone 1 minutes 0 zone "AMS"
stack
member 1 1    ! PCM8024-k
member 2 1    ! PCM8024-k
exit
interface out-of-band
ip address * 255.255.255.0 172.30.254.1
exit
boot auto-copy-sw
username "*" password * privilege 15 encrypted
no spanning-tree
!
interface Te1/0/1
mtu 9216
no lldp tlv-select dcbxp ets-config
no lldp tlv-select dcbxp ets-recommend
no lldp tlv-select dcbxp pfc
no lldp tlv-select dcbxp application-priority
exit
!
interface Te1/0/2
mtu 9216
no lldp tlv-select dcbxp ets-config
no lldp tlv-select dcbxp ets-recommend
no lldp tlv-select dcbxp pfc
no lldp tlv-select dcbxp application-priority
exit
!
interface Te1/0/3
mtu 9216
no lldp tlv-select dcbxp ets-config
no lldp tlv-select dcbxp ets-recommend
no lldp tlv-select dcbxp pfc
no lldp tlv-select dcbxp application-priority
exit
!
interface Te1/0/4
mtu 9216
no lldp tlv-select dcbxp ets-config
no lldp tlv-select dcbxp ets-recommend
no lldp tlv-select dcbxp pfc
no lldp tlv-select dcbxp application-priority
exit
!
interface Te1/0/5
mtu 9216
no lldp tlv-select dcbxp ets-config
no lldp tlv-select dcbxp ets-recommend
no lldp tlv-select dcbxp pfc
no lldp tlv-select dcbxp application-priority
exit
!
interface Te1/0/6
mtu 9216
no lldp tlv-select dcbxp ets-config
no lldp tlv-select dcbxp ets-recommend
no lldp tlv-select dcbxp pfc
no lldp tlv-select dcbxp application-priority
exit
!
interface Te1/0/7
mtu 9216
no lldp tlv-select dcbxp ets-config
no lldp tlv-select dcbxp ets-recommend
no lldp tlv-select dcbxp pfc
no lldp tlv-select dcbxp application-priority
exit
!
interface Te1/0/8
mtu 9216
no lldp tlv-select dcbxp ets-config
no lldp tlv-select dcbxp ets-recommend
no lldp tlv-select dcbxp pfc
no lldp tlv-select dcbxp application-priority
exit
!
interface Te1/0/9
mtu 9216
no lldp tlv-select dcbxp ets-config
no lldp tlv-select dcbxp ets-recommend
no lldp tlv-select dcbxp pfc
no lldp tlv-select dcbxp application-priority
exit
!
interface Te1/0/10
mtu 9216
no lldp tlv-select dcbxp ets-config
no lldp tlv-select dcbxp ets-recommend
no lldp tlv-select dcbxp pfc
no lldp tlv-select dcbxp application-priority
exit
!
interface Te1/0/11
mtu 9216
no lldp tlv-select dcbxp ets-config
no lldp tlv-select dcbxp ets-recommend
no lldp tlv-select dcbxp pfc
no lldp tlv-select dcbxp application-priority
exit
!
interface Te1/0/12
mtu 9216
no lldp tlv-select dcbxp ets-config
no lldp tlv-select dcbxp ets-recommend
no lldp tlv-select dcbxp pfc
no lldp tlv-select dcbxp application-priority
exit
!
interface Te1/0/13
mtu 9216
no lldp tlv-select dcbxp ets-config
no lldp tlv-select dcbxp ets-recommend
no lldp tlv-select dcbxp pfc
no lldp tlv-select dcbxp application-priority
exit
!
interface Te1/0/14
mtu 9216
no lldp tlv-select dcbxp ets-config
no lldp tlv-select dcbxp ets-recommend
no lldp tlv-select dcbxp pfc
no lldp tlv-select dcbxp application-priority
exit
!
interface Te1/0/15
mtu 9216
no lldp tlv-select dcbxp ets-config
no lldp tlv-select dcbxp ets-recommend
no lldp tlv-select dcbxp pfc
no lldp tlv-select dcbxp application-priority
exit
!
interface Te1/0/16
mtu 9216
no lldp tlv-select dcbxp ets-config
no lldp tlv-select dcbxp ets-recommend
no lldp tlv-select dcbxp pfc
no lldp tlv-select dcbxp application-priority
exit
!
interface Te1/0/17
mtu 9216
no lldp tlv-select dcbxp ets-config
no lldp tlv-select dcbxp ets-recommend
no lldp tlv-select dcbxp pfc
no lldp tlv-select dcbxp application-priority
exit
!
interface Te1/0/18
spanning-tree portfast
mtu 9216
no lldp tlv-select dcbxp ets-config
no lldp tlv-select dcbxp ets-recommend
no lldp tlv-select dcbxp pfc
no lldp tlv-select dcbxp application-priority
exit
!
interface Te1/0/19
spanning-tree portfast
mtu 9216
no lldp tlv-select dcbxp ets-config
no lldp tlv-select dcbxp ets-recommend
no lldp tlv-select dcbxp pfc
no lldp tlv-select dcbxp application-priority
exit
!
interface Te1/0/20
spanning-tree portfast
mtu 9216
no lldp tlv-select dcbxp ets-config
no lldp tlv-select dcbxp ets-recommend
no lldp tlv-select dcbxp pfc
no lldp tlv-select dcbxp application-priority
exit
!
interface Te2/0/1
mtu 9216
no lldp tlv-select dcbxp ets-config
no lldp tlv-select dcbxp ets-recommend
no lldp tlv-select dcbxp pfc
no lldp tlv-select dcbxp application-priority
exit
!
interface Te2/0/2
mtu 9216
no lldp tlv-select dcbxp ets-config
no lldp tlv-select dcbxp ets-recommend
no lldp tlv-select dcbxp pfc
no lldp tlv-select dcbxp application-priority
exit
!
interface Te2/0/3
mtu 9216
no lldp tlv-select dcbxp ets-config
no lldp tlv-select dcbxp ets-recommend
no lldp tlv-select dcbxp pfc
no lldp tlv-select dcbxp application-priority
exit
!
interface Te2/0/4
mtu 9216
no lldp tlv-select dcbxp ets-config
no lldp tlv-select dcbxp ets-recommend
no lldp tlv-select dcbxp pfc
no lldp tlv-select dcbxp application-priority
exit
!
interface Te2/0/5
mtu 9216
no lldp tlv-select dcbxp ets-config
no lldp tlv-select dcbxp ets-recommend
no lldp tlv-select dcbxp pfc
no lldp tlv-select dcbxp application-priority
exit
!
interface Te2/0/6
mtu 9216
no lldp tlv-select dcbxp ets-config
no lldp tlv-select dcbxp ets-recommend
no lldp tlv-select dcbxp pfc
no lldp tlv-select dcbxp application-priority
exit
!
interface Te2/0/7
mtu 9216
no lldp tlv-select dcbxp ets-config
no lldp tlv-select dcbxp ets-recommend
no lldp tlv-select dcbxp pfc
no lldp tlv-select dcbxp application-priority
exit
!
interface Te2/0/8
mtu 9216
no lldp tlv-select dcbxp ets-config
no lldp tlv-select dcbxp ets-recommend
no lldp tlv-select dcbxp pfc
no lldp tlv-select dcbxp application-priority
exit
!
interface Te2/0/9
mtu 9216
no lldp tlv-select dcbxp ets-config
no lldp tlv-select dcbxp ets-recommend
no lldp tlv-select dcbxp pfc
no lldp tlv-select dcbxp application-priority
exit
!
interface Te2/0/10
mtu 9216
no lldp tlv-select dcbxp ets-config
no lldp tlv-select dcbxp ets-recommend
no lldp tlv-select dcbxp pfc
no lldp tlv-select dcbxp application-priority
exit
!
interface Te2/0/11
mtu 9216
no lldp tlv-select dcbxp ets-config
no lldp tlv-select dcbxp ets-recommend
no lldp tlv-select dcbxp pfc
no lldp tlv-select dcbxp application-priority
exit
!
interface Te2/0/12
mtu 9216
no lldp tlv-select dcbxp ets-config
no lldp tlv-select dcbxp ets-recommend
no lldp tlv-select dcbxp pfc
no lldp tlv-select dcbxp application-priority
exit
!
interface Te2/0/13
mtu 9216
no lldp tlv-select dcbxp ets-config
no lldp tlv-select dcbxp ets-recommend
no lldp tlv-select dcbxp pfc
no lldp tlv-select dcbxp application-priority
exit
!
interface Te2/0/14
mtu 9216
no lldp tlv-select dcbxp ets-config
no lldp tlv-select dcbxp ets-recommend
no lldp tlv-select dcbxp pfc
no lldp tlv-select dcbxp application-priority
exit
!
interface Te2/0/15
mtu 9216
no lldp tlv-select dcbxp ets-config
no lldp tlv-select dcbxp ets-recommend
no lldp tlv-select dcbxp pfc
no lldp tlv-select dcbxp application-priority
exit
!
interface Te2/0/16
mtu 9216
no lldp tlv-select dcbxp ets-config
no lldp tlv-select dcbxp ets-recommend
no lldp tlv-select dcbxp pfc
no lldp tlv-select dcbxp application-priority
exit
!
interface Te2/0/17
channel-group 1 mode active
mtu 9216
no lldp tlv-select dcbxp ets-config
no lldp tlv-select dcbxp ets-recommend
no lldp tlv-select dcbxp pfc
no lldp tlv-select dcbxp application-priority
exit
!
interface Te2/0/18
spanning-tree portfast
mtu 9216
no lldp tlv-select dcbxp ets-config
no lldp tlv-select dcbxp ets-recommend
no lldp tlv-select dcbxp pfc
no lldp tlv-select dcbxp application-priority
exit
!
interface Te2/0/19
spanning-tree portfast
mtu 9216
no lldp tlv-select dcbxp ets-config
no lldp tlv-select dcbxp ets-recommend
no lldp tlv-select dcbxp pfc
no lldp tlv-select dcbxp application-priority
exit
!
interface Te2/0/20
spanning-tree portfast
mtu 9216
no lldp tlv-select dcbxp ets-config
no lldp tlv-select dcbxp ets-recommend
no lldp tlv-select dcbxp pfc
no lldp tlv-select dcbxp application-priority
exit
!
interface port-channel 1
mtu 9216
exit
!
interface port-channel 2
mtu 9216
exit
!
interface port-channel 3
mtu 9216
exit
!
interface port-channel 4
mtu 9216
exit
!
interface port-channel 5
mtu 9216
exit
!
interface port-channel 6
mtu 9216
exit
!
interface port-channel 7
mtu 9216
exit
!
interface port-channel 8
mtu 9216
exit
!
interface port-channel 9
mtu 9216
exit
!
interface port-channel 10
mtu 9216
exit
!
interface port-channel 11
mtu 9216
exit
!
interface port-channel 12
mtu 9216
exit
!
interface port-channel 13
mtu 9216
exit
!
interface port-channel 14
mtu 9216
exit
!
interface port-channel 15
mtu 9216
exit
!
interface port-channel 16
mtu 9216
exit
!
interface port-channel 17
mtu 9216
exit
!
interface port-channel 18
mtu 9216
exit
!
interface port-channel 19
mtu 9216
exit
!
interface port-channel 20
mtu 9216
exit
!
interface port-channel 21
mtu 9216
exit
!
interface port-channel 22
mtu 9216
exit
!
interface port-channel 23
mtu 9216
exit
!
interface port-channel 24
mtu 9216
exit
!
interface port-channel 25
mtu 9216
exit
!
interface port-channel 26
mtu 9216
exit
!
interface port-channel 27
mtu 9216
exit
!
interface port-channel 28
mtu 9216
exit
!
interface port-channel 29
mtu 9216
exit
!
interface port-channel 30
mtu 9216
exit
!
interface port-channel 31
mtu 9216
exit
!
interface port-channel 32
mtu 9216
exit
!
interface port-channel 33
mtu 9216
exit
!
interface port-channel 34
mtu 9216
exit
!
interface port-channel 35
mtu 9216
exit
!
interface port-channel 36
mtu 9216
exit
!
interface port-channel 37
mtu 9216
exit
!
interface port-channel 38
mtu 9216
exit
!
interface port-channel 39
mtu 9216
exit
!
interface port-channel 40
mtu 9216
exit
!
interface port-channel 41
mtu 9216
exit
!
interface port-channel 42
mtu 9216
exit
!
interface port-channel 43
mtu 9216
exit
!
interface port-channel 44
mtu 9216
exit
!
interface port-channel 45
mtu 9216
exit
!
interface port-channel 46
mtu 9216
exit
!
interface port-channel 47
mtu 9216
exit
!
interface port-channel 48
mtu 9216
exit
!
interface port-channel 49
mtu 9216
exit
!
interface port-channel 50
mtu 9216
exit
!
interface port-channel 51
mtu 9216
exit
!
interface port-channel 52
mtu 9216
exit
!
interface port-channel 53
mtu 9216
exit
!
interface port-channel 54
mtu 9216
exit
!
interface port-channel 55
mtu 9216
exit
!
interface port-channel 56
mtu 9216
exit
!
interface port-channel 57
mtu 9216
exit
!
interface port-channel 58
mtu 9216
exit
!
interface port-channel 59
mtu 9216
exit
!
interface port-channel 60
mtu 9216
exit
!
interface port-channel 61
mtu 9216
exit
!
interface port-channel 62
mtu 9216
exit
!
interface port-channel 63
mtu 9216
exit
!
interface port-channel 64
mtu 9216
exit
!
interface port-channel 65
mtu 9216
exit
!
interface port-channel 66
mtu 9216
exit
!
interface port-channel 67
mtu 9216
exit
!
interface port-channel 68
mtu 9216
exit
!
interface port-channel 69
mtu 9216
exit
!
interface port-channel 70
mtu 9216
exit
!
interface port-channel 71
mtu 9216
exit
!
interface port-channel 72
mtu 9216
exit
!
interface port-channel 73
mtu 9216
exit
!
interface port-channel 74
mtu 9216
exit
!
interface port-channel 75
mtu 9216
exit
!
interface port-channel 76
mtu 9216
exit
!
interface port-channel 77
mtu 9216
exit
!
interface port-channel 78
mtu 9216
exit
!
interface port-channel 79
mtu 9216
exit
!
interface port-channel 80
mtu 9216
exit
!
interface port-channel 81
mtu 9216
exit
!
interface port-channel 82
mtu 9216
exit
!
interface port-channel 83
mtu 9216
exit
!
interface port-channel 84
mtu 9216
exit
!
interface port-channel 85
mtu 9216
exit
!
interface port-channel 86
mtu 9216
exit
!
interface port-channel 87
mtu 9216
exit
!
interface port-channel 88
mtu 9216
exit
!
interface port-channel 89
mtu 9216
exit
!
interface port-channel 90
mtu 9216
exit
!
interface port-channel 91
mtu 9216
exit
!
interface port-channel 92
mtu 9216
exit
!
interface port-channel 93
mtu 9216
exit
!
interface port-channel 94
mtu 9216
exit
!
interface port-channel 95
mtu 9216
exit
!
interface port-channel 96
mtu 9216
exit
!
interface port-channel 97
mtu 9216
exit
!
interface port-channel 98
mtu 9216
exit
!
interface port-channel 99
mtu 9216
exit
!
interface port-channel 100
mtu 9216
exit
!
interface port-channel 101
mtu 9216
exit
!
interface port-channel 102
mtu 9216
exit
!
interface port-channel 103
mtu 9216
exit
!
interface port-channel 104
mtu 9216
exit
!
interface port-channel 105
mtu 9216
exit
!
interface port-channel 106
mtu 9216
exit
!
interface port-channel 107
mtu 9216
exit
!
interface port-channel 108
mtu 9216
exit
!
interface port-channel 109
mtu 9216
exit
!
interface port-channel 110
mtu 9216
exit
!
interface port-channel 111
mtu 9216
exit
!
interface port-channel 112
mtu 9216
exit
!
interface port-channel 113
mtu 9216
exit
!
interface port-channel 114
mtu 9216
exit
!
interface port-channel 115
mtu 9216
exit
!
interface port-channel 116
mtu 9216
exit
!
interface port-channel 117
mtu 9216
exit
!
interface port-channel 118
mtu 9216
exit
!
interface port-channel 119
mtu 9216
exit
!
interface port-channel 120
mtu 9216
exit
!
interface port-channel 121
mtu 9216
exit
!
interface port-channel 122
mtu 9216
exit
!
interface port-channel 123
mtu 9216
exit
!
interface port-channel 124
mtu 9216
exit
!
interface port-channel 125
mtu 9216
exit
!
interface port-channel 126
mtu 9216
exit
!
interface port-channel 127
mtu 9216
exit
!
interface port-channel 128
mtu 9216
exit
snmp-server engineid local 800002a203d067e5dc8cc4
enable password * encrypted
exit

Hello,

we're in the progress of rolling out 802.1X on N2000 switches. We want the following features:

• Fall Back to MAB
• Dynamic VLAN Assignment
• Guest VLAN (for PXE)
• AAA per MAC

So we have the following config on our test ports.

switchport mode general
switchport general allowed vlan remove 1
dot1x port-control mac-based
dot1x reauthentication
dot1x timeout guest-vlan-period 4
dot1x unauth-vlan 2
dot1x mac-auth-bypass
authentication order dot1x mab
authentication priority dot1x mab

This works fine so far. The client boots, passes PXE and then authenticates using 802.1X. The Problem here is, that the unauth VLAN does not get removed again. So all Broadcast from our unauth VLAN is visible on a Port where only one successfully authenticated Client is attached.

We would expect, that after the client switches to 802.1X and is authenticated, the unauth VLAN would be removed from the port. What is missing for this to happen?

Hi,

Just wondering if anyone has experienced this. We have a couple of PeR720s connected to EQL41xx units via the above 6224 (stacked). The PeR720s are part of a Hyper-V cluster (Server 20112 R2).

For a while now, the cluster has been falling over- every 2/3 weeks. the solution up till now seems to have been to carefully shut down "unnecessary" guests, move the critical ones to one host then reboot each host in turn.

This didn't work the other day and cause chaos- nothing came back properly, the guests crashed etc. I noticed- for the first time- that the shared host networks were all over the place- hosts couldn't ping guests on iSCSI networks etc and vice versa, or pings were intermittent.

I rebooted the 6224 stack and everything was much more stable- zero packet loss, cluster behaving nicely, everything much faster.

Has anyone noticed 6224 units freezing up like this? They're running firmware 3.3.11.2 which was only released in July '14 so they can't have been up more than 7 months since the upgrade and a reboot.

This is obviously serious; the cluster is in production, and- if it is switch related- has to be fixed, we can't be rebooting the stack every couple of months (besides which, automatically rebooting this stack would be tricky).

I've had luck in the past with configuring LLDP-MED on 5548P's; however, the N-series switches appear to handle things quite a bit differently.

Does anyone have a working configuration with these switches where the phone receives VLAN information via LLDP-MED and immediately boots to the voice VLAN?

sslt_control.c(577) SSLT: Exceeded maximum, ssltConnectionTask

and

sslt_control.c(1037) SSLT: error on accepting the SSL connection!

What do these mean?

Hello,

Does the PowerConnect 2816 support syslog? The product page states it supports the RFC 3164 — BSD Syslog Protocol standard, but I can not find anywhere in the guy or the cli to configure it.

TIA,

Jon

Hello,

I have N3024F and I can't config the SFP to work with 100MB.

Is it possible or I need to change the SFP or config another thing first?

Thanks

Sefi

Good afternoon all.

This may be a stupid question, hence the reason I'm not getting anywhere.

I have 3 switches.

1 Core and 2 connected to the main switch

So Core 6248 has a LAG Port and Physical Connection to Slave one. and Slave 2. for purpose of question.

We have VLAN 1 and 20 on all three switches and The LAG Ports are set as General with VLAN 1, & 20 Allowed.

We have an IP address assigned to one of the slave switches on VLAN20 in the 172.16.20.x Range and routing is enabled as follows.

Route Codes: R - RIP Derived, O - OSPF Derived, C - Connected, S - Static
B - BGP Derived, IA - OSPF Inter Area
E1 - OSPF External Type 1, E2 - OSPF External Type 2
N1 - OSPF NSSA External Type 1, N2 - OSPF NSSA External Type 2

S 0.0.0.0/0 [1/0] via 192.168.0.248, vlan 1
C 172.16.20.0/22 [0/1] directly connected, vlan 20 - Phone Network
C 192.168.0.0/22 [0/1] directly connected, vlan 1 - Core Network for Gateway and servers etc

This is owing to the fact the switch has ip phones attached to it, and pcs running via those phones, this routing allows the phones to talk to each other, and for the pc's to traverse the network, and get out to the default gateway for internet and service etc.

We now would like to add a phone to the second slave switch, that only has routing on the vlan1, but I can not see an easy way to get the VLAN 20 traffic to route, as if I assign a 172.16.20.x IP address to the VLAN interface it gets confused, as the routing is all wrong.

Current IP Route for Slave 2

Route Codes: R - RIP Derived, O - OSPF Derived, C - Connected, S - Static
B - BGP Derived, IA - OSPF Inter Area
E1 - OSPF External Type 1, E2 - OSPF External Type 2
N1 - OSPF NSSA External Type 1, N2 - OSPF NSSA External Type 2

S 0.0.0.0/0 [1/0] via 192.168.0.248, vlan 1
C 192.168.0.0/22 [0/1] directly connected, vlan 1

There is no VLAN routing setup on the Core (Main switch) other than the following route.

Route Codes: R - RIP Derived, O - OSPF Derived, C - Connected, S - Static
B - BGP Derived, IA - OSPF Inter Area
E1 - OSPF External Type 1, E2 - OSPF External Type 2
N1 - OSPF NSSA External Type 1, N2 - OSPF NSSA External Type 2

S 0.0.0.0/0 [1/0] via 192.168.0.248, vlan 1
C 192.168.0.0/22 [0/1] directly connected, vlan 1

what am I doing wrong. Many thanks in advance. 

Because of the routing as configured, on Slave I can ping IP Device on Slave 2 but not on VLAN20, so the phones will not work.

We have following Setup:

    2 redundant Dell 2848 Switches, identically configured and connected via 8-Port LAG on Ports 41-48.

    2 identically setup Dell R730 with BroadCom 5720. Operating System is Microsoft Server 2012-R2.

We wanted to make a fully redundant setup with maximum bandwidth. server S1&S2 port 1&2 are plugged into switch A and server S1&S2 port 3&4 are plugged into switch B.

On the server side, the 4 NIC are teamed together, on the switches the 2 ports each server is plugged in are put into LAG. Since the switches are only PowerConnect 2848 the LAGs are setup static. We only manage to achieve 2 GB/s.

SwitchA:

    LAG A1(Server1 p1 Server1 p2)
    LAG A2(Server2 p1 Server2 p2)
    LAG A3(Switch2 p41..p48)

SwitchB:

    LAG B1(Server1 p3 Server1 p4)
    LAG B2(Server2 p3 Server3 p4)

    LAG B3(Switch1 p41..p48)

    If we unplug LAG A1, we have a short drop and go back to 2 GB/s
    If we unplug LAG A2, we have a short drop and go back to 2 GB/s

All LAG plugged in again, next test:

    We unplug Server1 p1, we have a short drop and go back to 2 GB/s
    We unplug Server1 p3, we have a short drop and go back to 2 GB/s

This is where my confusion begins. Up until now i thought the multi-switch connection simply wasn't capable of bandwidth adding, but obviously with only one port plugged into each switch i once again have 2 GB/s. Yet i never had the hoped for 4 GB/s at the beginning.

When trying to find the source of the problem, more confusion arose:

    4 NIC teaming on each server, no LAG on switch, all ports plugged into one switch: 1 GB/s

    4 NIC teaming on each server, 4 port LAG on switch, all ports plugged into one switch: 4 GB/s

    one cable unplugged: drop to 2 GB/s.

I fail to understand this behaviour, maybe i am missing something simple or maybe i am simply dumb, but if you can, please explain it to me or make suggestions how to achieve maximum bandwidth with maximum redundancy.

Dear All,

I have to configure an MXL 10/40 GbE switch. In my scenario, each port 0/1-12 has to access 3 different networks.

1. Management (VLAN: 10)

2. Storage (VLAN: 11)

3. Admin (Untagged)

I can assign the ports to access multiple VLANs. (tagged tengigabitethernet 0/1 - 12 ). But what if I have to pass the untagged traffic as well? 

Regards,

Is there any way to enable TLS and SSLv3 on PC5448?  I have the latest firmware installed, 20046, but don't see any option to enable it. 

Thanks in advance.

Hey all,

I'm trying to setup an M1000e chassis I just received. I know about nothing related to networking, but I'm good with the hardware and software components of this system. Here is my situation and layout of setup.

Hardware layout:

2 Ethernet ports. (Eth0/Eth1)
2 M6220 Switches (no-stacking hardware) (A1/A2)
2 CMC modules (CMC1/CMC2)
16 M610 Blades (Bld1-Bld16)

Network layout:

University managed routers/network – source of 2 Ethernet ports above (Eth0/Eth1)
CMC1 connected to Eth0
A1 connected to Eth1 on Port 20
CMC2 connected to A1 port 17
A2 connected to A1 via port 18 on both.

I do not have control over the university managed Eth0/Eth1 ports. The ports provide IPs in the range of 10.110.x.x

I want to configure A1 to do the following:

• Act as a switch for Eth0 for CMC1/CMC2 as well as Bld1-Bld16.

By this I mean:

Have A1 plugged into Eth0. CMC1/CMC2 will also be connected to A1 and provide a university given IPs to both. A1 should also provide university given IPs to Bld1-16 so they can reach-out to the internet/each other.

If this is possible then have A2 be plugged into A1 on port 20. A2 would then provide university given IPs to Ports 16-19 so I can have other systems plugged into A2 (since we do not have enough Ethernet ports in the room).

I am not a network engineer, and I know very very little about configuring networks. Any help is appreciated. I’m not sure if what I am asking is able to be done. I was reading up about stacking modules, and what I want from the A1/A2 connection might only be done with a stacking configuration.

I don't know if this is asking a lot, but thanks for any help!

Hi All,

We try use external 4 port use LAG with LACP connect to H3C switch but some problem as below.

Both side setup LACP with trunk VLAN already

one cable connect 0/1 port to H3C only, external client can ping VRTX internal ESXi host, when connect one more cable 0/2 to H3C and client ping failed

disconnect 0/1 cable, connect one cable 0/2 port to H3C only, external client can ping VRTX internal ESXi host, when connect one more cable 0/1 to H3C and client ping failed

I am not sure which problem, is LACP static or dynamic mode problem, but R1-2401 cannot set static or dynamic.

Best regards,

Chung

Hello,

Disclosure: I have a moderate amount of IT knowledge but am a newbie when it comes to networking and all the various IEEE protocols.

I need a new Gigabit switch for my network to replace a 2716 that died on me.  I was all set to order a 2808 when I came across another post on this forum that has me concerned that the 2808 will not work for me (en.community.dell.com/support-forums/network-switches/f/866/t/19541840.aspx ).  I have a Synology DS412+ NAS that has 2 gigabit ports that I connected to the switch and configured with Link Aggregation.  A few days ago I needed to physically move the 2716 from one rack to a different one.  When I unplugged the power the switch just died.  It would not turn back on.  I assume the PSU couldn't handle the power cycle.

Needing a switch right away I ran to the nearest Fry's and purchased a NetGear switch.  When I tried to configure my NAS with LAG I was disappointed to receive an error message that my switch does not support 802.3ad.  I decided to keep the NetGear for a few days while I order a new PowerConnect.  This network is small - I only use 5 ports.  I was planning on buying the 2808 as I see it is listed as supporting 802.3ad.  Then I came across the above post that seems to say it supports some form of LAG, but not LACP 802.3ad.

Can someone please tell me in non technical terms what features are different (besides the number of ports) between the 2716 and 2808?  Will the 2808 work in LAG with my DS412+?  I should point out that my 192.168.1.xxx network is configured with fixed IP addresses.  I do not use DHCP.  Does that make a difference?

If the 2808 will not meet my needs, can you recommend other PowerConnect models that would be in the $150 price range that would?  If need be I can buy a used 2716 on eBay.  I would prefer buying a new switch to avoid having any problems down the road.

P.S.  I do not recall ever configuring my 2716.  If I buy the 2808, would I need to configure it or can I just "plug it in"?

Hi All

I have two N4032 switch (ver. 6.1.2.4) and they are stacking. Each of them has one 10GbE SFP+ module.

I try to apply ACL on interface port 17. I apply acl8, it is working.

Then I apply acl1 on port 17, I got the message "HW limit may have been exceeded."

How many rules can apply on N4032?

N4032 ACL Spec. is

Max number of ACLs: 100
Max ACL rules system-wide: 3,072
Max rules per ACL: 1,023
Max ACL rules per interface (IPv4): 2,047 (ingress), 1,023 (egress)
Max ACL rules per interface (IPv6): 1,021 (ingress), 512 (egress)
Max VLAN interfaces with
ACLs applied: 24

Thanks.

Hi everyone,

We have a few Powerconnect 8024F using more than 60% of its CPU time on `snoopTask`.

status      bytes
------ ----------
  free  674521408
 alloc  327563488



CPU Utilization:


  PID      Name                    5 Secs     60 Secs    300 Secs
-----------------------------------------------------------------
 4ad0a00 tTffsPTask                 0.00%       0.02%       0.00%
 4aede50 tNet0                      0.21%       0.08%       0.05%
 4d19990 ipnetd                     0.21%       0.03%       0.00%
 4d780d0 envMonTask                 0.00%       0.13%       1.18%
 4d818a0 osapiTimer                 0.00%       0.11%       0.14%
 4f93200 bcmL2X.0                   3.17%       3.44%       3.34%
 4fb9ac0 bcmCNTR.0                  0.84%       0.87%       0.84%
 500dde0 bcmTX                      2.33%       1.96%       1.76%
 56cbd50 bcmRX                      4.87%       4.45%       4.40%
 5cbdc90 MAC Send Task              2.75%       3.12%       3.19%
 5cc7190 MAC Age Task               1.90%       0.63%       0.67%
 6aa3310 bcmLINK.0                  1.27%       0.84%       0.68%
 91fa040 tL7Timer0                  0.00%       0.00%       0.01%
 921f950 osapiMonTask               0.00%       0.06%       0.07%
 9224e70 serialInput                0.00%       0.01%       0.01%
 a4fb110 portMonTask                0.00%       0.00%       0.01%
 a5254b0 simPts_task                0.00%       0.03%       0.05%
 ac294e0 emWeb                      0.00%       0.00%       0.01%
 ac3c400 dtlTask                    4.44%       4.31%       4.18%
 ac456d0 dtlAddrTask                0.00%       0.00%       0.01%
 ac8ebd0 hapiRxTask                 2.33%       1.55%       1.47%
 ba8b380 DHCP snoop                 0.00%       0.00%       0.02%
 ceea3a0 dot1s_timer_task           0.84%       0.35%       0.28%
 da20f40 unitMgrTask                0.00%       0.01%       0.00%
 dc03030 snoopTask                 66.73%      68.60%      67.56%
 ed219b0 dhcpsPingTask              0.00%       0.03%       0.03%
 eeb1d30 ipMapForwardingTask        1.27%       1.21%       1.22%
156d8780 ip6MapLocalDataTask        0.21%       0.31%       0.34%
15d09730 lldpTask                   0.21%       0.16%       0.16%
15fad980 tCptvPrtl                  0.00%       0.05%       0.03%
164cba80 isdpTask                   0.00%       0.05%       0.49%
16d41400 RMONTask                   0.21%       0.16%       0.19%
16d531f0 boxs Req                   0.00%       0.00%       0.01%
-----------------------------------------------------------------
 Total CPU Utilization             93.85%      92.74%      92.57%

These switches typically are connect to a dozen 5548s and running rstp in between, purely layer 2, all of them are on firmware 5.1.0.1.  We are quite surprised to see little performance issue given the high load.

Are we seeing a firmware bug or something a lot more sinister? What is `snoopTask` and how shall I troubleshoot such problems?

Please let me know if any additional info is required, Thank you very much.

Will

Dear All,

I have to configure my Force10 MXL 10/40 GbE for PS-M4110 storage array. I have two PS-M4110 connected to ports 0/13 and 0/15. I have configured it in the following way.

FTOS(conf)# no dcb enable

FTOS(conf)# iscsi enable

Configuration of ports 0/13 and 0/15 (same)

FTOS(conf-if-te-0/15)#sho con
!
interface TenGigabitEthernet 0/13
no ip address
mtu 12000
portmode hybrid
switchport
flowcontrol rx on tx off
spanning-tree mstp edge-port
spanning-tree rstp edge-port
spanning-tree 0 portfast
spanning-tree pvst edge-port
iscsi profile-compellent
no shutdown

I just need to know if these settings are okay. And do I have to configure iscsi target port (3260,860) ip-address (A.B.C.D) as well? if yes, then which IP is to be given here? group-IPaddress?

Hi There,

I'm trying to configure a PowerConnect 5424 switch to connect it within my network as one of the distribution switch. When I explain about my network; its very basic as we do not have any managed VLANs or any other complicated set-up. 

When I boot the switch connecting with putty via a serial cable, I can see the output of the switch where I cannot input anything. I've even tried three different terminal emulators which didn't work at all.

What can be the reason, how can I achieve this as I just want to configure an IP so that I can login to switch and monitor the ports... etc?