Error PowerConnect 3448.

Similar Questions

• Change of subnet PowerConnect 3448

  I just run the wizard from initial configuration to a PowerConnect 3448 and entered the wrong subnet. Can I change the subnet without erasing all parameters and rerun the wizard?

  Thank you

  
  

• PowerConnect 5548P Fatal Error - SNMP-F-BADTDOMAIN

  I have a stacked with 6 units of 5548P switch and I followed their status and basic via SNMP using Spiceworks and PRTG info.  Yesterday we had a weird breakdown where all the ports on the unit 4 are off (indicator HDMI and StackID remained upward) affecting traffic and POE devices connected to this unit.

  After the restart of unit 4, things are back to normal. Then, check the logs of the system, I found the following message is displayed. Has anyone seen this error before?

  % SYSARE STCK-A-UNITMSG: UNIT 1 ID, Msg: % SNMP-F-BADTDOMAIN: invalid or not supported TDomain received - function SNMPNotifyG_TDomainAndTAddress2UdpAddress 2 * FATAL ERROR * task Reporting: NCCD. Software version: 4.0.1.11 (October 16, 2011 time 18:10:50) 0x19f5c4 0x19c228 0x6aa9f4 0x49ba70 0x4a0f3c 0x4a10f8 0x484ba4 0x5dc3d4 0x5c6d44 0x5c6fc4 0x5c7028 0x5c7204 0x5c7258 0x5c79a4 0x5c7a70 0x5c7c20 0x5bfd78 0x5bff68 0x6856ac 0x68713c 0x4ca6dc 0x4caa9c 0x1548d0 * END OF FATAL ERROR *.

  Thank you

  I did some research about this error message and could not find a lot of information. The version of the software on the switch seems to be a very old version. The most recent firmware includes many improvements to SNMP and corrections where specific SNMP events would result in a switch to crash. A time to update the firmware of planning is the first step, I suggest you.

  http://Dell.to/1OQ6vi5

  Once updated, then watching to see if this problem persists.

