05-14-2015 01:32 PM - edited 03-05-2019 01:28 AM
Ok I need some help on this one.
I have spent about 6 hours scouring the internet but nothing even comes close to helping.
I have installed a VWIC3-2MFT-T1/E1 into a 1921 as you can see from these outputs from 'Show diag' and 'sho inv':
WIC Slot 0:
VWIC3-2MFT-T1/E1 - 2-Port RJ-48 Multiflex Trunk - T1/E1
Hardware Revision : 1.0
Top Assy. Part Number : 800-34658-01
Part Number : 73-13420-01
Board Revision : B0
Deviation Number : 0
Fab Version : 05
PCB Serial Number : FOC19038ER3
Version Identifier : V01
Product (FRU) Number : VWIC3-2MFT-T1/E1
CLEI Code : COUIA7NCAA
RMA Test History : 00
RMA Number : 0-0-0-0
RMA History : 00
EEPROM format version 4
EEPROM contents (hex):
NAME: "VWIC3-2MFT-T1/E1 - 2-Port RJ-48 Multiflex Trunk - T1/E1 on Slot 0 SubSlot 0", DESCR: "VWIC3-2MFT-T1/E1 - 2-Port RJ-48 Multiflex Trunk - T1/E1"
PID: VWIC3-2MFT-T1/E1 , VID: V01 , SN: FOC19038ER3
I also added the following:
card type t1 0 0
controller T1 0/0/0
cablelength long 0db
And I am expecting to see Serial interfaces now in the output of 'sho ip int brie' but here is what I am seeing:
Interface IP-Address OK? Method Status Protocol
Embedded-Service-Engine0/0 unassigned YES NVRAM administratively down down
GigabitEthernet0/0 10.10.10.10 YES NVRAM administratively down down
GigabitEthernet0/1 unassigned YES NVRAM administratively down down
Loopback0 10.27.249.164 YES NVRAM up up
Loopback1 unassigned YES unset up up
NVI0 10.27.249.164 YES unset up up
Oh the IOS is Version 15.4(3)M
05-15-2015 01:45 AM
Can u paste the complete output of "sh ver"
05-15-2015 10:42 AM
Cisco IOS Software, C1900 Software (C1900-UNIVERSALK9-M), Version 15.4(3)M, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2014 by Cisco Systems, Inc.
Compiled Mon 21-Jul-14 17:38 by prod_rel_team
ROM: System Bootstrap, Version 15.0(1r)M16, RELEASE SOFTWARE (fc1)
BSD6454 uptime is 21 hours, 54 minutes
System returned to ROM by reload at 19:40:58 UTC Thu May 14 2015
System image file is "usbflash0:c1900-universalk9-mz.SPA.154-3.M.bin"
Last reload type: Normal Reload
Last reload reason: Reload Command
This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.
A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html
If you require further assistance please contact us by sending email to
export@cisco.com.
Cisco CISCO1921/K9 (revision 1.0) with 487424K/36864K bytes of memory.
Processor board ID FTX184682KJ
2 Gigabit Ethernet interfaces
1 Serial interface
1 terminal line
2 Channelized T1/PRI ports
DRAM configuration is 64 bits wide with parity disabled.
255K bytes of non-volatile configuration memory.
249840K bytes of USB Flash usbflash0 (Read/Write)
License Info:
License UDI:
-------------------------------------------------
Device# PID SN
-------------------------------------------------
*1 CISCO1921/K9 FTX184682KJ
Technology Package License Information for Module:'c1900'
------------------------------------------------------------------------
Technology Technology-package Technology-package
Current Type Next reboot
------------------------------------------------------------------------
ipbase ipbasek9 Permanent ipbasek9
security None None None
data None None None
NtwkEss None None None
Configuration register is 0x2102
05-15-2015 02:01 AM
hi,
could you add these lines?
network-clock-participate wic 0
network-clock-select 1 T1 0/0/0
isdn switch-type <TYPE> <<< DEPENDS WITH SP/VENDOR (USUALLY primary-net5)
#isdn switch-type ?
primary-4ess Lucent 4ESS switch type for the U.S.
primary-5ess Lucent 5ESS switch type for the U.S.
primary-dms100 Northern Telecom DMS-100 switch type for the U.S.
primary-dpnss DPNSS switch type for Europe
primary-net5 NET5 switch type for UK, Europe, Asia and Australia
primary-ni National ISDN Switch type for the U.S.
primary-ntt NTT switch type for Japan
primary-qsig QSIG switch type
primary-ts014 TS014 switch type for Australia (obsolete)
05-15-2015 04:47 AM
Under the command controller t1 add this line
channel-group 1 timeslots 1-24
HTH
Rick
05-15-2015 07:15 AM
nice rick! forgot that one :)
05-15-2015 07:44 AM
This is my final goal:
interface Serial0/0/0
description ATT MPLS T1
bandwidth 3072
no ip address
encapsulation frame-relay
no fair-queue
service-module t1 timeslots 1-48
service-module t1 fdl both
frame-relay lmi-type cisco
!
interface Serial0/0/0.777 point-to-point
description ATT MPLS T1 ePVC to Fidelity IFS ATT MPLS Cloud
bandwidth 3072
ip address 10.10.10.10 255.255.255.252
no ip proxy-arp
ip accounting output-packets
ip flow ingress
ip nat outside
frame-relay interface-dlci 777 IETF
05-15-2015 07:58 AM
I do not understand what you are telling us in your most recent post which describes your final goal. Are you telling us that it is now working? Or are you telling us that for some reason it is still not working?
Have you added the channel-group timeslot command that I suggested? That is the step at which the serial interfaces actually get created.
I believe that the card that you are using for serial interfaces will require configuration a bit different from what you describe as your final goal. In particular I believe that it will not use the service-module commands and the serial interface identification will be slightly different.
HTH
Rick
05-15-2015 10:40 AM
The above added final goal is what I am trying to accomplish.
I made the change channel-group 1 timeslots 1-24.
After this I see the Serial interface as S0/0/0:1.
Can I add the subinterface s0/0/0.777 now?
05-15-2015 10:56 AM
Yes. When you configure the channel-group is when you actually get the serial interfaces created. Now you should have no problem in configuring the subinterfaces under the serial interfaces that were created.
Note that the serial interface identifier might be a bit different from s0/0/0.777.
If you are not sure, or if you try it and it does not work, then post the output of show ip interface brief. That should clarify the serial interface identifier to which you add the subinterface.
HTH
Rick
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide