no you can't.  I got straight from cisco that they have to be 100 meg
full-dux interfaces.
""MADMAN""  wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> Actually on some platforms with the right IOS you can trunk 10 meg ports:
>
> C3660B(config)#inter e2/0.1
> C3660B(config-subif)#encap dot1 1
> C3660B(config-subif)#
>
>   Dave
>
> danny wrote:
>
> > The router's ethernet must be 100 full dux.  You configure subinterfaces
on
> > the ethernet.  a trunking protocol must be configured on each sub with
the
> > corresponding vlan #.  The router will route between Vlans.
> >
> > Hope this helps.
> >
> > Danny
> > ""George Siaw""  wrote in message
> > [EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> > > Thanks for all your responses.
> > >
> > > One last question though. For external router, routing between vlans
if
> > > I have just one FastEthernet interface on the router can I route
between
> > > vlans?
> > >
> > > George.
> > >
> > > -----Original Message-----
> > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf
Of
> > > Scott H.
> > > Sent: 23 March 2002 00:53
> > > To: [EMAIL PROTECTED]
> > > Subject: Re: ISL Trunking from a h/w's perspective [7:39246]
> > >
> > > The only time the SC0 interface comes into play is for telnet into the
> > > box.
> > > If you have any 100 MB ports on your switch, you can run trunking.
> > >
> > > set trunk (mod/port) on isl
> > >
> > > If this trunk is running into a router, you need to create the
> > > subinterfaces
> > > on the router to enable routing between VLANS.
> > >
> > > int fa1/0.100
> > > ip address (the subnet of the vlan)
> > > encap isl (the vlan #)
> > >
> > > HTH,
> > > Scott
> > >
> > > ""George Siaw""  wrote in message
> > > [EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> > > > Do I need an Sc0 port when routing between Vlans? However, there's
no
> > > > uplink module on neither of my supervisor engines. Would you know a
> > > s/w
> > > > work around without having to buy the module?
> > > >
> > > > George.
> > > >
> > > > -----Original Message-----
> > > > From: Larry Letterman [mailto:[EMAIL PROTECTED]]
> > > > Sent: 23 March 2002 00:17
> > > > To: George Siaw; [EMAIL PROTECTED]
> > > > Subject: RE: ISL Trunking from a h/w's perspective [7:39246]
> > > >
> > > > You dont have to configure SC0 interface to do isl or dot1q. Its
only
> > > > needed
> > > > for management, telnet etc...
> > > >
> > > >
> > > > Larry Letterman
> > > > Cisco Systems
> > > > [EMAIL PROTECTED]
> > > >
> > > >
> > > > -----Original Message-----
> > > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf
Of
> > > > George Siaw
> > > > Sent: Friday, March 22, 2002 3:45 PM
> > > > To: [EMAIL PROTECTED]
> > > > Subject: ISL Trunking from a h/w's perspective [7:39246]
> > > >
> > > >
> > > > Guys,
> > > >
> > > >
> > > >
> > > > Any ideas as how I can configure isl trunking without an Sc0 port on
> > > the
> > > > supervisor engines? Can I configure on of the ports to assume this
> > > > position i.e. Sc0? If so what are the cmds?
> > > >
> > > >
> > > >
> > > > Regards,
> > > >
> > > > George.
> > > >
> > > >
> > > >
> > > > Configs as below:
> > > >
> > > >
> > > >
> > > > Console> (enable) sh mod 1
> > > >
> > > > Mod Module-Name         Ports Module-Type           Model
> > > Serial-Num
> > > > Status
> > > >
> > > > --- ------------------- ----- --------------------- ---------
> > > ---------
> > > > -------
> > > >
> > > > 1   ENGINE-1            0     Supervisor III        WS-X5530
> > > 012144234
> > > > ok
> > > >
> > > >
> > > >
> > > > Mod MAC-Address(es)                        Hw     Fw         Sw
> > > >
> > > > --- -------------------------------------- ------ ----------
> > > > -----------------
> > > >
> > > > 1   00-50-f0-0c-64-00 to 00-50-f0-0c-67-ff 3.0    3.1.2      4.3(1a)
> > > >
> > > >
> > > >
> > > > Mod Sub-Type Sub-Model Sub-Serial Sub-Hw
> > > >
> > > > --- -------- --------- ---------- ------
> > > >
> > > > 1   NFFC+    WS-F5531  0012153640 1.0
> > > >
> > > >
> > > >
> > > > Console> (enable) sh mod
> > > >
> > > > Mod Module-Name         Ports Module-Type           Model
> > > Serial-Num
> > > > Status
> > > >
> > > > --- ------------------- ----- --------------------- ---------
> > > ---------
> > > > -------
> > > >
> > > > 1   ENGINE-1            0     Supervisor III        WS-X5530
> > > 012144234
> > > > ok
> > > >
> > > > 2   ENGINE-2            0     Supervisor III        WS-X5530
> > > 010867093
> > > > standby
> > > >
> > > > 3   CCIE_LAB-0          24    10/100BaseTX Ethernet WS-X5224
> > > 012154555
> > > > ok
> > > >
> > > > 4   CCIE_LAB-1          24    10/100BaseTX Ethernet WS-X5224
> > > 009616952
> > > > ok
> > > >
> > > > 5   CCIE_LAB-2          24    10/100BaseTX Ethernet WS-X5224
> > > 016372420
> > > > ok
> > > >
> > > >
> > > >
> > > > Mod MAC-Address(es)                        Hw     Fw         Sw
> > > >
> > > > --- -------------------------------------- ------ ----------
> > > > -----------------
> > > >
> > > > 1   00-50-f0-0c-64-00 to 00-50-f0-0c-67-ff 3.0    3.1.2      4.3(1a)
> > > >
> > > > 2   00-50-f0-0c-64-00 to 00-50-f0-0c-67-ff 2.0    3.1.2      4.3(1a)
> > > >
> > > > 3   00-50-53-c4-42-08 to 00-50-53-c4-42-1f 1.4    3.1(1)     4.3(1a)
> > > >
> > > > 4   00-10-7b-83-36-d8 to 00-10-7b-83-36-ef 1.4    3.1(1)     4.3(1a)
> > > >
> > > > 5   00-30-b6-29-95-48 to 00-30-b6-29-95-5f 1.5    3.1(1)     4.3(1a)
> > > >
> > > >
> > > >
> > > > Mod Sub-Type Sub-Model Sub-Serial Sub-Hw
> > > >
> > > > --- -------- --------- ---------- ------
> > > >
> > > > 1   NFFC+    WS-F5531  0012153640 1.0
> > > >
> > > > 2   NFFC     WS-F5521  0010866222 1.1
> > > >
> > > >
> > > >
> > > > Console> (enable) sh ver
> > > >
> > > > WS-C5505 Software, Version McpSW: 4.3(1a) NmpSW: 4.3(1a)
> > > >
> > > > Copyright (c) 1995-1998 by Cisco Systems
> > > >
> > > > NMP S/W compiled on Nov 23 1998, 15:22:34
> > > >
> > > > MCP S/W compiled on Nov 23 1998, 15:19:30
> > > >
> > > >
> > > >
> > > > System Bootstrap Version: 3.1.2
> > > >
> > > >
> > > >
> > > > Hardware Version: 1.0  Model: WS-C5505  Serial #: 066526573
> > > >
> > > >
> > > >
> > > > Mod Port Model      Serial #  Versions
> > > >
> > >
> --- ---- ---------- --------- ----------------------------------------
> > > >
> > > > 1   0    WS-X5530   012144234 Hw : 3.0
> > > >
> > > >                               Fw : 3.1.2
> > > >
> > > >                               Fw1: 4.2(1)
> > > >
> > > >                               Sw : 4.3(1a)
> > > >
> > > > 2   0    WS-X5530   010867093 Hw : 2.0
> > > >
> > > >                               Fw : 3.1.2
> > > >
> > > >                               Fw1: 4.2(1)
> > > >
> > > >                               Sw : 4.3(1a)
> > > >
> > > > 3   24   WS-X5224   012154555 Hw : 1.4
> > > >
> > > >                               Fw : 3.1(1)
> > > >
> > > >                               Sw : 4.3(1a)
> > > >
> > > > 4   24   WS-X5224   009616952 Hw : 1.4
> > > >
> > > >                               Fw : 3.1(1)
> > > >
> > > >                               Sw : 4.3(1a)
> > > >
> > > > 5   24   WS-X5224   016372420 Hw : 1.5
> > > >
> > > >                               Fw : 3.1(1)
> > > >
> > > >                               Sw : 4.3(1a)
> > > >
> > > >
> > > >
> > > >        DRAM                    FLASH                   NVRAM
> > > >
> > > > Module Total   Used    Free    Total   Used    Free    Total Used
> > > Free
> > > >
> > > > ------ ------- ------- ------- ------- ------- ------- ----- -----
> > > -----
> > > >
> > > > 1       32640K  13381K  19259K   8192K   3984K   4208K  512K  116K
> > > 396K
> > > >
> > > >
> > > >
> > > > Uptime is 0 day, 0 hour, 13 minutes
> > > > _________________________________________________________
> > > > Do You Yahoo!?
> > > > Get your free @yahoo.com address at http://mail.yahoo.com
> --
> David Madland
> CCIE# 2016
> Sr. Network Engineer
> Qwest Communications Inc.
> 612-664-3367
> [EMAIL PROTECTED]




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=39270&t=39246
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Reply via email to