Cisco High-Speed Intrachassis Module Interconnect (HIMI) Configuration Guide

Table Of Contents

Cisco High-Speed Intrachassis Module Interconnect (HIMI) Configuration Guide

Contents

Restrictions for Cisco High-Speed Intrachassis Module Interconnect (HIMI) and Establishing a VLAN

Information About Cisco High-Speed Intrachassis Module Interconnect

Connection Configuration Mode

System Error Messages for the connect Command

How to Configure HIMI Connections

Establishing a HIMI Connection Between an SFP GE Port and a GE NME Slot

Troubleshooting Tips

Establishing a Connection Between Two GE NME Slots

Establishing a HIMI Connection Between an ISM GE Port and an SM GE Port

Examples

Establishing a VLAN Connection

Examples

Troubleshooting Tips

Deactivating a HIMI Connection

Configuration Examples for Cisco High-Speed Intrachassis Module Interconnect

Sample Connection Between an SFP GE Port and a GE NME Slot

Sample Connection Between Two GE NME Slots

Additional References

Related Documents

Technical Assistance

Cisco High-Speed Intrachassis Module Interconnect (HIMI) Configuration Guide

---

The Cisco High-Speed Intrachassis Module Interconnect (HIMI) feature provides the capability to establish a connection between two switch modules (SM), or between an SM and an integrated services module (ISM) on Cisco 2900 series (Cisco 2901 ISRs do not support the HIMI backplane feature.) and Cisco 3900 series routers.

History for the Cisco High-Speed Intrachassis Module Interconnect (HIMI) Feature

Release	Modification
12.4(2)T	This feature was introduced.
15.0(1)M	Added Cisco 2911, Cisco 2921, Cisco 2951, Cisco 3925, and Cisco 3945 routers support.

Finding Support Information for Platforms and Cisco IOS Software Images

Use Cisco Feature Navigator to find information about platform support and Cisco IOS software image support. Access Cisco Feature Navigator at http://www.cisco.com/go/fn. You must have an account on Cisco.com. If you do not have an account or have forgotten your username or password, click Cancel at the login dialog box and follow the instructions that appear.

Contents

•Restrictions for Cisco High-Speed Intrachassis Module Interconnect (HIMI) and Establishing a VLAN

•Information About Cisco High-Speed Intrachassis Module Interconnect

•How to Configure HIMI Connections

•Configuration Examples for Cisco High-Speed Intrachassis Module Interconnect

•Additional References

•Technical Assistance

Restrictions for Cisco High-Speed Intrachassis Module Interconnect (HIMI) and Establishing a VLAN

Connections can be only established as follows:

•All HIMI and VLAN end-point destinations using the connect command must use the interface designation of slot/0, with the exception of service ready engines (SRE), where only the slot/1 interface is capable of HIMI or VLAN connections.

•A module interconnection between the GE port on an SFP module and an NME slot or an NME-to-NME cross-connection is permitted at any given time, but both types of connections cannot exist at the same time.

---

Note On the Cisco 2900 series (Cisco 2901 ISRs do not support the HIMI backplane feature.) and Cisco 3900 series routers, if your ISM or SM supports the HIMI backplane and VLAN connection, the module interconnection between the GE port (with the exception of onboard GE ports) on any slot is permitted at any given time.

---

Cisco 2900 series (Cisco 2901 ISRs do not support the HIMI backplane feature.) and Cisco 3900 series routers support HIMI and VLAN connections. For the maximum number of HIMI and VLAN connections supported on each platform see Table 1.

Table 1 Number of HIMI and VLAN Connections on Cisco 2900 and Cisco 3900 Series Routers 

Router	Cisco 2901	Cisco 2911	Cisco 2921	Cisco 2951	Cisco 3925	Cisco 3945
HIMI Connections	Not supported	1	1	1	2	2
VLAN Connections	Not supported	5	5	7	7	11

Information About Cisco High-Speed Intrachassis Module Interconnect

To configure HIMI connections, you should understand the following concepts:

•Connection Configuration Mode

•System Error Messages for the connect Command

Connection Configuration Mode

