[f-nsp] Port state blocking?

[Chuck Ufarley]

I swear, I've done this.  Multiple cables, multiple connected switches,
multiple connected computers, and multiple ancillary line cards.  Even a
second chassis.  Everything works, *as long as this WSM6-1 isn't involved.*
Other WSM6-1s: yes.  This one: no.


I really appreciate everyone's help, but I've tried everything in this
thread, several times.  I think the card is bad.  I can't figure out how, or
why, but I think it's bad.


Thanks again.


On Tue, Feb 24, 2009 at 7:53 PM, Niels Bakker
<niels=foundry-nsp at bakker.net>wrote:

> * markentime at gmail.com (Chuck Ufarley) [Fri 20 Feb 2009, 18:55 CET]:
>
>> This might be a silly question, but I can't get a port to come up on a
>> ServerIron.  I enabled the interface and connected it properly to a
>> FES-X2402 switch, but the J-B16GC and the J-B2Gx ports just won't come up
>> and forward.  The cards have worked in other configs, but I can't get
>> anything to come out of "blocking" mode.  Here are the shows (any help
>> greatly appreciated):
>>
> [..]
>
>> ServerIronGT E-1#sho int e 4/9
>> GigabitEthernet4/9 is down, line protocol is down
>>
>
> Your port is down.  The interface, the cable or the other side is broken.
>  Test with different patch cables, a different port on this SI and different
> equipment on the other side, e.g. a laptop.
>
> And this:
>
>>  Member of L2 VLAN ID 1, port is untagged, port state is BLOCKING
>>
>
> is because the port is enabled but down, not due to your configuration.
>
> Is the FESX side set for autonegotiation?  Unless you used a crossover
> cable you need auto-MDI/MDIX.
>
>
>        -- Niels.
>
> --
> _______________________________________________
> foundry-nsp mailing list
> foundry-nsp at puck.nether.net
> http://puck.nether.net/mailman/listinfo/foundry-nsp
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/foundry-nsp/attachments/20090225/ee15cf51/attachment.html>