• Errors of battery port (PowerConnect 6248 switch)

  Please see the logs below. What is that saying? The question is on the network or physical problem on the cable/port?

  Log buffer:

  Errors detected on the Port of pile 1/xg1 (oldRxErrors = 3001 = currentRxErrors 3003 oldTxErrors = 0 currentTxErrors = 0). Use BRCM_escape_apos; See the battery-port diagBRCM_escape_apos; Watch detailed statistics.

  See the battery port diag:

  1 - xg1:
  RBYT:3e5cfaaa RPKT:9a4ba4b TBYT:e4c25325 TPKT:7d81423d
  RFCs:BC0 RFRG:0 RJBR:0 RUND:0 ROVR:0
  TFCS:0 TERR. : 0

  1 - xg2:
  RBYT:c2277bb1 RPKT:6b2c0473 TBYT:ea7e75d3 TPKT:4b0cf8ae
  RFCS:0 RFRG:0 RJBR:0 RUND:0 ROVR:0
  TFCS:0 TERR. : 0

  2 - xg1:
  RBYT:32f4ae8 RPKT:17590db0 TBYT:dcc05da9 TPKT:330ea6d7
  RFCS:1 RFRG:0 RJBR:0 RUND:0 ROVR:0
  -Other - or ITU (q)
  TFCS:0 TERR. : 0

  2 - xg2:
  RBYT:1e243193 RPKT:7ca8563e TBYT:dce26ec1 TPKT:4bb4d53
  RFCS:15 RFRG:0 RJBR:0 RUND:0 ROVR:0
  TFCS:0 TERR. : 0

  3 - xg1:
  RBYT:670d9fbf RPKT:8553d2af TBYT:82112954 TPKT:b6b0d342
  RFCS:0 RFRG:0 RJBR:0 RUND:0 ROVR:0
  TFCS:0 TERR. : 0

  3 - xg2:
  RBYT:fae703cb RPKT:d9fe988e TBYT:79ddb35 TPKT:b0647900
  RFCS:0 RFRG:0 RJBR:0 RUND:0 ROVR:0
  TFCS:0 TERR. : 0

  4 - xg1:
  RBYT:25865503 RPKT:4f3df21b TBYT:27359088 TPKT:6e8f38a5
  RFCS:0 RFRG:0 RJBR:0 RUND:0 ROVR:0
  TFCS:0 TERR. : 0

  4 - xg2:
  -Other - or ITU (q)
  RBYT:8210be41 RPKT:b6b0d2dc TBYT:670cbb4d TPKT:8553d1cd
  RFCS:0 RFRG:0 RJBR:0 RUND:0 ROVR:0
  TFCS:0 TERR. : 0

  Thank you

  Ok. Finally I found the downtime. We had to add a new switch of the battery.

  I took 1/xg1 cable and put it in the 4\xg1 port to connect to the new switch.

  Also updated to the latest firmware.

  Result:

  -There was no errors for 2 the first 2 days.

  -first 8 mistakes happened today on port 4/xg1

  ------------TX-------------- ------------RX--------------

  Data error data error

  Rate rate rate rate Total

  Interface Unit (MB/s) (errors/s) errors (MB/s) (errors/s) errors

  ---- ---------------- ------ ---------- ---------- ------ ---------- ----------

  1    xg1              554    0          0          288    0          0

  1    xg2              820    0          0          972    0          0

  1    xg3              0      0          0          0      0          0

  1    xg4              0      0          0          0      0          0

  2    xg1              428    0          0          298    0          0

  2    xg2              291    0          0          549    0          0

  2    xg3              0      0          0          0      0          0

  2    xg4              0      0          0          0      0          0

  3    xg1              53     0          0          17     0          0

  3    xg2              295    0          0          435    0          0

  3    xg3              0      0          0          0      0          0

  3    xg4              0      0          0          0      0          0

  4    xg1              971    0          0          821    0          8

  4    xg2              18     0          0          52     0          0

  4    xg3              0      0          0          0      0          0

  4    xg4              0      0          0          0      0          0

  5    xg1              973    0          0          818    0          0

  5    xg2              818    0          0          973    0          0

  ------------TX-------------- ------------RX--------------

  Data error data error

  Rate rate rate rate Total

  Interface Unit (MB/s) (errors/s) errors (MB/s) (errors/s) errors

  ---- ---------------- ------ ---------- ---------- ------ ---------- ----------

  5    xg3              0      0          0          0      0          0

  5    xg4              0      0          0          0      0          0

  It's the fault of physical cable. I have to replace the cable.

  Thank you all for help in the investigation.

• BIOHD-2 error

  I have a Pavilion 6210f which began to give me a black screen with "Reboot and select proper boot device or insert boot media in selected boot device and press a key_".  Running the BIOS indicates "none" under the playlists by car.  Run PC doctor diagnostics check the CPU and RAM, but returns error BIOHD-2 for hard drive.

  Traded to old drive hard with a good drive from another machine and BIOS did not recognize.  Power on all cables SATA and tried all different SATA and powerconnections ports and no change.  I tried a new hard drive and the BIOS does not detect either (although I could check that drive did turn.)

  I put the original disc in another computer and BIOS detected it and car seemed fine, all the files.  But it do not start the machine.

  I can't find recovery discs. I am at a loss to know what to do next.  The BIOS might be corrupted?  How update the BIOS without an operating system that works?  Could this be the motherboard?

  Thanks in advance for any help.

  Mike

  OK, reinstalled windows and have a computer to work again!  Thanks for all your help!

