ping [ip address] count [number of pings] On May 9, 2013, at 2:29 AM, Rajesh Singh <[email protected]> wrote:
> Hi, > > Good day > > Do any one know how to execute extended ping in brocade ? like in cisco we > use ping ip with the source and destination ip. > > cheeers > > Rajesh Singh, > راجيش سنج > Sr. Network Engineer, > مهندس شبكات أول > Abu Dhabi Media > > > [email protected] www.admedia.ae > > ________________________________________ > From: foundry-nsp [[email protected]] on behalf of David > Hubbard [[email protected]] > Sent: Thursday, May 09, 2013 3:33 AM > To: [email protected] > Subject: Re: [f-nsp] Experience with 5.4.00c on XMR? > > 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: > > 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. > > 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. > > 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. > > 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. > > David > >> -----Original Message----- >> From: foundry-nsp >> [mailto:[email protected]] On Behalf Of >> Youssef Bengelloun-Zahr >> Sent: Wednesday, May 08, 2013 5:39 PM >> To: Brad Fleming >> Cc: [email protected] >> Subject: Re: [f-nsp] Experience with 5.4.00c on XMR? >> >> Hello Brad, >> >> We have been through all subversions (a and b). Mainly have >> been hit by some nasty SSH bugs that TAC identified and >> corrected in c version. We are planning an upgrade soon. >> >> We have been running 540 on our backbone (MLXe-4 with HSF, >> 4x10G and 24x1G / CER-RT) for a year now. It's been good for us. >> >> Don't know what your environnement / expectations are. What >> are you running now ? Could you elaborate ? >> >> Best. >> >> >> >> Le 8 mai 2013 à 23:17, Brad Fleming <[email protected]> a écrit : >> >>> Anyone on the list have experience running IronWare 5.4.00c >> on XMR4000s with high capacity switch fabs, 1x20G, and 4x10G >> line cards? We're planning software updates for the summer >> and that looks like a reasonably deep release but it's only >> been on the street for about 6 weeks. Just wondering if >> anyone has experiences either way regarding this software >> release. Thanks in advance! >>> _______________________________________________ >>> foundry-nsp mailing list >>> [email protected] >>> http://puck.nether.net/mailman/listinfo/foundry-nsp >> >> _______________________________________________ >> foundry-nsp mailing list >> [email protected] >> http://puck.nether.net/mailman/listinfo/foundry-nsp > > _______________________________________________ > foundry-nsp mailing list > [email protected] > http://puck.nether.net/mailman/listinfo/foundry-nsp > --------------------------------------------------------------------------------------- > DISCLAIMER > 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. > --------------------------------------------------------------------------------------- > Please consider the environment before printing this email > > _______________________________________________ > foundry-nsp mailing list > [email protected] > http://puck.nether.net/mailman/listinfo/foundry-nsp _______________________________________________ foundry-nsp mailing list [email protected] http://puck.nether.net/mailman/listinfo/foundry-nsp
