See the additional lines of config, hope it helps.  It has been a while so I would have to dig up documents to understand the reason for these commands. chat-script ltescript "" "AT!CALL1" TIMEOUT 20 "OK" interface Cellular0 ip address negotiated ip access-group Secure_Access_In in no ip redirects no ip unreachables no ip proxy-arp ip nat outside ip inspect INSPECT-IN-OUT out ip virtual-reassembly in encapsulation slip load-interval 30 dialer in-band dialer enable-timeout 60 dialer string ltescript dialer watch-group 1 async mode interactive crypto map ezvpnmap dialer watch-list 1 ip 5.6.7.8 0.0.0.0 dialer watch-list 1 delay route-check initial 60 dialer watch-list 1 delay connect 1 interface Vlan1 ip address 169.254.254.254 255.255.0.0 ip access-group Limited_Internet in ip nat inside ip virtual-reassembly in ip tcp adjust-mss 1400 ip policy route-map clear-df ... View more

My cli commands and comments contain the fix.  Just suit the network addresses to your environment. The most important lines are: ip access-list extended NAT_Traffic !This is denying any VPN traffic that is outbound on the external interface. If this traffic is allowed it 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 !Confugure NAT ip nat inside source list NAT_Traffic interface Cellular0 overload ... View more

Did you find a resolution to these issues?  I wonder if the issues remained using the same SFP model (Cisco or Moxa) in both disparate switches.  I know Cisco requires a command to allow non-cisco SFPs to function. ... View more

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. ... View more