This is Akash.
Have query regarding internal vlan, we have Cisco 6500 switch with IOS version
s72033-adventerprisek9_wan-mz.122-33.SXI9, we have not configured ipv6 multicast still when we run the showw internal vlan usage we can see vlan 34 is used for IPv6 Multicast Egress multicast want to know how i can free this vlan for normal use and why it is showing used as internal vlan even tough we have not enable the ipv6 multicast.
CoreSwitch#sh vlan internal usage
34 IPv6 Multicast Egress multicast
quick response on this will realy appriciate.
Thanks in advance for your kind support.
Seems this internal VLAN is reserved for optimization of replicating multicast packets:
"Egress replication mode uses a special internal egress VLAN to distribute the replicated multicast packets to all egress (destination) modules. Membership to this internal VLAN is determined simply by including all egress-capable modules in a distribution list. Furthermore, there is only a single egress VLAN (per VRF). Hence, there is no guarantee that all programming messages will arrive (once transmitted), and all groups and associated egress modules share the same context."
The only thing you can choose is if to allocate internal VLANs from the bottom or from the top:
vlan internal allocation policy ascending or descending
The only thing I know of is to start assigning it from the top instead with the descending command. But I think that requires a reboot.
Not sure how the internal VLANs are assigned but probably that was the first available one? Do you use other VLANs up to 33?
Thanks for your quick response Daniel.
yes up to 33 vlans we have created, 34 vlan is not created may be that is the reason system has taken this vlan.
my question is can we disable the optimization of replicating multicast packets and what would be the impact of same.
to free vlan 34.
if no then other option would be
vlan internal allocation policy descending
this will require reload?
I'm not sure if it can be disabled. Do you run IPv6 multicast routing? It seems the allocation is done on bootup:
So the last time you booted VLAN 34 was allocated. Seems there is no easy solution unless it can be disabled or to reboot.