|
|
The primary goal of your Cisco StrataView Plus (SV+) network design is to build the simplest, most economical communication network possible while enabling both flat and tiered networks.
Determination of the number and placement of Cisco SV+ workstations throughout the network is largely dependent on the amount of message traffic between Cisco SV+ and the nodes within the network, and the ability of either Cisco SV+ or the individual IPX/BPX/IGX nodes to process the messages. As each component in the network owns indigenous factors that contribute to overall performance, a key issue becomes understanding the limitation of each component and determining which component is the limiting factor in the network design.
Each Cisco SV+ workstation resident within a network must be able to communicate with all nodes within the network.
Each node can have two different IP addresses. The first is the network IP address. You configure the network IP address on a switch by invoking the cnfnwip command from the Switch Command Line Interface (CLI). The network IP address is used by Cisco SV+ to communicate with all nodes in the network.
The second type of IP address, is the LAN IP address. It is configured on a switch by invoking the cnflan command from the Switch CLI. Cisco SV+ uses the LAN IP address for communicating with a gateway node and all feeder nodes.
Following are descriptions of various components found in a Cisco SV+ network:
A Gateway node provides topology and other vital information about the network to Cisco SV+. The Gateway node name is specified in the /usr/users/svplus/config.sv file on the Cisco SV+ workstation.
A proprietary protocol used by Cisco WAN switches to pass IP traffic over a WAN network.
A node in the WAN network used to relay IP traffic for a group of nodes in the network. When the nodes in the network are geographically distributed, or when the network is large and you created subnets to manage the network, one node in each subnet can be used to relay the IP traffic to all the nodes in that subnet.
Cisco SV+ and BPX/IPX/IGX nodes use a proprietary protocol to exchange network management information. Cisco SV+ establishes two types of links (Link0 and Link1) with BPX/IGX/IPX nodes. Cisco SV+ establishes a Link0 link with the Cisco SV+ Gateway node, and a Link1 link with all nodes in the network. A Link0 link is also established between Cisco SV+ and IPX/IGX feeder nodes.
Four types of network management traffic flows between Cisco SV+ and the Cisco WAN switches Cisco SV+ manages (Link0, Link1, TFTP, and SNMP). Cisco SV+ only uses SNMP and TFTP to communicate with AXIS nodes.
You have two options for configuring your network for network management. You can use In-Band Management or Out-of-Band Management.
When using In-Band Management, the network management traffic flows through the network you are managing. Switch software uses the proprietary IP Relay protocol to pass IP traffic over trunks in the WAN network for In-Band Management. To use In-Band Management, at least one node in the network to be managed by Cisco SV+, must be connected, by way of a LAN, to Cisco SV+. This node is called the Gateway node. All network management data from all other nodes in the network flows through the Gateway node to Cisco SV+. Two methods exist to configure Cisco SV+ to use In-Band Management:
1. The last field in the /usr/users/svplus/config.sv entry should be set to nwip_off.
2. The last field in the /usr/users/svplus/config.sv entry should be set to nwip_on and the routes to all nodes should be configured in such a way that all packets destined for all nodes are directed through the IP Relay Gateway node.
With Out-of-Band Management, the traffic flows directly from individual nodes to the Cisco SV+ workstation without being routed through the Gateway node. To configure Cisco SV+ to use Out-of-Band Management, the last field in the /usr/users/svplus/config.sv entry should be set to nwip_on and direct routes from Cisco SV+ to all individual nodes should exist.
Posted: Mon Oct 4 19:48:54 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.