Slides on Nexus 3000

Hi,
Does anyone have some slides on Nexus 3000 ?
Best regards

Please Get in touch with your local Cisco Sales team , they should be able to help you with it.
Regards
Abijith Sharma V S

Similar Messages

Cisco Nexus 3000 ssh access

I have a Cisco Nexus 3172T in a small environment running System version: 6.0(2)U3(1). I am using a vlan as management access, i.e. vlan100 is on every device and is using for snmp/ssh access. On the same switch I have one non-switchport (routed) port (eth1/6 in this case) connecting to a remote datacenter. I am able to SNMP poll and ping the vlan100 interface on the switch from everywhere, and I am able to SSH login while I am connected on any of the VLANs that are known to the switch. My problem comes when trying to access (SSH) the switch from the remote datacenter location (SNMP/Ping also works from the remote location). The only way to SSH access the switch from the remote location is only if I SSH in on the routed port (i.e. eth 1/6).
I am not using the dedicated management port on the switch (nor I have any plans in the future). I am also running very plain config, a few switchports, one routed port, and the default control-plane policy (which is only policy pps). There are the ACLs on the VTY.
Am I running into a known bug or is there some configuration requirement to allow this ?
thanks
dragan

Its not in a VRF or anything like that is it?
Also have you tried setting the ssh source interface to be vlan 100.
http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus3000/sw/security/6x/b_Cisco_n3k_Security_Config_6x/b_Cisco_n3k_Security_Config_6x_chapter_0110.html#task_4AFC76AF5CD04C728EF30CB15EAE2655

Qustion have 2 nexus 3000 setup in vPC domain, want to add the 3rd one, How is this done?

If some can supply a sample of what the 3rd Nexus Switch configuration.
Nexus-1 Config
vrf context management
ip route 0.0.0.0/0 192.168.50.1
vlan 1
vlan 10
name ISCSI_VLAN
vpc domain 1
peer-keepalive destination 192.168.50.242
peer-gateway
interface port-channel1
switchport mode trunk
switchport trunk allowed vlan 10
spanning-tree port type network
flowcontrol receive on
flowcontrol send on
no negotiate auto
vpc peer-link
interface Ethernet1/52/1 - 4
switchport mode trunk
switchport trunk allowed vlan 10
flowcontrol receive on
flowcontrol send on
channel-group 1 mode active
Nexsus-2 Config
vrf context management
vlan 1
vlan 10
name ISCSI_VLAN
no vpc domain 1
peer-keepalive destination 192.168.50.241
peer-gateway
vpc domain 1
peer-keepalive destination 192.168.50.241 vrf management
peer-gateway
interface port-channel1
switchport mode trunk
switchport trunk allowed vlan 10
spanning-tree port type network
flowcontrol receive on
flowcontrol send on
no negotiate auto
vpc peer-link
interface Ethernet1/51/1 - 4
switchport mode trunk
switchport trunk allowed vlan 10
flowcontrol receive on
flowcontrol send on
channel-group 1 mode active

VPC can only have 2 members
HTH

Ask the Expert: Different Flavors and Design with vPC on Cisco Nexus 5000 Series Switches

Welcome to the Cisco® Support Community Ask the Expert conversation. This is an opportunity to learn and ask questions about Cisco® NX-OS.
The biggest limitation to a classic port channel communication is that the port channel operates only between two devices. To overcome this limitation, Cisco NX-OS has a technology called virtual port channel (vPC). A pair of switches acting as a vPC peer endpoint looks like a single logical entity to port channel attached devices. The two devices that act as the logical port channel endpoint are actually two separate devices. This setup has the benefits of hardware redundancy combined with the benefits offered by a port channel, for example, loop management.
vPC technology is the main factor for success of Cisco Nexus® data center switches such as the Cisco Nexus 5000 Series, Nexus 7000 Series, and Nexus 2000 Series Switches.
This event is focused on discussing all possible types of vPC along-with best practices, failure scenarios, Cisco Technical Assistance Center (TAC) recommendations and troubleshooting
Vishal Mehta is a customer support engineer for the Cisco Data Center Server Virtualization Technical Assistance Center (TAC) team based in San Jose, California. He has been working in TAC for the past 3 years with a primary focus on data center technologies, such as the Cisco Nexus 5000 Series Switches, Cisco Unified Computing System™ (Cisco UCS®), Cisco Nexus 1000V Switch, and virtualization. He presented at Cisco Live in Orlando 2013 and will present at Cisco Live Milan 2014 (BRKCOM-3003, BRKDCT-3444, and LABDCT-2333). He holds a master’s degree from Rutgers University in electrical and computer engineering and has CCIE® certification (number 37139) in routing and switching, and service provider.
Nimit Pathak is a customer support engineer for the Cisco Data Center Server Virtualization TAC team based in San Jose, California, with primary focus on data center technologies, such as Cisco UCS, the Cisco Nexus 1000v Switch, and virtualization. Nimit holds a master's degree in electrical engineering from Bridgeport University, has CCNA® and CCNP® Nimit is also working on a Cisco data center CCIE® certification While also pursuing an MBA degree from Santa Clara University.
Remember to use the rating system to let Vishal and Nimit know if you have received an adequate response.
Because of the volume expected during this event, Vishal and Nimit might not be able to answer every question. Remember that you can continue the conversation in the Network Infrastructure Community, under the subcommunity LAN, Switching & Routing, shortly after the event. This event lasts through August 29, 2014. Visit this forum often to view responses to your questions and the questions of other Cisco Support Community members.

