Force10 E300 Terascale question

_______________________________________________
force10-nsp mailing list
force10-nsp <at> puck.nether.net
https://puck.nether.net/mailman/listinfo/force10-nsp

how to show Layer-3 VLAN interface traffics?

Hi,

Any one know how to show Layer-3 VLAN interface traffic?

For physical interface (no matter it is Layer-2, Layer-3 or
port-channel), we can use such as "show interface ten 0/1" to see the
bandwidth usage of the interface (bit per second).

But "show interface vlan xxx" does not have bit per second information
like what we can get from Cisco switch.

Is there any command can display a Layer-3 VLAN interface bandwidth
usage on a force10 switch? (specifically a S4810 switch.)

Thanks in advance,
--
Michel~

[Question] KERN-2-INT: sys_ioctl: _IOWR('u',12,269)

_______________________________________________
force10-nsp mailing list
force10-nsp <at> puck.nether.net
https://puck.nether.net/mailman/listinfo/force10-nsp

LACP drops simultaneously across multiple switches/products/versions

We're having a strange issue where LACP will bounce on multiple switches
simultaneously, typically several times in a row.

We previously would see this on our S50n stack when it was our core switch,
but it hadn't happened in over a year.  Now that we have a C300 in addition to
the S50n stack we've seen it 5 times in 4 days.

What we've seen so far is two LACP groups from the C300 to our only two S55s
will bounce, then all the LACP groups on the C300 will bounce as well as all
the LACP groups on the S50n stack.

We don't get any CPU watchdog notices, and traces don't show that the LACP
process has restarted.

Has anyone experienced these types of problems?  I have an open TAC case
currently but want to get others experiences here.

-Doug

_______________________________________________
force10-nsp mailing list
force10-nsp <at> puck.nether.net
https://puck.nether.net/mailman/listinfo/force10-nsp

S50n w/ 10ge Input CRCs/Discards

We're trying to deploy 10ge upstream to our S50n stack (read, all the port 0
modules are stacking modules).  We're seeing a decent amount of Input
CRCs/Discards and can't get the link to go > ~120Mbps.  We've replaced
*everything* in this link (other than the upstream RSP) -- fiber, 10ge module,
XFPs and are still seeing this problem.  Flow control is off on both ends; CPU
seems fairly low (<12%).

Any ideas on what might be going on here?  Anyone else having problems w/ 10GE
on S50?

-Doug

_______________________________________________
force10-nsp mailing list
force10-nsp <at> puck.nether.net
https://puck.nether.net/mailman/listinfo/force10-nsp

IPv6 options

I'm trying to put together a matrix of supported IPv6 features for various network and security hardware
and one of the vendors that I no longer have access to equipment to test with is Force10.  Can anyone tell me if
they know, or are currently using any of the features listed in this matrix?

http://tech.buraglio.com/2011/03/ipv6-features-matrix-for-network.html

nb

---
Nick Buraglio   
Network Engineer
University of Illinois CITES / ICCN
GPG key 0x2E5B44F4
Phone: 217.689.4254
buraglio <at> illinois.edu

Roll-call: S60s

Anyone deploying S60's in significant quantity yet? Would love to know
if you are experiencing mysterious reboots, too, because we sure are!

-M

Rate limit ICMP on control plane traffic

Hey gang --

I'm wondering if anyone on the list has implemented a control plane
rate-limiting solution for ICMP similar to the Cisco one outlined in
"draft-ietf-opsec-protect-control-plane"? Just wondering if there is
an analog on Force10 kit.

http://tools.ietf.org/html/draft-dugal-opsec-protect-control-plane-02#appendix-A

Thanks,

-M

MAC table update problems with PBR applied E1200

Hi All,

I do have a case open with Force10 support on this, but it's been a long 
standing issue and I've gone so far as to re-architect our rather 
heterogeneous network to maintain a force10-only network path between 
our various F5s and ServerIrons to stop vendor finger-pointing, so I'm 
interested to hear if anyone else is experiencing something similar.

