Trunk id doesn't have to be identical. Can you give me model of devices you are trying to trunk between with their os version?
Thanks, Pritesh From: Gary H [mailto:[email protected]] Sent: Friday, March 26, 2010 4:42 PM To: Pritesh Patel (CW) Subject: Re: [f-nsp] Multi Trunking separate VLANs between 2 switches Hi Pritesh I built my trunks with the tags and began connecting fiber ports and since that time, the DHCP server wasn't able to respond to voip phones on that network or the phones couldnt reach the DHCP server on the same ip subnet but different switch. This only happened after connecting the trunk fibers. Do the Trunk IDs for a trunk have to be identical between switches connected trunk groups? Is it a problem if the IDs match for other Trunks that are not part of the same trunk group on Switch A (NOC main switch)? Switch A TrunkBB e3/5 to 3/8 e4/4 to 4/8 ID 67 Switch B TrunkBB e1/4 to 1/8 e 2/4 to 2/8 ID 3 Switch A TrunkCC e5/5 to 5/8 e6/4 to 6/8 ID 131 Switch C TrunkCC e1/4 to 1/8 e2/4 to 2/8 ID 3 Switch A TrunkDD e7/5 to 7/8 e8/4 to 8/8 ID 195 Switch D TrunkDD e1/4 to 1/8 e2/4 to 2/8 ID 3 My NOC switch has several unique Trunk IDs however the switch closets all use similar IDs but they define unique trunks which connect to the NOC switch, meaning they are different on each end of the trunk. Gary On Fri, Mar 19, 2010 at 4:59 PM, Pritesh Patel (CW) <[email protected]<mailto:[email protected]>> wrote: No It won't create loop. You have to tag ports first then create a trunk. Vlan 10 Tag e 1/5 to 1/8 Vlan 11 Tag e1/5 to 1/8 Then create a trunk group. Older codes require you to do port /vlan config first before you deploy trunk Then Trunk ports .. Deploy Thanks, Pritesh From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Gary H Sent: Friday, March 19, 2010 1:54 PM To: [email protected]<mailto:[email protected]> Subject: Re: [f-nsp] Multi Trunking separate VLANs between 2 switches Port typo corrected in group1 SWITCH A TRUNK Group1 e1/1 to 1/4 e2/1 to 2/4 SWITCH B TRUNK Group1 e1/1 to 1/4 e2/1 to 2/4 On Fri, Mar 19, 2010 at 4:49 PM, Gary H <[email protected]<mailto:[email protected]>> wrote: I can't find an example of multi trunking VLANs between two switches to maximize Group1 and Group2 8GB trunk per vlan. Think this will work? (proper syntax not used) Is the Group2 trunk going to require tagged trunk ports and as a result, carry all the VLANs and then create a loop? VLAN 1 (default vlan) contains dual mode ports, but trunk shouldn't need dual mode SWITCH A TRUNK Group1 e1/2 to 1/4 e2/1 to 2/4 SWITCH B TRUNK Group1 e1/2 to 1/4 e2/1 to 2/4 VLAN 2 contains tagged ports and untagged ports and IP Subnet voice traffic SWITCH A TRUNK Group2 e1/5 to 1/8 e2/5 to 2/8 SWITCH B TRUNK Group2 e1/5 to 1/8 e2/5 to 2/8 Thank you Gary
_______________________________________________ foundry-nsp mailing list [email protected] http://puck.nether.net/mailman/listinfo/foundry-nsp