The HIMI feature provides the connect connection-name module Module1 Channel-id1 module Module2 Channel-id2 command for the Cisco IOS command line interface (CLI) that creates an interconnection between GE modules using the HIMI.

If the connect command is successfully executed, the router enters connection configuration mode, which is designated by the "config-module-conn" prompt. Once the router is in connection configuration mode, the commands shown in Table 2 can be issued.

To create a connection between two GE ENMs, or between the GE port on a SM and another SM GE port, for the purpose of sending data on a specified VLAN use the connect command in global configuration mode with the vlan vlan-id syntax as in connect connection-name module module1 vlan vlan-id module module2.

Table 2 Connection Configuration Mode Commands 

Command	Description
default	Sets a command to its default values. Has no effect on the connect command functionality.
exit	Exits connection configuration mode. After you exit connection configuration mode, the actual connection establishment phase starts.
shutdown	Shuts down the connection. This command effectively deactivates the connection.
no	Negates a command or sets it to default. The no shutdown command reactivates a previously shut down connection.

To establish a connection, after entering connection configuration mode, issue the exit command to return to configuration mode. The connection will be established after you leave connection configuration mode.

System Error Messages for the connect Command

Table 3 lists the informational error messages which may appear on the console during connection establishment or deletion phases:

Table 3 connect Command System Error Messages 

Message	Message Description
%%CONN MODULE: Slot <slot#> is not supported	The slot number you specified is not supported.
%%CONN MODULE: Interconnect endpoints cannot be on the same slot	The modules you are trying to connect cannot be in the same slot.
%%CONN MODULE: Cannot allocate segment memory	Attempts to allocate segment memory have failed.
%%CONN MODULE: Cannot allocate segment data memory	Attempts to allocate segment data memory has failed.
%%CONN MODULE: Cannot allocate element data memory	Attempts to allocate module list element memory have failed.
%%CONN MODULE: Cannot establish connection between same end-points	You have specified the same module for both segments of the connect command.
%%CONN MODULE: Cannot delete a connection that does not exist	You cannot delete a connection that does not exist.
%%CONN MODULE: At least one of the modules is already in use	You are trying to establish a connection to a module that already has a connection configured.
%%CONN MODULE: Invalid connection found	You are trying to establish a connection between two segments that are not modules.
%%CONN MODULE: Media type for interface <interface-e-name> is sfp	A connection cannot be established to GigabitEthernet0/0 when the mediatype is SFP.
%%CONN MODULE: Interface <interface-name>, Channel <channel-id> already in use	You are trying to establish a connection to GigabitEthernet0/0 when a connection to GigabitEthernet0/0 has already been configured.
%%CONN MODULE: Cannot allocate memory for <interface-name> connection setup	Attempts to allocate control message memory for the connection setup or teardown have failed.
%%CONN MODULE: Cannot find <interface-name> Service Module	The specified interface service module cannot be found in the service module database.
%%CONN MODULE: SerDes connection not supported	SerDes connection is not supported on this platform.
%%CONN MODULE: Interface <interface-name> already in use	You are trying to establish a SerDes connection for an interface that already has a connection configured.
%%CONN MODULE: SerDes connection limit reached	You have reached the SerDes connection limit on this platform.
%%CONN MODULE: At least one of the segments is already in use	You are trying to establish a connection for a segment that already has a connection configured. Note Syslog message for both the HIMI connection and VLAN connect connection.
%%CONN MODULE: VLAN connection not supported	VLAN connection is not supported on this platform. Note Syslog message for the VLAN connect connection only.
%%CONN MODULE: Interface <interface-name>, VLAN <VLAN-number> already in use	You are trying to establish a VLAN connection for an interface on a VLAN that already has a connection configured. Note Syslog message for the VLAN connect connection only.
%%CONN MODULE: VLAN connection limit reached	You have reached the VLAN connection limit on this platform. Note Syslog message for the VLAN connect connection only.

How to Configure HIMI Connections

This section contains the following procedures:

•Establishing a HIMI Connection Between an SFP GE Port and a GE NME Slot

