Hi Guys.

I have 2x 6024 using lacp's interconnected.

A server with 2 nics with an lacp bond both connected to the same port-channel ID on one of the switches works, and I assume it should even when it's not an mlag supported switch

I actually running this setup already for years without any issues.

Now would it be possible to create a port-channel on both switched on one port and trunk both connections to a 5448 where this same lacp lives ?

I was working before but now I have one port on the 5448 Active and one "Non-candidate"

Please help me out.

Hi all,

I'm fairly new to blade chassis/networking and have been tasked with setting up a M1000e with 12 blades with 4 mxl fabric switches splitting 4 VLANs across 2 VLT pairs (management & production in A2 & B1 / iSCSI & vMotion in A1 & B2).  There's a port channel from fabric A2 & B1 to a TOR N4032 (which will be VLT paired as our new core network).

So far i have the management and production switches configured and i've got one blade server installed in slot 1 (m620).  I see te 0/1 as up and on the default vlan (untagged) and both production and management (tagged).

Port                 Description  Status Speed        Duplex Vlan
Te 0/1                            Up     10000 Mbit   Full   1,405,410

Slot 1 has ESXi installed on it and if i run a ring test i get no responses from anything on the management or production VLANs.

If i check the mac address table on fabric B1 all i see is port channel (101) with no reference to the MAC address at te 0/1.

VlanId     Mac Address           Type          Interface        State
 1      14:18:77:d9:16:b1       Dynamic         Po 101          Active
 1      14:18:77:d9:16:b2       Dynamic         Po 101          Active
 1      44:a8:42:3b:d0:23       Dynamic         Po 101          Active
 405    00:00:74:df:0a:3b       Dynamic         Po 101          Active
 405    00:00:74:eb:79:64       Dynamic         Po 101          Active
 405    00:01:e8:8b:f0:be       Dynamic         Po 101          Active
 405    00:0c:29:5c:d9:e3       Dynamic         Po 101          Active
 405    00:12:79:d6:a0:ea       Dynamic         Po 101          Active
 405    00:12:79:d6:a0:eb       Dynamic         Po 101          Active
 405    00:15:c5:ef:d9:ad       Dynamic         Po 101          Active
 405    00:18:fe:69:fd:42       Dynamic         Po 101          Active
 405    00:19:b9:dd:dd:15       Dynamic         Po 101          Active
 405    00:19:b9:dd:dd:17       Dynamic         Po 101          Active
 405    00:19:b9:de:17:95       Dynamic         Po 101          Active
 405    00:19:b9:de:17:97       Dynamic         Po 101          Active
 405    00:1b:21:24:12:3b       Dynamic         Po 101          Active
 405    00:20:4a:71:04:ae       Dynamic         Po 101          Active
 405    00:20:4a:71:04:af       Dynamic         Po 101          Active
 405    00:20:4a:71:04:b0       Dynamic         Po 101          Active
 405    00:20:4a:71:04:b1       Dynamic         Po 101          Active
 405    00:20:4a:71:04:b2       Dynamic         Po 101          Active
 405    00:20:4a:71:04:b3       Dynamic         Po 101          Active
 405    00:20:4a:71:04:b4       Dynamic         Po 101          Active

I'm at a loss with why this would be.  Does anyone have any ideas?

thanks

.

Hello,

I'm looking at a S4048-ON switch and I'm wondering portmodes (aka Switchport mode) options DNOS 9 offer.  I can see there is hyrbid but that needs to be set?  If so, what mode is it in prior to being set?

Regards.

Hello,

Today, we have observed that some Dell N2048 stacks (running 6.3.0.6) fail to respond to SNMP requests. I haven't checked the logs of all of them but one device at least had this kind of log entries I haven't seen before:

<187> Aug 24 14:47:42 de2000-118.local.fe-3 DRIVER[trafficStormCon]: rpc.c(357) 121705 %% RPC - Timeout to CPU: f8:b1:56:8a:df:82.
<188> Aug 24 14:47:02 de2000-118.local.fe-3 DRIVER[bcmATP-RX]: atp.c(1178) 121704 %% ATP RX: Failed to alloc for reassem
<187> Aug 24 13:10:35 de2000-118.local.fe-3 DRIVER[trafficStormCon]: rpc.c(357) 121645 %% RPC - Timeout to CPU: f8:b1:56:8a:df:82.
<188> Aug 24 13:09:55 de2000-118.local.fe-3 DRIVER[bcmATP-RX]: atp.c(1178) 121644 %% ATP RX: Failed to alloc for reassem

What does these entries mean? Could these be linked to the failing SNMP queries or are they completely unrelated? The logs don't contain anything else relaiting either SNMP or resource starvation if I was able to understand the entries correctly.

Best regards,

Matti

I'm troubleshooting some user complaints of slow network response, and I'm looking at the link status lights for my PC RJ45 connections on the 6224.  All of the right LED's (above the RJ45 jacks) are solid green, meaning good connections (I think), but some of the left LEDs are blinking green and some are blinking amber.  On other switches I've used, I've understood a blinking amber light to mean that it's operating at 10/100 Mbps, rather than gigabit, speed.  Is this true of the 6224?  I've verified that all cables are cat-5e or cat-6, and the PC network card Link Speed is set to 1.0 GB full duplex, but there could be other errors in the line that's causing the link to downgrade.  The 6224 user manual isn't all that helpful in that it says blinking amber indicates "The powered device power conception exceeds the predefined power allotment"  

Thanks!

I have spent the better part of a day trying to find all of the part numbers for stacking cables for the N-Series switches.  I am specifically looking to stack two N3048P switches and I need a 2 meter cable.  I have one but need a second.  I thought I would ask the experts!  I have a ton of N3000 switches and need to stack them in various rack configurations so if I could find a parts list for ALL of the cables, it would help a lot.  Thanks in advance.

I am deploying a new stack of MXLs in a new M1000e next week and I've been looking through the manual.  I noticed a section entitled "Tunneling."  For explanation all that is given is the following:

Tunneling supports RFC 2003, RFC 2473, and 4213. DSCP, hop-limits, flow label values, OSPFv2, and OSPFv3 are also supported. ICMP error relay, PATH MTU transmission, and fragmented packets are not supported.

I am wondering what this is about, and when it is appropriate to use it.  What scenario requires this?  Can anyone tell me?  Thanks.

Hello,

I have two Dell S4810 switches bonded with 40G for redundancy and i have 3 clients directly plugged into the switches also bonded. All of the clients are on the same 192.168.1 network. I have a server on 10.1.1 network and a both switches have interface configured on that network. I'm trying to setup the switches as default gateways for clients so they can reach the server by creating a VLAN with 192.168.1.1 address, assigning client into the VLAN and use it as default gateway but i'm not getting any luck. I cant even ping  192.168.1.1 from the clients. 

Any ideas what i'm missing? Here is a sample of the config:

protocol spanning-tree rstp
no disable
bridge-priority 36864
!
vlt domain 999
peer-link port-channel 100
primary-priority 36864
unit-id 1
!
stack-unit 0 provision S4810
!
interface TenGigabitEthernet 0/1
description CLIENT 1
no ip address
mtu 9200
flowcontrol rx on tx off
no shutdown
!
interface TenGigabitEthernet 0/2
description CLIENT 2
no ip address
mtu 9200
flowcontrol rx on tx off
no shutdown
!
interface TenGigabitEthernet 0/3
description CLIENT 3
no ip address
mtu 9200
flowcontrol rx on tx off
no shutdown
!
interface TenGigabitEthernet 0/10
ip address 10.1.1.10/24
no shutdown
!
interface fortyGigE 0/56
no ip address
mtu 9200
flowcontrol rx on tx off
no shutdown
!
interface fortyGigE 0/60
no ip address
mtu 9200
flowcontrol rx on tx off
no shutdown
!
interface ManagementEthernet 0/0
ip address 10.1.2.10/24
no shutdown
!
interface Port-channel 1
description lag for CLIENT 1
no ip address
mtu 9200
switchport
channel-member TenGigabitEthernet 0/1
vlt-peer-lag port-channel 1
no shutdown
!
interface Port-channel 2
description lag for CLIENT 2
no ip address
mtu 9200
switchport
channel-member TenGigabitEthernet 0/2
vlt-peer-lag port-channel 2
no shutdown
!
interface Port-channel 3
description lag for CLIENT 3
no ip address
mtu 9200
switchport
channel-member TenGigabitEthernet 0/3
vlt-peer-lag port-channel 3
no shutdown
!
interface Port-channel 100
no ip address
mtu 9216
channel-member fortyGigE 0/56,60
no shutdown
!
interface VLAN 10
ip address 192.168.1.1/24
untagged port-channel 1
untagged port-channel 2
untagged port-channel 3
no shutdown
!
route-map route-map permit 10
!
management route 0.0.0.0/0 10.1.2.1
!
ip route 0.0.0.0/0 10.1.1.1

I recently acquired a dell powerconnect 2724 from a friend, and I cant seem to find the web interface. I tried the default IP addresses, and I looked on an app for listing all the IP addresses on the network, and the only dell thing was my PowerEdge R710. I made sure it was in managed mode and I tried resetting it. Suggestions?

Hello,

I'm trying to resolve an issue in a two-device stack of PowerConnect 6248s (firmware 3.3.3.3) that has me baffled.

Here are what I feel are the relevant configuration items:
-  "ip routing" enabled in global config
-  VLAN 10 configured without IP address & does not having "routing" in interface config
-  Port 1/g10 is access mode for VLAN 10
-  Lots of other ports are configured for VLAN 10 as general mode tagged traffic.  These ports go to virtual switches (hypervisor) with lots of ports in each NIC team (Windows Server 2012 R2).  The virtual switches are not configured to use tagged VLANs but one VM in environment uses VLAN 10 in tagged configuration.  This is configured per-VM, not per-hypervisor

-  Spanning tree is in default mode:
Spanning tree:  Enabled
BPDU flooding:  Disabled
Portfast BPDU filtering:  Enabled
Mode:  RSTP

Scenario:
When we connect the upstream device (Netvanta 4430) to a single port (1/g10), all VMs which reside in VLAN 20 lose connectivity.  The VMs that lose connectivity are on the hypervisors mentioned above and only relationship is they are on ports configured with tagged VLAN 10 (and a couple others).  When I shut down 1/g10, everything returns to normal...

The upstream device is a single device, single connection into our environment that is not connected anywhere else in our environment.

We had similar issues recently when connecting two devices in a redundant fashion to each physical switch in the stack and put this down to an undiagnosed STP issue but now realise that something else is going on.

My question is, what is the relationship between global config "ip routing" and routing on a VLAN interface.  Is there some layer 2 issue going on that is 'below' VLANs and allowing the untagged VLAN 10 device to communicate with devices connected on tagged VLAN 10 ports?

Any thoughts or feedback would be appreciated, thanks in advance...!

Full config follows:

!Current Configuration:
!System Description "PowerConnect 6248, 3.3.3.3, VxWorks 6.5"
!System Software Version 3.3.3.3
!Cut-through mode is configured as disabled
!
configure
vlan database
vlan 10,20,30,38-39,44,255
vlan routing 20 1
vlan routing 30 2
vlan routing 38 3
vlan routing 44 4
exit
hostname "dcsw01"
clock timezone 10 minutes 0
stack
member 1 2
member 2 2
exit
ip address none
ip routing
ip route 0.0.0.0 0.0.0.0 192.168.38.1
ip route 192.168.39.0 255.255.255.0 192.168.38.1
ip route 192.168.47.0 255.255.255.0 192.168.38.1
ip route 192.168.0.0 255.255.0.0 192.168.44.1 5
ip route 10.0.0.0 255.0.0.0 192.168.44.1 5
ip route 192.168.49.0 255.255.255.0 192.168.38.1
interface vlan 10
name "SIP"
exit
interface vlan 20
name "DataCentre"
routing
ip address 192.168.20.1 255.255.255.0
exit
interface vlan 30
name "SAN"
routing
ip address 192.168.30.1 255.255.255.0
exit
interface vlan 38
name "ASA"
routing
ip address 192.168.38.10 255.255.255.0
exit
interface vlan 39
name "Perimeter"
exit
interface vlan 44
name "PIPN"
routing
ip address 192.168.44.10 255.255.255.0
exit
interface vlan 255
name "Internet"
exit
username ******** password ******** level 15 encrypted
bridge multicast filtering
ip igmp snooping
ip igmp snooping querier
!
interface ethernet 1/g1
description 'ASA Primary'
switchport access vlan 38
exit
!
interface ethernet 1/g2
description 'PIPN Primary'
switchport access vlan 44
exit
!
interface ethernet 1/g3
description 'Internet Service'
switchport access vlan 255
exit
!
interface ethernet 1/g4
description 'DCSAN01 NIC1'
switchport access vlan 30
exit
!
interface ethernet 1/g5
description 'SAN PS6120 NIC1'
switchport access vlan 20
exit
!
interface ethernet 1/g6
description 'DCNAS02 NIC1'
switchport access vlan 20
exit
!
interface ethernet 1/g7
description 'DCHyperVSupport RAC'
switchport access vlan 20
exit
!
interface ethernet 1/g8
description 'DCHyperVSupport NIC1'
switchport access vlan 20
exit
!
interface ethernet 1/g9
description 'DCHyperVSupport NIC2'
switchport access vlan 20
exit
!
interface ethernet 1/g10
shutdown
description 'Netvanta SIP Service'
switchport access vlan 10
exit
!
interface ethernet 1/g11
switchport access vlan 255
exit
!
interface ethernet 1/g12
switchport access vlan 255
exit
!
interface ethernet 1/g14
switchport access vlan 20
exit
!
interface ethernet 1/g15
description 'DCHyperV03 RAC'
switchport access vlan 20
exit
!
interface ethernet 1/g16
description 'DCHyperV03'
switchport access vlan 20
exit
!
interface ethernet 1/g17
description 'DCHyperV03'
switchport mode general
switchport general pvid 20
switchport general allowed vlan add 20
switchport general allowed vlan add 10,30,255 tagged
exit
!
interface ethernet 1/g18
description 'Cisco ASA device 1'
switchport access vlan 255
exit
!
interface ethernet 1/g19
description 'DCHyperV04 RAC'
switchport access vlan 20
exit
!
interface ethernet 1/g20
description 'DCHyperV04'
switchport access vlan 20
exit
!
interface ethernet 1/g21
description 'DCHyperV04'
switchport mode general
switchport general pvid 20
switchport general allowed vlan add 20
switchport general allowed vlan add 10,30,255 tagged
exit
!
interface ethernet 1/g22
description 'DCHyperV04'
switchport mode general
switchport general pvid 20
switchport general allowed vlan add 20
switchport general allowed vlan add 10,30,255 tagged
exit
!
interface ethernet 1/g23
description 'DCHyperV01 RAC'
switchport access vlan 20
exit
!
interface ethernet 1/g24
description 'DCHyperV01'
switchport access vlan 20
exit
!
interface ethernet 1/g25
description 'DCHyperV01'
switchport mode general
switchport general pvid 20
switchport general allowed vlan add 20
switchport general allowed vlan add 10,30,255 tagged
exit
!
interface ethernet 1/g26
description 'DCHyperV01'
switchport mode general
switchport general pvid 20
switchport general allowed vlan add 20
switchport general allowed vlan add 10,30,255 tagged
exit
!
interface ethernet 1/g27
description 'DCHyperV01'
switchport access vlan 39
exit
!
interface ethernet 1/g28
switchport access vlan 20
exit
!
interface ethernet 1/g29
description 'DCHyperV02 RAC'
switchport access vlan 20
exit
!
interface ethernet 1/g30
description 'DCHyperV02'
switchport access vlan 20
exit
!
interface ethernet 1/g31
description 'DCHyperV02'
switchport mode general
switchport general pvid 20
switchport general allowed vlan add 20
switchport general allowed vlan add 10,30,255 tagged
exit
!
interface ethernet 1/g32
description 'DCHyperV02'
switchport mode general
switchport general pvid 20
switchport general allowed vlan add 20
switchport general allowed vlan add 10,30,255 tagged
exit
!
interface ethernet 1/g33
description 'DCHyperV02'
switchport access vlan 39
exit
!
interface ethernet 1/g34
description 'DCSW03 management'
switchport access vlan 20
exit
!
interface ethernet 1/g35
switchport access vlan 20
exit
!
interface ethernet 1/g36
description 'DCNAS01 NIC1'
switchport access vlan 20
exit
!
interface ethernet 1/g37
switchport access vlan 20
exit
!
interface ethernet 1/g38
switchport access vlan 20
exit
!
interface ethernet 1/g39
description 'DCHyperV03'
switchport mode general
switchport general pvid 20
switchport general allowed vlan add 20
switchport general allowed vlan add 10,30,255 tagged
exit
!
interface ethernet 1/g40
description 'DCHyperV04'
switchport access vlan 39
exit
!
interface ethernet 1/g41
description 'DCHyperVTest-RAC'
switchport access vlan 20
exit
!
interface ethernet 1/g42
description 'DCHyperVTest'
switchport access vlan 20
exit
!
interface ethernet 1/g43
description 'DCHyperVTest'
switchport access vlan 20
exit
!
interface ethernet 1/g44
shutdown
switchport access vlan 39
exit
!
interface ethernet 1/g45
description 'DCHyperV04'
switchport access vlan 39
exit
!
interface ethernet 1/g46
description 'DCHyperV03'
switchport access vlan 39
exit
!
interface ethernet 1/g47
switchport access vlan 39
exit
!
interface ethernet 1/g48
switchport access vlan 39
exit
!
interface ethernet 1/xg1
switchport access vlan 20
exit
!
interface ethernet 1/xg2
switchport access vlan 20
exit
!
interface ethernet 1/xg3
switchport access vlan 20
exit
!
interface ethernet 1/xg4
switchport access vlan 20
exit
!
interface ethernet 2/g1
description 'ASA Secondary'
switchport access vlan 38
exit
!
interface ethernet 2/g2
description 'PIPN Secondary'
switchport access vlan 44
exit
!
interface ethernet 2/g3
description 'Internet Service 2'
switchport access vlan 255
exit
!
interface ethernet 2/g4
description 'DCSAN01 NIC2'
switchport access vlan 30
exit
!
interface ethernet 2/g5
description 'SAN PS6120 NIC2'
switchport access vlan 20
exit
!
interface ethernet 2/g6
description 'DCNAS02 NIC2'
switchport access vlan 20
exit
!
interface ethernet 2/g7
switchport access vlan 20
exit
!
interface ethernet 2/g8
description 'DCHyperVSupport NIC3'
switchport access vlan 20
exit
!
interface ethernet 2/g9
description 'DCHyperVSupport NIC4'
switchport access vlan 20
exit
!
interface ethernet 2/g10
switchport access vlan 39
exit
!
interface ethernet 2/g11
switchport access vlan 20
exit
!
interface ethernet 2/g12
switchport access vlan 20
exit
!
interface ethernet 2/g13
switchport access vlan 20
exit
!
interface ethernet 2/g14
switchport access vlan 39
exit
!
interface ethernet 2/g15
switchport access vlan 20
exit
!
interface ethernet 2/g16
description 'DCHyperV03'
switchport access vlan 20
exit
!
interface ethernet 2/g17
description 'DCHyperV03'
switchport mode general
switchport general pvid 20
switchport general allowed vlan add 20
switchport general allowed vlan add 10,30,255 tagged
exit
!
interface ethernet 2/g18
description 'Cisco ASA device 2'
switchport access vlan 255
exit
!
interface ethernet 2/g19
switchport access vlan 20
exit
!
interface ethernet 2/g20
description 'DCHyperV04'
switchport access vlan 20
exit
!
interface ethernet 2/g21
description 'DCHyperV04'
switchport mode general
switchport general pvid 20
switchport general allowed vlan add 20
switchport general allowed vlan add 10,30,255 tagged
exit
!
interface ethernet 2/g22
description 'DCHyperV04'
switchport mode general
switchport general pvid 20
switchport general allowed vlan add 20
switchport general allowed vlan add 10,30,255 tagged
exit
!
interface ethernet 2/g23
switchport access vlan 20
exit
!
interface ethernet 2/g24
description 'DCHyperV01'
switchport access vlan 20
exit
!
interface ethernet 2/g25
description 'DCHyperV01'
switchport mode general
switchport general pvid 20
switchport general allowed vlan add 20
switchport general allowed vlan add 10,30,255 tagged
exit
!
interface ethernet 2/g26
description 'DCHyperV01'
switchport mode general
switchport general pvid 20
switchport general allowed vlan add 20
switchport general allowed vlan add 10,30,255 tagged
exit
!
interface ethernet 2/g27
description 'DCHyperV01'
switchport access vlan 39
exit
!
interface ethernet 2/g28
switchport access vlan 20
exit
!
interface ethernet 2/g29
switchport access vlan 20
exit
!
interface ethernet 2/g30
description 'DCHyperV02'
switchport access vlan 20
exit
!
interface ethernet 2/g31
description 'DCHyperV02'
switchport mode general
switchport general pvid 20
switchport general allowed vlan add 20
switchport general allowed vlan add 10,30,255 tagged
exit
!
interface ethernet 2/g32
description 'DCHyperV02'
switchport mode general
switchport general pvid 20
switchport general allowed vlan add 20
switchport general allowed vlan add 10,30,255 tagged
exit
!
interface ethernet 2/g33
description 'DCHyperV02'
switchport access vlan 39
exit
!
interface ethernet 2/g34
description 'DCSW04 management'
switchport access vlan 20
exit
!
interface ethernet 2/g35
switchport access vlan 20
exit
!
interface ethernet 2/g36
description 'DCNAS01 NIC2'
switchport access vlan 20
exit
!
interface ethernet 2/g37
switchport access vlan 20
exit
!
interface ethernet 2/g38
switchport access vlan 20
exit
!
interface ethernet 2/g39
description 'DCHyperV03'
switchport mode general
switchport general pvid 20
switchport general allowed vlan add 20
switchport general allowed vlan add 10,30,255 tagged
exit
!
interface ethernet 2/g40
description 'DCHyperV04'
switchport access vlan 39
exit
!
interface ethernet 2/g41
switchport access vlan 20
exit
!
interface ethernet 2/g42
description 'DCHyperVTest'
switchport access vlan 20
exit
!
interface ethernet 2/g43
description 'DCHyperVTest'
switchport mode general
switchport general pvid 20
switchport general allowed vlan add 20
switchport general allowed vlan add 10,30,255 tagged
exit
!
interface ethernet 2/g44
switchport access vlan 39
exit
!
interface ethernet 2/g45
description 'DCHyperV04'
switchport access vlan 39
exit
!
interface ethernet 2/g46
description 'DCHyperV03'
switchport access vlan 39
exit
!
interface ethernet 2/g47
switchport access vlan 20
exit
!
interface ethernet 2/g48
switchport access vlan 39
exit
!
interface ethernet 2/xg1
switchport access vlan 20
exit
!
interface ethernet 2/xg2
switchport access vlan 20
exit
!
interface ethernet 2/xg3
switchport access vlan 20
exit
!
interface ethernet 2/xg4
switchport access vlan 20
exit
snmp-server community public ro
exit

