12.07.2015 Views

Brocade MLX Series and Brocade NetIron XMR Diagnostic Guide ...

Brocade MLX Series and Brocade NetIron XMR Diagnostic Guide ...

Brocade MLX Series and Brocade NetIron XMR Diagnostic Guide ...

SHOW MORE
SHOW LESS
  • No tags were found...

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

5IS-ISConfiguration notesNone of the IS-IS parameters require a software reload for changes to take effect, <strong>and</strong> mostparameter changes take effect immediately. However, changes for the following parameters takeeffect only after you disable <strong>and</strong> then re-enable redistribution:• Changing the default metric.• Adding, changing, or negating route redistribution parameters.Common diagnostic scenarios• Packets are dropped during authentication mode change.Changing the authentication mode can cause packets to drop during the transition periodbecause not all of the routers are reconfigured simultaneously. During such a transition, it canbe useful to disable IS-IS authentication checking temporarily until all routers are reconfigured<strong>and</strong> the network is stable.Use the no isis auth-check comm<strong>and</strong> to disable IS-IS authentication checking on a specifiedinterface.<strong>Brocade</strong>(config)# interface ethernet 3/1<strong>Brocade</strong>(if-e10000-3/1)# no isis auth-check level-1Syntax: [no] isis auth-check [level-1 | level-2]This comm<strong>and</strong> enables <strong>and</strong> disables IS-IS authentication checking. The default is enabled <strong>and</strong>the no parameter disables authentication checking.The level-1 parameter specifies that authentication checking is enabled or disabled for Level 1Hello packets.The level-2 parameter specifies that authentication checking is enabled or disabled for Level 2Hello packets.NOTEIf either Level 1 or Level 2 are not specified, the configuration is applied to both Level 1 <strong>and</strong>Level 2.• <strong>NetIron</strong> LSPs are timed-out by its neighbors.The maximum LSP lifetime interval <strong>and</strong> the LSP refresh interval must be set so that the LSPsare refreshed before the maximum LSP lifetime interval expires; otherwise, the <strong>Brocade</strong>device's originated LSPs may be timed-out by its neighbors.To prevent a neighbor from timing-out LSPs, give the LSP refresh interval a shorter setting thanthat of the maximum LSP lifetime interval. The LSP refresh interval is the maximum number ofseconds the <strong>Brocade</strong> device waits between sending updated LSPs to its IS-IS neighbors. Theinterval can be from 1 through 65535 seconds. The default is 900 seconds.For example, to change the LSP refresh interval to 20000 seconds, enter a comm<strong>and</strong> similarto the following example.<strong>Brocade</strong>(config-isis-router)#lsp-refresh-interval 20000Syntax: [no] lsp-refresh-interval The parameter specifies the maximum refresh interval <strong>and</strong> can be from 1 through65535 seconds. The default is 900 seconds (15 minutes).174 <strong>Brocade</strong> <strong>MLX</strong> <strong>Series</strong> <strong>and</strong> <strong>Brocade</strong> <strong>NetIron</strong> <strong>XMR</strong> <strong>Diagnostic</strong> <strong>Guide</strong>53-1002426-02

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!