HI,
We just upgraded a customer to IPO R11.
here is the network config:
PC ----Network 10.0.0.0 --- 10.0.0.1 Router 172.12.12.254 --- Network 172.12.12.0 --- ipo 172.12.12.1
Windows has a a iproute 172.12.12.0 255.255.255.0 10.0.0.1
I can ping ipo without any issue
When we start the manager i can find a new iproute 172.12.12.1 255.255.255.255 10.0.0.1 metric 11, and i cannot ping ipo anymore but i can ping all others device in the network 172.12.12.0
Any idea why the manager create this iproute ?
How can i set up the manager to not create this route ?
we didn't had this issue in release 10.
Thx
ACIS - ACSS
We just upgraded a customer to IPO R11.
here is the network config:
PC ----Network 10.0.0.0 --- 10.0.0.1 Router 172.12.12.254 --- Network 172.12.12.0 --- ipo 172.12.12.1
Windows has a a iproute 172.12.12.0 255.255.255.0 10.0.0.1
I can ping ipo without any issue
When we start the manager i can find a new iproute 172.12.12.1 255.255.255.255 10.0.0.1 metric 11, and i cannot ping ipo anymore but i can ping all others device in the network 172.12.12.0
Any idea why the manager create this iproute ?
How can i set up the manager to not create this route ?
we didn't had this issue in release 10.
Thx
ACIS - ACSS