hy All, please helpme

I have Blade M1000e with configuration as follow;

• Server 4 unit
• force 10 MXL 2 unit (included each 4-port 10Base-T)

i want to configure as follow;

one force 10 MXL for use internal IP and another force 10 MXL for use public IP,

please help me to configure step by step, maybe included picture, thank's before

Hi, I have a S3048 running Dell IOS firmware 9.10. I would like to restrict access for telnet and ssh to the switch but i'm having trouble getting this to work. So what i have is:

ip access-list extended telssh
 seq 10 permit 22 192.168.5.0/24  host 192.168.5.1
 seq 11 permit 23 192.168.5.0/24 host 192.168.5.1
 seq 12 permit 22 192.168.5.0/24 host 10.0.200.1
 seq 13 permit 23 192.168.5.0/24  host 10.0.200.1
 seq 20 deny 22 any 192.168.5.1/24
 seq 21 deny 23 any 192.168.5.1/24
 seq 22 deny 22 any 10.0.200.1/24
 seq 23 deny 23 any 10.0.200.1/24
 seq 100 permit ip any any

I've applied this access policy to three interfaces - 2 vlan ones and 1 real interface via the 'ip access-group' command however it's still possible to get ssh and telnet access from any network. The switch management ip is the 192.168.5.1 address and the 10.0.200.1 address is on an interface port. I'd like to restrict access for telnet and ssh from pretty much everyting except the management port and designated ip addresses that would be arriviong inbound via the port with address 10.0.200.1. If i take the seq 100 permit ip any any out of the access rule then this blocks ALL traffic from these ports, if i put it back then traffic flows again but so does telnet and ssh - Is what i would like to do possible and can somebody point me as to where i'm going wrong ?   

