для Cisco Cisco 1900 2900 3900 Series 4-Port Gigabit Ethernet HS-WIC with PoE

The dual primary PDP contexts feature is supported on the EHWIC3.7G (HSPA+)/3.5G (HSPA) cards.

Each PDP context is the separate data link over common 3G data connection. It has its own IP address 
and its own data and QoS profile. For each PDP context, the new IOS cellular interface is created once 
the EHWIC is initialized in the system. In addition to that, each cellular interface has a corresponding 
TTY line. This is similar to HWICs with multiple ports. 

The EHWIC3.7G (HSPA+)/3.5G (HSPA) cards have Cellular 0/<ehwic_slot>/0, Cellular 
0/<ehwic_slot>/1, IOS interfaces. The last number in the triple numbering scheme is the port number.

The multiple cellular interfaces in these 3G HWIC cards behave independently. Any of them can be used 
to establish data connection. However, only the first interface (for example, Cellular 0/<ehwic_slot>/0), 
can be used to exercise the full set of modem AT commands using the Reverse Telnet feature. 

The HSPA/HSPA+ cellular modem allows you to configure up to16 profiles. The QoS profile configured 
for an interface is selected by the ATDT*98*#<profile_number>#...“CONNECT” (HSPA modem) or 
AT!SCACT=1,<profile_number>...“OK” (HSPA+ modem) command in the chat script corresponding 
to a cellular interface. You must use a different data profile for each cellular interface.

If all the three interfaces are used, you must create three separate chat scripts in the router configuration.

Simple Management Network Protocol (SNMP) development and use is centered around the MIB. An 
SNMP MIB is an abstract database, a conceptual specification for information that a management 
application may read and modify in a certain form. 

This does not imply that the information is kept in the managed system in that same form. The SNMP 
agent translates between the internal data structures and formats of the managed system and the external 
data structures and formats defined for the MIB. 

The SNMP MIB is conceptually a tree structure with conceptual tables. For more informtaion on Cisco 
3G MIB, see the 

. Relative to this tree 

structure, the term MIB is used in two senses. In one sense, it is actually a MIB branch, usually 
containing information for a single aspect of technology, such as a transmission medium or a routing 
protocol.

A MIB used in this sense is more accurately called a MIB module and is usually defined in a single 
document. In the other sense, a MIB is a collection of such branches. Such a collection might comprise, 
for example, all the MIB modules implemented by a given agent or the entire collection of MIB modules 
defined for SNMP. 

A MIB is a tree where the leaves are individual items of data called objects. An object may be, for 
example, a counter or a protocol status. MIB objects are also sometimes called variables. 

MIBs can be classified into three categories:

IF MIBs—Describe interface statistics.

Cisco-Entity-Vendortype-OID-MIB.my—ENTITY-MIBs are used to provide general hardware type 
for both the EHWIC and the modem. CISCO-ENTITY-VENDORTYPE-OID-MIB assigns OIDs for 
Cisco components (including the HWICs and the modems). The OIDs are then used as the values of 
entPhysicalVendorType in the ENTITY-MIB.

Cisco 3G WAN MIBs—cellular or wireless-specific MIBs.