On a 2911 with a VWIC3-1MFT-T1/E1, is there a special configuration that I need to do to make it data-only? We don't need voice yet, and all the configurations that I've seen as I read through hundreds of posts talk about configuring the card for voice, and so far zilch for data-only. My configuration is as follows:
! card type t1 0 0 ! ... ! controller T1 0/0/0 cablelength long 0db channel-group 0 timeslots 1-24 ! ... ! interface Serial0/0/0:0 description T1 to ISP ip address 192.168.0.2 255.255.255.252 !
As you can see, I used configuration examples I found on the Internet, which I found to be the right way to configure the VWIC3 according to the Cisco manual. This must be the bare minimum configuration to get it working. However, I feel that this configuration is for voice, and may hinder data traffic. If someone can point me in the right direction, that would be great.
I do not see anything in the config that you posted that looks to be oriented to voice. You asked to be pointed in the right direction and as far as I can tell you are going in the right direction already.
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...