We get messages like this all the time.

<189> AUG 29 09:56:24 192.168.0.254-1 BSP[90164720]: cpu_env_monitor.c(206) 4326 %% Temperature Status Change, current = 2, previous = 1 FanSpeed set to: 9000

<189> AUG 29 09:48:17 192.168.0.254-1 BSP[90164720]: cpu_env_monitor.c(206) 4324 %% Temperature Status Change, current = 1, previous = 2 FanSpeed set to: 6000

When we check the temperature on that switch, it shows the MAC sensor at 33', and the PHY at 29' both are reporting as good.

We trend the temperature in SolarWinds via a Universal Device Poller that queries OID

1.3.6.1.4.1.674.10895.5000.2.6132.1.1.43.1.8.1.5

boxServicesTempSensorTemperature

That confirms this. Is there any way, we can turn this reporting off? We can use Solarwinds to warn us if there is a large temperature change. Otherwise we get an email every time the fans speed up or slow down.

The switches are in a server room that is regulated at 20c. There is 2U under and above each of the switchs.

Hi all 

i am facing an issue while configuring force10 mxl as fcoe switch

here is the scenario

i have M830 blade server installed in M1000E blade chassis having  57810 dual port 10 bg CNA hba on b slot.

i have force10 mxl installed on b1

b1 force10 mxl have 4 port SF P + 10 gbe module 4 port connected with brocade 300 TOR switch with fiber LC-LC cable.

