Re: Foundry CLI manual?

2010-01-27 Thread Jonas Frey
If you have older foundry gear (IronCore, JetCore, MG8) do a google
search for Using Packet Over SONET Modules.

Jonas

On Sat, 2010-01-23 at 16:51, David Hubbard wrote:
 Anyone have the Foundry/Brocade CLI reference PDF
 they could send me?  Brocade feels you should have a
 support contract to have a list of commands the 
 hardware you purchased offers and I'm having difficulty
 with a oc12 pos module.
 
 Thanks,
 
 David





Re: Foundry CLI manual?

2010-01-25 Thread joe mcguckin
It would be a good idea to have a bug database that accessible to paying 
support customers.


Joe McGuckin
ViaNet Communications

j...@via.net
650-207-0372 cell
650-213-1302 office
650-969-2124 fax



On Jan 23, 2010, at 8:23 AM, Richard A Steenbergen wrote:

 On Sat, Jan 23, 2010 at 10:51:57AM -0500, David Hubbard wrote:
 Anyone have the Foundry/Brocade CLI reference PDF
 they could send me?  Brocade feels you should have a
 support contract to have a list of commands the 
 hardware you purchased offers and I'm having difficulty
 with a oc12 pos module.
 
 Ironically enough the manuals themselves are accessable without a login,
 but the list of manuals is not. You fail to mention which product you're
 interested in, so I'm going to take a stab and hope that it's something
 current with a pos card like an MLX/XMR. If you're still rocking an old
 B2P622, I'd say you're in need of far more help than any manual can
 provide. :)
 
 http://www.foundrynet.com/services/documentation/xmr_user/current/NetIron_04100_ConfigGuide.pdf
 http://www.foundrynet.com/services/documentation/xmr_diag/current/NetIronXMR-MLX_04100_DiagnosticRef.pdf
 
 -- 
 Richard A Steenbergen r...@e-gerbil.net   http://www.e-gerbil.net/ras
 GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF 4C41 5ECA F8B1 2CBC)




Re: Foundry CLI manual?

2010-01-23 Thread Richard A Steenbergen
On Sat, Jan 23, 2010 at 10:51:57AM -0500, David Hubbard wrote:
 Anyone have the Foundry/Brocade CLI reference PDF
 they could send me?  Brocade feels you should have a
 support contract to have a list of commands the 
 hardware you purchased offers and I'm having difficulty
 with a oc12 pos module.

Ironically enough the manuals themselves are accessable without a login,
but the list of manuals is not. You fail to mention which product you're
interested in, so I'm going to take a stab and hope that it's something
current with a pos card like an MLX/XMR. If you're still rocking an old
B2P622, I'd say you're in need of far more help than any manual can
provide. :)

http://www.foundrynet.com/services/documentation/xmr_user/current/NetIron_04100_ConfigGuide.pdf
http://www.foundrynet.com/services/documentation/xmr_diag/current/NetIronXMR-MLX_04100_DiagnosticRef.pdf

-- 
Richard A Steenbergen r...@e-gerbil.net   http://www.e-gerbil.net/ras
GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF 4C41 5ECA F8B1 2CBC)



Re: Foundry CLI manual?

2010-01-23 Thread Jens Link
Richard A Steenbergen r...@e-gerbil.net writes:

 Ironically enough the manuals themselves are accessable without a login,
 but the list of manuals is not. 

Outch. Personally I don't like when company's hides documentation or
require me to register (or even get a support contract) to read the
documentation. On the other hand there are several vendor that are very
forthcoming vendors that even send you test equipment for free. 

Guess which company's I'm recommending to customers.

cheers

Jens
-- 
-
| Foelderichstr. 40  | 13595 Berlin, Germany | +49-151-18721264 |
| http://www.quux.de | http://blog.quux.de   | jabber: jensl...@guug.de |
-



Re: Foundry CLI manual?

2010-01-23 Thread Bjørn Mork
Jens Link li...@quux.de writes:
 Richard A Steenbergen r...@e-gerbil.net writes:

 Ironically enough the manuals themselves are accessable without a login,
 but the list of manuals is not. 

 Outch. Personally I don't like when company's hides documentation or
 require me to register (or even get a support contract) to read the
 documentation.

Cannot agree more.  It's a major drawback even with a support contract.
I often use Google to search for particular features, bugs, workarounds
or whatever, limiting the scope to site:somevendor.com.  This naturally
doesn't work with those who hide their docs.  And the site internal
search engines are usually a bad joke at best.

Regarding Foundry, I remember they used to have public docs several
years ago.  But all of a sudden it was closed. Around 2003 maybe?

Nowadays, Huawei is on top of my oh i hate that web site list. No
useful public content whatsoever.  Don't understand why they even bother
putting up a web server.

I appreciate that there still are serious vendors like Cisco and
Juniper who don't mind making their docs public. Thanks guys!



Bjørn



Re: Foundry CLI manual?

2010-01-23 Thread Mark Smith
On Sat, 23 Jan 2010 21:25:28 +0100
Bjørn Mork bj...@mork.no wrote:

 Jens Link li...@quux.de writes:
  Richard A Steenbergen r...@e-gerbil.net writes:
 
  Ironically enough the manuals themselves are accessable without a login,
  but the list of manuals is not. 
 
  Outch. Personally I don't like when company's hides documentation or
  require me to register (or even get a support contract) to read the
  documentation.
 
 Cannot agree more.  It's a major drawback even with a support contract.
 I often use Google to search for particular features, bugs, workarounds
 or whatever, limiting the scope to site:somevendor.com.  This naturally
 doesn't work with those who hide their docs.  And the site internal
 search engines are usually a bad joke at best.
 
 Regarding Foundry, I remember they used to have public docs several
 years ago.  But all of a sudden it was closed. Around 2003 maybe?
 
 Nowadays, Huawei is on top of my oh i hate that web site list. No
 useful public content whatsoever.  Don't understand why they even bother
 putting up a web server.
 
 I appreciate that there still are serious vendors like Cisco and
 Juniper who don't mind making their docs public. Thanks guys!
 

Agree. The first thing a vendor can do to have a chance of you buying
their gear is to make it as easy as possible to transition to it, and
that includes becoming familiar with it's CLI, and working out how much
effort you'll need to spend on converting to different syntax. What's
so proprietary about how to configure OSPF that it needs to be kept a
secret?



 
 
 Bjørn