•Establishing a Connection Between Two GE NME Slots

•Establishing a HIMI Connection Between an ISM GE Port and an SM GE Port

•Establishing a VLAN Connection

•Deactivating a HIMI Connection

Establishing a HIMI Connection Between an SFP GE Port and a GE NME Slot

Follow these steps to establish a connection between an SFP module GE port and a GE NME.

SUMMARY STEPS

1. enable

2. configure terminal

3. interface gigabitethernet 0/0

4. media-type rj45

5. exit

6. connect connection-name module Module1 Channel-id1 module Module2 Channel-id2

7. exit

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Router> enable	Enables privileged EXEC mode. •Enter your password if prompted.
Step 2	configure terminal Example: Router# configure terminal	Enters global configuration mode.
Step 3	interface gigabitethernet 0/0 Example: Router(config)# interface gigabitethernet 0/0	Enters interface configuration mode on the Gigabit Ethernet 0/0 interface.
Step 4	media-type rj45 Example: Router(config-if)# media-type rj45	Sets the media type on the Gigabit Ethernet 0/0 interface to RJ-45. Note In order to create a connection to the GE port on the SFP module, the media type on the GE interface must be RJ-45. A connection cannot be established if the media type is SFP.
Step 5	exit Example: Router(config-if)# exit	Exits interface configuration mode.
Step 6	connect connection-name module Module1 Channel-id1 module Module2 Channel-id2 Example: Router(config)# connect connection1 module GigabitEthernet0/0 0 module GigabitEthernet4/0 0	Creates the connection identified as connection-name between the GE module Module1 and the GE module Module2. Note Since this procedure creates a connection between the SFP GE port and an NME, either Module1 or Module2 must be GigabitEthernet0/0. After this command is issued, the router enters connection configuration mode.
Step 7	exit Example: Router(config-module-conn)# exit	Exits module configuration mode. After you exit connection configuration mode, the connection establishment begins.

Troubleshooting Tips

In addition to the system error messages listed in the "System Error Messages for the connect Command" section, the following commands can help troubleshoot NME connections:

•show connection all

•show connection id connection-id

where connection-id is in the range of 0 to 10000

•show connection name connection-name

•show interfaces gigabitethernet 0/0—If a connection has successfully been established between the SFP module and an NME slot, this command will display the output "SFP in use with an NME in Module Interconnection."

Establishing a Connection Between Two GE NME Slots

Follow these steps to establish a connection between two GE NMEs.

SUMMARY STEPS

1. enable

2. configure terminal

3. connect connection-name module module1 channel-id1 module module2 channel-id2

4. exit

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Router> enable	Enables privileged EXEC mode. •Enter your password if prompted.
Step 2	configure terminal Example: Router# configure terminal	Enters global configuration mode.
Step 3	connect connection-name module Module1 Channel-id1 module Module2 Channel-id2 Example: Router(config)# connect connection1 module GigabitEthernet2/0 0 module GigabitEthernet4/0 0	Creates the connection identified as connection-name between the GE NME slot Module1 the GE NME slot Module2. After this command is issued, the router enters module configuration mode.
Step 4	exit Example: Router(config-module-conn)# exit	Exits module configuration mode. After exiting module configuration mode, the connection establishment begins.

Establishing a HIMI Connection Between an ISM GE Port and an SM GE Port

Follow these steps to establish a connection between an ISM module GE port and an SM GE port.

SUMMARY STEPS

1. enable

2. configure terminal

3. connect connection-name module module-type interface-number channel-id module module-type interface-number channel-id

4. end

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Router> enable	Enables privileged EXEC mode. •Enter your password if prompted.
Step 2	configure terminal Example: Router# configure terminal	Enters global configuration mode.
Step 3	connect connection-name module module-type interface-number channel-id module module-type interface-number channel-id Example: Router(config)# connect connection1 module ISM 0/0 0 module SM 1/1 0	<<>>
Step 4	end Example: Router(config-module-conn)# end	Returns you to privileged EXEC mode.

Examples

Router# configure terminal

Enter configuration commands, one per line.  End with CNTL/Z.

