<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=windows-1256">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">If you want the output to look similar to a cisco ping, add *<b>brief</b>* to the end of your cmd.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">ping x.x.x.x c 1000 brief
<o:p></o:p></span></b></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Sending 1000, 16-byte ICMP Echo to X.X.X.X, timeout 5000 msec, TTL 64<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Type Control-c to abort<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Success rate is 100 percent (1000/1000), round-trip min/avg/max=1/1/3 ms.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:18.0pt;font-family:"Arial","sans-serif";color:#EE2526"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#EE2526">-matt</span><span style="font-size:18.0pt;font-family:"Arial","sans-serif";color:#EE2526"><br>
<br>
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> foundry-nsp [mailto:foundry-nsp-bounces@puck.nether.net]
<b>On Behalf Of </b>Greg<br>
<b>Sent:</b> Thursday, May 09, 2013 5:07 AM<br>
<b>To:</b> Rajesh Singh<br>
<b>Cc:</b> foundry-nsp@puck.nether.net<br>
<b>Subject:</b> Re: [f-nsp] Extending Ping<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">Use the count option, e.g. <b>ping 127.0.0.1 count 10000</b><o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal">if you want to skip DNS resolution use num option, e.g. <b>ping 127.0.0.1 count 10000 num</b><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">HTH,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Gregory<o:p></o:p></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On 9 May 2013 09:29, Rajesh Singh <<a href="mailto:Rajesh.Singh@admedia.ae" target="_blank">Rajesh.Singh@admedia.ae</a>> wrote:<o:p></o:p></p>
<p class="MsoNormal">Hi,<br>
<br>
Good day<br>
<br>
Do any one know how to execute extended ping in brocade ? like in cisco we use ping ip with the source and destination ip.<br>
<br>
cheeers<br>
<br>
Rajesh Singh,<br>
ÑÇÌíÔ ÓäÌ<br>
Sr. Network Engineer,<br>
ãåäÏÓ ÔÈßÇÊ Ãæá<br>
Abu Dhabi Media<br>
<br>
<br>
<a href="mailto:rajesh.singh@admedia.ae">rajesh.singh@admedia.ae</a> <a href="http://www.admedia.ae" target="_blank">www.admedia.ae</a><br>
<br>
________________________________________<br>
From: foundry-nsp [<a href="mailto:foundry-nsp-bounces@puck.nether.net">foundry-nsp-bounces@puck.nether.net</a>] on behalf of David Hubbard [<a href="mailto:dhubbard@dino.hostasaurus.com">dhubbard@dino.hostasaurus.com</a>]<br>
Sent: Thursday, May 09, 2013 3:33 AM<br>
To: <a href="mailto:foundry-nsp@puck.nether.net">foundry-nsp@puck.nether.net</a><br>
Subject: Re: [f-nsp] Experience with 5.4.00c on XMR?<br>
<br>
We're running 5400c on two MLXe 400's with 4x10G cards and 24x1g; mr2 management and the -x series cards (1 mil route in hardware). Not doing anything terribly exciting, full bgp feeds from four upstreams, ospf on the inside, ipv4 and ipv6. Only couple things
that have really bugged me so far:<br>
<br>
1) The management port is completely useless, and this isn't a 5400c code-specific issue from what I understand. The problem is you can't hadd the management port to a management vrf, so you can't do things like routes specific to the management port, forcing
you to waste a line card port for management functions unless your management network can work without routes and the vrf security isn't necessary.<br>
<br>
2) The "ipv6 nd reachable-time" has a bug where it accepts a value in seconds but the show interface output tells you milliseconds; i.e. 900 seconds shows as 900 milliseconds but the bug is that it really is 900 seconds, so the command is successful but the
display output is wrong.<br>
<br>
3) If you enable "dampening" under "router bgp" you will only enable dampening for ipv4. You have to go into address-family ipv6 unicast explicitly and enable it there for dampening to be enabled for ipv6.<br>
<br>
4) The docs don't tell you this, but the "ipv6 nd ra-interval" command actually uses a randomized value of 0.5 to 1.5 times the value you enter, per RFC 4861, so don't be alarmed when the show interface output gives you numbers that are different than expected.<br>
<br>
David<br>
<br>
> -----Original Message-----<br>
> From: foundry-nsp<br>
> [mailto:<a href="mailto:foundry-nsp-bounces@puck.nether.net">foundry-nsp-bounces@puck.nether.net</a>] On Behalf Of<br>
> Youssef Bengelloun-Zahr<br>
> Sent: Wednesday, May 08, 2013 5:39 PM<br>
> To: Brad Fleming<br>
> Cc: <a href="mailto:foundry-nsp@puck.nether.net">foundry-nsp@puck.nether.net</a><br>
> Subject: Re: [f-nsp] Experience with 5.4.00c on XMR?<br>
><br>
> Hello Brad,<br>
><br>
> We have been through all subversions (a and b). Mainly have<br>
> been hit by some nasty SSH bugs that TAC identified and<br>
> corrected in c version. We are planning an upgrade soon.<br>
><br>
> We have been running 540 on our backbone (MLXe-4 with HSF,<br>
> 4x10G and 24x1G / CER-RT) for a year now. It's been good for us.<br>
><br>
> Don't know what your environnement / expectations are. What<br>
> are you running now ? Could you elaborate ?<br>
><br>
> Best.<br>
><br>
><br>
><br>
> Le 8 mai 2013 à 23:17, Brad Fleming <<a href="mailto:bdflemin@gmail.com">bdflemin@gmail.com</a>> a écrit :<br>
><br>
> > Anyone on the list have experience running IronWare 5.4.00c<br>
> on XMR4000s with high capacity switch fabs, 1x20G, and 4x10G<br>
> line cards? We're planning software updates for the summer<br>
> and that looks like a reasonably deep release but it's only<br>
> been on the street for about 6 weeks. Just wondering if<br>
> anyone has experiences either way regarding this software<br>
> release. Thanks in advance!<br>
> > _______________________________________________<br>
> > foundry-nsp mailing list<br>
> > <a href="mailto:foundry-nsp@puck.nether.net">foundry-nsp@puck.nether.net</a><br>
> > <a href="http://puck.nether.net/mailman/listinfo/foundry-nsp" target="_blank">
http://puck.nether.net/mailman/listinfo/foundry-nsp</a><br>
><br>
> _______________________________________________<br>
> foundry-nsp mailing list<br>
> <a href="mailto:foundry-nsp@puck.nether.net">foundry-nsp@puck.nether.net</a><br>
> <a href="http://puck.nether.net/mailman/listinfo/foundry-nsp" target="_blank">http://puck.nether.net/mailman/listinfo/foundry-nsp</a><br>
><br>
<br>
_______________________________________________<br>
foundry-nsp mailing list<br>
<a href="mailto:foundry-nsp@puck.nether.net">foundry-nsp@puck.nether.net</a><br>
<a href="http://puck.nether.net/mailman/listinfo/foundry-nsp" target="_blank">http://puck.nether.net/mailman/listinfo/foundry-nsp</a><br>
---------------------------------------------------------------------------------------<br>
DISCLAIMER<br>
This message (including any attachments) is confidential and intended solely for the person or organization to whom it is addressed. It may contain privileged and confidential information. If you are not the intended recipient, you should not copy, distribute
or take any action in reliance on it. If you have received this message in error, please notify us immediately by telephoning or E-mailing the sender. This footnote also confirms that this E-mail message has been scanned for the presence of computer viruses.<br>
---------------------------------------------------------------------------------------<br>
Please consider the environment before printing this email<br>
<br>
_______________________________________________<br>
foundry-nsp mailing list<br>
<a href="mailto:foundry-nsp@puck.nether.net">foundry-nsp@puck.nether.net</a><br>
<a href="http://puck.nether.net/mailman/listinfo/foundry-nsp" target="_blank">http://puck.nether.net/mailman/listinfo/foundry-nsp</a><o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</body>
</html>