Internal Integration between Ether Switch Module and CME Route Module
I am having Cisco 2811 CME router with NME-16ES-1G-P Module. I am able to login to the sevice module and configure the same.
But the switch service module is integrated with the router's gig interface externally using cat5 cable. I strongly believe that there must be a way to connect the switch service module with the router module internally by running some command/s.
I have already gone through "Cisco EtherSwitch Service Modules Feature
Guide" and didn't find any way to integrate them internally.
Kindly help me to understand this integration between Router Module with Switch service Module.
Re: Internal Integration between Ether Switch Module and CME Rou
I couldn't find the document that helped. So I'll try to do my best. If you have any questions please ask.
The NME-16ES-1G-P module is managed with an ip address assigned to it's external gigabit port on the router. On the 2811 it fills the NM port on the router assigning itself to GI1/0.
Management is accomplished by the following:
ip address x.x.x.x x.x.x.x
service-module gigabitethernet 1/0 session
The module itself acts as an external 3750 switch. Any updates to the IOS should use 3750 images.
This is where it gets a little more complicated. Even though Gi1/0 is external on the NME module it can be used by the router itself and by the switch.
For example the router sees this port as Gi10/0. The switch sees this port externally as GI1/0/1. You may use this port as an uplink to additional external switches and or hubs. You can also send VLAN, VTP and trunking features across this interface.
The NME sees it's internal communications with the router using the internal port of GI1/0/2. You can send VLAN, VTP and trunking features. However these will be seen by the router.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.