11-30-2011 09:13 AM - edited 03-07-2019 03:40 AM
Hi Experts,
I am facing problem to configure MWAM. I have installed MWAM module in 6506-E slot 2 with sup720-3B. After installing MWAM the Status is PwrDown. I tried to turn on the power but its not happening. MWAM is installed in slot 2 and here is the result of show module 2
My Sup720-eB IOS image is s72033-advipservicesk9_wan-mz.122-33.SXJ1.bin
6506-E#show module 2
Mod Ports Card Type Model Serial No.
--- ----- -------------------------------------- ------------------ -----------
2 3 MWAM Module WS-SVC-MWAM-1 SAD081203GK
Mod MAC addresses Hw Fw Sw Status
--- ---------------------------------- ------ ------------ ------------ -------
2 0003.feae.bb8c to 0003.feae.bb93 3.0 Unknown Unknown PwrDown
Mod Online Diag Status
---- -------------------
2 Not Applicable
Kindly tell me what could be the reason. And how to solve this issue.
Solved! Go to Solution.
12-02-2011 12:49 AM
Greetings Faisal,
Unfortunately the MWAM is not supported in releases after SXF, from the release notes:
"Release 12.2(33)SXH and later releases do not support the following hardware:
WS-SVC-MWAM-1 Multi-Processor WAN Application Module"
http://www.cisco.com/en/US/docs/switches/lan/catalyst6500/ios/12.2SX/release/notes/hardware.html
Typically you would have a syslog message such as "unsupported card type" when trying to power up an unsupported module. You would need to downgrade to 12.2SXF to use your MWAM in this chassis.
Hope this helps,
/Phil
12-02-2011 12:49 AM
Greetings Faisal,
Unfortunately the MWAM is not supported in releases after SXF, from the release notes:
"Release 12.2(33)SXH and later releases do not support the following hardware:
WS-SVC-MWAM-1 Multi-Processor WAN Application Module"
http://www.cisco.com/en/US/docs/switches/lan/catalyst6500/ios/12.2SX/release/notes/hardware.html
Typically you would have a syslog message such as "unsupported card type" when trying to power up an unsupported module. You would need to downgrade to 12.2SXF to use your MWAM in this chassis.
Hope this helps,
/Phil
12-03-2011 12:19 PM
Dear Phillips,
Thank you so much for your help. It is 100% fine . My MWAM is up. I am using 12.2(18)SXF. Thanks again.
Now I am facing another problem. I wonder if you can help me. My GGSN is not responding to PDP-Context request.
Here is my configuration.
aaa new-model
!
!
aaa acc
ounting suppress null-username
aaa accounting update periodic 5
aaa accounting network vmuk start-stop group radius
!
aaa pod server auth-type any server-key mysecret
aaa session-id common
clock timezone GMT 0
!
!
ip cef
ip name-server x.x.x.x
!
!
!
interface GigabitEthernet0/0
no ip address
!
interface GigabitEthernet0/0.172
description ### GRX User Space ###
encapsulation dot1Q 172
ip address x.x.x.x. x.x.x.x
!
interface GigabitEthernet0/0.569
description ### GRX Space ###
encapsulation dot1Q xxx
ip address x.x.x.x x.x.x.x
!
interface Virtual-Template1
ip unnumbered GigabitEthernet0/0.xxx
encapsulation gtp
gprs access-point-list gprs
!
!
no ip http server
!
!
!
gprs access-point-list gprs
access-point 1
access-point-name mobile.barablu.com
ip-address-pool dhcp-proxy-client
aggregate auto
dhcp-server x.x.x.x y.y.y.y
dhcp-gateway-address x.x.x.x
network-request-activation
dns primary x.x.x.x secondar y y.y.y.y
!
!
!
gprs mcc xxx mnc xxx
gprs gtp echo-timer dynamic enable
gprs gtp n3-requests 8
gprs gtp ip udp ignore checksum
gprs default ip-address-pool dhcp-proxy-client
gprs qos map canonical-qos
gprs qos default-response requested
!
radius-server host x.x.x.xauth-port 1645 acct-port 1646 non-standard key 7 xxxxxxxxxxxxxxxxxxxxx
radius-server key 7 xxxxxxxxxxxxxxxxxxxxxx
radius-server vsa send accounting
!
and here is debug log
Dec 3 20:03:04.489: GPRS:proc_udp_input: signalling packet from X.X.X.X(2123)
Dec 3 20:03:04.489: GPRS:gtp_mgmt_process: wakes up
Dec 3 20:03:04.489: GPRS:major 2 minor 2;
Dec 3 20:03:04.489: GPRS:gtp_mgmt_process_qinput: GTPv1C_MSG
Dec 3 20:03:04.489: GPRS:sequence num 0xF571
Dec 3 20:03:04.489: GPRS:gtpv1_ggsnmsg_create_pdp_context_req: TEID 00 from X.X.X.X
Dec 3 20:03:04.489: GPRS:Found PDP Context
Dec 3 20:03:04.489: GTP IE:extract_teid: return teid 0xE8AA3414
Dec 3 20:03:04.489: GPRS:apn_lookup:apn TEST.COM
Dec 3 20:03:04.489: GPRS: found apn TEST.COM
Dec 3 20:03:04.489: GPRS:pdpmcb_create_by_teid:teid 0x0000001F, pdpmcb 2356587C
Dec 3 20:03:04.489: GPRS:pdp_create_by_tid:tid 3204011040029159, pdp 235558C0
Dec 3 20:03:04.489: GPRS:sequence num 0xF571
Dec 3 20:03:04.489: GTP IE:3204011040029159:IMSI[2]:3204011040029109
Dec 3 20:03:04.489: GTP IE:3204011040029159:Recover[14]:142
Dec 3 20:03:04.489: GTP IE:3204011040029159:Selection Mode[15]:0
Dec 3 20:03:04.489: MS or network provided APN, subscribed verified
Dec 3 20:03:04.489: GTP IE:3204011040029159:TEID Data1[16]:0x235558F8
Dec 3 20:03:04.489: GTP IE:3204011040029159:TEID Control[17]:0x235558F0
Dec 3 20:03:04.489: GTP IE:3204011040029159:NSAPI[20]:5
Dec 3 20:03:04.489: GTP IE:3204011040029159:Charging Characteristics[26]:0x8
Dec 3 20:03:04.489: GPRS:apn_lookup:apn TEST.COM
Dec 3 20:03:04.489: GPRS: found apn TEST.COM
Dec 3 20:03:04.489: GTP IE:3204011040029159:APN[131]:TEST.COM
Dec 3 20:03:04.489: GPRS:apn_lookup:apn TEST.COM
Dec 3 20:03:04.489: GPRS: found apn TEST.COM
Dec 3 20:03:04.489: GTP IE:3204011040029159:PCO[132](PAP):
Dec 3 20:03:04.489: GTP IE:3204011040029159:PCO[132](IPCP primary DNS addr):0.0.0.0
Dec 3 20:03:04.489: GTP IE:3204011040029159:PCO[132](IPCP secondary DNS addr):0.0.0.0
Dec 3 20:03:04.489: GTP IE:3204011040029159:GSN Addr[133](sig):X.X.X.X
Dec 3 20:03:04.489: GTP IE:3204011040029159:GSN Addr[133](data):149.254.198.75
Dec 3 20:03:04.489: GTP IE:3204011040029159:MSISDN[134]:447574370984
Dec 3 20:03:04.489: GTP IE:3204011040029159:QoS[135]:value incorrect
Dec 3 20:03:04.489: GTP IE:3204011040029159:QoS[135]:len 13 incorrect
Dec 3 20:03:04.489: GTP IE:3204011040029159:Mandatory IE invalid 135 flag:0x10000002
Dec 3 20:03:04.489: %GTP-2-PDPACTIVATIONFAIL: GTP PDP activation/update failed, GSN: 0.0.0.0, TID: 00, Reason: Mandatory info element invalid
Dec 3 20:03:04.489: GPRS:sequence num 0xF571
Dec 3 20:03:04.489: GPRS:3204011040029159:gtp_msg_send_res: pdp_entry 0x235558C0, replymsg 0x11, cause 0xC9
Dec 3 20:03:04.489: %GTP-0-GTPv1PACKETPARSINGERROR: GSN: Y.Y.Y.Y, TEID: E8AA3414, APN: NULL, Reason: Mandatory ie incorrect
Dec 3 20:03:04.489: GPRS:GTP enqueues pak of size 16 (refcount 1)
Dec 3 20:03:04.489: GPRS:gprs_output:idb 0x2244743C, pkt 0x22E51E0C, path 0x0, pdp 0x0
Dec 3 20:03:04.489: GPRS:ip=C005618, ip->prot=17
Dec 3 20:03:04.489: GPRS:path_lookup: path to (dst:port) (X.X.X.X:2123)
Dec 3 20:03:04.489: GPRS::src Y.Y.Y.Y,dst X.X.X.X,srcport 2123,dstport 2123
Dec 3 20:03:04.489: GPRS:: Calling ip_udp_send()
Dec 3 20:03:04.489: GPRS:3204011040029159:pdp_cleanup: refcnt 0, pdp 235558C0, apn 239FC8D0, path 0, data_path 0
Dec 3 20:03:04.489: GPRS:3204011040029159:stop_msgtimer: PDP context 235558C0 timer 23555960
Dec 3 20:03:04.489: GPRS:3204011040029159:msgtimer is already off, pdp 235558C0
Dec 3 20:03:04.489: GPRS:3204011040029159:stop_purgetimer:pdp 235558C0
Dec 3 20:03:04.489: GPRS:radix_free: freeup PDP 235558C0
Dec 3 20:03:04.489: GPRS:pdpmcb_cleanup: refcnt 0, pdpmcb 2356587C, apn 239FC8D0
Dec 3 20:03:04.489: GPRS:gtp_apn_pdpmcb_unlink_one: list_remove() error
Dec 3 20:03:04.489: GPRS:gtp_mgmt_process_qinput: msg(17) processed
Dec 3 20:03:04.489: GPRS:gtp_mgmt_process: sleep
Dec 3 20:03:04.489: GPRS:proc_udp_input: signalling packet from X.X.X.X(2123)
Dec 3 20:03:04.489: GPRS:gtp_mgmt_process: wakes up
Dec 3 20:03:04.489: GPRS:major 2 minor 2;
Dec 3 20:03:04.489: GPRS:gtp_mgmt_process_qinput: GTPv1C_MSG
Dec 3 20:03:04.489: GPRS:sequence num 0xF571
Dec 3 20:03:04.489: GPRS:gtpv1_ggsnmsg_create_pdp_context_req: TEID 00 from X.X.X.X
Dec 3 20:03:04.489: GPRS:Found PDP Context
Dec 3 20:03:04.489: GTP IE:extract_teid: return teid 0xE8AA3414
Dec 3 20:03:04.489: GPRS:apn_lookup:apn TEST.COM
Dec 3 20:03:04.489: GPRS: found apn TEST.COM
Dec 3 20:03:04.489: GPRS:pdpmcb_create_by_teid:teid 0x0000001F, pdpmcb 2356587C
Dec 3 20:03:04.489: GPRS:pdp_create_by_tid:tid 3204011040029159, pdp 235558C0
Dec 3 20:03:04.489: GPRS:sequence num 0xF571
Dec 3 20:03:04.489: GTP IE:3204011040029159:IMSI[2]:3204011040029109
Dec 3 20:03:04.489: GTP IE:3204011040029159:Recover[14]:142
Dec 3 20:03:04.489: GTP IE:3204011040029159:Selection Mode[15]:0
Dec 3 20:03:04.489: MS or network provided APN, subscribed verified
Dec 3 20:03:04.489: GTP IE:3204011040029159:TEID Data1[16]:0x235558F8
Dec 3 20:03:04.489: GTP IE:3204011040029159:TEID Control[17]:0x235558F0
Dec 3 20:03:04.489: GTP IE:3204011040029159:NSAPI[20]:5
Dec 3 20:03:04.489: GTP IE:3204011040029159:Charging Characteristics[26]:0x8
Dec 3 20:03:04.489: GPRS:apn_lookup:apn TEST.COM
Dec 3 20:03:04.489: GPRS: found apn TEST.COM
Dec 3 20:03:04.489: GTP IE:3204011040029159:APN[131]:TEST.COM
Dec 3 20:03:04.489: GPRS:apn_lookup:apn TEST.COM
Dec 3 20:03:04.489: GPRS: found apn TEST.COM
Dec 3 20:03:04.489: GTP IE:3204011040029159:PCO[132](PAP):
Dec 3 20:03:04.489: GTP IE:3204011040029159:PCO[132](IPCP primary DNS addr):0.0.0.0
Dec 3 20:03:04.489: GTP IE:3204011040029159:PCO[132](IPCP secondary DNS addr):0.0.0.0
Dec 3 20:03:04.489: GTP IE:3204011040029159:GSN Addr[133](sig):X.X.X.X
Dec 3 20:03:04.489: GTP IE:3204011040029159:GSN Addr[133](data):149.254.198.75
Dec 3 20:03:04.489: GTP IE:3204011040029159:MSISDN[134]:447574370984
Dec 3 20:03:04.489: GTP IE:3204011040029159:QoS[135]:value incorrect
Dec 3 20:03:04.489: GTP IE:3204011040029159:QoS[135]:len 13 incorrect
Dec 3 20:03:04.489: GTP IE:3204011040029159:Mandatory IE invalid 135 flag:0x10000002
Dec 3 20:03:04.489: %GTP-2-PDPACTIVATIONFAIL: GTP PDP activation/update failed, GSN: 0.0.0.0, TID: 00, Reason: Mandatory info element invalid
Dec 3 20:03:04.489: GPRS:sequence num 0xF571
Dec 3 20:03:04.489: GPRS:3204011040029159:gtp_msg_send_res: pdp_entry 0x235558C0, replymsg 0x11, cause 0xC9
Dec 3 20:03:04.489: %GTP-0-GTPv1PACKETPARSINGERROR: GSN: Y.Y.Y.Y, TEID: E8AA3414, APN: NULL, Reason: Mandatory ie incorrect
Dec 3 20:03:04.489: GPRS:GTP enqueues pak of size 16 (refcount 1)
Dec 3 20:03:04.489: GPRS:gprs_output:idb 0x2244743C, pkt 0x22E51E0C, path 0x0, pdp 0x0
Dec 3 20:03:04.489: GPRS:ip=C005618, ip->prot=17
Dec 3 20:03:04.489: GPRS:path_lookup: path to (dst:port) (X.X.X.X:2123)
Dec 3 20:03:04.489: GPRS::src Y.Y.Y.Y,dst X.X.X.X,srcport 2123,dstport 2123
Dec 3 20:03:04.489: GPRS:: Calling ip_udp_send()
Dec 3 20:03:04.489: GPRS:3204011040029159:pdp_cleanup: refcnt 0, pdp 235558C0, apn 239FC8D0, path 0, data_path 0
Dec 3 20:03:04.489: GPRS:3204011040029159:stop_msgtimer: PDP context 235558C0 timer 23555960
Dec 3 20:03:04.489: GPRS:3204011040029159:msgtimer is already off, pdp 235558C0
Dec 3 20:03:04.489: GPRS:3204011040029159:stop_purgetimer:pdp 235558C0
Dec 3 20:03:04.489: GPRS:radix_free: freeup PDP 235558C0
Dec 3 20:03:04.489: GPRS:pdpmcb_cleanup: refcnt 0, pdpmcb 2356587C, apn 239FC8D0
Dec 3 20:03:04.489: GPRS:gtp_apn_pdpmcb_unlink_one: list_remove() error
Dec 3 20:03:04.489: GPRS:gtp_mgmt_process_qinput: msg(17) processed
Dec 3 20:03:04.489: GPRS:gtp_mgmt_process: sleep
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