• RJ45 LEDs on a PowerConnect 6224

  I am troubleshooting a few complaints from users of slow response in the network, and I try to link status lights for my PC RJ45 connections on the 6224.  All the LED right (above the RJ45 Sockets) are solid green, feel good connections (I think), but some of the left LED green flashing and some are orange flashing.  On the other switches I've used, I get a flashing orange light means that it works at the speed of 10 / 100 Mbps over gigabit.  Is this true for the 6224?  I checked all of the cables are cat-5e or cat-6 and the network link speed PC card has the value 1.0 GB full duplex, but there may be other errors in the line that is causing the downgrade link.  The 6224 user manual isn't all this useful in this so-called orange flashing indicates "power device design exceeds the predefined power allotment.

  Thank you!

  Hello

  You're right, it's on at 10/100. Page 66 downloads.dell.com/.../powerconnect-6224_user's guide_en - us.pdf

• Port Mirroring a LAG on stacked Dell PowerConnect 6248 s

  Hello

  It is possible to port mirror use as a source, a SHIFT, consisting of 4 ports (2 in each Member of a set of 6248 s PowerConnect stacked). Whenever I'm trying to add the source, using GUI, I get an error:

  Error! There not together "Type" with "Tx and Rx" error occurred in FILTER_MISSING

  This allusion is what filter?

  I can't select a spring, unit 1 or unit 2, members of the LAG, like the gui only shows them not from the ports drop.

  Thank you.

  Unfortunately, the switch is able to mirror individual ports as source ports. You can check this by trials of establishing a mirror session where the source port is not part of a LAG.

• Restart Powerconnect 6248 without disturbing the Configuration

  I apologize in advance for the entry-level position and if that's the answer elsewhere, please point me in the right direction:

  I inherited load on a network LAG / VLAN with a central 2-battery Dell switch Powerconnect 6248 functioning as a main switch and routing of traffic between the VLANs that are shared it resources.

  I want to restart this switch without losing any configuration, because I'm just to enter this network, I don't want to disrupt or rebuild the configuration.

  I can get Telnet or SSH access to the switch but now use the GUI. When I go to reboot I choose to restart the two batteries and am met with the message:

  "The unit will restart with the startup configuration, not the running configuration. Do you want to continue? »

  I had a contractor separate network restart the switch before and I don't know if it simply ignored the message and proceeded. I would like to be able to restart this switch without losing any configuration.

  My question is, I'm ok to move forward through this error message? Or do I need to configure backup to restart? What is the best way to proceed with a simple reboot of two chimneys, while maintaining the current configuration.

  Here is the procedure, I suggest you take.

  -If the running configuration is operational and you want to keep on the switch, and then save it in the startup configuration.

  -before to restart, save the configuration.

  -Keep the battery restart.

  You can then use this backup config as a reference in case something happens to the configuration of the switch. It's a good idea to take the habit of saving after all change config, before the updates of the firmware, reboot, etc.

  Here is an article that will guide you through the commands to perform these actions.

  http://Dell.to/1NPR5aY

  Hope you find it useful.

• PowerConnect M6220 ACL issues

  Hi, received a pair of blade switches PowerConnect M6220, pretty much the same as 6224

  I try to apply ACLs in interface, and I'm unable to do so.
  Here's what I'm trying to do:

  coresw (config) #access - internet-out list deny ip any 10.0.0.0 255.0.0.0
  coresw (config) #access - list on the internet permit each

  coresw (config-if-article gi1/0/17) #ip group-access internet-output

  Error when processing the ACL.

  coresw(Config-if-Gi1/0/17) #.

  <190>MAR 25 00:37:12 10.128.101.1 - 1 DRIVER [126512544]: broad_acl.c (1611) 4% ACL not applied to 134217728 port

  In this switch or on any interface on the switch, there is no other ACL.
  As you can see, it is a LCD 2 lines in the 90s, who refuses to work. Basically, what I'm trying to do is filter all local ip traffic.
  I'm doing something wrong here? According to www.dell.com/.../pwcnt_IP_ACLs.pdf , I can filter output destination.

  Any help is appreciated, thanks.

  I was able to test this on a M6220 and I can confirm the behavior you're seeing is a hardware limitation. IP based ACL cannot be applied evacuation. You should have no problem in applying the penetration.

