Glenn,
In a couple of cases that I have worked in the past, I have seen
flowcontrol issues from a Foundry Big Iron switch. These were typically
resolved by setting the switchport to default on the GB interface. I am
not a Foundry expert and do not know the commands to do this. However,
setting the GB port to default has solved this problem in the past in a
few of the cases that I have had.
-----Original Message-----
From: Philip Boyle [mailto:philip.boyle@eircom.net]
Sent: Tuesday, March 28, 2006 11:03 AM
To: Glenn Walker
Cc: toasters(a)mathworks.com
Subject: Re: Flow Control Query
Hi Glenn,
Thanks for the response. I'd seen a forum posting regarding the
'transmit desired' config options, however, the foundry kit we have only
supports either 'flowcontrol' or 'no flowcontrol'.
We're going to open a case with Foundry. Given we have this working
using fibre, I can only imagine it's a possible hardware incompatability
issue.
Thanks alot for replying.
Regards,
Philip
On Monday 27 March 2006 18:31, Glenn Walker wrote:
> eircom net email protector: Modified this message.
>
> | Generic modifications by safety-net.
> | Details:
> |
> |https://emailprotector.eircom.net/m?i=x/DMVFsb_LS015ygR,RCgighHsCQ@ma
> |ilav
> |as00
>
> If the filer is set to full (which it is) then the problem lies with
> the switch (in every case I've ever seen).
>
> On the switch, the flowcontrol should be set to 'transmit desired' and
> 'receive desired'. Otherwise, the filer will accept whatever the
> switch is set to during the negotiation.
>
> Typically, the Cisco default is 'transmit desired', which forces the
> filer into 'receive' mode - meaning the switch can tell the filer to
> stop sending frames, but the filer cannot tell the switch to 'pause'.
>
> However, I've never seen a Foundry switch have a flow control setting
> in the past - if I recall, they did not support it's configuration.
> I'd be very interested in knowing what Foundry means by 'flow control
> enabled' - is that send? receive? Both??
>
> Glenn
>
> ________________________________
>
> From: owner-toasters(a)mathworks.com on behalf of Philip Boyle
> Sent: Mon 3/27/2006 10:56 AM
> To: toasters(a)mathworks.com
> Subject: Flow Control Query
>
>
>
> Hi guys,
>
> Have any of you had issues with the network interface on a filer not
> negociating to full flowcontrol?
>
> I'm seeing the issue using gigE dual port cards on the filer
> connecting back into a jet core foundry switch Gig Copper Module.
> Filer is running ONTAP 7.0.4.
>
> Interface is fine:
>
> e9: flags=848043<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
> ether xxxxxxxxxxx (auto-1000t-fd-up) flowcontrol full
> trunked vifbxx
>
> Switch setup is fine:
>
> GigabitEthernetx/x is up, line protocol is up
> Hardware is GigabitEthernet, address is xxxxxxxxxx (bia xxxxxxxxxx)
> Configured speed auto, actual 1Gbit, configured duplex fdx, actual
fdx
> Member of Lx VLAN ID xxx, port is untagged, port state is FORWARDING
> STP configured to ON, priority is level0, flow control enabled
>
> ifstat shows flowcontrol set to none :-(
>
> ifstat e9
> LINK_INFO
> Current state: up | Up to downs: 9 | Auto:
> on Speed: 1000m | Duplex: full | Flowcontrol:
> none
>
>
> Potential hardware compatability issue.........?
>
> Note, mirrored setup using fibre cards/ports works fine.
>
> The fibre card is:
> 1000sx-fd
>
> gigE card is:
> 1000t-fd
>
> Thanks,
> Philip
>
>
>
>
>
>
>
>
>
> ------------------
> Philip Boyle
> eircom net systems
>
> philip.boyle(a)eircom.net
> tel: +353 1 701 0921
> mob: +353 85 1744 354
--
------------------
Philip Boyle
eircom net systems
philip.boyle(a)eircom.net
tel: +353 1 701 0921
mob: +353 85 1744 354