cancelar
Mostrando los resultados de 
Buscar en lugar de 
Quiere decir: 
cancel
442
Visitas
0
ÚTIL
7
Respuestas

MultiLayer Switch IPv6 with Vlans

Estebanvargas
Level 1
Level 1

Estebanvargas_1-1730663848715.png

Hi, I'm setting up a network lab in Cisco Packet Tracer where a Multilayer Switch (MLS) acts as a DHCPv6 server for many VLANs, assigning IPv6 addresses to devices in those VLANs. I also have a router that is configured to route traffic between these VLANs. The idea is that the MLS will assign IPv6 addresses to devices in each VLAN using Stateful DHCPv6, but they are not currently receiving addresses.

Configured VLANs:
VLAN 10 (Name: Guest) (PC 9 and 7)
VLAN 20 (Name: Internal) (PC 6 and
VLAN 40 (Name: ServerPrinters)
VLAN 99 (Name: Native, used as management VLAN and native on trunks)

Configurations done:
1. Router Configuration
IPv6 routing enabled on the router.
Subinterfaces created for each VLAN, with IPv6 addresses assigned and managed-config-flag and other-config-flag flags enabled.
I originally tried to use ipv6 dhcp relay destination to redirect DHCPv6 requests to the MLS, but this command generated errors, so it was omitted.

Code that I used:

ipv6 unicast-routing

interface FastEthernet0/0.10
description Conexión a VLAN 10 - Guest
encapsulation dot1Q 10
ipv6 address 2001:1200:A12::1/64
ipv6 nd managed-config-flag
ipv6 nd other-config-flag

interface FastEthernet0/0.20
description Conexión a VLAN 20 - Internal
encapsulation dot1Q 20
ipv6 address 2001:1200:C12::1/64
ipv6 nd managed-config-flag
ipv6 nd other-config-flag

interface FastEthernet0/0.40
description Conexión a VLAN 40 - ServerPrinters
encapsulation dot1Q 40
ipv6 address 2001:1200:D22::1/64
ipv6 nd managed-config-flag
ipv6 nd other-config-flag

interface FastEthernet0/0.99
description Conexión a VLAN 99 - Native
encapsulation dot1Q 99 native
ipv6 address 2001:1200:C99::1/64
ipv6 nd managed-config-flag
ipv6 nd other-config-flag

MLS Configuration
DHCPv6 server configured in the MLS for each VLAN.
DHCPv6 pools created with IPv6 prefixes, DNS servers, and domain names.
Each VLAN interface configured with its IPv6 address and assigned to the corresponding DHCPv6 pool.

Configuration:

ipv6 unicast-routing

ipv6 dhcp pool DHCPV6_Guest
address prefix 2001:1200:A12::/64
dns-server 2001:1200::53
domain-name guest.local

ipv6 dhcp pool DHCPV6_Internal
address prefix 2001:1200:C12::/64
dns-server 2001:1200::53
domain-name internal.local

ipv6 dhcp pool DHCPV6_ServerPrinters
address prefix 2001:1200:D22::/64
dns-server 2001:1200::53
domain-name serverprinters.local

ipv6 dhcp pool DHCPV6_Native
address prefix 2001:1200:C99::/64
dns-server 2001:1200::53
domain-name native.local

interface Vlan10
ipv6 address 2001:1200:A12::1/64
ipv6 dhcp server DHCPV6_Guest

interface Vlan20
ipv6 address 2001:1200:C12::1/64
ipv6 dhcp server DHCPV6_Internal

interface Vlan40
ipv6 address 2001:1200:D22::1/64
ipv6 dhcp server DHCPV6_ServerPrinters

interface Vlan99
ipv6 address 2001:1200:C99::1/64
ipv6 dhcp server DHCPV6_Native

Diagnostics Completed
- I confirmed that the VLANs are correctly configured on both devices, and the trunks are allowing traffic from all VLANs.
- I tried with static IPv6 addresses and I can ping the addresses configured on the router and the MLS, so there is connectivity between the devices.

If you know what is wrong or what else I can  do I will be grateful

 

 

 

7 RESPUESTAS 7

@Estebanvargas 

  Did you create the vlans among all switch?

 Can I see your pkt file? you need to zip in order to attach here

Estebanvargas
Level 1
Level 1

This is the project

What´s wrong? I checked one PC and it is getting IPv6 via DHCP

FlavioMiranda_0-1730712577336.png

 

Estebanvargas
Level 1
Level 1

It's getting an SLAAC IPv6 and the MLS is configurated to give Stateful Ips

I dont believe you can go farther than that with PacketTracer. 

What you can try is use a server as DHCP, not the switch. 

This is the topology they gave me, I need to configure it like this

Statefull DHCPv6 requires command we can not see on the PacketTracer device.  Not in the DHCP scope but in interfaces.