brocade 300 switch is already connected to some fiber channel san.

i wanted to mount volumes from san to my M830 server in this scenario.

i have enabled FCOE on M830 by doing NPAR on 2nd partition.

now what configuration is required on force 10 mxl switch to mount LUN coming from SAN.

means how to get WWN of my M830 HBA on brocade 300 TOR switch in this scenario.

Please help.

Regards

Farhan Ashraf

Hi friends,

I work with IT and my expertise is Linux. Now, I'm setting a Captive Portal in my work with AP (Motorola AP-5131) that has a unique physical ethernet port, but is it possible to create 2 LANs in its configuration. Each LAN can be separated by VLANs.

The design is:

AP-5131
LAN1: 192.168.1.0/24 - VLAN2
LAN2: 10.0.0.0/24 - VLAN3

Now I need to connect the ethernet cable on the switch PC 2848, and I need to split the 2 LANs. The side B is a PFSENSE Firewall with 1 interface in VMWARE ESXi subdivided in 2 vlans (2 and 3) like in the AP. In this side also need connect a unique cable and to split in VLANs.

By default PC 2848 was setted all ports to VLAN 1 and the Management Port is setted to VLAN1.

I need to connect the AP LAN1 to my local Network and LAN2 to other devices in my Captive Portal.

How Can I do this action?

