This is usual because the gateway has been assigned to a Route patterns. Check your route patterns and see which one this gateway has already been assigned to. Remove the gateway and then you can add it to a route group
Please rate all useful posts
"The essence of christianity is not the enthronement but the obliteration of self --William Barclay"
aokanlawon is correct (+5), to quickly see which route patterns use this GW directly (not a good practice) you can use dependency records (upper right corner drop box) assuming you have dependency records enabled via enterprise parameters.
thank you so much all , i found the issue , the sub unit wasn't in a device pool , it eas in none device pool ,and when i change the device pool coinfiguration for this port , the decice appeared in the list
I'm not able to access my old voice mail messages all of a sudden. The recording says something like 'the message is currently not available'. This has never happened before in all the years I have been using this system. I have t...
If you have 2 ISR routers, one acting as Failover, do we need to have both the same number of SRST licenses on the 2 routers?
No. You will only need the SRST licenses on the primary router. Because this feature...