5660 and vlans

[Anonymous]

I'm a bit behind the times.

On the 5660 I can set up virtual interfaces on a single physical interface.   My question is simply what do you connect to that physical interface that will recognize the virtual interfaces?

In my situation, this is a rather simple network.

Upstream ISP   <==>  NV 5660  <==> NV 1335   <==> clients and other NV switches

The NV1335 had been used as a router, but we were running into speed issues, so it will be just a switch when the NV5660 gets up and running.

We have 4 subnets (VLANs) on the NV1335  Need to route between two of them, the others need internet access, but do not need to talk to each other.

So getting back to my main question.    If I set a port on the NV1335 to trunk the vlans and then assign those vlans as virtual interfaces on a single physical interface on the NV5660, will that work?

[jayh]

You won't need VLAN interfaces on the 1335 once you're finished other than one to assign an IP to the switch itself for management. IP routing, addressing, and services will be on the 5660. Set up a trunk between the 5660 and 1335, extend the VLANs over it and build the VLAN interfaces on the 5660.

[Anonymous]

Is setting up a trunk on the 5660 just a matter of setting up the virtual interfaces on a single interface?   There doesn't seem to be any trunk commands on the 5660.

[thebearak]

Just to complete this, yes, setting the virtual interfaces with the ce-vlan-id on the same physical interface creates a trunk.   Example below.  

interface gigabit-eth 0/5
no shutdown
!
!
interface gigabit-eth 0/5.1
ce-vlan-id 26
ip address 10.26.26.1 255.255.255.0
!
interface gigabit-eth 0/5.2
ce-vlan-id 192
ip address 192.168.100.1 255.255.255.0
!
interface gigabit-eth 0/5.3
ce-vlan-id 40
ip address 10.40.40.1 255.255.255.0
!
interface gigabit-eth 0/5.4
ce-vlan-id 85
ip address 10.85.85.1 255.255.255.0

Creates 4 VLANs, 4, 26, 85, 192 over the Trunk interface Gig 0/5