31.
Brocade1
Aug 28, 2025, 12:09 AM
31. Brocade1
Play
00:00
31:37
Mute
Settings
(0:00) Okay. (0:01) Now I'm going to log into one of my switch. (0:08) Admin is the
default user name.
(0:12) And you have to give the password. (0:14) It's like the same way you log
into a controller. (0:17) I mean, you log into the NetApp cluster, you can log into
the switch by using (0:20) the same way, I mean, by using putty.
(0:23) Okay. (0:23) So the command line of the switch. (0:25) So this is my switch
name.
(0:29) SWD77 is my switch name. (0:30) And admin is a user, which I use to log into
the switch. (0:34) Okay.
(0:35) If you use different name, then it will display here. (0:40) So now, Fabric
show, this is the command to give us the details about the fabric. (0:49) I mean,
for example, if you log into any switch and it will, if you run this (0:54)
command, it will display us, I mean, how many switches we have in that fabric.
(1:00) Like that, it will give you all the details about the entire fabric. (1:03)
That means what are the partner switches we have, I mean, which are connected
(1:07) with this switch in the same SAN network. (1:09) It will display all the
details.
(1:11) Here in my environment, this is a small data center where I logged into.
(1:16) Okay. (1:17) And here we have only two switches, one as a Fabric A and we
are using (1:22) another, another switch as a Fabric B. (1:24) That is the reason
we don't have more switches.
(1:27) We have only one switch in this fabric. (1:29) Okay. (1:30) So here, this is
the domain ID of the switch.
(1:34) Just a second. (1:59) Okay. (2:00) So this is the domain ID of the switch.
(2:02) Okay. (2:03) And this is the IP address of the switch. (2:04) IP address
means we don't use IPs in the SAN switches.
(2:07) Only IP we'll use in SAN switches, that is for management purpose. (2:11) If
you want to log into the switch remotely, you can log into the switch (2:15) using
this IP address, that is the only IP we have. (2:18) Okay.
(2:18) In order to present, in order to connect a storage or server, we don't need
any (2:23) IP address here because this is a SAN network and this is the switch
name. (2:28) Okay. (2:28) And you can notice a greater than symbol in front of this
switch.
(2:33) Okay. (2:33) Greater than symbol indicates that this is the principle switch
in this fabric. (2:38) We have only one switch, right? (2:40) That is the reason
that right away it has a greater than symbol in front of it.
(2:46) For example, if we have more than one switch, like let's assume we have five
(2:51) switches in this fabric, only one switch will be having greater than symbol
(2:57) in front of its name. (3:00) So what does it mean by greater than symbol?
(3:03) It means it is a principle switch. (3:05) Principle switch, it is a role,
this is a role which will be assigned to the one (3:11) of the switch in the
fabric.
(3:13) So what the principle switch will do is, it will make sure that whatever
changes (3:18) we are doing on fabric, it will make sure that those changes will be
distributed (3:24) to all the switch in the fabric. (3:26) That is the main
functionality of the principle switch. (3:29) Principle switch don't have any other
privileges than that.
(3:32) What it will do? (3:33) It will make sure that all the configuration changes
will be replicated (3:40) to all the switches. (3:41) That is the only
functionality principle switch will do. (3:44) I mean, that is the only extra
responsibility it has.
(3:47) Okay. (3:47) Apart from that, it don't have any extra features or extra
functionalities. (3:51) Okay.
(3:52) How principle switch can be elected means, whatever the switch, the switch,
which (3:57) is having highest dominant, highest dominant in the center here, it
will be (4:03) like a ranking system, for example, highest dominant here is one,
one is the (4:08) highest dominating. (4:09) Second one is the second highest
dominating. (4:12) Third is three is the third highest dominating like that.
(4:15) Okay. (4:16) Now here, for example, if you have a five switches and the
dominating of those five (4:20) switches is one, two, three, four, five, then
switch, I mean, the switch, which (4:26) is having dominated one will be elected as
a principle switch automatically. (4:30) For example, due to some maintenance
activity or due to some other activity, (4:35) you're planning to remove this, uh,
switch, which is having (4:38) dominated one from this fabric.
(4:40) Then the next week, which is having highest dominating will be elected
(4:44) as a, elected as a principle switch automatically by fabric itself. (4:49)
Okay. (4:49) If you want, you can do it manually by using a command.
(4:53) So what I'll do, I cannot show it here because this is a production
environment. (4:57) What I'll do, I'll share, I'll share a document, which is
having (5:00) commands and description with you. (5:02) So we can go through that.
(5:03) I mean, this is the command to change that principle switch like that.
(5:06) Okay. (5:07) I'll share the document with you.
(5:08) Separate document. (5:09) We have, I'll share the document with you. (5:11)
Okay.
(5:14) Next thing, this is the command to check that and then fabric. (5:19) And
what are the switches in this fabric? (5:21) If you want to, if you want to check
that detail information on switch, (5:26) which he logged into the command is
switch show, which show command will (5:31) display that in detail information
about the switch where you logged into. (5:36) Okay.
(5:36) Yeah. (5:37) This is the switch name and switch type. (5:40) Uh, when you
logged into NetApp, we'll show you the model number straight away.
(5:44) Right. (5:45) But in brocade, it will not show you the model number straight
away. (5:48) What, what it will do, it will show you the switch type from the
switch type.
(5:53) You, uh, by using some, I mean, uh, you can, you can enter the switch type
in (5:58) Google like brocade switch models. (6:03) If you on this, just open this
link and you can able to find the all (6:08) switch types and which models. (6:11)
Let me show you that.
(6:13) So you can understand here. (6:16) Our switch type is, uh, 71 71.2. (6:21)
And that means 71, we have to consider switch type. (6:25) 71 means that is a
brocade 300 feet.
(6:29) Let's assume if it is a 77, then the switch model is DCX forest. (6:35)
Okay. (6:35) Brocade switch will not display the model number in a command line.
(6:39) Okay. (6:40) It will show you only which type from switch type you have to
find that which (6:44) model, okay. (6:48) And it will show you like, uh, uh, what
is the role of this, which is it a (6:53) principal switch or a secondary switch?
(6:54) Everything.
(6:55) What is the domain ID? (6:56) Everything. (6:56) It will display. (6:57)
Okay.
(6:58) What is the zoning status here? (7:00) We have not enabled zoning because we
have only one server and one storage. (7:05) So we don't need to perform a zoning.
(7:07) If we have only one server and one storage, because only two devices (7:11)
are connected to this fabric.
(7:13) So both of them will be connected directly to each other. (7:16) Okay.
(7:18) And these are the ports.
(7:19) Well, what we have in this speech, we have a 24 ports. (7:23) Uh, zero is
the first port and 23 is the last port. (7:26) Okay.
(7:27) And here, these are the port speeds, like, uh, first reports are 4gb ports
(7:34) and the remaining all are 8gb ports. (7:37) That's why it is showing as an
eight and four like that. (7:40) Okay.
(7:40) And here you can notice that there are a lot of, uh, I mean, uh, we (7:45)
have a different states here. (7:46) Uh, some of them are showing online. (7:48)
Some of them are showing a no light.
(7:50) Some of the, some of them are showing no module. (7:53) What does it mean?
(7:54) Like I'll explain you now. (7:56) Okay.
(8:11) Let's assume this is our switch, right? (8:13) Uh, our switch have a
sandbox, as I mentioned earlier. (8:16) Okay. (8:17) These sandbox are, it's the,
it kind of just a whole, you cannot connect (8:21) cable to this sandbox directly.
(8:23) Okay. (8:24) You, you, you have a intermediate component called SFO. (8:28)
Sorry.
(8:34) Okay. (8:35) You have a, one more component called SFP. (8:38) What do you
have to do? (8:39) You have to purchase as a piece.
(8:41) Okay. (8:42) How to purchase SFP modules, uh, that we models are, uh, they,
they're like this. (8:48) This, this is the sand SFP module.
(8:50) Okay. (8:50) We need to purchase this module and you have to insert this
module in switchport. (8:56) Okay.
(8:56) You have to insert this module in switchport. (8:59) Then only you can able
to connect fiber channel cable to switch. (9:03) I'll show you how fiber channel
cable will be.
(9:12) So, yeah, uh, this is our fiber channel cable. (9:16) Okay. (9:17) One is
for transmission and another one is for receiving data, transmitting (9:22) data
and receiving data.
(9:23) Okay. (9:24) You, you can connect this cable to that, uh, SFP and SFP will
be (9:28) inserted into that switchport. (9:31) That, that is how it will work
here.
(9:34) If it is showing online means then SFP module is, uh, already inserted in
that (9:40) board and cable also connected. (9:43) Then only it will show you
online. (9:45) It will, it will show the port status as online.
(9:49) If you have only SFP module is present, but you have not connected the cable
to (9:54) it, cable to the SFP module, then it will show you like no light. (9:58)
Okay. (9:59) SFP module is there on that port, but you have not yet connected the
cable.
(10:04) Then it will show you as no light. (10:07) Even SFP module is not there on
that port. (10:09) I mean, SFP module is not inserted to that port.
(10:12) Then it will show you like no module. (10:14) These are the three states.
(10:16) Okay.
(10:17) Uh, you got it? (10:18) Any doubts so far? (10:29) Okay. (10:32) Okay.
(10:32) And we are using only these six ports.
(10:36) Okay. (10:37) But these are the, and these are the WWPN of the host, which
(10:41) are connected to the switch. (10:43) Uh, it might be storage or it might be
server.
(10:46) The, I mean, these are the, uh, host initiative, WWPNs, which (10:51) are
connected to these ports. (10:52) Okay. (10:57) Next, if you want to see, um, what
is the management IP configuration (11:01) and everything, those details, you can
run this command IP ADDR show.
(11:08) This command will display what is the management IP of the (11:12) speech
and everything, uh, details. (11:14) If you, uh, you, you bought this, uh, switch
first time, you (11:18) don't have any management IP. (11:19) You logged into
console.
(11:21) Uh, and you connected to the switch through console. (11:24) Then if you
want to configure IP address, then you can run this (11:27) command IP ADDR set and
hit enter. (11:31) Then it will ask you to enter the IP, enter the subnet mask,
enter (11:35) the gateway, all those details.
(11:37) It will ask you to enter. (11:39) Okay. (11:40) IP address set.
(11:44) If you want to do some health check, like, uh, uh, temperature, like
(11:49) you can run this command temp show. (11:50) It will display the temperature
of the switch. (11:54) And fan show, it will display the fans.
(11:58) I mean, we, we used to have a fancy in this, inside this speech, which
(12:01) will help us to pull the speech because it will be up and running all the
time. (12:05) Right? (12:05) So these fans will help us to reduce the temperature
of the speech. (12:09) So we, we, you can check the fan status also and BS show.
(12:15) It will display the power supply status. (12:17) Uh, this is a very bold
speech we have. (12:20) That is why we got only one power supply, but nowadays we
are (12:23) getting, uh, features with a redundant power supply.
(12:26) That means more than one power supply will be there. (12:28) So if one
power supply, uh, loss also, we can switch, can able to survive (12:32) with the,
and the power supply. (12:35) Okay.
(12:37) And if you want to check the logs of the speech, then the command is
support show. (12:43) This is the command to check the logs of the speech support
show. (12:54) So these are the logs.
(12:57) Okay. (13:04) I'm stopping this one. (13:06) Okay.
(13:06) No control. (13:07) See, if you press control, see, then immediately it
will stop displaying (13:11) new blocks. (13:12) Uh, for example, if you got some
issue, uh, you requested you, you, you, you (13:17) are in call with vendor.
(13:18) He requested you to upload the logs. (13:21) He wants, he wants to, he
wants to review the logs. (13:24) Okay.
(13:25) In order to do that, you need to, you need to submit the logs to him.
(13:28) Okay. (13:29) You need to upload the logs to the vendor in order to do
that.
(13:32) First you have to save the logs. (13:33) You have to capture the logs from
the speech and then only you can upload it. (13:37) Right? (13:37) So in order to
capture the logs, in order to save the logs from the speech, (13:41) command is
support, same support, say with the command to save the logs from the (13:47)
speech, if you run this command, it will, it will ask you for your confirmation.
(13:53) I said, yes. (13:55) Then it will ask you to enter the IP address. (13:57)
I mean, IP address, IP address of the server where you are planning to save the
(14:02) logs.
(14:03) After that, it will ask you for username and password. (14:06) Once we
entered username and password, then it will ask you for the location (14:09) where
you want to store like a folder location or something. (14:12) If you enter that,
then it will save the logs in that given location.
(14:17) Okay. (14:18) From there, you can upload the logs to that vendor. (14:20)
So he can go through those logs and he will give us the information.
(14:26) What is the issue? (14:26) Everything we can, we can tell us, we can give
us a solution by reviewing the (14:32) logs. (14:33) Okay. (14:34) These are the
two very, very two important commands, support save and support show.
(14:40) Okay. (14:43) So if you want to see in detail information about the port,
we can run this command (14:49) port show, and you have to give the port number.
(14:53) So it will display in detail information like what is the remote device
connected (15:03) to this port.
(15:03) That means whatever storage or server connected to this port, it will
display (15:07) that, uh, WWPN number and what is the speed of the port? (15:12)
Everything it will display. (15:13) Okay. (15:13) All the details, uh, in detail
information about that particular port.
(15:19) Okay. (15:22) You can check it on all the ports like that. (15:28) Okay.
(15:29) There is no device connected to it. (15:31) That's why it is showing empty
here. (15:33) Okay.
(15:36) So if you want to check about that, uh, if we want to check about the
details of (15:41) SFP, which is presented on that port, we can run this command as
a show and how to (15:47) get the port number there. (15:49) So it will display
that details about the SFP. (15:52) I said to me that module, which we have
inserted to that port here in SFP, you (15:57) can see that RX and TX two values
will be there.
(16:00) RX TX means that transmission and receiving speed. (16:03) Okay. (16:03) It
will display that transmission and receiving power.
(16:07) So, um, if, if, if it is not displaying any value, sometimes, uh, it will
not (16:13) display any values in RX or TX. (16:16) That means that SFP is faulty.
(16:18) You need to replace that SFP.
(16:20) If SFP is a faulty, then you'll, you used to get a lot of performance
issues or (16:25) your server may not able to see the LUNs, server or storage will
not able to see (16:30) the LUNs, those kinds of issues will be occurred. (16:32)
We'll, we'll discuss more about this in a sand troubleshooting, which we'll (16:36)
discuss at the end of the course. (16:38) Okay.
(16:40) These are the command to check the detail information about the SFP.
(16:47) Okay. (16:48) So again, I'll show these commands to check the aliases.
(16:52) As I, as I mentioned here, we don't have, we haven't configured aliases
(16:56) and don't show the configuration because we don't have any, you know, uh,
we have (17:02) only one server and one storage connected to this particular
fabric. (17:06) That is the reason we have not configured. (17:08) And, uh, and
those are not licensed even actually, um, we purchased the (17:13) sandwich without
a zoning license as we don't need a zoning, but if you want (17:18) to implement
zoning, you need to purchase a license, like you can see (17:21) the licenses here,
license show.
(17:24) By using this command, you can check the licenses, whatever licenses,
licenses we (17:28) have, we have only fabric license, all these stuff, only these
licenses only. (17:33) Okay. (17:34) We don't have a zoning license.
(17:35) If you, if you want to configure zoning aliases, all this stuff, then
(17:39) you need to purchase another license. (17:40) But nowadays it will be, uh,
it will be coming with the switch by default (17:45) zoning license will be there
in each and every stage. (17:48) Okay.
(17:52) Um, uh, CFG show, it will display you the active configuration. (17:58) We
do we, as I mentioned earlier, we haven't configured any (18:02) configurations
also, CFG, ACTV show. (18:06) It will display the only active configuration.
(18:09) Okay. (18:11) Thing is, uh, in my company, uh, these sand switches will be
(18:16) taken care by a networking team only. (18:18) That is the reason I don't
have access to those sand switches.
(18:20) Only features I have access is that these two switches on, uh, these, these
fabrics (18:25) only because they are not in production. (18:27) They are into
development. (18:28) That is the reason they provided access to me.
(18:30) Just a second. (18:31) I'm getting it. (18:34) Okay.
(19:16) Next. (19:22) Okay. (19:22) These are the things, uh, you can see, and
apart from this, uh, as I mentioned (19:29) here earlier, uh, like, uh, switcher
fabric is a intelligent network, right? (19:34) So why, why we call it as
intelligent network? (19:36) Because whatever the ports, which are resets on the
sand switches, (19:41) those software specific, and they can configure themselves.
(19:45) So if we connect server, it can automatically, uh, configure itself.
(19:50) Um, I mean, according to the server, if you connect storage, it will
(19:54) automatically reconfigure itself according to the storage. (19:58) Okay.
(19:58) So these are the ports we have. (20:01) I mean, uh, type of ports, the type
of ports means these are (20:04) not a physical type of ports. (20:06) These are
configuration ports.
(20:08) I mean, like, uh, you can, you can change the configuration on ports.
(20:11) Okay. (20:12) We have a five types.
(20:13) Actually we have more than this, but most of the times we'll (20:15) use
only these five ports only. (20:17) Uh, by default, all the ports will be in, uh,
marked as a G port. (20:22) G port means generic port.
(20:24) That means which are ready to configure as any port. (20:28) Okay. (20:30)
And NL port means node loop port.
(20:32) And the FL port means fabric loop port. (20:35) This node loop port and
fabric loop port we'll use, we'll configure (20:39) as these ports, uh, when, when
they are placed into, or when they are (20:43) connected to any FCL topology.
(20:45) So we don't have any FCL topologies now.
(20:48) I mean, that means, uh, nowadays nobody using FCL topology. (20:52) So you
will not get a chance to see these two ports. (20:55) I mean, you don't need to
configure ports, port type to these two ports.
(20:59) Okay. (21:00) E port means expansion port. (21:02) Expansion port means,
uh, let's assume, uh, I have a sand switch.
(21:09) Okay. (21:10) In this sand switch, I mean, all the ports are full now.
(21:14) So what I have done, I have bought a new switch, one more sand switch.
(21:19) So in order to, uh, make sure that both of them are in fabric, I (21:24)
need to connect these two. (21:25) Okay. (21:27) I need to connect these two
switches.
(21:29) Then only they can able to communicate with each other and they can form
it. (21:34) Uh, they'll be in a single fabric. (21:37) Okay.
(21:38) In order to do that, I need to make sure that I configured whatever the
ports on (21:45) both switches, which are connected to each other, I must have to
make sure that (21:49) I configured them as a E port. (21:52) Then only they can
able to communicate with each other. (21:55) I mean, whatever port you configured
as a E port, that port only (21:59) can able to communicate with the other port on
the switch.
(22:02) Okay. (22:04) If you configure it as a F port, then it is a port which,
which is ready to (22:09) connect to any server or storage. (22:11) Okay.
(22:12) These are the types of ports what we have. (22:14) Okay. (22:16) By
default, every port will be in a report will be G port only.
(22:21) Okay. (22:21) You need to change the configuration. (22:24) I'll give you
commands that I'm going to provide you a document, which will give (22:28) us how
to, how to change the port configuration also.
(22:31) Okay. (22:33) That you can able to see how to change the port configuration
to E port, how to (22:37) change the port configuration to F port, how to change it
to FL port, everything (22:41) will be there in the document. (22:43) Okay.
(22:49) So, uh, can I proceed or can I stop it for today? (22:53) It's your wish.
(23:07) No, you can proceed. (23:11) So let's assume what we'll do.
(23:14) Uh, in, in order to connect multiple switches in a fabric, what we'll do.
(23:21) We'll establish that first. (23:23) What we'll do, we'll convert the ports
as expansion ports.
(23:31) Okay. (23:32) In the old days, we used to do that expansion. (23:47) Okay.
(23:50) So what I used to do, we used to connect these two ports here, these two
ports (23:55) here, we used to configure two more ports here, we used to configure
two more ports (24:05) here, like that we used to configure a fabric. (24:09) Okay.
(24:09) All these are E ports only, because if you are connecting, uh, one switch
(24:13) another with another switch, you need to configure those ports as an
expansion port.
(24:17) Okay. (24:19) But, uh, some, sometimes we might have a different models.
(24:24) I mean, it is not mandatory to use same models within the fabric.
(24:29) You can use a different models like, uh, let's assume ZDCX 85104. (24:37)
Let's assume that is okay. (24:39) And we have 48K here, 48,000.
(24:45) You can use different models of switches within a fabric. (24:48) You can
combine the different models. (24:51) It is unlike NetApp.
(24:52) NetApp, it is not possible, right? (24:54) You have to use the same model
within HFA, but here you can use different (24:58) models of switches, switches.
(25:01) Okay. (25:01) In this kind of scenario, uh, there may be, uh, I mean, what
you'll do in order (25:08) to improve the bandwidth, in order to improve the
communication between the (25:11) switches, what you will do, you'll trunk these
ports sometimes.
(25:16) Okay. (25:17) You can configure trunking. (25:19) Trunking means, you know,
right.
(25:21) If groups, it's like a, if grouping on NetApp. (25:23) What we'll do here,
we'll trunk the ports. (25:26) I mean, we combine those two physical ports and
we'll make it as a logical port.
(25:32) After that, what we'll do, we configure ISL. (25:36) That means inter-
switch link. (25:39) In order to establish the communication between these two
switches, you (25:42) must have to configure the ISL.
(25:45) Then only these two switches can able to communicate with each other.
(25:48) You need to configure ISL within all of them. (25:52) Whatever the switches
we have in Fabric, we need to configure ISL within all of (25:57) them, then only
they can able to communicate with each other.
(26:01) This ISL means inter-switch link. (26:08) Okay. (26:08) This is a, uh, I
mean, uh, this is a concept which we'll use to establish (26:15) the communication
between the switches.
(26:17) But, uh, the, whatever new model switches we have in a generation (26:21)
that means, uh, DCX, but in order to configure this inter-switch link, we (26:27)
must have to, uh, I mean, uh, use the ports, right, ports on the switch. (26:33) So
we are, if we, if we have only three switches, then we have used (26:38) four ports
on each switch, right? (26:40) So that is that, that means we are wasting four
ports on each switch to establish (26:46) the communication between those switches.
(26:47) If you have a more switches, not, you have to use more ports, right?
(26:53) That will be based of ports.
(26:54) So in order to reduce this, uh, wastage of ports, they bought a concept
called ICL. (27:01) ICL means inter-chassis link. (27:06) Okay.
(27:07) Inter-chassis link. (27:08) This is the one more concept. (27:10) So, okay.
(27:11) This inter-chassis link, this concept is, uh, started from only DCX series.
(27:17) Now, now it is only with DCX series, DCX and DCX4S, DCX85104 and DCX85108.
(27:37) Only we have this concept in these switches only, ICL concept.
(27:42) That means you used to have a dedicated port for this, uh, inter-switch
(27:48) communication. (27:48) That means if you want to connect one switch with
another switch, you can use (27:53) these ports, ICL ports, which are dedicated for
internal communication (27:59) between switches. (28:00) Okay.
(28:00) You can use those ports. (28:02) So if you are using ICL ports now, you
don't need to waste the normal ports and (28:09) you don't need to configure them
as a E-port. (28:11) You can use them instead of configuring ISL, you can use them
for, uh, you know, (28:18) uh, to connect to the server or to connect to the
storage.
(28:21) Okay. (28:22) That is the difference between ISL and ICL. (28:25) Now I'll
show you, uh, ISL and ICL ports physically.
(28:30) Okay. (28:49) Okay. (28:57) Yes.
(28:58) Uh, this is a DCX8510 series switch and all these are normal fabric (29:03)
port switches. (29:04) I mean, fabric ports, and this is a service place, a
service, service (29:08) processor blade. (29:09) These two are, okay.
(29:12) These two are service processor blades and we have extra blades, right?
(29:18) These two extra blades. (29:19) These are ICL blades, ICL port blades.
(29:22) Okay.
(29:22) These two are ICL port blades, which will be used for internal (29:26)
communication between the switches. (29:29) Okay. (29:30) Uh, if you go to, uh, 48K
or whatever series is we have 24K, 12K, we don't (29:37) have these, uh, ICL
chassis.
(29:40) Okay. (29:41) And these are not DCX. (29:42) Okay.
(29:49) Yes. (29:49) This is a 48K. (29:51) This don't have any, uh, ICL chassis.
(29:54) I mean, ICL blade will be not there in this 48K. (29:58) You must have to
use these, uh, you know, whatever ports we have. (30:04) Generic ports only.
(30:05) We have to convert them into E ports. (30:07) Then only we can establish
the communication between two switches. (30:11) But in DCX series, we have a
separate slot, separate blade called ICL blade.
(30:17) Okay. (30:17) By using the ICL ports, we can establish the communication
between (30:20) the switches within the fabric. (30:22) Okay.
(30:24) They'll not ask you these, uh, all these topics in an interview, interview
(30:27) perspective, these are not important, but if you want to be a SME, you want
(30:31) to configure a new fabric, you want to expand a new fabric, uh, then only
(30:36) you, you used to work on these topics. (30:38) These are very crucial, uh,
you know, concepts, ICL and ISL, all these (30:43) terms of port configuration,
these are very, very crucial stuff. (30:47) They'll not allow you to work on these.
(30:49) Uh, I mean, you'll get a chance to work on this very rarely. (30:52) Okay.
(30:53) When I, I, I, I configured all this stuff only once in my career.
(30:58) That's it. (30:59) If you're configuring any new data center, you don't
have anything there. (31:03) You are configuring your SAN setup first time, then
only you will get a (31:06) chance to work on all this stuff.
(31:09) Okay. (31:13) Uh, any doubts so far? (31:20) Oh, fine. (31:21) Okay.
(31:24) I'm going to start a new meeting. (31:26) Please join me so we can finish
this.
