We have an IDS ver 4.1 in a cat 6k, and initially addressed it in a lab in vlan 1 as such:
vlan 1: 126.96.36.199 /24
IDS: 188.8.131.52 /24
the IDS gateway is Vlan 1 ip.
this has worked fine, able to ping and telnet btw. the 6k and the IDS. but in getting ready for deployment, we have decided that we would rather not use vlan 1, and created a new vlan for our IDS and NAM, say VLAN 100. we removed the addressing from VLAN 1 and shut it down. Addressed VLAN 100 in the say way, but now no longer to even ping the IDS from the cat 6k. I even added a static route:
ip route 184.108.40.206 255.255.255.255. vlan 100
still unable to ping the IDS. It seems that the vlan 1 info is cached in some way, preventing any access through the new vlan 100. we cleared the arp, is there anything else that needs cleared so the IDS can be part of vlan 100 as it was in vlan 1.
Also, is there any known issue if we were to decide to put the IDS and NAM back into vlan 1 ?
BenefitsDocumentationPrerequisiteImage Download LinksLimitationsSupported PlatformsLicense RequirementsTopologyStep-By-Step ConfigurationConfigure Virtual ServiceActivate the virtual service and configure guest IPsConfiguring UTD (Service Plane)Configurin...
Login to the FXOS chassis manager.
Direct your browser to https://hostname/, and log-in using the user-name and password.
Go to Help > About and check the current version:
Check the current version availa...
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...