| Author |
Message |
Steve Sal
Guest
|
 Posted:
Wed Aug 04, 2004 10:12 pm Post subject:
MLT Between Passport 8006 & 470-48T |
|
|
I am setting up a new network and have not had much experience with MLT.
It seems easy enough to setup, but I've tried and it doesn't seem to working
properly.
I have a Passport 8006 as the core switch, and will be connecting a 4 switch
470-48T stack and a 3 switch 470-48T stack back to the Passport with MMF.
I've configured each 470T stack with one MLT group using switch 1 Port 47
and switch 4 Port 48 to connect back to the core.
At the core I have 2- 8632TXM modules. My idea is to connect ports 47 and 48
from stack 1 to ports 33 and 34 of the first 8632TXM and then connect ports
47 and 48 of the second stack to ports 33 and 34 of the second 8632TXM. So
far so good???
My real question is the MLT config on the 8006. Does the MLT mode have to be
trunk or access? I had heard that switch to switch connections need to be
trunk. Am I configuring 1 MLT group or 2? I would like to aggregate my
bandwidth so I have 4 gig of fiber between the core and the stacks.
Any help would be great. Thanks in advance. |
|
| Back to top |
|
 |
MC
Guest
|
| Posted:
Thu Aug 05, 2004 4:33 am Post subject:
Re: MLT Between Passport 8006 & 470-48T |
|
|
If I understand the 8600 and switch stack configuration correctly that you
have and want setup, Then this is what I would recommend below. One thing,
Each seperate switch stack would have a different MLT group defined on the
8600 and the bandwidth is what the number x speed of the total links going
to a single stack in this case which would be 2GB if using 2 GB links each
stack. I can not remember on the 470 but though it had the same or similar
switch bandwidth as the BPS2000and 450 switches which is about 2.5GB (some
say 3GB but 2.5 is documented) so I do not think that more than 2GB unplinks
are going to do much good. We so far have several 470 stacks going to 8600's
and nver see utilization needing more than 2GB on thje uplinks. In some are
8 470's in a stack. These are clinet/printer subnets in building. We have
smaller stacks for servers and still see no problems with just 2GB, server
stacks are using most all ports.
What I would do (I can send a diagram and some configuration screen shots if
necessary but may take a while)
Assuming using the fiber GBIC ports of course
Setup two MLT groups on 8600
First MLT group
Add ports 33 from both 8632TX modules
Second MLT group
Add port 34 from both 8632TX modules
First 470 switch stack
Configure and MLT group with port 48 on first switch memeber and port 48
from other switch member
Connect port 48 on the first switch to port 33 on the first 8632TXM module
in the 8600
Connect port 48 on the second switch (or another switch in the stack) to
port 33 on the second 8632TXM module in the 8600
Second 470 switch stack
Configure and MLT group with port 48 on first switch memeber and port 48
from other switch member
Connect port 48 on the first switch to port 34 on the first 8632TXM module
in the 8600
Connect port 48 on the second switch (or another switch in the stack) to
port 34 on the second 8632TXM module in the 8600
This is called DMLT (Distributed MLT), Allows have members in a trunk
accross different switches in a stack/chassis. more redundancy.
Also can not remember on the GBIC ports on the 8632TX- modules but many
adjoining ports on a module may be associated with the same backplane
connection to the switch fabric, something like OCTAL PID or something, got
to go back to school again!. Want to have connections spread out accross
these backplane connections, OCTAL PID (ASIC, backplane connections,etc
????) as possible for better redundnacy and performance in some cases. There
is a lot of techincal resources on this I could look up but really is not
necessary, just try and spread out the connection accross switches in a
stack, accross blades, and not adjacent ports if possible when setting up
trunks.
Also switch to switch want to be in access mode ? I think, Seems I am
alwayes getting this backwards so better to look at the DOC's again!
I can find out if can not find it metioned anywhere.
"Steve Sal" <123@456.org> wrote in message
news:10h29q0bojsfke2@corp.supernews.com...
| Quote: | I am setting up a new network and have not had much experience with MLT.
It seems easy enough to setup, but I've tried and it doesn't seem to
working
properly.
I have a Passport 8006 as the core switch, and will be connecting a 4
switch
470-48T stack and a 3 switch 470-48T stack back to the Passport with MMF.
I've configured each 470T stack with one MLT group using switch 1 Port 47
and switch 4 Port 48 to connect back to the core.
At the core I have 2- 8632TXM modules. My idea is to connect ports 47 and
48
from stack 1 to ports 33 and 34 of the first 8632TXM and then connect
ports
47 and 48 of the second stack to ports 33 and 34 of the second 8632TXM. So
far so good???
My real question is the MLT config on the 8006. Does the MLT mode have to
be
trunk or access? I had heard that switch to switch connections need to be
trunk. Am I configuring 1 MLT group or 2? I would like to aggregate my
bandwidth so I have 4 gig of fiber between the core and the stacks.
Any help would be great. Thanks in advance.
|
|
|
| Back to top |
|
|
Steve Sal
Guest
|
| Posted:
Thu Aug 05, 2004 6:29 pm Post subject:
Re: MLT Between Passport 8006 & 470-48T |
|
|
Thanks MC.
I'm going to sit down and draw up a scenario with Visio and I'll get back to
you.
"MC" <mwclarke1@yahoo.com> wrote in message
news:AphQc.7816$Ns.7481@bignews5.bellsouth.net...
| Quote: | If I understand the 8600 and switch stack configuration correctly that you
have and want setup, Then this is what I would recommend below. One thing,
Each seperate switch stack would have a different MLT group defined on the
8600 and the bandwidth is what the number x speed of the total links going
to a single stack in this case which would be 2GB if using 2 GB links each
stack. I can not remember on the 470 but though it had the same or similar
switch bandwidth as the BPS2000and 450 switches which is about 2.5GB (some
say 3GB but 2.5 is documented) so I do not think that more than 2GB
unplinks
are going to do much good. We so far have several 470 stacks going to
8600's
and nver see utilization needing more than 2GB on thje uplinks. In some
are
8 470's in a stack. These are clinet/printer subnets in building. We have
smaller stacks for servers and still see no problems with just 2GB, server
stacks are using most all ports.
What I would do (I can send a diagram and some configuration screen shots
if
necessary but may take a while)
Assuming using the fiber GBIC ports of course
Setup two MLT groups on 8600
First MLT group
Add ports 33 from both 8632TX modules
Second MLT group
Add port 34 from both 8632TX modules
First 470 switch stack
Configure and MLT group with port 48 on first switch memeber and port 48
from other switch member
Connect port 48 on the first switch to port 33 on the first 8632TXM module
in the 8600
Connect port 48 on the second switch (or another switch in the stack) to
port 33 on the second 8632TXM module in the 8600
Second 470 switch stack
Configure and MLT group with port 48 on first switch memeber and port 48
from other switch member
Connect port 48 on the first switch to port 34 on the first 8632TXM module
in the 8600
Connect port 48 on the second switch (or another switch in the stack) to
port 34 on the second 8632TXM module in the 8600
This is called DMLT (Distributed MLT), Allows have members in a trunk
accross different switches in a stack/chassis. more redundancy.
Also can not remember on the GBIC ports on the 8632TX- modules but many
adjoining ports on a module may be associated with the same backplane
connection to the switch fabric, something like OCTAL PID or something,
got
to go back to school again!. Want to have connections spread out accross
these backplane connections, OCTAL PID (ASIC, backplane connections,etc
????) as possible for better redundnacy and performance in some cases.
There
is a lot of techincal resources on this I could look up but really is not
necessary, just try and spread out the connection accross switches in a
stack, accross blades, and not adjacent ports if possible when setting up
trunks.
Also switch to switch want to be in access mode ? I think, Seems I am
alwayes getting this backwards so better to look at the DOC's again!
I can find out if can not find it metioned anywhere.
"Steve Sal" <123@456.org> wrote in message
news:10h29q0bojsfke2@corp.supernews.com...
I am setting up a new network and have not had much experience with MLT.
It seems easy enough to setup, but I've tried and it doesn't seem to
working
properly.
I have a Passport 8006 as the core switch, and will be connecting a 4
switch
470-48T stack and a 3 switch 470-48T stack back to the Passport with
MMF.
I've configured each 470T stack with one MLT group using switch 1 Port
47
and switch 4 Port 48 to connect back to the core.
At the core I have 2- 8632TXM modules. My idea is to connect ports 47
and
48
from stack 1 to ports 33 and 34 of the first 8632TXM and then connect
ports
47 and 48 of the second stack to ports 33 and 34 of the second 8632TXM.
So
far so good???
My real question is the MLT config on the 8006. Does the MLT mode have
to
be
trunk or access? I had heard that switch to switch connections need to
be
trunk. Am I configuring 1 MLT group or 2? I would like to aggregate my
bandwidth so I have 4 gig of fiber between the core and the stacks.
Any help would be great. Thanks in advance.
|
|
|
| Back to top |
|
|
Charles R. Anderson
Guest
|
| Posted:
Fri Aug 06, 2004 12:32 pm Post subject:
Re: MLT Between Passport 8006 & 470-48T |
|
|
Steve Sal <123@456.org> wrote:
| Quote: | My real question is the MLT config on the 8006. Does the MLT mode have to be
trunk or access? I had heard that switch to switch connections need to be
trunk. Am I configuring 1 MLT group or 2? I would like to aggregate my
bandwidth so I have 4 gig of fiber between the core and the stacks.
Any help would be great. Thanks in advance.
|
It depends what you want to do. "Trunk" means 802.1Q VLAN Tagging
will be enabled on the MLT/802.3ad Link Aggregation, so that you can
transport more than one VLAN across the MLT. "Access" means that
802.1Q is disabled, so that only one port-based VLAN, plus possibly
other policy-based VLANs (byProtocol, byIpSubnet, etc.) can be used on
the MLT. Switches at both ends of the MLT links should be configured
the same way--either trunk/802.1Q or access/server.
Usually, I always configure trunk/802.1Q mode between switches, so
that additional VLANs can be added in the future without service
interruption. Access mode would be used to connect to servers with
bonding/802.3ad Ethernet card drivers.
Sometimes, you may want/need Access mode between a PP8600 switch and
edge switches, in case you have to use special policy-based VLANs.
Policy-based VLANs will only filter traffic into their respective
Protocols or IP Subnets on access ports, not trunk/tagging enabled
ports. |
|
| Back to top |
|
|
Steve Sal
Guest
|
| Posted:
Sat Aug 07, 2004 8:35 am Post subject:
Re: MLT Between Passport 8006 & 470-48T |
|
|
Thanks for your input Charles.
Lucky for me, the network in question is quite simple, so the 8006 is only
configured at Layer 2 with Default VLAN1.
All the servers (and the default gateway-ASN with dual MCT1 mods and 2-24
channels T1's) will be directly connected to the 8006.
The problem is that I am trying to do an IP address conversion for not only
the network in question, but also 2 remote links, so until the big cutover,
I have had to put a secondary IP interface on the default gateways ethernet
to "move around"
Stay Tuned... Once Again... Thanks for your help.
"Charles R. Anderson" <craIHateSpam@wpi.edu> wrote in message
news:slrnch6uih.ppd.craIHateSpam@angus.ind.WPI.EDU...
| Quote: | Steve Sal <123@456.org> wrote:
My real question is the MLT config on the 8006. Does the MLT mode have
to be
trunk or access? I had heard that switch to switch connections need to
be
trunk. Am I configuring 1 MLT group or 2? I would like to aggregate my
bandwidth so I have 4 gig of fiber between the core and the stacks.
Any help would be great. Thanks in advance.
It depends what you want to do. "Trunk" means 802.1Q VLAN Tagging
will be enabled on the MLT/802.3ad Link Aggregation, so that you can
transport more than one VLAN across the MLT. "Access" means that
802.1Q is disabled, so that only one port-based VLAN, plus possibly
other policy-based VLANs (byProtocol, byIpSubnet, etc.) can be used on
the MLT. Switches at both ends of the MLT links should be configured
the same way--either trunk/802.1Q or access/server.
Usually, I always configure trunk/802.1Q mode between switches, so
that additional VLANs can be added in the future without service
interruption. Access mode would be used to connect to servers with
bonding/802.3ad Ethernet card drivers.
Sometimes, you may want/need Access mode between a PP8600 switch and
edge switches, in case you have to use special policy-based VLANs.
Policy-based VLANs will only filter traffic into their respective
Protocols or IP Subnets on access ports, not trunk/tagging enabled
ports. |
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in