• Reference Dell PowerConnect 3524 - "SW3P_callback_rx_frame - arp - scrapped intervention."

  Hello everyone.

  The company I work for, I test switches to see who is good and who is bad. I've already marked the switch in question as 'bad' for these mistakes - but I've never seen this error before. My colleagues have not either. Therefore, I ask the community what kind of error is what it means and whether it is potentially fixable.

  My device is a Dell PowerConnect 3524. He is currently out of warranty.

  What I did: I have deleted the startup configuration and then run the Setup Wizard. I put an IP address, gateway, and password. The rest, I left the default values. This configuration works on all switches that I have ever tested, including this model, so I think that this configuration is not serious.

  Then I plug in an ethernet cable in all ports and the other end into a very small 5 port switch that also has other trendy items above, the phone and my main computer. They all get internet, I don't think that there is a problem.

  I plug another cable in another port of the switch and the other end in a laptop sitting on top of the switch (my laptop test).

  I start ping the local firewall and run it with the "-t" parameter so it does not stop.

  It is fine for about 5-10 minutes usually. I can trade ports and others and she'll pick up ping soon and do what it is supposed to. After plugging into the wrong port, (7 or 8), I get the error "SW3P_callback_rx_frame - intervention arp - put the scrapped." and cannot pass traffic. PuTTY shows that the connection is established and transfer, but the ping is not possible.

  I am only an intern, this switch is not vital and will be sent to the "cemetery" and all my business done with switches will be. I am just curious to know what it is. Anyone know what it is and what could be done to solve the problem?

  Thank you for your time!

  I couldn't find any relevant information on this error message. With errors that occur only on specific ports and a new configuration, it really sounds as a kind of material error. Will there be another message that accompany this message? If you haven't already done so, re-flashing the firmware of the switch can help ensure that the message is not caused by an image that has become corrupt.

  http://Dell.to/1XmQxPU

• CWDM between Powerconnect 6200's

  Hello

  I try to get CWDM working between two sites in London on Dell Powerconnect 6224 and 6248 a. I have the 2 x 10 GB SFP + modules both at the back and some optical CWDM SFP + listening that are coded to dell.

  I have a link on both sides, however, cannot get any job adequate connectivity. Another post suggested that they were working with these switches before CWDM.

  I've put the transceiver diagnostic information below:
  
  Site1:
  Temperature         54.1  (oC)
  Voltage         3.293  (V)
  Current         23.3  (mA)
  Ouput Power         -2.470  (dBm)
  Input Power         -10.685  (dBm)
  Transmitter Fault         No
  Loss of Signal         No
  
  Site2:
  Temperature         50.1  (oC)
  Voltage         3.239  (V)
  Current         29.9  (mA)
  Ouput Power         -0.496  (dBm)
  Input Power         -13.747  (dBm)
  Transmitter Fault         No
  Loss of Signal         No
  
  On both sites we are seeing transmit data but no received:
  
  Site1:
  Receive Statistics  Total Bytes(Octets)         0
  Unicast Packets         0
  Multicast Packets         0
  Broadcast Packets         0
  Packets with Errors         0
  Packets Discarded         0
  
  Transmit Statistics  Total Bytes(Octets)         390208219
  Unicast Packets         50889
  Multicast Packets         140321
  Broadcast Packets         1106698
  Packets Discarded         3
  
  Site2:
  Receive Statistics  Total Bytes(Octets)         0
  Unicast Packets         0
  Multicast Packets         0
  Broadcast Packets         0
  Packets with Errors         0
  Packets Discarded         0
  
  Transmit Statistics  Total Bytes(Octets)         2346760
  Unicast Packets         0
  Multicast Packets         24674
  Broadcast Packets         0
  Packets Discarded         0
  
  Any suggestions, should CWDM SFP+ optics work in these switches?
  
  Thanks,Peter
  

  Hello

  I don't think that no matter what optical CWDM provided by Dell.

  Anyway, I managed to borrow some perspective to test with and they work very well. CWDM works on these switches...

  Peter

