|
|
|
(Applies to Bivio 2000 appliances only.)
If you intend to connect the NBA to a hub or policy engines, you must connect the NBA management port to a router, and not directly to a switch. Furthermore, the management port must be on a different IP subnet to the policy engine port, s0.e2.
Specifically, you must connect the NBA management port to a router that has at least two Ethernet ports. You connect the NBA management port to one Ethernet port, then connect the router via a second Ethernet port to your corporate network. In effect, you are using a router to isolate the NBA management port from your corporate network. Note that you will set the management port IP address in the next section.
Why is the setup necessary? Using a router prevents potential time-outs or ‘page not found’ errors when, respectively, a policy engine communicates with port s0.e2 or the NBA console communicates with the management port. If you were to connect the NBA management port to a switch instead of a router, you could experience intermittent race conditions whereby the management port replies to a policy engine request or the s0.e2 port responds to a NBA console request.
When you have connected the NBA management port to the router, you can assign an IP address to this port; see the next section for details.
Note: The architecture diagram in Output to socket connection: Active and passive modes shows how a router is incorporated into an NBA deployment.
| Copyright © 2011 CA. All rights reserved. | Email CA Technologies about this topic |