I known that the PC2848 is limited but I think is it possible to do.

Thanks for your help.

Dear Sir

anyone knows about this error message?

"broad_hpc_drv.c(4429) 8705 %% _soc_xgs3_mem_dma: FP_TCAM.ipipe0 failed(NAK)"

I got N4032 x 1 and N4032F x 1  stacking together

use firmware version 6.2.7.2

I have check   the release notes for 6.3.0.18a21/6.3.0.16a20/6.3.0.15a18/6.3.0.9a17/6.3.0.6a16/

but I don't see any known issue about this

anyone can help?

Thanks....

Hey everyone,

I'm in serious trouble...

The switch doesn't respond to ping (even after hard reboot), and I have lost the console password...

I am looking for a way to get out of this mess, and be able to log into the switch CLI.

I have tried to connect through the M1000e CMC, but it also prompted me, a need for password.

Could you guys help me on this ? What are my options ? Can I somehow reset the switch ?

Thank you for your help,

Regards

Jérémy

Anyone know?  It seems like most of the newer Cisco switches do not like these SFP modules and we had some spare 2848 switches.  The modules are in use with switches that need replacement (well out of warranty) so I can't test them at this time but I was just curious if anyone has been in this situation where older single mode FE modules are difficult to mate with the right switches.  Thank you!

I am having issues getting VLAN's setup on my PC 2724. I have 2 switches, a 5324 that connects to most of my servers and a 2724 for core networking (routers, backup NAS, cablecard tuners, wireless, etc.)

They both connect with a Gigabit Fiber SFP on Port 24. On the 5424 its in trunk mode with the native VLAN being 101 (the main client network), the rest of the switch is set to native VLAN 100 (main server network). In this configuration the 2724 has a native vlan of 101 and allowing all the other vlans. When i put the 2724 in managed mode and setup the VLAN where 23/24 had all tagged vlans, all the ports were set to untagged with PVID 101. It looked to work but for some reason DHCP was no longer working for my client in 101 (dont know about the other VLAN yet because were in the middle of recovering our VMware cluster)

Sorry for no spell check were really busy today trying to fix vmware

Howdy,

I have a PowerConnect 6224 that I'm using at home on my home network.  I recently started having a really *** internet connection with Pings in the multi-hundred range.  My setup is very simple:

Cable Modem -> Wireless Router -> PC 6224 -> stuff (printers, VOIP box, file server computer, etc)

If I go to www.pingtest.net with everything connected (I'm on wifi to the router), I was averaging around a 300ms ping response.  I then found that if I simply disconnect the switch from the router and run the test again, I get a sub 20ms ping without making any other changes.  If I then plug the switch back in, my pings are back up into the multi-hundred range.

I then unplugged the switch for a bit and let it reboot.  I rant the pingtest again it jumped up to around 95ms ping.  This is much better than it was before the reboot but still not as good as I'd like.

So this seems to tell me that the traffic from the switch is flooding the router with something that's causing all the traffic to slow way down.  When I brought the switch home, I installed the latest firmware and reset all the settings to their default and didn't change anything.

I'm wondering if there are certain settings I should change on the switch that might help with this problem.  Should I just get in the habit of rebooting it every so often?  Anything I can do?

Thanks for any help!