• Error STATSMGR - failure of the collectorGet function

  I started getting errors STATSMGR the log files excluding anyone on the core of PowerConnect 7048 of filling pile. The current firmware is 4.1.0.6 and I hesitate to upgrade the firmware after that an update of the firmware on a sharp N2048s corrupt their configuration. These manage the network and any failure would be catastrophic. Any other suggestions for clearing that issue of upgrading the firmware?

  <190>21 Jul 06:22:02 172.16.2.20 - 1 STATSMGR [237994160]: collector.c (1066) 75143% failed in function collectorGet

  Thank you!

  Sandi

  I know that you don't want to hear about the firmware, but the update of the firmware is specifically stated that this warning message is resolved in 4.2.0.4 on-site.

  http://Dell.to/1LrjXZO

  "Repeated messages in the switch connects <190>APR 28 19:39:22 10.1.208.10 - 1 STATSMGR [239558880]:

  collector.c (1066) 3445% deficiency in the function collectorGet. Resolution: SNMP walk / in contact with counters

  for CPU / vlan routing ports not supported by the platform is no longer log a warning message. «Affected platforms: 4.2 all supported platforms»

  Do you have any monitoring software on the network that could be polling the switch of these counters? You see that any performance hits on the battery? Being just a warning, I don't think that this will affect performance.

  A solution would be to change the severity of logging to not include warnings.

  # error logging in buffered memory

  the disadvantage of this would be that you wouldn't see an another warning message.

• Reference Dell Equallogic Interface errors

  Hi guys, I got a big problem here in my room. My equallogic iscsi interfaces have a lot of erros. What can be?

  

  First of all, make sure you run the latest version of FW and SANHQ table.

  Packet errors are often the cause of bad cable, bad switch ports and a misconfiguration on switch iSCSI ports.   The only way to erase the mistakes of packages on Equallogic arrays must restart the table.

  • Replacement cable between the controller port and switch port with known good cable.

  • 10 GB cables must be SFF-8472 compliant to work with 10 GB Equallogic arrays.

  • Confirm that the switch is a minimum firmware to work with Berry Equallogic en.community.dell.com/.../2661.equallogic-compatibility-matrix

  (Note: if unable to switch, you can disable protocols spanning tree on ports connect to the table).

  • Use the tech TR1017 report to verify the configuration of the switch and confirm it meets best practices.

  • Run a show of support on the switches to review port errors.   If a Powerconnect or Force10 switch then engage networks dell help examine the switch logs. If another provider, and then engage the seller to switch to help examine the switch logs.

  • Cards network host to firmware update and the latest network card driver

  • The direct link to TR1017:

  Media.Community.Dell.com/.../tr1017-v4-Network-Guidelines.pdf

  If the host Linux with Multipath.d, you may need to modify the multipath.conf file to include: tur path_checker in the devices section.

  Joe

