Hi Dave! Point to your suggestions. It's completely true; the tagged port with both vlans will be the one uplink port that will be connecting with another switch to make vlan broadcasting pass to that another switch.
Sent from my iPhone On Sep 11, 2010, at 4:48 PM, "Jolie, David" <[email protected]> wrote: > Hi Mike, > > I see that you have configured a router interface for VLAN two on network > 192.168.28.0 and applied that VLAN to one port (FE.1.10). However, that > router does not have a local interface in 192.168.26.0 nor does it know how > to get to network 192.168.26.0. > > As Egbert suggests, if you create a second interface for subnet 192.168.26.0 > and put apply the "Set VLAN Host" command you should be able to reach both > networks. > > ------------------------------------------------------------------------- > Egbert, > > I don't believe you need to tag both VLANs out the port connected to the DHCP > server - the IP Helper on the router interface should take care of getting > DHCP broadcasts from VLAN 28 over to the DHCP server on VLAN 26. > > You should be able to get this to work just fine with > set port vlan fe.1.x 26 modify-egress > on the DHCP server port. > > The way you have it shown below, the DHCP server would be seeing two requests > from each client in VLAN 28 (one directly out the port tagges as VLAN 28 and > another forwarded from the router on VLAN 26). In fact, if the DHCP is > listening to tagged frames this can cause issues with clients - I had a site > with Avaya IP phones that wouldn't come up until they removed all tagged > VLANs from the DHCP server port on the switch. Apparently the DHCP server > was ACKing one request and NACKing the other and it confused the Avaya IP > phones. > > Cheers! > Dave J. > > > > -----Original Message----- > From: Egbert Rodriguez [mailto:[email protected]] > Sent: Saturday, September 11, 2010 11:10 AM > To: Enterasys Customer Mailing List > Subject: Re: [enterasys] C2 VLAN > > Hi Mike! > > I'm kind newbie too, but I will advice you what already learned to make this > happens. > > Creating two vlans with their respective interface for communicate between > each ip scope. > set vlan create 26,28 > set host vlan 26 > > In router mode: > interface vlan 26 > set ip address 192.168.26.1 mask 255.255.255.0 no shutdown > > interface vlan 28 > set ip address 192.168.28.10 mask 255.255.255.0 ip helper-address <ip address > of dhcp server> no shutdown > > In dhcp server port connected on Switch: > set vlan egress fe.1.x 26,28 tagged > set port vlan fe.1.x 26 no-modify-egress > > *** the dhcp server must contain the two scopes with the router option been > the same of the interface created in the switch. The tagged command is saying > that will pass two or more vlans from that port. The no-modify-egress will > change the pvid value from 1 to 26. *** > > In user ports connected on switch: > set port vlan fe.1.10 28 modify-egress > > *** the vlan value will change according the user port *** > > With this config you will be able to reach the dhcp server if you already > have one on vlan 26 from vlan 28 > > Hope this work, > Egbert > > Sent from my iPhone > > On Sep 11, 2010, at 10:32 AM, Mike Hall <[email protected]> wrote: > >> OK..Thanks William. >> >> Here is the config. Ideally, I would like to reach the VLAN 2 from my >> router which is 192.168.26.1. The C2 IP is 192.168.26.136 and VLAN two is >> 192.168.28.10. >> >> >> >> C2(su)->show config >> This command shows non-default configurations only. >> Use 'show config all' to show both default and non-default configurations. >> >> begin >> ! >> #***** NON-DEFAULT CONFIGURATION ***** ! >> ! >> #Router Configuration >> router >> enable >> configure >> interface vlan 2 >> no shutdown >> ip address 192.168.28.10 255.255.255.0 exit exit exit exit >> >> #arp >> ! >> >> #arpinspection >> ! >> >> #banner >> ! >> >> #cdp >> ! >> >> #ciscodp >> ! >> >> #console >> ! >> >> #dhcps >> ! >> >> #dhcpsnooping >> ! >> >> #eapol >> ! >> >> #flowcontrol >> ! >> >> #garp >> ! >> >> #gvrp >> ! >> >> #history >> ! >> >> #igmp >> ! >> >> #inlinepower >> ! >> >> #ip >> set ip address 192.168.26.135 mask 255.255.255.0 gateway 192.168.26.1 >> ! >> >> #ipv6 >> ! >> >> #lacp >> ! >> >> #length >> ! >> >> #lldp >> ! >> >> #linkflap >> ! >> >> #logging >> ! >> >> #logout >> set logout 60 >> ! >> >> #mac >> ! >> >> #macauthentication >> ! >> >> #maclock >> ! >> >> #mtu >> ! >> >> #multiauth >> ! >> >> #newaddrtrap >> ! >> >> #nodealias >> ! >> >> #cos setting >> ! >> >> #cos state >> ! >> >> #cos port-config >> ! >> >> #cos port-resource >> ! >> >> #cos reference >> ! >> >> #policy >> ! >> >> #port >> set port vlan fe.1.10 2 >> ! >> >> #prompt >> ! >> >> #pwa >> ! >> >> #radius >> ! >> >> #rmon alarm >> ! >> >> #rmon capture >> ! >> >> #rmon channel >> ! >> >> #rmon event >> ! >> >> #rmon filter >> ! >> >> #rmon history >> ! >> >> #rmon stats >> ! >> >> #snmp >> set snmp access ro security-model v1 exact read All notify All >> nonvolatile set snmp access ro security-model v2c exact read All >> notify All nonvolatile set snmp access public security-model v1 exact >> read All write All notify All non volatile set snmp access public >> security-model v2c exact read All write All notify All no nvolatile >> set snmp access public security-model usm exact read All write All >> notify All no nvolatile set snmp community >> :3fb03022e4966512343b511c263dcf1240739359ec6cad7d8c6277007e7e >> 0657521e0641967b150156: >> set snmp group ro user ro security-model v1 set snmp group public user >> public security-model v1 set snmp group ro user ro security-model v2c >> set snmp group public user public security-model v2c set snmp group >> public user public security-model usm set snmp user public >> authentication md5 :3f1357d0d919d45f7b021886721fb6b6: priva cy >> :3f1357d0d919d45f7b021886721fb6b6: >> set snmp view viewname All subtree 1 >> ! >> >> #sntp >> ! >> >> #spantree >> ! >> >> #ssh >> ! >> >> #ssl >> ! >> >> #summertime >> ! >> >> #system >> set switch member 1 5 >> ! >> >> #telnet >> ! >> >> #tftp >> ! >> >> #timezone >> ! >> >> #vlan >> set vlan create 2 >> set vlan name 2 "mike" >> clear vlan egress 1 fe.1.10 >> set vlan egress 2 fe.1.10 untagged >> ! >> >> #vlanauthorization >> ! >> >> #webview >> ! >> >> #width >> ! >> end >> >> >> C2(su)-> >> >> -----Original Message----- >> From: William Olive [mailto:[email protected]] >> Sent: Friday, September 10, 2010 10:15 PM >> To: Enterasys Customer Mailing List >> Subject: RE: [enterasys] C2 VLAN >> >> A post of your config will help. >> >> Billo >> Data Communications Co-Ordinator >> Information Technology & Telecommunications Hunter New England Health >> Service ph 0249 213804 fax 0249 213038 >> [email protected] >> ________________________________________ >> From: Mike Hall [[email protected]] >> Sent: Saturday, 11 September 2010 8:54 AM >> To: Enterasys Customer Mailing List >> Subject: re:[enterasys] C2 VLAN >> >> Hello, >> >> I'm a new-bee here and was hoping to get help on setting up a vlan on port >> 10 of a C2. I have an IP of 192.168.28.10 on this port 10 and can ping it >> from the host. >> >> The Host IP is 192.168.26.135. However, if I put a laptop into port 10 and >> give it an ip address of 192.168.28.11, I cannot ping it from the host (or >> vice verse). Any idea what I am missing? >> >> Thanks >> >> --- >> To unsubscribe from enterasys, send email to [email protected] with the >> body: unsubscribe enterasys [email protected] >> >> --- >> To unsubscribe from enterasys, send email to [email protected] with the >> body: unsubscribe enterasys [email protected] >> >> --- >> To unsubscribe from enterasys, send email to [email protected] with the >> body: unsubscribe enterasys [email protected] > > --- > To unsubscribe from enterasys, send email to [email protected] with the body: > unsubscribe enterasys [email protected] > > > > --- > To unsubscribe from enterasys, send email to [email protected] with the body: > unsubscribe enterasys [email protected] --- To unsubscribe from enterasys, send email to [email protected] with the body: unsubscribe enterasys [email protected]
