HDLC on dialup async lines
Hi,
I have AS5350 with two PRI's and 60NP.
the dialing end is using HDLC encapsulation.
although the modems are connecting fine, the HDLC handshake is not done and the connection fail.
what is the problem? and how can I use HDLC encapsulation on the async line?
Hello,
this is not really a direct answer to your question, but I know that on ISDN, HDLC does not support dynamic mapping, and you need to have static maps. Not sure in how far that applies to you, but HDLC also does not support any sort of authentication...
Regards,
GP
Similar Messages
-
What is the meant of "line 66"?
I meet a set of access management as follows, does anyone know the use of line 66? Thanks
line con 0
stopbits 1
line aux 0
line 66 (////////// why line 66 required ??)
no activation-character
no exec
transport preferred none
transport input all
transport output all
line vty 0 4
access-class 2 in
password 7 02050D480809
loginI believe that line 66 is an async line on this router. The IOS numbering of lines makes allowances for what might be present in the router as far as numbering async lines is done. It might help to understand the relationship here if you would post the output of show line from this router.
HTH
Rick -
Weird dots, lines, special characters with triggering uevents.
I'm trying to install arch on my uefi laptop and I'm going into UEFI Shell x86_64 v2, letting it load then exiting and starting up the Arch Linux archiso x86_64 UEFI CD and it's just displaying a ton of random dots, lines, underscores, etc. I've tried selecting the boot option and hitting tab to see if I can't add a boot option, but that doesn't even let me append options to it. Here's a picture of what's going on since I don't even know what this is called to begin searching for answers on it.
http://i50.tinypic.com/24njtwl.jpgEd
Can you tell us whether your async line configuration includes the command no exec?
I have seen situations where async lines used for reverse telnet/terminal server and configured with the default setting of exec will send extra/garbage characters to the console of the controlled device.
HTH
Rick -
CSACS capable of dropping lines and users?
Hello
Is Cisco ACS capable of dropping users logged in vthrough a NAS. I have seen a purge option but I dont think this does the trick. I am looking at dropping a specific user from the CSACS ineterface.
Also is it capable of showing what password has been entered by the user while logging in for troubleshooting purposes?.
ThanksFor the first one I mean dropping an already logged in user User on an Async line. (Perhaps resetting the line on the NAS from CSACS).
for the second one I mean actually seeing what the user has entered for his/her password while he/she was logging in, to verify if she is entering a wrong password. (CSACS only gives me a general password incorrect message but I want to see what the password entered was.)
Thanks -
User-land async comms programming questions
I've ported wx200d from linux code to solaris 7/8. It reads data on
com1 from the RadioShack WX200 weather sensor hardware. The
daemon compiles and runs but when it gets killed (any term signal) the
serial port becomes unusable. Restart attempts fail with errors such as:
"wx200d: bind: Address already in use" or "all ports busy".
The C code sets up the async line with termios. Once the port is hosed
trying 'fuser /dev/cua/a' sees nothing, so how do you detect what is
hanging on the line or causing it to block further attempts to use it?
How do you clear it? Is there a user-land command-line app that
will flush/close/reset the serial port? Rebooting does not clear it.
Do I have to do a 'pmadm -r -p zsmon -s ttya' to remove the zsmon
port monitor? Should I be using /dev/term/a instead of /dev/cua/a if
I am only opening the device O_RDONLY? I am frustrated in my
attempts to find how-to's, programmer reference guides, tutorials,
example code, whatever to help me understand impacts of SAF/SAC &c
when programming Solaris 2.x async comms for other than modems
or terminals (ie. Celeste's tutorial &c). I haven't had to deal with UNIX
async comms since Interactive SVR3.2.2 when getty/inittab/uucp was
simple. I have already rtfm'ed: pmadm,sacadm,ttymon,ttyadm,saf,sac...
Pointers? Help? Explanations? TIA. Please Cc replies to:
<[email protected]> or <[email protected]>
regards, calI guess my problem is that I have some basic college experience in digital circuit design, and would like the forms to be programmed and behave in the same fashion as digital logic.
The "Clear Form" menu item, of course, would be equivalent to the reset button.
Perhaps it is possible to hook my code onto the "Clear Form" menu item?
-Ramon -
Site-to-site VPN failover via 3G HWIC
Small problem. Branch utilizes a 2811 router connected via MPLS to core via serial interface. If serial ip sla reachability fails, fire up the cell interface, dial out and connect to the internet. Establish ipsec tunnel to a peer ASA and pass local LAN traffic over the tunnel. Problem is the tunnel does come up and I am 'briefly' able to communicate across the tunnel but then *poof*. No more communication. Tried multiple ideas and thoughts (different encypt, authentication etc). I am thinking that per my config, the IPSEC session is trying to establish before the dialer session is fully up, thus potentially causing problems with the authentication to the peer. Any help would be appreciated. Here is the debug of isakmp, ipsec, dialer and ppp when I manually kill the serial interface:
14th_Street(config)#int s0/1/0:0
14th_Street(config-if)#shut
14th_Street(config-if)#
*Nov 25 17:44:55.011 UTC: %BGP-5-ADJCHANGE: neighbor xxx.xxx.xxx.xxx Down Interface flap
*Nov 25 17:44:55.911 UTC: IPSEC(sa_initiate): Kicking the dialer interface
*Nov 25 17:44:55.911 UTC: Ce0/0/0 DDR: place call
*Nov 25 17:44:55.911 UTC: Ce0/0/0 DDR: Dialing cause ip (s=xxx.xxx.xxx.xxx, d=xxx.xxx.xxx.xxx)
*Nov 25 17:44:55.911 UTC: Ce0/0/0 DDR: Attempting to dial cdma
*Nov 25 17:44:55.911 UTC: CHAT0/0/0: Attempting async line dialer script
*Nov 25 17:44:55.911 UTC: CHAT0/0/0: Dialing using Modem script: cdma & System script: none
*Nov 25 17:44:55.911 UTC: CHAT0/0/0: process started
*Nov 25 17:44:55.911 UTC: CHAT0/0/0: Asserting DTR
*Nov 25 17:44:55.911 UTC: CHAT0/0/0: Chat script cdma started
*Nov 25 17:44:55.915 UTC: IPSEC(sa_initiate): Kicking the dialer interface
*Nov 25 17:44:56.999 UTC: %LINK-5-CHANGED: Interface Serial0/1/0:0, changed state to administratively down
*Nov 25 17:44:56.999 UTC: Se0/1/0:0 PPP: Sending Acct Event[Down] id[1]
*Nov 25 17:44:56.999 UTC: Se0/1/0:0 CDPCP: State is Closed
*Nov 25 17:44:56.999 UTC: Se0/1/0:0 IPCP: State is Closed
*Nov 25 17:44:57.003 UTC: Se0/1/0:0 PPP: Phase is TERMINATING
*Nov 25 17:44:57.003 UTC: Se0/1/0:0 LCP: State is Closed
*Nov 25 17:44:57.003 UTC: Se0/1/0:0 PPP: Phase is DOWN
*Nov 25 17:44:57.003 UTC: Se0/1/0:0 IPCP: Remove route to xxx.xxx.xxx.xxx
*Nov 25 17:44:57.007 UTC: IPSEC(sa_initiate): Kicking the dialer interface
*Nov 25 17:44:57.099 UTC: %TRACKING-5-STATE: 1 ip sla 1 reachability Up->Down
*Nov 25 17:44:57.811 UTC: CHAT0/0/0: Chat script cdma finished, status = Success
*Nov 25 17:44:58.031 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/0:0, changed state to down
*Nov 25 17:44:58.031 UTC: IPSEC(sa_initiate): Kicking the dialer interface
*Nov 25 17:44:58.035 UTC: IPSEC(sa_initiate): Kicking the dialer interface
*Nov 25 17:44:58.911 UTC: IPSEC(sa_initiate): Kicking the dialer interface
*Nov 25 17:45:00.027 UTC: %LINK-3-UPDOWN: Interface Cellular0/0/0, changed state to up
*Nov 25 17:45:00.027 UTC: Ce0/0/0 DDR: Dialer statechange to up
*Nov 25 17:45:00.027 UTC: Ce0/0/0 DDR: Dialer call has been placed
*Nov 25 17:45:00.031 UTC: Ce0/0/0 PPP: Using dialer call direction
*Nov 25 17:45:00.031 UTC: Ce0/0/0 PPP: Treating connection as a callout
*Nov 25 17:45:00.031 UTC: Ce0/0/0 PPP: Session handle[FD000001] Session id[2]
*Nov 25 17:45:00.031 UTC: Ce0/0/0 PPP: Phase is ESTABLISHING, Active Open
*Nov 25 17:45:00.031 UTC: Ce0/0/0 PPP: Authorization NOT required
*Nov 25 17:45:00.031 UTC: Ce0/0/0 PPP: No remote authentication for call-out
*Nov 25 17:45:00.031 UTC: Ce0/0/0 LCP: O CONFREQ [Closed] id 1 len 20
*Nov 25 17:45:00.031 UTC: Ce0/0/0 LCP: ACCM 0x000A0000 (0x0206000A0000)
*Nov 25 17:45:00.031 UTC: Ce0/0/0 LCP: MagicNumber 0x13255539 (0x050613255539)
*Nov 25 17:45:00.031 UTC: Ce0/0/0 LCP: PFC (0x0702)
*Nov 25 17:45:00.031 UTC: Ce0/0/0 LCP: ACFC (0x0802)
*Nov 25 17:45:00.031 UTC: IPSEC(sa_initiate): Kicking the dialer interface
*Nov 25 17:45:00.035 UTC: Ce0/0/0 LCP: I CONFREQ [REQsent] id 0 len 24
*Nov 25 17:45:00.035 UTC: Ce0/0/0 LCP: MRU 1500 (0x010405DC)
*Nov 25 17:45:00.035 UTC: Ce0/0/0 LCP: ACCM 0x00000000 (0x020600000000)
*Nov 25 17:45:00.035 UTC: Ce0/0/0 LCP: MagicNumber 0xCD87E220 (0x0506CD87E220)
*Nov 25 17:45:00.035 UTC: Ce0/0/0 LCP: PFC (0x0702)
*Nov 25 17:45:00.035 UTC: Ce0/0/0 LCP: ACFC (0x0802)
*Nov 25 17:45:00.035 UTC: Ce0/0/0 LCP: O CONFACK [REQsent] id 0 len 24
*Nov 25 17:45:00.035 UTC: Ce0/0/0 LCP: MRU 1500 (0x010405DC)
*Nov 25 17:45:00.035 UTC: Ce0/0/0 LCP: ACCM 0x00000000 (0x020600000000)
*Nov 25 17:45:00.035 UTC: Ce0/0/0 LCP: MagicNumber 0xCD87E220 (0x0506CD87E220)
*Nov 25 17:45:00.035 UTC: Ce0/0/0 LCP: PFC (0x0702)
*Nov 25 17:45:00.035 UTC: Ce0/0/0 LCP: ACFC (0x0802)
*Nov 25 17:45:00.035 UTC: Ce0/0/0 LCP: I CONFACK [ACKsent] id 1 len 20
*Nov 25 17:45:00.035 UTC: Ce0/0/0 LCP: ACCM 0x000A0000 (0x0206000A0000)
*Nov 25 17:45:00.035 UTC: Ce0/0/0 LCP: MagicNumber 0x13255539 (0x050613255539)
*Nov 25 17:45:00.035 UTC: Ce0/0/0 LCP: PFC (0x0702)
*Nov 25 17:45:00.035 UTC: Ce0/0/0 LCP: ACFC (0x0802)
*Nov 25 17:45:00.035 UTC: Ce0/0/0 LCP: State is Open
*Nov 25 17:45:00.035 UTC: Ce0/0/0 PPP: Phase is FORWARDING, Attempting Forward
*Nov 25 17:45:00.035 UTC: Ce0/0/0 PPP: Phase is ESTABLISHING, Finish LCP
*Nov 25 17:45:00.039 UTC: Ce0/0/0 PPP: Phase is UP
*Nov 25 17:45:00.039 UTC: Ce0/0/0 IPCP: O CONFREQ [Closed] id 1 len 22
*Nov 25 17:45:00.039 UTC: Ce0/0/0 IPCP: Address 0.0.0.0 (0x030600000000)
*Nov 25 17:45:00.039 UTC: Ce0/0/0 IPCP: PrimaryDNS 0.0.0.0 (0x810600000000)
*Nov 25 17:45:00.039 UTC: Ce0/0/0 IPCP: SecondaryDNS 0.0.0.0 (0x830600000000)
*Nov 25 17:45:00.039 UTC: Ce0/0/0 PPP: Process pending ncp packets
*Nov 25 17:45:00.039 UTC: Ce0/0/0 IPCP: I CONFREQ [REQsent] id 0 len 10
*Nov 25 17:45:00.039 UTC: Ce0/0/0 IPCP: Address xxx.xxx.xxx.xxx (0x030642AEA8C0)
*Nov 25 17:45:00.039 UTC: Ce0/0/0 IPCP: O CONFACK [REQsent] id 0 len 10
*Nov 25 17:45:00.039 UTC: Ce0/0/0 IPCP: Address xxx.xxx.xxx.xxx (0x030642AEA8C0)
*Nov 25 17:45:00.043 UTC: Ce0/0/0 IPCP: I CONFNAK [ACKsent] id 1 len 22
*Nov 25 17:45:00.043 UTC: Ce0/0/0 IPCP: Address xxx.xxx.xxx.xxx (0x0306A69F5EA9)
*Nov 25 17:45:00.043 UTC: Ce0/0/0 IPCP: PrimaryDNS xxx.xxx.xxx.xxx (0x810642AE4721)
*Nov 25 17:45:00.043 UTC: Ce0/0/0 IPCP: SecondaryDNS xxx.xxx.xxx.xxx (0x8306454E600E)
*Nov 25 17:45:00.043 UTC: Ce0/0/0 IPCP: O CONFREQ [ACKsent] id 2 len 22
*Nov 25 17:45:00.043 UTC: Ce0/0/0 IPCP: Address xxx.xxx.xxx.xxx (0x0306A69F5EA9)
*Nov 25 17:45:00.043 UTC: Ce0/0/0 IPCP: PrimaryDNS xxx.xxx.xxx.xxx (0x810642AE4721)
*Nov 25 17:45:00.043 UTC: Ce0/0/0 IPCP: SecondaryDNS xxx.xxx.xxx.xxx (0x8306454E600E)
*Nov 25 17:45:00.043 UTC: Ce0/0/0 IPCP: I CONFNAK [ACKsent] id 2 len 4
*Nov 25 17:45:00.043 UTC: Ce0/0/0 IPCP: O CONFREQ [ACKsent] id 3 len 22
*Nov 25 17:45:00.043 UTC: Ce0/0/0 IPCP: Address xxx.xxx.xxx.xxx (0x0306A69F5EA9)
*Nov 25 17:45:00.043 UTC: Ce0/0/0 IPCP: PrimaryDNS xxx.xxx.xxx.xxx (0x810642AE4721)
*Nov 25 17:45:00.047 UTC: Ce0/0/0 IPCP: SecondaryDNS xxx.xxx.xxx.xxx (0x8306454E600E)
*Nov 25 17:45:00.047 UTC: Ce0/0/0 IPCP: I CONFNAK [ACKsent] id 3 len 4
*Nov 25 17:45:00.047 UTC: Ce0/0/0 IPCP: O CONFREQ [ACKsent] id 4 len 22
*Nov 25 17:45:00.047 UTC: Ce0/0/0 IPCP: Address xxx.xxx.xxx.xxx (0x0306A69F5EA9)
*Nov 25 17:45:00.047 UTC: Ce0/0/0 IPCP: PrimaryDNS xxx.xxx.xxx.xxx (0x810642AE4721)
*Nov 25 17:45:00.047 UTC: Ce0/0/0 IPCP: SecondaryDNS xxx.xxx.xxx.xxx (0x8306454E600E)
*Nov 25 17:45:00.051 UTC: Ce0/0/0 IPCP: I CONFACK [ACKsent] id 4 len 22
*Nov 25 17:45:00.051 UTC: Ce0/0/0 IPCP: Address xxx.xxx.xxx.xxx (0x0306A69F5EA9)
*Nov 25 17:45:00.051 UTC: Ce0/0/0 IPCP: PrimaryDNS xxx.xxx.xxx.xxx (0x810642AE4721)
*Nov 25 17:45:00.051 UTC: Ce0/0/0 IPCP: SecondaryDNS xxx.xxx.xxx.xxx (0x8306454E600E)
*Nov 25 17:45:00.051 UTC: Ce0/0/0 IPCP: State is Open
*Nov 25 17:45:00.051 UTC: Ce0/0/0 IPCP: Install negotiated IP interface address xxx.xxx.xxx.xxx
*Nov 25 17:45:00.059 UTC: IPSEC(recalculate_mtu): reset sadb_root 4975A1A8 mtu to 1500
*Nov 25 17:45:00.063 UTC: Ce0/0/0 IPCP: Install route to xxx.xxx.xxx.xxx
*Nov 25 17:45:00.063 UTC: Ce0/0/0 DDR: dialer protocol up
*Nov 25 17:45:00.067 UTC: Ce0/0/0 IPCP: Add link info for cef entry xxx.xxx.xxx.xxx
*Nov 25 17:45:01.027 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Cellular0/0/0, changed state to up
*Nov 25 17:45:29.763 UTC: DDR: IP Address is (xxx.xxx.xxx.xxx) for (Ce0/0/0)
*Nov 25 17:45:29.763 UTC: IPSEC(sa_request): ,
(key eng. msg.) OUTBOUND local= xxx.xxx.xxx.xxx, remote= xxx.xxx.xxx.xxx,
local_proxy= 192.168.221.0/255.255.255.0/0/0 (type=4),
remote_proxy= 0.0.0.0/0.0.0.0/0/0 (type=4),
protocol= ESP, transform= esp-3des esp-sha-hmac (Tunnel),
lifedur= 86400s and 4608000kb,
spi= 0x0(0), conn_id= 0, keysize= 0, flags= 0x0
*Nov 25 17:45:29.767 UTC: ISAKMP:(0): SA request profile is (NULL)
*Nov 25 17:45:29.767 UTC: ISAKMP: Created a peer struct for xxx.xxx.xxx.xxx, peer port 500
*Nov 25 17:45:29.767 UTC: ISAKMP: New peer created peer = 0x47AC3A08 peer_handle = 0x80000002
*Nov 25 17:45:29.767 UTC: ISAKMP: Locking peer struct 0x47AC3A08, refcount 1 for isakmp_initiator
*Nov 25 17:45:29.767 UTC: ISAKMP: local port 500, remote port 500
*Nov 25 17:45:29.767 UTC: ISAKMP: set new node 0 to QM_IDLE
*Nov 25 17:45:29.771 UTC: insert sa successfully sa = 4B6322B8
*Nov 25 17:45:29.771 UTC: ISAKMP:(0):Can not start Aggressive mode, trying Main mode.
*Nov 25 17:45:29.771 UTC: ISAKMP:(0):found peer pre-shared key matching xxx.xxx.xxx.xxx
*Nov 25 17:45:29.771 UTC: ISAKMP:(0): constructed NAT-T vendor-rfc3947 ID
*Nov 25 17:45:29.771 UTC: ISAKMP:(0): constructed NAT-T vendor-07 ID
*Nov 25 17:45:29.771 UTC: ISAKMP:(0): constructed NAT-T vendor-03 ID
*Nov 25 17:45:29.771 UTC: ISAKMP:(0): constructed NAT-T vendor-02 ID
*Nov 25 17:45:29.771 UTC: ISAKMP:(0):Input = IKE_MESG_FROM_IPSEC, IKE_SA_REQ_MM
*Nov 25 17:45:29.771 UTC: ISAKMP:(0):Old State = IKE_READY New State = IKE_I_MM1
*Nov 25 17:45:29.771 UTC: ISAKMP:(0): beginning Main Mode exchange
*Nov 25 17:45:29.771 UTC: ISAKMP:(0): sending packet to xxx.xxx.xxx.xxx my_port 500 peer_port 500 (I) MM_NO_STATE
*Nov 25 17:45:29.771 UTC: ISAKMP:(0):Sending an IKE IPv4 Packet.
*Nov 25 17:45:29.927 UTC: ISAKMP (0:0): received packet from xxx.xxx.xxx.xxx dport 500 sport 500 Global (I) MM_NO_STATE
*Nov 25 17:45:29.927 UTC: ISAKMP:(0):Input = IKE_MESG_FROM_PEER, IKE_MM_EXCH
*Nov 25 17:45:29.931 UTC: ISAKMP:(0):Old State = IKE_I_MM1 New State = IKE_I_MM2
*Nov 25 17:45:29.931 UTC: ISAKMP:(0): processing SA payload. message ID = 0
*Nov 25 17:45:29.931 UTC: ISAKMP:(0): processing vendor id payload
*Nov 25 17:45:29.931 UTC: ISAKMP:(0): processing IKE frag vendor id payload
*Nov 25 17:45:29.931 UTC: ISAKMP:(0):Support for IKE Fragmentation not enabled
*Nov 25 17:45:29.931 UTC: ISAKMP:(0):found peer pre-shared key matching xxx.xxx.xxx.xxx
*Nov 25 17:45:29.931 UTC: ISAKMP:(0): local preshared key found
*Nov 25 17:45:29.931 UTC: ISAKMP : Scanning profiles for xauth ...
*Nov 25 17:45:29.931 UTC: ISAKMP:(0):Checking ISAKMP transform 1 against priority 1 policy
*Nov 25 17:45:29.931 UTC: ISAKMP: encryption 3DES-CBC
*Nov 25 17:45:29.931 UTC: ISAKMP: hash SHA
*Nov 25 17:45:29.931 UTC: ISAKMP: default group 2
*Nov 25 17:45:29.931 UTC: ISAKMP: auth pre-share
*Nov 25 17:45:29.931 UTC: ISAKMP: life type in seconds
*Nov 25 17:45:29.931 UTC: ISAKMP: life duration (VPI) of 0x0 0x1 0x51 0x80
*Nov 25 17:45:29.931 UTC: ISAKMP:(0):atts are acceptable. Next payload is 0
*Nov 25 17:45:29.931 UTC: ISAKMP:(0):Acceptable atts:actual life: 0
*Nov 25 17:45:29.931 UTC: ISAKMP:(0):Acceptable atts:life: 0
*Nov 25 17:45:29.931 UTC: ISAKMP:(0):Fill atts in sa vpi_length:4
*Nov 25 17:45:29.931 UTC: ISAKMP:(0):Fill atts in sa life_in_seconds:86400
*Nov 25 17:45:29.931 UTC: ISAKMP:(0):Returning Actual lifetime: 86400
*Nov 25 17:45:29.931 UTC: ISAKMP:(0)::Started lifetime timer: 86400.
*Nov 25 17:45:29.971 UTC: ISAKMP:(0): processing vendor id payload
*Nov 25 17:45:29.971 UTC: ISAKMP:(0): processing IKE frag vendor id payload
*Nov 25 17:45:29.971 UTC: ISAKMP:(0):Support for IKE Fragmentation not enabled
*Nov 25 17:45:29.971 UTC: ISAKMP:(0):Input = IKE_MESG_INTERNAL, IKE_PROCESS_MAIN_MODE
*Nov 25 17:45:29.971 UTC: ISAKMP:(0):Old State = IKE_I_MM2 New State = IKE_I_MM2
*Nov 25 17:45:29.971 UTC: ISAKMP:(0): sending packet to xxx.xxx.xxx.xxx my_port 500 peer_port 500 (I) MM_SA_SETUP
*Nov 25 17:45:29.975 UTC: ISAKMP:(0):Sending an IKE IPv4 Packet.
*Nov 25 17:45:29.975 UTC: ISAKMP:(0):Input = IKE_MESG_INTERNAL, IKE_PROCESS_COMPLETE
*Nov 25 17:45:29.975 UTC: ISAKMP:(0):Old State = IKE_I_MM2 New State = IKE_I_MM3
*Nov 25 17:45:30.171 UTC: ISAKMP (0:0): received packet from xxx.xxx.xxx.xxx dport 500 sport 500 Global (I) MM_SA_SETUP
*Nov 25 17:45:30.171 UTC: ISAKMP:(0):Input = IKE_MESG_FROM_PEER, IKE_MM_EXCH
*Nov 25 17:45:30.171 UTC: ISAKMP:(0):Old State = IKE_I_MM3 New State = IKE_I_MM4
*Nov 25 17:45:30.171 UTC: ISAKMP:(0): processing KE payload. message ID = 0
*Nov 25 17:45:30.219 UTC: ISAKMP:(0): processing NONCE payload. message ID = 0
*Nov 25 17:45:30.219 UTC: ISAKMP:(0):found peer pre-shared key matching xxx.xxx.xxx.xxx
*Nov 25 17:45:30.223 UTC: ISAKMP:(1001): processing vendor id payload
*Nov 25 17:45:30.223 UTC: ISAKMP:(1001): vendor ID is Unity
*Nov 25 17:45:30.223 UTC: ISAKMP:(1001): processing vendor id payload
*Nov 25 17:45:30.223 UTC: ISAKMP:(1001): vendor ID seems Unity/DPD but major 71 mismatch
*Nov 25 17:45:30.223 UTC: ISAKMP:(1001): vendor ID is XAUTH
*Nov 25 17:45:30.223 UTC: ISAKMP:(1001): processing vendor id payload
*Nov 25 17:45:30.223 UTC: ISAKMP:(1001): speaking to another IOS box!
*Nov 25 17:45:30.223 UTC: ISAKMP:(1001): processing vendor id payload
*Nov 25 17:45:30.223 UTC: ISAKMP:(1001):vendor ID seems Unity/DPD but hash mismatch
*Nov 25 17:45:30.223 UTC: ISAKMP:(1001):Input = IKE_MESG_INTERNAL, IKE_PROCESS_MAIN_MODE
*Nov 25 17:45:30.223 UTC: ISAKMP:(1001):Old State = IKE_I_MM4 New State = IKE_I_MM4
*Nov 25 17:45:30.223 UTC: ISAKMP:(1001):Send initial contact
*Nov 25 17:45:30.223 UTC: ISAKMP:(1001):SA is doing pre-shared key authentication using id type ID_IPV4_ADDR
*Nov 25 17:45:30.223 UTC: ISAKMP (0:1001): ID payload
next-payload : 8
type : 1
address : xxx.xxx.xxx.xxx
protocol : 17
port : 500
length : 12
*Nov 25 17:45:30.223 UTC: ISAKMP:(1001):Total payload length: 12
*Nov 25 17:45:30.227 UTC: ISAKMP:(1001): sending packet to xxx.xxx.xxx.xxx my_port 500 peer_port 500 (I) MM_KEY_EXCH
*Nov 25 17:45:30.227 UTC: ISAKMP:(1001):Sending an IKE IPv4 Packet.
*Nov 25 17:45:30.227 UTC: ISAKMP:(1001):Input = IKE_MESG_INTERNAL, IKE_PROCESS_COMPLETE
*Nov 25 17:45:30.227 UTC: ISAKMP:(1001):Old State = IKE_I_MM4 New State = IKE_I_MM5
*Nov 25 17:45:30.495 UTC: ISAKMP (0:1001): received packet from xxx.xxx.xxx.xxx dport 500 sport 500 Global (I) MM_KEY_EXCH
*Nov 25 17:45:30.495 UTC: ISAKMP:(1001): processing ID payload. message ID = 0
*Nov 25 17:45:30.495 UTC: ISAKMP (0:1001): ID payload
next-payload : 8
type : 1
address : xxx.xxx.xxx.xxx
protocol : 17
port : 500
length : 12
*Nov 25 17:45:30.495 UTC: ISAKMP:(0):: peer matches *none* of the profiles
*Nov 25 17:45:30.495 UTC: ISAKMP:(1001): processing HASH payload. message ID = 0
*Nov 25 17:45:30.495 UTC: ISAKMP:received payload type 17
*Nov 25 17:45:30.495 UTC: ISAKMP:(1001): processing vendor id payload
*Nov 25 17:45:30.495 UTC: ISAKMP:(1001): vendor ID is DPD
*Nov 25 17:45:30.495 UTC: ISAKMP:(1001):SA authentication status:
authenticated
*Nov 25 17:45:30.495 UTC: ISAKMP:(1001):SA has been authenticated with xxx.xxx.xxx.xxx
*Nov 25 17:45:30.495 UTC: ISAKMP: Trying to insert a peer xxx.xxx.xxx.xxx/xxx.xxx.xxx.xxx/500/, and inserted successfully 47AC3A08.
*Nov 25 17:45:30.495 UTC: ISAKMP:(1001):Input = IKE_MESG_FROM_PEER, IKE_MM_EXCH
*Nov 25 17:45:30.499 UTC: ISAKMP:(1001):Old State = IKE_I_MM5 New State = IKE_I_MM6
*Nov 25 17:45:30.499 UTC: ISAKMP:(1001):Input = IKE_MESG_INTERNAL, IKE_PROCESS_MAIN_MODE
*Nov 25 17:45:30.499 UTC: ISAKMP:(1001):Old State = IKE_I_MM6 New State = IKE_I_MM6
*Nov 25 17:45:30.499 UTC: ISAKMP:(1001):Input = IKE_MESG_INTERNAL, IKE_PROCESS_COMPLETE
*Nov 25 17:45:30.499 UTC: ISAKMP:(1001):Old State = IKE_I_MM6 New State = IKE_P1_COMPLETE
*Nov 25 17:45:30.499 UTC: ISAKMP:(1001):beginning Quick Mode exchange, M-ID of 458622291
*Nov 25 17:45:30.503 UTC: ISAKMP:(1001):QM Initiator gets spi
*Nov 25 17:45:30.503 UTC: ISAKMP:(1001): sending packet to xxx.xxx.xxx.xxx my_port 500 peer_port 500 (I) QM_IDLE
*Nov 25 17:45:30.503 UTC: ISAKMP:(1001):Sending an IKE IPv4 Packet.
*Nov 25 17:45:30.503 UTC: ISAKMP:(1001):Node 458622291, Input = IKE_MESG_INTERNAL, IKE_INIT_QM
*Nov 25 17:45:30.503 UTC: ISAKMP:(1001):Old State = IKE_QM_READY New State = IKE_QM_I_QM1
*Nov 25 17:45:30.503 UTC: ISAKMP:(1001):Input = IKE_MESG_INTERNAL, IKE_PHASE1_COMPLETE
*Nov 25 17:45:30.503 UTC: ISAKMP:(1001):Old State = IKE_P1_COMPLETE New State = IKE_P1_COMPLETE
*Nov 25 17:45:30.715 UTC: ISAKMP (0:1001): received packet from xxx.xxx.xxx.xxx dport 500 sport 500 Global (I) QM_IDLE
*Nov 25 17:45:30.715 UTC: ISAKMP:(1001): processing HASH payload. message ID = 458622291
*Nov 25 17:45:30.715 UTC: ISAKMP:(1001): processing SA payload. message ID = 458622291
*Nov 25 17:45:30.715 UTC: ISAKMP:(1001):Checking IPSec proposal 1
*Nov 25 17:45:30.715 UTC: ISAKMP: transform 1, ESP_3DES
*Nov 25 17:45:30.715 UTC: ISAKMP: attributes in transform:
*Nov 25 17:45:30.715 UTC: ISAKMP: SA life type in seconds
*Nov 25 17:45:30.715 UTC: ISAKMP: SA life duration (VPI) of 0x0 0x1 0x51 0x80
*Nov 25 17:45:30.715 UTC: ISAKMP: SA life type in kilobytes
*Nov 25 17:45:30.715 UTC: ISAKMP: SA life duration (VPI) of 0x0 0x46 0x50 0x0
*Nov 25 17:45:30.715 UTC: ISAKMP: encaps is 1 (Tunnel)
*Nov 25 17:45:30.715 UTC: ISAKMP: authenticator is HMAC-SHA
*Nov 25 17:45:30.715 UTC: ISAKMP:(1001):atts are acceptable.
*Nov 25 17:45:30.715 UTC: IPSEC(validate_proposal_request): proposal part #1
*Nov 25 17:45:30.715 UTC: IPSEC(validate_proposal_request): proposal part #1,
(key eng. msg.) INBOUND local= xxx.xxx.xxx.xxx, remote= xxx.xxx.xxx.xxx,
local_proxy= 192.168.221.0/255.255.255.0/0/0 (type=4),
remote_proxy= 0.0.0.0/0.0.0.0/0/0 (type=4),
protocol= ESP, transform= NONE (Tunnel),
lifedur= 0s and 0kb,
spi= 0x0(0), conn_id= 0, keysize= 0, flags= 0x0
*Nov 25 17:45:30.715 UTC: Crypto mapdb : proxy_match
src addr : 192.168.221.0
dst addr : 0.0.0.0
protocol : 0
src port : 0
dst port : 0
*Nov 25 17:45:30.715 UTC: ISAKMP:(1001): processing NONCE payload. message ID = 458622291
*Nov 25 17:45:30.715 UTC: ISAKMP:(1001): processing ID payload. message ID = 458622291
*Nov 25 17:45:30.715 UTC: ISAKMP:(1001): processing ID payload. message ID = 458622291
*Nov 25 17:45:30.719 UTC: ISAKMP:(1001): processing NOTIFY RESPONDER_LIFETIME protocol 3
spi 399189113, message ID = 458622291, sa = 4B6322B8
*Nov 25 17:45:30.719 UTC: ISAKMP:(1001):SA authentication status:
authenticated
*Nov 25 17:45:30.719 UTC: ISAKMP:(1001): processing responder lifetime
*Nov 25 17:45:30.719 UTC: ISAKMP (1001): responder lifetime of 28800s
*Nov 25 17:45:30.719 UTC: ISAKMP:(1001): Creating IPSec SAs
*Nov 25 17:45:30.719 UTC: inbound SA from xxx.xxx.xxx.xxx to xxx.xxx.xxx.xxx (f/i) 0/ 0
(proxy 0.0.0.0 to 192.168.221.0)
*Nov 25 17:45:30.719 UTC: has spi 0x498026E2 and conn_id 0
*Nov 25 17:45:30.719 UTC: lifetime of 28790 seconds
*Nov 25 17:45:30.719 UTC: lifetime of 4608000 kilobytes
*Nov 25 17:45:30.719 UTC: outbound SA from xxx.xxx.xxx.xxx to xxx.xxx.xxx.xxx (f/i) 0/0
(proxy 192.168.221.0 to 0.0.0.0)
*Nov 25 17:45:30.719 UTC: has spi 0x17CB2479 and conn_id 0
*Nov 25 17:45:30.719 UTC: lifetime of 28790 seconds
*Nov 25 17:45:30.719 UTC: lifetime of 4608000 kilobytes
*Nov 25 17:45:30.719 UTC: ISAKMP:(1001): sending packet to xxx.xxx.xxx.xxx my_port 500 peer_port 500 (I) QM_IDLE
*Nov 25 17:45:30.719 UTC: ISAKMP:(1001):Sending an IKE IPv4 Packet.
*Nov 25 17:45:30.723 UTC: ISAKMP:(1001):deleting node 458622291 error FALSE reason "No Error"
*Nov 25 17:45:30.723 UTC: ISAKMP:(1001):Node 458622291, Input = IKE_MESG_FROM_PEER, IKE_QM_EXCH
*Nov 25 17:45:30.723 UTC: ISAKMP:(1001):Old State = IKE_QM_I_QM1 New State = IKE_QM_PHASE2_COMPLETE
*Nov 25 17:45:30.723 UTC: IPSEC(key_engine): got a queue event with 1 KMI message(s)
*Nov 25 17:45:30.723 UTC: Crypto mapdb : proxy_match
src addr : 192.168.221.0
dst addr : 0.0.0.0
protocol : 0
src port : 0
dst port : 0
*Nov 25 17:45:30.723 UTC: IPSEC(crypto_ipsec_sa_find_ident_head): reconnecting with the same proxies and peer xxx.xxx.xxx.xxx
*Nov 25 17:45:30.723 UTC: IPSEC(policy_db_add_ident): src 192.168.221.0, dest 0.0.0.0, dest_port 0
*Nov 25 17:45:30.723 UTC: IPSEC(create_sa): sa created,
(sa) sa_dest= xxx.xxx.xxx.xxx, sa_proto= 50,
sa_spi= 0x498026E2(1233135330),
sa_trans= esp-3des esp-sha-hmac , sa_conn_id= 2001
*Nov 25 17:45:30.723 UTC: IPSEC(create_sa): sa created,
(sa) sa_dest= xxx.xxx.xxx.xxx, sa_proto= 50,
sa_spi= 0x17CB2479(399189113),
sa_trans= esp-3des esp-sha-hmac , sa_conn_id= 2002
*Nov 25 17:45:30.723 UTC: IPSEC(update_current_outbound_sa): updated peer xxx.xxx.xxx.xxx current outbound sa to SPI 17CB2479
*Nov 25 17:45:46.935 UTC: ISAKMP (0:1001): received packet from xxx.xxx.xxx.xxx dport 500 sport 500 Global (I) QM_IDLE
*Nov 25 17:45:46.935 UTC: ISAKMP: set new node -1909459720 to QM_IDLE
*Nov 25 17:45:46.939 UTC: ISAKMP:(1001): processing HASH payload. message ID = -1909459720
*Nov 25 17:45:46.939 UTC: ISAKMP:(1001): processing NOTIFY DPD/R_U_THERE protocol 1
spi 0, message ID = -1909459720, sa = 4B6322B8
*Nov 25 17:45:46.939 UTC: ISAKMP:(1001):deleting node -1909459720 error FALSE reason "Informational (in) state 1"
*Nov 25 17:45:46.939 UTC: ISAKMP:(1001):Input = IKE_MESG_FROM_PEER, IKE_INFO_NOTIFY
*Nov 25 17:45:46.939 UTC: ISAKMP:(1001):Old State = IKE_P1_COMPLETE New State = IKE_P1_COMPLETE
*Nov 25 17:45:46.939 UTC: ISAKMP:(1001):DPD/R_U_THERE received from peer xxx.xxx.xxx.xxx, sequence 0x7BDFE4C6
*Nov 25 17:45:46.939 UTC: ISAKMP: set new node -777989143 to QM_IDLE
*Nov 25 17:45:46.939 UTC: ISAKMP:(1001):Sending NOTIFY DPD/R_U_THERE_ACK protocol 1
spi 1224841120, message ID = -777989143
*Nov 25 17:45:46.939 UTC: ISAKMP:(1001): seq. no 0x7BDFE4C6
*Nov 25 17:45:46.939 UTC: ISAKMP:(1001): sending packet to xxx.xxx.xxx.xxx my_port 500 peer_port 500 (I) QM_IDLE
*Nov 25 17:45:46.939 UTC: ISAKMP:(1001):Sending an IKE IPv4 Packet.
*Nov 25 17:45:46.939 UTC: ISAKMP:(1001):purging node -777989143
*Nov 25 17:45:46.943 UTC: ISAKMP:(1001):Input = IKE_MESG_FROM_PEER, IKE_MESG_KEEP_ALIVE
*Nov 25 17:45:46.943 UTC: ISAKMP:(1001):Old State = IKE_P1_COMPLETE New State = IKE_P1_COMPLETE
And here is the config:
Building configuration...
Current configuration : 10137 bytes
version 12.4
service pad to-xot
service tcp-keepalives-in
service tcp-keepalives-out
service timestamps debug datetime msec show-timezone
service timestamps log datetime msec show-timezone
service password-encryption
hostname Test
boot-start-marker
boot-end-marker
card type t1 0 1
logging message-counter syslog
logging buffered 4096
aaa new-model
aaa authentication login default local
aaa authentication ppp network local-case
aaa authorization console
aaa authorization exec default local
aaa session-id common
clock timezone EST -5
clock summer-time EDT recurring
network-clock-participate wic 1
network-clock-select 1 T1 0/1/0
dot11 syslog
no ip source-route
ip cef
no ip dhcp use vrf connected
ip dhcp excluded-address 192.168.121.1 192.168.121.99
ip dhcp excluded-address 192.168.121.200 192.168.121.254
ip dhcp excluded-address 192.168.221.1 192.168.221.99
ip dhcp excluded-address 192.168.221.200 192.168.221.254
ip dhcp pool Voice
network 192.168.121.0 255.255.255.0
option 150 ip 10.101.90.6
default-router 192.168.121.254
ip dhcp pool Data
network 192.168.221.0 255.255.255.0
default-router 192.168.221.254
dns-server 10.1.90.189 10.5.100.30
no ip bootp server
no ip domain lookup
ip domain name xxxxxx
ip multicast-routing
no ipv6 cef
multilink bundle-name authenticated
chat-script cdma "" "ATDT#777" TIMEOUT 60 "CONNECT"
voice service voip
allow-connections h323 to h323
allow-connections h323 to sip
allow-connections sip to h323
allow-connections sip to sip
no supplementary-service sip moved-temporarily
fax protocol pass-through g711ulaw
no fax-relay sg3-to-g3
h323
modem passthrough nse codec g711ulaw
sip
header-passing error-passthru
outbound-proxy ipv4:xxx.xxx.xxx.xxx
early-offer forced
midcall-signaling passthru
voice class codec 1
codec preference 1 g711ulaw
codec preference 2 g729r8
voice class h323 1
h225 timeout tcp establish 3
voice translation-rule 1
rule 1 // // type any international
voice translation-rule 3
rule 1 /^8/ //
voice translation-profile International
translate called 1
voice translation-profile OutboundRedirecting
translate called 3
voice-card 0
no dspfarm
dsp services dspfarm
username xx
archive
log config
hidekeys
crypto isakmp policy 1
encr 3des
authentication pre-share
crypto isakmp key xxxxxxxxx address xxx.xxx.xxx.xxx
crypto ipsec transform-set CellFOSet esp-3des esp-sha-hmac
crypto map CellFOMap 1 ipsec-isakmp
set peer xxx.xxx.xxx.xxx
set security-association lifetime seconds 190
set transform-set CellFOSet
match address 100
controller T1 0/1/0
framing esf
linecode b8zs
cablelength long 0db
channel-group 0 timeslots 1-24
ip tftp source-interface FastEthernet0/0.1
track 1 ip sla 1 reachability
class-map match-all VOICE
match ip dscp ef
class-map match-any VOICE-CTRL
match ip dscp af31
match ip dscp cs3
policy-map WAN-EDGE
class VOICE
priority 384
set ip dscp ef
class VOICE-CTRL
set ip dscp af21
bandwidth 32
class class-default
fair-queue
set ip dscp default
interface Loopback0
ip address 192.168.222.21 255.255.255.255
h323-gateway voip interface
h323-gateway voip bind srcaddr 192.168.222.21
interface FastEthernet0/0
description Physical Interface for Data VLAN 10 and Voice VLAN 20
no ip address
ip flow ingress
ip pim sparse-dense-mode
no ip route-cache cef
duplex auto
speed auto
interface FastEthernet0/0.1
description Interface to Data VLAN 10
encapsulation dot1Q 10
ip address 192.168.221.254 255.255.255.0
no ip redirects
no ip unreachables
ip flow ingress
ip flow egress
ip pim sparse-dense-mode
ip virtual-reassembly
no cdp enable
interface FastEthernet0/0.2
description Interface to Voice VLAN 20
encapsulation dot1Q 20
ip address 192.168.121.254 255.255.255.0
no ip redirects
no ip unreachables
ip flow ingress
ip flow egress
ip pim sparse-dense-mode
no cdp enable
interface FastEthernet0/1
description Unused port
no ip address
shutdown
duplex auto
speed auto
no cdp enable
interface Cellular0/0/0
ip address negotiated
ip virtual-reassembly
encapsulation ppp
dialer in-band
dialer string cdma
dialer-group 1
async mode interactive
ppp chap hostname [email protected]
ppp chap password 7 xxxxxxxxxxxxxxxx
ppp ipcp dns request
crypto map CellFOMap
interface Serial0/1/0:0
ip address xxx.xxx.xxx.xxx 255.255.255.252
ip flow ingress
ip flow egress
encapsulation ppp
service-policy output WAN-EDGE
router bgp 65000
no synchronization
bgp log-neighbor-changes
bgp suppress-inactive
network xxx.xxx.xxx.xxx mask 255.255.255.252
network 192.168.121.0
network 192.168.221.0
network 192.168.222.21 mask 255.255.255.255
neighbor xxx.xxx.xxx.xxx remote-as 15270
default-information originate
no auto-summary
ip forward-protocol nd
ip route 0.0.0.0 0.0.0.0 Serial0/1/0:0 track 1
ip route 0.0.0.0 0.0.0.0 Cellular0/0/0 20
no ip http server
no ip http secure-server
ip flow-export source FastEthernet0/0.1
ip flow-export version 5
ip flow-export destination 10.1.90.25 2055
ip nat inside source list 100 interface Cellular0/0/0 overload
ip access-list standard MON_SNMP_RO
permit xxx.xxx.xxx.xxx
permit xxx.xxx.xxx.xxx
permit xxx.xxx.xxx.xxx
permit xxx.xxx.xxx.xxx
ip radius source-interface FastEthernet0/0.1
ip sla 1
icmp-echo xxx.xxx.xxx.xxx
timeout 1000
threshold 2
frequency 3
ip sla schedule 1 life forever start-time now
logging trap notifications
logging 10.1.90.167
access-list 100 remark = FO to C0/0/0 for Branch =
access-list 100 permit ip 192.168.221.0 0.0.0.255 any
access-list 100 permit ip any any
access-list 100 deny eigrp any any
access-list 100 deny igmp any any
dialer-list 1 protocol ip list 100
snmp-server community xxx RO
snmp-server enable traps tty
<---------- Truncated to remove VoIP Rules -------------->
banner motd ^C
This is a proprietary system.
^C
line con 0
line aux 0
line 0/0/0
script dialer cdma
modem InOut
no exec
rxspeed 3100000
txspeed 1800000
line vty 0 4
transport input telnet
line vty 5 15
transport input telnet
scheduler allocate 20000 1000
ntp server 10.1.99.5
endHi,
Here is configurations from my Lab ASA5520 with Dual ISP
interface GigabitEthernet0/0
description Primary ISP
nameif WAN-1
security-level 0
ip address 192.168.101.2 255.255.255.0
interface GigabitEthernet0/1
description Secondary ISP
nameif WAN-2
security-level 0
ip address 192.168.102.2 255.255.255.0
interface GigabitEthernet0/2
description LAN
nameif LAN
security-level 100
ip address 10.0.20.2 255.255.255.0
route WAN-1 0.0.0.0 0.0.0.0 192.168.101.1 1 track 200
route WAN-2 0.0.0.0 0.0.0.0 192.168.102.1 254
route LAN 10.0.0.0 255.255.255.0 10.0.20.1 1
access-list L2L-VPN-CRYPTOMAP remark Encryption Domain
access-list L2L-VPN-CRYPTOMAP extended permit ip 10.0.0.0 255.255.255.0 10.10.10.0 255.255.255.0
access-list LAN-NAT0 extended permit ip 10.0.0.0 255.255.255.0 10.10.10.0 255.255.255.0
nat (LAN) 0 access-list LAN-NAT0
sla monitor 200
type echo protocol ipIcmpEcho 192.168.101.1 interface WAN-1
num-packets 3
timeout 1000
frequency 5
sla monitor schedule 200 life forever start-time now
track 200 rtr 200 reachability
crypto ipsec transform-set AES-256 esp-aes-256 esp-sha-hmac
crypto ipsec security-association lifetime seconds 28800
crypto ipsec security-association lifetime kilobytes 4608000
crypto map CRYPTOMAP 10 match address L2L-VPN-CRYPTOMAP
crypto map CRYPTOMAP 10 set peer 192.168.103.2
crypto map CRYPTOMAP 10 set transform-set AES-256
crypto map CRYPTOMAP interface WAN-1
crypto map CRYPTOMAP interface WAN-2
crypto isakmp enable WAN-1
crypto isakmp enable WAN-2
crypto isakmp policy 10
authentication pre-share
encryption aes-256
hash sha
group 2
lifetime 28800
tunnel-group 192.168.103.2 type ipsec-l2l
tunnel-group 192.168.103.2 ipsec-attributes
pre-shared-key *****
Hope this helps
- Jouni -
"failed to find profile ID" on Cellular Interface
Hello World,
I try to make a connection to a Wirelless 3G.
I configure modem and I think that the modem is connected
show cellular 0/0/0 all
Hardware Information
====================
Modem Firmware Version = T1_0_3_2AP R361 CNSZ
Modem Firmware built = 04/15/11
Hardware Version = 1.0
International Mobile Subscriber Identity (IMSI) = 546010100686679
International Mobile Equipment Identity (IMEI) = 357115041341178
Integrated Circuit Card ID (ICCID) = 8968701111106200287
Mobile Subscriber International Subscriber
IDentity Number (MSISDN) =
Factory Serial Number (FSN) = CC3322315641011
Modem Status = Online
Current Modem Temperature = 29 deg C, State = Normal
PRI SKU ID = 9900198, SKU Rev. = 1.2
Profile Information
====================
Profile 1 = INACTIVE* **
PDP Type = IPv4
Access Point Name (APN) = USB
Authentication = None
Username:
Password:
* - Default profile
Data Connection Information
===========================
Data Transmitted = 0 bytes, Received = 0 bytes
Profile 1, Packet Session Status = INACTIVE
Inactivity Reason = Normal inactivate state
Profile 2, Packet Session Status = INACTIVE
Inactivity Reason = Normal inactivate state
Profile 3, Packet Session Status = INACTIVE
Inactivity Reason = Normal inactivate state
Profile 4, Packet Session Status = INACTIVE
Inactivity Reason = Normal inactivate state
Profile 5, Packet Session Status = INACTIVE
Inactivity Reason = Normal inactivate state
Profile 6, Packet Session Status = INACTIVE
Inactivity Reason = Normal inactivate state
Profile 7, Packet Session Status = INACTIVE
Inactivity Reason = Normal inactivate state
Profile 8, Packet Session Status = INACTIVE
Inactivity Reason = Normal inactivate state
Profile 9, Packet Session Status = INACTIVE
Inactivity Reason = Normal inactivate state
Profile 10, Packet Session Status = INACTIVE
Inactivity Reason = Normal inactivate state
Profile 11, Packet Session Status = INACTIVE
Inactivity Reason = Normal inactivate state
Profile 12, Packet Session Status = INACTIVE
Inactivity Reason = Normal inactivate state
Profile 13, Packet Session Status = INACTIVE
Inactivity Reason = Normal inactivate state
Profile 14, Packet Session Status = INACTIVE
Inactivity Reason = Normal inactivate state
Profile 15, Packet Session Status = INACTIVE
Inactivity Reason = Normal inactivate state
Profile 16, Packet Session Status = INACTIVE
Inactivity Reason = Normal inactivate state
Network Information
===================
Current Service Status = Normal, Service Error = None
Current Service = Combined
Packet Service = UMTS/WCDMA (Attached)
Packet Session Status = Inactive
Current Roaming Status = Home
Network Selection Mode = Automatic
Country = NCL, Network = MOBNCL
Mobile Country Code (MCC) = 546
Mobile Network Code (MNC) = 1
Location Area Code (LAC) = 10
Routing Area Code (RAC) = 1
Cell ID = 30521
Primary Scrambling Code = 434
PLMN Selection = Automatic
Registered PLMN = NCL MOBILIS , Abbreviated = MOBNCL
Service Provider =
Radio Information
=================
Radio power mode = ON
Current Band = WCDMA 2100, Channel Number = 10762
Current RSSI(RSCP) = -63 dBm
Band Selected = Auto
Number of nearby cells = 1
Cell 1
Primary Scrambling Code = 0x1B2
RSCP = -64 dBm, ECIO = -7 dBm
Modem Security Information
==========================
Card Holder Verification (CHV1) = Disabled
SIM Status = OK
SIM User Operation Required = None
Number of CHV1 Retries remaining = 3
GPS Information
==========================
GPS Info
GPS State: GPS disabled
SMS Information
===============
Incoming Message Information
SMS stored in modem = 1
SMS archived since booting up = 0
Total SMS deleted since booting up = 0
Storage records allocated = 60
Storage records used = 1
Number of callbacks triggered by SMS = 0
Number of successful archive since booting up = 0
Number of failed archive since booting up = 0
Outgoing Message Information
Total SMS sent successfully = 0
Total SMS send failure = 0
Number of outgoing SMS pending = 0
Number of successful archive since booting up = 0
Number of failed archive since booting up = 0
Last Outgoing SMS Status = SUCCESS
Copy-to-SIM Status = 0x0
Send-to-Network Status = 0x0
Report-Outgoing-Message-Number:
Reference Number = 0
Result Code = 0x0
Diag Code = 0x0 0x0 0x0 0x0 0x0
SMS Archive URL =
Error Information
=================
Cached info is displayed
at!err
QDSP6 ARM9 (not saved)
00 08 uim 08480 00 01 hsu_conf_sel_nv 00572
01 63 gsnvif 00245 01 01 hsu_conf_sel_nv 00616
02 FF cmtask 01162 02 01 timer 03552
03 1B mmglbl 00392
04 1B gsnvif 00478
05 1B rr_init 01597
06 1B rr_init 01601
07 1B rrcdata 08026
08 01 gmmutil 01099
09 01 gmmutil 01118
10 01 gmmutil 01141
11 01 gmmutil 01156
12 01 gmmutil 01174
13 01 gmmutil 01198
14 14 rrcllcp 16550
15 04 rrccspf 02198
16 17 rrccsp 20686
17 04 gsdi 09787
18 01 gsdi_co 01538
19 1B cnlbs 03307
OK
at!gcdump
No crash data available
OK
Modem Crashdump Information
===========================
Modem crashdump logging: off
I have the following config
chat-script OPT3G "" "ATDT*99***1#"
interface Cellular0/0/0
ip address negotiated
ip virtual-reassembly in
encapsulation slip
no ip route-cache
load-interval 60
dialer in-band
dialer string OPT3G
dialer-group 1
async mode interactive
interface Cellular0/0/1
no ip address
encapsulation slip
ip forward-protocol nd
no ip http server
no ip http secure-server
ip route 0.0.0.0 0.0.0.0 Cellular0/0/0
dialer-list 1 protocol ip permit
access-list 1 permit any
line 0/0/0
exec-timeout 0 0
script dialer OPT3G
login
modem InOut
no exec
transport input all
transport output all
autoselect during-login
autoselect ppp
line 0/0/1
exec-timeout 0 0
script dialer OPT3G
login
modem InOut
no exec
transport input all
I make debug
debug chat
debug cellular 0/0/0 messages all
I try to start the interface
Sending 5, 100-byte ICMP Echos to 8.8.8.8, timeout is 2 seconds:
*Jul 22 07:08:31.363: [Cellular0/0/0]:MGMT RX (RSCP_ECIO) (24 bytes):
00 14 6B 96 70 0B 07 00 00 00 00 00 00 0A 00 01
00 01 01 B2 00 3E 00 0D
*Jul 22 07:08:32.283: CHAT0/0/0: Attempting async line dialer script
*Jul 22 07:08:32.283: CHAT0/0/0: Dialing using Modem script: OPT3G & System script: none
*Jul 22 07:08:32.283: CHAT0/0/0: process started
*Jul 22 07:08:32.283: CHAT0/0/0: Asserting DTR
*Jul 22 07:08:32.283: CHAT0/0/0: Chat script OPT3G started
*Jul 22 07:08:32.283: CHAT0/0/0: Sending string: ATDT*99***1#
*Jul 22 07:08:32.283: CHAT0/0/0: Chat script OPT3G finished, status = Success.
*Jul 22 07:08:34.283: %LINK-3-UPDOWN: Interface Cellular0/0/0, changed state to up
*Jul 22 07:08:34.283: cellular_dip_ip_address_negotiated: failed to find profile ID for Cellular0/0/0
*Jul 22 07:08:34.363: [Cellular0/0/0]:MGMT RX (RSCP_ECIO) (24 bytes):
00 14 6B 97 70 0B 07 00 00 00 00 00 00 0A 00 01
00 01 01 B2 00 3F 00 0C
*Jul 22 07:08:35.283: %LINEPROTO-5-UPDOWN: Line protocol on Interface Cellular0/0/0, changed state to up.
*Jul 22 07:08:36.283: cellular_dip_cell_set_encap_whip: Invalid profile ID 255 for Cellular0/0/0
*Jul 22 07:08:36.835: [Cellular0/0/0]:MGMT RX (HEARTBEAT) (14 bytes):
00 0A 6B 98 00 00 07 00 00 00 00 00 00 00
*Jul 22 07:08:37.363: [Cellular0/0/0]:MGMT RX (RSCP_ECIO) (24 bytes):
00 14 6B 99 70 0B 07 00 00 00 00 00 00 0A 00 01
00 01 01 B2 00 3E 00 0C
*Jul 22 07:08:38.283: cellular_dip_cell_set_encap_whip: Invalid profile ID 255 for Cellular0/0/0.
*Jul 22 07:08:40.283: cellular_dip_cell_set_encap_whip: Invalid profile ID 255 for Cellular0/0/0
*Jul 22 07:08:40.367: [Cellular0/0/0]:MGMT RX (RSCP_ECIO) (24 bytes):
00 14 6B 9A 70 0B 07 00 00 00 00 00 00 0A 00 01
00 01 01 B2 00 40 00 0F
Success rate is 0 percent (0/5)
RTR-TEST98#
*Jul 22 07:08:43.371: [Cellular0/0/0]:MGMT RX (RSCP_ECIO) (24 bytes):
00 14 6B 9B 70 0B 07 00 00 00 00 00 00 0A 00 01
00 01 01 B2 00 3C 00 11
*Jul 22 07:08:43.835: [Cellular0/0/0]:MGMT RX (HEARTBEAT) (14 bytes):
00 0A 6B 9C 00 00 07 00 00 00 00 00 00 00
*Jul 22 07:08:46.375: [Cellular0/0/0]:MGMT RX (RSCP_ECIO) (24 bytes):
00 14 6B 9D 70 0B 07 00 00 00 00 00 00 0A 00 01
00 01 01 B2 00 3E 00 0D
*Jul 22 07:08:49.379: [Cellular0/0/0]:MGMT RX (RSCP_ECIO) (24 bytes):
00 14 6B 9E 70 0B 07 00 00 00 00 00 00 0A 00 01
00 01 01 B2 00 3E 00 0C
*Jul 22 07:08:50.835: [Cellular0/0/0]:MGMT RX (HEARTBEAT) (14 bytes):
00 0A 6B 9F 00 00 07 00 00 00 00 00 00 00
*Jul 22 07:08:52.383: [Cellular0/0/0]:MGMT RX (RSCP_ECIO) (24 bytes):
00 14 6B A0 70 0B 07 00 00 00 00 00 00 0A 00 01
00 01 01 B2 00 3E 00 0Ehello everyone,
I still have my issue and can't connect my 3G interface.
I can complete my issue with this log
*Aug 12 08:35:34.023: cellular_dip_ip_address_negotiated: failed to find profile ID for Cellular0/0/0
*Aug 12 08:35:38.019: cellular_dip_cell_set_encap_whip: Invalid profile ID 255 for Cellular0/0/0
Thank's for your help. -
I have inherited a system that has a terminal server set up for remote connections. How do I get into the individual lines?
It is a:
dc4-tsv-02#sh inv
NAME: "2821 chassis", DESCR: "2821 chassis"
PID: CISCO2821 , VID: V04 , SN: FTX1222A00S
NAME: "High Speed Wan Interface card with 16 RS232 async ports(HWIC-16A)", DESCR: "High Speed Wan Interface card with 16 RS232 async ports(HWIC-16A)"
PID: , VID: V01 , SN: FOC12114NTR
NAME: "High Speed Wan Interface card with 16 RS232 async ports(HWIC-16A)", DESCR: "High Speed Wan Interface card with 16 RS232 async ports(HWIC-16A)"
PID: , VID: V01 , SN: FOC12114NXH
NAME: "Virtual Private Network (VPN) Module", DESCR: "Encryption AIM Element"
PID: AIM-VPN/EPII-PLUS , VID: V02 , SN: FOC12184MGV
and is running:
dc4-tsv-02#sh ver
Cisco IOS Software, 2800 Software (C2800NM-ADVIPSERVICESK9-M), Version 12.4(18a), RELEASE SOFTWARE (fc3)
I looked at the confguration guide at javascript:newWin('http://www.cisco.com/en/US/tech/tk801/tk36/technologies_configuration_example09186a008014f8e7.shtml') and my TS does not have any of the "ip host" commands.
Is this important given that my connections are all async consoles? What is the syntax for connecting to the individual async lines? I tried connect, etc. to no avail. The lines are all set up like this one:
interface Async0/0/0
no ip address
encapsulation slip
The lines appear to be live:
dc4-tsv-02#sh line
Tty Line Typ Tx/Rx A Modem Roty AccO AccI Uses Noise Overruns Int
0 0 CTY - - - - - 0 0 0/0 -
1 1 AUX 9600/9600 - - - - - 0 0 0/0 -
0/0/0 2 TTY 9600/9600 - - - - - 4 0 0/0 -
0/0/1 3 TTY 9600/9600 - - - - - 1 0 0/0 -
0/0/2 4 TTY 9600/9600 - - - - - 1 0 0/0 -
0/0/3 5 TTY 9600/9600 - - - - - 1 0 0/0 -
0/0/4 6 TTY 9600/9600 - - - - - 4 12674 0/0 -
0/0/5 7 TTY 9600/9600 - - - - - 1 140 0/0 -
0/0/6 8 TTY 9600/9600 - - - - - 1 0 0/0 -
0/0/7 9 TTY 9600/9600 - - - - - 2 0 0/0 -
0/0/8 10 TTY 9600/9600 - - - - - 2 2619168 0/0 -
0/0/9 11 TTY 9600/9600 - - - - - 2 0 0/0 -
etc.
Thanks in advance!Yes, that helped. I found the information through another source in the meantime (http://books.google.com/books?id=UbuEHLfhNmMC&pg=PA370&lpg=PA370&dq=connect+async+line+cisco+console&source=bl&ots=J5mBA0_clW&sig=fpvGz6W_xikAzImRdnaWZNMIoHs&hl=en&ei=aBnrSoqsHI2zlAfE9YCABQ&sa=X&oi=book_result&ct=result&resnum=8&ved=0CCcQ6AEwBzgU#v=onepage&q=connect%20async%20line%20cisco%20console&f=false)
The "gotcha" here was to note that I needed to execute the telnet x.x.x.x zzzz from the terminal server host (x.x.x.x) itself.
Thanks for the assist though - I rated your post accordingly. -
POTS/Analog Dial Access with PVDM3 and 3900? Possible?
I have a PVDM3-16, 3925 and HWIC-CE1T1-PRI.
I have a T1 terminating in the HWIC and the other end goes to an ATLAS 800. I dial into it with an analog v.92 modem. It provides dial-tone and a phone numbering setup. Sort of a self-contained phone system in-a-box.
My old, existing, setup is an AS5200 hanging off of that same ATLAS, on another T1 port.
All I want to do is dial in and establish a PPP session. Simple on the AS5200. Not so much with the PVDM3.
I have seen all sorts of documentation about doing this with a PVDM2, but not with a PVDM3. I assume the "3" would have all of the features of the "2" with newer ones to boot.
My main problem is figuring out how to refer to the 16 "modems" in my router. The PVDM2 docs note the line numbers created when it is installed in X800 series routers, but I have found no such documentation for the PVDM3. Also, I am having some conceptual difficulty getting my mind around modems that don't have hardware support. In the AS5200's modem cards, I can deal with actual "line" commands, however, I assume that the digital modems in the PVDM3 don't generate that. Is that correct?
If anyone is using PVDM3 modems to support POTS/Analog dial-in via a channelized T1 or PRI, I would greatly appreciate any direction you can provide.
I'm not asking for someone to essentially configure it for me. I'd be happy knowing how to setup the PVDM3 to act like run of the mill analog modems and maybe some insight into how that translates into async line references.
Thanks,
AndyPaolo,
Thank you for your reply.
I can't actually find any documentation that differentiates between a PVDM2 and a PVDM2-XXDM. As far as I can see, the "XX" is the number of modems contained on the card. Like PVDM2-12DM, where "12" replaces the generic "XX". Is this not the case? Are "PVDM2"s and "PVDM2-12DM"s, for example, two different SKUs?
I had heard, but have not yet found supporting info online, that the PVDM2s have been announced as EOS.
I have seen the PVDM EOS/EOL announcement onnline. -
Problems dialing from a external modem to a isdn router
Hi,
I have trouble with my modem dial-in in an other router using his isdn interface.
The problem looks like the following:
The calling router:
router-2523#debug dialer events
Dial on demand events debugging is on
router-2523#ping 172.16.4.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.16.4.1, timeout is 2 seconds:
00:17:50: Se5 DDR: rotor dialout [best] least recent failure is also most recent failure
00:17:50: Se5 DDR: rotor dialout [best] also has most recent failure
00:17:50: Se5 DDR: rotor dialout [best]
00:17:50: Se5 DDR: Dialing cause ip (s=172.16.4.2, d=172.16.4.1)
00:17:50: Se5 DDR: Attempting to dial 51
00:17:50: CHAT5: Attempting async line dialer script
00:17:50: CHAT5: Dialing using Modem script: Dialout & System script: none
00:17:50: CHAT5: process started
00:17:50: CHAT5: Asserting DTR
00:17:50: CHAT5: Chat script Dialout started.....
Success rate is 0 percent (0/5)
router-2523#
00:18:02: CHAT5: Found abort string BUSY expecting CONNECT
00:18:02: CHAT5: Chat script Dialout finished, status = Connection aborted
00:18:02: Se5 DDR: disconnecting call
router-2523#
The called router:
router-2503-II#debug isdn events
ISDN events debugging is on
router-2503-II#debug isdn q931
ISDN Q931 packets debugging is on
router-2503-II#
00:18:58: ISDN BR0: RX <- SETUP pd = 8 callref = 0x01
00:18:58: Bearer Capability i = 0x9090A3
00:18:58: Channel ID i = 0x8A
00:18:58: Progress Ind i = 0x8583 - Origination address is non-ISDN
00:18:58: Calling Party Number i = 0x01, 0x83, '15', Plan:ISDN, Type:Unknown
00:18:58: Called Party Number i = 0x81, '51', Plan:ISDN, Type:Unknown
00:18:58: CCBRI_Go Fr L3 pkt (Len=27) :
00:18:58: 5 1 81 90 4 3 90 90 A3 18 1 8A 1E 2 85 83 6C 4 1 83 31 35 70 3 81 35 31
00:18:58:
00:18:58: ISDN BR0: Incoming call id = 0x000B, dsl 0
00:18:58: ISDN BR0: LIF_EVENT: ces/callid 1/0xB HOST_INCOMING_CALL
00:18:58: ISDN BR0: HOST_INCOMING_CALL: (non-POTS) VOICE
00:18:58: ISDN BR0: HOST_INCOMING_CALL: (1) call_type = VOICE
00:18:58: ISDN BR0: HOST_INCOMING_CALL: voice_answer_data = FALSE call type is VOICE ALAW
00:18:58: ISDN BR0: Event: Received a VOICE call from 15 on B2 at 64 Kb/s
00:18:58: ISDN BR0: Event: Accepting the call id 0xB
00:18:58: ISDN BR0: INCOMING CALL: VOICE ERROR: Bearer capability not available(0x3A): bchan 1, call id B
00:18:58: ISDN BR0: process_disconnect(): call id 0xB, call type is VOICE, b_idb 0x24F470, ces 1, cause Bearer capability not available(0x3A)
00:18:58: ISDN: get_isdn_service_state(): idb 0x24F470 bchan 3 is_isdn 1 Not a Pri
00:18:58: CCBRI_Go Fr Host InPkgInfo (Len=9) :
00:18:58: 7 0 1 0 B 3 18 1 8A
00:18:58:
00:18:58: CCBRI_Go Fr Host InPkgInfo (Len=13) :
00:18:58: 5 0 1 0 B 3 8 1 BA 8 2 80 BA
00:18:58:
00:18:58: ISDN BR0: TX -> CALL_PROC pd = 8 callref = 0x81
00:18:58: Channel ID i = 0x8A
00:18:58: ISDN BR0: TX -> DISCONNECT pd = 8 callref = 0x81
00:18:58: Cause i = 0x80BA - Bearer capability not available
00:18:58: ISDN BR0: RX <- RELEASE pd = 8 callref = 0x01
00:18:58: CCBRI_Go Fr L3 pkt (Len=4) :
00:18:58: 4D 1 81 97
00:18:58:
00:18:58: ISDN BR0: LIF_EVENT: ces/callid 1/0xB HOST_DISCONNECT_ACK
router-2503-II#
00:18:58: ISDN: get_isdn_service_state(): idb 0x24F470 bchan 3 is_isdn 1 Not a Pri
00:18:58: ISDN BR0: HOST_DISCONNECT_ACK: call type is VOICE
00:18:58: ISDN BR0: HOST_DISCONNECT_ACK: VOICE ERROR: Bearer capability not available(0x3A): bchan 1, call id B
00:18:58: ISDN BR0: TX -> RELEASE_COMP pd = 8 callref = 0x81
router-2503-II#
Does anyone know whats going wrong and why I could not get a connection th the 2503-II router? When I try the connection from an other router using isdn on both sides the connection works fine...
I added the configuration of both routers in the attachments...
Best Regards
MarcosHi,
I configured the ISDN BRI Intaerface on the Router-2503-II in the following manner:
router-2503-II#sh run int bri 0
Building configuration...
Current configuration : 133 bytes
interface BRI0
no ip address
encapsulation ppp
dialer pool-member 1
isdn switch-type basic-net3
isdn incoming-voice data
end
router-2503-II#
after this I tried it again and got the following debug output:
router-2503-II#
00:11:54: ISDN BR0: RX <- SETUP pd = 8 callref = 0x01
00:11:54: Bearer Capability i = 0x9090A3
00:11:54: Channel ID i = 0x8A
00:11:54: Progress Ind i = 0x8583 - Origination address is non-ISDN
00:11:54: Calling Party Number i = 0x01, 0x83, '15', Plan:ISDN, Type:Unknown
00:11:54: Called Party Number i = 0x81, '51', Plan:ISDN, Type:Unknown
00:11:54: CCBRI_Go Fr L3 pkt (Len=27) :
00:11:54: 5 1 81 90 4 3 90 90 A3 18 1 8A 1E 2 85 83 6C 4 1 83 31 35 70 3 81 35 31
00:11:54:
00:11:54: ISDN BR0: Incoming call id = 0x0008, dsl 0
00:11:54: ISDN BR0: LIF_EVENT: ces/callid 1/0x8 HOST_INCOMING_CALL
00:11:54: ISDN BR0: HOST_INCOMING_CALL: (non-POTS) VOICE
00:11:55: ISDN BR0: HOST_INCOMING_CALL: (1) call_type = VOICE
00:11:55: ISDN BR0: HOST_INCOMING_CALL: voice_answer_data = TRUE call type is VOICE ALAW
00:11:55: ISDN BR0: call id 0x8 call treated as DOV
00:11:55: ISDN BR0: Event: Received a DATA call from 15 on B2 at 64 Kb/s
00:11:55: ISDN BR0: Event: Accepting the call id 0x8
00:11:55: ISDN BR0:2: Incoming call rejected, unbindable
00:11:55: ISDN BR0: process_disconnect(): call id 0x8, call type is DATA, b_idb 0x24F470, ces 1, cause Call rejected(0x15)
00:11:55: ISDN: get_isdn_service_state(): idb 0x24F470 bchan 3 is_isdn 1 Not a Pri
router-2503-II#
00:11:55: ISDN BR0: HOST_INCOMING_CALL: DIALER ERROR 1: bchan 1, call id 8
00:11:55: CCBRI_Go Fr Host InPkgInfo (Len=13) :
00:11:55: 5 0 1 0 8 3 8 1 95 8 2 80 95
00:11:55:
00:11:55: ISDN BR0: LIF_EVENT: ces/callid 1/0x8 HOST_DISCONNECT_ACK
00:11:55: ISDN: get_isdn_service_state(): idb 0x24F470 bchan 3 is_isdn 1 Not a Pri
00:11:55: ISDN BR0: HOST_DISCONNECT_ACK: call type is VOICE
00:11:55: ISDN BR0: TX -> RELEASE_COMP pd = 8 callref = 0x81
00:11:55: Cause i = 0x8095 - Call rejected
router-2503-II#
Have you any ideas where to look from here?
Regards
Marcos -
Hi,
I want to use a HWIC-3G-GSM for remote dialin connection. My configuration looks like this:
interface Cellular0/3/0
ip address 192.168.1.19 255.255.255.0
encapsulation ppp
dialer in-band
dialer-group 1
async mode interactive
dialer-list 1 protocol ip permit
line 0/3/0
no exec
transport input all
rxspeed 236800
txspeed 118000
I assume that I need a chat-script, but I cannot find anything for dialin. All chat-scripts try to dialout to provide backup connectivity for a wan failure, but this is not my scenario.
Does anyone know what for AT commands need to be passed to the modem to setup dialin? At the moment, my dialin attempt looks like this (debug chat + ppp nego)
Router#telnet 192.168.1.19
Trying 192.168.1.19 ...
As65 DDR: rotor dialout [best] least recent failure is also most recent failure
As65 DDR: rotor dialout [best] also has most recent failure
As65 DDR: rotor dialout [best]
As65 DDR: Dialing cause ip (s=192.168.1.1, d=192.168.1.19)
As65 DDR: Attempting to dial xxxxxx
CHAT65: Attempting async line dialer script
CHAT65: no matching chat script found for xxxx
CHAT65: Dialing using Modem script: d0efault-d0ials0cript & System script: none
CHAT65: process started
CHAT65: Asserting DTR
CHAT65: Chat script d0efault-d0ials0cript started
CHAT65: Chat script d0efault-d0ials0cript finished, status = Success
%LINK-3-UPDOWN: Interface Async65, changed state to up
As65 DDR: Dialer statechange to up
%DIALER-6-BIND: Interface As65 bound to profile Di1
As65 DDR: Dialer call has been placed
As65 PPP: Using dialer call direction
As65 PPP: Treating connection as a callout
As65 PPP: Session handle[C50001D8] Session id[100]
As65 PPP: Phase is ESTABLISHING, Active Open
As65 LCP: O CONFREQ [Closed] id 178 len 25
As65 LCP: ACCM 0x000A0000 (0x0206000A0000)
As65 LCP: AuthProto CHAP (0x0305C22305)
As65 LCP: MagicNumber 0x15783024 (0x050615783024)
As65 LCP: PFC (0x0702)
As65 LCP: ACFC (0x0802)
As65 LCP: Timeout: State REQsentI am also looking for a way to retrieve sim information, and sms messaged form a cisco router.
-
Thinking about switching over to Java for EMAIL software I wrote
Hi...
I am the current author of a unique EMAIL client/server program for the old MS-DOS operating system called D'Bridge. It is from the BBS days of Fidonet and I've recently began recoding some elements of the program to facilitate Internet support and whatnot. D'Bridge is over 20 years old and is written half in Borland Pascal 5.5 and half in Visual BASIC for DOS.
After careful thinking (and one of those "wouldn't it be cool?" thoughts), I'm thinking of rewriting the entire code in JAVA to have a platform independant solution. I would like to write a "server" edition which would serve Web, POP3/SMTP, FTP and Telnet users in addition to legacy Fidonet support via. traditional dialup modem lines. I would then like to write a "client" edition which would be totally slimmed-down to run on PDA's such as Palm OS or Windows CE.
I generally am new to the language but I'm going to take an entire printout of my current work and then go step-by-step into an OOP transition - D'Bridge was obviously written before the days of OOP and therefore makes heavy use of global variables, assembly language and other elements. Nearly half of the code is entirely devoted to controlling the menu system and screen elements - you could say that I'd like to use Java to concentrate more on what D'Bridge does instead of what it looks like. :-)
I guess I'm looking for any advice, feedback, criticism, encouragement, words of wisdom, whatever you want to call it. After studying the fundimentals of the language, I believe I can make the transition but need to know from you guys if a full-blown server package is possible - because thats what my DOS application is doing now, with a loyal and dedicated fan club that just loves it.
Nickbut need to know from you guys if a full-blown server
package is possible Yes.
JBoss and Tomcat are two free frameworks that exist solely to act as servers to support different parts of the documented J2EE API.
There are commercial versions that support the same framework as well as other types of solutions including forum software (like this site), middleware, message systems, Network Management Systems, etc.
And those are just the ones that I know about (and which I have implemented commercial solutions as well.) -
Hi,
I was wondering if anyone has managed to sucessfully configure the EHWIC-4G-LTE-G network module for use on the O2-UK network?
I am succesfully registering to o2 (network 10) in the uk (country 234) without roaming (home):
#sh cellular 0/0/0 network
Current Service Status = Normal
Current Service = Packet switched
Current Roaming Status = Home
Network Selection Mode = Automatic
Mobile Country Code (MCC) = 234
Mobile Network Code (MNC) = 10
Packet switch domain(PS) state = Attached
Registration(EMM) state = Registered
And I have a really good 3G (UMTS) signal (-31dBm is like 5 bars):
#sh cellular 0/0/0 radio
Radio power mode = ON
Current RSSI(RSCP) = -31 dBm
LTE Technology Preference = AUTO
LTE Technology Selected = UMTS
But the profile won't stay active.
If I ping an address on the internet like 8.8.8.8, the default route and chat-script bring the modem online and if I very quickly view the profile it does become active:
#sh cellular 0/0/0 profile
Profile 1 = ACTIVE*
PDP Type = IPv4
PDP address = 10.122.1.178
Access Point Name (APN) = mobile.o2.co.uk
Authentication = Unknown
Username: bypass
Password:
Primary DNS address = 82.132.254.2
Secondary DNS address = 82.132.254.3
However, after a few seconds it always reverts back to the inactive state:
#sh cellular 0/0/0 profile
Profile 1 = INACTIVE*
PDP Type = IPv4
Access Point Name (APN) = mobile.o2.co.uk
Authentication = Unknown
Username: bypass
Password:
This is repeatable and I have tried vertigo, bypass and o2web as different APNs. Here is the profile configuration I'm using:
#cellular 0/0/0 lte profile create 1 mobile.o2.co.uk pap bypass password ipv4
I have also tried a variety of chat-scripts like:
chat-script modem "" "AT!CALL1" TIMEOUT 30
chat-script modem "" "ATDT*99*1#" TIMEOUT 60 "OK"
chat-script modem "" "ATDT*99*1#" TIMEOUT 60 "CONNECT"
chat-script modem "" "ATDT*99***1#" TIMEOUT 60 "CONNECT"
To no avail. Here is the debug output that does not look good:
*Dec 23 16:10:56.907: CHAT0/0/0: Attempting async line dialer script
*Dec 23 16:10:56.907: CHAT0/0/0: process started
*Dec 23 16:10:56.907: CHAT0/0/0: Asserting DTR
*Dec 23 16:10:56.907: TTY0/0/0: no timer type 1 to destroy
*Dec 23 16:10:56.907: TTY0/0/0: no timer type 0 to destroy
*Dec 23 16:10:56.907: TTY0/0/0: no timer type 2 to destroy
*Dec 23 16:10:57.063: TTY0/0/0: DSR was dropped
*Dec 23 16:10:57.063: tty0/0/0: Modem: READY->(unknown).
*Dec 23 16:10:58.063: TTY0/0/0: dropping DTR, hanging up
*Dec 23 16:10:58.063: TTY0/0/0: Async Int reset: Dropping DTR
For reference, here is the rest of the configuration:
interface Cellular0/0/0
ip address negotiated
encapsulation slip
dialer in-band
dialer idle-timeout 0
dialer string modem
dialer-group 1
async mode interactive
end
ip route 0.0.0.0 0.0.0.0 Cellular0/0/0
dialer-list 1 protocol ip permit
line 0/0/0
exec-timeout 0 0
script dialer modem
modem InOut
no exec
Any suggestions much appreciated.
Many thanks,
JonnyFor anyone who is interested, below is my working solution. The trick was to create a dialer interface with PPP encpasulation and join it to the cellular interface which has SLIP encapsulation:
ip dhcp pool LAN
network 192.168.1.0 255.255.255.0
default-router 192.168.1.1
dns-server 8.8.8.8 8.8.4.4
chat-script lte "" "AT!CALL1" TIMEOUT 30 "OK"
interface GigabitEthernet0/0
ip address 192.168.1.1 255.255.255.0
ip nat inside
ip virtual-reassembly in
duplex auto
speed auto
interface Cellular0/0/0
ip address negotiated
ip nat outside
ip virtual-reassembly in
encapsulation slip
dialer in-band
dialer pool-member 1
dialer-group 1
async mode interactive
routing dynamic
interface Dialer1
ip address negotiated
ip nat outside
ip virtual-reassembly in
encapsulation ppp
dialer pool 1
dialer idle-timeout 0
dialer string lte
dialer persistent
dialer-group 1
ppp authentication pap callin
ppp pap sent-username o2web password 0 password
ppp ipcp dns request
ip nat inside source list 1 interface Dialer1 overload
ip route 0.0.0.0 0.0.0.0 Dialer1
access-list 1 permit ip any
dialer-list 1 protocol ip permit
line 0/0/0
script dialer lte
modem InOut
no exec
transport input all
transport output all
rxspeed 100000000 <-- Max LTE download speed populated automatically
txspeed 50000000 <-- Max LTE upload speed populated automatically
As you can see the 10.x address assigned by o2 goes onto the Dialer interface instead:
GigabitEthernet0/0 192.168.1.1 YES NVRAM up up
Cellular0/0/0 unassigned YES NVRAM up up
Cellular0/0/1 unassigned YES unset down down
Cellular0/0/2 unassigned YES unset down down
Cellular0/0/3 unassigned YES unset down down
Dialer1 10.65.98.14 YES IPCP up up
NVI0 192.168.1.1 YES unset up up
These lines are also required but are the same as before:
#cellular 0/0/0 lte profile create 1 mobile.o2.co.uk pap o2web password ipv4
#cellular 0/0/1 lte profile create 1 mobile.o2.co.uk pap o2web password ipv4 <-- Necessary for some reason
#(config)interface cellular 0/0/0
#(config-if)#no shutdown
#(config)interface cellular 0/0/1
#(config-if)#shutdown -
1921 and EHWIC-4G-LTE-V Failures On Connecting LAN
I am running into an issue regarding usage of a 1921 (15.3(2)T) and EHWIC-4G-LTE-V (firmware SWI9600M_03.05.10.06).
With the EHWIC installed in the router, I am able to establish a data connection on the Verizon LTE network. RSSI approx -64 consistently.
However, the oddities begin when I connect the LAN (or a laptop, for troubleshooting purposes) to the internal interface (Gig 0/1).
Output when no other devices connected to the router
===============================================
arch-eng-router1#ping 4.2.2.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 4.2.2.1, timeout is 2 seconds:
Success rate is 100 percent (5/5), round-trip min/avg/max = 40/80/224 ms
Profile Information
====================
Profile 1 = ACTIVE*
PDP Type = IPv4
PDP address = 10.172.240.7
Access Point Name (APN) = VZWINTERNET
Authentication = None
Username:
Password:
Primary DNS address = 198.224.169.135
Secondary DNS address = 198.224.170.135
* - Default profile
Output when another device is connected to the router
================================================
[Note: 'debug dialer' and 'debug chat' enabled for output]
*Jul 10 03:34:04.643: %LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed state to up
*Jul 10 03:34:05.643: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed state to up
*Jul 10 03:34:09.779: %LINK-5-CHANGED: Interface Cellular0/0/0, changed state to reset
*Jul 10 03:34:09.779: Ce0/0/0 DDR: has total 0 call(s), dial_out 0, dial_in 0
*Jul 10 03:34:09.779: %DIALER-6-UNBIND: Interface Ce0/0/0 unbound from profile Di1
*Jul 10 03:34:09.783: Di1 DDR: No free dialer - starting fast idle timer
*Jul 10 03:34:10.207: Di1: No free dialer - starting fast idle timer
*Jul 10 03:34:10.207: Di1: No free dialer - starting fast idle timer
*Jul 10 03:34:10.211: Di1: No free dialer - starting fast idle timer
*Jul 10 03:34:10.211: Di1: No free dialer - starting fast idle timer
*Jul 10 03:34:10.779: %LINEPROTO-5-UPDOWN: Line protocol on Interface Cellular0/0/0, changed state to down
*Jul 10 03:34:10.783: Di1 DDR: No free dialer - starting fast idle timer
*Jul 10 03:34:11.551: Di1: No free dialer - starting fast idle timer
*Jul 10 03:34:11.551: Di1: No free dialer - starting fast idle timer
*Jul 10 03:34:11.551: Di1: No free dialer - starting fast idle timer
*Jul 10 03:34:11.783: Di1 DDR: No free dialer - starting fast idle timer
*Jul 10 03:34:12.551: Di1: No free dialer - starting fast idle timer
*Jul 10 03:34:12.551: Di1: No free dialer - starting fast idle timer
*Jul 10 03:34:12.551: Di1: No free dialer - starting fast idle timer
*Jul 10 03:34:12.783: Di1 DDR: No free dialer - starting fast idle timer
*Jul 10 03:34:13.551: Di1: No free dialer - starting fast idle timer
*Jul 10 03:34:13.551: Di1: No free dialer - starting fast idle timer
*Jul 10 03:34:13.551: Di1: No free dialer - starting fast idle timer
*Jul 10 03:34:13.551: Di1: No free dialer - starting fast idle timer
*Jul 10 03:34:13.551: Di1: No free dialer - starting fast idle timer
*Jul 10 03:34:13.551: Di1: No free dialer - starting fast idle timer
*Jul 10 03:34:13.551: Di1: No free dialer - starting fast idle timer
*Jul 10 03:34:13.551: Di1: No free dialer - starting fast idle timer
*Jul 10 03:34:13.551: Di1: No free dialer - starting fast idle timer
*Jul 10 03:34:13.783: Di1 DDR: No free dialer - starting fast idle timer
*Jul 10 03:34:14.207: Di1: No free dialer - starting fast idle timer
*Jul 10 03:34:14.211: Di1: No free dialer - starting fast idle timer
*Jul 10 03:34:14.211: Di1: No free dialer - starting fast idle timer
*Jul 10 03:34:14.211: Di1: No free dialer - starting fast idle timer
*Jul 10 03:34:14.779: %LINK-3-UPDOWN: Interface Cellular0/0/0, changed state to down
*Jul 10 03:34:14.783: Di1 DDR: No free dialer - starting fast idle timer
*Jul 10 03:34:15.551: Di1: No free dialer - starting fast idle timer
*Jul 10 03:34:15.551: Di1: No free dialer - starting fast idle timer
*Jul 10 03:34:15.551: Di1: No free dialer - starting fast idle timer
*Jul 10 03:34:15.551: Di1: No free dialer - starting fast idle timer
*Jul 10 03:34:15.551: Di1: No free dialer - starting fast idle timer
*Jul 10 03:34:15.551: Di1: No free dialer - starting fast idle timer
*Jul 10 03:34:15.783: Di1 DDR: No free dialer - starting fast idle timer
*Jul 10 03:34:15.795: Di1: No free dialer - starting fast idle timer
*Jul 10 03:34:15.799: Di1: No free dialer - starting fast idle timer
*Jul 10 03:34:16.783: Di1 DDR: No free dialer - starting fast idle timer
*Jul 10 03:34:16.795: Di1: No free dialer - starting fast idle timer
*Jul 10 03:34:16.799: Di1: No free dialer - starting fast idle timer
*Jul 10 03:34:17.783: Di1 DDR: No free dialer - starting fast idle timer
*Jul 10 03:34:17.795: Di1: No free dialer - starting fast idle timer
*Jul 10 03:34:17.799: Di1: No free dialer - starting fast idle timer
*Jul 10 03:34:18.783: Di1 DDR: No free dialer - starting fast idle timer
*Jul 10 03:34:19.551: Di1: No free dialer - starting fast idle timer
*Jul 10 03:34:19.551: Di1: No free dialer - starting fast idle timer
*Jul 10 03:34:19.551: Di1: No free dialer - starting fast idle timer
*Jul 10 03:34:19.551: Di1: No free dialer - starting fast idle timer
*Jul 10 03:34:19.551: Di1: No free dialer - starting fast idle timer
*Jul 10 03:34:19.551: Di1: No free dialer - starting fast idle timer
*Jul 10 03:34:19.783: Di1 DDR: No free dialer - starting fast idle timer
*Jul 10 03:34:19.795: Di1: No free dialer - starting fast idle timer
*Jul 10 03:34:19.795: Di1: No free dialer - starting fast idle timer
*Jul 10 03:34:19.799: Di1: No free dialer - starting fast idle timer
*Jul 10 03:34:19.799: Di1: No free dialer - starting fast idle timer
*Jul 10 03:34:20.771: Di1: No free dialer - starting fast idle timer
*Jul 10 03:34:20.783: Di1 DDR: No free dialer - starting fast idle timer
*Jul 10 03:34:21.775: Di1: No free dialer - starting fast idle timer
*Jul 10 03:34:21.783: Di1 DDR: No free dialer - starting fast idle timer
*Jul 10 03:34:22.775: Di1: No free dialer - starting fast idle timer
*Jul 10 03:34:22.783: Di1 DDR: No free dialer - starting fast idle timer
*Jul 10 03:34:23.783: Di1 DDR: No free dialer - starting fast idle timer
*Jul 10 03:34:23.795: Di1: No free dialer - starting fast idle timer
*Jul 10 03:34:23.795: Di1: No free dialer - starting fast idle timer
*Jul 10 03:34:23.799: Di1: No free dialer - starting fast idle timer
*Jul 10 03:34:23.799: Di1: No free dialer - starting fast idle timer
*Jul 10 03:34:24.775: Di1: No free dialer - starting fast idle timer
*Jul 10 03:34:24.775: Di1: No free dialer - starting fast idle timer
*Jul 10 03:34:24.779: Ce0/0/0 DDR: re-enable timeout
*Jul 10 03:34:24.783: Ce0/0/0 DDR: rotor dialout [best] least recent failure is also most recent failure
*Jul 10 03:34:24.783: Ce0/0/0 DDR: rotor dialout [best] also has most recent failure
*Jul 10 03:34:24.783: Ce0/0/0 DDR: rotor dialout [best]
*Jul 10 03:34:24.783: Di1 DDR: Nailing up the Dialer profile [attempt 16]
*Jul 10 03:34:24.783: Di1 DDR: Dialer dialing - persistent dialer profile
*Jul 10 03:34:24.783: Ce0/0/0 DDR: Dialing cause Persistent Dialer Profile
*Jul 10 03:34:24.783: Ce0/0/0 DDR: Attempting to dial lte
*Jul 10 03:34:24.783: CHAT0/0/0: Attempting async line dialer script
*Jul 10 03:34:24.783: CHAT0/0/0: Dialing using Modem script: lte & System script: none
*Jul 10 03:34:24.783: CHAT0/0/0: process started
*Jul 10 03:34:24.783: CHAT0/0/0: Asserting DTR
*Jul 10 03:34:24.783: CHAT0/0/0: Chat script lte started
*Jul 10 03:34:24.783: CHAT0/0/0: Sending string: AT!CALL1
*Jul 10 03:34:24.783: CHAT0/0/0: Expecting string: OK
*Jul 10 03:34:25.571: CHAT0/0/0: Completed match for expect: OK
*Jul 10 03:34:25.571: CHAT0/0/0: Chat script lte finished, status = Success
*Jul 10 03:34:26.583: Ce0/0/0 DDR: disconnecting call
*Jul 10 03:34:28.775: Di1: No free dialer - starting fast idle timer
*Jul 10 03:34:28.775: Di1: No free dialer - starting fast idle timer
*Jul 10 03:34:33.999: Di1: No free dialer - starting fast idle timer
*Jul 10 03:34:34.999: Di1: No free dialer - starting fast idle timer
*Jul 10 03:34:37.643: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed state to down
*Jul 10 03:34:38.643: %LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed state to down
*Jul 10 03:34:41.583: Ce0/0/0 DDR: re-enable timeout
*Jul 10 03:34:42.583: Ce0/0/0 DDR: rotor dialout [best] least recent failure is also most recent failure
*Jul 10 03:34:42.583: Ce0/0/0 DDR: rotor dialout [best] also has most recent failure
*Jul 10 03:34:42.583: Ce0/0/0 DDR: rotor dialout [best]
*Jul 10 03:34:42.583: Di1 DDR: Nailing up the Dialer profile [attempt 17]
*Jul 10 03:34:42.583: Di1 DDR: Dialer dialing - persistent dialer profile
*Jul 10 03:34:42.583: Ce0/0/0 DDR: Dialing cause Persistent Dialer Profile
*Jul 10 03:34:42.583: Ce0/0/0 DDR: Attempting to dial lte
*Jul 10 03:34:42.583: CHAT0/0/0: Attempting async line dialer script
*Jul 10 03:34:42.583: CHAT0/0/0: Dialing using Modem script: lte & System script: none
*Jul 10 03:34:42.583: CHAT0/0/0: process started
*Jul 10 03:34:42.583: CHAT0/0/0: Asserting DTR
*Jul 10 03:34:42.583: CHAT0/0/0: Chat script lte started
*Jul 10 03:34:42.583: CHAT0/0/0: Sending string: AT!CALL1
*Jul 10 03:34:42.583: CHAT0/0/0: Expecting string: OK
*Jul 10 03:34:43.671: CHAT0/0/0: Completed match for expect: OK
*Jul 10 03:34:43.671: CHAT0/0/0: Chat script lte finished, status = Success
*Jul 10 03:34:45.671: %LINK-3-UPDOWN: Interface Cellular0/0/0, changed state to up
*Jul 10 03:34:45.671: Ce0/0/0 DDR: Dialer statechange to up
*Jul 10 03:34:45.671: %DIALER-6-BIND: Interface Ce0/0/0 bound to profile Di1
*Jul 10 03:34:45.671: Ce0/0/0 DDR: Dialer call has been placed
*Jul 10 03:34:45.671: Ce0/0/0 DDR: dialer protocol up
*Jul 10 03:34:45.671: Di1 DDR: Persistent Dialer Profile nailed up successfully
*Jul 10 03:34:46.671: %LINEPROTO-5-UPDOWN: Line protocol on Interface Cellular0/0/0, changed state to up
Profile Information
====================
Profile 1 = INACTIVE*
PDP Type = IPv4
Access Point Name (APN) = VZWINTERNET
Authentication = None
Username:
Password:
* - Default profile
arch-eng-router1#ping 4.2.2.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 4.2.2.1, timeout is 2 seconds:
Success rate is 0 percent (0/5)
Ultimately... once the Ethernet cable is attached, the Cellular 0/0/0 interface resets, attempts to connect, connects, resets, etc... Once the Ethernet cable is disconnected, the Cellular 0/0/0 interface successfully reconnects.
I am not really sure how to further troubleshoot this and was hoping someone in the community would have some additional thoughts on how to proceed.
Thanks so much for your time!I have recently dealt with a similar issue and it was due to NAT not being configured correctly causing the cell card to flop. You really have to NAT all inside traffic regardless of whether is it allowed out or not otherwise Verizon detects it as invalid traffic and drops your cell connection. The blocking of outside traffic to the outside interface should be handled as a "in" ACL on the LAN interface. See some of my config below with some other lines of code I found helpful, tailor to your needs. Let me know how it goes.
ip access-list extended NAT_Traffic
!This is denying any VPN traffic that is outbound on the external interface. If this traffic allows will flop the cell interface.
deny ip any 10.254.254.0 0.0.0.15
!You can modify this to only be the LAN subnets you are actually using but try "any any" just to test.
permit ip any any
ip access-list extended Limited_Internet
!This allows my LAN to communicate with my 10.x.x.x VPN subnets.
permit ip 169.254.0.0 0.0.255.255 10.254.254.0 0.0.0.15
!This allows the one ip address to access the internet and denies all other LAN traffic.
permit ip host 169.254.231.201 any
deny ip 169.254.0.0 0.0.255.255 any
!restrict all traffic except listed below for cell port.
ip access-list extended Secure_Access_In
!I specify the Static IP used but you will have to suit a dynamic IP.
permit tcp any host A.B.C.D eq 22
!Confugure NAT
ip nat inside source list NAT_Traffic interface Cellular0 overload
!Apply ACLs to interfaces
interface Vlan1
!Restricts internet to a limited set of IPs and allows VPN traffic to flow.
ip access-group Limited_Internet in
interface Cellular0
ip access-group Secure_Access_In in
!To allow internet access out from LAN hosts if you have a ACL blocking traffic in on the Cell interface. Always a good idea.
!What to inspect for contect based access control.
ip inspect name INSPECT-IN-OUT tcp
ip inspect name INSPECT-IN-OUT udp
ip inspect name INSPECT-IN-OUT icmp
!where to apply the outgoing CBAC inspection
interface Cellular0
ip inspect INSPECT-IN-OUT out
Hopefully you haven't pulled too much hair out and this helps to fix. -
Number of Asychronous Interface on AS5350XM ...
Hi Experts,
I am setting up an AS5350XM gateway and I notice that the default Async Interfaces are from int 1/0 - 1/59 and 2/0 to 2/59 which means that there are 120 Asycn interfaces.
My question is that if I have say 3 E1 lines, which means that I would the capability to have 96 lines and I would only need to set 96 Async interface out of the 120 Async interfaces that I have.
Would this be correct ?
Pls advice,
Cheers,
- sn -The async line capacity is set by the number of SPE's (Signal Processing Elements). Each SPE carrier card has 60 channels and since you have 2 (slot 1 and slot 2) then you could terminate 120 calls.
This is the equivalent to 4 E1's worth of traffic (4 interfaces by 30 channels). So if you have 3 E1's, then you will have some spate capacity.
Maybe you are looking for
-
Command to open a PDF generated Oracle Report in New browser window
I know this is probably something for the Oracle Forums but I'll ask anyway because I can't find any info out there on this, without some extra work. I am generating a PDF file from 10g Oracle reports on Linux RHEL 5 and storing the PDF file to the s
-
Iphone 4 won't show up in Itunes update 11.1.5
Okay, so I just updated my Itunes to 11.1.5. My Apple TV shows up in devices, but my Iphone 4 won't. I want to downlaod my new music. I have tried reinstalling Itunes I have tried basically everything. PLEASE HELP ME!!!
-
Difference between exists and in operators in oracle?
what is difference between exists and in operators in oracle? what is faster and why?
-
After recording an old audio tape, how do I insert track (song) numbers?
After recording an old audio tape, how do I insert track (song) numbers?
-
What should i do after 2.3 years in ABAP
Hi All, I am an ABAP consultant with 2.3 years of experiance. Now i want to explore other areas in SAP (technical). So please suggest me that which area will be helpful for servival & growth. Thanks RK