3900-ism(config)# connect test module se0/1 0 module se2/1 0

3900-ism(config-module-conn)# end

3900-ism# show version

*Feb 23 19:01:22.411: %SYS-5-CONFIG_I: Configured from console by cons        

3900-ism# show connections all

ID   Name               Segment 1                      Segment 2                     State       

==========================================================================================

2    test              Service-Module-GigEther0/1 0         Service-Module-GigEther2/1 0         
UP          

3900-ism# show running interface se0/0 

Building configuration...

Current configuration : 305 bytes

!

interface Service-Module-GigEther0/0

 ip address 30.0.0.1 255.255.255.0

 load-interval 30

 service-module backplane ip address 20.0.0.2 255.255.255.0

 service-module ip address 30.0.0.2 255.255.255.0

 !Application: FNDN Running on ISM

 service-module ip default-gateway 30.0.0.1

 hold-queue 60 out

end

3900-ism# show running interface se2/0

Building configuration...

Current configuration : 342 bytes

!

interface Service-Module-GigEther2/0

 ip address 100.0.0.1 255.255.255.0

 service-module fail-open

 service-module external ip address 150.0.0.1 255.255.255.0

 service-module backplane ip address 200.0.0.2 255.255.255.0

 service-module ip address 100.0.0.2 255.255.255.0

 service-module ip default-gateway 100.0.0.1

 hold-queue 60 out

end

3900-ism# show running interface se0/1

Building configuration...

Current configuration : 59 bytes

!

interface Service-Module-GigEther0/1

 no ip address

end

3900-ism# show running interface se2/1

Building configuration...

Current configuration : 59 bytes

!

interface Service-Module-GigEther2/1

 no ip address

end

Establishing a VLAN Connection

Follow these steps to establish a VLAN connection.

SUMMARY STEPS

1. enable

2. configure terminal

3. connect connection-name module module1 vlan vlan-id module module2

4. exit

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Router> enable	Enables privileged EXEC mode. •Enter your password if prompted.
Step 2	configure terminal Example: Router# configure terminal	Enters global configuration mode.
Step 3	connect connection-name module module1 vlan vlan-id module module2 Example: Router(config)# connect connection1 module GigabitEthernet2/0 vlan 100 module GigabitEthernet3/0	Creates the connection identified as connection-name between the GE slot Module1, the vlan-id, and the GE slot Module2. After this command is issued, the router enters module configuration mode.
Step 4	exit Example: Router(config-module-conn)# exit	Exits module configuration mode. After exiting module configuration mode, the connection establishment begins.

Examples

The example below shows the creation of a connection between two GE interfaces:

Router(config)# connect connection1 module gi2/0 vlan 10 module gi3/0

Router(config-module-conn)# connect connection2 module gi3/0 vlan 5 module gi4/0

Router(config-module-conn)# exit

Troubleshooting Tips

In addition to the system error messages listed in the "System Error Messages for the connect Command" section, the following commands can help troubleshoot NME connections:

•show connection all

•show connection id connection-id

where connection-id is in the range of 0 to 10000

•show connection name connection-name

•show service-module status—If a connection has successfully been established to an NME slot, this command will display the output "Interface GigabitEthernet <port_number> is connected to BACKPLANE."

Deactivating a HIMI Connection

Follow these steps to deactivate a connection between two GE modules.

SUMMARY STEPS

1. enable

2. configure terminal

3. no connect connection-name

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Router> enable	Enables privileged EXEC mode. •Enter your password if prompted.
Step 2	configure terminal Example: Router# configure terminal	Enters global configuration mode.
Step 3	no connect connection-name Example: Router(config)# no connect connection1	Removes the connection specified by connection-name.

Configuration Examples for Cisco High-Speed Intrachassis Module Interconnect

This section contains the following examples:

•Sample Connection Between an SFP GE Port and a GE NME Slot

•Sample Connection Between Two GE NME Slots

Sample Connection Between an SFP GE Port and a GE NME Slot

The following sample output from a router configuration file shows a connection between the GE port on an SFP module and a GE slot on an NME:

