<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div>In 5.6 they added the ability to remove the config while the card is in interactive mode. </div><div><br></div><div></div><blockquote type="cite"><div>Line Module Configuration Deletion in Interactive Boot Mode</div><div>Operational enhancements are made so that line module configurations can be deleted when a module is in interactive boot mode.</div></blockquote><div><br></div><div>Regards,</div><div>Mike</div><div><br></div><br><div><div>On Mar 17, 2014, at 7:11 PM, Cameron Daniel <<a href="mailto:cdaniel@nurve.com.au">cdaniel@nurve.com.au</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">You also need to make sure you remove the module line from the config while the LP slot is empty, it won't let you do it if you've already inserted the new card.<br><br>Cameron<br><br>On 2014-03-18 11:49 am, Mike Tindle wrote:<br><blockquote type="cite">Not that I’ve discovered. Unless it’s an identical card type swap,<br>it’s not possible. Even physically identical port layouts (Gen1<br>4x10g vs Gen1.1 4x10g) won’t work. The new LP won’t come up until<br>you physically remove the card and “no” out the relevant module<br>line in the config. When you do that, it blasts out any interface<br>config that was associated with the card.<br>This may be changed in newer NetIron versions. I haven’t tried it<br>since 5.2.<br>Regards,<br>Mike<br>On Mar 17, 2014, at 5:26 PM, Josh Farrelly<br><<a href="mailto:Josh.Farrelly@manukau.ac.nz">Josh.Farrelly@manukau.ac.nz</a>> wrote:<br><blockquote type="cite">Hi all<br>Just wanted to check if anyone knew whether the configuration<br>that’s already applied to interfaces stays valid after a line card<br>is swapped with another.<br>In this example I am wanting to swap a “BR-MLX-10Gx24-DM 24-port<br>10GbE Module” with a “NI-MLX-10Gx8-M 8-port 10GbE (M) Module”<br>but I want the relevant configuration for each port to stay exactly<br>the same.<br>I am assuming so, but thought best to check before proceeding. I can<br>assume we’d only run in to issues where moving to a card with less<br>interfaces (e.g. as the startup-config was applied, no matching<br>interface for eth1/9 on an 8-port card would be found).<br>Kind Regards,<br>JOSH FARRELLY<br>_Infrastructure Architect, ICTS._<br>Manukau Institute of Technology<br>_______________________________________________<br>foundry-nsp mailing list<br><a href="mailto:foundry-nsp@puck.nether.net">foundry-nsp@puck.nether.net</a><br>http://puck.nether.net/mailman/listinfo/foundry-nsp [1]<br></blockquote>*----------- H U R R I C A N E - E L E C T R I C ---------->><br>| Mike Tindle | Senior Network Engineer | <a href="mailto:mtindle@he.net">mtindle@he.net</a><br>| ASN 6939 | <a href="http://www.he.net">http://www.he.net</a> [2] | 510-580-4126<br>*--------------------------------------------------->><br>Links:<br>------<br>[1] <a href="http://puck.nether.net/mailman/listinfo/foundry-nsp">http://puck.nether.net/mailman/listinfo/foundry-nsp</a><br>[2] <a href="http://www.he.net">http://www.he.net</a><br>_______________________________________________<br>foundry-nsp mailing list<br><a href="mailto:foundry-nsp@puck.nether.net">foundry-nsp@puck.nether.net</a><br>http://puck.nether.net/mailman/listinfo/foundry-nsp<br></blockquote>_______________________________________________<br>foundry-nsp mailing list<br><a href="mailto:foundry-nsp@puck.nether.net">foundry-nsp@puck.nether.net</a><br>http://puck.nether.net/mailman/listinfo/foundry-nsp</blockquote></div><br><div apple-content-edited="true">
<span class="Apple-style-span" style="border-collapse: separate; border-spacing: 0px;"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; border-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">*----------- H U R R I C A N E - E L E C T R I C ---------->><br>| Mike Tindle | Senior Network Engineer | <a href="mailto:mtindle@he.net">mtindle@he.net</a><br>| ASN 6939 | <a href="http://www.he.net">http://www.he.net</a> | 510-580-4126<br>*--------------------------------------------------->></div></span></div></span>
</div>
<br></body></html>