Hello Gustavo
Please see my responses to your questions:
Yes almost all routing protocols use Multicast to establish adjacencies. We are dealing with two different type of traffic –Control Plane and Data Plane.
Control Plane: To establish Routing adjacency, the first packet (hello) is punted to CPU. So in the case of triangle routed VPC topology as specified on the Operations Guide Link, multicast for routing adjacencies will work. The hellos packets will be exchanged across all 3 routers and adjacency will be formed over VPC links
http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5000/sw/operations/n5k_L3_w_vpc_5500platform.html#wp999181
Now for Data Plane we have two types of traffic – Unicast and Multicast.
The Unicast traffic will not have any forwarding issues, but because the Layer 3 ECMP and port channel run independent hash calculations there is a possibility that when the Layer 3 ECMP chooses N5k-1 as the Layer 3 next hop for a destination address while the port channel hashing chooses the physical link toward N5k-2. In this scenario,N5k-2 receives packets from R with the N5k-1 MAC as the destination MAC.
Sending traffic over the peer-link to the correct gateway is acceptable for data forwarding, but it is suboptimal because it makes traffic cross the peer link when the traffic could be routed directly.
For that topology, Multicast Traffic might have complete traffic loss due to the fact that when a PIM router is connected to Cisco Nexus 5500 Platform switches in a vPC topology, the PIM join messages are received only by one switch. The multicast data might be received by the other switch.
The Loop avoidance works little different across Nexus 5000 and Nexus 7000.
Similarity: For both products, loop avoidance is possible due to VSL bit
The VSL bit is set in the DBUS header internal to the Nexus.
It is not something that is set in the ethernet packet that can be identified. The VSL bit is set on the port asic for the port used for the vPC peer link, so if you have Nexus A and Nexus B configured for vPC and a packet leaves Nexus A towards Nexus B, Nexus B will set the VSL bit on the ingress port ASIC. This is not something that would traverse the peer link.
This mechanism is used for loop prevention within the chassis.
The idea being that if the port came in the peer link from the vPC peer, the system makes the assumption that the vPC peer would have forwarded this packet out the vPC-enabled port-channels towards the end device, so the egress vpc interface's port-asic will filter the packet on egress.
Differences: In Nexus 5000 when it has to do L3-to-L2 lookup for forwarding traffic, the VSL bit is cleared and so the traffic is not dropped as compared to Nexus 7000 and Nexus 3000.
It still does loop prevention but the L3-to-L2 lookup is different in Nexus 5000 and Nexus 7000.
For more details please see below presentation:
https://supportforums.cisco.com/sites/default/files/session_14-_nexus.pdf
DCI Scenario: If 2 pairs are of Nexus 5000 then separation of L3/L2 links is not needed.
But in most scenarios I have seen pair of Nexus 5000 with pair of Nexus 7000 over DCI or 2 pairs of Nexus 7000 over DCI. If Nexus 7000 are used then L3 and L2 links are required for sure as mentioned on above presentation link.
Let us know if you have further questions.
Thanks,
Vishal

Catalyst 3850 vs Nexus 3K

Hi ,
I have a question. If the only requirement for the DC is to have iSCSI for some servers , is it better to go for Nexus 3K or I should choose Cat 3850. Apparently with 10 gig uplinks Cat 3850 is more expensive. Can someone plz tell what would be the benefits of each in this scenario?
Fawad

Hi ,
Cat 3850 is mainly used for unify wired and wireless networks. Cisco Catalyst 3850 Switches, which combine wired and wireless by supporting wireless tunnel termination and full wireless LAN controller functionality.
In other hand , Nexus 3000 is datacenter top of the rack switch and low latency , unify data ad storage switch and well suited for your Iscsi requirement . so i would suggest nexus 3000 .
HTH
Regards,
VS.Suresh.
*Plz rate the usefull posts *

Adapter-fex Supported VICs and Nexus Switches

HI,
I am thinking of using C220M4 in standalone mode. I have been reading about adapter-fex and I am wondering which Cisco VIC supports adapter-fex and which Nexus Switch will support adapter-fex.
I am thinking of using a VIC1225 and Nexus 3000.
Thanks.

I believe that adaptor fex is supported only with Nexus 5k and N2k:
Network Adapter Virtualization Design (Adapter-FEX) with Cisco Nexus 5500 Switches and Cisco Nexus 2232 Fabric Extenders
http://www.cisco.com/c/en/us/products/collateral/switches/nexus-5000-series-switches/guide_c07-690080.html
http://www.cisco.com/c/en/us/products/collateral/switches/nexus-5000-series-switches/data_sheet_c78-657397.html