Router# show running-config

.

.

.

interface GigabitEthernet0/0

 mac-address 0002.0022.2222

 ip address 192.168.0.2 255.255.255.0

 load-interval 30

 duplex auto

 speed auto

 media-type rj45

.

.

.

interface GigabitEthernet4/0 
ip address 192.168.4.1 255.255.255.0 
! 
ip classless 
ip route 10.10.0.0 255.255.0.0 1.3.0.1 
! 
ip http server 
! 
connect connection-1 module GigabitEthernet0/0 0 module GigabitEthernet4/0 0 
.

.

---

Note If the speed and duplex setting for g0/0 in SFP mode is speed=1000 and duplex=full, autonegotiation is in forced mode and autonegotiation is turned off. For all other mode settings of speed or duplex for SFP, autonegotiation is turned on.

If speed=1000 and duplex=full modes are specified for both g0/0 and g0/1 interfaces in copper mode (RJ-45), autonegotiation is still turned on. This is considered to be in forced mode for speed=1000. This occurrence is per the Annex 28D.5 extensions required for clause 40 (1000-BASE-T) IEEE 802.3.

When the speed and duplex modes are forced for 10/100, and full or half modes are forced for g0/0 and g0/1 interfaces, autonegotiation is turned off. If the interfaces are not in forced mode for 10/100 speeds, then autonegotiation will be turned on.

---

Sample Connection Between Two GE NME Slots

The following sample output from a router configuration file shows a connection between two GE slots on an NME:

Router# show running-config

.

.

interface GigabitEthernet4/0 
ip address 192.168.4.1 255.255.255.0 
! 
ip classless 
ip route 10.10.0.0 255.255.0.0 1.3.0.1 
! 
ip http server 
! 
connect connection-1 module GigabitEthernet2/0 0 module GigabitEthernet4/0 0 

Additional References

The following sections provide references related to the Cisco High-Speed Intrachassis Module Interconnect (HIMI) feature.

Related Documents

Related Topic	Document Title
Hardware installation instructions for network modules	Cisco 2900 Series and 3900 Series Hardware Installation
General information about configuration and command reference.	Cisco 3900 Series, 2900 Series, and 1900 Series Integrated Services Routers Software Configuration Guide
Regulatory compliance information for Cisco 2900 series routers.	Regulatory Compliance and Safety Information for Cisco 2900 Series Integrated Services Routers
Regulatory compliance information for Cisco 3900 series routers.	Regulatory Compliance and Safety Information for Cisco 3900 Series Integrated Services Routers

Technical Assistance

Description	Link
The Cisco Technical Support website contains thousands of pages of searchable technical content, including links to products, technologies, solutions, technical tips, and tools. Registered Cisco.com users can log in from this page to access even more content.	http://www.cisco.com/techsupport

CCDE, CCENT, CCSI, Cisco Eos, Cisco Explorer, Cisco HealthPresence, Cisco IronPort, the Cisco logo, Cisco Nurse Connect, Cisco Pulse, Cisco SensorBase, Cisco StackPower, Cisco StadiumVision, Cisco TelePresence, Cisco TrustSec, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip Mino, Flipshare (Design), Flip Ultra, Flip Video, Flip Video (Design), Instant Broadband, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn, Cisco Capital, Cisco Capital (Design), Cisco:Financed (Stylized), Cisco Store, Flip Gift Card, and One Million Acts of Green are service marks; and Access Registrar, Aironet, AllTouch, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Lumin, Cisco Nexus, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, Continuum, EtherFast, EtherSwitch, Event Center, Explorer, Follow Me Browsing, GainMaker, iLYNX, IOS, iPhone, IronPort, the IronPort logo, Laser Link, LightStream, Linksys, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, PCNow, PIX, PowerKEY, PowerPanels, PowerTV, PowerTV (Design), PowerVu, Prisma, ProConnect, ROSA, SenderBase, SMARTnet, Spectrum Expert, StackWise, WebEx, and the WebEx logo are registered trademarks of Cisco and/or its affiliates in the United States and certain other countries.

All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1002R)