Howard, Not sure if it's ideal or not but we've always added the statements for each subnet: ip route XXX.XXX.3.0 255.255.255.128 XXX.XXX.12.56 (VLAN 300) ip route XXX.XXX.3.128 255.255.255.128 XXX.XXX.12.56 (VLAN 301) ip route XXX.XXX.4.0 255.255.255.128 XXX.XXX.12.56 (VLAN 400) ip route XXX.XXX.4.128 255.255.255.128 XXX.XXX.12.56 (VLAN 401) ip route XXX.XXX.5.0 255.255.255.128 XXX.XXX.12.56 (VLAN 500) ip route XXX.XXX.5.128 255.255.255.128 XXX.XXX.12.56 (VLAN 501) ip route XXX.XXX.6.0 255.255.255.128 XXX.XXX.12.56 (VLAN 600) ip route XXX.XXX.6.128 255.255.255.128 XXX.XXX.12.56 (VLAN 601)
CH From: Cisco Clean Access Users and Administrators [mailto:[email protected]] On Behalf Of Speight, Howard Sent: Thursday, March 25, 2010 02:17 PM To: [email protected] Subject: Sad but true I feel more comfortable asking questions or advice on this list than contacting TAC. Yes, I did open a TAC case... :) Those of you using Real-IP In-Band, how do you have your route statements configured on the router? For example: Managed subnets n.n.1.0 - n.n.14.0 Ip route n.n.1.0 255.255.255.0 n.n.n.n (IP address of CAS or service IP for those in HA mode) Ip route n.n.2.0 255.255.255.0 n.n.n.n Ip route n.n.3.0 255.255.255.0 n.n.n.n Etc... Ip route n.n.14.0 255.255.255.0 Or Ip route n.n.1.0 255.255.252.0 n.n.n.n (n.n.1.0 - n.n.4.0) Ip route n.n.5.0 255.255.252.0 n.n.n.n (n.n.5.0 - n.n.8.0) Ip route n.n.9.0 255.255.252.0 n.n.n.n (n.n.9.0 - n.n.12.0) Ip route n.n.13.0 255.255.254.0 n.n.n.n (n.n.13.0 - n.n.14.0) Reduces IP route statements from 14 to 4. That would be ideal, but if you're like us the managed subnets are spread all over the place. Just curious, I haven't tried this, yet? If you're wondering why bother, beside less typing (copy/paste), smaller memory utilization on router, probably insignificant. Thanks, Howard
