|
|
The primary goal of your Cisco WAN Manager (CWM) 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 CWM workstations throughout the network is largely dependent on the amount of message traffic between CWM and the nodes within the network, and the ability of either CWM or the individual IPX, BPX® 8600 series, or IGX 8400 series 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 CWM 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 CWM 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. CWM uses the LAN IP address for communicating with a gateway node and all feeder nodes.
Following are descriptions of various components found in a CWM network:
A Gateway node provides topology and other vital information about the network to CWM. The Gateway node name is specified in the /usr/users/svplus/config.sv file on the CWM workstation.
IP Relay is a proprietary protocol used by Cisco WAN switches to pass IP traffic within a Cisco WAN network. The IP-Relay function stops at the gateway switch.
The IP Relay gateway is 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 that are connected via trunks. IP Relay traffic will pass through a trunk's Statistical Reserve, but not pass over lines.
CWM and BPX 8600 series, IPX, or IGX 8400 series nodes use a proprietary protocol to exchange network management information. CWM establishes two types of links (Link0 and Link1) with BPX 8600 series, IPX, or IGX 8400 series nodes. CWM establishes a Link0 link with the CWM Gateway node, and a Link1 link with all nodes in the network. A Link0 link is also established between CWM and IPX or IGX 8400 series feeder nodes.
Four types of network management traffic flow between CWM and the Cisco WAN switches CWM manages
CWM only uses SNMP and TFTP to communicate with MGX 8200 series nodes.
This section provides information about ports used by CWM for outgoing and incoming communications.
Table 12-1, "Outgoing Ports Used by CWM", lists the outgoing ports CWM uses to communicate with the nodes.
Protocol | Port, Function |
|---|---|
udp | 161, SNMP get/set |
udp | 69, tftp server |
tcp | 23, telnet |
tcp | 13, daytime |
Table 12-2, "Incoming Ports Used by CWM", lists the incoming ports the nodes use to communicate with CWM.
Protocol | Port, Function |
|---|---|
udp | 162, SNMP Trap |
udp | 2500, rtm |
udp | 8161, SNMP Agent |
tcp | 8888, HPOV Topology daemon |
tcp | 9999, HPOV Database daemon |
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 CWM, must be connected, by way of a LAN, to CWM. This node is called the Gateway node. All network management data from all other nodes in the network flows through the Gateway node to CWM. You can configure CWM to use In-Band Management using a basic hub attachment without a router or across routers.
Figure 12-1 is an illustration of a typical network set up for In-Band management without routers. The following configuration of workstation files is required to support in-band management of the network without routers.
Step 1 Modify the /usr/users/svplus/config.sv file to include the name of the Gateway node, igx2-lan, in the third field and change the last field to nwip_off.
The contents of the config.sv file should look similar to the following:
0|Network1|igx-lan2|9600|0|7|6|0|30|1024|9.2|nwip_off|
Step 2 Modify the /etc/hosts file to include the following (along with the file's usual contents).
IP Address | Device Name |
|---|---|
172.70.207.6 | igx2-lan |
192.0.0.6 | igx2 |
192.0.0.7 | igx3 |
192.0.0.8 | bpx4 |
172.70.207.9 | axis1-lan |
192.0.0.9 | axis1 |
172.70.207.10 | axis2-lan |
192.0.0.10 | axis2 |
Step 3 Modify the /etc/rc2.d/S72inetsvc file to add routes by adding a lines similar to the following:
/usr/sbin/route add net 192.0.0.0 172.70.207.6 1
Add this line after the line similar to the following:
/usr/sbin/route add -interface -netmask "240.0.0.0" "224.0.0.0" "$mcastif"
Step 4 Verify your network structures by issuing "netstat -rn" and checking the results against the following table.
Routing Table Destination | Gateway | Flags | Ref | Use | Interface |
|---|---|---|---|---|---|
127.0.0.1 | 127.0.0.1 | UH | 0 | 6061 | lo0 |
192.0.0.0 | 172.70.207.6 | UG | 0 | 461 |
|
172.70.207.0 | 172.70.207.5 | U | 3 | 1311 | hme0 |
224.0.0.0 | 172.25.70.8 | U | 3 | 0 | hme0 |
The following tables provide node configuration information about the nodes shown in Figure 12-1, In-Band Management - Basic Hub Attachment Without Router.
CLI Command | Data |
|---|---|
cnfname | igx2 |
cnflan (IP address, subnet mask, default)) |
|
cnfnwip (IP address, subnet mask |
|
cnfstatmast | 172.70.207.5 |
cnffwswinit | 170.70.207.5 |
cnfswfunc | Configure/Save/Restore |
cnffunc | Download/Remote/Sv+ |
cnfsnmp | public, private, public |
CLI Command | Data |
|---|---|
cnfname | bpx4 |
cnflan (IP address, subnet mask, default)) |
|
cnfnwip (IP address, subnet mask |
|
cnfstatmast | 172.70.207.5 |
cnffwswinit | 170.70.207.5 |
cnfswfunc | Configure/Save/Restore |
cnffunc | Download/Remote/Sv+ |
cnfsnmp | public, private, public |
CLI Command | Data |
|---|---|
cnfname | axis1 |
cnfifip (26 Ethernet, subnet mask, default) |
|
cnfifip (37 ATM, subnet mask) |
|
cnfstatmast | 172.70.207.5 |
cnffwswinit | 170.70.207.5 |
CLI Command | Data |
|---|---|
cnfname | igx3 |
cnflan (IP address, subnet mask, default) |
|
cnfnwip (IP address, subnet mask) |
|
cnfstatmast | 172.70.207.5 |
cnffwswinit | 170.70.207.5 |
cnfswfunc | Configure/Save/Restore |
cnffunc | Download/Remote/Sv+ |
cnfsnmp | public, private, public |
CLI Command | Data |
|---|---|
cnfname | axis2 |
cnfifip (26 Ethernet, subnet mask, default) |
|
cnfifip (37 ATM, subnet mask) |
|
cnfstatmast | 172.70.207.5 |
cnffwswinit | 170.70.207.5 |
Figure 12-2 is an illustration of a typical network set up for In-Band management using routers. The following configuration of workstation files is required to support in-band management of the network using routers.
Step 1 Modify the /usr/users/svplus/config.sv file to include the name of the Gateway node, igx2-lan, in the third field and change the last field to nwip_off.
0|Network1|igx2-lan|9600|0|7|6|0|30|1024|nwip_off|
Step 2 Modify the /etc/hosts file to include the following (along with the usual contents of this file).
IP Address | Device Name |
|---|---|
172.70.207.6 | igx2-lan |
192.0.0.6 | igx2 |
192.0.0.7 | igx3 |
192.0.0.8 | bpx4 |
172.70.207.9 | axis1-lan |
192.0.0.9 | axis1 |
172.70.207.10 | axis2-lan |
192.0.0.10 | axis2 |
Step 3 Modify the /etc/defaultrouter file to include the following line:
172.70.106.1 1
Step 4 Modify the /etc/rc2.d/S72inetsvc file to add routes by including the following lines:
/usr/sbin/route add default 172.70.108.1 1
/usr/sbin/route add net 192.0.0.0 172.70.106.1 1
Add these lines after the line similar to the following:
/usr/sbin/route add -interface -netmask "240.0.0.0" "224.0.0.0" "$mcastif"
Step 5 Verify your network structures by issuing "netstat -rn" and checking the results against the following table.
Routing Table Destination | Gateway | Flags | Ref | Use | Interface |
|---|---|---|---|---|---|
127.0.0.1 | 127.0.0.1 | UH | 0 | 6061 | lo0 |
192.0.0.0 | 172.70.207.6 | UG | 0 | 461 |
|
172.70.207.0 | 172.70.207.5 | U | 3 | 1311 | hme0 |
224.0.0.0 | 172.25.70.8 | U | 3 | 0 | hme0 |
Default | 172.70.106.1 |
|
|
|
|
The following tables provide node configuration information about the nodes shown in Figure 12-2, In-Band Management Using an IP Relay Gateway.
CLI Command | Data |
|---|---|
cnfname | igx2 |
cnflan (IP address, subnet mask, default)) |
|
cnfnwip (IP address, subnet mask |
|
cnfstatmast | 172.70.207.5 |
cnffwswinit | 170.70.207.5 |
cnfswfunc | Configure/Save/Restore |
cnffunc | Download/Remote/Sv+ |
cnfsnmp | public, private, public |
CLI Command | Data |
|---|---|
cnfname | bpx4 |
cnflan (IP address, subnet mask, default)) |
|
cnfnwip (IP address, subnet mask |
|
cnfstatmast | 172.70.207.5 |
cnffwswinit | 170.70.207.5 |
cnfswfunc | Configure/Save/Restore |
cnffunc | Download/Remote/Sv+ |
cnfsnmp | public, private, public |
CLI Command | Data |
|---|---|
cnfname | axis1 |
cnfifip (26 Ethernet, subnet mask, default) |
|
cnfifip (37 ATM, subnet mask) |
|
cnfstatmast | 172.70.207.5 |
cnffwswinit | 170.70.207.5 |
CLI Command | Data |
|---|---|
cnfname | igx3 |
cnflan (IP address, subnet mask, default) |
|
cnfnwip (IP address, subnet mask) |
|
cnfstatmast | 172.70.207.5 |
cnffwswinit | 170.70.207.5 |
cnfswfunc | Configure/Save/Restore |
cnffunc | Download/Remote/Sv+ |
cnfsnmp | public, private, public |
CLI Command | Data |
|---|---|
cnfname | axis2 |
cnfifip (26 Ethernet, subnet mask, default) |
|
cnfifip (37 ATM, subnet mask) |
|
cnfstatmast | 172.70.207.5 |
cnffwswinit | 170.70.207.5 |
This section provides information about how to configure the MGX 8850 switch as a feeder.
To set up an MGX 8850 Feeder session, complete the following steps:
Step 1 Use the cnfname command to assign a name to the MGX 8850 node. The syntax for this command is: cnfname <node name>
> cnfname popeye3a
Step 2 Use the cnfifip command to configure the internet address of the MGX 8850. The syntax for this command is: cnfifip <interface> <IP address> <net mask> <broadcast address>
> cnfifip 28 172.29.37.78 255.255.255.000 0
> cnfifip 37 172.1.1.78 255.255.255.000 0
> cnfnwip 172.1.1.78
Step 3 Use the dspifip command to check LAN IP and NWIP
> dspifip
Interface IP Address NetMask BroadcastAddress
--------- -------- ------ -------------
Ethernet 172.29.37.78 255.255.255.000
Slip 255.255.255.000
ATM 172.1.1.78 255.255.255.000
Step 4 Use the addln command to configure a line. The syntax of this command is:
addln -ds3 <line number> | -e3 <line number> | -sonet <line number>
> addln -sonet 7.1
Step 5 Use the upif command to add a logical interface to a broadband port on a PXM. The syntax for this command is: upif <if_num> <lin_num> <pct_bw> <min_vpi> <max_vpi>
> upif 1 1 100 0 4095
Step 6 Use the addrscprtn command to specify the parameters for the resource partitions. The syntax for this command is: addrscprtn <if_num> <ctrlr_num> <ingr_pct_bw> <egr_pct_bw> <min_vpi> <max_vpi> <min_vci> <max_vpi> <max_chans>
> addrscprtn 1 1 100 0 4095 0 65535 32767
Step 7 Use the cnfswfunc command to configure the node-level features of the MGX 8850 switch as a feeder node. The syntax of this command is: cnfswfunc [ <-vsvd enable(yes) | disable<no)> ] | [ <-ndtype> <fdr | routing>]
> cnfswfunc -ndtype fdr
Step 8 Use the cnfifastrk command to configure the interface as a feeder trunk. The syntax of this command is: cnfifastrk <slot.port><iftype>
> cnfifastrk 7.1 ftrk
Step 9 Telnet to the BPX® 8600 series switch. (This example assumes that the MGX 8850 trunk is connected to slot 9, line 1.)
> telnet xxxyyyzzz
Step 10 Use the uptrk command to (to be supplied).
> uptrk 9.1
Step 11 Use the addshelf command to (to be supplied)
> addshelf 9.1 x
Step 12 Use the dsptrks command to display the trunk status and verify that the trunk is clear.
> dsptrks
TRK Current Alarm Status Other End
7.1 Clear bpx4
Step 13 At the CWM workstation, become the root user.
Step 14 Issue the route command to (to be supplied).
> route add net 172.1.1.0 bpx_IP_address 1
Step 15 Issue a ping command to the MGX 8850 feeder.
> ping 172.1.1.78
If the ping command is successful, CWM can reach the MGX 8850 feeder node.
Posted: Wed Mar 31 15:19:08 PST 1999
Copyright 1989-1999©Cisco Systems Inc.