[f-nsp] foundry-nsp Digest, Vol 94, Issue 10

[Nick Jumonville]

It is most likely a software problem, try to upgrade the card, then reboot
it.  It might need the correct mbridge, I have seen this happen before.

-Nick Jumonville

On Thu, Nov 18, 2010 at 9:00 AM, <foundry-nsp-request at puck.nether.net>wrote:

> Send foundry-nsp mailing list submissions to
>        foundry-nsp at puck.nether.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
>        http://puck.nether.net/mailman/listinfo/foundry-nsp
> or, via email, send a message with subject or body 'help' to
>        foundry-nsp-request at puck.nether.net
>
> You can reach the person managing the list at
>        foundry-nsp-owner at puck.nether.net
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of foundry-nsp digest..."
>
>
> Today's Topics:
>
>   1. Re: New MG8 switch blade  BIMG8-10Gx4-v6-A
>      CARD_STATE_INTERACTIVE (Remco Bressers)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 18 Nov 2010 16:44:08 +0100
> From: Remco Bressers <remco at signet.nl>
> To: foundry-nsp at puck.nether.net
> Subject: Re: [f-nsp] New MG8 switch blade       BIMG8-10Gx4-v6-A
>        CARD_STATE_INTERACTIVE
> Message-ID: <4CE549C8.7060601 at signet.nl>
> Content-Type: text/plain; charset=ISO-8859-1
>
> What happens if you login to the card itself (# rconsole 2) and reboot
> the thing? You should see the boot log and reason why the card won't
> work. Are the software versions OK?
>
>
> --
> Regards,
> Signet bv
>
>
> Remco Bressers
>
> T 040 - 707 4 907
> F 040 - 707 4 909
> E rbressers at signet.nl
>
>
>
> On 11/18/2010 03:49 PM, Dominic Douglas wrote:
> > Hi Justin,
> >
> > I saw your problem with the XMR 10G blade, but the problem is harder
> > then I expected.
> >
> > Lets go:
> >
> > 1. Removed blade from slot 2.
> > 2. Sh mod:
> > S2: Configured as BIMG8-10Gx4-v6 4-port 10GbE IPv4/v6 Module
> >
> > Log:
> > Nov 18 14:20:17:N:Module was removed from slot 2
> >
> > But the slot is already configured with the right module. I will remove
> > the config and reconfigure it:
> >
> > 3. (config)#no mod 2 bimg8-v6-10g-4-port
> > 4. (config)#module 2 bimg8-v6-10g-4-port
> > 5. Sh mod:
> > S2: Configured as BIMG8-10Gx4-v6 4-port 10GbE IPv4/v6 Module
> >
> > 6. Insert module:
> >
> > S2: Invalid Module  CARD_STATE_DOWN (7)  (previous state =
> > CARD_STATE_SW_LOADED)
> >
> > End after the module startup:
> >
> > S2: BIMG8-10Gx4-v6-A 4-port 10GbE IPv4/v6 Module (OACL)
> > CARD_STATE_INTERACTIVE    0
> >
> > It might be a bigger problem. This (new) module is an A module:
> >
> > BIMG8-10Gx4-v6-A
> >
> > Our other modules:
> >
> > M1 (upper): BIMG8-MR Management Module     Active
> > M2 (lower):
> > F1: BIMG8-SFM Switch Fabric Module         Active
> > S1:
> > S2: BIMG8-10Gx4-v6-A 4-port 10GbE IPv4/v6 Module (OACL)
> > CARD_STATE_INTERACTIVE    0
> > S3:
> > S4:
> > S5:
> > S6:
> > S7: BIMG8-1Gx40-SFP-v6 40-port 1 GbE IPv4/v6 Module (IPv6+OACL)
> > CARD_STATE_UP    40
> >
> >
> > Extra logging:
> >
> > Nov 18 14:26:07:N:Module 2 is reset by mgmt (reason: boot to interactive
> > mode)
> > Nov 18 14:25:38:N:Module was inserted to slot 2
> > Nov 18 14:20:17:N:Module was removed from slot 2
> > Nov 18 13:36:35:N:Module 2 is reset by mgmt (reason: boot to interactive
> > mode)
> > Nov 18 13:36:10:N:Module 2 is reset by mgmt (reason: CLI command)
> > Nov 18 13:24:17:N:Module 2 is reset by mgmt (reason: boot to interactive
> > mode)
> > Nov 18 13:23:48:N:Module 2 is reset by mgmt (reason: lp sync during
> booting)
> > Nov 18 13:22:19:N:Module was inserted to slot 2
> >
> >
> > The module is forced to interactive mode by the management. It might be
> > a software problem..
> >
> > Kind regards,
> >
> > Dominic
> >
> >
> >
> >
> >
> >
> >
> > On Thu, Nov 18, 2010 at 3:17 PM, Justin Suyk - Signet BV
> > <jsuyk at signet.nl <mailto:jsuyk at signet.nl>> wrote:
> >
> >     Hi,
> >
> >     We had to remove the blade before changing the config.
> >     So :
> >
> >     1. remove module
> >     2. remove the blade config (no module ... bi-...)
> >     3. config the blade
> >     4. insert the blade
> >     5. get a beer
> >
> >
> >     Regards,
> >     Signet bv
> >
> >
> >     Justin Suyk
> >
> >     T 040 - 707 4 907
> >     F 040 - 707 4 909
> >     Kvk 17089930
> >
> >
> >
> >     On 11/18/2010 03:11 PM, Dominic Douglas wrote:
> >>
> >>     *Hi All,
> >>
> >>     We do have a problem with one of our MG8 switches. We've added a
> >>     new BIMG8-10Gx4-v6-A blade, but after configuration the blade will
> >>     not recover from CARD_STATE_INTERACTIVE.
> >>
> >>     S2: BIMG8-10Gx4-v6-A 4-port 10GbE IPv4/v6 Module (OACL)
> >>     CARD_STATE_INTERACTIVE    0   000c.db27.4560
> >>
> >>     Steps taken:
> >>
> >>     1. Reset module.
> >>     2. Set type to the slot port.
> >>     3. Turn on/off module.
> >>
> >>     Unfortunately we can't find any logs about the new blade, only the
> >>     current state: **CARD_STATE_INTERACTIVE.
> >>
> >>     Kind regards,
> >>
> >>     Dominic
> >>     **
> >>
> >>     *
> >>
> >>
> >>     _______________________________________________
> >>     foundry-nsp mailing list
> >>     foundry-nsp at puck.nether.net <mailto:foundry-nsp at puck.nether.net>
> >>     http://puck.nether.net/mailman/listinfo/foundry-nsp
> >
> >
> >
> >
> > _______________________________________________
> > foundry-nsp mailing list
> > foundry-nsp at puck.nether.net
> > http://puck.nether.net/mailman/listinfo/foundry-nsp
>
>
> ------------------------------
>
> _______________________________________________
> foundry-nsp mailing list
> foundry-nsp at puck.nether.net
> http://puck.nether.net/mailman/listinfo/foundry-nsp
>
> End of foundry-nsp Digest, Vol 94, Issue 10
> *******************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/foundry-nsp/attachments/20101118/cbe2af00/attachment.html>