Question about Nexus 3548 vPC setup

Hi.
We have just installed our two first Nexus 3548 switches in our Catalyst environment. We want to set up a vPC domain between the Nexuses, to use for connections to storage and other equipment.
I have read the guide at http://www.cisco.com/c/en/us/products/collateral/switches/nexus-3000-series-switches/white_paper_c11-685753.html and tried setting it up. I created a vPC domain on both switches like this:
nexus1:
vpc domain 1
role priority 2000
system-priority 4000
peer-keepalive destination 192.168.105.40 source 192.168.105.39 vrf default
nexus2:
vpc domain 1
system-priority 4000
peer-keepalive destination 192.168.105.39 source 192.168.105.40 vrf default
The switches are connected with a port-channel consisting of 2x 10GE. The IP addresses above are the ones we use for managing the switches. When I configure the port-channel as "vpc peer-link", the vpc status looks OK:
vPC domain id                     : 1
Peer status                       : peer adjacency formed ok
vPC keep-alive status             : peer is alive
Configuration consistency status : success
Per-vlan consistency status       : success
Type-2 consistency status         : success
vPC role                          : primary
Number of vPCs configured         : 0
Peer Gateway                      : Disabled
Dual-active excluded VLANs        : -
Graceful Consistency Check        : Enabled
Auto-recovery status              : Disabled
vPC Peer-link status
id   Port   Status Active vlans
1    Po2    up     1,6,100,102,106
The problem I have is that I lose connection to nexus2 when I bring up the vPC. I can no longer access it on its IP (192.168.105.40). I cannot ping it from nexus1 either. The Nexus switches are connected to our core switches, which are Catalyst 6509. nexus1 is connected to coreswitch1 using a portchannel of 2xGE and nexus2 is connected to coreswitch2 the same way. A spanning-tree cost has been set on the uplink from nexus2, to make spanning tree block that uplink, and allow traffic between the nexuses to go over the 2x 10GE portchannel instead of over the core switches. I have attached a drawing of this.
Maybe I shouldn't use the management IP:s for peer keepalive? Does the peer keepalive need to be on a different physical link than the peer-link?
Regards,
Johan

We are not using the management ports for management, but an ordinary Vlan Interface in the default vrf, as seen below. We can of course change that and instead use the mgmt0 port if that is the best approach.
vrf context management
vlan configuration 1,100
vlan 1
vlan 100
name DMMgmtPriv
vpc domain 1
role priority 2000
system-priority 4000
peer-keepalive destination 192.168.105.40 source 192.168.105.39 vrf default
interface Vlan1
interface Vlan100
no shutdown
no ip redirects
ip address 192.168.105.39/23

Problem Display JQuery Script

Hi Gang,
Been wrestling with a JQuery script, getting it to display on this page for the main images:
http://72.29.76.51/~organica/index.html
Any insight to what I'm doing wrong is appreciated.
Here's the page code:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />

<title>Organica Natural Foods | Northvale, New Jersey</title>

