cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2177
Views
30
Helpful
13
Replies

Issue related to how to use Service Module NME-WAE-502-K9

In my production house 2800 series router there is module called "Integrated Services Engine".

when I  did a "show inventory" it shows that this module: NME-WAE-502-K9, was in the Router.

I want to start implementing and using it, but have not much idea how to use it properly?

Just for understanding the application of this WAAS:

I have a metro-ethernet based service at 200Mbps.

I have a Gre Tunnel set up from my office to a corporate Office in the US, Miami.

What do I need to set this up?

Do I need something on the Corp Office's end?

How can I effectively use this WAAS device?

Any Help in this regard would be apreciable.

Regards

Smith

6 Accepted Solutions

Accepted Solutions

sachinga.hcl
Level 4
Level 4

Hi Smith,

You need to try the followingsteps out of which some of them you might have done already as the module is in the router as of now:

To Initialize Application Accelerators
The NME-WAEs that participate in the network as application accelerators should be brought online after Central Manager, and then registered with Central Manager, using the following sequence:


1. Insert network module into router. -Done
2. Configure network module internal interfaces on the router.
3. Connect to the network module via router console.
4. Complete the CLI setup script.
5. Assign a primary interface.
6. Specify the device mode.
7. Specify the Central Manager IP.
8. Enable CMS.
9. Save the configuration.

The router CLI can be used to verify that the NME-WAE is properly inserted and powered up.
Use the sh ver command within the router CLI to validate that an Integrated Services Engine
appears in the hardware listing. Also, the service-module integrated-Services-Engine 1/0
status command validates that the NME-WAE is running Cisco WAAS software and a
hardware and software state.

The Cisco NME-WAE modules are supported in WAAS 4.0.3 and later versions of WAAS software.

Use the show version command to ensure that the router is running the IOS version.

For NME-WAE-502-K9 IOS Version Required 12.4(9)T or 12.4(9)T1 (recommended).

Make a note of the network module's location in the host router:

slot—Number of the router chassis slot for the module.

     After you install the module, you can get this information from the router's show running-config command output.

unit—Number of the daughter card on the module. This value is always 0.

You can configure network  module software only by using a console that connects to a single  serial-port console port on the host router

You can access the WAAS software that runs on the network module by first accessing one of the following:

The router's Cisco IOS command-line interface (CLI) to open a console session to the network module

The WAAS graphical user interface (GUI)

SUMMARY STEPS

From the Host-Router CLI

1. enable

2. configure terminal

3. interface integrated-service-engine slot/0

4. ip address router-side-ip-address subnet-mask

5. service-module ip address module-side-ip-address subnet-mask

or

service-module external ip address module-side-ip-address subnet-mask

6. service-module ip default-gateway gateway-ip-address

7. end

8. copy running-config startup-config

9. show running-config

he following is sample output of the show diag command for an integrated-service-engine WAAS network module that is installed in slot 2 of a Cisco 3845 router:

Router# show diag 2

Slot 2:

        Integrated Service Engine Port adapter, 1 port

        Port adapter is analyzed 

        Port adapter insertion time unknown

        EEPROM contents at hardware discovery:

        Hardware Revision        : 1.0

        Top Assy. Part Number    : 800-28152-01

        Board Revision           : 03

        Deviation Number         : 0

        Fab Version              : 01

        PCB Serial Number        : FOC101430NK

        RMA Test History         : 00

        RMA Number               : 0-0-0-0

        RMA History              : 00

        Version Identifier       : NA

        CLEI Code                : TDB

        Product (FRU) Number     : NME-WAE-502-K9

        EEPROM format version 4

        EEPROM contents (hex):

          0x00: 04 FF 40 05 5B 41 01 00 C0 46 03 20 00 6D F8 01

          0x10: 42 30 33 88 00 00 00 00 02 01 C1 8B 46 4F 43 31

          0x20: 30 31 34 33 30 4E 4B 03 00 81 00 00 00 00 04 00

          0x30: 89 4E 41 00 00 D9 02 40 C1 C6 8A 54 44 42 00 00

          0x40: 00 00 00 00 00 CB 88 4E 4D 45 2D 52 56 50 4E FF

          0x50: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF

          0x60: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF

          0x70: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF



Kindly check the following URL for more information in this regard:

http://www.cisco.com/en/US/docs/app_ntwk_services/waas/waas/v403/module/configuration/guide/wsnmecfg.html

Please rate.

Regards,

Sachin

View solution in original post

Hi Smith,

1. You can configure the interface for the integrated service module as a  normal interface on the router (Ip addresses, etc.).

2. Then you configure  the NME's IP address and the default gateway from the router. 

3. Then  you should be able to ping the device, and you can either session into  the module from the router or telnet directly to the device like an  appliance.

Hope that Helps.

Sachin

View solution in original post

The Central Manager (CM)is a mandatory part of every WAAS  installation.

It allows you to have a single HTTPS address from which  you manage all the WAEs.

The  CM demonstrates it true worth when you consider having to scale up your  implemenation and you

start using Groups to manage your configurations  across regions and timezones.

Hope this helps to your initial question.

Sachin

View solution in original post

Smith,

It's basically just the number of managed devices.  Most of what the CM  does is push configs, replicate the stats and provide reporting.  It's a  very important piece of the infrastructure, however as long as the CM  is within recommended device number, you should be fine.

Sachin

View solution in original post

Robert,

Each device type configured as a Central Manager has a hard limit on  the number of WAAS endpoint devices which it can support.

Here are some  guidelines for Number of Managed Devices per Central Manager appliance :

  • WAVE-274: 125 Devices
  • WAVE-474: 250 Devices
  • WAVE-574-3GB: 500 Devices
  • WAVE-574-6GB:1000 Devices
  • WAVE-674-4GB: 2000 Devices
  • WAVE-674-8GB: 2500 Devices

Sachin

View solution in original post

13 Replies 13

sachinga.hcl
Level 4
Level 4

Hi Smith,

You need to try the followingsteps out of which some of them you might have done already as the module is in the router as of now:

To Initialize Application Accelerators
The NME-WAEs that participate in the network as application accelerators should be brought online after Central Manager, and then registered with Central Manager, using the following sequence:


1. Insert network module into router. -Done
2. Configure network module internal interfaces on the router.
3. Connect to the network module via router console.
4. Complete the CLI setup script.
5. Assign a primary interface.
6. Specify the device mode.
7. Specify the Central Manager IP.
8. Enable CMS.
9. Save the configuration.

The router CLI can be used to verify that the NME-WAE is properly inserted and powered up.
Use the sh ver command within the router CLI to validate that an Integrated Services Engine
appears in the hardware listing. Also, the service-module integrated-Services-Engine 1/0
status command validates that the NME-WAE is running Cisco WAAS software and a
hardware and software state.

The Cisco NME-WAE modules are supported in WAAS 4.0.3 and later versions of WAAS software.

Use the show version command to ensure that the router is running the IOS version.

For NME-WAE-502-K9 IOS Version Required 12.4(9)T or 12.4(9)T1 (recommended).

Make a note of the network module's location in the host router:

slot—Number of the router chassis slot for the module.

     After you install the module, you can get this information from the router's show running-config command output.

unit—Number of the daughter card on the module. This value is always 0.

You can configure network  module software only by using a console that connects to a single  serial-port console port on the host router

You can access the WAAS software that runs on the network module by first accessing one of the following:

The router's Cisco IOS command-line interface (CLI) to open a console session to the network module

The WAAS graphical user interface (GUI)

SUMMARY STEPS

From the Host-Router CLI

1. enable

2. configure terminal

3. interface integrated-service-engine slot/0

4. ip address router-side-ip-address subnet-mask

5. service-module ip address module-side-ip-address subnet-mask

or

service-module external ip address module-side-ip-address subnet-mask

6. service-module ip default-gateway gateway-ip-address

7. end

8. copy running-config startup-config

9. show running-config

he following is sample output of the show diag command for an integrated-service-engine WAAS network module that is installed in slot 2 of a Cisco 3845 router:

Router# show diag 2

Slot 2:

        Integrated Service Engine Port adapter, 1 port

        Port adapter is analyzed 

        Port adapter insertion time unknown

        EEPROM contents at hardware discovery:

        Hardware Revision        : 1.0

        Top Assy. Part Number    : 800-28152-01

        Board Revision           : 03

        Deviation Number         : 0

        Fab Version              : 01

        PCB Serial Number        : FOC101430NK

        RMA Test History         : 00

        RMA Number               : 0-0-0-0

        RMA History              : 00

        Version Identifier       : NA

        CLEI Code                : TDB

        Product (FRU) Number     : NME-WAE-502-K9

        EEPROM format version 4

        EEPROM contents (hex):

          0x00: 04 FF 40 05 5B 41 01 00 C0 46 03 20 00 6D F8 01

          0x10: 42 30 33 88 00 00 00 00 02 01 C1 8B 46 4F 43 31

          0x20: 30 31 34 33 30 4E 4B 03 00 81 00 00 00 00 04 00

          0x30: 89 4E 41 00 00 D9 02 40 C1 C6 8A 54 44 42 00 00

          0x40: 00 00 00 00 00 CB 88 4E 4D 45 2D 52 56 50 4E FF

          0x50: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF

          0x60: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF

          0x70: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF



Kindly check the following URL for more information in this regard:

http://www.cisco.com/en/US/docs/app_ntwk_services/waas/waas/v403/module/configuration/guide/wsnmecfg.html

Please rate.

Regards,

Sachin

Thanks for the reply.

I understand when the WAAS is an external appliance connected to the router, but what happens when the card is embedded?

Any help would be appreciable.

Smith.

Hi Smith,

1. You can configure the interface for the integrated service module as a  normal interface on the router (Ip addresses, etc.).

2. Then you configure  the NME's IP address and the default gateway from the router. 

3. Then  you should be able to ping the device, and you can either session into  the module from the router or telnet directly to the device like an  appliance.

Hope that Helps.

Sachin

Thanks for your quick reply.

One more question in this regard  is it mandatory for performing basic WAN acceleration I have to use WAAS Manager or we could do it with 2x NME-WAE-502s ?

Smith

The Central Manager (CM)is a mandatory part of every WAAS  installation.

It allows you to have a single HTTPS address from which  you manage all the WAEs.

The  CM demonstrates it true worth when you consider having to scale up your  implemenation and you

start using Groups to manage your configurations  across regions and timezones.

Hope this helps to your initial question.

Sachin

If i want to choose a WAE Model to act as a Central Manager, what should i pay attention, beside the Number of Managed Devices ?

In my production environment:

I am having 10 CM WAE-512-1G and 12 WAE-512-1G as "Core", 3 NME-WAE-302, 2  NME-WAE-502, and the client is expecting to grow to more 30 remote  sites.

I'm planning to advise the client to upgrade the  Core Appliance from WAE-512-1G to WAE-512-2G, or to buy a WAE-612-2GB,  cause he's concerned with the Optimized TCP Connections limit.

If i change the WAE Core to a greater Model, should i change the CM WAE to ?

Smith

Smith,

It's basically just the number of managed devices.  Most of what the CM  does is push configs, replicate the stats and provide reporting.  It's a  very important piece of the infrastructure, however as long as the CM  is within recommended device number, you should be fine.

Sachin

Does the Central Manager have a a hard limit or does it depend on the device type ?

Smith

Robert,

Each device type configured as a Central Manager has a hard limit on  the number of WAAS endpoint devices which it can support.

Here are some  guidelines for Number of Managed Devices per Central Manager appliance :

  • WAVE-274: 125 Devices
  • WAVE-474: 250 Devices
  • WAVE-574-3GB: 500 Devices
  • WAVE-574-6GB:1000 Devices
  • WAVE-674-4GB: 2000 Devices
  • WAVE-674-8GB: 2500 Devices

Sachin

Superb. This is the answer what I was looking for.

Thanks a ton Sachin. You are the man.

ktunugun
Cisco Employee
Cisco Employee

Hi Robert,

In your post you have said that WAN is based on metro ethernet with 200 Mbps. Have you refered to the WAAS sizing guidelines for this site. How much optimized traffic is expected for this site. Please refer to the attached sizing guide for correct WAAS device sizing for your sites.

https://www.myciscocommunity.com/docs/DOC-4431

Also attached the configration guide for Network Module that will help you with step by step configuration of NM.

Hope this helps.

Kiran.

Hi

I am not able to see this weblink you send to me.

Smith.