• Request support by MD3220i - error cluster [CF]

  Buon giorno, US vs riscontro gentile e di assistenza in merito al evento following preventivo:

  The infrastruttura e nostra composed da UN MD3220i con 3 host due e R610 PowerConnect 2848 switch, da some giorno a perdere instradamento verso gli hanno begun the host Announces where the MD3220i.

  Da una prima disgnostica di message following sulla MD abbiamo rilevato it 'alert ':

  Date/time: 08/01/16 8.26.31
  Sequence number: 41599
  Type of event: 4011
  Event category: error
  Priority: critical
  Description: Virtual disk not a being preferred due to the AVT/RDAC failover
  Specific event codes: 0/0/0
  Component type: RAID Controller Module
  Location of components: enclosure 0, Slot 1
  Recorded by: Module to slot 1 RAID controller

  Raw data:
  4 d 45 a2 7f 48 03 00 00 00 00 00 00 00 00 00 4 c
  11 40 18 01 97 eb 57 00 00 00 00 00 00 00 00-9F
  00 00 00 00 01 00 00 00 22 00 00 00 22 00 00 00
  08 00 00 00 00 00 00 00 02 00 00 00 01 00 00 00
  0 a 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00
  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  01 00 00 00 00 00 01 00 00 00 00 00

  We have tried a curare infrastruttura MD, host switch e spegnere.

  After the riaccensione he message di "alert" su e scomparso totally, senza più particular if MD, recoupling outdo degli host verso MD3220i risultava Semper ad where con conseguente perdita accesso alle cartelle di rete e macchine virtuali.

  Host No. 2 dei R610 abbiamo quindi con spento 3 he risultato che dopo d manuale da console del servizio cluster it sistema e partito a funzionare senza problemi di comunicazione più correctly.

  Lato host abbiamo rilevato che some door ISCSI MD non sono più ragiugibili del (nello specifico n ° 1 of the castroni sono no door porta del MD3220i controller)

  The VLAN non sono state modificate e lato PowerConnect 2848 switch if not rilevano if.

  Current location: MD3220I senza if a host adapter solo di n ° 3 access.

  Company di MD3220i:

  He prodotto e stato nel 2010 labor-intensive, co del prodotto e scaduta it 13/12/2015.

  Re: MD3220i fuori co serial number F1QGY4J

  Buongiorno, the sto contattando by mail.

• PowerConnect 6224 VLAN config / default gateway

  Hello

  I am new to configuring a VLAN and work with DELL going on so please forgive my ignorance.

  I joined a small agency that currently has a flat structure networking including 1 6224 linked to two 5548 one is connected to three 3548 (access), and the other is connected to a server. The 6224 connects to a proxy (default gateway), and then on the Web. All devices are currently on a 192.168.78.0 24 network with ip default gateway 192.168.80.1

  We want to segment the network using two VLAN initially. VLAN 1 user "80" and vlan 1 safety '70' and I want to clarify a few things before that I try:

  1. can you stay the ip on the network switch for vlan user ex: 192.168.80.123 or should I create a vlan separate management?

  2. I know in order for the inter - vlan, the ip of the gateway routing vlan must be on the 6224 and I then have to configure a default route to the proxy. The proxy must be on one VLAN separate or could I leave on VLAN 80 and change the ip address another que.1?

  Thanks in advance.

  I did it several times myself.  You can do almost an infinite number of ways, but it will be better to stick to certain typical networking practices.  Here is the version digest readers of what would be preferable to do so.

  1 enable routing on the switch stack.

  2. make a 80 VLAN for your network 24.80.  Assign the IP 192.168.80.1 to this VLAN.  In this way, customers will now be a ".". 1' default to the network gateway, they are on.

  3 make an another VLAN 70 for your network 24.70.  Assign the IP 192.168.70.1 to this VLAN.  This will be the default gateway for the network.  Repeat for however many VLANS / networks you want to.

  4. create a separate VLAN for his own 'bubble' network between the switch and the upstream proxy server.  (Lets call him a dummy VLAN 100 with an IP range x.x.100.x 29.  It can be just a little/29 block or something or 24 if this is confusing. Configuring the ports a few ports 'access' for this VLAN for that no marked traffic pass over this network.  Set x.x.100.1 to your Proxy Server and x.x.100.2 to your switch, then make sure you have directions on both sides about where traffic should go.

  5. save your configuration so that you have to rebuild it after a reboot.  :-)

  It will be best to set your expecations about it.  You want realistic during a weekend/maintenance window.  ARP cache and other issues can make for some downtime.  In addition, there are certainly other ways to do it, but that may be hurtful on the road when you need to increase or scale.  Two years on the road someone wondered why a default gateway is on a few eccentric IP, or there are errors of routing intermentent, etc..

  Powerconnect worldwide, just be clear what is the difference between a port of "access" to the port of 'general', and are a port 'trunk '.  Conditions may be different from the Lim to make, and if one comes to tell the world of Cisco, this may be a little different.

  Finally, don't forget to come up with a good procedure for this during your maintenance window.  Come up with a good plan documented and so well thought out, when run you it, it will be nothing more than a task in office project.