[f-nsp] Couple of total newbie questions About TurboIron 24x while I wait for my support to get activated.

[Jared Valentine]

Haven't had any hands-on time with the TurboIron yet.  

1.) check the "install guide" for the pinout on the TurboIron.  Match that
up with the Raritan pinout and you should be good.  I recently did this with
a Cyclades ACS console server.  Had to think about it, but once I understood
the pinouts, making the cable wasn't difficult.  

2.) The TurboIron is a 28-port switch.  All of Brocade's "shared" ports also
share the same port #'s.  So, because it's ports 25-28, then they're
dedicated ports.  

3.) Under your "management vlan" add the keyword "management-vlan".  That
will restrict access to the switches' IP address to that particular VLAN.
I'm not sure why Brocade does it this way, but once you add management-vlan,
you'll also need to add "default-gateway x.x.x.x 1" under that same VLAN.
I'm pretty sure the global default gateway statement will be removed.  (at
least that's how it is on other platforms).  

Good luck,

-Jared


-----Original Message-----
From: foundry-nsp-bounces at puck.nether.net
[mailto:foundry-nsp-bounces at puck.nether.net] On Behalf Of Drew Weaver
Sent: Monday, November 22, 2010 6:45 AM
To: foundry-nsp
Subject: [f-nsp] Couple of total newbie questions About TurboIron 24x while
I wait for my support to get activated.

Hi,

We just bought a pair of TurboIron 24x switches and so far they seem to be
pretty great, I am running into a few problems but I am sure you guys have
seen them all before.

#1

I am unable to get the console port of the TurboIron 24x to communicate with
my Raritan Serial Console switch, it works fine using the included serial
cable from Brocade to a PC, but I need it to be accessible via the Raritan
Switch.

I assume there is just a certain way you have to wire the cat5 cable to make
it work, has anyone figured this out yet?

#2

Does using the 4x Copper 1Gb ports on the switch disable fiber ports? If so
does anyone know which fiber ports are disabled for which copper ports?

I.e. if you use 25 then 1 is disabled, 26 then 2, etc? I have tested a bit
and so far I don't notice any ports being shut down when I use 25, 26, 27,
or 28.

#3

Are the global 'IP commands' only applied to the default VLAN, or how does
that work?

I noticed that if I globally assign an IP address to the switch, I can
access it just fine through the 'management port' but I can also access it
from any other port as well.

I would really like to isolate the management traffic to only the management
port, has anyone figured out a way to do this yet?

Anyway thanks if anyone knows the answers to any of these questions,
hopefully the support administrator at brocade will add my serial numbers to
their system soon so that I can ask them =)

thanks,
-Drew
 

_______________________________________________
foundry-nsp mailing list
foundry-nsp at puck.nether.net
http://puck.nether.net/mailman/listinfo/foundry-nsp