It was recently found that when adding permit statements to a match crypto-map access-list that if the sequence of permit statements was re-arranged that some of the phase 2 associations over the vpn peer sessions would no longer associate therefore no SPI’s were created for them. To fix this problem we placed the permit statements back in the original order or sequence that they were in and just added any new ones at the bottom of the permit list. Then we hardware disconnected the interface the vpn connected through on the router and let the vpn peers phase 1 re-establish. All came up and worked after that. Is this someting that is common on Cisco Routers? Is there a better solution to this?