Unnecessary base vaccess created for vtemplate subinterface
"The Virtual-Access1 interface is a Base VtMgr vaccess (also seen in
the output of "show interface virtual-access 1"). This is created for
internal use and is not freed.
When PPPoE or PPPoA are enabled, a base vaccess is created for each application. Similarly, when a VPDN tunnel is terminated on the LNS, a base vaccess is created for it. These base vaccess are needed to support sub-interfaces, utilizing the various vectors
in the base vaccess's hwidb. These base vaccesses are not freed, and this is the expected behavior."
Then there is also CSCdy60608 (not viewable), which I think eliminates this VA creation for any image that has the PPPoE subsystem (regardless
of PPPoE being configured).
This appears to be fixed in 12.3.Can you try and load 12.3, and check if the problem persists ?
Thank you. I will upgrade to 12.3 and update the results.
There is another weird problem that I have been facing with virtual-access interface on 7200 VXR.
I am using PPP multilink on the dialer interface. And there also are manually defined multilinks grouping multiple channels in channelized E1.
Now when I administratively shut down channelized E1 multilink, the dialer dials as per interesting traffic. And virtual-access interface also gets into UP status. The problem is thst now if I administratively no shut on channelized E1 multilink then it remains in down state till the time virtual-access is up. It seems as if virtual-access interface is somehow conflicting with multilink interfaces. To bring multilink up I have to administratively shut down the dialer interface which brings virtual-access interface down.
Are there any known issues for such problem or am I missing something??
Regarding the channel group allocation for each site can u revert whether you have induvidual 64K connecting ur DC to the respective locations (like faizabad,kanpur) or is it a single 384K or 256K link connecting the locations ??
If thats the case u can modify the config by mapping the timeslots to a particular channelgroup instead of configuring different serial itnerfaces and binding them under a single multilink interface.
controller E1 5/0
channel-group 0 timeslots 1-5
description ******** CE FAIZABAD *******
ip address x.x.x.x x.x.x.x
you can do something like wht i hve outlined above i feel that will help u upto a gr8 extent while troubleshooting as well during management purpose..
it represents a single pipe of 384K B/W to location Faizabad...accordingly u can configure for other locations tooo..
We are pleased to announce availability of Beta software for 16.6.3. 16.6.3 will be the second rebuild on the 16.6 release train targeted towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are looking for early feedback from custome...