In a nutshell, the MAC address table isn't getting updated on an E1200 
terascale that has PBR ip-redirect lists on all of my vlans.  I can make 
virtual IPs (whose actual mac address moves with the IP's home) fail 
over from systems connected to the stated E1200 to a C300 that's doing 
only layer 2 switching, but failing back to the original loadbalancers 
doesn't work.  No link-state events necessarily occur when they move, 
which may be part of why it seems to ignore the gratuitous ARPs.  I need 
to clear the arp cache on the E1200 so it will flood and relearn to 
restore connectivity.

I have the basic things like "mac-address-table station-move 
refresh-arp" and "arp learn-enable" set. I'm aware of the various PBR 
fixes that have been made lately, and I've recently taken the downtime 
to update to the latest FTOS (8.4.2.1) and enable the microcode ipv4-lda 
to no effect (which also removes IPv6 support ... good thing I only had 
that in testing and not production yet).  So I'm appealing to a larger 
audience to see if anyone has had similar experiences, or can recommend 
some way to redesign around this.  I'm not in a position to pitch-fork 
these particular boxes yet, and PBR is important for my ability to get 
line-rate connectivity between our public and non-public IP spaces 
without a NAT bottleneck.

Thanks,

  - mike

Re: Kern Mem

_______________________________________________
force10-nsp mailing list
force10-nsp <at> puck.nether.net
https://puck.nether.net/mailman/listinfo/force10-nsp

Kern Mem

Hi All,

What's going on with my switch ?

Jan 26 11:42:24.538 UTC: %STKUNIT0-M:CP %KERN-2-INT: soc_l2x_thread: DMA failed: Operation failed
Jan 26 11:42:24.538 UTC: %STKUNIT0-M:CP %KERN-2-INT: _soc_xgs3_mem_dma: L2_ENTRY.ipipe0 failed(NAK)
Jan 26 11:42:23.429 UTC: %STKUNIT0-M:CP %KERN-2-INT: soc_l2x_thread: DMA failed: Operation failed
Jan 26 11:42:23.428 UTC: %STKUNIT0-M:CP %KERN-2-INT: _soc_xgs3_mem_dma: L2_ENTRY.ipipe0 failed(NAK)
Jan 26 11:42:22.189 UTC: %STKUNIT0-M:CP %KERN-2-INT: soc_l2x_thread: DMA failed: Operation failed
Jan 26 11:42:22.188 UTC: %STKUNIT0-M:CP %KERN-2-INT: _soc_xgs3_mem_dma: L2_ENTRY.ipipe0 failed(NAK)
Jan 26 11:42:20.848 UTC: %STKUNIT0-M:CP %KERN-2-INT: soc_l2x_thread: DMA failed: Operation failed
Jan 26 11:42:20.848 UTC: %STKUNIT0-M:CP %KERN-2-INT: _soc_xgs3_mem_dma: L2_ENTRY.ipipe0 failed(NAK)
Jan 26 11:42:19.630 UTC: %STKUNIT0-M:CP %KERN-2-INT: soc_l2x_thread: DMA failed: Operation failed
Jan 26 11:42:19.630 UTC: %STKUNIT0-M:CP %KERN-2-INT: _soc_xgs3_mem_dma: L2_ENTRY.ipipe0 failed(NAK)
Jan 26 11:42:18.535 UTC: %STKUNIT0-M:CP %KERN-2-INT: soc_l2x_thread: DMA failed: Operation failed
Jan 26 11:42:18.534 UTC: %STKUNIT0-M:CP %KERN-2-INT: _soc_xgs3_mem_dma: L2_ENTRY.ipipe0 failed(NAK)
Jan 26 11:42:17.210 UTC: %STKUNIT0-M:CP %KERN-2-INT: soc_l2x_thread: DMA failed: Operation failed
Jan 26 11:42:17.209 UTC: %STKUNIT0-M:CP %KERN-2-INT: _soc_xgs3_mem_dma: L2_ENTRY.ipipe0 failed(NAK)
Jan 26 11:42:16.109 UTC: %STKUNIT0-M:CP %KERN-2-INT: soc_l2x_thread: DMA failed: Operation failed
Jan 26 11:42:16.109 UTC: %STKUNIT0-M:CP %KERN-2-INT: _soc_xgs3_mem_dma: L2_ENTRY.ipipe0 failed(NAK)
Jan 26 11:42:14.807 UTC: %STKUNIT0-M:CP %KERN-2-INT: soc_l2x_thread: DMA failed: Operation failed
Jan 26 11:42:14.806 UTC: %STKUNIT0-M:CP %KERN-2-INT: _soc_xgs3_mem_dma: L2_ENTRY.ipipe0 failed(NAK)
Jan 26 11:42:13.609 UTC: %STKUNIT0-M:CP %KERN-2-INT: soc_l2x_thread: DMA failed: Operation failed

sh mem

    Statistics On Unit 0 Processor
     ===========================
   Total(b)      Used(b)       Free(b)      Lowest(b)      Largest(b)
   268435456       2367012     266068444    266051880    266068444

      CPU Statistics Of Unit 0 
     =======================================

CPU utilization for five seconds: 0%/0%; one minute: 4%; five minutes: 3%
PID        Runtime(ms)    Invoked       uSecs     5Sec   1Min   5Min  TTY       Process
0x4293e000          10           1       10000    0.00%   0.00%    0.00%   0            POEAgt
0x4292a000     2901770      290177       10000    0.00%   0.00%    0.00%   0           diagagt
0x42916000           0           0           0    0.00%   0.00%    0.00%   0          debugagt

Kabayan