| CPUG | |
| The Check Point User Group | |
| A Resource For The Check Point Community. Fast. Useful. Independent. | |
|
| |||||||
![]() |
| | LinkBack | Thread Tools | Search this Thread | Display Modes |
| |||
| Hi, we run static routing on 1/ a pair of VSX Nokia boxes running NGX R65 2/ a pair of VSX Nokia boxes running NG +AI ( R54/55) The pair running R65 have seperate routing tables per instance The pair running NG +AI ( R54/55) seems to show all routes in any instance (static arp entries are seperate). has anyone come across this before? |
| |||
| Which versions of IPSO are involved? I'm guessing IPSO 5.0 for the R65 boxes and IPSO 3.7.89 or similar for the R54/R55 boxes. Has the behavior always been this way or did it just start? Perhaps a reboot is in order. Or an upgrade, since R5x stuff is surely end of support :) |
| |||
| All routes that have been added with 'propagate to adjacent virtual devices' will do that, i.e. all the other VS on the system will see these routes. There is a column in the far right of the route list in the GUI which will show you which have been set to propagate. |
| |||
| R65 ipso = IPSO-5.0-BUILD067-06.16.2009-184058-1515 R55 ipso = IPSO-3.9.91-BUILD014-11.06.2006-192810-1515 All of the output = No in regards to route propagation Some history that might assist: 1/ in the past, we have published routes using Voyager instead of on dashboard. 2/ Also we have tried to build a new virtual instance and had it fail (holding off until we upgrade to R65 now). |
![]() |
| Thread Tools | Search this Thread |
| Display Modes | |
| |