<link href="main.css" rel="stylesheet" type="text/css" />
<link href="Spry-UI-1.7/css/Menu/basic/SpryMenuBasic.css" rel="stylesheet" type="text/css" />
<link href="s3slider.css" rel="stylesheet" type="text/css" />
<script src="js/jquery-1.6.4.min.js" type="text/javascript"></script>
<script src="js/s3Slider.js" type="text/javascript"></script>
<script type="text/javascript">
    $(document).ready(function() {
        $('#slider').s3Slider({
            timeOut: 3000
</script>
<script src="Spry-UI-1.7/includes/SpryDOMUtils.js" type="text/javascript"></script>
<script src="Spry-UI-1.7/includes/SpryDOMEffects.js" type="text/javascript"></script>
<script src="Spry-UI-1.7/includes/SpryWidget.js" type="text/javascript"></script>
<script src="Spry-UI-1.7/includes/SpryMenu.js" type="text/javascript"></script>
<script src="Spry-UI-1.7/includes/plugins/MenuBar2/SpryMenuBarKeyNavigationPlugin.js" type="text/javascript"></script>
<script src="Spry-UI-1.7/includes/plugins/MenuBar2/SpryMenuBarIEWorkaroundsPlugin.js" type="text/javascript"></script>
<style type="text/css">
/* BeginOAWidget_Instance_2141544: #MenuBar */
/* Settable values for skinning a Basic menu via presets. If presets are not sufficient, most skinning should be done in
    these rules, with the exception of the images used for down or right pointing arrows, which are in the file SpryMenuBasic.css
     These assume the following widget classes for menu layout (set in a preset)
    .MenuBar - Applies to all menubars - default is horizontal bar, all submenus are vertical - 2nd level subs and beyond are pull-right.
    .MenuBarVertical - vertical main bar; all submenus are pull-right.
    You can also pass in extra classnames to set your desired top level menu bar layout. Normally, these are set by using a preset.
    They only apply to horizontal menu bars:
        MenuBarLeftShrink - The menu bar will be horizontally 'shrinkwrapped' to be just large enough to hold its items, and left aligned
        MenuBarRightShrink - Just like MenuBarLeftShrink, but right aligned
        MenuBarFixedLeft - Fixed at a specified width set in the rule '.MenuBarFixedLeft', and left aligned.
        MenuBarFixedCentered - - Fixed at a specified width set in the rule '.MenuBarFixedCentered',
                        and centered in its parent container.
        MenuBarFullwidth - Grows to fill its parent container width.
    In general, all rules specified in this file are prefixed by #MenuBar so they only apply to instances of the widget inserted along
    with the rules. This permits use of multiple MenuBarBasic widgets on the same page with different layouts. Because of IE6 limitations,
    there are a few rules where this was not possible. Those rules are so noted in comments.
#MenuBar {
    background-color:#003300;
    font-family: "Lucida Sans Unicode", "Lucida Grande", sans-serif; /* Specify fonts on on MenuBar and subMenu MenuItemContainer, so MenuItemContainer,
                                                MenuItem, and MenuItemLabel
                                                at a given level all use same definition for ems.
                                                Note that this means the size is also inherited to child submenus,
                                                so use caution in using relative sizes other than
                                                100% on submenu fonts. */
    font-weight: bold;
    font-size: 12px;
    font-style: normal;
    padding:0;
/* Caution: because ID+class selectors do not work properly in IE6, but we want to restrict these rules to just this
widget instance, we have used string-concatenated classnames for our selectors for the layout type of the menubar
in this section. These have very low specificity, so be careful not to accidentally override them. */
.MenuBar br { /* using just a class so it has same specificity as the ".MenuBarFixedCentered br" rule bleow */
    display:none;
.MenuBarLeftShrink {
    float: left; /* shrink to content, as well as float the MenuBar */
    width: auto;
.MenuBarRightShrink {
    float: right; /* shrink to content, as well as float the MenuBar */
    width: auto;
.MenuBarFixedLeft {
    float: left;
    width: 100%;
.MenuBarFixedCentered {
    float: none;
    width: 100%;
    margin-left:auto;
    margin-right:auto;
.MenuBarFixedCentered br {
    clear:both;
    display:block;
.MenuBarFixedCentered .SubMenu br {
    display:none;
.MenuBarFullwidth {
    float: left;
    width: 100%;
/* Top level menubar items - these actually apply to all items, and get overridden for 1st or successive level submenus */
#MenuBar .MenuItemContainer {
    padding: 0px 0px 0px 0px;
    margin: 0;
     /* Zero out margin on the item containers. The MenuItem is the active hover area.
                For most items, we have to do top or bottom padding or borders only on the MenuItem
                or a child so we keep the entire submenu tiled with items.
                Setting this to 0 avoids "dead spots" for hovering. */
#MenuBar .MenuItem {
    padding: 0px 8px 0px 8px;
    background-color:transparent;
    border-right: 1px solid #FFF;
    border-left: 1px solid #FFF;
#MenuBar .MenuItemFirst {
    border-style: none none none none;
#MenuBar .MenuItemLast {
    border-style: none solid none none;
#MenuBar .MenuItem .MenuItemLabel{
    text-align:left;
    line-height:1.4em;
    color:#ffffff;
    background-color:transparent;
    padding: 6px 15px 6px 15px;
    width: 10em;
    width:auto;
.SpryIsIE6 #MenuBar .MenuItem .MenuItemLabel{
    width:1em; /* Equivalent to min-width in modern browsers */
/* First level submenu items */
#MenuBar .SubMenu .MenuItem {
    font-family: Arial, Helvetica, sans-serif;
    font-weight: bold;
    font-size: 12px;
    font-style: normal;
    background-color:transparent;
    padding:0px 8px 0px 0px;
    border-width:1px;
    border-color: #cccccc #cccccc #cccccc #cccccc;
    /* Border styles are overriden by first and last items */
    border-style: solid solid none solid;
#MenuBar .SubMenu .MenuItemFirst {
    border-style: solid solid none solid;
#MenuBar .SubMenu .MenuItemFirst .MenuItemLabel{
    padding-top: 6px;
#MenuBar .SubMenu .MenuItemLast {
    border-style: solid solid solid solid;
#MenuBar .SubMenu .MenuItemLast .MenuItemLabel{
    padding-bottom: 6px;
#MenuBar .SubMenu .MenuItem .MenuItemLabel{
    text-align:left;
    line-height:1em;
    background-color:transparent;
    color:#ffffff;
    padding: 6px 12px 6px 5px;
    width: 7em;
/* Hover states for containers, items and labels */
#MenuBar .MenuItemHover {
    background-color: transparent;
    border-color: #cccccc #cccccc #cccccc #cccccc;
#MenuBar .MenuItemWithSubMenu.MenuItemHover .MenuItemLabel{
    background-color: transparent; /* consider exposing this prop separately*/
    color: #999999;
#MenuBar .MenuItemHover .MenuItemLabel{
    background-color: transparent;
    color: #999999;
#MenuBar .SubMenu .MenuItemHover {
    background-color: #003300;
    border-color: #cccccc #cccccc #cccccc #cccccc;
#MenuBar .SubMenu .MenuItemHover .MenuItemLabel{
    background-color: transparent;
    color: #999999;
/* Submenu properties -- First level of submenus */
#MenuBar .SubMenuVisible {
    background-color: #003300;
    min-width:0%; /* This keeps the menu from being skinnier than the parent MenuItemContainer - nice to have but not available on ie6 */
    border-color: #ffffff #ffffff #ffffff #ffffff;
    border-width:0px;
    border-style: none none none none;
#MenuBar.MenuBar .SubMenuVisible {/* For Horizontal menubar only */
    top: 100%;    /* 100% is at the bottom of parent menuItemContainer */
    left:0px; /* 'left' may need tuning depending upon borders or padding applied to menubar MenuItemContainer or MenuItem,
                    and your personal taste.
                    0px will left align the dropdown with the content area of the MenuItemContainer. Assuming you keep the margins 0
                    on MenuItemContainer and MenuItem on the parent
                    menubar, making this equal the sum of the MenuItemContainer & MenuItem padding-left will align
                    the dropdown with the left of the menu item label.*/
    z-index:10;
#MenuBar.MenuBarVertical .SubMenuVisible {
    top: 0px;
    left:100%;
    min-width:0px; /* Do not neeed to match width to parent MenuItemContainer - items will prevent total collapse */
/* Submenu properties -- Second level submenu and beyond - these are visible descendents of .MenuLevel1 */
#MenuBar .MenuLevel1 .SubMenuVisible {
    background-color: #003300;
    min-width:0px; /* Do not neeed to match width to parent MenuItemContainer - items will prevent total collapse*/
    top: 0px;    /* If desired, you can move this down a smidge to separate top item''s submenu from menubar -
                that is really only needed for submenu on first item of MenuLevel1, or you can make it negative to make submenu more
                vertically 'centered' on its invoking item */
    left:100%; /* If you want to shift the submenu left to partially cover its invoking item, you can add a margin-left with a
                negative value to this rule. Alternatively, if you use fixed-width items, you can change this left value
                to use px or ems to get the offset you want. */
/* IE6 rules - you can delete these if you do not want to support IE6 */
/* A note about multiple classes in IE6.
* Some of the rules above use multiple class names on an element for selection, such as "hover" (MenuItemHover) and "has a subMenu" (MenuItemWithSubMenu),
* giving the selector '.MenuItemWithSubMenu.MenuItemHover'.
* Unfortunately IE6 does not support using mutiple classnames in a selector for an element. For a selector such as '.foo.bar.baz', IE6 ignores
* all but the final classname (here, '.baz'), and sets the specificity accordingly, counting just one of those classs as significant. To get around this
* problem, we use the plugin in SpryMenuBarIEWorkaroundsPlugin.js to generate compound classnames for IE6, such as 'MenuItemWithSubMenuHover'.
* Since there are a lot of these needed, the plugin does not generate the extra classes for modern browsers, and we use the CSS2 style mutltiple class
* syntax for that. Since IE6 both applies rules where
* it should not, and gets the specificity wrong too, we have to order rules carefully, so the rule misapplied in IE6 can be overridden.
* So, we put the multiple class rule first. IE6 will mistakenly apply this rule. We follow this with the single-class rule that it would
* mistakenly override, making sure the misinterpreted IE6 specificity is the same as the single-class selector, so the latter wins.
* We then create a copy of the multiple class rule, adding a '.SpryIsIE6' class as context, and making sure the specificity for
* the selector is high enough to beat the single-class rule in the "both classes match" case. We place the IE6 rule at the end of the
* css style block to make it easy to delete if you want to drop IE6 support.
* If you decide you do not need IE6 support, you can get rid of these, as well as the inclusion of the SpryMenuBarIEWorkaroundsPlugin.js script.
* The 'SpryIsIE6' class is placed on the HTML element by the script in SpryMenuBarIEWorkaroundsPlugin.js if the browser is Internet Explorer 6. This avoids the necessity of IE conditional comments for these rules.
.SpryIsIE6 #MenuBar .MenuBarView .MenuItemWithSubMenuHover .MenuItemLabel /* IE6 selector */{
    background-color: transparent; /* consider exposing this prop separately*/
    color: #999999;
.SpryIsIE6 #MenuBar .MenuBarView .SubMenu .MenuItemWithSubMenuHover .MenuItemLabel/* IE6 selector */{
    background-color: transparent; /* consider exposing this prop separately*/
    color: #999999;
.SpryIsIE6 #MenuBar .SubMenu .SubMenu /* IE6 selector */{
    margin-left: -0px; /* Compensates for at least part of an IE6 "double padding" version of the "double margin" bug */
/* EndOAWidget_Instance_2141544 */
</style>
<script type="text/xml">

</script>


</head>
<body bgcolor="#17321A">
<div id="outerWrapper">
<div id="header"><img src="media/header.jpg" width="960" height="160" alt="organica title" /></div>
<div id="navbar">
    <ul id="MenuBar">
      <li> <a href="index.html">Home</a></li>
      <li> <a href="kitchen.html">Kitchen</a>
      <ul>
          <li> <a href="menus.html">Menus</a></li>
          <li> <a href="catering.html">Catering</a></li>
      </ul>
      </li>
      <li> <a href="juicebar.html">Juice Bar</a></li>
      <li> <a href="produce.html">Produce</a></li>
      <li> <a href="supplements.html">Supplements</a></li>
      <li> <a href="grocery.html">Grocery</a>
      <ul>
          <li> <a href="packaged.html">Packaged Goods</a></li>
          <li> <a href="refrigerated.html">Refrigerated</a></li>
          <li> <a href="frozen.html">Frozen Foods</a></li>
          <li> <a href="glutenfree.html">Gluten Free</a></li>
      </ul>
      </li>
      <li> <a href="bodycare.html">Body Care</a></li>
      <li> <a href="events.html">Events</a></li>
      <li> <a href="contact.html">Contact</a>
      <ul>
          <li> <a href="directions.html">Directions</a></li>
          <li> <a href="employment.html">Employment</a></li>
      </ul>
      </li>
      </ul>
    <script type="text/javascript">
// BeginOAWidget_Instance_2141544: #MenuBar
var MenuBar = new Spry.Widget.MenuBar2("#MenuBar", {
      widgetID: "MenuBar",
      widgetClass: "MenuBar MenuBarFullwidth",
      insertMenuBarBreak: true,
      mainMenuShowDelay: 100,
      mainMenuHideDelay: 200,
      subMenuShowDelay: 200,
      subMenuHideDelay: 200
// EndOAWidget_Instance_2141544
    </script>
</div>
<div id="contentWrapper">
    <div id="sidebar">
      <h2>Get Your Organica Loyalty Card<br />
        <img src="media/loyalty.jpg" width="200" height="129" alt="loyalty" /></h2>
      <hr width="90%" size="1" />
      <p>
        <style>
.link,
.link a,
.signupframe
    color: #000000;
    font-family: Arial, Helvetica, sans-serif;
    font-size: 13px;
    .link,
    .link a {
        text-decoration: none;
    .signupframe {
        border: 0px solid #000000;
        background: #ffffff;
.signupframe .required {
    font-size: 10px;
    </style>
      </p>
      <form method="post" action="https://app.icontact.com/icp/signup.php" name="icpsignup" id="icpsignup8190" accept-charset="UTF-8" onsubmit="return verifyRequired8190();" >
        <input type="hidden" name="redirect" value="http://organicanaturalfoods.com/thanks.html" />
        <input type="hidden" name="errorredirect" value="http://www.icontact.com/www/signup/error.html" />
        <div id="SignUp">
          <h2>Sign-up for our Organica e-News<br />
            Receive coupons, event info, and more! </h2>
          <table width="200" align="center" class="signupframe" border="0" cellspacing="0" cellpadding="5">
            <tr>
              <td align="center"><input type="text" name="fields_email" /></td>
            </tr>
            <input type="hidden" name="listid" value="70490" />
            <input type="hidden" name="specialid:70490" value="HHBU" />
            <input type="hidden" name="clientid" value="971128" />
            <input type="hidden" name="formid" value="8190" />
            <input type="hidden" name="reallistid" value="1" />
            <input type="hidden" name="doubleopt" value="0" />
            <tr>
              <td><div align="center">
                <input type="submit" name="Submit" value="Submit" />
              </div></td>
            </tr>
          </table>
        </div>
      </form>
      <script type="text/javascript">
var icpForm8190 = document.getElementById('icpsignup8190');
if (document.location.protocol === "https:")
    icpForm8190.action = "https://app.icontact.com/icp/signup.php";
function verifyRequired8190() {
if (icpForm8190["fields_email"].value == "") {
    icpForm8190["fields_email"].focus();
    alert("The Email field is required.");
    return false;
return true;
    </script>
      <p></p>
      <p>
<iframe src=
"http://www.facebook.com/plugins/likebox.php?href=http%3A%2F%2Fwww.facebook.com%2FOrganicaN aturalFood&width=250&colorscheme=light&show_faces=true&border_color&stream=false&header=fa lse&height=258" scrolling="no" frameborder="0" style="border:none; overflow:hidden; width:250px; height:258px;" allowTransparency="true"></iframe>
      </p>
    </div>

    <div id="content">
      <div id="s3slider">
   <ul id="s3sliderContent">
      <li class="s3sliderImage">
          <img src="media/front_1.jpg" />
          <span>Welcome to Organica!</span>
      </li>
      <li class="s3sliderImage">
          <img src="media/front_2.jpg" />
          <span>Welcome to Organica!</span>
      </li>
      <div class="clear s3sliderImage"></div>
   </ul>
</div>
    </div>
    
    <div id="footer">
      <a href="index.html">Home</a> | <a href="about.html">About Us</a> | <a href="links.html">Links</a> | <a href="directions.html">Directions</a> | <a href="employment.html">Employment</a> | <a href="contact.html">Contact Us</a><br />
    All contents ©2011 Organica Natural Foods | Site Design: <a href="http://nowagenewmedia.com" target="_blank">Now Age New Media</a></div>
</div>
</div>
</body>
</html>

Usually, the reason why a widget does not work is because the support files are not-present/corrupt/out-of-date.
Try using
<script type="text/javascript" src="http://ajax.googleapis.com/ajax/libs/jquery/1.4.2/jquery.min.js"></script>
<script type="text/javascript" src="http://s3slider-original.googlecode.com/svn/trunk/s3Slider.js"></script>
it may help. The jQuery version can be changed to a more modern one.
Gramps

Support for C 'n' Q with CG-revision Athlon 64

Recently I bought a MSI K8T FSR motherboard and an Athlon 64 3000+, CG-revision. The new system is very stable and fast, the processor seems to be correctly identified, the only problem is Cool and Quiet isn't working.
I've installed clean copy's of Windows XP and Windows 2000, installed all latest software (corecenter etc), biosses and drivers, configured power management in Windows and enabled the feature in the bios, installed the special processor driver/software but still the clockspeed seems to be locked. The AMD cpuinfo tool and the msi corecenter both report a constant clockspeed of 2000 Mhz when run in Windows 2000 and a constant speed of 1600Mhz when run in XP. Heavy benchmarking or let the pc idling for 15 minutes, clockspeeds won't change. The constant 1600 Mhz reading in Xp is especially starnge, according the to AMD whitepaper this isn't a speedstepping for the processor, it should be switching between 1000/1800/2000Mhz. (see http://www.amd.com/us-en/assets/content_type/white_papers_and_tech_docs/30430.pdf , page 9, at column ADA3000AEP4AR)
In the release notes, it says support for the CG-revision of the processor is added in the last bios version, but C 'n' Q for Cg is still to come?
In a dutch forum, I'm not the only one encountering this problem, so I suspect it's not a standalone case.
The other hardware in my system, just for the reference: zalman 7000A cooler, nexus 3000 psu, 40 GB maxtor harddisk, geforce 2 MX, 512 MB PC3200 Kingston mem.

Quote
Originally posted by IceOnFire
Ironic that we take so much effort in making our pc's slower :-). For me too the automatic clockdown was a major reason to buy the Athlon 64. The "special extentions" I referred to are the AMD processor driver (downloadable from amd.com)
That worked! I went to the AMD site you mentioned, more specifically, this page, and downloaded the last program on the bottom of the page. After a restart, vwaa-la! 800 MHz! Never thought I'd be so happy to see my new machine run slower than my old machine.
Anyway, it works now... thanks for the help ... hope you get yours working too.

No ifIndex table when querying via SNMP

Hello, looking for suggestions before opening up a TAC case.
Just received a Nexus 3000 with NX-OS 6.0(2)U2(1) and when I attempt to walk the ifTable via SNMP the ifIndex table is not present. Walking the ifIndex table itself results in "IF-MIB::ifIndex = No Such Instance currently exists at this OID". show interface snmp-ifindex is fine and the rest of the ifTable displays properly.
My switch config is just a basic RO community with no ACL's or anything yet. A pair of the same switches with NX-OS 5.0(3)U5(1a) display the table no problem.
Any suggestions, or has anyone else seen this?

Did you navigate the FireFox plugin to the DB file that is in the Simulator app bundle:
/Users/YOURUSERID/Library/Application Support/iPhone Simulator/User/Applications/SYSTEMGENERATED_NAME/YOURAPP.app
or
/Users/YOURUSERID/Library/Application Support/iPhone Simulator/User/Applications/SYSTEMGENERATEDNAME/Documents
Message was edited by: xnav

DCNM-SAN supporting FI

Using DCNM-SAN with UCS (2.1.2a); I created on all FC devices (MDS and N5k) a user "dcnmuser" with netadmin rights. I also created a snmp v3 user "dcnmuser" with UCSM. Then I did a fabric discovery with DCNM-SAN; I see the fabric, MDS, N5k and FI, however, the FI have a red arrow, which means not manageable.
Q. what could be wrong ? or is this really supported ?

Understood, thanks Robert
We only want to monitor UCS-FI with DCNM-SAN.
The release notes 6.1.2
http://www.cisco.com/en/US/docs/switches/datacenter/sw/6_x/dcnm/release/notes/dcnm_6_1_relnotes.html
are quite misleading:
Introduction
Cisco Data Center Network Manager combines the management of Ethernet and storage networks into a single dashboard to help network and storage administrators manage and troubleshoot health and performance across the following product families that run Cisco NX-OS software:
•Cisco MDS 9500 Series Multilayer Directors and Cisco MDS 9200 and 9100 Series Multilayer Switches
•Cisco Nexus 1000V Series Switches and Cisco Nexus 1010 Virtual Services Appliance
•Cisco Nexus 2000 Series Fabric Extenders
•Cisco Nexus 3000, 4000, 5000, and 7000 Series Switches
•Cisco Catalyst 6500 Series Switches
•Cisco UCS 6100 and 6200 Series Fabric Interconnects
•Cisco FireWall Service Module (FWSM)
Cisco DCNM-SAN Release 6.1(1b) and later releases do not support Cisco Nexus 5000 Series switches and UCS devices running Cisco NX-OS Release 4.1(3) or an earlier release.
However, Table 9 Hardware Features Supported by Cisco DCNM Release 6.1
doesn't show UCS FI !

Slideshow: flash between pix

i have a very simple slideshow controled through xml and
actionscript ... but between the images i have an anoying flash
every time ... even when the pix are loaded!
check out an example
frame-eleven.com/newyork/dummy
and heres the script:
slides_xml = new XML();
slides_xml.onLoad = startSlideShow;
slides_xml.load("slides.xml");
slides_xml.ignoreWhite = true;
// Show the first slide and intialize variables
function startSlideShow(success) {
if (success == true) {
rootNode = slides_xml.firstChild;
totalSlides = rootNode.childNodes.length;
firstSlideNode = rootNode.firstChild;
currentSlideNode = firstSlideNode;
currentIndex = 1;
updateSlide(firstSlideNode);
// Updates the current slide with new image and text
function updateSlide(newSlideNode) {
imagePath = newSlideNode.attributes.jpegURL;
loadMovie(imagePath, targetClip);
// Event handler for 'Next slide'
setInterval(next,3000);
function next() {
nextSlideNode = currentSlideNode.nextSibling;
if (nextSlideNode == null) {
currentIndex = 1;
currentIndex++;
updateSlide(firstSlideNode);
currentSlideNode = firstSlideNode;
} else {
currentIndex++;
updateSlide(nextSlideNode);
currentSlideNode = nextSlideNode;
is there any solution to get rid of the flash and to preload
the pix?
thanks a lot
best
florian

The link you provided is for a tutorial, and it appears to be a fairly basic approach to one, so you should be able to follow through that tutorial to get the effect that you say it has that you want, and it even includes the option to download the file so that you can learn from it. If you cannot follow that tutorial then you should search Google for others... there are likely plenty of them around... just search using terms like "AS3 slideshow tutorial" (or substitute "AS2" for "AS3" if that's what you plan to use).

Dealing with JavaScript conflicts [was: javascript]

Is there something in Dreamweaver to fix Javascript conflicts? I got two scripts that are conflicting and won't work unless I diable one. So is there anything in dreamweaver to fix this?
[Subject line edited by moderator for clarity]

Assuming that both use the same framework (jQuery?), you should be able to merge them like this:
$(document).ready(function(){
$("#ajax-contact-form").submit(function(){
     var str = $(this).serialize();
     $.ajax({
     type: "POST",
     url: "contact.php",
     data: str,
     success: function(msg){
       $("#note").ajaxComplete(function(event, request, settings){
          if(msg == 'OK') // Message Sent? Show the 'Thank You' message and hide the form
            result = '<div class="notification_ok">Your message has been sent. Thank you!</div>';
            $("#fields").hide();
          else
            result = msg;
          $(this).html(result);
     return false;
$('#slider').s3Slider({
     timeOut: 3000
$('#slider1').s3Slider({
     timeOut: 4000
$('#slider2').s3Slider({
     timeOut: 5000

Ultra low latency switch

Hi,
what condition/when we need a ultra low latency switch(nexus 3000)?
thanks

Hello, Wendy.
Ultra low latency are usually configurable and sometimes in modes (such as in Nexus 3500 switches). Is this for your existing Nexus setup or a new deployment? Let me know if you have additional concerns or e-mail ([email protected]) me directly. Kind regards.

Difference between Port Channel and VPc

Hi Friends,
Could you please provide the difference between Port Channel and VPC.
Regards,
Zaheer

Read :)
http://www.cisco.com/c/en/us/products/collateral/switches/nexus-3000-series-switches/white_paper_c11-685753.html
Virtual PortChannel Technology
Virtual PortChannels (vPCs) allow links that are physically connected to two different Cisco® switches to appear to a third downstream device to be coming from a single device and as part of a single PortChannel. The third device can be a switch, a server, or any other networking device that supports IEEE 802.3ad PortChannels.
Cisco NX-OS Software vPCs and Cisco Catalyst® Virtual Switching Systems (VSS) are similar technologies. For Cisco EtherChannel technology, the term “multichassis EtherChannel” (MCEC) refers to either technology interchangeably.
vPC allows the creation of Layer 2 PortChannels that span two switches. At the time of this writing, vPC is implemented on the Cisco Nexus® 7000 and 5000 Series platforms (with or without Cisco Nexus 2000 Series Fabric Extenders).

Slides on Nexus 3000

Similar Messages

Maybe you are looking for